Related
Hello,
I have an Evo Shift stuck in the boot loop. As soon as I put the battery in all it does is reset itself to the screen with the white background and green "HTC" logo, and will keep restarting until the battery dies.
If I hold volume down and turn it on, it does go into the bootloader, but picking ANYTHING, such as recovery or factory reset, does nothing but sending it back to the HTC screen.
I have tried flashing the RUU.exe (2.27.651.2) through Fastboot USB and it completed successfully, but it just restarts right back to the HTC screen. I have also put PG06img that I found on here on the root of my card, and it will never load it up.
Are there any other solutions anyone can think of? They would be much appreciated. I see a lot of these threads for regular Evos, but not for Shifts.
The only other thing I really know about the phone is that it is:
S-On
Hboot- 0.98.0001
Radio- 1.08.00.0506
Thank you so much for all of your help!
Seems to me you aren't rooted and that's more than likely your problem, boot into fastboot and use the ruu application for gingerbread.
Sent from my PG06100 using Tapatalk
Rooster85 said:
Seems to me you aren't rooted and that's more than likely your problem, boot into fastboot and use the ruu application for gingerbread.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
While I am pretty sure I am not rooted, if you are talking about the early RUU release; 1.17.651.1, the application starts and then ends up failing in the beginning of the process. Is this what you are talking about? The drivers should be all good, the application starts to flash and then dies though. Thanks!
samcrac said:
While I am pretty sure I am not rooted, if you are talking about the early RUU release; 1.17.651.1, the application starts and then ends up failing in the beginning of the process. Is this what you are talking about? The drivers should be all good, the application starts to flash and then dies though. Thanks!
Click to expand...
Click to collapse
Use the new RUU. But make sure your SD card is formatted to a FAT32 partition. (Stock 2gig sd card and some other store boughts are not)
You can format on your computer and then place the RUU on the root of sd card again
(Bootloader won't recognize the ruu zip if not partitioned)
Sent from my Supreme Shift
notsointeresting said:
Use the new RUU. But make sure your SD card is formatted to a FAT32 partition. (Stock 2gig sd card and some other store boughts are not)
You can format on your computer and then place the RUU on the root of sd card again
(Bootloader won't recognize the ruu zip if not partitioned)
Click to expand...
Click to collapse
Ok, I just did this, everything updated fine and all completeted on the bootloader. It then said "press power to reboot." I did so, and went right back into the same boot loop. Any other ideas. I figured running this, and the RUU.exe on the computer were the sure fire ways to get this thing working again???
samcrac said:
Ok, I just did this, everything updated fine and all completeted on the bootloader. It then said "press power to reboot." I did so, and went right back into the same boot loop. Any other ideas. I figured running this, and the RUU.exe on the computer were the sure fire ways to get this thing working again???
Click to expand...
Click to collapse
So just a little information.
you said your not rooted?
So that means you have no ability to flash anything because you have no custom recovery and the bootloader isnt unlocked (S-on)
So what DID you do before it bootlooped? there had to have been something you were trying to do.
Not trying to blame anything on you at all just want to make sure we are helping the most accurate way possible
notsointeresting said:
So just a little information.
you said your not rooted?
So that means you have no ability to flash anything because you have no custom recovery and the bootloader isnt unlocked (S-on)
So what DID you do before it bootlooped? there had to have been something you were trying to do.
Not trying to blame anything on you at all just want to make sure we are helping the most accurate way possible
Click to expand...
Click to collapse
No I hear ya. I was sold the phone fairly cheap and was told "all you need to do is to reinstall the RUU, that is all that is wrong." Obviously I was skeptical, but when I checked everything out, everything looked good, and again, for the price, I knew it was a gamble. That being said, I'm sure something was tried in order to modify the phone and this is how it got like this.
I have soft bricked my old Evo 4g a handful of times and an RUU or Rom flash would always solve the problem.
Anyway, there is no custom recovery, and I'm pretty sure theres no root because it is still "S-ON," I am just trying to see if anyone here has any more info before it goes in for repair.
The only last thing I would guess you MIGHT be able to do is to install a custom recovery, but is there ANY way to do this by just being in the bootloader and using FASTBOOT USB? Any more help is greatly appreciated. Thanks!
samcrac said:
No I hear ya. I was sold the phone fairly cheap and was told "all you need to do is to reinstall the RUU, that is all that is wrong." Obviously I was skeptical, but when I checked everything out, everything looked good, and again, for the price, I knew it was a gamble. That being said, I'm sure something was tried in order to modify the phone and this is how it got like this.
I have soft bricked my old Evo 4g a handful of times and an RUU or Rom flash would always solve the problem.
Anyway, there is no custom recovery, and I'm pretty sure theres no root because it is still "S-ON," I am just trying to see if anyone here has any more info before it goes in for repair.
The only last thing I would guess you MIGHT be able to do is to install a custom recovery, but is there ANY way to do this by just being in the bootloader and using FASTBOOT USB? Any more help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
It shouldn't have a custom recovery if it shows s-on.
I don't see why the RUU wouldn't work.
Honestly it doesn't sound like a softbrick- sounds like its just bricked (Which ive only heard of 1 Shift getting bricked completley)
notsointeresting said:
It shouldn't have a custom recovery if it shows s-on.
I don't see why the RUU wouldn't work.
Honestly it doesn't sound like a softbrick- sounds like its just bricked (Which ive only heard of 1 Shift getting bricked completley)
Click to expand...
Click to collapse
Make it 2! Thanks for your help though!!!
Also Stuck In A Bootloop
samcrac said:
Hello,
I have an Evo Shift stuck in the boot loop. As soon as I put the battery in all it does is reset itself to the screen with the white background and green "HTC" logo, and will keep restarting until the battery dies.
If I hold volume down and turn it on, it does go into the bootloader, but picking ANYTHING, such as recovery or factory reset, does nothing but sending it back to the HTC screen.
I have tried flashing the RUU.exe (2.27.651.2) through Fastboot USB and it completed successfully, but it just restarts right back to the HTC screen. I have also put PG06IMG that I found on here on the root of my card, and it will load it up (I'll see the blue loading bar and then the brown loading bar in the top right hand corner of the screen), but it then checks it again, and then goes back to the original screen for the bootloader.
Are there any other solutions anyone can think of? They would be much appreciated. I see a lot of these threads for regular Evos, but not for Shifts.
The only other thing I really know about the phone is that it is:
S-On
Hboot- 0.98.0001
Radio- 1.08.00.0506
Thank you so much for all of your help!
Click to expand...
Click to collapse
I'm trying to resolve a very similar problem as him, but I know of the history of my phone (since I'm the only owner), so hopefully an answer for me can assist him also.
The Story: One day, I'm playing Uno HD (downloaded from Android Market). I toss out a Draw 4, and then I see: "Google Infrastructure Failure" and a Triangle with an exclamation mark. I reset the phone, and it starts up fine. Then a few hours later, my phone randomly restarts itself into the bootloader screen after trying to reload the home screen (because the memory manager is overly aggressive).
I see no HTC Screen. It goes straight to the bootloader without any input. If I plug it to the charger from an off state, the amber light comes on, and 10 seconds later, bootloader screen. With a battery, it appears automatically after 45 seconds.
Fastboot can read my memory card just fine. It's already been re-formatted as FAT32 in my pitiful attempt to try to repair it. It's checked and read a PG06IMG file I placed on the SD Card's root, went through the entire process of reading it, but it doesn't ask me if I want to upgrade. It takes me back to the original screen. (Maybe I'm loading the wrong file).
Recovery and Factory Reset immediately restarts the bootloader after showing me the skateboarding android splash screen.
I've also tried to flash the newest stock RUU for it. (2.76.651.4), but after the RUU sends the command to start up in bootloader mode, the phone shuts off. Thus giving me the connection error.
(Maybe if someone could rewrite the .exe file to not send out the command to begin loading as if it was in the bootloader screen, it could work. I'd pay for that.)
Other Stuff:
ROM: Stock Sprint Gingerbread OTA ROM. I've been living the vanilla life. No root access. No funny stuff. Just a stock phone with apps (Third Blade, Uno HD, ASTRO File Manager, ect...)
Directly from bootloader screen:
SPEEDY XA SHIP S-ON
HBOOT-0.98.0001
RADIO-1.08.00.0506
eMMC-boot
April 11 2011, 22:32:34
Is there a way we can flash a file from the SD Card which will turn off the security and/or temp/perm root it? (forgive my noobness for such a question)
EDIT: I'm referring to a way that's outside of the adb push method. My device can't be found, and the device won't get past the bootloader screen, so that method doesn't help me too much. However, I do have the ADK Installed and the ADB Command Line works fine.
Ok .. HERE'S THE SOLUTION:
First off all if your S- ON it means you are NOT rooted
If you get stuck in a bootloop .. don't worry it can be fixed.
What you need to do is download PG06IMG.ZIP and place it on your sd card, you can access your sd card by going into recovery then mount section, then usb. This will allow you to move the file from your computer to the root of your sd card.
Once you do this be sure you back up any info you don't want to lose. Once you have the file in place, go back to fastboot ( hold vol down and power) it will read file and when it asks you to update press vol up. It will take a few minutes to update this will revert your phone back to stock but if you have an old recovery it will not do a full restore, it will only update the rom.
Once you get your phone back to working, I recommend updating your recovery by downloading Rom Manager and flashing the latest clockwork recovery. This problem happens usually due to an old recovery.
One other thing you can try if you do NOT want to reset your phone, you can try flashing a new kernal.
Sent from my PG06100 using Tapatalk
RUU won't work if your stuck in bootloop ..
Sent from my PG06100 using Tapatalk
If you want to root your phone use visionary to temp root then use shift rr .. you can then flash a custom recovery which is essential to avoid this from happening again
flylike2kites said:
I'm trying to resolve a very similar problem as him, but I know of the history of my phone (since I'm the only owner), so hopefully an answer for me can assist him also.
The Story: One day, I'm playing Uno HD (downloaded from Android Market). I toss out a Draw 4, and then I see: "Google Infrastructure Failure" and a Triangle with an exclamation mark. I reset the phone, and it starts up fine. Then a few hours later, my phone randomly restarts itself into the bootloader screen after trying to reload the home screen (because the memory manager is overly aggressive).
I see no HTC Screen. It goes straight to the bootloader without any input. If I plug it to the charger from an off state, the amber light comes on, and 10 seconds later, bootloader screen. With a battery, it appears automatically after 45 seconds.
Fastboot can read my memory card just fine. It's already been re-formatted as FAT32 in my pitiful attempt to try to repair it. It's checked and read a PG06IMG file I placed on the SD Card's root, went through the entire process of reading it, but it doesn't ask me if I want to upgrade. It takes me back to the original screen. (Maybe I'm loading the wrong file).
Recovery and Factory Reset immediately restarts the bootloader after showing me the skateboarding android splash screen.
I've also tried to flash the newest stock RUU for it. (2.76.651.4), but after the RUU sends the command to start up in bootloader mode, the phone shuts off. Thus giving me the connection error.
(Maybe if someone could rewrite the .exe file to not send out the command to begin loading as if it was in the bootloader screen, it could work. I'd pay for that.)
Other Stuff:
ROM: Stock Sprint Gingerbread OTA ROM. I've been living the vanilla life. No root access. No funny stuff. Just a stock phone with apps (Third Blade, Uno HD, ASTRO File Manager, ect...)
Directly from bootloader screen:
SPEEDY XA SHIP S-ON
HBOOT-0.98.0001
RADIO-1.08.00.0506
eMMC-boot
April 11 2011, 22:32:34
Is there a way we can flash a file from the SD Card which will turn off the security and/or temp/perm root it? (forgive my noobness for such a question)
EDIT: I'm referring to a way that's outside of the adb push method. My device can't be found, and the device won't get past the bootloader screen, so that method doesn't help me too much. However, I do have the ADK Installed and the ADB Command Line works fine.
Click to expand...
Click to collapse
Sent from my PG06100 using Tapatalk
Also if your phone can't be found its b/c you need to put it into diag mode .. ##DATA .. if you need more help google
tech-9 said:
If you want to root your phone use visionary to temp root then use shift rr .. you can then flash a custom recovery which is essential to avoid this from happening again
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Sent from my PG06100 using Tapatalk
For the thread starter, the person that sold you the phone probably tried writing to the system partition with s-on. Since you can get to the bootloader, see if you can get into recovery. If you can, recovery can be seen in adb, even the stock recovery. From there, gingerbread root, plenty of guides out there, make sure you flash the misc.img, download the froyo downgrade zip (that pgimg09.zip or something like that, just search for it, but not with the numbers I just gave, those are made up.)
From there either flash the gingerbread zip or ruu, and goon with a unrooted life. Or follow one of the many guides to froyo root, and live the life of the rooted. Your choice.
For the second person with a similar issue, the same method will work for you (assuming you can get to recovery), gingerroot, froyo downgrade, and since you like being unrooted, just ruu or zip back to gingerbread.
Solution found enjoy, and just think, if root hadn't been discovered for gingerbread, you would be screwed right now, make sure to thank otaking.
I have the same boot loop problem. I tried using the PG06IMG.zip file and fastboot/bootloader screen says I have the wrong image. It's most likely because it's for 2.2 and I have 2.3. I also don't have any recovery. Is there a PG06IMG.zip for 2.3 or the like?
similar problem here
i'm fairly certain i tried recovery with the wrong or corrupt or incomplete PG06IMG.zip on my first attempt. i got the right one from here http://forum.xda-developers.com/showthread.php?t=1255474
i ran it, says update installed, but when i reboot i still get the loop
from bootloader
SPEEDY XE SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Nov 15 2010, 13:19:54
zdavidzz said:
i'm fairly certain i tried recovery with the wrong or corrupt or incomplete PG06IMG.zip on my first attempt. i got the right one from here http://forum.xda-developers.com/showthread.php?t=1255474
i ran it, says update installed, but when i reboot i still get the loop
from bootloader
SPEEDY XE SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Nov 15 2010, 13:19:54
Click to expand...
Click to collapse
Try downloading the zip again and re run it. Possibly a bad download?
Sent from my PG06100 using Tapatalk
also adb is telling me device not found. i think i might have to factory reset. is that crazy?
---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------
and... that didn't help
i'm downloading the zip again right now.
since i have s-on, will i be able to install it though?
i can get the file on the root of the sdcard with an adapter since i can't push from adb. and i can't temp root the phone because if i try a normal reboot i get this stupid boot loop. is there a way to get s-off through hboot on the phone?
i don't know why i didn't notice that first file was messed up, it was only 6MB.
Dear forum,
I kind of hesitated to start a thread for my problem, but after a long time I still haven't found a solution. I have contacted HTC (no answer yet), but hope to resolve my problem in meanwhile instead of waiting 1 month+ for a replacement.
I got the -by now familiar- freeze, and after rebooting it would go beyond the HTC logo, then stay stuck in a backlit black screen mode. Tried removing the battery, sim card, sd card etc. Then decided to boot into recovery (vol down + power) which worked, but any option would freeze the phone, like factory reset which I tried first.
Right now, the phone already freezes at the carrier logo, and I can't even get into recovery again (vol down + power). The phone won't respond to the key presses, and eventially boot and freeze at the carrier logo. The weird thing is that before, after a lot of trying and re-inserting the battery, it would eventually boot and work just fine for about 1 in 10 tries.
Does anyone have any ideas what I could try? Any help would be greatly appreciated!
edit: Okay, after a while I finally managed to get into HBoot again! Now what should I do to get my phone resetted/fixed? I guess it's not possible for me to flash another ROM or something as i'm not rooted. Details shown are: S-OFF, HBOOT 98.0002
can you get into recovery from bootloader?
Seems like I now consistently can boot into HBOOT. When I choose recovery, it will reboot, show the carrier logo, show the green logo with circular arrows, and then switch to the phone logo with a red exclamation mark for two seconds. Then, it shuts off. Also, when I tried that just now, it buzzed for like 6 times very fast after turning off.
On the second try, exactly the same happened: red exclamation mark, screen off, +- 6 fast buzzes.
After doing that, it doesn't respond to vol down+power or power at all. After reinserting the battery, I can get back into HBOOT
edit: it didn't want to boot into HBOOT, but now it does again. Anyhow, chosing recovery is still green logo, red logo, screen off and some buzzes. The phone doesn't show up in "adb devices" neither.
Whatever you are going to do; do not root your device as it will void your warrenty.
Is there anything else i can try doing? The situation so far:
-normal boot just stays stuck into carrier logo
-hboot->recovery gives a reboot, green logo, switch to red logo, screen off and +- 6 fast buzzes, then nothing. Needs battery reinsertion to be able to respond to vol down + power again
-hboot->factory reset just freezes on the same screen, no response, needs battery removal
-noshow in adb devices (update: show in fastboot!)
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
maxxur said:
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
Click to expand...
Click to collapse
Slow down maxxur, wait for this quesstion to be out there for long enough for someone to answer it.
Dont go on a battery pulling spree, coz that is the first and most tempting response on a frozen phone. But i hope you know what that can do to this phone...
Give the xda community some time to figure this out. Hold your ground till then. Need to go in to the theatre now. Will get back in the evening and try to figure this out.
Try running the RUU while in the fastboot menu (usb mode). Also my suggestion is not to make the process more complicated by downgrading - just reflash 1.47...
Thanks for the response guys
The RUU I found was 1.37. Could you point me to a 1.47 RUU for the 3UK network?
Also, running that RUU when in Fastboot USB mode is what I tried. The info on the RUU shows that it hangs indefinitely at "rebooting bootloader". That is expected, as when I try to manually reboot bootloader in my fastboot menu, my phone will also freeze.
I'm wondering if running a different recovery image could be of any help? Last night I tried running CWM recovery to see my options, by entering "fastboot boot recovery.img" but i'd get a "remote: not allow" error.
Have not noticed that you are not rooted!
Why don't you try the revolutionary tool? If you have luck it will restore your bootloader if it is broken (keep in mind that is not the best option because it will break you warranty). Then you will just need to flash an eng hboot and run the RUU, or better try some custom ROM
But in my opinion the best option for you is to go for a replacement rather to try yourself, since you dont have any custom software on it it has to be covered by your warranty (probably it is a faulty device to go like this from nothing).
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
maxxur said:
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
Click to expand...
Click to collapse
Of course you can if you are eager to try this. When you run the RUU, even when there is no phone connected there is a folder in your C: drive created (I assume that you are using Windows). Open your Windows Explorer and search for the rom.zip. When you have it copy it somewhere and close the RUU screen. Then if you open the RUU all the *.img files are there. You can try flashing the stock recovery or hboot or whatewer using the fastboot command. But I have to say again the best option for you is to bring the phone for a repair before you end up with something irreversible and void your warranty.
Thanks for keeping me sane on what to do with my problem Mentally, I came to the point where I'd go flash CWM recovery on my phone and try to flash that RUU rom from there, but you helped me get around that thought and now I made arrangements for HTC to come and pick it up. I'll keep you guys posted!
PS: you've got to love our desire s community, it's the best.
Cheered too early
Now HTC suddenly responds that while entering my phone in their warranty service thingy and the phone seemed to be 3G UK branded, they told me they "can't" do repairs for those.
Seriously, HTC is trying to troll me saying the inner hardware could differ between a UK and a Belgian Desire S?? Could this be true in any way?? :/
Maybe some parts are cheaper but with the same parameters...but I thought that when you have a branded phone you should seek your warrancy support from the carrier's office?!?
Sent from my HTC Desire S
Options for solution!
Option 1: Copy rom.zip (from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed) to your sd rename it to PG88IMG.zip and let m boot into hboot.
If option 1 is not ok try option 2.
Option 2: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU then after that run ruu RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.
If option 2 not OK then there is option 3.
Option 3: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU after that run in dos/terminal fastboot flash zip rom.zip (extracted from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed)
Let me know if one of these option worked for you if not I can help you with reflashing your hboot again.
NikMel,
Thank you so much for the tips. Currently I'm trying the first HBOOT + .ZIP method. It detected it, asked me to update and is now showing a pink "Updating" sign. How long should this normally take? I have a strong feeling it simply froze again, and it really turns out to be a hardware problem.
Is that updating next to radio?
If yes it will take realy long so wait!!
I have followed all of the procedures to reload my phone stuch on the splash screen, but have had no luck. Before I dispose of the phone, as it is in mint condition, I want to be sure there is no other options to update / reformat the bootloader
1. I have loaded the image for 2.2.1 AND 2.3.4 MULTIPLE TIMES
2. I have cleared the Cache's and no change
3. status on bootloader shows
GLACIAER PVT SHIP S-ON
HBOOT-09.0006
MICROP-0429
RADIO-26.13.04.19_M
eMMC-BOOT
Jul 15 2011, 16:45:17
I guess the last hope since th reloading the original images did not work is to reload / format the bootloader using ADB, but I believe that I have the wrong HBoot.
Is the phone eMMC bad and the phone bricked or is there something else to try?
johnmbailey said:
I have followed all of the procedures to reload my phone stuch on the splash screen, but have had no luck. Before I dispose of the phone, as it is in mint condition, I want to be sure there is no other options to update / reformat the bootloader
1. I have loaded the image for 2.2.1 AND 2.3.4 MULTIPLE TIMES
2. I have cleared the Cache's and no change
3. status on bootloader shows
GLACIAER PVT SHIP S-ON
HBOOT-09.0006
MICROP-0429
RADIO-26.13.04.19_M
eMMC-BOOT
Jul 15 2011, 16:45:17
I guess the last hope since th reloading the original images did not work is to reload / format the bootloader using ADB, but I believe that I have the wrong HBoot.
Is the phone eMMC bad and the phone bricked or is there something else to try?
Click to expand...
Click to collapse
When you try to flash PDwhatever.IMG, what does it tell you?
Glacier locked at Mytouch logo, without image load errors
THEindian said:
When you try to flash PDwhatever.IMG, what does it tell you?
Click to expand...
Click to collapse
It does not give any errors after flashing to 2.3.4, as it loads, verifies, then asks to load. It then successfully loads all pieces of the image, only to reboot to the same Mytouch logo screen.
When I use recovery, it can't mount anything, and when I wipe the Cache, it give arror that Ext3 is not compatible.
I reboot and factory restore in recovery, and gives the Ext3 compatibility message and can't mount anything.
I never receive any image loading errors, but I cannot load the 2.2.1 image, as it never give me a chance to say 'yes' to loading it.
If it doesn't work, care to sell it? I need a back and home button for mine lol
I also think my volume buttons will be gone soon, their starting to stick
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
siloner said:
If it doesn't work, care to sell it? I need a back and home button for mine lol
I also think my volume buttons will be gone soon, their starting to stick
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
Click to expand...
Click to collapse
The phone is in Mint Condition, so I hoped to resurrect it if at all possible, but if it is not possible I definitely will be selling it whole or in part.
johnmbailey said:
It does not give any errors after flashing to 2.3.4, as it loads, verifies, then asks to load. It then successfully loads all pieces of the image, only to reboot to the same Mytouch logo screen.
When I use recovery, it can't mount anything, and when I wipe the Cache, it give arror that Ext3 is not compatible.
I reboot and factory restore in recovery, and gives the Ext3 compatibility message and can't mount anything.
I never receive any image loading errors, but I cannot load the 2.2.1 image, as it never give me a chance to say 'yes' to loading it.
Click to expand...
Click to collapse
Thats really weird because usually if the emmc is dead, the image doesn't load completely in the bootloader. Have you tried calling tmo and telling them about your predicament? I know you are over warrenty but they might still help.
Glacier Stuck on Splash, now on StraightTalk service
THEindian said:
Thats really weird because usually if the emmc is dead, the image doesn't load completely in the bootloader. Have you tried calling tmo and telling them about your predicament? I know you are over warrenty but they might still help.
Click to expand...
Click to collapse
I am now on Straight Talk, so I no longer have a TMobile account to call about. My PAygo ended on Sunday with them.
Can I load anything from ADB with this version of the HBoot / Bootloader? Does the Ext3 mean it had a newer Rom, so I need to change to a supported type using ADB? IT almost looked like the Ext3 format was causing the problem. This also might be a red flag to support if it was not on a factory format. I inherited the phone, so I do not know the history.
Since it never finished booting, is there any way to use the original HTC.exe programs that install the RUU image?
Why are you s-on? Shouldn't you be s-off if you want to install a rom??
Have you tried rooting method again? As far as i know using the gfree method should not give you this issue,
Sent from my Arrows Z using xda app-developers app
Mytouuch 4g - stuck at splash screee
I bought phone from CL. As I suspected previous owner tried to mod the phone. It loads to splash screen. I can get into bootloader but can not select RECOVERY or FACTORY RESET. I tried the PD15IMG.ZIP but when i extracted hboot is 0.89 (and the following happens):
***LOCKED***
GLACIER PVT SHIP S-ON
HBOOT-0.90.0000
MICROP-0429
RADIO-26.13.04.19_M
eMMC-boot
PD15DIAG.ZIP
no image
PD15DIAG.nbh
no image
Main Version is older!
Update Fail!
Press<power> to reboot
I think i need the IMG that pertains to the HBOOT.
HELP PLEASE
Thank you all
Glacier is Stuch at Splash, so what are options after reloading img?
NeuroticallyYou said:
Why are you s-on? Shouldn't you be s-off if you want to install a rom??
Have you tried rooting method again? As far as i know using the gfree method should not give you this issue,
Sent from my Arrows Z using xda app-developers app
Click to expand...
Click to collapse
The phone is stuck at the splash, so what options do I have that load from SD or USB at the 'Stuck' splash or 'Bootloader'? Can I use the HTC EXE programs to reload the phone or do they require a 'fully booted' phone? Is there any way to load the engineered hboot / bootloader so that I can have ADB options?
johnmbailey said:
The phone is stuck at the splash, so what options do I have that load from SD or USB at the 'Stuck' splash or 'Bootloader'? Can I use the HTC EXE programs to reload the phone or do they require a 'fully booted' phone? Is there any way to load the engineered hboot / bootloader so that I can have ADB options?
Click to expand...
Click to collapse
ok let's calm down and not panic, something similar happened to me when i started rooting my first MT4G, did you try to root the phone? if not i will suggest you to do that with the cyanogenmod guide HERE but before you follow the guide try to boot into bootloader by shutting the phone down, leave it off for like 10 seconds then turn it on by pressing the power button+volume down key, you will enter into bootloader usually you will see 3 androis at the bottom of the screen on skateboards if you don't see that but instead the phone keeps booting into splash screen then try again until you enter bootloader, wihle in bootloader you need to tell me what options you get and what options are enabled, since you can't mount the SD card you will have to get an adapter to download all software needed on the SD card(remember you have to remove the sd card from the phone since you can't mount it). Proceed with the guide until you install a custom rom like CyanogenMod 7.
this type of errors can be reproduced easily for example on a rooted phone wipe the phone completely and reboot, the phone will do exactly the same your phone is doing another thing is i don't know what is this HTC.exe program you are talking about everything is done with the android SDK so before doing everything in the guide you need to download and isntall the android SDK.
it seems like the previous person tried to root but instead messed up the phone system, probably corrupted? like i said i have reproduced the same behaviour on my MT4G many times and by now i don't freak out like it was the first time, the thing that have saved me is the rooting guide, i know by experience that you CAN'T install a rom or anything if you are S-ON.
Bootloader options on Glacier Stuck at bootloader
NeuroticallyYou said:
ok let's calm down and not panic, something similar happened to me when i started rooting my first MT4G, did you try to root the phone? if not i will suggest you to do that with the cyanogenmod guide HERE but before you follow the guide try to boot into bootloader by shutting the phone down, leave it off for like 10 seconds then turn it on by pressing the power button+volume down key, you will enter into bootloader usually you will see 3 androis at the bottom of the screen on skateboards if you don't see that but instead the phone keeps booting into splash screen then try again until you enter bootloader, wihle in bootloader you need to tell me what options you get and what options are enabled, since you can't mount the SD card you will have to get an adapter to download all software needed on the SD card(remember you have to remove the sd card from the phone since you can't mount it). Proceed with the guide until you install a custom rom like CyanogenMod 7.
this type of errors can be reproduced easily for example on a rooted phone wipe the phone completely and reboot, the phone will do exactly the same your phone is doing another thing is i don't know what is this HTC.exe program you are talking about everything is done with the android SDK so before doing everything in the guide you need to download and isntall the android SDK.
it seems like the previous person tried to root but instead messed up the phone system, probably corrupted? like i said i have reproduced the same behaviour on my MT4G many times and by now i don't freak out like it was the first time, the thing that have saved me is the rooting guide, i know by experience that you CAN'T install a rom or anything if you are S-ON.
Click to expand...
Click to collapse
The 2.2.1 image does not load due to 'older version' error in the bootloader, so I renamed it so that it would stop at bootloader to test working options.
Glacier pvt ship s-on
HBOOT-0.89.0006
MICROCROP-0429
RADIO-26.13.04.19_M
cMMC-boot
Jul 15 2011, 16:45:17
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Fastboot of course works, as I am able to run the image load from SD card
REcovery works, but give the various mounting errors mentioned earlier
factory reset can be selected but does not change anything and it returns to the splash screen
I did not try simlock, as it looks irrelevant
image crc works and seems to check an image somewhere
When I select RECOVERY, Press UP Volume and Power to get past Triangle, it enters the recovery with all of the mount errors, and then the menu pops up
Androic System Recovery <3e>
Use volume .....
Select w Power....
Reboot System Now
Apply Update from SD card
Wipe data / Factory Reset
Wipe Cache Partition
Wiping DAta completes with Ext3 error, unable to mount anything, and unable to open errors, and returns to Recovery menu
Wiping Cache completes wipe with Ext3 error, unable to mount, unable to open and then reboots
Apply Update from SD Card also appears to fail
Rebooting by reason OEM
Cant mount
Count open
then it reboots
From what screens can you mount the 'drive' to use with ADB? When trying to run the ADB commands, I get the error device not found, so I either am not in the correct mode on the phone or I do not have the correct drivers. When coinnectd at the splash screen, my device manafer shows a Portable Device with Drive f:\ and the details show an Android Phone, but the drive is not visible or accessible by ADB.
When I start bootloader with Hboot at USB PLUG mode, the device manage on my computer changes to Android Bootloader device, but I still get 'Device Not Found' after executing the first ADB command. I then followed the info (I think) at http://forum.xda-developers.com/showthread.php?t=881324 with no success for ADB to work, so I something must be wrong.
It seems the S-ON option is not letting you go further, if it gave you a ext3 format error most likely is because the phone can't erase or rewrite the partition needed. Now I'm no expert on the hardware part but I put my small knowledge on that it have to do with the S-ON part of the phone.
Was the phone booting up properly before? If the phone can't boot to android then you can't use adb commands(for what I know) also the fact you don't have a custom recovery image will make it hard for you reinstall android.
I can probably make some time to help you but nothing is better than having the phone so I can troubleshoot. If you want we can chat on gmail to set up a remote session? Other than that I don't see how I can help you.
Sent from my Arrrows Z using xda app-developers app
FINAL Questions on Recovering Glacier MyTouch 4g stuck at Splash
NeuroticallyYou said:
It seems the S-ON option is not letting you go further, if it gave you a ext3 format error most likely is because the phone can't erase or rewrite the partition needed. Now I'm no expert on the hardware part but I put my small knowledge on that it have to do with the S-ON part of the phone.
Was the phone booting up properly before? If the phone can't boot to android then you can't use adb commands(for what I know) also the fact you don't have a custom recovery image will make it hard for you reinstall android.
I can probably make some time to help you but nothing is better than having the phone so I can troubleshoot. If you want we can chat on gmail to set up a remote session? Other than that I don't see how I can help you.
Sent from my Arrrows Z using xda app-developers app
Click to expand...
Click to collapse
Since the phone will not go pase the splash or bootloader / hboot.....
Questions:
1. Can the original manufacturer RUU - Rom Update Utility be downloaded somewhere and if so wouldn't it just need the phone in Bootloader mode?
2. For the ADB method, will it work with thge phone at the Bootloader screen, and if so what drivers arfe needed as the Android Bootloader ones do not work that are showing. Is these another setting beyond just the driver that needs to be set to use ADB?
3. Will a program like Odin that I used to recover my samsung image from bootloader work for these phones?
4. Does anyone have any ideas or should I just part out this Mint phone?
Please refer to previous posts for the details on what has already been tried....and what it is still doing.
johnmbailey said:
Since the phone will not go pase the splash or bootloader / hboot.....
Questions:
1. Can the original manufacturer RUU - Rom Update Utility be downloaded somewhere and if so wouldn't it just need the phone in Bootloader mode?
2. For the ADB method, will it work with thge phone at the Bootloader screen, and if so what drivers arfe needed as the Android Bootloader ones do not work that are showing. Is these another setting beyond just the driver that needs to be set to use ADB?
3. Will a program like Odin that I used to recover my samsung image from bootloader work for these phones?
4. Does anyone have any ideas or should I just part out this Mint phone?
Please refer to previous posts for the details on what has already been tried....and what it is still doing.
Click to expand...
Click to collapse
I don't know of an external app like odin that works for our phone. Also, there are no RUU's for the Glacier, only PD15IMG.zip files.
Since Mint MyTouch 4g Phone is Bricked, how much will work for Slide Version?
I saw an old post with a broken link for an RUU that was supposed to work on the Glacier called the panache. I finally found a working link and downloaded the RUU for Gingerbread, but when I ran it it gave and error that the battery was below 30%, even though fully charged and verified with my wall charger, and 2 usb chargers and 2 different batteries. I might try a powered USB hub, but this data on battery condition might have been stored on the phone somehow? If it could get the phone to work again, then a I could always reflash with a different ROM later.
If there is no hope of recovering this Mint MyTouch 4g Stuck on the splash screen, so can parts be used on the shift / slide version such as LCD / Digitizer, push buttons, or ????
It makes me sick to tear it apart.....
Any other thoughts?
Ran into similar problem
I ran into a similar problem with a message about the version number of the recovery image being wrong. This was a few weeks ago and I didn't keep a log of exactly how I fixed it but this is what I remember:
It turned out that during an attempt to root before I knew what I was doing I had changed the version number using the guide at the link below.
http://www.androidauthority.com/mytouch-4g-t-mobile-root-custom-recovery-74465/
That error message was misleading and the problem was instead due to the fact the phone was unlocked (although mine did say so on the bootloader screen.) HTC images have apparently been created to require a locked phone to successfully load. I relocked it in Fastboot USB mode with the command "fastboot oem relock" and was able to successfully load any version number after that.
Good luck.
Hello, have you tried using a different SD card?
Sent from my HTC Sensation 4G using xda app-developers app
I'm sure you've had thousands of threads about this and I've probably looked through 90% of them, I've also looked through the Desire troubleshooting to no avail. I believe I have a specific issue. I have a HTC Desire S which, whenever I turn it on, gets stuck on the '3' logo (it's a Three branded phone I believe). I can go into HBoot where I have the options of fastboot, recovery, factory reset, simlock and image crc. Both recovery and factory reset give me the '3' logo screen. Also, I have no idea why it has this boot problem, my brother bought this phone from someone and I'm trying to fix it for him.
Attempted Solutions:
1. I've tried RUU. This goes past the 'Updating Signature' upto 18% where it is "checking MID/CID" which makes the phone boot up (?) and I get the same '3' logo screen for ages.
2. I've tried S-OFF and flashing boot.img, recovery.img, system.img but I get the same screen when I reboot.
3.I noticed hboot looking for a PG88DIAG.ZIP? So I downloaded this, extracted it and put it on a SD card. It boots up into some diagnosis thing where I can run a few tests and write something (mentions something about IMEI). Obviously have no idea what this is for so I'm not messing about with it. It probably is of no use to me.
Basically it seems whatever I do I still get stuck on the boot screen.
Do you guys have any ideas or is it a hardware fault?
Your help is greatly appreciated.
Thank you.
Install abd and fasboot (follow the guide in my signature)
Reboot it to bootloader screen (whre you see RECOVERY/IMAGE CRC, etc options). There should be written "FASTBOOT USB" on the screen when you connect it to PC. If not select the fastboot option from the menu
Type in cmd on the PC while connected in fastboot mode:
Code:
fastboot getvar version-main
Download a RUU that hav the same number like your version in its name (example 2.10.401.8 is for Europe) and run it, while connected in fastboot usb mode
themetcast said:
3.I noticed hboot looking for a PG88DIAG.ZIP
Click to expand...
Click to collapse
edit: sorry, was wrong
What does your bootloader show exactly ?
There are too many things you're doing wrong, while thinking that your issue is "special" - instead of reading more thoroughly and understanding that you're doing just about everything wrong.
1) You're trying to install a wrong RUU. RUU should either match your CID or you should use goldcard - and in any case RUU version number should be same or bigger than your current main version.
2) You're unlocking the phone, since you can't achieve S-OFF without functional ADB. If you're unlocked - your bootloader should read "UNLOCKED" and remain S-ON. In any case fastboot flash system.img will likely fail.
3) You didn't attempt a basic thing - factory reset (can be done using bootloader menu).
But I can already tell that things don't look good for you - if you've successfully unlocked through HTCDev and flashed recovery, the flash went well but you still see the phone stuck on logo when trying to boot into recovery - it means that your eMMC has probably failed, which means your phone is dead.
amidabuddha said:
Install abd and fasboot (follow the guide in my signature)
Reboot it to bootloader screen (whre you see RECOVERY/IMAGE CRC, etc options). There should be written "FASTBOOT USB" on the screen when you connect it to PC. If not select the fastboot option from the menu
Type in cmd on the PC while connected in fastboot mode:
Code:
fastboot getvar version-main
Download a RUU that hav the same number like your version in its name (example 2.10.401.8 is for Europe) and run it, while connected in fastboot usb mode
Click to expand...
Click to collapse
version-main: 2.13.771.4
I've tried RRUs that are above that and below. I've tried H3G, Europe, WWE? Any ideas?
Thank you.
Jack_R1 said:
There are too many things you're doing wrong, while thinking that your issue is "special" - instead of reading more thoroughly and understanding that you're doing just about everything wrong.
1) You're trying to install a wrong RUU. RUU should either match your CID or you should use goldcard - and in any case RUU version number should be same or bigger than your current main version.
2) You're unlocking the phone, since you can't achieve S-OFF without functional ADB. If you're unlocked - your bootloader should read "UNLOCKED" and remain S-ON. In any case fastboot flash system.img will likely fail.
3) You didn't attempt a basic thing - factory reset (can be done using bootloader menu).
But I can already tell that things don't look good for you - if you've successfully unlocked through HTCDev and flashed recovery, the flash went well but you still see the phone stuck on logo when trying to boot into recovery - it means that your eMMC has probably failed, which means your phone is dead.
Click to expand...
Click to collapse
First of all, thank you for taking your time out to reply. Really appreciate it.
1) I'm using a gold card, I'm not sure if I successfully managed to create one? How do I tell once I've plugged it in? Another option for me was to order a 2GB Kingston card just to be sure I have a fully functioning gold card as this unbranded microsd card might not be compatible?
2) Oh yes, you're right! Would S-OFF help me? (even though it's not possible right now).
3) If you read OP I said that the factory reset takes me to the '3' screen.
I believe the phone is pretty much dead so it could be that.
themetcast said:
version-main: 2.13.771.4
I've tried RRUs that are above that and below. I've tried H3G, Europe, WWE? Any ideas?
Click to expand...
Click to collapse
The only availabe that will work for you is RUU_Saga_H3G_UK_1.31.771.1_Radio_20.28b.30.0805U_3 8.03.02.14_M_release
But it needs a change of the main version which is possible only via adb that you do not have.
Actually the ICS RUU should debrand your device but if it failes than JackR1 is most probably right and your chip is gone
themetcast said:
1) I'm using a gold card, I'm not sure if I successfully managed to create one? How do I tell once I've plugged it in? Another option for me was to order a 2GB Kingston card just to be sure I have a fully functioning gold card as this unbranded microsd card might not be compatible?
2) Oh yes, you're right! Would S-OFF help me? (even though it's not possible right now).
3) If you read OP I said that the factory reset takes me to the '3' screen.
I believe the phone is pretty much dead so it could be that.
Click to expand...
Click to collapse
1) If RUU fails CID check - it means goldcard doesn't work. That's pretty much the only check I know. You can try a separate card, or you can try to format your card in PC and make a goldcard again - there are several methods and several tools for the job.
2) It would help you - because it would allow you to flash unsigned PG88IMG.ZIP that you could create with whatever you want as main_version. But you can't achieve it without a functional ADB, which you're not getting to, and even with HTCDev unlock you should still be able to boot into the recovery you're flashing. If it doesn't happen - it means something is bad, and it's most likely the HW.
The suggested method would be to create a good goldcard and run ICS RUU. If it fails - the diagnosis is clear, if it succeeds - you'll either boot or know that the boot fails because of HW failure - but not eMMC, something else.
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.