Develop Bugs

[Q] rooted evo... bricked evo... help!

got my evo about a month ago. rooted lastnight since unrevoked finally pushed out their 3.3 version which is updated for my version of hboot (2.02). the root went very smoothly. i installed the latest cyanogenmod rom, only to discover there was no market or gmail app with the rom! wish i had known that before. after doing some research online, i found out i needed to flash or install a "gapps" apk. so, looked around for that for a couple hours and couldn't find it. i downloaded what i thought would be the right .zip file to get the market on my phone (a vending.apk that was listed in another thread having to do with this same issue). so anyway... downloaded that, moved it to the root of my sd card, flashed it through clockworkmod recovery (by the way, everything up until this point was perfect) and finally rebooted my phone... only it never rebooted. the white htc EVO 4G screen was there. then, black screen, as if it was about to begin the cyanogenmod boot screen and fully boot. but, no. it went from white evo screen to black screen... to OFF. after this, i couldn't even turn it on to get it into hboot or access recovery. tried to do that for two hours. and finally i was able to get in... so i tried doing a factory/data reset through recovery, then a cache clear, then reboot. nothing. same thing. went back into recovery, tried reflashing cyanogenmod rom again. nothing. tried flashing myn's rom. nothing. all i get is installation aborted.
i am pretty sure that this is not a complete brick since i am now able to access hboot and recovery. but if i can't flash anything... and i'm stuck in hboot and recovery and cant boot my phone... what the hell do i do now? please help me figure this out!! anybody have any good advice or a known fix...??

Boot into recovery. Do a factory reset. then wipe cache and dalvik catch. Re flash cynagon and let it boot. You then need to find gapps.zip. Boot into recovery flashing gapps.zip.

i did all that. step by step. and when i reflashed the rom, that is when it wouldn't install, saying installation aborted. but, i'm gonna do it again. let's see if my phone wants to play nice now...

brtnygrey said:
i did all that. step by step. and when i reflashed the rom, that is when it wouldn't install, saying installation aborted. but, i'm gonna do it again. let's see if my phone wants to play nice now...
Click to expand...
Click to collapse
If that does not work! you are going to have to update with sprint lovers rom, that is in a PCM36IMG.ZIP. Install it by holding the _vol and th power button, boot into boot loader, than it will search for the zip file and ask you if you want to update, say yes ans just weigh for it to be done. Its going to take few minutes first boot! just hold on. I hope this helps in anyway.

evolishesh said:
If that does not work! you are going to have to update with sprint lovers rom, that is in a PCM36IMG.ZIP. Install it by holding the _vol and th power button, boot into boot loader, than it will search for the zip file and ask you if you want to update, say yes ans just weigh for it to be done. Its going to take few minutes first boot! just hold on. I hope this helps in anyway.
Click to expand...
Click to collapse
do you think that sprintlovers rom will install even if no other rom will install? because... i was able to install Gapps.zip file just fine. but every rom i install is unsuccessful.

brtnygrey said:
do you think that sprintlovers rom will install even if no other rom will install? because... i was able to install Gapps.zip file just fine. but every rom i install is unsuccessful.
Click to expand...
Click to collapse
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk

mysteryemotionz said:
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
ok is the install through recovery supposed to be almost instantaneous? it didn't take a minute like every other rom. and after reboot (10 minutes ago) i'm still sitting on the white htc EVO 4G screen. i don't think this is working either. but i really do appreciate your help. any other suggestions? is there anything else through recovery that I can do (since i cant make it past that) that might fix my system? anything in partition? i'm so stuck!

mysteryemotionz said:
The springlovers rom gets flashed the same way sprint flashes there upgrades so it should
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
and also... when i go into hboot, and it runs through the "checking sd" thing before i can select options... it says "no image or wrong image". what?

Nothing is working!!

Did you try a rooted RUU yet?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Wipe everything twice first (just to be safe). Are you using Amon RA or Clockwork, by the way? The only other thing I can think of would be that your SD card isn't formatted properly, but that would have to mean you intentionally formatted it or put in a new one that didn't have the right files on it.

SilverZero said:
Did you try a rooted RUU yet?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs
Wipe everything twice first (just to be safe). Are you using Amon RA or Clockwork, by the way? The only other thing I can think of would be that your SD card isn't formatted properly, but that would have to mean you intentionally formatted it or put in a new one that didn't have the right files on it.
Click to expand...
Click to collapse
i am using clockwork. i've wiped so many times... but i can't make anything happen. and, i did format the sd card eventually, but not until a couple of hours ago... and only as a last resort because nothing else worked and i've been trying to fix this since last night, so i figured it couldn't hurt. but if that is part of the problem... how can i fix it? thanks for your response. i don't know what else to do other than take it in for a switch.l but if i can get into hboot... then sprint can too... and they will see that i'm rooted and void warranty. so am i completely screwed?

I had same issue.
I just reflashed the sprintlover rom (PC36IMG.ZIP) which came with Amon_RA recovery.
Then i installed the CM6 with Amon_RA recovery and everything works fine now.
Good that i did Titanium backup few days before

This is happening to me too. Almost everything he's describing is the same. Except I installed a gapps.zip and then it wouldn't boot after that. No matter what I flash, it either gives me a status 7 error and aborts the install or it may "install successfully" but it never boots. Also tried the pc36img.zip as well. I had a nandroid backup and tried to restore that, but that aborts saying cannot flash boot image. Tried a rooted and also an unrooted stock ruu, they won't work and the .exe version on a pc can't find my phone when I plug it in and power it on. Anyone have any Ideas for me. I can get more specific error messages and hboot numbers, etc. if needed.

