It's all Dr. Dre's fault

[squarerootz]

Fellow Geeks,

I'm in dire straits for some assistance.

I've been a member for some time now, lurking here and there, contributing when I have something of value. I've been through several phones, with an EVO 4G being my latest acquisition. Once I left Sprint as my carrier (Monthly rates were just too high for my blood), I was left with a phone that I couldn't flash to another carrier worth my valuable dollars (yes I know I could flash to Cricket or Metro PCS but I've never been a fan of their service). So, I started reading this forum and may others in regards to rooting and flashing.

After accomplishing this and having a case of ORD, I finally settled on FreshROM.

It worked well and outside of the occasional lag, I was pretty happy with my setup. Then a friend of mine finally converted from the TP2 to the EVO 3D. After answering several of his questions about rooting and flashing, he made the leap and flashed InfectedROM w/ beats audio baked in.

Being an audiophile and music blogger, I was of course interested to see if there was a ROM available w/ beats in it for my device. I found this one HERE called BlazingROM and installed the file from the first D/L link using the normal SD card method and Clockwork.

I of course cleared the Dalvik and the other cache. I didn't make a backup of my FreshROM as I already had one on my SD Card and in Dropbox for safekeeping as well as a Stock Odexed backup just in case.

The ROM installed just fine and I was enjoying the different elements of it while re-installing my apps with Titanium Backup when, the ROM started giving me messages that I was running low on internal storage space. I stopped TB and started using Apps2SD to move what I'd installed so far to the card. I then went back to TB to finish but with every installation, I'd get the "Internal Memory Low" message again.

By this time, I was scratching my head. I mean, yes I do have 20 must have apps but with FreshROM and Apps2SD, I was able to have almost all of those apps on the SD card without any issue. Now with this BlazingROM, why would I be encountering this issue? I then noticed that this new ROM had some sort of baked in Task Manager, which was the process giving me the error messages. So I attempted to use it instead of A2SD to move anything I could to the card. After doing so, I once again went back to TB to finish but upon the first install, I got the error message again. By now, I'm getting a little pissed and I still haven't even tried out the beats audio part of the ROM yet.

So, I decided to go back to basics. I opened Clockwork and did a Dalvik wipe and a re-flash of the ROM. Once that finished, I re-booted the phone. It was to no avail, as the Task Manager happily told me my Internal Memory was still too low.

I kind of panicked, not really…but a little…but I kept my wits about me and quickly went back to the post I got the ROM from in search of answers. I scoured any and all related replies which the consensus of brought me to the conclusion that my SD card should be formatted and then partitioned to accommodate the BlazingROM’s internal memory quirk.

Having no need to ever do so before, I then asked Mr. Google how it is properly done. Of course searching there brought back many links and after reading the majority of them, I settled on the method that involved ditching Clockwork Mod for Amon Ra’s recovery as it had more necessary options to partition than CW. That accomplished, I then found a guide for the different sizes of partitions as well as a discussion on the difference between EXT2 and EXT3 as well as the pros and cons of upgrading from one to the other.

I opted to leave the swap size at 0 (zero) and go for a 512MB partition. Once that was done, I then once again went through the steps to get BlazingROM flashed and running and once again, the evil “Internal Memory Low” message laughed at my efforts.

Fine I thought, I'll just go back to my good old trusty FreshROM until I come across another one w/ beats audio and none of these memory issues. I turned off the device, went to the Bootloader, chose Recovery and from CW Recovery, wiped the Dalvik again and chose to install FreshROM from zip on SD card.

Everything was going fine. It installed and I chose to re-boot the phone. That's when tragedy struck.

When my phone attempted to start up, the normal Boot Screen I'd come to love, where if you have the volume up, you see a hybrid of Tux and Andy while being greeted with a stylized "FRESHHHHHHHH!!" became stuck in the dreaded Boot Loop.

Back I went to Mr. Google to get some answers. This time he directed me to posts from here at PPCG to XDA to Android Central and various others. Almost every post I read instructed me that a Boot Loop could easily be fixed by placing the PC36IMG on the roots of my card and allowing the Recovery to find it in the Bootloader. I did so but it didn’t seem to make any difference. The phone continued to loop.

I did a battery pull but this time when I went to the Bootloader, ensured that it was indeed finding the PC36IMG and re-booted, I ended up with the Black HTC screen with four exclamation marks in the corners.

I’d never seen this screen before…so now I’m really panicking.

Off I went again in search for a solution. This time, I came across posts at all of the sites mentioned before but with a different solution involving the use of an RUU to take the phone back to it’s out of the box stock ROM state. Fine I thought. The phone will still be S-Off and I’ve got everything backed up on TB and Dropbox, it won’t be hard to get it back to where it was.

After checking the posting dates to ensure I was getting fresh info and links, I ended up at Shipped-ROMS. I D/Led what appeared to be the latest one and most recommended (RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15. 00.11.19_NV_1.90_release_161482_signed.exe) to remedy my issue along with some instructions in a Word Doc regarding it as well that I found on another site. I even followed another post that added that I should install HTC Sync in order to have the right drivers on my PC for the RUU to work properly.

