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.
Related
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"
I have been looking through different radios to flash and I just have a question. Some of the "PG05IMG.zip" files I have found only include 1 radio. Others (like the ones I find for the OTA update) include both the CMDA and LTE radios. If the PG05IMG.zip file includes both radios do I need to extract them and place them into their own PG05IMG.zip files and flash them separately or do I just go with that one file that includes both?
I am learning about RUU and radio versions right now so I'm getting all the numbers jumbled up. I had planned on the newest OTA radio as it should be stable. Is there another I might have better luck with? Could anyone, and I might be pushing it here, possibly link what they believe to the best the most stable radio out right now for a Gingerbread ROM?
I have flashed a new ROM but I haven't tried the radio before and I'm terrified of bricking my phone so I'd better ask the pros.
Thanks so much and I'll be perusing the threads while I await your wisdom!
Installing the latest leaked ruu is probably your best bet. It'll update you to gingerbread and it will also update your radios automatically.
Warning: if your rooted just make sure that you have a perminate s-off hboot, there are threads already on that so I won't go onto that, but with out you'll loose the ability to get root again.
Sent from my ADR6400L using xda premium
Good advice above on the locked hboot. Do that first.
Radio performance varies from both the device and the area you are in. Reading the forums you'll see a wide variance in user experience. Don't be afraid to try different ones. I ran the leaked MR2 long after people had moved on because the latter leaks didn't work as well for me. I went to Chingy's leak, now on the 2.11 RUU.
Make sure you have enough battery when you flash because you could brick if your phone turns off mid flash. Check the md5 to ensure the file is good. Also once you flash and reboot, got straight to your SD and move the radio zip from the root of the SD.
courtesy of my bolt and Tapatalk
Hey guys i just got the 3d today and have it rooted. I installed 1 or 2 updates already but still had 1.4. But im curious as to what update exactly changes my hboot to 1.5. can any one help?
DO NOT OTA UPDATE YOUR PHONE! You do not want the HBOOT 1.5 it will make your life difficult. Stick with your bootloader and if you want to UG do it via a custom ROM.
jrockisme said:
Hey guys i just got the 3d today and have it rooted. I installed 1 or 2 updates already but still had 1.4. But im curious as to what update exactly changes my hboot to 1.5. can any one help?
Click to expand...
Click to collapse
The RUU for software verison 2.08 should also update hboot to version 1.5.
Probably best not to load this version unless you're up for an adventure! The
RUU software version 2.08 which also contains Hboot 1.5 patches all previously used exploits. Meaning, a new exploit will have to be developed and released in order to achieve the same unlocked access on Hboot 1.5 as was available for previous versions of Hboot.
Hope that helps answer your question!
divedr said:
DO NOT OTA UPDATE YOUR PHONE! You do not want the HBOOT 1.5 it will make your life difficult. Stick with your bootloader and if you want to UG do it via a custom ROM.
Click to expand...
Click to collapse
ahh, its not too bad. Granted i wish i had 1.30 or 1.40 but ADB & Fastboot aren't too bad.
joeykrim said:
The RUU for software verison 2.08 should also update hboot to version 1.5.
Probably best not to load this version unless you're up for an adventure! The
RUU software version 2.08 which also contains Hboot 1.5 patches all previously used exploits. Meaning, a new exploit will have to be developed and released in order to achieve the same unlocked access on Hboot 1.5 as was available for previous versions of Hboot.
Hope that helps answer your question!
Click to expand...
Click to collapse
That doesnt answer my question but it does answer which RUU i need to download for my Hboot version. But thanks for that one!
jrockisme said:
That doesnt answer my question but it does answer which RUU i need to download for my Hboot version. But thanks for that one!
Click to expand...
Click to collapse
Wait I am confused, do you want to have hboot 1.5? If so why?
Sent from my PG86100 using xda premium
jrockisme said:
Hey guys i just got the 3d today and have it rooted. I installed 1 or 2 updates already but still had 1.4. But im curious as to what update exactly changes my hboot to 1.5. can any one help?
Click to expand...
Click to collapse
joeykrim said:
The RUU for software verison 2.08 should also update hboot to version 1.5.
Probably best not to load this version unless you're up for an adventure! The
RUU software version 2.08 which also contains Hboot 1.5 patches all previously used exploits.
Click to expand...
Click to collapse
jrockisme said:
That doesnt answer my question but it does answer which RUU i need to download for my Hboot version. But thanks for that one!
Click to expand...
Click to collapse
If your question, as I read your post was, "what update exactly changes my hboot to 1.5" and you're on the Sprint version of the EVO 3D, then my answer above is correct. Software version 2.08.651.2 contains an update to bootloader version 1.5.
Perhaps I'm wrong in assuming you're on the Sprint device and perhaps you're using a GSM version. I'm not familar with the history of the GSM software versions, but I'm sure somebody else can post up to help clarify. Not sure where else the miscommunication could have occured.
Off the top of my head and to reiterate:
There have only been four updates for the EVO 3D from Sprint for their CDMA version of the EVO 3D.
1.11.651.2, 1.13.651.7, 2.08.651.2 an 2.08.651.3 (no leak RUU yet, only OTA, minor system software/kernel changes, no updated bootloader/radio).
If you're interested in gaining the ability to answer this question yourself, the hboot version is generally listed in the hboot file name of the image provided inside the firmware.zip of the RUU rom.zip (often renamed as PG86IMG.zip) included inside the RUU .exe. Hboot file name is generally, Hboot1.4_signed.img or something similar.
Also, if you feel adventurous, you could open the hboot img in a hex editor and search for the string containing the version number! Thats an adventure I don't take very often.
To obtain the extracted rom .zip files, renamed as PG86IMG.zip files or the original RUU .exe files for any of these software versions which have been leaked online, goo-inside.me keeps a reliable collection: http://www.goo-inside.me/shooter/ruu .
Allowing EVO 3D users to revert back to any previous software version or update to the recent versions.
Hope that helps answer your question with more detail/insight or help anybody coming across this post that might have the same/related questionand resolve any miscommunication! Money back guarantee!
SketchyStunts said:
ahh, its not too bad. Granted i wish i had 1.30 or 1.40 but ADB & Fastboot aren't too bad.
Click to expand...
Click to collapse
Agreed, a little more of a pain but also makes you learn things other people may not be savvy on! Great opinion man!
joeykrim said:
Off the top of my head and to reiterate:
There have only been four updates for the EVO 3D from Sprint for their CDMA version of the EVO 3D.
1.11.651.2, 1.13.651.7, 2.08.651.2 an 2.08.651.3 (no leak RUU yet, only OTA, minor system software/kernel changes, no updated bootloader/radio).
If you're interested in gaining the ability to answer this question yourself, the hboot version is generally listed in the hboot file name of the image provided inside the firmware.zip of the RUU rom.zip (often renamed as PG86IMG.zip) included inside the RUU .exe. Hboot file name is generally, Hboot1.4_signed.img or something similar.
Click to expand...
Click to collapse
I am sure I know the answer, cause if it were this easy we wouldn't have so many *****ing about 1.5, but if the RUU installs the bootloader, would it be possible to use an RUU of 1.11 or 1.13 to get the older bootloader?
Bob
ParrSt said:
I am sure I know the answer, cause if it were this easy we wouldn't have so many *****ing about 1.5, but if the RUU installs the bootloader, would it be possible to use an RUU of 1.11 or 1.13 to get the older bootloader?
Bob
Click to expand...
Click to collapse
No, it won't work. I believe the install will fail and cancel itself.
ParrSt said:
I am sure I know the answer, cause if it were this easy we wouldn't have so many *****ing about 1.5, but if the RUU installs the bootloader, would it be possible to use an RUU of 1.11 or 1.13 to get the older bootloader?
Bob
Click to expand...
Click to collapse
Short answer: No and I think the exact error people receive is "Main version is older". As far as I recall, main version information is stored in the misc partition.
We've had a few threads on this, usually the title or key phrase is "downgrading" the bootloader.
Essentially, the HTC EVO Shift was able to have the bootloader downgraded two different ways after two different releases, but neither method will work for hboot 1.5.
If you're interested in a longer semi technical explanation, I've quoted my previous posts below for convenience.
http://forum.xda-developers.com/show...88&postcount=2
the shift didn't have all the partitions nand write locked like the EVO 3D does.
1st time around: shift didnt 'have nand write lock on the hboot partition, hence being able to temp root and directly flash eng hboot to the hboot partition.
2nd time around: shift didn't have the nand write lock on the misc partition, hence being able to temp root and flash a lower version to the misc partition then hboot would allow a downgraded version of software to be loaded.
esseentially it seems as if htc was doing the bare minimum to protect the shift from being unlocked/rooted as all these methods were known and some were used on the HTC EVO prior to the shift software releases.
this has been covered a few times on the forums, but i hope rehashing old ideas/attempts might spark new ones! sometimes it only takes a slight tweak to an old method for it to bypass a patch and work! hope that helps!
Click to expand...
Click to collapse
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
I'd like to update to the new Stock ROM with Goodies- Questions....
1. Hotspot work on this ROM?
2. What firmware/Radio do I need for this or does any of that get updated automatically?
3. Is there a walk through instruction/video for this update...from such an old ROM?
I have:
Hboot 1.12.0000
S-on
Radio 1.02.12.0427
TWRP 2.1.8
Well to start you need to decide if you want to s- off or not. If you don't i believe you can update firmware with the 1.12 hboot.
I'd update the firmware in consecutive order from where you are now. You want the firmware zips without the hboot img
Then you can flash the new rom you want.
I would follow the directions for s- off personally. It makes things alot easier
Sent from my EVO using xda premium
NaterTots said:
Well to start you need to decide if you want to s- off or not. If you don't i believe you can update firmware with the 1.12 hboot.
I'd update the firmware in consecutive order from where you are now. You want the firmware zips without the hboot img
Then you can flash the new rom you want.
I would follow the directions for s- off personally. It makes things alot easier
Sent from my EVO using xda premium
Click to expand...
Click to collapse
If I turn the device into s-off, then I can use TWRP to update from zip files right?
I read that I don't want to jump firmware to the latest or I could brick the device. So I thought the process might look like this.
PLEASE CORRECT ME IF I'M WRONG:
1. LazyPanda ( http://forum.xda-developers.com/showthread.php?t=1737123 )
to "s-off" the device
2. Run zip for 2.13.651.1 OTA (which one though?)
....Reboot THEN
run zip for 3.16.651.3 OTA
So I don't brick it
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
3. Install Stock ROM with Goodies...
Am I missing something?
What about the radio (comes with the firmware?)? What's the deal with the boot.img or not (I don't see the firmware WITHOUT boot.img included)?
Lazy panda is not technically supported anymore, so not sure how much luck you'll have there, but I would say run the 3.15 RUU, then s-off with dirty racun .
Stock with goodies is using the 3.16 base, so once you're s-off you can update to that firmware/radio version via the bootloader...assuming you're coming from 3.15. Just make sure to flash the 3.16 zip without the tp img, or your touch screen won't work with any other base.
http://forum.xda-developers.com/showthread.php?t=1704612
Sent from my EVO LTE
premo15 said:
Lazy panda is not technically supported anymore, so not sure how much luck you'll have there, but I would say run the 3.15 RUU, then s-off with dirty racun .
Stock with goodies is using the 3.16 base, so once you're s-off you can update to that firmware/radio version via the bootloader...assuming you're coming from 3.15. Just make sure to flash the 3.16 zip without the tp img, or your touch screen won't work with any other base.
http://forum.xda-developers.com/showthread.php?t=1704612
Sent from my EVO LTE
Click to expand...
Click to collapse
OK. let me revise then
1. S-off through RUU 3.15, then use Dirty Racun
2. Then update through TWRP (do I need a specific version or do I HAVE to use the Hboot?) to 3.15, then reboot and change to 3.16 (without tp.img in it)
3. install new ROM stock with goodies 3.16
Do I have it now?
(sigh...my Sprint Epic 4G first gen, and my wife's Galaxy Note 2 are SOOO much less complicated than HTC stuff)
ZenInsight said:
OK. let me revise then
1. S-off through RUU 3.15, then use Dirty Racun
2. Then update through TWRP (do I need a specific version or do I HAVE to use the Hboot?) to 3.15, then reboot and change to 3.16 (without tp.img in it)
3. install new ROM stock with goodies 3.16
Do I have it now?
(sigh...my Sprint Epic 4G first gen, and my wife's Galaxy Note 2 are SOOO much less complicated than HTC stuff)
Click to expand...
Click to collapse
That's what I was saying in another thread. With samsung phones you just flash and reboot. With these HTC phones you have to update this downgrade that just to flash a rom. I came from a one X and you had to flash the boot.img every time you wanted to flash a rom/kernel/modem.
Sent from my SAMSUNG-SGH-I717
No. Dont s-off then run dirty racun. S-off is what dirty racun does. He's saying Use RUU to get to 3.15, THEN use dirty racun (as per their instructions).
Then STAY at 3.15. Uncles you wanna use a 3.16 sense ROM (which is no different than a 3.15 ROM). If you S-off and update to 3.16 firmware AND flash the 3.16 touch panel image (tp.IMG), you will not be able to use any ROMs that aren't sense 3.16. I would suggest leaving your firmware where it is, and try the ROM you want. Generally, you DO NOT need current firmware to run a current ROM. The two are mutually exclusive (firmware and ROM). I always rock old radios. Newer isn't always better.
From my Evo LTE, yup.
1. S-OFF with DirtyRacun (doesn't really matter which RUU you choose)
2. Install custom recovery through fastboot (latest TWRP should be fine, depending on the ROM you choose - you might need 2.4.0.0 or older if flashing a ROM with an outdated update binary)
3. Flash ROM of your choice.
4. Update to latest firmware using most recent zip from firmware thread (this is done through the bootloader, not recovery)
5. Profit.
I feel pretty stupid with how confusing this is.
So
1. Use dirty Racun to go to s-off
2. I already have TWRP 2.1.8 for installing zip updates (Can I leave that version or do I need to change it?),,,
3. Install 3,15 firmware (or install 3.16 but without the tp img or my touchscreen in recovery will be busted.
Also, once I go to 3.16 I can only use 3.16 ROMS in the future.
4. Install any ROM which automatically changes me to the latest radio (is that true?).
I want this one:
http://forum.xda-developers.com/showthread.php?t=1701117
but does that mean I HAVE to have 3.16 firmware to use a 3.16 ROM? Or can I just leave it at 3.15?
ZenInsight said:
I feel pretty stupid with how confusing this is.
So
1. Use dirty Racun to go to s-off
2. I already have TWRP 2.1.8 for installing zip updates (Can I leave that version or do I need to change it?),,,
3. Install 3,15 firmware (or install 3.16 but without the tp img or my touchscreen in recovery will be busted.
Also, once I go to 3.16 I can only use 3.16 ROMS in the future.
4. Install any ROM which automatically changes me to the latest radio (is that true?).
I want this one:
http://forum.xda-developers.com/showthread.php?t=1701117
but does that mean I HAVE to have 3.16 firmware to use a 3.16 ROM? Or can I just leave it at 3.15?
Click to expand...
Click to collapse
2. The S-OFF process involved flashing an RUU, which will replace TWRP with the stock recovery. So like I said, you will need to flash TWRP. Since I don't know if flex has updated the update binary in that ROM, I would flash TWRP 2.4.0.0.
3. Just flash the 3.16 firmware. I've taken out anything that would be of concern, so you can flash whatever ROMs you want.
4. Radio is part of the firmware.
Captain_Throwback said:
2. The S-OFF process involved flashing an RUU, which will replace TWRP with the stock recovery. So like I said, you will need to flash TWRP. Since I don't know if flex has updated the update binary in that ROM, I would flash TWRP 2.4.0.0.
3. Just flash the 3.16 firmware. I've taken out anything that would be of concern, so you can flash whatever ROMs you want.
4. Radio is part of the firmware.
Click to expand...
Click to collapse
Ok. I get it. I lose TWRP once I "s-off", so I have to put it back on.
Just flash 3.16...it doesn't matter anymore about the touchscreen, that's been fixed.
Radio is included in the 3.16 firmware, not the ROM.
Flash the Stock with goodies...and I'll be fine.
Phew.... I hope this is right.
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
scottspa74 said:
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
Click to expand...
Click to collapse
No, it won't. Otherwise I would've said so. You obviously haven't been reading the firmware thread .
scottspa74 said:
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
Click to expand...
Click to collapse
Funny you say that since 3.15 firmware was causing soft bricks with older hboots. The only problem with the latest update is that aosp roms are stuck with out touch screen support for now.
Captain_Throwback said:
No, it won't. Otherwise I would've said so. You obviously haven't been reading the firmware thread .
Click to expand...
Click to collapse
Alright. Guess I missed something. Last time I was in there , if you didn't do 3.15 prior to 3.16 you were hosed.
But I did see the firmware haus dropped that it was said would be OK regardless of 3.15 or not. Just hadn't seen anyone try it.
Definitely listen to Cap'n. He's the man when it comes to firmwares and radios.
From my Evo LTE, yup.
Okay, I wish I had read this before I did what I just did. My device seems to be bricked
Was running 1.22.651.3 and MeanROM-ICS-v65 and went to update things to JB. Updated using PJ75IMG_3.16.651.3_firmware in HBOOT and now the screen won't turn on and none of the LEDs light up when plugged in. The device manager shows QHSUSB_DLOAD when it's plugged into the PC.
Any way to unbrick this?
(insert obligatory "I feel like an idiot for not doing more reading on here ahead of time" statement)
Trioculus said:
Okay, I wish I had read this before I did what I just did. My device seems to be bricked
Was running 1.22.651.3 and MeanROM-ICS-v65 and went to update things to JB. Updated using PJ75IMG_3.16.651.3_firmware in HBOOT and now the screen won't turn on and none of the LEDs light up when plugged in. The device manager shows QHSUSB_DLOAD when it's plugged into the PC.
Any way to unbrick this?
(insert obligatory "I feel like an idiot for not doing more reading on here ahead of time" statement)
Click to expand...
Click to collapse
Did you not download the most recent firmware from my thread? Because there's no way it should've bricked you. I personally updated from 1.22 firmware up to 3.16 with no issues, and someone else updated from 1.13 firmware up to 3.16. What exact file did you use?
EDIT: I just looked, and I don't even have a file available with that name in my thread (anymore). The only one I have is this, which is the extended firmware which eliminates the bricking issue. Sounds like you had an old download.
Captain_Throwback said:
What exact file did you use?
Click to expand...
Click to collapse
I used the one linked to from the wiki page: http://d-h.st/9L9 PJ75IMG_3.16.651.3_firmware.zip
Any way to fix this? Thanks for your help
Trioculus said:
I used the one linked to from the wiki page: http://d-h.st/9L9 PJ75IMG_3.16.651.3_firmware.zip
Any way to fix this? Thanks for your help
Click to expand...
Click to collapse
Ouch. I'll have to update the Wiki. I'll be sure to mention it to Haus.
And no, your device is bricked. Time to get a replacement.
EDIT: Wiki updated with proper link.
Captain_Throwback said:
Ouch. I'll have to update the Wiki. I'll be sure to mention it to Haus.
And no, your device is bricked. Time to get a replacement.
EDIT: Wiki updated with proper link.
Click to expand...
Click to collapse
ouch..That sucks, man.