I think you should get Amon recovery PCIMG zip file and change recovries and try everything again... IMO
Edit: I posted the Amon file and all you have to do is rename it to PCIMG.zip. Also I think the gapps you were looking for you can find on the cm site itself or within that thread. Sorry if it sounds like I a being negative but I see alot of people get on noob and I wondered why but unfortunately its because things like this happen. In the OP for CM6 it says to use Amon and backup your keys. Now if you get your phone backup you got to first check and make sure your RSA keys are in tact unless you backed them up already.
Joeykrim has a app on the market to check or there are numerous threads on what to do. Sorry and hope it works out for you if not INS is your friend
View attachment PC36IMG-Amon-V2.2.1.zip

playya said:
I think you should get Amon recovery PCIMG zip file and change recovries and try everything again... IMO
Click to expand...
Click to collapse
some people dont like clockwork with the evo's...thats just the general feeling im getting from the boards. i just got my evo rooted and what not. i use clockwork and it has worked well for what i need.
op, try amon like has been suggested.

tailsthecat3 said:
some people dont like clockwork with the evo's...thats just the general feeling im getting from the boards. i just got my evo rooted and what not. i use clockwork and it has worked well for what i need.
op, try amon like has been suggested.
Click to expand...
Click to collapse
Yea but have you tried Amon and from what I read and this is from developers Amon has a much better handle on things as far as backing stuff up, partitions and protection of keys.
I ran Clockwork on my wifes phone because to me its simple and works with Rom manager but after a while I just said F it and switched since it was messing up my backups. Hey to each his own..

Ok, I don't believe that your device is bricked. You may have flash the wrong gapps or something, but is should be easy to fix.
First, download these 3 files and put them on the root of your SD card:
Cyanogen 6 stable for evo
Latest gapps for HDPI
Calkulin's format all
Red through first, then follow my instructions EXACTLY:
1.) Boot into recovery.
2.) Flash Calkulin's all format. This will wipe everything that needs wiping. (everything but the SD card)
3.) Without exiting recovery immediately flash the CM6 .zip. Do not flash the gapps yet.
4.) Reboot the device now. It will boot into cyanogen, but will not have market or anything. Once fully booted, reboot to recovery.
5.) Do not wipe or anything, just flash the gapps HDPI.
6.) Boot the phone and enjoy.

Evo won't load any roms, can only get into clockwork recovery
Okay, so if I try your steps, just like before The install gets almost to the end, then I get:
"assert failed: write_raw_image ("/tmp/boot.img","boot")
E:Error in /sdcard/update-cm-6.1.2-supersonic-signed.zip
(Status 7)
Installation aborted.
Sorry Playya, I wanted to try this one more time first. I'm going to try loading Amon Ra now. do I need to rename it to pcimg.zip or should i just flash the current file name?
In case it helps anyone, I have
ClockworkMod Recovery v2.5.0.1
my boot loader screen shows
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
TOUBH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Oct 15 2010

Awesome, Amon Ra Worked, and now i'm up and running on cyanogen mod with google apps as well. My only problem now, is I can't backup, when I try it says oops... something went wrong! Please check the recovery log!

hcavlnch said:
Awesome, Amon Ra Worked, and now i'm up and running on cyanogen mod with google apps as well. My only problem now, is I can't backup, when I try it says oops... something went wrong! Please check the recovery log!
Click to expand...
Click to collapse
it may say oops if you battery level is low... I think Amon is so much better its just that Unrevoked puts Clockwork in with their root so people get lazy and leave it in... Amon - its the way to go.
1. Charge your battery and try again
2. Backup your wimax keys - then check how big the file is and hopefully its like 12 megs... If so keys may be ok

Evo Loops At HTC White Screen - No Recovery

I know I've seen other people with this problem, but I don't think I've seen a fix but I'm hoping I'm wrong.
Installed CM7 RC2 and everything works great for a month. Some random reboots but no big deal. Today I get a reboot but instead of reloading it hangs on the CM7 boot logo. I go into clockwork recovery, do a full wipe, and reboot. From then on, all I can do is loop in the white HTC screen. No ROM, no Recovery.
I've tried to flash Amon Ra recovery and a stock RUU via at PCImag file. No love. Any ideas?

BrashL said:
I know I've seen other people with this problem, but I don't think I've seen a fix but I'm hoping I'm wrong.
Installed CM7 RC2 and everything works great for a month. Some random reboots but no big deal. Today I get a reboot but instead of reloading it hangs on the CM7 boot logo. I go into clockwork recovery, do a full wipe, and reboot. From then on, all I can do is loop in the white HTC screen. No ROM, no Recovery.
I've tried to flash Amon Ra recovery and a stock RUU via at PCImag file. No love. Any ideas?
Click to expand...
Click to collapse
I posted directions in reply to your PM. Here's the first thing to try. See if you can flash this, it's Amon Ra recovery v2.3

k2buckley said:
I posted directions in reply to your PM. Here's the first thing to try. See if you can flash this, it's Amon Ra recovery v2.3
Click to expand...
Click to collapse
DONT FLASH IT.
Put in root of sdcard, boot into bootloader, update, let it boot or boot into recovery.

Lol, I gave him detailed instructions on how to flash it using the bootloader, don't worry. I was pm ing with him.
Sent from my PC36100 using XDA App

r916 said:
DONT FLASH IT.
Put in root of sdcard, boot into bootloader, update, let it boot or boot into recovery.
Click to expand...
Click to collapse
He uploaded a recovery image in a PC36IMG, so it NEEDS to be flashed in the bootloader.

