Root My phone refuses to flash AOSP ROMs properly?!

[heythereitsv]

I literally flashed one three days ago, worked fine. But now, they seem to only go to the boot logo very briefly, and reboot. Made sure that I was on the ENG 1.04 HBOOT, flashed it again, reflashed 4EXT, and then flashed TWRP recovery. Still does the exact same thing! I've tried combinations of flashing the ROM, then buttertoast kernel, no kernel, super safe settings, etc. Redownloaded AND re copied several times to my SD. Nothing seems to work. Weird thing? Unlocked Potential (Sense) works perfectly. What's up with my phone?!

Also, about to try a different cable with a different SD and see if it's with those.

*note- no error in flashing. Shows update installed, etc etc.

*EDIT* Copying a fresh copy of CM10 GangnamStyle using a different cable to a different SD, wiping all partitions, and then flashing using TWRP didn't work. WTF?!

 

[davidmargolin]

check to make sure that you are wiping all partitions (except sd) before flashing.. also, if you are flashing the same file over and over, it might be corrupt so try redownloading

 

[heythereitsv]

check to make sure that you are wiping all partitions (except sd) before flashing.. also, if you are flashing the same file over and over, it might be corrupt so try redownloading

Wiped all partitions, and I redownloaded and copied over multiple times. It's a local problem.

 

[ramjet73]

Wiped all partitions, and I redownloaded and copied over multiple times. It's a local problem.

Users of the Evo 3D with this type of problem have gotten past it by flashing the RUU to get everything in sync, then installing a custom hboot and recovery and flashing the ROM again. I can't guaranty it will resolve your issues but it might be worth a try.

ramjet73

 

[heythereitsv]

Users of the Evo 3D with this type of problem have gotten past it by flashing the RUU to get everything in sync, then installing a custom hboot and recovery and flashing the ROM again. I can't guaranty it will resolve your issues but it might be worth a try.

ramjet73

What would the root of this problem be though? AFAIK, everything's pretty in sync- the flash memory is formatted properly, the HBOOT is the correct one, and the kernel is compatible... Also, would I have to go back to S-ON to run the RUU?

 

[ramjet73]

What would the root of this problem be though? AFAIK, everything's pretty in sync- the flash memory is formatted properly, the HBOOT is the correct one, and the kernel is compatible... Also, would I have to go back to S-ON to run the RUU?

No, flashing an RUU (exe or zip) when S-OFF will not reset radio security to S-ON.

The "ala carte" updating of firmware has caused booting problems for many Evo 3D/V users that is only cleared by installing an RUU that formats and restores most of the partitions and firmware used by the phone to stock, including pieces like adsp.img that are not normally updated. I can't tell you specifically what may get "out of sync" with the flashing of firmware, hboots, recoveries and ROM's over time but it defintely happens.

It takes about 10 minutes to flash the RUU.exe and no special preparation if you are already S-OFF. After it is installed, flashing a custom hboot and recovery and the OTA firmware update will get you back to the point where you can restore a nandroid or flash a custom ROM so the whole process should take less than an hour.

ramjet73

 

[heythereitsv]

No, flashing an RUU (exe or zip) when S-OFF will not reset radio security to S-ON.

The "ala carte" updating of firmware has caused booting problems for many Evo 3D/V users that is only cleared by installing an RUU that formats and restores most of the partitions and firmware used by the phone to stock, including pieces like adsp.img that are not normally updated. I can't tell you specifically what may get "out of sync" with the flashing of firmware, hboots, recoveries and ROM's over time but it defintely happens.

It takes about 10 minutes to flash the RUU.exe and no special preparation if you are already S-OFF. After it is installed, flashing a custom hboot and recovery and the OTA firmware update will get you back to the point where you can restore a nandroid or flash a custom ROM so the whole process should take less than an hour.

ramjet73

Can you link me to an RUU? And is it carrier locked by any chance? I'm asking because of my phone being on Virgin. Also, just making sure- I can flash this while being S-OFF and on the ENG HBOOT 1.04 right?

 

