Database Users

[Q] ADB Way into recovery, bootloop

Okay so I flashed a rom and im stuck in a bootloop, but I cant get into recovery to restore a nandroid. My power button receded so as soon as I put in a battery it immediately turns on. But if i go into bootloader, not the power button nor the volume keys will work. So I cant get into recovery that way. Is there any other way like with adb in bootloader? Or am i screwed lol.
Thanks in advance for help, I could really use it.

adb reboot bootloader
adb reboot recovery
It should be obvious what they do. Bootloader won't do you much good without a power button.
Sent from my HTC Glacier using XDA App

estallings15 said:
adb reboot bootloader
adb reboot recovery
It should be obvious what they do. Bootloader won't do you much good without a power button.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I tried running adb in the bootloader but it wont connect to my phone. What exactly should I be typing to connect it? Its plugged in with a usb cord. Sorry, obviously im a huge newb

perhac89 said:
I tried running adb in the bootloader but it wont connect to my phone. What exactly should I be typing to connect it? Its plugged in with a usb cord. Sorry, obviously im a huge newb
Click to expand...
Click to collapse
if you are in bootloader mode, make sure the phone says FASTBOOT USB somewhere on the screen when connected to the computer.
then type
Code:
fastboot reboot (whatever it is you want to reboot to)
adb only works in recovery or android itself.

saranhai said:
if you are in bootloader mode, make sure the phone says FASTBOOT USB somewhere on the screen when connected to the computer.
then type
Code:
fastboot reboot (whatever it is you want to reboot to)
adb only works in recovery or android itself.
Click to expand...
Click to collapse
Then only thing Im getting is Hboot Usb Plug, not Fastboot Usb
Edit: Okay now I have Fastboot USB showing, but cmd doesnt recognize fastboot, nor will it connect to my device

Just boot the phone in the regular way.
While it boots, in bootanimation or even a bit before that, execute "adb reboot recovery".

Jack_R1 said:
Just boot the phone in the regular way.
While it boots, in bootanimation or even a bit before that, execute "adb reboot recovery".
Click to expand...
Click to collapse
All Im getting when I do this is error device not found

Bump.
I can't get it back into fastboot usb either, I think the power button fixed for a second before and selected fastboot.

Do you have a warranty on this phone?
If not, you may want to open it where you can access the power button more easily.
Before you do that though, get it caught in a bootloop and try adb reboot recovery. Reboot and try again at a different point. It should work eventually. Persistence might pay off.
Sent from my HTC Glacier using XDA App

perhac89 said:
All Im getting when I do this is error device not found
Click to expand...
Click to collapse
Since you're in the bootloop, your device is connecting and disconnecting. See when it connects (easily recognized Windows "USB device connected" sound), then execute "adb reboot recovery" until the command catches or the phone reboots. Attempt several times.
If it won't work - open the phone and fix the button.

Stuck bootloader

Ok so i tried to root my N7 and im pretty sure i screwed up because now when i enter the boot loader with the usb connected, it crashes. On my computer it says the device is not running, i can get bootloader working if its not plugged into my computer.Help plz!

Does your computer recognize the fact that it's plugged in? And if so - do you have Android Debugging installed?
If you have both of these things working you can flash the stock image and basically start over. You can either go install the Nexus toolkit or do it manually through ADB - both of those are found over in the Development section and are pretty straight forward.
Try rooting/installing CWM through the Nexus Toolkit, it's essentially foolproof save unplugging your device.

brianjr1 said:
Does your computer recognize the fact that it's plugged in? And if so - do you have Android Debugging installed?
If you have both of these things working you can flash the stock image and basically start over. You can either go install the Nexus toolkit or do it manually through ADB - both of those are found over in the Development section and are pretty straight forward.
Try rooting/installing CWM through the Nexus Toolkit, it's essentially foolproof save unplugging your device.
Click to expand...
Click to collapse
Thanks for replying so quickly. I can boot up into jelly bean, but i can't boot into boot loader.
In both the bootloader and the actual rom my computer can detect it with ADB installed; however heres the problem, when in the bootloader it gets stuck, i can't use the volume buttons i can't click anything and on my computer (inside device manager) it tells me:
This device cannot start. (Code 10)
If i don't plug in the USB i can use the boot loader, and because I can't leave the usb in while in bootloader, i can't flash anything.
*edit also i can't go into recovery mode, it just gets stuck at the google logo