Ive had the same problem for two days now and have tried everything in the book it seems. Using fastboot or manually from the bootloader, every pc36img.zip fails with an error at (8) partition update failed! or remote : 51 partition update fail. I can get the newest ruu to get me stuck at the four triangle error and then I have to flash PC36IMG_AmonRA-v2.3-hausmod_revA.zip just to get back to the htc boot screen loop (which at least lets me get back to bootloader to start the vicious cycle again) . ANY help would be greatly appreciated. Heck, even any way to make it presentable at a sprint store would even work at this point (since it says s-off I'm guessing someone in the line of repair will realize its been rooted.
p.s. I have never had any problem with my phone and have flashed just about every rom out there and I always do a full wipe and usually a format_all too. This happened about two hours after I flashed Kings UNleashed Ultra Blakk R3 ( it just did a reboot on its own and its been in this mess ever since)

100proof said:
Ive had the same problem for two days now and have tried everything in the book it seems. Using fastboot or manually from the bootloader, every pc36img.zip fails with an error at (8) partition update failed! or remote : 51 partition update fail. I can get the newest ruu to get me stuck at the four triangle error and then I have to flash PC36IMG_AmonRA-v2.3-hausmod_revA.zip just to get back to the htc boot screen loop (which at least lets me get back to bootloader to start the vicious cycle again) . ANY help would be greatly appreciated. Heck, even any way to make it presentable at a sprint store would even work at this point (since it says s-off I'm guessing someone in the line of repair will realize its been rooted.
p.s. I have never had any problem with my phone and have flashed just about every rom out there and I always do a full wipe and usually a format_all too. This happened about two hours after I flashed Kings UNleashed Ultra Blakk R3 ( it just did a reboot on its own and its been in this mess ever since)
Click to expand...
Click to collapse
Once you've gotten back into recovery, specifically, amon RA 2.3, use the MS-USB menu and copy the contents of your SD card onto an external disk drive. Afterwards, use amon RA to partition and reformat your card. When you're done, copy only the Rom and amon RA (PC36IMG) file to your SD card. Shut down your device. Now while pressing the down volume key, press the power button to enter the hboot screen and pay attention to see whether or not you still have S-OFF. If you do not, you need to re-root. If you do, great. Reflash amon RA and afterwards, reboot into recovery and flash the rom.
Just Me, D
via the XDA Premium app

Think we have different problems. Every time I try to flash something new it completes fine, but it still boot loops. Hell, yours might be fixable.
I've tried everything now with no luck. Everything updates and completes but has absolutely no effect on the boot looping. This is really insane and my advice to anyone would be to stop using CM7 immediately as it seems to be confined to that ROM.
If anyone else has had this exact problem please post, I want to get a tally of how many people are affected and try to find a commonality.

Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.

teh roxxorz said:
Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.
Click to expand...
Click to collapse
But my phone ran for a month without any problems except for some random reboots which seem to be common with this phone in general. I didn't add software or flash anything before this happened, it just happened. That seems to be the experience most people are having, the only thing in common is that they were running CM7 or had been running it recently and tried to flash to a different rom.
What software problem wouldn't be corrected by a successfully completed reflash with a stock RUU? That's the major question.

Hmm, that is awkward; at that point, I would just take it in if you're still getting random reboots. Been on CM7 for the longest and no random reboots on my end.

teh roxxorz said:
Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.
Click to expand...
Click to collapse
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....

dougjamal said:
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....
Click to expand...
Click to collapse
I agree, that is exactly what they should.

dougjamal said:
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....
Click to expand...
Click to collapse
I would love to, but I can't load any recovery. I've tried to flash amon ra and clockwork, and all seem to flash ok, but on reboot it's back to boot loop even if I try to go into recovery.

BrashL said:
I would love to, but I can't load any recovery. I've tried to flash amon ra and clockwork, and all seem to flash ok, but on reboot it's back to boot loop even if I try to go into recovery.
Click to expand...
Click to collapse
Try flashing amon_ra 2.3....place on sdcard, go into the bootloader, update,reboot, then try the bootloader. But before you do, select clear storage, which will do a factory reset, to see if that helps.

teh roxxorz said:
Try flashing amon_ra 2.3....place on sdcard, go into the bootloader, update,reboot, then try the bootloader. But before you do, select clear storage, which will do a factory reset, to see if that helps.
Click to expand...
Click to collapse
Already tried it, no dice. Goes through fine but then keeps bootlooping. On a side note, is there a way to get S-On through the bootloader since I can't access recovery?

You would have to download the RUU exe and then run the phone in fastboot while connected to the pc.

teh roxxorz said:
You would have to download the RUU exe and then run the phone in fastboot while connected to the pc.
Click to expand...
Click to collapse
Did that buy still S-Off

http://www.shipped-roms.com/shipped/Supersonic/ Did you run the right RUU for your software version?
And I'm heading tot he gym for ~1hr; you can pm me in the meantime and I'll answer when I get back if you still need assistance.

dougjamal said:
Once you've gotten back into recovery, specifically, amon RA 2.3, use the MS-USB menu and copy the contents of your SD card onto an external disk drive. Afterwards, use amon RA to partition and reformat your card. When you're done, copy only the Rom and amon RA (PC36IMG) file to your SD card. Shut down your device. Now while pressing the down volume key, press the power button to enter the hboot screen and pay attention to see whether or not you still have S-OFF. If you do not, you need to re-root. If you do, great. Reflash amon RA and afterwards, reboot into recovery and flash the rom.
Just Me, D
via the XDA Premium app
Click to expand...
Click to collapse
I'm sorry I wasn't clear . Days of reading every post in any thread I can find has left me running on no sleep. The huge problem is that no matter what recovery rom is flashed it wont let me boot into RECOVERY MODE. It flashes fine whether it is from the sd or through cmd using fastboot (Ive tried almost every version including the newest of both Amen RA and Clockwork). This gets me stuck in the white HTC screen boot loop. If I flash a RUU it will at least hang with a partition error and get stuck in the four triangle error, which will at least let you charge the battery so I can start all over again. Is there maybe a way to wipe the partition or reformat in fastboot as that is really the only thing working (regular adb wont detect). It seems a ton of people have been popping up with this same problem out of the blue the last few days.

Root + Flash Recovery was successful, but can't flash any roms?

Some background:
-This is my 4th Evo. Previous 3 were all rooted.
-Rec'd the new Evo last Thursday, rooted it immediately using the Auto Root method.
-Everything was successful, and Sprint Lover's ROM was automatically flashed on my phone, until I tried flashing a new rom.
Roms I tried flashing:
-MIUI
-BOS "Royal Liquid"
What happens:
-With MIUI, it flashes, restarts and then boots up all the way and then freezes after 20 secs and restarts, EVERY TIME.
-With BOS, stuck in bootloop. Keeps restarting at the white "htc EVO 4g" screen.
Tried both recoveries, Amon_RA AND Clockword Mod(CWM).
Yes, wiped every time. Even d/led "Calkulin's Format ALL" and flashed it (in Amon RA, it wouldn't let me in CWM.)
Please help, and ask me any questions you may need. I'll do my best to provide every answer.

I'm dealing with the same issues except i was trying to flash to Koni Elite 3

I'm can't even do a restore,cuz i get a recovery error.

Update i can do a recovery to an old backup

androidrookie84 said:
Update i can do a recovery to an old backup
Click to expand...
Click to collapse
Next time just update your same post or make a thread of your own. No sense of posting your problems in someone's else's problems thread. But I'm glad it's working for you now.
[Update]
Just d/led and flashed CM7 using ClockwordMod. Everything seems to be working fine.
I don't know what's going on anymore.
I am going to try to flash BOS Royal Liquid again and see what happens.

Make sure your device still displays "S-OFF" in the bootloader screen. Reflash amon RA or flash amon RA v2.3 and then go to the wipe menu and wipe EVERYTHING in it except the SD card itself. Now flash the rom you want to flash.
posting & replying via the XDA Premium app.

Yes Sir!
arozer said:
Next time just update your same post or make a thread of your own. No sense of posting your problems in someone's else's problems thread. But I'm glad it's working for you now.
[Update]
Just d/led and flashed CM7 using ClockwordMod. Everything seems to be working fine.
I don't know what's going on anymore.
I am going to try to flash BOS Royal Liquid again and see what happens.
Click to expand...
Click to collapse
Sent from my PC36100 using Tapatalk

dougjamal said:
Make sure your device still displays "S-OFF" in the bootloader screen. Reflash amon RA or flash amon RA v2.3 and then go to the wipe menu and wipe EVERYTHING in it except the SD card itself. Now flash the rom you want to flash.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
In the bootloader, my info reads:
SUPERSONIC EVT3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
Not sure if any of that means anything.
Also, I tried that, and nothing! =[
-D/led Amon_RA v2.3 from his post. Flashed it using Terminal Emulator.
-Flashed Calkulin's Format ALL
-Wiped everything but "SDCARD" and "SDCard:.android_secure"
-Flashed ROM BOS.. and same thing; bootloop...
One thing I noticed is that when I try to Wipe Dalvik Cache in Amon-RA, it says:
"Formatting DATA: dalvik-cache...
Formatting CACHE: calvik-cache...
Skipping format SDEXT:dalvik-cache...
DALVIK-CACHE: wipe complete!"
That 3rd line kinda has me worried.. I don't think I ever seen that before.
And when I try to Wipe Dalvik-Cache in CWM, it gives me:
"E: unknown volume for path [/sd-ext]"
even BEFORE I select "yes" from the menu.
Once I select "yes".. IMMEDIATELY it says "Dalvik Cache wiped."
I don't remember that either from my previous phones.
ALSO TRIED..
I just Flashed an older version of CWM(v2.5.0.7) that allows to flash Amend zips.
-Then tried wiping, and when I tried wiping "Dalvik-cache" this is what I got:
"E: Can't mount /dev/block/mmcblk0p2
(File exists)"
Could that be the problem?

[Another update..]
When I try to flash the Royal Liquid ROMS in CWM, it gives me an error saying something like:
"Cannot install because of Android 1.5 or something.
It was necessary to something something Android 3.0 Gingerbread" or something like that.
Does this mean I can only flash Gingerbread ROMS.. which is CM7 is the only one that works?

The error when trying to flash the BOS rom is because of how it is packed. A lot of people still like to packages their ROMs using an older way that I guess google and Kush are wanting to phase out. It should flash ok with clockwork 2.5 or Amon RA's.
With the reboot issue it sounds like something may have gotten corrupted on your phone. If you still have the autoroot folder on your computer try making a backup on just your Data and .android partitions, and then run the FlashZip script that comes with autoroot and use it to flash the PC36IMG_SprintLovers...zip. That one should give you a clean flash that you can work from. It may be a good idea to mount your sd card as a disk drive and scan it for errors too, a corrupt sd card can do all sorts of weird stuff.

xHausx said:
The error when trying to flash the BOS rom is because of how it is packed. A lot of people still like to packages their ROMs using an older way that I guess google and Kush are wanting to phase out. It should flash ok with clockwork 2.5 or Amon RA's.
With the reboot issue it sounds like something may have gotten corrupted on your phone. If you still have the autoroot folder on your computer try making a backup on just your Data and .android partitions, and then run the FlashZip script that comes with autoroot and use it to flash the PC36IMG_SprintLovers...zip. That one should give you a clean flash that you can work from. It may be a good idea to mount your sd card as a disk drive and scan it for errors too, a corrupt sd card can do all sorts of weird stuff.
Click to expand...
Click to collapse
Just tried it. Same thing bro.
What I did:
-Backed up CM7 in CWM.
-Flashed Amon_RA v2.3 via Terminal Emulator
-Backed up data and .android partitions in recovery
-Restarted phone and ran "FlashZip", chose Option 1 "SPrintLover....zip"
-Flashed it successfully.
-Restarted phone to make sure it works. Went back into recovery and wiped everthing (factory reset, cache, dalvik cache and data), also flashed "Format All"
-Tried flashing BOS and bootloop again.

arozer said:
Just tried it. Same thing bro.
What I did:
-Backed up CM7 in CWM.
-Flashed Amon_RA v2.3 via Terminal Emulator
-Backed up data and .android partitions in recovery
-Restarted phone and ran "FlashZip", chose Option 1 "SPrintLover....zip"
-Flashed it successfully.
-Restarted phone to make sure it works. Went back into recovery and wiped everthing (factory reset, cache, dalvik cache and data), also flashed "Format All"
-Tried flashing BOS and bootloop again.
Click to expand...
Click to collapse
Have you tried pulling your sd card to see if that could be doing it?
Sent from my PC36100 using XDA Premium App

xHausx said:
Have you tried pulling your sd card to see if that could be doing it?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I'm sorry, I don't know what you mean by "pulling the sd card". Care to elaborate?
Also an update:
While trying to get BOS to work, I was stuck in bootloop.
So I reflashed it again without wiping anything.
It bootlooped 4 times and then PHONE TURNED ON!! Using BOS rom.
However, same as MIUI, about 10 secs into it, the phone freezes and restarts.
What do you think it could be?
MIUI does the same thing, except the whole bootloop trial.

arozer said:
I'm sorry, I don't know what you mean by "pulling the sd card". Care to elaborate?
Click to expand...
Click to collapse
Try pulling the sd card out of the phone to see if anything changes. You can find it under the battery.
Sent from my PC36100 using XDA Premium App

xHausx said:
Try pulling the sd card out of the phone to see if anything changes. You can find it under the battery.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Lol. Wow bro, way to put it like that and make me feel silly.
I thought maybe "pulling the battery" has a different means in terms of rooting.
And yes, I re-flashed BOS and powered the phone off,
-removed SD card
-Restarted and again, stuck in bootloop.
Btw, did you see my update in my previous post?
Also, I thank you VERY much for taking your time to try and help me.
Seems like only Gingerbread based roms (like CM7) are working. I haven't tried any other ones, other than Sprint Lovers and CM7, but they seem to work perfectly fine without ANY problems.

Have you tried:
Pulling the battery, going back to recovery and wiping dalvik and cache again then rebooting (sorry if I missed you doing this)
or
Re-downloading the BOS ROM, could be a bad download, esp if downloaded from your phone
or
Flashing a completely different ROM like Unleashed, Myn, EViO or MikFroyo?

Sorry, didn't mean for it to come across like that. It's possible there is just something about that ron that doesn't want to work with your phone.
If you want to send me the logcat I can take a look at it for ya.
Sent from my PC36100 using XDA Premium App

jstalford said:
Have you tried:
Pulling the battery, going back to recovery and wiping dalvik and cache again then rebooting (sorry if I missed you doing this)
or
Re-downloading the BOS ROM, could be a bad download, esp if downloaded from your phone
or
Flashing a completely different ROM like Unleashed, Myn, EViO or MikFroyo?
Click to expand...
Click to collapse
Yes. Just tried that brother and doesn't work. (referring to 1&2)
I will try downloading another rom now.
Hopefully BOS and MIUI are just having their own problems, as CM7 works just fine.
xHausx said:
Sorry, didn't mean for it to come across like that. It's possible there is just something about that ron that doesn't want to work with your phone.
If you want to send me the logcat I can take a look at it for ya.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Where do I find the logcat? Sorry.. just don't to send you the wrong one.

Spiicytuna said:
Option #1
1. Download aLogcat from the market
2. Launch the aLogcat
3. Go launch the program thats crashing, allow it to crash
4. Go back to aLogcat
5. Menu -> Send
6. Email it to yourself, then post it on here for shinzul/toast + thread
Option #2
1. Hook your phone to your computer with the usb cable
2. With your fav CLI type: "adb shell logcat > crashlog.txt" (w/o the " ")
3. On the EVO launch the program that's causing problems, allow it to crash
4. In the CLI hit "crtl+c" (to stop the logging process)
5. In the same folder as adb will be a text file called "crashlog.txt"
6. Post it on here so that shinzul/toast + thread can take a look at it
Option #3
1. open terminal on your phone
2. if the character showing is a '$' type "su"
3. type "locat > /sdcard/logcat.txt"
4. post the logcat.txt file on your SD card on here so that shinzul/toast + thread can take a look at it
Click to expand...
Click to collapse
Instructions on how get a logcat

No roms will flash, they all hang on the white boot screen. Ever heard of this? wtf?

It is slowly driving me mad. I can get into recovery and restore my current ROM (leaked GB base). However, if I flash a new rom - any rom - it flashes, reboots into white HTC boot screen, and just hangs there.
I'm using ROM manager, clockwork.
What do I do? It doesn't make sense.
Thanks for any advice.
Later.

1. Stop using ROM Manager
2. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
3. Shutdown your device.
4. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
5. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
6. Go to the flash menu and flash the rom you desire to flash.
posting & replying via the XDA Premium app.

Did you try it? If so, how did it for for you?
posting & replying via the XDA Premium app.

I have had it take 3-5 min to get past the white screen, it happened with some custom roms. I thought it was hung also but it finally continued..how long did you wait?
Sent from my secret place where no-one can find me.

Oh wow, you are awesome. I really appreciate you taking the time to tell me that. Worked perfectly. If I could buy you a beer I would. Have a good one!
dougjamal said:
1. Stop using ROM Manager
2. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
3. Shutdown your device.
4. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
5. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
6. Go to the flash menu and flash the rom you desire to flash.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse

Sprockethead said:
Oh wow, you are awesome. I really appreciate you taking the time to tell me that. Worked perfectly. If I could buy you a beer I would. Have a good one!
Click to expand...
Click to collapse
(Laughing)...You're very welcome. I'm glad I was able to help. Enjoy the rest of your day.
posting & replying via the XDA Premium app.

Was having the same trouble. I think Rom Manager has some flaws cause it works fine from Recovery

Raehtz10 said:
Was having the same trouble. I think Rom Manager has some flaws cause it works fine from Recovery
Click to expand...
Click to collapse
ROM Manager has its uses, but, in my opinion, it is far too easy to simply boot or reboot into recovery and flash, especially with amon RA. It has a common sense menu layout.
posting & replying via the XDA Premium app.

Just MY opinion, but ROM Manager is useless. I see more people have issues because of ROM Manager. My advice, dump it and do everything in Recovery.

+1
Sent from "The" Evo using XDA Premium VIA your moms house. ™

Hmmm, so what happens if I'm still having this problem after trying this fix? I've been having the "can't flash any other roms because they all hang at the white evo4g screen" problem and have been stuck on the same rom for over a month now. Is there something else I can try if this doesn't work?

superhiro415 said:
Hmmm, so what happens if I'm still having this problem after trying this fix? I've been having the "can't flash any other roms because they all hang at the white evo4g screen" problem and have been stuck on the same rom for over a month now. Is there something else I can try if this doesn't work?
Click to expand...
Click to collapse
I would do a clean wipe, factory/data, cache, and dalvik, then go to the bootloader, select the clear storage for overkill, then try to flash a rom.

jayharper08 said:
+1
Sent from "The" Evo using XDA Premium VIA your moms house. ™
Click to expand...
Click to collapse
+1.....again

Thanks for the quick reply man. Tried the wipe of data, cache and dalvik, rebooted to bootloader and cleared storage. Tried to install a rom and still hung up at the htc evo 4g white boot screen. Anything else I can try?

Which rom are you trying to flash? I would re-download it to make sure its not corrupted in any fashion.

Hmmm I was wondering if that might be the problem, because I've gotten this rom to flash ONCE before. It's the End of Days rom from Magnus. I got it to work the first time I tried to flash it but then at some point I rebooted it and it started boot looping to the point where I couldn't get it to load anymore. That's when I wiped, tried to reflash the rom and all this madness started. I'll try to redownload, but I figured if the ROM worked once, it should be able to work again... right? I mean I'm not flashing it any differently.

superhiro415 said:
Hmmm I was wondering if that might be the problem, because I've gotten this rom to flash ONCE before. It's the End of Days rom from Magnus. I got it to work the first time I tried to flash it but then at some point I rebooted it and it started boot looping to the point where I couldn't get it to load anymore. That's when I wiped, tried to reflash the rom and all this madness started. I'll try to redownload, but I figured if the ROM worked once, it should be able to work again... right? I mean I'm not flashing it any differently.
Click to expand...
Click to collapse
It should work.
http://dl.dropbox.com/u/19699565/PC36IMG.zip Place that on your sdcard, boot into the bootloader and flash it. That'll reflash the amon_ra 2.3 recovery, then try flashing the rom again.

Yea I tried the Pc36img thing already too. Let the bootloader find it, applied the update, rebooted into recovery, reflashed, nothing. Same results, hung up on white evo screen.
I'm actually noticing that when I try to wipe the "sd ext" in Amon Ra's wipe menu, it just says "skipping format sdext" or something like that, is that normal?

superhiro415 said:
Yea I tried the Pc36img thing already too. Let the bootloader find it, applied the update, rebooted into recovery, reflashed, nothing. Same results, hung up on white evo screen.
I'm actually noticing that when I try to wipe the "sd ext" in Amon Ra's wipe menu, it just says "skipping format sdext" or something like that, is that normal?
Click to expand...
Click to collapse
That's normal; it only says that because you don't have that partition. The only thing I can think of at this point would be to backup everything, quickly unroot, then re-root.

My Evo is doing something similar. I flash ANY of the new Sense 2.x (or Sense 3.0) ROMs, and they just reboot on the white HTC EVO 4G screen. Ive wiped everything, used Calks Format All, Im using the latest Amons, etc to no avail. However, all AOSP GB ROMs (MIUI,CM7, EoD, etc) work like a charm! Any kind soul that knows what the hell is going on with my phone?

[SOLVED] Looking to update from CM7.2 to an ICS ROM

Ive always been running CM roms since I got the phone nearly two years ago, but recently have been reading too many good things about ICS roms. My phone has been laggy as of late, and honestly after nearly 2 years, I wanna see and try something new. I've been reading some stuff about updating 4EXT or something like that. Can someone link me or explain in great details how i do this? What is it? And if I do that, will i still be able to run my old CM rom if i decide the ICS roms arent for me? I dont want to be unable to roll back.
Whats the best ICS roms out there right now?
Many thanks!
___________________
SOLVED AFTER A STEP BY STEP INSTALLATION WITH KB!! MANY THANKS
Sent from my T-Mobile G2 using xda app-developers app

mapheG2 said:
Ive always been running CM roms since I got the phone nearly two years ago, but recently have been reading too many good things about ICS roms. My phone has been laggy as of late, and honestly after nearly 2 years, I wanna see and try something new. I've been reading some stuff about updating 4EXT or something like that. Can someone link me or explain in great details how i do this? What is it? And if I do that, will i still be able to run my old CM rom if i decide the ICS roms arent for me? I dont want to be unable to roll back.
Whats the best ICS roms out there right now?
Many thanks!
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
Depends on your definition of best, personally I like EliteMod ICS (in my signature) but you may want to try out Andromadus Mimicry 1.3.0, it's pretty nice out of the box and has a graphical installer (aroma).
Just be aware that due to the fact that the Desire-Z/G2 does not have an official ICS release, that some things such as hardware drivers have their limits.
1) Camera drivers are not fully available, so the camera won't function as well as it would have on a GB rom.
2) No Wireless-N, also due to drivers, but Wifi-B/G are available.
and a number of other smaller issues which are mentioned varying on the roms, but the two above are the most common complaints, something to keep in mind before you start updating the thread about lack of it.
4EXT Recovery is just another recovery, like ClockworkMod is another recovery.
I personally prefer 4EXT Touch Recovery ( http://www.4ext.net/ has the app to install it ), but both ClockworkMod (what you may have now) and 4EXT can create backups, and restore your backups to the phone (just make sure you do a factory-reset/wipe cache, when you're flashing a brand new rom on, and when you wish to restore a backup.)

So i can flash ics roms with clock work mod and not use 4ext?
Sent from my T-Mobile G2 using xda app-developers app

mapheG2 said:
So i can flash ics roms with clock work mod and not use 4ext?
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
You can, they're both recoveries and will both apply a rom zip. I just find 4EXT to have quite a bit more features that pertain to ICS (i.e.: the ability to convert some of your partitions from the older ext3 filesystem to the ext4 filesystem which is better, but not all roms support it, most ICS roms do though), as well as the ability to do tar-based backups (compresses, smaller backup size), and the paid version of the app lets you configure a number of settings in 4EXT (much like the paid version of Rom Manager).
Just don't flash roms via the app, always do that from the actual recovery, or you risk causing problems.
Generally speaking: Reboot into recovery (you can do this from the power menu in CM7.2)
1) Perform a backup of your currently installed Rom to the SD card
2) (toggle USB storage and copy over the rom zip if you haven't already done so)
3) Perform a Factory Reset/Wipe and wipe cache
4) Goto Apply zip from SD Card and select the new ROM
5) Flash any additional zips you want on top, google apps, wifi calling, etc (note the thread for any specifics, for example Mimicry doesn't come with Google Apps so need to flash the ICS google apps if you want them, where as EliteMod includes a custom set of google apps already)
6) reboot and enjoy.
If you decide you don't like it, just repeat the above steps, just do a restore at #4 and reboot.
Both of the ones I mentioned (mimicry, elitemod) by no means require a swap partition or sd-ext partition, but you can partition the card via either clockworkmod or 4EXT, just skip the sd-ext2 option (since elitemod doesn't support a secondary one [and not much point either). And don't set a sd-ext size less than 1.5GB (no sense in making it smaller than your /data partition).
For both though, skipping an SD swap is advised, I only have SD swap on mine cuz no other rom I know of supports dataswap and I'd rather have my SD Card partitioned already to test out other roms than to re-do the SD Card each time (since you gota make sure to back up the content of the SD Card to the PC). 4EXT though will let you repartition the SD card without erasing the FAT32 partition, where as clockworkmod will always wipe the whole card before repartitioning (it's just easier to partition from scratch though).

