Related
I have been trying for months to try and get back to stock in order to get S-OFF and rooted. I have tried many tut's and when I get to the RUU part, it stops me and prompts the error 140. Then I have gone to other websites and threads to find a solution to the problem but I haven't found a successful one.
As of right now this is what I have when I go into bootloader:
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1. 58.0000
eMMC-boot
May 17 2012,15:06:44
lxbeale said:
I have been trying for months to try and get back to stock in order to get S-OFF and rooted. I have tried many tut's and when I get to the RUU part, it stops me and prompts the error 140. Then I have gone to other websites and threads to find a solution to the problem but I haven't found a successful one.
As of right now this is what I have when I go into bootloader:
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1. 58.0000
eMMC-boot
May 17 2012,15:06:44
Click to expand...
Click to collapse
What RUU are you trying to run? Since you are S-ON with hboot 1.58 the only version that should work is the Sprint ICS (2.89.651.2) version.
If you issue the following commands from fastboot you can verify that you have correct CID and man version (mainver) to flash that RUU:
fastboot getvar cid
fastboot getvar mainver
Click to expand...
Click to collapse
ramjet73
ramjet73 said:
What RUU are you trying to run? Since you are S-ON with hboot 1.58 the only version that should work is the Sprint ICS (2.89.651.2) version.
If you issue the following commands from fastboot you can verify that you have correct CID and man version (mainver) to flash that RUU:
ramjet73
Click to expand...
Click to collapse
Do you have a link to a RUU that would work? And I was trying RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
lxbeale said:
Do you have a link to a RUU that would work? And I was trying RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Click to expand...
Click to collapse
Yea, that's the latest GB version but won't flash over the Sprint ICS build.
Here's the one you want.
ramjet73
ramjet73 said:
Yea, that's the latest GB version but won't flash over the Sprint ICS build.
Here's the one you want.
ramjet73
Click to expand...
Click to collapse
I downloaded it and ran it, It got about 3 minutes into it and then gave me ERROR[132]: Signature error
lxbeale said:
I downloaded it and ran it, It got about 3 minutes into it and then gave me ERROR[132]: Signature error
Click to expand...
Click to collapse
Did you ever run the fastboot commands posted above to display your CID and mainver? If so, what were the values they returned?
Also, did you check the MD5 for the RUU.exe file after you downloaded it? I know that RUU.exe is good because there have been almost 1400 downloads without any problems reported.
Is the phone in "fastboot USB" mode when you start the RUU.exe? Here's a post with some more RUU.exe troubleshooting tips that might help.
ramjet73
ramjet73 said:
Did you ever run the fastboot commands posted above to display your CID and mainver? If so, what were the values they returned?
Also, did you check the MD5 for the RUU.exe file after you downloaded it? I know that RUU.exe is good because there have been almost 1400 downloads without any problems reported.
Is the phone in "fastboot USB" mode when you start the RUU.exe? with some more RUU.exe troubleshooting tips that might help.
ramjet73
Click to expand...
Click to collapse
I Got SPCS_001 and 2.89.651.2,
I did not check the MD5 because I have no clue what that is,
It was in fastboot usb mode when I started it.
lxbeale said:
I Got SPCS_001 and 2.89.651.2,
I did not check the MD5 because I have no clue what that is,
It was in fastboot usb mode when I started it.
Click to expand...
Click to collapse
You have the correct CID and mainver for the Sprint ICS build, so that looks good.
Have you tried a different USB cable and/or another PC? Based on everything I've seen in this thread so far you are doing things right, but something may be corrupting the RUU as it's being flashed.
ramjet73
I have tried different cables but not different PC's, I will give it another go with my laptop
ramjet73 said:
You have the correct CID and mainver for the Sprint ICS build, so that looks good.
Have you tried a different USB cable and/or another PC? Based on everything I've seen in this thread so far you are doing things right, but something may be corrupting the RUU as it's being flashed.
ramjet73
Click to expand...
Click to collapse
I have tried a different cable but not a different PC, I will have another go with my laptop
lxbeale said:
I have tried a different cable but not a different PC, I will have another go with my laptop
Click to expand...
Click to collapse
I just tried using my laptop and got Error 170, so I tried a different cord and that didn't work, I then thought that the file may have been corrupted and re downloaded it and still got the same problems. I then went to go and see if the other RUU (2.17) would connect to the phone and it did but still got me the error 140. Would I need to use another PC or what, cause I don't know where to go from here
lxbeale said:
I just tried using my laptop and got Error 170, so I tried a different cord and that didn't work, I then thought that the file may have been corrupted and re downloaded it and still got the same problems. I then went to go and see if the other RUU (2.17) would connect to the phone and it did but still got me the error 140. Would I need to use another PC or what, cause I don't know where to go from here
Click to expand...
Click to collapse
Let's take a different approach.
Try downloading the 2.89.651.2 RUU (the first one) from this post, place it in the root of your SD card and rename it to PG86IMG.zip, then start your bootloader and press the power button once. That should give you a prompt to authorize the installation so go ahead and do that.
This approach will eliminate both the cable and the PC as possible causes of the problem.
ramjet73
ramjet73 said:
Let's take a different approach.
Try downloading the 2.89.651.2 RUU (the first one) from , place it in the root of your SD card and rename it to PG86IMG.zip, then start your bootloader and press the power button once. That should give you a prompt to authorize the installation so go ahead and do that.
This approach will eliminate both the cable and the PC as possible causes of the problem.
ramjet73
Click to expand...
Click to collapse
I performed this twice on two different computers using different cords each time and when I went into the bootloader, on the top right it went through a blue and then a brown loading bar and then went back to bootloader doing nothing
lxbeale said:
I performed this twice on two different computers using different cords each time and when I went into the bootloader, on the top right it went through a blue and then a brown loading bar and then went back to bootloader doing nothing
Click to expand...
Click to collapse
Did you try flashing the zip version that I linked in my last post from the bootloader?
ramjet73
ramjet73 said:
Did you try flashing the zip version that I linked in my last post from the bootloader?
ramjet73
Click to expand...
Click to collapse
Yes I did, do you think if I would root my phone again and then relock it, this could be fixed?
lxbeale said:
Yes I did, do you think if I would root my phone again and then relock it, this could be fixed?
Click to expand...
Click to collapse
I really don't know what the problem is but you would definitely have a better chance of fixing it if you are S-OFF. You could unlock the bootloader, flash a custom recovery and then a stock rooted ROM and try the wire trick. If you can get that to work you should definitely be able to flash the RUU.
There is a stock rooted version of the Sprint ICS ROM in this post.
ramjet73
ramjet73 said:
I really don't know what the problem is but you would definitely have a better chance of fixing it if you are S-OFF. You could unlock the bootloader, flash a custom recovery and then a stock rooted ROM and try the wire trick. If you can get that to work you should definitely be able to flash the RUU.
There is a stock rooted version of the Sprint ICS ROM in this post.
ramjet73
Click to expand...
Click to collapse
Okay so I unlocked my bootloader and put 4ext recovery on, but I am still having problems flashing firmware, it goes to a loading bar then it says it is parsing then returns back to the bootloader
lxbeale said:
Okay so I unlocked my bootloader and put 4ext recovery on, but I am still having problems flashing firmware, it goes to a loading bar then it says it is parsing then returns back to the bootloader
Click to expand...
Click to collapse
Unlocking your bootloader and installing a custom recovery is considered "rooting" and not the same as being S-OFF. If you want to flash PG86IMG.zip files from your bootloader you will have to perform the wire trick procedure to get radio S-OFF.
ramjet73
ramjet73 said:
Unlocking your bootloader and installing a custom recovery is considered "rooting" and not the same as being S-OFF. If you want to flash PG86IMG.zip files from your bootloader you will have to perform the wire trick procedure to get radio S-OFF.
ramjet73
Click to expand...
Click to collapse
But in order to do the wire trick, you have to be on a stock RUU and at the moment I am not. I tried installing the stock rom but all its getting me is to the sprint loading screen when trying to boot. Will the wire trick still work?
lxbeale said:
But in order to do the wire trick, you have to be on a stock RUU and at the moment I am not. I tried installing the stock rom but all its getting me is to the sprint loading screen when trying to boot. Will the wire trick still work?
Click to expand...
Click to collapse
According to the OP of this thread you have hboot 1.58 and should be able to boot a rooted stock Sprint ICS ROM. Did you do a wipe before you flashed it?
If you can't get the rooted stock ROM working you can try doing the wire trick with a "stockish" ROM like MeanROM 2.6. That's not supported by the JBear team but it's worked for some users.
You can't use a GB stock ROM because it won't boot with 1.58, so that's not an option.
ramjet73
so i recently tried rooting and putting a rom on my brothers phone. i have already done mine so i thought it would be easy. i didnt not know of the s-on/s-off concept. so i put on a rom that required s-off on the s-on htc evo 3d. i put a rom on that is compatible with s-on for the mean time. what i want to know is there a way to return to the stock rom, or fix it from here and go to s-off.
HTC EVO 3D from sprint CDMA
hboot 1.58
s-on
to add, i am still a newb at this whole thing. if anyone can help please do. if anyone needs more info please ask.
Follow the guide here: http://forum.xda-developers.com/showthread.php?t=1889438
You'll relock and run the ruu.exe. This will put everything back to stock. You can then follow the guide to get s-off.
thanks!
coal686 said:
Follow the guide here: http://forum.xda-developers.com/showthread.php?t=1889438
You'll relock and run the ruu.exe. This will put everything back to stock. You can then follow the guide to get s-off.
Click to expand...
Click to collapse
thanks, i will have to try this later my brother is currently at work. thanks for the guide. il let you know how it turns out
usb
coal686 said:
Follow the guide here: http://forum.xda-developers.com/showthread.php?t=1889438
You'll relock and run the ruu.exe. This will put everything back to stock. You can then follow the guide to get s-off.
Click to expand...
Click to collapse
In the guide it says connect phone, does it have to be in recovery, or in fastboot usb. also i tried this and it says i have the wrong ruu
error code
alexp07 said:
In the guide it says connect phone, does it have to be in recovery, or in fastboot usb. also i tried this and it says i have the wrong ruu
Click to expand...
Click to collapse
says i got error code 155
alexp07 said:
In the guide it says connect phone, does it have to be in recovery, or in fastboot usb. also i tried this and it says i have the wrong ruu
Click to expand...
Click to collapse
alexp07 said:
says i got error code 155
Click to expand...
Click to collapse
Fastboot USB is what you need to be in. That error code typically means that you forgot to relock the bootloader before running the ruu. It could also mean that you have the wrong ruu.exe. Did you get yours from the zip in ramjet's thread?
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
So I've searched for ways to get S-Off on this thing (HTC EVO 3D hboot 1.58 software 2.89) and I can't seem to find anything. Juponutbear doesn't support windows anymore so I can't do the wire trick. Anything will help, I just want to get this thing S-OFF! :fingers-crossed:
SemaFlo said:
So I've searched for ways to get S-Off on this thing (HTC EVO 3D hboot 1.58 software 2.89) and I can't seem to find anything. Juponutbear doesn't support windows anymore so I can't do the wire trick. Anything will help, I just want to get this thing S-OFF! :fingers-crossed:
Click to expand...
Click to collapse
Have you already installed a custom recovery?
If so, flash the rooted stock ROM from this post then go directly to Step3 of my root/S-OFF guide. You will need to download and unzip the Sprint version of the all-in-one file, but don't even try to flash the RUU that's included.
Once you are S-OFF you can flash the Virgin Mobile RUU then update to current firmware by installing the OTA's or flashing the firmware only zip files.
ramjet73
ramjet73 said:
Have you already installed a custom recovery?
If so, flash the rooted stock ROM from this post then go directly to Step3 of my root/S-OFF guide. You will need to download and unzip the Sprint version of the all-in-one file, but don't even try to flash the RUU that's included.
Once you are S-OFF you can flash the Virgin Mobile RUU then update to current firmware by installing the OTA's or flashing the firmware only zip files.
ramjet73
Click to expand...
Click to collapse
Does it matter if I'm Sprint CDMA though? Or is this only for VM?
I also don't have Ubuntu or Linux. I have Windows. Am I helpless now..?
SemaFlo said:
Does it matter if I'm Sprint CDMA though? Or is this only for VM?
Click to expand...
Click to collapse
SemaFlo said:
I also don't have Ubuntu or Linux. I have Windows. Am I helpless now..?
Click to expand...
Click to collapse
OK, somehow I missed that you are Sprint not VM.
That makes it easier actually. Just follow the guide from the beginning and post in that thread if you have any problems. That procedure should work for you regardless or whether or not unlimited.io supports it and the worst case is that you might have to flash the RUU again and download their Linux version and LiveCD but that's not likely to happen.
Good luck!
ramjet73
ramjet73 said:
OK, somehow I missed that you are Sprint not VM.
That makes it easier actually. Just follow the guide from the beginning and post in that thread if you have any problems. That procedure should work for you regardless or whether or not unlimited.io supports it and the worst case is that you might have to flash the RUU again and download their Linux version and LiveCD but that's not likely to happen.
Good luck!
ramjet73
Click to expand...
Click to collapse
Wait, so I do need Linux or Ubuntu to do the trick? Cause I don't have either? Is there any way to get S-OFF with windows? That's what my whole problem is, getting S-OFF on Windows..
ramjet73 said:
OK, somehow I missed that you are Sprint not VM.
That makes it easier actually. Just follow the guide from the beginning and post in that thread if you have any problems. That procedure should work for you regardless or whether or not unlimited.io supports it and the worst case is that you might have to flash the RUU again and download their Linux version and LiveCD but that's not likely to happen.
Good luck!
ramjet73
Click to expand...
Click to collapse
Oh yeah and by the way, I can't even flash the ROM. I have TWRP 2.4.4.0 and when I try, it says failed. I'm starting to really hate this phone now.
SemaFlo said:
Wait, so I do need Linux or Ubuntu to do the trick? Cause I don't have either? Is there any way to get S-OFF with windows? That's what my whole problem is, getting S-OFF on Windows..
Click to expand...
Click to collapse
Did you read through the guide that I linked? There's no Linux mentioned there except a link for Linux users that can't use that guide.
ramjet73
ramjet73 said:
Did you read through the guide that I linked? There's no Linux mentioned there except a link for Linux users that can't use that guide.
ramjet73[
Well, I think im cool now, but, I get this message nonstop:
Let's take one more......
S-OFF Failed
Errorcode: 66732337
ErrorMsg: Still sober
Quit....
Press ENTER to exit.....
I've tried different timings and I've been doing it for like the past half hour now, what's wrong??????
Click to expand...
Click to collapse
SemaFlo said:
ramjet73 said:
Did you read through the guide that I linked? There's no Linux mentioned there except a link for Linux users that can't use that guide.
Click to expand...
Click to collapse
Well, I think im cool now, but, I get this message nonstop:
Let's take one more......
S-OFF Failed
Errorcode: 66732337
ErrorMsg: Still sober
Quit....
Press ENTER to exit.....
I've tried different timings and I've been doing it for like the past half hour now, what's wrong??????
Click to expand...
Click to collapse
You're doing fine if you got to the wire trick.
That error just means the timing is not right or the wire isn't making proper contact. Try watching the videos in #1 of the tips and references section for Step3 if you haven't already, and sometimes it helps to use a lower capacity SD card if you have one.
ramjet73
i had to do this probably 5 times before I got it right. and i thought i bricked in the middle. but it all worked out in the end