I have to ship my hox+ back soon and for some reason the ruu doesn't work I get bootloader version error. This is the ruu that I have been using RUU_EVITARE_UL_JB_45_Cingular_US_1.15.502.9_Radio_1.09.55.17_18.20.95.55L_release_290329_signed.exe. Any help would be much appreciated I need to get this thing back to stock.
Has your phone already booted into hboot when you get that error? I had a similar error (maybe the same one) when I was flashing the 1.15 stock 2 weeks ago because the phone didn't boot into hboot on its own. I put the phone into hboot after relocking the bootloader. Then ran the RUU and it worked perfectly.
are you on Hboot 1.40? If so, you'll probably want to use the 1.19 RUU.
Where is the 1.19? I've only found the one I'm using.
EDIT:I am running HBOOT 1.40 I will try running the ruu again and see if it works this time.
Found it http://forum.xda-developers.com/showthread.php?t=2238839
Sent from my HTC One X using Tapatalk 2
You can also get the 1.19 RUU from HTC's website.
Related
I have S-off and my hboot reads 2.21 .0000. I've noticed on other people's devices the hboot is 2.11.1111. What's the difference?
Sent from my ADR6425LVW using xda premium
cam1pbell said:
I have S-off and my hboot reads 2.21 .0000. I've noticed on other people's devices the hboot is 2.11.1111. What's the difference?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Ones GB the other ICS
Sent from my ADR6425LVW using Tapatalk 2
The 2.21 is ics and 2.11 is gb.
Sent from my ADR6425LVW using xda premium
Once I get S-OFF I can just flash the latest GB OTA RUU and that should bring me back to HBoot 2.11?
I'm already on ICS firmware but want to go back to out of the box stock GB.
Sent from my ADR6425LVW using Tapatalk 2
GoldenCyn said:
Once I get S-OFF I can just flash the latest GB OTA RUU and that should bring me back to HBoot 2.11?
I'm already on ICS firmware but want to go back to out of the box stock GB.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Yap. The ruu will drop you back to 2.11 and also reinstall the older radios. I did this right after obtaining S-OFF to start with a fresh phone. I am now on GB firmware(ENG hboot) running ICS using the old firmware patch.
ih8mydroid said:
Yap. The ruu will drop you back to 2.11 and also reinstall the older radios. I did this right after obtaining S-OFF to start with a fresh phone. I am now on GB firmware(ENG hboot) running ICS using the old firmware patch.
Click to expand...
Click to collapse
thanks, I can't wait to get home and do this.
Sent from my ADR6425LVW using Tapatalk 2
ih8mydroid said:
Yap. The ruu will drop you back to 2.11 and also reinstall the older radios. I did this right after obtaining S-OFF to start with a fresh phone. I am now on GB firmware(ENG hboot) running ICS using the old firmware patch.
Click to expand...
Click to collapse
So you ran the full gb ruu and your hboot downgraded to 2.11 but still s-off/locked correct? Then you fastboot flashed the 2.11 eng hboot correct?
Just asking because I will try this later.
HTC Rezound via TT2
Ok, I'm confused on one thing, at what points from s-off to gb ruu to eng hboot do I have to lock and relock?
Sent from my ADR6425LVW using Tapatalk 2
GoldenCyn said:
Ok, I'm confused on one thing, at what points from s-off to gb ruu to eng hboot do I have to lock and relock?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I just tried this running the juopunutbear modified hboot 2.21 s-off locked. I ran the full gb ruu, bootloader no longer said juopunutbear, it just showed a stock 2.11 locked s-off. I flashed the 2.11 eng hboot in fastboot. Now it shows locked, hboot 2.11 eng s-off. No issues at all. I never once had to unlock.
HTC Rezound via TT2
cdexsw said:
I just tried this running the juopunutbear modified hboot 2.21 s-off locked. I ran the full gb ruu, bootloader no longer said juopunutbear, it just showed a stock 2.11 locked s-off. I flashed the 2.11 eng hboot in fastboot. Now it shows locked, hboot 2.11 eng s-off. No issues at all. I never once had to unlock.
HTC Rezound via TT2
Click to expand...
Click to collapse
Ok but right now I'm on ICS firmware from the ICS Leaked RUU and HBoot 2.21 and at the top of the bootloader it says Tampered ReLocked.
So your saying that at no point do I need to unlock? I'm gonna go home and s-off the run the GB OTA RUU and then flash Amon Ra recovery and possibly flash ENG HBoot, and I don't need to unlock?
Sent from my ADR6425LVW using Tapatalk 2
GoldenCyn said:
Ok but right now I'm on ICS firmware from the ICS Leaked RUU and HBoot 2.21 and at the top of the bootloader it says Tampered ReLocked.
So your saying that at no point do I need to unlock? I'm gonna go home and s-off the run the GB OTA RUU and then flash Amon Ra recovery and possibly flash ENG HBoot, and I don't need to unlock?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
The unlock is useless once you obtain s-off.
The ***tampered*** is showing because you are still using the stock 2.21 hboot. If you flash the juopunutbear modified hboot in fastboot you will no longer see the ***tampered*** or the ***locked*** in the hboot, it will only show Juopunutbear at the top.
here are 3 pictures to better explain using the 2.21 hboot.
left: unlocked/s-on/tampered.
middle: locked/s-off/tampered
right: s-off/juopunutbear
juopunutbear is a modified 2.21 hboot, almost like a eng hboot for ONLY ics firmware,
make sense?
Yes but do I have to take the jbear hboot during s-off? I just want to go back to GB and I don't mind using the GB HBoot. I may try the ENG HBoot after I'm on GB HBoot.
Sent from my ADR6425LVW using Tapatalk 2
rename jb_hboot.zip found in the "controlbear" folder to PH98IMG.zip and flash it as you normally flash a PH image.
that will change your hboot to their modified version where is says juopunutbear.
**ONLY IF YOU ARE ON THE HBOOT 2.21**
---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------
GoldenCyn said:
Yes but do I have to take the jbear hboot during s-off? I just want to go back to GB and I don't mind using the GB HBoot. I may try the ENG HBoot after I'm on GB HBoot.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
i did not take it. i flashed it manually as i heard others saying it did not flash. so i skipped it and did it myself.
as far as downgrading a stock hboot 2.21 s-off to to stock 2.11 s-off i do not know...i see no reason why you cannot?
the gb ruu will give you a stock 2.11 anyway while keeping your status to s-off.
i will try later tonight. i just came back from the doctors a little nauseated from some meds....
cdexsw said:
rename jb_hboot.zip found in the "controlbear" folder to PH98IMG.zip and flash it as you normally flash a PH image.
that will change your hboot to their modified version where is says juopunutbear.
**ONLY IF YOU ARE ON THE HBOOT 2.21**
---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------
i did not take it. i flashed it manually as i heard others saying it did not flash. so i skipped it and did it myself.
as far as downgrading a stock hboot 2.21 s-off to to stock 2.11 s-off i do not know...i see no reason why you cannot?
the gb ruu will give you a stock 2.11 anyway while keeping your status to s-off.
i will try later tonight. i just came back from the doctors a little nauseated from some meds....
Click to expand...
Click to collapse
Now I get it, thanks cdexsw. Basically it doesn't matter because the gb ota ruu will bring me back to gb hboot anyway. Thanks a bunch guys.
Sent from my ADR6425LVW using Tapatalk 2
No authority here, but just passing along a couple of things as they were explained to me:
1. Even with S-off, you might not be able fastboot flash (installing recovery, for example) while locked. Alternatives would be to either unlock, install the ENG HBOOT, or flash with PH98IMG.zip.
2. Also, I believe there was a big note in a thread saying that you could brick your phone by relocking over the ENG HBOOT. The instructions were to restore the correct HBOOT for your configuration before relocking.
As for me, I decided that I do enough flashing that I want fastboot commands to work, and I'm less afraid of resetting everything to restore my phone to factory "LOCKED" indicator than I am afraid of reflashing the only thing that absolutely must be intact to keep from bricking the phone. So I unlocked the stock loader despite having s-off already.
cpurick said:
No authority here, but just passing along a couple of things as they were explained to me:
1. Even with S-off, you might not be able fastboot flash (installing recovery, for example) while locked. Alternatives would be to either unlock, install the ENG HBOOT, or flash with PH98IMG.zip.
2. Also, I believe there was a big note in a thread saying that you could brick your phone by relocking over the ENG HBOOT. The instructions were to restore the correct HBOOT for your configuration before relocking.
As for me, I decided that I do enough flashing that I want fastboot commands to work, and I'm less afraid of resetting everything to restore my phone to factory "LOCKED" indicator than I am afraid of reflashing the only thing that absolutely must be intact to keep from bricking the phone. So I unlocked the stock loader despite having s-off already.
Click to expand...
Click to collapse
#1 is definitely up for debate but so far I have had no issues using fastboot to flash recoveries and kernels. I tested this stock hboot 2.11 and 2.21 with locked s-off.
#2 I was advised not to try when this question was asked from another thread. I would not even want to. the chances of big brother actually checking for s-on/s-off or locked/unlock/relocked is slim to none.....i would not even bother with an s-on command.
I am currently locked on 2.11 eng s-off running RezROM S4 v1.1 with his firmware patch. phone has great battery life, no data loss and operates much much cooler
My original 1.30 hboot that i had died and sprint gave me a new one of course it had 1.50 and 2.17 on it. So i downgraded the hboot 1.40 and now stuck at security warning. Im assuming its because the wrong software is detected for the 1.40 and its throwing a fit. anyone have a link to the one i can flash now either via PG86IMG or ruu.exe to make it where all i need to do now is then run revolutionary?
You need to flash the old ruu which I suppose is the 1.13 , and then run Revolutionary
Sent from my PG86100 using XDA
So I bought a phone from a guy on Craigslist, while it works fine, there's something weird here. What I want to do is have it S-OFF, but here's whats up:
Bootloader is HBOOT 2.21.0000. It says ***UNLOCKED*** but also it says ***TAMPERED***. Also it says VIGOR PVT SHIP S-ON RL.
Everything seems to be working fine; it currently has CleanROM 4.3 on it. I'm afraid to start doing anything until I know where to start. I *THINK* what I need to do is the following:
1. fastboot oem lock the bootloader
2. Flash latest ICS leak RUU twice.
3. Follow the Juopounut guide for S-OFF using the 2.21.0000 modified HBOOT
Does this sound right? Thanks for your help!
If its already unlocked, stay unlocked. Relocking it is going backwards toward s-off. Once s-off you will have a locked bootloader. I did not install the jbear modified hboot. I installed Amon ra as a ph img after s-off and ics ruu
You should just follow the jbear s-off instructions since you already have unlock
S-off prior to ics is my preferred method, if something goes wrong with the ruu, you're stuck.
Also, no need to unlock once you have s-off
I got it. I wanted to go back to the newest leak and then proceed. I flashed the latest leak RUU and then re-unlocked.
The ***TAMPERED*** appears once I flashed the amon-ra recovery. Guess thats normal on the ICS builds...
Mine does not show tampered. I am s-off, locked, ics 3.14 firmware with ruu hboot, amon ra recovery, running newts one xxx
in_retrospekt said:
Mine does not show tampered. I am s-off, locked, ics 3.14 firmware with ruu hboot, amon ra recovery, running newts one xxx
Click to expand...
Click to collapse
Yep mine doesn't either. I'm just guessing but I think it might only been the 3.11.605.22 leak that did that.
Sent from my Sense4 ICS Rezound
Mine doesn't show it now that its truly S-OFF. Thanks all!
Is it possible with hboot 1.19 s-on running MeanBean? If so what method? I tried dirty racun and it failed on the on the step fastboot oem rebootRUU and black screen with HTC. Then wouldn't flash RUU. t/u
Ruu when in bootloader. Then unlock and then run racun.
Sent from my EVO using xda premium
Last weekend I relocked my phone then ran the RUU and took the OTA then unlocked and rooted again. I couldn't get Racun to work for me either.
Sent from my EVO using xda premium
T/u
I will most likely try the unroot method since I have tried the racun and was stuck with a phone not working for a while.
What RUU
xbmoyx said:
Last weekend I relocked my phone then ran the RUU and took the OTA then unlocked and rooted again. I couldn't get Racun to work for me either.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
What RUU did you use or what post did you follow. Asking so when i do this this evening i don't get stuck and have to do a lot of reading. t/u
kaw900r said:
What RUU did you use or what post did you follow. Asking so when i do this this evening i don't get stuck and have to do a lot of reading. t/u
Click to expand...
Click to collapse
The RUU to use depends on your hboot, for example, if youre on hboot 1.15 use RUU 1.22.651.3 - HBOOT 1.15
for hboot 1.19 use RUU 2.13.651.1 - HBOOT 1.19
The best guide to follow is the unlimited guide from their site, they will acutally support your efforts live! I used this method and I was able to gain s-off, unlock my bootloader and root; here's the link (it contains eveything you need including the RUU):
http://unlimited.io/jewel.htm
kcsween said:
The RUU to use depends on your hboot, for example, if youre on hboot 1.15 use RUU 1.22.651.3 - HBOOT 1.15
for hboot 1.19 use RUU 2.13.651.1 - HBOOT 1.19
The best guide to follow is the unlimited guide from their site, they will acutally support your efforts live! I used this method and I was able to gain s-off, unlock my bootloader and root; here's the link (it contains eveything you need including the RUU):
http://unlimited.io/jewel.htm
Click to expand...
Click to collapse
That is the one I was using and failed on step 8 second command went to black screen with HTC in center and nothing after that. Then failed to load the RUU. I am on HBOOT 1.19. I will look at it again tonight and might give it a try again.
I am trying to flash my phone with the RUU 2.13 so I can get the new firmware and flash meanbean. I am following this post (http://forum.xda-developers.com/showpost.php?p=31520093&postcount=11730) to do so. After following what Captain says, which is to relock the bootloader I can't get past the bootloader (which I now understand is normal right?) and then try to run the RUU through HBOOT, however I get the USB error. Is this due to the bootloader being relocked or am I missing the htc drivers on my computer?
Also, I'd rather go to S-Off, so if anyone could shed some light on how I would go from S-On to S-Off I would greatly appreciate it.
Which firmware are you trying to get on your phone? Because the way I'm reading it is you're using the older ruu file to try to get the newest firmware. Just wanna make sure you're using the newest ruu of 3.15 (came out December 22).
Sent from my EVO using xda app-developers app
onefasttreopro said:
Which firmware are you trying to get on your phone? Because the way I'm reading it is you're using the older ruu file to try to get the newest firmware. Just wanna make sure you're using the newest ruu of 3.15 (came out December 22).
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Ya wow can't believe how long it's been since I've flashed a rom. An old version of MeanRom has lasted me so long. I am on an old firmware (1.13) I believe. I want to preferably go from S-On to S-Off. Before, I tried Captain Throwbacks method (relocking the bootloader, flashing the RUU) however I ran into a USB Connection Problem with the RUU. So I am trying to figure out if it was because I didn't have the right htc drivers installed or something else. If S-On to S-Off would eliminate the need for those steps I would much rather do that. I am trying to get to the latest firmware. Thanks!
What Hboot are you on?
Edit: If you're on 1.12 you're going to have to go the Dirty Racun route, since Lazy Panda is no longer officially supported. This, of course, requires you to RUU to upgrade to either Hboot 1.15 or 1.19, then run Dirty Racun to get S-off. Getting S-off is definitely the way to go, as it can save you some headache down the road. Also, don't run the RUU for 3.15 (JB) as this will update your Hboot and currently there is no exploit to get S-off with the new Hboot. You can still unlock and root it, but you'll be S-on.
Sent using my HTC EVO LTE and a magic wand
FinZ28 said:
What Hboot are you on?
Sent using my HTC EVO LTE and a magic wand
Click to expand...
Click to collapse
^^^^What he said
Sent from my EVO using xda app-developers app