First off: I have an AT&T HTC one X
I am an almost total noob when it comes to this stuff so please bear with me here.
I had my roommate put cyanogenmod onto my phone when I got it and all was well until I moved to Asia and got an unlock code from AT&T to be able to use it over here. The unlock code wouldn't work and I found some stuff online saying that it might be a problem with cyanogenmod.
I followed a youtube instruction guide on how to get rid of the mod and everything was going fine until right at the end when I got a windows notification that the RUU had stopped working. I figured I would just do it again, but the actual program itself said it was successful. As I waited for it to reboot and load the roms, it started a loop. The loop is the white screen with the green htc letters for a few seconds and then it goes to a black screen with a phone logo in the middle. Around the phone logo is what looks like a recycling symbol except circular instead of triangular and on the screen portion of the phone logo there is an arrow facing down.
I assume this is just telling me I need to actually download some software on the phone, but it won't connect via USB and every time it starts up it says that the drivers were not successfully installed and htc sync manager doesn't recognize that a device is even connected. The loop continued and i tried to boot it back into the fastloader which did nothing. I held down the buttons as if to boot it into fastloader, but this time for about 15 seconds which took me to a battery charging screen and finally ended the loop.
I assume(hope) that since it's actually responding to input from the buttons that it's not irreversibly bricked. Is there any way I can get some version of android back on this thing? Any help would be much appreciated
Are you able to get the phone into the bootloader?
To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines. Also, exactly which RUU did you try to use?
Sent from my Evita
Happened to me as well..I reran ruu and then flashed a custom recovery. That symbol of charging with that arrow scared me. Lol
Yeah I was the friend that helped tpank unlock and put cyanogenmod on. I'm just too noob to help him halfway across the world get his phone back to stock
Swilli89 said:
Yeah I was the friend that helped tpank unlock and put cyanogenmod on. I'm just too noob to help him halfway across the world get his phone back to stock
Click to expand...
Click to collapse
This is why people should be learning to do things themselves. Now you've put him in a situation where he doesn't know what he's doing, very dangerous on a modified device with root access.
Sent from my Evita
the RUU i tried was the update from the htc site "HTC One X for AT&T Software Upgrade 1.29.2014"
the first five lines that appear on the phone are
*** RELOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.18.0000
RADIO-1.35A.32.45.27
OpenDSP-v33.1.0.45.1128
also my computer doesn't recognize my phone is even plugged in at this point
Before you attempt to run the RUU again it's very important that we find out what your current CID is, if it's still SuperCID and you run the RUU you could brick your phone. To do this you're gonna need to have a working connection between your phone and your PC, so you'll need to make sure you have drivers installed, and you'll also need to have adb/fastboot installed. Do you have any drivers currently installed? If so, how did you install them?
Sent from my Evita
i have the RUU that I showed you and I just installed another RUU on my computer: RUU_M7_UL_JB43_SENSE50_MR_CINGULAR_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed.2.exe but I haven't done anything with that yet. The only drivers I would have on my phone might be the ones from the original RUU I downloaded and ran which got me into this mess in the first palce, but I dont even know if they're on the phone since it's in its current state. I have adb and fastboot from downloading the android sdk slim pack. I also have HTC sync, but I'm not sure how that fits into the equation
tpankfashank said:
i have the RUU that I showed you and I just installed another RUU on my computer: RUU_M7_UL_JB43_SENSE50_MR_CINGULAR_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed.2.exe but I haven't done anything with that yet. The only drivers I would have on my phone might be the ones from the original RUU I downloaded and ran which got me into this mess in the first palce, but I dont even know if they're on the phone since it's in its current state. I have adb and fastboot from downloading the android sdk slim pack. I also have HTC sync, but I'm not sure how that fits into the equation
Click to expand...
Click to collapse
Whoa. Whoa, whoa, whoa. Where on earth did you get that RUU? It isn't even for this device. Delete it now.
Drivers don't go on your phone, they're on your PC. HTC Sync Manager fits into the equation because it's the best way to get the drivers installed on your PC.
Uninstall HTC Sync Manager and the drivers that should be in the same sub-menu in the start bar on your PC. Uninstall any other phone software you might have on your PC.
Install HTC Sync Manager again, put your phone in fastboot mode, connect your phone to your PC, drivers should begin to auto-install.
Navigate to where you have adb.exe and fastboot.exe on your PC (we'll call this your fastboot folder). Shift + right click anywhere within that folder, select open command prompt here, issue the following command:
Code:
fastboot oem readcid
Please post the result.
Before we go any further, I need to be brutally honest with you. Once you have successfully run the correct RUU, which will return the phone to a stock configuration, leave it stock. Judging from your couple of posts here you're on a collision course to bricking your phone. You just don't seen to posses the slightest idea of what you're doing, couple that with owning a modified device, and the results are almost always disastrous. I'm not saying this to be cruel, I'm saying this because I'd hate to see you brick your device. The only way it's safe to have a modified device is if you're willing to put in the hard work of researching (days/weeks/months/years), and continuing to research to stay on top of this ever changing game.
Sent from my Evita
ok i attempted all of this, but nothing happens because my computer won't even recognize that my phone is plugged in. So htc sync manager is telling me to connect a device and the command prompt just says <waiting for device> when I type in the command to figure out the CID.
Also, I take no offense from your warning. I wasn't going to try to mess with it any more after I got my the stock OS and my phone unlocked for asian networks. I really appreciate all the help
tpankfashank said:
ok i attempted all of this, but nothing happens because my computer won't even recognize that my phone is plugged in. So htc sync manager is telling me to connect a device and the command prompt just says when I type in the command to figure out the CID.
Also, I take no offense from your warning. I wasn't going to try to mess with it any more after I got my the stock OS and my phone unlocked for asian networks. I really appreciate all the help
Click to expand...
Click to collapse
There's no point in attempting any fastboot command until you can get the PC to recognise the device. Are you using a usb 2.0 port, and the original HTC usb cable? What does it say on the screen of your phone when you connect it while it's in the bootloader? It should say fastboot, fastboot usb, or fastboot ac.
Sent from my Evita
timmaaa said:
There's no point in attempting any fastboot command until you can get the PC to recognise the device. Are you using a usb 2.0 port, and the original HTC usb cable? What does it say on the screen of your phone when you connect it while it's in the bootloader? It should say fastboot, fastboot usb, or fastboot ac.
Sent from my Evita
Click to expand...
Click to collapse
Tpank, use the snipping tool on your computer to post a screen capture of your fastboot adb folder. its the folder that you are running the command prompt from (or should be).
BTW thanks Timaaaaa for helping my friend out. When I unlocked his phone we didn't know he would have the opportunity to move out of the US to Thailand so I figured I would be around to help with something like this. Thanks again.
Why would we need a screenshot of the fastboot folder?
Sent from my Evita
These guys are on a collision course. ?
timmaaa said:
There's no point in attempting any fastboot command until you can get the PC to recognise the device. Are you using a usb 2.0 port, and the original HTC usb cable? What does it say on the screen of your phone when you connect it while it's in the bootloader? It should say fastboot, fastboot usb, or fastboot ac.
Sent from my Evita
Click to expand...
Click to collapse
ok so it says "Fastboot usb". I am using the original htc usb cable. I'm not sure if it's a usd 2.0 port all I know is that it's an Intel 6 Series/C200 Series.
When I ran the command prompt it says:
<bootloader> cid: 11111111
OKAY [ 0.017s]
Ok, so you have a working fastboot connection now, right? The problem you face at the moment is that you can't run an RUU with your phone in the current configuration. S-on + SuperCID + jb RUU = brick. Your only real option at this stage is to do this:
-Unlock the bootloader at htcdev.
-Flash TWRP recovery.
-Flash a ROM to get the phone booting.
-Get s-off via Facepalm S-off.
-Run the correct at&t RUU to return the device to stock
-Change the CID back to the at&t CID.
-Relock the bootloader.
-Go back to s-on.
That probably seems like a lot of work but it's the only way for you to proceed. I have detailed instructions for several of those procedures in the How-To Guide For Beginners thread in my signature.
Sent from my Evita
So I can;t get past the first step because it's not recognizing my phone still. When I ran the first command in the command prompt, where it should have listed my phone it says "List of connected devices" and nothing underneath it.
How did you get the CID?
Sent from my Evita
I'm not sure why I can find the CID and not get it listed as an attached device. I tried to run the adb devices command a few times and then ran the fastboot oem readcid command in the same window and I could get the cid but still cant get it to recognize the device
Are you attempting adb commands while the device is in fastboot mode? They won't work, only fastboot commands will work there, adb commands work while the phone is booted into the OS. Use "fastboot devices" while in fastboot mode.
Sent from my Evita
Related
So I've tried to get S-On back for warranty purpose. I've used this tutorial:
S-ON
You may want to put your phone back to S-ON after following the rest of this guide, for example if you have reflashed your original rom and want to return it for warranty repair. Thanks to ikhzter thread, we have a way to do this!
1. Open Command Prompt, either Run "cmd" or go to Start, Accesories, Command Prompt
2. Enter the command: "cd C:\platform-tools" (Or whatever location you copied the folder to earlier)
3. Ensure your phone is switched on (regular home screen) and connect it by USB in charging mode (Ensure usb debugging is on settings > applications > development)
4. Enter the command "adb devices". It should come back with list of devices attached and then your serial number.
5. Enter the command "adb reboot bootloader". (You device will restart and boot into fastboot USB)
6. Enter the command "fastboot oem writesecureflag 3". (Thanks Dazweeja)
7. Reboot into bootloader using "fastboot reboot-bootloader" or remove & reinsert the battery and press power on while keeping hold of volume down.
8. Bootloader should now read Pyramid PVT Ship S-ON RL.
9. Remove and reinsert the battery. Press power on as normal
You should now have S-on back and you can return your device or do whatever it is covered again under warranty.
10. IF IT DOESN'T REBOOT and bootloader says ***Security Warning**
Remove and re-insert the battery and go back into bootloader and holding Volume Down +power button select fastboot
11. Run RUU_Pyramid_***.exe to reflash stock rom. (the one you downloaded earlier) and then reboot. It should work now
Now my phone is dead. When I connect it to my laptop I get a driver notification.
QHSUSB_DLOAD
Is there a way to fix this?
Thanks
Up HELP!? Someone??
I found the driver for QHSUSB_DLOAD. Now what?
Does it boot in bootloader ( Vol- + Power ) ?
No. It's dead. No led blinking.
Now it shows up in device manager unknown device when I connect it to my laptop.
Hi, stylus1828
I have similar prob.
My htc Sensation it's bricked. NO screen, NO lights, NO nothing
Qualcomm HS-USB QDLoader 9008
download mode waiting
how to start normal phone mode
please help me
I had the same problem once, I pulled the battery for a couple of hours.
After a few hours I placed it again and it just booted.
Don't know what to say but I think I'm screwed. I'm gonna send it to HTC, maybe they will not see what I've done and get a replacement. MAYBE!
A friend of mine had a full brick to because of bad rooting and got a new one without any probs. I hope you"ll be lucky aswell.
Let's hope so. Today I sent my phone back to warranty. Tomorrow I will get my answer.
stylus1828 said:
Let's hope so. Today I sent my phone back to warranty. Tomorrow I will get my answer.
Click to expand...
Click to collapse
Did you hear back from HTC? What did they say? I feel that unless you totally fried the phones internals they can probably tell that you rooted it when they try to diagnose the problem. What you are describing is the main reason I am so hesitant to root this phone. For your sake, I really hope they fix it for you! Let us know how this develops.
I sent my phone back to the online store from were I bought it. They seem to have an authorized gsm service and I'm waiting for a good answer from them.
I hope that I will get a new one without the dust issue. That was the reason I wanted to get S-ON back.
I just used those exact instructions to get back S-ON and my sensation appears to be bricked as well! someone should change those instructions! any way to fix this?
Instructions work fine if you actually follow them. I've done it. You skipped the most important part! You didn't flash stock ruu BEFORE doing anything else. Then you writesecure flag, then flash ruu again. It clearly states in the instructions to flash the ruu no matter what. Whether you're on stock already or not to make sure that nothing gets fouled up when s-on is set.
Behold_this said:
Instructions work fine if you actually follow them. I've done it. You skipped the most important part! You didn't flash stock ruu BEFORE doing anything else. Then you writesecure flag, then flash ruu again. It clearly states in the instructions to flash the ruu no matter what. Whether you're on stock already or not to make sure that nothing gets fouled up when s-on is set.
Click to expand...
Click to collapse
For what it is worth, I did flash back to stock rom before following these steps and I still got bricked.... has anyone actually followed these exact directions and not been bricked? I'm just thinking that for a stickied post with information in it that appears to have bricked several user's phones, it might need to be re-worded....
Even i used the exact same thing to get S-ON back and now my phone is bricked!!
Did htc replace or repair your handset?
I used the same instructions and it worked flawlessly, I also sent my phone because of the dust issue. I did follow it by the letter, maybe you forgot to boot the RUU when you installed it, or didn't have superCID?
Yes I have done the method without being bricked
I have a Htc Sensation running on the Tmobile network
i decided to go with a different rom and tried to install the rom from COREDROID SENSATION XE & 4G v5.1.
after installing it was stock on the boot screen.
I tried to SCID and install PG58DOAG.
at this point my phone will not boot.
I can get into the the recovery mode after i select "recovery" it goes to a screen with a red triangle and an exclamation mark.
I the volume up and power and the try to install a update...but non has worked
can get one help??
download this file http://www.filefactory.com/file/c19...00U_10.14.9035.01_M_release_223976_signed.exe
and run it with your phone plugged in your pc, it should do a stock recovery on your phone.
I faced the same issue with another ROM.
The only way I found to reboot was to reinstall the firmware while connected via USB with the PC.
And after that, I reinstalled the ROM.
I couldnt even boot.
primekrieger said:
I couldnt even boot.
Click to expand...
Click to collapse
Okay, first off stop digging up multiple 1 and 2 year old threads to post about your problem.
Second, be MUCH more specific about what the issue is. What happened before it stopped booting? Was it dropped or something or was it working fine?
Is it rooted?
Is it S-Off?
Skipjacks said:
Okay, first off stop digging up multiple 1 and 2 year old threads to post about your problem.
Second, be MUCH more specific about what the issue is. What happened before it stopped booting? Was it dropped or something or was it working fine?
Is it rooted?
Is it S-Off?
Click to expand...
Click to collapse
Sorry about that.
Here are the full details:
I have a Sensation XE, it was running ARHD 7.2, rooted, Bootloader Unlocked, S-OFF
I was playing subway surfers when all of a sudden the phone froze, no buttons nothing worked. After a while it itself restarted and got stuck on the white HTC boot screen. When it didnt progress for some minutes, I removed the battery, reinserted it and tried turning it on. But nothing, no signs of life were shown. Even on connecting the wall charger there was no charging LED.
Only thing is that windows can detect it as QHSUSB_DLOAD or something.
I checked out the Unbricking Sensation forum at: http://forum.xda-developers.com/show....php?t=1522351
but they say it works only for devices bricked while turning to S-ON, but as I mentioned mine is S-OFF. So, can I still use their method or is there some alternative?
Thanks
primekrieger said:
Sorry about that.
Here are the full details:
I have a Sensation XE, it was running ARHD 7.2, rooted, Bootloader Unlocked, S-OFF
I was playing subway surfers when all of a sudden the phone froze, no buttons nothing worked. After a while it itself restarted and got stuck on the white HTC boot screen. When it didnt progress for some minutes, I removed the battery, reinserted it and tried turning it on. But nothing, no signs of life were shown. Even on connecting the wall charger there was no charging LED.
Only thing is that windows can detect it as QHSUSB_DLOAD or something.
I checked out the Unbricking Sensation forum at: http://forum.xda-developers.com/show....php?t=1522351
but they say it works only for devices bricked while turning to S-ON, but as I mentioned mine is S-OFF. So, can I still use their method or is there some alternative?
Thanks
Click to expand...
Click to collapse
Can you get into recovery?
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
Can you get into recovery?
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
No, I can't get to recovery. The phone doesn't start up at all. But windows detects something like QHSUSB_DLOAD when connecting through usb.
primekrieger said:
No, I can't get to recovery. The phone doesn't start up at all. But windows detects something like QHSUSB_DLOAD when connecting through usb.
Click to expand...
Click to collapse
Is the battery charging when you connect it to USB like that? If so I'd say to try an ruu to return it to completely stock. You will lose all user data on the internal memory when doing this. And it will return the phone to s-on and stock ROM. You will have to start over.
Do a search for ruu and you should find the thread that walks you through the process. Its really easy. You basically just run an .exe file from windows and it does everything else.
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
Is the battery charging when you connect it to USB like that? If so I'd say to try an ruu to return it to completely stock. You will lose all user data on the internal memory when doing this. And it will return the phone to s-on and stock ROM. You will have to start over.
Do a search for ruu and you should find the thread that walks you through the process. Its really easy. You basically just run an .exe file from windows and it does everything else.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
No, the charging LED doesnt glow.
Phone is detected on USB connection after i remove the battery. And moreover windows doesnt detect it as a phone i think.
PS: Losing data, S-OFF, ROM is not a concern. I just want it working, bought it just 6 months ago :crying:
primekrieger said:
No, the charging LED doesnt glow.
Phone is detected on USB connection after i remove the battery. And moreover windows doesnt detect it as a phone i think.
PS: Losing data, S-OFF, ROM is not a concern. I just want it working, bought it just 6 months ago :crying:
Click to expand...
Click to collapse
Do you have access to another battery just to make sure your battery isn't fried? If there is physical damage to the battery it will neither charge nor will it power on.
Also, try doing the ruu thing anyway. Worst its going to do is not work.
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
Do you have access to another battery just to make sure your battery isn't fried? If there is physical damage to the battery it will neither charge nor will it power on.
Also, try doing the ruu thing anyway. Worst its going to do is not work.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
As you said I searched for RUU for my phone, but now the problem is I can't decide what RUU to download since the phone wont start and therefore I can't see software number or CID.
primekrieger said:
As you said I searched for RUU for my phone, but now the problem is I can't decide what RUU to download since the phone wont start and therefore I can't see software number or CID.
Click to expand...
Click to collapse
from bootloader connect the device in the pc via usb(it should say fastboot usb)
open a cmd in the folder where you have adb and fastboot files and do these commands
fastboot getvar version-main
fastboot getvar cid
rzr86 said:
from bootloader connect the device in the pc via usb(it should say fastboot usb)
open a cmd in the folder where you have adb and fastboot files and do these commands
fastboot getvar version-main
fastboot getvar cid
Click to expand...
Click to collapse
Hi there!
Even my device is facing similar sort of problems. Although the situation is not as bad as the op,but still the phone is still just a paperweight.
Now what I did- unlocked bootloader via HTC dev site( HBOOT Ver 1.27)
Decided to S-off by J.Bear method.
Everyhting went fine untill the phone restarted. Controlbear no longer recognised the device. It said check your drivers.
That was the time when everything messed up.
Now the phone would no longer boot ahead of the white HTC bootscreen. And sometimes it even powers on directly to recovery(even when i'm not pressing volume down).
And one more strange thing happening.."adb devices" command doesn't show any devices listed although i can check the firmware and cid version(via fastboot command). And the device is showing up in device manager(my HTC). But adb commands are not working.
Am i missing something?
Any help would be much appreciated.
walkermoon said:
Hi there!
Even my device is facing similar sort of problems. Although the situation is not as bad as the op,but still the phone is still just a paperweight.
Now what I did- unlocked bootloader via HTC dev site( HBOOT Ver 1.27)
Decided to S-off by J.Bear method.
Everyhting went fine untill the phone restarted. Controlbear no longer recognised the device. It said check your drivers.
That was the time when everything messed up.
Now the phone would no longer boot ahead of the white HTC bootscreen. And sometimes it even powers on directly to recovery(even when i'm not pressing volume down).
And one more strange thing happening.."adb devices" command doesn't show any devices listed although i can check the firmware and cid version(via fastboot command). And the device is showing up in device manager(my HTC). But adb commands are not working.
Am i missing something?
Any help would be much appreciated.
Click to expand...
Click to collapse
probably your hboot get locked after S-OFF.that's why adb commands don't work(i think)
check your bootloader details
if now you have S-OFF and locked hboot flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also patched hboot which is unlocked
follow the instructions to the letter(important)
and before flashing check md5 sums(important)
rzr86 said:
probably your hboot get locked after S-OFF.that's why adb commands don't work(i think)
check your bootloader details
if now you have S-OFF and locked hboot flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also patched hboot which is unlocked
follow the instructions to the letter(important)
and before flashing check md5 sums(important)
Click to expand...
Click to collapse
Appreciate your concern.
But the thing is my device is still S On. The JBear method didn't finish. It messed up in between.
I'm attaching a pic. Give a look.
walkermoon said:
Appreciate your concern.
But the thing is my device is still S On. The JBear method didn't finish. It messed up in between.
I'm attaching a pic. Give a look.
Click to expand...
Click to collapse
hmm,
probably you need to use the temproot remove.bat file to remove temproot
check for troubleshooting in this thread
http://forum.xda-developers.com/showthread.php?t=1661631
also refer you issue there
ganeshp will help you further
or you can install 4ext recovery
enable smartflash from it and flash a custom rom
First of all I apologize if this has been covered, I have been trying to find a solution for 3 days straight. I have a Rogers Wireless HTC One X I managed to unlock bootloader and root as well as having access to TWRP 2.1.8. recovery.
My problem is when I tried to apply the 3 dot removal mod my phone suddenly would not boot past the first screen, and a message would appear for developers use do not distribute but just stay on that screen. I have tried numerous things to no avail. I can boot in recovery and mount sd card from there (but have not found a successful way to restore from within recovery mode) otherwise in fastboot etc. the computer does mount the phone at all. it will not mount as a device properly so I cannot run the RUU and flash to stock.
So I am left with a unmountable and unbootable phone (brick) and have no other ideas on how to fix it if possible. BTW the device does show in device mgr and the computer gives the connect and disconnect alert, but it will not mount. Also, I have read the bootloader has to be relocked to flash back to stock if I relock the phone I cannot access recovery therefore an endless nightmare. Also, within TWRP recovery I try to reboot and it gives an error saying no Android OS found, install a rom or restore from backup (which I have neither) so I have to hold the power and dwn volume button to reboot each time to switch from recovery to fastboot. I think its toast.
Thank you in advance for any responses, I have been up almost 36 hours straight trying to figure this out and the phone is not even a week old. :crying:
There's a link in dev to unofficial twrp with usb mount support install that by following the directions in the thread. Then you'll be able to copy a rom to the phone for flashing.
Or you can install HTC Sync on your computer and that may allow you to use a RUU to flash back to stock. HTC Sync has the required drivers to make a Windows PC recognize the HOX.
gunnyman said:
There's a link in dev to unofficial twrp with usb mount support install that by following the directions in the thread. Then you'll be able to copy a rom to the phone for flashing.
Click to expand...
Click to collapse
Thank you very much I will look into that today. Fingers crossed!
i ran into a similar situation about a week ago. hard shut down the phone by holding down power button for like 10 seconds, then boot into bootloader. hit fastboot. connect your phone to computer, and fastboot oem lock bootloader. now you can ruu. Download Rogers RUU utility and follow steps. Voila! Phone is just like new! but first make sure you still have your old unlock_bin code in case you want to reunlock bootloader.
stnguyen09 said:
Or you can install HTC Sync on your computer and that may allow you to use a RUU to flash back to stock. HTC Sync has the required drivers to make a Windows PC recognize the HOX.
Click to expand...
Click to collapse
Yes, thank you I have HTC Sync installed and it does not recognize the phone when it is connected either. I will keep searching. Thanks.
ethantarheels123 said:
i ran into a similar situation about a week ago. hard shut down the phone by holding down power button for like 10 seconds, then boot into bootloader. hit fastboot. connect your phone to computer, and fastboot oem lock bootloader. now you can ruu. Download Rogers RUU utility and follow steps. Voila! Phone is just like new! but first make sure you still have your old unlock_bin code in case you want to reunlock bootloader.
Click to expand...
Click to collapse
Yes, I have tried relocking bootloader, it did not help with the phone being recognized by the computer also when I oem lock I cannot access recovery and such. I will have some more time to poke around with it, I have downloaded the RUU utility although it sends back error with device not found. Thanks for your reply, I will keep at it I know the phone can not be bricked, well I am hoping not!
I bought a HTC One S for T-Mobile USA. Has been working flawlessly. Today I got an OTA and my world is now upside down. I have spent 5 hours trying countless things to get my phone back up to no avail.
my phone stats:
hboot 1.09.0000
radio 0.16.31501s.16_2
open dsp-v28.1.0.32.0504
emmc-boot apr 2 2012,21:08:24
UNLOCKED
TAMPERED
How do I get back to square one and turn this phone back into something usable?
It has something called TWRP 2.1.7 installed on it and I have tried fastboot and a host of other things to remove it. I have even tried the thread on sending your phone back to stock but I can't access RUU because it won't load the driver. I have never rooted this phone nor do I believe USB Debugging was turned on before I accepted the OTA. I can communicate via fastboot in the command shell via a usb cable. The PC wont mound the SD card so I can't copy a new image and reboot this thing on a different rom and then send it back to stock.
I am about ready to throw it away because i can't seem to get a .zip file to it so it will run again (for putting a working build on it). There are no images to boot to. Somehow that got wiped and no backup was done. I don't give a poop if the data is whiped. Its all backed up via dropbox and exchange. I just want it up and running so i can use RUU and send it back to stock.
Any help would be appreciated.
Scuba_Luv said:
I bought a HTC One S for T-Mobile USA. Has been working flawlessly. Today I got an OTA and my world is now upside down. I have spent 5 hours trying countless things to get my phone back up to no avail.
my phone stats:
hboot 1.09.0000
radio 0.16.31501s.16_2
open dsp-v28.1.0.32.0504
emmc-boot apr 2 2012,21:08:24
UNLOCKED
TAMPERED
How do I get back to square one and turn this phone back into something usable?
It has something called TWRP 2.1.7 installed on it and I have tried fastboot and a host of other things to remove it. I have even tried the thread on sending your phone back to stock but I can't access RUU because it won't load the driver. I have never rooted this phone nor do I believe USB Debugging was turned on before I accepted the OTA. I can communicate via fastboot in the command shell via a usb cable. The PC wont mound the SD card so I can't copy a new image and reboot this thing on a different rom and then send it back to stock.
I am about ready to throw it away because i can't seem to get a .zip file to it so it will run again (for putting a working build on it). There are no images to boot to. Somehow that got wiped and no backup was done. I don't give a poop if the data is whiped. Its all backed up via dropbox and exchange. I just want it up and running so i can use RUU and send it back to stock.
Any help would be appreciated.
Click to expand...
Click to collapse
I hate to tell you this but if you never unlocked or rooted your phone, somebody did. Your device is unlocked and running a custom recovery therefore you cannot accept over the air updates and that is your problem. You did not buy your phone that way from T-Mobile so what did you really do to get to this point?
Behold_this said:
I hate to tell you this but if you never unlocked and rooted your phone, somebody did. Your device is unlocked and running a custom recovery therefore you cannot accept over the air updates and that is your problem. You did not buy your phone that way from T-Mobile so what did you really do to get to this point?
Click to expand...
Click to collapse
I never said I bought it as OEM. I also never thought to ask the guy I got it from if he rooted it or unlocked it.
Relocking the boot loader then running an RUU should fix the issue. Once you do that enter the recovery and wipe everything/factory reset.
Then if you are trying to run a custom ROM you should be able to mount your SD card and push one to the phone.
Sent from my HTC One S using xda premium
beats4x said:
Relocking the boot loader then running an RUU should fix the issue. Once you do that enter the recovery and wipe everything/factory reset.
Then if you are trying to run a custom ROM you should be able to mount your SD card and push one to the phone.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Great reply however I am short on knowledge on how to do what you have recommended. I don't know how to relock the boot loader nor can I run RUU because I can't get the driver installed. Any help would be awesome. Thank in advance. Sorry I'm a noob at this.
In the dev section there is an all in one toolkit that will execute the correct scripts for you. Download it, then run it. You may also need the HTC sync drivers installed on your computer.
Once you see that the bootloader is locked run the ruu.
And don't apologize for being a noob, I am too lol. We all need help to get started.
Sent from my HTC One S using xda premium
If you install HTC sync to your pc it should install the driver's you need. Then install the one s tool kit in developers section to relock. Then run ruu.
Also, anything you see in blue text is what you'll need to type, or copy/paste, to avoid any quote confusion.
Files You Need:
T-Mobile USA RUU file (mirror) - it's about 563 mb, and worth saving once you download it.
Extremely Important: If you're on another carrier you'll need a different RUU file - DO NOT try and run this RUU file, it could really screw you up. Go to this link to find the right RUU file.
HTC Drivers (mirror) - You probably already have the drivers installed if you're needing this thread, but just in case...
ADB / Fastboot (mirror) - same as the drivers, but again, just in case...
Initial Setup:
Again, some of this might be redundant as you might already have this setup if you rooted/unlocked.
Install the HTC drivers if you haven't already
Unzip the adbfastboot.zip file to your desktop (anywhere, but I find it easiest to get to it on the desktop for my habits)
Getting into the bootloader (hboot):
If you're stuck in a boot loop, pull the batt... oh wait, we can't do that here. To perform a hard reset, hold down the power button for 10 seconds - in the process you'll see the softkeys start blinking, then it should reset. As soon as it starts to reset, release power, and hold down the volume-down button - hold it until hboot pops up (white screen, colored text).
If you're phone is fully powered off (make sure "fastboot" is disabled - settings > power), hold the volume-down key and while holding it, press and hold power for a few seconds. You can probably release the power button, just make sure you keep holding volume-down - after probably 3-5 seconds (maybe a bit more), hboot should come up.
If the phone is on and you're plugged in to your computer, make sure "usb debugging is enabled" (settings > developer options), shift+right-click the adbfastboot directory on your desktop (or wherever you put it), choose "open command window here", and in the prompt that comes up, input adb reboot bootloader.
Restoring:
Once you're in hboot, make sure you select Fastboot (if you don't see it, you're in Fastboot already). In the command prompt referenced above, input fastboot oem lock. This will relock your bootloader in order to allow the RUU to run. Historically this has been necessary for an RUU to run, but I haven't actually tested it without relocking on the One S, and assumed based on previous HTC devices that this would continue to be the case. Edit: thanks rbrookstx for confirming that re-locking is necessary
Your phone will reboot when it relocks - follow the steps above to get back into hboot.
Once you're back in hboot, make sure you're in Fastboot, and open / run the RUU file. It'll go through some initial prompts, then it should start. It takes about 10-15 minutes, maybe less, depending on your computer.
Once it's done, it'll simply go back into hboot - reboot, and you're good to go.
A couple of notes:
When you unlocked and flashed a custom recovery (if you did that), hboot probably said "tampered with" and when it booted up, it probably had a red message under the "HTC" logo about being a developer only device. That should be gone now. It should boot up clean, and hboot should simply say "relocked", with no tampered message.
Until a better solution comes out, once you unlock the bootloader with HTC's official method, it can never be locked the way it was from the factory. "Relocked" is the best you can do.
Click to expand...
Click to collapse
This is what worked. I had to search the internet for this stuff but the HTC driver, the fast boot and the RUU with a matching or higher radio number all made it work out.
Hi. I'm a newbie on these forums, so please be easy on me. My father recently decided that he wanted to enter the smartphone world and decided on a One XL. He bought it on eBay from a Chinese seller, so I'm pretty sure the One XL is the Chinese variant w/ the 2600 band for LTE.
I'm generally a BlackBerry guy (currently own a Z10), but have used all the phone OSes at some point. I've been pretty comfortable modifying my own BlackBerry, I use Linux at home as my main OS, and I'm also a computer science major studying programming (so I'm not in over my head here).
There are few things that I think would be cool for my Dad:
1) LTE speeds on T-Mobile. If not, 3G or HSPA
2) Android 4.4 KitKat
3) Sense 5
I'm pretty familiar with sideloading so that shouldn't be a problem (Flappy Bird).
I hope my Dad didn't didn't mess up for himself by buying the Chinese version if he wants faster speeds (than EDGE) on T-Mobile. I appreciate any help you may give. Thank you!
You should have no problems getting LTE on the device. You can have KitKat but it will be via an aosp ROM, not Sense. Sense ROMs for our device only go up to Android 4.2.2 and that's probably where they'll stay.
If you want to run a custom ROM on it just head over to htcdev and unlock the bootloader, then you can install a custom recovery, and from there you can install a custom ROM. I have detailed instructions for many of these operations in my How-To Guide For Beginners thread in my signature. You should also read the Evita FAQ thread in my signature, and bookmark the resource thread.
What are the bootloader details on the device? To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Sent from my One XL using Tapatalk
timmaaa said:
You should have no problems getting LTE on the device. You can have KitKat but it will be via an aosp ROM, not Sense. Sense ROMs for our device only go up to Android 4.2.2 and that's probably where they'll stay.
If you want to run a custom ROM on it just head over to htcdev and unlock the bootloader, then you can install a custom recovery, and from there you can install a custom ROM. I have detailed instructions for many of these operations in my How-To Guide For Beginners thread in my signature. You should also read the Evita FAQ thread in my signature, and bookmark the resource thread.
What are the bootloader details on the device? To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines.
Sent from my One XL using Tapatalk
Click to expand...
Click to collapse
Thanks! My dad can live without KitKat. Here's the bootloader details:
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.09.0000
RADIO-0.16a.32.09.17_2
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012,21:08:24
EVITA
Jaguarandine said:
Thanks! My dad can live without KitKat. Here's the bootloader details:
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.09.0000
RADIO-0.16a.32.09.17_2
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012,21:08:24
EVITA
Click to expand...
Click to collapse
Well you got really lucky and bought a device that's been modified in the past. It already has s-off and SuperCID (11111111). That's half the work done for you. What does it say above those lines though? It should say locked/unlocked/relocked and possibly also tampered.
Your firmware is a bit outdated so you'll need to update that, which will be easy because you already have s-off on the device. Before we go any further I need the other lines from the bootloader though.
Sent from my One XL using Tapatalk
timmaaa said:
Well you got really lucky and bought a device that's been modified in the past. It already has s-off and SuperCID (11111111). That's half the work done for you. What does it say above those lines though? It should say locked/unlocked/relocked and possibly also tampered.
Your firmware is a bit outdated so you'll need to update that, which will be easy because you already have s-off on the device. Before we go any further I need the other lines from the bootloader though.
Sent from my One XL using Tapatalk
Click to expand...
Click to collapse
I'm at work now, and left the phone at home. I believe it said unlocked. I'll be able to work on this some more in a few hours. Thanks for all your help so far.
No problems. I'm subscribed to this thread so just pop in later and we'll sort you out. If it does say unlocked that leaves very little actual work for you to do, it's pretty much all been done. One thing you will need to do though is to install adb & fastboot on your PC, if you Google "minimal adb & fastboot" the first result will be an XDA thread which details how to do it, that's the easiest way. Another thing you'll need to do is install HTC drivers on the PC, the best way to do this is to install HTC Sync Manager and then connect your phone (first while booted into the OS, and secondly while in bootloader mode), this should install the drivers automatically. Once you've done that you test it by doing the following:
Navigate to the folder where adb.exe and fastboot.exe are located on your PC, shift + right click, select open command prompt here, then issue these commands:
Code:
adb devices
(While booted into Android)
Code:
fastboot devices
(While in bootloader mode, with "fastboot usb" showing on the phone screen)
Each command should return the serial number of your device. While you're issuing the adb command make sure your screen is on and unlocked because you may see a prompt asking to grant access which you need to confirm.
Before doing this you will also need to navigate to /settings/developer options on the device and enable usb debugging. If developer options doesn't appear in your settings you just need to navigate to /settings/about phone, then find the "build number" category and tap it about eight or so times, this unlocks developer options.
Sent from my One XL using Tapatalk
timmaaa said:
No problems. I'm subscribed to this thread so just pop in later and we'll sort you out. If it does say unlocked that leaves very little actual work for you to do, it's pretty much all been done. One thing you will need to do though is to install adb & fastboot on your PC, if you Google "minimal adb & fastboot" the first result will be an XDA thread which details how to do it, that's the easiest way. Another thing you'll need to do is install HTC drivers on the PC, the best way to do this is to install HTC Sync Manager and then connect your phone (first while booted into the OS, and secondly while in bootloader mode), this should install the drivers automatically. Once you've done that you test it by doing the following:
Navigate to the folder where adb.exe and fastboot.exe are located on your PC, shift + right click, select open command prompt here, then issue these commands:
Code:
adb devices
(While booted into Android)
Code:
fastboot devices
(While in bootloader mode, with "fastboot usb" showing on the phone screen)
Each command should return the serial number of your device. While you're issuing the adb command make sure your screen is on and unlocked because you may see a prompt asking to grant access which you need to confirm.
Before doing this you will also need to navigate to /settings/developer options on the device and enable usb debugging. If developer options doesn't appear in your settings you just need to navigate to /settings/about phone, then find the "build number" category and tap it about eight or so times, this unlocks developer options.
Sent from my One XL using Tapatalk
Click to expand...
Click to collapse
So it looks like my Dad bought a used phone, right? With everything that's been done, I'm not sure if that's a bad thing or not. Since my Dad wouldn't be happy, I do think I'll keep this little detail between us though
4.2.2 + Sense is better, right? I wouldn't want to shoehorn KitKat on here if there are some features missing and the performance is not as good.
Btw out of curiosity, do these programs have a Linux equivalent? If not, it's cool, I have a Windows machine at home too.
Jaguarandine said:
So it looks like my Dad bought a used phone, right? With everything that's been done, I'm not sure if that's a bad thing or not. Since my Dad wouldn't be happy, I do think I'll keep this little detail between us though
4.2.2 + Sense is better, right? I wouldn't want to shoehorn KitKat on here if there are some features missing and the performance is not as good.
Btw out of curiosity, do these programs have a Linux equivalent? If not, it's cool, I have a Windows machine at home too.
Click to expand...
Click to collapse
Oh yeah, the phone is without a doubt pre-owned. Whether Sense or aosp is better is a matter of taste, and your dad won't really know which one is best for him unless he's able to play with each of them for a few days to get the feel of them both.
I had forgotten you mentioned having Linux as your main OS at home, and yes adb & fastboot are Linux compatible, they're actually much easier to install because they don't require drivers on Linux. Just Google how to install them on Linux, you should get a bunch of results with clear directions.
Sent from my One XL using Tapatalk
Well, I was wrong. The top line says *** LOCKED ***. Looking for the other programs now.
Edit: Took me a while, but I was able to find and get the drivers working in Ubuntu successfully
Code:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT288W303498 device
After going into bootloader, and entering fastboot mode, I get the following:
Code:
[email protected]:~$ sudo fastboot devices
HT288W303498 fastboot
Ok, that's good. Your bootloader is actually in a relocked state but the previous owner has spoofed it to say locked, that's my guess anyway. Either way, your next step is to head over to htcdev and dole the directions there to unlock your bootloader. You can skip the installing fastboot part obviously.
Sent from my Evita
Ok, bootloader now says unlocked.
Jaguarandine said:
Ok, bootloader now says unlocked.
Click to expand...
Click to collapse
Cool. Now is the point where you need to upgrade the firmware on the device. This is pretty straight forward command line stuff using fastboot.
Download the firmware from here:
http://www.androidfilehost.com/?fid=23060877490004040
Place it in your fastboot folder (the folder where you have fastboot located on your PC). Rename it to "215firmware.zip" to make things easier later on. Open a command prompt from within that folder, or just open a command prompt and use the CD command to change directory to that fastboot directory. Connect your phone in fastboot mode and issue this command to make sure your connection is good:
Code:
fastboot devices
Once you've established a working connection (it'll show your serial number) you can start the process with this command:
Code:
fastboot oem rebootRUU
The phone will not boot into rebootRUU mode which is a black screen with the HTC logo. Now issue this command:
Code:
fastboot flash zip 215firmware.zip
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command again. If it ends with "INFO..... OK", just reboot to the bootloader with this command:
Code:
fastboot reboot-bootloader
Verify everything was successful by looking at the hboot version and radio version in the bootloader screen. They should be as follows:
Hboot: 2.15
Radio: 1.31a.32.45.16_2
Now just reboot your phone by issuing this command:
Code:
fastboot reboot
Sent from my Evita
timmaaa said:
Cool. Now is the point where you need to upgrade the firmware on the device. This is pretty straight forward command line stuff using fastboot.
Download the firmware from here:
http://www.androidfilehost.com/?fid=23060877490004040
Place it in your fastboot folder (the folder where you have fastboot located on your PC). Rename it to "215firmware.zip" to make things easier later on. Open a command prompt from within that folder, or just open a command prompt and use the CD command to change directory to that fastboot directory. Connect your phone in fastboot mode and issue this command to make sure your connection is good:
Code:
fastboot devices
Once you've established a working connection (it'll show your serial number) you can start the process with this command:
Code:
fastboot oem rebootRUU
The phone will not boot into rebootRUU mode which is a black screen with the HTC logo. Now issue this command:
Code:
fastboot flash zip 215firmware.zip
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command again. If it ends with "INFO..... OK", just reboot to the bootloader with this command:
Code:
fastboot reboot-bootloader
Verify everything was successful by looking at the hboot version and radio version in the bootloader screen. They should be as follows:
Hboot: 2.15
Radio: 1.31a.32.45.16_2
Now just reboot your phone by issuing this command:
Code:
fastboot reboot
Sent from my Evita
Click to expand...
Click to collapse
Very detailed instructions, thanks! everything Seems to be working well and Hboot and Radio have been updated.
Jaguarandine said:
Very detailed instructions, thanks! everything Seems to be working well and Hboot and Radio have been updated.
Click to expand...
Click to collapse
You're doing well, all that's left to do now is to flash TWRP recovery and install a ROM. You'll need to decide what kind of ROM you're going to flash because currently Sense ROMs and KitKat aosp ROMs need different recoveries.
For any Sense ROM you can use this recovery:
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.3.0-evita.img
For any KitKat aosp ROM you need to ue this recovery:
http://www.androidfilehost.com/?fid=23252070760973615
Once you've installed the recovery you will need to make a backup of your current system just in case anything goes wrong in future, or if you want to use it again. Check the How-To Guide For Beginners thread in my signature for detailed instructions on how to do that.
Once you've done that you can go ahead and find a ROM you want to install and flash it. Our two develpment sections are as follows:
Android Development
(for Sense ROMs)
Original Android Development
(for aosp ROMs)
Once you've picked one you can download it and head back to my guide thread for full instructions on how to flash it.
@timmaaa your awesome dude, keep up the great help you offer :thumbup:
Sent from my One using Xparent Red Tapatalk 2
I started noticing this strange flickering on the sides of the screen. The screen is fine on a white background or when the brightness is turned down. But as soon as color is introduced on a white background, the flickering starts. Is this normal? And will it go away?
Jaguarandine said:
I started noticing this strange flickering on the sides of the screen. The screen is fine on a white background or when the brightness is turned down. But as soon as color is introduced on a white background, the flickering starts. Is this normal? And will it go away?
Click to expand...
Click to collapse
Was this happening before the firmware flash? Is it happening since the firmware flash?
---------- Post added at 04:00 AM ---------- Previous post was at 04:00 AM ----------
rc420head said:
@timmaaa your awesome dude, keep up the great help you offer :thumbup:
Sent from my One using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Thanks buddy, appreciate it.
Well, I've never noticed it before. I am however, using the phone a lot more regularly since I started updating it. I looked around, and it seems to be an issue a number of people have with the screen. I'll deal with it for now and see if gets any better. Brightness levels won't be too high most of the time anyway.
I think I'll choose Sense 5 and start installing the recovery.
It could simply be a mismatch between the firmware and whatever software version is currently installed on it. Or it could be a hardware defect. You could try running an RUU to rule that out, but that would require a Windows machine with adb/fastboot plus drivers.
Sent from my Evita
Now it's gone away. I dunno. The phone otherwise seems fine. I'll keep observing and if anything happens, I'll report back here.
Recovery installation went well. Now on to flashing the ROM.
Out of curiosity, which ROM do you have on your phone?
One thing I did notice is that some ROMS recommend Jellybean should be installed. Is that an issue for this phone?