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.
hi,
Ive recently rooted my phone with no problems using the ace hack kit. i tried flashing the newest andriod revolution hd rom and was having problems with the superuser app force closing and the phone wasnt giving me root privledges. i decided to try and reroot the phone using the ace hack kit. (i realize this was my mistake). it stopped in the middle of the process. so i had to pull the battery. when i tried turning the phone back on the screen was black for about 6 or 7 mins. no vibrations or leds to indicate the phone was on. then the htc white screen comes on and the phone vibrates for 2 or 3 minutes straight and proceeds to come on. Ive tried to flash other roms using cwm recovery and itll load what ever rom i choose but i cant get into the hboot or anything and it does the the black screen everytime along with the vibration. is there anyway to fix this? ive tried over and over to boot into recovery through usb but it doesnt work.
so ive done a little research, could this be a eMMC problem? if so is it fixable... And if not would replacing the hboot help?
You've got a bad or corrupt hboot. The wrong hboot (ENG hboot included in a short-lived version of the hack kit on the newest run of Inspires) or a corrupt hboot from an interrupted hack kit run.
Thanks for the help. I tried replacing the eng hboot with the link provided on freenode and it work.
After a failed attempt at running the ace hack kit (could only get into hboot), and an ever worse failed attempt at restoring to a stock rom (my stupid mistake), I am seeing the same signature as jbryancs.
Would you share the link and instructions for replacing the hboot? Any assistance is much appreciated.
wleven said:
After a failed attempt at running the ace hack kit (could only get into hboot), and an ever worse failed attempt at restoring to a stock rom (my stupid mistake), I am seeing the same signature as jbryancs.
Would you share the link and instructions for replacing the hboot? Any assistance is much appreciated.
Click to expand...
Click to collapse
really? so jumping into the IRC channel is not your best move as instructed to the OP?
I was hoping not to disturb the IRC, but I will jump in tomorrow. Just for background, here's a rough list of what I've done and what I'm seeing now.
Setup: Linux Mint 11 (Ubuntu Derivative) Clean Install for ACE Hack Kit, WinXP for the rest.
1. Ran ACE Hack Kit first time -> stalled early in process
2. Rebooted phone and everything appeared normal
3. Rac ACE Hack Kit second time -> completed process, but noticed some errors/warnings along the way
4. Rebooted phone and it would be stuck at the white HTC logo screen
5. Rebooted to hboot, but none of the options there would restore the phone.
6. Downloaded original ACE firmware and copied ZIP to SD card. It recognized this and performed install, in all appearances successfully until the reboot.
7. On reboot, the phone appeared completely dead. Later discovered that it would spring to life after ~7mins, vibrate 2-3 min, and then boot into Froyo
Phase II
1. Downloaded gingerbread RUU from HTC and ran it. Gets stuck on "Waiting for bootloader"
2. Thought perhaps hboot was corrupted, so ran instructions here "wiki.cyanogenmod.com/wiki/HTC_Ace:_Rooting_%26_CyanogenMod" to install hboot-eng and clockworkmod
3. This did not fix the booting (still wait 7mins, vibrate 2-3), but I do have root now, as verified through su root on the phone's terminal console.
4. Tried the RUU again, stuck on "Waiting for bootloader"
5. Noticed that if I had the phone USB connected to the PC when power cycling, it would come to a black HTC screen after about 7mins. In this mode, the phone seems to connect in Android bootloader interface.
6. Tried the RUU again, and this time it makes it past "Waiting for bootloader", but hangs (no error message) on "Sending". I've left it for nearly an hour with no change -- just keeps showing the black HTC screen.
I still can't get the phone into HBOOT (using the volume down + power method).
Hello,
Could someone tell me if there's an enclosure or a solution to this problem?
I've searched a few forums, and it appear to me that the conclusion is the old (ENG) HBOOT is incompatible with newer hardware.
Thanks.
hchao said:
Hello,
Could someone tell me if there's an enclosure or a solution to this problem?
I've searched a few forums, and it appear to me that the conclusion is the old (ENG) HBOOT is incompatible with newer hardware.
Thanks.
Click to expand...
Click to collapse
You will have to flash the original RUU again and then try to root the cell with the Hack Kit. You can find the original RUU in the general section or go to the htc site and just run the .exe update from fastboot. Let your cell reboot (it will take about 30 minutes) and then flash it.
jbryancs said:
hi,
Ive recently rooted my phone with no problems using the ace hack kit. i tried flashing the newest andriod revolution hd rom and was having problems with the superuser app force closing and the phone wasnt giving me root privledges. i decided to try and reroot the phone using the ace hack kit. (i realize this was my mistake). it stopped in the middle of the process. so i had to pull the battery. when i tried turning the phone back on the screen was black for about 6 or 7 mins. no vibrations or leds to indicate the phone was on. then the htc white screen comes on and the phone vibrates for 2 or 3 minutes straight and proceeds to come on. Ive tried to flash other roms using cwm recovery and itll load what ever rom i choose but i cant get into the hboot or anything and it does the the black screen everytime along with the vibration. is there anyway to fix this? ive tried over and over to boot into recovery through usb but it doesnt work.
so ive done a little research, could this be a eMMC problem? if so is it fixable... And if not would replacing the hboot help?
Click to expand...
Click to collapse
I am having this same problem I have searched and searched and this post was the only one that had the same issue could someone please help me out on this and post the fix. Thanks
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Edit: Problem fixed. Downloaded the original all in 1 tool for htc one s, plugged phone into comp went to fastboot and with the tool flashed the phones stock recovery. I reset to factory defaults and cleared storage with it from the bootloader. After that, I flashed clockwork mod recovery again and my SD card was able to be mounted and accepted files from my adb push, and I reflashed cyanogenmod. Wuzzah!
milesmarrero said:
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Click to expand...
Click to collapse
lol, meant to "quote" not "thanks".
Can you fastboot a new recovery?
Did you do a full wipe coming from CM9 to TrickDroid
Well I can't access the phone from usb on my computer (still takes charge though), so I don't think I can flash a recovery thru fastboot (I'm not too experienced though). From cm9, I wiped all and flashed trickdroid + tweak set, then it just stat their at home screen. CMW being lost occurred later.
Im in the same situation rght now. I have trickdroid and I went into my tweaks to set them back to their original setup...so removing all of the options I chose before when I used the tweaks for the first time. When I rebooted my phone it just hangs on the HTC screen. I can get into recovery and I tried reinstalling trickdroid but its still getting stuck. Not sure what to do at this point. I don't think I can put a recovery file on this since I can't connect it to my computer.
Hopefully someone can help us.
But the thing is I can't access recovery. I try to flash it again with the all in 1 tool and it won't work. It says it went through, but accessing it doesn't work.
If its recognised by USB when plugged in computer just run an ruu that's my solution all The time lol
Sent from my HTC One S using xda premium
Ok i somehow managed to get TWR on my phone, but still unable to mount the SD. How do I run the RUU? I downloaded it, but the instructions are flawed I think
Connect with USB to.computer go into faatboot USB then run ruu on pc
Sent from my HTC One S using xda premium
Well I thought the RUU was going to work, but it just stops at the HTC and gives me an error saying I can't. What now?
Ok currently, I relocked my bootloader in an attempt to do the RUU, but I get a 155 Unknown Error up doing such, using the TMOUS 1.53 ruu... other places I have seen say something about returning to the stock img etc, but I'm quite stuck. Any advice appreciated
htc one s stuck in bootloop almost unresponsive
hey guys, got a brain teaser for you.
i have a tmobile htc one s, unlocked, rooted using all in one htc tool, been at it for two days now. im stuck on the boot screen showing its unlocked, i used to be able to get into the boot loader screen but now it seems ive dead ended. ill hold any combination of power and vol up/down, the keys flash for 10 sec and the screen flashes once, i let go and it reboots, keeps that htc screen, after 20-30 sec goes black. my pc doings like it detects a device but i cant locate it. ive used adb and the htc all in one unlock tool trying to get any kind of os to launch.
Shortly before this i was able to go into the boot loader, clear and master reset the files and cache, and search for the rom zip, thus never allowing me to flash. on a journey to place this in the phone through various combinations of the all in one, adb push, and everything else i found on youtube, countless forum posts, i seem to be in a deeper hole now.
I ultimately want to end with a cm10 nightly on my tmo htc one s. I have never done this to a phone without a sd card. i come to this community humbly seeking any and all advice. thank you.
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
Novice here.
Ran the All-in-One utility today and after the CWM installed I hit "Perm root" without reading the thing below telling me to boot to recovery first. It's now stuck in boot loop. Everything went off fine up until the Perm root. Even that said successful and then restarted. Only after the process was completed did the recovery loop begin. No HTC logo loop. Just reboots into CWM over and over no matter what technique I use (except for opening the case).
I've read this: http://forum.xda-developers.com/showthread.php?t=1599363
And am trying to install ADB to push ANY possible ROM over to the SD card. My recovery allows the toggle of /mount sdcard and /mount system, however adb fastboot push doesn't work. "error: device not found"
And I can't do this: http://forum.xda-developers.com/showthread.php?t=1644730 because my phone is stuck in the recovery loop. If I try volume down + power, it just comes back to recovery screen. I've tried factory reset, I've tried wiping cache, I've tried wiping Dalvik, and still nothing. I did flash the SuperSu.zip after I had used the Perm Root button on Haroon2000's app.
I'm incredibly flustered as I've rooted devices for years and this is my first problem. I've seen similar complaints all with ideas of breaking into the phone and unplugging it's battery so I can get to the bootloader etc, but I'm so very confused. So many posts telling me to do so many things.
Can someone please help break down a tangible solution here? I'm freaking out.
Cheers
EDIT: If someone can get my phone fixed, I'll Paypal them $50 USD. I really need my phone back ASAP :\
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
beats4x said:
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
nik.the said:
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
Click to expand...
Click to collapse
Okay, update.
I was able to get ADB working and detect my phone.
Next, I was able to push Venom Rom to phone. I factory reset, wiped cache, wiped Dalvik, and was able to install Venom.zip. It then asked to reboot (per Venom screen) and I said okay. It then returned to CWM Recovery. I was confused but left everything as is. I have now reset the phone by holding the power button for around 10 seconds. It then restarted to the HTC Quietly Brilliant screen. I have been looking at that screen for about 5 minutes.
Also pertinent: I did try to run the RUU, but it didn't connect through USB. (I forget what it said verbatim). So that didn't work. I also was able prior to this entire process get into the bootloader via dumb luck.
Any suggestions? I am staring at the HTC boot screen still. Do I try to restart and enter bootloader? If so, then what? It seems there is something wrong with CWM. Can I switch recoveries? Can I uninstall it?
Calm down we have all been there,
When you flashed venom did you flash the boot image? Also i use twrp instead of cwm i find twrp better .
To enter bootloader hold power button and down vol together .
As gazknight said, this seems like proper kernel not being flashed or having an issue. If you flashed the boot.img with fastboot, try again erasing cache from fastboot first. The commands are as follow:
fastboot erase cache
fastboot flash boot boot.img (where this boot.img is the one inside the zip from the rom you choose and must be left in the same folder than fastboot)
It happened to me a couple times when i was on hboot 1.14 that I had to flash the boot.img a second time sometimes, somehow it was not working the first time, randomly, even though the flash had completed ok on fastboot.
If still doesn't work try doing a factory reset from TWRP and flashing ViperOneS again.
If that still doesn't work, you might want to try another rom, like TrickDroid, you would then have to flash the boot.img from this other room with fastboot, remember that.
Try and let us know
Hold down volume down while you're trying to boot, that will get you in boot loader, go to fast boot by pressing the power key, connect your phone to your computer, run the flash viper boot img thingy and you're set!
Envoyé depuis mon HTC One S avec Tapatalk
Same issue with HTC One S bricked but in European version, Stock ROM
hello,
I did't want to start a new topic, as I'm experiencing a similar issue with my HOS. Briefly, yesterday morning I plug the phone from charger at 06.00 am. Play with it for a while and then go to work. Used it at work for a few phone calls until 10.00 am (so 4 hours on fully charge battery). Then at 10.00 am I went into a meeting and left the phone out of my sight for 20-30 minutes. When I came back from the meeting I realize that the phone was closed. I try to open it (power button) but nothing. Press power for 10-30 seconds with volume down - still no effect.
Then I took the charger (the original one that I always use to cherge it) and plug it, left it for 2-3 minutes and press power. The phone starts but all I have is the white screen with HTC logo and if I press the power button + volume down the phone goes into bootloader. That's all I can do with it for now.
I have stock rom, bootloader is locked and I never try to root the phone. Is it any chance to repair it by myself or I have to sent it to the repair shop.
many thanks in advance.
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
nik.the said:
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
Click to expand...
Click to collapse
You might need to do it as administrator.
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
nik.the said:
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
Click to expand...
Click to collapse
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Darknites said:
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Click to expand...
Click to collapse
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Yeah! Fixed!
After enough toggling, I changed the recovery to the T one and relocked my bootloader. It turns out detecting the device wasn't necessary somehow. Then I ran the RUU and voila!
nik.the said:
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Click to expand...
Click to collapse
Not sure whats up with that, never had any issue on win7.
Windows 8 fastboot works on my laptop for some reason. I installed the drivers from the HTC Sync folder.
Sent from my HTC One S using Tapatalk 2