Develop Bugs

[Q] Need a custom rom that I can activate my EVO on: Tried everything I can think of!

I have cm6, rooted via simpleROOT. Hboot 0.76.2000, and NANDunlocked
I updated to Clockwork 2.5.0.1
I can only seem to boot to CM6 Roms including nightlys. And I cannot ACTIVATE my phone with CM6, I have my MSL but they dont work with the dialpad.
Need to know what to do here, Ive had my previous EVO that was activated, but took it off because the employee plan didnt allow it. I had an insurance claim on it so I got a new one and decided to wait until they allowed it on employee plans. ( which is today)
I was using the phone unactivated and tied to wifi for the last few months now ( can do everything except call/text/gps) However now that its allowed on an account I want to do everything else with it. I installed CM6 because I need an HID profile for keyboard/mouse/wii remote ( works great as a portable emulator entertainment center)
From what I understand I need to go to a stock rom or stock rooted rom to activate. Ive downloaded the following:
OMJ_EVO_2.2 - Error 7
CM6 Nightly sept 23- Installs but cant activate
CM6 RC1- Installs but cant activate
Fresh-Evo 3.3- error writing recovery: No space left on device
SteelROM-error writing recovery: No space left on device xda
Evo-Froyo-2.2 Rooted Stock Odexed- error writing recovery: No space left on device xda
BakedSnack 1.7: error writing recovery: No space left on device xda
So.. Before EVERY FLASH:
Ive cleared dalvik cache, wiped ALL PARTITIONS, Cleared cache, Wiped all data, went under advanced and cleared everything except the sd card, ive swapped sd cards.
Wtf is going on here.
Why will only CM6 roms install but NO OTHERS will?

Also I have never messed around with Kernels..
When i originally rooted it was in August.. Used the Simpleroot program 1.47 i believe, i was already on 2.1 and went immediately to cm6 and have been there since.
Im seriously at the point where I will paypal someone 5 bucks if you can give a solition that will work and I can stay rooted.
Just tried rooted_stock.zip
Got this:
E: Error finishing BOOT:
E: Failure at line 79
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.

Have you tried to use Amon's RA Recovery to flash your ROMs? You can flash RA Recovery via ROM Manager. Just open ROM Manager and then scroll to the bottom and press Flash Alternate Recovery. After that, try flashing a ROM again and let's see what happens this time. Just remember - with RA you need to keep your zip files on the root of your SDcard. Maybe this will work out for you, maybe it won't. Good luck.

Yes im going through the process of flashing every rom now with RA recovery
Im getting Error Writing Boot: Failure at line 82 for Supersonic-mynOTA
Did OMJ_EVO and got Failure at line 85 Error writing boot no space left on device.
This is ****ing annoying.
I dont think its possible that i downloaded 8 bad roms and magically CM installs fine any nightly from june till current is no problem.

