Database Users

Nexus 7 won't show up in adb devices, what should I do?

Earlier today I flashed Kaos Droid to try it out, but it put my Nexus in a state where it would not go past the screen that says Google and has the lock at the bottom. Since I have TWRP, Reboot to recovery from boot loader didn't work. I tried fixing the problem in not Windows and Ubuntu, but Windows kept on ending up as unknown device and no matter what drivers I tried to make it use it would not take, and in Linux it didn't show up in adb devices. I got lucky and it rebooted into TWRP after my fifth try of selecting recovery from the boot loader. I restored from backup, but I don't want this to happen again, if that ever happens. What should I do to get it in adb devices? Thanks.
Sent from an 8-core device from 2015

usb debugging

Try
Code:
adb kill-server
adb start-server
Can't remember if you need superuser permissions or not.

thebobp said:
Try
Code:
adb kill-server
adb start-server
Can't remember if you need superuser permissions or not.
Click to expand...
Click to collapse
I tried that, didn't work.

sonikot said:
usb debugging
Click to expand...
Click to collapse
How could I turn that on from bootloader? It was and is on before flashing the ROM and after restore.

Should have been able to run fastboot commands, either to try to reboot into the existing recovery, reboot into a recovery image, or flash a new recovery.
Sent from my Nexus 7 using xda premium

jcracken said:
Earlier today I flashed Kaos Droid to try it out, but it put my Nexus in a state where it would not go past the screen that says Google and has the lock at the bottom. Since I have TWRP, Reboot to recovery from boot loader didn't work. I tried fixing the problem in not Windows and Ubuntu, but Windows kept on ending up as unknown device and no matter what drivers I tried to make it use it would not take, and in Linux it didn't show up in adb devices. I got lucky and it rebooted into TWRP after my fifth try of selecting recovery from the boot loader. I restored from backup, but I don't want this to happen again, if that ever happens. What should I do to get it in adb devices? Thanks.
Sent from an 8-core device from 2015
Click to expand...
Click to collapse
Have a look at the Device Manager in Windows with your tablet plugged in. If there's that yellow triangle, just right click and choose update driver. Then you just browse and point Windows to where you have your N7 drivers.

akbar26 said:
Have a look at the Device Manager in Windows with your tablet plugged in. If there's that yellow triangle, just right click and choose update driver. Then you just browse and point Windows to where you have your N7 drivers.
Click to expand...
Click to collapse
That's the thing, I pointed it to official N7 drivers, Google USB Drivers, SuperOneClick drivers, and a bunch of other ones. It would never take--saying either that the best drivers are already installed (even though none were installed) or no suitable drivers exist in that directory.

I'm having a similar issue here, except I can get to the "X" boot animation.

jcracken said:
That's the thing, I pointed it to official N7 drivers, Google USB Drivers, SuperOneClick drivers, and a bunch of other ones. It would never take--saying either that the best drivers are already installed (even though none were installed) or no suitable drivers exist in that directory.
Click to expand...
Click to collapse
same problem here ... did u ever solve it ?

sonikot said:
usb debugging
Click to expand...
Click to collapse
Sometimes it seems to me that, even though USB debugging is "on", it really isn't.
Several times I have had to un-check and re-check "USB debugging" before adb would recognize the device.
Just my experience. Your milage may vary.

i'm in the same boat !
,
Any ?

Are you on 4.2.2? There now should be a security dialog upon executing an ADB command on the device, it will prompt you to allow the command to be executed.
If tou aren't on 4.2.2 - then it seems to be either a driver or a ROM issue

Yes I'm on 4.2.

I had this problem too and reinstalling the SDK tools fixed it for me for some reason.
Sent from my Paranoid 3.0 Nexus7 running M-Kernel mr1

I reinstall sdk without sucess

Maybe try using wugfresh toolkit. I've seen people say they couldn't use adb or fastboot but the toolkit worked. Doesn't really make sense to me since the toolkit just sends the commands for you but hey, worth a shot. It will walk you through uninstalling current drivers and doing a fresh driver install also.
Sent from my Paranoid 3.0 Nexus7 running M-Kernel mr1

