I installed the Nexus Root Toolkit v1.9.4 onto my PC and followed all the steps to update my kitkat Nexus to 5.0.
All was going well until 1 minute into my Nexus getting updated my battery died and it powered off (I didn't realised I was on 3% or so battery). So now when I switch it on I can’t get passed the fastboot mode screen and nothing gets found when I plug it into my laptop. Also when I try to re-run the Nexus Root Toolkit v1.9.4 it says it can’t find the ADB.
Is there any way to save my Nexus 7?
Related
Hello All,
I've got my nexus 7 about a week. The first day i used the nexus toolkit 2.0.0 to root and unlock the bootloader of the tablet so I can use a flash drive. I haven't flashed any custom rom on the tablet. Just now i looked at my nexus 7 and it's not responding (the battery is 100% not empty). Just a black screen. When i plug him in the computer, the computer doesnt recognize him and when i plug him in the AC he just doesn;t want to run.
Please help me!
Question: What should I do to try to resuscitate my ASUS Nexus 7 WiFi version?
Immediate Problem:
1) Tablet will not start up - absolutely no signs of life when holding power button alone (up to 20 sec), OR power & vol down buttons.
2) Tablet does not show the battery charging icon when connected to AC charger - screen remains blank.
Events prior to no boot/charge problem.
Tablet successfully running Android V4.2.1
I installed NRT from XDA forums - see INTRODUCING THE GOOGLE NEXUS 7 TOOLKIT
Successfully rooted device
Successfully executed Nandroid full system image via NRT
Got notification a few days ago android 4.2.2 OTA available so I agreed to apply it
I saw messages during upgrade saying the tablet had been upgraded
A message appeared on tablet saying something like "Optimizing applications" and it seemed to ork its way through the 100 or so apps I had installed.
This check became stuck on app no #98
I held down power button until the device shut off (suspect this could be part root cause)
The tablet never woke up after that.
I now receive an error message from Windows when connect tablet via USB cable saying there is a fault with device.
The up to date NRT just gets stuck and no longer recognises the tablets serial number no NRT commands seem to work. (restore etc)
What I do next?
Try going into the device manager and uninstall the drivers for your nexus 7 or try updating them by installing the drivers of the nexus 7 toolkit
Sent from my Nexus 7 running Android 4.2.2
No power up or USB connection
I tried to uninstall the drivers, scan for new hardware etc no improvement in position.
I have also re-applied the ADB drivers again latest NRT - no improvement.
The fact the tablet no longer shows the charging battery icon when plugged in to AC charger suggests to me I have a bigger problem than just loss of USB driver recognition/connectivity.
I have a Nexus 7 16 gb and I installed the Nexus 7 toolkit and followed instructions, installed drivers, device manager shows Android Phone-Android ADB Interface.
I reboot and toolkit shows devices attached with a serial number ADB mode but it says "offline" but I know the device is not offline I have it opened USB debugging mode is on as is Unkown sources ticked.
The device is unlocked and was rooted with stock 4.1.1 and superuser privileges but after a Google upgrade 4.2.2 I have lost root and superuser.
I was trying to back up all my apps with the toolkit but cannot work out how to get to android mode and the offline issue.
Any ideas please.
Solved
Solved - I had to remove the Nexus drivers twice not sure why it took 2 times But a reinstall and reboot gave me access to the device and resolved my problems
My nexus 7 was on 4.2.1 and receive a notification to update to 4.3. It got stuck on no command. Now I cannot get it back even after I wipe data or do anything. I've tried to use NRT to get it running but apparently it requires the usb debug mode to be on and I didn't have this on before the crash. Is there any way I can get this thing up back to factory without having usb debug mode on or can I turn this mode on via command line some how? TIA.
Wugs toolkit can get it back to stock. I'd imagine. I was in similar situation and it saved me.
Sent from my Nexus 7 using Tapatalk now Free
I also have this problem, stock unrooted 4.2.2, and I just opend it. First time turning it on, went to the update to 4.3, and stuck on the big X, tried factory reset but nothing.
Im going to try Wugs toolkit, because usb debugging is also off
Sent from my SGH-T999 using Tapatalk 4
Hi All
I have developed a problem with my Nexus 7 which I have been trying to sort for a bit and don't seem to be getting anywhere. Here is a bit of back ground, sorry it is so long!
I have a Nexus 7 (2012) which while using decided to shut down and will no longer boot up, it got stuck in a boot loop. It is not USB debugged or had any custom recovery on it. I have however managed to get the bootloader unlocked.
I tried to restore it manually following the guide on here but I could not get it to recognise the device despite following every step carefully. The computer (running on Windows 7) sees the Nexus now as it didn't when it first crashed. I have downloaded WugFresh 1.9.9 and tried to restore it from there and it looks like it is working but it now gets stuck on writing system. It does everything to this point fine. I have tried different USB ports, cables and someone else tried it on a different computer (running Windows XP) and he got stuck at the same point.
Can anyone suggest anything else I can do to try and restore my Nexus as I'm at a bit of a loss as to what to do next.
Thanks in advance
Vaughan