Long story short, after trying 10 different RUU’s as well as installing HTC Sync, uninstalling Sync and installing different HBoot drivers (2.10, 2.02, etc.) in all possible combinations, the only thing I’ve managed to do is end up with my phone still showing a Black HTC four exclamation mark screen. The only time the screen is different is when the RUU fails (either due to Error 152, Error 238 or Error 330) and I unplug the USB cable. The screen then shows an RUU Bootloader with these results:

SUPERSONIC EVT1 ENG S-OFF
HBOOT-2.10.0001 (PC36****)
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.0808
Mar 30 2010, 11:24:04

RUU
Parsing ….[downloading ZIP]
[1] RADIO_V2 -OK
[2] SPLASH -Fail-PU
[3] RECOVERY -Fail-PU
[4] WIMAX -Fail-PU
[5] USERDATA -Fail-PU
[6] BOOTLOADER -Fail-PU
[7] SYSTEM -Fail-PU
[8] BOOT -Fail-PU

Partition update fail!
Update Fail!

For some reason, each and every RUU gets up to around 32% to 40% and begins to show signs of failing while Updating User Data.

I’m reluctantly conceding defeat on this, as I have no clue as to what to do now. I’ve even gone as far as downloading Android SDK to try and figure out how to push the RUU or some kind of fix through ABD Shell.

If anyone has anything constructive that could help, I’d appreciate it greatly.

[darren.wlsn1]

moved...

[Karl]

Originally Posted by squarerootz

Fellow Geeks,

I'm in dire straits for some assistance.

I've been a member for some time now, lurking here and there, contributing when I have something of value. I've been through several phones, with an EVO 4G being my latest acquisition. Once I left Sprint as my carrier (Monthly rates were just too high for my blood), I was left with a phone that I couldn't flash to another carrier worth my valuable dollars (yes I know I could flash to Cricket or Metro PCS but I've never been a fan of their service). So, I started reading this forum and may others in regards to rooting and flashing.

After accomplishing this and having a case of ORD, I finally settled on FreshROM.

It worked well and outside of the occasional lag, I was pretty happy with my setup. Then a friend of mine finally converted from the TP2 to the EVO 3D. After answering several of his questions about rooting and flashing, he made the leap and flashed InfectedROM w/ beats audio baked in.

Being an audiophile and music blogger, I was of course interested to see if there was a ROM available w/ beats in it for my device. I found this one HERE called BlazingROM and installed the file from the first D/L link using the normal SD card method and Clockwork.

I of course cleared the Dalvik and the other cache. I didn't make a backup of my FreshROM as I already had one on my SD Card and in Dropbox for safekeeping as well as a Stock Odexed backup just in case.

The ROM installed just fine and I was enjoying the different elements of it while re-installing my apps with Titanium Backup when, the ROM started giving me messages that I was running low on internal storage space. I stopped TB and started using Apps2SD to move what I'd installed so far to the card. I then went back to TB to finish but with every installation, I'd get the "Internal Memory Low" message again.

By this time, I was scratching my head. I mean, yes I do have 20 must have apps but with FreshROM and Apps2SD, I was able to have almost all of those apps on the SD card without any issue. Now with this BlazingROM, why would I be encountering this issue? I then noticed that this new ROM had some sort of baked in Task Manager, which was the process giving me the error messages. So I attempted to use it instead of A2SD to move anything I could to the card. After doing so, I once again went back to TB to finish but upon the first install, I got the error message again. By now, I'm getting a little pissed and I still haven't even tried out the beats audio part of the ROM yet.

So, I decided to go back to basics. I opened Clockwork and did a Dalvik wipe and a re-flash of the ROM. Once that finished, I re-booted the phone. It was to no avail, as the Task Manager happily told me my Internal Memory was still too low.

I kind of panicked, not really…but a little…but I kept my wits about me and quickly went back to the post I got the ROM from in search of answers. I scoured any and all related replies which the consensus of brought me to the conclusion that my SD card should be formatted and then partitioned to accommodate the BlazingROM’s internal memory quirk.

Having no need to ever do so before, I then asked Mr. Google how it is properly done. Of course searching there brought back many links and after reading the majority of them, I settled on the method that involved ditching Clockwork Mod for Amon Ra’s recovery as it had more necessary options to partition than CW. That accomplished, I then found a guide for the different sizes of partitions as well as a discussion on the difference between EXT2 and EXT3 as well as the pros and cons of upgrading from one to the other.

I opted to leave the swap size at 0 (zero) and go for a 512MB partition. Once that was done, I then once again went through the steps to get BlazingROM flashed and running and once again, the evil “Internal Memory Low” message laughed at my efforts.

Fine I thought, I'll just go back to my good old trusty FreshROM until I come across another one w/ beats audio and none of these memory issues. I turned off the device, went to the Bootloader, chose Recovery and from CW Recovery, wiped the Dalvik again and chose to install FreshROM from zip on SD card.

Everything was going fine. It installed and I chose to re-boot the phone. That's when tragedy struck.

When my phone attempted to start up, the normal Boot Screen I'd come to love, where if you have the volume up, you see a hybrid of Tux and Andy while being greeted with a stylized "FRESHHHHHHHH!!" became stuck in the dreaded Boot Loop.