travisjustin said:
Maybe try using wugfresh toolkit. I've seen people say they couldn't use adb or fastboot but the toolkit worked. Doesn't really make sense to me since the toolkit just sends the commands for you but hey, worth a shot. It will walk you through uninstalling current drivers and doing a fresh driver install also.
Sent from my Paranoid 3.0 Nexus7 running M-Kernel mr1
Click to expand...
Click to collapse
I use this kit. Remove all drivers. Then install the driver again. The drivers has been install in fastboot mode and recovery mode. The nexcus is recognized in these mode by the wugfresh toolkit.
Unfortunately in normal mode, when i active usb debug mode, i get a unkown device on windows 7 32 with any possibility to update the drivers.
I get error unkow device, device is stop error 43
Cable is stock and also try another one.
I get same message error on another computer with windows 8

I confirm that my usb issue is solved.
After a factory reset, i reinstall the last release Usb ROM and USB comes back to life on my nexus.
The nexus is no more recognized as unkown device by my computer and i can install the adb driver.
During this story, i try also to get acces via wifi but was unable to connect even with adb over wifi enable on the nexus.
That why Timur recommands me to made a full factory reset.
My problem seems to be due to corrupt data that block every connections between the computer and the nexus (adb wifi and usb) based on last 4.2.2 new safety features.
So far i recommand full wipe between two rom install to avoid such trouble.
Thank a lot to timur for his support during the week end.

If your nexus is rooted, go in recovery mode and install a new rom from zip.
How to ?
Download rom of your choice via wifi
You can download a rom directly from your nexus to sd.
Check here for download (example)
http://mehrvarz.github.com/nexus-7-usbrom/
Download Google applications on your nexus via wifi
Download from here : http://donandroid.com/gapps
Before installing new rom make a save using titanium backup.
https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup&hl=fr
Save all your application and data in batch mode.
Create titanium.zip on your nexus 7 sd.
Then from recovery mode make a full wipe but without erasing sd data.
Follow these instructions :
Unless you format the system partition and system caches, you aint wiped nothing, there is only one way to carry out a proper full wipe, and thats the full wipe the correct way.
1. Boot into recovery
2. Wipe the cache partition
3. Go to advanced and wipe dalvik and batt stats.
4. Go back to mounts and storage and format system, then data, then cache.
5. Go back and install the rom zip file from the sd card.
6. Reboot.
No need to wipe data/factory reset, the contents of your internal and external sd cards are untouched.
From Recovery mode
- install titanium.zip.
- install gapps.zip
Reboot
Go to titanium backup and recover all your data.
Et voila...

[Q] bootloop, usb debugging not enabled, no back up, help!

Alright here is my situation. I ran the latest OTA update on the stock rom and the phone started going into
a boot loop. My problem is that I havent performed a recent backup and need to access some files on the
phone. Developer mode is enabled, however I disabled USB debugging prior to running the update. When my
phone reboots, I remove the battery and restart the phone but every once in a while my phone successfully
loads and I am able to punch in my pin to unlock the phone. However, a few seconds later the phone reboots.
I tried to access the phone using ADB but because I dont have USB debugging enabled I dont see any devices
when I run the "adb devices" command. I also tried to acquire a smartphone image using encase forensic, but
yet again, because USB debuggin is not enabled, I am not able to pull data.
I am able to go into recovery mode and I tried to wipe my cache partition, but that did not help.
My questions are:
1. Is there a way for me to access my data files while the phone is stuck in a boot loop and USB debugging is
disabled?
2. Is it possible for me to download the latest update, copy it over to my sdcard and rerun the update from
my sdcard from recovery mode? Could this possibly solve my problem?
3. In a worst case scenario, if I do a factory wipe/reset, will this solve my problem and what is the
likelyhood of recovering my files from the data partition?
Any tips, tricks, advice is greatly appreciated.

