Develop Bugs

[Q] Try to restore backup --> Bricked!

Hiya,
Firstly, yes, I did a search. Here's my problem.
I used unrevoked and rooted my phone, so I could remove bloatware, tether etc. I then installed the hydra kernel to OC to 1.113 (stock volt), and this worked fine too. Couple weeks passed, everything's dandy, and today I decided to give Cyanogenmod 6.1 a try. So I get that up and running and decide that I like the Sense UI better, so I go into the ROM Manager app and tried to restore a backup that I made before installing the ROM. So the phone restarted, and then displayed the HTC Incredible logo and it stayed there.
I waited 30 minutes, pulled the battery, tried to boot. Same thing.
I held down vol down and went into HBOOT, and selected recovery. I get the black screen with vertical white lines on the sides. Waited thirty minutes, no change.
I then tried to reset factory settings through main HBOOT menu. Got the black screen with white stripes again.
So, it appears I bricked my phone. My theory is that the space on my SD card was too low and when I did the backup not all the information was saved, and when the phone tried to reset it pooped out, on account of the fact that the restore data was incomplete.
Thoughts? I do have the Best Buy warranty on this thing, so I'm wondering how that could offer some sort of solution (although I am pretty sure they will not like the fact that it has been rooted..). So in summary: Halp!!
Thanks yall.
IHateMayonnaise

Hater of Mayonnaise,
Have you ever been inside the recovery, working? I'm guessing no. The screen you described is an older clockwork recovery on an incompatible LCD screen. Try one of the newer recoveries. 2.5.1.2 should work work, as well as BAMod, and I believe Doug piston has one up. Rename the file to the proper PB31IMG.zip format and load from HBOOT. After that, look for your backup or install a new ROM.
You're not bricked till the phone doesn't turn on.
Sent from my ADR6300 using XDA App

PonsAsinorem said:
Hater of Mayonnaise,
Have you ever been inside the recovery, working? I'm guessing no. The screen you described is an older clockwork recovery on an incompatible LCD screen. Try one of the newer recoveries. 2.5.1.2 should work work, as well as BAMod, and I believe Doug piston has one up. Rename the file to the proper PB31IMG.zip format and load from HBOOT. After that, look for your backup or install a new ROM.
You're not bricked till the phone doesn't turn on.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yes I've been in it many times. When I first tried (while rooting my phone) I had the same thing happen, but I got the newer recovery or something (I forget what I did) and it went away. Why would this problem come back?

Maybe koush didn't fix the new one, so when you upgraded it broke. Go back to the older one that did work and all is dandy.
Sent from my ADR6300 using XDA App

yep it worked thanks!

lost android process
my phone gives the message android .process.acore has stopped unexpectedly.
cant get anything to work.

Just fyi. Bricked is completely dead. Not stuck at a boot screen.
Sent from my Sprint Galaxy Tab

+1 on this bricked is thrown around far too much
shoman24v said:
Just fyi. Bricked is completely dead. Not stuck at a boot screen.
Sent from my Sprint Galaxy Tab
Click to expand...
Click to collapse
Sent from my Incredible using XDA App

uwintoday said:
my phone gives the message android .process.acore has stopped unexpectedly.
cant get anything to work.
Click to expand...
Click to collapse
Which ROM?
Sent from my ADR6300 using XDA App

uwintoday said:
my phone gives the message android .process.acore has stopped unexpectedly.
cant get anything to work.
Click to expand...
Click to collapse
When does this happen? It started happening to me after I flashed data throttle zip on OMGB v6. only when I toggle 3G though.
Sent from my Htc Incredible using XDA App