Yeah the whole partition and swapping was the confusing part. But good to hear I don't have to do any of that. I did see the gapps zip included in the mimicry thread, but where can I find a wifi calling apk to install? Also +1 thanks to u for the detailed reply! Thanks!
Sent from my T-Mobile G2 using xda app-developers app

mapheG2 said:
Yeah the whole partition and swapping was the confusing part. But good to hear I don't have to do any of that. I did see the gapps zip included in the mimicry thread, but where can I find a wifi calling apk to install? Also +1 thanks to u for the detailed reply! Thanks!
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
In Mimicry the Aroma installer will actually let you pick that option during the graphical install. It's one of those roms that presents you with a nice installation menu after you select the zip to be applied. Just bear in mind though you need the 26.13.04.19 radio in order to use the T-Mobile Wifi calling app (and course be on T-Mobile). EDIT If you're one of those people who end up getting no WIFI at all after flashing the Wifi calling app from the aroma installer and have the 26.13.04.19 radio, in the first post of the mimicry thread there's a mention of a Wifi-Fix app you can install that might be able to fix that.
For EliteMod ICS, you would apply it by downloading the zip in my signature (for the wifi calling) and flashing that after flashing the rom. But again, needs the 26.13.04.19 radio, as the app won't work with an old radio (26.03.*)
The thread on applying the radio is also linked from my signature , if you're on a T-Mobile G2, you can just grab the first 26.13.04.19 zip file, rename it PC10IMG.zip just like the instructions say there, put it on the SD Card, reboot into the boot loader and apply the radio. Also if you're planning on flashing either mimicry or Elitemod immediately after flashing the new radio, both roms already Clean your EFS partition for you when you install them in recovery, so you don't have to run the EFS wipe zip (something you normally need to flash in recovery after changing a radio).