bump

Have you tried to boot into the boot loader through adb?
Also, I'm pretty sure its a known issue that you can't boot into recovery from the boot loader menu. I'd suggest flashing the stock nakasi file through adb and see if that fixes it for you.
Sent from my Nexus 7 using xda app-developers app

I also had trouble getting the bootloader to operate correctly with the USB connected.
Disconnect USB
Hold down vol+, vol- and pwr to get into the bootloader
Reconnect USB once you are in the bootloader

Softbricked Nexus 7 - Debugging Off?

Hi guys, after restoring from a backup I made in CWM - which apparently was corrupted - I can't boot past the "X" boot animation, and because of the glitch in the bootloader, I cannot boot to recovery, which would at least allow me to flash a clean ROM. At any rate, I tried to boot to recovery from my computer, but I keep getting "error: device not found" errors from ADB and the Nexus 7 ToolKit (which uses ADB anyway). I have tried all possible scenarios with drivers, but to no avail. I can only assume that debugging is disabled. Is this a reasonable assumption, and if it is true, am I completely screwed out of $250, or is there something I can do?

SpaceToast7 said:
Hi guys, after restoring from a backup I made in CWM - which apparently was corrupted - I can't boot past the "X" boot animation, and because of the glitch in the bootloader, I cannot boot to recovery, which would at least allow me to flash a clean ROM. At any rate, I tried to boot to recovery from my computer, but I keep getting "error: device not found" errors from ADB and the Nexus 7 ToolKit (which uses ADB anyway). I have tried all possible scenarios with drivers, but to no avail. I can only assume that debugging is disabled. Is this a reasonable assumption, and if it is true, am I completely screwed out of $250, or is there something I can do?
Click to expand...
Click to collapse
Can you get to fastboot if you have the USB plugged in? If so you can use it to restore stock with the factory images from Google.