android .process.acore
[ROM] SkyRaider Vanilla 3.0.1 RC3 ran this for a few days. did a back up and installed Incredible Gingerbread[Android 2.3 ran this for around twenty minutes. no back up done and tryed to install The Ultimate Droid 2.5.0. Thats when the problem started.
my phone has the andorid in the middle of the screen and says touch to continue. gives this error android .process.acore when android is touched. can only dial 911.

Since you didn't do a backup, make sure you do a complete wipe. If necessary, do a RUU and try again.
Sent from my ADR6300 using XDA App

android .process.acore
I dont see a complete wipe option.
I only have hboot options.

uwintoday said:
I dont see a complete wipe option.
I only have hboot options.
Click to expand...
Click to collapse
Factory reset, or something similar. Can't remember exactly. If not there, try fastboot.
Sent from my ADR6300 using Tapatalk

the ruu updates says loading PB31IMG.zip no image wrong image

Try going into the phone from safe mode. It might help you figure out if its the rom or an app on the rom.
Sent from my ADR6300 using Tapatalk

uwintoday said:
the ruu updates says loading PB31IMG.zip no image wrong image
Click to expand...
Click to collapse
Which means either your sd card is not FAT32, or you named it wrong.
Sent from my ADR6300 using Tapatalk

Or the file may have been corrupted during download. See if the md5 checksum matches that posted on the download site.
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.11.15

This is driving me crazy. No phone for days.
Ok i formated the sd card to fat32 via my computer sd slot. downloaded radio to computer from here
radios/2.15.00.07.28/ copy PB31IMG.zip to sd card via computer. with s off i did this , power off phone. Hold DOWN volume and press power. to accesses the hboot screen. hboot updateed PB31IMG.zip. yeah.
when i rebooted it goes into this endless loop of the red eye and the word droid.
Please advise.
Thanks

It isn't the radio you need to flash. An RUU is a stock rom as delivered by HTC. Try one of these.
http://shipped-roms.com/shipped/Incredible/
Sounds like you may need to reflash recovery too.
Edit: On second thought, you're recovery is probably ok. I was getting your problem confused with the original poster's problem.
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.11.15

[Q] ROM flashing

Hello. today ive got my 1st android device - htc desire. i know that i was sim locked to band " 3 ", and is now sim unlocked, at boot screen i still see big "3" after HTC. i have rooted it with unrevoked team, clockwork recovery works. i have downloaded "LeeDrOiD's" rom, and placed into my sd card (it also has two partitions for a2sd). then when i engage clockwork recovery and try to install that rom, nothing happens, it just blinks, some text shades fast, and here i am back on the rom(.zips) selection... so anyone any suggestions on this? btw my radio is 32.41 if it has anything to do with this.

Check md5 and disable signature verification. It's in the install zip from sd menu.
Sent from my HTC Desire using XDA Premium App

where exactly is that md5 and how do i check it?

The leedroid mini site has the information or try: http://goo.gl/FEzxL
Sent from my HTC Desire using XDA Premium App

even if i check it, i will not know if it is right, however. this developer is serious and this is nothing bad about this rom i think. imo its about the phone. so what else can go wrong?

i find that software number : 1.22 can be problem

I think you need to do some reading on how to flash a rom, sounds to me like you have absolutely no idea what you are doing.
What do the lines even say when you flash the rom but it fails?
Sent from my HTC Desire using XDA Premium App

actually i have idea what i do. when i start flashing custom rom, it just blinks and returns back to custom recovery, and now this turned that it froze on "installing" for two mins, then it started installing, and get bricked. i saw htc in white screen, and then custom firmware boot screen blinking 3 sec intervals. i have done ruu software upgrade so far, and have advanced to 2.2 froyo and software 2.29.405.5 in that way, and i am failing to root the phone now.

Saying 'it just blinks' isn't exactly descriptive of the issue. What do you see on the screen? We need as much information as possible to even begin to help you

found that unrevoked 3.2 (older version) soloved my problem, phone is rooted, and custom rom already sucesfully installed

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

Boot Loops, forever.

So, I don't really post on forums because I'm pretty tech-savvy, but I have a big problem that I can't fix, and I can usually fix everything (thanks to you guys!)
This morning, my incredible acted up as I was checking an e-mail and it froze, so I decided to battery pull because restarting my phone didn't work. (Note, my incredible has been running VERY solidly on a CM7.1 nightly). As I tried to boot up the phone again, it would stay on the white HTC Incredible screen. When I rebooted into recovery thru HBOOT, i realized that there was an error mounting something, like recovery_log, or something like that (i didn't mind this because I thought I knew what I was doing), but I tried restoring my old nandroid backup that was working well, but it didn't work. It said it couldn't format /data or something... It ended up staying on the white HTC incredible screen. So, I wiped data/cache like 10 times, and dalvik cache as well and tried re-flashing a clean install of cm7.1 stable, but didn't work again - led me straight to the white Incredible screen. So, installing a fresh rom AND restoring a solid backup didn't work... so...
I found the RUU 2.3 stock rom on the development forums, and tried to install that like I do with the radios (PB31IMG.zip) through HBOOT, but no cigar. It did go PASSED the white screen, but boot loops at the Droid eye.
So, I thought I'd find a different stock img, and found the 2.2 official OTA .zip and installed it the same way, but got the exact same result (boot loops, forever).
Any suggestions? I can't think of anything else.... I feel like my phone is bricked, but I didn't do anything to make that happen.
I feel like something happened that made me not able to format the /data, and stuff. I even formatted my SDcard in case it was the problem.
Any help is appreciated. Thanks!

