Ive installed a few different roms and when the phone boots up the animation, it reboots and just reboots at the HTC Evo white screen..
ive gone into the recovery and deleted the Cache and Davlik.. rebooted, and same thing... out of 10 boots, it booted 2 times successfully into the rom but then after 10mins, it reboots again and get stuck...
anyone know whats wrong or how to fix this..
thanx
gd6noob said:
Ive installed a few different roms and when the phone boots up the animation, it reboots and just reboots at the HTC Evo white screen..
ive gone into the recovery and deleted the Cache and Davlik.. rebooted, and same thing... out of 10 boots, it booted 2 times successfully into the rom but then after 10mins, it reboots again and get stuck...
anyone know whats wrong or how to fix this..
thanx
Click to expand...
Click to collapse
If your not running any scripts then I would try fresh download wipe all except sdcard battery and rotation and reflash don't flash any thing else until after you boot up then flash each additional item that you like one at a time rooting between each one that way you can find out what if anything is causing your problem hope that helps
ive used the wipe on EVERY options.. even wipe sdcard, battery and rotate screen option...
I dont flash any extras then the actual rom..
gd6noob said:
ive used the wipe on EVERY options.. even wipe sdcard, battery and rotate screen option...
I dont flash any extras then the actual rom..
Click to expand...
Click to collapse
Then I would try a fresh download you may have a bad copy
I had the same issue on a replacement Evo, it had never been rooted. Eventually it wouldn't boot up at all, even after 20+ tries. I took it into the Sprint store and they ordered a replacement (they did check for s-off).
I would try running an RUU. If the problem persists, then do whatever you have to do to get s-on so you can get a replacement. I'm not familiar with the new rooting and unrooting methods, haven't done it since FroYo. If running an RUU will revert you to s-on, then I'd use an easily rootable RUU in case it solves your problem. Good luck!
Like plainjane said. In case you need to unroot and have it replaced, I'd follow captain_throwbacks thread at the mik-mik to downgrade radios and hboot to froyo (radio 2.15.00.11.19 hboot 2.10) before your phone becomes completely unalterable, then you'll still be root, and if the unthinkable happens, you'll also be in good shape for sprint checking your setup. Look in the general sub-forum,... much talk and info about this. Look for info from Captain_Throwback.
Sent from my PC36100 using xda premium
If you wiped your SDCard, then you have nothing on there. Definitely run the RUU and see where you can go from there
Might wanna check ur permissions ad well....not sure which rom ur running but the boot animations..are either in data....local....or says...media...resources ...if I'm remembering correctly ....long press and check ur permissions once you've found them
Sent from my Expressed out eVo using xda premium
how long have yo let it go? Iv had a similar problem when i boot to a new rom for the first time. it goes through the splash screen, then to bootanimation, then back to splash then animation again. this usually happens 1-2x then once its all up, settled in and i have my settings and apps reapplied it doesnt happen again. Just my experience.
the only problem is....
Im not on sprint.. heck im not even in the U.S.
Im up in Canada. I bought this phone for my media player instead of an ipod, which is more (got this phone for $50) and for taking pictures... If its dead (i hope its not) then its no big deal...
also, i have a habit of backing up my important info and wiping my SDcard when install a new rom..
im kinda getting fed up with this constent reboots..
im thinking if I flash the stock RUU, this would unroot my phone.. then I will reroot it.. would this be a good idea??
I read that the lastest RUU cant be unlocked yet.. so which is the latest version that can be unlocked and s=ff?
gd6noob said:
im kinda getting fed up with this constent reboots..
im thinking if I flash the stock RUU, this would unroot my phone.. then I will reroot it.. would this be a good idea??
I read that the lastest RUU cant be unlocked yet.. so which is the latest version that can be unlocked and s=ff?
Click to expand...
Click to collapse
I'm surprised no one's asked you this yet, but what recovery are you using?
Amon RA, from the following link. Flash it via hboot using PC36IMG.zip
http://forum.xda-developers.com/showthread.php?t=705026
IIRC, after i flashed this recovery, i started having these issues... before I was on the revolutionary recovery and didnt have any issues..
Related
Ever since I flashed LeeDroid 1.8b, I've been having this odd problem. I've wiped the phone since and have flashed Open Desire 3.1.0 and I love it but I'm terrified to reboot my phone.
The phone will boot and freeze at the HTC white screen. This happens even if I try to boot into Recovery, (I can hold down vol+down and power button) but as soon as I select Recovery, it will freeze there at the HTC screen.
The only solution I have is to pull the battery and try again. It will do it around 2 - 3 times before it finally boots into Clockwork Recovery Mod SLCD or boot into Open Desire if I don't boot into recovery. This is the same if I decide to REBOOT the phone or power down and boot up.
This problem never happened when I originally flashed Cyanogen. I'm thinking there's still some files or something left that causes this freezing.. I also did a wipe and delete cache before flashing a new rom.
Does anyone else have this problem or help me sort it out?
Edit: Ah shoot.. wrong forum My bad..
no one?
Although Lee newer acknowledged it, I think it has to do with his ROM. I experienced the same issue while running 1.8b, with 1.8c I haven't rebooted by now, but still I have experienced this only after switching to his ROM and I noticed I am not alone on the ROM thread (other people are complaining too about getting stuck at the bootscreen).
I have changed many ROMs (generic 2.1, generic 2.2, pays, adamg ROM...) and never had such an issue, that is why I think it has to do something with lee's ROM.
If you have OpenDesire I would suggest to reboot it just to see how it will go.
Thanks for your response man! The problem is that I've wiped and everything and flashed Open Desire and I'm still experiencing the issue. Is there another way I can completely delete/format any traces of any previous ROM? I believe there's still some sort of remnants of his files left that are causing this!
THanks,
JD
A full wipe can never hurt.
As for freezing at the HTC screen when trying to boot into recovery, I experience this too. What I have found is that if I press no buttons after booting into HBOOT, until HBOOT has tried to load from the SDCard, and THEN selecting Recovery, Recovery boots every time.
However, if I push a button before HBOOT has loaded from the SDCard, I will freeze on the HTC screen regularly.
TheLastOne said:
A full wipe can never hurt.
As for freezing at the HTC screen when trying to boot into recovery, I experience this too. What I have found is that if I press no buttons after booting into HBOOT, until HBOOT has tried to load from the SDCard, and THEN selecting Recovery, Recovery boots every time.
However, if I push a button before HBOOT has loaded from the SDCard, I will freeze on the HTC screen regularly.
Click to expand...
Click to collapse
I will definitely try that.. do you ever have problems booting though? I freeze on the HTC screen during boot up as well and have to do 2 - 3 battery pulls before it finally decides to boot!
I do not, but hopefully a full wipe (data, cache, dalvik, etc) will solve that. Have you tried wiping everything?
I have, but the only wipe I perform is the one in the Clockwork Recovery. Also deleted the cache, but never have deleted or wiped dalvik cache?
I will try this later today and see what happens.. thanks!
TheLastOne said:
I do not, but hopefully a full wipe (data, cache, dalvik, etc) will solve that. Have you tried wiping everything?
Click to expand...
Click to collapse
Just sayin' I've not ever had a boot problem like this with LeeDrOiD. Running 1.8c at the moment.
Ditto.. No issues, its not a rom issue, you may have bad blocks on your nand.
Sent from my HTC Desire using XDA App
Tawm said:
Just sayin' I've not ever had a boot problem like this with LeeDrOiD. Running 1.8c at the moment.
Click to expand...
Click to collapse
I believe it was an issue with 1.8b..
LeeDroid said:
Ditto.. No issues, its not a rom issue, you may have bad blocks on your nand.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Hmm.. anyway to confirm this? It's a brand new device, barely two weeks old and never had this issue until I flashed 1.8b.. I'm going to try to wipe it completely and go from there, hopefully that solves the issue.
What's a nand?
Hi Quazis,
I have had a very similar problem with my Telstra desire after rooting and installing a Lee based rom called NexTSense. After that I installed Open Desire and experienced the same problems.
I am just now re-rooting my phone and going to install Pinky.
Just out of interest are you running on the 850mhz Rogers network? If so have you updated to the latest radios (5.09.20 I think?)? Telstra runs off this frequency also and I think it may have something to do with incompatible radios. -- Can anyone confirm this?
If this is the case maybe try Open Desire without updating the radios?
Hey,
We got the A8182 version of the Desire which has 850/1900 (I believe), so both bands that run on 3G.
Before I flashed LeeDroid, I had updated the radio (.20) and was on Cyanogen nightly build. I had no booting problems with that ROM, but I wanted something a little more stable. I modded it as well and the phone booted up no problem, also into recovery.
Once I flashed LeeDroid, that's when my problems arose. I only wiped/formated data and the cache.. I never formated that dalvik cache. I will wait until Open Desire 3.2.0 releases today and try that a full wipe/format.
Another member said he doesn't touch anything on the phone when he boots into recovery until the phone does the SD card check.. I tried it once and it went into recovery with no issues so maybe pressing buttons before the SD check does something??
I don't, but I did a full flash, and used my separate test sd card.
plasmafire said:
I don't, but I did a full flash, and used my separate test sd card.
Click to expand...
Click to collapse
I'm going to do this.. thankfully I have't customized my phone a lot so I'm going to format both the FAT32 and EXT3 partitions and full wipe.. to do a full wipe.. there's only data/factory, cache, davlik cache and battery stats correct? If I wipe those 4 items in Clockwork, that's considered a full wipe?
JD
Full flash wont help. I know because I did it.
I am to lazy from installing different ROMs, resetting my device, etc... so I will leave it as it is for now (LeeDroid 1.8c), and will try to reboot it as rare as possible (bootscreen takes a while, bootloop is possible too). But when I'll have some more time I will re-root and install another ROM and I am sure the issue will be gone.
Lee, nothing personal (in the end, I am using your ROM right now) but I think you should read more carefully the thread about LeeDroid. You will see many people get stuck at the booscreen and/or their devices keep rebooting with this ROM.
I don't have this issue with the same ROM as you.
-----------------------------------
- Sent via my HTC Desire -
Yes, not everyone has that problem (in that case we wouldn't need to talk about it - we would KNOW it). Just some people have this issue with that ROM. I would say 5% of the people have the bootloop problem, and 10% of the people have longer-than-average the bootscreen.
Still, it worths taking a look since 3-4 people from 10 participants on this thread say they have this problem with -this- ROM.
My 2 cents.
ljesh said:
Full flash wont help. I know because I did it.
I am to lazy from installing different ROMs, resetting my device, etc... so I will leave it as it is for now (LeeDroid 1.8c), and will try to reboot it as rare as possible (bootscreen takes a while, bootloop is possible too). But when I'll have some more time I will re-root and install another ROM and I am sure the issue will be gone.
Lee, nothing personal (in the end, I am using your ROM right now) but I think you should read more carefully the thread about LeeDroid. You will see many people get stuck at the booscreen and/or their devices keep rebooting with this ROM.
Click to expand...
Click to collapse
Why won't a full flash help? I don't have LeeDroid anymore, I had it for about 10 minutes because I didn't like it. I've since gone to Open Desire and the issue still persisted.. but it never happened when I had Cyanogen installed.
I'm scared to re-root because it requires a reboot and sometimes the HTC screen never goes away.. lol
hey there, its intresting to see that you have the same problem as me,
http://forum.xda-developers.com/showthread.php?t=755835&highlight=Recovery+Issue
the people who are saying they dont have a problem, i'd like to know what recovery you are using?
and what hboot you orignally came from, i.e. do you have a SLCD screen? and how did you root?
because it is now becoming obvious that leedroid rom is causing this issue as a lot of people are having problems.
during the weekend i will try flash the RUU for WWE with the hboot 0.83 included (using gold card)
and start from scratch and flash another.
no disprespect to the developer of leedroid, his work is good. just a lot of people on hboot 0.83 with the SLCD screen have issues.
Well I could not get out the bootloader and bootloop after running the stock ruu.exe and updating several recovery images PC36img none of em work so I had to go to sprint to order a new one. I really want to come back to MYN ROm when I get my new Evo..But I do not want to brick it again. The only dilemma is I really do not have the total idea of what made my phone just crash force close android and start bootlooping.
I used the unrevoked one click root method and the unrevoked forever to nand unlock it. I was flashing several different kernels at first. When I saw still no improvement in battery life I went to start off flashing Fresh, then AVA then Myn. I had got a force close to with AVA rom and bootloop but i was able to get into recovery and to the splash screen. I wished I had pay attention to what kernel I flashed which was 24hrs before my phone crashed same thing happened when I flashed Myn's rom. However, I was getting crazy bootloops when I first used the battery tweak and after I saw the battery drain I tried a different kernel. At first i was wiping both cache in between but since so many kernels even the stock kernel was giving me a loop at the splash screen (where myn warm 2.2. would come up) I started wiping less just to finally get a kernel which would be stable. The last kernel I flashed I remember was netarchy 4.1.8 cfs fresh compatible around saturday 3pm and around 3am the phone just crashed android crashed and the worst bootloop started happening.
So can anyone give me some feedback please that has their device running smooth with this Rom and/or have had this issue before? Do you recommend unrevoked forever? Does anyone may think its due to flashing so many kernels?
Are you paying for the new phoneor is the warranty taking fare of it.
I'm new to to android scene, but it seems like you shot first and asked questions later... approach could have cost you a new phone.
Anyways have you given up on your old phone. I'm sure there's ways to fix.
What recovery version do you have?
Depending on what recovery you have, you should have usb access still, if so drop a another rom in there and flash via recovery.
Sent from my PC36100 using XDA App
you more then likely didnt actually brick that phone. i would wager if you had asked and tried a few more things that you could have gotten it to work. If the phone boots at all and goes to a boatloader or fastboot then it is 99.999% of the time not bricked and can be fixed.
for example (and you may have tried) the only PC36IMG that normally works most of the time is the original eng bootloader in toasts old root method. if you tried any others most have them dont seem to rewrite everything to get it working.
as far as what caused it there is no way of knowing with the information you provided. I have run the rom and it has been stable. I doubt it was flashing so much as myself and many others flash daily with out problems.
At a lost but luckily I did not have to pay for a new phone
omegasun18 said:
you more then likely didnt actually brick that phone. i would wager if you had asked and tried a few more things that you could have gotten it to work. If the phone boots at all and goes to a boatloader or fastboot then it is 99.999% of the time not bricked and can be fixed.
for example (and you may have tried) the only PC36IMG that normally works most of the time is the original eng bootloader in toasts old root method. if you tried any others most have them dont seem to rewrite everything to get it working.
as far as what caused it there is no way of knowing with the information you provided. I have run the rom and it has been stable. I doubt it was flashing so much as myself and many others flash daily with out problems.
Click to expand...
Click to collapse
I agree I do not think i bricked it but I have tried so many PC36IMG and different bootloaders I am now way more familiar with android and recovery than before lol. I saw your posts in another thread about a guy with the same issue flintr i think but the toast 2 eng still was not working however those were the first i was trying it may work now since I'm sure I was using a different hboot the 97 version then.
I am not sure if there is anyway its going to work now since even though it still says im Ship S-off I have tried running the stock ruu. I tried the fastboot and i flashed an older hboot to get my fastboot commands..so i ran the command fastboot flash recovery recovery-1.8ra. img but it still would not get into recovery i really do not have any idea what happened.
I really think somehow my kernel is affecting everything. I tried to flash a kernel through fastboot and i was getting error it could also be though i do not have the right format for my kernel file.
potna said:
Are you paying for the new phoneor is the warranty taking fare of it.
I'm new to to android scene, but it seems like you shot first and asked questions later... approach could have cost you a new phone.
Anyways have you given up on your old phone. I'm sure there's ways to fix.
What recovery version do you have?
Depending on what recovery you have, you should have usb access still, if so drop a another rom in there and flash via recovery.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I can't get into recovery..as soon as i select recovery it starts bootlooping.
I'm not paying for the new phone I went to a small sprint store so they just looked at it tried to clear data in bootloader and then ordered me a new phone.
Fair enough, sometimes a fresh start can be good. Good luck
Sent from my PC36100 using XDA App
Hey Guys-
Couldnt find a thread similar so I'll start my own.
6 days ago i updated my rom to CM 7.0.3 and the newest version of Savaged Zen Kernel (dont remember version). Everything was fine until leaving work last night and it began to boot loop in my pocket while driving home. Phone had worked as normal all day (web, text, talk), no changes made to phone either. The only thing i can do is get into the bootloader (by holding power and volume up). Although when i try to enter recovery from there to flash a backup, it just puts me back into the boot sequence again. Any help guys?
http://api.viglink.com/api/click?fo...ersonic-v2.3 - xda-developers&txt=PC36IMG.zip
download that rename PC36IMG and put on root of sd card now go into bootloader go into fastboot and it should stay start update press volume up for yes and then when its done put yes it gonna reboot now take out battery put it in evo again and go into bootloader againthen from bootloader go into recovery from there and you should see amon-ra and from there try to do a nandroid or flash a new rom
I got the update to go through, but now when it prompts me for a reboot it just keeps looping. Even when i select no i dont want to reboot and then try and go into recovery, it loops.
try taking out battery for 2 hours and try again
cool will let it rest and let you know the results when I try again.
ar4senal said:
cool will let it rest and let you know the results when I try again.
Click to expand...
Click to collapse
Do you have insurance on your Evo? Is it still within it's 1 year warranty? It sounds like you got the eternal bootloop of death. Is your bootloader S-on or S-off? The condition you're experiencing is unexplained and usually not fixable. running an RUU is your only hope, and if that failed...your pretty much out of luck.
See this thread: http://forum.xda-developers.com/showthread.php?t=1009672&highlight=boot+looping+no+recovery+access
Yea I'm pretty sure it is still under warranty. I got the phone last August. My bootloader is S-Off. Ill check that thread out.
All you should need to do is wipe and re flash cm7... Our write and re store a back up
Sent by Supersonic!
could be the battery is bad and it is just not getting a constant connection, thus boot looping. i had this issue with a bad battery, swapped it out, no problems
For the record, I mis-spoke...
Sent by Supersonic!
Yea Its not taking anything I flash onto it. No way to get the S On back either. After reading that thread its looking like I am gonna have to somehow fully brick it and take it back to Sprint for a new one......UGH!
First, there are a lot of instances of this happening. Well, not a LOT, but there are several threads about it.
Anyhow, give me a few minutes to upload a file to my mediafire. It's a walk through someone on here wrote that is very detailed and it takes some work, but if everything else fails, it has been known to work.
I'll post the link in a few.
http://www.mediafire.com/download.php?9zc41jsfs7sm1qf
That's it.
You said that you installed the new recovery and still getting loops. That's because you didn't do anything in recovery. Go into recovery and try wiping cache/dalvik cache. See if it boots. If it doesn't go back into recovery go to the wipe menu and wipe everything except SD card and rotate settings. Reflash cm7 and it should work. Loops are a common thing and easy fix
P.s. I don't know if you did this but ill throw it in there anyway. You have to wipe cache and dalvik cache when flashing new kernels.
Sent from my PC36100 using XDA Premium App
ar4senal said:
Yea Its not taking anything I flash onto it. No way to get the S On back either. After reading that thread its looking like I am gonna have to somehow fully brick it and take it back to Sprint for a new one......UGH!
Click to expand...
Click to collapse
You can get s-on with 2 files one you flash in recovery the other in the bootloader (the same way you updated to amon recovery). I would post a link but can't cuz I'm on my evo. Just go into the evo development section and there is a thread like 2nd or 3rd page maybe farther back that is called "how to unroot in 2 steps" or something like that. Just did it for a friend 2 days ago so I know it works.
Sent from my PC36100 using XDA Premium App
The issue is that I cannot get into recovery AT ALL. Have tried numerous things. It just wont go into recovery. I bit the bullet and took it into the Sprint Store, they pulled up bootloader and never noticed the S Off at the top. Unfortunately my phone had undergone some sort of water damage. (?) So they were unable to do anything for me, looks like ill be paying the $100 deductible for the refurb.
On a side note the tech at the store told me he has been harvesting parts from evos and epics, and has amassed quite a collection of odds and ends, and that if I ever needed a screen replaced, etc. He would do it under the table for a small charge instead of going through the insurance company. Since i still have the phone ill try all these things again just to see if I can get it working again.
@HipCat- Posted before i read your post....Ill try those steps here in a minute. Thats something I have not tried.
PhxkinMassacre said:
You can get s-on with 2 files one you flash in recovery the other in the bootloader (the same way you updated to amon recovery). I would post a link but can't cuz I'm on my evo. Just go into the evo development section and there is a thread like 2nd or 3rd page maybe farther back that is called "how to unroot in 2 steps" or something like that. Just did it for a friend 2 days ago so I know it works.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I cant get into recovery.....
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
Okay, so I'm brand new to this board, so I appreciate any input you can give. I have an HTC Droid Incredible, have had it over a year. Have had the phone replaced 3 times due to excessive rebooting.
I have the OEM HTC extended battery, and have had numerous issues on the battery overheating and rebooting the phone. It seems to happen mostly when using the GPS in the car. Its also happened while excessively texting.
After having the phone replaced three times, I decided to root, and am now on CM7. It was working fine for a couple weeks, then rebooted again. I then took the phone to the Verizon store, and they replaced the battery. The phone still tends to reboot!
Please give me any advice you guys might have. I'm at my wits end here!
Again, Dinc, rooted, on GB, and using CM7.
Thanks!
Undervolt. Use incredikernel and incredicontrol. Drop the minium 25 or 50 and do the same to the Max.
-My life is a shooting range, people never change-
Thanks so much, but I have no idea what you're talking about. I downloaded Incredikernel, and it bricked my phone....Any other ideas?
ari-nj said:
Thanks so much, but I have no idea what you're talking about. I downloaded Incredikernel, and it bricked my phone....Any other ideas?
Click to expand...
Click to collapse
It bricked your phone? Can you give some more details at to what happened?
It just came back on the "HTC Incredible" white screen and did nothing. Had to reboot, and restore.
Well at least your phone isn't "Bricked". If it was your phone would not work period. How long did you let the phone sit? I'm running CM and I have Chad's latest Incredikernel and it runs like a champ! I'm assuming you are running the latest AOSP kernel correct?
I have no idea what an AOSP Kernel is, so I highly doubt I am. Last night, I had my phone in my hand for a few minutes, when to download something from the App Market, and it kept resetting. Do you think I might need to uninstall and re-install the App Market? I'm at a loss here...
CM is an AOSP Rom and needs an AOSP Kernel to run not the sense kernel. If u go to the downloads section at incredikernel.com you will see the AOSP Kernels. Download the latest version and flash it when you reboot just set the phone down and be patient. As far as the app that you installed, what app was it? You can uninstall the app and see if that fixes ur reboots
Sent from my Droid Incredible
I downloaded the kernel, and when I went to flash it from the sd card, I still get the same thing. The white "htc Incredible" screen comes on and nothing else. I've let it run for 10 minutes, then I have to pull the battery and the restore to my last backup. Am I doing something wrong?
Thanks again for your patience, I'm just a little retarded when it comes to this stuff...Btw, I like your sig, I actually sell Jager, so I truly appreciate it!
I just wanted to bump this back up to the top to see if anyone else has any ideas. I did a restore to when I first rooted the phone, and everything seemed fine. However, last night, I was watching a couple Youtube videos, and in about 5 minutes the phone reset.
I have tried to flash kernels, but cannot figure that out, so I'm still using the stock kernel from CM7. PLEASE help, I'm beyond clueless, and am about to throw this phone out the window!
Thanks in advance!
If you are flashing the latest AOSP (Gingerbread) Incredikernel it should work. You can try wiping your dalvik cache in CWM and then flash the kernel again. I have read in many posts that people have waited up 15 minutes after flashing a kernel for there phone to boot. Try that and be patient.
ok so the reason why incredicontrol didnt work is because the stock kernel doesnt have HVAS. so do this.
download :http://www.incredikernel.com/wp-con...php?id=2.6.38.8-incredikernel-gb-11272011.zip
also can you tell me which hBOOT you are running and what radio you have.
to find out what hBOOT you are running please turn of the phone.
once off hold power and vol -
at the top left of the screen please post all that is there.
for radio go into settings > about phone > Baseband Version
please post this info.
boot into CWM do not use rom manager to install.
flash zip above.
reboot and wait. it should take up to 2 min for the phone to rebuild dalvik and boot into the os.
then install incredibcontrol from market.
go to the HVAS tab and lower min by 25 and max by 25.
reboot.
report back please
(note the instructions above will only work for CM7.)
Wow, thanks for all that info! I'm working on installing that kernel now, but before I do anything, I am on Baseband version 2.15.00.07.28
It also says:
Incrediblec XC Ship S-Off
HBOOT-0.92.0000
Mircrop-0417
Touch Panel-ATMEL224_16ab
Radio-2.15.00.07.28
Jul 23 2010,18:06:51
I will report back later on with my progress.
Thanks again!
I'm trying to reboot into hboot, but now I cannot get into CWM...I have no clue what's going on! HELP!
ari-nj said:
I'm trying to reboot into hboot, but now I cannot get into CWM...I have no clue what's going on! HELP!
Click to expand...
Click to collapse
What happens when you try to go in recovery (CWM)? Don't freak out, if you can't get into recovery you may just need to reflash it. This can be done with Rom Manager or Hboot.
Also you need to update your radio to a Gingerbread radio if you are using CM7. That is more than likely the reason your phone stays on the HTC screen after you flash the Incredikernel. If you have never updated your radio do some research first or just ask and I'll help you thru it.
I have to research the new radio... I was trying to backup from rom manager, and it still stuck on the white screen. Any suggestions on the new radio? I had no clue that it had to do that as well.
Sent from my ADR6300 using XDA App
ari-nj said:
I have to research the new radio... I was trying to backup from rom manager, and it still stuck on the white screen. Any suggestions on the new radio? I had no clue that it had to do that as well.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Go here http://pvillecomp.com/?page_id=18 and download the 2.15.10.07.07 (Gingerbread) radio. All you need to do is name the file PB31IMG.zip and place it on the root of your SD card, basically not in any folder. Just to be safe make sure you don't have any other PB31IMG files on the root of your SD card. Then go into Hboot (Volume down = Power button), just wait (like 5-10 seconds) and you will see that it will auto load the file. When it is ready it will ask you if you will like to install, accept by pressing the volume up button. Let it do its thing, when its done it'll ask you if you want to reboot, hit the volume up button to say yes. Make sure you have a good charge or leave it plugged in to your charger. After you do this wait and see if the phone boots properly, wait like 10 minutes or so. Let me know how that goes...
I'm at a loss here...I did just what you said, and when I get into Hboot, nothing happens....I really don't know what else to do. Is there any way to un-root the phone, and start from scratch? At this point, I cannot get into CWM, and cannot revert back to a restore, so what are my options?
Is your SD card in FAT32 format? You can check on you pc/laptop, just right click on it go to properties. If it is not in FAT32 format you will need to reformat your SD card. Before you reformat it copy everything from your card and paste it to a folder on your desktop. Then reformat your SD card to FAT32, then paste everything back to your card. This could be why your phone is not loading the PB31IMG file (The radio you are trying flash in Hboot).
Ok, stupid me renamed it .zip, as opposed to not...got the radio on there, but still cannot get it to boot into CWM. I feel I'm making a little progress. However, when I go to into Hboot, it still comes up asking if I want to upgrade the radio...It shows Radio 2-15.10.07.07