I managed to use the fastboot method to solve the problem. Everything went nicely for about a day, and just an hour ago my soft navigation buttons stopped responding to touch. A factory reset from the device did not resolve the problem. I'm going to try some work in ADB once I get access to a proper windows computer, but that may not be for a while, is there anything that might work that doesn't require a computer in the meantime? (I'm clueless when it comes to Linux. I tried installing Java and the Android SDK using a LiveCD of Ubuntu, but my efforts were met with frustration.)

You can just put windows on through a disk rather than buying a PC
Sent from my Nexus 7 using xda app-developers app

Nah, I have a fully functional custom rig, but windows killed itself and my cracked disk image of the install disk is on the same hard drive on the same partition. I'm waiting for my SSD to come in, so I can install Mint on it and burn the iso on my hard drive from there, then install Windows on my SSD.
At any rate, I used my friend's computer to flash to stock from fastboot and it didn't fix anything. Now, every time i try to touch the screen it just pulls the notification bar down to that point on the screen. I'm ready to re-lock my bootloader and bring it back to the store if nobody has a more convenient solution.
UPDATE: I rebooted from there and I'm back where I was in the last post. My navigation buttons at the bottom don't work, and sometimes touches don't register on the rest of the screen. The lock screen also doesn't respond to touch either.

ADB commands only work when its on. Fastboot boot commands when in bootloader.
Or just plug the N7 into the PC, hold down all the buttons to boot into fastboot, then select recovery. It has to be plugged in to the PC to get into ClockworkMod.
Sent from my Nexus 7 using xda premium

player911 said:
ADB commands only work when its on. Fastboot boot commands when in bootloader.
Or just plug the N7 into the PC, hold down all the buttons to boot into fastboot, then select recovery. It has to be plugged in to the PC to get into ClockworkMod.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
But I'm not attempting to do anything in ADB, unless there is some way I can use ADB to fix my nav bar and lockscreen.
UPDATE: It seems the lockscreen is working. Also, my navigation bar sometimes feels like activating buttons without me touching them.
UPDATE 2: And just like that my lockscreen isn't responding to touch again.

Bump?

can we launch fast boot while in recovery cause mine n7 always boot into clockwork recovery, i can not boot into my rom

Bricked nexus 7 please read!

Hi,
I. Have gotten myself into quit a frustrating situation. My nexus 7 was unlocked, rooted and had several different custom roms installed at various times and had never had a problem. But then one time in particular, when trying to flash a rom (which I can't even remember which one it was,) after the rom had "successfully" been flashed, it rebooted to the splash screen, which it stayed at for a very long time; before just turning into a series of flashing vertical lines that never end. I can use the power+vol- method to get to fastboot, but not recovery; it would appear that my recovery has been wiped as I get the same google splash screen loop as when I try to boot. My problem is that nothing I do allows me to successfully connect the device to my pc (w7, 32bit.)
I have uninstalled any conflicting drivers, un/re-installed the proper drivers from like 7 different guides, I have also tried two different nexus root toolkits. I even tried to use a Linux machine to no avail. I have switched USB cables, everything I have tried has not worked. This is by no means my first foray into android devices, I even freshly installed my android SDK and still my computer just fails to recognize the nexus 7 in fastboot mode.
Any tips or advice would be a godsend. Thanks.

This sounds like a issue a few people have been having.. As far as i know as of a week ago there is no solution . You need to flash the boot-loader it sounds like. There is a thread about this. Search for NV FLASH .. OR APX MODE. Sorry for being lazy and not looking for the thread for you..
They may have some things in that thread that you have not tried.

Turn your Nexus off and plug it into your computer. Does your Nexus start charging? A completely bricked Nexus wouldn't charge. If it starts charging, then try turning it on into Fastboot mode.
Sorry, I'm no dev. Just a random thought to try. But if your Nexus can charge you shouldn't be fully bricked, hopefully. At least this is what I think.

When you say your computer fails to recognise the device...
If you open your device manager in Windows and then plug in the nexus 7 in fastboot mode, what happens? Does it show up in the device manager in any category? Even with a yellow exclamation mark or as unknown device?
Sent from my Nexus 7 using Tapatalk 2

My bro bricked his N7
He was rooted and unlocked, flashed a rom now it bootloops on the logo. Now when doing adb devices, it doesnt detect the device when in bootloader, went to device manager and shows problem with driver. Tried other drivers but says its up to date. Thing is I just upgared his friends N7 with the same drivers so I know thats not a problem.
It wont go into recovery either. Now when it is bootlooping, the decive is recognised when doing adb devices. So can I flash a factory image when it is bootlooping or does it have to be in fastboot?

TRY THIS
from powered down,
hold VOL- and POWER for ten seconds,. then let go of POWER and still hold down VOL-

dramdrum said:
When you say your computer fails to recognise the device...
If you open your device manager in Windows and then plug in the nexus 7 in fastboot mode, what happens? Does it show up in the device manager in any category? Even with a yellow exclamation mark or as unknown device?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
it doesn't even acknowledge that I plugged anything in to the computer at all.

chismay said:
TRY THIS
from powered down,
hold VOL- and POWER for ten seconds,. then let go of POWER and still hold down VOL-
Click to expand...
Click to collapse
Just goes to bootloader?
Edit seems to be working now even though when doing adb devices in fastboot it doesnt list the device id

In fatboot mode you don't have adb access - down load a recovery image and name recovery.img
Hold shift and right click in the folder recovery.img is in
Choose open command here, in cmd type
fastboot devices
If you see your serial number proceed
fastboot flash recovery recovery.img
When finished reboot to recovery and flash rom of choice
ps, you have had to either change your path in enviromental variables to include platform-tools from the sdk or have both fastboot.exe and recovery.img in the same folder that cmd is pointed to
Sent from my HTC Vision using xda premium

nexus 6p not showing on device manager

Hi, my 6p will not show up on my PC. Have tried installing drivers, different PC, different cable but nothing works.
I recently upgraded to android O. I extracted the files from system image and flashed boot image, vendor image, and system. But now when I try to go into recovery it says no command and I lost root access but my bootloader is unlocked. I never flashed the recovery thinking TWRP would stay intact but I guess I was wrong. Normally I would just use ADB and fix it but hence my problem. Is there any way to root without PC or any way I can fix my situation?

Having the same exact issue here, hope someone has a way to fix it.

sonysingh1983 said:
Hi, my 6p will not show up on my PC. Have tried installing drivers, different PC, different cable but nothing works.
I recently upgraded to android O. I extracted the files from system image and flashed boot image, vendor image, and system. But now when I try to go into recovery it says no command and I lost root access but my bootloader is unlocked. I never flashed the recovery thinking TWRP would stay intact but I guess I was wrong. Normally I would just use ADB and fix it but hence my problem. Is there any way to root without PC or any way I can fix my situation?
Click to expand...
Click to collapse
So your phone will boot into the OS, or not? If so, make sure USB debugging is set to "on" in Developer Settings. Can you put your device in fastboot mode by holding down the volume down button before hitting the power button? The "no command" means you are in (stock) recovery. You then have to hold the power button down while using the volume buttons to navigate. Power button is confirm. Get your phone into bootloader mode and use ADB to flash TWRP again. @meoshe

v12xke said:
So your phone will boot into the OS, or not? If so, make sure USB debugging is set to "on" in Developer Settings. Can you put your device in fastboot mode by holding down the volume down button before hitting the power button? The "no command" means you are in (stock) recovery. You then have to hold the power button down while using the volume buttons to navigate. Power button is confirm. Get your phone into bootloader mode and use ADB to flash TWRP again. @meoshe
Click to expand...
Click to collapse
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.

sonysingh1983 said:
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
Click to expand...
Click to collapse
Gotcha. What about the other points? Entering bootloader mode from a powered off state, and that you are in Recovery mode (no command), and navigating thru it with the power+volume buttons?

v12xke said:
Gotcha. What about the other points? Entering bootloader mode from a powered off state, and that you are in Recovery mode (no command), and navigating thru it with the power+volume buttons?
Click to expand...
Click to collapse
Yes that works. Thank you. But still can't root phone and can't flash TWRP. Was looking at a root APK but not sure if they will work with O. If I could root then I could install TWRP thru it's app but I need root for that.

You can't root the phone until you have a working custom recovery. Focus on either fastboot flashing or fastboot booting TWRP.img

v12xke said:
You can't root the phone until you have a working custom recovery. Focus on either fastboot flashing or fastboot booting TWRP.img
Click to expand...
Click to collapse
How do I go about fastboot booting TWRP image?
I can get into bootloader from phone but I can't use a PC.

I did read your OP, but this sounds like a driver issue. There are two drivers that need to be installed first the USB and then fastboot. Since you can boot the device and use it, maybe you should try NRT by Wugfresh to install, test and confirm the drivers are properly installed. Booting or flashing TWRP is just a different command. Instead of fastboot flash recovery twrp.img, you use fastboot boot recovery recovery.img. The NRT toolkit can also either boot or flash a recovery image.
EDIT: Also try "Revoking ADB debugging" and re-enabling @sonysingh1983

sonysingh1983 said:
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
Click to expand...
Click to collapse
Hi, just tried the mtp setting in developer options. Didn't get it the first time but now am able to access internal storage. I have plug sound app from play installed and I get a notification sound when plugging and unplugging. First try there was no sound when changing from charging to mtp. Ok after repeating it. Hope that helps.

Just as a follow up I got my win10 pc to recognize my O flashed nexus. I booted into bootloader after I had updated my sdk and drivers through android studio. It recognized the phone but nothing was happening. I rebooted into the os and the access allow prompt popped up on the phone and adb was able to see it under listed devices.