5,597,138 Members 43,539 Now Online
XDA Developers Android and Mobile Development Forum

Did anyone's TWRP become broken after updating to 4.4.2?

Tip us?
 
urbanman2004
Old
#1  
Junior Member - OP
Thanks Meter 0
Posts: 20
Join Date: Sep 2013
Default Did anyone's TWRP become broken after updating to 4.4.2?

Did anyone's TWRP become broken after updating to 4.4.2? Thought I'd ask because everytime I attempted to gain access to Recovery Mode, I would get an error (it said something like "No connecrtion"). I had to manually flash TWRP with Wugs and was able to successfully gain access to Recovery Mode again.
Nexus 7, 32GB (2012) / Samsung Galaxy S4 (Sprint)
 
enderwiggin13
Old
#2  
enderwiggin13's Avatar
Junior Member
Thanks Meter 1
Posts: 2
Join Date: Dec 2007
Quote:
Originally Posted by urbanman2004 View Post
Did anyone's TWRP become broken after updating to 4.4.2? Thought I'd ask because everytime I attempted to gain access to Recovery Mode, I would get an error (it said something like "No connecrtion"). I had to manually flash TWRP with Wugs and was able to successfully gain access to Recovery Mode again.
I've not updated my Nexus 7 to KitKat yet, but I just noticed on my Nexus 5 that TWRP is broken after updating to the 4.4.2 OTA. I don't get the "No connection" error, I just get the little dead android icon with the red exclamation point. Too bad I'm at work and won't be able to re-flash it until I get home.

You're not alone.
The Following User Says Thank You to enderwiggin13 For This Useful Post: [ Click to Expand ]
 
bftb0
Old
#3  
Senior Member
Thanks Meter 774
Posts: 2,120
Join Date: Feb 2010
Quote:
Originally Posted by urbanman2004 View Post
Did anyone's TWRP become broken after updating to 4.4.2? Thought I'd ask because everytime I attempted to gain access to Recovery Mode, I would get an error (it said something like "No connecrtion"). I had to manually flash TWRP with Wugs and was able to successfully gain access to Recovery Mode again.

Lacking any and all details about how you upgraded, I would have to say that is to be expected. The OTAs usually directly overwrite the recovery with a new version of the stock recovery.

Moreover, the most recent OTA used that "/system/recovery-from-boot.p" patch file and associated script "/system/etc/install-recovery.sh" mechanism that automatically overwrites the recovery by patching the boot partition image; I think this happens either on every boot (or maybe during a clean shutdown).

So, not having noticed that, I flashed a custom recovery & booted the stock ROM... and next time I rebooted into recovery, I was back at the stock recovery ... WTF?, right?

I renamed those files to stop that from happening. I think some of the recoveries are aware of this and perform similar tricks on your behalf when they "install root" for you, but if you continue to get your recovery overwritten by stock, this is the place to look.


FYI I capture a full nandroid backup of every new stock release, whether or not I plan on using stock. I set them aside (copy them to a PC) so that they are always available.

I do this by:

- TiBu user app & data backup
- make a nandroid backup of my current ROM
- restore a nandroid backup of the prior release of the pure Stock ROM including it's matching stock recovery
- take the OTA and apply it (note everything is COMPLETELY, 100% stock during this operation)
- soft-boot a custom recovery via fastboot ("fastboot boot ...")
- make a nandroid backup of the new pure Stock ROM, including it's matching stock recovery

- flash a custom recovery and either restore a different ROM, or root the stock ROM and move forward with TiBu


This may seem like a lot of work, but it preserves maximum flexibility and safety:

(a) I can roll back to pure stock (any version!) any time I please from my archive of stock nandroid backups.
(b) I never - ever - have problems with OTA installation (including hazardous things like bootloader installs)
(c) I never need to go begging on the internet "please anybody, can you send me file "xxxx" from the stock release "xyz" ? I already have them - all of them.**

hope that helps


** note that TWRP's ".win" files are just tar archives. You don't even need to restore prior ROMs to pluck out individual stock ROM files.
"I'm gonna start coding placebo apps. That way I will be sure that the complaints are real and the praises hollow."
The Following User Says Thank You to bftb0 For This Useful Post: [ Click to Expand ]
Tags
4.4.2, kit kat, root toolkit, twrp, wugs
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes