Develop Bugs

[Q] Boot into bootloader without volume keys

My volume keys aren't working, and my phone is bootlooping after I tried to unroot it. The volume keys not working is a hardware issue. Is there anything I can do on the computer end to boot into the bootloader?
Thanks
Alec

Try to get adb to work for you.
If the system bootloops after adb service is brought up, you can try using 'adb reboot recovery' or 'adb reboot bootloader'.
If you made it, get back to stock and turn it in for the killing.

alec534 said:
My volume keys aren't working, and my phone is bootlooping after I tried to unroot it. The volume keys not working is a hardware issue. Is there anything I can do on the computer end to boot into the bootloader?
Thanks
Alec
Click to expand...
Click to collapse
bk201doesntexist said:
Try to get adb to work for you.
If the system bootloops after adb service is brought up, you can try using 'adb reboot recovery' or 'adb reboot bootloader'.
If you made it, get back to stock and turn it in for the killing.
Click to expand...
Click to collapse
It's bootlooping at the Google logo, and so adb isn't recognizing it. Frown. Thanks for your idea though.

alec534 said:
My volume keys aren't working, and my phone is bootlooping after I tried to unroot it. The volume keys not working is a hardware issue. Is there anything I can do on the computer end to boot into the bootloader?
Thanks
Alec
Click to expand...
Click to collapse
You can type adb reboot-bootloader in a command prompt. You can also download Quick Boot from the market, and you can reboot into the bootloader from your device.
EDIT: Oops, I took to long in replying... didn't see that it was already suggested.
EDIT 2: Mis-read your post. Think you are out of luck.
Sent from my Galaxy Nexus using Tapatalk

efrant said:
You can type adb reboot-bootloader in a command prompt. You can also download Quick Boot from the market, and you can reboot into the bootloader from your device.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
All I get is a "device not found" error. Adb doesn't seem to recognize the phone while it's bootlooping.

You can buy a jig for it to force it into boot loader. I also used it on mine to force it into boot loader download. Purchased one just in case something bad happened.
http://www.amazon.com/gp/aw/d/B0053...ile?redirect=true&ref_=oh_o00_s00_i00_details
Sent from my Galaxy Nexus using Tapatalk

purelife82 said:
You can buy a jig for it to force it into boot loader. I also used it on mine to force it into boot loader download. Purchased one just in case something bad happened.
http://www.amazon.com/gp/aw/d/B0053...ile?redirect=true&ref_=oh_o00_s00_i00_details
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
You are a life-saver if this works on the Nexus too. Thanks so much.

its works on my nexus.
Sent from my Galaxy Nexus using Tapatalk

Broken powerbutton, need to unroot and re-lock

Hey all,
My power button stopped working and I, thinking it was a software issue, pulled the battery and found out I could not restart. I need to get into recovery or at least turn on the phone to unroot and relock it before heading to verizon.
So far I have had no luck turning the phone back on. I'm sure there is a way to do this... any help is greatly appreciated.

You can use a jig to go into the download mode
And flash a rom
Sent from my GT-N7000 using xda premium

Is the jig the only option? I don't currently have a jig so if that's the only thing I can do I will need to order one ASAP so I can get this thing working.
danteoo7 said:
You can use a jig to go into the download mode
And flash a rom
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse

evahnyird said:
Hey all,
My power button stopped working and I, thinking it was a software issue, pulled the battery and found out I could not restart. I need to get into recovery or at least turn on the phone to unroot and relock it before heading to verizon.
So far I have had no luck turning the phone back on. I'm sure there is a way to do this... any help is greatly appreciated.
Click to expand...
Click to collapse
you might want to check this out..
http://www.ifixit.com/Answers/View/84579/Power+Button+stopped+responding.+Phone+will+not+turn+on.

Try to start it via adb, usb connect it, then type in adb devices, and then just adb reboot bootloader
Sent from my Sensation using xda premium

DesperadoX93 said:
Try to start it via adb, usb connect it, then type in adb devices, and then just adb reboot bootloader
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
Are you talking about in command prompt? I tried
Code:
adb-windows.exe devices
which returns " list of devices attached" with none listed.

If you can't get it to turn on they won't be able to either it will probably be fine.
Sent from my Galaxy Nexus using xda premium