So i got RA recovery to get fresh-evo to ALMOST install..
It will write
data
system
symlinks
set permissions
as soon as it get to boot.img i get :
assert failed: write_raw_image ("/tmp boot.img".
E: Error in /sdcard fresh-evo-3.3.0.1.zip
(status 7)
It appears that EVERY ROM except anything from Cyanogen will screw up when it gets to the boot.img
Any ideas?

Fixed my issue.
I had to reinstall everything as if i was going the root method to get a stock 2.1 rom on there. PC36IMG method
Thank god i saved my simpleroot and old roms when i originally rooted.
Now im reflashing cm6 after and its working.
Thanks for the help

I'm glad to hear you got everything sorted out Now, on to the fun stuff!
Have a good one.

Help, What is wrong with my recovery!?

Think i messed everything up now:
e:Can't chown/mod /data/sd
(no such file or directory)
e:failure at line 10:
set_perm 0 0 0777 DATA:sd
I have no idea what the hell that means. Think I fried my SD card
This is what I get!!!
also...
e: can't symlink /system/xbin/[
e: failure at line 14:
symlink busybox system x:bin/[
little confused

Since I got no reply, i used hboot to go to stock. I cant believe I am back at stock.

Were you already rooted, or did you use unrevoked just now? It's kind of hard to point you in the right direction based on the info provided. You don't even mention which recovery you are having an issue with.
My girl just her Evo last week, and I used Unrevoked to root it. I immediately flashed the engineering SPL right after, and when I tried to flash a ROM, I got a similar message about it not being able to chmod. However, all I did was wipe and try again, and it worked. I was able to flash the new ROM and have not looked back since.
I'm thinking maybe it was a hiccup similar to what happened to me the other day. Did you try wiping and doing it again? You have a lot of posts on here so I don't think you're a noob, but without more details, it's hard to point you in the right direction.
What root method did you use or were you trying to use?
What recovery are you using?
What ROM were you flashing?
Did you wipe everything before flashing the rom?
Did you try redownloading the file you were flashing to make sure you don't have a corrupted file?

What root method did you use or were you trying to use?
I used hboot like a boss method.
What recovery are you using?
Amon RA_1.8.
What ROM were you flashing?
MYN's RLS4
Did you wipe everything before flashing the rom?
Wipe eveything through recovery, factor, cache, dalvik, batt, and rotate.
Did you try redownloading the file you were flashing to make sure you don't have a corrupted file?
Redownloaded multiple times. I tried to go back to stock but it kept giving a android.process FC. So i went to best buy and got a new one. They didnt have any more so I settled with a white.

marcusva79 said:
What root method did you use or were you trying to use?
I used hboot like a boss method.
What recovery are you using?
Amon RA_1.8.
What ROM were you flashing?
MYN's RLS4
Did you wipe everything before flashing the rom?
Wipe eveything through recovery, factor, cache, dalvik, batt, and rotate.
Did you try redownloading the file you were flashing to make sure you don't have a corrupted file?
Redownloaded multiple times. I tried to go back to stock but it kept giving a android.process FC. So i went to best buy and got a new one. They didnt have any more so I settled with a white.
Click to expand...
Click to collapse
Hold on, I'm confused now. In your second post, you said you had to go back to stock, but now you're saying it's a new phone. Have both phones given you the chmod error, or was it the one you returned?
Also, the "like a boss" method is for people with the 2.02 hboot. The Evo I just rooted for my girl is white, and it was a 0003 version that had the 1.96 hboot (or whatever the exact number is). If this root method is ONLY for 2.02 phones, that could explain why you were getting the error.
I would just try the Unrevoked method. I can't begin to tell you how easy it was compared to what I went through in June when I rooted mine.

rugedraw said:
Hold on, I'm confused now. In your second post, you said you had to go back to stock, but now you're saying it's a new phone. Have both phones given you the chmod error, or was it the one you returned?
Also, the "like a boss" method is for people with the 2.02 hboot. The Evo I just rooted for my girl is white, and it was a 0003 version that had the 1.96 hboot (or whatever the exact number is). If this root method is ONLY for 2.02 phones, that could explain why you were getting the error.
I would just try the Unrevoked method. I can't begin to tell you how easy it was compared to what I went through in June when I rooted mine.
Click to expand...
Click to collapse
I think I had messed up my recovery and tried to go back to stock. I did go back to stock with my older phone, but always got FC's so I just went and returned it today at Best Buy and got the white one.
It does in fact have:
HBOOT 2.02.000000
3.30.621OSA
Like a boss method should work correct?

Like a boss method should work, yes. It specifies that particular hboot. However, it requires a lot of ADB and if you made a typo on any one line, who knows what part of the process can be affected? If you have your heart set on doing it the long way, then try again and just be very careful when typing to make sure everything is exact.
Read the first few lines of the "like a boss" thread carefully. The OP states people had problem with the recovery and that there is a custom recovery in a PC36IMG.zip format available for download on that same thread. Did you use that specific recovery when you tried?

The one that was specified in the like a boss thread was the one I used. On my old phone I rooted successfully. Later on though I was trying to flash another rom and thats when the recovery started acting up giving me all these errors chmod, installation abort, etc..... using PC36IMG.zip. I will be okay I have helped others root it that way to as well. It be nice to have a wingman helping me out to as weel hahahah

CDMA Desire has NO recovery after using unrEVOked...halp!

Ok, so after running the latest version of unrEVOked on my CDMA (U.S. Cellular) Desire, everything seemed to work smoothly, unrEVOked said "Done" on the PC end, but at the end, on my handset I get this error...
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log
E:Error in /data/local/unrevoked-forever.zip
(Status 42)
Installation aborted
Failure at line 1:
install_zip DATA:local/unrevoked-forever.zip
I thought okay no big deal, it didn't flash Clockwork and stayed S-ON. No big deal... But, problem. It did "attempt" to flash Clockwork, so now my recovery image is indeed Clockwork but it's a completely non-functional version of it, leaving me with literally no recovery at all, which is obviously a problem. I've searched high and low through these and about 5 other forums and I've seen a few other people that had the same error occur, but never anybody that found a solution or anybody that mentioned that they literally did not have a functioning recovery system, even the stock recover. So, again... HALP! I'm by no means an expert but have had and flashed Android devices for around a year now and this one has me puzzled.
Oh, and before anyone asks. HBOOT version 0.98, Radio/baseband of 2.05.10.08.11
When I reboot into recovery, it shows the Clockworkmod Recovery UI that I'm used to (actually prefer Amon's but... nevermind) but any time I select anything within the Clockwork UI it just goes to a blank black screen. A battery pull is required to reboot and then it's back to normal. Oh, and I do actually have root within Android itself. Sorry for the long winded post but this one's driving me nuts. Thanks for any help guys.
Edit: And the Soff.log basically just repeats what I mentioned above, @PID: 88, "BRAVO_C" Got radio version: 2.05.10.08.11 E:Unsupported radio version, update failed.
Is it simply that unrEVOked doesn't support this particular CDMA Desire yet?

jjones1983 said:
Ok, so after running the latest version of unrEVOked on my CDMA (U.S. Cellular) Desire, everything seemed to work smoothly, unrEVOked said "Done" on the PC end, but at the end, on my handset I get this error...
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log
E:Error in /data/local/unrevoked-forever.zip
(Status 42)
Installation aborted
Failure at line 1:
install_zip DATA:local/unrevoked-forever.zip
I thought okay no big deal, it didn't flash Clockwork and stayed S-ON. No big deal... But, problem. It did "attempt" to flash Clockwork, so now my recovery image is indeed Clockwork but it's a completely non-functional version of it, leaving me with literally no recovery at all, which is obviously a problem. I've searched high and low through these and about 5 other forums and I've seen a few other people that had the same error occur, but never anybody that found a solution or anybody that mentioned that they literally did not have a functioning recovery system, even the stock recover. So, again... HALP! I'm by no means an expert but have had and flashed Android devices for around a year now and this one has me puzzled.
Oh, and before anyone asks. HBOOT version 0.98, Radio/baseband of 2.05.10.08.11
When I reboot into recovery, it shows the Clockworkmod Recovery UI that I'm used to (actually prefer Amon's but... nevermind) but any time I select anything within the Clockwork UI it just goes to a blank black screen. A battery pull is required to reboot and then it's back to normal. Oh, and I do actually have root within Android itself. Sorry for the long winded post but this one's driving me nuts. Thanks for any help guys.
Edit: And the Soff.log basically just repeats what I mentioned above, @PID: 88, "BRAVO_C" Got radio version: 2.05.10.08.11 E:Unsupported radio version, update failed.
Is it simply that unrEVOked doesn't support this particular CDMA Desire yet?
Click to expand...
Click to collapse
Hmm, I PM'd you but I noticed something else. When you are trying to select a menu option on Clockwork, are you pressing power? That will give you that black screen. You should be using the optical trackpad button to select.