[Rxpert83]

And ruu will reinstall everything from radios to hboot.

It will leave s-off though

 

[ramjet73]

Can you link me to an RUU? And is it carrier locked by any chance? I'm asking because of my phone being on Virgin. Also, just making sure- I can flash this while being S-OFF and on the ENG HBOOT 1.04 right?

Here's a link to the Virgin Mobile RUU. Yes, you can flash it without any special considerations when S-OFF, although sometimes I've had to cancel the Windows task and restart it if a custom hboot (like ENG) is installed and it hangs after flashing the bootloader.

ramjet73

 

[wolfu]

I literally flashed one three days ago, worked fine. But now, they seem to only go to the boot logo very briefly, and reboot. Made sure that I was on the ENG 1.04 HBOOT, flashed it again, reflashed 4EXT, and then flashed TWRP recovery. Still does the exact same thing! I've tried combinations of flashing the ROM, then buttertoast kernel, no kernel, super safe settings, etc. Redownloaded AND re copied several times to my SD. Nothing seems to work. Weird thing? Unlocked Potential (Sense) works perfectly. What's up with my phone?!

Also, about to try a different cable with a different SD and see if it's with those.

*note- no error in flashing. Shows update installed, etc etc.

*EDIT* Copying a fresh copy of CM10 GangnamStyle using a different cable to a different SD, wiping all partitions, and then flashing using TWRP didn't work. WTF?!

This happened to me once on unlocked potential too I had to fastboot flash the boot img saved in my fastboot (sdk) then reinstalled the rom I wanted via recovery. My phone was fine after that not sure if that would solve your issue or not.

 

[mrawesome22]

Flash Freeza's 2.89 firmware package. Downgrade hboot. AOSP roms will flash for you.

Make sure to change spcs_001 to spcs_002 in android-info.txt.

The 2.89 package is over at XDA.

 

[ramjet73]

Flash Freeza's 2.89 firmware package. Downgrade hboot. AOSP roms will flash for you.

Make sure to change spcs_001 to spcs_002 in android-info.txt.

The 2.89 package is over at XDA.

If you want to try that the freeza firmware is in this post.

My preference would still be to flash the Virgin Mobile RUU and OTA firmware, then install the ENG 1.04 or JBear 1.50.5050 hboot and 4EXT recovery, since I know that combination has worked for other people running the AOSP based ROM's.

ramjet73

 

[heythereitsv]

Here's a link to the Virgin Mobile RUU. Yes, you can flash it without any special considerations when S-OFF, although sometimes I've had to cancel the Windows task and restart it if a custom hboot (like ENG) is installed and it hangs after flashing the bootloader.

ramjet73

Do you have a flashable version of the RUU? The device ID doesn't seem to match, spits out an error 155 when trying to run it.

This happened to me once on unlocked potential too I had to fastboot flash the boot img saved in my fastboot (sdk) then reinstalled the rom I wanted via recovery. My phone was fine after that not sure if that would solve your issue or not.

Were you S-ON? It seems like everything is flashing properly on my phone, just won't start...

Flash Freeza's 2.89 firmware package. Downgrade hboot. AOSP roms will flash for you.

Make sure to change spcs_001 to spcs_002 in android-info.txt.

The 2.89 package is over at XDA.

Flashed this on Juopunutbear 1.57, and then downgraded to ENG 1.04. Still refuses to boot AOSP. Don't know what I'm doing wrong. And also, worth mentioning, the boot logo doesn't even show up anymore.

Also, flashed the boot.img (fastboot flash boot boot.img) from CM10 Gangnam style just for kicks, didn't work. What's going on here?!

*note, I've flashed AOSP ROMs properly, I wiped after downgrading/upgrading HBOOTs and am doing the steps rightfor flashing them*

 

[ramjet73]

Do you have a flashable version of the RUU? The device ID doesn't seem to match, spits out an error 155 when trying to run it.

