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:
Related
During the process, and after this output, Nothing happens on my phone and the remain locked even though it says it's unlocked...
sending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.159s
whats going on here.
treopro408 said:
During the process, and after this output, Nothing happens on my phone and the remain locked even though it says it's unlocked...
sending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.159s
whats going on here.
Click to expand...
Click to collapse
I had an evo 3d I ended up having to take back and get another one that nothing I did worked to unlock it, tried on windows, mac, tried it like 50 times and nothing worked....not sure of a fix when that happens but in searching on some evo 3d's with certain ruu's it's just not working for i'm sure/hope someone helps ya
Yea same here...this is a Replacement through Asurion...my original the Vibrate motor went out...now im SOL...or Iphone Bound....UGH
Did you flash CWM recovery and then superuser after you unlocked?
JayDaKissEP said:
Did you flash CWM recovery and then superuser after you unlocked?
Click to expand...
Click to collapse
I think he means that it isn't actually unlocking. It says that it's sending the unlock token, but the unlock process that should then start on the phone was never initiated..
(if this is what he's talking about, the same thing happened here.. I had to backtrack myself and do everything over from the start before it would finally unlock it)..
Good luck
Did you run the latest OTA to ensure you are on hboot 1.5? I hust got a replacement phone from Sprint over the weekend and it came out of the box with hboot 1.4. I don't think the official HTC unlock method will work unless you are on hboot 1.5. If you are on hboot 1.4 then you can unlock using the revolutionary tool.
First, this doesn't belong in this section, you should have posted in Q&A.
Second, this has been answered before in the thread about unlocking hboot 1.5. I believe you have to flash the 2.08 RUU an then unlock. I'm on my phone now so I can't link you, but I think it's the first thread linked in the Sticky Rollup thread.
If you aren't on 1.5 as another member mentioned, then don't take the OTA an update your hboot to 1.5. Go to Revolutionary website an unlock that way. It's much easier in the long run as you'll be able to flash radios since you'll be s-off with 1.4, an you'll still be s-on with 1.5 even after unlocking.
Good luck
Sent from my PG86100 using xda premium
Hi..
I had the same problem. I fixed it by first doing all OTA updates (I had to do this twice to completely update the phone) and then using this:
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.exe
And installing right OVER the v2.17.651.5 that the phone currently had. Strange to have to do this, but when done, the HTC unlock worked like a charm.
EDIT:
This is it:
http://www.filefactory.com/file/c19...216_NV_NV_spcs_1.42_release_233304_signed.exe
In looking for a download link to your ROM, but I don't see anything. Or a change log, is this ICS????
Sent from my PG86100 using Tapatalk
stanglifemike said:
First, this doesn't belong in this section, you should have posted in Q&A.
Second, this has been answered before in the thread about unlocking hboot 1.5. I believe you have to flash the 2.08 RUU an then unlock. I'm on my phone now so I can't link you, but I think it's the first thread linked in the Sticky Rollup thread.
If you aren't on 1.5 as another member mentioned, then don't take the OTA an update your hboot to 1.5. Go to Revolutionary website an unlock that way. It's much easier in the long run as you'll be able to flash radios since you'll be s-off with 1.4, an you'll still be s-on with 1.5 even after unlocking.
Good luck
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Listen to this guy. If you have HBOOT 1.4, DON'T TAKE THE OTA UPDATE! Use Revolutionary. If you have 1.5 already, I can confirm that installing the RUU should fix the problem.
Sent from my lean, mean 2.17.651.5 machine using Tapatalk
Right. My post is assuming you are on v1.50, which is why you had to go the HTC unlock route in the first place (like I did). Obviously if you are on 1.30/1.40, you do NOT want to do it this way. Use Revolutionary if on less than 1.50, use the method I posted if on 1.50.
Downloading that new Rom Now...When I woke up this morning I did the HTC update and then it downloaded a 9mb system update...then when that was done I did it again and got a 29mb update...now the Phone is at v2.17.651.5 which was now more updated than I had before.. and downloading the rom link that was posted. It should work after that in theory correct?
I already have the BIN unlock I received from HTC. would the same file work again or do I need to get a new one because of the new updates I flashed to the phone.
Thank You XDA For your Help..
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
treopro408 said:
Downloading that new Rom Now...When I woke up this morning I did the HTC update and then it downloaded a 9mb system update...then when that was done I did it again and got a 29mb update...now the Phone is at v2.17.651.5 which was now more updated than I had before.. and downloading the rom link that was posted. It should work after that in theory correct?
I already have the BIN unlock I received from HTC. would the same file work again or do I need to get a new one because of the new updates I flashed to the phone.
Thank You XDA For your Help..
Click to expand...
Click to collapse
I would get a new one just to be on the safe side (that is what I did). It should work fine after using the RUU update over the updates you already have performed, so yes, it should work fine.
When I run the Rom Update with the Rom Posted earlier in the thread I get an
Error 132 Rom Signature Error...Any Advice?
treopro408 said:
When I run the Rom Update with the Rom Posted earlier in the thread I get an
Error 132 Rom Signature Error...Any Advice?
Click to expand...
Click to collapse
Not sure. Try redownloading?
treopro408 said:
When I run the Rom Update with the Rom Posted earlier in the thread I get an
Error 132 Rom Signature Error...Any Advice?
Click to expand...
Click to collapse
If your running and RUU.exe, you should relock your bootloader "fastboot oem lock". After that run the RUU.exe from your PC to bring your phone back to factory. Then you can install the OTA's. I did this the other day.
treopro408 said:
Downloading that new Rom Now...When I woke up this morning I did the HTC update and then it downloaded a 9mb system update...then when that was done I did it again and got a 29mb update...now the Phone is at v2.17.651.5 which was now more updated than I had before.. and downloading the rom link that was posted. It should work after that in theory correct?
I already have the BIN unlock I received from HTC. would the same file work again or do I need to get a new one because of the new updates I flashed to the phone.
Thank You XDA For your Help..
Click to expand...
Click to collapse
Same Unlock_code.bin will work
Sent from my lean, mean 2.17.651.5 machine using Tapatalk
Well I called Asurion and told them that my phone is not working..."Wont Unlock" and the had me do some trouble shooting...long story short I called them 11am pst on Wednesday and they apologized and said they will send out another replacement for the replacement..got that around 2pm today (They fed ex overnight) was able to Unlock Via HTC. And Flash CWM and reload my Rom..like you all said...it took was a simple exchange...
This is my 3rd EVO 3D, had an hboot 1.4 and 1.5 previously, both unlocked, so I know both methods. My new one is another 1.5, but when I get to Step 12 of the HTC Unlock method, I get the correct response in ADB which is flashing the Unlock_code.bin to the Unlocktoken location. It replies that it flashed correctly but will not leave fastboot usb white screen. Any help here would be greatly appreciated. I did the FOTA Update that removed CarrierIQ and upgraded to the 2.17
nicktheqwik82 said:
This is my 3rd EVO 3D, had an hboot 1.4 and 1.5 previously, both unlocked, so I know both methods. My new one is another 1.5, but when I get to Step 12 of the HTC Unlock method, I get the correct response in ADB which is flashing the Unlock_code.bin to the Unlocktoken location. It replies that it flashed correctly but will not leave fastboot usb white screen. Any help here would be greatly appreciated. I did the FOTA Update that removed CarrierIQ and upgraded to the 2.17
Click to expand...
Click to collapse
Whats the size of the bin file when it sends?
I had that problem and i used ruu wich i found on xda page. To download the software number if your last s.# is 3 or higher thats the problem
Sent from my HTC.EVO.3D.Xda Premium
megabiteg said:
Whats the size of the bin file when it sends?
Click to expand...
Click to collapse
It looks like it is 1kb. Seems kinda small.
nicktheqwik82 said:
This is my 3rd EVO 3D, had an hboot 1.4 and 1.5 previously, both unlocked, so I know both methods. My new one is another 1.5, but when I get to Step 12 of the HTC Unlock method, I get the correct response in ADB which is flashing the Unlock_code.bin to the Unlocktoken location. It replies that it flashed correctly but will not leave fastboot usb white screen. Any help here would be greatly appreciated. I did the FOTA Update that removed CarrierIQ and upgraded to the 2.17
Click to expand...
Click to collapse
I had this same trouble until I flash the 2.08 RUU Once I did this it unlocked immediately
you need to use this ruu
you need to use this ruu to downgrade the software number
(it will wipe all your data)
http://www.scottsroms.com/downloads.php?do=file&id=9
Efrencalvario said:
you need to use this ruu to downgrade the software number
(it will wipe all your data)
http://www.scottsroms.com/downloads.php?do=file&id=9
Click to expand...
Click to collapse
OK, but how would I flash this if I can't unlock the bootloader to get to recovery? Do I just download the file and the rename it PG86IMG.zip and then copy it to the SD, then let reboot into the bootloader, and answer yes when it asks if I want to install the update?
You won't be able to run the lower 2.08 Ruu since u took the update. You have to use the full 2.17 Ruu.zip that xhausx posted, then the unlock will work. See guide/flashing notes in my signature for details & link.
Yes, the process u described is correct for using the zip.
Sent from my PG86100 using Tapatalk
nicktheqwik82 said:
This is my 3rd EVO 3D, had an hboot 1.4 and 1.5 previously, both unlocked, so I know both methods. My new one is another 1.5, but when I get to Step 12 of the HTC Unlock method, I get the correct response in ADB which is flashing the Unlock_code.bin to the Unlocktoken location. It replies that it flashed correctly but will not leave fastboot usb white screen. Any help here would be greatly appreciated. I did the FOTA Update that removed CarrierIQ and upgraded to the 2.17
Click to expand...
Click to collapse
I'm curious, you say you've had others before, did you get them replaced with sprint? (for free via insurance)
I'm wondering about HTC's unlock flagging the phone so that they will charge me if I unlock it...
Why are you on your 3rd EVO 3d
Sent from my HTC EVO 3D X515m using Tapatalk
The RUU in footballs thread always worked in the past
It seems like the questions about returning to 100% stock are coming up more often lately, possibly because more users are moving on to other devices. Whatever the reason, I thought a simple guide might be useful to avoid having to duplicate this info in other threads and PM's.
This procedure should work for any CDMA or GSM Evo 3D/V that is S-OFF. There is no way to get an S-ON device that has been HTC unlocked back to 100% stock since relocking the bootloader will result in a status of "relocked".
Here are the steps to do it:
1. Flash the "query_bootloader.zip" file attached to this post in recovery. If the status message shows your bootloader is "unlocked" or "relocked" flash the "lock_bootloader.zip" file from the same post to reset it to "locked".
2. Download an RUU.exe (Windows) or RUU.zip (bootloader) file for your model from this page and flash it using the appropriate method.
If you use the .exe version from Windows it works best if you put the phone into "fastboot USB" mode, and you may have to cancel the RUU utility and restart if it hangs after flashing the stock bootloader when you start with a custom hboot installed.
To flash the RUU.zip via the bootloader it must be renamed to PG86IMG.zip and placed in the root of your SD card, and may need to be flashed twice if a custom hboot is installed the first time it is flashed.
I recommend using the latest version for your model but any compatible RUU can be flashed while S-OFF. It's also a good idea to boot the ROM without doing any setup after flashing the RUU to make sure the ROM has been reset to the stock version.
3. Confirm that the bootloader shows "***LOCKED***" on the top line of the screen and the HBOOT version is a stock bootloader for your device.
4. Issue the "fastboot oem writesecureflag 3" command from a PC.
Note: Make 100% sure you have the stock bootloader installed before issuing this command or you will brick your phone.
Your phone will now be 100% stock.
ramjet73
Thanks for the nice toturial but i´m just wondering one thing.
If you fail with the command
Code:
fastboot oem writesecureflag 3
, will your phone get hardbricked or is it possible to flash a recovery and start over again with fastboot?
dR.BaNaNe said:
Thanks for the nice toturial but i´m just wondering one thing.
If you fail with the command
Code:
fastboot oem writesecureflag 3
, will your phone get hardbricked or is it possible to flash a recovery and start over again with fastboot?
Click to expand...
Click to collapse
If that command fails nothing will happen and your phone will stay S-OFF but the odds of that happening are very small unless your phone is not in "fastboot usb" mode when you issue it.
The risk involves issuing that command when you have a custom hboot like JBear or Revolutionary installed because those bootloaders are not signed and will cause the phone to brick. In that scenario you would not be able to get into recovery.
ramjet73
Ok thanks man.
Ok, in the RUU's I can download I have 2 problems:
1) How do I know which one to download? I see a few that have Sprint ICS. I have the Virgin Mobile phone Evo V 4g. Which one would I get?
2) I have already tried downloading a few of them, and each time it stops at a different point and windows says the zip file is not valid. Is there another place I can download the correct RUU?
I need to get this done soon as I have a replacement headed this way.
matt965 said:
Ok, in the RUU's I can download I have 2 problems:
1) How do I know which one to download? I see a few that have Sprint ICS. I have the Virgin Mobile phone Evo V 4g. Which one would I get?
Click to expand...
Click to collapse
This is the correct RUU for your phone.
2) I have already tried downloading a few of them, and each time it stops at a different point and windows says the zip file is not valid. Is there another place I can download the correct RUU?
Click to expand...
Click to collapse
If that link doesn't work for you the same RUU is available here, including an MD5 checksum you can use to verify the download.
I need to get this done soon as I have a replacement headed this way.
Click to expand...
Click to collapse
ramjet73 said:
1. Flash the "query_bootloader.zip" file attached to this post in recovery. If the status message shows your bootloader is "unlocked" or "relocked" flash the "lock_bootloader.zip" file from the same post to reset it to "locked".
Click to expand...
Click to collapse
how do i do this if i have no working recovery? iv been trying to ruu with RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_219445_signed.exe
iv tried many ruu's but only 2 have ever gone through. when it does i just get reboots on htc screen. recovery does not seem to work.
thanks for the help. hope i havnt bricked my phone
birddseedd said:
how do i do this if i have no working recovery? iv been trying to ruu with RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_219445_signed.exe
iv tried many ruu's but only 2 have ever gone through. when it does i just get reboots on htc screen. recovery does not seem to work.
thanks for the help. hope i havnt bricked my phone
Click to expand...
Click to collapse
This is the wrong thread for what you need to do and I posted a link to the correct guide in the thread you opened in the development forum that got moved to Q&A.
When you are ready to download the RUU look for the 2.89.651.2 version.
ramjet73
thank you ramjet for the link. my phone is now 99% stock. The 1% is because of the S-OFF part of the bootloader. It shows it is locked so that's good, but I think that means I can't turn S-ON, as it says in the first post. Oh well, hopefully they will accept it like that.
matt965 said:
thank you ramjet for the link. my phone is now 99% stock. The 1% is because of the S-OFF part of the bootloader. It shows it is locked so that's good, but I think that means I can't turn S-ON, as it says in the first post. Oh well, hopefully they will accept it like that.
Click to expand...
Click to collapse
if you figure out how to get jb roms to boot post back so we all can know how
birddseedd said:
if you figure out how to get jb roms to boot post back so we all can know how
Click to expand...
Click to collapse
JB roms don't boot with this phone??? Strange since mine booted just fine with them.
matt965 said:
JB roms don't boot with this phone??? Strange since mine booted just fine with them.
Click to expand...
Click to collapse
They do.
This is the wrong thread to discuss booting JB ROM's and I don't know why he posted that here.
ramjet73
Thanks for this thread, great to go back to 100% stock for warranty purposes...
But for sellers who's warranty has run out, the newest JB or ICS rom is the best
Which RUU do i use for a Sprint Evo 3?
I'd like to follow the instructions here; you pointed me to this OP in another reply when I asked how to go back to stock, but I don't know which one to use. I'm on hboot 1.50.5050 running CM 10.1 on a Sprint Evo 3D, using "Wild for the Night" and I want to go back to 100% stock, S-ON, unrooted, locked.
Is 'WWE' the US version? I know not to use RUUs for other countries but I can't tell which to use from the list.
(I used the jbear wire trick and have Ext4 installed if it makes any difference.)
occulus said:
I'd like to follow the instructions here; you pointed me to this OP in another reply when I asked how to go back to stock, but I don't know which one to use. I'm on hboot 1.50.5050 running CM 10.1 on a Sprint Evo 3D, using "Wild for the Night" and I want to go back to 100% stock, S-ON, unrooted, locked.
Click to expand...
Click to collapse
This is the RUU you want to use.
ramjet73
Does it work for EVO 3D GSM with Revolutionary?
Sorry for my english.
ramjet73 said:
This procedure should work for any CDMA or GSM Evo 3D/V that is S-OFF. There is no way to get an S-ON device that has been HTC unlocked back to 100% stock since relocking the bootloader will result in a status of "relocked".
Click to expand...
Click to collapse
t_mcpardi said:
Does it work for EVO 3D GSM with Revolutionary?
Sorry for my english.
Click to expand...
Click to collapse
Probably not, since ramjet said that in the OP.
t_mcpardi said:
Does it work for EVO 3D GSM with Revolutionary?
Sorry for my english.
Click to expand...
Click to collapse
raptoro07 said:
Probably not, since ramjet said that in the OP.
Click to expand...
Click to collapse
If he has Revolutionary and is S-OFF this guide should work as long as the RUU is available for the model of his phone. That's the only thing that is specific to the GSM or CDMA model.
ramjet73
Which ruu do I use I'm running hboot 1.50.5050 and bootloader is unlocked
rafylora1230 said:
Which ruu do I use I'm running hboot 1.50.5050 and bootloader is unlocked
Click to expand...
Click to collapse
The hboot doesn't matter, but if you are on Virgin Mobile you need this one.
ramjet73
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
Full disclosure, this isn't my phone and I'm helping a coworker who did some things. The phone was originally purchased without service as she was switching from AT&T to T-mobile and didn't have it setup yet.
Incident: The phone was unlocked and rooted when last night she used a "toolkit" (I have no idea which one and she said she deleted the folder with everything), then locked it with the toolkit and used the fastboot oem unlock to get back in. When the stock rom was installed again the screen wouldn't work and I was able to navigate with a OTG mouse connected. All of the custom roms work fine as far as the screen goes but the stock one is like it's missing a driver. The other issue here is the SIM card doesn't pickup a network, I verified the Access Point is setup correctly and tried with both the LTE (fast) setup and regular. It's entirely possible that the radio was hosed to start with and we didn't find out until the sim card was purchased on Monday. At this point I'd just like to get it back to FULL stock and see if she can do anything with the Warranty (not sure if this is really possible yet). So, on to things I've tried.
1. Display Issue on Stock, I read this could be a kernel issue and attempted to flash several Stockish roms from here. Also the kernel from mugetsu666. That kernel a long with the other 3-4 stock roms from page 1. Nothing resolved.
2. No Signal. While going through the stock and custom roms all I really need is the signal to work. The PA install had the wrong APN settings and I updated them with the Defaults. No change, so I moved on to radios, maybe that's it. Flashed all the radios from here and a couple other random ones from the individual rom I was using. Nothing.
3. Ok, at this point I just want back to stock. This phone is toast and I'm tired of dealing with it for the day. Found the t-mobile ruu file here and attempted to run it as admin on a windows 7 and 8 machines. The bootloader was locked before attempting this and I tried in fastboot or just the phone being on. All I get is error 170 which is the usb connection issue. Fastboot does recognize my device so the RUU should pickup, now i'm really stuck.
Needless to say it's hasn't been a productive day at work. Any assistance is greatly appreciated. THANKS!!
I see you tired the T-Mobile ruu have your tried offival att ruu yet?
Sent from inside the T.A.R.D.I.S
joselv456 said:
I see you tired the T-Mobile ruu have your tried offival att ruu yet?
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
You should run the revone s-off before you do anything after unlocking the bootloader. The first RUU should have been ATT since it is an ATT phone, like the last poster mentioned. After you unlock the bootloader, run revone to get s-off, then get superCID and run whatever RUU you like ATT,GPE, or T-Mo.
This one?. The link is dead. Can I use another supercid by at or M7?
Thanks for the help. I'm really a Samsung user so this is new
C Murder said:
You should run the revone s-off before you do anything after unlocking the bootloader. The first RUU should have been ATT since it is an ATT phone, like the last poster mentioned. After you unlock the bootloader, run revone to get s-off, then get superCID and run whatever RUU you like ATT,GPE, or T-Mo.
Click to expand...
Click to collapse
Bootloader unlocked
s-off complete
CID-11111111
I'm running the Signed2 from this list.
http://www.androidruu.com/index.php?developer=M7
Error 170, USB issue. Fastboot can see the device but the RUU can't, odd.
Edit: Running the RUU when the phone is booted to PA gets pasted the error 170. Now it's an error 155 and it's stuck on the HTC logo. Powering it off and it's still hosed.
Sooooo, I think there is more wrong here than a simple RUU update. I noticed under the *** UNLOCKED *** that the model is M7_UL, which i'm finding is a Europe model. I'm toast.. warm buttery toast i think.
Side note: Don't offer to help coworkers if you haven't worked on a phone like this before.
I have m7ul which was originally a t-mobile device when I got it used. I flashed the GE ruu no problem. You should be ok with that device.
Sent from my HTC One using Tapatalk 4
kronikwisdom said:
Bootloader unlocked
s-off complete
CID-11111111
I'm running the Signed2 from this list.
http://www.androidruu.com/index.php?developer=M7
Error 170, USB issue. Fastboot can see the device but the RUU can't, odd.
Edit: Running the RUU when the phone is booted to PA gets pasted the error 170. Now it's an error 155 and it's stuck on the HTC logo. Powering it off and it's still hosed.
Click to expand...
Click to collapse
Did you try running the tmobile RUU.exe from your pc. I know it's in the Tmobile HTC One forum. I'm sure it's here somewhere too. The kernels and recovery are there too, with guides to take you back to stock.
C Murder said:
Did you try running the tmobile RUU.exe from your pc. I know it's in the Tmobile HTC One forum. I'm sure it's here somewhere too. The kernels and recovery are there too, with guides to take you back to stock.
Click to expand...
Click to collapse
Yes, I've tried the tmobile RUU from these forums.
I've just made things worse now it seems because I updated the CID back to "T-MOB010" and now the recovery image won't stick. Seems like I'm missing something else from the boot.img but I've tried to flash the original firmware.zip on these forums. So tired of this thing.
Monday and I'm still at this. After relocking my boot loader per the request of the owner I'm unable to unlock it now. Requested a new code and that didn't change anything. The command to unlock from fastboot completes and writes successfully but the screen doesn't popup on my phone to accept the unlock.
Fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 kb)... <--- not sure if that's correct, the file is actually 256b but maybe it's under 1 so it doesn't show.
OKAY [ 0.150s ]
writing 'unlocktoken'...
OKAY [ 0.010s ]
finished. total time: 0.160s
this phone is going further down hill.
last ditch effort and I ran the RUU from Tmobile on an old XP machine, worked. back to stock.. not sure what to say but i'm tired of looking.. haha
I don't know why she needed to do all that soff in the first place ... This device doesn't require soff to flash roms or even soff to flash tmobile roms on the att m7 or vise versa
It's a lot like nexus model the boot.img flashes In roms soff is usually needed to do that on other htc devices not the One
Simple carrier unlock and Bootloader unlock with recovery is all you need to flash any Rom onto any m7 besides sprint and vzw
Soff and supercid doesnt seem like it was necessary in her case
HTC is touchy stuff takes reading 10 times over before attempting anything...
If we had a samsung Odin method we would be golden ..
Glad it's fixed
Sent from my HTC One using xda app-developers app