Back I went to Mr. Google to get some answers. This time he directed me to posts from here at PPCG to XDA to Android Central and various others. Almost every post I read instructed me that a Boot Loop could easily be fixed by placing the PC36IMG on the roots of my card and allowing the Recovery to find it in the Bootloader. I did so but it didn’t seem to make any difference. The phone continued to loop.

I did a battery pull but this time when I went to the Bootloader, ensured that it was indeed finding the PC36IMG and re-booted, I ended up with the Black HTC screen with four exclamation marks in the corners.

I’d never seen this screen before…so now I’m really panicking.

Off I went again in search for a solution. This time, I came across posts at all of the sites mentioned before but with a different solution involving the use of an RUU to take the phone back to it’s out of the box stock ROM state. Fine I thought. The phone will still be S-Off and I’ve got everything backed up on TB and Dropbox, it won’t be hard to get it back to where it was.

After checking the posting dates to ensure I was getting fresh info and links, I ended up at Shipped-ROMS. I D/Led what appeared to be the latest one and most recommended (RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15. 00.11.19_NV_1.90_release_161482_signed.exe) to remedy my issue along with some instructions in a Word Doc regarding it as well that I found on another site. I even followed another post that added that I should install HTC Sync in order to have the right drivers on my PC for the RUU to work properly.

Long story short, after trying 10 different RUU’s as well as installing HTC Sync, uninstalling Sync and installing different HBoot drivers (2.10, 2.02, etc.) in all possible combinations, the only thing I’ve managed to do is end up with my phone still showing a Black HTC four exclamation mark screen. The only time the screen is different is when the RUU fails (either due to Error 152, Error 238 or Error 330) and I unplug the USB cable. The screen then shows an RUU Bootloader with these results:

SUPERSONIC EVT1 ENG S-OFF
HBOOT-2.10.0001 (PC36****)
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.0808
Mar 30 2010, 11:24:04

RUU
Parsing ….[downloading ZIP]
[1] RADIO_V2 -OK
[2] SPLASH -Fail-PU
[3] RECOVERY -Fail-PU
[4] WIMAX -Fail-PU
[5] USERDATA -Fail-PU
[6] BOOTLOADER -Fail-PU
[7] SYSTEM -Fail-PU
[8] BOOT -Fail-PU

Partition update fail!
Update Fail!

For some reason, each and every RUU gets up to around 32% to 40% and begins to show signs of failing while Updating User Data.

I’m reluctantly conceding defeat on this, as I have no clue as to what to do now. I’ve even gone as far as downloading Android SDK to try and figure out how to push the RUU or some kind of fix through ABD Shell.

If anyone has anything constructive that could help, I’d appreciate it greatly.

ok thats a lot to read so i didnt..

so what do you want to do unroot?

[squarerootz]

Well, over the years of being at this forum, I've noticed that sometimes people aren't thorough enough with explaining what is wrong and what they've already done. So that accounts for the length.

I really just want to get the phone working again. Its only showing me the black HTC screen and none of the RUU's I've tried are working.

[trav230]

Cursory Googleing:
Error 152 is an Activesync error, which makes me think this is not a valid error code for android.

Error 238 is a file read error, "This error message may appear when, for some unknown reason, the ROM image on the Mobile Device is corrupt. Download the whole RUU and try again."

Error 330 is a ROM image error, "This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and make sure the image file is correct to upgrade."

When installing BlazingROM did you use Kingsmod format after wiping the data 2-3 times befor installing the ROM?

RUU Errors - XDA-Developers
xda-developers - View Single Post - [ROM's]+[FEARMEde]-//3.5¦¦B.6.5~10-10~\\

[squarerootz]

I got the Error 152 message when I had HTC Sync installed. Is it possible the RUU gave me the only code it could find similar enough to a syncing program error? I began getting the 238 and 330 Errors after trying the Hboot drivers.

As far as the Kingsmod, wasn't aware of it before flashing, so no, I didn't use it. I went with the regular old Clockwork Mod. Then when I was having issues with the Low Memory messages, flashed again with Amon Ra.

[trav230]

I think you can ignore 152 if it happened while you had Sync installed. BlazingROM wants Amon Ra as the recovery so I would use that, wipe user data 2-3 times, run Kingsmod to wipe completely wipe the internal memory and then reinstall from a known good source. If possible make sure that the md5 hash is correct before trying to install. It sounds like there will be a new update this week so you might just switch to that version.

Hope that helps,
-Travis

[squarerootz]

Ok. Here's a question. If all I'm getting is the black screen, with no way to interface with the phone, even when it's plugged into a PC, how do I run the Kingsmod? Is it an RUU? Cause unless you have an alternative, I have not other way to even interface with the phone right now.

[trav230]

If you can get into recovery you can run the .zip from your SD card but if you can't access the SD card and can't boot to recovery it sounds like it might have been bricked. If that is what happened all you can do is take it to Sprint and get them to replace it.

-Travis

[mikewest]

One of the steps he says he took was to leave sprint, as his blood can not handle it.

So, for him, no warranty or Asurion.