[Q] Cannot restore Nexus 7 - Nexus 7 Q&A, Help & Troubleshooting

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

Related

Need Help Unbricking Nexus 7

The problem is I can't unbrick and restore my nexus to stock rom.
I can't boot the device and I'm only able to boot to bootloader. However, my computer doesn't recognize the nexus. It keeps saying Window cannot recognize it whenever I plug my tablet to the computer in bootloader. I tried uninstall and reinstall driver several times, but none of them seems to work . ----> That means I can't even use adb to restore the phone simply because my tablet is not recognized in window.
Is there anyway to fix this problem? I really need your helps as soon as possible.
Thank you for reading !
Get to bootloader. Then use Wugs toolkit, open advanced options. On the very left is something like "temp boot to recovery". Once that boots it to recovery, ADB should work. It did for me. I was in some trouble last night and got out by this. If you know how to use adb/fastboot commands, you should be good. And I uninstalled my drivers and when I plugged it in the device automagically reloaded the drivers. But you have to do it a few times. Had to do it in bootloader, recovery, and another point. Anytime it asks to load drivers/etc do it.
I can't boot to recovery through Wug Tool Kit. It keeps saying Fastboot device was not found >"<
By the way, whenever I connnected my device to computer, the bootloader freezes :|
What were you doing before you go into this situation?
I was on Glazed Jelly Bean rom and wanted to go back to stock rom. I used nexus 7 toolkit to do all the work for me. However, there was something wrong like the toolkit didnt extract the stock img right or something like that, my tablet got bootloop, and what happened next was what i had been telling you guys.
Best bet is if somehow you could get into recovery or get adb working. Might want to uninstall drivers and install again and reboot computer. I would suggest using this thread and flash things manually back to stock. http://forum.xda-developers.com/showthread.php?t=1907796 but you would need adb working.
When you power off device and use volume and power can you get it to go into boot loader then plugged into computer try to get to recovery or adb.
Consider deleting the drivers from Windows after uninstalling them otherwise Windows may try to be "clever" and reinstall the bad driver when you plug the device in. The Nexus 7 drivers from Asus can be downloaded here and Google's USB drivers are here
Travisdroidx2 said:
Best bet is if somehow you could get into recovery or get adb working. Might want to uninstall drivers and install again and reboot computer. I would suggest using this thread and flash things manually back to stock. http://forum.xda-developers.com/showthread.php?t=1907796 but you would need adb working.
When you power off device and use volume and power can you get it to go into boot loader then plugged into computer try to get to recovery or adb.
Click to expand...
Click to collapse
What if I couldn't get adb working?
I tried everything and windows still doesn't recognize my device in fastboot
Have you tried Nexus Root Toolkit v .1.5.4?
kiddo94 said:
I tried everything and windows still doesn't recognize my device in fastboot
Click to expand...
Click to collapse
try connecting to the usb port at the back of your computer
Paranoid flashed with the bricked kernel did this to me once right after the move to 4.1.2. Even with a full wipe and all the usual safety precautions it just stuck on bootloop forever and wouldn't let me in. I chalked it up as that's what I get for being the guy that's never satisfied with stock. I was unable to get my nexus7 fixed. I sent you a suggestion on pm though.
Never mind everyone. Thank you so much for your help.
I tried install the nexus 7's driver on another computer and it recognized my device in bootloader mode, and restore everything back to stock now. Thank you so much!!!!
Mine did that to the first time I tried. After I got it to work, the permissions were all messed up and I could not get it to download anything off the web and I was getting a playstore error 90% of the time as well. I finally just wiped everything on my tablet, installed the stock rom via N7 toolkit, then reflashed smooth rom, and all is working now. It may have been a bug with the older version of N7 toolkit, as I updated it before I reran everything.

[Q] Device Manager Error 43 + No ROM installed

