Related
Hi everyone,
I've found the information in these forums to be very helpful and have never posted on anything before, but I have a question that I'm not finding a good answer for.
I successfully unlocked my bootloader and rooted last night and am now running scrosler's CleanROM. However I want to return to stock using the RUU from here:
http://forum.xda-developers.com/showthread.php?t=1338916
When I run the RUU I am getting stuck at the HTC recovery screen, and the windows installer tells me that the RUU is not compatible. I tried extracting the rom.zip, renamed it to PH98IMG.zip, copied it to the SDcard and load it in HBOOT, but it won't work either.
Any ideas? I mainly just want to make sure I have a working method to return to stock just in case I accidentally brick the phone at some point, but otherwise I'm good for now.
You run the ruu from your pc if it's like other htcs
sent from my newly unlocked Rezound
phackney said:
Hi everyone,
I've found the information in these forums to be very helpful and have never posted on anything before, but I have a question that I'm not finding a good answer for.
I successfully unlocked my bootloader and rooted last night and am now running scrosler's CleanROM. However I want to return to stock using the RUU from here:
http://forum.xda-developers.com/showthread.php?t=1338916
When I run the RUU I am getting stuck at the HTC recovery screen, and the windows installer tells me that the RUU is not compatible. I tried extracting the rom.zip, renamed it to PH98IMG.zip, copied it to the SDcard and load it in HBOOT, but it won't work either.
Any ideas? I mainly just want to make sure I have a working method to return to stock just in case I accidentally brick the phone at some point, but otherwise I'm good for now.
Click to expand...
Click to collapse
You need to have a recovery backup. Then you can always go back.
Sent from my Galaxy Tab 10.1
Neither of these answers attempt to address the issue of why the RUU doesn't work.
Have you tried both?
sent from my newly unlocked Rezound
Here's a more specific account of what happens when I run the RUU.
I get the progress bar that says "Sending......." but then after a few seconds I get the following error:
Error [155] unknown error
The ROM Update Utility cannot update your Android phone
Please get the correct ROM Update Utility and try again
I've spent the last hour Googling this error and have found that it is a known error with other HTC devices but can't find any info on the Rezound.
Found this helpful thread for a similar issue with the Desire:
http://forum.xda-developers.com/showthread.php?t=1029401
Tried starting the RUU with the phone already in fastboot but that didn't change anything.
What does it do when you copy the zip to the sd card and run it?
marclile said:
What does it do when you copy the zip to the sd card and run it?
Click to expand...
Click to collapse
I get the little progress bar in the upper right corner of HBOOT that shows it is reading the file, however it doesn't present me with the option to flash it. Instead it just skips to the HBOOT menu.
phackney said:
I get the little progress bar in the upper right corner of HBOOT that shows it is reading the file, however it doesn't present me with the option to flash it. Instead it just skips to the HBOOT menu.
Click to expand...
Click to collapse
Interesting, I wonder if anyone has ran it this ruu successfully
Solved
Figured it out. On a hunch I re-locked the bootloader and tried running the RUU using the Windows installer and it worked. It must be some sort of security check thing. I'll just unlock the bootloader again after it's done flashing. It might be good for someone with more seniority on the forum to make this information more visible in case anyone else runs into this issue.
phackney said:
Figured it out. On a hunch I re-locked the bootloader and tried running the RUU using the Windows installer and it worked. It must be some sort of security check thing. I'll just unlock the bootloader again after it's done flashing. It might be good for someone with more seniority on the forum to make this information more visible in case anyone else runs into this issue.
Click to expand...
Click to collapse
I agree. It probably needs to be added to the post that has the ruu files and it.
Glad you got it working.
Sent from my Galaxy Tab 10.1
marclile said:
I agree. It probably needs to be added to the post that has the ruu files and it.
Click to expand...
Click to collapse
Can you make that happen?
phackney said:
Can you make that happen?
Click to expand...
Click to collapse
i can't change the post but i'll post something in that thread.
Any idea on how to get the phone to relock if "fastboot oem lock" goes to "waiting for device" without responding?
I'm in a similar situation, but I cannot seem to get my phone to relock.
Nevermind. I forgot to get into bootloader mode via adb.
phackney said:
Figured it out. On a hunch I re-locked the bootloader and tried running the RUU using the Windows installer and it worked. It must be some sort of security check thing. I'll just unlock the bootloader again after it's done flashing. It might be good for someone with more seniority on the forum to make this information more visible in case anyone else runs into this issue.
Click to expand...
Click to collapse
Thank you. Had the same error. Felt like an idiot when I read your post. Can't believe I didn't think of that first.
So how do you re-lock? Thanks
Fastboot oem lock
Sent from my ADR6425LVW using XDA
10 characters
I rooted my evo 4g lte. I was having issues with data today and updating the profile. so I was going to unroot and try it stock. I relocked the bootlader, and somehow my rom image is gone!!!! i cant flash the ruu, it keeps failing error 155. someone please help me
Wrong thread. Need to be posted in q&a
sent from my EVO LTE with it's security flags down.
jrgalioto said:
I rooted my evo 4g lte. I was having issues with data today and updating the profile. so I was going to unroot and try it stock. I relocked the bootlader, and somehow my rom image is gone!!!! i cant flash the ruu, it keeps failing error 155. someone please help me
Click to expand...
Click to collapse
Similar thing happened to me. I have hboot 1.15. I relocked the the phone ran the RUU. Phone booted up normal with the everything stock. I then took the OTA and when it rebooted it was updating then it rebooted and the phone never turned on again. I sent it to HTC for warranty. They will get it tuesday. I'll see how this goes.
Okay guys... Enough with the flaming. If you can help, post! If not, don't. Grow up. It was posted in the wrong section. Use the report button in the upper-right corner of the post and report it.
Now, let me see if I can actually help you.
You're getting this error because you're trying to flash an older RUU on the phone than what's already on there. You'll need to flash the same RUU version or higher. If you took the latest OTA update, there may not be one available yet. I'd suggest you go through the HTCDev unlock again until that RUU makes it to the internet.
Team Nocturnal posted a couple of the older RUU versions.
http://www.androidfilehost.com/main/EVO_4G_LTE_Developers/Team.Nocturnal/RUU/
~co~
closeone said:
Okay guys... Enough with the flaming. If you can help, post! If not, don't. Grow up. It was posted in the wrong section. Use the report button in the upper-right corner of the post and report it.
Now, let me see if I can actually help you.
You're getting this error because you're trying to flash an older RUU on the phone than what's already on there. You'll need to flash the same RUU version or higher. If you took the latest OTA update, there may not be one available yet. I'd suggest you go through the HTCDev unlock again until that RUU makes it to the internet.
Team Nocturnal posted a couple of the older RUU versions.
http://www.androidfilehost.com/main/EVO_4G_LTE_Developers/Team.Nocturnal/RUU/
~co~
Click to expand...
Click to collapse
Here is the issue with that though. When i run the RUU, it says my current image is........nothing. i have tried to flash the newest and the oldest versions.
jrgalioto said:
Here is the issue with that though. When i run the RUU, it says my current image is........nothing. i have tried to flash the newest and the oldest versions.
Click to expand...
Click to collapse
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
closeone said:
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
Click to expand...
Click to collapse
I relocked because I needed to bring it back to Sprint for service, so I needed to unroot it, because I wasn't receiving data to it. But I got it figured out now. I was able to unlock the bootloader again and my recovery was still there. So i reflashed a custom ROM, so I at least had something on my phone. When I called Sprint, I told them it was not a phone issue, they updated my username in the system, then I was able to ##72786# to get the hands free activation to complete without error 1012. So I am now back in business. However, If I ever do have to unroot again, I will be in the same boat.
jrgalioto said:
I relocked because I needed to bring it back to Sprint for service, so I needed to unroot it, because I wasn't receiving data to it. But I got it figured out now. I was able to unlock the bootloader again and my recovery was still there. So i reflashed a custom ROM, so I at least had something on my phone. When I called Sprint, I told them it was not a phone issue, they updated my username in the system, then I was able to ##72786# to get the hands free activation to complete without error 1012. So I am now back in business. However, If I ever do have to unroot again, I will be in the same boat.
Click to expand...
Click to collapse
For future ref...sprints tep policy covers rooted phones
Of course the first variable that could be the issue in any given situation is the fact that a phone is rooted
Sent from my SPH-L710 using xda app-developers app
00mred00 said:
For future ref...sprints tep policy covers rooted phones
Of course the first variable that could be the issue in any given situation is the fact that a phone is rooted
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That was the 1st thought I had. What if the root is causing the issue. It, however was not the case. and all is now right with the world, and I am no longer a brick...for now...
jrgalioto said:
That was the 1st thought I had. What if the root is causing the issue. It, however was not the case. and all is now right with the world, and I am no longer a brick...for now...
Click to expand...
Click to collapse
Hi jrgalioto,
I was able to get a link to the new RUU for you. This one should work fine for you.
~co~
Yep...... sprint doesnt care that you're rooted.
I frequently tell them mine is so they dont go messing with things they shouldnt be
OK I just cleaned this thread of a bunch of GARBAGE.
If you don't want to help, post on a blog.
The guy is looking for help.
Seriously .
il Duce said:
OK I just cleaned this thread of a bunch of GARBAGE.
If you don't want to help, post on a blog.
The guy is looking for help.
Seriously .
Click to expand...
Click to collapse
Sorry duce
Sent from the depths of hell
Hey I try to help and I have even written a guide with a ton of info, I even went so far as to write down troubleshooting stuff and they still post the exact same stuff over and over, some times its a bit frustrating. I even gave instructions on what they need to do should they completely ruin the file tree, when have you seen anyone completely destroy the internal memory lol
closeone said:
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
Click to expand...
Click to collapse
Any luck on the mirror for the new RUU download? I'm using the latest one I can find and I am stuck and can't get my phone to reboot, shutdown or anything. I can't run fastboot either. all I see is ***Tampered*** unlocked*** ....RUU update fail!
My phone won't respond to the volume down and power button either.
any suggestions?
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
While you're at bootloader, connect USB and then flash a stock RUU.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Thanks for the reply. Will i lose s-off with this?
Tones1971 said:
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
Click to expand...
Click to collapse
You didn't say what version of the Evo 3D you have (CDMA or GSM) or what bootloader is installed, but if it's a Sprint CDMA model I would recommend flashing the Sprint ICS RUU.exe from Windows after putting the phone into fastboot mode in the bootloader. You may have to relock the bootloader with the "fastboot oem lock" command first if it shows "***UNLOCKED***" at the top of the screen.
That will fix a lot of problems, especially when the phone is in an indeterminate state. After flashing the RUU you can HTC unlock, flash a custom recovery and then root the stock ROM or flash a rooted ROM.
ramjet73
Sorry it is a UK GSM (Europe). I have revolutionary bootloader installed. Got an RUU to try now thanks.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Tones1971 said:
Thanks for the reply. Will i lose s-off with this?
Click to expand...
Click to collapse
^^^^ He got it first with the short version.
No, you won't lose S-OFF and won't need to relock the bootloader first if that's your current status.
And if it's a GSM model everything still applies, you just need a different RUU, which you already have.
ramjet73
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Tones1971 said:
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Click to expand...
Click to collapse
Error 170 means that the RUU utility can't find the phone. There's a readme.doc for running the RUU here, and the error codes are towards the end of that.
Are you putting it into "fastboot" mode in the bootloader, which should change to "fastboot usb" when it is connected to a computer? You also need to have the HTC USB drivers active, which can be accomplished by installing HTC Sync.
ramjet73
Tones1971 said:
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Click to expand...
Click to collapse
adb push into a bootlooping phone?
do you have the drivers for the phone? (if not download and install HTC Sync as they come with it)
did you try flashing a custom recovery img through fastboot? (go to bootloader select fastboot, connect USB, type "fastboot flash recovery nameOfYourRecoveryImg.img")
Yeah have tried installing custom recovery through fast boot again, and im in fastboot ok when trying to run the RUU. Also have HTC Sync installed from when i had the phone.. Drivers seemed to be ok as i was able to install the custom recovery with adb, alhough i still got bootloop after that.
Ive a few other things to try when i get home from work. Im sure it shouldnt be too difficult to resolve. Hopefully anyway.
Well this isnt going smoothly at all. Used another PC and was able to get the RUU to run.
However it now comes up with Error 131 Customer ID problem. The RUU was for HTC Europe (non branded). The phone was sim free. When i posted months back my cid was HTC_001. I checked it here: http://forum.xda-developers.com/showpost.php?p=22394863&postcount=172
However now when i get my CID it is showing as CID0202. Any way i can get an RUU to install? Any idea how a CID could change?
EDIT: noticed i used a different command last time.
fastboot getvar cid shows CID0202
adb shell getprop ro.cid now shows device not found (previously showed CID_001)
Thats typing both commands in same window, one after the other. One gets CID0202, the other device not found???
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
dessolator666 said:
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
Click to expand...
Click to collapse
Thanks for this. Ill see if i can find anything else out about it. So saves running the RUU exe and no cid check done then?
Need to bump this as im not getting anywhere. No RUU's will install, error 31 customer error. Have flashed recovery via ADB and through PG86IMG.ZIP, but still cant get in to recovery as it just continually reboots.
S-OFF with revolutionary. Anybody any ideas please?
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Tones1971 said:
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Click to expand...
Click to collapse
You need to stop cross posting in the d3rp Q&A thread and your own thread if you want more help. Cross-posting is stongly discouraged on XDA and it's really confusing when you are asking for help in one thread while getting different advice in another.
It sounds to me like all the CID changes on your phone have left it in an indeterminate state and I'm not sure at this point what is the correct CID and RUU for your model. If you could detemine that, set the CID correctly and flash the right RUU the phone should work, but it might be too late if you have in fact been flashing firmware that doesn't match your phone because the right RUU may not back that out properly.
That's all I can offer at this point, but since I don't know the history of your phone and how it got the various CID's you have reported, you will probably be the one that needs to figure it out.
ramjet73
Okay I have made a thread about this before, but no one had an answer for me, so I will try again, but I will be more descriptive of my issue.
So the other day, my Evo 3D, which is flashed to MetroPCS, lost its carrier settings when I was flashing a ROM. So I had to go home and use QPST to edit some files in the nvm/num folder (Using EFS). While I was editing, the program crashed, and I was forced to unplug my Evo.
Now, after it rebooted, it would go past the HTC Screen, and flash the boot animation for a split second, then shut off and restart. It would loop like this no matter how long I left it.
So I went into 4-EXT recovery, and formatted system, boot, data etc, and then flashed a ROM. Rebooted and got the same thing. So in a last ditch effort, I downloaded the latest ICS RUU for this phone, and tried all three methods to install. I ran the .exe, the program ran as expected, and the phone showed the progress bar on a black HTC Screen as updating, it rebooted when done, and then just continued to bootloop. I also pulling the rom.zip and renaming it to PG86IMG.zip and flashing it from fastboot. It worked and once it rebooted, did the same thing. I also ran it from fastboot usb, and got the same result.
However, I extracted the rom.zip and tried to use fastboot to flash individual .img files, and on EVERY one, I got "FAILED - Error: (remote: not allowed).
I had previously used the wiretrick to get S-OFF on my Hboot 1.58.
It says "Unlocked" at the top of the bootloader.
I really need to get my phone working, can someone PLEASE point me in the correct direction or at least help me out? Is my phone ruined? Is there a way I can clear the NV memory or something to truly reset the phone?
Once again, I will repeat, RUUs will not work!, I am S-OFF on HBOOT 1.58, my bootloader says "unlocked." No matter what I do it will bootloop. I can flash a recovery, but if I flash a rom it does the same stuff.
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
coal686 said:
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
Click to expand...
Click to collapse
I don't remember, but wouldn't the RUU fail if it was unlocked? Because it didn't fail, it just didnt work.
So now I screwed up, I got it to be able to erase/write in fastboot, I used fastboot erase instead of fastboot format and now my partitions are gone, how do I get those back?
AtmosFEAR4701 said:
I don't remember, but wouldn't the RUU fail if it was unlocked? Because it didn't fail, it just didnt work.
Click to expand...
Click to collapse
Sounds like a similar thing that happened to me when trying to flash a JB rom with a kernal that was not compatable....no matter what I did I could not get it out of the boot loop...I am Hboot 1.58 HTC unlocked and wire trick S-off...I finally flashed an old backup I had with a stock kernal and it fixed it all...dont know if this helps you at all but try wiping everything possible and flashing a stock kernal or an old backup you may have...
coal686 said:
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
Click to expand...
Click to collapse
His s-off so doesn't matter if its locked or not.
iTzLOLtrain said:
His s-off so doesn't matter if its locked or not.
Click to expand...
Click to collapse
Good to know. I always thought you had to lock the bootloader anyway but leave it s-off. I learn something new everyday. :beer:
coal686 said:
Good to know. I always thought you had to lock the bootloader anyway but leave it s-off. I learn something new everyday. :beer:
Click to expand...
Click to collapse
Ok so I had accidenatly did "fastboot erase" and lost my partitions. I flashed the RUU again and now they are back, but if I try to use fastboot format, it says "Failed - Error: (remote: unknown command)." and it also said something about cannot determine partition type or something. I really need some help lol.
AtmosFEAR4701 said:
Ok so I had accidenatly did "fastboot erase" and lost my partitions. I flashed the RUU again and now they are back, but if I try to use fastboot format, it says "Failed - Error: (remote: unknown command)." and it also said something about cannot determine partition type or something. I really need some help lol.
Click to expand...
Click to collapse
Why are you using fastboot commands like "erase" and "format". Partitions should be formatted in recovery, not the bootloader.
If the RUU ran successfully it should reboot into the stock ROM when it finished. Did that work?
ramjet73
ramjet73 said:
Why are you using fastboot commands like "erase" and "format". Partitions should be formatted in recovery, not the bootloader.
If the RUU ran successfully it should reboot into the stock ROM when it finished. Did that work?
ramjet73
Click to expand...
Click to collapse
My first post says that I have run the RUU countless times and it still bootloops.
Nevermind... I sold it.
AtmosFEAR4701 said:
Nevermind... I sold it.
Click to expand...
Click to collapse
That's one way to solve the problem.
Sorry we couldn't figure it out.
coal686 said:
That's one way to solve the problem.
Sorry we couldn't figure it out.
Click to expand...
Click to collapse
It's okay. I am not buying another Evo 3D though. I am a MetroPCS customer so I buy flashed phones a lot, and I have a low budget so I'll either grab a flash Galaxy S2, or possibly grab the MetroPCS Galaxy S3 when I get some money.
[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: