[RADIO] HTC Evo 3D (GSM) Radios [PG86IMG.zip] (Updated: 20 Oct 2011) - HTC EVO 3D

These radios are for the GSM HTC Evo 3D (e.g. Vodaphone).
Do NOT flash these radios on a CDMA HTC EVO 3D!​
Code:
/* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or the end of the world. Please do some research
* if you have any concerns about flashing a radio before flashing it!
* YOU are choosing to make these modifications, and if you point the
* finger at me for messing up your device, I will laugh at you. */
How to Flash:
In order for this to work, the HTC Evo 3D needs to be S-OFF. Flashing the radio with a corrupt file or interrupting the flash, can brick the device, please proceed with caution.
Download the your choice of radio for the HTC Evo 3D.
Make sure the filename is PG86IMG.zip exactly or it will not work and copy it to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the HTC Evo 3D to the computer via USB.
On the computer, open terminal and run the following commands:
Code:
adb push PG86IMG.zip /sdcard/PG86IMG.zip
adb shell md5sum /sdcard/PG86IMG.zip
NOTE: The md5 should match up the provide the original download location. If not, redownload & try again.
Code:
adb reboot bootloader
The HTC Evo 3D will reboot & usually boot into fastboot. Pressing the Power button will put the device into the bootloader.
The bootloader will scan for the radio update. Once it finds the update, select Yes.
Allow the bootloader to finish flashing the updated radio, and reboot the HTC Evo 3D normally.
Downloads:
From Gingerbread-based RUUs:
From the 1.20.401.2 RUU:
10.53.9020.00_10.13.9020.08_2
md5: ab817b2ee368c028a1725e7fe6a11b7a
From the 1.20.401.8 RUU:
10.59.9020.00_10.15.9020.06
md5: 4736366057b45ed472d80fe6cf054492
From the 1.20.468.2 RUU:
has the same radio as the 1.20.401.2 RUU
From the 1.20.631.2 RUU:
has the same radio as the 1.20.401.2 RUU
From the 1.21.161.1 RUU:
has the same radio as the 1.20.401.2 RUU
From the 1.21.163.1 RUU:
has the same radio as the 1.20.401.2 RUU
From the 1.21.166.1 RUU:
has the same radio as the 1.20.401.2 RUU
From the 1.21.183.1 RUU:
has the same radio as the 1.20.401.2 RUU
From the 1.22.707.2 RUU:
10.55.9020.00_10.13.9020.29
md5: 227f01bb2be5057a62ba2fa3e65a8237
From the 1.22.708.4 RUU:
has the same radio as the 1.22.707.2 RUU
From the 1.22.720.1 RUU:
10.54.9020.00_10.13.9020.20
md5: d8891b6e8fc2f7adb310ec482686eb1f
From the 1.23.921.5 RUU:
has the same radio as the 1.22.707.2 RUU

Revolutionary just pushed it's tool for unlocking the bootloader.
'fastboot flash radio radio.img' should make it now.

problem
I just rooted my evo 3d and forgot to back it up and something went wrong and all i could get into was recovery mode. so i managed to install virtuous rom, then i tried high rom but i cannot get 3g or and data connection anymore.
I think it is because im using a rogers evo 3d and the roms are not compatible.
can i use these radios to restore my data connecting.

akira8473 said:
I just rooted my evo 3d and forgot to back it up and something went wrong and all i could get into was recovery mode. so i managed to install virtuous rom, then i tried high rom but i cannot get 3g or and data connection anymore.
I think it is because im using a rogers evo 3d and the roms are not compatible.
can i use these radios to restore my data connecting.
Click to expand...
Click to collapse
I think I the same issue as you, this morning. Do you have no cell service at all? I eventually re-downloaded virtuous, and re-installed the ROM, and all was good. I think I had a corrupt download.