Beamer9408 said:
If you can't get it to turn on they won't be able to either it will probably be fine.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The issue is that the phone is in no way broken other than the power button. I'll have to take it in and hope for the best if I can't figure something out, but I'd really like the peace of mind knowing that all of my files and data aren't stuck on it (I'd also like to get my lastest nandroid or do another one).
I saw a timing trick on http://forum.xda-developers.com/showthread.php?t=1731128 that is supposed to allow the device to boot, but I haven't gotten it to work yet.

Google wugfresh nexus root toolkit
It has a simple one click fix for flashing stock and unrooting when the device can't boot up

Or you can use something like glados cp to relock the boot loader as your rooted then delete the superuser apk in system app
Sent from my Galaxy Nexus using xda premium

I've gotten the phone into download mode using a jig, but it still doesn't seem to be recognized by the computer. Is this an issue of re-installing the Samsung drivers/adb or a limitation of download mode? Do I need to use odin?

evahnyird said:
I've gotten the phone into download mode using a jig, but it still doesn't seem to be recognized by the computer. Is this an issue of re-installing the Samsung drivers/adb or a limitation of download mode? Do I need to use odin?
Click to expand...
Click to collapse
Are you sure you have ADB configured properly for the device to be picked up via command line? USB debugging would have to of been turned on for ADB commands..

I'm almost positive USB debugging is on, especially since I think it's a default option in kang. I can get into download mode but not anything else. At this point I think I'm going to have to use ODIN and lose my data. Stupid power button...

Try removing the battery then tapping the metal battery pins against the phone pins repeatedly.
A friend of mine used to have to do this to get his nexus one to boot.. it can be a bit temperamental but does work.

evahnyird said:
I've gotten the phone into download mode using a jig, but it still doesn't seem to be recognized by the computer. Is this an issue of re-installing the Samsung drivers/adb or a limitation of download mode? Do I need to use odin?
Click to expand...
Click to collapse
Make sure you have the correct drivers installed. From download mode you will have to use Odin.
Note: since the device won't actually boot into Android, you don't have to worry about USB Debugging.
Note x2: the only driver that would let my device be recognized was the PDA Net driver, you may want to give it a try.
Sent from my Galaxy Nexus using Tapatalk 2

Well guys, thanks for all the suggestions. In the end I could get nothing to work other than Download mode with a jig and Odin to restore to stock. I lost everything on the phone, including my nandroid backups (should have copied them over more recently ...), but was able to re-lock the bootloader with nexus root toolkit after using Odin to flash the stock rom. ]
Moral of the story, if you lose your power button, you are screwed.

DesperadoX93 said:
Try to start it via adb, usb connect it, then type in adb devices, and then just adb reboot bootloader
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
Unfortunately you can't use adb to turn on a powered off device; not saying that wouldn't be awesome.

[Q] Broken Power button. Need to Boot Into Recovery

I managed to download an app that will wake the phone up with the proximity sensor but I cant seem to find a workaround to get into recovery. I remember using the command prompt to give the phone commands before we were spoiled with a convenient toolkit. Does anyone have any ideas?I want to unroot and take it back to get it replaced.

blacknsb said:
I managed to download an app that will wake the phone up with the proximity sensor but I cant seem to find a workaround to get into recovery. I remember using the command prompt to give the phone commands before we were spoiled with a convenient toolkit. Does anyone have any ideas?I want to unroot and take it back to get it replaced.
Click to expand...
Click to collapse
adb reboot recovery. Certain apps also add the functionality (with root) Switch Pro & Widgetsoid to name a few

I guess I was a little too hasty. I updated the Galaxy Nexus toolkit and it now has boot options!

blacknsb said:
I guess I was a little too hasty. I updated the Galaxy Nexus toolkit and it now has boot options!
Click to expand...
Click to collapse
You shouldn't rely on toolkits. Basic adb and fastboot commands are very easy to learn and remember. They are also universal with any android device.
Take a look at efrants android 101 guide in the Q&A stickies. It has a lot of valuable information.
Sent from my Nexus 7 using xda premium

Just install quickboot from the market and your problem is solved.

RogerPodacter said:
Just install quickboot from the market and your problem is solved.
Click to expand...
Click to collapse
what if i cant get my phone on because my power button is broken but want to boot into recover...is that possible?

physically bricked?

phone stuck in bootloop. the kicker is my volume rocker is shot. and adb doesnt recognize while still in boot up. aaaaaaaaaaand the warranty is definetly not an option since i have had the inductive charge mod for quite some time now. if anyone knows of a way to go into recovery mode without turning the device on, OR pressing the volume buttons, please, come forth....

I think if all of those are true, you're SOL. In order for ADB or Fastboot commands from your PC to work, the phone must either be in the Bootloader or in Android with USB debugging on.
And to get into Bootloader, you must have a working volume rocker.... Are you sure you can't like hit it and it'll work or something like that?
Otherwise, your best bet is to send it in for warranty replacement and hope they won't notice, which might not be as much of a long shot as you think...