I am indeed using power, I came from the EVO. If it's something that silly I'm going to feel like a moron. Let me give it a shot.
Sent from my PB99400 using XDA App

Well if that wasn't the most noobish mistake I've ever made, I'm not sure what is. I assume it wouldn't hurt to try and flash unrevoked-forever.zip though recovery now to try and obtain S-OFF?
Sent from my PB99400 using XDA App

<shakes head in shame> Move along. Nothing to see here. Everything is fine now, and tons of thanks for your help man.

jjones1983 said:
<shakes head in shame> Move along. Nothing to see here. Everything is fine now, and tons of thanks for your help man.
Click to expand...
Click to collapse
Enjoy your phone!

I am now. Flashed Cyanogen and been getting everything set up. It's tough to find CDMA Roms which is unfortunate. As much as I like CM some options would be nice. Tried Ultimate Droid which I was a fan of on the EVO but it was buggy as hell on this handset.
Sent from my HTC Desire CDMA using XDA App

jjones1983 said:
I am now. Flashed Cyanogen and been getting everything set up. It's tough to find CDMA Roms which is unfortunate. As much as I like CM some options would be nice. Tried Ultimate Droid which I was a fan of on the EVO but it was buggy as hell on this handset.
Sent from my HTC Desire CDMA using XDA App
Click to expand...
Click to collapse
MIUI is another great ROM. It's what I've been running for awhile. Very few bugs and it looks pretty slick.