tparnet said:
Alright here is my situation. I ran the latest OTA update on the stock rom and the phone started going into
a boot loop. My problem is that I havent performed a recent backup and need to access some files on the
phone. Developer mode is enabled, however I disabled USB debugging prior to running the update. When my
phone reboots, I remove the battery and restart the phone but every once in a while my phone successfully
loads and I am able to punch in my pin to unlock the phone. However, a few seconds later the phone reboots.
I tried to access the phone using ADB but because I dont have USB debugging enabled I dont see any devices
when I run the "adb devices" command. I also tried to acquire a smartphone image using encase forensic, but
yet again, because USB debuggin is not enabled, I am not able to pull data.
I am able to go into recovery mode and I tried to wipe my cache partition, but that did not help.
My questions are:
1. Is there a way for me to access my data files while the phone is stuck in a boot loop and USB debugging is
disabled?
2. Is it possible for me to download the latest update, copy it over to my sdcard and rerun the update from
my sdcard from recovery mode? Could this possibly solve my problem?
3. In a worst case scenario, if I do a factory wipe/reset, will this solve my problem and what is the
likelyhood of recovering my files from the data partition?
Any tips, tricks, advice is greatly appreciated.
Click to expand...
Click to collapse
Boot phone into recovery mode. You can access phone now and make backup or download need files to PC.

svs57 said:
Boot phone into recovery mode. You can access phone now and make backup or download need files to PC.
Click to expand...
Click to collapse
Thanks svs57 for the quick reply.
Would you mind elaborating a bit more? I am an IT guy but by no means a developer. When I boot into recovery is the phone supposed to show up in My Computer via MTP or PTP? The phone is not showing up as a device. Or am I supposed to use adb commands to pull the files down?
When I go into recovery and run the "adb devices" command now I get what appears to be a serial number followed by the word "unauthorized". I rebooted and went into recovery mode again this time tried "apply update from ADB". When I try using either the adb push or adb pull I get "error: closed"
Thanks again for the help.

You have to use latest version of adb. Then you can login to phone via adb and find file you want to backup. Then use "adb pull" to get file to PC.
If you have custom recovery you also can make backup you data using recovery.
Also you can flash the same ROM you have without wipe data.

[Q] No USB debugging, can I adb?

Back story: Nexus 7 2012 WiFi, unlocked, rooted, TWRP, ROM'd
Tried to stock to 4.3. Power + volume down = Android on his back. can scroll Start, Restart Bootloader, Recovery Mode, Power Off. Select anything but Power Off and "booting failed" pops up in top left corner.
Anyone.....Anywhere.....Any IDEAS?
Without access I can't turn on USB debugging. I am no pro, but I'm not new. I have spent days trying to breathe life into this dude and I am at my end.

You don't need debugging to use fastboot. Look at the sticky at the top that says how to restore a factory image or something like that.
Sent from my Nexus 7(2012) that has zero issues.

SlowCobra96 said:
You don't need debugging to use fastboot. Look at the sticky at the top that says how to restore a factory image or something like that.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
Exactly, fastboot has absolutely nothing to do with a switch within Android such as that of USB debugging. You have two courses of action; either flash stock images as suggested or proceed to flash a custom recovery, from which you can flash any custom ROM.

let me try again...
Via terminal: adb finds no devices; fast boot returns with a number for a device found, but when you flash from fast boot... nothing actually happens. I assumed that USB debugging was a moot point, but it seems most of the direction's you read a always start with "turn on USB debugging". When I go through and type in erase this, reboot that it say failed. Is there any caveman way of replacing fast boot? As I said, the cable is good, the USB port is good, I have gone at it through both Windows 7 Pro 64bit and Linux Mint 15 and I believe I have tried every suggestion I could find on the web. I will check the sticky above as suggested but I am stumped.

Fastboot and adb are not cross compatible. You cannot expect adb commands to work work in fastboot just as you should not expect fastboot commands to work in adb.
You have not actually stated WHAT you have tried in fastboot. What commands are you typing and what files are you using? You ask how to replace fastboot yet that is not possible nor is it sane to even think to replace it. Fastboot is there for a reason.
Sent from my Galaxy Nexus

