Official 4.2 issues thread

[commodore128]

updated both versions of the nexus toolkits. still having problems with both. with wugs i can complete back up and re-boot but when i close the dialogue box and the backup should be pushed to my PC. i get another dialogue with error message --line 11245(file c:program files(x86)wugfresh development etc. error subscript used with non array variable. tried removing and re-installing to different director--same fault. with twrp i can make a back up but after completion and re-booting should go into recovery but goes into the page with the android on its side with red exclamation mark. on re-booting go into bootloader and load twrp recovery image it does not find the backup. anyone got any ideas. had no problems with 4.1.2

[birdastrompgman]

The dead Android bootloader is a known bug in the 4.2 recovery. The Nexus 7 Toolkit lets you revert to the previous 3.34 recovery, or you can install TWRP or another custom recovery.

The lost backup locations are a result of 4.2's new directory structure. It will be a while before the developers patch their programs. I heard TWRP has a new version (3.21?)  that finds its backup.

I push my Nandroid backups from my PC, and pull them there for storage using the Nexus 7 Toolkit. No issues with that method.

Sent from my Nexus 7 w/ Tapatalk 2 @ 49.6 mpg

[loociddreemr]

Without s tool kit, can you boot into TWRP? The android with the red exclamation mark is part of stock recovery. You need to make sure TWRP is installed correctly first, and will renter TWRP after a reboot.

Sent From my Razr Maxx (iKreaM.4.1.2.AOKP) via Tapatalk 2

[commodore128]

many thanks for info. thought for a while i was going mad. while waiting for 4.2 to get sorted may try another rom.


                                                      many thanks

                                                                  dave

[loociddreemr]

This is not just an issue with 4.2. The ability to enter recovery properly started with 4.0, and is not exclusive to the N7.

Sent From my Razr Maxx (iKreaM.4.1.2.AOKP) via Tapatalk 2

[bjs229]

I was getting the red droid. I flashed the new recovery with ROM toolbox and was fine ever since.

[birdastrompgman]

I push my Nandroid backups from my PC, and pull them there for storage using the Nexus 7 Toolkit. No issues with that method.

There is an issue with that method.  I tried a restore onto my new N7-16, running 4.2, and I pushed the backup files to sdcard/Clockworkmods, where CWM failed to find them.

[fxsarge]

So I still can't access play store or my G+ account and I heard if I remove my account and re add it that could fix the problem. Would I loose all my apps? (I know they will be in the cloud but I mean will they all be uninstalled loosing all of my in app purchases. )

[loociddreemr]

No, there will be no change to the apps or files on your device.

Sent From my Razr Maxx (iKreaM.4.1.2.AOKP) via Tapatalk 2

[fxsarge]

Fixed.

[bjs229]

What's fixed?

[fxsarge]

What's fixed?

My issue with connecting to Google servers.

[bjs229]

Three times now in the last day my location services has turned off by itself.

Sent from my Nexus 7 using Tapatalk 2

[techguy]

I'm on my second Nexus 7 (dont ask)
The first one I did the 4.2 update, and got poor battery life (five hours) and the Media server service was regularly hitting 45% (More than the screen!.
On my second one, I've left it on 4.1 and media server is only around 3-4%. I havent done a battery life check yet as I've only had it 12 hours. Is anybody else getting heavy media server use on 4.2?
I've googled around and it seems a lot of 4.2 users are getting it.

[birdastrompgman]

??  Media Services is a catch-all, with modules that might be called by a movie player, magazine or book reader, music player, etc.

If your N7 goes into battery hog heaven, regardless of its OS, the solution is to find and close the rogue app.

I'm not the lowest of the low, but I am the slowest of the slow (49.6 mpg over 38k miles in  Scion xB)