Load the RUU onto a different fat32 sd card and see if you are able to boot.
Sent from my ADR6300 using XDA Premium App

i'll try that and give an update. thanks for the reply!
*update* no luck. same thing happens. i tried on three different sdcards formatted fat32...

Can you factory reset and flash a ROM from a different sd than the one you were using? Description sounds like bad sd, and AOSP roms interact with the sd on boot. If original (CM 7) sd is toast, it'll never boot, hence different sd card and prefably RUU
Sent from my ADR6300 using XDA Premium App

I had this happen once where no matter what rom i flashed all i got was bootloops. I had to get the stock froyo ruu.exe that you run from your pc and install it that way. Then once installed boot up and go to settings/sd & phone storage and do a factory reset from there. This factory reset is a true reset as it wipes out vzw programing also. After reset folow on screen steps to reactivate your phone, you can skip the rest of the setup. Once thats done your good to go just flash clockwork or amon ra recovery and then flash what ever rom you want. No guarantees but it worked for me.
NOTE: This assumes you are s-off, if your not after flashing the ruu you will have to use unrevoked to regain root and s-off again.

You can also try wiping /system and /boot.

*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.

sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
if you are non root. you will need to download the RUU.exe for 2.2 and install if from you pc.
http://androidforums.com/htc-droid-...mplest-instructions-ever-windows-xp-only.html
follow that and your phone will be back to the day you got it out of the box.

All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.

SlimSnoopOS said:
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
Click to expand...
Click to collapse
RUU = ROM Update Utility

no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.

sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Then its gotta be a hardware failure.
Sent from my sexy assistant. (AMOLED HTC Incredible)

wow... what a bummer. thanks for the help anyway, it's much appreciated.

sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Does it give any specific error code when it says it can't connect to the phone?
Someone correct me if I'm wrong but don't you have to have HTC sync installed on your pc to use an ruu.exe? Do you have that installed?
Sent from my ADR6300 using xda premium

I'll try it again to verify the code, I'm pretty sure it was "170"

sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
I had this issue the first time i rooted my phone and attempted to put on a ROM, and i resolved it when i found this post to get back to stock. I also used this to fix a problem where my phone had a black screen with a line through it on booting to recovery or attempting to do a nandroid back up:
droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
All i did was basically use the PB31IMG Method without turning s=on, ( i had stock radio and still have 7.28 )
1) download that PB31IMG.zip and drop it on the root of your sd card ( it has to be named ( PB31IMG.zip ) so make use you have file extensions showing on your PC.
2) boot to hboot and and let see the file and install it
3) used unrevoked ( remove sd card ) to aquire root again.
idk if this helps, but this seems to get me out of the few weird situations i had

sl4m said:
I'll try it again to verify the code, I'm pretty sure it was "170"
Click to expand...
Click to collapse
Check this out to fix your 170 error.
http://androidforums.com/incredible...170-171-solution-windows-7-a.html#post1472468

This low key happened to me and I booted in to HBOOT and went to clear storage and it did its thing and booted up, from there I had to activate it then I was set!
Sent from my ADR6300 using XDA App

=D
Sent from sweet snacks off tapatalk.

[Q] Evo 4g can only flash CM7, nothing else

I originally had this question in the general q and a, but some have told me to move it here:
Ok, so i've exhausted all searches. I always always search first and try every possible solution, after a week, i'm back to square one.
I rooted my htc evo 4g with unrevoked. Ive been flashing and rooting for almost a year now and never enountered a problem like this before
Amon_ra 2.3
S-OFF
Hboot 2.10.0001
hardware 0003
the issue is everytime i try to flash a rom other than CM7, i get this error:
assert failed: write_raw_image("/tmp/boot.img","boot") Status 7
I am only trying to flash a sense rom so i can update my prl.
I followed the advice on this page: http://androidforums.com/evo-4g-all-...oot-error.html
but i still get boot: PU-Fail running the all in one PC36IMG.zip, when that didnt work, i tried the stand alone version
I then tried partitioning my sdcard using this: http://forum.xda-developers.com/show....php?t=1158993
and still no luck. Everytime i mess up, i just re-flash CM7 and it works like nothing was wrong. I could live with cm7 forever, i just want to update my prl then go back to cm7.
These are the roms ive tried:
Sprint lovers stand alone| Result: didnt give me error but stayed on white screen for over 1.5 hours.
sprint lovers all in one PC36IMG.zip| Result: boot-PU-Fail, update failed
latest fresh. 4.3.3.| Result: assert failed: write_raw_image("/tmp/boot.img","boot") Status 7
Stock rom deodexed: assert failed: write_raw_image("/tmp/boot.img","boot") Status 7
synergy| result: assert failed: write_raw_image("/tmp/boot.img","boot") Status 7
FYI i do a full wipe of system, dalvich cache, and then flash the virus wipe zip.
I am stuck. I feel like i cant flash any sense rom and i can only flash CM7.
Please help let me know if you need any other info

