JB 4.20 available

[CBers]

Wow I didn't realize that there's a separate drop down on the right side of the screen

And multi user access.

[CBers]

Open Super SU and update the binaries and OTA Rootkeeper should see the Super SU app.

Where is that option? I have it installed but can't find where you update the binaries.

[S.Prime]

Did you check OTA RootKeeper before you ran the 4.2 update, to make sure all 4 boxes were checked and the Root was backed up?

[birdastrompgman]

Prime, yes I did, since I was expecting to lose root during the upgrade.

CBers, Super SU gave me a dialogue box asking if I wanted to update the binary when I tried to run it.  When I tried the update, the installation failed - repeatedly.

I chose to clean the system to re-download Super SU from Google Play.  It said it would take a few seconds, and would close the Super SU app if successful.  It wasn't successful.

So I went to Google Play, and uninstalled Super SU.  When that completed, instead of a choice to install the app, I got update and open options in GP.  I chose update, which took me to the Super SU update binary dialogue box.  Again, the installation failed.  Now I have no rooted apps showing in the Super SU apps tab. 

It looks like I'm going to have to re-root and restore, and/or reinstall apps manually.

[CBers]

Sorry to hear about your woes birdastrompgman.

I wonder if anyone else has tried.

[CBers]

Seems to be a DAYDREAM function under the DISPLAY settings.

Acts a bit like a screen saver on a PC.

Read here for more information.

[S.Prime]

Prime, yes I did, since I was expecting to lose root during the upgrade.

CBers, Super SU gave me a dialogue box asking if I wanted to update the binary when I tried to run it.  When I tried the update, the installation failed - repeatedly.

I chose to clean the system to re-download Super SU from Google Play.  It said it would take a few seconds, and would close the Super SU app if successful.  It wasn't successful.

So I went to Google Play, and uninstalled Super SU.  When that completed, instead of a choice to install the app, I got update and open options in GP.  I chose update, which took me to the Super SU update binary dialogue box.  Again, the installation failed.  Now I have no rooted apps showing in the Super SU apps tab. 

It looks like I'm going to have to re-root and restore, and/or reinstall apps manually.

Bird, weren't your running a custom ROM (Paranoid Android) and did you return to a stock ROM before the update? If not I suspect this is the source of your lost root.

S.Prime

[JayJ]

The only problem I had when updating was that I had previously turned the Asus keyboard to a user app to stop it refreezing so I could try it, had changed it back to a system app and refrozen it but the update zip wouldn't take stating that the fail was because of XT9IME. apk (Asus keyboard) so I replaced the apk and all was good.

Great thread CBers, your a true part of the community. A thumbs up I think...

[Gunner6101]

If it is at all relevant I installed the touch version of cwm available from rom toolbox pro and I noticed that when it was done and I hit reboot it went to another screen and informed me that root might be broken and would attempt to fix it I chose yes and it worked great for me... So for those still looking to upgrade if you haven't done so I recommend using that option if your worried about losing root

[birdastrompgman]

My tale of woe continues.  Prime, I did return to stock Android 4.1.2 before flashing the 4.2 ROM.  4.2 is running fine (I like the new scrolling owner info message).

I've lost the CWM custom recovery during the re-rooting attempt.

I couldn't get rooted, because Wugfresh's toolkit doesn't unlock the bootloader.  It flashes a quick message about that, but skips or fails the attempt.  Instead of getting an unlock option in the bootloader, it simply goes to the bootloader and reboots.  I had to grab a PrtScr capture of the message, and paste the screen capture into Paint, to be able to read the message.

[birdastrompgman]

I've tried changing the device type to Nexus 7 other, and N7 4.1.2, but that didn't help.  I've tried installing both the option #1 and option #2 device drivers, and that didn't help either.

[loociddreemr]

You can unlock the bootloader manually. In order to do so, you must have the fastboot drivers installed. These are included in the toolkit folder typically. Open the toolkit folder and then open a command window. You should be able to type "fastboot" and hit enter to see a list of commands. If you do not get a response, you are missing the drivers. Maybe download an older version of the toolkit.
If you do get a response, boot the N7 into fastboot mode and type into the command window "fastboot oem unlock" hit enter. When the device finishes use the command "fastboot reboot"

[bjs229]

Oh no. Not this again. Lol. I think I am going to wait for the OTA.
Unlock bootloader? So installing this update entails wiping your whole system? I'm lost again. I thought you could just flash it like a rom.

[CBers]

Great thread CBers, your a true part of the community. A thumbs up I think...

Thanks

[bjs229]

By the way, losing custom recovery with the toolkit happened last time with WF. I thought there would be a fix by now but I believe he suggested flashing the older bootloader.