It has come to a lot of peoples furious attention that there is an issue with the latest RUU from HTC. I firsthand had to deal with it an it is documented in this thread http://forum.xda-developers.com/showthread.php?t=2074643 in which i attempted to restore my htcdev unlocked phone back to stock.
THE ISSUE
The problem is the ruu is updating hboot and seemingly nothing else. Radios, recovery, rom, etc all have remained the same after running the ruu. Attempts at re running the ruu do nothing and various ways of flashing/applying the ruu are ineffective. This creates a stable but malfunctioning phone with mismatched hboot, radios, rom, and seems unable to take you back to fully stock.
Pre-RUU:
s-on
hboot: 1.19
radio: 1.05.11.0606
rom: stock rooted jb with superuser
Post-RUU: (after multiple flashings/applications)
hboot: 2.09
radio: 1.05.11.0606
rom: stock rooted jb with superuser (i'm assuming that this should have been completely stock instead its the same rom i had previous to ruu application)
In the mean time, I've been running the latest stock jb rom and its stable enough for a functioning phone but things like cellular data (streaming music from google music doesn't work or sending sexy pics to the ladies on snap chat) and lte is completely absent. If you experience the same issue post in here with what happened, solutions, fixes, etc.
GOING BACK TO STOCK
If you need to get back to stock or semi bricked your phone use the ruu for your current software not the latest (for example if your hboot is 1.19 use the ruu with hboot 1.19 not the jb ruu with 2.09 hboot)
For now it seems the best thing to do is aware htc of the problem, wait for a new ota update/ruu fix, and/or wait for new s-off method for 2.09,
tankerevo has been working on various attempts/fixes and i've forwarded this thread along with some other information to htc.
RESPONSE FROM HTC
Dear rollerpig,
Thank you for contacting the HTC Technical Support Center in regards to your issue suggestion.
We are glad to know there are customers like you committed with our brand to improve our service and customer satisfaction. We understand there could be a lot of users and fans waiting for a fix on this RUU. We think it is amazing to have a good support in our users to enhance our products and releases. Right now we will share this concern with the Develop Team to look forward on a solution. We expect this issue will be fixed as soon as possible.
Rollerpig, we want to thank you once again for working with us, and for caring about our brand.
If you require further assistance in the near future please contact us through http://www.htc.com/us/support/email-support or call us at +1-866-449-8358 from 6AM to 1AM EST, 7 days a week.
Have a nice day,
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
Julian
HTC
Want to see what others are saying? Have a question to ask other HTC fans?
Become a fan of HTC facebook.com/htc
Follow us on Twitter twitter.com/htc
Subscribe to our YouTube Channel youtube.com/htc
Explore our development resources developer.htc.com
Please visit us at htc.com if you have any questions or need further assistance.
Click to expand...
Click to collapse
THE FIX
Here's a possible fix complements of user Fuses. I have not tried this yet because i'm on vacation but it looks very promising and most likely works. http://forum.xda-developers.com/showthread.php?t=2097150
Fix
- Download JB OTA firmware from http://unlimited.io/jewel.htm
- Download fastboot executable (google)
- Put all files in one directory
- Reboot phone into fastboot mode
- Make sure that bootloader is Locked or Relocked. If bootloader is Unlocked, relock it with command fastboot oem lock
- Enter commands
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
NOTE:
If you see FAILED (remote: 90 hboot pre-update! please flush image again immediately) text after running fastboot flash zip command you have to run fastboot flash zip command again.
After this flash stock RUU again.
Permanent fix
- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily.
Click to expand...
Click to collapse
Obviously, depending on the firmware version you are frozen at there will likely be variance in stability and function between ROMs and other users with the issue stuck at a different firmware version.
For me the last ICS stock ROM is working the best including LTE. But WiFi, Cell, and Data do restart rather incessantly.
MeanBean 2.0 works alright considering... But LTE doesn't work at all and the radios get very weak signals to the point that I start to enter roaming often.
It might help to post before and after info of the radio versions, hboot, pri, all that stuff so if someone were to have used the RUU and it worked they can compare what the old stuff is to the new stuff.
does gps work well on the ics stock?
sickied for a little while until issue is resolved
Papa Smurf151 said:
sickied for a little while until issue is resolved
Click to expand...
Click to collapse
good deal... And also , Thanks OP for the heads up
I've got my lte back, but had to nandroid back to superlte. I went to ##3282# and set profile to 1, and changed scan timer to 2 and max timer 30. It has been the longest I've had constant lte in a month.
Sent from my EVO using Tapatalk 2
Mine was hosed too. If I ran the 2.13 RUU, it said you have a 2.13 image, would you like to update it to 2.13. If I ran the 3.15 RUU, it would say you have a 3.15 image on your phone, would you like to update it to 3.15?
Needless to say, none of that worked. I even tried the P75 image of JB direct from Sprint through recovery. No workie. I gave up and took it to Sprint. Explained that after RUU just aint going to work and this phone is stuck in ICS/JB hybrid limbo.
Sprint replaced the phone and I am now good to go. If you want to wait for a hack fix, then wait. Otherwise, you can try getting Sprint to replace it with a new one.
So back to my original question, can someone post what the 3.15.651.16 official numbers should be.
PRI, Radio, All those magical numbers were talking about..
Id like to check mine and see. I do remember downloading the RUU and installing it..
IAmSixNine said:
So back to my original question, can someone post what the 3.15.651.16 official numbers should be.
PRI, Radio, All those magical numbers were talking about..
Id like to check mine and see. I do remember downloading the RUU and installing it..
Click to expand...
Click to collapse
PRI - 2.87_003
Baseband - 1.12.11.1119
bigdaddy619 said:
PRI - 2.87_003
Baseband - 1.12.11.1119
Click to expand...
Click to collapse
OK those numbers match my device so i guess im OK..
The file i used to upgrade was downloaded 12/24/2012
RUU_JEWEL_CL_BJ_45_S_SPRINT_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe
This is the RUU i used on mine because i was impatient and didnt want to wait for the OTA to hit my phone.
From what i can tell it did the upgrade just fine.
IAmSixNine said:
The file i used to upgrade was downloaded 12/24/2012
RUU_JEWEL_CL_BJ_45_S_SPRINT_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe
This is the RUU i used on mine because i was impatient and didnt want to wait for the OTA to hit my phone.
From what i can tell it did the upgrade just fine.
Click to expand...
Click to collapse
IAmSixNine, could you give us a bit more detail on your setup. OS (windows etc), where you downloaded the RUU, and what software version were you running before you upgraded.
Windows 7 home, i was on the latest stock, unlocked device prior to that update coming out.
Where did i DL it at, http://www.htcruu.com/?dir=Jewel
Try this one, please report on that thread if fix works for you also
http://forum.xda-developers.com/showthread.php?t=2097150
I installed the 3.15 RUU from CM10 to try to bring my phone back to stock.
The RUU took, but now my phone is incredibly slow, freezes, screen goes unresponsive, camera wont work...All kinds of issues]
I even reapplied the same RUU from the stock 3.15 ROM.
Are my issues symptoms of this problem outlined in this thread?
Possibly. What's you baseband version?
If its less than 1.12 then yes.
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
Also if it is less then fllow fuses thread link above.
update baseband
is there a way to update the baseband version mine is less then 1.12, I am s-off and am running the latest meanrom because meanbean was super unstable for me.
do I need to download the latest ruu to update it, then flash it with the latest meanbean?
frey482 said:
is there a way to update the baseband version mine is less then 1.12, I am s-off and am running the latest meanrom because meanbean was super unstable for me.
do I need to download the latest ruu to update it, then flash it with the latest meanbean?
Click to expand...
Click to collapse
Here is the full firmware minus hboot-recovery-kernel
http://d-h.st/4Y0
MD5 2a9b2c8f6a969fe0163df5738e8f4b5
Rename it PJ75IMG and place it on your ext sdcard/boot into bootloader/ it should ask you if you want to update follow the on screen instructions once you are rebooted remove the file from your sdcard if you don't you will be asked to update every time you enter bootloader
I rooted my phone this morning, and attempted to install cm10. the screen became inop. so I tried a recovery and it put it into boot loop. I have relocked the phone and tried some RUUs but all come back with bootloader, or signature errors, I have tried this method as well to no avail all i end up getting is this:
C:\Users\Downloads>fastboot flash zip RUU.zip
sending 'zip' (659905 KB)...
OKAY [ 27.926s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 106.089s
Boot Screen:
*tampered
*relocked
s on
hboot 2.09
radio 1.12.11.1210
opendsp-v31.1.45.0815
eMMC-boot
Any help would be appreciated
Related
Not my first time around the block I did this with hboot 1.5 the only thing i can think of is HTCDEV.com sent me a F**ked up file.
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.156s
and WTF nothing happens no menu pops up to unlock or anything
I sent in the full and correct no space unlock code to htcdev.com
This is iratating
I had the same thing happen. No clue how to make it work. Earlier hboot maybe...
Sent from my PG86100 using xda premium
Did you take the OTA?
Even if you didn't, I had the same problem.
What I had to do to fix it is run the RUU.
http://forum.xda-developers.com/showpost.php?p=30106576&postcount=20
Then do the HTC unlock crap again. It will then work.
You'll know because your phone will display a pop-up asking you if you want to unlock or not.
Didn't take the ota..
Sent from my PG86100 using xda premium
I would try it anyways. Can't hurt.
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
I cant get any of the RUUs to work because the boatloader and all the software on the phone is newer and the RUUs just fail on start.
hypersonicx said:
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
I cant get any of the RUUs to work because the boatloader and all the software on the phone is newer and the RUUs just fail on start.
Click to expand...
Click to collapse
Have you tried the 2.89 RUU that was linked in post #3 above? I flashed it after using virus's firmware upgrade and taking the Sprint ICS OTA and it still ran fine for me. It should be the same as the OTA, but I have more confidence in the RUU.
ramjet73
halfaddict said:
Not my first time around the block I did this with hboot 1.5 the only thing i can think of is HTCDEV.com sent me a F**ked up file.
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.156s
and WTF nothing happens no menu pops up to unlock or anything
I sent in the full and correct no space unlock code to htcdev.com
This is iratating
Click to expand...
Click to collapse
FOUND SOLUTION..............
You have to download the RUU that matches the HTC Software on your phone. Go to settings > about > scroll down to Software Version and google search the RUU that matches.
Enable USB Debugging and let phone sit at home screen.
Run the RUU exe from withing windows on your PC wait for it to finish and and it will wipe phone in the process.
After it is done, boot to fastboot and run the HTC Unlock Token command again and this time you will get the prompt on the cell phone screen.
I spent 6 hours plus trying to root my wife phone wile tetherd from my Epic Touch GS2.
Samsung side of the world is a WHOLE lot easier. Everything is done within Oden for Samsung devices.
Anyway, there you go guys!
hypersonicx said:
FOUND SOLUTION..............
Click to expand...
Click to collapse
That's what I was recommending, except you don't have to relock your bootloader before running the RUU and unlock it after if you are S-OFF. And here's the downloads for the current RUU so others don't have to Google it.
Glad it worked for you.
ramjet73
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
htcdev.com said:
HTC has identified a known issue that may be experienced by some users with a Sprint EVO 3D that shipped with version 2.08.651.2, even if it was updated to a newer software version via FOTA. When attempting to unlock, a blank screen appears on the device after step 12 in the instructions and the process does not complete. As a workaround for users who experience this issue, we suggest you upgrade the ROM to 2.17.651.5 first via OTA then download and install the RUU from the table below to fix the issue before attempting the unlock process. This issue will also be fixed in the ICS update scheduled for EVO 3D.
Click to expand...
Click to collapse
t3project said:
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
Click to expand...
Click to collapse
That's odd, because the OP of this thread stated that it failed with hboot 1.5, which would indicate that he was already on the 2.17.651.5 build.
In any case, it appears that HTC unlock wants a pure stock configuration, so running either the 2.17 or 2.89 RUU before flashing the token should work.
ramjet73
ramjet73 said:
That's odd, because the OP of this thread stated that it failed with hboot 1.5, which would indicate that he was already on the 2.17.651.5 build.
In any case, it appears that HTC unlock wants a pure stock configuration, so running either the 2.17 or 2.89 RUU before flashing the token should work.
ramjet73
Click to expand...
Click to collapse
no, he stated he could unlock with 1.5 but couldn't unlock with 1.58.
hypersonicx said:
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
Click to expand...
Click to collapse
t3project said:
no, he stated he could unlock with 1.5 but couldn't unlock with 1.58.
Click to expand...
Click to collapse
And 1.58 is the stock bootloader of the official Sprint ICS build, which is where HTC said it would be fixed. Of course it depends on how he got the 1.58 bootloader but the OTA should have been fine, and at least one person said they had problems unlocking after taking the OTA.
ramjet73
ramjet73 said:
And 1.58 is the stock bootloader of the official Sprint ICS build, which is where HTC said it would be fixed. Of course it depends on how he got the 1.58 bootloader but the OTA should have been fine, and at least one person said they had problems unlocking after taking the OTA.
ramjet73
Click to expand...
Click to collapse
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
t3project said:
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
Click to expand...
Click to collapse
The firmware updates don't update you 100% to the 2.89 build. You need to flash the 2.89 RUU to do that, as has already been pointed out in this thread, and for some reason the HTC unlock appears to work after that. I really don't know what the difference is between taking the OTA and flashing the RUU is, but they should be the same.
For someone like you that is already S-OFF, you could always flash the JuopunutBear 1.58.5858 bootloader if you need to run the 2.89 kernel and get most of the benefits of the ENG bootloader. However, that bootloader will not work properly with GB and AOSP ROM's.
ramjet73
i know this man!!! lol
t3project said:
i know this man!!! lol
Click to expand...
Click to collapse
t3project said:
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
Click to expand...
Click to collapse
That's good. Now you also know that flashing the 2.89.651.2 RUU.exe will let you do the HTC unlock with the 1.58 bootloader.
ramjet73
t3project said:
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
Click to expand...
Click to collapse
I concur. I'm not a novice when it comes to unlocking bootloaders & rooting phones. I've unlocked more bootloaders through htcdev.com than I can count & this gentleman is absolutely right! HTC really needs to get it together! Samsung devices are so much easier to work with. You don't run into these stupid little problems with Samsung phones. Usually, what goes for one Samsung device goes for all!
I digress, but anyhow, I'm well aware that reinstalling the operating system on an EVO 3D via an RUU will allow the token that you get from htcdev.com to work, and I have used this fix several times in the past on the last Gingerbread OS (Software version 2.17.651.5), but here's my issue. I have an EVO 3D with S-ON & a LOCKED bootloader that was updated over the air to ICS & when I go to unlock the bootloader via htcdev.com, nothing happens & HTC claimed that this issue would be fixed with the ICS update, but guess what? It wasn't!
Nonetheless, you would think that reinstalling the ICS operating system (Software version 2.89.651.2) on the phone via an RUU or a PG86IMG file would work. Neither one works for me! Every time I go to run the ICS RUU, it throws back a 170 USB connection error & this is crazy because the RUU that I have for the last Gingerbread OS (Software version 2.17.651.5) never throws back any type of errors! It has worked on every single EVO 3D that I have had to use the fix on! I have tried running the ICS RUU several times and have used several different USB cables & have had no success whatsoever.
So what I did from here is requested for someone from the XDA community to create a PG86IMG for me so that I could see about reinstalling the ICS OS on the phone through the bootloader (Shout outs to Karl! He came through on this right away. Karl you are the man!). Unfortunately, when I go to use the PG86IMG file, it does all of this loading & appears as if it's going to work but ultimately goes back to the HBOOT home screen & doesn't give me an option to install the f'n operating system! This sh*t blows & I am all out of ideas as to what to do from here. I am basically stuck.
On anther note, I tried to use the ICS RUU that I have on another EVO 3D with no success, but I was successfully able to reinstall the ICS operating system on this same EVO 3D via the PG86IMG file that Karl provided. What in the world is going on here?! If anyone can offer any helpful advice, I'd certainly appreciate it. Thanx in advance. (On a side note this other EVO 3D that I was able to reinstalled the ICS OS on via the PG86IMG file has an UNLOCKED bootloader & is S-OFF. I don't know if this makes any difference, but I thought I'd share this anyway.)
RioSoul said:
Nonetheless, you would think that reinstalling the ICS operating system (Software version 2.89.651.2) on the phone via an RUU or a PG86IMG file would work. Neither one works for me! Every time I go to run the ICS RUU, it throws back a 170 USB connection error & this is crazy because the RUU that I have for the last Gingerbread OS (Software version 2.17.651.5) never throws back any type of errors! It has worked on every single EVO 3D that I have had to use the fix on! I have tried running the ICS RUU several times and have used several different USB cables & have had no success whatsoever.
Click to expand...
Click to collapse
The 170 error means that the RUU.exe can't find your phone. Make sure the phone is in "fasboot USB" mode in the bootloader, then try running "fastboot devices" from the PC directory you used to root your phone. It should come back with a serial number that starts with "HT". If it doesn't, you may have a problem with the USB port on your phone, although it probably won't go into fastboot USB mode in the bootloader if that is the case. If you get the serial number, try running the RUU.exe again from there. If you get a 17x error with the RUU.exe, usually restarting it will get past that error as long as you have the proper connectivity to the phone.
ramjet73
achppr who
Confirmed, this worked for me. Thanks for your help! :good:
The issue
If you flash new 3.15.651.16 JellyBean RUU and it only updates hboot to 2.09, phone might end-up in semi-bricked state.
RUU refuses to flash any other partition (even if bootloader is in locked/relocked state) so its impossible to return phone to stock rom.
Error message from fastboot flash zip is;
Code:
fastboot flash zip RUU.zip
sending 'zip' (659905 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 22 loading zip info fail)
What is causing this
Hboot fails to read ruu-info from new encrypted zip after hboot-preupdate and stops flashing process.
Solution
Solution is to flash firmware.zip from JellyBean OTA. Firmware.zip is "old style" zip file, hboot can open this zip and update radio and sbls.
Fix
- Download JB OTA firmware from http://unlimited.io/jewel.htm
- Download fastboot executable (google)
- Put all files in one directory
- Reboot phone into fastboot mode
- Make sure that bootloader is Locked or Relocked. If bootloader is Unlocked, relock it with command fastboot oem lock
- Enter commands
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
NOTE:
If you see FAILED (remote: 90 hboot pre-update! please flush image again immediately) text after running fastboot flash zip command you have to run fastboot flash zip command again.
After this flash stock RUU again.
Permanent fix
- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily. :good:
Please report any success / failures into this thread. Also tell little bit information about your device, like;
- What hboot you had
- Was radio flashed through recovery
- Was hboot downgraded
- CID
-- Reserved --
Thanks for your work
Sent from my EVO using xda premium
thanks fuses
Wow fuses, this is gonna help A LOT of people. This community is really lucky to have your attention. Thanks. :thumbup::beer:
Sent from my EVO using xda premium
I ran this... Worked to a T. Debating whether or not to s-off...
But, this did in fact update my radios..
Phenomenal. Just to be clear with what I did...
Ran Fuses instructions. Then I did the RUU GUI update in Windows... back to stock, Tampered in bootloader removed. Testing the stock radios and what not, but so far it's perfect.
*** Phone has to be RELOCKED****
I am not sure if I am successful or not right now. Phone is showing HTC black screen with green bar below it. The green bar is not ALL the way across, looks like 95% after running the commands. Not sure what to do so I issued "fastboot reboot"
Phone looks to be in bootloop so I got back into HBOOT.
First I relocked the phone. Rebooted. Then Rebooted into fastboot.
Then ran commands, screen shots are attached.
Seeing this message after running commands:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Changes noticed in Bootloader:
My RADIO updated from 1.02.12.0427 to 1.12.11.1119
OpenDSP updated from OpenDSP-v25.1.0.32.0405 to OpenDSPv31.1.0.45.0815
Update:
Put the phone into fastboot and then ran the windows Jellybean RUU. Looked like the RUU got about 98% thru and then gave me a USB error. Then the phone rebooted and it looks like everything updated. Phone is booting into JellyBean. Should I retry installing the RUU?
Cloves
Rerun the ruu. Just hit the up arrow and then enter
Sent from my EVO using Tapatalk 2
I don't personally have a need for this but I know others do so thanks! Nice to know this is there if needed. :thumbup:
Thanks,
Everything looks good. Phone shows RELOCKED and 4.1 is running. Thanks for the fix!
saved my ass. thanks!
My 4G LTE was on HBOOT 2.09
Tried to S-OFF and downgrade HBOOT by DirtyRacun
Was stuck at a point where the screen went blank for a long time
After that the phone does not power on...
Even the PC does not detect it...
Help please...
Seek out soul shadow . He's usually in the stickied threads in original development. He seems to know a hell of a lot about this phone and bricks/semi bricks
Sent from my EVO using xda premium
aankush said:
My 4G LTE was on HBOOT 2.09
Tried to S-OFF and downgrade HBOOT by DirtyRacun
Was stuck at a point where the screen went blank for a long time
After that the phone does not power on...
Even the PC does not detect it...
Help please...
Click to expand...
Click to collapse
Fastest way to get support for DirtyRacun is to join #unlimited channel on freenode.
Lets keep this thread clean, semi-brick on 3.15.651.16 stock RUU stuff only.
Well guys, time to add some info. If you lock and re-flash the RUU file and you get "SBL VERIFY FAILED" errors (but the RUU still completes) and you can't htcdev unlock (signature failed), you should use this fix. Helped me get my friend's phone S-off using Dirty Racun.
Fuses said:
Permanent fix
- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily. :good:
Click to expand...
Click to collapse
is this true?
if we're running stock JB (newer hboot), then we can downgrade it to stock ICS (older hboot) via RUU
un1ocked said:
is this true?
if we're running stock JB (newer hboot), then we can downgrade it to stock ICS (older hboot) via RUU
Click to expand...
Click to collapse
Um,...yes. if fuses posted it and it's about S-off,... it's true.
Sent from my EVO using xda premium
un1ocked said:
is this true?
if we're running stock JB (newer hboot), then we can downgrade it to stock ICS (older hboot) via RUU
Click to expand...
Click to collapse
Yes it is true, but always download full stock RUU and use that. There is some problems with repacked firmwares.
After I typed rebootRUU my screen changed to an HTC screen and stayed there for like 30 min, I tried to flash the zip but my phone wasn't recognized. But ever since that exact moment my computer has f***** up. Does anyone know why this happened
Sent from my EVO using xda premium
Jeffrey4Free said:
After I typed rebootRUU my screen changed to an HTC screen and stayed there for like 30 min, I tried to flash the zip but my phone wasn't recognized. But ever since that exact moment my computer has f***** up. Does anyone know why this happened
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Probably windows dropped fastboot-drivers. Try installing drivers again or use Linux, ubuntu live-cd works just fine.
Hi I just updated my htc evo 4g 3d from Sprint to 2.95 via ota and after that i cannot use wifi at all it just says error. please Help!!!!
b0235g10d said:
Hi I just updated my htc evo 4g 3d from Sprint to 2.95 via ota and after that i cannot use wifi at all it just says error. please Help!!!!
Click to expand...
Click to collapse
You probably took the update and tried to install it with a custom recovery installed. If so, it appears that will result in a partially installed update with the ROM updated and the kernel not being flashed, which causes WiFi errors.
If that's your situation the best thing to do is flash a stock rooted ROM if that is what you were using prior to taking the OTA.
ramjet73
ramjet73 said:
You probably took the update and tried to install it with a custom recovery installed. If so, it appears that will result in a partially installed update with the ROM updated and the kernel not being flashed, which causes WiFi errors.
If that's your situation the best thing to do is flash a stock rooted ROM if that is what you were using prior to taking the OTA.
ramjet73
Click to expand...
Click to collapse
Can you please give me the official ics 2.89 rom or find it please?
b0235g10d said:
Can you please give me the official ics 2.89 rom or find it please?
Click to expand...
Click to collapse
You can find a rooted version in this post.
ramjet73
ramjet73 said:
You can find a rooted version in this post.
ramjet73
Click to expand...
Click to collapse
I found this thread because I'm in a similar situation. I tried downloading from the quoted link and using 4eXT recovery to load the zip file from sd card and it says "installation aborted".
Any ideas on what to try next? My eventual goal is to get back to 100% showroom stock non-rooted, locked booloader, so that the phone will accept OTA updates fully. Modding/ROMing is a drug I experimented with, and am now ready to go back to the straight and narrow. I'd prefer the phone not have any scars whatsoever from my old habits.
Additional background:
Started with ICS OTA. Used HTC unlock to unlock bootloader. Coworker installed rom toolbox, superSU and 4eXT recovery (not sure what order) to get SOS rom up and running. Never did go for S-OFF.
Decided I wanted to return to 100% Sprint factory stock. Coworker promptly moved across country, leaving me to figure this out. Tried using several ROMs from XDA and elsewhere, and eventually ended up with a rooted almost stock ROM, but had to flash my own radios via 4eXT, as wifi and 4G weren't working from the rom. Flashing my own radios via 4eXT, got to 2.89 with then current radios.
While sitting in my hotel travelling abroad with no international data plan and super slow hotel wifi, I foolishly downloaded OTA this morning, promptly killing my phone's wifi. Phone is still rooted with 4eXT, superSU, installed on it if that helps.
ramjet73 said:
You can find a rooted version in this post.
ramjet73
Click to expand...
Click to collapse
I just did this yesterday (Thanks to ramjet for pointing it out). Backup first. It dose a factory reset. You also need to install the blue tooth fix from this post after flashing the ROM http://forum.xda-developers.com/showpost.php?p=29707708&postcount=303
fixed thanks
Hi to all
I just fixed my phone thanks to Mr ramjet and I used the last one because I completely formatted my phone and only had 4ext it takes while to load the first time but be patient and it will work
How about S-Off phones?
Hello... so my fiance' has a Virgin Mobile Evo 3D. I downloaded the update from them and tried to install it through the custom recovery. It did what Ramjet said by updating the ROM and not the Kernel. I now have no wifi,it says wifi error when trying to turn it on. Since then, I have made sure the stock ROM was rooted, and have also HTCDev unlocked the device as well as S-Off with the Junobear wire trick and Linux. Now that I'm S-Off, is it ok to use an RUU to downgrade everything? Just wondering before I go any further and brick the device or screw up something I shouldn't. I figure it's better to ask questions first before doing it lol! Any help is greatly appreciated from anybody! I have my specs listed here for you all:
HTC Evo 3D 4G Virgin Mobile
Mods: Rooted,HTCDev Unlocked, S-Off
JuopunutBear
Shooter XC SHIP S-OFF RL
HBOOT: 1.57.5757
Radio: 1.09.00.0706
Android Version 4.0.3
Sense Version 3.6
Software number 2.95.652.5 710RD
Kernel Version: 3.0.16-g4211684
[email protected] #1
SMP PREEMPT
Baseband Version:1.09.00.0706
Build Number: 2.95.652.5 CL560640 release-keys
EDIT: Problem has been fixed and I will post a new thread on how to fix the problem soon.
PS4AndroidHacker said:
EDIT: Problem has been fixed and I will post a new thread on how to fix the problem soon.
Click to expand...
Click to collapse
Was this new thread ever made because I am a Virgin Mobile user too just like the above user and ever since last update my wireless has stated error.
If ur phone's bootloader is unlocked, relock your phone by using the fastboot command "fastboot oem lock". Then just download the 2.89 RUU.exe. (i know ur on 2.95 but i have not seen the 2.95 ruu floating around hgere yet) Run it on a windows PC and follow the prompts and it should flash correctly on your phone (caution, it will erase everything on your phone). Once its flashed, the phone will reboot (sometimes more than once) just let it do its thing
Once the phone has flashed correctly, do a software update and it will update to 2.95
Worked for me when i had to go back to stock in order to return it for warranty when the digitizer went out
EDIT:
Here is the link to the 2.95 OTA http://d-h.st/vUe
Download to your PC, then unzip it, and run it after you have relocked your phone
Should you need them, here is the list of HBOOTS (thanks to ramjet73) http://forum.xda-developers.com/showthread.php?p=29844945#post29844945
sixty9fordkiller said:
If ur phone's bootloader is unlocked, relock your phone by using the fastboot command "fastboot oem lock". Then just download the 2.89 RUU.exe. (i know ur on 2.95 but i have not seen the 2.95 ruu floating around hgere yet) Run it on a windows PC and follow the prompts and it should flash correctly on your phone (caution, it will erase everything on your phone). Once its flashed, the phone will reboot (sometimes more than once) just let it do its thing
Once the phone has flashed correctly, do a software update and it will update to 2.95
Worked for me when i had to go back to stock in order to return it for warranty when the digitizer went out
EDIT:
Here is the link to the 2.95 OTA http://d-h.st/vUe
Download to your PC, then unzip it, and run it after you have relocked your phone
Should you need them, here is the list of HBOOTS (thanks to ramjet73) http://forum.xda-developers.com/showthread.php?p=29844945#post29844945
Click to expand...
Click to collapse
This sounds hopeful, I did try to install this before with no luck, it gave me a 131 custom id error. I did it relocked and I am currently 2.95.652.5, and S-ON.
any suggestions?
Thanks
Hey all,
So I'm sending my Rezound back to Verizon as a warranty replacement, and today I tried to revert it to stock. It was rooted, S-OFF, with Infected ROM installed (based off CM10.1.2). However, the re-lock process didn't work correctly. I received the below error in the command prompt when I tried to relock it with fastboot oem lock:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
The steps I took are as follows:
1) Re-installed RUU using this file: Rezound_Global_ICS_4.03.605.2_Full_RUU_PH98IMG (renamed to PH98IMG and done through bootloader)
2) Attempted fastboot oem lock (and got the above error)
This process worked on a different Rezound that I also received as a warranty replacement which itself was also defective, but in that case I locked the phone first and THEN flashed the RUU. In my haste today I accidentally flipped the order to what you see above.
Now, the phone will not go back to ***LOCKED*** up at the top. Instead, it says ***RELOCKED*** which is not what I want here. I am afraid to set the S-OFF flag back to ON while the phone is displaying "relocked". The RUU did work, as the phone has stock firmware on it once again and boots up fine. I attempted to relock it again and RUU it again with the same results, still got the above error and still showing ***RELOCKED***.
I did some research but couldn't find anything specific to the Rezound; the nearest thing I was able to find was some info about how CleanROM can cause this on a different device, and something about mainver, which I'm not familiar with. I did use CleanROM for nearly a year before going S-OFF and moving to CM10. If anyone has an idea on how to fix it I would be eternally grateful.
tigerxchaos said:
Hey all,
So I'm sending my Rezound back to Verizon as a warranty replacement, and today I tried to revert it to stock. It was rooted, S-OFF, with Infected ROM installed (based off CM10.1.2). However, the re-lock process didn't work correctly. I received the below error in the command prompt when I tried to relock it with fastboot oem lock:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
The steps I took are as follows:
1) Re-installed RUU using this file: Rezound_Global_ICS_4.03.605.2_Full_RUU_PH98IMG (renamed to PH98IMG and done through bootloader)
2) Attempted fastboot oem lock (and got the above error)
This process worked on a different Rezound that I also received as a warranty replacement which itself was also defective, but in that case I locked the phone first and THEN flashed the RUU. In my haste today I accidentally flipped the order to what you see above.
Now, the phone will not go back to ***LOCKED*** up at the top. Instead, it says ***RELOCKED*** which is not what I want here. I am afraid to set the S-OFF flag back to ON while the phone is displaying "relocked". The RUU did work, as the phone has stock firmware on it once again and boots up fine. I attempted to relock it again and RUU it again with the same results, still got the above error and still showing ***RELOCKED***.
I did some research but couldn't find anything specific to the Rezound; the nearest thing I was able to find was some info about how CleanROM can cause this on a different device, and something about mainver, which I'm not familiar with. I did use CleanROM for nearly a year before going S-OFF and moving to CM10. If anyone has an idea on how to fix it I would be eternally grateful.
Click to expand...
Click to collapse
You need to get ahold of either the ph98img.zip for 3.14.605.12 like HERE and put it on your sd card and run that at hboot after renaming it ph98img.zip or get a copy of the full RUU (RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe) for 3.14.605.12 at ONE OF THESE LINKS and run this on your pc with the phone connected by the USB cable. Make sure on the exe version that you have USB debugging enabled. The RUU you used is a leak and not an "official" full RUU. You need to run a full official RUU to accomplish what you want and the full RUU for 4.05.605.14 has not been released yet. If you use either of the ones I provided links for, the hboot will show "locked" but an earlier version. Then if you want it to show the latest version, leave your SIM card in the phone, let it bootup, when the setup starts, just press the home key and it will bypass setup. The get into settings and into the software update and run that. It will update to the next version. Let it reboot and again bypassing the setup. Then run software update one more time and you will have 4.05.605.14 which is the latest version and your hboot will now show locked. Now you can go ahead and re S-on the phone.
However, I have heard over and over that Verizon never checks the software on the phones and you could just send it back the way it is now. But I'm sure that you are paranoid about this like I am and want it fully stock again so there are no red flags...
mikeyk101 said:
You need to get ahold of either the ph98img.zip for 3.14.605.12 like HERE and put it on your sd card and run that at hboot after renaming it ph98img.zip or get a copy of the full RUU (RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe) for 3.14.605.12 at ONE OF THESE LINKS and run this on your pc with the phone connected by the USB cable. Make sure on the exe version that you have USB debugging enabled. The RUU you used is a leak and not an "official" full RUU. You need to run a full official RUU to accomplish what you want and the full RUU for 4.05.605.14 has not been released yet. If you use either of the ones I provided links for, the hboot will show "locked" but an earlier version. Then if you want it to show the latest version, leave your SIM card in the phone, let it bootup, when the setup starts, just press the home key and it will bypass setup. The get into settings and into the software update and run that. It will update to the next version. Let it reboot and again bypassing the setup. Then run software update one more time and you will have 4.05.605.14 which is the latest version and your hboot will now show locked. Now you can go ahead and re S-on the phone.
However, I have heard over and over that Verizon never checks the software on the phones and you could just send it back the way it is now. But I'm sure that you are paranoid about this like I am and want it fully stock again so there are no red flags...
Click to expand...
Click to collapse
Thanks very much for the suggestion. I'll give this a try shortly.
It's just weird that this RUU successfully took another phone back to fully stock. The only difference between the two is that the other phone never had CleanROM installed on it.
EDIT: Just realized one other thing, at one point I manually updated the radios on the first phone (the one that is now giving me trouble) but didn't do this on the one that went back to stock properly. I'm going to give the PC method a try since it mentions the radios in the file name.
Sent from my SCH-I535 using xda app-developers app
Went ahead and ran the full RUU from my PC as suggested above. Unfortunately it didn't accomplish the goal. The RUU completed successfully, but HBOOT still says ***RELOCKED***. I tried unlocking and then relocking again, and got the same error:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.958s
Not sure where to go from here.
With S-off, the radios shouldnt matter. Seems to me when I s-offed this latest phone, it was on 4.05.605.14 and I had to unlock the bootloader to do the s-off. After I achieved s-off, I dont remember relocking, I just ran that ph98img from android police. The bootloader then displayed that it was locked. Maybe try to run either of those RUUs after unlocking the bootloader.
mikeyk101 said:
With S-off, the radios shouldnt matter. Seems to me when I s-offed this latest phone, it was on 4.05.605.14 and I had to unlock the bootloader to do the s-off. After I achieved s-off, I dont remember relocking, I just ran that ph98img from android police. The bootloader then displayed that it was locked. Maybe try to run either of those RUUs after unlocking the bootloader.
Click to expand...
Click to collapse
I think the key is this error I'm getting via the command line. I didn't get it with the other phone and on that one, after I relocked, it said **TAMPERED** across the top; after the RUU, it just said **LOCKED**. This one is saying **RELOCKED** instead of **TAMPERED** and it's the one that won't go back to locked after a RUU. If we can figure out what's causing this error, might be the key to solving the issue. However, that's where I'm falling short in my research.
tigerxchaos said:
I think the key is this error I'm getting via the command line. I didn't get it with the other phone and on that one, after I relocked, it said **TAMPERED** across the top; after the RUU, it just said **LOCKED**. This one is saying **RELOCKED** instead of **TAMPERED** and it's the one that won't go back to locked after a RUU. If we can figure out what's causing this error, might be the key to solving the issue. However, that's where I'm falling short in my research.
Click to expand...
Click to collapse
IIRC, when it says Tampered across the top of the bootloader, it just means that the bootloader is unlocked and that a other than factory recovery has been installed such as TWRP or AmonRa. Relocked means that the bootloader had originally been unlocked at some point and then locked again. If it were me, I would
1. Try to unlock the bootloader again,
2. Reinstall either AmonRa or TWRP if either is not there, then
3. Wipe everything such as cache, dalvik cache, wipe ALL data/factory reset, and possibly even wipe system.
(Normally you would not want to wipe system because pretty much everything is then gone but since you have the RUU.exe, you have the means to reinstall the original OS.)
4. After wiping everything above, reboot from recovery to bootloader and try running that RUU again.
You are right though and this is weird. Normally when you run a full factory RUU, it should reset EVERYTHING back to factory original condition.
BTW, I have just been trying to come up with a workable solution. I was kind of hoping that someone with more experience would pipe in. Unfortunately it looks like the Rezound and development is dying a slow but sure death and many have moved on...
Just trying to think of alternate solutions again, I know that it is possible to change just the hboots by using the proper ph98img.zip files. I remember using one awhile back when I was unlocked that changed the hboot from tampered to read locked. I cant find the thread but I think it came from Vinylfreak . I attached it in this post but it will read 2.27.0000 as the version. I have also included the factory 2.28.0000 in a separate ph98img file below. Maybe try one of these and it might take care of it. Put these on your sd card, change the name of the first one to ph98img.zip and get into the bootloader hboot and let it update. If that doesn't work, try the second one.
If needed, I could also probably make one for the 3.05.605.12 and upload that as well. I just need to check the hboot version it came with.
ETA, I think the first one came from THIS THREAD and it is just renamed by me so I could keep track of what it was...
mikeyk101 said:
Just trying to think of alternate solutions again, I know that it is possible to change just the hboots by using the proper ph98img.zip files. I remember using one awhile back when I was unlocked that changed the hboot from tampered to read locked. I cant find the thread but I think it came from Vinylfreak . I attached it in this post but it will read 2.27.0000 as the version. I have also included the factory 2.28.0000 in a separate ph98img file below. Maybe try one of these and it might take care of it. Put these on your sd card, change the name of the first one to ph98img.zip and get into the bootloader hboot and let it update. If that doesn't work, try the second one.
If needed, I could also probably make one for the 3.05.605.12 and upload that as well. I just need to check the hboot version it came with.
ETA, I think the first one came from THIS THREAD and it is just renamed by me so I could keep track of what it was...
Click to expand...
Click to collapse
Thanks again for all your suggestions, you've been REALLY helpful.
I'll try out the hboot method you listed above and see what I can come up with. My concern there is that I think vinylfreak's hboot was an engineering hboot, which will brick the phone if I try to go back to S-ON with it installed.
Rezound development is actually still alive and well, among several dedicated developers who are working on some great software for the phone. @Flyhalf205 has been releasing regular updates to his Rezound build of CyanogenMod 10.1 and as I understand it, is responsible for a ton of the recent progress made on bringing Jellybean to the Rezound. @IAmTheOneTheyCallNeo has a fantastic ROM based off of CM called Infection, and a variant of it based on PACMan called Tron. @iHateWebOS has a great kernel called HIRO, @Snuzzo has another one called Funky Kernel, and there are other devs that I'm less familiar with working on other projects. Check out their work, it breathed new life into my phone.
tigerxchaos said:
Thanks again for all your suggestions, you've been REALLY helpful.
I'll try out the hboot method you listed above and see what I can come up with. My concern there is that I think vinylfreak's hboot was an engineering hboot, which will brick the phone if I try to go back to S-ON with it installed.
Rezound development is actually still alive and well, among several dedicated developers who are working on some great software for the phone. @Flyhalf205 has been releasing regular updates to his Rezound build of CyanogenMod 10.1 and as I understand it, is responsible for a ton of the recent progress made on bringing Jellybean to the Rezound. @IAmTheOneTheyCallNeo has a fantastic ROM based off of CM called Infection, and a variant of it based on PACMan called Tron. @iHateWebOS has a great kernel called HIRO, @Snuzzo has another one called Funky Kernel, and there are other devs that I'm less familiar with working on other projects. Check out their work, it breathed new life into my phone.
Click to expand...
Click to collapse
I didn't quite elaborate on what I was thinking. But you are absolutely correct about doing S-on with an engineered hboot and that it would brick it. However, since it is going back as a warranty replacement, maybe bricking it might not be such a bad idea. LOL. I should have added that by using the fake locked hboot, it may trick the phone into thinking it really was locked. And then flash the second one and the banner just might stay showing locked. I have actually gone back and forth between the two but have always been locked so I am not sure how yours would work out. BTW, that second one is the original factory hboot extracted off the full OTApkg.zip for 4.05.605.14 and packaged in a ph98img file. I extracted it in the event that I might have to S-on again sometime in the future. I also extracted the original factory recovery and packaged that in a ph98img file as well in case I ever had to revert back to stock for the same reason. I just have to unroot (I am using supersu), reinstall the factory recovery, reinstall the factory hboot, do a factory wipe in recovery and finally do the write secure flag command and I am golden. I know that there are still many very cool roms out there. I used to be a big fan of CleanROM but that is no longer supported by the developer. Since then I have gotten kind of used to using a rooted stock rom. I know I may be missing some bells and whistles but I mostly rooted and S-offed just because I could and have a few more choices available to me. I hope you are able to find a solution.
I had this happen a wile ago what worked for me was that I ran the ruu to back to stock, then go through the unlock process, once unlocked s-off. Once s-off run ruu, then follow directions in this link http://forum.xda-developers.com/showthread.php?t=1612937
Sent from my Infected Rezound using xda app-developers app
My rooted Evo 4G LTE is running HBOOT 2.09, Android 4.1.1, and radio 1.12.11.1210. And I've been trying for days now to get this thing running on Cyanogenmod 12.
For one thing, most of the tutorials I'm finding have dead links, so I'm having to piece together information.
Plus, I even downloaded a couple RUUs that were specifically for the Jewel, and yet when I ran them, it said I had the wrong one (so my device is now wiped, without an OS).
Most notably, any time I try to get S-Off, I get as far as the "unlock token check successful" message, but then I'm not seeing a prompt on the phone itself that apparently I should be able to press Volume-Up to confirm the S-Off.
I know that part of my difficulty is needing to update HBOOT because several times over, I've seen a message stating that the installer package was made for 2.10 and up.
I've been spinning my wheels quite a bit here, and I'm just lost and could use your help. Any helpful advice would be greatly appreciated :good:
UPDATE: Following the trail of others who have been stuck in S-On, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2492469&page=2
...which led me to try sending a lock command before unlocking, and in that case, I actually got the prompt on the phone's display like I'm supposed to get, BUT if I select 'Yes', it reboots, and gets stuck at the HTC logo (since the OS was wiped with a failed RUU update), and if I power off the phone (by holding the power button for quite a while since the battery isn't removable in this lovely model of phone) and go back to fastboot, I'm still S-On and the CID is SPCS_001.
Here's the output:
C:\Users\admin\Downloads\fastboot-win>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.943s
C:\Users\admin\Downloads\fastboot-win>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.144s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.005s]
finished. total time: 0.149s
C:\Users\admin\Downloads\fastboot-win>
Click to expand...
Click to collapse
Okay, so ultimately where you'd like to get is the latest CM for the jewel, right?
I'm a little confused regarding your current status about s-on/off because the process you're describing is around unlocking your bootloader.
Since you're on 2.09 you've got to do s-off the way i did it way back when using dirtyracun http://unlimited.io/jewel.htm
i honestly don't remember doing this all through linux/ubuntu, (read, i probably went the long way 'round the barn to do it using Windows) but just follow the directions. there are links to the stock RRU's to the right of the page if you want to see the device boot normally before proceeding. This will get you to s-off
next you wan to get to current firmware, I still have a copy of the most recent RUU for the jewel, the one Sprint released and then pulled. You can find it and instructions here https://www.dropbox.com/sh/hl5zaxvdjjokrhm/AAAR5iEqCvTQ09vHhDA0MWODa?dl=0
this will bring your SPCS_001 to HBOOT 2.10 and the 1.13 radio etc. on stock Jellybean 4.3 (as i recall), you will still be s-off and there's no need to unlock your bootloader again; i never did.
once that's all done you can fastboot flash the latest TWRP from here https://dl.twrp.me/jewel/
and then there's the last cm 12.1 build i did (as far as i know it was the last one built and shared) https://www.dropbox.com/sh/r11bcdephdslkvh/AAC8mSKwOkdbug4VGUROlUaYa?dl=0
good luck. i see it was over two weeks ago that you posted this, i just happened to bop over to see if anyone else had been tinkering with cm13 still. hopefully it's still helpful
I'm in the same boat
This post is a couple months old now, but just found it. I was given an old HTC Evo 4g LTE (Jewel) so I'm trying to bring it up to date with current software.
Thanks for the response dangle79.
It looks like I am in the same position as CarpeDiemTim.
I have:
uninstalled HTC Sync
the HTC drivers
fastboot
ADB
Windroid toolkit
Stock rom
android 4.1.1
Hboot 2.09
Software version 3.17.651.9 710RD
I was able to use Windroid toolkit to unlock the bootloader, install super su and root
I was able to install the latest TWRP 3.0.2.0 for the jewel. (I think this is the same as CaptainThrowback's TWRP since he maintains it.)
I downloaded a PAC-Rom for android 5.1.1 and a corresponding Gapps zip.
I made a backup in TWRP and then tried to flash the rom.
When I flash the PAC-Rom, it says it is made for Hboot 2.10+ and mine is 2.09
I am also S-on, so most of the other Roms say that I have to be S-off and have Hboot 2.10+
I found Sunshine, but it is a pay to play and although I appreciate other people's work, I am trying to avoid paying $25 to *maybe* get this working.
I found Moonshine, but it only lists a linux and windows download for rom version 3.16.651.3 (I have 3.17 so not sure this would work, although I didn't try the 3.16 version)
I tried firewater but it wouldn't work. I follow the directions from the website and when I run the command for the firewater file, I just get a blank line after it in the command prompt instead of the firewater program actually running.
I tried rumrunner and it gets all the way to the end and then says that I have two options, one is that I need to install a unsecure kernel or something else. (I think maybe I need to flash a rom that is stock rom but unsecured and then run the rumrunner again)
I have not tried DirtyRancun because I am on windows 7 pro 64 bit. I'll try to do the liveCD thing with ubuntu and see if I can get it with DirtyRacun.
But the instructions on the website are a little vague now that it is so old relating to the software version and running babyracun. He addresses version 3.16 or older than 3.16, but I guess if it applies to 3.16 it would apply to 3.17 too and when he wrote it 3.17 just wasn't out yet.
I am on software 3.17 so I'm not sure if I need to run babyracun or not, I'll try it first and then if it doesn't work try it again without using babyracun.
Again, thanks and I'll post back in a few days when I get to it.