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.
I have a Verizon GN. My phone had root on it and for some reason now I don't. Super user says my SU binary cannot be found and ROM manager says an error occurred while attempting to run privileged commands. I tried flashing a different custom ROM so I shut the phone off and attempted to boot into the boot loader and go into recovery from there. Once the boot loader comes up the phone shuts rite off. Is there a way I can get into recovery other than fastboot, ROM manager or terminal emulator? The phone also shuts off as soon as I plug it in via USB.
dlnsrg said:
I have a Verizon GN. My phone had root on it and for some reason now I don't. Super user says my SU binary cannot be found and ROM manager says an error occurred while attempting to run privileged commands. I tried flashing a different custom ROM so I shut the phone off and attempted to boot into the boot loader and go into recovery from there. Once the boot loader comes up the phone shuts rite off. Is there a way I can get into recovery other than fastboot, ROM manager or terminal emulator? The phone also shuts off as soon as I plug it in via USB.
Click to expand...
Click to collapse
shutdown, vol up+power
bk201doesntexist said:
shutdown, vol up+power
Click to expand...
Click to collapse
I tried that. But the phone shuts down as soon as I let go of the buttons.
adb reboot recovery
3rdstring said:
adb reboot recovery
Click to expand...
Click to collapse
Phone shuts down as soon as USB cord is plugged in. Is there some sort of app that will let me boot into recovery or maybe update the SUbinary ?
AFAIK an app is going to need root to accomplish either of those tasks
3rdstring said:
AFAIK an app is going to need root to accomplish either of those tasks
Click to expand...
Click to collapse
So I'm screwed? Lol. The current ROM im running has no gapps. How can I download them without Gplay. Cruz I need to recover all my contacts from Google
If you can't get into fastboot to flash back to stock (or re-flash) a custom recovery, I would guess the next step would be flashing back to a stock image via odin. I've never had to use it (knockonwood) but I found this in the Verizon Dev forum
You may be able to use adb wireless to 'adb reboot recovery'.
https://play.google.com/store/apps/details?id=siir.es.adbWireless
Sent from my Galaxy Nexus using Tapatalk 2
That needs root.
3rdstring said:
If you can't get into fastboot to flash back to stock (or re-flash) a custom recovery, I would guess the next step would be flashing back to a stock image via odin. I've never had to use it (knockonwood) but I found this in the Verizon Dev forum
Click to expand...
Click to collapse
For some reason the phone shuts down as soon as its plugged in via USB ..
3rdstring said:
That needs root.
Click to expand...
Click to collapse
No it does not.
Adb over network only requires adb debugging to be enabled.
Sent from my Galaxy Nexus using xda premium
fire & ice said:
No it does not.
Adb over network only requires adb debugging to be enabled.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I was just reading from the app description
Rooted Phone Only!
Click to expand...
Click to collapse
---------- Post added at 07:55 AM ---------- Previous post was at 07:53 AM ----------
dlnsrg said:
For some reason the phone shuts down as soon as its plugged in via USB ..
Click to expand...
Click to collapse
Try ... a different USB cable, a different USB port, and if possible a different PC.
how can a device shut down when plugged in to usb?
perhaps OP has fastcharge on? does the wallcharger charge ok? maybe battery? I'd try battery. If it shuts down when you hook it up to usb, and with the wall charger, then I'd definately would go for the battery or the power source itself. do you have any UV set?
oh, maybe even a short on the usb pins with your pc's usb ports. even worse would be your nexus usb port just died.
bk201doesntexist said:
how can a device shut down when plugged in to usb?
perhaps OP has fastcharge on? does the wallcharger charge ok? maybe battery? I'd try battery. If it shuts down when you hook it up to usb, and with the wall charger, then I'd definately would go for the battery or the power source itself. do you have any UV set?
oh, maybe even a short on the usb pins with your pc's usb ports. even worse would be your nexus usb port just died.
Click to expand...
Click to collapse
I will definitely have to try a new battery. I have tried several USB cords. And different computers. And I always get the same results. The phone also shuts down on its own when its on sleep mode. Which is really annoying cuz I have to turn the phone back on every time the screen goes off.
fire & ice said:
No it does not.
Adb over network only requires adb debugging to be enabled.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks, I will look into this. I just need to find an apk download from a different source other than Gplay since I have no gapps
I don't know if it will work but ... adbWireless 1.4.1.apk
3rdstring said:
I don't know if it will work but ... adbWireless 1.4.1.apk
Click to expand...
Click to collapse
Okay I downloaded and installed the app. It gave me my IP address along with the port. But when I go to adb and try to ping my device adb says it can't connect.
infazzdar said:
You may be able to use adb wireless to 'adb reboot recovery'.
https://play.google.com/store/apps/details?id=siir.es.adbWireless
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
fire & ice said:
No it does not.
Adb over network only requires adb debugging to be enabled.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That app DOES need root...
Is there a way to gain temporary root access? I tried using z4root but it keeps force closing on me. Also I just went out and purchased a brand new extended battery and I still get the same results . It can't be my USB port either cuz it only turns of when plugged in to a PC but when plugged in to a wall charger its fine . I'm thinking its the kernel?
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
Heya, got an issue with a Galaxy Nexus phone. Phone does not seem to get any reception, I've attempted to add the Rogers network multiple times, and still either it says error or there is no reception at all. It is an unlocked phone, as the lock image shown upon restarting is unlocked, and as indicated in fastboot mode.
I figured it is the radio that is messed up. So I attempted to return to stock on my friend's phone. However, USB cable does not function properly, as I have attempted fastboot multiple times such as "fastboot devices" with the proper drivers installed etc. Using AirDroid to move the files, I've entered recovery mode only for it to load to the red triangle and then it restarts.
Also have repeated the steps after factory resetting. I am out of ideas guys, hoping maybe someone can provide some insight. Greatly appreciate it!!
Galaxy Nexus is the GSM one, not LTE. Thanks again.
-Thiefa
The red triangle is the stock recovery.
Having ADB working does not mean fastboot will work as well, they require different drivers, check in Device Manager for something like Android 1.0 or Android, then update drivers for it. There is a nice guide in this section by Jubakuba.
Mach3.2 said:
The red triangle is the stock recovery.
Having ADB working does not mean fastboot will work as well, they require different drivers, check in Device Manager for something like Android 1.0 or Android, then update drivers for it. There is a nice guide in this section by Jubakuba.
Click to expand...
Click to collapse
Will look into the guide.
The thing is, with the phone plugged into any computer, it doesn't show up at all on the device manager, in order for me to update the driver.
Use the gnexus toolkit
Sent from my Galaxy Nexus using xda app-developers app
ilmezzelfo said:
Use the gnexus toolkit
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Don't create a "HALPZ I IZ BRICKZ MAH FONE!!" thread later on.
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
http://forum.xda-developers.com/showthread.php?t=1469909
Mach3.2 said:
Don't create a "HALPZ I IZ BRICKZ MAH FONE!!" thread later on.
http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
I don't use the toolkit in general, but it's probably the easiest way to get the proper drivers installed.
raptir said:
I don't use the toolkit in general, but it's probably the easiest way to get the proper drivers installed.
Click to expand...
Click to collapse
Sorry, but if you think that, then you're holding it wrong.
Sent from my i9250
bk201doesntexist said:
Sorry, but if you think that, then you're holding it wrong.
Sent from my i9250
Click to expand...
Click to collapse
The drivers are a pain the the arse.
Actually, i did that for my N7, install the drivers and the toolkit never saw the light of the day anymore.
Btw regarding the naked drivers, plug the phone in > device manager > update drivers > then direct to the naked drivers folder right?
See the problem is I've updated the drivers and everything.
Whether in Odin, I don't see the phone pop up when I plug it in.
And no IMEI shows when I use a command prompt and attempted fastboot devices.
I'm just going to tell my friend to return it to Bell.
Thanks guys.
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