jimmyco2008 said:
I think if all of those are true, you're SOL. In order for ADB or Fastboot commands from your PC to work, the phone must either be in the Bootloader or in Android with USB debugging on.
And to get into Bootloader, you must have a working volume rocker.... Are you sure you can't like hit it and it'll work or something like that?
Otherwise, your best bet is to send it in for warranty replacement and hope they won't notice, which might not be as much of a long shot as you think...
Click to expand...
Click to collapse
Well if they turn it on wouldn't they notice the different bootup animation and the fact that it wont turn on? Who should I send it to? Google or Samsung? And how? Do u know of a best method?

bump for possible genius to know if theres a way to enter recovery without volume rocker or phone being on.

Are you stuck at the Google screen and when you use adb does it just say waiting for device?
Sent from my Galaxy Nexus using xda app-developers app

Andro X said:
Are you stuck at the Google screen and when you use adb does it just say waiting for device?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
no it goes past the google screen and gets stuck on the bootup image. it happened when i flashed superROM. it never went past the bootup image after that. and adb commands say "waiting for device" yes.

Ok. Are you using windows on your pc?
Sent from my Galaxy Nexus using xda app-developers app

Andro X said:
Ok. Are you using windows on your pc?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
yeah. windows

Oh yeah what about ODIN? That might work for getting back to stock and a working Android OS that'll actually boot up.
That's probably why he's asking. Forgot all about ODIN. Although the fact that you can't boot up might be an issue... I'm gonna hand this over to Andro X.
I just meant hit like a light hit on the volume rocker to see if it'll knock something back into place...I don't think it'll really work though, I just gave out a sort of last resort option.

donavo said:
yeah. windows
Click to expand...
Click to collapse
Make a command prompt shortcut on your desktop. Right click and click new then shortcut then cmd for location and cmd for name. Once that's done right click on the cmd shortcut you made and run as administrator. Then adb kill-server and then adb start-server. Now try adb devices and see if your device is now recognized. If it is then awesome you can get to recovery by adb reboot recovery and bootloader by adb reboot bootloader.
Edit...
Just noticed I typed killer server lol by accident. It's adb kill-server. Now fixed above.

Andro X said:
Make a command prompt shortcut on your desktop. Right click and click new then shortcut then cmd for location and cmd for name. Once that's done right click on the cmd shortcut you made and run as administrator. Then adb kill-server and then adb start-server. Now try adb devices and see if your device is now recognized. If it is then awesome you can get to recovery by adb reboot recovery and bootloader by adb reboot bootloader.
Edit...
Just noticed I typed killer server lol by accident. It's adb kill-server. Now fixed above.
Click to expand...
Click to collapse
i type "adb kill-server" in the cdm prompt that opens after i run it as admin? cuz it dsnt look like that does anything...and it still says device not found

I'm new here, coming from another phone, a Galaxy S variant. There, we had a little contraption called a download jig. You put that thingie into a USB port, and a phone goes straight into the download mode. Don't know if such thing exists for Nexus. Does it?
Sent from my SGH-T959V using xda app-developers app

Hmm... That's something you could do. A jib..... I'd like to know more, perhaps it will work, they're both Samsung, after all.
Andro X, I was hoping you were leading to ODIN lol.
What about ODIN? Try getting that set up and hitting start on ODIN just as you power on your Galaxy Nexus. Don't hold your breath, though, it may fail like getting adb commands working, because you're not in bootloader or Android.
adb kill-server is instantaneous, you wouldn't see any real output on command prompt- that is normal.

jimmyco2008 said:
Hmm... That's something you could do. A jib..... I'd like to know more, perhaps it will work, they're both Samsung, after all.
Andro X, I was hoping you were leading to ODIN lol.
What about ODIN? Try getting that set up and hitting start on ODIN just as you power on your Galaxy Nexus. Don't hold your breath, though, it may fail like getting adb commands working, because you're not in bootloader or Android.
adb kill-server is instantaneous, you wouldn't see any real output on command prompt- that is normal.
Click to expand...
Click to collapse
yeah but making th enew shortcut didnt help. i went to program files/android master. shift right click and open a cmd window there. from there i did the commands. there was some response but still the phone was not found

okay here is what im coming up with. i can open the phone and find the contacts for where the volume attaches. does anyone know what i can do from there? soldering the volume button back on is not an option. ive been trying that all day. only thing left is shorting the contacts so the phone is fooled into a state where the buttons are held. there are 3 contacts. anyone know which ones i should be shorting? or if thats even workable? i may have completely screwed the contacts by now....ive tried maybe 40 times.

