Related
how does this happen? solutions? im also not able to flash an ruu for some reason...stumped and have been working on this for an hour or so
rezin said:
how does this happen? solutions? im also not able to flash an ruu for some reason...stumped and have been working on this for an hour or so
Click to expand...
Click to collapse
Tampered is normal. Did you try flashing it with a ph98img, or as an .exe
It happens after you unlock and install a custom recovery I believe. Are you re-locked when you try to ruu?
Sent from my ADR6425LVW using Tapatalk 2
big_mike_2k6 said:
And are you re-locked when you try to ruu?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Yeah make sure your bootloader is relocked
i was in the middle of doing s-off when the phone froze and corrupted the mem card...so i tried redoing the whole process over and i havent been able to get past the hboot...im still unlocked and have access to recovery and hboot but i cant flash a rom and boot into it...i cant run an ruu but the phone is not technically bricked...its an odd predicament...i just flashed a rom and i still cant get it to get past the hboot
Have you tried re-locking the bootloader and then run the ruu?
Sent from my ADR6425LVW using Tapatalk 2
i was hesitant to do anything else aside from the things i mentioned incase i was unable to get those back...gonna let the phone recharge and try again later tonight...any ideas are welcome in the mean time...and ill go ahead and relock it and try later
rezin said:
i was hesitant to do anything else aside from the things i mentioned incase i was unable to get those back...gonna let the phone recharge and try again later tonight...any ideas are welcome in the mean time...and ill go ahead and relock it and try later
Click to expand...
Click to collapse
just run the latest ruu in hboot if you are s-off it will make the phone like it was from factory.
if you are s-on but unlocked you will need to do the "fastboot oem lock" then runn the ruu.
in both cases the ruu will nuke the internal storage. first pass with install a new hboot and stock recovery along with 2 other items, then the phone will reboot into fastboot and install the rest. i recommend that you have a 60% or more battery life.
synisterwolf said:
just run the latest ruu in hboot if you are s-off it will make the phone like it was from factory.
if you are s-on but unlocked you will need to do the "fastboot oem lock" then runn the ruu.
in both cases the ruu will nuke the internal storage. first pass with install a new hboot and stock recovery along with 2 other items, then the phone will reboot into fastboot and install the rest. i recommend that you have a 60% or more battery life.
Click to expand...
Click to collapse
Yeah I already got it up n running...between being unlocked and having a slightly dead battery I wasn't even being given the option to run an ruu...its running now but I still need to do s-off again, and of course my sd card is corrupted so ill work on that tonight
The same thing happened to me, glad I found your thread! Were you trying to s-off on the official ICS? That's what I was trying. I ran the .12 RUU and had unlocked, rooted and was trying to get S-off. I did the wire trick I was getting an HTC logo instead of Jbear logo. Right now I just relocked and it's running the RUU so I hope I can get back up and running.
I guess I should have just S-offed before running the ICS RUU
Edit: I am back up and running!
willdo7474 said:
The same thing happened to me, glad I found your thread! Were you trying to s-off on the official ICS? That's what I was trying. I ran the .12 RUU and had unlocked, rooted and was trying to get S-off. I did the wire trick I was getting an HTC logo instead of Jbear logo. Right now I just relocked and it's running the RUU so I hope I can get back up and running.
I guess I should have just S-offed before running the ICS RUU
Edit: I am back up and running!
Click to expand...
Click to collapse
Hey, I didn't have to do this, but if you noticed, controlbear makes backup copies of stuff like boot.img (forget what else) and puts them on your computer. If you crap out you ought to be able to fastboot flash boot [bootimgfilename.img] and be able to boot up your phone. I saw where one person did this to get going again after a failed soff.
Yeah well happened in my case is that I was already s-offed and then I flashed the ruu to go back to stock...then I relocked my phone cuz I'm having an issue with one of the pins on phone (the terminal that connects to battery).so I was gonna get it exchanged, I wanted it to look absolutely stock...so the "relocked" status wasn't good enough, so someone suggested doing s-off again so it will show locked in hboot...well that's where everything went wrong, the phone froze at the wire trick and then the entire memory card was corrupted which is normal...so when I went to redo the whole s-off procedure again I kept rebooting into the blank screen with the arrow...could not get past that, so I resorted to putting my real sd card in...I had no backups for that card cuz that one has my actual personal stuff so I figures it'd be ok since I used a spare to do s-off anyway...well upon powering on the phone it was also corrupted...so Ive actually given up on s-off and getting my phone restored and replaced for a while...I don't know why s-off has always given me problems I've watched and read every vid or post about s-off and am in no way tech illiterate but I've always had problems with s-off (i lost all my pics and documents the first time I did s-off even thought I backed everything up cuz the only way to get it right was to eliminate every file in the folder and rerun it again cuz it didn't back up my sd correctly If at all)...its beyond infuriating
well that didnt last long...i just unlocked and s-offed my phone again, only to be returned to s-on and fully locked (indistinguishable from brand new in box), as i originally intended...im gonna miss this particular phone but it has to be done
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
Background:
Was gonna let a friend borrow my DNA to see how she liked it. She has ATT. Flashed Newts Sense 5 ROM and played with APN settings. No data...so screw it..I get to keep my phone. Reboot to recovery and wipe and re install the ROM...no data.
What Ive done:
Mostly panicked...but I eventually found a thread to get back to stock and then I was gonna unlock. I'm S-Off. I did fastboot oem lock and RUU'd
Now my screen says Relocked but still S-Off.
How the heck can i flash a recovery so I can flash a rom? I don't want to boot my phone untill i'm rooted cause i don't want the OTA
Unlock again using the Unlock_code.bin HTC gave you with fastboot flash unlocktoken Unlock_code.bin, then flash the recovery.
If your S-OFF what's the big deal about taking the OTA? You can always go back with S-OFF. I had no data issue too just make sure your on the pre ota hboot and relocked then RUU should work. After RUU completes factory reset and your good to go.
Sent from my 5 Senses of DNA
LakerStar25 said:
If your S-OFF what's the big deal about taking the OTA? You can always go back with S-OFF. I had no data issue too just make sure your on the pre ota hboot and relocked then RUU should work. After RUU completes factory reset and your good to go.
Sent from my 5 Senses of DNA
Click to expand...
Click to collapse
Mine was quite different.. I had a CID of 11111111
....I couldnt use my unlock code...so I had to change my CID to 2222222
Worked like a charm. Thank you for pointing me in the right direction,.
andrewp3481 said:
Mine was quite different.. I had a CID of 11111111
....I couldnt use my unlock code...so I had to change my CID to 2222222
Worked like a charm. Thank you for pointing me in the right direction,.
Click to expand...
Click to collapse
Yea no problem
Sent from my 5 Senses of DNA
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 !
So yesterday I had my Aria in my pocket and I guess the power button got nudged and the screen turned on, lo and behold I pull my phone out of my pocket to find the lovely words written on the screen that too many pattern attempts have been attempted and that the device is locked. Only problem is I use this phone for everything but the phone function, I don't even have a sim in there. So with WiFi off, and no mobile network I was stuck for a bit. But then I finally sat down with it and luckily I had kept USB debugging on so I used adb to hack it. And that is where my urgent problem starts. After finally unlocking it I decided to might as well upgrade it, it was running 2.0.2 I believe Liberated ROM with CWM. So I started browsing around because I haven't really worked with this phone before all that much, I ended up reflashing to stock rom and then was going to use a nifty tool to get my hboot to 1.02, well it worked, the nifty tool flashed my hboot alright, along with my ROM and everything else there was. I am now stuck with a brick, the phone goes to the boot logo and then reboots... over and over and over until I pull the battery. I was charging the phone the whole time while working on it and after the tool was done flashing the hboot I unplugged the phone and a long list of errors ran down the screen of files that the OS was missing. I can get into fastboot, haven't had luck with any reflashs, adb is dud (while in recovery computer recognizes the adb connection but adb only lists the device as inactive. Ever since I lost my Inspire 4G this was my only working mobile device. If you have any tips tricks or clues as to how or if it is possible to come back from this destruction I am all ears.
Thank you in advance :fingers-crossed:
To clarify a bit further, the part that screwed me was the Upgrade HTC Gratia HBOOT for AlpharevX S-OFF tool. It was chugging along just fine up until the very end. The original sites listed for making a gold card are all dead but I managed to find a working one. Now I am trying to figure out what went wrong and why.
LIBERTY PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-031b
TOUCH PANEL-STN21_03
RADIO-7.13.35.13
Nov 4 2010,23:12:58
The time and date are frozen
First you should S-OFF your phone with revolutionary. Then you need to flash a working recovery image and reflash ROM from there. Should work. If this still doesn't work, flash a modified hboot from the Development forum and see if you have any luck with that...
dansou901 said:
First you should S-OFF your phone with revolutionary. Then you need to flash a working recovery image and reflash ROM from there. Should work. If this still doesn't work, flash a modified hboot from the Development forum and see if you have any luck with that...
Click to expand...
Click to collapse
I cannot get revolutionary to find the device, the system version is 2.37.709.11 and I cannot do anything, if I try flashing anything the sig verification always fails.
(EDIT: Well I got lucky, found an asian RUU with same version, reflashed phone, S-Off, flashed unofficial CWM recovery and unofficial cyanogen 11.)
The problem I was having with revolutionary not recognizing the device was because my hboot version was too old (0.57). I used this AT&T Update package to get back to stock 2.2 and revolutionary worked straight away.
HTC_Aria_for_ATT_Android_2.2_ROM_Update.exe
http://www.mediafire.com/download/mch2657rdy8aqct/HTC_Aria_for_ATT_Android_2.2_ROM_Update.exe