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
Related
Hi guys,
I have rooted, S-OFF, 4EXT recovery, SuperCID, running Stock T-Mobile ICS HTC Amaze. My current configuration is
SHIP S-OFF
HBOOT 1.93.2222
Radio_1.14.550L.17DC_30.78.550L.15
I have searched "Amaze how to revert to stock" from within the forum and google as well but the answers came up so confuse and not very clear. So I dare to oen a new thread here asking for help. Somebody else might looking for the same thing.
Basically I want to go back to T-Mobile Stock Gingerbread. I have:
Hasson AllinOne V3.1,
PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_228638_signed
How would I safely going back to stock?
I know I have to flash the PH85IMG_Ruby_TMOUS_1.43.531.3 via fastboot as the last step but what step should I take first? Flash the stock bootloader first or flash the stock recovery first?
Any advice would be appriciated
Im S-on so idk if its different.
download this: http://www.filefactory.com/file/c0d...19DC_30.66.550L.08D_release_228638_signed.zip
idk if its the same one you have but just download it just in case, and RENAME IT to PH85IMG.
AFter that put it in your sd and boot into bootloader and then fastboot so it reads that file. then just click yes to the update and you are set.
^^ will that "update" revert EVERYthing back to s-on, shipped bootloader and recovery?
Will it revert the radio as well?
You might need to run the Mainver Error Fix in the all-in-one toolkit. It "spoofs your software version so you can downgrade your ROM."
Hasoon can correct me on this if I'm wrong.
kered424 said:
You might need to run the Mainver Error Fix in the all-in-one toolkit. It "spoofs your software version so you can downgrade your ROM."
Hasoon can correct me on this if I'm wrong.
Click to expand...
Click to collapse
Thanks. I tried this, running the mainver error fix, but it fails, saying device not found. I ran this with the phone connected to the computer via usb, and the phone in fastboot.
aiwapro said:
Thanks. I tried this, running the mainver error fix, but it fails, saying device not found. I ran this with the phone connected to the computer via usb, and the phone in fastboot.
Click to expand...
Click to collapse
Someone PLEASE reply to this gentlemen. This is the exact same problem I'm having at the moment, and have been for a week. I've looked high and low, and was on the verge of creating a new thread.
Just flash the stock file you have via hboot by renaming it to PH85IMG and placing it on your sdcard.
Dark Nightmare said:
Just flash the stock file you have via hboot by renaming it to PH85IMG and placing it on your sdcard.
Click to expand...
Click to collapse
This is the same process I've been following. When I flash the stock file, I get the Mainver Error. When I try using Hasoon's Mainver Error Fix, command prompt tells me the device isnt found. I get no further than this.
Sylvaeria said:
This is the same process I've been following. When I flash the stock file, I get the Mainver Error. When I try using Hasoon's Mainver Error Fix, command prompt tells me the device isnt found. I get no further than this.
Click to expand...
Click to collapse
Is the device in fastboot mode?
Are you s-on or s-off?
Also are you on GB or ICS?
Dark Nightmare said:
Is the device in fastboot mode?
Are you s-on or s-off?
Also are you on GB or ICS?
Click to expand...
Click to collapse
Fastboot.
This was my first root, and I've done nothing to mess around with anything related to security, so I'm gonna say S-On.
And I'm currently on ICS.
Sylvaeria said:
Fastboot.
This was my first root, and I've done nothing to mess around with anything related to security, so I'm gonna say S-On.
And I'm currently on ICS.
Click to expand...
Click to collapse
If you're on ICS, you cannot revert to GB, so your best option would be to flash a custom recovery, 4EXT recommended and look in the dev section for Hasoon2000's thread of stock zip files, download the carrier file that's for your device and flash that via a custom recovery, since T-Mobile is the only carrier we have bootloader flashable ruu files.
Dark Nightmare said:
If you're on ICS, you cannot revert to GB, so your best option would be to flash a custom recovery, 4EXT recommended and look in the dev section for Hasoon2000's thread of stock zip files, download the carrier file that's for your device and flash that via a custom recovery, since T-Mobile is the only carrier we have bootloader flashable ruu files.
Click to expand...
Click to collapse
I actually meant I was flashing to stock ICS. I just posted here for sake of simplicity. I have all of this ready to go already. Recovery and stock .zip. The only problem left is that the Mainver Fix in Hasoon's AIOT doesn't detect my device. I heard the fix for this is enabling USB Debugging, but I cannot do that since I get a permanent whitescreen after I boot up my device, and I've unlocked/relocked my bootloader and it reset the USB Debugging option. I feel like I'm pretty screwed at this point. Definitely not giving up, though.
Sylvaeria said:
I actually meant I was flashing to stock ICS. I just posted here for sake of simplicity. I have all of this ready to go already. Recovery and stock .zip. The only problem left is that the Mainver Fix in Hasoon's AIOT doesn't detect my device. I heard the fix for this is enabling USB Debugging, but I cannot do that since I get a permanent whitescreen after I boot up my device, and I've unlocked/relocked my bootloader and it reset the USB Debugging option. I feel like I'm pretty screwed at this point. Definitely not giving up, though.
Click to expand...
Click to collapse
What is your device's bootloader version and what carrier are you on?
You're going around in circles and that's not exactly gonna solve the problem atm.
Dark Nightmare said:
What is your device's bootloader version and what carrier are you on?
You're going around in circles and that's not exactly gonna solve the problem atm.
Click to expand...
Click to collapse
No kidding. T-Mobile. Not sure how to check version, so this is what I see:
RUBY PVT SHIP S-ON (Welp, I guess I got it right) RL
HBOOT-1 1.93.0002 (Assuming this is it?)
Open ADSP-v02.6.0.2226.00.0202
eMMC-boot
Mar 15 2012, 21:46:51
Sylvaeria said:
No kidding. T-Mobile. Not sure how to check version, so this is what I see:
RUBY PVT SHIP S-ON (Welp, I guess I got it right) RL
HBOOT-1 1.93.0002 (Assuming this is it?)
Open ADSP-v02.6.0.2226.00.0202
eMMC-boot
Mar 15 2012, 21:46:51
Click to expand...
Click to collapse
Download this file: http://d-h.st/3VD
Relock your devices bootloader, put the device into fastboot, get hasoon's tool ver 3.2, or whatever the latest atm is, relock/lock the bootloader command.
rename that file PH85IMG exactly like that, put it on your sdcard, not your phone memory, do not extract it or place it into any folders, reboot into bootloader, volume up to update.
Let it boot completely at least once before attempting to root/flashing a custom rom.
Going for it. Thanks for the help so far. I'll report back soon.
Okie dokie artichokie.
Dark Nightmare said:
Download this file: http://d-h.st/3VD
Relock your devices bootloader, put the device into fastboot, get hasoon's tool ver 3.2, or whatever the latest atm is, relock/lock the bootloader command.
rename that file PH85IMG exactly like that, put it on your sdcard, not your phone memory, do not extract it or place it into any folders, reboot into bootloader, volume up to update.
Let it boot completely at least once before attempting to root/flashing a custom rom.
Click to expand...
Click to collapse
You, sir, are a god among men. Thank you SO much. Is there any way I can thank you twice?
Sylvaeria said:
You, sir, are a god among men. Thank you SO much. Is there any way I can thank you twice?
Click to expand...
Click to collapse
Lol, you're welcome, happy you got it resolved, have fun.
Hi guys
Is there any chance that I can reinstall android OS from scratch? The reason why I need to do that, is because I removed the SD card from phone while firmware update was taking place and updating failed. Now my phone cannot boot up and factory reset cannot be done as well.
Thanks
run an RUU
you cant boot to Hboot?
sitlet said:
run an RUU
Click to expand...
Click to collapse
I have a post here with download links and information for flashing the RUU.exe from Windows. Note that the procedure is slightly different depending if you are S-On or S-OFF, since you didn't say which you are.
I usually recommend putting the phone into fastboot USB mode in the bootloader before running the RUU, but if you can't do that just connect it via USB and try running the RUU.exe. It can usually find the phone.
ramjet73
ronilzizou said:
you cant boot to Hboot?
Click to expand...
Click to collapse
Yes I can
ramjet73 said:
I have a post here with download links and information for flashing the RUU.exe from Windows. Note that the procedure is slightly different depending if you are S-On or S-OFF, since you didn't say which you are.
I usually recommend putting the phone into fastboot USB mode in the bootloader before running the RUU, but if you can't do that just connect it via USB and try running the RUU.exe. It can usually find the phone.
ramjet73
Click to expand...
Click to collapse
Can you please explain a bit clearer what do you mean? ;/ I am a noob on these staff... I need thorough explanation on how to do the steps.. Also my mobile is not a Sprint one. Will the ruu.exe work?
Varnis9 said:
Can you please explain a bit clearer what do you mean? ;/ I am a noob on these staff... I need thorough explanation on how to do the steps.. Also my mobile is not a Sprint one. Will the ruu.exe work?
Click to expand...
Click to collapse
I wouldn't recommend running the 2.89 RUU if you are not a Sprint user. I guess you need to tell us a little more about your configuration and how you got to where you are now.
ramjet73
ramjet73 said:
I wouldn't recommend running the 2.89 RUU if you are not a Sprint user. I guess you need to tell us a little more about your configuration and how you got to where you are now.
ramjet73
Click to expand...
Click to collapse
Well my phone has an Asian software installed. I bought my phone from amazon uk. All the rest are described in the thread.
P.S. When I go into the Fastboot screen the following appear in green colour.
****LOCKED****
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0012
eMMC-boot
Aug 4 2011, 14:10:29
Try this:
http://forum.xda-developers.com/showthread.php?t=1563342
or this:
http://forum.xda-developers.com/showthread.php?t=1627917
Both provide ways to "unbrick" your phone
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
silenthatred said:
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
Click to expand...
Click to collapse
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
silenthatred said:
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
Click to expand...
Click to collapse
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
silenthatred said:
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
Click to expand...
Click to collapse
This happens sometimes if you have a custom bootloader installed when you flash the RUU. Just cancel the Windows task and restart it and you should be fine.
ramjet73
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
silenthatred said:
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
Click to expand...
Click to collapse
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
Click to expand...
Click to collapse
Why is this? Is there not a full RUU for the latest version?
ramjet73 said:
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
silenthatred said:
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
Click to expand...
Click to collapse
Does it still say ** LOCKED ** Or does it say ** UNLOCKED ** now?
Unknownforce said:
Why is this? Is there not a full RUU for the latest version?
Click to expand...
Click to collapse
No. Virgin Mobile released an OTA update in November but there's no RUU that corresponds to it available yet. Fortunately, the bootloader version didn't change so the original RUU can be flashed with S-ON if the mainver is set low, but you need to be unlocked and rooted already to flash the zip file that does that.
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
Click to expand...
Click to collapse
That would be a problem for him then. I don't know of anyway to flash the RUU with S-ON after the OTA has been installed if the bootloader is actually locked and he can't unlock it.
ramjet73
Yeah, not looking good. Thanks for the help though!
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
I recently bought a replacement Rezound, which has Hboot 2.25/Radios 1.22.10 0421r &0424r. I have unlocked the bootloader and installed TWERP 2.6.3.0 and Infection 2.9.1. I am sure I should have thought of this before installing Infection, but my battery life is worse than my original phone and it runs hot. No reboots or other problems.
I have searched for instructions and recommendations for upgrading Hboot, but haven't found anything clear enough to overcome my nervousness about this process. I have one bricked phone on the desk in front of me and I don't want another. I will be grateful to anyone who can recommend what Hboot to flash (I'm thinking 2.27 or 2.28?) and guide me through the process.
Thanks,
geronimo48 said:
I recently bought a replacement Rezound, which has Hboot 2.25/Radios 1.22.10 0421r &0424r. I have unlocked the bootloader and installed TWERP 2.6.3.0 and Infection 2.9.1. I am sure I should have thought of this before installing Infection, but my battery life is worse than my original phone and it runs hot. No reboots or other problems.
I have searched for instructions and recommendations for upgrading Hboot, but haven't found anything clear enough to overcome my nervousness about this process. I have one bricked phone on the desk in front of me and I don't want another. I will be grateful to anyone who can recommend what Hboot to flash (I'm thinking 2.27 or 2.28?) and guide me through the process.
Thanks,
Click to expand...
Click to collapse
look at my downgrade/upgrade guide here in the rezound q&a.....the 3 ph98img ota files are the updates you want
REV3NT3CH said:
look at my downgrade/upgrade guide here in the rezound q&a.....the 3 ph98img ota files are the updates you want
Click to expand...
Click to collapse
Your initial comment, "For this you MUST BE S-OFF FOR DOWNGRADING with a relocked bootloader and make sure you are not on a custom or hex edited hboot or you can brick your device." stopped me. My phone is S-on and Hboot is unlocked. Do I have to be S-off and unlocked to flash the three OTAs?
geronimo48 said:
Your initial comment, "For this you MUST BE S-OFF FOR DOWNGRADING with a relocked bootloader and make sure you are not on a custom or hex edited hboot or you can brick your device." stopped me. My phone is S-on and Hboot is unlocked. Do I have to be S-off and unlocked to flash the three OTAs?
Click to expand...
Click to collapse
yes thats for downgrading with the ruu.exe's not for updating...to update just follow the OTA part with the ph98img.zips
REV3NT3CH said:
yes thats for downgrading with the ruu.exe's not for updating...to update just follow the OTA part with the ph98img.zips
Click to expand...
Click to collapse
I downloaded all three files and checked md5 - all checked out. I then put the 1st file on the root directory of my ex sd card, renamed it PH98IMG.zip and rebooted into the unlocked bootloader. Bootloader recognized the zip, the progress bar appeared and the file transferred. Then the progress bar disappeared and nothing else happened. There was no instruction to press Volume up. I repeated everything and got the same result. I can still boot into TWERP and my phone still starts up with Infection 2.9.1.
Let me say at this point, THANK GOD NOTHING BAD HAPPENED!
Any suggestions?
geronimo48 said:
I downloaded all three files and checked md5 - all checked out. I then put the 1st file on the root directory of my ex sd card, renamed it PH98IMG.zip and rebooted into the unlocked bootloader. Bootloader recognized the zip, the progress bar appeared and the file transferred. Then the progress bar disappeared and nothing else happened. There was no instruction to press Volume up. I repeated everything and got the same result. I can still boot into TWERP and my phone still starts up with Infection 2.9.1.
Let me say at this point, THANK GOD NOTHING BAD HAPPENED!
Any suggestions?
Click to expand...
Click to collapse
hmmm for s and g's relock the bootloader....are you absolutely sure you are on 2.25...the first ph98img is hboot 2.27 with the firmware....also just rename it to just PH98IMG if you type the zip with it the phone will read it as PH98IMG.zip.zip and wont work
REV3NT3CH said:
hmmm for s and g's relock the bootloader....are you absolutely sure you are on 2.25...the first ph98img is hboot 2.27 with the firmware....also just rename it to just PH98IMG if you type the zip with it the phone will read it as PH98IMG.zip.zip and wont work
Click to expand...
Click to collapse
I am looking at my Hboot screen. It says:
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
I transferred the 1st file to my SD card and deleted "this 1st " from the name. I watched it reading in Hboot and saw "PH98IMG.ZIP".
I'll try relocking the bootloader.
Thanks.
EDIT - Looks like the bootloader needs to be locked. The first file is finished, starting on the second.
EDIT 2 - OK. I can't get the 2nd file to flash with the bootloader locked or unlocked.
BUT, I now have:
HBOOT-2.27.000
RADIO-2.22.20.0801r/2.22.10.0803r
geronimo48 said:
I am looking at my Hboot screen. It says:
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
I transferred the 1st file to my SD card and deleted "this 1st " from the name. I watched it reading in Hboot and saw "PH98IMG.ZIP".
I'll try relocking the bootloader.
Thanks.
EDIT - Looks like the bootloader needs to be locked. The first file is finished, starting on the second.
Click to expand...
Click to collapse
ah thanks for the info bud much appreciated....glad relocking it worked for you
REV3NT3CH said:
ah thanks for the info bud much appreciated....glad relocking it worked for you
Click to expand...
Click to collapse
Please see EDIT 2. I can't flash the 2nd file with the bootloader locked or unlocked.
I can boot into Hboot, but when I try to open Recovery I first get the green arrows (circle and down), then I get the red triangle with exclamation mark. When I booted the phone I got the setup wizard and a notice that my phone was just activated. Of course it was already activated. I suppose this just means everything has been wiped and I'm starting fresh with the firmware from the 1st downloaded zip. I didn't go through setup.
Any ideas?
geronimo48 said:
Please see EDIT 2. I can't flash the 2nd file with the bootloader locked or unlocked.
I can boot into Hboot, but when I try to open Recovery I first get the green arrows (circle and down), then I get the red triangle with exclamation mark. When I booted the phone I got the setup wizard and a notice that my phone was just activated. Of course it was already activated. I suppose this just means everything has been wiped and I'm starting fresh with the firmware from the 1st downloaded zip. I didn't go through setup.
Any ideas?
Click to expand...
Click to collapse
yes....after 1st ota phone is suppose to activate through verizon
REV3NT3CH said:
yes....after 1st ota phone is suppose to activate through verizon
Click to expand...
Click to collapse
Any ideas on how to install the other two OTAs?
geronimo48 said:
Any ideas on how to install the other two OTAs?
Click to expand...
Click to collapse
all 3 install through bootloader....must have a relocked bootloader...the other 2 ph98img.zip's are not firmware or rom....just radios, hboot, and required system files for them
REV3NT3CH said:
all 3 install through bootloader....must have a relocked bootloader...the other 2 ph98img.zip's are not firmware or rom....just radios, hboot, and required system files for them
Click to expand...
Click to collapse
I noticed they were smaller. I installed the 1st OTA with the bootloader relocked. The 2nd OTA wouldn't complete installation locked or unlocked. I reflashed the first OTA just to make sure and the process worked flawlessly. The 2nd OTA acts like it is loading, but I don't get the notice to press Vol Up.
If you think of a way that might work to get the other OTAs installed, let me know.
Thanks again for all your help.
geronimo48 said:
I noticed they were smaller. I installed the 1st OTA with the bootloader relocked. The 2nd OTA wouldn't complete installation locked or unlocked. I reflashed the first OTA just to make sure and the process worked flawlessly. The 2nd OTA acts like it is loading, but I don't get the notice to press Vol Up.
If you think of a way that might work to get the other OTAs installed, let me know.
Thanks again for all your help.
Click to expand...
Click to collapse
Same issue here thanks for addressing it.
drhile said:
Same issue here thanks for addressing it.
Click to expand...
Click to collapse
hmm strange....works for some doesnt for others...i know flyhalf posted a method of this somewhere for s-on users...required extra step i think
geronimo48 said:
Any ideas on how to install the other two OTAs?
Click to expand...
Click to collapse
I guess you haven't thought of anything.
I am thinking of having another go at installing all three OTAs. I have installed CWM and TACHYON. I don't have FCs or bootloops, but my battery life is poor, the camera doesn't work and the phone runs hot (>110). I have tried SetCPU with limited success.
You and others have stated that outdated HBOOT/radios can cause overheating, so I want to try.
Question: Do I need to do a factory reset and start over with the 1st OTA?
Thanks again for all of your help.
geronimo48 said:
I guess you haven't thought of anything.
I am thinking of having another go at installing all three OTAs. I have installed CWM and TACHYON. I don't have FCs or bootloops, but my battery life is poor, the camera doesn't work and the phone runs hot (>110). I have tried SetCPU with limited success.
You and others have stated that outdated HBOOT/radios can cause overheating, so I want to try.
Question: Do I need to do a factory reset and start over with the 1st OTA?
Thanks again for all of your help.
Click to expand...
Click to collapse
If you're at hboot 2.27, that's not your problem, you have other issues, being you're s-on, how did you flash the kernel for Tachyon?
geronimo48 said:
I guess you haven't thought of anything.
I am thinking of having another go at installing all three OTAs. I have installed CWM and TACHYON. I don't have FCs or bootloops, but my battery life is poor, the camera doesn't work and the phone runs hot (>110). I have tried SetCPU with limited success.
You and others have stated that outdated HBOOT/radios can cause overheating, so I want to try.
Question: Do I need to do a factory reset and start over with the 1st OTA?
Thanks again for all of your help.
Click to expand...
Click to collapse
as stated there is a method with the last two foe s-on users...having to use fastboot i believe
REV3NT3CH said:
as stated there is a method with the last two foe s-on users...having to use fastboot i believe
Click to expand...
Click to collapse
Thanks. I'll post if I figure it out.
geronimo48 said:
Thanks. I'll post if I figure it out.
Click to expand...
Click to collapse
according to flyhalf as the this 3rd was uploaded by him you just need a relocked bootloader for s-on....im s-off though but can guarantee links work as i just used them...but in all seriouness if your not really using stock i highly suggest gaining s-off as it will make life easier....plus it has less of a chance on fully and permanently bricking your rez...with s-on there isnt really much you can do in a brick