KB suggested EliteMOD to me a few days ago,...... Gota say it is running vnice at the moment, highly recommend it. w/ SD EXT, no swap.

I downloaded the zip file from the Andromadus thread, and proceeded to flash the ROM. It says the flash was successful, however upon rebooting, I would see the HTC screen but it would never make it to the boot animation. I would just get a black screen. I tried flashing through ClockWorldMod v5. I cleared all data and caches, and then flashed the ROM.. still not working?

mapheG2 said:
I downloaded the zip file from the Andromadus thread, and proceeded to flash the ROM. It says the flash was successful, however upon rebooting, I would see the HTC screen but it would never make it to the boot animation. I would just get a black screen. I tried flashing through ClockWorldMod v5. I cleared all data and caches, and then flashed the ROM.. still not working?
Click to expand...
Click to collapse
What's the exact details of your phone, i.e.: hboot information and radio version.

I flashed the radio from your signature. Hboot information: 0.82.0000
blkjack said I needed to do a superwipe. If that is the case, how would I perform one?

mapheG2 said:
I flashed the radio from your signature. Hboot information: 0.82.0000
blkjack said I needed to do a superwipe. If that is the case, how would I perform one?
Click to expand...
Click to collapse
hboot in my signature is a 0.84.2000 which is a desire-z engineering hboot.
0.82.000 would be an S-ON hboot which you wouldn't be able to change much at all. (which would be odd if you managed to get the 26.13.04.19 radio flashed, while S-On since it wouldn't normally allow you to).
May want to reboot into the boot loader mode and verify all your hboot information.

