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
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!
hello friends...
i try this all method http://forum.xda-developers.com/showthread.php?t=1743466
and als try http://unlimited.io/ wire trick
not work ... for me
i want to s-off . bcz i am going bore with official ics ..
plz help me
Are you on the stock rom, or did you flash a modified one? If you are still on the stock rom, unlock your bootloader via www.htcdev.com and then try the wire trick again. I had to do it a lot of times, but it eventually worked. Just keep trying and eventually you will succeed
thanks
posedatull said:
Are you on the stock rom, or did you flash a modified one? If you are still on the stock rom, unlock your bootloader via www.htcdev.com and then try the wire trick again. I had to do it a lot of times, but it eventually worked. Just keep trying and eventually you will succeed
Click to expand...
Click to collapse
thanks bro from last 3 days i try more then 20 time but not work ...
i always stuck on juopuntbear screen after that adb not work ...\i don't know what should i do
i try restart my pc and mobile both so many time but not work for me
it sucks .....
thsnks for reply
faizan950 said:
thanks bro from last 3 days i try more then 20 time but not work ...
i always stuck on juopuntbear screen after that adb not work ...\i don't know what should i do
i try restart my pc and mobile both so many time but not work for me
it sucks .....
thsnks for reply
Click to expand...
Click to collapse
Did you get s off or not? Tell me exactly what you have done so far. I can give you step by step instructions and guide you through the process.
MrJyrks said:
Did you get s off or not? Tell me exactly what you have done so far. I can give you step by step instructions and guide you through the process.
Click to expand...
Click to collapse
thanks bro ....
i try with control bear box
my mobile going junpuntbear after that my pc not dedect my htc .... adb fail always
my phone is unlocked recovery installed
i want s-off
i also attached one picture ... stuck there every time....
wait for you tips
thanks
First of all, you must be on stock rom. Every sense 3.6 based rom should work. Did you run ControlBear as administrator?
If you did, run murder.bat from the attached .rar as administrator, wait till it's done. Try again. Still not working? Extract all the files from the rar to a folder. Run controlbear from there (run as admin). Give me feedback if it worked!
Edit: I have to upload the file somewhere else, it's over 8 mb so cant upload here.
Here's the link: https://docs.google.com/file/d/0B-fWg2dqIcnRT0xSZUdnVFRHeVk/edit?usp=sharing
Also It's a good idea to disable antivirus. I always do it as a precaution so I don't screw up anything.
If you need to know, the bat file searces for processes that may be interfering with controlbear and kills them.
Also none of this is my work, so all the thanks go to unlimited team.
MrJyrks said:
First of all, you must be on stock rom. Every sense 3.6 based rom should work. Did you run ControlBear as administrator?
If you did, run murder.bat from the attached .rar as administrator, wait till it's done. Try again. Still not working? Extract all the files from the rar to a folder. Run controlbear from there (run as admin). Give me feedback if it worked!
Edit: I have to upload the file somewhere else, it's over 8 mb so cant upload here.
Here's the link: https://docs.google.com/file/d/0B-fWg2dqIcnRT0xSZUdnVFRHeVk/edit?usp=sharing
Also It's a good idea to disable antivirus. I always do it as a precaution so I don't screw up anything.
If you need to know, the bat file searces for processes that may be interfering with controlbear and kills them.
Also none of this is my work, so all the thanks go to unlimited team.
Click to expand...
Click to collapse
thank you very much ....
i just use samsumg galaxy s3 data cable and every think work fine and finlly i did s-off thanks for you reply ...
Hello, I tried this junpuntbear s-off tutorial, but I'm stuck on junpuntbear boot. My pc can't find my phone from adb and it just stays there.
I unlocked with htcdev my bootloader, 4ext recovery installed, rooted. "Still not found device" etc... Any suggestion? I installed all drivers, fastboot/adb works fine. I installed mwakious3Drom 16.0.150_BASE_FINAL_RELEASE rom on my phone, is this the problem?
mhnx said:
Hello, I tried this junpuntbear s-off tutorial, but I'm stuck on junpuntbear boot. My pc can't find my phone from adb and it just stays there.
I unlocked with htcdev my bootloader, 4ext recovery installed, rooted. "Still not found device" etc... Any suggestion? I installed all drivers, fastboot/adb works fine. I installed mwakious3Drom 16.0.150_BASE_FINAL_RELEASE rom on my phone, is this the problem?
Click to expand...
Click to collapse
You need to go stock ROM first and then try s-off
Sent from my Evo 3D GSM using xda premium
simran420 said:
You need to go stock ROM first and then try s-off
Sent from my Evo 3D GSM using xda premium
Click to expand...
Click to collapse
Thanks for your reply, how can I go to stock ICS? Which RUU I must pick to flash? I'm from Greece. (GSM Model)
If I keep a Nandroid, can I restore it after s-off with wiping the stock rom? Or I must start from the begining?
Well, in theory any sense 3.6 based roms should work. Not sure about mwakiousrom though. To go completely stock you must flash a ruu as far as im concerned. Just download the appropriate ics RUU. Link
Since you are s on, lock bootloader with"fastboot oem lock". Run RUU. It will take a long time to finish. After that you must unlock bootloader from htcdev. Flash recovery. And finally, do the wire trick. After wire trick flash hboot 1.49. Link. You need to format all partitions except sd card after hboot change.
You can get the correct Europe ICS RUU from here -> http://www.androidfiles.org/ruu/sec...00U_11.25.3504.06_M_release_262714_signed.exe
MrJyrks said:
Well, in theory any sense 3.6 based roms should work. Not sure about mwakiousrom though. To go completely stock you must flash a ruu as far as im concerned. Just download the appropriate ics RUU. Link
Since you are s on, lock bootloader with"fastboot oem lock". Run RUU. It will take a long time to finish. After that you must unlock bootloader from htcdev. Flash recovery. And finally, do the wire trick. After wire trick flash hboot 1.49. Link. You need to format all partitions except sd card after hboot change.
Click to expand...
Click to collapse
I will do it with revolutionary because I know how revolutionary works (old Desire Z user ) but I need to downgrade hboot. In theory can I get a nandroid and restore after all this? Or the rom should be unstable?
You can restore stuff from a nandroid using this app
It restores apps/data, wifi settings, sms etc. It will require you to have a rooted rom. So in theory after you have done the wire trick you can flash a rooted rom and restore important stuff with this app
---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------
https://play.google.com/store/apps/details?id=com.rerware.android.MyBackup&hl=en
Another backup option
And just a reminder, wire trick sometimes corrupts sdcards. so save your backups before doing wire trick
Oh, your on hboot 1.49? Revolutionary tools needs 1.49 afaik. If so, get the gb RUU.
MrJyrks said:
Oh, your on hboot 1.49? Revolutionary tools needs 1.49 afaik. If so, get the gb RUU.
Click to expand...
Click to collapse
I'm downloading the GB RUU, I think...
Code:
RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed.exe
is that right?
and one last thing, I think my mobile is vodafone branded, CID VODAP102.
then you should flash a vodafone ruu. And what hboot do you have? you cant run a GB ruu on a phone with the ics bootloader(1.53)
EM|NEM said:
then you should flash a vodafone ruu. And what hboot do you have? you cant run a GB ruu on a phone with the ics bootloader(1.53)
Click to expand...
Click to collapse
I have 1.53.0007 hboot. how I can downgrade the hboot? any suggestion?
mhnx said:
I have 1.53.0007 hboot. how I can downgrade the hboot? any suggestion?
Click to expand...
Click to collapse
Gosh. Maybe there is a way, but i am not aware of it. It is certainly a lot more easier to do the wire trick.
MrJyrks said:
Gosh. Maybe there is a way, but i am not aware of it. It is certainly a lot more easier to do the wire trick.
Click to expand...
Click to collapse
Then I'm going to make the wire trick, just hoping the ics ruu will work to get stock back. How much fool am I?
EDIT: The
Code:
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed
RUU doesn't work, It reads the software info, I press start and nothing happens to my phone.
[Q] Getting "Error [140]: Bootloader Version Error" when I try to downgrade my HBoot
Okiedoke. So, I've got a little experience with the Evo 3D, but my last one was shoddily done and I don't think I ever even attained S-OFF on it, so when I had to get mine replaced by Sprint, I figured I'd follow a guide and do this thing right.
I first followed the HTC method of unlocking my bootloader and rooting the device, and then installed TWRM. I was using my phone for about a week before I just today decided I had enough time to look at these instructions and follow them. I successfully used this PG86IMG file (from this thread) to brick my device, followed the instructions from the original thread up to 27, and then realized I might have a problem on my hands. I can't boot my phone into the OS anymore (I get a sudden slowdown and then freeze of the boot animation before it restarts itself), but I can still get into the bootloader and Fastboot. So, I figured, why not just run the 1.13 RUU EXE in Fastboot? So I tried, but every time I try to run an RUU EXE (I've tried several, both 1.13 and 2.17 versions), after the RUU pushes the file to the phone and checks signatures I get error 140. I saw that Unknownforce said here that these instructions are "extremely dated" and to use the new ones in his newer thread, but I'm not sure where to pick up.
In short, I would love it if someone could recognize what the next step I need to take is. Ask me for any further information I haven't provided, I'll be more than glad to help you guys help me!
I'm having a similar issue, the only difference between our issues being that I get Error 131: CUSTOMER ID ERROR. Still working on how to fix it.
Macadamia Daze said:
I'm having a similar issue, the only difference between our issues being that I get Error 131: CUSTOMER ID ERROR. Still working on how to fix it.
Click to expand...
Click to collapse
Well this probably won't help with my issue, but this guy seems to have found a solution for yours.
Macadamia Daze said:
I'm having a similar issue, the only difference between our issues being that I get Error 131: CUSTOMER ID ERROR. Still working on how to fix it.
Click to expand...
Click to collapse
Put the PG86IMG(.zip) on the sdcard and boot to bootloader and update that way. The ruu exe checks the Cid, the bootloader flash doesn't.
Sent from my SPH-L720 using xda app-developers app
Unknownforce said:
Put the PG86IMG(.zip) on the sdcard and boot to bootloader and update that way. The ruu exe checks the Cid, the bootloader flash doesn't.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I tried this two different ways:
Got a 1.13 PG86IMG ZIP from Shipped ROMs, renamed to PG86IMG and put on my SD card, but my phone didn't want anything to do with it (it would load and check it, but then kick me back out to the main bootloader screen). Then I downloaded a 1.13 RUU EXE and extracted the "rom" file from it, renamed and slapped on card. Phone loads and checks correctly, but then returns the "Main version is older!" error.
DavisJ3608 said:
I tried this two different ways:
Got a 1.13 PG86IMG ZIP from Shipped ROMs, renamed to PG86IMG and put on my SD card, but my phone didn't want anything to do with it (it would load and check it, but then kick me back out to the main bootloader screen). Then I downloaded a 1.13 RUU EXE and extracted the "rom" file from it, renamed and slapped on card. Phone loads and checks correctly, but then returns the "Main version is older!" error.
Click to expand...
Click to collapse
Then your misc version didn't downgrade as it should have. Go to the main thread and flash the firmware zip file that's listed there, it will put you up to 1.58 hboot, then start that process from scratch.
Unknownforce said:
Then your misc version didn't downgrade as it should have. Go to the main thread and flash the firmware zip file that's listed there, it will put you up to 1.58 hboot, then start that process from scratch.
Click to expand...
Click to collapse
Okiedoke. Just to verify (sorry for being thick), when you say "Main Thread" you're talking about this one, right? I ask because the only firmware I see there is for Virgin, and I'd rather keep Sprint firmware on my phone (unless it really, truly doesn't change anything but the name).
Also, your method requires launching a Linux distro, yes? Is it OK if it's off a live USB, like the Ubuntu installer OS? For some reason I can't get my machine to cooperate when I try to install a permanent Linux OS (something to do with UEFI settings, I think).
DavisJ3608 said:
Okiedoke. Just to verify (sorry for being thick), when you say "Main Thread" you're talking about this one, right? I ask because the only firmware I see there is for Virgin, and I'd rather keep Sprint firmware on my phone (unless it really, truly doesn't change anything but the name).
Also, your method requires launching a Linux distro, yes? Is it OK if it's off a live USB, like the Ubuntu installer OS? For some reason I can't get my machine to cooperate when I try to install a permanent Linux OS (something to do with UEFI settings, I think).
Click to expand...
Click to collapse
That thread yes, but I mean the PG86IMG file from the downgrade section there, use that to update the hboot and firmware, then start that section from scratch.
And yes any linux will work USB or not.
Unknownforce said:
That thread yes, but I mean the PG86IMG file from the downgrade section there, use that to update the hboot and firmware, then start that section from scratch.
And yes any linux will work USB or not.
Click to expand...
Click to collapse
I actually ended up pulling an old laptop out from storage and putting Ubuntu on that so I can have an actual workstation. I ran the PG86IMG you mentioned, which got my phone back up and running with HBOOT 1.58. Then I followed all of your instructions to the letter, down to where you say to run the 1.13 RUU EXE. I tried running that on Ubuntu using WINE, but I kept getting an error. Then I tried running it on Windows 8, but I can't seem to get the EXE to detect my phone is connected. Then I even tried running the RUU in a WinXP virtual machine, but I can't seem to get that to work either. I then tried simply using the 1.13 ZIP as PG86IMG, but I'm getting the same error where after it loads and scans the file, it kicks me out to the main bootloader screen with no warnings or error messages.
At this point, what would be the better option? Should I attempt Revolutionary and get S-Off, then redo the instructions? Or should I do something else? Do I even need to install the 1.13 RUU? I assume I do, because my phone is unusable if I don't...
DavisJ3608 said:
I actually ended up pulling an old laptop out from storage and putting Ubuntu on that so I can have an actual workstation. I ran the PG86IMG you mentioned, which got my phone back up and running with HBOOT 1.58. Then I followed all of your instructions to the letter, down to where you say to run the 1.13 RUU EXE. I tried running that on Ubuntu using WINE, but I kept getting an error. Then I tried running it on Windows 8, but I can't seem to get the EXE to detect my phone is connected. Then I even tried running the RUU in a WinXP virtual machine, but I can't seem to get that to work either. I then tried simply using the 1.13 ZIP as PG86IMG, but I'm getting the same error where after it loads and scans the file, it kicks me out to the main bootloader screen with no warnings or error messages.
At this point, what would be the better option? Should I attempt Revolutionary and get S-Off, then redo the instructions? Or should I do something else? Do I even need to install the 1.13 RUU? I assume I do, because my phone is unusable if I don't...
Click to expand...
Click to collapse
If the bootloader is not saying anything about the zip file it's not a valid signed zip. Find another copy of it or extract it from the ruu exe. Run the exe and open up the temp folder and search for rom.zip then rename to PG86IMG(.zip) and put on sdcard. Then try again. You need special drivers for windows 8, which is why that didn't work, the other two are emulated versions of Windows, and don't have the proprietary drivers to work properly either. So unless you have access to another windows pc that isn't 8, your only option is to get the sdcard the correct file.
Sent from my SPH-L720 using xda app-developers app
DavisJ3608 said:
Well this probably won't help with my issue, but this guy seems to have found a solution for yours.
Click to expand...
Click to collapse
No dice. I can't change my CID without getting an error, presumably because I can't HTCDev unlock (when I get to the final step, I get success on fastboot but never the prompt on the phone).
Unknownforce said:
Put the PG86IMG(.zip) on the sdcard and boot to bootloader and update that way. The ruu exe checks the Cid, the bootloader flash doesn't.
Click to expand...
Click to collapse
Hboot just checked my CID and kicked me out.
Macadamia Daze said:
No dice. I can't change my CID without getting an error, presumably because I can't HTCDev unlock (when I get to the final step, I get success on fastboot but never the prompt on the phone).
Hboot just checked my CID and kicked me out.
Click to expand...
Click to collapse
Uhhh... Pretty sure that is to super cid a gsm phone
I don't think it's meant for CDMA!!
Unknownforce said:
If the bootloader is not saying anything about the zip file it's not a valid signed zip. Find another copy of it or extract it from the ruu exe. Run the exe and open up the temp folder and search for rom.zip then rename to PG86IMG(.zip) and put on sdcard. Then try again. You need special drivers for windows 8, which is why that didn't work, the other two are emulated versions of Windows, and don't have the proprietary drivers to work properly either. So unless you have access to another windows pc that isn't 8, your only option is to get the sdcard the correct file.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Oh my god, I feel like a dumbass for not pulling the rom from the EXE before saying anything o.o
Anywho, I pushed the 1.13 PG86IMG correctly, then ran Revolutionary on Ubuntu, and now my phone's S-Off and 1.40! Thanks so much! Hand to god, when I get paid I'm sending you beer money.
DavisJ3608 said:
Oh my god, I feel like a dumbass for not pulling the rom from the EXE before saying anything o.o
Anywho, I pushed the 1.13 PG86IMG correctly, then ran Revolutionary on Ubuntu, and now my phone's S-Off and 1.40! Thanks so much! Hand to god, when I get paid I'm sending you beer money.
Click to expand...
Click to collapse
Haha, glad it worked :highfive:
I would like to start out with saying that I am not new to rooting/roms but a lot has changed since I went to iOS. I have TWRP accessible and I can push files to my /sdcard/
I have tried several rooms but all of them fail to install.
Can someone please tell me the steps I need to take to go back to either stock or have another ROM working? (RUU fails as well, however it does detect the phone)
Any help is appreciated and trust me I spent hours reading threads so not just posting this for an easy way out.
chirayu said:
I would like to start out with saying that I am not new to rooting/roms but a lot has changed since I went to iOS. I have TWRP accessible and I can push files to my /sdcard/
I have tried several rooms but all of them fail to install.
Can someone please tell me the steps I need to take to go back to either stock or have another ROM working? (RUU fails as well, however it does detect the phone)
Any help is appreciated and trust me I spent hours reading threads so not just posting this for an easy way out.
Click to expand...
Click to collapse
First, this should probably be in the Q&A section
Second, gonna need WAY more info about your phone. I assume you're rooted? S-off or S-on? What hboot version are you on? What version of TWRP are you currently using? What ROM are you on now? What RUU are you trying to use? Gonna have to give a little bit for us to work with.
Edit: Your signature also says you have the Evo Shift? Are you on the write forum?
Greenfieldan said:
First, this should probably be in the Q&A section
Second, gonna need WAY more info about your phone. I assume you're rooted? S-off or S-on? What hboot version are you on? What version of TWRP are you currently using? What ROM are you on now? What RUU are you trying to use? Gonna have to give a little bit for us to work with.
Edit: Your signature also says you have the Evo Shift? Are you on the write forum?
Click to expand...
Click to collapse
I apologize for posting this in the wrong forum, like I was saying I haven't been here in a while and signature is outdated by about 6 years
Heres the info
TWRP v2.7.1.0
S-ON
HBOOT-2.10.0000
RADIO-1.13.11.1105
I had the last leaked RUU installed before I attempted flashing a custom ROM
Thank you for your reply!
chirayu said:
I apologize for posting this in the wrong forum, like I was saying I haven't been here in a while and signature is outdated by about 6 years
Heres the info
TWRP v2.7.1.0
S-ON
HBOOT-2.10.0000
RADIO-1.13.11.1105
I had the last leaked RUU installed before I attempted flashing a custom ROM
Thank you for your reply!
Click to expand...
Click to collapse
Is your goal to flash another ROM or to go back to stock?
If you're going to be trying to flash another ROM I'd highly recommend running rumrunner and getting s-off. Otherwise there are a lot of hoops you'll need to jump through in order to flash ROMs (for starters, you'll need to flash the kernel separately).
Code:
Greenfieldan said:
Is your goal to flash another ROM or to go back to stock?
Click to expand...
Click to collapse
Whichever one is faster, I just want the phone up and running again.
So it's not running at all now? I'm assuming you can boot into bootloader and recovery but nothing else, right? You can run an RUU while in fastboot if I recall, which will give you at least a usable phone. That's also probably the fastest thing to do.
After that I'd highly recommend using rumrunner to get s-off. Otherwise flashing new ROMs will be a bear.
Greenfieldan said:
So it's not running at all now? I'm assuming you can boot into bootloader and recovery but nothing else, right? You can run an RUU while in fastboot if I recall, which will give you at least asable phone. That's also probably the fastest thing to do.
After that I'd highly recommend using rumrunner to get s-off. Otherwise flashing new ROMs will be a bear.
Click to expand...
Click to collapse
RUU fails with errors and it gets stuck at "HTC" screen
Do you have HTC Sync installed on your computer?
Greenfieldan said:
Do you have HTC Sync installed on your computer?
Click to expand...
Click to collapse
Ah, I think something else made me delete it.
That'll do it. You need to have HTC Sync and all of the necessary drivers to run the RUU
Greenfieldan said:
That'll do it. You need to have HTC Sync and all of the necessary drivers to run the RUU
Click to expand...
Click to collapse
Thank you! giving that a try now
greenfieldan said:
that'll do it. You need to have htc sync and all of the necessary drivers to run the ruu
Click to expand...
Click to collapse
error [155]: Uknown error
chirayu said:
error [155]: Uknown error
Click to expand...
Click to collapse
D'oh! I bet your bootloader is still unlocked. It needs to be relocked before running the RUU.
Fastboot command 'fastboot oem lock' ought to do the trick.
Greenfieldan said:
D'oh! I bet your bootloader is still unlocked. It needs to be relocked before running the RUU.
Fastboot command 'fastboot oem lock' ought to do the trick.
Click to expand...
Click to collapse
You're a life saver! at least you can bet I have rooting/unrooting down for this EVO. Just like the old times
Moved to Q&A forum