Just decided to root my Rezound mostly because of the need for wireless tether. I'm fairly new to this method of rooting, but have rooted an HTC EVO 4G about a year ago and that went much smoother. After trying to figure out the order of things (which i'm not sure i did correctly), I finally started the process I followed which i've outlined below. I successfully rooted, but once i updated to the most recent RUU (3.14.605.5) and semi-successfully S-OFF (i'll explain below), i noticed that i no longer have root access. Tried to re-root, but nothing has worked... Anything i can do??
Here is the process I took (mainly tried to follow this a playlist on youtube i found - sorry can't post a URL):
1. Unlocked Bootloader via HTCDev
2. Tried to perform root with OneClickRoot 1.1, this didn't work.
3. Googled other ways to root the rezound
4. Found rEZoundRoot 1.5 - Tried it and obtained root.
5. Updated SuperUser app, verified root access worked
6. Installed clockwork touch recovery as per the video playlist above
7. At this point i kept reading about all the ICS ROMs out there and decided that's what i was going to update. Noticed that it looked just easier to update the firmware and S-OFF before putting a custom ROM on
8. downloaded the RUU 3.14.605.5. and flashed to phone.
9. during this process i had to relock the bootloader, so i had to unlock again.
10. The RUU also updated firmware
11. Followed the S-OFF directions by running ControlBear for 3.14.605.5
12. Here's where it gets weird. First of all it took me about 10 times to get the wire trick down. but once i finally did, the phone jacked up? along the way (not sure what happened, but there was a picture of a phone with a red triangle with an exclamation point in it). By the time this showed up, ControlBear had timed out. I then pulled battery and restarted. checked bootloader and it's showing S-OFF now. Fully booted phone and it started just fine. Figured everything was OK and continued on
13. After the phone booted i noticed superuser was no longer installed (since the RUU update) I redownloaded. Tried to update, and that's where it failed gaining root access. I then tried to re-root with rEZoundRoot 1.5 and that didn't work (still no root access). Then tried with OneClickRoot 1.1, this time it did much more than the first time, appearing to work. Phone rebooted but still no root.
This is now where i'm at... Stuck with S-OFF and RUU 3.14.605.5 and NO ROOT. Anyone have any ideas??
This is what my hboot says:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
The "TAMPERED" was never there until one of the final steps above. Not sure if that has something to do with it or not.
Basically all i want to do is have rooted phone with the newest firmware and S-OFF. Then apply any custom ROMs from there as I see fit.
If anyone can help, it'd be greatly appreciated! Thanks in advance.
biscuitgod said:
Just decided to root my Rezound mostly because of the need for wireless tether. I'm fairly new to this method of rooting, but have rooted an HTC EVO 4G about a year ago and that went much smoother. After trying to figure out the order of things (which i'm not sure i did correctly), I finally started the process I followed which i've outlined below. I successfully rooted, but once i updated to the most recent RUU (3.14.605.5) and semi-successfully S-OFF (i'll explain below), i noticed that i no longer have root access. Tried to re-root, but nothing has worked... Anything i can do??
Here is the process I took (mainly tried to follow this a playlist on youtube i found - sorry can't post a URL):
1. Unlocked Bootloader via HTCDev
2. Tried to perform root with OneClickRoot 1.1, this didn't work.
3. Googled other ways to root the rezound
4. Found rEZoundRoot 1.5 - Tried it and obtained root.
5. Updated SuperUser app, verified root access worked
6. Installed clockwork touch recovery as per the video playlist above
7. At this point i kept reading about all the ICS ROMs out there and decided that's what i was going to update. Noticed that it looked just easier to update the firmware and S-OFF before putting a custom ROM on
8. downloaded the RUU 3.14.605.5. and flashed to phone.
9. during this process i had to relock the bootloader, so i had to unlock again.
10. The RUU also updated firmware
11. Followed the S-OFF directions by running ControlBear for 3.14.605.5
12. Here's where it gets weird. First of all it took me about 10 times to get the wire trick down. but once i finally did, the phone jacked up? along the way (not sure what happened, but there was a picture of a phone with a red triangle with an exclamation point in it). By the time this showed up, ControlBear had timed out. I then pulled battery and restarted. checked bootloader and it's showing S-OFF now. Fully booted phone and it started just fine. Figured everything was OK and continued on
13. After the phone booted i noticed superuser was no longer installed (since the RUU update) I redownloaded. Tried to update, and that's where it failed gaining root access. I then tried to re-root with rEZoundRoot 1.5 and that didn't work (still no root access). Then tried with OneClickRoot 1.1, this time it did much more than the first time, appearing to work. Phone rebooted but still no root.
This is now where i'm at... Stuck with S-OFF and RUU 3.14.605.5 and NO ROOT. Anyone have any ideas??
This is what my hboot says:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
The "TAMPERED" was never there until one of the final steps above. Not sure if that has something to do with it or not.
Basically all i want to do is have rooted phone with the newest firmware and S-OFF. Then apply any custom ROMs from there as I see fit.
If anyone can help, it'd be greatly appreciated! Thanks in advance.
Click to expand...
Click to collapse
There are stock rooted versions of the leak, it would be easiest to just flash one on your phone. Scott has them posted and the PKMN Team for Sense 4.0 is amazing!
If you really want to root it yourself first (which isn't necessary) you could use Amon Ra install SU, and flatest binaries zip for SU. That's what I did at first so I could take a stab at customizing and designing.
biscuitgod said:
Just decided to root my Rezound mostly because of the need for wireless tether. I'm fairly new to this method of rooting, but have rooted an HTC EVO 4G about a year ago and that went much smoother. After trying to figure out the order of things (which i'm not sure i did correctly), I finally started the process I followed which i've outlined below. I successfully rooted, but once i updated to the most recent RUU (3.14.605.5) and semi-successfully S-OFF (i'll explain below), i noticed that i no longer have root access. Tried to re-root, but nothing has worked... Anything i can do??
Here is the process I took (mainly tried to follow this a playlist on youtube i found - sorry can't post a URL):
1. Unlocked Bootloader via HTCDev
2. Tried to perform root with OneClickRoot 1.1, this didn't work.
3. Googled other ways to root the rezound
4. Found rEZoundRoot 1.5 - Tried it and obtained root.
5. Updated SuperUser app, verified root access worked
6. Installed clockwork touch recovery as per the video playlist above
7. At this point i kept reading about all the ICS ROMs out there and decided that's what i was going to update. Noticed that it looked just easier to update the firmware and S-OFF before putting a custom ROM on
8. downloaded the RUU 3.14.605.5. and flashed to phone.
9. during this process i had to relock the bootloader, so i had to unlock again.
10. The RUU also updated firmware
11. Followed the S-OFF directions by running ControlBear for 3.14.605.5
12. Here's where it gets weird. First of all it took me about 10 times to get the wire trick down. but once i finally did, the phone jacked up? along the way (not sure what happened, but there was a picture of a phone with a red triangle with an exclamation point in it). By the time this showed up, ControlBear had timed out. I then pulled battery and restarted. checked bootloader and it's showing S-OFF now. Fully booted phone and it started just fine. Figured everything was OK and continued on
13. After the phone booted i noticed superuser was no longer installed (since the RUU update) I redownloaded. Tried to update, and that's where it failed gaining root access. I then tried to re-root with rEZoundRoot 1.5 and that didn't work (still no root access). Then tried with OneClickRoot 1.1, this time it did much more than the first time, appearing to work. Phone rebooted but still no root.
This is now where i'm at... Stuck with S-OFF and RUU 3.14.605.5 and NO ROOT. Anyone have any ideas??
This is what my hboot says:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
The "TAMPERED" was never there until one of the final steps above. Not sure if that has something to do with it or not.
Basically all i want to do is have rooted phone with the newest firmware and S-OFF. Then apply any custom ROMs from there as I see fit.
If anyone can help, it'd be greatly appreciated! Thanks in advance.
Click to expand...
Click to collapse
When you flashed the RUU, you lost root and should have rerooted before running the controlbear. The controlbear requires root and maybe that is what led to your problem. I s-offed first and then updated the firmware. I then had to flash Amon-RA recovery in a PH98IMG file and install SU (through the recovery's advanced menu) to regain root. Finally was able to flash the ROM of my choice.
Thanks for the replies! I actually found a fix LATE last night which worked great. I would've posted the URLs for reference, but I can't... So here's a snipit of that post:
I went back to unlimited dot io, downloaded the ICS hboot package for vigor, and followed the instructions:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
I also had to:
fastboot reboot
That last line was left out of the instructions. Good thing I found that in some random forum thread, because I thought something had failed: the progress bar on the HTC screen during 'flash zip' just sits there at like 3/4 full. Anyway, once I did that, I rebooted back to fastboot and was able to flash Amon Ra. Then I booted to Amon Ra recovery, mounted the external SD card over USB and copied up the SuperUser zip package at androidsu dot com, unmounted USB, went to flash zip menu, and installed that. Rebooted to Android and I now have root.
Click to expand...
Click to collapse
Following all of that seemed to work in my case, but now seeing what TopGun wrote, I just had the order of things wrong... Good to know for next time and just happy I got it taken care of!
Thanks for the replies everyone.
Related
Hi,
Well, i got myself into this mess and after 3 days of trying to fix it, i give up and call for your assistance.
I had a working S-ON HBOOT 0.47 rooted Legend running CM7.2 and recently changed to Jelly_Bean_Extras_HomICS_2.0_Venus.
I liked the new rom but link2sd didn't work.
My guess was that i need to have it S-OFF.
So... i headed to HTCDEV but first i needed to be on one of the listed RUU.
My original RUU was RUU_Legend_HTC_ISR_2.05.461.52_Radio_47.39.35.09_7.08.35.21_release_140015_signed.zip
I used the LEGEIMG.zip method to flash the RUU and then i flashed the one from HTCDEV which holds "hboot_legend_7227_1.02.0000_111223.nb0" only.
Now the HBOOT got to be 1.02.0000
After flashing this, i got stuck.
No recovery - i get signature failed message - even after putting CWM update.zip on the SD.
No ADB - at all states, only fastboot sees the device.
RUU update gets fails either due to version 3.30.0000, signature or device.
fastboot flash - i thought i will manually flash the various parts. i get FAILED (remote: signature verify fail).
CID was HTC__K18
did a new goldcard based on the old mail i had (from 2010) with the goldcard file (thank you gmail).
but nothing seems to help.
I read a lot of forum posts and tried many things over these 3 days but i'm willing to start over, step by step, with anyone willing to assist.
Hopefully this step by step will assist me and will be a reference guide for others.
Guy
guyvago said:
Hi,
Well, i got myself into this mess and after 3 days of trying to fix it, i give up and call for your assistance.
I had a working S-ON HBOOT 0.47 rooted Legend running CM7.2 and recently changed to Jelly_Bean_Extras_HomICS_2.0_Venus.
I liked the new rom but link2sd didn't work.
My guess was that i need to have it S-OFF.
So... i headed to HTCDEV but first i needed to be on one of the listed RUU.
My original RUU was RUU_Legend_HTC_ISR_2.05.461.52_Radio_47.39.35.09_7.08.35.21_release_140015_signed.zip
I used the LEGEIMG.zip method to flash the RUU and then i flashed the one from HTCDEV which holds "hboot_legend_7227_1.02.0000_111223.nb0" only.
Now the HBOOT got to be 1.02.0000
After flashing this, i got stuck.
No recovery - i get signature failed message - even after putting CWM update.zip on the SD.
No ADB - at all states, only fastboot sees the device.
RUU update gets fails either due to version 3.30.0000, signature or device.
fastboot flash - i thought i will manually flash the various parts. i get FAILED (remote: signature verify fail).
CID was HTC__K18
did a new goldcard based on the old mail i had (from 2010) with the goldcard file (thank you gmail).
but nothing seems to help.
I read a lot of forum posts and tried many things over these 3 days but i'm willing to start over, step by step, with anyone willing to assist.
Hopefully this step by step will assist me and will be a reference guide for others.
Guy
Click to expand...
Click to collapse
Have actually flashed hboot 1.02 yet?
Have followed ALL the instructions at htcdev?
Have you followed all the instructions sent to you via email about how to unlock the locked hboot 1.02, the email also includes a unlock.bin attached to the email which you need in order to unlock your boot loader?
If you had read ANY of the other question thread about this subject (there are a few) you would have found out that after you unlock your boot loader with hboot 1.02 you can no longer use update.zip cwm recovery, you can only use the S-OFF recovery method...
Sent from my Legend using xda app-developers app
I was expecting feeling stupid, missing something simple.
Originally, I couldn't get to step 8 since it requires that the unit didn't respond to fastboot command and while trying to find a fix, i got stuck with only fastboot and didn't remember that this was the step i was stuck in.
Anyway, your response had me go back to htcdev just to prove my point and i found that i can continue.
Finally.
Now i am unlocked and can continue with S-OFF methods.
Thank you.
Guy
Currently the phone starts with:
*** LOCKED (OOW) ***
LEGEND PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0816
TOUCH PANEL-SYN07_0103
RADIO-7.08.35.21
Dec 23 2011, 16:36:48
Guy
Have actually flashed hboot 1.02 yet?
Have followed ALL the instructions at htcdev?
Have you followed all the instructions sent to you via email about how to unlock the locked hboot 1.02, the email also includes a unlock.bin attached to the email which you need in order to unlock your boot loader?
If you had read ANY of the other question thread about this subject (there are a few) you would have found out that after you unlock your boot loader with hboot 1.02 you can no longer use update.zip cwm recovery, you can only use the S-OFF recovery method...
Click to expand...
Click to collapse
Guess what, your phone is still locked, you typed it yourself, you still need to unlock it using the bin file sent to you in the email.
Don't feel stupid mate, this rooting thing can be confusing and fearsome at times. Even I had that "can't use update.zip" issue and thought my phone was f'ed till I realised I needed to flash the recovery image.
Sent from my Legend using xda app-developers app
ok.
now everything is ok.
flashed cwm.
got the rom back
and restored almost everything.
thank you
just to point out
Jelly_Bean_Extras_HomICS_2.0_Venus is not ROM
If you flashed a good ROM and your stuck in hboot, use fastboot and use the following command 'fastboot oem boot' that should force your phone to boot.
K… Bought a HTC Amaze 4G through Telus. I travel a lot and need to be able charge the phone on the road so i was using any charger that would fit in the port to charge the device. This gave my serious battery life problems. Brought the phone back to Telus. They gave me a new battery, but i had the same results.
So I,
- Unlocked the bootloader (through HTC.Dev)
- Rooted the phone with HTC Super Tool V3
- Installed Battery Cal App from the market place
- Bumped charged to battery until i figured it was full
- Then reset the Battery Cal file
Once i tested the battery and found it to be like new i,
- Flashed CWM recovery and backed up the phone.
All was well till Telus OTA'ed ICS. I tried to update and could not. I read on all the XDA forums you cannot OTA update with root/custom recovery/blah, blah, blah….
I tried to,
- Unroot with HTC Super Tool V3. Nope
- Unroot with ADB. Nope
- Re-locked the bootloader and unlocked a couple of times trying different things. At this point the phone still worked as a phone. Just would not OTA update.
So i decided to try S-Off with Hasoon's Amaze S-off All In One Kit V1.0. Then maybe flash Energy Rom. I tried for a couple of days. First i had ADB issues. Wiped laptop. New ADB. Then it kept giving me Errorcode: 66732337 ErrorMsg: Still sober. I could not boot the phone anymore. Just to Hboot. After a weekend of this i kept reading and found to get back to stock all i had to do was flash RUU through Hboot. Then i could get the OTA. So I,
- Found RUU_Ruby_TELUS_WWE_1.41.661.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_222694_signed.exe
- Zipped it and renamed it PH85DIAG.zip
- Put it on root of SD card
- Booted in Hboot
Then the phone,
- Loaded the .zip (blue bar on the right)
- Checked the .zip (orange bar on the right)
But it does not return to stock. Then i read this "return to stock" method only works if you are using stock recovery. So i,
- found stock recovery from Telus-1.41-Restore-Flasher
- flash recovery with Fastboot
But the phone still does not return to stock.
At this point the phone only boots to Hboot. It says,
*** RELOCKED ***
*** Security Warning ***
Ruby PVT SHIP S-ON RL
HBOOT-1.90.0006
eMMC-boot
I just want to return to stock and get the Telus OTA. I don't know what i am doing wrong. Do i need lock the bootloader not relock the bootloader. Do i have the wrong Hboot or something.
THX
Have you tried Hasoon's All-in-one Toolkit?
When using the ruu signed exe file, you do not zip it and rename it to anything, simple boot the device into hboot, select fastboot, plug in the usb cable and run the ruu exe file on your pc, follow all on screen instructions then let it update the device, once complete, let it boot full, then check for software update via settings to install the ICS ota from TELUS.
kered424 said:
Have you tried Hasoon's All-in-one Toolkit?
Click to expand...
Click to collapse
I have Hasoon's HTC Amaze All-In-One Kit V3.2. How do i use it to return to stock?
Dark Nightmare said:
When using the ruu signed exe file, you do not zip it and rename it to anything, simple boot the device into hboot, select fastboot, plug in the usb cable and run the ruu exe file on your pc, follow all on screen instructions then let it update the device, once complete, let it boot full, then check for software update via settings to install the ICS ota from TELUS.
Click to expand...
Click to collapse
See.... now i feel like an idiot!!! Ran Telus RUU .exe and it worked like a charm. Anyway, THX guys!!!:good::good: Got my OTA.
It's been awhile since I've had a chance to get back to xda, so when I saw the htc dev bootloader unlock method, I jumped at the chance to unlock my version 1.5 bootloader and be able to get root without downgrading. However, just a few days later, the Ics ota was released. I had
1. unlocked my bootloader VIA HTC dev method,
2. Flashed twrp from command prompt, and
3. Flashed Su from twrp.
In a nutshell, I had root but was on a stock 2.17 ruu (latest gingerbread ruu) and had root. In order to try to revert to stock, I used the command "fastboot oem lock" to relock my EVO (cdma) so i could ota update, because when i tried to with root, I simply was booted into twrp.
So, after locking (and also removing the recovery.img from my sdcard) my bootloader, I tried to ota, which only put me into my bootloader with a message under "relocked"(at the top of the screen in bootloader) which said "security warning". I've tried to run the 2.17 ruu when in fastboot (because it would only give me security warning otherwise) but there was pretty much no visible effect on my phone. The ruu said it ran successfully, but after booting up I still had Su, and none of my app data had been deleted. I also couldn't do a factory reset from the OS or from bootloader. If anybody could help me get to ics anything, or at least back to stock w/o root (,so i can apply the ota and go from there) it would be greatly appreciated.
As a sidenote, I haven't used the ruu.zip method (PG86IMG.ZIP).
Ryoma Echizen said:
It's been awhile since I've had a chance to get back to xda, so when I saw the htc dev bootloader unlock method, I jumped at the chance to unlock my version 1.5 bootloader and be able to get root without downgrading. However, just a few days later, the Ics ota was released. I had
1. unlocked my bootloader VIA HTC dev method,
2. Flashed twrp from command prompt, and
3. Flashed Su from twrp.
In a nutshell, I had root but was on a stock 2.17 ruu (latest gingerbread ruu) and had root. In order to try to revert to stock, I used the command "fastboot oem lock" to relock my EVO (cdma) so i could ota update, because when i tried to with root, I simply was booted into twrp.
So, after locking (and also removing the recovery.img from my sdcard) my bootloader, I tried to ota, which only put me into my bootloader with a message under "relocked"(at the top of the screen in bootloader) which said "security warning". I've tried to run the 2.17 ruu when in fastboot (because it would only give me security warning otherwise) but there was pretty much no visible effect on my phone. The ruu said it ran successfully, but after booting up I still had Su, and none of my app data had been deleted. I also couldn't do a factory reset from the OS or from bootloader. If anybody could help me get to ics anything, or at least back to stock w/o root (,so i can apply the ota and go from there) it would be greatly appreciated.
As a sidenote, I haven't used the ruu.zip method (PG86IMG.ZIP).
Click to expand...
Click to collapse
You don't need to upgrade to ics to get a custom ics rom, if that's what your asking. Reunlock, and check out the development forums and find an ics rom that works with 2.17 (eg, cool sense, meanrom, homebrew, common sense [my rom lol]). Go ahead and flash one, and enjoy ics
Stay on 2.17 though, first rule: NEVER accept ota. It's kinda rule of thumb. I learned the hard way.
Sent from my EVO 3DMA with a little "common sense"
I assume you're s-on..
You said you tried the ota and it took you to the hboot. Did it upgrade your hboot to 1.58?
I think the security warning is due to having a custom recovery (i think)
Wikd said:
I assume you're s-on..
You said you tried the ota and it took you to the hboot. Did it upgrade your hboot to 1.58?
I think the security warning is due to having a custom recovery (i think)
Click to expand...
Click to collapse
Yeah I checked out some other threads (none for the 3d though) and they said pretty much that it did have to do with the custom recovery like you said. And you are right on the other two counts, but no, it didn't upgrade me to 1.58, I'm still on 1.5.
Alright, thanks! I'll try to re-unlock using the HTC method(I'm assuming ill need to get another unlock_code.bin since the one I used isn't working anymore for some reason). I'll post again and let you know how it goes.
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 !
The back story...
I had to ditch Verizon. I didn't want to fork over $300 for a Republic Wireless phone only to be stuck with their crappy ROM, and the only 4G LTE android phone supported by Ting is the Evo 4G LTE; picked one up for $50 on ebay. I installed Cyanogenmod on a half dozen devices, newer and older than this phone, and thought this HTC Evo 4G LTE would be as easy as they were to unlock, root, S-OFF and flash. I've been more wrong before, but not without resulting in bodily harm. A hearty 'get stuffed' to HTC for this, and a plea for future rooters to have a concise guide on how to repair their phone under these circumstances.
The flawed process...
I went through HTC's unlock method to unlock the phone. Then I installed the latest TWRP via fastboot command line (2.7.1.0b as I found in a thread somewhere). No problems so far... I then went to install the latest CM build for Jewel (10.2.0 ) through TWRP 2.7.1.0b and it failed. This marked the first time I'd ever seen a fail message in TWRP. I thought no big deal, I'll restore the backup... The backup was gone. Now we have problems; phone is stuck in a bootloop. After reading many threads stating that S-OFF is required to flash their ROM, I tried to achieve that in Windows 7 to no avail through all available means. I then tried the closest RUU for my phone, and it failed. I then tried every RUU I could find, all failed. I tried a full firmware update to 4.13 via PJ75IMG.zip on the SD card, which failed.
The repair process that worked for my situation...
Once I focused on the HBOOT as a potential issue, I found this thread: http://forum.xda-developers.com/showthread.php?p=40848479#post40848479
Quite simply, MeanBean 3.09 worked as advertised, and my phone has booted into a ROM for the first time in days! A HUGE thanks to both Magnum_Enforcer and mikeyxda.
Specific phone information
TAMPERED
UNLOCKED
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.13.11.0830
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012, 15:46:20
IMAGE CRC
rpm: 0xBC1CB8D
sbl1: 0x507A9B32
sbl2: 0xEAF345D0
sbl3: 0xD5BB18AD
tz: 0xFB084399
radio: 0xC78A66EB
boot: 0xB683E2D
recovery: 0xB47A92E4
system: 0x376A0C9B
Software Version Reported by RUU: 3.17.651.5
Glad to help:thumbup:
Sent from my HTC device
I'm going to keep this log going, since I think quite a few people will follow a similar path as I'm following.
Just tried to achieve S-OFF with the new MeanBean ROM I'm running.
First attempt: Firewater
All of the steps went exactly as expected. The command line dialog was amusing, and ended in "nasty, needs a chaser" or something and rebooted to the ROM. Once rebooted into recovery to verify s-off status, S-ON is reported.
Second attempt: Rumrunner
More interesting dialog in the process, and it, too, went smoothly. Rebooted into bootloader and voila...S-OFF achieved.
Installed Dirty Unicorns 4.4.4
So, after the first day's use I've come to realize that my PRL needs updating and the Dirty Unicorn 4.4.4 ("du_jewel_4.4.4_20140621-0657") ROM doesn't have a 'Update PRL' function as far as I can tell. I backed up DU 4.4.4 and restored MeanBean, updated the PRL, and restored back into DU 4.4.4 with ease.
After using DU for a week, I've come to realize it's fairly unstable. I'll be looking for a different rom soon.
OMG!!!! FINALLY!!!
I've been reading and reading and pulling my hair out for 3 days after attempting to load a custom Rom on my Evo 4G LTE.
I have almost exactly the same situation/experience as you did. I was able to get the CyanogenMod to load but for the life of I can't get any gapps installed. I've tried loading from TWRP and the SDcard to no avail. It looks like it flashes fine but when I reboot the phone no apps are installed. I like CM 10.2.0 but I need the Google apps. Right now I'm missing so many things like contacts, etc. I've tried to install Google Play and just download each app individually but it crashes on start. I'm really feeling lost here and helpless. I never had problems like this with my original EVO or EVO 3D. Tried to go back to stock using Sprint RUU's but nothing works...
I've highlighted my differences in RED.
Is there anyway you could explain your method to get your EVO S-off in more detail? Is this the problem?
SethW said:
The flawed process...
I went through HTC's unlock method to unlock the phone. Then I installed the latest TWRP via fastboot command line (2.7.1.0b as I found in a thread somewhere) (I loaded TWRP 2.7.1.0 which seemed to work) . No problems so far... I then went to install the latest CM build for Jewel (10.2.0 ) through TWRP 2.7.1.0b and it failed (I was able to load CM 10.2.0 through Fast Boot boot.img command) . This marked the first time I'd ever seen a fail message in TWRP. I thought no big deal, I'll restore the backup... The backup was gone (Same here, Backup gone). Now we have problems; phone is stuck in a bootloop (I watched the CyanogenMod screen spin for 2 hours). After reading many threads stating that S-OFF is required to flash their ROM, I tried to achieve that in Windows 7 to no avail through all available means (same here, tried several ways but nothing worked for Windows 7). I then tried the closest RUU for my phone, and it failed (same here). I then tried every RUU I could find, all failed. ( I tried a full firmware update to 4.13 via PJ75IMG.zip on the SD card, which failed.
Specific phone information My Info is exactly the same
TAMPERED
UNLOCKED
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.13.11.0830
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012, 15:46:20
Software Version Reported by RUU: 3.17.651.5
Click to expand...
Click to collapse
airdog99 said:
Is there anyway you could explain your method to get your EVO S-off in more detail? Is this the problem?
Click to expand...
Click to collapse
I just ran the program as it specified. Make sure your drivers are installed correctly... that step usually caught me up because some Android device drivers conflicted with some of my other Android device drivers.