OMG!!!!!! i just did some soldering. pressed power button and now im in ODIN MODE. idk what this means.....all it says is "downloading do not turn off target. what do i do??????

Uh... Flash something
I777 gets it done, gnex just for fun

Cmoore0965 said:
Uh... Flash something
I777 gets it done, gnex just for fun
Click to expand...
Click to collapse
how?? it wont let me do anything. its in odin mode....cant do recovery with adb. not sure what odin mode even does

donavo said:
how?? it wont let me do anything. its in odin mode....cant do recovery with adb. not sure what odin mode even does
Click to expand...
Click to collapse
if you have correctly installed the samsung drivers, you can flash a rom via odin (proggram on your computer.)

thegtfusion said:
if you have correctly installed the samsung drivers, you can flash a rom via odin (proggram on your computer.)
Click to expand...
Click to collapse
oh man do i need ur help now. how do i do that? when i rooted the phone im sure all the drivers installed correctly. but where do i get the odin program??

[Q]Galaxy Nexus really bricked? No ADB/Recovery [HELP]

My Galaxy Nexus won’t boot into Paranoid Android after flashing a mod. It is not in a real bootloop (I don’t see a reboot including the Google splash screen) but keeps loading/booting the rom (Paranoid Android Logo). Reflash through recovery you would think.
Problem: my volumekeys are broken (cable broken when replacing USB-port)
So I can’t enter recovery with volume buttons. Therefor I wanted to use ADB commands but I only get ‘device not found’ when I type ADB devices or ADB reboot recovery.
ADB has always worked on this laptop so the drivers are installed correctly. Just to be sure I reinstalled the ADB drivers but with no success.
When I connect my Galaxy Nexus while in bootloop I see the Windows device manager showing: Galaxy Nexus (and after reinstall of ADB drivers it says Samsung Galaxy Nexus ADB Interface)
TLDR: Galaxy Nexus wont respond to ADB commands.
How to enter bootloader/recovery/push working rom or solve my problem any other way?

Try the galaxy nexus toolkit. It has an option for recovery even when ADB seems to be unavailable. Worked for me as my device was bricked.

wictor1992 said:
Try the galaxy nexus toolkit. It has an option for recovery even when ADB seems to be unavailable. Worked for me as my device was bricked.
Click to expand...
Click to collapse
Thank you for your reply. Could you tell me which option? Im in the toolkit now but can't seem to find the exact option you mentioned.

Is USB debugging on?
Sent from my i9250

bk201doesntexist said:
Is USB debugging on?
Sent from my i9250
Click to expand...
Click to collapse
To be honest I don't know. Since I just flashed Paranoid Android and booted my GN to see if it worked (which did) I immediately rebooted to flash the Mod. So it depends on the standard setting for this specific ROM.
Say it is not on, is there any way I could activate it without ADB and volume keys for recovery?
Im starting to think the only chance would be to buy new volume buttons strip and replace it myself.
I just don't get is why Windows recognises a Samsung Galaxy Nexus ADB Interface when i connect my phone while in bootloop and still the ADB drivers do not work.

bk201doesntexist said:
Is USB debugging on?
Sent from my i9250
Click to expand...
Click to collapse
this.. most likely debugging if not on

k786 said:
this.. most likely debugging if not on
Click to expand...
Click to collapse
I guess that is a problem, however i read some topics where people say that ADB should still work without USB Debugging on so I'm not really sure if that is the problem or not. Honestly I would think USB debugging would be on by default on a custom ROM to enable ADB in case of a bootloop.
Anyway, what are my options besides hardware repair volume button or buy new phone?

I'm having almost the exact same problem. Would appreciate it if you could PM me if you find a solution. Thanks.
Sent from my MB860 using xda app-developers app

mitchell.23 said:
I'm having almost the exact same problem. Would appreciate it if you could PM me if you find a solution. Thanks.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Unless someone knows a way to force ADB connection i think it will be a hardware repair for the volume button. If you find a solution let me know as well

there has to be a way

victor00100 said:
there has to be a way
Click to expand...
Click to collapse
Real helpful....
Anyway..if you can get to the bootanimation you're not bricked...even with the volume buttons not working. How badly are your volume buttons broken?
It should be possible if you know a bit of electrical stuff...if you find a way to close the circuit between the volume buttons then press the press the power button. It is possible...I just took apart my phone and if that isn't a problem for you, then it is possible to manually close the circuit.