Database Users

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.

Help required - Bootloader only

Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks

herghost said:
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
Click to expand...
Click to collapse
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers

jombo2323 said:
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
Click to expand...
Click to collapse
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue

herghost said:
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
Click to expand...
Click to collapse
you are 100% positive you did EXACTLY what i said?

I have no idea what went wrong
That's the problem with toolkits though. People don't know what they're doing and when something goes wrong you don't know how to fix it!! I understand where toolkits come from, but they are only useful if you know what happens in the background when you click on a button.

Thread Moved
Thread belongs in Q&A. Not the Dev Forum
Post moved.
MD

I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck

erica_renee said:
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
Click to expand...
Click to collapse
You Star
Put me on the right track, my PC was basically assuming that it was my S3, in the end I removed everything with samsung in it from the registry, uninstalled all the drivers then tried again, correctly showing as a nexus and not a samsung

[Q] USB and recovery problems after OTA upgrade to 4.3

I took the OTA to 4.3 on my Nexus 7. It was previously unlocked and rooted, but had no kernels, etc changed. After the update ran, I lost root as expected, however, in trying to get it back, I've discovered I'm having a couple of other issues.
First, the device is no longer working properly via USB on my PCs. On both my Win 7 and Win 8 PCs, the device won't properly connect to where I can browse files or anything else. On the Win 8 computer, I see a Nexus 7 device in Device manager, but drivers won't install. I downloaded the drivers from the Asus site, but trying to manually install them doesn't work on the Win 7 machine, and on the Win 8 machine, they install but don't seem to be working with the Nexus 7 as it still shows a problem in Device Manager.
The tablet also will not boot into recovery mode. I can power it up into fastboot mode, but if I select "Recovery Mode" and hit the power button, I just got the Android with the red triangle for a few minutes before it boots back into the OS. After doing some searching, I saw where you might need to have it plugged into a PC to get it to go into recovery, but that doesn't work, either (might be tied to the USB problem).
Ideas?

Did you turn on developer options, and USB debugging? Have you tried USB connection type PTP instead of MTP?
If you have the stock recovery, the red triangle and Android are normal. You can bring up a blue options menu by pressing the power and volume up buttons from the red triangle Android.
Sent from my rooted Nexus 7 @ 49.4 mpg

exglynco said:
Did you turn on developer options, and USB debugging?
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
Yes.

Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg

exglynco said:
Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
I was using the stock drivers off the Asus page. I'll look around for the two you mention. I assume they're posted on here somewhere.

And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7

Red Devil said:
And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7
Click to expand...
Click to collapse
Without USB access? That's my dilemma.

OK, I'm getting closer. I got TWRP installed and rerooted it. I had to do the "Revoke USB debugging authorizations" on the Dev Options screen. Then it would work via ADB.
Still not browsing files yet on my desktop, but at least I know I'm talking to it. So now I'll play with the driver installation a bit.
EDIT: Well, drivers reinstalled for about the 4th time, and it's still not allowing me to browse files from my desktop. Galaxy S4 works fine as soon as I plug it in, even if I also uninstall it's drivers. Ideas? I obviously have it working over USB because I can give it commands and reboot it via the PC.

OK, try this one. Plug in your tablet to pc, go to hardware manager, find your Android Device then choose Uninstall (choose Remove all drivers for this device), unplug and plug in your tablet again. Your Windows should discover few new devices (mine has discovered three) and download drivers for them then you should see Android ADB Interface in Android Devices and Nexus 7 in Mobile Devices.
--edit--
I've solved my issue
http://forum.xda-developers.com/showthread.php?p=44322739#post44322739

Already been done that road multiple times.

have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.

xxut said:
have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.
Click to expand...
Click to collapse
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta

SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I personally did all of those things. After having the Nexus "forget" all the other PC authorizations on the dev screen, I finally got it to accept ADB commands, just not to properly install drivers that would allow me to browse files like it had done on 4.2.

SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.