boot into recovery TWRP
goto advanced > adb sideload
on your pc command prompt goto adb (where ever your sdk is installed) and push the rom image to root directory
after that's done, cancel out of adb sideload and go back to main. do a wipe (factory reset, cache, dalvik cache, system) and go back to main.
click install and find the rom image (click internal storage on top)

Open Source Paul said:
Via terminal: adb finds no devices; fast boot returns with a number for a device found, but when you flash from fast boot... nothing actually happens. I assumed that USB debugging was a moot point, but it seems most of the direction's you read a always start with "turn on USB debugging". When I go through and type in erase this, reboot that it say failed. Is there any caveman way of replacing fast boot? As I said, the cable is good, the USB port is good, I have gone at it through both Windows 7 Pro 64bit and Linux Mint 15 and I believe I have tried every suggestion I could find on the web. I will check the sticky above as suggested but I am stumped.
Click to expand...
Click to collapse
Let us try, AGAIN. ADB and FASTBOOT are 2 DIFFERENT programs. Stop trying to use ADB to reinstall the OS. At the top of this page there is a sticky that literally holds your hand through the FASTBOOT command process. Read that. Forget for the time being that ADB exists. Think of it as ADB ONLY exists if you have a working OS. You currently don't so you NEED to use FASTBOOT.
Flashing a factory image using fastboot/restore to stock
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-grouper-4.23.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasi-jwr66v.zip

Soft Bricked Nexus 6P With Locked Bootloader (Need Help)

My Nexus 6P is stuck on the Android boot animation after installing the Android Beta OTA that came out today. I waited like 30 Minutes and nothing was happening so I tried Clearing Cache which did nothing then factory resetting, Clearing Cache & Even sideloading the OTA using ADB to no avail. My huge mistake was not having OEM Unlocking enabled so now I can't even flash stock android.. I know this is my fault for being so stupid but is there anything at all I can do to save my phone?

AlfexOmega said:
My Nexus 6P is stuck on the Android boot animation after installing the Android Beta OTA that came out today. I waited like 30 Minutes and nothing was happening so I tried Clearing Cache which did nothing then factory resetting, Clearing Cache & Even sideloading the OTA using ADB to no avail. My huge mistake was not having OEM Unlocking enabled so now I can't even flash stock android.. I know this is my fault for being so stupid but is there anything at all I can do to save my phone?
Click to expand...
Click to collapse
I'm in the exact same boat...hopefully something can be done, but I'm afraid we're idiots for not having checked OEM Unlocking. I've tried adb sideloading the OTA image, but as you said, with a locked bootloader, we've got nothing. Anybody have any ideas?

You might be able to use ADB to modify the OEM Unlock setting while booting.
Also, if you ever plan to mess with your OS, especially alpha/beta versions, always have your bootloader unlocked to prevent issues like this.

Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.

imatts said:
Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.
Click to expand...
Click to collapse
Live booting TWRP works on the 6P even with the bootloader is locked?
Sent from my Nexus 5X using Tapatalk

imatts said:
Use Fastboot boot [[[name of latest twrp]]].img (make sure the .img is in the adb folder on your pc) and then do a full system wipe (not just factory reset, but literally everything, internal and external -- access this from the advanced menu in twrp). That should boot you into the system so that you can enable oem unlocking, unlock the bootloader, and carry on like normal.
Click to expand...
Click to collapse
Can't boot twrp.img because the device is locked. Anything else I can do?

I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try

spookytay said:
I had something similar like this happen, for my fix, all I did was boot to bootloader, cleared cache and then did a complete shutdown, do not just reboot, just rebooting, would go thru the boot loop, but a full power down allowed it to boot up normally. Not sure if it will help in your situation, but it's an easy try
Click to expand...
Click to collapse
No luck for me, unfortunately. Keep in mind that I tried to sideload the OTA.zip with a locked bootloader before doing this, so that may have made this process not work. For those who haven't tried to "fix" their failed installation like I did, give the cache clear a try first.