kbeezie said:
hboot in my signature is a 0.84.2000 which is a desire-z engineering hboot.
0.82.000 would be an S-ON hboot which you wouldn't be able to change much at all. (which would be odd if you managed to get the 26.13.04.19 radio flashed, while S-On since it wouldn't normally allow you to).
May want to reboot into the boot loader mode and verify all your hboot information.
Click to expand...
Click to collapse
I flashed a radio in the past. And it clearly says I have S-OFF on the top. I had the (26.03.02.26) radio before. And it did successfully flash the radio linked from your signature. HBoot says 0.82.0000. Where to go now?
EDIT: I found this link (http://forum.xda-developers.com/showthread.php?t=1044992) but dunno if this is outdated or not. If not, which of the three files do I want?

mapheG2 said:
I flashed a radio in the past. And it clearly says I have S-OFF on the top. I had the (26.03.02.26) radio before. And it did successfully flash the radio linked from your signature. HBoot says 0.82.0000. Where to go now?
EDIT: I found this link (http://forum.xda-developers.com/showthread.php?t=1044992) but dunno if this is outdated or not. If not, which of the three files do I want?
Click to expand...
Click to collapse
I think, the -=SuperWipeG2+=-.zip should be the right one, but as I'm not sure, I did a quick Google search for you and found this:
EdKeys said:
I recently flashed the new 4EXT Mod of ClockworkMod Recovery. The 4EXT Recovery is based off of Koush's CWM Recovery but offers additional power options, one of which is the ability to show the file system format your partitions are formatted in. To my surprise my system was formatted in the Ext 4 format and my data and cache partitions were formatted in Ext 3. The new 4EXT Recovery offers the option to convert the format without deleting any of the data. Your ROM will stay intact after the conversion. I selected that option and changed my data and cache partitions to ext 4 to match my system, rebooted, and notice quite an improvement in speed and smoothness in my current CM7 Nightly. After looking into it further I found out that the SuperwipeG2 that many of us have been flashing is formatting our partitions in the Ext 3 format. The reason only my system was formatted in ext 4 is because I used ClockworkMod Recovery the last time I did a full wipe to first flash the Superwipe, and then I immediately formatted system again with ClockworkMod Recovery. If you've used SuperwipeG2 to do a wipe, more than likely your system, data, and cache partitions are now Ext 3. You might want to check with your ROM developer to see if your ROM will run on the Ext 4 format. If its a CM7 based ROM, it will.
You can find more information about the Ext 4 format here.
Tsubus has since modified SuperwipeG2 so that it now formats the partitions into ext 4 when you flash it. I've used it and it also includes the EFS wipe. You can find it here. As I said, if there is no reason to wipe right now the new 4EXT Recovery can convert your partitions if you choose if they are in currently Ext 3. At the very least you can see what format they're currently in with 4EXT. I highly recommend it. You can always flash back to CWM Recovery if and when you choose. The partitions will remain Ext 4 once you choose to convert.
UPDATE: Several users have reported that checking partition information with Terminal Emulator is not reliable.
Click to expand...
Click to collapse
This one should definitely be the right one.
Besides that, the problem might also be a bad download, as your symptom fits a known issue in blk_jack's thread:
blk_jack said:
...
Q) After flashing I'm stuck at the HTC logo screen!
A) This is likely the result of a bad download. Check your downloaded md5sum hash against the one listed next to the download link above.​...
Click to expand...
Click to collapse

