Related
Hi everyone, first time posting here so forgive me if I've done something wrong or overlooked anything. I've read the superguide, I've used the search function, etc.
Me and my sister both have the HTC Aria on Optus (we're in Australia). I managed to get s-off and root my phone after a fair few painstaking hours (attn1 may remember me, he was the one who helped me take the phone from being softbricked back to life again).
I'd like to get s-off on my sisters phone as well, but I'm a little worried that I'll run into the same problem again, and I REALLY don't want to go through all of that again/not have a working phone. Is there anything different between the AT&T and the Optus phones that may have caused everything to just blow up in my face?
I do have a feeling that it may have died halfway through for me due to low battery and that was the cause of it all, but I'd just like to be 100% sure that there's nothing else I may have missed.
The other phone has been upgraded to 2.2 via the OTA update.
Thanks!
EDIT: I just had a quick thought, I re-read the Aria guide on how to root/s-off, and I noticed one of the steps was to grab the AT&T stock ROM/update from the HTC site. Is it possible to update the already updated Aria to the AT&T 2.2, thus hopefully allowing for root/s-off to be achieved with ease?
What version of HBOOT does the phone have? (Press volume down + power when the phone is off. After you're done there, select fastboot then select reboot to get out of that menu.)
drumist said:
What version of HBOOT does the phone have? (Press volume down + power when the phone is off. After you're done there, select fastboot then select reboot to get out of that menu.)
Click to expand...
Click to collapse
HBOOT version is 1.02, so I can't go about using the Unrevoked method gotta use the AlphaRev/Revolutionary tool.
lostie888 said:
HBOOT version is 1.02, so I can't go about using the Unrevoked method gotta use the AlphaRev/Revolutionary tool.
Click to expand...
Click to collapse
You are good to go. Just remember to follow the directions closely,
lostie888 said:
HBOOT version is 1.02, so I can't go about using the Unrevoked method gotta use the AlphaRev/Revolutionary tool.
Click to expand...
Click to collapse
Yeah, but if you have 1.02 then it will be very easy. You do not need to flash any ROM first. Just run the Revolutionary tool and that's it.
drumist said:
Yeah, but if you have 1.02 then it will be very easy. You do not need to flash any ROM first. Just run the Revolutionary tool and that's it.
Click to expand...
Click to collapse
But like I said earlier, it pretty much softbricked my phone when I did it. I ended up with the yellow triangle for a while before I managed to get around it (which I can't remember how to do anymore ). Then again, I did use it when it was first released (i.e, before it was re-named Revolutionary), so maybe I wont run into the same problem?
lostie888 said:
But like I said earlier, it pretty much softbricked my phone when I did it. I ended up with the yellow triangle for a while before I managed to get around it (which I can't remember how to do anymore ). Then again, I did use it when it was first released (i.e, before it was re-named Revolutionary), so maybe I wont run into the same problem?
Click to expand...
Click to collapse
Revolutionary will probably be better for you. It automatically installs Clockworkmod Recovery for you, which should leave your phone in a state where you can flash a ROM of your choice. (i.e., no yellow triangle)
drumist said:
Revolutionary will probably be better for you. It automatically installs Clockworkmod Recovery for you, which should leave your phone in a state where you can flash a ROM of your choice. (i.e., no yellow triangle)
Click to expand...
Click to collapse
It installs Clockworkmod automatically?! That's pretty cool! Probably something the Root guide should update as well
I'll try and give it a go tonight, I'll report back here if I have any problems (which I hopefully shouldn't)!
Thanks for the help!
Update: She doesn't want her phone rooted (yes, I know, weird, but whatever). Thanks for the help anyway!
Hi Everyone,
I accidentally hit the OTA update (software ver. 1.22.651.3 710RD) for my rooted HTC EVO 4G LTE phone (whoops!). I have SuperSU Pro with Survival Mode activated but that didn't work. I never installed special ROMs and primarily used ROOT for Tethering.
At any rate, my root is now gone and I can't find any discussions about how to re-root after an OTA update. I don't want to screw up my phone any further since it seems to be working ok otherwise.
Any suggestions?
Thanks!
skejmal said:
Hi Everyone,
I accidentally hit the OTA update (software ver. 1.22.651.3 710RD) for my rooted HTC EVO 4G LTE phone (whoops!). I have SuperSU Pro with Survival Mode activated but that didn't work. I never installed special ROMs and primarily used ROOT for Tethering.
At any rate, my root is now gone and I can't find any discussions about how to re-root after an OTA update. I don't want to screw up my phone any further since it seems to be working ok otherwise.
Any suggestions?
Thanks!
Click to expand...
Click to collapse
You'll have to do the HTCDev unlock method (easiest way is through RegawMod). That's the only way right now.
eXplicit815 said:
You'll have to do the HTCDev unlock method (best way is through RegawMod). That's the only way right now.
Click to expand...
Click to collapse
actually the best way is htc dev using the adb tools mini sdk, regawmod has not been fixed and there are a lot of users complaining that they get stuck. To me it only takes a little common sense to solve 90% of the issues using regawmod but some people need their hands held and that thread is slowly boiling down to the worlds most repetitive support desk.
HTC Dev Unlock
Requirements
HTC Drivers
ADB Tools Mini SDK
Setup
Install HTC Drivers if necessary
Extract ADB Tools anywhere, doesnt matter
Open ADB Tools and hold shift+right click, select open command window here
In phone settings, enable usb debugging and disable fasboot
Connect the phone to pc
Steps
In the command window type adb start-server
Next type adb reboot bootloader
Select fastboot
Type fastboot devices to make sure you are connected
Type fastboot oem get_identifier_token
Right click and select mark, click and drag from the top arrows to the bottom arrows and make sure not to highlight any empty spaces as this will confuse the website, right click and it will be saved to clipboard
Now go to HTC Dev and if you don't already have an account, sign up for it
Go to unlock bootloader and select other supported models and accept the agreements
Skip the steps until you get the to token submit window and paste the token you copied earlier and submit.
Go to your email and download the unlock_bin code
Put the code in the ADB Tools folder
Type fastboot flash unlocktoken Unlock_code.bin
When the phone prompt comes up to unlock bootloader hit yes, now you are unlocked, re-enable usb debugging and disable fastboot
Type adb reboot bootloader
Type fastboot devices to make sure phone connected
Type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img
Type erase cache
Reboot phone and you will have unlock and recovery, all thats missing is to restart phone in bootloader and select recovery to flash a rom. Wipe Dalvik, cache, Factory reset, system and then install the rom. If it doesn't boot, extract the boot.img from the rom and put it in the adb folder and in fastboot type fastboot flash boot boot.img and reboot
Thanks for responding so quickly! I will try this.
skejmal said:
Thanks for responding so quickly! I will try this.
Click to expand...
Click to collapse
Does this work for an LTE EVO running 2.13.651.1 710RD as well? That is what my phone is showing. Thanks.
steveiott06 said:
Does this work for an LTE EVO running 2.13.651.1 710RD as well? That is what my phone is showing. Thanks.
Click to expand...
Click to collapse
Should work for all versions because it's the HTC method for unlocking your phone to root.
eXplicit815 said:
Should work for all versions because it's the HTC method for unlocking your phone to root.
Click to expand...
Click to collapse
Hmm. Thanks for the help. However I was not aware that rooting the phone and doing this process would completely reset the phone back to stock. Now I have to set everything up again. Is this normal?
steveiott06 said:
Hmm. Thanks for the help. However I was not aware that rooting the phone and doing this process would completely reset the phone back to stock. Now I have to set everything up again. Is this normal?
Click to expand...
Click to collapse
Yes. It even tells you when you accept the terms on the phone.
skejmal said:
Thanks for responding so quickly! I will try this.
Click to expand...
Click to collapse
One last stupid question...Are the steps you describe to re-root applicable to a Mac? or Windows-based computer?
skejmal said:
One last stupid question...Are the steps you describe to re-root applicable to a Mac? or Windows-based computer?
Click to expand...
Click to collapse
Windows, although there are methods for OS X.
steveiott06 said:
Hmm. Thanks for the help. However I was not aware that rooting the phone and doing this process would completely reset the phone back to stock. Now I have to set everything up again. Is this normal?
Click to expand...
Click to collapse
Well, after getting the phone going and attempting to use programs with root privileges, it seems that the rooting process didnt work. All the steps went just fine until I got to the last one and it said to "wipe cashe" when I typed that in it didnt work, so I just skipped that step and rebooted the phone.
Is that what caused the root to not take to the phone?
steveiott06 said:
Well, after getting the phone going and attempting to use programs with root privileges, it seems that the rooting process didnt work. All the steps went just fine until I got to the last one and it said to "wipe cashe" when I typed that in it didnt work, so I just skipped that step and rebooted the phone.
Is that what caused the root to not take to the phone?
Click to expand...
Click to collapse
What steps did you do? I did RegawMOD last week and it was done in like 5 minutes.
eXplicit815 said:
What steps did you do? I did RegawMOD last week and it was done in like 5 minutes.
Click to expand...
Click to collapse
I did the HTC Dev unlock steps.
steveiott06 said:
I did the HTC Dev unlock steps.
Click to expand...
Click to collapse
Do THIS, and get back to me.
steveiott06 said:
I did the HTC Dev unlock steps.
Click to expand...
Click to collapse
You need to flash superuser in recovery or flash a rom
eXplicit815 said:
Do THIS, and get back to me.
Click to expand...
Click to collapse
Also tried this last night. I plug my phone in, hit the ROOT button and nothing happens. I actually get a "not responding" on the software. My phone does not reboot into recovery. Does the HBOOT version matter with this? I am v1.19
Sorry, I am still learning all these terms. Not exactly sure what effects what.
I rooted and put Cyanogenmod on my OG EVO and never had this much trouble.
FYI: I was rooted before doing the latest OTA update. So I still have a Super user icon but if I click it it cant update the binary (because I am no longer rooted)...I read somewhere that people said to do a factory reset then try this rooting method again, because of old junk files left behind on the phone. This true?
Does this work on hboot 1.19?
Sent from my EVO using xda premium
If I want to completely update my phone (Android 4.0.3, Soft ver 1.22.651, baseband 1.02 because I pretty much got the phone the phone in December and immediately rooted it), will this method work? I'd really like to get Mean Rom but obviously, I'm in need of a few updates and I'm trying to figure out the simplest way to get there. It seems like doing all the official updates and then re-rooting and then installing MR would be the simplest way to do it buuuuut better to ask and be wrong and pointed in the right direction than screw everything up.
ashemountain said:
If I want to completely update my phone (Android 4.0.3, Soft ver 1.22.651, baseband 1.02 because I pretty much got the phone the phone in December and immediately rooted it), will this method work? I'd really like to get Mean Rom but obviously, I'm in need of a few updates and I'm trying to figure out the simplest way to get there. It seems like doing all the official updates and then re-rooting and then installing MR would be the simplest way to do it buuuuut better to ask and be wrong and pointed in the right direction than screw everything up.
Click to expand...
Click to collapse
Why don't you try getting S-off, then updating everything without having to unroot & root again?
Sent from my EVO using xda premium
FinZ28 said:
Why don't you try getting S-off, then updating everything without having to unroot & root again?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
What he said
Sent from my HTCONE using xda app-developers app
[SOLVED - See Post #9]
Hey everyone,
So, I have some experience with rooting/ROMs, bootloaders and recoveries, all specifically on my HTC Droid Incredible (Yep, the original). But that's long in the tooth these days, and getting rather difficult to stand the slower speeds and all.
I decided to pick up a used phone, in this case an HTC Rezound, to repair and serve as my default. Cracked digitizer, but that's an easy fix, and it works for the moment which is all that matters. Turns out there was one more problem with it - it doesn't boot Android. It gets stuck in a bootloop if you allow it to boot, but it does go to hboot if you boot it up and hold the VOL down key, as expected. I cannot boot into recovery.
I tried flashing the 4.03.605.2 RUU from AndroidPolice - same problem. So, I'm not sure where the issue lies. I'd like to start by just getting the phone back to stock, and booting into Android if anyone can help me. I should be able to do everything properly from there.
I'm not entirely certain if HBOOT is stock - it shows the Android on the skateboard at the bottom - I'm not sure if that's a custom HBOOT or not, and I can't seem to find any specific reference to it. It is LOCKED with S-ON, so, I've been assuming that it hasn't been tampered with too deeply, someone just hosed an upgrade and I'm not sure how to go about getting it fixed.
Any help is deeply appreciated.
- Katie
lolatvincent said:
You have to fastboot oem rebootRUU first
then fastboot flash zip PH98IMG.zip
you may have to flash the zip twice.
Code:
androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
(I can't link yet)
Click to expand...
Click to collapse
This might be able to help you too. You have adb and fastboot on your computer right?
lolatvincent said:
This might be able to help you too. You have adb and fastboot on your computer right?
Click to expand...
Click to collapse
Yes, I do. Thank you, I'll check that out!
Like I was saying, I knew it wasn't bricked, I just didn't know how to go about doing it. I think I get where I need to go with that.
ncc74656m said:
Yes, I do. Thank you, I'll check that out!
Like I was saying, I knew it wasn't bricked, I just didn't know how to go about doing it. I think I get where I need to go with that.
Click to expand...
Click to collapse
Flash a recovery in a zip right after you finish the ruu using the same method (no need for reboot).
To get root again you might want this: downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip
lolatvincent said:
Flash a recovery in a zip right after you finish the ruu using the same method (no need for reboot).
To get root again you might want this: downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip
Click to expand...
Click to collapse
Ok, no such luck. I did the RUU flash and then tried rebooting, no go, tried reflashing from my SD after that, nothing. I'm not sure what to do now. :/
Update
Small update - I did the HTC bootloader unlock and successfully got Amon Ra flashed onto it. Now working on getting Android to boot. *sigh* This thing is a serious pain in the... :angel:
If I get it to work, I'll be sacrificing a ram, or at least some RAM. :fingers-crossed:
Still, I'm open to any suggestions or help anyone can offer. Thank you!
I would make a nandroid now and keep it as is for a bit just to make sure it functions okay.
Then if all is good flash a ROM!
I'm running ViperRez and it's very good. Doesn't seem to stream bluetooth media but all else is good. Very nice daily driver. There might be an update coming which will hopefully fix the bt steaming.
feralicious said:
I would make a nandroid now and keep it as is for a bit just to make sure it functions okay.
Then if all is good flash a ROM!
I'm running ViperRez and it's very good. Doesn't seem to stream bluetooth media but all else is good. Very nice daily driver. There might be an update coming which will hopefully fix the bt steaming.
Click to expand...
Click to collapse
Heh, that would be doing things the SMART way. I'm going to do the unofficial CM9 which has BT streaming media, but not phone - sadly, something I'm much more interested in. I am wondering if I can't get the stock ICS or JB on there and just stick with that, since I do like using my BT headset. But since I've had no luck so far getting that to go on there, I think I'll take my chances with CM9 first, and go from there.
If I get that, I'll back it up thoroughly and then try my hand at putting the stock 4.03 on instead.
Solved!
Ok, so, I got CM9 booted!
The short of what I did was the following steps:
1) HTC Dev Bootloader Unlock
2) Installed Amon Ra
3) Installed CM9 using the S-ON instructions found at the site below - I can't link yet, so forgive me.
Code:
http://forum.xda-developers.com/showthread.php?t=1885553
4) Letting the bootloader flash the Kernel failed, so I had to do it manually by following the instructions for S-ON below in case of a parsing failure:
Code:
http://www.androidauthority.com/rezound-android-4-0-4-ics-cyanogenmod-9-cm9-rom-unofficial-120696/
5) Boot and done!
ncc74656m said:
Ok, so, I got CM9 booted!
The short of what I did was the following steps:
1) HTC Dev Bootloader Unlock
2) Installed Amon Ra
3) Installed CM9 using the S-ON instructions found at the site below - I can't link yet, so forgive me.
Code:
http://forum.xda-developers.com/showthread.php?t=1885553
4) Letting the bootloader flash the Kernel failed, so I had to do it manually by following the instructions for S-ON below in case of a parsing failure:
Code:
http://www.androidauthority.com/rezound-android-4-0-4-ics-cyanogenmod-9-cm9-rom-unofficial-120696/
5) Boot and done!
Click to expand...
Click to collapse
Oh! I misread your last post above mine and thought you had gotten it back to stock.
Your issue was exactly what you figured out, that when you are s-on you need to flash the kernel separately after flashing a ROM or else you'll get stuck. If you s-off that will be automated but s-off makes it easier to brick your phone. I don't flash often so I'm staying s-on.
Sorry I misread your post, I could've let you know about that.
feralicious said:
Oh! I misread your last post above mine and thought you had gotten it back to stock.
Your issue was exactly what you figured out, that when you are s-on you need to flash the kernel separately after flashing a ROM or else you'll get stuck. If you s-off that will be automated but s-off makes it easier to brick your phone. I don't flash often so I'm staying s-on.
Sorry I misread your post, I could've let you know about that.
Click to expand...
Click to collapse
No worries, it happens, thank you!!!!
I'm trying to help a buddy of mine. He has a Thunderbolt, issued through work. It is stock, unrooted, locked, never modded. He recently got the ICS OTA update. Phone was functional, but laggy and a bit unstable. He did a factory reset, and initially the phone was fine for a few hours, then it was acting buggy. After a reboot it was fine for a bit, then froze. Usable time kept diminishing with subsequent reboots. He tried another factory reset, and the phone won't boot now. If you power it up, you get the white screen with the HTC logo, then a black screen, and nothing ever happens. I can get to Hboot. I can get to fastboot. Not sure if recovery does anything. I get the recovery screen, then a reboot, and then nothing.
I've been trying to read up on how to fix this, and I'm not sure how to go about it since the phone is currently locked, and won't boot. I looked at the Thunderbolt All In One tool, but it looks like it needs the phone to be booted to start the process.
My end goal is to get back to stock, unrooted, (Gingerbread, then OTA update I suppose), and S-on. But to do that, I need to obtain s-off first. Any info would be greatly appreciated.
I've attached a couple of pics.
Thank you.
a little side note
from what I've read verison has been replacing some phones that the ota has killed or broken something..
worth checking out...
I believe even out of warrenty..
cujo6801 said:
a little side note
from what I've read verison has been replacing some phones that the ota has killed or broken something..
worth checking out...
I believe even out of warrenty..
Click to expand...
Click to collapse
Good to know. Thank you. I think because it was employer issued, he's going to try to get a newer device if we can't get it running. But I just had to make some attempt to get it running.
Pm disconnecktie as you should be able to flash via abd beings you can get in to fastboot. He knows a lot about the workings of these phones.
Sent from my ADR6425LVW using Tapatalk 2
It could possibly be fixed by fastboot flashing the official release but I think a package would need to be put together for that to work correctly. Since the phone doesn't boot it limits the ways to fix it especially since we don't have an Ruu for the ics ota. Also because it doesn't boot adb commands are useless. Fastboot commands are unlikely to work either but I guess you could try by connecting the usb cable. Open a command prompt and type fastboot devices. If it shows the serial number then fastboot commands will work.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
It could possibly be fixed by fastboot flashing the official release but I think a package would need to be put together for that to work correctly. Since the phone doesn't boot it limits the ways to fix it especially since we don't have an Ruu for the ics ota. Also because it doesn't boot adb commands are useless. Fastboot commands are unlikely to work either but I guess you could try by connecting the usb cable. Open a command prompt and type fastboot devices. If it shows the serial number then fastboot commands will work.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Fastboot does work. I was able to do the "fastboot devices" command before, and saw the phone. I was also able to "fastboot flash zip" the file from post 12 from this tread (link below), BUT even though the file transferred from the computer to the phone, the actual flash failed... I'm assuming because the phone is locked.
http://forum.xda-developers.com/showthread.php?t=2120985&page=2
Try downloading the official ota zip over at the developer section. Put it on the root of your sd card and rename it to PG05IMG. Then run the update through fastboot. I seriously doubt this will solve the problem long term but it may work. I have doubts. I am beginning to think htc released the ota purely for development purposes. More and more people are popping in here with problems similar to this.
Sent from my ADR6400L using Tapatalk 2
I downloaded santod040's full ODEXED ICS ROM. That's the only thing I noticed that said "Official". Hopefully I didn't miss something obvious. I put it on the SD card and renamed it. Booted Hboot, and the file loaded, checked, then stopped and went back to the Hboot menu. No option to flash or install. Then, I tried doing fastboot flash zip from the command line while the phone was in Fastboot. It sent the file, and loaded it, then failed booloader signature checking. I'm not sure if there is another method to try. I have SOME working knowledge on how to do this stuff, but not as much as many of the members here, I'm sure.
SoundTech said:
I downloaded santod040's full ODEXED ICS ROM. That's the only thing I noticed that said "Official". Hopefully I didn't miss something obvious. I put it on the SD card and renamed it. Booted Hboot, and the file loaded, checked, then stopped and went back to the Hboot menu. No option to flash or install. Then, I tried doing fastboot flash zip from the command line while the phone was in Fastboot. It sent the file, and loaded it, then failed booloader signature checking. I'm not sure if there is another method to try. I have SOME working knowledge on how to do this stuff, but not as much as many of the members here, I'm sure.
Click to expand...
Click to collapse
You need to be rooted to use a rom
Sent from my Nexus 7 using Tapatalk 2
Yeah, that wasn't too swift of me, was it now?
I grabbed the zip from this thread:
http://forum.xda-developers.com/showthread.php?t=2144326
Tried Hboot with the file renamed, same results as previous post. Tried fastboot flash zip, same results as above. No joy.
Going to try to see if HTCDev will get the bootloader unlocked in the current phone state.
Well since the ota isn't a downgrade I thought it may work. If HTC dev is able to unlock his bootloader maybe he can get further.
Sent from my personally built from source CM10.1 N7.
Bootloader is unlocked now, since it was all through fastboot. Still S-on. Tried with the OTA zip still on the SD card as "PG05IMG.zip." It loaded, started to check, started to parse for a moment, then went back to the Hboot screen, reboot got me nowhere. I need to go deal with the rest of life now. I'll try again tomorrow. I appreciate everyone's help today. Thank you.
At this point just s off and install a recovery then you can flash that ROM.
Sent from my Nexus 7 using Tapatalk 2
Use this guide here. Make sure you have plenty of time before hand and FOLLOW THE DIRECTIONS IN ORDER TO A T. It is very important that you don't skip over stuff. This is the only current method to get s off with ics.
Sent from my ADR6400L using Tapatalk 2
Long day at work, but back to it. Making sure the battery is charged up, and downloading files.
I'm looking at a post on ThunderboltForums. Making absolutely sure here: Is THAT the one I should be following?
Follow-up: At the end of step 28, after flashing the .19 ROM, is says to use the All-In-One tool. IF I plan to be stock, unrooted, locked, S-on, it seems I'm there at this point, and I can let the OTA update run. Is that correct?
Thanks again.
Looks like I'm on stock Gingerbread, S-off, re-locked, stock recovery. Heck, it finally boots! I'll see about trying OTA update tomorrow.
Thanks again.
S off and relocked? You need to run the allinonetool first and unlock the bootloader before you flash anything.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
S off and relocked? You need to run the allinonetool first and unlock the bootloader before you flash anything.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Huh. I never did use the tool. I went through the steps on the ThunderboltForums post all the way through flashing the .19 ROM. Unless I missed something or did something wrong, before the flash it said I would be re-locked and S-on. After the flash it said the phone should be "back to normal". The next step was the All-In-One tool. But the device actually booted into android with the .19 ROM. That was the first time I saw it boot since I got my hands on it. Perhaps the process in that thread helped repair whatever part of the system was buggered up to begin with?
Regardless, I tried the OTA update, and the phone took the ICS update through Verizon. It seems to be running better now than it did before. It's back in my buddy's possession, and he's in the process of getting his apps and data reinstalled.
He thanked me profusely for getting it running again. So I, in turn, pass his thanks on to everyone here that helped me out, the people that worked to get the Thunderbolt resources to where they are now, and to the forum in general for existing and doing what it does. Thank you all.
Been a lurker for a while, now I need some input if possible. I have a Thunderbolt whose touchscreen is not fully working, there is a strip about 1/4" wide top to bottom that does not respond to input. I rooted it using trter's Thunderbolt Tool and have been running Santod's ICS. When I decided to return to stock I did not read anything and merely ran trtr's tool and used the unroot option. This has me stuck now with a weird state.
Boot screen:
*** UNLOCKED ***
MECHA XD SHIP S-ON
HBOOT-1.05.0000
MICROP-/
RADIO-1.48.00.0930w_3
eMMC-boot
Jul 19 2011, 14:51:08
4ext recovery is still installed for some reason.
Here are things I have tried:
1. Unroot using trtr's tool - leaves me in a non-booting state with a Security warning and Main Version failure.
2. Used HTCDev unlock and pushed PG05IMG.zip of 2.11.605. This allows me to boot to a seemingly stock ROM.
3. OTA's get pushed, device reboots but OTA's fail to install.
4. Tried recovering Nandroid backups with 4ext, no matter which one I try to restore I get stuck in a boot loop (BAMF SoaB, ICS Santod, Liquid ICS, Multi-source ICS, ICS stock deodex).
5. Tried using 4ext to install the above ROMS directly, along with full wipes and partition formats before each attempt. They seem to install but get stuck in a boot loop on each.
6. Other various combinations of HTCdev, Thunderbolt Tool, FastBoot boot.img pushes, etc. Trtr's tool connecting in booted and fastboot modes fails to unroot or root or change S-ON state.
7. Did step 2 again to get me a working phone (except touch screen problem) until I can figure out WTH is going on.
Current state - the above Boot Screen details, 2.11.605.19 deodexed-signed image, and lucky I have not totally bricked it yet.
Help please? I've googled for the last 3 days and read countless posts and am not sure what to do from here. All I need is to get it back to stock so I can send it back to HTC and get a replacement. I have a working ADB set up and am willing to follow steps exactly or read whatever page you believe I have missed, or call me a dumb n00b, berate me for not reading something, anything... at this point I have no interest in retaining data on the phone or SD card or my dignity, just a stock phone that I can send back.
Thanks all!
Me too
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
That's major coincidence I have exact same problem, down to dead touch screen strip. I've been trying to get unrooted for a week and was supposed to mail the thing back last Friday . .
Here's hoping a solution gets posted. I don't want to pay cuz the insurance refurb was fail, when my warranty service is supposed to be free replacement and it is stupid hardware failure.
All I can say is trter supposedly updated his tool to work with the latest ota, but its been about a week and he hasn't released it yet.
He did say something about having a problem with his host though.
washuai said:
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Click to expand...
Click to collapse
This is how I fixed the security warning when I first got it, using HTCDev unlock. I also used adb fastboot relock to lock back before trying the tool.
washuai said:
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
Click to expand...
Click to collapse
Yep - got that too...
Weird. Guess I'll wait for the new tool and see what it does...
As far as the identical touchscreen issue, this phone is also a refurb, my second with a touchscreen problem. The really weird part is that it works sometimes, particularly after all this work flashing and re-flashing, but I don't think it has anything to do with the ROMS or software, rather the fact that during all this work I am constantly doing battery pulls and SD card swaps and maybe it's because of a flaky ribbon connection or something - if it was not under warranty I would open it up and just try reseating anything I could find inside.
Have you tried to RUU back? It is a way manufacturers refurb or make the software new again without having to figure out what state it is in.
As long as you can get in fastboot it will work... Also could you possibly fastboot an ENG HBOOT? It doesn't show if it's unlocked nor does
it have any of those pink banners up at top.... Those I believe allow you to flash anything you couldn't normally do before... Try that.. Also I
ALWAYS manually push and flash my stuff through ADB and fastboot. It is faster (if you know what you are doing) AND it has better control
over what I am doing. I made a tut on how to flash boot screens (the very first image that comes up when you turn it on) and it is just about
same commands to flash normally stuff.
I run a Linux Box and always use root terminal so I am not certain at what point you would need superuser if any but as follows
#fastboot devices
#fastboot flash zip "name of zip" (no it doesn't have to be called anything specific, it could be called file1.zip)
#fastboot erase [option] /cache /data /system
to force it into the special RUU mode to use HTC's RUU, this is the command
#fastboot oem rebootRUU
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
jnorth said:
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
Click to expand...
Click to collapse
If you can give me today and I'll send you either the link to download the RUU or the exe itself.
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
The ota's don't install because of the custom recovery.
Backups don't work because your s-on and the kernel can be installed.
You may be able to install santod's ota rom in recovery and install the boot.IMG from the rom (kernel) in fasboot = ./fastboot flash boot boot.img
Relock the boot loader and send it in looking like stock.
There is also a way to spoof your main version and downgrade from ICS to GB Ruu stock. That is posted on another site.
Sent from my ConD3m3dPaC-man ADR6425LVW using xda app-developers app
tburns said:
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
Click to expand...
Click to collapse
Working on this now, as soon as I figure out how to get s-off again. Thanks!
http://androidfiles.org/ruu/?developer=Mecha
The RUU's to take you back to stock
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
jnorth said:
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
Click to expand...
Click to collapse
that is what the community is all about , right?
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
you could ALWAYS use an ENG and nobody would be non-the-wiser if you rooted or not! It would look like a developer phone instead..
when it says ***RELOCKED*** it tells anybody and everybody you have been rooted at one point or another (no bueno for warranty)
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
this -SHOULD- take care of the pink banner up at top BE CAREFUL WITH THIS!!!
there again... I run constant root terminal so I do not know if it requires root or not soooo.....
#fastboot oem mw 8d08ac54 1 31302E30
#fastboot flash hboot whateverhbootfile.nb0