[CDMA] Radios, Hboot & Firmware - All Downloads

Warning: For CDMA phones only!!!Do not use on GSM phones!
Will work on Sprint and Virgin Mobile.
S-off Required.

How to use a PG86IMG.zip file!

First let me start by stressing something important! Verify the integrity of the download by checking the file against its md5 checksum that I provided for each file. You can use a free software such as MD5 Checker to do the job. Or if you'd like to check on your phone without a pc, download MD5 Checker for android from the play store. If for whatever reason your download gets corrupted, using a corrupted file can brick your phone! So use an md5 checker to verify the integrity of the file, it's quick and easy and can keep your phone safe!

*The presence of the file on your sd card will prevent you from entering recovery in an emergency situation. It's nothing to panic about, but if you get caught in a bootloop, you will have to manually remove the file using a pc and card reader or another phone. That said, to avoid bootloops and being stuck with no way to boot up and no way to enter recovery, plan ahead. If you are on a rom that requires hboot 1.58 and you flash hboot 1.5, you will hit a bootloop and not be able to access recovery. You would then need to remove the file or flash a compatible rom through fastboot connected to a pc.

Okay. Now with instructions and warnings out of the way, I will give you my personal preference on how to flash a different hboot that will be incompatible with your current rom without getting a bootloop and having to use a pc to fix the situation.

Follow steps 1-3 above. Stop! Now, instead of rebooting into the bootloader, we are going to bypass the bootloader by rebooting directly into recovery. Some roms have this feature built in. I recommend downloading something like ROM TOOLBOX from the play store. It's a great app to have if you are rooted. Rom Toolbox has a built in rebooter menu (with widgets) that allows this function. Alternatively go get QUICK BOOT from the play store.So once in recovery, wipe and flash the rom normally. Once finished, continue to steps 4-7.

This will allow you to do everything completely from your phone and avoid getting stuck. Remember, this is just for when you are changing hboots that will be incompatible with the rom you are already using (ie: ICS to GB). Just following steps 1-7 normally is fine for just flashing radios or switching between different GB hboots etc.

Warning: For CDMA phones only!!!Do not use on GSM phones!
Will work on Sprint and Virgin Mobile.
S-off Required.

These files will update your base, hboot, radios, and firmware. They are more or less similar to running the RUU but with less hassle and without losing root. When changing between ICS & GB (1.58 and 1.5-) hboots for roms that require it, I would recommend using these full update packages as you will likely want more than just the hboot switching between roms that require a different build.

*Download "Info.txt" to see additional details and list of files contained in the zip.

I have a question though... regarding the latest ICS firmware shown for Sprint here (build 2.89.651.2), does this contain Android 4.0.4? The firmware on my phone shows this build number, but the Android version shows as 4.0.3. My Evo 3D is not yet activated so I can't do OTA (will activate it in a week or two), but I'd like to get 4.0.4 installed ahead of time (it has a few fixes, including some improvements to the camera function).

I have a question though... regarding the latest ICS firmware shown for Sprint here (build 2.89.651.2), does this contain Android 4.0.4? The firmware on my phone shows this build number, but the Android version shows as 4.0.3. My Evo 3D is not yet activated so I can't do OTA (will activate it in a week or two), but I'd like to get 4.0.4 installed ahead of time (it has a few fixes, including some improvements to the camera function).

Click to expand...

None of these files contain any software. Just the firmware from all the updates. So when using these, it will not change or update your software version.
It's been awhile since I've been on stock. But I'm not sure that they updated the evo 3d to anything newer than what you're on. You can flash roms that are built around software we don't have though

Thanks, Brian. I have since learned a few more useful things regarding Android ICS versions.

While Android ICS finished up with 4.0.4, there was no release made for the Evo 3D. Thus, 4.0.3 remains the latest via OTA. I have no idea if anybody created a custom ICS ROM that incorporates some of the fixes that were made for 4.0.4.

Also, I noticed you're using 4EXT for recovery. I'm curious as to why you prefer this over TWRP 2. I've been using TWRP and have found it very robust and reliable. But I have to admit I'm not familiar with 4EXT and don't know if there's functionality provided that is superior... or just different.

Also, I noticed you're using 4EXT for recovery. I'm curious as to why you prefer this over TWRP 2. I've been using TWRP and have found it very robust and reliable. But I have to admit I'm not familiar with 4EXT and don't know if there's functionality provided that is superior... or just different.

