I'm trying to reset my device to stock, and for this i need the correct RUU.. But the ones i tried give the same error, saying it's the wrong RUU file.
It's a GSM EVO 3D, rooted/S-OFF'd with revolutionary and has baseband 11.77.3504.00U_11.25.3504.06_M.
I tried downloading and using this one:
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.exe
But that gives me an error.
Then i remembered i had downloaded the RUU when i got the phone to start with, when i was first rooting my phone so i could revert back if needed (had it stored away on my old HDD). Tried this:
RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9020.00_10.13.9020.08_2M_release_203403_signed.exe
And still got the same error.
Could anyone help me?
You have to flash it from your computer if you haven't tried that already. Make sure USB debugging is enabled first before attempting to run your exe.
Jsparta26 said:
You have to flash it from your computer if you haven't tried that already. Make sure USB debugging is enabled first before attempting to run your exe.
Click to expand...
Click to collapse
Yes i'm doing it from my computer.
Yes i have USB debugging on.
I can connect just fine using both ADB and Fastboot aswell, so not even drivers can be a problem (if they're even needed).
Try relocking your boot loader.
Assuming you actually do have the right ruu.exe for your region and carrier, I can think of two issues:
1. Did you relock the bootloader as jsparta said?
2. Have you changed your cid/device id in the past? Maybe the ruu thinks the phone is a different model if you did.
coal686 said:
Assuming you actually do have the right ruu.exe for your region and carrier, I can think of two issues:
1. Did you relock the bootloader as jsparta said?
2. Have you changed your cid/device id in the past? Maybe the ruu thinks the phone is a different model if you did.
Click to expand...
Click to collapse
Bingo!
According to this post it looks like his CID has been changed. Many people have had problems flashing an RUU after changing the CID and I'm not sure how to fix it since I've never needed to do that myself.
ramjet73
I never knowingly changed my CID, and it's so long ago i rooted my Evo 3D that i can't even remember exactly how i did it, but i used Revolutionary for some of it (my HBOOT says "Revolutionary" at the top).
I tried to do "fastboot oem lock", and it said "Device is already locked" or something along those lines.
Is there any CID that i can just change to (with "fastboot oem writecid XXX") in order to make the RUU work?
Moonbloom said:
I never knowingly changed my CID, and it's so long ago i rooted my Evo 3D that i can't even remember exactly how i did it, but i used Revolutionary for some of it (my HBOOT says "Revolutionary" at the top).
I tried to do "fastboot oem lock", and it said "Device is already locked" or something along those lines.
Is there any CID that i can just change to (with "fastboot oem writecid XXX") in order to make the RUU work?
Click to expand...
Click to collapse
Don't know much about Revolutionary since I used JuopunutBear (wire trick) to gain S-OFF. I'm also CDMA and not familar with the GSM RUU's, but someone posted this list of CID's and HTC_Y13 seems to be Norway if that helps someone with pointing you to the correct version.
Edit1: BTW, what error are you getting when you try to flash the RUU?
Edit2: This thread might be of some help to you. It looks like CID HTC_Y13 is supported by the RUU you already have, but some people have had to modify it to fix status 6 or 7 errors.
ramjet73
Maybe try to run flash directly from bootloader. Run your RUU file, go to your temp directory and search for file named rom.zip. Change it name to PG86IMG.zip, put it in sd card. Then go to bootloader and it should ask you to flash this soft. This one is stock ics rom and it worked for me but I was on Jbear hboot:
http://www.filefactory.com/file/2hw...00U_11.25.3504.06_M_release_262714_signed.exe
It will change your bootloader to 1.53.0007
Or you can try to find and download some GB RUU and try the same as above.
Good luck!
c000ler said:
Maybe try to run flash directly from bootloader. Run your RUU file, go to your temp directory and search for file named rom.zip. Change it name to PG86IMG.zip, put it in sd card. Then go to bootloader and it should ask you to flash this soft.
Click to expand...
Click to collapse
Good idea.
The link in the second edit of my previous post has a download for the .zip version of the ROM from that same RUU and a PG86IMG.zip firmware file without the bootloader so he doesn't have to extract it from the RUU.exe. If he wants the bootloader that comes with that build he should be able to flash it separately since he is S-OFF.
ramjet73
c000ler said:
Maybe try to run flash directly from bootloader. Run your RUU file, go to your temp directory and search for file named rom.zip. Change it name to PG86IMG.zip, put it in sd card. Then go to bootloader and it should ask you to flash this soft. This one is stock ics rom and it worked for me but I was on Jbear hboot:
http://www.filefactory.com/file/2hw...00U_11.25.3504.06_M_release_262714_signed.exe
It will change your bootloader to 1.53.0007
Or you can try to find and download some GB RUU and try the same as above.
Good luck!
Click to expand...
Click to collapse
ramjet73 said:
Good idea.
The link in the second edit of my previous post has a download for the .zip version of the ROM from that same RUU and a PG86IMG.zip firmware file without the bootloader so he doesn't have to extract it from the RUU.exe. If he wants the bootloader that comes with that build he should be able to flash it separately since he is S-OFF.
ramjet73
Click to expand...
Click to collapse
That RUU was the first one i tried to use, so i already have the file on my desktop at the moment.
Since i'm trying to go completely stock, i guess just flashing the rom.zip (after renaming it to PG86IMG.zip) will return me to stock ICS rom, stock (and updated) bootloader and S-ON ?
Moonbloom said:
That RUU was the first one i tried to use, so i already have the file on my desktop at the moment.
Since i'm trying to go completely stock, i guess just flashing the rom.zip (after renaming it to PG86IMG.zip) will return me to stock ICS rom, stock (and updated) bootloader and S-ON ?
Click to expand...
Click to collapse
If you can flash the RUU successfully from the .zip file, you will need to issue the following fastboot command to set S-ON, but make 100% sure you have the stock bootloader installed or it will brick your phone if you still have Revolutionary or another unsigned custom bootloader:
fastboot oem writesecureflag 3
ramjet73
Assuming that fastboot is saying that you are on locked bootloader, after flashing this stock ics soft you will be on stock 1.53.0007 locked bootloader. After that you must make S-ON, to do that use command:
fastboot oem writesecureflag 3
But make sure that you are 100% on stock bootloader, cause if not, you can birck your phone. Good luck!
ramjet73 was faster
I'll try to do it tomorrow, as I'm heading to bed now, but thanks for the advice so far, I'll probably be back again
Sent from my GT-N7100 using xda app-developers app
I think if you are s-off you don't need to lock the bootloader. Could he just use the PG86IMG version but alter the cid info in the android-info.txt file to match his phone's cid? It seems like it would work. I have done this with extracted portions of an ruu and altered the cid to work with VM evo v. Basically I made an hboot 1.5 PG86IMG for evo v by extracting from the sprint ruu and editing the android-info.txt to use vm cid
Sent from my PG86100 using Tapatalk 2
Brian706 said:
I think if you are s-off you don't need to lock the bootloader. Could he just use the PG86IMG version but alter the cid info in the android-info.txt file to match his phone's cid? It seems like it would work. I have done this with extracted portions of an ruu and altered the cid to work with VM evo v. Basically I made an hboot 1.5 PG86IMG for evo v by extracting from the sprint ruu and editing the android-info.txt to use vm cid
Click to expand...
Click to collapse
I recently discovered that you can specify multiple CID's in the android-info.txt file so the hboot .zip files in this post have all been modified to work with the Evo 3D and Evo V, in case you need to change hboots again.
ramjet73
ramjet73 said:
I recently discovered that you can specify multiple CID's in the android-info.txt file so the hboot .zip files in this post have all been modified to work with the Evo 3D and Evo V, in case you need to change hboots again.
ramjet73
Click to expand...
Click to collapse
Thanks. I actually have a sprint 3vo and have made my own hboot and other files for myself. Just made a couple for the evo v the other day because a few people were looking for 1.5.
So how does that multiple cid work? Do you just add extra lines into the android-info.txt or separate with a comma? I'd like to learn this. It could come in handy TIA!
Eta:
I misread your last post. I will download one of those and check it out. Thank you!
Sent from my PG86100 using Tapatalk 2
---------- Post added at 07:12 PM ---------- Previous post was at 06:45 PM ----------
Cool. It looks just like I pictured it! Thanks for sharing.
Sent from my PG86100 using Tapatalk 2
Brian706 said:
So how does that multiple cid work? Do you just add extra lines into the android-info.txt or separate with a comma? I'd like to learn this. It could come in handy TIA!
Eta:
I misread your last post. I will download one of those and check it out. Thank you!
Click to expand...
Click to collapse
There are instructions towards the end of this post from the Sensation forum. I used UltraEdit instead of Notepad++ and copied the line with the Sprint CID (SPCS_001) to a new line then modified it to the VM CID (SPCS_002). There must be an LF character that the default Notepad doesn't recognize because it opens it as one line, but WordPad and the editors show multiple lines.
Once I had the android-info.txt modified, it was easy to delete the existing version in the hboot zip files using WinZip and then copy the new version to replace it.
ramjet73
Related
hey yall i used the htc dev method to unluck the sprint 3d however when i do the flash recovery img in fastboot i get a failed remote not allowed- i have done this on other phones with no issue but i have tried every recovery.img with no luck . i also tried the PG86IMG but it just says either main version older or PARSING . ant help is MUCH appreciated.
ganjamatik said:
hey yall i used the htc dev method to unluck the sprint 3d however when i do the flash recovery img in fastboot i get a failed remote not allowed- i have done this on other phones with no issue but i have tried every recovery.img with no luck . i also tried the PG86IMG but it just says either main version older or PARSING . ant help is MUCH appreciated.
Click to expand...
Click to collapse
What exactly does your bootloader say? It sounds like it is not unlocked.
If you relocked to run the RUU.exe or take the OTA update it may not be locked now.
ramjet73
ramjet73 said:
What exactly does your bootloader say? It sounds like it is not unlocked.
If you relocked to run the RUU.exe or take the OTA update it may not be locked now.
ramjet73
Click to expand...
Click to collapse
its shows UNLOCKED and hboot 1.58 s-on
ganjamatik said:
its shows UNLOCKED and hboot 1.58 s-on
Click to expand...
Click to collapse
Hmmm...
Well, you won't be able to flash PG86IMG.zip files from the bootloader with S-ON unless thay are signed by HTC so that's probably your problem there.
The "remote not allowed" is usually an indication the bootloader is locked. Make sure your phone is in "fastboot usb" mode in the bootloader, then issue the following commands:
fastboot devices
fastboot flash recovery recovery.img (where "recovery.img" is the file name of your custom recovery)
What responses do you get?
ramjet73
it shows my device listed and then says the same remote not allowed-
Did you check usb debugging in your phone's settings first? Also if you have htc sync on your pc you may want to unistall it also. Some programs do interfere with fastboot.
ganjamatik said:
it shows my device listed and then says the same remote not allowed-
Click to expand...
Click to collapse
Can you try those fastboot commands again and copy and paste the actual output from the commands into this thread? Sometimes there is something in that which might give us a clue as to what the problem is.
Edit: Never mind. I saw you posted again in the other thread so you can wait for a response over there. Make 100% sure your bootloader is unlocked because sometimes flashing the unlock bin file doesn't take and the phone doesn't show the unlock option if you upgraded to ICS via the OTA. If nothing else works I would suggest relocking the bootloader and starting over with the RUU.exe, per the instructions in my root and S-OFF guide.
ramjet73
From the other thread
mpgrimm2 said:
My guess is that you are not really unlocked (Screenshot?) or you are not using a compatible recovery file/filename.
Have a look at the HTC Unlock Guide in my signature to see if anything stands out that you are overlooking.
Even if you get a recovery going, I'm not sure what your ultimate goal is here. You should continue this in one thread, specifically your Remote Not Allowed thread.
Click to expand...
Click to collapse
Go with Ramjet's suggestion if you don't figure it out.
I bought Evo which was already upgraded to ICS (OTA I assume), and it was branded I think. I've unlocked it via HTCDev, flashed '4ext touch recovery' and then rooted. Then I flashed MIUI ICS ROM, and everything is OK for now.
I want to use BootManager to flash multiple ROMs. It requires s-off. I tried it already with s-on, because I've read that SmartFlash (from 4ext recovery) makes my phone like s-off, so ROM on SD card installed, but won't boot. I had many problems going back to my Phone ROM, I restored my backup, wiped many times, installed fresh ROM and still had a bootloop. Finally I got it working again by flashing boot.img via fastboot (glad I did nandroid backup before). I didn't try again with different ROM, because after 2 hours of trying to recover my base ROM I've had enough. So I'm pretty sure BootManager will work better if my phone will be s-off.
So my question is - what to do next? We have so many guides and different comments here, sometimes the same method works for one, and doesn't work for another one, and I'm really confused.
I assume I should follow the instructions here http://forum.xda-developers.com/showthread.php?t=1743466 but I don't understand few things:
friend.evil said:
flash an ICS ROM from recovery(Method B from 10 to 14)
open ICS ROM.zip and extract boot.img to a folder which contains adb, fastboot and AdbWinApi.dll
go to fastboot and type:
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Do I have to do this if I'm already have MIUI with root privileges? Do I still need that boot.img from MIUI, and put it together with fastboot.exe?
Or should I restore stock ICS? I'm pretty sure I did nandroid backup before flashing MIUI.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
Do I need to fix hboot after s-off? What hboot version I have after doing steps 1 to 4 from section E? There's a big zip file (PG86IMG.zip), is it another ROM or what?
And most important question - if method D doesn't work, method F is recommended, but:
elias17 said:
Hboot s on will only flash roms that are based on ics 3.28xx and sense 4 roms using a special boot.img ! U can never flash GB roms until u go s off like i did its a tricky process but it works and now i can flash any rom in the gsm section
Click to expand...
Click to collapse
friend.evil said:
2_flash Leedroid GB ROM from recovery http://leedroid.ftp.rshost.eu/Shoote....zip(Don't forget to wipe data/factory reset and wipe cache + dalvik)
Click to expand...
Click to collapse
I don't get it - can I flash GB ROM or not if I have hboot 1.53.0007 s-on? Can I use method F if method D fail?
Sorry for my english, I'm from Poland.
Thanks in advance for any tip.
You're confusing yourself, What you need to do my friend is.
1. Download RUU, Run RUU
2. HTC Unlock bootloader again
3. Do the Juopunutbear Wiretrick to get s-off
4. Download the 1.04 ENG hboot (There is one of those for the GSM I think... not sure though)
5. Flash a badass Android 4.2.1 rom. They work.
There's much more detailed guides on what to do, BUT This is a summary of what you want.
Be sure to hit thanks [= I'm almost to 100
Which RUU should I search for? GB or ICS?
But isn't the 1+2 the same as restoring my ICS Stock ROM from backup?
I think hboot 1.49.0007 would be enough, I've read that BootManager works well with that version.
1. Yes you can just restore your stock ics backup BUT you will have to root it using the file provided in method B.
2. Yes the 1.49.0007 hboot is best for gsm
3. You can flash a GB rom with your hboot no problem. It just dont think it will boot. so technically you should be able to do the wire trick with a GB rom flashed(not booted into). You'll be in fastboot mode for the wiretrick. There are different files for GB and ICS when doing the wiretrick
Your best bet is to run an ICS RUU, unlock bootloader, root rom, do the wire trick, change hboot to 1.49.0007 and then flash any rom you want
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
mars28 said:
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
Click to expand...
Click to collapse
That should work But unlocking again is really easy
You should still have you unlock token in the same place,
You just plug up to the computer hop into fastboot usb and type
Fastboot flash unlocktoken Unlock_Code.bin
to unlock and then
fastboot flash recovery recovery.img
for a recovery,
Then move SU to your sd card and flash it in recovery.
Then your all ready for the wire trick, The more you do these things the more experience you get at them and the better you get with fastboot. I suggest you go through the process opposed to just restoring (First off it's much much safer) and you'll know the ropes if you (or anyone else) has this problem.
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "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" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "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" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
The token and the unlock code are specific to the phone, And doesn't change until you get a new phone.
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "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" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
you can easily get a new token from htc dev web site
Sent from my HTC EVO 3D X515m using xda app-developers app
Can't_Live_Without_My_Evo said:
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
Click to expand...
Click to collapse
I know I use shooter_u, I asked because I've found another RUU which have "Rogers_WWE" in name of the file, and the rest of the file name is identical, and I remember that I had to choose "rogers" when I was unlocking via htcdev. That's why I wasn't 100% sure if I had to choose "HTC_Europe" or "Rogers_WWE".
Another thing which confuses me:
http://forum.xda-developers.com/showthread.php?t=1495358
mpgrimm2 said:
Note 3: If you previously did the HTC Unlock, you'd have to "RELOCK" BEFORE running the RUU.
To do this from fastboot type: fastboot oem lock
Click to expand...
Click to collapse
Should I do this or start directly with RUU.exe? My phone is currently "UNLOCKED, hboot 1.53.0007, s-on".
And what about CID? I've read somewhere that I have to change to supercid or something, to be able to flash zips via fastboot. How to check my current CID?
Search for cid getter on play store to get your cid
You certainly need to relock you hboot before running RUU. For the correct ruu you should check the box that your phone came in. It should have the details (atleast i think so)
P.S. you probably don't need to change cid. Infact i'd recommend you not to do that just yet
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
mars28 said:
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
Click to expand...
Click to collapse
I think yours might be an european model. i had the exact same cid as yours.
when you get to that step of corrupted hboot just follow the steps on this thread and flash hboot 1.49.0007
http://forum.xda-developers.com/showthread.php?t=1906172
Cant kive without my evis comments about the wire trick are bang on. It will fix everything. Having s-off is just much easier so do the wire trick. It will work. My wife and I both have an evo. I had to do the wire trick twice on hers for it to work and four times on mine for it to work. Be patient if it fails the first few times. And if the screen gets stuck on the jounuo whatever screen you can fix that.
If you are stuck at Juopunutbear screen and if you can go to bootloader you need to connect the phone to pc, go to fastboot ( should say fastboot usb)*Go to controlbear folder (from where you ran controlbear to begin withon you pc then open command window in it (hold shift and right click, that willopen command window rigjt there and then*when you get into it you need to enter:
"ControlBear.exe -f" no quotes or "ControlBear f" notice the space after the exe !
Lots of peopke forget to put it in and say it didnt work.
I presume this will fix the problem
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
My phone is now s-off. I didn't flash RUU, just restored stock rooted ROM from backup, did the wire trick (just one time, surprisingly) and everything went nice and smooth. Then I flashed hboot 1.49.0007 with no problems at all. Thanks guys for the tips.
One more thing - my phone state is now "LOCKED" - should I bother?
So I got what I wanted - I've installed ROM in BootManager (the one which doesn't boot before, while phone was 's-on') and this time it booted from SD. Today I'll try more ROMs in BootManager.
Locked doesn't matter as long as you are s-off. It only creates problems if you ever plan on using fastboot commands. Trust me, you dont need to bother with it
But if you really want to know heres a quote from ramjet where he explains it a bit.
ramjet73 said:
Once the RUU.exe is run and the stock bootloader is installed, the phone will be bootloader S-ON regardless of the radio S-OFF status. To run fastboot commands like "flash" and "erase" the stock bootloader needs to be unlocked by the htcdev method or a custom bootloader modified to support those commands needs to be flashed, which requires radio S-OFF.
Click to expand...
Click to collapse
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
This is going to be a short and simple guide for S-OFF users that want to update to the current RUU level or refresh their phone because they are having issues like being unable to boot certain ROM's. You will not lose S-OFF by flashing the RUU.
1. Do a nandroid backup of your current ROM if you want to restore it later.
2. Download the current version of the RUU for your phone in exe or zip format from this page.
3. Run the exe version of the RUU in Windows or the zip version as a PG86IMG.zip file through the bootloader. If using the bootloader method make sure the file is named exactly "PG86IMG.zip" and placed in the root of your SD card before starting the bootloader.
There is no need to unlock the bootloader before running it if you are S-OFF and there is troubleshooting information in this post if you have problems. It may be necessary to run the RUU twice if you have a custom bootloader installed when it is run the first time. If the utility hangs after flashing the bootloader from Windows just cancel it and restart.
I recommend downloading and installing the OTA(s) immediately after flashing the RUU to get the most current firmware while still 100% stock, but the OTA firmware update(s) can be downloaded as a separate PG86IMG.zip file if you forget or can't do that for some reason.
4. Flash a custom hboot using the instructions in this post. My recommendation for a good general purpose hboot is the JBear GB 1.50.5050 version unless you are running an ICS Sense ROM like stock or Cool ICS that requires an ICS bootloader (1.57.xxxx or 1.58.xxxx).
5. Connect your phone to a PC and start the bootloader in "fastboot USB " mode, then issue the following command to flash your favorite recovery:
fastboot flash recovery recovery.img (where "recovery.img" is the name of the recovery file in your ADB/fastboot directory)
6. Boot into recovery and restore a nandroid or flash another custom ROM. You may have to wipe cache+dalvik and restart recovery if you get any error messages from the recovery program.
That's it. You're now updated or re-synced with the current firmware, the hboot that meets your requirements and your favorite recovery.
Here are some additional links that might be helpful:
4EXT Recovery OP for the Evo 3D CDMA thread with a direct link to recovery.img in the download section (not the most current version)
Current TeamWin (TWRP2) touch recovery for the CDMA Evo 3d.
Virgin Mobile OTA firmware only in PG86IMG.zip format.
Sprint OTA firmware only in PG86IMG.zip format.
ramjet73
Thanks for this.
Question,the RUU links...
Am I looking for the link with the radio he has currently on his phone?
0.97.10.0530?
3volution said:
Thanks for this.
Question,the RUU links...
Am I looking for the link with the radio he has currently on his phone?
0.97.10.0530?
Click to expand...
Click to collapse
No. That's an older GB level and the most current RUU for the Evo 3D is the 2.89.651.2 ICS version. That's the one I recommend.
Since he is S-OFF already it's easy to revert to a GB RUU if neccessary.
ramjet73
I better not mess with it,lol
This isn't anything like flashing new ROM's on my phone.
Thanks though.
3volution said:
I better not mess with it,lol
This isn't anything like flashing new ROM's on my phone.
Thanks though.
Click to expand...
Click to collapse
You're welcome.
It's not really that difficult if you are familiar with rooting and flashing HTC devices but I can understand how it might be for users coming from other brands. Samsung in particular is definitely less complicated.
ramjet73
Thanks!
Thanks for this great post ramjet. Really a great concise How-to.
Nevermind, fixed.
ramjet73 said:
No. That's an older GB level and the most current RUU for the Evo 3D is the 2.89.651.2 ICS version. That's the one I recommend.
Since he is S-OFF already it's easy to revert to a GB RUU if neccessary.
ramjet73
Click to expand...
Click to collapse
I flashed the above RUU .exe and I'll get to 10%, then my phone reboots (RUU program says "attaining bootloader" or something) and go into a bootloop. Is there a specific hboot necessary to run this. I am on 1.04.200 and s-off, 1.09.00.706
I also tried updating via the bootloader method as well..... runs well....updates like four of the ten check offs and then bootloops as well.
Edit: turns out I was flashing the wrong version, oops
Hedied4me said:
I flashed the above RUU .exe and I'll get to 10%, then my phone reboots (RUU program says "attaining bootloader" or something) and go into a bootloop. Is there a specific hboot necessary to run this. I am on 1.04.200 and s-off, 1.09.00.706
Click to expand...
Click to collapse
From experience I've discovered that the RUU.exe utility will sometimes stop after flashing the stock bootloader if it is run with a custom hboot installed, which is why I put this comment in the OP:
If the utility hangs after flashing the bootloader from Windows just cancel it and restart.
Click to expand...
Click to collapse
I've had no problem completing the RUU.exe flash if I just cancel the utility in the Windows task manager and restart it.
Others have reported that re-flashing the RUU.zip file through the bootloader also works if the original flash is incomplete.
Also, make sure that you downgrade your hboot after flashing the RUU since the stock hboot won't boot GB or AOSP based ROM's.
ramjet73
Ok one more stupid question, after successfully flashing the correct RUU my phone boots into the stock virgin mobile. How do I get into bootloader (to flash OTA update and hboot) from here since holding power and volume down button from off no longer work.
Sent from my HTCEVOV4G using Tapatalk 2
Hedied4me said:
Ok one more stupid question, after successfully flashing the correct RUU my phone boots into the stock virgin mobile. How do I get into bootloader (to flash OTA update and hboot) from here since holding power and volume down button from off no longer work.
Click to expand...
Click to collapse
Try removing/replacing the battery and then use the Power+VolumeDown buttons together to enter the bootloader.
The stock ROM has the "fast boot" option turned on in the power settings by default and that will interfere if you try to enter the bootloader after powering down from the stock ROM.
ramjet73
Thank you very much for your patience and help Ramjet. Everything went well.
Sent from my Evo V 4G using Tapatalk 2
Please excuse me this might have been asked before.
I'm currently S-Off H-boot 1.40 but still on gingerbread firmware(2.17 radio 0.97.10.0530). also flashed to Boost Mobile. My question is if I run RUU to newest build will I lose boost mobile flash?
El Queson said:
Please excuse me this might have been asked before.
I'm currently S-Off H-boot 1.40 but still on gingerbread firmware(2.17 radio 0.97.10.0530). also flashed to Boost Mobile. My question is if I run RUU to newest build will I lose boost mobile flash?
Click to expand...
Click to collapse
I honestly don't know.
There is a post by a cricket user in my rooting and S-OFF guide that says the customization is not lost for that carrier but I've never used Boost and can't speak to that.
Perhaps another Boost user on these forums has experience with flashing the RUU.
ramjet73
++sorry++
Using the bootloader procedure is, by far, the easiest way of doing the RUU process that I've encountered. From custom ROM, to stock, back to a custom ROM in less than 45 minutes.
ramjet, thank you for your contributions to our platform.
so my wife is hboot 1.40, radio version 0.97.... running a GB ROM. I need to update her EVERYTHING(you pointed me here) and get her on NegaLite BluROM. I believe I will need to update her hboot as well. At what point in this process should that be done? Do I need to be worried that her current ROM is incompatible with either the new RUU or the new bootloader? And if it is, then I just work through it all in recovery?
Very useful thread, and thank you very much, by the way.
GAPO said:
so my wife is hboot 1.40, radio version 0.97.... running a GB ROM. I need to update her EVERYTHING(you pointed me here) and get her on NegaLite BluROM. I believe I will need to update her hboot as well. At what point in this process should that be done? Do I need to be worried that her current ROM is incompatible with either the new RUU or the new bootloader? And if it is, then I just work through it all in recovery?
Very useful thread, and thank you very much, by the way.
Click to expand...
Click to collapse
Is her phone S-OFF? If so, there is a link in the OP to a post that covers updating the hboot. If not, the only way to update the hboot is to flash a more current RUU.
ramjet73
ramjet73 said:
Is her phone S-OFF? If so, there is a link in the OP to a post that covers updating the hboot. If not, the only way to update the hboot is to flash a more current RUU.
ramjet73
Click to expand...
Click to collapse
Yes she is S-off. She also already has 4ext recovery installed.
Does this negate my need to flash recovery in the downloader?
Since she is S-off, this should be pretty easy.
I will still need to access the bootloader via Windows cmd, yes? Or can I accomplish all of this using only the handset?
Sent from my PG86100 using xda premium
---------- Post added at 07:07 PM ---------- Previous post was at 06:52 PM ----------
Her hboot is:
SHOOTER XC SHIP S-OFF RL
HBOOT-1.40.0000
RADIO-0.97.10.0530
eMMC-boot
Jun 8 2011, 17:20:22
Is this a custom hboot, or stock? I ask because of the caution on the OP regarding custom bootloaders. And I am not sure because I changed her bootloader a week or so ago and had to change it back.
Sent from my PG86100 using xda premium
GAPO said:
Is this a custom hboot, or stock? I ask because of the caution on the OP regarding custom bootloaders. And I am not sure because I changed her bootloader a week or so ago and had to change it back.
Click to expand...
Click to collapse
That's a stock hboot so you should be fine. You can still update using the RUU if a custom hboot is installed, but it might take a restart to complete after the stock hboot is installed.
ramjet73
Hey, I am trying to root my HTC evo 3d phone with hboot 1.58. I followed all 12 steps on htcdev.com, except on the final step I punch in: fastboot flash unlocktoken Unlock_code.bin and enter, then noting happens. The phone is supposed to reboot with the unlock option..but nothing happens
Also, the phone is Sprint CDMA if that makes any difference, so no sim card
....................................................................................................................................................................
THREAD SUMMARY
K finally got th phone rooted so here is what you have to do. The following applied to my ***locked*** S-ON Sprint HTC Evo3d with hboot 1.58 but should work with any other version higher than hboot 1.40.
The purpose is to get S-OFF(ROOT the phone) and also continue to use your factory HbOOT 1.58 and main version in the end.
1. Brick the phone carefully following steps outlined in unknownforce's [TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset). Scroll down to the "Downgrade/Unbrick" section and begin the bricking process with the PG86IMG.zip he mentions in "things you'll need".(place the zip on SD card in the main directory and name it PG86IMG)
2. Once phone is bricked(indicated by SOLID and very dimly lit charge light with the AC charger connected. Also the phone will not turn on or boot), download latest version of URT 3.1(first link in [TOOL] thread), continue to the second step 2 which involves booting up with Linux live boot CD on your PC, OR you can use URTLiveCD 1.0 and you will not need Linux
I did it the hard way an used latest version of URT with Ubuntu v12.04 LiveCD. I would recommend URTLiveCD 1.0 as you will boot straight to the tool and will not need the Ubuntu terminal.
3. After successfully completing downgrade with URT 3.1 downgrade, boot up to your new HBOOT 1.40 bootloader screen and enter fastboot USB mode. CHECK THAT THE MAIN VERSION HAS BEEN LOWERED ALONG WITH THE HBOOT.
Log back into windows
3.(A) If you haven't done this yet, get a fastboot PC command directory to retrieve all phone identification info from the bootloader. I used ROOTEVO3DNEW to check my phone's identity info at this point(though there are many programs that do the same thing). Create a new folder in C:\ and name it rootevo3dnew. Unzip all rootevo3dnew.zip contents into that folder.
Now open the command prompt with the phone connected to PC in fastboot USB. Type cd \rootevo3dnew and enter. Now type the following: "fastboot getvar all" (without quotations) and enter. A list should appear. Check that you have: (bootloader) version-main: 0.01.651.1. If this number is still 2.95.XXX.XXX or something close to it, then YOU MUST BRICK THE PHONE AGAIN. See posts starting at #35 of this thread for a more detailed guide through the second brick. It may be very tricky but very much the same process!!!!!
4. After successfully lowering HBoot to 1.40 and the main-version to 0.01.651.1 you can run the 1.13 RUU.exe found HERE: http://d-h.st/h1p . Connect the phone to fastboot USB and RUN the .exe....after the 1.13 .exe successfully runs, your main version should now be 1.13.651.7...again, checking using your rootevo3dnew tool from 3.(A) above....
5. REVOLUTIONARY S-OFF. Very simple, download for windows(or Linux) and fill in your info and retrieve you BETA key. Run REVOLUTIONARY application (which will run in the command prompt) and after successfully completely revolutionary S-off, YOU ARE ROOTED...continue to step 6
6. RESTORE your main version to 2.95(from 1.13) by running the 2.89 zip (HERE . Place this .zip in your main directory(RENAME IT PG86IMG) on the SD card and let it unzip and install it from the bootloader.
After that, you are pretty much finished!! boot up to android(main version 2.89) and let system updates detect and bring you back to 2.95.xxx.xxx..
....
Download and Install a custom recovery. Rename that .zip PG86IMG and install from bootloader as you did with the 2.89 zip. Now you have a custom recovery where you can backup and restore, install ROMS or other software without having to rename it PG86IMG every time, wipe partitions and lots of other stuff...
Now, download this and place it on your SD main directory. Then, using your new recovery(by selecting "recovery" in bootloader menu), select "install from sdcard" and "choose zip from sdcard", select the SuperSU zip and let it install. Reboot, get to homepage, and install SuperSU from the play store. You now hae an administrative super APP that will let you choose which apps are given root access.
Custom ROMS can be installed the same way from the custom recovery. I am currently using Negalite BluRom and loving it
...
THE 6 STEPS OUTLINED HERE PRETTY MUCH COVER EVERYTHING FROM THIS THREAD
HUGE THANKS TO USERS MPGRIMM2 AND BRIAN706 FOR NEARLY 3 DAYS OF HARD WORK !!
Did you get your motherboard replaced at some point of time?
Can't think of a good sig
donkeykong1 said:
Did you get your motherboard replaced at some point of time?
Can't think of a good sig
Click to expand...
Click to collapse
My what? Yes I swapped out my 67370m dv6 pavilion mainboard for radeon HD 6550m graphics chipset. How did you know?
otto325 said:
My what? Yes I swapped out my 67370m dv6 pavilion mainboard for radeon HD 6550m graphics chipset. How did you know?
Click to expand...
Click to collapse
On the phone?
Can't think of a good sig
donkeykong1 said:
On the phone?
Can't think of a good sig
Click to expand...
Click to collapse
Oh ok, what the hell..No, I just got the phone on ebay for $30, currently locked and I am trying to root it. Some Brittney girl owned according to phone identity info left on the phone
Do I need to downgrade the hboot from 1.58 to 1.4? Sorry I'm really new to smartphones, any help is really appreciated
Just in case it was missed, the phone doesn't reboot upon flashing the unlock token. A prompt should appear on the device and you have to confirm the bootloader unlock.
He asked about the motherboard, because there is an issue if the motherboard has been swapped; sometimes the bootloader will not unlock. I think it's due to mismatched firmware.
Usually running the RUU will solve the issue.
You can download a copy here: https://copy.com/jF1Mm
The only problem is, if the phone had taken the latest Ota update and you are on main version 2.95 instead of 2.89, the RUU will not run because it won't let you downgrade.
You can also check your main version by running a fastboot getvar all.
Is there any chance your device is already s-off from a previous owner? It will say s-on or s-off on the bootloader screen.
If you're lucky enough to already have s-off, you can skip the bootloader unlock altogether.
Brian706 said:
Just in case it was missed, the phone doesn't reboot upon flashing the unlock token. A prompt should appear on the device and you have to confirm the bootloader unlock.
He asked about the motherboard, because there is an issue if the motherboard has been swapped; sometimes the bootloader will not unlock. I think it's due to mismatched firmware.
Usually running the RUU will solve the issue.
You can download a copy here: https://copy.com/jF1Mm
The only problem is, if the phone had taken the latest Ota update and you are on main version 2.95 instead of 2.89, the RUU will not run because it won't let you downgrade.
You can also check your main version by running a fastboot getvar all.
Is there any chance your device is already s-off from a previous owner? It will say s-on or s-off on the bootloader screen.
If you're lucky enough to already have s-off, you can skip the bootloader unlock altogether.
Click to expand...
Click to collapse
THANKS
main version 2.95.651.5. If I factory reset the phone and discard updates, will the main version reset to 2.89 making the RUU possible?
EDIT: factory reset and no updates did not bring main version down to 2.89
***LOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012, 15:06:44
Also check most recent post (#508) in the guide thread.
http://forum.xda-developers.com/showthread.php?t=1889438&page=51
Factory reset won't affect your main version
As DK mentioned, a factory reset only resets your current build. It would only take you back to the point of the last OTA update.
Unfortunately, you can't lower the mainversion without the bootloader unlocked, so it's a catch 22 there.
As a long shot, you might look into the new towelroot, thought I really don't think it will work for this phone because HTC locks down the /system partition. It would at least be worth looking in to.
As far as the hboot downgrade method (I assume you mean THIS) it was intended to downgrade from 1.50 Gingerbread to 1.40 Gingerbread. I have no idea if it will work to downgrade from 1.58 ICS?? You might want to ask around a little about that.
Okay... I just saw your posts in the other thread, have you actually received the unlock token from HTC?
IE, you received a file via email named Unlock_Code.bin that you placed in your fastboot directory and then typed the command: fastboot flash unlocktoken Unlock_code.bin ??
Also, when you say nothing happens after running the command, something must happen whether it's the intended results or not. Can you tell us what the command prompt returns after running the command? Maybe just copy/paste it here.
There will either be an error or a confirmation after running the command.
Comes up as successful on the command prompt. But the phone does not reboot or direct to the unlock screen. I just remains on the fastboot USB screen and does nothing.
C:\rootevo3dnew>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.153s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.163s
Thanks for that... That's a bummer. Looks to me like you have the motherboard swap issue. It really sucks that you can't RUU.
It looks like someone answered the question in the other thread though about the hboot downgrade method.
So I got the HBOOT downgrade(0.8.2) boot for a disk but it says the phone needs to be bricked before the downgrade..
That's where I'm at now basically, I'm going to do a little more reading on bricking...
Also would be good to have confirmed that this downgrade will work starting with hboot 1.58, so I don't mess anything up
mpgrimm2 may have found found his way over here from from the [Guide] thread
Also I hope I am downloading the correct RUU's. I had to fish them from various searches because the link supplied in Unknownforce's thread is invalid:
2.17 RUU:
http://d-h.st/ru0ow8ps0i01/PG86IMG_2.17.651.5.zip
1.13 RUU:
http://d-h.st/Xrp
mpgrimm2 said:
Well. Post that in Unknownforce's Ultimate Recovery Tool thread so you are not "off topic" here.
I haven't used the Evo3d in a while but you should probably look over my ...
Post 781 in Unknownforce's thread and the follow up posts right after.
Additional info you may need from my
[Guide]My Hboot 1.5x HTC Unlock/recovery/rom/kernel flashing notes 2-13-13
and
Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself)
Click to expand...
Click to collapse
Fyi, I think Unknownforce indicated in one of his first 3 posts that u can brick with the last 2.95 PG86IMG.zip file he linked and then downgrade to 1.13 for s-off. Have to go check...
Keep in mind that you may want to considering posting any issues with the URT/Downgrade tool in Unknownforce's thread if you want any chance of assistance from him.
Bad link in his op but this post has it...
Unknownforce said:
Well, with the 2.95 OTA, they included the HBOOT in the firmware, so it's now much faster of a load time for PG86IMG when doing the brick.
I pulled the new PG86IMG.zip from the OTA update, and it's only 19MB, which takes only 15-20 seconds to fully load and be ready to press volume up to update... this will significantly cut down on the time it takes to downgrade, as you can re-try over and over very quickly now.
Here's the PG86IMG file -> http://d-h.st/3p8
Click to expand...
Click to collapse
And just as a reference for you later I will quote myself from Ramjet73's 2.95 ota update thread
mpgrimm2 said:
ramjet73 and others. I see we still don't have any source for the 2.95.651.6 RUU's. Since I just went ahead and reset my 2 Evo3d's back to stock/S-off as a backup here are the files I had to step through if you want to add or host them directly:
- PG86IMG 2.89.651.2.zip - 449.18 MB
Full RUU.zip for use in bootloader (rename to PG86IMG.zip & place on /sdcard)
- OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.5-2.89.651.2_release_307948lagg6bmccb9c63ip.zip - 51.11 MB
2.89.651.2 update to 2.95.651.5 zip for use in bootloader (rename PG86IMG.zip & place on /sdcard ) or stock recovery (place in /sdcard/download )
This is the last official update that just downloaded to my phone after the other Ruu's/updates that were posted previously
- OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.6-2.95.651.5_release_315505rm3j000awvlstw9z.zip - 10.59 MB
2.95.651.5 update to 2.95.651.6 zip for use in bootloader (rename PG86IMG.zip & place on /sdcard ) or stock recovery (place in /sdcard/download )
Wish someone with HTC/Sprint access would post up the latest full RUU. It was a bit of a pain stepping through the updates, but definitely easier being s-Off. Seems that if someone is S-On with the 2.95.651.6 update and can't get past step 13 of the HTC Unlock or needs to RUU back, their only option is Unknownforce's Hboot Downgrade Ultimate Toolkit and "Brick it Twice" to get back to an earlier version for Revolutionary S-Off and then go through the updates from 2.89 on up.
Hope this helps others.
EDIT:
I may be too tired at the moment to figure this out, but for some darn reason both the official OTA Updates would not flash from the bootloader on a stock 2.89.651.2 phone with S-Off (both phones actually). Didn't matter if it was renamed PG86IMG.zip or left as officially downloaded to sdcard/download and booting into the stock recovery. The MD5 of my 651.5 update file matches Ramjet73's as well. But If I connect to wifi, do a system update, let it download (how I got the files) and reboot automatically, it works fine and updates without issue.
Click to expand...
Click to collapse
Forgive me for being such a noob with this stuff.
I'm reading about hboot 1.58 needing to be bricked twice to be able to run the 1.13 RUU.
So to start, do I place the 18.7mb PG86IMG .zip (from the second quote in your last post) in the "download" folder of the sd card?
The stock
(OTA_Shooter_ICS_35_S_Sprint_WWE_2.95.651.6-2.95.651.5_release_315505rm3j000awvlstw9z)
Click to expand...
Click to collapse
is there, so do I remove that one and replace it?
I don't think so but just to be sure, I drop the 18.7 PG86IMG zip folder in downloads and begin the brick process, then run the hboot 0.8.2 to downgrade?
*EDIT* ok, place in the MAIN directory. It's working and is unloading the .zip in bootloader
I need a new data sync cable, mine has started intermittently losing connection off and on...going to wait until I have a new one before I go any further.
Also, the latest version of ubuntu that Linux offers did not work. I found an earlier version(12.04) and the boot disk works so I am good to go on that
What is Hboot 0.8.2 ? Are you using Unknownforce's URT 3.1 Tool and following the "Downgrade/Unbrick" section?
This one:
http://forum.xda-developers.com/showthread.php?t=1563342
Yep, that is an outdated/earlier version. You need to use the Ultimate Recovery Tool from Unknownforce's thread as I linked earlier (URT v3.1) and use the LiveCd link.
see here
Sent from my "Up All Night Sleep All Day" Nexus 5!
THANKS
Well I just did a dry run with the Linux boot disk and terminal. Extracted downgrade.zip to HOME folder, ran the commands. I'm getting the correct code returns in the terminal. I got up to the:
Code:
Step 1... Plug in Device while holding down Volume Down key...
Waiting for device...
Just a matter of getting a new data sync cable now and I can do this...
Again thanks for your help, I'm pretty new to this process I've never altered a devices firmware manually before so it's an awesome experience as well..
Will report back in a couple days, hopefully with a newly rooted phone
--------
Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?
otto325 said:
Also, do you have a direct link to the correct 1.13 RUU EXE to run after the downgrade?
Click to expand...
Click to collapse
Yep. Previously...
mpgrimm2 said:
....
Additional info you may need from my
[Guide]My Hboot 1.5x HTC Unlock/recovery/rom/kernel flashing notes 2-13-13
and
Post 11. My Gathered RUU .exe/.zip Links (& How to extract RUU zip yourself) <<<--- HERE
Click to expand...
Click to collapse
Sent from my "Up All Night Sleep All Day" Nexus 5!