xxut said:
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.
Click to expand...
Click to collapse
Try turning off usb debugging. My tablet cannot connect to pc but with usb debugging off it at least recognises tablet as a media device and this enables me to view its files
.but still the problem of not being able to root

Bricked Device

I had a rooted 4.3 stock image on my N10. Got the notification about the downloaded update for 4.4
It did the update through TWRP (which was weird to me) and finished, restarts and gets stuck on the boot loading screen.
So I went into recovery, and cleared cache, no luck, then complete factory reset, no luck, then I added "System" to that wipe, not knowing what it was an now there is no OS installed.
I installed the Nexus 10 Toolkit (Unified Toolkit) and install the USB drivers, but my computer is not seeing my device..
Help?

As long as you can get to the bootloader, you can reflash a stock image. Easiest way is with wugfresh nexus root toolkit. It will walk you through the driver installation and the various image downloads.

That did not work.
The computer is not seeing my device. Drivers are installed, not seeing it, it's in the proper Boot mode.

I followed the mode that said I didn't need debugging enabled, still nothing.

bmancell said:
I followed the mode that said I didn't need debugging enabled, still nothing.
Click to expand...
Click to collapse
I would recommend uninstalling the USB drivers you installed with the toolkit and manually installing the Google USB drivers attached to this post. After you have installed the USB drivers I would recommend manually booting into your devices bootloader by simultaneously holding down the power button + volume up button + volume down button. Once you are in bootloader mode I would recommend download this Android 4.4 KitKat Factory Image and flashing it to your device in order to restore things to a working order. Let me know if you still have questions I'll be happy to help you out.

And want explain to me how I copy that file to my device when the computer can't see it?

bmancell said:
And want explain to me how I copy that file to my device when the computer can't see it?
Click to expand...
Click to collapse
Check out my previous post and see if those steps will allow your computer to see your device, and let me know how that goes for you.

Ok, I unziped the folder, got the tablet in bootloader mode, which I already said I tried, nothing.

Weird thing, I plugged the tablet into my other computer, it makes the noise for Windows 8.1 that you hear when you plug a USB device in, but there is no notifcation, nothing in device manager, nothing. Just the sound .

bmancell said:
Weird thing, I plugged the tablet into my other computer, it makes the noise for Windows 8.1 that you hear when you plug a USB device in, but there is no notification, nothing in device manager, nothing. Just the sound .
Click to expand...
Click to collapse
I just want to re-state everything to make sure anyone can understand.
This was a Nexus 10 rooted 4.3 Stock. I got the 4.4 update, it finished without issues, but got the boot loop issue.
I cleared cache, factory reset and eventually the system without luck, which left the tablet without an OS (bootloader or recovery only options).
My systems can not detect the tablet, I have installed, re-installed, tried two different toolkits and no luck.
I can't believe it's an actual brick that can't be fixed? Anyone?

Its definitely NOT your tablet. I had similar issues when rooting a Kindle and it was an issue with the PC's USB drivers. If you search the forums for USB / ADB drivers you will find a detailed discussion on how to delete existing drivers (its a process) and update new drivers.

sojthumper said:
Its definitely NOT your tablet. I had similar issues when rooting a Kindle and it was an issue with the PC's USB drivers. If you search the forums for USB / ADB drivers you will find a detailed discussion on how to delete existing drivers (its a process) and update new drivers.
Click to expand...
Click to collapse
Did you read? I have installed/reinstalled the drivers 3 times.

bmancell said:
Did you read? I have installed/reinstalled the drivers 3 times.
Click to expand...
Click to collapse
I also tried a third computer, and another cable. It will charge from a computer, nothing else.

I went through the same experience; it *was* the drivers. If you're using the wugfresh toolkit, it gives at least three options for driver installation. In my case only the drivers from pdanet worked. I've had similar issues in the past with my N7; in that case only the pdanet drivers worked on one computer, and only the Koush drivers worked on a different computer -- both Win 7 by the way; I have no idea why.
I did have to go through the whole procedure described in the toolkit to manually unistall old drivers and manually remove references to the device before reinstalling the driver.

You can get into TWRP, correct? Do you have a USB-OTG cable? You could download a ROM, put it on a flash drive then install it directly from the USB drive. There should be some flashable stock roms, or if you have an old Nandroid backup on your computer (always a good idea to have) you could restore it.
Sent from my Nexus 7 using xda app-developers app

gc84245 said:
You can get into TWRP, correct? Do you have a USB-OTG cable? You could download a ROM, put it on a flash drive then install it directly from the USB drive. There should be some flashable stock roms, or if you have an old Nandroid backup on your computer (always a good idea to have) you could restore it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Don't know what a USB-OTG cable is, and not sure how you'd connect a flash drive, but...
I tried one more computer, this time it was a computer with Windows 7 one it. Detected the tablet right away.
So, why the heck does Windows 8 (8.1 to be exact) not allow my tablet to be seen (im sure with the OS on, and booted in, it will)./

tjupille said:
I went through the same experience; it *was* the drivers. If you're using the wugfresh toolkit, it gives at least three options for driver installation. In my case only the drivers from pdanet worked. I've had similar issues in the past with my N7; in that case only the pdanet drivers worked on one computer, and only the Koush drivers worked on a different computer -- both Win 7 by the way; I have no idea why.
I did have to go through the whole procedure described in the toolkit to manually unistall old drivers and manually remove references to the device before reinstalling the driver.
Click to expand...
Click to collapse
This must be why my Windows 8 machines don't work, but I dont remember seeing other driver options, only the one, will keep in mind in the future.

Sounds like the problem is solved, but I highly recommend getting a USB-OTG cable anyways. Go to Amazon and search for "USB-OTG". You can connect flash drives and external hard drives to your tablet. I got mine for $2.
Sent from my Nexus 7 using xda app-developers app

[Q] adb working correctly fastboot wont recognize device

I encrypted my phone without realizing that CWM did not support encrypted devices. To fix this I was going to install TWRP since it does support it. My phone is working correctly with adb but I cannot get fastboot to find the device at all. This is making it so I cannot install TWRP on my phone now. Anyone have any ideas or suggestions? Thanks for any help.

You can install the recovery directly through the phone through Goomanager, but the fact that your computer doesn't recognize the device in fastboot is an issue I feel needs to be addressed. Goomanager solves the problem of the recovery, but I'm not sure about the fastboot issue.
Sent from my Nexus 4 using XDA Free mobile app

mikeric said:
I encrypted my phone without realizing that CWM did not support encrypted devices. To fix this I was going to install TWRP since it does support it. My phone is working correctly with adb but I cannot get fastboot to find the device at all. This is making it so I cannot install TWRP on my phone now. Anyone have any ideas or suggestions? Thanks for any help.
Click to expand...
Click to collapse
I had this issue on a different device. To solve it I went into control panel, device manager. Then look for the usb device that had an exclamation mark on it (with your device plugged into the usb port). Right click on it and update driver software. Then go to browse my computer and choose, let me pick from a list...... Pick the android composite adb interface. It'll ask you if your sure, just say yes
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I had this issue on a different device. To solve it I went into control panel, device manager. Then look for the usb device that had an exclamation mark on it (with your device plugged into the usb port). Right click on it and update driver software. Then go to browse my computer and choose, let me pick from a list...... Pick the android composite adb interface. It'll ask you if your sure, just say yes
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you, thank you, thank you. This enabled MTP mode for me in about 3 seconds on my Windows 8 PC. I had tried using Wug's toolkit both automated and manual even disabling enforcement of digital signatures on driver installation and had also installed latest ADK and Google drivers to no avail (all that got me was connection in camera mode and ability to see only DCIM). I don't remember having this kind of trouble last time I decided to play with my Nexus 4. Not sure if I was using my old Windows 7 machine then or if there is a conflict with the other drivers on my machine (I have recently flashed both Motorola and Samsung devices too). I wish you had posted a couple of hours sooner lol.