Ok so heres the deal. I have an HTC Evo 3D from Rogers in Canada and I had an unlocked bootloader and S-OFF (currently (re)locked and S-OFF). I was running the stock Rogers Rom but with CWM recovery. Yesterday I downloaded the new OTA update for android 4.0 with sense 3.6 and of coarse I found out that custom recoveries won't flash stock HTC zips, and I wanted this new update. So I downloaded the official stock RUU and tried to reflash to a "true stock" form so I could update the phoen. First error I encountered when trying to use the RUU was "error 131 Customer ID error", which I found out was a problem with the CID of the phone (don't know how it was changed). Tried setting the CID to ROGER001, which is supposedly the default CID, but the RUU still would still get the CID error. So I changed the CID to 11111111 (superCID) through fastboot and tried the RUU again. It worked this time but now I'm stuck at the HTC sceen and the phone will not boot.
I have tried manually flashing the boot.img from the RUU through fastboot. Also since I'm still S-OFF and i tried reflashing CWM recovery and tried flashing an assortment of ROMs including the backup of the stock ROM that I was just on and NO rom would boot. Roms with custom boot animations would get past the HTC logo but then just sit loading forever but never actually finish booting. Also tried flashing the RUU via the bootloader by renaming the rom.zip to PG86IMG.zip and still nothing. I still have access to the bootloader and fastboot and recovery. RUU flash completes everytime I try it but never boots, and nobody seems to have had the same problem as me after using an RUU.
I am at a complete loss for what to try next and really need help.
Hboot of my phone is 1.49.08
SOLVED
Finally got the phone working again today. Looks like the RUU I was using may have been corrupt and wasn't playing nice with the ROGER001 CID. Finally was able to sucessfully download the 3.28 RUU and tried loading that after changing the CID back to ROGER001 and BAM! phone booted up after that. Crappy thing was I thought it was dead for good so I ended up going out and buying the new Galaxy S III for $650+tax :laugh:. Oh well the GS3 is a better phone anyways haha.
Point is my original problem is now solved so mods can delete this or move it or whatever.
Hey people,
since HTC released their new update I tried to install it on my device.
Unfortunately my phone doesn't boot anymore.
So I'm stuck at the "HTC"- welcome (boot) screen.
Some specs about my phone:
HTC EVO 3d - X515m >GSM<
HBOOT 1.49.0018
S-On with HTC unlocked.
4EXT Recovery (CWM didn't work)
-Updated with the Systemupdate.
Greetings
You have to relock your bootloader and use an ruu to go back to stock before you can take the official OTA.
I've went back to stock (Relocked) and I have not found a method to flash to the new ICS. This phone is not on the Sprint network.
Any solutions other than S-OFF?
I just rooted my mother's phone and was going to flash a custom ROM, when she took the OTA and ended in the same result, locked at htc boot screen. I relocked the phone via fastboot and flashed a stock gingerbread rom via USB to get the phone running again. I'm now taking the OTA update of ICS for her. I'll try to unlock her on the other side.
Thanks,
I figured it out.
The needed to upgrade to ICS final is to "Relock" then take the OTA after connecting to the Internet..
I used WiFi for the download.
Dogpack said:
I just rooted my mother's phone and was going to flash a custom ROM, when she took the OTA and ended in the same result, locked at htc boot screen. I relocked the phone via fastboot and flashed a stock gingerbread rom via USB to get the phone running again. I'm now taking the OTA update of ICS for her. I'll try to unlock her on the other side.
Click to expand...
Click to collapse
Hello,
Right, I am aware that I've probably made a huge mistake, but I thought, "hey, warranty void because of my screen, why not?", but I have searched and searched and was up until three this morning trying to find a solution, but I only kept getting confused (bare in mind I'm only sixteen).
I rooted my phone using the HTCDev method, and flashed the LoLic Sense ROM, it worked and I turned my phone back on and it got stuck on the bootscreen. So, I downloaded the RUU and tried to go back to stock, and it kept failing. I even tried the PG86IMG.zip and even that didn't work. So, I downgraded to the LEEDroid ROM that came with the revolutionary package I'd used before the official update to ICS, and now I can't even get past the initial HTC screen.
Please can anybody help me get back to stock on my phone? I've managed it before, but this time I keep seeming to come up short.
Thank you
EDIT:
I'm on HBOOT 1.53.0007 - after updating to the official ICS.
I've tried downgrading using the Gingerbread RUU and it won't install on the phone. I can't S-OFF using the wire trick because I'm afraid to break it even more.
I've tried flashing the rooted GB zip in clockworkmod and it says its installed, but I can't turn the phone on and it only gets to the first white HTC screen and then turns itself off.
I'm terrified that I may have broken my only phone and I don't know what to do, please can somebody help me?
If you are S-ON HTC Dev unlocked you need 4ext with smartflash or fastboot flash boot boot.img to install the kernel.
Alright I will try to recap what ive done today. I Was rooted with s-off via the thunderbolt tool and had the new ICS rom installed and running fine. But I decided to sell it so I used the thunderbolt tool to unroot and return to stock.
All was going well then in the boot-loader the update failed and i got stuck with boot-loader locked security warning, which would not let me do anything, was stuck in the boot-loader.
After some searching I found a link to unlock the boot-loader via htcdev to fix the security warning and allowed me to finally boot back into the rom but the phone kept shutting down after it booted up past the thunderbolt screen. So after searching I found this link http://www.thunderboltforums.com/forum/htc-thunderbolt-help/7853-how-fix-security-warning.html and used the 2nd method to fix it since I still have a custom recovery on the phone. Now my problem is I am once again trying to get s-off through the thunderbolt tool like it says in the guide but every time I use the tool it says Starting up... and does nothing. Bascially im now stuck with s-on and an unlocked boot-loader. oh I tried to relock the bootloader but it just gives me a security warning again and im stuck in the bootloader again.
Any Ideas?
Alright never-mind I just used the Revolutionary 0.4 program and gained "revolutionary" in the pink field and s-off again so im good there again.
The thunderbolt tool is still stuck at "starting up"..., is there another way to get the tbolt back to stock condition?
dlahmeyer said:
Alright never-mind I just used the Revolutionary 0.4 program and gained "revolutionary" in the pink field and s-off again so im good there again.
The thunderbolt tool is still stuck at "starting up"..., is there another way to get the tbolt back to stock condition?
Click to expand...
Click to collapse
If you have S-off then just grab a stock RUU (easiest probably gingerbread) and flash the RUU in hboot. This will completely return your phone to stock as well as unroot you. If you wish to keep root then flash a leaked RUU that someone put up.
Jeagle88 said:
If you have S-off then just grab a stock RUU (easiest probably gingerbread) and flash the RUU in hboot. This will completely return your phone to stock as well as unroot you. If you wish to keep root then flash a leaked RUU that someone put up.
Click to expand...
Click to collapse
So how the hell do you do that?
fillyo said:
So how the hell do you do that?
Click to expand...
Click to collapse
If you're already rooted go to the development section and download the new radio and put it on the root of your sd card, rename it to PG05IMG.zip, reboot into the bootloader. The bootloader will automatically scan for the update and ask it you want to update. Select yes. Once it is finished and the phone boots back up. Use a file manager to browse to the radio and rename it. Then download and flash the official ics build. Don't confuse it with the leak. The leak is a worthless piece of crap and doesn't come close to how much better the ota is.
Sent from my ADR6400L using Tapatalk 2
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
brownsfan said:
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
Click to expand...
Click to collapse
So I think I found out what I did. 2.28 is the Global version. I must of rooted that version and flashed roms. I wanted to unroot and get back to stock software version.
Where should I go from here? Is there an RUU for the ICS Global? I can not seem to find one.
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Thingula said:
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Yes I can unlock again and that does get me unstock from the boot screen but still cant get where I want. Hmm.
I wonder if you can fastboot-flash the older kernels, using a computer, then flash the old stock ROM, lock the bootloader, then run an RUU.. Can anyone confirm this? Sounds too simple to work on an HTC phone.
Edit: No, of course that doesn't work. Sorry, I can't really offer any more help.. I'll have to just hope that someone more knowledgeable can take over.
Sent from my ADR6425LVW using xda app-developers app
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Very much so! Thank you. If I could hit the thanks button 10x I would.
Im sure im not the only only to have the Hboot 2.28 issue.
hey man you still around ? i need some help with a situation like this
dust906 said:
hey man you still around ? i need some help with a situation like this
Click to expand...
Click to collapse
I replied to you in your thread.
S-On Locked stock !
mikeyk101 said:
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Click to expand...
Click to collapse
This guide was FREAKING AWESOME. It led me to finally after 2 years go S-Off (wire trick) to do RUU, etc. Have to return phone and have already got replacement. Crossed my fingers and everything looks stock stock stock !