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!!
Has bought from the USA of HTC Inspite 4g (AT&T). Wanted to receive Root, S-OFF, Rom manager with ClockworkMod. Has started to do to change an insertion. Has received goldcard. After an overload phone has started to change an insertion. This process proceeded 2 hours (in the end of process there was a black screen). I have decided to overload phone. Has stopped process. After that problems have begun. Root, S-OFF, Clockworkmod I have received. But after reboot of phone it does not work about 10 minutes. 5 minutes at it absolutely black screen, then the white screen with an inscription of HTC simultaneously work 3 minutes the motor, loading of 2 minutes then begins. Process of switching-on or reboot of phone proceeds 10 minutes. Tried to replace an insertion once again. After that changes nothing. Did before setting of an insertion full surep wipe. It has not helped. I still have a problem. I want to enter into engineering menu HBOOT. I push down+power. I wait for 5 minutes (phone so is overloaded). I enter in HBOOT, but thus buttons (volume up and down, power) any more do not work. As to me to receive normal phone. I can not HBOOT make in it recovery. Where to me to take for HTC INspire 4G (AT&T) PD98IMG.zip. Also help me with the instruction. How to apply this file in RECOVERY.
I'm having a hard time with your English (or is it just fed into google translate?).
It looks like you installed the ENG hboot on a later model device that is incompatible.
You need to get it to boot (it will eventually) and put the newer hboot back on it. You can do this through ADB from a console. Here are the instructions:
http://paste.pocoo.org/show/495273/
@ Gene Poole
I had a hard time with his English too, but I understand exactly what he is saying because I did the same thing. I will try to re-explain it and hopefully someone can help us out.
In a nutshell, it sounds like we both flashed an Engineering HBoot starting with a stock US ATT Inspire 4G that came with Gingerbread. Specifically, what I did was I followed a guide on Cyanogenmod's wiki for the Inspire 4G which gave direction to downgrade to Froyo, root, and setup to use eng hboot. This apparently was a huge mistake. After the downgrade, when rebooting or powering on the phone, nothing would happen for a long time (black screen for 5 - 10 minutes, i.e. phone was off), then, screen would turn on with white background and HTC logo and phone would vibrate non-stop for several minutes, and eventually, phone would turn on. After the downgrade and making it to the home screen, I copied CM7 zip on to the SD card and rebooted into recovery via adb. Same exact weird process happened with phone being off for several minutes, then vibrating, then eventually i made it to cwm recovery. After installing CM7 and rebooting, same crazy startup process and made it into CM7 home screen.
I was hoping once CM7 was installed that the crazy startup process would disappear but it didn't. I saw afterwards in a CM forum that this happened to someone else and they had asked if the wiki could be updated to point to the Ace hack kit guide to rooting the Inspire 4g (which mentions that eng hboot shouldn't be used with the phone I had as configured). I then rebooted into bootloader via adb and after crazy startup and fastboot did not work at all (fastboot devices returned nothing). Further still, no buttons work in hboot at all (Vol Up, Vol Down, Power).
At this point, I could still get into the phone, but I wanted to try to undo everything I did and start over using the Ace hack kit. I then tried to use the Ace hack kit to unroot the phone by using the ATT GB RUU. The process seemed to go pretty far, but after a reboot, the phone never came back, and that's where I am currently. If I start the phone, it does crazy startup but never fully boots...stays on white HTC screen forever...which means I can't use adb (to my knowledge). I was able to get to hboot by putting elastics around volume down button and waiting a very long time, but it looks like hboot is still the eng hboot because none of the buttons work and I can't use fastboot. I was hoping that as part of RUU flashing that hboot would be restored to original one. I put the RUU (PD98IMG.img) on SD card, but again I can't get to it because buttons don't work.
So, it sounds like spv4 above is in a very similar boat. I have no idea what else to try. Only thing I can think of is if it's possible to somehow modify an RUU to start automatically when getting to hboot without any user input.
If anyone has any suggestions, I am more than willing to try anything. Thanks very much.
EDIT: So, as I was typing this post earlier, I had been "sitting" in hboot the whole time. When I was done, I looked at phone and PD98IMG.zip was been applied to phone automatically! Don't know if this was common knowledge or not, but everything updated OK. When it was done, hitting the power button to reboot didn't work, but I just removed battery and when putting it back in, phone booted normally back to what looks like stock RUU. Hopefully this info helps someone else.
JayB059 said:
@ Gene Poole
EDIT: So, as I was typing this post earlier, I had been "sitting" in hboot the whole time. When I was done, I looked at phone and PD98IMG.zip was been applied to phone automatically! Don't know if this was common knowledge or not, but everything updated OK. When it was done, hitting the power button to reboot didn't work, but I just removed battery and when putting it back in, phone booted normally back to what looks like stock RUU. Hopefully this info helps someone else.
Click to expand...
Click to collapse
Great! Glad you got it back, but you could have saved a lot of time.
The main problem is that the ENG hboot (or pre-GB hboots) doesn't recognize something in the hardware of the new phones. The end result is that the hboot runs at about 50x slower. It eventually gets booted, and once booted to an OS (either the main OS or the recovery OS) it runs fine since hboot has exited and passed control to the OS. So anytime hboot is in control, things crawl at a snail's pace.
Because the OS runs fine and hboot has exited, it is possible to overwrite the hboot partition from the booted OS. That's what you are doing in the instructions that I posted a few posts back. Once the correct hboot is installed, all is fine.
I agree that someone needs to update the cyanogenmod wiki. It's way out of date.
I'm currently experiencing the same problem.
I followed the instructions on how to downgrade using a goldcard, successfully rooted and i also flashed TrickDroid on it, but every time i turn the device on i have to hold the power button for 20 seconds and wait 10 minutes till the HTC logo appears, then it takes 2 minutes vibrating and i seriously can't deal with this.
can you please tell me how to fix this?
Revolver95 said:
I'm currently experiencing the same problem.
I followed the instructions on how to downgrade using a goldcard, successfully rooted and i also flashed TrickDroid on it, but every time i turn the device on i have to hold the power button for 20 seconds and wait 10 minutes till the HTC logo appears, then it takes 2 minutes vibrating and i seriously can't deal with this.
can you please tell me how to fix this?
Click to expand...
Click to collapse
Find the fix in the guide in my signature....you need to have basic knowledge of adb commands. If you need further help just let me know. :good:
Moved to Q & A section.
Sent from my Galaxy Nexus using Tapatalk 2
edit
I had the hTC EVO Design 4G as pretty much my first Smart Android. (Im not including the LG optimus M). The Switched to the Galaxy note & S3 for a while NOw Im using the HTC one S. I normally never have these problems or ever post on the forums. But Im desperate for fast help. I know how to do everything on both the htc evo 4g and design.
but The Ville is diff. without the removable battery
im blabbering....
let me try to STEPbySTEP explain my steps up to my not working Device.
!. I tried to Flash the Energy_9.07.2012.OneS.zip rom through TWRP at first. (thats was the suggesttion in the thread. So that the recovery would Flash the correct Kernel. But upon reboot. I discovered that contrary to the devs suggestion the WiFi still didnt work. So I flashed CWM through ROM manager. reboot into recovery flash wiped cache/ factory reset. But I dont think I wiped system, data, or anything not in the main Menu, Energy_9.07.2012.OneS.zip and I reboot. Upon reboot the HTC screen had the warning for use in htc do not distribute...then the bootanimation popped up and finally the booted up fine. Wifi was working this time. But now my network wasnt right. I didnt give the rom time to settle in though. I panic and open CMD and ran adb reboot fastboot.
Waited waited
now the boot loader was up. I had to unplug my deviice for the screen to show fastboot usb.
then this is where I think I ****ed up my phone
(I extracted the boot.img from the Energy_9.07.2012.OneS.zip and placed it in my android folder on C I also adb pulled my twrp recovery to
C:\android and renamed to recovery,img I wanted TWRP back I hate how CWM automaticaly boots when you plug it in tp charge from dead)
Now I had in my C:\Android\boot.img and \recovery.img.
I ran the command (im not sure if I ran boot or recovery first)Also my phone was anywhere near a full battery cloase to dead but my CMD window showed complete.
C:\Windows\system32>fastboot flash boot C:\android\boot.img
C:\Windows\system32>fastboot flash recovery C:\android\recovery.img
Now my phone is plugged into my Lenovo Thinkpad t410 with Win7 Pro OEM The red light to the top right isnt blinking like the battery to low to power on notification. Its steady. but when I hold down to turn on either the lights for the capacitie buttons flash untill I let go of the button or I do a combo of plugging in and out the usb and holding the power and volume bottons not sure Which order. PLEASE HELP! iM EXPECTING A PHONE CALL ABOUT A JOB INTERVIEW RESULTS.
In my time in CMD this error did pop up a few times. But I open HTC sync let it load. and then it would work.
C:\Windows\system32>adb reboot device
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Would A ruu fix this????? Although I haven't once successively used one.
COMMENT, PM, IM, ME I DON'T CARE JUST PLEASE HELP ME AN MY POOR [PHONE] GUARANTEED THANKS BUTTON!!!!!!! USAGE AS FOR HELPING.
why would you flash something made for HTC ONE S if you have HTC EVO
especially when you're just starting to learn about
sorry, but I would guess that you're chance is to find somewhere a ruu for your model
ultimul said:
why would you flash something made for HTC ONE S if you have HTC EVO
especially when you're just starting to learn about
sorry, but I would guess that you're chance is to find somewhere a ruu for your model
Click to expand...
Click to collapse
I have the HTC One S Ville
I was stating how I use to have the evo
gisaac2157 said:
I had the hTC EVO Design 4G as pretty much my first Smart Android. (Im not including the LG optimus M). There is no development forum for that devices in XDA so I used SDX-DEV I actually started learning how to kang my own roms.
im blabbering....
let me try to STEPbySTEP explain my steps up to my not working Device.
!. I tried to Flash the Energy_9.07.2012.OneS.zip rom through TWRP at first. (thats was the suggesttion in the thread. So that the recovery would Flash the correct Kernel. But upon reboot. I discovered that contrary to the devs suggestion the WiFi still didnt work. So I flashed CWM through ROM manager. reboot into recovery flash wiped cache/ factory reset. But I dont think I wiped system, data, or anything not in the main Menu, Energy_9.07.2012.OneS.zip and I reboot. Upon reboot the HTC screen had the warning for use in htc do not distribute...then the bootanimation popped up and finally the booted up fine. Wifi was working this time. But now my network wasnt right. I didnt give the rom time to settle in though. I panic and open CMD and ran adb reboot fastboot.
Waited waited
now the boot loader was up. I had to unplug my deviice for the screen to show fastboot usb.
then this is where I think I ****ed up my phone
(I extracted the boot.img from the Energy_9.07.2012.OneS.zip and placed it in my android folder on C I also adb pulled my twrp recovery to
C:\android and renamed to recovery,img I wanted TWRP back I hate how CWM automaticaly boots when you plug it in tp charge from dead)
Now I had in my C:\Android\boot.img and \recovery.img.
I ran the command (im not sure if I ran boot or recovery first)Also my phone was anywhere near a full battery cloase to dead but my CMD window showed complete.
C:\Windows\system32>fastboot flash boot C:\android\boot.img
C:\Windows\system32>fastboot flash recovery C:\android\recovery.img
Now my phone is plugged into my Lenovo Thinkpad t410 with Win7 Pro OEM The red light to the top right isnt blinking like the battery to low to power on notification. Its steady. but when I hold down to turn on either the lights for the capacitie buttons flash untill I let go of the button or I do a combo of plugging in and out the usb and holding the power and volume bottons not sure Which order. PLEASE HELP! iM EXPECTING A PHONE CALL ABOUT A JOB INTERVIEW RESULTS.
In my time in CMD this error did pop up a few times. But I open HTC sync let it load. and then it would work.
C:\Windows\system32>adb reboot device
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Would A ruu fix this????? Although I haven't once successively used one.
COMMENT, PM, IM, ME I DON'T CARE JUST PLEASE HELP ME AN MY POOR [PHONE] GUARANTEED THANKS BUTTON!!!!!!! USAGE AS FOR HELPING.
Click to expand...
Click to collapse
If you hold down the power button long enough the leds should stop flashing. You should try that and then once it goes off, hold down the volume down and the power button.
That should get you back into bootloader. From there you may want to try flashing a custom kernel (the SENSE version of Fusion, for example).
An RUU could help, but you would need to relock your bootloader in order to flash it. You would need to be able to get to your bootloader screen. RUUs are EXE files and are pretty self explanatory when you run them and have your phone connected. See http://www.4shared.com/folder/jKN2qjTl/HTC_Ville_RUU_Collection.html for RUUs. There is also a thread on RUUs in the development thread. Read that too.
But first things first, you need to be able to access your bootloader! Keep fiddling with your power button and volume down button.
AKToronto
gisaac2157 said:
I have the HTC One S Ville
I was stating how I use to have the evo
Click to expand...
Click to collapse
can you reboot into recovery/fastboot? press the power button for 5-7 seconds until the keys start blinking;
the phone should reset after it
some RUU, you can find here:
http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Thanks so much.
AKToronto said:
If you hold down the power button long enough the leds should stop flashing. You should try that and then once it goes off, hold down the volume down and the power button.
That should get you back into bootloader. From there you may want to try flashing a custom kernel (the SENSE version of Fusion, for example).
An RUU could help, but you would need to relock your bootloader in order to flash it. You would need to be able to get to your bootloader screen. RUUs are EXE files and are pretty self explanatory when you run them and have your phone connected. See <font color="red"> as a new member cant post links</font> for RUUs. There is also a thread on RUUs in the development thread. Read that too.
But first things first, you need to be able to access your bootloader! Keep fiddling with your power button and volume down button.
AKToronto
Click to expand...
Click to collapse
I feel really stupid for not knowing THAT. Now whats up with the energy rom? the thread says stable. How am I suppose to flash it?
First off: I have an AT&T HTC one X
I am an almost total noob when it comes to this stuff so please bear with me here.
I had my roommate put cyanogenmod onto my phone when I got it and all was well until I moved to Asia and got an unlock code from AT&T to be able to use it over here. The unlock code wouldn't work and I found some stuff online saying that it might be a problem with cyanogenmod.
I followed a youtube instruction guide on how to get rid of the mod and everything was going fine until right at the end when I got a windows notification that the RUU had stopped working. I figured I would just do it again, but the actual program itself said it was successful. As I waited for it to reboot and load the roms, it started a loop. The loop is the white screen with the green htc letters for a few seconds and then it goes to a black screen with a phone logo in the middle. Around the phone logo is what looks like a recycling symbol except circular instead of triangular and on the screen portion of the phone logo there is an arrow facing down.
I assume this is just telling me I need to actually download some software on the phone, but it won't connect via USB and every time it starts up it says that the drivers were not successfully installed and htc sync manager doesn't recognize that a device is even connected. The loop continued and i tried to boot it back into the fastloader which did nothing. I held down the buttons as if to boot it into fastloader, but this time for about 15 seconds which took me to a battery charging screen and finally ended the loop.
I assume(hope) that since it's actually responding to input from the buttons that it's not irreversibly bricked. Is there any way I can get some version of android back on this thing? Any help would be much appreciated
Are you able to get the phone into the bootloader?
To boot into the bootloader there are two methods.
With phone powered on
Hold the volume down button, then hold the power button (so you're holding both buttons together), the button lights will start to flash, they will stop flashing and the screen will go blank, after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
With phone powered off
Hold the volume down button, then hold the power button (so you're holding both buttons together), after a couple of seconds let go of the power button but continue to hold the volume down button until you reach the white screen with text, this is your bootloader.
Please post the first five lines. Also, exactly which RUU did you try to use?
Sent from my Evita
Happened to me as well..I reran ruu and then flashed a custom recovery. That symbol of charging with that arrow scared me. Lol
Yeah I was the friend that helped tpank unlock and put cyanogenmod on. I'm just too noob to help him halfway across the world get his phone back to stock
Swilli89 said:
Yeah I was the friend that helped tpank unlock and put cyanogenmod on. I'm just too noob to help him halfway across the world get his phone back to stock
Click to expand...
Click to collapse
This is why people should be learning to do things themselves. Now you've put him in a situation where he doesn't know what he's doing, very dangerous on a modified device with root access.
Sent from my Evita
the RUU i tried was the update from the htc site "HTC One X for AT&T Software Upgrade 1.29.2014"
the first five lines that appear on the phone are
*** RELOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.18.0000
RADIO-1.35A.32.45.27
OpenDSP-v33.1.0.45.1128
also my computer doesn't recognize my phone is even plugged in at this point
Before you attempt to run the RUU again it's very important that we find out what your current CID is, if it's still SuperCID and you run the RUU you could brick your phone. To do this you're gonna need to have a working connection between your phone and your PC, so you'll need to make sure you have drivers installed, and you'll also need to have adb/fastboot installed. Do you have any drivers currently installed? If so, how did you install them?
Sent from my Evita
i have the RUU that I showed you and I just installed another RUU on my computer: RUU_M7_UL_JB43_SENSE50_MR_CINGULAR_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed.2.exe but I haven't done anything with that yet. The only drivers I would have on my phone might be the ones from the original RUU I downloaded and ran which got me into this mess in the first palce, but I dont even know if they're on the phone since it's in its current state. I have adb and fastboot from downloading the android sdk slim pack. I also have HTC sync, but I'm not sure how that fits into the equation
tpankfashank said:
i have the RUU that I showed you and I just installed another RUU on my computer: RUU_M7_UL_JB43_SENSE50_MR_CINGULAR_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed.2.exe but I haven't done anything with that yet. The only drivers I would have on my phone might be the ones from the original RUU I downloaded and ran which got me into this mess in the first palce, but I dont even know if they're on the phone since it's in its current state. I have adb and fastboot from downloading the android sdk slim pack. I also have HTC sync, but I'm not sure how that fits into the equation
Click to expand...
Click to collapse
Whoa. Whoa, whoa, whoa. Where on earth did you get that RUU? It isn't even for this device. Delete it now.
Drivers don't go on your phone, they're on your PC. HTC Sync Manager fits into the equation because it's the best way to get the drivers installed on your PC.
Uninstall HTC Sync Manager and the drivers that should be in the same sub-menu in the start bar on your PC. Uninstall any other phone software you might have on your PC.
Install HTC Sync Manager again, put your phone in fastboot mode, connect your phone to your PC, drivers should begin to auto-install.
Navigate to where you have adb.exe and fastboot.exe on your PC (we'll call this your fastboot folder). Shift + right click anywhere within that folder, select open command prompt here, issue the following command:
Code:
fastboot oem readcid
Please post the result.
Before we go any further, I need to be brutally honest with you. Once you have successfully run the correct RUU, which will return the phone to a stock configuration, leave it stock. Judging from your couple of posts here you're on a collision course to bricking your phone. You just don't seen to posses the slightest idea of what you're doing, couple that with owning a modified device, and the results are almost always disastrous. I'm not saying this to be cruel, I'm saying this because I'd hate to see you brick your device. The only way it's safe to have a modified device is if you're willing to put in the hard work of researching (days/weeks/months/years), and continuing to research to stay on top of this ever changing game.
Sent from my Evita
ok i attempted all of this, but nothing happens because my computer won't even recognize that my phone is plugged in. So htc sync manager is telling me to connect a device and the command prompt just says <waiting for device> when I type in the command to figure out the CID.
Also, I take no offense from your warning. I wasn't going to try to mess with it any more after I got my the stock OS and my phone unlocked for asian networks. I really appreciate all the help
tpankfashank said:
ok i attempted all of this, but nothing happens because my computer won't even recognize that my phone is plugged in. So htc sync manager is telling me to connect a device and the command prompt just says when I type in the command to figure out the CID.
Also, I take no offense from your warning. I wasn't going to try to mess with it any more after I got my the stock OS and my phone unlocked for asian networks. I really appreciate all the help
Click to expand...
Click to collapse
There's no point in attempting any fastboot command until you can get the PC to recognise the device. Are you using a usb 2.0 port, and the original HTC usb cable? What does it say on the screen of your phone when you connect it while it's in the bootloader? It should say fastboot, fastboot usb, or fastboot ac.
Sent from my Evita
timmaaa said:
There's no point in attempting any fastboot command until you can get the PC to recognise the device. Are you using a usb 2.0 port, and the original HTC usb cable? What does it say on the screen of your phone when you connect it while it's in the bootloader? It should say fastboot, fastboot usb, or fastboot ac.
Sent from my Evita
Click to expand...
Click to collapse
Tpank, use the snipping tool on your computer to post a screen capture of your fastboot adb folder. its the folder that you are running the command prompt from (or should be).
BTW thanks Timaaaaa for helping my friend out. When I unlocked his phone we didn't know he would have the opportunity to move out of the US to Thailand so I figured I would be around to help with something like this. Thanks again.
Why would we need a screenshot of the fastboot folder?
Sent from my Evita
These guys are on a collision course. ?
timmaaa said:
There's no point in attempting any fastboot command until you can get the PC to recognise the device. Are you using a usb 2.0 port, and the original HTC usb cable? What does it say on the screen of your phone when you connect it while it's in the bootloader? It should say fastboot, fastboot usb, or fastboot ac.
Sent from my Evita
Click to expand...
Click to collapse
ok so it says "Fastboot usb". I am using the original htc usb cable. I'm not sure if it's a usd 2.0 port all I know is that it's an Intel 6 Series/C200 Series.
When I ran the command prompt it says:
<bootloader> cid: 11111111
OKAY [ 0.017s]
Ok, so you have a working fastboot connection now, right? The problem you face at the moment is that you can't run an RUU with your phone in the current configuration. S-on + SuperCID + jb RUU = brick. Your only real option at this stage is to do this:
-Unlock the bootloader at htcdev.
-Flash TWRP recovery.
-Flash a ROM to get the phone booting.
-Get s-off via Facepalm S-off.
-Run the correct at&t RUU to return the device to stock
-Change the CID back to the at&t CID.
-Relock the bootloader.
-Go back to s-on.
That probably seems like a lot of work but it's the only way for you to proceed. I have detailed instructions for several of those procedures in the How-To Guide For Beginners thread in my signature.
Sent from my Evita
So I can;t get past the first step because it's not recognizing my phone still. When I ran the first command in the command prompt, where it should have listed my phone it says "List of connected devices" and nothing underneath it.
How did you get the CID?
Sent from my Evita
I'm not sure why I can find the CID and not get it listed as an attached device. I tried to run the adb devices command a few times and then ran the fastboot oem readcid command in the same window and I could get the cid but still cant get it to recognize the device
Are you attempting adb commands while the device is in fastboot mode? They won't work, only fastboot commands will work there, adb commands work while the phone is booted into the OS. Use "fastboot devices" while in fastboot mode.
Sent from my Evita