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

Root Rooted and rolled back to 4.4.4 and have a small problem

Outatime

Android Expert
Hello all,

Recently I purchased a lightly used Nexus 7 2012 WiFi that already had 5.1.1 installed. I've been doing just about everything in the book to try and eek some performance out of this and finally gave up. Last night I DL'ed Wug's root tool and went to work.

Unlocked the bootloader with no problem. Rooted with no problem. I decided to flash the latest AOKP (which is actually pretty old, but I remembered using that from my old Gal Nex days) which is where I ran into my first burp.

The OS seemed to flash correctly but got stuck on the loading screen. I let it go for a LONG time... I'd say in excess of 30 minutes. I finally gave up and power cycled it, which worked, but it went back to the same thing. I successfully used the soft brick recovery and was able to flash the SDK factory 4.4.4 image to the device and it's working perfectly. Actually, I can't believe how good it works compared to the sluggishness of 5.1.1, but that's a different subject.

Of course because I flashed a factory image, I lost root. I went back to Wug's tool, updated it to reflect that it was now on 4.4.4 KTU84P and tried to re-establish root. The bootloader is still unlocked. It said I needed to put it into USB debugging mode, which I had already done. It also said I needed to uninstall the old drivers and launched Device Manager. I did find one that was Other > Nexus and deleted it, but when I click root in Wug's it's still telling me there's an issue and wouldn't proceed.

I also rebooted my computer and tried again thinking I had to clear the driver from ROM and it still didn't work.

Any ideas of what I can try?
 
Have you tried flashing or soft-booting TWRP from a command-line prompt via fastboot? (I'd recommend soft-booting since if you don't need to keep TWRP installed then a soft-boot is the way to go)

If you were able to get Wug's to work once with restoring a factory image, then you should be able to manually do the fastboot commands.

c:\> fastboot devices

If you get/see your device's info (serial number) with the above command, then you should be good-to-go.

c:\> fastboot boot twrp-recovery.img

That's not the exact name of the current/latest version of TWRP of course, but just illustrates the command. That command "soft-boots" the given bootable image and does not flash (write) it to your device--keeping the stock recovery intact.

I guess you could simply be having a problem with the adb USB drives from Wug's if it's trying to push the UPDATE-SuperSU*.zip file over to your N7. But you can get around that by downloading that root package from a browser on your N7 when booted normally and then do the above fastboot stuff to get to the flash/install .zip function in TWRP.

I have seen the fastboot USB drivers work when the adb USB drivers don't want to... Also, disabling MTP seems to be trick to getting the adb USB connectivity to work (at least on my N5 anyways).

Does that make sense?
 
Thanks for the quick reply SA!

Yes, that make sense. I will have a go at that tonight when I get home from work. Hey speaking of MTP... I do recall seeing that on Wug's... for the life of me I can't find it in settings. Do you know where that is on Kit Kat?

Edit: Found it. Google is my friend.
 
No problem :).

I don't have my 2012 N7 here with me, either (am at work), but I'm pretty sure you should be able to find it in Settings -> Storage -> top-right corner of screen to find the 3 vertical dots (ellipses) to bring-up the USB computer connection menu -> toggle Media device (MTP) off and Camera (PTP) on.

^^^ That's just the generic path to get there on my N5...should be sort-of similar on the N7 (hopefully!).

Best of luck! Hopefully it's just that stupid MTP thing ;) :D.
 
I award you ten internets from my own personal stash.

I ran home at lunch, checked the box. I was rooted in about 4 minutes. LOL.

Thanks again SA!
 
Back
Top Bottom