memekmek said:
I originally had this question in the general q and a, but some have told me to move it here:
Ok, so i've exhausted all searches. I always always search first and try every possible solution, after a week, i'm back to square one.
I rooted my htc evo 4g with unrevoked. Ive been flashing and rooting for almost a year now and never enountered a problem like this before
Amon_ra 2.3
S-OFF
Hboot 2.10.0001
hardware 0003
the issue is everytime i try to flash a rom other than CM7, i get this error:
assert failed: write_raw_image("/tmp/boot.img","boot") Status 7
I am only trying to flash a sense rom so i can update my prl.
I followed the advice on this page: http://androidforums.com/evo-4g-all-...oot-error.html
but i still get boot: PU-Fail running the all in one PC36IMG.zip, when that didnt work, i tried the stand alone version
I then tried partitioning my sdcard using this: http://forum.xda-developers.com/show....php?t=1158993
and still no luck. Everytime i mess up, i just re-flash CM7 and it works like nothing was wrong. I could live with cm7 forever, i just want to update my prl then go back to cm7.
These are the roms ive tried:
Sprint lovers stand alone| Result: didnt give me error but stayed on white screen for over 1.5 hours.
sprint lovers all in one PC36IMG.zip| Result: boot-PU-Fail, update failed
latest fresh. 4.3.3.| Result: assert failed: write_raw_image("/tmp/boot.img","boot") Status 7
Stock rom deodexed: assert failed: write_raw_image("/tmp/boot.img","boot") Status 7
synergy| result: assert failed: write_raw_image("/tmp/boot.img","boot") Status 7
FYI i do a full wipe of system, dalvich cache, and then flash the virus wipe zip.
I am stuck. I feel like i cant flash any sense rom and i can only flash CM7.
Please help let me know if you need any other info
Click to expand...
Click to collapse
Sounds like bad blocks on your boot partition. If this is the problem then unfortunately there's not a fix that I know of. Since you're using Amon Ra, have you tried wiping boot? I'm not sure if this would help, hurt, or even make a difference.
If I'm right, the boot partition on the roms you're trying to flash is too large. There's a way to check if you have bad blocks, but I'm not sure of the method. Now that you have an idea of what it might be you can search further. I could be completely wrong, I'm just recalling what I've read on here before.
I hope whatever the issue is can be fixed.
Supersonic Evo 4G | MIUI | Tapatalk

You don't need to be on sense to update prl. Search and you'll find what you need.
Try using bootmanager too idk why or how it'd work but its worth a try
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702

plainjane said:
Sounds like bad blocks on your boot partition. If this is the problem then unfortunately there's not a fix that I know of. Since you're using Amon Ra, have you tried wiping boot? I'm not sure if this would help, hurt, or even make a difference.
If I'm right, the boot partition on the roms you're trying to flash is too large. There's a way to check if you have bad blocks, but I'm not sure of the method. Now that you have an idea of what it might be you can search further. I could be completely wrong, I'm just recalling what I've read on here before.
I hope whatever the issue is can be fixed.
Supersonic Evo 4G | MIUI | Tapatalk
Click to expand...
Click to collapse
i think its bad blocks :/ all aosp roms work, no sense roms work

Crossrocker said:
You don't need to be on sense to update prl. Search and you'll find what you need.
Try using bootmanager too idk why or how it'd work but its worth a try
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
Click to expand...
Click to collapse
thanks! i'll keep looking

1st off I'm a total noob when it comes to flashing roms, but like yourself I've tried to do alot of searching to get to learn the process. That being said I'm pretty sure that I do remember reading somewhere that you can manually update you PRL for CM7. Apparently as a noob as well I can't post a link to the thread I read this in but on the CyanogenMod forum in the HTC EVO General area there is a thread called [guide] the hitchhikers guide to flashing and CyanogenMod, in the OP the 3rd and 4th quote box lists the info I was talking about. I hope this helps and that I'm correct in what I was thinking.