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:
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
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
Hey, I am trying to root my HTC evo 3d phone with hboot 1.58. I followed all 12 steps on htcdev.com, except on the final step I punch in: fastboot flash unlocktoken Unlock_code.bin and enter, then noting happens. The phone is supposed to reboot with the unlock option..but nothing happens
Also, the phone is Sprint CDMA if that makes any difference, so no sim card
....................................................................................................................................................................
THREAD SUMMARY
K finally got th phone rooted so here is what you have to do. The following applied to my ***locked*** S-ON Sprint HTC Evo3d with hboot 1.58 but should work with any other version higher than hboot 1.40.
The purpose is to get S-OFF(ROOT the phone) and also continue to use your factory HbOOT 1.58 and main version in the end.
1. Brick the phone carefully following steps outlined in unknownforce's [TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset). Scroll down to the "Downgrade/Unbrick" section and begin the bricking process with the PG86IMG.zip he mentions in "things you'll need".(place the zip on SD card in the main directory and name it PG86IMG)
2. Once phone is bricked(indicated by SOLID and very dimly lit charge light with the AC charger connected. Also the phone will not turn on or boot), download latest version of URT 3.1(first link in [TOOL] thread), continue to the second step 2 which involves booting up with Linux live boot CD on your PC, OR you can use URTLiveCD 1.0 and you will not need Linux
I did it the hard way an used latest version of URT with Ubuntu v12.04 LiveCD. I would recommend URTLiveCD 1.0 as you will boot straight to the tool and will not need the Ubuntu terminal.
3. After successfully completing downgrade with URT 3.1 downgrade, boot up to your new HBOOT 1.40 bootloader screen and enter fastboot USB mode. CHECK THAT THE MAIN VERSION HAS BEEN LOWERED ALONG WITH THE HBOOT.
Log back into windows
3.(A) If you haven't done this yet, get a fastboot PC command directory to retrieve all phone identification info from the bootloader. I used ROOTEVO3DNEW to check my phone's identity info at this point(though there are many programs that do the same thing). Create a new folder in C:\ and name it rootevo3dnew. Unzip all rootevo3dnew.zip contents into that folder.
Now open the command prompt with the phone connected to PC in fastboot USB. Type cd \rootevo3dnew and enter. Now type the following: "fastboot getvar all" (without quotations) and enter. A list should appear. Check that you have: (bootloader) version-main: 0.01.651.1. If this number is still 2.95.XXX.XXX or something close to it, then YOU MUST BRICK THE PHONE AGAIN. See posts starting at #35 of this thread for a more detailed guide through the second brick. It may be very tricky but very much the same process!!!!!
4. After successfully lowering HBoot to 1.40 and the main-version to 0.01.651.1 you can run the 1.13 RUU.exe found HERE: http://d-h.st/h1p . Connect the phone to fastboot USB and RUN the .exe....after the 1.13 .exe successfully runs, your main version should now be 1.13.651.7...again, checking using your rootevo3dnew tool from 3.(A) above....
5. REVOLUTIONARY S-OFF. Very simple, download for windows(or Linux) and fill in your info and retrieve you BETA key. Run REVOLUTIONARY application (which will run in the command prompt) and after successfully completely revolutionary S-off, YOU ARE ROOTED...continue to step 6
6. RESTORE your main version to 2.95(from 1.13) by running the 2.89 zip (HERE . Place this .zip in your main directory(RENAME IT PG86IMG) on the SD card and let it unzip and install it from the bootloader.
After that, you are pretty much finished!! boot up to android(main version 2.89) and let system updates detect and bring you back to 2.95.xxx.xxx..
....
Download and Install a custom recovery. Rename that .zip PG86IMG and install from bootloader as you did with the 2.89 zip. Now you have a custom recovery where you can backup and restore, install ROMS or other software without having to rename it PG86IMG every time, wipe partitions and lots of other stuff...
Now, download this and place it on your SD main directory. Then, using your new recovery(by selecting "recovery" in bootloader menu), select "install from sdcard" and "choose zip from sdcard", select the SuperSU zip and let it install. Reboot, get to homepage, and install SuperSU from the play store. You now hae an administrative super APP that will let you choose which apps are given root access.
Custom ROMS can be installed the same way from the custom recovery. I am currently using Negalite BluRom and loving it
...
THE 6 STEPS OUTLINED HERE PRETTY MUCH COVER EVERYTHING FROM THIS THREAD
HUGE THANKS TO USERS MPGRIMM2 AND BRIAN706 FOR NEARLY 3 DAYS OF HARD WORK !!
Did you get your motherboard replaced at some point of time?
Can't think of a good sig
donkeykong1 said:
Did you get your motherboard replaced at some point of time?
Can't think of a good sig
Click to expand...
Click to collapse
My what? Yes I swapped out my 67370m dv6 pavilion mainboard for radeon HD 6550m graphics chipset. How did you know?
otto325 said:
My what? Yes I swapped out my 67370m dv6 pavilion mainboard for radeon HD 6550m graphics chipset. How did you know?
Click to expand...
Click to collapse
On the phone?
Can't think of a good sig
donkeykong1 said:
On the phone?
Can't think of a good sig
Click to expand...
Click to collapse
Oh ok, what the hell..No, I just got the phone on ebay for $30, currently locked and I am trying to root it. Some Brittney girl owned according to phone identity info left on the phone
Do I need to downgrade the hboot from 1.58 to 1.4? Sorry I'm really new to smartphones, any help is really appreciated
Just in case it was missed, the phone doesn't reboot upon flashing the unlock token. A prompt should appear on the device and you have to confirm the bootloader unlock.
He asked about the motherboard, because there is an issue if the motherboard has been swapped; sometimes the bootloader will not unlock. I think it's due to mismatched firmware.
Usually running the RUU will solve the issue.
You can download a copy here: https://copy.com/jF1Mm
The only problem is, if the phone had taken the latest Ota update and you are on main version 2.95 instead of 2.89, the RUU will not run because it won't let you downgrade.
You can also check your main version by running a fastboot getvar all.
Is there any chance your device is already s-off from a previous owner? It will say s-on or s-off on the bootloader screen.
If you're lucky enough to already have s-off, you can skip the bootloader unlock altogether.
Brian706 said:
Just in case it was missed, the phone doesn't reboot upon flashing the unlock token. A prompt should appear on the device and you have to confirm the bootloader unlock.
He asked about the motherboard, because there is an issue if the motherboard has been swapped; sometimes the bootloader will not unlock. I think it's due to mismatched firmware.
Usually running the RUU will solve the issue.
You can download a copy here: https://copy.com/jF1Mm
The only problem is, if the phone had taken the latest Ota update and you are on main version 2.95 instead of 2.89, the RUU will not run because it won't let you downgrade.
You can also check your main version by running a fastboot getvar all.
Is there any chance your device is already s-off from a previous owner? It will say s-on or s-off on the bootloader screen.
If you're lucky enough to already have s-off, you can skip the bootloader unlock altogether.
Click to expand...
Click to collapse
THANKS
main version 2.95.651.5. If I factory reset the phone and discard updates, will the main version reset to 2.89 making the RUU possible?
EDIT: factory reset and no updates did not bring main version down to 2.89
***LOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
Also check most recent post (#508) in the guide thread.
http://forum.xda-developers.com/showthread.php?t=1889438&page=51
Factory reset won't affect your main version
As DK mentioned, a factory reset only resets your current build. It would only take you back to the point of the last OTA update.
Unfortunately, you can't lower the mainversion without the bootloader unlocked, so it's a catch 22 there.
As a long shot, you might look into the new towelroot, thought I really don't think it will work for this phone because HTC locks down the /system partition. It would at least be worth looking in to.
As far as the hboot downgrade method (I assume you mean THIS) it was intended to downgrade from 1.50 Gingerbread to 1.40 Gingerbread. I have no idea if it will work to downgrade from 1.58 ICS?? You might want to ask around a little about that.
Okay... I just saw your posts in the other thread, have you actually received the unlock token from HTC?
IE, you received a file via email named Unlock_Code.bin that you placed in your fastboot directory and then typed the command: fastboot flash unlocktoken Unlock_code.bin ??
Also, when you say nothing happens after running the command, something must happen whether it's the intended results or not. Can you tell us what the command prompt returns after running the command? Maybe just copy/paste it here.
There will either be an error or a confirmation after running the command.
Comes up as successful on the command prompt. But the phone does not reboot or direct to the unlock screen. I just remains on the fastboot USB screen and does nothing.
C:\rootevo3dnew>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.153s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.163s
Thanks for that... That's a bummer. Looks to me like you have the motherboard swap issue. It really sucks that you can't RUU.
It looks like someone answered the question in the other thread though about the hboot downgrade method.
So I got the HBOOT downgrade(0.8.2) boot for a disk but it says the phone needs to be bricked before the downgrade..
That's where I'm at now basically, I'm going to do a little more reading on bricking...
Also would be good to have confirmed that this downgrade will work starting with hboot 1.58, so I don't mess anything up
mpgrimm2 may have found found his way over here from from the [Guide] thread
Also I hope I am downloading the correct RUU's. I had to fish them from various searches because the link supplied in Unknownforce's thread is invalid:
2.17 RUU:
http://d-h.st/ru0ow8ps0i01/PG86IMG_2.17.651.5.zip
1.13 RUU:
http://d-h.st/Xrp
mpgrimm2 said:
Well. Post that in Unknownforce's Ultimate Recovery Tool thread so you are not "off topic" here.
I haven't used the Evo3d in a while but you should probably look over my ...
Post 781 in Unknownforce's thread and the follow up posts right after.
Additional info you may need from my
[Guide]My Hboot 1.5x HTC Unlock/recovery/rom/kernel flashing notes 2-13-13
and
Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself)
Click to expand...
Click to collapse
Fyi, I think Unknownforce indicated in one of his first 3 posts that u can brick with the last 2.95 PG86IMG.zip file he linked and then downgrade to 1.13 for s-off. Have to go check...
Keep in mind that you may want to considering posting any issues with the URT/Downgrade tool in Unknownforce's thread if you want any chance of assistance from him.
Bad link in his op but this post has it...
Unknownforce said:
Well, with the 2.95 OTA, they included the HBOOT in the firmware, so it's now much faster of a load time for PG86IMG when doing the brick.
I pulled the new PG86IMG.zip from the OTA update, and it's only 19MB, which takes only 15-20 seconds to fully load and be ready to press volume up to update... this will significantly cut down on the time it takes to downgrade, as you can re-try over and over very quickly now.
Here's the PG86IMG file -> http://d-h.st/3p8
Click to expand...
Click to collapse
And just as a reference for you later I will quote myself from Ramjet73's 2.95 ota update thread
mpgrimm2 said:
ramjet73 and others. I see we still don't have any source for the 2.95.651.6 RUU's. Since I just went ahead and reset my 2 Evo3d's back to stock/S-off as a backup here are the files I had to step through if you want to add or host them directly:
- PG86IMG 2.89.651.2.zip - 449.18 MB
Full RUU.zip for use in bootloader (rename to PG86IMG.zip & place on /sdcard)
- OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.5-2.89.651.2_release_307948lagg6bmccb9c63ip.zip - 51.11 MB
2.89.651.2 update to 2.95.651.5 zip for use in bootloader (rename PG86IMG.zip & place on /sdcard ) or stock recovery (place in /sdcard/download )
This is the last official update that just downloaded to my phone after the other Ruu's/updates that were posted previously
- OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.6-2.95.651.5_release_315505rm3j000awvlstw9z.zip - 10.59 MB
2.95.651.5 update to 2.95.651.6 zip for use in bootloader (rename PG86IMG.zip & place on /sdcard ) or stock recovery (place in /sdcard/download )
Wish someone with HTC/Sprint access would post up the latest full RUU. It was a bit of a pain stepping through the updates, but definitely easier being s-Off. Seems that if someone is S-On with the 2.95.651.6 update and can't get past step 13 of the HTC Unlock or needs to RUU back, their only option is Unknownforce's Hboot Downgrade Ultimate Toolkit and "Brick it Twice" to get back to an earlier version for Revolutionary S-Off and then go through the updates from 2.89 on up.
Hope this helps others.
EDIT:
I may be too tired at the moment to figure this out, but for some darn reason both the official OTA Updates would not flash from the bootloader on a stock 2.89.651.2 phone with S-Off (both phones actually). Didn't matter if it was renamed PG86IMG.zip or left as officially downloaded to sdcard/download and booting into the stock recovery. The MD5 of my 651.5 update file matches Ramjet73's as well. But If I connect to wifi, do a system update, let it download (how I got the files) and reboot automatically, it works fine and updates without issue.
Click to expand...
Click to collapse
Forgive me for being such a noob with this stuff.
I'm reading about hboot 1.58 needing to be bricked twice to be able to run the 1.13 RUU.
So to start, do I place the 18.7mb PG86IMG .zip (from the second quote in your last post) in the "download" folder of the sd card?
The stock
(OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.6-2.95.651.5_release_315505rm3j000awvlstw9z)
Click to expand...
Click to collapse
is there, so do I remove that one and replace it?
I don't think so but just to be sure, I drop the 18.7 PG86IMG zip folder in downloads and begin the brick process, then run the hboot 0.8.2 to downgrade?
*EDIT* ok, place in the MAIN directory. It's working and is unloading the .zip in bootloader
I need a new data sync cable, mine has started intermittently losing connection off and on...going to wait until I have a new one before I go any further.
Also, the latest version of ubuntu that Linux offers did not work. I found an earlier version(12.04) and the boot disk works so I am good to go on that
What is Hboot 0.8.2 ? Are you using Unknownforce's URT 3.1 Tool and following the "Downgrade/Unbrick" section?
This one:
http://forum.xda-developers.com/showthread.php?t=1563342
Yep, that is an outdated/earlier version. You need to use the Ultimate Recovery Tool from Unknownforce's thread as I linked earlier (URT v3.1) and use the LiveCd link.
see here
Sent from my "Up All Night Sleep All Day" Nexus 5!
THANKS
Well I just did a dry run with the Linux boot disk and terminal. Extracted downgrade.zip to HOME folder, ran the commands. I'm getting the correct code returns in the terminal. I got up to the:
Code:
Step 1... Plug in Device while holding down Volume Down key...
Waiting for device...
Just a matter of getting a new data sync cable now and I can do this...
Again thanks for your help, I'm pretty new to this process I've never altered a devices firmware manually before so it's an awesome experience as well..
Will report back in a couple days, hopefully with a newly rooted phone
--------
Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?
otto325 said:
Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?
Click to expand...
Click to collapse
Yep. Previously...
mpgrimm2 said:
....
Additional info you may need from my
[Guide]My Hboot 1.5x HTC Unlock/recovery/rom/kernel flashing notes 2-13-13
and
Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself) <<<--- HERE
Click to expand...
Click to collapse
Sent from my "Up All Night Sleep All Day" Nexus 5!
The back story...
I had to ditch Verizon. I didn't want to fork over $300 for a Republic Wireless phone only to be stuck with their crappy ROM, and the only 4G LTE android phone supported by Ting is the Evo 4G LTE; picked one up for $50 on ebay. I installed Cyanogenmod on a half dozen devices, newer and older than this phone, and thought this HTC Evo 4G LTE would be as easy as they were to unlock, root, S-OFF and flash. I've been more wrong before, but not without resulting in bodily harm. A hearty 'get stuffed' to HTC for this, and a plea for future rooters to have a concise guide on how to repair their phone under these circumstances.
The flawed process...
I went through HTC's unlock method to unlock the phone. Then I installed the latest TWRP via fastboot command line (2.7.1.0b as I found in a thread somewhere). No problems so far... I then went to install the latest CM build for Jewel (10.2.0 ) through TWRP 2.7.1.0b and it failed. This marked the first time I'd ever seen a fail message in TWRP. I thought no big deal, I'll restore the backup... The backup was gone. Now we have problems; phone is stuck in a bootloop. After reading many threads stating that S-OFF is required to flash their ROM, I tried to achieve that in Windows 7 to no avail through all available means. I then tried the closest RUU for my phone, and it failed. I then tried every RUU I could find, all failed. I tried a full firmware update to 4.13 via PJ75IMG.zip on the SD card, which failed.
The repair process that worked for my situation...
Once I focused on the HBOOT as a potential issue, I found this thread: http://forum.xda-developers.com/showthread.php?p=40848479#post40848479
Quite simply, MeanBean 3.09 worked as advertised, and my phone has booted into a ROM for the first time in days! A HUGE thanks to both Magnum_Enforcer and mikeyxda.
Specific phone information
TAMPERED
UNLOCKED
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.13.11.0830
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012, 15:46:20
IMAGE CRC
rpm: 0xBC1CB8D
sbl1: 0x507A9B32
sbl2: 0xEAF345D0
sbl3: 0xD5BB18AD
tz: 0xFB084399
radio: 0xC78A66EB
boot: 0xB683E2D
recovery: 0xB47A92E4
system: 0x376A0C9B
Software Version Reported by RUU: 3.17.651.5
Glad to help:thumbup:
Sent from my HTC device
I'm going to keep this log going, since I think quite a few people will follow a similar path as I'm following.
Just tried to achieve S-OFF with the new MeanBean ROM I'm running.
First attempt: Firewater
All of the steps went exactly as expected. The command line dialog was amusing, and ended in "nasty, needs a chaser" or something and rebooted to the ROM. Once rebooted into recovery to verify s-off status, S-ON is reported.
Second attempt: Rumrunner
More interesting dialog in the process, and it, too, went smoothly. Rebooted into bootloader and voila...S-OFF achieved.
Installed Dirty Unicorns 4.4.4
So, after the first day's use I've come to realize that my PRL needs updating and the Dirty Unicorn 4.4.4 ("du_jewel_4.4.4_20140621-0657") ROM doesn't have a 'Update PRL' function as far as I can tell. I backed up DU 4.4.4 and restored MeanBean, updated the PRL, and restored back into DU 4.4.4 with ease.
After using DU for a week, I've come to realize it's fairly unstable. I'll be looking for a different rom soon.
OMG!!!! FINALLY!!!
I've been reading and reading and pulling my hair out for 3 days after attempting to load a custom Rom on my Evo 4G LTE.
I have almost exactly the same situation/experience as you did. I was able to get the CyanogenMod to load but for the life of I can't get any gapps installed. I've tried loading from TWRP and the SDcard to no avail. It looks like it flashes fine but when I reboot the phone no apps are installed. I like CM 10.2.0 but I need the Google apps. Right now I'm missing so many things like contacts, etc. I've tried to install Google Play and just download each app individually but it crashes on start. I'm really feeling lost here and helpless. I never had problems like this with my original EVO or EVO 3D. Tried to go back to stock using Sprint RUU's but nothing works...
I've highlighted my differences in RED.
Is there anyway you could explain your method to get your EVO S-off in more detail? Is this the problem?
SethW said:
The flawed process...
I went through HTC's unlock method to unlock the phone. Then I installed the latest TWRP via fastboot command line (2.7.1.0b as I found in a thread somewhere) (I loaded TWRP 2.7.1.0 which seemed to work) . No problems so far... I then went to install the latest CM build for Jewel (10.2.0 ) through TWRP 2.7.1.0b and it failed (I was able to load CM 10.2.0 through Fast Boot boot.img command) . This marked the first time I'd ever seen a fail message in TWRP. I thought no big deal, I'll restore the backup... The backup was gone (Same here, Backup gone). Now we have problems; phone is stuck in a bootloop (I watched the CyanogenMod screen spin for 2 hours). After reading many threads stating that S-OFF is required to flash their ROM, I tried to achieve that in Windows 7 to no avail through all available means (same here, tried several ways but nothing worked for Windows 7). I then tried the closest RUU for my phone, and it failed (same here). I then tried every RUU I could find, all failed. ( I tried a full firmware update to 4.13 via PJ75IMG.zip on the SD card, which failed.
Specific phone information My Info is exactly the same
TAMPERED
UNLOCKED
JEWEL PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.13.11.0830
OpenDSP-v31.1.0.45.0815
eMMC-boot
Oct 18 2012, 15:46:20
Software Version Reported by RUU: 3.17.651.5
Click to expand...
Click to collapse
airdog99 said:
Is there anyway you could explain your method to get your EVO S-off in more detail? Is this the problem?
Click to expand...
Click to collapse
I just ran the program as it specified. Make sure your drivers are installed correctly... that step usually caught me up because some Android device drivers conflicted with some of my other Android device drivers.