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??
Related
Ok so the other day i turned my phone on and it went straight into the bootloader and the volume and power buttons arent responding. When i try to connect to adb it doesnt recognize that the phone is connected. I know i have adb set up right cause i can connaect my HD2 to it and it connects fine. I searched on here but couldnt find an answer and i dont wanna do anything that could make the situation worse. Does anyone know what i should do or is there a thread somewhere that would help me? Thanks
Anyone? I also have it rooted with eng-hboot and s-off and have been on CM7 for a while. I dont think its a prob with the wrong drivers either cause i have htc sync installed . I did try PDAnet but it fails at the last step and says something about failed to handshake.
Think i posted this in the wrong section.
Daryl Keith said:
Ok so the other day i turned my phone on and it went straight into the bootloader and the volume and power buttons arent responding. When i try to connect to adb it doesnt recognize that the phone is connected. I know i have adb set up right cause i can connaect my HD2 to it and it connects fine. I searched on here but couldnt find an answer and i dont wanna do anything that could make the situation worse. Does anyone know what i should do or is there a thread somewhere that would help me? Thanks
Click to expand...
Click to collapse
Are you s-off or s-on? If it's s-off try putting an ruu as a pc10img.zip on your sdcard and flashing it through bootloader.
if that dont work......
Try removing your SD card, then see if you can get to recovery through the BL.
if that dont work......
You need adb. I'm not saying it will work but its worth a shot. If you don't know adb there is a guide in the dev section.
If you can get adb connected to your device after you adb shell into phone you can run "adb reboot recovery".
If you have the fastboot binary, type this in your computer's Terminal:
fastboot reboot
Click to expand...
Click to collapse
blackknightavalon said:
If you have the fastboot binary, type this in your computer's Terminal:
Click to expand...
Click to collapse
I'm having the same darn issue...I tried the fastboot connect command "reboot recovery"and it does the reboot but comes right back to the boot loader screen no options to scroll and select anything...phone was fine until it froze and couldnt do no reboot power down or anything had no choice to pull the battery...theirs gotta be a work around on this...
im also having a problem, my phone has broken volume buttons, i can get to recovery but after that i dont know what to do since theres no volume buttons. i want to refllash cm7 but how?
stumpyz9 said:
im also having a problem, my phone has broken volume buttons, i can get to recovery but after that i dont know what to do since theres no volume buttons. i want to refllash cm7 but how?
Click to expand...
Click to collapse
Use the trackpad
Sent from my HTC Vision using xda premium
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.
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.
Was trying to get my Gnex back to factory trying every way possible to use adb and could get the files to find their way to my phone. So finally i said hell with it and Second try fails and i unplug it to try and turn it back on and i get a screen with a phone and computer and a yellow triangle in the middle of both. Will not boot into anything. But when i plug it into my computer it will make the noise that something is plugged in and i try odin again and i can see the blue bar on my phone like its trying to download something to it, So i dont know where to go from here. Any way in hell i could take it to Verizon and have them do a factory reset? Any help would be appreciated.
Can you get into fastboot ? And do you have drivers installed?
Sent from my GNexus
ray3andrei said:
Can you get into fastboot ? And do you have drivers installed?
Sent from my GNexus
Click to expand...
Click to collapse
To be honest i lack the knowledge of knowing everything unless i am following a guide on how to do things. So if i plug my phone in and here the sound it makes to connect and pull up a command prompt i type in adb fastboot and it brings up this long list of commands. Is this what you are talking about?
aaronstrong1988 said:
To be honest i lack the knowledge of knowing everything unless i am following a guide on how to do things. So if i plug my phone in and here the sound it makes to connect and pull up a command prompt i type in adb fastboot and it brings up this long list of commands. Is this what you are talking about?
Click to expand...
Click to collapse
Type adb devies and see if anything comes back.
drake90001 said:
Type adb devies and see if anything comes back.
Click to expand...
Click to collapse
yes list of devices came back so that works
aaronstrong1988 said:
yes list of devices came back so that works
Click to expand...
Click to collapse
What device names came back? Did it actually list any serial numbers?
drake90001 said:
What device names came back? Did it actually list any serial numbers?
Click to expand...
Click to collapse
after i typed in adb devices it came back with
*daemon not running. starting in now on port 5037*
*daemon started successfully*
List of devices attached
and thats all
Then your device is not recognized by adb. So it's not working. If it was it would've shown a serial #.
063_XOBX said:
Then your device is not recognized by adb. So it's not working. If it was it would've shown a serial #.
Click to expand...
Click to collapse
how do i get it to show my serial number?
aaronstrong1988 said:
how do i get it to show my serial number?
Click to expand...
Click to collapse
You install the correct driver
Sent from my Galaxy Nexus using Tapatalk 2
Use the Galaxy Nexus tool. It is fantastic.
It installs all drivers and really is helpful and straight forward.
Sent from my Galaxy Nexus using xda premium
Yupp, unfortunately the drivers are probably the hardest part.. I never managed to get them working on first try...
Anyhow, download the latest Android sdk and have it download the Usb Drivers section if you didn't already. Then try installing those drivers. Remember you have to reboot your pc after each try (trust me, there will be multiple tries) otherwise it won't work.
Once you got the drivers installed get back to us. And don't panic, your phone's fine.
Sent from my Galaxy Nexus
Lazer Bear said:
Yupp, unfortunately the drivers are probably the hardest part.. I never managed to get them working on first try...
Anyhow, download the latest Android sdk and have it download the Usb Drivers section if you didn't already. Then try installing those drivers. Remember you have to reboot your pc after each try (trust me, there will be multiple tries) otherwise it won't work.
Once you got the drivers installed get back to us. And don't panic, your phone's fine.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
i hope so i will uninstall sdk and try it all over
Ok, I'm praying that someone can help me with a solution to this problem.
I have a T-Mobile Galaxy S2 that has a fantastically cracked LCD & Digitizer. It's so bad that the screen doesn't even turn on anymore. Maybe the ribbon cable is disconnected when I slammed the phone down on the counter thus cracking the screen. Who knows but I don't really want to tear it apart to find out.
Anyway the phone was rooted and running:
Juggernaut_50_0218
Blaze_4G_LB7
Sadly there is a pattern lock and I can't see the dumb screen to unlock it or do anything period. I know the phone works because I put the battery in and turn on the phone and I see all the touch buttons at the bottom light up.
Now, Kies doesn't even recognize the rooted device and I need to get my stuff off. Yes I know, I should've backed everything up but let's just say it was a hard learned lesson.
I know someone must've been able to get their files off their device that was in a similar situation. :crying:
Xyberz said:
Ok, I'm praying that someone can help me with a solution to this problem.
I have a T-Mobile Galaxy S2 that has a fantastically cracked LCD & Digitizer. It's so bad that the screen doesn't even turn on anymore. Maybe the ribbon cable is disconnected when I slammed the phone down on the counter thus cracking the screen. Who knows but I don't really want to tear it apart to find out.
Anyway the phone was rooted and running:
Juggernaut_50_0218
Blaze_4G_LB7
Sadly there is a pattern lock and I can't see the dumb screen to unlock it or do anything period. I know the phone works because I put the battery in and turn on the phone and I see all the touch buttons at the bottom light up.
Now, Kies doesn't even recognize the rooted device and I need to get my stuff off. Yes I know, I should've backed everything up but let's just say it was a hard learned lesson.
I know someone must've been able to get their files off their device that was in a similar situation. :crying:
Click to expand...
Click to collapse
Try booting into recovery and copy whatever possible, I'm not sure about installed files though :/
Maybe you could use adb or something
I can't see the screen to be able to even know which screen it's at. How would I do that?
Hopefully you had debigging enabled. If you did, boot it up normal. Then use the adb pull command from your computer. HTH
Sent from my SGH-T989 using Tapatalk 2
ackliph said:
Hopefully you had debigging enabled. If you did, boot it up normal. Then use the adb pull command from your computer. HTH
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure but I'm assuming it was since the phone was rooted with a custom rom. It's been a little while since I've seen this phone on.
Don't know how to use ADB pull command and what software to do it with.
Xyberz said:
I'm not sure but I'm assuming it was since the phone was rooted with a custom rom. It's been a little while since I've seen this phone on.
Don't know how to use ADB pull command and what software to do it with.
Click to expand...
Click to collapse
I'm not by my computer now, but I'll try to steer you in the right direction. Adb.exe should be on your computer somewhere. If not, do a google search. Usually you can find adb.exe and fastboot.exe packaged together. You'll then want to use adb to pull your files. Open up a command prompt. Change to the directory that has adb.exe. then type "adb pull /data \data" you can also try "adb pull /sdcard \sdcard"
You can also try the adb pull command after you boot into recovery mode. Play with it. I bet you can do it.
Sent from my SGH-T989 using Tapatalk 2
---------- Post added 27th February 2013 at 12:02 AM ---------- Previous post was 26th February 2013 at 11:59 PM ----------
Here is adb in the download section on the first post.
http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1
Sent from my SGH-T989 using Tapatalk 2
ackliph said:
I'm not by my computer now, but I'll try to steer you in the right direction. Adb.exe should be on your computer somewhere. If not, do a google search. Usually you can find adb.exe and fastboot.exe packaged together. You'll then want to use adb to pull your files. Open up a command prompt. Change to the directory that has adb.exe. then type "adb pull /data \data" you can also try "adb pull /sdcard \sdcard"
You can also try the adb pull command after you boot into recovery mode. Play with it. I bet you can do it.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Ok, I will try this later on when I get home from work. I'm praying it works but hate using command prompts lol. GUI is always easier but I can't complain if it works!