froesei said:
I think I the same issue as you, this morning. Do you have no cell service at all? I eventually re-downloaded virtuous, and re-installed the ROM, and all was good. I think I had a corrupt download.
Click to expand...
Click to collapse
i just get no data coverage, 2g works, but 3g and 4g dont.

faithcry said:
i just get no data coverage, 2g works, but 3g and 4g dont.
Click to expand...
Click to collapse
apn settings man!!!!!!!

Flashmaniac said:
Revolutionary just pushed it's tool for unlocking the bootloader.
'fastboot flash radio radio.img' should make it now.
Click to expand...
Click to collapse
I tested and it works good !
I confirm that there is no problem like with my DHD.

Updated OP with the 10.54.9020.00_10.13.9020.20 radio from the 1.22.720.1 RUU.

gu1dry said:
Updated OP with the 10.54.9020.00_10.13.9020.20 radio from the 1.22.720.1 RUU.
Click to expand...
Click to collapse
which radio would you recommand matey?

Radio
I just flashed the way I did with my DHD..
Extracted the radio image into a folder on the desktop.
Cd'd into the directory from CMD, Rebooted the device into bootloader so;
C:\Users\Dan\Desktop\Radio>adb reboot bootloader
Waited for it to go into the Bootloader..
C:\Users\Dan\Desktop\Radio>fastboot flash radio radio.img
< waiting for device >
sending 'radio' (22141 KB)...
OKAY [ 3.341s]
writing 'radio'...
OKAY [ 2.778s]
finished. total time: 6.124s
C:\Users\Dan\Desktop\Radio>fastboot reboot
rebooting...
finished. total time: 0.988s
C:\Users\Dan\Desktop\Radio>
Worked fine, Always found this much easier than faffing around with moving stuff onto SD cards - all done from your PC then, You could probs even batch file it if you trusted it enough

Can anyone with the Rogers device confirm if any of these newer radios work?

Total noob question here but what exactly is this file for?
Sent from my HTC EVO 3D X515m using XDA App

Its the Radios of the device.
Newer version can improve operator connection, Wifi, Bluetooth etc.
Can also improve batteri life
It has everything to do with Radio connection.

Where can we find the correct RIL files for the radios???
Thanx

gu1dry said:
These radios are for the GSM HTC Evo 3D (e.g. Vodaphone).
Do NOT flash these radios on a CDMA HTC EVO 3D!​
Code:
/* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or the end of the world. Please do some research
* if you have any concerns about flashing a radio before flashing it!
* YOU are choosing to make these modifications, and if you point the
* finger at me for messing up your device, I will laugh at you. */
How to Flash:
In order for this to work, the HTC Evo 3D needs to be S-OFF. Flashing the radio with a corrupt file or interrupting the flash, can brick the device, please proceed with caution.
Download the your choice of radio for the HTC Evo 3D.
Make sure the filename is PG86IMG.zip exactly or it will not work and copy it to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the HTC Evo 3D to the computer via USB.
On the computer, open terminal and run the following commands:
Code:
adb push PG86IMG.zip /sdcard/PG86IMG.zip
adb shell md5sum /sdcard/PG86IMG.zip
NOTE: The md5 should match up the provide the original download location. If not, redownload & try again.
Code:
adb reboot bootloader
The HTC Evo 3D will reboot & usually boot into fastboot. Pressing the Power button will put the device into the bootloader.
The bootloader will scan for the radio update. Once it finds the update, select Yes.
Allow the bootloader to finish flashing the updated radio, and reboot the HTC Evo 3D normally.
Downloads:
From Gingerbread-based RUUs:
From the 1.20.401.2 RUU:
10.53.9020.00_10.13.9020.08_2
md5: ab817b2ee368c028a1725e7fe6a11b7a
From the 1.20.468.2 RUU:
has the same radio as the 1.20.401.2 RUU
From the 1.20.631.2 RUU:
has the same radio as the 1.20.401.2 RUU
From the 1.21.161.1 RUU:
has the same radio as the 1.20.401.2 RUU
From the 1.21.163.1 RUU:
has the same radio as the 1.20.401.2 RUU
From the 1.21.166.1 RUU:
has the same radio as the 1.20.401.2 RUU
From the 1.21.183.1 RUU:
has the same radio as the 1.20.401.2 RUU
From the 1.22.707.2 RUU:
10.55.9020.00_10.13.9020.29
md5: 227f01bb2be5057a62ba2fa3e65a8237
From the 1.22.708.4 RUU:
has the same radio as the 1.22.707.2 RUU
From the 1.22.720.1 RUU:
10.54.9020.00_10.13.9020.20
md5: d8891b6e8fc2f7adb310ec482686eb1f
From the 1.23.921.5 RUU:
has the same radio as the 1.22.707.2 RUU
Click to expand...
Click to collapse
Good day, I just bought an evo 3D here in France under SFR network. my baseband is
10.53.9020.00U_10.13.9020.08_2M
Please help me what radios do you recommend to update it?