Click to expand...

4EXT provides a more consistent way for S-ON folks to successfully flash custom ROMs. It's also touch enabled, so it's a little bit easier to navigate, IMO.

Thanks, Brian. I have since learned a few more useful things regarding Android ICS versions.

While Android ICS finished up with 4.0.4, there was no release made for the Evo 3D. Thus, 4.0.3 remains the latest via OTA. I have no idea if anybody created a custom ICS ROM that incorporates some of the fixes that were made for 4.0.4.

Also, I noticed you're using 4EXT for recovery. I'm curious as to why you prefer this over TWRP 2. I've been using TWRP and have found it very robust and reliable. But I have to admit I'm not familiar with 4EXT and don't know if there's functionality provided that is superior... or just different.

Click to expand...

I've not used twrp 2. I had twrp 1.1.1 which compared to 4ext is quite bland. 4ext works well, I'm used to it and have never had any problems using it. I can really give a comparison as I haven't used twrps touch version. But as toad said, 4ext is very beneficial to s-on users. It allows them to flash some roms more easily.

Thanks, Toad & Brian. I've installed 4EXT on my Evo 3D and I really like it. I guess that "touch enabled" is all about the installed app that integrates use of the recovery options from the active ROM? It's really terrific, a good step above TWRP. Well anyway, it seems that 4EXT has a very limited release of supported phones, so if yours falls within it's best to gear up for the advantages it gives over TWRP and CWM.

And yes, being given the chance to apply custom ROMs with S-ON is a nice advantage. I wonder... does this mean that ROMs like CM10 that say you need S-OFF can still work on your hboot with S-ON as long as the version matches?

Thanks, Toad & Brian. I've installed 4EXT on my Evo 3D and I really like it. I guess that "touch enabled" is all about the installed app that integrates use of the recovery options from the active ROM? It's really terrific, a good step above TWRP. Well anyway, it seems that 4EXT has a very limited release of supported phones, so if yours falls within it's best to gear up for the advantages it gives over TWRP and CWM.

And yes, being given the chance to apply custom ROMs with S-ON is a nice advantage. I wonder... does this mean that ROMs like CM10 that say you need S-OFF can still work on your hboot with S-ON as long as the version matches?

Click to expand...

The app is optional. It's fully functional without the app. You will see that even inside the recovery, touch screen is enabled.

Assuming you were on the proper hboot, which you can't change while s-on, you should be able to flash with 4ext.

I downgraded my Hboot from 1.57.5757 (jbear) to 1.40 using this method on my Evo 3d CDMA (Virgin Mobile). Though after the update installed from bootloader, it booted into a bootloop. I was running an ICS stock rom I downloaded. I cannot access recovery directly, and trying to boot into fastboot asks me to update again. How can I flash a different Rom without recovery? Or is there another fix?

I downgraded my Hboot from 1.57.5757 (jbear) to 1.40 using this method on my Evo 3d CDMA (Virgin Mobile). Though after the update installed from bootloader, it booted into a bootloop. I was running an ICS stock rom I downloaded. I cannot access recovery directly, and trying to boot into fastboot asks me to update again. How can I flash a different Rom without recovery? Or is there another fix?

Click to expand...

Hey Kelly,
First off, to save some typing, I am going to copy/paste from the first post the instructions that are hidden below the "Show" button.

First let me start by stressing something important! Verify the integrity of the download by checking the file against its md5 checksum that I provided for each file. You can use a free software such as MD5 Checker to do the job. Or if you'd like to check on your phone without a pc, download MD5 Checker for android from the play store. If for whatever reason your download gets corrupted, using a corrupted file can brick your phone! So use an md5 checker to verify the integrity of the file, it's quick and easy and can keep your phone safe!

*The presence of the file on your sd card will prevent you from entering recovery in an emergency situation. It's nothing to panic about, but if you get caught in a bootloop, you will have to manually remove the file using a pc and card reader or another phone. That said, to avoid bootloops and being stuck with no way to boot up and no way to enter recovery, plan ahead. If you are on a rom that requires hboot 1.58 and you flash hboot 1.5, you will hit a bootloop and not be able to access recovery. You would then need to remove the file or flash a compatible rom through fastboot connected to a pc.

Okay. Now with instructions and warnings out of the way, I will give you my personal preference on how to flash a different hboot that will be incompatible with your current rom without getting a bootloop and having to use a pc to fix the situation.