I'm having one heck of a problem here. So I've got my Nexus 7, on stock Android, but rooted and unlocked.
I wanted to try Paranoid Android, so I installed the TeamWin Recovery using the Nexus Root Toolkit, then flashed the ROM and wiped cache/dalvik. I tried to boot into the new ROM, but it just stayed on the boot animation. So I looked up the issue, and the solution seemed to be return to stock Android, then flash Paranoid Android again.
So I tried to use the 'Flash Stock and unroot functionality' of the Nexus Root Toolkit, which proceeded fine until the copying of 'system' onto the device... This lasted for about an hour without progress, so I decided to try again with a different version of stock Android. This too didn't work.
So then I (foolishly) rebooted the tablet. But when I got back to fast boot, it didn't show up in Windows (on either of the two machines I have here, and with two cables that have both worked previously, in multiple USB ports). The specific error is that it shows up as an unknown device (which is fine) but also in the device manager there is error 43, which states that the USB has malfunctioned so it has stopped.
For that reason, it's impossible for me to connect it to a computer or even re(install) the proper drivers for it. And as it doesn't have a working OS, i can't get to ADB either. So right now I can't think of anything that will work - no fast boot, no recovery, no connection to a PC.
Any ideas?
Really, no ideas? Come on XDA Developers, you're my only hope <3
Hi there!
ive got the same issue and i can tell what is NOT working to fix this problem:
deleting ALL usb drivers from pc and installing adb drivers, windows troubleshoot and nrt
i'm just like confused but i think it's all windows fault, if i could i would trie on linux or any other pc os

Bricked & Unseen...

Ok, here goes my story.
Just a week ago from the date this was posted, I decided to update my recovery (TWRP) through ROM Installer. Surprisingly, I didn't see TWRP at all in the "Recoveries" section of the application. Stock, ClockworkMod Touch, regular Clockworkmod (no touch), and unofficial Clockworkmod were available - from what I can remember. I decided to use Clockworkmod (no touch) to install Paranoid Android. Coming from OmniROM, I factory reset and flashed the .zip.
Flashing ended in error with Status 7. A while before I had used ClockworkMod Touch to try another ROM and had no such issue. I ignored the error and restarted my tablet hoping that it would still boot fine. It rebooted, gave me the Google logo for about 5-10 seconds and automatically rebooted into recovery.
I saw a bypass for Status 7. Removing some lines from the updater-script was the solution. Having no access to my Nexus 7 storage, this bypass is unusable
I tried flashing a new recovery using flashboot fastboot. After verifying that I had my drivers installed (Universal ADB by Koush), I opened up adb in the command line (Windows) as an administrator. I could not see my device. I tried the drivers from Asus, multiple USB 2.0 ports, and a different USB cord, but same results. I tried on a different computer. Still no detection.
Systems used: Windows 8.1, Windows 7 (x64), Windows 7 (x86)
I tried using Wug's Toolkit and used Flash Stock + Unroot, since it didn't need USB Debugging enabled. Same results...
I also tried plugging in another Android phone (LG Optimus Dynamic II) to see if Windows would recognize it. Windows recognized it, installed drivers automatically, and was recognized in ADB immediately. This practically unknown phone (XDA doesn't have a section for it yet) could be recognized, but my world famous Nexus 7 2012 can't be seen.
I have absolutely no idea of what to do now...
Are you on the bootloader screen when trying to use fastboot?
PrizmaticSmoke said:
Are you on the bootloader screen when trying to use fastboot?
Click to expand...
Click to collapse
Yes. Every time I use fastboot, I am in the bootloader.
I'm not new to this at all, so say whatever you need to ^^
The main problem is my PC not recognizing my Nexus 7 through adb. Again, I have used multiple cables with no success.
The computer I am using for this runs Windows 7 x64. I have only tried using USB 2.0 ports to connect my tablet.
Thank you!
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
PrizmaticSmoke said:
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
Click to expand...
Click to collapse
Thank you so much for all of this! I'll need all the luck I can get...
By the way, I checked that softbrick option ^^!

[Q] Nexus 4 FUll Wipe Help

Had some great help already but still stuck. Here is the situation. Fully wiped my Nexus 4 and now I have no OS. No backup. Nothing. Phone will not connect to ANY computer I have tried. Used Wugs Toolkit to double and triple check drivers on three computers and still the phone does not connect. Is there ANY possible way to install a rom or stock on this phone without being able to get a computer to recognize it? I have access to TWRP but there is NOTHING to install or restore. HELP!

Nexus 7 Bricked?

I've been trying for a while to "fix" a 1st gen Nexus 7.
Been using the Nexus Root Toolkit from three different PCs with a bunch of different cables, same result.
Seems to get stuck on writing system. I've let it go for hours, only time it finishes is if the host PC goes to sleep and wakes up. My guess is that the USB recycle does something to make it think the write was successful. I've only been able to get it in fastboot.
Tried different stock roms, even the latest lollipop. I also tried the "fixed" 4.23 bootloader...
Before I throw it out, wondering if there's anything else I can try?

Categories

Resources