I thought it was a bad download too, so I downloaded from one of the mirrors. Still the same problem.

mapheG2 said:
I thought it was a bad download too, so I downloaded from one of the mirrors. Still the same problem.
Click to expand...
Click to collapse
So you did not check the MD5 hash?

Im a bit of a noob and all of this wasnt around when I was flashing CM roms ages ago. How do I do that? Would that fix my issue??
Sent from my T-Mobile G2 using xda app-developers app

mapheG2 said:
Im a bit of a noob and all of this wasnt around when I was flashing CM roms ages ago. How do I do that? Would that fix my issue??
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
An MD5 hash is something like a fingerprint of a file and it was definitely there when you first flashed CyanogenMod ROMs. The MD5 hash/sum is used to compare two files because it is possible that a downloaded file is slightly different from the original file due to mistakes that could have happened during transfer. So "checking the MD5 hash" means using a program to calculate that "fingerprint" of your downloaded file and comparing it with the "fingerprint" mentioned in blk_jack's thread. If the file you have downloaded is slightly different, its MD5 hash will be different from the MD5 hash that it should have and thus will be unusable and lead to a phone being stuck at HTC boot logo.
By the way, downloading a file from two different mirrors doesn't exclude the risk of getting a corrupt file.

I ran "md5 update.zip" from my Mac's desktop where the file is located. I was returned MD5 (update.zip) = 2a314e5f1361825c83a354aea38c6c4b .. which matches the md5sum of what was given. What next?
And I noticed you have the same H-Boot information that KB was talking about earlier, so I guess that can't be the problem either. Should I just try to Superwipe?

