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

Root I think I messed up :/

D

Dudditz

Android Enthusiast
Wondering if any of you guys could help me out here?

By the way, if this is the wrong section for this, apologies and feel free to move?

Nexus 7, 16gb, rooted with stock 4.1.2. I have not edited the build.prop, still using the 4.1.2 Keyboard, Gmail etc.

So, nothing changed other than unlocked/rooted.

I have superSU pro and have 'Survival Mode' enabled, which is basically and OTA Rootkeeper (I am sure you already know this...)

When we got the OTA to 4.1.2, it worked no problem, survival mode worked and I kept root and custom recovery.

So this morning I get a notification to upgrade to 4.2, which I done. It restarted, and installed with no errors etc, then comes the Google screen with the unlocked padlock... and it stayed this way for an hour, so I am assuming it is borked?

I restarted it, same again, so rebooted into the bootlaoder menu. Going into recovery shows the android dude on his back, red triangle ! etc, so I gather my custom recovery is gone.

So the question is, where to go from here, and is there a walkthrough I can use to resuce this (I am techy enough minded, but given the state it is in, loathed to make it worse down to sheer stupidity)?

Any help would be much appreciated guys.

BTW - I used Wugs Toolkit to root, so that is all set up with drivers etc, can that be used now to recover?
 
Timely question: I rooted mine with WUG and updated to 4.2 last night (I only rooted to get TBU). Everything seems to work fine, I re-rooted, but when I go into the Recovery part of the bootloader I get the Red Triangle Dude.

SInce I can reboot it normally and, as I said all else seems fine, I'm not worried about it. Suspect it's trying to tell me there's something wrong somewhere. Just curious.
 
I'm guessing the update pushes stock recovery over your custom recovery and that's what went wrong. Try using wugs to install twrp, the open source recovery or whatever it's called and that should fix it for both of you so you can boot into recovery again.
 
Sorted.

Used wugs toolkit to roll back to stock unrooted and then proceeded to update to 4.1.2 and then 4.2, then went on to root manually via adb and fast boot.

Simple and took around half an hour all in all.

Worst part was the complete wiping of the tab and having to set up again but at least it is now working.
 
Teknologic said:
I'm guessing the update pushes stock recovery over your custom recovery and that's what went wrong. Try using wugs to install twrp, the open source recovery or whatever it's called and that should fix it for both of you so you can boot into recovery again.
Click to expand...
Did you try this first?
 
@tek I was asking the guy you were giving the advice too. It was solid. That way you don't spend hours reinstalling.
 
Teknologic said:
I'm guessing the update pushes stock recovery over your custom recovery and that's what went wrong. Try using wugs to install twrp, the open source recovery or whatever it's called and that should fix it for both of you so you can boot into recovery again.
Click to expand...

If you have custom recovery, the OTA will fail.
 
You must log in or register to reply here.
Back
Top Bottom