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.
Ive had nothing, but bad luck lately and i'm not sure why. I got a factory replacement in the mail today and everything was good, but i wanted to get all my custom stuff back so i rooted it and then after that i was in hboot and no matter which option i would choose it would bring me to a black screen with white bars down the sides. i did some research and got clockwork working properly. it ended up being some issue with unrevoked not recognizing the new screens they are putting in the dincs or something like that. ANYWAYS, now I cant get my phone to boot past the "HTC incredible" screen. Ive tried installing previous nandroid backups and nothing works. When I try to do a factory reset i get a message that says "E:Invalid command argument". I know the basics like rooting, flashing, and theming, but I don't know what to do about this situation i've got right now. All i want to do is get my phone to boot. Any ideas?
Thanks in advance. This community is an amazing source for help.
Also, I'm getting this when I try to wipe data
localceleb said:
Also, I'm getting this when I try to wipe data
Click to expand...
Click to collapse
Seems like you have the slcd screen you need the update for clockwork mod. Not sure what the link is though I now its on koush's Twitter somewhere
RLKirk said:
Seems like you have the slcd screen you need the update for clockwork mod. Not sure what the link is though I now its on koush's Twitter somewhere
Click to expand...
Click to collapse
I have updated Clockwork and I still am unable to get my phone to boot past the initial HTC Incredible screen no matter what....very frustrating!!
Late last night I was able to get my phone to boot up after flashing Skyraider 3. And it seems to be running pretty stable right now. Should I be concerned about trying to load any other roms at this point?
so I know just enough to be dangerous.... apparently.
I decided to start fresh, completely... wiped user data, dalvik, cache and did the factory reset thing. then I reflashed warm 2.2 and can not get past the white htc evo 4g screen. I have done a nandroid backup that is still there and I have tried to restore that, but it still goes to white screen and stays... I keep it on the white screen and after 15 minutes I try again after removing the battery... any ideas would be great... I am not an expert but I have installed different ROMs in the past without any real issue.
So, to summerize.
I have a rom on the device,
I can boot into recovery, hboot, etc
I can flash rom's, or the backup but can not get past white screen...
Thanks!
Maybe your SD card is going or the files on there are messed up try flashing different Rom something basic like fresh and see what happens
Sent from my PC36100 using XDA App
so what is the easy way to put a new rom on when you cant get the phone to boot up? Do I have to do it from a reader? Sorry, told ya I know enough to be dangerous.
resolved
put a different kernel on it, and it booted, thanks for the help though!
Installed, went to reboot system, all it does it go to the htc incredible screen, reboot, htc incredible screen, then goes to recovery. wtf over?
so i formated the cache, dalvik, and fixed permissions and still no luck.
what do i do next?
I second this...
In fact, today was the very first day it wouldn't do that when I flashed a Sense 3.0 ROM... now it's back to not flashing them anymore.
They weren't kidding in the instructions where it says to wipe cache/data three times. I started from scratch, wiped everything a bunch of times, reinstalled and it worked. My phone is very picky, because when I flash any ROM, it will never load the first time unless I go back and re-wipe everything. It's a pain, but it's a nice rom. Only thing i found that doesn't work is the flash on my camera, and the flashlight.??
RMinor205 said:
They weren't kidding in the instructions where it says to wipe cache/data three times. I started from scratch, wiped everything a bunch of times, reinstalled and it worked. My phone is very picky, because when I flash any ROM, it will never load the first time unless I go back and re-wipe everything. It's a pain, but it's a nice rom. Only thing i found that doesn't work is the flash on my camera, and the flashlight.??
Click to expand...
Click to collapse
What version of Clockworkmod are you using?
I had made sure I had done it several times.... and it's very arbitrary to be honest it seems whether a ROM will flash or not. RLS7 seems to flash just fine... but I can't get .5 on there again... I'll see what I can do..
Yeah... so apparently my phone is an exception of sorts... it seems like I've been having trouble flashing any sort of Gingersense ROM... but I am able to get RLS7 onto my phone. It's booting now. But I can't for the life of me seem to be able to get .5 on there. What's the difference anyways? Anyone.\lol
**By the way, I am 100% sure I wiped everything 3 times... and it would still get stuck on splash screen.
BrettApple said:
What version of Clockworkmod are you using?
Click to expand...
Click to collapse
3.0.0.8
i'm going to update to RLS 0.5... maybe. Just to see if that fixes the bug.
It says "flash disabled due to cold weather, low battery, or use of an app that uses a lot of battery power".
I live in Florida, have a full battery, and haven't re installed any apps.
Installing 0.5 - hopefully it worked.
Wiping several times DOES NOTHING. No matter if you say it did or not. The way to fix that, as I have had it happen is simply flash the rom again without wiping. So, say you wipe and flash, reboot, it goes back to recovery, just install zip again.
I also have the "flash disabled due to cold weather, low battery, or use of an app that uses a lot of battery power". Full battery, no high power apps running.
Hey everyone... Im in a serious situation... I have scoured the entire internet trying to find a solution to my boot loop problem, but it isnt looking good... I originally had an older version of CWM, then a while back I flashed the original stock recovery and used the phone that way... well recently, I got bored and wanted something better than the 4.1.2 JB stock mod, and wanted something a little more, new! (which is why were all here, yeah?) anyways, I reflashed CWM (i dont remember which one, but it had to be older) and kept getting the dreaded STATUS 7... so, I moved up to PhilZ Touch 6 (CWM 6.0.4.5), and was able to flash 4 different roms..... but EVERY single one of them just boot loops... Also, I would have cleared DALVIK cache (in both older and NEWER CWM), but it doesnt do a damn thing... like it literally flickers the screen for a half second, and goes right back to where I was..... I just need a working phone!!! I honestly dont give a damn what OS I am using, I just cant go another day without my phone. Any and all help is much much much appreciated.... (Crosses fingers)
I am also getting every sort of E: cannot do this or that or mount bla bla bla...
I am still able to get into recovery, sync with Odin and do minimal things... Only thing it WONT do is BOOT!
JeffreeHomicyde said:
Hey everyone... Im in a serious situation... I have scoured the entire internet trying to find a solution to my boot loop problem, but it isnt looking good... I originally had an older version of CWM, then a while back I flashed the original stock recovery and used the phone that way... well recently, I got bored and wanted something better than the 4.1.2 JB stock mod, and wanted something a little more, new! (which is why were all here, yeah?) anyways, I reflashed CWM (i dont remember which one, but it had to be older) and kept getting the dreaded STATUS 7... so, I moved up to PhilZ Touch 6 (CWM 6.0.4.5), and was able to flash 4 different roms..... but EVERY single one of them just boot loops... Also, I would have cleared DALVIK cache (in both older and NEWER CWM), but it doesnt do a damn thing... like it literally flickers the screen for a half second, and goes right back to where I was..... I just need a working phone!!! I honestly dont give a damn what OS I am using, I just cant go another day without my phone. Any and all help is much much much appreciated.... (Crosses fingers)
I am also getting every sort of E: cannot do this or that or mount bla bla bla...
I am still able to get into recovery, sync with Odin and do minimal things... Only thing it WONT do is BOOT!
Click to expand...
Click to collapse
Have you tried to flash a stock rom through odin? It'll restore your kernel, recovery and system back to stock and should not bootloop.
What carrier are you with?
chevymeister said:
Have you tried to flash a stock rom through odin? It'll restore your kernel, recovery and system back to stock and should not bootloop.
What carrier are you with?
Click to expand...
Click to collapse
Yes, of course. I have been online for 2 days straight trying to fix this issue and tried MANY "FIXES" for similar issues, but no Cigar...
I am with TMO (SGH-T999L) US, btw
I would sincerely love just to have my phone back and operation-able..... weather an old custom ROM or back to factory 4.1.2 ... I truly dont mind either way, I just need her working again. lol
You need to factory reset most likely. Wiping dalvik alone doesn't usually solve boot hangs. Factory resetting almost always does.
DocHoliday77 said:
You need to factory reset most likely. Wiping dalvik alone doesn't usually solve boot hangs. Factory resetting almost always does.
Click to expand...
Click to collapse
That did absolutely nil. Tried it many many times over...
I think a sensitive folder got deleted or something. I just had them send me a replacement. Thanks!
Ok. Sorry I couldn't help. Glad to hear you're getting it taken care of though!