{"id":104,"date":"2014-06-07T09:37:18","date_gmt":"2014-06-07T09:37:18","guid":{"rendered":"http:\/\/blog.catalystlogic.com.au\/?p=104"},"modified":"2026-03-01T01:44:18","modified_gmt":"2026-02-28T14:44:18","slug":"fighting-obsolescence-of-6-phones-with-cyanogenmod","status":"publish","type":"post","link":"http:\/\/54.253.247.134\/?p=104","title":{"rendered":"Fighting Obsolescence of 6 phones with Cyanogenmod"},"content":{"rendered":"<p>At about the same time a family member needed a new phone, some old units at work were getting thrown out. So i though i would grab them, and also go through my collection and see if i could update them all to the latest Cyanogenmod \u00a0or equivalent.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-105\" src=\"http:\/\/54.253.247.134\/wp-content\/uploads\/2014\/06\/Phones.jpg\" alt=\"Phones\" width=\"3264\" height=\"2448\" \/><\/p>\n<p>From Top Left<\/p>\n<ul>\n<li>Stock Android 2.3 on a Galaxy SII.<\/li>\n<li>Stock Android 4.1 on a Galaxy SII.<\/li>\n<li>Modded AOSP 4.1 Rom on a My Touch 4G Slide aka Doubleshot<\/li>\n<li>Stock Android 4.1 on a Galaxy Note (N7000).<\/li>\n<li>Stock Android Desire Z (Vision).<\/li>\n<li>Broken CM Rom on a Galaxy SII (Was given to me in the pictured looping boot state)<\/li>\n<\/ul>\n<p>Photo was taken after I had already loaded\u00a0Cyanogenmod on the\u00a0Note &amp; Doubleshot, while the Doubleshot was very straight forward as I had root &amp; ClockWorkMod already on it, the Note was one of the nastier I've encountered.<\/p>\n<h3>Galaxy Note N7000<\/h3>\n<p>The <a href=\"http:\/\/wiki.cyanogenmod.org\/w\/Install_CM_for_n7000\">Cyanogenmod instructions<\/a>\u00a0require a bit of USB\u00a0driver juggling via <a href=\"https:\/\/github.com\/pbatard\/libwdi\/wiki\/Zadig\">Zadig<\/a>, which I have used before on USB SDR Sticks &amp; USB Missle Launchers alike. This allowed\u00a0<a href=\"http:\/\/glassechidna.com.au\/heimdall\/\">Heimdall<\/a>\u00a0to talk to \u00a0the Note. Heimdall, which allowed me to avoid using <a href=\"http:\/\/forum.xda-developers.com\/sitesearch.php?q=ODIN\">Odin<\/a> for this particular Samsung phone, let me inject the recovery image into the device.<\/p>\n<p>Or at least it did eventually,<\/p>\n<pre class=\"theme:monokai lang:batch highlight:0 decode:true\">C:\\&gt;heimdall flash --kernel zImage --no-reboot\n\nHeimdall v1.4.0\n\nCopyright (c) 2010-2013, Benjamin Dobell, Glass Echidna\n\nThis software is provided free of charge. Copying and redistribution is\nencouraged.\n\nIf you appreciate this software and you would like to support future\ndevelopment please consider donating:\n\nInitialising connection...\nDetecting device...\nClaiming interface...\nSetting up interface...\n\nInitialising protocol...\nProtocol initialisation successful.\n\nBeginning session...\n\nSome devices may take up to 2 minutes to respond.\nPlease be patient!\n\nSession begun.\n\nDownloading device's PIT file...\nPIT file download successful.\n\nERROR: Partition \"kernel\" does not exist in the specified PIT.\nEnding session...\nReleasing device interface...<\/pre>\n<p>As this Note was bought at Android 2.3, and memories of the 3 or 4 tense reboots needed when I suggested she run the OTA Jellybean update popped into my head.<\/p>\n<p>The <a href=\"http:\/\/forum.cyanogenmod.com\/topic\/86804-issue-with-heimdall-partition-kernel-does-not-exist-in-the-specified-pit\/\">cyanogenmod forums<\/a>\u00a0mentioned stating KERNEL in uppercase. I have that a try and was told:<\/p>\n<pre class=\"theme:monokai lang:batch highlight:0 decode:true\">Initialising connection...\nDetecting device...\nClaiming interface...\nSetting up interface...\n\nInitialising protocol...\nERROR: Protocol initialisation failed!\n\nReleasing device interface...<\/pre>\n<p>As this seemed to error before even connecting, let alone looking for the Partition, I assumed this was the Downloader getting stuck issue on the How to Guide tips &amp; tricks section.<\/p>\n<p>Persistence payed off as a reboot of the PC and the device payed off.<\/p>\n<p>However, while Cyanogenmod\u00a0booted\u00a0without a hitch, from the depths of ROM hell spawned my next adversary...<\/p>\n<h3>Yellow Triangle on Boot<\/h3>\n<p>The yellow triangle with black exclamation mark pops up on the kernel boot screen when the device detects a modification to the kernel. Obviously a feature to avoid warranty repaired on rooted devices, I wanted to get rid of it, as while long out of warranty, it was just plain unsightly.<\/p>\n<p>Luckily for me <a href=\"http:\/\/chainfire.eu\/\">Chainfire<\/a>, one of the most respected developer in the community, has released a tool to fix this, <a href=\"http:\/\/forum.xda-developers.com\/sitesearch.php?q=Triangle%20away\">Triangle Away<\/a>.<\/p>\n<p>While there is no shortness of warnings, are you sure's, confirmation dialogs and telling you know in on uncertain terms, that is can brick your phone, one caught my eye. Advising me that SuperSU, Chainfire's Super User app is recommended. While SuperSU is a bit more feature rich, CM's opensource implementation does the job, and allows it to ship with the ROM.<\/p>\n<p>However, I was going to risk a bricking this far in. Just installing SuperSU did not meet the\u00a0criteira, and Triangle Away still used the CM root app when launching. However after loading SuperSU as a zip via recovery, the dialog didn't appear.<\/p>\n<p>After a few tense pauses during the process, by Triangle, was in fact away.<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>At about the same time a family member needed a new phone, some old units at work were getting thrown out. So i though i would grab them, and also go through my collection and see if i could update them all to the latest Cyanogenmod \u00a0or equivalent. From Top Left Stock Android 2.3 on <a class=\"read-more\" href=\"http:\/\/54.253.247.134\/?p=104\">...continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-104","post","type-post","status-publish","format-standard","hentry","category-android"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"http:\/\/54.253.247.134\/index.php?rest_route=\/wp\/v2\/posts\/104","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/54.253.247.134\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/54.253.247.134\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/54.253.247.134\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/54.253.247.134\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=104"}],"version-history":[{"count":1,"href":"http:\/\/54.253.247.134\/index.php?rest_route=\/wp\/v2\/posts\/104\/revisions"}],"predecessor-version":[{"id":233,"href":"http:\/\/54.253.247.134\/index.php?rest_route=\/wp\/v2\/posts\/104\/revisions\/233"}],"wp:attachment":[{"href":"http:\/\/54.253.247.134\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=104"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/54.253.247.134\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=104"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/54.253.247.134\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=104"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}