I loved MIUI on my EVO, I didn't realize it was available for this handset. If only I could hit that "thanks" button again.
Swyped from my Desire on CM 6.1

We should make a MIUI fanboys club :cD
Sent from my HTC Desire using XDA App

i have this problem too, please help

[Q - SOLVED!] "Verification Signature Failed" on ROM Install

Hey people, I've search far and wide, both on-forum and off-forum, and I cannot find a solution (it's quarter to 10pm EST and I've been searching since about noon EST... sigh)...
ISSUE:
- Had AuraxTSense running fine, but wanted to cook a custom using www.cookmyrom.se (recommended off of XDA-forums)
- Tried numerous times, using either AuraxT or Leedroid, cooked, downloaded and installed only to be reverted back to RelfexTSence, which I had BEFORE AuraxTSence. Odd, since Aurax was my most recent ROM, NOT Reflex... WEIRD, I KNOW!
- Ever since that, I cannot install any ROM. Install will fail, citing "Verification Signature Failed", "Installation Aborted".
THINGS I'VE TRIED:
-disabling verification (it's disabled by default, however, I enable it, then disable it just to make sure)
- Re-cooking, re-downloading, re-installing numerous, I stress, NUMEROUS times
- clearing all sorts of caches before AND after installs
- Wiping, re-formatting and re-partitioning SD Card (only thing I backed up was pictures and a kernel, but I didn't even restore because I couldn't get a ROM to work (re: issue above)
- tried installing via Rom Manager as opposed to via clockwork = still didn't work
SPECS/INFO:
- HBoot 0.83.xxx something
- Clockwork Recovery 0.2.5.7
- unbranded, rooted HTC Desire
- Last-running kernel was Coutts .975mV
- Last correctly running ROM was AuraxTSense (with new sense, apps2sd+ etc.)
- Second last correctly running ROM was ReflexTSense (yadda yadda)
- Third last correcetly running ROM was Leedroid (Can't remember the version, maybe d?)
But it keeps reverting to a half, slow, cheap install of ReflexTSense (no disrespect to the author of ReflexTSense, the ROM was great, it's my phone that makes it a crap experience)...
HELP! lol
Thanks a ton in advance!

Is the file verification enabled? If so disable it. If that doesn't work, make a Goldcard.

Thanks for the reply mate. I've read a bit about this "goldcard" business, but I can't seem to understand it.. have a link or anything, maybe a guide? I can't seem to pull anything useful up (sigh, after 10 hours or searching XDA + Google)...
Also, yes, verification was off :/

Gold card isn't needed to flash a custom ROM so don't worry about that. Chances are its the signature verification being turned on. Turn it off and it should work

It isn't but if disabling the signature verification in recovery isn't helping then making a Goldcard is the fastest way to go about it instead of farting around with a load of s**t.

Gold card only lets you flash a stock RUU from a different build then your original one. It does nothing for flashing custom ROMs

Have you tried switching from Clockwork Recovery 0.2.5.7 to AmonRa Recovery minimum 2.0.0? I don't know about Clocwork recovery options, as I used it only briefly, but the newer versions of amonra allow you to switch verification OFF. Give it a shot.
P.S. I use version 2.0.0 - the option is in the meniu -> other -> Toggle Signature Verify
Later edit: BTW, your version of Clockwork recovery is quite old - I've seen some 3.0 version talk here http://forum.xda-developers.com/showthread.php?t=897026

Thank you all for the replies. Clockwork DOES allow you to turn signature verification off, however as Stefen mentioned, it might be outdated. I'll first try to update clockwork since I'm familiar with it. If not, I'll try switching to AmonRa Recovery. Thank you all for the suggestions so far, I'll post back if solved!

Alright, so I cannot upgrade/downgrade my clockwork recovery, it just doesn't work. I've followed all steps (I AM technologically literate) to no avail...
What to do.......... ?

You need to either be S-OFF or re-run unrEVOked to update it. What have you tried to do?

EddyOS said:
You need to either be S-OFF or re-run unrEVOked to update it. What have you tried to do?
Click to expand...
Click to collapse
I have tried:
- disabling verification signature, then flashing
- wiping, literally, everything there is to wipe, then flashing
- updating recovery through HBoot (unsuccessful)
- updating recovery through ROM Manager (error on every version except current version I have)
- tried numerous ROMs that HAVE worked every time until recently (both verified through Desire Development threads, i.e. Leedroid, AuraxTSense etc., and custom cooked ROMs off of www.cookmyrom.se)
Specs:
- Desire AMOLED
- HBoot-0.83.0001
- Radio-4.08.00.09
- Current ROM: AuraxTSense (New Sense HD) -> It forces me on it
- Kernal: 2.26.32.26 [email protected] #34
- Recovery: Clockword Recovery 2.5.0.7
If I'm missing anything, ask me and I'll give you the info.

I mean you can ONLY update CWM by running unrEVOked again and pointing it to a newer version or do it once you've S-OFF - no other way will work

Oh ok, I understand now.. however, is updating my CWM the way to fix this issue?
I've read that CWM 3.0.0.0 and up only read Edify, meanwhile lots of ROMs are still zipped using the older-based script... So far, everyone reports 2.5.7.x to be working. Unfortunately, I'm stuck in a "no-flash-anything" zone :/

No idea, I use AmonRA

I'm going to try IntertCoin ROM, it's said to be zipped using Edify, which CWM 2.5.7.0 apparently supports... this way I'll know if it's CWM screwing me or not...
EDIT: Can't flash this one either. Still says verification signature failed even though I've disabled it, and the author of the ROM says it's signed.... like wtf man? All I've done is switch a few ROMs over a couple of months, nothing crazy, how could this happen???

BUMP..... I need help man... it's already rooted but I can't do ANYTHING! Can't flash, nothing...........

Go back to 100% stock, root again using AmonRA and flash another ROM

EddyOS said:
Go back to 100% stock, root again using AmonRA and flash another ROM
Click to expand...
Click to collapse
I've been searching on how to unroot.. can't find anything.. I found ONE tutorial on XDA and it looks complicated as hell.. I have OSX or windows 7... I originally rooted on Windows 7.

I've unrooted my phone, and have succesfully RE-rooted my phone only to end up with CWM 2.5.0.7 again, and sure enough, I cannot install ANY ROM again.
Since no one cares to help, I guess I'll just keep trying God knows what, and maybe I'll post results... thanks anyway...

How did you unroot? Did you run the original RUU for your phone?
Also, have you tried AMONRA recovery? You need to specify amonra when running unrevoked to flash it rather than clockworkmod.
Sent from my HTC Desire using Tapatalk

Stuck on white Htc EVo screen after succesful flash w/ almost every Rom

Hello everyone,
I just want to say I did not make this thread prematurely. Iv had this current issue for over a month. Iv talked to various people on here and other related forums and tried everything others have suggested with nothing working, So I come here to hopefully, somehow, get an answer or a fix.
I've had my Evo since Feb, rooted almost immediately and have been trying different roms ever since. Yet I always found myself going back to CM. Well just recently, Iv run into a problem where ALMOST every rom I try to flash, it gets stuck at the white htc evo 4g screen, constantly rebooting over and over. I actually waited once for hours to see if it eventually would go into the rom but it didnt. Iv tried battery pulls, clearing cache and davlich, nothing works.
Here is what works with no issues that iv tried: Any CM, Miui, Mikfroyo, MikZ, Myns, MynsZ
WHat iv tried and does not work:Mikg, Virus, Kings, Leo, Alliance, Stock Gb,
Btw, I was originally using clockwork and was told to go to Amon Ra(latest version yes)-
Heres what exactly happens:
I download the rom, which Iv tried from my phone and my pc both. Put it on root of sd. reboot into recovery. Wipe: Cache,Davlick,Boot,System,Sd ext.,Data,Sd secure, All userdata/factory reset in that order and sometimes 2 and 3 times. I then flash the rom. The screen shows the progress of the installation of w/e rom it is, always says complete or successful. Reboot.
Almost immediately Shows the screen with the squigley colored lines then after a second or 2, phone vibrates, reboots right to white evo 4g screen. Sits on that screen for approx.10-15 seconds, vibrates goes black for 2-3 seconds and then back to the white evo 4g screen and it does this over and over til im forced to pull the battery. Very VERy frustrating.
I was told maybe the links of the downloads were bad so i tried multiple downloads of the same zip. I was told to check to see if the md5 sum thing matched, it did. I was told to download sd formatter, did that. I was told to update all the latest radios,prl,ext.
I do not know a whole lot about this but Im thinking that every Gb rom i try doesnt work. With the exception of 2 Aosp roms(cm and miui). I could be way off here but im just throwing that out there.
One thing I will mention. In the middle of trying to figure all this out, I deleted my sd card when trying to wipe. Now what is important is this issue was def. happening before I ever made this mistake. SO maybe its a moot point, I just want to mention everything.
Im hoping, praying that some of you MUCH more knowledgeable flashmatics can point me in the right direction because Iv been pulling my hair out for over a month trying everything I can read or was told to come to a conclusion as to why this would be happening.
Thank you for your time. Its much appreciated.

Try downloading and flashing a stock HTC kernel,then reflash the Rom you're trying to run .
Sent from my PC36100 using XDA App

BrianBusby2038 said:
Try downloading and flashing a stock HTC kernel,then reflash the Rom you're trying to run .
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You are the only response Iv gotten so i thank you.
Someone else mentioned this.
So I downloaded: Htc kernel #15
WHat I did was flash the rom(had been various ones) then flashed this kernel, rebooted, same result. Is this what you mean?
Have youve ever even heard of this? WHere every froyo rom iv tried works, 2 specific gb roms work(CM and miui) yet various other(gb) will not work.
Has anyone EVER heard of anything like this?

What hboot version?
Sent from my PC36100 using XDA Premium App

My suggestion is go completely stock. Unroot with a 3.70 RUU and then root your phone again. Start from scratch and then load up or attempt to load up one of the Sprint Lovers rom and see what happens. Maybe just maybe you had a bad root. I do recommend Amon as well though.
Or try this get Caulkins wipe all zip and format your phones harddrive and load up Sprint Lovers and see what happens

I would recommend flashing the kernel first before the ROM,however,since you can successfully flash froyo ROMS,playa may be right and you should try running the ruu and starting over.I was thinking the problem was an incompatibility between an ASOP ROM and a Sense kernel but doesn't hold water if you can get froyo based ROMS to boot up.
Sent from my PC36100 using XDA App

unvivid said:
What hboot version?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
not sure how do i find that out? I though if I updated all radios, ext. it included that. If im way off here sorry.

playya said:
My suggestion is go completely stock. Unroot with a 3.70 RUU and then root your phone again. Start from scratch and then load up or attempt to load up one of the Sprint Lovers rom and see what happens. Maybe just maybe you had a bad root. I do recommend Amon as well though.
Or try this get Caulkins wipe all zip and format your phones harddrive and load up Sprint Lovers and see what happens
Click to expand...
Click to collapse
Like I said I will try anything, so I will be trying to do this as soon as I have time. I may run into problems with how to do this, can you possibly point me in the direction or a how to? I mean I obviously would know how to flash a sprint lovers rom but im talking about the un-rooting step regarding 3.70 ruu??, Iv never did it and probably would be lost(noob).

htcevo4g03 said:
not sure how do i find that out? I though if I updated all radios, ext. it included that. If im way off here sorry.
Click to expand...
Click to collapse
Not a problem. Turn your phone off and hold the power button and the volume down button. This will take you to the bootloader screen. The hboot and radio versions should be at the top. I'm betting your hboot is .76
I had the same issue that you did and nothing worked, I was unable to flash any new GB Rom besides cm. I tried flashing stock, using multiple versions of clockwork and amon ra. Nothing worked, updating my hboot to the latest version fixed my issue, I'm guessing its something to do with the hboot version and hardware combination. You may lose fastboot commands, if you're unsure of what those commands are I doubt you'll miss them. And recent developments have allowed for downgrading of hboot. I'll dig the link up for the latest hboot.
Edit: http://forum.xda-developers.com/showthread.php?p=7027238
I personally flashed the 2.02 hboot for downgradability. I'd avoid 2.16 since it is so new and I've heard of issues after flashing. Anything prior to that should be fine.
Sent from my PC36100 using XDA Premium App

unvivid said:
Not a problem. Turn your phone off and hold the power button and the volume down button. This will take you to the bootloader screen. The hboot and radio versions should be at the top. I'm betting your hboot is .76
I had the same issue that you did and nothing worked, I was unable to flash any new GB Rom besides cm. I tried flashing stock, using multiple versions of clockwork and amon ra. Nothing worked, updating my hboot to the latest version fixed my issue, I'm guessing its something to do with the hboot version and hardware combination. You may lose fastboot commands, if you're unsure of what those commands are I doubt you'll miss them. And recent developments have allowed for downgrading of hboot. I'll dig the link up for the latest hboot.
Edit: http://forum.xda-developers.com/showthread.php?p=7027238
I personally flashed the 2.02 hboot for downgradability. I'd avoid 2.16 since it is so new and I've heard of issues after flashing. Anything prior to that should be fine.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
This.
I was having the same problem htcevo4g03 was having and I had hboot 0.76.2000. Here is what I did:
Made a nandroid backup
Using rom manager I downgraded to clockworkmod 2.5.0.7
Downloaded hboot 2.10.0001 under Evo Stock and Radios
Wiped data and cache (I don't know is this is necessary but probably not a bad idea)
Flashed hboot 2.10.0001
Downloaded and flashed fresh evo 4.2 (a rom that wouldn't flash before) via recovery and it worked!

unvivid said:
Not a problem. Turn your phone off and hold the power button and the volume down button. This will take you to the bootloader screen. The hboot and radio versions should be at the top. I'm betting your hboot is .76
I had the same issue that you did and nothing worked, I was unable to flash any new GB Rom besides cm. I tried flashing stock, using multiple versions of clockwork and amon ra. Nothing worked, updating my hboot to the latest version fixed my issue, I'm guessing its something to do with the hboot version and hardware combination. You may lose fastboot commands, if you're unsure of what those commands are I doubt you'll miss them. And recent developments have allowed for downgrading of hboot. I'll dig the link up for the latest hboot.
Edit: http://forum.xda-developers.com/showthread.php?p=7027238
I personally flashed the 2.02 hboot for downgradability. I'd avoid 2.16 since it is so new and I've heard of issues after flashing. Anything prior to that should be fine.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Hey Man,
I haven't tried anything yet but im going to this morning.
Looking at the bootloader screen, says:
Supersonic EVT2-3 SHIP S-OFF
HBOOT-2.10.001
MICROP-041f
RADIO-2.15.00.05.02
Ok so I should download anything prior to 2.16 and flash like a rom?
Thoughts after youve seen my version?

TeamGold said:
This.
I was having the same problem htcevo4g03 was having and I had hboot 0.76.2000. Here is what I did:
Made a nandroid backup
Using rom manager I downgraded to clockworkmod 2.5.0.7
Downloaded hboot 2.10.0001 under Evo Stock and Radios
Wiped data and cache (I don't know is this is necessary but probably not a bad idea)
Flashed hboot 2.10.0001
Downloaded and flashed fresh evo 4.2 (a rom that wouldn't flash before) via recovery and it worked!
Click to expand...
Click to collapse
looks like the hboot version youve downgraded too is the one Iv had

unvivid said:
Not a problem. Turn your phone off and hold the power button and the volume down button. This will take you to the bootloader screen. The hboot and radio versions should be at the top. I'm betting your hboot is .76
I had the same issue that you did and nothing worked, I was unable to flash any new GB Rom besides cm. I tried flashing stock, using multiple versions of clockwork and amon ra. Nothing worked, updating my hboot to the latest version fixed my issue, I'm guessing its something to do with the hboot version and hardware combination. You may lose fastboot commands, if you're unsure of what those commands are I doubt you'll miss them. And recent developments have allowed for downgrading of hboot. I'll dig the link up for the latest hboot.
Edit: http://forum.xda-developers.com/showthread.php?p=7027238
I personally flashed the 2.02 hboot for downgradability. I'd avoid 2.16 since it is so new and I've heard of issues after flashing. Anything prior to that should be fine.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I downloaded and flashed Hboot 2.02 from the evo stock and radios and then tried to flashed Virus and Synergy, but the same thing is happening.
Im going to try hboot 2.15 but it sure dont look good. This is UNREAL

Bump:
Anyone of you guys that replied earlier in the thread or Anyone else out there?
Any help would be very much appreciated!
Sent from my PC36100 using XDA App

Might sound weird, but have you tried reformatting the SD card?

tnEVo said:
Might sound weird, but have you tried reformatting the SD card?
Click to expand...
Click to collapse
hey the reply is much appreciated!
If you read my op, I mentioned someone told me to dl sd formatter on my pc which I went through the steps and it didnt work.
Hey man If you get a chance please read my op, this is prob going on a month and a half and no fix to this point. I would have though if I brought the issue here, it would be resolved like that but it hasnt. Iv tried everything ppl have thrown at me and not a thing has worked. Other than froyo roms and 2 gb roms(cm7/miui), cannot getting anything to work. Ill flash a rom, it always says successful I reboot, turns to the white screen and gets stuck, rebooting over and ove, always back to the white screen and Im forced with a battery pull to do anything else. AMAZING!
If you can just look over the OP maybe just maybe you might have something you think could work.
The very last thing i tried, in which 2 ppl said they were having the same issue, was to downgrade the Hboot. I did this and it didnt work. SO frustrating.
The one thing I did not try that was said to do was unroot, go back to stock, and root again.
SO lost here. Again thanks for contributing to this thread.

htcevo4g03 said:
hey the reply is much appreciated!
If you read my op, I mentioned someone told me to dl sd formatter on my pc which I went through the steps and it didnt work.
Hey man If you get a chance please read my op, this is prob going on a month and a half and no fix to this point. I would have though if I brought the issue here, it would be resolved like that but it hasnt. Iv tried everything ppl have thrown at me and not a thing has worked. Other than froyo roms and 2 gb roms(cm7/miui), cannot getting anything to work. Ill flash a rom, it always says successful I reboot, turns to the white screen and gets stuck, rebooting over and ove, always back to the white screen and Im forced with a battery pull to do anything else. AMAZING!
If you can just look over the OP maybe just maybe you might have something you think could work.
The very last thing i tried, in which 2 ppl said they were having the same issue, was to downgrade the Hboot. I did this and it didnt work. SO frustrating.
The one thing I did not try that was said to do was unroot, go back to stock, and root again.
SO lost here. Again thanks for contributing to this thread.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I would just go ahead a unroot,wipe the hell out of it then go a reroot the see what you get. With everything you have tried so far that maybe the thing you need,sorry I couldn't be more help.

Same situation here now
So.. i'm in basically the same situation.. with a wrinkle.
I just tried.. about 8 roms.. ALL of them get stuck on the white screen
Except.. CM 7.0.3.1.. that seems to install
Any thoughts on what the heck that could be?
Roms I tried:
miui
warm 2.2
calkins new one
kings 3d
fresh 4.2

I agree... unroot, run the s-on tool form unrevoked.
run the RUU for your phone
re-root
flash Amon Ra recovery and try a new ROM

Hey hip,
OK if I have to start from scratch I will. But since I'm a super noob, can you please be a little more specific on the steps I have to take? I don't know much about s-off and s-on tool and also what ruu is. If you can just point me in the right direction then I can follow the directions.
And ty for your time
Sent from my PC36100 using XDA App