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

[Q] Cant access bootloader

Hi,
I ran into a problem with my Nexus 4, the plan was to unlock the bootloader using my mac and fastboot. (used this as information but didn't follow it step by step, youtube.com/watch?v=fHZJ2f6JLw0)
I turned off the phone and went into the bootloader with volume down + power button. From here i used "fastboot devices" to secure that i was able to communicate with the phone. My device showed up together with an error message saying "ERROR: could not get pipe properties nexus 4".
Before doing any more i wanted to understand what this message meant so I searched the web without any success. I booted up my android, turned on usb debugging and used "adb devices". This time only my devices showed up and no error messages. I used the "adb reboot boatloader" to access the bootloader once again.
I still had the same error message with "flashboot devices" as before.
From here i didn't do anything more, I may have disconnected the usb from the computer while the terminal window was open and the phone in bootloader but without running any command from fastboot.
So I didn't run "fastboot oem unlock" or anything else.
I turned off the phone and tried to access the bootloader one more time with the volume down + power button. It didn't respond to this any more and nothing happened, the device just stayed turn off.
I turned on the phone and tried to use adb to access the bootloader but now when running the "adb devices" it just responds "-bash: adb: command not found".
I have tried to restore the phone thru the android setting meny without any success. The phone is working fine without any problem except i cant access the bootloader or use adb.
So I desperately need help from you guys. :crying:
Have any of you heard of this problem before?
Regards Rasmus

I have to change my statement.
Actually I succeeded rooting and installing CWM recovery using a win7 computer together with Nexus4 toolkit.
The issue i have right now is that i can't start the device into bootloader using volume and power buttons.
To access bootloader i have to go thru the toolkit and this can be an issue in case i flash a bad rom or kernel and can access android usb debugging.
Is it possible to restore the bootloader?

rallanand said:
The issue i have right now is that i can't start the device into bootloader using volume and power buttons.
Click to expand...
Click to collapse
Are you holding the down volume and pressing the power button?

What OS is the computer that you are using? If you have reset the device, make sure that USB debugging is checked again. I know it sounds dumb, but a lot of times it's the simplest things we forget. Once you factory reset your device, it resets everything.
If you are on Windows 7, make sure you are starting the command prompt from the same location your adb is installed. If you are on Ubuntu or another Linux distro, please let me know which one. This seems like it should be an easy fix for you, but a little more info is needed. Thanks!

Soft Bricked Nexus, fastboot/bootloader non-responsive

So I managed to bricked Nexus last night trying to flash the factory images. It wouldn't flash correctly through the Nexus Root Toolkit, due to the outdated bootloader. I tried to install the 4.2 boot loader through recovery, (as it was flashable). It it didn't work, and I can't boot into recovery as it gets stuck on the splash screen. And of course I can do anything in fastboot because the tablet freezes when I plug in USB. Anything else I can try?
Here's some quick info.
Recovery- TWRP 2.3.3.x
Bootloader- 3.3.4
ROM- CM10.1
Sent from my Rooted Nexus 4

JiG Brick USB
JiG Brick USB might help, but i don't know for sure.

AW: Soft Bricked Nexus, fastboot/bootloader non-responsive
Are you able to boot into boot loader? If yes, you are not bricked. You can flash the factory image and you can flash a new recovery.
Sent from my Nexus 7 using xda app-developers app

So I got back from school today and tried to turn it back on again, and it decided to boot up normally.

This is happening to me. I can boot the Nexus into Fastboot, but as soon as you plug in a USB it freezes and any commands sent from the PC receive only "awaiting device" in response. I can't boot into recovery, it just stays on the Google splash screen and unfortunately the ROM I was trying to install didn't work. Any advice?

Ethicistabdiel said:
This is happening to me. I can boot the Nexus into Fastboot, but as soon as you plug in a USB it freezes and any commands sent from the PC receive only "awaiting device" in response. I can't boot into recovery, it just stays on the Google splash screen and unfortunately the ROM I was trying to install didn't work. Any advice?
Click to expand...
Click to collapse
Could you please describe a bit in more details what you are doing nd what is freezing?
If you are in bootloader mode, you can send only fastboot commands to your device, nothing else, so I am wondering what is freezing ...

AndDiSa said:
Could you please describe a bit in more details what you are doing nd what is freezing?
If you are in bootloader mode, you can send only fastboot commands to your device, nothing else, so I am wondering what is freezing ...
Click to expand...
Click to collapse
What I mean is that as soon as the USB is plugged in, the bootloader on the Nexus becomes completely unresponsive, I can no longer use the volume buttons to navigate the options or the power button to progress. It appears for all intents and purposes frozen and remains so after the USB is unplugged. Commands sent from ADB while the Nexus is in the bootloader just say "awaiting device" and nothing happens and I can't see the Nexus with ADB Devices.
I may not be using the best terms, I'm assuming the bootloader is the screen where you are given the options of recovery, restart the bootloader, start and so on. That screen becomes completely frozen when the usb cable is plugged in. If I select for it to go to recovery and do not plug in the USB cable, it goes to the google splash screen and the recovery never loads. I've had this Nexus fully rommed before, it has Clockwork Mod Recovery Manager on it and I've had no trouble getting it to load previously.
I'm doing all this because I tried to install a new rom (Paranoid Android Nightlies, latest version) and it did not install properly, upon start it says gapps has stopped and the setup wizard has stopped working - the OS will not load but will just keep repeating these error messages. Thus, I'm trying to either get into recovery or send ADB commands to the tablet to fix it.

AW: Soft Bricked Nexus, fastboot/bootloader non-responsive
1.) When you are in boot loader, adb will not be able to connect to your device, you need to use fastboot instead. This command is part of the SDK and can be called from the command line. Eventually you need to add the directory containing the fastboot executable to your path.
2.) That the buttons do not respond any longer after plugging to USB is very strange.
- What bootloader version is installed on your device?
- What does fastboot devices print on the screen?
- Did you try already with a different USB-port / cable?
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
1.) When you are in boot loader, adb will not be able to connect to your device, you need to use fastboot instead. This command is part of the SDK and can be called from the command line. Eventually you need to add the directory containing the fastboot executable to your path.
2.) That the buttons do not respond any longer after plugging to USB is very strange.
- What bootloader version is installed on your device?
- What does fastboot devices print on the screen?
- Did you try already with a different USB-port / cable?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
All fixed now. It was actually the computer, an issue with the USB, did it on my laptop and was able to fix it pretty quickly. It was you differentiating Fastboot from ADB that got me there though, I tried that on my PC and when it didn't work I then did it on the laptop. Most likely wouldn't have gotten there without you, at least not so quickly. Thank you very much!

