Unsure what happened. Phone has been rebooting and overheating for days so I went to RUU it and after I relocked the bootloader my phone decided not to go past bootloader anymore. When I try RUU I get Error 140 Bootloader Version Error. My bootloader has a Security Warning at the top which was not there before. I would like to RUU and get S-OFF so I can take the phone in without issue but am having no luck.
Some more info would be useful. What Hboot & baseband are you currently on, and what RUU did you try to run?
Sent from my EVO using xda premium
FinZ28 said:
Some more info would be useful. What Hboot & baseband are you currently on, and what RUU did you try to run?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
The 3.15 RUU and HBoot 2.09 I dunno basebands. If there is a working 3.16 RUU that would be helpful but there isn't...
Vysse said:
The 3.15 RUU and HBoot 2.09 I dunno basebands. If there is a working 3.16 RUU that would be helpful but there isn't...
Click to expand...
Click to collapse
Baseband is your radio version, and you can check it in the bootloader.
Sent from my EVO using xda premium
FinZ28 said:
Baseband is your radio version, and you can check it in the bootloader.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
1.12
Vysse said:
1.12
Click to expand...
Click to collapse
The radio version is directly below the Hboot version. That looks like the Hboot version. Boot into the bootloader and list the info displayed in the top left corner of the screen, all the way down to the radio version.
You relocked so you'll need to unlock again. You may even need to install a recovery again. What ROM/kernel combo were you on? If you were on a custom kernel, I would try a different one or stick with stock. Some kernels don't play well with certain phones, especially if you're overclocking or changing the voltage any. For now, try unlocking and getting the phone up and running again.
Also, gaining S-off is highly recommended
Sent from my EVO using xda premium
FinZ28 said:
The radio version is directly below the Hboot version. That looks like the Hboot version. Boot into the bootloader and list the info displayed in the top left corner of the screen, all the way down to the radio version.
You relocked so you'll need to unlock again. You may even need to install a recovery again. What ROM/kernel combo were you on? If you were on a custom kernel, I would try a different one or stick with stock. Some kernels don't play well with certain phones, especially if you're overclocking or changing the voltage any. For now, try unlocking and getting the phone up and running again.
Also, gaining S-off is highly recommended
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hboot is 2.09 Radio is 1.12 I cannot unlock because it won't write. I cannot seem to do anything. I tried using the Unbricking tool but it does not recognize my device. I think this issue started when I tried to lock after a failed s-off attempt.
What do you mean when you say it won't write?
Also, for your radio, use the last four digits, not the ones at the beginning.
Sent from my EVO using xda premium
FinZ28 said:
What do you mean when you say it won't write?
Also, for your radio, use the last four digits, not the ones at the beginning.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Full Radio is 1.12.11.1210 and when I flash something via fastboot it sends it then has a write error. I have tried flashing RUU's, recovery, my unlock_code all to no avail. I tried using the unbricking tool but linux doesn't seem to see my device (I am new to linux). I appreciate the help btw.
You won't be able to use fastboot commands to push a recovery to your phone while it's relocked. Also, the RUU won't work because you're on a software version higher than the most recent RUU.
Sent from my EVO using xda premium
FinZ28 said:
You won't be able to use fastboot commands to push a recovery to your phone while it's relocked. Also, the RUU won't work because you're on a software version higher than the most recent RUU.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
This is where HTC screwed us with no recent ruu... Smh.
The the op... Have you gone through the steps to HTC Dev unlock again? What does it say when you send the unlock token?
Sent from my Evo 3D CDMA using Tapatalk 4 Beta
gunfromsako said:
This is where HTC screwed us with no recent ruu... Smh.
The the op... Have you gone through the steps to HTC Dev unlock again? What does it say when you send the unlock token?
Sent from my Evo 3D CDMA using Tapatalk 4 Beta
Click to expand...
Click to collapse
The unlock token won't write. Nothing will write. If there was a modified RUU that would help. If I could modify my version so the RUU would work that would work... and yeah HTC really screwed us...
Edit: Actually the unlock_code.bin writes but then nothing happens on the phone...
Update: took it to a sprint store and they fixed it. They apparently have 3.16 RUU. Or magic....
Sent from my EVO using xda app-developers app
Related
I rootrd my Thunderbolt using Jcase's manual method shortly after the phone was released. I have the following (unimportant or matching info omitted):
MECHA XD ENG S-OFF
HBOOT 1.04.2000
A friend just rooted using Revolutionary and he has the following:
MECHA XD SHIP S-OFF
HBOOT 6.04.1002
I've been reading some info about Revolutionary and it looks like the program essentially turns off security so you can install SuperUser and flash CWM Recovery. I assume it does not replace the stock (SHIP) bootloader. Does this limit the phone at all? Can he still flash radios through bootloader? What's the easiest/safest way to install the engineering bootloader, or is it even needed?
I noticed that bootloader and CWM both say Revolutionary as well now. Any modifications going on behind the scenes that I may need to know? I ask all of this because his phone has been force closing a lot and "messing up" so I'm going to be fixing it. I've onpy had my hands on the device for about 5 minutes so that's really all of the info I know about it.
Any/all feedback is appreciated!
Sent from my ADR6400L using Tapatalk
joshw0000 said:
I rootrd my Thunderbolt using Jcase's manual method shortly after the phone was released. I have the following (unimportant or matching info omitted):
MECHA XD ENG S-OFF
HBOOT 1.04.2000
A friend just rooted using Revolutionary and he has the following:
MECHA XD SHIP S-OFF
HBOOT 6.04.1002
I've been reading some info about Revolutionary and it looks like the program essentially turns off security so you can install SuperUser and flash CWM Recovery. I assume it does not replace the stock (SHIP) bootloader. Does this limit the phone at all? Can he still flash radios through bootloader? What's the easiest/safest way to install the engineering bootloader, or is it even needed?
I noticed that bootloader and CWM both say Revolutionary as well now. Any modifications going on behind the scenes that I may need to know? I ask all of this because his phone has been force closing a lot and "messing up" so I'm going to be fixing it. I've onpy had my hands on the device for about 5 minutes so that's really all of the info I know about it.
Any/all feedback is appreciated!
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Actually, Revolutionary does replace the bootloader. The difference between the ADB method and Revolutionary is that ADB uses a soft-patched engineering bootloader, whereas Revolutionary uses a hard-patched release version of the bootloader.
So basically what you're saying is I can flash another hboot over my hboot and it would take (i.e. I could act stupid and brick the phone) but if you use Revolutionary you can flash whatever in hboot but the actual hboot will not be replaced? Or is there a different meaning implied?
Sent from my ADR6400L using Tapatalk
joshw0000 said:
So basically what you're saying is I can flash another hboot over my hboot and it would take (i.e. I could act stupid and brick the phone) but if you use Revolutionary you can flash whatever in hboot but the actual hboot will not be replaced? Or is there a different meaning implied?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
As far as I know, the Revolutionary hboot is patched to prevent flashing over. I don't know all the ins and outs. Never used the newer hboot because... if it's not broke, I don't fix it.
Alright, thanks for sending your thoughts. I don't think anything with the rooting method is causing his problem. I'll reflash the official MR2, do a full wipe, and install a fresh rom. He'll be good as new.
Sent from my ADR6400L using Tapatalk
joshw0000 said:
Alright, thanks for sending your thoughts. I don't think anything with the rooting method is causing his problem. I'll reflash the official MR2, do a full wipe, and install a fresh rom. He'll be good as new.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
I hope you're not saying you're going to flash the MR2 RUU.... If you do you'll loose your recovery.
joshw0000 said:
So basically what you're saying is I can flash another hboot over my hboot and it would take (i.e. I could act stupid and brick the phone) but if you use Revolutionary you can flash whatever in hboot but the actual hboot will not be replaced? Or is there a different meaning implied?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Correct. The only way to overwrite revolutionary hboot (that i know of) is to flash a new one with adb.
Sent from my HTC ThunderBolt using Tapatalk
loonatik78 said:
I hope you're not saying you're going to flash the MR2 RUU.... If you do you'll loose your recovery.
Click to expand...
Click to collapse
No I flashed the MR2 radio only. I'm pretty sure he already had that radio but I did it just to make sure.
Sent from my ADR6400L using Tapatalk
First off, I've gone through thread after thread hoping to find an answer, but simply have not.
I rooted my phone back in July and don't remember which method I used. I need to get my phone back to stock for warranty (I have a dead strip on my screen) and before I thought, I used SU to get back to S-On, but now I can't get back to stock.
I've tried to run various RUU's, more specifically regaw's version among others, but I haven't had any success. Every time I run an RUU it says that my phone is not connected to my computer. I've also downloaded the PJ75IMG and tried that method as well, but nothing happens.
Phone: Evo 4g LTE
HBOOT: 1.12.000
ROM: UR/EVO 4G LTE SIX
SilverJaw said:
First off, I've gone through thread after thread hoping to find an answer, but simply have not.
I rooted my phone back in July and don't remember which method I used. I need to get my phone back to stock for warranty (I have a dead strip on my screen) and before I thought, I used SU to get back to S-On, but now I can't get back to stock.
I've tried to run various RUU's, more specifically regaw's version among others, but I haven't had any success. Every time I run an RUU it says that my phone is not connected to my computer. I've also downloaded the PJ75IMG and tried that method as well, but nothing happens.
Phone: Evo 4g LTE
HBOOT: 1.12.000
ROM: UR/EVO 4G LTE SIX
Click to expand...
Click to collapse
Do you have HTC Sync installed? I know that has been a issue for myself, if so uninstall that, and you will need to run the RUU for the Firmware you have. Also I have downloaded mine from this website. http://shipped-roms.com/index.php?category=android&model=Jewel
lloydw82 said:
Do you have HTC Sync installed? I know that has been a issue for myself, if so uninstall that, and you will need to run the RUU for the Firmware you have.
Click to expand...
Click to collapse
I don't have HTC Sync installed. How do you know which RUU will work for which firmware?
Sent from my EVO using xda app-developers app
In your settings under about -> Software Information -> More -> Baseband Version.... That will be the RUU you will Run, i had the same issue with my old EVO 3D
lloydw82 said:
In your settings under about -> Software Information -> More -> Baseband Version.... That will be the RUU you will Run, i had the same issue with my old EVO 3D
Click to expand...
Click to collapse
Got the correct firmware, started the process no problem. Now I've got an Error [155]: Unknown and that's as far as it'll take me. I've tried multiple times, and nothing happens. When the phone is supposed to restart it just sits there as if nothing happened to it at all. The RUU instructed me to restart the phone and do the recovery through the program. Once through, it says that I should now try to start the RUU again. and the same thing happens. Am I missing something here?
When running the RUU, are you getting a 155 Error Code?
Yeah, the Error 155 keeps coming up.
Sent from my EVO using xda app-developers app
SilverJaw said:
Yeah, the Error 155 keeps coming up.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Is your bootloader relocked?
lloydw82 said:
Is your bootloader relocked?
Click to expand...
Click to collapse
I have S-On but it still shows "tampered" and "unlocked."
Sent from my EVO using xda app-developers app
SilverJaw said:
I have S-On but it still shows "tampered" and "unlocked."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
you HAVE to relock your bootloader inorder to run the RUU
Follow these steps
http://forum.xda-developers.com/showthread.php?t=1655832
lloydw82 said:
you HAVE to relock your bootloader inorder to run the RUU
Follow these steps
http://forum.xda-developers.com/showthread.php?t=1655832
Click to expand...
Click to collapse
Yep, that's the problem I was having. Once I relocked the bootloader the RUU ran smooth as butter. Took a little while so make sure you have enough battery/have it plugged in.
kidstechno said:
Yep, that's the problem I was having. Once I relocked the bootloader the RUU ran smooth as butter. Took a little while so make sure you have enough battery/have it plugged in.
Click to expand...
Click to collapse
Glad i could help you. I had those same issues so it was just in my knowledge. Now i am S-OFF and love it so far.
I was running the Fresh rom for nearly a year and was totally happy with it. I now have a new evo because of a screen failure. I rooted and S-offed it with dirtyracun and flashed rage. I still pretty much hate everything about JB and want my Fresh back. I have flashed the 2.13.651.1 firmware and tried to install the rom and get a false boot after step 2 of 6. I then have to boot into bootloader and reinstall the above rom again. Is there anything I can do to go back?
Anyone?
Are you s-off or s-on?
You might need to fastboot the boot.img... Did you Ruu or just used captain's firmware bits to update to 2.13 firmware?
Sent from my EVO using xda app-developers app
jocarog said:
Are you s-off or s-on?
You might need to fastboot the boot.img... Did you Ruu or just used captain's firmware bits to update to 2.13 firmware?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
s-off, labeled "full" RUU from captain Did not flash boot.img because I couldn't find one.
What exactly do you mean by a "false boot"?
Sent from my EVO using xda premium
FinZ28 said:
What exactly do you mean by a "false boot"?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Shows the HTC boot screen (before it's actually installed the rom) and will sit there as long as I let it. I have to force reboot into bootloader and recover previous rom.
therealratfink said:
Shoes the HTC boot screen (before it's actually installed the rom) and will sit there as long as I let it. I have to force reboot into bootloader and recover previous rom.
Click to expand...
Click to collapse
Boot into your bootloader and list the info in the top left corner of the screen. First five lines will do.
Sent from my EVO using xda premium
FinZ28 said:
Boot into your bootloader and list the info in the top left corner of the screen. First six lines will do.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Would have responded sooner but I have to wait 5 minutes between posts even if I am just editing my own. Kinda silly.
JEWEL PVT SHIP S-OFF RL
CID-SPCS_001
HBOOT-2.09.4444
RADIO-1.12.11.0809
openDSP-v29.1.0.45.0622
eMMC-boot
therealratfink said:
Would have responded sooner but I have to wait 5 minutes between posts even if I am just editing my own. Kinda silly.
JEWEL PVT SHIP S-OFF RL
CID-SPCS_001
HBOOT-2.09.4444
RADIO-1.12.11.0809
openDSP-v29.1.0.45.0622
eMMC-boot
Click to expand...
Click to collapse
No problem. Have you verified MD5 on the download to make sure the download wasn't bad? Also, have you tried flashing a different ICS ROM? I can't think of any reason why you would be having these issues, other than not wiping correctly in recovery (system wipe, flash ROM & reboot).
Sent from my EVO using xda premium
FinZ28 said:
No problem. Have you verified MD5 on the download to make sure the download wasn't bad? Also, have you tried flashing a different ICS ROM? I can't think of any reason why you would be having these issues, other than not wiping correctly in recovery (system wipe, flash ROM & reboot).
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I used the same download I used on my last phone so that should be good. I have not tried any ics, just jb.
therealratfink said:
I used the same download I used on my last phone so that should be good. I have not tried any ics, just jb.
Click to expand...
Click to collapse
My bad, I thought from the way were talking that you had reverted to ICS. Try this. Download the ROM again and verify MD5. Make a backup of your current setup, then do a system wipe in recovery, flash the newly-downloaded ROM, and reboot.
Sent from my EVO using xda premium
FinZ28 said:
My bad, I thought from the way were talking that you had reverted to ICS. Try this. Download the ROM again and verify MD5. Make a backup of your current setup, then do a system wipe in recovery, flash the newly-downloaded ROM, and reboot.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Sadly I am on hold with sprint customer service over an unrelated matter so It'll have to be in a few minutes. LOL
How do I verify the MD5? Do I need to flash the RUU again? I'm not a newbie, but I forget it all after I do it. LOL
(woohoo one more post until the time limit and captcha goes away)
Sorry, blatant post count increaser. I need to edit some bad typing. LOL
It looks like Flipz site is down so I am not able to download the rom again. Bummer
In es file explorer hit properties and then show checksum and make sure it matches the one in the OP
Sent from my EVO using xda app-developers app
Sorry I guess I'm slow. How would I know what to match? It shows the file name.
What version of twrp are you on? I want to say people had problems flashing older roms on newer versions, but I can't personally confirm that...worth a shot though.
Sent from my EVO LTE
premo15 said:
What version of twrp are you on? I want to say people had problems flashing older roms on newer versions, but I can't personally confirm that...worth a shot though.
Sent from my EVO LTE
Click to expand...
Click to collapse
That's the only thing I haven't tried. I am on the new version I believe. Any idea where I could find the version for 2.13.651.1
Never mind I still had the old root folder. Trying now.
therealratfink said:
That's the only thing I haven't tried. I am on the new version I believe. Any idea where I could find the version for 2.13.651.1
Click to expand...
Click to collapse
Here's the version I've been using since I got the phone (2.2.2.0), has worked great for ICS and JB alike. Just rename this file to PJ75IMG.zip and put on the root of your external sd card, then reboot into the bootloader and it will install automatically. Remember to remove it afterwards or it will try to install again next time you enter the bootloader.
premo15 said:
Here's the version I've been using since I got the phone (2.2.2.0), has worked great for ICS and JB alike. Just rename this file to PJ75IMG.zip and put on the root of your external sd card, then reboot into the bootloader and it will install automatically. Remember to remove it afterwards or it will try to install again next time you enter the bootloader.
Click to expand...
Click to collapse
Thank you very much, I'll try that next if the version I used on my last phone doesn't work.
I have a Sprint HTC Evo 3D with HBOOT 1.58 running ICS. I managed to Unlock the Bootloader and get TWRP on it...but when I try flashing [ROM] CyanogenMod 11.0 - VILLUMINATI, it throws up an error...I admit, i've not tried any other ROM but that one seems to be the one that i want. I have re-downloaded it and get the same results. Do I need S-OFF? I think I still have S-ON.....I just got this phone so i'm very new to it....and I can't post in the thread about that ROM b/c of my low post count.....
You will need soff and to change your hboot to 1.50 or lower.
ICS needs 1.57 or 1.58
Anything else needs 1.50 or lower
Sent from my Evo V 4G using XDA Free mobile app
hossman said:
You will need soff and to change your hboot to 1.50 or lower.
ICS needs 1.57 or 1.58
Anything else needs 1.50 or lower
Sent from my Evo V 4G using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for that...I watched a video on it, and maybe i can do it...this is the most "Extreme" method of "modding" a phone software.....The ROM i'm trying to install is 4.4.2 I think, so I need to keep it at 1.58 I assume for that?
NOW i got another problem. Trying to get the RUU file installed from a guide i found on here and i had to run that SetLowVer app or whatever its called and RUU Installer shows its 1.00.000.0 and trying to update to 2.89.651.2 but it fails every time!
EDIT: Got the RUU done, turns out I had to RELOCK the device
EDIT 2: I have S-OFF now! Now gotta figure out how to "downgrade" HBOOT
Dvdxploitr said:
NOW i got another problem. Trying to get the RUU file installed from a guide i found on here and i had to run that SetLowVer app or whatever its called and RUU Installer shows its 1.00.000.0 and trying to update to 2.89.651.2 but it fails every time!
EDIT: Got the RUU done, turns out I had to RELOCK the device
EDIT 2: I have S-OFF now! Now gotta figure out how to "downgrade" HBOOT
Click to expand...
Click to collapse
Did you figure it out?
If you have s off the hard part is done!
To change hboot all you need to do is flash a pg86img through bootloader
Sent from my Evo V 4G using XDA Free mobile app
hossman said:
Did you figure it out?
If you have s off the hard part is done!
To change hboot all you need to do is flash a pg86img through bootloader
Sent from my Evo V 4G using XDA Free mobile app
Click to expand...
Click to collapse
Yup! All Done! This thread can be closed/deleted at this point if need be..
Hey all,
I am looking to sell my Evo 4g lte because sprint really messed things up but that is neither here nor there. I would like to return it to stock for ease of selling it. can i do this without having a stock rooted rom and if possible can i run the updates to get the phone current for the next user? IF one of you want the rooted phone pm me i am up for anything.
Phone has MEAN BEAN rom on it and is s-off h boot 1.12.2222 radio 1.12.11.1210
thanks
stubby
stubby1 said:
Hey all,
I am looking to sell my Evo 4g lte because sprint really messed things up but that is neither here nor there. I would like to return it to stock for ease of selling it. can i do this without having a stock rooted rom and if possible can i run the updates to get the phone current for the next user? IF one of you want the rooted phone pm me i am up for anything.
Phone has MEAN BEAN rom on it and is s-off h boot 1.12.2222 radio 1.12.11.1210
thanks
stubby
Click to expand...
Click to collapse
Hit the top link in my sig and go to the section on RUU's. At the bottom of the first post I have links to all applicable RUU's for the EVO LTE. Easiest thing would be to run one of them if you want to get back to stock. If you want to go back to being S-on and stock, use VipeRUU.
Magnum_Enforcer said:
Hit the top link in my sig and go to the section on RUU's. At the bottom of the first post I have links to all applicable RUU's for the EVO LTE. Easiest thing would be to run one of them if you want to get back to stock. If you want to go back to being S-on and stock, use VipeRUU.
Click to expand...
Click to collapse
Thanks Magnum
Using the VipeRUU was supper easy and quick. Back to stock off to sell.:good:
Not a problem. Just remember that the RUU is run from your computer. Connect your phone and PC via USB cable, and once the connection is complete double-click the RUU file to start the installer. You may need to install HTC Sync so that you have the proper drivers installed on your computer. It takes about 10-15 minutes for the RUU to run, so be patient. VipeRUU is a little bit different. When you double-click the file to start the process, it will bring up a menu with options in it for you to choose from. It's pretty straightforward, though.
I've run VipeRUU a few times, but the bootloader stays unlocked. Anyone have any suggestions to get it back to a "Locked" state? I'm S-OFF, HBOOT 2.09.
Sent from my EVO using Tapatalk
CornDogg said:
I've run VipeRUU a few times, but the bootloader stays unlocked. Anyone have any suggestions to get it back to a "Locked" state? I'm S-OFF, HBOOT 2.09.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
fastboot oem lock
Sent from my Nexus 5 using XDA Premium 4 mobile app
That would just make it show "Relocked", though, right?
Sent from my EVO using Tapatalk
Evolution_Freak said:
fastboot oem lock
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't believe that will work being S-off (I've tried it before just for kicks and it didn't do anything). Even if it did, the bootloader would show the tampered and unlocked warning.