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
Related
so this is what i have. software is on 2.08.651.3 and i have hboot 1.50
tried doing the dev unlock but keep getting error 173. any ideas
mecksg1 said:
so this is what i have. software is on 2.08.651.3 and i have hboot 1.50
tried doing the dev unlock but keep getting error 173. any ideas
Click to expand...
Click to collapse
Update software to 2.17 latest radios and everything.... Then do the unlock thing .... if you get to the unlock code bin part and apply and it says sucess but nothing happens.... Then you will have to snag the 2.17 RUU exe and run it then after that reapply the unlock code bin...
noob ? then. that is sytem update right?
Figured that out lol
Which root method should I use then
mecksg1 said:
Which root method should I use then
Click to expand...
Click to collapse
Ya update software you found it then do the HTC dev method since you are hboot 1.5
If i do the HTC dev unlock, will I still be able to fully unlock someday?
detroit2hi said:
If i do the HTC dev unlock, will I still be able to fully unlock someday?
Click to expand...
Click to collapse
I guess you can. You still can relock your phone I don't see why not
I have no problem using hboot 1.5 You can get a app on here or on the market called flash gui works like a champ when it comes to flashin roms and kernels without having to use a computer...
I just couldn't stand the bloatware on the stock phone now it's all gone
So after unlocking and putting Su and can on I can flash roms
Flash gui image is a must have if you are stuck with hboot 1.5
Sent from my PG86100 using Tapatalk
can u put pur recovery on it. trying now but its not allowing me to. i am unslocked thou
ok so i'm unlocked but not rooted. cant flash cwm, what the hell am i not doing?
mecksg1 said:
ok so i'm unlocked but not rooted. cant flash cwm, what the hell am i not doing?
Click to expand...
Click to collapse
Are you opening your cmd prompt to the appropriate folder and is your recovery image there?
At the command prompt, type: fastboot flash recovery recovery.img[2nd recovery = your recovery's name, you could also rename to "recovery"]. Good luck.
Sent from my PG86100 using xda premium
This might help clear some of it up for you;
http://forum.xda-developers.com/showthread.php?p=22054499
(Q) How To Flash A Recovery From Bootloader 1.5
Sent from my "Up all night, sleep all day" Evo3D via Tapatalk.
hi s-off my phone when the hboot was 1.49.0007
but after the ics update i re(s-on) my phone for the new ics update
but now the hboot is 1.53.0007 and can't make it s-off(Update sucks nothing special)
1_tried using unlimited.io but didn't work made an error my guess because it's ics
2_tried using GB ROM(Leedroid) didn't work
used fastboot flash boot boot.img still no luck (restarts every 5 seconds)
3_PG86IMG.zip fails (Main version is Older)
4_last shooter ruu error 140
Any advice? thank you
If you accepted an official OTA update, then you are likely now stuck in Hboot1.5-Hell. (I made this mistake many moons ago.)
You can try one of the many methods to downgrade your HBoot, but I don't know how that works with the official ICS update.
Sorry.
thanks for answering
hope there will be a solution soon
not much of a problem still can flash any ICS ROM Unless Sense 4.0
but if there are any other ideas please help
friend.evil said:
hi s-off my phone when the hboot was 1.49.0007
but after the ics update i re(s-on) my phone for the new ics update
but now the hboot is 1.53.0007 and can't make it s-off(Update sucks nothing special)
1_tried using unlimited.io but didn't work made an error my guess because it's ics
2_tried using GB ROM(Leedroid) didn't work
used fastboot flash boot boot.img still no luck (restarts every 5 seconds)
3_PG86IMG.zip fails (Main version is Older)
4_last shooter ruu error 140
Any advice? thank you
Click to expand...
Click to collapse
What error code did you get?
Sent from my PG86100 using xda premium
error 140 Bootloader version error
This may sound dumb like a dumb question but do you see super user in your apps?
Sent from my PG86100 using xda premium
That error could mean the update put your bootloader to stock I'm not certain of what your capable of doing at the moment but I do know to unlock the bootloader for hboot 1.5 you had to use the HTC unlock method and maybe you'll have to use it. I'm not an expert so this may not be the case but keep in mind you said your hboot is at a different value than previous to me it would only make sense to use the HTC method to unlock reestablish root the use the wire trick to get s-off. If you try this I wish you success. Sorry if this seems lacking but if I find something out I'll make sure you know
Sent from my PG86100 using xda premium
sorry non of that works
anyways
thanks for trying to help
friend.evil said:
sorry non of that works
anyways
thanks for trying to help
Click to expand...
Click to collapse
Did u tried the pg86img gingerbread with goldcard ?
Or the official pg86img with changed older hboot ?
Sent from my HTC EVO 3D X515m using xda premium
friend.evil said:
hi s-off my phone when the hboot was 1.49.0007
but after the ics update i re(s-on) my phone for the new ics update
but now the hboot is 1.53.0007 and can't make it s-off(Update sucks nothing special)
1_tried using unlimited.io but didn't work made an error my guess because it's ics
2_tried using GB ROM(Leedroid) didn't work
used fastboot flash boot boot.img still no luck (restarts every 5 seconds)
3_PG86IMG.zip fails (Main version is Older)
4_last shooter ruu error 140
Any advice? thank you
Click to expand...
Click to collapse
1_ you tried unlimited.io and it didn't work? Thats surprising to me.
2_ have you tried booting recovery from fastboot and flashing a gb rom? Fastboot boot recovery yourrecovery.img
3_ You can run an older ruu if you change your main version, but it still won't lower your hboot, your phone says its version "x.x.x.x" and the ruu is lower so it won't flash.
4_ you will never be able to lower your hboot unless you use a downgrade method like unknownforces brick/downgrade. If you put a lower hboot in the newest ruu, it won't run because you've broken the HTC signature. Id try the wire trick again if I were you.
Question, why did you s-on? I've taken ota's with s-off and as soon as I see the new hboot I just reflash the engineering hboot.
I have ~ the same problem as friend.evil, although he says he can run roms with Sense < 4, (if i understood correctly) while i can not.
I did try the lastest GB (provided by anryl) PG86IMG, with no luck (device always stuck in boot loop), but i do not have any goldcard (nor could i find one for evo 3d, but i did not google for it that much)
I am not sure about what you (anryl) mean by « official pg86img with changed older hboot ? » ?
Would an ICS RUU solve the problem ? I will probably also try to downgrade hboot if no other suggestions pops up =S
(More context: http://forum.xda-developers.com/showpost.php?p=28076870&postcount=231 )
espace.ariane said:
I have ~ the same problem as friend.evil, although he says he can run roms with Sense < 4, (if i understood correctly) while i can not.
I did try the lastest GB (provided by anryl) PG86IMG, with no luck (device always stuck in boot loop), but i do not have any goldcard (nor could i find one for evo 3d, but i did not google for it that much)
I am not sure about what you (anryl) mean by « official pg86img with changed older hboot ? » ?
Would an ICS RUU solve the problem ? I will probably also try to downgrade hboot if no other suggestions pops up =S
(More context: http://forum.xda-developers.com/showpost.php?p=28076870&postcount=231 )
Click to expand...
Click to collapse
I don't mean to be insensitive but if you s-on'd and then took a new ota then youve got a problem on your hands. An older ruu with an older hboot will do you no good as it won't flash unless you change your main version, and even if you do that it won't flash an older hboot, just an older system (gb). You should go ahead and check in to downgrading.
wikdNoob said:
I don't mean to be insensitive but if you s-on'd […].
Click to expand...
Click to collapse
(It has always been s-on)
espace.ariane said:
(It has always been s-on)
Click to expand...
Click to collapse
Gotcha, well you should consider downgrading to get s-off. It's much more trouble free than s-on. Are you gsm or cdma?
NVM, dumb question, lol, if you took an ics ota then you're gsm
Edit... After reading your post in the link provided, is say that an ics ruu would fix u up. I'm cdma so I wouldn't know where to find it at.
Thanks for you suggestions… But still, i don't understand why downgrading should be necessary : why would flashing a rom, stock or not be a problem for the bootloader ? Can we not write to system or flash the boot partition anymore (from fastboot, using fastboot flash boot boot.img ?) in 1.53.0007 ?
(And indeed, gsm forgot to mention, sry)
espace.ariane said:
Thanks for you suggestions… But still, i don't understand why downgrading should be necessary : why would flashing a rom, stock or not be a problem for the bootloader ? Can we not write to system or flash the boot partition anymore (from fastboot, using fastboot flash boot boot.img ?) in 1.53.0007 ?
Click to expand...
Click to collapse
You might be on to something there, some hboots don't accept commands that others do. I would think that if you changed your main version and then ran a gb pg86img, it would get you back to gb but it won't change your hboot.
Have you tried booting a recovery from fastboot with fastboot boot recovery.img?
You can't use radios, ruu's, or the juop s-off method with 1.53. It's like having a locked/unlocked boatloader.
Sent from my extremely under rated EVO 3d with a shiny aluminum bezel like the EVO 4g LTE on, you guessed it, Sprint!
kiewee3 said:
You can't use radios, ruu's, or the juop s-off method with 1.53. It's like having a locked/unlocked boatloader.
Sent from my extremely under rated EVO 3d with a shiny aluminum bezel like the EVO 4g LTE on, you guessed it, Sprint!
Click to expand...
Click to collapse
Sent from my HTC EVO 3D X515m using xda premium
the problem in JuopunutBear is that it keeps waiting for the device
tells me to check if adb and fast drivers are installed but i am positive they are
Is there a possibility for a GB ROM to work on hboot 1.53.0007?
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:
So I have the virgin mobile 3d and I am rooted with s-on. I've been trying to get it off tho. So I was following the quick and dirty thread. And so I relocked the boot loader and then I started up the RUU like the guide. And about halfway through the installation it gave me boot loader version error 140. So I looked it up and I think it means that I was trying to downgrade. And that's why it didn't work. I was supposedly going from 1.14 down to 1.13. These are the version The ruu gave. I'm not sure what the numbers were about but can someone help? That ruu was supposed to be the most updated one. And i have been searching like crazy. Any help would be appreciated. I understand these things, so don't be afraid to talk techy to me lmfao. Thanks
Sent from my SPH-L710 using xda app-developers app
monstaX said:
So I have the virgin mobile 3d and I am rooted with s-on. I've been trying to get it off tho. So I was following the quick and dirty thread. And so I relocked the boot loader and then I started up the RUU like the guide. And about halfway through the installation it gave me boot loader version error 140. So I looked it up and I think it means that I was trying to downgrade. And that's why it didn't work. I was supposedly going from 1.14 down to 1.13. These are the version The ruu gave. I'm not sure what the numbers were about but can someone help? That ruu was supposed to be the most updated one. And i have been searching like crazy. Any help would be appreciated. I understand these things, so don't be afraid to talk techy to me lmfao. Thanks
Click to expand...
Click to collapse
See the note for S-ON users in this post, which is also linked in the informational posts after Step3 of the guide. The reason you are having this problem is because you have already installed the OTA, which has a higher main version (mainver) than the VM RUU.
ramjet73
ramjet73 said:
See the note for S-ON users in this post, which is also linked in the informational posts after Step3 of the guide. The reason you are having this problem is because you have already installed the OTA, which has a higher main version (mainver) than the VM RUU.
ramjet73
Click to expand...
Click to collapse
ramjet youre the man. Im about to read it. I will try and then report back thanks
monstaX said:
ramjet youre the man. Im about to read it. I will try and then report back thanks
Click to expand...
Click to collapse
Good.
Don't forget to download and flash the OTA again after the RUU is flashed since it requires the stock recovery.
ramjet73
ramjet73 said:
Good.
Don't forget to download and flash the OTA again after the RUU is flashed since it requires the stock recovery.
ramjet73
Click to expand...
Click to collapse
So it worked!! I finally got s-off!!! Now one last thing, how do i go about downgrading the hboot. I plan on going SlimBean. I tried flashing the sprint 1.5 hboot but it failed. The error said that the custom ID failed. . Is there any way to downgrade?
monstaX said:
So it worked!! I finally got s-off!!! Now one last thing, how do i go about downgrading the hboot. I plan on going SlimBean. I tried flashing the sprint 1.5 hboot but it failed. The error said that the custom ID failed. . Is there any way to downgrade?
Click to expand...
Click to collapse
That's in this post, which is also linked after Step3 of the guide.
ramjet73
I have tried this. And a side note* when I boot into the boot loader it doesn't look for PG86IMG.zip it looks for PG86DIAG.zip. its really weird. Anyone know what this is? I tried renaming it to that but it doesn't do anything. It just reboots the boot loader. I have also tried flashing it through fastboot
Sent from my SPH-L710 using xda app-developers app
monstaX said:
I have tried this. And a side note* when I boot into the boot loader it doesn't look for PG86IMG.zip it looks for PG86DIAG.zip. its really weird. Anyone know what this is? I tried renaming it to that but it doesn't do anything. It just reboots the boot loader. I have also tried flashing it through fastboot
Click to expand...
Click to collapse
The PG86DIAG.zip file is an advanced diagnostic that is very tightly controlled by HTC, but the bootloader always looks for it anyway.
The filename for the zip doesn't matter when you use the fastboot flashing method. Can you paste the messages you are getting here starting with the "fastboot erase cache" command? Make sure you delete the PG86IMG.zip file from the root of the SD card before trying the fastboot method.
ramjet73
ramjet73 said:
The PG86DIAG.zip file is an advanced diagnostic that is very tightly controlled by HTC, but the bootloader always looks for it anyway.
The filename for the zip doesn't matter when you use the fastboot flashing method. Can you paste the messages you are getting here starting with the "fastboot erase cache" command? Make sure you delete the PG86IMG.zip file from the root of the SD card before trying the fastboot method.
ramjet73
Click to expand...
Click to collapse
OK sweet that it good to know. I tried both methods and it didn't work. But when I used the fast boot method I got a custom I'd check failed error. I'm not by the phone right now. But I remember the error. That's the only one I got. When I tried downgrading from 1.57jboot to 1.5
Sent from my SPH-L710 using xda app-developers app
monstaX said:
OK sweet that it good to know. I tried both methods and it didn't work. But when I used the fast boot method I got a custom I'd check failed error. I'm not by the phone right now. But I remember the error. That's the only one I got. When I tried downgrading from 1.57jboot to 1.5
Click to expand...
Click to collapse
If you are on hboot 1.57 then you probably have the Evo V 4G which means you need to use the Virgin Mobile version of the RUU.
ramjet73
ramjet73 said:
If you are on hboot 1.57 then you probably have the Evo V 4G which means you need to use the Virgin Mobile version of the RUU.
ramjet73
Click to expand...
Click to collapse
So you're saying I should extract the PG86IMG.zip from an older VM ruu? And then place in the root of my sdcard? That would give me the stock boot loader :-/. I already got s-off with jbear hboot 1.7
I'm trying to dual boot eventually so I want to be on hboot 1.5
Edit: one thing I haven't tried is leaving it named PG86IMG.zip and placing it on the SD card. But using 1.5 is that safe to try?. I'm thinking it will work because it is a sprint phone. It has sprint branding. It is just on VM. Let me know what you think
Sent from my SPH-L710 using xda app-developers app
monstaX said:
So you're saying I should extract the PG86IMG.zip from an older VM ruu? And then place in the root of my sdcard? That would give me the stock boot loader :-/. I already got s-off with jbear hboot 1.7
I'm trying to dual boot eventually so I want to be on hboot 1.5
Edit: one thing I haven't tried is leaving it named PG86IMG.zip and placing it on the SD card. But using 1.5 is that safe to try?. I'm thinking it will work because it is a sprint phone. It has sprint branding. It is just on VM. Let me know what you think
Click to expand...
Click to collapse
Follow the instructions in this post since you are S-OFF already. I recommend the JBear 1.50.5050 instead on the 1.50 hboot since that doesn't need to be unlocked to run extended fastboot commands.
ramjet73
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