Apparently some people can use the fastboot format command while their bootloader is locked. You can try booting into the bootloader and issuing these commands. (THIS WILL WIPE YOUR ENTIRE DEVICE INCLUDING SDCARD/INTERNAL STORAGE. Of course, your device is now bricked, so I'm sure this is fine for you.)
Code:
fastboot format cache
fastboot format userdata

My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip

AlfexOmega said:
My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
Glad you got it working! Hopefully it works for the other guy too. Probably best to use the factory image if you wanna update to N, with OEM Unlocking enabled

lightmastertech said:
Glad you got it working! Hopefully it works for the other guy too. Probably best to use the factory image if you wanna update to N, with OEM Unlocking enabled
Click to expand...
Click to collapse
This method will work 100% just adb sideload the package and done. My idea worked thanks to the guy who posted the ota zip

Ame123 said:
This method will work 100% just adb sideload the package and done. My idea worked thanks to the guy who posted the ota zip
Click to expand...
Click to collapse
Hello guys. I'm having the same problem here: installed the update last Thursday, apparently didn't have usb debugging checked on and I can't get past the boot animation.
Tried everything: format several times, cleared cache, sideload, etc. I've tried to sideload this package you guys are talking about but unfortunately this doesn't work either... In cmd it says <waiting for devices>. Tried different usb ports and everything - still nothing

silviuardelean said:
Hello guys. I'm having the same problem here: installed the update last Thursday, apparently didn't have usb debugging checked on and I can't get past the boot animation.
Tried everything: format several times, cleared cache, sideload, etc. I've tried to sideload this package you guys are talking about but unfortunately this doesn't work either... In cmd it says <waiting for devices>. Tried different usb ports and everything - still nothing
Click to expand...
Click to collapse
Seems like it could be a driver issue. If you run adb devices does your device show up?

freezerbite said:
Seems like it could be a driver issue. If you run adb devices does your device show up?
Click to expand...
Click to collapse
Yes, the device was showing up in cmd but couldn't get over <waiting for devices>... I've tried to install TWRP and failed again. After trying to sideload the image a dozen times and clearing cache, formatting data, etc several times, it somehow worked in the end. Thank you very much!

It might sound like a dumb question, but how do i Side load through ADB? can you please point me in the right direction. I'd really appreciate it! @silviuardelean @Ame123 @AlfexOmega Actually, I don't think I ever enabled usb debugging

GeorgeOSbeta said:
It might sound like a dumb question, but how do i Side load through ADB? can you please point me in the right direction. I'd really appreciate it! @silviuardelean @Ame123 @AlfexOmega Actually, I don't think I ever enabled usb debugging
Click to expand...
Click to collapse
I was able to get mine to work without having it enabled you could try using Nexus Root Toolkit it guides you through how to do everything
https://www.youtube.com/watch?v=LfDSZsr6230

Locked bootloader 7.1.1 ota preview help!
I have the latest preview build directly installed ota from Google. The phone just started bootlooping the other day for no apparent reason. I didn't have the developer options on or oem unlock enabled.
I can get to bootloader mode and recovery mode. I have wiped and reset from recovery with no help. I can access adb and fastboot on the pc but it won't let me write any files because of the locked bootloader. Anything I try to sideload so far gives an error. Any further suggestions?

AlfexOmega said:
My 6P is now fully working thanks to Matt1515 on another thread! This is a link to the OTA downgrade from N developer preview 3 to 6.0.1 worked like a charm for me! Just use recovery ADB sideloading
https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Click to expand...
Click to collapse
I'm full stock with locked bootloader. How do I install this package? Flashing through recovery or with adb (and in this case, which commands should I use)?

solefero69 said:
I'm full stock with locked bootloader. How do I install this package? Flashing through recovery or with adb (and in this case, which commands should I use)?
Click to expand...
Click to collapse
You use recovery to sideload it via adb. If you are unsure how to do so you can download and use Nexus Root Toolkit it does everything for you, it's really useful This video will help
https://www.youtube.com/watch?v=LfDSZsr6230

Need help!!! Cannot boot into twrp

Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!

any luck?
ahq1216 said:
Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
Click to expand...
Click to collapse
different route but im in the same boat. any luck?

I fixed this shortly after. Wanted to avoid returning to stock as. The only option was you and I was on 10d. I had to go back to stock but luckily the recovery method still works.