Hi - posted this elsewhere but really need help.
First off - I think I made a serious of noob mistakes that have resulted in my problem. I desperately want to be able to recover my phone, so please be nice.
I have a rooted incredible with the leaked 2.05 OTA radio update and have been running Cyanogenmod 6 rc3 and then 6.0. This morning I tried updating to 6.0.1 but for some reason it didn't update. It kept rebooting to 6.0 and telling me I needed to update again.
I decided to just unroot the phone and go back to stock to take advantage of the stock 2.2 update. I put the earlier 2.1 stock file on my SD card and pressed power and volume down to boot into recovery. The phone then started to update to the older version, but ultimately wouldn't do it, telling me this was an older version.
I realized this was because of the leaked radio update I had. Until I can fix that, I want to just reboot back into CM6, but I can't. The only way to turn the phone on and off is to pull the battery, but the phone won't boot, it just goes into recovery -- and I can't use the volume or power buttons at all to select menu items. So I have to pull the battery again...
So I'm stuck there. Any ideas how to at least fix so I can use CM6 again?
I should also mention that I recently replaced the digitizer, which was cracked, and almost everything works, except now I can't use the trackball
lvjy said:
Hi - posted this elsewhere but really need help.
First off - I think I made a serious of noob mistakes that have resulted in my problem. I desperately want to be able to recover my phone, so please be nice.
I have a rooted incredible with the leaked 2.05 OTA radio update and have been running Cyanogenmod 6 rc3 and then 6.0. This morning I tried updating to 6.0.1 but for some reason it didn't update. It kept rebooting to 6.0 and telling me I needed to update again.
I decided to just unroot the phone and go back to stock to take advantage of the stock 2.2 update. I put the earlier 2.1 stock file on my SD card and pressed power and volume down to boot into recovery. The phone then started to update to the older version, but ultimately wouldn't do it, telling me this was an older version.
I realized this was because of the leaked radio update I had. Until I can fix that, I want to just reboot back into CM6, but I can't. The only way to turn the phone on and off is to pull the battery, but the phone won't boot, it just goes into recovery -- and I can't use the volume or power buttons at all to select menu items. So I have to pull the battery again...
So I'm stuck there. Any ideas how to at least fix so I can use CM6 again?
I should also mention that I recently replaced the digitizer, which was cracked, and almost everything works, except now I can't use the trackball
Click to expand...
Click to collapse
Is soff?
Sent from my Incredible using XDA App
tcberg2010 said:
Is soff?
If it is u could run the new ruin from hboot. This will give u stock 2.2 and stock recovery. But you'll be able to flash clockworkmod again.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Sent from my Incredible using XDA App
tcberg2010 said:
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Nope, s-on.
Is there a way to make it s-off in this state? I'd be happy to just get it into stock 2.2. Thanks.
Related
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
So i rooted my brother's incredible and then he started installing system updates and now everything force closes. I put the zip onto the sd card but when I try to reboot into recovery, the screen blacks out with white lines down the sides...any suggestions? I told him that I would just probably have to find a way to take his phone back to stock...I'm a n00b myself so still trying to figure this out.
UCE HAMOCIDE said:
So i rooted my brother's incredible and then he started installing system updates and now everything force closes. I put the zip onto the sd card but when I try to reboot into recovery, the screen blacks out with white lines down the sides...any suggestions? I told him that I would just probably have to find a way to take his phone back to stock...I'm a n00b myself so still trying to figure this out.
Click to expand...
Click to collapse
It sounds like it's an slcd screen. Did you use the latest unrevoked? I think that comes with an slcd compatible clockwork.
Sent from my ADR6300 using XDA App
This is what i will guess happened...because it happened to me too.
1. when you rooted his phone, you never checked that recovery was actually worked.
2. It was when you tried to recover is when you discovered it didn't work.
As the previous problem is probably because of the slcd screen. Unrevoked 3.3 supports installing recovery to the slcd versions of the phone.
3. After you gave your brother the phone back, a few hours later the nagging "system update avaliable" pop-up well, popped-up and he in stalled it thus erasing the root.
you can simply unroot it again using Unrevoked, but you will simply continue getting the message unless u are familiar enough with adb or terminal to make it stop.
The first thing you need to do after you re-root it is download Rom Manager from the marketplace and BACK UP the current setup...
If your brother really likes the feel of the Sense UI then you can DL the Virtuous Rom straight from the app. Plus the Virtuous app includes the modded flash and hulu apps.
Or you can try many of the other avaliable Roms in the app. I reccomend buying the full app btw b/c its a life saver...or at the very least leave the ads on.
also..your phone is not "bricked". It is a simple matter of removing removing the battery and putting it back in to get you on the road to recovery...pun intended.
I also HIGHLY reccomend using the search function.
http://forum.xda-developers.com/showthread.php?t=855515
I hope this helps.
I didn't think the ota would work with a custom recovery.
Sent from my ADR6300 using XDA App
LoL, thats sorta the point...the OTA doesnt work. It frazzles the phone and removes the S-OFF
brownrt said:
LoL, thats sorta the point...the OTA doesnt work. It frazzles the phone and removes the S-OFF
Click to expand...
Click to collapse
Maybe that's the case with a stock rooted phone, but installing the ota from skyraider doesn't work and doesn't break root or soff.
Sent from my ADR6300 using XDA App
Okay, so I was unrooting my droid incredible and it brought it to stock 2.1 i was trying to install the update.zip to update it to 2.2, but it wasnt working...so i tried installing the 2.2 RUU onto it...and now when i try to turn on my phone it always boots into the Bootloader...what should i do?
Note: LED charging light still comes on, and i can still go into recovery(stock recovery though since my phone is no longer rooted)
If theres no way to fix it, can i just play dumb and tell verizon its not starting up, because doesnt HTC have to reflash everything anyway for security purposes....the only downside though is they would probably send me an SLCD Incredible
First and foremost, your phone is not bricked... not even close.
Simply try reinstalling the 2.1 RUU. Being that it's signed by HTC, you should be able to do what you need to in the stock recoveryThat being said, your update.zip probably failed because your phone was restored to a state prior to the May OTA. Without being at the correct software version, you cannot use the update.zip to install Froyo.
If you get the bootloader, you should be ok. I think the zip has to be on the root of the SD and named update.zip for the stock recovery.
Sent from my DInc
Look in the android development forum for "the ultimate back to stock thread". download the "PB31IMGxxxxx" file there, rename it to just PB31IMG.zip and put it on the root of your sd card. Go into the bootloader and let it run the update. This will bring you back to a 2.2 stock. From there you can re-root and do whatever else you like.
Sent from my ADR6300 using XDA App
Okay, well it was the get back to stock thread that i followed...and i know that i was trying to do the update.zip from a version of android that was too old, because i was the one who posted a thread a few months back with the update.zip in it. However, i was obviously stupid enough to not save teh "May" OTA and now the link is dead. Some people were reporting however that it still worked without it, so i wanted to see for myself.
In any case, it seems that a 5 hour battery pull seemed to do the trick, go figure. Can someone explain to me what a battery pull on this kind of stuff makes a difference and why the length of time sometimes makes a difference as well?
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
Anyone know how to get s-on without recovery?
Long story short, loaded miui 10/14 with tiamat 4.1 sbc kernel last night. Everything fine.
Woke up this morning in an endless bootloop and it won't go away no matter what I do. Have the PC36IMG on the card, it asks to update, it does but no recovery. Just an endless bootloop.
Try to run ruu, 107 usb connection error.
Change batteries, still nothing, same bootloop.
Got a card reader, replaced the PC36IMG with a new one, same bootloop.
Format card, put PC36IMG back on the card, it updates per normal. Still nothing
Any thoughts would be appreciated otherwise I believe I have a fried phone
http://forum.xda-developers.com/showthread.php?t=1218386&highlight=how+to+root. You might wanna check out the files in the faq's in that thread. Im no droid expert just taking a shot in the dark. Hope you get your evo functioning again.
What radio version do you have?
Concordium said:
What radio version do you have?
Click to expand...
Click to collapse
Whatever the radio version that comes with the PC36IMG update for froyo, hboot version 2.10
Ran that update last night and everything updated. Then it stayed in the endless bootloop
Sent from my PC36100 using XDA App
andygu3 said:
Whatever the radio version that comes with the PC36IMG update for froyo, hboot version 2.10
Ran that update last night and everything updated. Then it stayed in the endless bootloop
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yeah it helps when you load HBoot and actually look at what radio version you have. Assuming things doesn't bode well for your phone when you start flashing things through HBoot.