mapheG2 said:
Ok, so if it is a bad download, how do you remedy it? Because there are only so many options to download the ROM right. And what program are you referring to
Click to expand...
Click to collapse
There are actually lots of programs to calculate an MD5 hash. If you are on Linux it usally is as easy as typing md5sum <path to file> in a shell and reading the output. If you are on Windows, I'd recommend a Google search for "md5 generator" or something like this. Maybe even your recovery is able to calculate a file's MD5 hash - I'm using 4EXT and it definitely is, though I don't know if ClockwordMod is.
You can't remedy a bad download except trying to download it again, hoping that the file will be transferred right.
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
mapheG2 said:
I ran "md5 update.zip" from my Mac's desktop where the file is located. I was returned MD5 (update.zip) = 2a314e5f1361825c83a354aea38c6c4b .. which matches the md5sum of what was given. What next?
And I noticed you have the same H-Boot information that KB was talking about earlier, so I guess that can't be the problem either. Should I just try to Superwipe?
Click to expand...
Click to collapse
Oh, sorry - didn't update the thread's page before submitting my reply.
Just try it, there should be nothing wrong with it.

Okay, I read that I should manually clear all the data and cache first and THEN run the superwipe, followed by installing the ROM right? And I will be downloaded from the thread I listed because I still have ext3 I guess and don't want to deal with a ext4 change right now.