adrain said:
Good day, I just bought an evo 3D here in France under SFR network. my baseband is
10.53.9020.00U_10.13.9020.08_2M
Please help me what radios do you recommend to update it?
Click to expand...
Click to collapse
Stay with this radio, I tried all the others and there is nothing better.
"Garde la, j'ai essayé toutes les autres et il n'y a pas d'améliorations dans celles là"

Kroutnuk said:
Stay with this radio, I tried all the others and there is nothing better.
"Garde la, j'ai essayé toutes les autres et il n'y a pas d'améliorations dans celles là"
Click to expand...
Click to collapse
could you provide it to us?
since its not in the first post.

Flashmaniac said:
could you provide it to us?
since its not in the first post.
Click to expand...
Click to collapse
All are in the first post.

It always says "wrong zipped file" when i try to flash...I downloaded normally and it is also on the root of my sd card but its not working. Could it depend on my sd card also?

RobbyTouchHD said:
It always says "wrong zipped file" when i try to flash...I downloaded normally and it is also on the root of my sd card but its not working. Could it depend on my sd card also?
Click to expand...
Click to collapse
Tried a different sd card...sitll says "wrong zipped file"

Related

[RADIO] HTC Evo 3D (CDMA) Radios [PG86IMG.zip] (Updated: 31 July 2012)

