• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root True Recovery

OptimusSlime

Well-Known Member
So... I was messing around today and realized that PlayfulGod's Touch CWM can be accessed by holding Vol Up and Power at boot. This means no more unbrick method. We can just put an "Update.zip" and boot from it... right? I'm super excited, hopefully not prematurely.
 
Well now I would say its a good week. We have an almost fully functional CM10, and a recovery we can access when bricked. No more laptop! No more unbrick method! This being said thank you to everyone who has put in work and made solutions to our issues. You guys are amazing!
 
Well now I would say its a good week. We have an almost fully functional CM10, and a recovery we can access when bricked. No more laptop! No more unbrick method! This being said thank you to everyone who has put in work and made solutions to our issues. You guys are amazing!

You can still brick. It is still not permanently installed.
 
You can still brick. It is still not permanently installed.


While this is true, something like a Morningcall error can now be resolved lickity split. CWM seems to inhabit two folders, Clockwork and 0. Not sure why I added that other than to say try not to delete them ;-)
 
While this is true, something like a Morningcall error can now be resolved lickity split. CWM seems to inhabit two folders, Clockwork and 0. Not sure why I added that other than to say try not to delete them ;-)

The installation of CM10 causes the install of the 2nd init recovery to work with key combo, not running CWM alone ;)
 
The installation of CM10 causes the install of the 2nd init recovery to work with key combo, not running CWM alone ;)


I am by no means a Dev, but I love logic and computers. Since someone mentioned that the phone looks at both SD and Ext SD during boot, I thought I would try something. Note that I am running KATANA, not a CM10 build. I am using the touch recovery. I just MOVED the O and Clockwork folders from SD to my external, hit REBOOT RECOVERY, and was amazed to see the CWM Rec still function. This means ( I think) that even if I brick or erase certain parts of my SD that I can still run the Katana.zip (which I renamed update.zip and placed on my Ext SD along with the O and Clockwork folders. May still be a way to make it brick but at this point it seems less likely.

EDIT!!! While you do NOT need CM10 as a ROM for the Vol UP + Power key combo to work, the CWM files placed in data/app and data/data CANNOT be moved to Ext SD and be used. This means that anything that erases your data folder or returns it to "stock" ( no touch rec) would disable the recovery. I do not know of any way to make the whole damn program boot from ExtSD, which would be amazing lol.
 
I am by no means a Dev, but I love logic and computers. Since someone mentioned that the phone looks at both SD and Ext SD during boot, I thought I would try something. Note that I am running KATANA, not a CM10 build. I am using the touch recovery. I just MOVED the O and Clockwork folders from SD to my external, hit REBOOT RECOVERY, and was amazed to see the CWM Rec still function. This means ( I think) that even if I brick or erase certain parts of my SD that I can still run the Katana.zip (which I renamed update.zip and placed on my Ext SD along with the O and Clockwork folders. May still be a way to make it brick but at this point it seems less likely.

EDIT!!! While you do NOT need CM10 as a ROM for the Vol UP + Power key combo to work, the CWM files placed in data/app and data/data CANNOT be moved to Ext SD and be used. This means that anything that erases your data folder or returns it to "stock" ( no touch rec) would disable the recovery. I do not know of any way to make the whole damn program boot from ExtSD, which would be amazing lol.
That might be because recovery isnt on the sdcard, internal or external. The clockwork dir is where your backups are placed and where RM places stuff dl'd thru it.

The 2nd-init recovery gets placed in system.xbin and a tar (recovery.tar) and they are severval scripts that control it (one that hijacks boot, unpacks the tar, loads the contents into ramdisk, etc etc). ;)
 
Back
Top Bottom