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?
Related
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
A couple of weeks ago my N4 decided that it didn't want connect to my computer. I tried windows xp, 7, and osx. I tried 5 different usb cables that worked with other android phones just fine. I tried all usb ports on said computers. I've uninstalled and re-installed all drivers, using all the known methods. Then I noticed that I was getting terrible battery life. Like 5% gone in 20 minutes with all radios turned off and leaving it in my pocket. I was on the latest verison of PA with the latest verion of franco.kernel and I've had no previous problems with my phone.
So I thought maybe I did something to it like a bad flash, so i downloaded a stock 4.2.2 zip and flashed it (with gapps). The problem persisted. So I proceeded to wipe the phone in cwm in an act of desperation, and lo and behole I was then stuck with the same problem as before, but this time with no working os to boot to, and no way of connecting it to fastboot or adb in order to put any files on the sdcard/ flash it back to stock. I am, however, still able to boot into cwm and the bootloader. Then, thinking it might be a problem with the usb daughter board as whenever I tried to plug my phone into a computer it gave me this:"windows has stopped this device because it has reported problems. (code 43)", I ordered a replacement. Replacement came, I swapped them out, and absolutely nothing has changed. I tried uninstalling/deleting drivers and re-installing them just to make sure, but same results as before. Also, the N4 DOES charge when plugged into a power source like normal.
So the way I see it, I can either keep trying to replace parts, or one of you wonderful people know some crazy fix to my problem. If not, then I could go the other way, and attempt to brick the N4 even further in order to get it replaced (I.e. it's not possible to see whether or not it's unlocked/has a custom recovery). Also, I can enter "download mode" by holding down the volume buttons and connecting a usb cable, but windows still doesn't recognize the device.
[Q] Nexus 2012 doesn't turn on. I get "USB Device not recognized" when plugged in PC
fixed
Cocalarix said:
I was trying to install 4.4 and it got stuck at the sending 'boot' command. I tried a few times more, tried other drivers, same thing. It was in bootloader so I decided to restart it (this is the moment I regret). Since then I can't open it up. Tried the Vol buttons + Power for 20 secs, nothing works.
The only sign of life is when I connect it to a PC via USB. The PC shows me a Device not recognized error. Is there anything I can do?
It's a Nexus 2012 Wi-Fi 16 GB and I had 4.2.2 installed on it, but now everything is wiped out.
I found this: http://forum.xda-developers.com/showthread.php?t=2455927<br />
But I only made a backup with apps and user data with the Nexus Toolkit. I don't think I have the Blobs on that.
Also, the Nexus Toolkit tells me if I can't get to the bootloader, I might need to use ODIN, but I have no idea how to use that: http://www.andromint.com/download-odin-latest-version/
Anything I can do?
Click to expand...
Click to collapse
I'm in the same boat as you and I've been doing this stuff for years, do I have NO idea what I did. I was reimaging it back to 4.3 from 4.4 since Kit Kat broke flash videos for me.
As for ODIN, where you linked to is for Samsung devices. I don't know anything about ODIN, so not sure if that will help. It appears our devices are bricked. Whether they are hard or soft bricked, who knows. Also, since fastboot and adb cannot recognize our devices, ODIN doesn't do us any good even if it WERE for the Nexus 7.
I'm sending mine back into ASUS since it's still under warranty. At least, it's not a year old, but unlocking the bootloader has probably voided my warranty, but I have no other choice.
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
I know what your thinking another newb not installing drivers properly or hasn't changed to file transfer mode.... This is not the case. I been installing adb and USB drivers since the og droid.
I have a real problem here....
I been on custom ROMs and wanted to fastboot back to stock however none of my computers are detecting my phone... Tried on 2 windows 10 x64 and one windows 7 x64 with same result. None even pop up a notification or ding a sound that the phone has been plugged into it. Nothing in device manager either. The phone charges at least I have also tried 4 different cables granted 3 came in a bundle pack that I do not trust but reviews state although not full speed they should do data....
Now here is the kicker:
If I turn off my phone and boot to the bootloader my 3 computers detect a device has been connected but the drivers fail and say something about the device signature can't be recognized. I have tried disabling the device signature validation in windows 10 with no luck and also windows 7....
Tried manually installing the drivers but says not compatible with device hardware
At this point I'm baffled luckily I'm rooted twrp and can download files to install directly but I rely heavily on fastboot as my goto if something goes wrong I'll be hosed!
I did factory reset and even flashed another custom rom to see if it was the ROM I was using.
Please help if you have any ideas to try. I have yet another cord coming Friday just in case the offchanse the main went bad and the other three from the bundle pack are ****
Sending back to google I hope they don't mind the custom rom, unlocked bootloader and twrp recovery lol