[Q] Soft-Bricked Refurbished Stock Nexus 7

I recently bought a refurbished 2012 Nexus 7 on 4.2. The only things that I have done on the phone are entering my Google account details and downloading a single app (papyrus). I then clicked to install the automatically downloaded software update (it downloaded 4.3), and after restarting the tablet was stuck on the Nexus X boot animation forever. Factory reset/cache wipes do not help.
I found drivers for the phone to be recognized while showing the X, and I found drivers for the phone to be recognized after selecting the a "apply update from ADB" option from stock recovery. However Windows does not recognize the phone at all in recovery mode before selecting that option. Nothing changes in the device manager when plugged/unplugged. Windows doesn't attempt to install anything. It's as if I unplugged the cord once it enters recovery from the bootloader. I assume USB debugging is off, because it would be at the default setting. I tried using the Flash Stock + Unroot option in the Nexus Root Toolkit with the Soft-Bricked/Bootloop setting in, but that fails in both normal recovery (with the device unnoticed) and sideload mode. I'm guessing that debugging needs to be on for this?
Does anyone have any suggestions for other things to try? I have no way of knowing what the original owner may or may not have done, and this was the first time that I restarted the device, so I have no way to know if the problem was caused by the OTA or not.
EDIT: It looks like I made the situation worse. I attempted running the Flash Stock + Unroot option from the bootloader. I am not sure what happened, but now the device starts at the Google page with green start in an arrow. I have the bootloader options, and start and recovery options give me a "booting failed" message in the top left and just stay on the google page. Restarting the bootloader gives me the normal bootloader android image and the options have the same effects.

For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?

wioneo said:
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
Click to expand...
Click to collapse
still have a problem?

Wrong drivers, try other USB ports. Had that happen with another tablet. Only recognized in adb side load with galaxy nexus driver loading, possibly from universal adb drivers... Switched to a port on the other side and correct drivers finally worked.
Sent from my Le Pan TC1020 using Tapatalk

norwoodesteel said:
still have a problem?
Click to expand...
Click to collapse
As far as I know, no. I was never able to get the device is to be detected by my computer while in stock recovery mode, however it was detected after I flashed ClockworkMod Recovery. So I still have no idea what was causing that problem, but it is no longer relevant.