Related
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 side buttons is not working for me.(the volume keys)
Any one know any way to boot to recovery?
i have a logo loop now.so i can't enter to the system.
help:crying:
ilia333 said:
My side buttons is not working for me.(the volume keys)
Any one know any way to boot to recovery?
i have a logo loop now.so i can't enter to the system.
help:crying:
Click to expand...
Click to collapse
Use adb from bootlooping screen. The command is "adb reboot recovery". Adb is part of android SDK. There are plenty of guides on how to set up adb out there and its easy.
Sent from my Inspire 4G using xda premium
Gizmoe said:
Use adb from bootlooping screen. The command is "adb reboot recovery". Adb is part of android SDK. There are plenty of guides on how to set up adb out there and its easy.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
"device not found"
i hjave to enter to fastboot mod but i can't.
ilia333 said:
My side buttons is not working for me.(the volume keys)
Any one know any way to boot to recovery?
i have a logo loop now.so i can't enter to the system.
help:crying:
Click to expand...
Click to collapse
As Gizmoe told you..use adb commands to achive that. Use the guide in my signature to see how that is done. :good:
---------- Post added at 11:53 AM ---------- Previous post was at 11:52 AM ----------
ilia333 said:
"device not found"
i hjave to enter to fastboot mod but i can't.
Click to expand...
Click to collapse
Make sure that you have usb debugging enabled and the driver is installed correctly (with the phone unplugged)
glevitan said:
Make sure that you have usb debugging enabled and the driver is installed correctly (with the phone unplugged)
Click to expand...
Click to collapse
It is but i have to be in Hboot to apply the adb commands
ilia333 said:
It is but i have to be in Hboot to apply the adb commands
Click to expand...
Click to collapse
You can run adb from pretty much anywhere. Even if you were stuck in the splashscreen or in the rom.
Sent from a dream.
Teichopsia said:
You can run adb from pretty much anywhere. Even if you were stuck in the splashscreen or in the rom.
Sent from a dream.
Click to expand...
Click to collapse
but how can i check that usb debugging enabled?
if i cant accese the system?
ilia333 said:
but how can i check that usb debugging enabled?
if i cant accese the system?
Click to expand...
Click to collapse
You don´t to have be in hboot to use adb. You have to be with the phone on normally or from the splash screen itself. If you are in hboot then choose fastboot and try from there but using fastboot devices command instead.
As long as you have not factory reseted the phone the usb debugging drivers will stay in the phone.
ilia333 said:
but how can i check that usb debugging enabled?
if i cant accese the system?
Click to expand...
Click to collapse
USB debugging should always be enabled by default in any custom Rom. The thing that will disable it is doing factory reset from hboot screen. But you can't get there anyways so it should be enabled. Start the phone as normal and let it go to splash screen. Plug into pc and be sure to check that pc sees the phone. If not, unplug phone. Uninstall drivers. Re install drivers and then plug phone back in. From adb type "adb devices". You should see your device. After that run the "adb reboot recovery". If it still doesn't see it plug phone into different port. Preferably one that goes straight into mother board and remove any other USB devices that are plugged in.
Sent from my Inspire 4G using xda premium
glevitan said:
You don´t to have be in hboot to use adb. You have to be with the phone on normally or from the splash screen itself. If you are in hboot then choose fastboot and try from there but using fastboot devices command instead.
As long as you have not factory reseted the phone the usb debugging drivers will stay in the phone.
Click to expand...
Click to collapse
any other way to enable it ?
I did a factory reset.
i just installed a new rom.
thank you for trying to help any way/
Go to settings>Applications>development and check USB debugging.
If you're still getting device not recognized, you should reinstall HTC drivers by reinstalling HTC sync. ( if you haven't installed those in the first place, then you won't be able to use adb unless you do)
ilia333 said:
any other way to enable it ?
I did a factory reset.
i just installed a new rom.
thank you for trying to help any way/
Click to expand...
Click to collapse
When you say "factory reset," do you mean that you ran a RUU? Or that you chose "factory reset" in recovery, so you still have a custom ROM installed? If the answer is the latter, you probably have USB Debugging enabled. Just give ADB a try.
bananagranola said:
When you say "factory reset," do you mean that you ran a RUU? Or that you chose "factory reset" in recovery, so you still have a custom ROM installed? If the answer is the latter, you probably have USB Debugging enabled. Just give ADB a try.
Click to expand...
Click to collapse
I have a custom ROM.i did a factory reset from the recovery.
But i have message that "device not found".
ilia333 said:
I have a custom ROM.i did a factory reset from the recovery.
But i have message that "device not found".
Click to expand...
Click to collapse
Do you have the HTC sync drivers installed? If not, you should be able to find guides for it, like glevitan said.
bananagranola said:
Do you have the HTC sync drivers installed? If not, you should be able to find guides for it, like glevitan said.
Click to expand...
Click to collapse
Thank You guys !!!!
I did it.
From fuly turned off phone.
Weird, but hey. Whatever works. Glad you got it.
Sent from my Inspire 4G using xda premium
Bump Bump Bump!!!
I have the same problem with HTC Desire HD!
And guess what? It belongs to my wife!!! And I have to give it back to her or I should stay several nights
in the street.... and instead of a pillow I should put a cat or something under my head!
Problem.... Stuck at htc boot screen... not able to enter recovery
I installed 4ext recovery ages ago....
the main problem is that the volume keys ( both up and down ) are broken and neither of them work!
adb restart recovery doesn't work
no device find!
yes I installed all the drivers, and I can boot other phones into recovery
What should I do?
Please help!
tanx!
hrkh83 said:
Bump Bump Bump!!!
I have the same problem with HTC Desire HD!
And guess what? It belongs to my wife!!! And I have to give it back to her or I should stay several nights
in the street.... and instead of a pillow I should put a cat or something under my head!
Problem.... Stuck at htc boot screen... not able to enter recovery
I installed 4ext recovery ages ago....
adb restart recovery doesn't work
no device find!
yes I installed all the drivers, and I can boot other phones into recovery
What should I do?
Please help!
tanx!
Click to expand...
Click to collapse
How did you end like this? can you access hboot?
glevitan said:
How did you end like this? can you access hboot?
Click to expand...
Click to collapse
How?
I installed the R26.2 successfully, the JB Rom I mean..
Then installed all the tweaks in PIMP my ride successfully again ( I am not a noob.... )
That didn't triggered it...
At the end I was trying to install Int2ext+ and it happened....! I don't know why!
I had done this before on various phones.... I don't know what happened!
The only thing I was able to access so far was HTC BOOT SCREEN! :laugh: and I also
can access a choke hold from my wife soon I guess!
I don't know why these things always happen to her phone... other friends phones are fine when
I change their roms bla bla bla!
hrkh83 said:
How?
I installed the R26.2 successfully, the JB Rom I mean..
Then installed all the tweaks in PIMP my ride successfully again ( I am not a noob.... )
That didn't triggered it...
At the end I was trying to install Int2ext+ and it happened....! I don't know why!
I had done this before on various phones.... I don't know what happened!
The only thing I was able to access so far was HTC BOOT SCREEN! :laugh: and I also
can access a choke hold from my wife soon I guess!
I don't know why these things always happen to her phone... other friends phones are fine when
I change their roms bla bla bla!
Click to expand...
Click to collapse
Pull the battery and then put it back. And try to boot, pressing power + volume down until you get hboot.
Sent from my GT-N7000 using xda app-developers app
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??
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.
I am trying to update the HTC One VX AT&T version to the new JB official rom. however, i cannot use the update software on the phone or the recommended manual update as described at htc's website.
I have previously rooted and unlocked via the HTC developers code that they sent to me, and that all went fine. However, now my PC will not recognize the phone when it is in fastboot, and the HBOOT menu says I am ***TAMPERED***
Phone is recognized via HTC Sync program, and will go throught the initial steps in the RUU update file from HTC.com but as soon as the bootloader starts up, I is unrecognized again...
If anyone has any ideas or recommendations, or if there is any more information I can give you, please let me know.
Thanks in advance!
bobdallama said:
I am trying to update the HTC One VX AT&T version to the new JB official rom. however, i cannot use the update software on the phone or the recommended manual update as described at htc's website.
I have previously rooted and unlocked via the HTC developers code that they sent to me, and that all went fine. However, now my PC will not recognize the phone when it is in fastboot, and the HBOOT menu says I am ***TAMPERED***
Phone is recognized via HTC Sync program, and will go throught the initial steps in the RUU update file from HTC.com but as soon as the bootloader starts up, I is unrecognized again...
If anyone has any ideas or recommendations, or if there is any more information I can give you, please let me know.
Thanks in advance!
Click to expand...
Click to collapse
If you were unlocked and s-on then you must relock bootloader before updating with ruu.
Just type this in fastboot, without the quotes
"Fastboot oem lock" in command prompt.
Sent from my HTC One VX using xda premium
el_venga said:
If you were unlocked and s-on then you must relock bootloader before updating with ruu.
Just type this in fastboot, without the quotes
"Fastboot oem lock" in command prompt.
Sent from my HTC One VX using xda premium
Click to expand...
Click to collapse
how would one do this if phone is not recognized in fastboot mode via adb?
uninstall htc sync. drivers will stay. sync gets in the way sometimes. I just used the ruu from the htc site and the setup wizard did it all. very easy, you could do it that way, no need to relock bootloader. or flash one of the Jellybean roms jmz has out. that would be the easiest way.
Thanks. Tried uninstalling HTC sync, and rebooting my pc. Still hangs when the phone restarts into bootloader. Still telling me it is unrecognized...
Sent from my LG-E970 using xda app-developers app
bobdallama said:
how would one do this if phone is not recognized in fastboot mode via adb?
Click to expand...
Click to collapse
hboot and fastboot menus are the same. the tampered part is because of the custom recovery. if you are selecting fastboot and pc is not detecting the device, thats odd. if you havent, change usb port and cable.
it is possible to get drivers issues with fastboot/hboot. when connecting usb cable after fastboot is selected does it change to FASTBOOT USB?
did you turn USB debugging on? are you going to fastboot after going into the bootloader?
el_venga said:
hboot and fastboot menus are the same. the tampered part is because of the custom recovery. if you are selecting fastboot and pc is not detecting the device, thats odd. if you havent, change usb port and cable.
it is possible to get drivers issues with fastboot/hboot. when connecting usb cable after fastboot is selected does it change to FASTBOOT USB?
Click to expand...
Click to collapse
I have tried with about 3 different USB cables, and every different available USB port. all to no avail. If i select fastboot manually by holding the power and volume down, then it will say fastboot, until I push the volume up or down, then it will switch to fastboot usb.
when the RUU program triggers a reboot into the fastboot mode (I'm assuming that's what it is trying to do, anyway) it just hangs on a black screen with a big white HTC logo, until the program times out and I have to exit. Restarting the phone is no issue, because it just starts up like normal.
Johann12911 said:
did you turn USB debugging on? are you going to fastboot after going into the bootloader?
Click to expand...
Click to collapse
USB debugging is on, and see above reply regarding fastboot.
Thanks everyone for their help so far...I know we can get to the bottom of this!
bobdallama said:
I have tried with about 3 different USB cables, and every different available USB port. all to no avail. If i select fastboot manually by holding the power and volume down, then it will say fastboot, until I push the volume up or down, then it will switch to fastboot usb.
when the RUU program triggers a reboot into the fastboot mode (I'm assuming that's what it is trying to do, anyway) it just hangs on a black screen with a big white HTC logo, until the program times out and I have to exit. Restarting the phone is no issue, because it just starts up like normal.
Click to expand...
Click to collapse
Do "fastboot oem rebootRUU". You should see the device in device manager. Then run the ruu again.
Sent from my HTC One VX using xda premium
Same deal if I reboot to fastboot via ADB or manually with the phone. As soon as I enter fastboot, no longer recognized by the computer.
Sent from my LG-E970 using xda app-developers app
bobdallama said:
Same deal if I reboot to fastboot via ADB or manually with the phone. As soon as I enter fastboot, no longer recognized by the computer.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
you said that the phone gets into black screen with htc white letters. that means normal fastboot still works because the RUU sends that same command. i ask you again to check windows device manager and see if your device is there. if its not, try unplug and replug usb cable.
Unplugging and plugging the cord back in did nothing. Device manager lists the device as unknown. It says something about device reporting error.
Sent from my LG-E970 using xda app-developers app
bobdallama said:
Unplugging and plugging the cord back in did nothing. Device manager lists the device as unknown. It says something about device reporting error.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Try another pc. Either laptop or desktop, even both.
Sent from my HTC One VX using xda premium
el_venga said:
Try another pc. Either laptop or desktop, even both.
Sent from my HTC One VX using xda premium
Click to expand...
Click to collapse
OK. I will try that. I'm running a system I built myself with Windows 8. Do you think that windows 8 is causing some issues? my wife's laptop is still windows 7...I will try that tonight. fingers crossed!
So I tried on windows 7, and the RUU is able to get as far as the part that says updating signature, at which point it sits there for a few minutes, then gives me error 132 and tells me to download the correct rom update utility for my phone??!
Is there any chance that having twrecovery is causing this? If so, an ideas on how to go back to stock recovery?
Sent from my LG-E970 using xda app-developers app
bobdallama said:
So I tried on windows 7, and the RUU is able to get as far as the part that says updating signature, at which point it sits there for a few minutes, then gives me error 132 and tells me to download the correct rom update utility for my phone??!
Is there any chance that having twrecovery is causing this? If so, an ideas on how to go back to stock recovery?
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
If you are s-on then you have to relock bootloader to flash ruu.
Sent from my HTC One VX using XDA Premium 4 mobile app