Hello guys,
So I have an unlocked, unroot AT&T HTC One X, running stock rom JB 4.1.2 & Sense 4. The other day I was just using it when all of a sudden the phone froze & stop responding. I pressed and held the power button, trying to reset it. Ever since then, it had been stuck in a boot loop ("HTC -quietly brilliant" appeared, then reboot). I did not have any recovery like TWRP installed or anything similar. When I tried to enter HBoot, this is what I get"
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012,18:37:14:-1
and a bunch of options as usual. I tried everything from factory reset, clear storage, to recovery, but nothing works. I tried fastboot then install the RUU, but when I plug the phone in the USB port, it is not recognized by my pc. When I opened cmd and type "fastboot device", it says <waiting for device> and nothing happened.I have already installed HTC Sync Manager and the driver, but the problem is still there. Can anyone please help me? I'm a total noob and don't know what to do now. I just want to wipe everything clean and return it to stock.
Any help would be greatly appreciated. Thanks!
dxbach12 said:
Hello guys,
So I have an unlocked, unroot AT&T HTC One X, running stock rom JB 4.1.2 & Sense 4. The other day I was just using it when all of a sudden the phone froze & stop responding. I pressed and held the power button, trying to reset it. Ever since then, it had been stuck in a boot loop ("HTC -quietly brilliant" appeared, then reboot). I did not have any recovery like TWRP installed or anything similar. When I tried to enter HBoot, this is what I get"
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012,18:37:14:-1
and a bunch of options as usual. I tried everything from factory reset, clear storage, to recovery, but nothing works. I tried fastboot then install the RUU, but when I plug the phone in the USB port, it is not recognized by my pc. When I opened cmd and type "fastboot device", it says <waiting for device> and nothing happened.I have already installed HTC Sync Manager and the driver, but the problem is still there. Can anyone please help me? I'm a total noob and don't know what to do now. I just want to wipe everything clean and return it to stock.
Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Are you sure the device is unlocked? It says locked in your bootloader screen. Did you perform a factory reset from the bootloader? That causes the sd card to become corrupt on modified devices, so if you've done that you've created another problem for yourself. Whatever you do, absolutely do not run an RUU, you'll brick your phone. S-on + SuperCID + jb RUU = brick, that's assuming your phone is modified like you say, but it isn't worth the risk. What happens when you enter recovery? And did you have fastboot working previously or have you installed it since this happened?
Sent from my Evita
timmaaa said:
Are you sure the device is unlocked? It says locked in your bootloader screen. Did you perform a factory reset from the bootloader? That causes the sd card to become corrupt on modified devices, so if you've done that you've created another problem for yourself. Whatever you do, absolutely do not run an RUU, you'll brick your phone. S-on + SuperCID + jb RUU = brick, that's assuming your phone is modified like you say, but it isn't worth the risk. What happens when you enter recovery? And did you have fastboot working previously or have you installed it since this happened?
Sent from my Evita
Click to expand...
Click to collapse
My bad, I mean the device is sim-unlocked (I used it with t-mobile). I did try the factory reset from the bootloader, and it seems like I do have a corrupt sd card, just like you suggested. When I enter recovery, the phone reboot, and stuck in boot loop again. I also agree that install the RUU with s-on is a recipe for a bricked phone. I never had fastboot working before, I just tried it for the sake of installing the RUU.
Do you think that the phone's microusb port is broken?
Ok, so an RUU is possibly safe for you, if the phone has never been modified in the past. The only way to be sure of this is to check the CID but to do that you need a working fastboot connection. The command is this:
Code:
fastboot oem readcid
If it comes back as CWS__001 you're safe to run an RUU, but if it comes back as 11111111 (or anything else) it isn't safe.
When you connect the phone to your PC while the phone is in bootloader mode what does it say on the screen of the phone? It should either say fastboot usb or fastboot ac. If it says fastboot usb your usb port is fine, if it says fastboot ac there could be a problem with the data pins on the port.
Sent from my Evita
timmaaa said:
Ok, so an RUU is possibly safe for you, if the phone has never been modified in the past. The only way to be sure of this is to check the CID but to do that you need a working fastboot connection. The command is this:
Code:
fastboot oem readcid
If it comes back as CWS__001 you're safe to run an RUU, but if it comes back as 11111111 (or anything else) it isn't safe.
When you connect the phone to your PC while the phone is in bootloader mode what does it say on the screen of the phone? It should either say fastboot usb or fastboot ac. If it says fastboot usb your usb port is fine, if it says fastboot ac there could be a problem with the data pins on the port.
Sent from my Evita
Click to expand...
Click to collapse
Yeah, I tried to look up my CID too, but the pc doesnt recognize the phone. When I connect the phone to the pc and I enter the fastboot menu, there're 4 options: bootloader, reboot, reboot bootloader, and power down. It says fastboot usb when I move down to the 3 bottom options.
Still, when I typed in "fastboot oem readcid" in cmd, it stills says < waiting for device >. Could I be setting up the fastboot wrong?
dxbach12 said:
Yeah, I tried to look up my CID too, but the pc doesnt recognize the phone. When I connect the phone to the pc and I enter the fastboot menu, there're 4 options: bootloader, reboot, reboot bootloader, and power down. It says fastboot usb when I move down to the 3 bottom options.
Still, when I typed in "fastboot oem readcid" in cmd, it stills says < waiting for device >. Could I be setting up the fastboot wrong?
Click to expand...
Click to collapse
You can try "fastboot devices" to see if its connecting, beyond that you can check device manager to check if your PC can actually see the device, but perhaps hasn't installed it properly.
For fastboot to work properly you need fastboot installed (obviously), you need the proper drivers installed, you need to be using a usb 2.0 port, and you need to be using the original HTC cable (or one that's known to have good data transmission properties). Do you meet all those requirements? If you have drivers installed how did you install them? The fact that fastboot usb shows up on your screen suggests that the port on your phone is ok. What os are you running on your PC?
Sent from my Evita
timmaaa said:
For fastboot to work properly you need fastboot installed (obviously), you need the proper drivers installed, you need to be using a usb 2.0 port, and you need to be using the original HTC cable (or one that's known to have good data transmission properties). Do you meet all those requirements? If you have drivers installed how did you install them? The fact that fastboot usb shows up on your screen suggests that the port on your phone is ok. What os are you running on your PC?
Sent from my Evita
Click to expand...
Click to collapse
This may be where the problem lies. I don't have an OEM HTC data cable. I've been using a 3rd party one, and before the boot loop problem, the cable works fine. I tried both USB 2.0 port and 3.0 port, but neither works. The pc runs Windows 8.1. I install the driver using "HTC Driver Installer.msi" from another thread on XDA. Still, in device manager, the phone is shown as "Unknown USB Device (Device Failed Enumeration)". I tried to update the driver using local files with no luck.
Ok, your problem is Windows 8.1, there are no compatible fastboot drivers. You need to downgrade to Windows 8 or lower and you should be fine.
Sent from my Evita
timmaaa said:
Ok, your problem is Windows 8.1, there are no compatible fastboot drivers. You need to downgrade to Windows 8 or lower and you should be fine.
Sent from my Evita
Click to expand...
Click to collapse
Sorry for the delayed response, I have been away on business.
So I tries the fastboot on my wife's win 7 pc and it works, finally. When I ran fastboot oem readcid, it returns CWS_001. It looks like I can install the RUU after all.
What guide would you recommend me following? I tried to google one but there're just too many.
Thanks in advance!
All you need to do is connect your phone in fastboot mode and run the RUU exe in Windows. Make sure HTC Sync Manager is uninstalled, make sure no other programs are running, and make sure screen saver/hibernation is turned off. All you need to do is follow the prompts.
Sent from my Evita
timmaaa said:
All you need to do is connect your phone in fastboot mode and run the RUU exe in Windows. Make sure HTC Sync Manager is uninstalled, make sure no other programs are running, and make sure screen saver/hibernation is turned off. All you need to do is follow the prompts.
Sent from my Evita
Click to expand...
Click to collapse
I put the phone in fastboot, ran the RUU, and after a few prompts, clicked "Update", I reached the screen where it says "Waiting for bootloaders" with a status bar. Then after a while (seems like the bootloader fails?), Error [171]: USB Connection Error screen pops up. I gues this is because I can't boot the phone up and select USB debugging as the connection mode. What can I do now? Is it possible to fix the bootloader or put the phone is USB debugging mode?
Thanks!
dxbach12 said:
I put the phone in fastboot, ran the RUU, and after a few prompts, clicked "Update", I reached the screen where it says "Waiting for bootloaders" with a status bar. Then after a while (seems like the bootloader fails?), Error [171]: USB Connection Error screen pops up. I gues this is because I can't boot the phone up and select USB debugging as the connection mode. What can I do now? Is it possible to fix the bootloader or put the phone is USB debugging mode?
Thanks!
Click to expand...
Click to collapse
It has nothing to do with the usb debugging option, I've run RUUs with no OS on my phone before, they do not require that. The problem is your usb connection, this can be sure to multiple things. Are you using a usb 2.0 port? Are you using an original HTC cable or a cable that's known to work with adb/fastboot? You're not still using the PC with Windows 8.1 on it are you?
Sent from my Evita
timmaaa said:
It has nothing to do with the usb debugging option, I've run RUUs with no OS on my phone before, they do not require that. The problem is your usb connection, this can be sure to multiple things. Are you using a usb 2.0 port? Are you using an original HTC cable or a cable that's known to work with adb/fastboot? You're not still using the PC with Windows 8.1 on it are you?
Sent from my Evita
Click to expand...
Click to collapse
Let me tried borrowing someone else's cable. I was using a LG G2 one, so that could be a usb 3.0 cable.
You didn't answer my question, what OS are you using on the PC now?
Sent from my Evita
timmaaa said:
You didn't answer my question, what OS are you using on the PC now?
Sent from my Evita
Click to expand...
Click to collapse
Sorry. It's Windows 7 Professional SP1.
Ok, check the cable and check the port too.
Sent from my Evita
timmaaa said:
Ok, check the cable and check the port too.
Sent from my Evita
Click to expand...
Click to collapse
Ok, so far I have tried connecting the phone to the usb 2.0 port of the win 7 sp1 laptop using:
- 3rd party usb 2.0 cable
- OEM LG G2 cable (probably usb 3.0)
- OEM Kindle usb 2.0 cable
None have works so far. Every time, error [171] pops up.
Could it be a problem with the battery? The RUU recommends charging the phone at least to 30%. When I plug a charger in the phone, the boot loop continues, so I don't think my phone is charging.
dxbach12 said:
Ok, so far I have tried connecting the phone to the usb 2.0 port of the win 7 sp1 laptop using:
- 3rd party usb 2.0 cable
- OEM LG G2 cable (probably usb 3.0)
- OEM Kindle usb 2.0 cable
None have works so far. Every time, error [171] pops up.
Could it be a problem with the battery? The RUU recommends charging the phone at least to 30%. When I plug a charger in the phone, the boot loop continues, so I don't think my phone is charging.
Click to expand...
Click to collapse
So the phone bootloops even when in the bootloader?
Sent from my Evita
timmaaa said:
So the phone bootloops even when in the bootloader?
Sent from my Evita
Click to expand...
Click to collapse
No, that doesnt happen. When it's not in HBOOT, that happens. I'm charging it while putting in HBOOT right now.
Related
I relocked my bootloader and tried running a RUU but it keeps telling me that my phone is not connected. I'm using parallels for mac, I installed the drivers and I notice that when i connect the phone it doesn't say "fastboot usb" but when i push volume down is changes yet it still is unable to detect the phone. I installed the htc drivers but when I connect the phone is shows i dont have the drivers for " HTC Remote NDIS based device"
Could this be because im using parallels instead of a full windows pc?
please help, this is my very first android device and im scared I already ruined it
Yeah parallels is touchy. It works in VMware. Make sure in vm settings the usb device for the phone is set to always available to windows. If it is set to ask then it can lose connection.
Ok, Ill give a try.
I still have another problem. When I try to install the htc drivers, I get an error saying device not found. How am I able to install the drivers now?
I found the best way to get the driver installed is to install HTC sync
Thanks for the replies gunnyman, I have one last problem and hopefully theres a fix. I have a low battery and unable to flash the RUU. Is there a fix?
Is there battery actually low? Just shut down the phone and charge it up.
When I plug in the phone, it boot up on its own into fastboot and it says "fastboot ac". Is it charging?
Jaykelso said:
When I plug in the phone, it boot up on its own into fastboot and it says "fastboot ac". Is it charging?
Click to expand...
Click to collapse
Sorry. No idea. Sounds like it.
Hello xda,
a friend of mine just gave me his HTC Sensation because it isnt running quite a while. The problem is that i haven't had a HTC device ever and I don't really know what to do and what information you need to help me so I'd be happy if u just tell me what information you need and I will try to get them for you.
The Information I got so far is:
- if I want to boot it, it stays at the HTC Logo
- CWM starts with some errors but you can't perform a wipe (just turns off)
- Bootloader starts as well but you can't perform wipe either, nor flash new CWM
- If i connect it with the computer while in fastboot it changes to "fastboot usb" but adb cannot find the device, though i installed first the drivers, lateron htc sync. Windows just calls it "myhtc"
bootloader says:
"PYRAMID PVT SHIP S-OFF RL
HBOOT . 1.27.1100
RADIO - 11.22.3594.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34"
So what should I try to do or what information will you need.
I would be very happy if u can help me
fnstGoliath said:
Hello xda,
a friend of mine just gave me his HTC Sensation because it isnt running quite a while. The problem is that i haven't had a HTC device ever and I don't really know what to do and what information you need to help me so I'd be happy if u just tell me what information you need and I will try to get them for you.
The Information I got so far is:
- if I want to boot it, it stays at the HTC Logo
- CWM starts with some errors but you can't perform a wipe (just turns off)
- Bootloader starts as well but you can't perform wipe either, nor flash new CWM
- If i connect it with the computer while in fastboot it changes to "fastboot usb" but adb cannot find the device, though i installed first the drivers, lateron htc sync. Windows just calls it "myhtc"
bootloader says:
"PYRAMID PVT SHIP S-OFF RL
HBOOT . 1.27.1100
RADIO - 11.22.3594.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34"
So what should I try to do or what information will you need.
I would be very happy if u can help me
Click to expand...
Click to collapse
Hi,
Go HERE
Install 4 EXT recovery,using one of the 3 methods available.(probably third)
Then,try to install ARHD ROM.(same guide)
No need to change the firmware.
So I just tried to flash 4 EXT Recovery but it doesn't work..
It finds the zip, ask me whether i want to start the update, i press vol up and "Update is in progres.." appears but nothing more, I'm waiting since 5 minutes and will probably have to power off the phone now.. the same happened when i tried to install cwm so theres something wrong with the bootloader?
What can I do now?
fnstGoliath said:
So I just tried to flash 4 EXT Recovery but it doesn't work..
It finds the zip, ask me whether i want to start the update, i press vol up and "Update is in progres.." appears but nothing more, I'm waiting since 5 minutes and will probably have to power off the phone now.. the same happened when i tried to install cwm so theres something wrong with the bootloader?
What can I do now?
Click to expand...
Click to collapse
Hi,
Maybe you should run a RUU.
Look HERE
I also thought about this but as I said adb doesn't find the device.
Since I never ran a RUU, can I still flash or do I have to get adb to run with the device.
Anyway, I cannot read out the CID of the device so if it is possible, which RUU should I flash?
Thanks for your help
fnstGoliath said:
I also thought about this but as I said adb doesn't find the device.
Since I never ran a RUU, can I still flash or do I have to get adb to run with the device.
Anyway, I cannot read out the CID of the device so if it is possible, which RUU should I flash?
Thanks for your help
Click to expand...
Click to collapse
Hi,
Try installing these windows 7 & 8 drivers (assuming you have a windows 7 or 8 machine)
Reboot your PC and see if your phone is recognized in ADB.
You are s-off,so you do not have to match it 100%
Just get a RUU that is close to your region or carrier.
If you get the wrong one,it is not a problem.
It will just give you an error.
Then,just try another.
)
Well I just installed those drivers but same result as before..
Windows says "MyHTC" and after i write "adb devices" into the cmd window it says "daemon not running. starting it on port 5037. daemon started succesfully. List of devices attached." and the next time i write adb devices it just says "List of devices attached".
Bootloader still says Fastboot USB.
So maybe there's something wrong with my adb?
Well can i flash RUU without adb finding my device or cant I?
fnstGoliath said:
Well I just installed those drivers but same result as before..
Windows says "MyHTC" and after i write "adb devices" into the cmd window it says "daemon not running. starting it on port 5037. daemon started succesfully. List of devices attached." and the next time i write adb devices it just says "List of devices attached".
Bootloader still says Fastboot USB.
So maybe there's something wrong with my adb?
Well can i flash RUU without adb finding my device or cant I?
Click to expand...
Click to collapse
Hi,
Not sure what is happening with your ADB.
Look HERE for help.
In order to run a RUU ,you need to put the bootloader into fastboot,and plug in the USB.
It should show what yours is showing.
So, it should work.
After "List of devices attached" there is no device shown, I didn't leave anything adb shows, so this is still right? Usually it always shows my device ^^
So my adb is probably not running right or it is about my phone
So my next step should be adb showing my device and therefore reinstall android sdk, java, stuff until it might show the phone
or just do something with the phone?
I still think that i cannot run a ruu without any device shown? Didnt really get an answer on this question I guess or I didnt realize it
fnstGoliath said:
After "List of devices attached" there is no device shown, I didn't leave anything adb shows, so this is still right? Usually it always shows my device ^^
So my adb is probably not running right or it is about my phone
So my next step should be adb showing my device and therefore reinstall android sdk, java, stuff until it might show the phone
or just do something with the phone?
I still think that i cannot run a ruu without any device shown? Didnt really get an answer on this question I guess or I didnt realize it
Click to expand...
Click to collapse
Hi,
Just run the RUU.
It will only show error if it does not work.
No big deal,and no damage done.
Just try another one.
if you enable usb debugging might help too
Well.. I just started "RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed" and everything went fine until installation, no errors at all. Now the installer is stuck at "restarting bootloader" (or something equal, the installation is german) and the phone didnt do anything at all. It's now 15 minutes since the installation started so I probably will try another one but isn't it weird that ther is no error at all?
What should I do if the next RUU does exactly the same?
*edit:
just seeing page 2. How should I enable usb debugging without booting the phone?
*edit2:
second RUU: Same thing, no error but it didnt go further then "Restarting bootloader".
What to do now?
Any further Ideas what I could try?
Puuuush
fnstGoliath said:
Any further Ideas what I could try?
Puuuush
Click to expand...
Click to collapse
Put phone into bootloader then connect to pc and run the RUU
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
The phone was in fastboot usb while running the ruu for sure ..
fnstGoliath said:
The phone was in fastboot usb while running the ruu for sure ..
Click to expand...
Click to collapse
Hi,
Try running a RUU with the same radio (11.22) that you have installed.
You will not damage the phone.
It is not always an exact science with RUU.
Sometimes it is just trial and error.
So it is often that there is no error at all?
I just thought flashing wrong RUU will cause an error and not stopping at restarting bootloader. And anyway the bootloader seems pretty broken since it is not flashing anything at all ^^
Still i gonna try it
fnstGoliath said:
So it is often that there is no error at all?
I just thought flashing wrong RUU will cause an error and not stopping at restarting bootloader. And anyway the bootloader seems pretty broken since it is not flashing anything at all ^^
Still i gonna try it
Click to expand...
Click to collapse
Hi,
Probably ,the only thing that will fix your problem is a RUU.
So,keep trying different ones until it works.
I finally managed to find the phone via adb! I think that's a great step.
The biggest problem is that I lose any contact to the phone when i reboot it into bootloader.
I can just boot the phone into recovery and use any other adb function but as soon as I boot it into bootloader I can't do anything anymore.
That's why I cannot use any fastboot commands to flash a zip, neither run a RUU completely i guess.
So I think that i need any rom to either flash via recovery or just via PC not using fastboot/bootloader at all.
Are there any possibilities for me now?
fnstGoliath said:
I finally managed to find the phone via adb! I think that's a great step.
The biggest problem is that I lose any contact to the phone when i reboot it into bootloader.
I can just boot the phone into recovery and use any other adb function but as soon as I boot it into bootloader I can't do anything anymore.
That's why I cannot use any fastboot commands to flash a zip, neither run a RUU completely i guess.
So I think that i need any rom to either flash via recovery or just via PC not using fastboot/bootloader at all.
Are there any possibilities for me now?
Click to expand...
Click to collapse
Hi,
Plug your phone into the PC.
Go to device manager,and where it says MyHTC,right click and update driver.
Browse to the windows 7 & 8 drivers I gave you earlier.
Update,unplug phone ,and reboot PC.
Get a RUU that shows 3.32 or 3.33 in the title,and matches your region
Pull your battery.
Put it back in,and hold volume down and power button together.
Scroll to fastboot.
Plug in usb and run RUU from the PC
Hi,
I have two HTC One S, one connects to the PC and I have been able to install CM10.1, all is good, other than it doesn't charge the battery no-matter what. The other one, while connected to any USB power, charges the battery but it doesn't allow to get in communication with the same computer that the other one talks with.
1) The two One S are both S4 -
2) The drivers on the PC are OK otherwise they both wouldn't connect, same with fastboot and adb, if it works for one it must (?) work for the other.
3) Swapped cables, no luck, swapped USB port, no luck, various PC and phone reboots...
4) The ONE S that charges but doesn't communicate with the PC is still Locked and has the latest OTA from T-Mobile. I can't unlock the bootloader because, while it can go to HBOTT/Fastboot, it doesn't switch to "fastboot usb" when connected.
5) The ONE S that charges, even if I enable debugging option, it still doesn't show in ADB Devices....
Do you think it is an hardware issue? If it were, how would I go to investigate/fix? (Can it be fixed?)
Is it possible to unlock the bootloader without the USB connection using the stock T-Mobile software?
Anyone?
Thank You
Hardware or Software issue?
Well, no-one has responded to this one. So I thought I might just as well update the status of the issue which is still an issue. How would I be able to understand if the issue is software or hardware? - If the fastboot driver is installed properly, as it works with another phone (exactly the same model, same cable, same port) why doesn't it switch from "fastboot" to "fastboot usb"? How do I tell if there is an issue with the software on the phone or an hardware problem again , on the phone? -
Why, if I enable ADB on the phone then it doesn't show the ADB sign? See, this is a big issue as I can't unlock the bootloader and SIM without access to fastboot (or am I wrong?).
Anyway here are some details about the specific phone:
Model: HTC One S (Ville)
Android Version: 4.0.4
HTC Sense Version: 4.1
Software Number: 2.35.531.12 710RD
HTC SDK API Leve: 4.23
HTC Extension version: HTCExtension_403_1_GA_20
Kernel Version: 3.0.8-01602-gc3009b9
[email protected]#1
SMP Preempt
Baseband Version: 1.13.50.05.25_10.29.50.08L
Browser Version: WebKit/534.30
Info from HBOOT:
LOCKED
VLE PVT SHIP S-ON RL
HBOTT-1.14.0005
RADIO-1.13.50.05.25
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012, 12:17:41
evoarcher said:
Hi,
I have two HTC One S, one connects to the PC and I have been able to install CM10.1, all is good, other than it doesn't charge the battery no-matter what. The other one, while connected to any USB power, charges the battery but it doesn't allow to get in communication with the same computer that the other one talks with.
1) The two One S are both S4 -
2) The drivers on the PC are OK otherwise they both wouldn't connect, same with fastboot and adb, if it works for one it must (?) work for the other.
3) Swapped cables, no luck, swapped USB port, no luck, various PC and phone reboots...
4) The ONE S that charges but doesn't communicate with the PC is still Locked and has the latest OTA from T-Mobile. I can't unlock the bootloader because, while it can go to HBOTT/Fastboot, it doesn't switch to "fastboot usb" when connected.
5) The ONE S that charges, even if I enable debugging option, it still doesn't show in ADB Devices....
Do you think it is an hardware issue? If it were, how would I go to investigate/fix? (Can it be fixed?)
Is it possible to unlock the bootloader without the USB connection using the stock T-Mobile software?
Anyone?
Thank You
Click to expand...
Click to collapse
I have the same problem. The update stated security enhancements, so I'm wondering if they did something to prevent it from being rooted because I had no issue doing it with previous releases.
Don't know which one are you referring to. The problem that it doesn't charge or that it doesn't connect to via usb? - For me the one that doesn't charge is rooted and Cyanogen Mod 10.1 is installed. The other one, the one that doesn't communicate but charges via usb has the stock "from recovery" of T-Mobile. With this one I have tried a hard reset and loaded from recovery. I wish there was a way to put an T-Mobile update.zip on it and re-flash it from recovery.
evoarcher said:
Don't know which one are you referring to. The problem that it doesn't charge or that it doesn't connect to via usb? - For me the one that doesn't charge is rooted and Cyanogen Mod 10.1 is installed. The other one, the one that doesn't communicate but charges via usb has the stock "from recovery" of T-Mobile. With this one I have tried a hard reset and loaded from recovery. I wish there was a way to put an T-Mobile update.zip on it and re-flash it from recovery.
Click to expand...
Click to collapse
My problem was it wouldn't unlock the bootloader. It would only charge. I could sync with htc sync so I know my cable was good and the driver installed properly. After several hours of using the all in one tool, and other programs I've found online, I went ahead and went through the process on htc site to unlock the boot loader again. Boot the phone to bootloader, Press the power button to select it. You should hear some noises on the pc indicating it's recognizing the phone. Now on the pc run the following command through adb. I don't remember doing this the first time I unlocked it, so not sure if this is new or not. Make sure your Unlock_code.bin file is in the same folder as adb
Code:
fastboot flash unlocktoken Unlock_code.bin
Your phone will now have an unlocked bootloader. You may have to reboot the device before you can flash the recovery.
After that is done flash a recovery through adb, I did the htc1s touch from cwm.
Code:
fastboot flash recovery recoveryfilename.img
Now reboot your phone normally, You will need the file SuperSU.zip, get the cwm installable one. I can't post links since I don't have enough posts yet, but simple google search will give you the download for it.
Now mount the htc 1s as a disk drive then copy the SuperSU.zip to the /sdcard, which will be the drive you have in windows, I think it's just over 9gb. So you should have some folders in there, just put it in with the folders. Now reboot the phone through adb to the recovery, and choose to flash zip file from sdcard, then locate the SuperSU.zip and select it. Now reboot the phone, mine rebooted 2x before it booted into where I could use the phone. The phone is now rooted!
My phone doesn't sync. it doesn't switch to adb it's not detected by the PC. A different phone (same model) connects fine same port same PC same cable. In hboot it doesn't turn to USB when I connect the cable.
Sent from my One S using xda app-developers app
evoarcher said:
My phone doesn't sync. it doesn't switch to adb it's not detected by the PC. A different phone (same model) connects fine same port same PC same cable. In hboot it doesn't turn to USB when I connect the cable.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Does your phone show connected under device manager? Mine has two entries, one for htc device, and one for android adb device. Which driver did you use for the phone, the htc one or the one in the sdk? Also have you tried connecting this phone to another computer to see if the same problem exists of it not being recognized?
I would ultimately take the unrooted one back. If it still doesn't work, the issue is on your end.
This is an eBay phone, so realistically, I can't return it. I was wondering if, to rule out an hardware issue, as I can get to the recovery screen:
-> Android system recovery <3e>
->Use volume key to highlight; click power key to select..
-> Reboot system now
-> Apply update from external storage
-> Wipe data/factory reset
->Wipe cache partition
->Apply update from cache
->Apply update from internal storage.
If I could download in the phone storage or connect an external usb drive, and use this menu to re-load a stock t-mobile update.zip file?
Would it be possible? Would it help?
Hello,
I was reading a thread on someone who had the exact same issue, but no solution was ever posted.
Here's the thread http://forum.xda-developers.com/showthread.php?t=1458066
Background - this is a friends HTC Inspire, no rooting or anything was attempted, factory untouched phone bought new from AT&T.
Turns on, eventually goes to a 2 green arrows in a circle around a phone and then to a red triangle with red exclamation point over a black phone. I can hold the volume up and power to reset or wipe cache, neither does anything. Comes back to the same screen. says:
E:Can't open /cache/recovery/command
-- Wiping data...
Formatting /data...
E:Can't open /data/cwpkg.zip
E:Can't open /data/cw.prop
E:Can't open /cache/cwpkg.zip
E:Can't open /cache/cw.prop
Formatting /cache...
Data wipe complete
Doing a boot holding volume down and power shows this info:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011,00:55:45
HBOOT
I tried formatting the sd card and using recovery and stock rom to load, nothing worked, as if not recognized. The sd card had data on it(which was accessible), which I transfered to the computer before formatting.
Any ideas? I have never used an android device but I've been reading through this forum and others for hours now... phone is outside of warranty now too, so that's no longer an option. Thanks in advance.
Devin
It failed during the update to the current rom version or was reset/lost power during update. Use a pc to download the most recent ruu update for the inspire from HTC. Then download and install htc sync on pc. Place phone into fastboot mode with sd card inserted and then plug into pc. Run ruu from pc. Data will be lost but phone will be usable.
Gizmoe said:
It failed during the update to the current rom version or was reset/lost power during update. Use a pc to download the most recent ruu update for the inspire from HTC. Then download and install htc sync on pc. Place phone into fastboot mode with sd card inserted and then plug into pc. Run ruu from pc. Data will be lost but phone will be usable.
Click to expand...
Click to collapse
Dude you rock! That did it, thanks so much!
Devin
HTC Inspire needs RUU
Gizmoe said:
It failed during the update to the current rom version or was reset/lost power during update. Use a pc to download the most recent ruu update for the inspire from HTC. Then download and install htc sync on pc. Place phone into fastboot mode with sd card inserted and then plug into pc. Run ruu from pc. Data will be lost but phone will be usable.
Click to expand...
Click to collapse
So Gizmoe, I am in the same boat as original poster. I downloaded the correct ruu from HTC , but PC won't recognize phone. Point of clarification
When you say "place phone into fast boot mode" does that mean just connect to PC at that point or do I shut phone down and then connect. I've been going bonkers since ATT pushed software update and bricked the phone.
Thanks for any advice.
Terry
ILCUL8R said:
So Gizmoe, I am in the same boat as original poster. I downloaded the correct ruu from HTC , but PC won't recognize phone. Point of clarification
When you say "place phone into fast boot mode" does that mean just connect to PC at that point or do I shut phone down and then connect. I've been going bonkers since ATT pushed software update and bricked the phone.
Thanks for any advice.
Terry
Click to expand...
Click to collapse
It means with phone powered off hold down volume up and press power. Continue to hold volume until you see the hboot screen. Then select fastboot ( vol + - to make choice power to select). Then plug into pc. You should see the words fastboot usb on phone.
Gizmoe said:
It means with phone powered off hold down volume up and press power. Continue to hold volume until you see the hboot screen. Then select fastboot ( vol + - to make choice power to select). Then plug into pc. You should see the words fastboot usb on phone.
Click to expand...
Click to collapse
Ok, we'll I got it into fast boot USB mode, plugged in USB to PC, ran exe ruu file (which takes forever btw) and then got connection error. Ruu application then exits. Must be something hosed up in the phone with drivers. Bummer
I just checked Windows devices and it is showing as a "Device failed enumeration" error. Trying to troubleshoot that but have my doubts right now. I did notice that when I connected it earlier today PC saw it as G drive for a split second and then it dropped.
ILCUL8R said:
Ok, we'll I got it into fast boot USB mode, plugged in USB to PC, ran exe ruu file (which takes forever btw) and then got connection error. Ruu application then exits. Must be something hosed up in the phone with drivers. Bummer
I just checked Windows devices and it is showing as a "Device failed enumeration" error. Trying to troubleshoot that but have my doubts right now. I did notice that when I connected it earlier today PC saw it as G drive for a split second and then it dropped.
Click to expand...
Click to collapse
Do you have HTC sync installed and running?
Hi Gizmoe. Well I have HTC Sync but I didn't think I needed to have that running. I just ran the ruu exe file, but got connection error. I just tried HTC Sync with phone in fastboot usb mode but HTC Sync can't see it. Version of HTC Sync is 3.3.63. The other thing I noticed is that if phone is off and plugged into PC it is recognized as a removable device with a G: drive letter in device manager, but doesn't show up in file explorer and running exe or HTC Sync still can't see it.
If it's connected when it's in fastboot usb mode then windows says "last device connected malfunctioned " and PC doesn't see it.
I'm in this catch 22. Tried to do recovery process to install a ruu off sdcard which errors out, and can't install ruu from pc since phone usb connection not recognized.
ILCUL8R said:
Hi Gizmoe. Well I have HTC Sync but I didn't think I needed to have that running. I just ran the ruu exe file, but got connection error. I just tried HTC Sync with phone in fastboot usb mode but HTC Sync can't see it. Version of HTC Sync is 3.3.63. The other thing I noticed is that if phone is off and plugged into PC it is recognized as a removable device with a G: drive letter in device manager, but doesn't show up in file explorer and running exe or HTC Sync still can't see it.
If it's connected when it's in fastboot usb mode then windows says "last device connected malfunctioned " and PC doesn't see it.
I'm in this catch 22. Tried to do recovery process to install a ruu off sdcard which errors out, and can't install ruu from pc since phone usb connection not recognized.
Click to expand...
Click to collapse
UPDATE: I decided to just try the recovery method again while the phone was plugged into USB cable just to charge it. Well it downloaded the latest HTC version of the ROM and it installed....YEAH, BUT phone thinks it's a Desire , not an Inspire and the IMEI MMEI etc. info is missing. No connectivity to mobile network. And I don't have keyboard function either. Sooo, I think I will try another ruu and see if that works starting from scratch. I guess I'm still missing some files or steps in this process. I used to be in the PC business and thought they could be convoluted, but cellphones take the cake.
ILCUL8R said:
UPDATE: I decided to just try the recovery method again while the phone was plugged into USB cable just to charge it. Well it downloaded the latest HTC version of the ROM and it installed....YEAH, BUT phone thinks it's a Desire , not an Inspire and the IMEI MMEI etc. info is missing. No connectivity to mobile network. And I don't have keyboard function either. Sooo, I think I will try another ruu and see if that works starting from scratch. I guess I'm still missing some files or steps in this process. I used to be in the PC business and thought they could be convoluted, but cellphones take the cake.
Click to expand...
Click to collapse
Yes they do. Just an fyi the desire and inspire are exactly the same device and HTC left the inspire name out of the build prop. It will say it's a desire HD, so that's normal. The rest isn't though. Yeah I would try the ruu again. Just make sure HTC sync is installed and running. You can run it from the phones os too.
Gizmoe said:
Yes they do. Just an fyi the desire and inspire are exactly the same device and HTC left the inspire name out of the build prop. It will say it's a desire HD, so that's normal. The rest isn't though. Yeah I would try the ruu again. Just make sure HTC sync is installed and running. You can run it from the phones os too.
Click to expand...
Click to collapse
Gizmoe, thought I'd give you the latest update: I was able to finally get the PC (Win8) to recognize the phone by installing HTC Sync 3.3.63, installing Win7 64bit drivers.
Then I downloaded RUU_Ace_Sense30_S_Cingular_US_3.20.502.63_Radio_12.69c.60.29U_26.09.13.17_M_release_335423_signed from HTC site. This is an exec file.
Got phone into USB debugging mode, fastboot off , charge only, and ran the above RUU. Seemed to be working as it asked if I wanted to update etc. and warned about losing data. Said ok and RUU exec then popped up status window saying "Waiting for bootloader......................"
This ran for a few minutes and then Windows popped up message saying last USB device connected failed. Then RUU exec finally popped up and said Connection Error 171. No choice but to exit program. This has happened twice. Very annoying. Took forever to get PC to recognize phone and now I'm still stuck with a brick thanks to ATT.
Any thoughts ?
ILCUL8R said:
Gizmoe, thought I'd give you the latest update: I was able to finally get the PC (Win8) to recognize the phone by installing HTC Sync 3.3.63, installing Win7 64bit drivers.
Then I downloaded RUU_Ace_Sense30_S_Cingular_US_3.20.502.63_Radio_12.69c.60.29U_26.09.13.17_M_release_335423_signed from HTC site. This is an exec file.
Got phone into USB debugging mode, fastboot off , charge only, and ran the above RUU. Seemed to be working as it asked if I wanted to update etc. and warned about losing data. Said ok and RUU exec then popped up status window saying "Waiting for bootloader......................"
This ran for a few minutes and then Windows popped up message saying last USB device connected failed. Then RUU exec finally popped up and said Connection Error 171. No choice but to exit program. This has happened twice. Very annoying. Took forever to get PC to recognize phone and now I'm still stuck with a brick thanks to ATT.
Any thoughts ?
Click to expand...
Click to collapse
Ahh yes windows 8 is a ***** with android devices and fastboot drivers. I would recommend trying it on a machine with windows 7. Also are you s off. If so you can try PD98IMG.
Gizmoe said:
Ahh yes windows 8 is a ***** with android devices and fastboot drivers. I would recommend trying it on a machine with windows 7. Also are you s off. If so you can try PD98IMG.
Click to expand...
Click to collapse
Yes, apparently there are a lot of issues with Win8 and android. I can try it on a machine with 7 or even XP. Unfortunately I'm S-ON so no go on PD98IMG. I'll let you know what happens when I try it on the other Windows machines.
Thanks
ILCUL8R said:
Yes, apparently there are a lot of issues with Win8 and android. I can try it on a machine with 7 or even XP. Unfortunately I'm S-ON so no go on PD98IMG. I'll let you know what happens when I try it on the other Windows machines.
Thanks
Click to expand...
Click to collapse
UPDATE:
SUCCESS !! :good: Well it only took a boatload of patience and a 7 yr. old laptop running XP to get the phone re-imaged. Process was sloooow (about 30 minutes) but all drivers loaded and the stock ROM from HTC installed fine. Phone is now back to operational. Turns out I didn't lose contacts since they were apparently backed up in Google account. (YEAH) Now I just have to manually install 4 more small security patches from HTC. Their website isn't too clear as to how to do this but I'll muddle thru it.
Thanks Gizmoe for your help and suggestions. You are right I would definitely recommend that anyone trying to root, recover or re-image from scratch an Android from a PC to avoid Win8 at this time and stick with Win7 or XP.
Help me please!
ILCUL8R said:
Yes, apparently there are a lot of issues with Win8 and android. I can try it on a machine with 7 or even XP. Unfortunately I'm S-ON so no go on PD98IMG. I'll let you know what happens when I try it on the other Windows machines.
Thanks
Click to expand...
Click to collapse
Please help me, i'm having the same problem and i'm trying to apply this solution but i can't understand what do you mean with "go on PD98IMG" please please tell me what does that means and how to do it please!
---------- Post added at 07:26 AM ---------- Previous post was at 07:21 AM ----------
Gizmoe said:
Ahh yes windows 8 is a ***** with android devices and fastboot drivers. I would recommend trying it on a machine with windows 7. Also are you s off. If so you can try PD98IMG.
Click to expand...
Click to collapse
Gizmoe, please can you tell me what do you mean with "try PD98IMG" i guess that it's a way to get the inspire 4g/DHD s-off but i can't find how to apply it. please help me
rokr_64 said:
Please help me, i'm having the same problem and i'm trying to apply this solution but i can't understand what do you mean with "go on PD98IMG" please please tell me what does that means and how to do it please!
---------- Post added at 07:26 AM ---------- Previous post was at 07:21 AM ----------
Gizmoe, please can you tell me what do you mean with "try PD98IMG" i guess that it's a way to get the inspire 4g/DHD s-off but i can't find how to apply it. please help me
Click to expand...
Click to collapse
A PD98IMG is a way to install various things but requires an s off device. It is not a method to acheive s off. What exactly is the problem you are having? Are you not able to boot your device? If you are still stock, run the current RUU from HTC through fastboot as explained in previous posts in this thread.
HTC bootloader problem
Gizmoe, I am joining this group, I have the same problem, followed all steps. my problem is that RUU during the process sends msg to phone to reboot and start Bootloader my phone reboots and stays with white screen / green HTC logo (freezes?) RUU after waiting for Bootloader returns error 171 connection problem. My guess is that bootloader is not starting and RUU times out and thinks that it is connection problem.
Uninstalled sync and reinstalled latest version, deleted and re downloaded latest RUU. System recognizes phone ( device manager shows HTC). Any suggestions? Thanks.
raydilba said:
Gizmoe, I am joining this group, I have the same problem, followed all steps. my problem is that RUU during the process sends msg to phone to reboot and start Bootloader my phone reboots and stays with white screen / green HTC logo (freezes?) RUU after waiting for Bootloader returns error 171 connection problem. My guess is that bootloader is not starting and RUU times out and thinks that it is connection problem.
Uninstalled sync and reinstalled latest version, deleted and re downloaded latest RUU. System recognizes phone ( device manager shows HTC). Any suggestions? Thanks.
Click to expand...
Click to collapse
What Windows version are you on?
Gizmoe said:
What Windows version are you on?
Click to expand...
Click to collapse
Windows 7 Pro.
raydilba said:
Windows 7 Pro.
Click to expand...
Click to collapse
Yeah there seems to be a communication issue. Try putting phone into fastboot. Make sure phone reads fastboot usb. Then run RUU. There may be programs in pc as well blocking it. See if you can send fadtboot commands if the aforementioned method doesn't work. If that's how you already tried running it then run it from booted phone.
Hi guys
Desire S.
Unrooted, no custom recovery, basically everything default.
HBoot 2.00.0002
.
To root, i need the 0.98 version.
Using HTCdev.com, i tried to unlock, but at step 5, where i should type fastboot oem get_identifier_token, the phone doesnt come up at all, and cmd just continues to wait for device.
Before you ask, I HAVE (i hope) followed all steps.
This includes updating drivers manually, using htc sync (latest and older versions), swapping usb port and cable, reunzipping adb and fastboot material from other sources, and reading for a decent number of hours throughout xda and other external forums and guides.
But there is still no success.
Anyone help please? I don't just want fast, "get it working for me" type answers, but actually want to know why it refuses to greet me!
Cheers
BTW, i'm on a windows 8.1 laptop, and have updated the relevant drivers, still to no avail.
InV15iblefrog said:
Hi guys
Desire S.
Unrooted, no custom recovery, basically everything default.
HBoot 2.00.0002
.
To root, i need the 0.98 version.
Using HTCdev.com, i tried to unlock, but at step 5, where i should type fastboot oem get_identifier_token, the phone doesnt come up at all, and cmd just continues to wait for device.
Before you ask, I HAVE (i hope) followed all steps.
This includes updating drivers manually, using htc sync (latest and older versions), swapping usb port and cable, reunzipping adb and fastboot material from other sources, and reading for a decent number of hours throughout xda and other external forums and guides.
But there is still no success.
Anyone help please? I don't just want fast, "get it working for me" type answers, but actually want to know why it refuses to greet me!
Cheers
BTW, i'm on a windows 8.1 laptop, and have updated the relevant drivers, still to no avail.
Click to expand...
Click to collapse
your phone must be in FASTBOOT bootloader mode..not in the HOME of your ROM..
if you don't wan to turn off your phone first and pressing volume down + power to go to bootloader..then you can using a adb command on cmd while your phone is still in the HOME of your ROM.. type "adb reboot bootloader" then select "FASTBOOT" now you can type "fastboot oem get_identifier_token"
don't forget to disabled Fast boot mode and enable USB Debuging first from the system settings and just connect your phone to pc as charge mode..
hope this help..
Sorry mate. Tried that before your post though.
However the person for whom I was doing this no longer needs it doing, and plans for a newer device, so I no longer have this device available. Thus, i thanked you, since it was a cue for me to mention that.
Cheers.
This model of HTC is died