If your CID doesn't match the one in the RUU.exe that I linked you have a bigger problem because that version has worked on many Evo V 4G phones before. You can check your CID with the following command:

fastboot getvar cid

It should be "SPCS_002" or else someone has changed it on your phone.

I don't have a zip version of the VM RUU that can be flashed in the bootloader but you can extract the rom.zip from the RUU.exe and using this procedure, then rename it to PG86IMG.zip and flash it from your bootloader.

ramjet73

 

[mrawesome22]

Splash screen doesn't show or boot screen doesn't show?

And I think you have to flash a locked bootloader to run ruu's.

I had this same problem when I ruu'd back to 1.13 just for kicks. AOKP just bootlooped until I reinstalled the 2.89 firmware.

Thinking I had to lock the bootloader before the ruu would run.

 

[ramjet73]

And I think you have to flash a locked bootloader to run ruu's.

There is no need to lock the bootloader to flash an RUU using the .exe or .zip version if you are S-OFF, and it doesn't reset the radio security to S-ON. Many 3D users that have flashed only freeza's firmware zip ultimately have booting problems, which is why I recommend the RUU. The firmware in freeza's file is all included in the RUU, although VM users should flash the firmware from the OTA after installing the RUU since that contains fixes for the radio and PRI.

However, the AOSP based ROM's will not boot after flashing the RUU until an hboot at 1.50 or lower is installed.

ramjet73

 

[mrawesome22]

I found the opposite.

The 1.13 firware that the ruu installs made it impossible to flash aokp.

Flashed back to the 2.89 (vm 1.14 equivalent) and flashing aokp was back to normal.

 

[ramjet73]

I found the opposite.

The 1.13 firware that the ruu installs made it impossible to flash aokp.

Flashed back to the 2.89 (vm 1.14 equivalent) and flashing aokp was back to normal.

I've already stated in several posts that the firmware from the VM OTA update should be flashed after installing the RUU to bring the firmware (baseband) level to exactly the same as the Sprint ICS 2.89.651.2 build (1.09.00.0706). That should eliminate the signal fluctuation and resource shortages of the original VM firmware, and I've found from experience that it's always better to update things the way the vendor intended unless that doesn't work for you. I know some of the VM users currently on mazda's AOKP are running it successfully with that configuration.

YMMV.

ramjet73

 

[heythereitsv]

Thank you guys so much! Ran the RUU (Fixed Error 155 by rebooting to fastboot mode), it ran successfully (stopped after flashing HBOOT, ran again after that perfectly), updated using the OTA, used the unlock token to unlock bootloader again, flashed a recovery, downgraded the HBOOT, and whaddya know? It works now!

 

[ramjet73]

Thank you guys so much! Ran the RUU (Fixed Error 155 by rebooting to fastboot mode), it ran successfully (stopped after flashing HBOOT, ran again after that perfectly), updated using the OTA, used the unlock token to unlock bootloader again, flashed a recovery, downgraded the HBOOT, and whaddya know? It works now!

Glad it worked for you!

It's not a big deal but you could have flashed a custom recovery after installing a custom hboot and not have to unlock the bootloader. The wire trick leaves the bootloader locked, but the custom bootloaders like ENG and JBear allow the fastboot commands that would normally require unlocking.

ramjet73

 

[heythereitsv]

Glad it worked for you!

It's not a big deal but you could have flashed a custom recovery after installing a custom hboot and not have to unlock the bootloader. The wire trick leaves the bootloader locked, but the custom bootloaders like ENG and JBear allow the fastboot commands that would normally require unlocking.

ramjet73

Wouldn't I need to unlock the bootloader to flash a different one anyway?

 

[ramjet73]

Wouldn't I need to unlock the bootloader to flash a different one anyway?

Only S-OFF is required to flash an hboot without installing an RUU. The only time unlocking the stock bootloader is necessary on the Evo 3D/V is to enable fastboot commands like "flash" and "erase" for S-ON users. Flashing a custom hboot like ENG, JBear or Revolutionary will enable those commands for S-OFF users.

ramjet73