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

Root [Recovery] TWRP 2.8.6.0

Looking at porting some TWRP themes but most are for 2.6.3.1 and 2.7.X.X I'll look at them and see what differences are as we currently have 2.6.3.0 :D
 
I believe if your coming from a different ROM besides the first beta cm11 posted recently then you should format everything except for external SD, boot, and recovery. If updating cm11 with the newer build then you don't have to wipe anything.
 
Would like to make note to anyone else who has never used TWRP as opposed to CWM...
Dont try to restore cwm backups! They are not cross compatible.
On the subject at hand, TWRP is amazing! I have it on all of my devices and glad to finally have it on my AWE. Great job phenom!

Someone correct me if I'm wrong, but I'm pretty sure PhilZ can restore both CWM and TWRP backups as well as make backups in both formats. ;)
 
Someone correct me if I'm wrong, but I'm pretty sure PhilZ can restore both CWM and TWRP backups as well as make backups in both formats. ;)
If it were more stable and less buggy...for me the format, back up and restore speed of twrp is worth losing my old backups lol. I think Philz has promise though just needs more work/refinement.
 
Hey Phen, I have reason to believe that TWRP could be causing issues with writing the boot partition in some phones, which could potentially cause people some big problems if they freak out and do all the wrong things at the wrong times, Lol

The problems could be caused by a compatibility issue between CM11, TWRP and the solo boot.img itself. As it seems that the stock boot.img flashes along with the Rom just fine. Solo boot images appear to flash in TWRP correctly without error, but then cause the phone to be unable to boot. I am able to flash solo boot images with Philz recovery, however obviously can't flash CM11 with it, which then leads to the possibility of the problem just being a CM11/Kernel compatibility issue, probably specific to certain phones. I could attempt to leave the custom boot.img in the boot partition and then flash TWRP and then CM11 to see if it'll boot the boot.img with CM11 if it has already been flashed in Philz recovery.
 
Hey Phen, I have reason to believe that TWRP could be causing issues with writing the boot partition in some phones, which could potentially cause people some big problems if they freak out and do all the wrong things at the wrong times, Lol

The problems could be caused by a compatibility issue between CM11, TWRP and the solo boot.img itself. As it seems that the stock boot.img flashes along with the Rom just fine. Solo boot images appear to flash in TWRP correctly without error, but then cause the phone to be unable to boot. I am able to flash solo boot images with Philz recovery, however obviously can't flash CM11 with it, which then leads to the possibility of the problem just being a CM11/Kernel compatibility issue, probably specific to certain phones. I could attempt to leave the custom boot.img in the boot partition and then flash TWRP and then CM11 to see if it'll boot the boot.img with CM11 if it has already been flashed in Philz recovery.
I flash boot images all the time without error. Why are you flashing other boot images when there is only one compatible with cm11?
 
I flash boot images all the time without error. Why are you flashing other boot images when there is only one compatible with cm11?

Ummm, oh ....I didn't know. It worked for me before. Ooops :p

...wait, how the hell are you flashing mad boot images all the time IN TWRP if only one is compatible with CM11?
 
all the sudden I can't get in recovery but can boot all way up when I tryvto get in recovery all I get is green android and red light on how van I fix please help
 
all the sudden I can't get in recovery but can boot all way up when I tryvto get in recovery all I get is green android and red light on how van I fix please help

I do think it's worth looking into. TWRP acts wonky for me sometimes too when trying to boot into it. Maybe somehow it's getting corrupted. The most recent has been where it boots to a colourful like static lined screen, like something you would see on an old Sega if the cartridge wasn't inserted all the way. My best recommendation for you and I use it as my back up plan to save my ass (if I still have a bootable ROM) anyhow download Rashr root recovery tools flasher, from the play store and open up your recovery.zip file with your own file explorer and extract the recovery.img. The Rashr app will then allow you to flash that recovery.img. You should be good to go.
 
tryed that didn't work I used that tool and flashed cwm then flashed twrp in cwm now I'm ready to go thanks great minds think alike lok:)
 
I do think it's worth looking into. TWRP acts wonky for me sometimes too when trying to boot into it. Maybe somehow it's getting corrupted. The most recent has been where it boots to a colourful like static lined screen, like something you would see on an old Sega if the cartridge wasn't inserted all the way. My best recommendation for you and I use it as my back up plan to save my ass (if I still have a bootable ROM) anyhow download Rashr root recovery tools flasher, from the play store and open up your recovery.zip file with your own file explorer and extract the recovery.img. The Rashr app will then allow you to flash that recovery.img. You should be good to go.

I don't know if there are other causes that make it happen, but I know I always get the "wonky" screen when booting to TWRP for the first time when changing between cm11 and anything based on stock, also happens when flashing the other direction. The only reason this happens for me I believe, is because the read location for the internal TWRP folder is changing.
 
I don't know if there are other causes that make it happen, but I know I always get the "wonky" screen when booting to TWRP for the first time when changing between cm11 and anything based on stock, also happens when flashing the other direction. The only reason this happens for me I believe, is because the read location for the internal TWRP folder is changing.

Ahhh, dude... That's a really good theory, which may explain where my original problem with Data Encryption started, because I only noticed problems occurring after flashing back and forth like you said.
 
Back
Top Bottom