These radios are for the CDMA HTC Evo 3D (e.g. Sprint).
Do NOT flash these radios on a GSM HTC EVO 3D!​
Code:
/* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or the end of the world. Please do some research
* if you have any concerns about flashing a radio before flashing it!
* YOU are choosing to make these modifications, and if you point the
* finger at me for messing up your device, I will laugh at you. */
How to Flash:
In order for this to work, the HTC Evo 3D needs to be S-OFF. Flashing the radio with a corrupt file or interrupting the flash, can brick the device, please proceed with caution.
Download the your choice of radio for the HTC Evo 3D.
Make sure the filename is PG86IMG.zip exactly or it will not work and copy it to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the HTC Evo 3D to the computer via USB.
On the computer, open terminal and run the following commands:
Code:
adb push PG86IMG.zip /sdcard/PG86IMG.zip
adb shell md5sum /sdcard/PG86IMG.zip
NOTE: The md5 should match up the provide the original download location. If not, redownload & try again.
Code:
adb reboot bootloader
The HTC Evo 3D will reboot & usually boot into fastboot. Pressing the Power button will put the device into the bootloader.
The bootloader will scan for the radio update. Once it finds the update, select Yes.
Allow the bootloader to finish flashing the updated radio, and reboot the HTC Evo 3D normally.
Downloads:
From Gingerbread-based RUUs:
From the 1.07.651.1 RUU:
CDMA: 0.97.00.0513
md5: fdec2ed4be3b35a9b190da8085dc8a0d
WiMax: no WiMax radio was included in this leak
From the 1.11.651.2 RUU (Stock):
CDMA: 0.97.00.0518
md5: 5f6f35dedf37921438b056db8590ff1e
WiMax: 28735
md5: 78c03fb844b7761d0d6611bf7e8b3791
From the 1.13.651.7 OTA/RUU:
CDMA: 0.97.10.0530
md5: 0ab6aeb4ca9421d5ea8e9ced722554bc
WiMax: 29047
md5: 3123a4a3654cf5d22228117258702b21
From the 2.08.651.2 OTA:
CDMA: 0.97.10.0808
md5: a8acc161e58d3e2d3d1cd4954975802b
WiMax: contains the same WiMax radio from the 1.13.651.7 OTA/RUU
From the 2.17.651.5 OTA:
CDMA: 1.06.00.1216
md5: 84cd45b311bb176457cd32e45839529a
WiMax: no WiMax radio was included in this OTA
From Ice Cream Sandwich-based RUUs:
From the 2.89.651.2 OTA:
CDMA: 1.09.00.0706
md5: 3fa00b5e3e8b9bcdbe3e325e8609dbfa
WiMax: no WiMax radio was included in this OTA
gu1dry said:
Downloads:
From Gingerbread-based RUUs:
From the 1.07.651.1 RUU:
Radio: 0.97.00.0513
md5: fdec2ed4be3b35a9b190da8085dc8a0d
WiMax: no WiMax radio was included in this leak
From the 1.11.651.2 RUU (Stock):
Radio: 0.97.00.0518
md5: 5f6f35dedf37921438b056db8590ff1e
WiMax: 28735
md5: 78c03fb844b7761d0d6611bf7e8b3791
From the 1.13.651.7 OTA/RUU:
Radio: 0.97.10.0530
md5: 0ab6aeb4ca9421d5ea8e9ced722554bc
WiMax: 29047
md5: 3123a4a3654cf5d22228117258702b21
​
Click to expand...
Click to collapse
Awesome, thanks for taking the time to gather this.​
I like 4G... Got a 2 bar 4G signal as I write this. :-(
Sent from my PG86100 using Tapatalk
As a quick FYI, if your WiMAX fails to start after you update, don't say I didn't experience this
Currently in the process of checking if it is due to updating the WiMAX partition, or since I am still running the OS from before the OTA.
Full flash of the new software revision fixed the WiMAX issue.
So, does any of the latest radios (Im still on .0513) offer a significant increase in signal? My signal at my house is CRAP, and I already have an Airave for my mom's house, so I cant contact Sprint and request another one. This is actually one of the MAIN reasons for me wanting root, so we could flash newer (and potentially better) radios (seeing that a better radio will help with any battery issue also).
Thank you. Will update this to my thread when I get on a computer.
http://forum.xda-developers.com/showthread.php?t=1192661
Just and idea, but how about adding a date beside the radio's to show when they were updated.
So if your on .530 already this is pointless to do right?
Question
- what file do I flash first the winmax or the radio?
- can i grab the file and place them o. My SD card and flash VIA recovery?
- can i back up my current status (radio and winmax ) incase something goes wrong I can revert back?
I have hboot 1.40 and radio .518 don't know the winmax s-off cwm recovery and stock ROM with super user if it helps.
southern87 said:
So if your on .530 already this is pointless to do right?
Click to expand...
Click to collapse
Yup, no need to reflash if your already on it.
Thanks for posting. I'm still on 518 and have no issues. Anyone who has upgraded to 530 notice a difference?
vWvSTATICvWv said:
Thanks for posting. I'm still on 518 and have no issues. Anyone who has upgraded to 530 notice a difference?
Click to expand...
Click to collapse
Is your WIMAX working?
since I did the s-off my 3g has been real bad. Is this known issue?
alammori said:
Is your WIMAX working?
Click to expand...
Click to collapse
Yea...WiMax is fine. It's been shoddy in my neighborhood but it's great everywhere else I've tried.
So has anyone bumped up to the latest radio? I'm already on current wimax, but my radio version is the one it seems everyone else is on. I'm also skeptical that they're in named PG56IMG.zip, and shooter's supposed to be PG86IMG.zip... any clues? Has anyone done this and verified that everything is still operating? Radio was a huge part of S-OFF, so I'm quite leary to flash the latest...
Also, has anyone worked on pulling NV/PRI? Those will most likely exist inside all of the RUUs/OTAs mentioned.. I know it's early to dig into this type of stuff at all, but I'm sure someone has been daring enough to test the latest radio
myndwire said:
So has anyone bumped up to the latest radio? I'm already on current wimax, but my radio version is the one it seems everyone else is on. I'm also skeptical that they're in named PG56IMG.zip, and shooter's supposed to be PG86IMG.zip... any clues? Has anyone done this and verified that everything is still operating? Radio was a huge part of S-OFF, so I'm quite leary to flash the latest...
Click to expand...
Click to collapse
The reason the files was named PG56IMG was due to a minor mistake on my part. The file is valid, just a brainfart moment from working a 8h shift thru the night.
myndwire said:
Also, has anyone worked on pulling NV/PRI? Those will most likely exist inside all of the RUUs/OTAs mentioned.. I know it's early to dig into this type of stuff at all, but I'm sure someone has been daring enough to test the latest radio
Click to expand...
Click to collapse
If you tell me which images they are I'll pull them & setup the zips, but the Evo 3D's naming convention for those images is different from past "Evo" devices.
myndwire said:
So has anyone bumped up to the latest radio? I'm already on current wimax, but my radio version is the one it seems everyone else is on. I'm also skeptical that they're in named PG56IMG.zip, and shooter's supposed to be PG86IMG.zip... any clues? Has anyone done this and verified that everything is still operating? Radio was a huge part of S-OFF, so I'm quite leary to flash the latest...
Also, has anyone worked on pulling NV/PRI? Those will most likely exist inside all of the RUUs/OTAs mentioned.. I know it's early to dig into this type of stuff at all, but I'm sure someone has been daring enough to test the latest radio
Click to expand...
Click to collapse
Flashed the latest wimax and radio (and yes I changed the name tp PG86IMG.zip) and still have s-off, root and no brick. All is well.
Can't say it made any real difference, but typically radios don't so I'm not surprised.
myndwire said:
So has anyone bumped up to the latest radio? I'm already on current wimax, but my radio version is the one it seems everyone else is on. I'm also skeptical that they're in named PG56IMG.zip, and shooter's supposed to be PG86IMG.zip... any clues? Has anyone done this and verified that everything is still operating? Radio was a huge part of S-OFF, so I'm quite leary to flash the latest...
Also, has anyone worked on pulling NV/PRI? Those will most likely exist inside all of the RUUs/OTAs mentioned.. I know it's early to dig into this type of stuff at all, but I'm sure someone has been daring enough to test the latest radio
Click to expand...
Click to collapse
i flashed both of them everything is fine im guessin the newest ones were the bottom ones?
smw6180 said:
Flashed the latest wimax and radio (and yes I changed the name tp PG86IMG.zip) and still have s-off, root and no brick. All is well.
Can't say it made any real difference, but typically radios don't so I'm not surprised.
Click to expand...
Click to collapse
Same here, worked perfect! thanks OP
I may have working update.zips that are flashable via recovery, but I need someone to test it. Join me on Freenode #cm-wiki if you would like to help with testing.

Unable to use Mobile Network on HTC Amaze w/ Revolution HD ROM

Hello XDA,
I need some help getting mobile network to function on my HTC Amaze 4G. I am on the Mobilicity network and have S-OFF, SuperCID, and the Android Revolution HD ROM.
I was told to install radio.img for android revolution hd. I have attempted, but when I type "fastboot flash radio radio.img" into command prompt it fails, and does not install (It says: "Failed: remote not allowed").
Wi-fi works, and as far as I can tell, Bluetooth does too.
I need to know how to fix this, mobile network is important to me. Thank you ahead of time!
Robert
(moved from Android Q & A)
SOLVED
I needed to update the APN (Access Point Name). A quick google search will turn up the settings on Howard Forums.
Thanks everyone for your help!
APNs needs to be added.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Not quite, to flash the radio.img, you need to change your boot image, download the ENG hboot, rename it to PH85IMG and flash via hboot, retry fastboot flashing the radio.img after that, should be fine, SHP hboot doesn't allow fastboot commands like flashing, sadly.
you don't need the radio, just set up your apn. Look in the general section for apn settings
What's not working really? Mobile network or just data?
Dark Nightmare said:
Not quite, to flash the radio.img, you need to change your boot image, download the ENG hboot, rename it to PH85IMG and flash via hboot, retry fastboot flashing the radio.img after that, should be fine, SHP hboot doesn't allow fastboot commands like flashing, sadly.
Click to expand...
Click to collapse
I've already flashed PH85IMG, but I'm not sure what ENG hboot is, could you explain that please? Thanks.
Dark Nightmare said:
What's not working really? Mobile network or just data?
Click to expand...
Click to collapse
Just mobile network.
Thanks.
Trewyy said:
I've already flashed PH85IMG, but I'm not sure what ENG hboot is, could you explain that please? Thanks.
Just mobile network.
Thanks.
Click to expand...
Click to collapse
So you basically have no service?
This is ENG hboot: http://forum.xda-developers.com/attachment.php?attachmentid=1023388&d=1335318318
Try flashing the radio after installing that, follow directions according to the rom thread on how to flash. That bootloader allows fastboot commands.
Flash the eng hboot via bootloader, just rename the file PH85IMG and you know the rest.
Dark Nightmare said:
So you basically have no service?
This is ENG hboot: http://forum.xda-developers.com/attachment.php?attachmentid=1023388&d=1335318318
Try flashing the radio after installing that, follow directions according to the rom thread on how to flash. That bootloader allows fastboot commands.
Flash the eng hboot via bootloader, just rename the file PH85IMG and you know the rest.
Click to expand...
Click to collapse
Sorry, I should have been more clear in my original post. Voice and sms are working, just not mobile data.
Anyways, the other's were right, it was the APN. A quick google search turned up the settings for the APN.
Thanks for everyone's help!
Robert

Need some questions answered about Team Venom's Viper3D Rom/JBear H-Boot Issues

Running Viper3D 1.0.0 Nightly on my Evo, I think I updated it in August or September last. I know they push light updates here and there that add new features or bug fixes, but lately I haven't been able to acquire a recent update. I went to the infectedrom forum where the Viper3D is posted and when I click the Nightly folder on androidfilehost there are about 8-10 posts. Now at the beginning of the posts they say like Oct 12, Oct 15, Oct 19, etc. But they also have a 88kb zipmd5 file below each 600+mb zip file which confuses me. Before androidfilehost changed, it just had one specific file that you download, flash, and done. But I tried to open the .zip file and the zipmd5 file and it comes back with error (bad). I'm using 4ext testing rc by the way.
Also, I recently s-offed using JBear (don't know how to spell it off hand) using the wire trick and installed the custom JBear hboot and for some reason when I place a PG86IMG.zip on the root of my SD card and boot into fastboot, it says "CID Incorrect update failed" for some reason.
If anyone can give me a pointer as to what I'm doing wrong or to what I need to do, please take the time and tell me. Much appreciated. Thank you.
if you look closely you'll see that the files on androidfilehot have a particular revision number too. the latest right now is r202. so it would look something like this "Viper3D_19Oct12_0656_r202_s.zip". theres no need to download the md5 zip.
people get corrupted zips mostly because they use IDM to dl. I'd suggest you dl from your browser (chrome or firefox)
As for the PG86IMG issue i'm not sure. If you are a gsm user you should downgrade to 1.49 using this method: http://forum.xda-developers.com/showthread.php?t=1906172
Hey guys, what's up? I'm also running viper 3d on sprint with the latest radios s-off. In the latest update r202 in the settings, the system update option is missing. Along with firmware, data profile, and prl update are missing too. The last update r192 had them but not the new one. I reflashed the Rom a few times and still the same thing. Does anybody know what files and apks are missing and how I can implement them into the Rom to make it work again?
Okay thank you very much for clearing that up for me. before androidfilehost changed I used to download them from my phone using Dolphin Browser and they seemed to flash fine... Until now. I downloaded the latest and when it got to 633mb it said download failed. What is IDM or whatever you mentioned? Also, what's with the zipmd5 files then?
I'm using the Virgin Mobile Evo V. (CDMA) hboot 1.57. I think it might have something to do with JBear's custom hboot, but then again I could be wrong.
TheKnux said:
I'm using the Virgin Mobile Evo V. (CDMA) hboot 1.57. I think it might have something to do with JBear's custom hboot, but then again I could be wrong.
Click to expand...
Click to collapse
That is important information. Since you have an Evo V instead of the Sprint model, the CID in the android-info.txt file that's included in the PG86IMG.zip files intended for that phone is SPCS_002 instead of SPCS_001. There is a note regarding this on the OP of the Viper 3D ROM thread.
Changing that will allow you to flash the PG86IMG.zip, but be very careful since flashing files intended for other phones can cause serious problems.
You might want to review this thread to see how other people with the Evo V have handled it.
ramjet73
Its happening with me too...
I have downloaded r195 and r202 like 5-6 times from every browser..and the dl completes but whenever i open the zip it gives error
[Viper3D_1.0.0_R284.zip] Phone Stuck while boot up
I have tried several flashing the latest rom by viper3d and the phone gets stuck after it says HTC EVO 3D, and then it flips over and it has a picture of a viper with the words VIPER 3D. It just stays there. I've never had a problem with their previous roms. I'm not sure what is wrong. Can someone please help me. Here is my recovery information.
-Revolutionary-
SHOOTER XC SHIP S-OFF RL
HBOOT-1.40.1100
RADIO-0.97.10.0530
eMMC-boot
Jun 8 2011, 17:20:22
HTC EVO 3D » virus » root » Viper3D » Nightly »
Ironman_1218 said:
Can someone please help me. Here is my recovery information.
-Revolutionary-
SHOOTER XC SHIP S-OFF RL
HBOOT-1.40.1100
Click to expand...
Click to collapse
Check the OP (or several recent posts) in that thread. The current version (r284) requires hboot 1.58 or JBear 1.58.5858 to boot, although virus posted recently that he found a way to remove that restriction so the next version may not.
ramjet73
ramjet73 said:
Check the OP (or several recent posts) in that thread. The current version (r284) requires hboot 1.58 or JBear 1.58.5858 to boot, although virus posted recently that he found a way to remove that restriction so the next version may not.
ramjet73
Click to expand...
Click to collapse
is there an easy way to upgrade my hboot to 1.58 or JBear 1.58.5858? Or do you suggest that I stay at my lower hboot version?
Ironman_1218 said:
is there an easy way to upgrade my hboot to 1.58 or JBear 1.58.5858? Or do you suggest that I stay at my lower hboot version?
Click to expand...
Click to collapse
Pretty easy since you are S-OFF.
ramjet73

[Guide] Quick And Dirty RUU Flashing for CDMA S-OFF Users

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

*Solved* CDMA Sprint Hboot 1.58 Total noob guide for S-off[ROOT]

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!

Categories

Resources