Follow steps 1-3 above. Stop! Now, instead of rebooting into the bootloader, we are going to bypass the bootloader by rebooting directly into recovery. Some roms have this feature built in. I recommend downloading something like ROM TOOLBOX from the play store. It's a great app to have if you are rooted. Rom Toolbox has a built in rebooter menu (with widgets) that allows this function. So once in recovery, wipe and flash the rom normally. Once finished, continue to steps 4-7.

This will allow you to do everything completely from your phone and avoid getting stuck. Remember, this is just for when you are changing hboots that will be incompatible with the rom you are already using (ie: ICS to GB). Just following steps 1-7 normally is fine for just flashing radios or switching between different GB hboots etc.

Click to expand...

The reason your phone won't boot is because Stock ICS isn't compatible with that hboot. Above in the instructions I posted, there is also pointers on how to do this without getting stuck in a bootloop. Hopefully if you understand the steps, you won't get stuck again in the future.

You need to remove the PG86IMG.zip from the sd card. Either with a card reader or by putting the sd card into a spare device. As long as it's there, you can't access recovery.

Once removed, you can flash any compatible rom through your recovery or change back to hboot 1.57.

Hey Y'all! Finally scratched up the courage to downgrade my HBoot, because I suspect a couple of issues I've had with some 4.1 sense ROMs were HBoot related. Anyway, either stupidly or courageously, I tried an alternate method of flashing a new Hboot (discovered on XDA and confirmed at Unlimited.IO), that mostly eliminates the risk of leaving a P86IMG file on SD. I just tried it and found it quite easy. I was 1.5858 (JBear) and just flashed 1.5050. I flashed it while I was on NegaLite-BluRom. (Yeah, I know my profile might say something else, but I'm a flash-a-holic due to someone's (no names mentioned, Brian ) help!

Basically what happened is you flashed an hboot that isn't compatible with your rom. That rom requires a newer hboot 1.58.0000.

You flashed a lower hboot hence the bootloop. You need to either flash a compatible rom or flash back to the other hboot.

Also view my instructions in post one by clicking show to see how to avoid bootloops while changing hboots to switch roms. I know you weren't changing roms though. If you are going to flash another rom, you need to remove the PG86IMG file from your sd card with a card reader or another device so that you can access recovery. Or you can get to recovery by using adb to get to fastboot usb mode (adb reboot bootloader) and then boot recovery with (fastboot boot recovery.img) then mount sd through recovery and remove the PG86IMG file. Either replace it with the 1.58 bootloader or flash a gb or jb rom that I compatible with 1.50

Basically what happened is you flashed an hboot that isn't compatible with your rom. That rom requires a newer hboot 1.58.0000.

You flashed a lower hboot hence the bootloop. You need to either flash a compatible rom or flash back to the other hboot.

Also view my instructions in post one by clicking show to see how to avoid bootloops while changing hboots to switch roms. I know you weren't changing roms though. If you are going to flash another rom, you need to remove the PG86IMG file from your sd card with a card reader or another device so that you can access recovery. Or you can get to recovery by using adb to get to fastboot usb mode (adb reboot bootloader) and then boot recovery with (fastboot boot recovery.img) then mount sd through recovery and remove the PG86IMG file. Either replace it with the 1.58 bootloader or flash a gb or jb rom that I compatible with 1.50

Click to expand...

Thanks, Brian. I thought I was cool, but it rebooted a time or thousand after seemingly good for a few. Wiping Dalvik/Cache seemed to help a bit, but not for long... Reflashing a Sense 4.1 I had issues with earlier, now (though I'd really rather go to sleep!). NOW, I have no good reason NOT to flash JB!

Thanks, Brian. I thought I was cool, but it rebooted a time or thousand after seemingly good for a few. Wiping Dalvik/Cache seemed to help a bit, but not for long... Reflashing a Sense 4.1 I had issues with earlier, now (though I'd really rather go to sleep!). NOW, I have no good reason NOT to flash JB!

Hey!! To the OP will you be updating virgin mobile newest hboot,firmware,radio!! No rush but I would rather wait for you to post the Pg.... I don't want to run ruu, the update, them update again, them root, etc.. thanks in advance!!

Hey!! To the OP will you be updating virgin mobile newest hboot,firmware,radio!! No rush but I would rather wait for you to post the Pg.... I don't want to run ruu, the update, them update again, them root, etc.. thanks in advance!!