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.
Related
I've tried searching the forum on this one, and I can't quite find a thread that describes my exact problem. For the most part, people's problems seem to be resolved by performing a full wipe prior to installing a ROM.
I rooted my Desire (Telus GSM, SLCD screen) a long ways back, using Unrevoked 3. I loaded clockwork recovery 2.5, and upgraded the radio. After a while I wanted to try some custom ROMs, or at least get Froyo. I tried Leedroid primarily, plus a few others. I always wipe/factory reset, wipe cache, and wipe Dalvik cache beforehand.
Every ROM I tried had the same problem - it would install, and boot up perfectly. I could use the phone, install apps, etc. But as soon as I would reboot the phone, it would freeze at the green HTC screen and never go past this again.
I finally found one ROM that worked - it was a stock HTC Sense Froyo ROM.
Its getting to the point where I wanted to upgrade again, to Gingerbread this time. I've tried Oxygen and Redux, and they both hang at the HTC logo on the first reboot as before.
I've played with partitioning with my SD card with gparted, resizing the FAT32 partition and putting an EXT3 partition on the end, and when that didn't fix it repartitioning the card from scratch. I also upgraded to a newer radio. Same result..
I was wondering if anyone else has experienced this on their Desire and gotten past it. Unfortunately I don't have a lot of time to mess around right now, but I'd appreciate any suggestions and I'll try them as soon as I can.
T-Mobile G2 Bootloop
I have a T-Mobile G2 which is bootlooping on CM7 and Virtuous GLite 1.0.1. I have been running CM7 without problems since it was released. The bootloop started during the night without any prior symptoms. I have searched the xda and other sites extensively for days and tried so many things to fix this, some of which I was unsure about, but figured 'what the hey' since I had such limited success reflashing roms, clearing data, dalvik cache, etc...
Here is some information:
If I immediately put the phone in airplane mode upon bootup while running CM 7.03 it will not go into bootloop. I can use it indefinitely in this state (it seems) but there is only so much fun you can have in airplane mode...
With CM7.03 installed, here is the info from my 'about phone' section:
Model: HTC Vision, Android Version: 2.3.3, Baseband Version: 12.28b.60.140eU_26.03.02.26_M, Kernel Version: 2.6.32.40-cyanogenmod [email protected] #1, Mod Version: CyanogenMod-7.0.3-vision, Build Number: GRI40
I have Rom Manager v4.2.0.2
-----
Some other information:
I am, however, able to run another mod, Stock w/root (http://forum.xda-developers.com/showthread.php?t=836042) which I was able to flash, along with pershoot's kernel (http://forum.xda-developers.com/showthread.php?t=847672). When I run this mod I am not able to activate WiFi. I click to enable it and after a few seconds I get an error and it turns itself off.
Interesting to note- the first boot-up after flashing CM7 I get about 20-30 seconds before it starts bootlooping. During this time I tried to quickly activate WiFi and it errored out the same way is it did running the "Stock w/root" mod listed above.
This made me think (in my limited knowledge) that it could be related to a radio issue... so I tried to flash a couple different radios claiming to be for the G2/desire. No luck there.
-------
I am able to access recovery mode, flash roms, restore roms, etc...
-------
The bottom line for me, I want to run CM7... I know it works(ed) on my phone. How many layers do I have to strip away to get to the point that whatever bad thing is causing my phone to do this with multiple roms is gone?
Rom? Kernel? Radio? what else is there to fix? Any suggestions on where I go from here? What about the no WiFi issue?
I have already searched the forums as I stated, so linking the first 'G2 bootlooping solved' thread you can find probably wont help me. Maybe understanding more about what could be causing this so I can have a direction to persue this further would be most helpful.
Thanks very much!
Did you wipe your phone before applying CM7?
re: did you wipe your phone
blackknightavalon said:
Did you wipe your phone before applying CM7?
Click to expand...
Click to collapse
Yes- in recovery mode I performed a wipe, then cleared cache and dalvik cache before flashing.
---------
Also, to add more info to the original bit of information I shared- last night I flashed CM6 without any bootlooping issues, but the WiFi problem is still there.
Is it possible to set a radio image to read only so that a recovery wipe/dalvik cache clear will not have permission to clear it? If so, maybe when I flashed a radio before I set it that way without knowing (I honestly can't remember, but I do know that at one point a guide had me flashing something using fastboot and setting chmod something-or-other).
^ I guess I can just press Vol down and Power to check my radio version to see what one I am running and check if it is compatible with CM7.
Any suggestions?
Crazy coincidence.. This morning at 7:45 am my wifes G2 started boot looping. I know it was 7:45, because it was about the time the alarm was supposed to go off.
Hers appears to be a bit worse off, as while I can get into hboot, it won't let me into recovery (and it boot loops before i see cyanogen logo).
I curious to see if anyone else is seeing this, and what the fix might be. I haven't really tried much except getting into recovery since I'm cautious to screw it up further.
Anyone have any ideas?
I now firmly hold the hypothesis that my individual bootloop problem is being caused by my wifi adapter. I am able to flash any rom that doesn't use a kernel based on CM7. On every rom that works ('Stock w/root', Cyanogen6, GingerSense) the WiFi is the only problem. On CM7 and another rom I flashed which was based on the CM7 kernel it bootloops.
So, I am convinced that something in the CM7 kernel polls my wifi adapter when it starts up, figures out that it is borked and then craps out and goes into a bootloop. To further reinforce this idea, as I mentioned in an earlier post- I can boot into CM7 based roms while in airplane mode and use them indefinitely that way. As soon as airplane mode is disabled it goes bonkers.
I'm done t/s this issue for my problem, going to replace the device.
sgshanaf said:
...I can get into hboot, it won't let me into recovery (and it boot loops before i see cyanogen logo).
Click to expand...
Click to collapse
What happens when you select recovery from hboot? If nothing, what about trying a factory reset from hboot? I neither work you should have access to fastboot, but I understand your hesitation if that is the only option you have. Some things I have come across in my searches that could cause bootloops were sim cards, sd cards, and a mess of other things. You can try pulling out the two of those one at a time and doing a normal startup to see if anything changes. Let me know how far you get with the HBoot options and I will try and suggest some other things based on that.
Thanks for responding. I spent a lot of time reading all the different posts I could find with similar issues and decided to take the plunge on this solution:
http://forum.xda-developers.com/showthread.php?t=912399&page=4
and it worked for me.
**UPDATE: below I was having a problem not being able to instal a rom. For whatever reason CM 6.1.1 worked fine. I was then able to go into rom manager and update that way to CM 7.03, and that time it worked. No clue what happened, maybe a bad rom .zip, maybe my SD card is getting flakey. /Shrug
The Phone is booting into that rom fine. Interestingly, while the phone now has eng hboot and working CWM recovery (in addition to still reporting S-OFF), I can't get past the "HTC" splashscreen after installing cyanogen 7 update.zip for the phone. GAPPS or not. I am doing the cache and data wipes
I can get back into recovery fine, but it's just not taking the rom install.
Scott
greenguitar28 said:
What happens when you select recovery from hboot? If nothing, what about trying a factory reset from hboot? I neither work you should have access to fastboot, but I understand your hesitation if that is the only option you have. Some things I have come across in my searches that could cause bootloops were sim cards, sd cards, and a mess of other things. You can try pulling out the two of those one at a time and doing a normal startup to see if anything changes. Let me know how far you get with the HBoot options and I will try and suggest some other things based on that.
Click to expand...
Click to collapse
Hey guys, I was wondering if you all could help me with an issue I've been having lately.
For some reason, I can't flash any ROMs. When I do, it hangs and hangs and hangs on the Splash Screen. It hasn't always been this way, everything worked just fine until last month I flashed MIUI. It worked, but after I decided I didn't like it, I couldn't flash any new ROM, and none of my backups worked until I wiped data and what not.
I've reformated my SD card, and I still can't flash any new ROMs. Help?
I'm kind of worried that if I decide to flash the stock 2.3 update when it comes, I'll brick my phone.
I struggled with my phone for three days trying to flash roms recently. At one point I went to an older version of CWM 3.0.0.5 and it worked once, but then it stopped flashing again.
Tried Amon_Ra and didnt have any luck either due to signatures or something. Went back to CWM 3.0.0.8 and havent had any problems since. CWM must be messing up every once in a while or something.
Good Luck
Sorrows said:
Hey guys, I was wondering if you all could help me with an issue I've been having lately.
For some reason, I can't flash any ROMs. When I do, it hangs and hangs and hangs on the Splash Screen. It hasn't always been this way, everything worked just fine until last month I flashed MIUI. It worked, but after I decided I didn't like it, I couldn't flash any new ROM, and none of my backups worked until I wiped data and what not.
I've reformated my SD card, and I still can't flash any new ROMs. Help?
I'm kind of worried that if I decide to flash the stock 2.3 update when it comes, I'll brick my phone.
Click to expand...
Click to collapse
I've had the same problem then someone suggested I flash a temporary 2.x clockworkmod to whipe bc clockworkmod 3.x has reported issues of not wiping completely.
Here's the zip I used, flashing will temporarily give 2.5.1.2. When you reboot, it will be back to whatever you had before. Also try repeatedly wiping data, cache, dalvik 3x or more. Hope this helps
http://forum.xda-developers.com/attachment.php?attachmentid=549325&d=1300835217
MojoRisin011 said:
I've had the same problem then someone suggested I flash a temporary 2.x clockworkmod to whipe bc clockworkmod 3.x has reported issues of not wiping completely.
Here's the zip I used, flashing will temporarily give 2.5.1.2. When you reboot, it will be back to whatever you had before. Also try repeatedly wiping data, cache, dalvik 3x or more. Hope this helps
http://forum.xda-developers.com/attachment.php?attachmentid=549325&d=1300835217
Click to expand...
Click to collapse
And that could cause it to hang on the Splash Screen?
Sorrows said:
And that could cause it to hang on the Splash Screen?
Click to expand...
Click to collapse
I'm just speaking from personal experience.. it can't hurt.
Is your hboot version .92?
Sent from my ADR6300 using XDA App
INCREDIBLEC XD SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.07.28
And it could hurt actually, because it is incredibly difficult for my phone to restore even.
Also, I can't flash the alternate recovery for some reason. Every time I try, it says there was an error.
Sorrows said:
INCREDIBLEC XD SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.07.28
And it could hurt actually, because it is incredibly difficult for my phone to restore even.
Also, I can't flash the alternate recovery for some reason. Every time I try, it says there was an error.
Click to expand...
Click to collapse
You know.. its interesting that you mention this..
I have been following the CM7 nightlies for a while, and got fed up at one point and just stuck with one of there nightlies. Well... I noticed I couldn't flash ANYTHING at one point. Couldn't upgrade the kernel, radio, ROM... it would all cause it to hang up at the boot screen. I had to get EVERYTHING back to exactly how it was and then restore the most recent image I had created. It's the only thing that will work on my phone as of now. I wonder what happened, I feel like the phone lost its writing ability or something..
I had a similar problem a while back. I had a 2GB laying around as a spare, made sure it was formatted on my comp FAT32 and then put whatever ROM I wanted on it and tried it from there. It stopped the looping issues I was having. So I saved all my stuff from my daily SD card (16GB) and formatted that and put it back in the Inc and I haven't had a problem since. Maybe try a new SD?
Hypcrsy said:
I had a similar problem a while back. I had a 2GB laying around as a spare, made sure it was formatted on my comp FAT32 and then put whatever ROM I wanted on it and tried it from there. It stopped the looping issues I was having. So I saved all my stuff from my daily SD card (16GB) and formatted that and put it back in the Inc and I haven't had a problem since. Maybe try a new SD?
Click to expand...
Click to collapse
Your right, I think I'm going to try another SD card... or back this one up and format it...
But the weird thing is I can flash tweaks to the ROM, but I can't change kernels, ROM, radio.... without it getting stuck on the splash screen...
But I'm gonna go ahead and try another SD, because I had another SD that messed up on me, and it gave me similar issues. I just haven't had any problems with this one... so yeah.
If that doesn't work, you might try doing an RUU completely back to stock. then try flashing a new ROM.
Good luck!
Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
eMMC-boot
OS ver 1.34.707.3
CID 1111111111
Click to expand...
Click to collapse
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
cyber-mythius said:
Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
Click to expand...
Click to collapse
Pull /proc/last_kmsg and see what it says; should help you narrow it down.
Sent from my HTC Vision using XDA App
could you gimme hand how? - the only point where I can get in the phone is to bootloader / recovery.
so i cant run terminal from apps in phone.
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
cyber-mythius said:
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
Click to expand...
Click to collapse
Sorry, I just got to work. The last_kmsg is on your device, not the sdcard. If you have ADB set up you should be able to access it by connecting your phone to your computer
Sent from my HTC Vision using XDA App
I have everything installed on the other PC where Ill be on monday. Maybe Ill find some time to look through it tommorow.
Thank you now for pointing me somewhere - Ill add more info when I ll have it.
I had a similar problem after flashing new rom. My Desire Z was also rebooting after a few seconds.
I downloaded 1.34.707.3 firmware(used to downgrade Desire Z from gingerbread) from CM wiki, installed it through fastboot (step 8) , rooted my phone once again following the wiki and since then my phone is working without any problems.
Battery can be charged up while the phone is turned off.
well I flashed phone with the downgrading rom as you mentioned and it helped a little
- phone is running and not restarting after few seconds - but randomly after 5-60 seconds (so I am able to do at least something ))...
On monday I ll root that bi*ch again, pull there CM7 or some other ROM and post here actual status.
Thank you so far
Similar problem
Hi, I have the exact same problem with my Desire Z. I've attached the last_msg if someone could help me with that.. also, my sdcard is not partitioned so could that have anything to do with it? Thanks, hopefully I'll get an answer soon
Resurrecting a bit of an old thread here but I have just experienced these exact symptoms.
A friend gave me his old Desire-Z so of course I immediately set about rooting it and trying some ROMs.
As a start I went with the most recent Cyanogenmod which is 7.2 at this time. Everything was going smoothly and was just getting used to the phone and it's physical keyboard. My biggest worry was that the battery life wouldn't be good enough for me so I was running a test to see how long it would last. I am a very light phone user. With background wifi disabled, gps disabled and the phone set to 2G only it ran for 7days and 3 hours! No problems there even with a well used battery. When it eventually died I hit the power button to wake it and it started booting and then shutdown again as you would expect. However after I had fully charged it it booted no problems but then went into the boot loop described above. It boots successfully to the home screen but then after 10-15 seconds it reboots. Frustrating!
I tried some things:
Clear cache from CWM: No change
Factory reset from CWM: No change
Reflash CM7.2 from CWM: No change
Clear Dalvik Cache from CWM: No change
Clear Battery stats from CWM: No change. I was hopeful this might be the problem as the battery had been unusually flat, perhaps some flag had been set that caused the reboot.
I have now recovered by reflashing the exploitable original image, PC10IMG.zip, and then going back through the rooting process. I wouldn't want to have to do it again though.
Possible explainations for the behaviour: I was running a battery monitor app (GSam Battery Monitor) which runs continuously and has various power related functions. Though I would have thought anything that was doing would have been removed by factory reset or reflashing CM.
During the 7 days I was testing ROM manager prompted me to update it and then to update the version of CWM that I had. This is perhaps more likely as would have survived everything else I tried to recover until I reflashed the original recovery.
Hope that helps someone and if anyone has any insight on this I'd lobe to hear it.
Steve
Looks like I spoke too soon. First time I had to reboot the phone I got stuck in the reboot loop again.
Hmm, really confused now. No idea what can be causing this that isn't solved by reflashing CM7.2 but is by going back to the original rom?
Steve
the only thing, that helped me back then was to flash another ROM ... give it a try.
there is several other ROMs based on CM, I'm pretty sure, that you'll find one, that will suit you best.
Thanks for the reply I appreciate you taking the time.
It's very odd I can't think what might be causing this. I ran CM7.2 with zero issues for a week. Then first time I had to reboot it gets stuck in the loop.
Since I was away from home I could not get into recovery. I could get into HBoot (by holing Vol. Down + Power) but because I had a PC10IMG.zip file on my sdcard it would just go straight in to asking if I wanted to update from that with no way to select recovery. And of course I needed to have the sdcard in the phone to get an image from it!
So I have been running from the exploitable 2.2 Rom from the rooting procedure since. That can reboot no problems.
Today I tried a much more recent CM10.1 based rom - stuck in boot loop.
Then a tried the Rooted G2 stock ROM which is obviously much older. It booted correctly one time. Then I rebooted it (actually shutdown and then turned on, it doesn't have a reboot option) and now I'm stuck in the reboot loop.
I'm doing a factory reset and clearing the Dalvik cache after flashing each ROM.
I have also tried booting without the sdcard or SIM card, no change.
Something I have observed is that the phone will reboot once after flashing with every ROM, even the original ROM, but then either runs correctly or continuously reboots.
I can only think that possibly I have wrong phone model. I know that the previous owner bought this contract free so it may be some import. Perhaps it's actually a G2 and I'm using the wrong HBoot? I think that's unlikely as it would show an error during the rooting process.
Steve
I doubt you have the wrong hboot, it wouldn't even start if you did. I would do a complete wipe and format maybe change firmware as well. Backup SD and reformat that as well. If you have true radio soff (rooted via gfree) then you are safe to use one of the pc10img.zips I created here
http://forum.xda-developers.com/showthread.php?p=27796375 (see post 30)
Make sure to remove it from SD this time or at least change the name when done
This will give you new engineering hboot, updated 4ext recovery, .19 radio but all can be changed to whatever if you want.
After the flash reformat all in recovery and flash a new rom
Sent from my Nexus 7 using xda premium
Thanks for your input.
Updating the radio rom does seem tempting if potentially dangerous! The claimed power saving especially. I haven't ever used 4ext recovery but given how CWM seems to be failing me I might give it a try.
I don't wan to speak too soon here (but doing so anyway!) it looks like I may have corrected the problems by using SuperWipeG2+ from here: http://forum.xda-developers.com/showthread.php?t=1044992
After running that, which can easily be done from CWM, the phone booted first time with no reboots.
I'll update this if that did not fix it.
Steve
Yep spoke too soon!
However I have found a way to reliably recover but it's not straight forward.
Boot to recovery. Run SuperWipeG2+.
Attempt to boot the phone, boot fails as there is no ROM installed. This step seems important.
Boot to recovery. Install ROM from zip and Gapps from zip.
Reboot and phone will boot successfully and stay booted!
I then have to recover all my contacts and apps from Google which takes a further 20/25 mins.
Having done that I still cannot reboot the phone. If I reboot (or shutdown and power on) it is then stuck ion the boot loop and I have to do that all over again!
This means I cannot ever allow the phone to go flat.
Aaarrgh!
Any suggestions? It has been suggested that installing another ROM could fix this. Any specific ROM? Any idea why that would work?
I have found that the light sensor doesn't seem to be working and the suggested fix for that is to install a Sense based ROM and then switch back. I can't see how that could work either.
Steve
Yeah I've heard the sense ROM thing works, I don't see how but people seem to swear by it. I would suggest you change all your firmware, new hboot, new radio, new recovery and what not a new ROM. There are lots of good ROMs to choose from so I wouldn't know what to recommend for you, personally I almost always use gingerbread based ones
Sent from my Nexus 7 using xda premium
HI,
I am facing a peculiar kind of a problem. I recently rooted my Desire Z following the cyanogen wiki to the letter. I have tried many ROMS but whichever ROM I install, I am facing this problem. For the first few days of Install, my phone works perfectly. But after a few days if I reboot, my phone gets stuck is a bootloop( i dont know if thts the right word, coz it boots and it starts the android but before the launcher is started it restarts again.
First I was using Flinny's CM10.1 test builds, and then I changed it cause I thought that was the problem. Now I am using Andromadus' Mimicry 1.5 which is also giving me same problem.
Everytime this happens I have to use the PCIMG10 file to restore it and then root it again and then install the ROM..
Is there any way to solve this problem.. I'll provide logs if u require... I am desperate..
yes a log cat would help much maybe a cat /proc/last_kmsg or have adb running during the bootloop and post here.
seems a strange issue and may just be an evil app installed or something else entirely but without more info i would just be guessing. and do actually have to reroot? i mean what would happen if you were just to wipe clean and install a new rom via recovery? also it may help so could you provide all that is on your bootloader screen
also see HERE for some more help, feel free to post in there as well (trying to reduce the clutter in these forums)
demkantor said:
yes a log cat would help much maybe a cat /proc/last_kmsg or have adb running during the bootloop and post here.
seems a strange issue and may just be an evil app installed or something else entirely but without more info i would just be guessing. and do actually have to reroot? i mean what would happen if you were just to wipe clean and install a new rom via recovery? also it may help so could you provide all that is on your bootloader screen
also see HERE for some more help, feel free to post in there as well (trying to reduce the clutter in these forums)
Click to expand...
Click to collapse
I have a logcat from when I was running Flinny's CM10.1 test builds.. I faced this many times with that ROM and so I took a log last time it happened.
BootLoopLog_CM10.1
The latest time since I was in a hurry to get my phone back to working condition couldnt get a log. But soon after, it happened again. I installed only "Explorer" and "What'sapp" when this happened again. I have captured the logs and here it is.
BootLoopLog_Mimicry1.5
And ya I did try and restore a previous backup, and I also tried wiping and installing the ROM, but in both the cases the Phone will hang at the boot animation screen or restart again. Here attached is a log of the phone restarting after a clean wipe and fresh install of the ROM.
BootLoopLog_Mimicry1.5-after reinstall
Code:
Bootloader screen info
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.03.02.18_M3
eMMC-boot
Sep 8 2010,15:56:30
Please help me out... this is kind of frustrating.
P.S- I did see that thread.. but since my phone was not bricked, I didnt post it over there..
are you sure you did a full wipe? there was definitely more than just a couple user apps installed, could be some leftovers from last rom. there isnt anything im seeing too specifically in the logcats to show your issue, all of them seem to bootloop in slightly different times but while running some java system frameworks
anyhow, if you were to start completely fresh, unroot, reroot, flash rom, etc - all works fine? lets say you just signed into gmail, then reboot phone, would it loop? or do you need to run the os for some time then turn it off and then it happens?
for now how about this, flash THE DZ ONE through bootloader as described in the thread,
then flash SUPERWIPE through recovery
then when all is done flash rom of choice, for fun lets do mimicry, let it boot, sign into google, let phone sit like 10min, choose reboot and see what happens
demkantor said:
are you sure you did a full wipe? there was definitely more than just a couple user apps installed, could be some leftovers from last rom. there isnt anything im seeing too specifically in the logcats to show your issue, all of them seem to bootloop in slightly different times but while running some java system frameworks
anyhow, if you were to start completely fresh, unroot, reroot, flash rom, etc - all works fine? lets say you just signed into gmail, then reboot phone, would it loop? or do you need to run the os for some time then turn it off and then it happens?
for now how about this, flash THE DZ ONE through bootloader as described in the thread,
then flash SUPERWIPE through recovery
then when all is done flash rom of choice, for fun lets do mimicry, let it boot, sign into google, let phone sit like 10min, choose reboot and see what happens
Click to expand...
Click to collapse
What I mean by full wipe is.. First I would do the factory reset from recovery, then proceed to wipe the "cache partition" , dalvik cache, battery stats, and then in the mounts and storage menu, again do a format of cache, data and system... Is there anything else I should do to do a clean wipe?
And If i start fresh, nothin happens immediately.. u need to let the OS run for a day or two and then this happens..
Anyways.. i'll try what you suggested and get back to you.... thanks for all the help..
manujosephv said:
What I mean by full wipe is.. First I would do the factory reset from recovery, then proceed to wipe the "cache partition" , dalvik cache, battery stats, and then in the mounts and storage menu, again do a format of cache, data and system... Is there anything else I should do to do a clean wipe?
And If i start fresh, nothin happens immediately.. u need to let the OS run for a day or two and then this happens..
Anyways.. i'll try what you suggested and get back to you.... thanks for all the help..
Click to expand...
Click to collapse
I did what you suggested.. and the phone is not rebooting as of now... I'll run the OS for a couple of days..and see what happens.. i'll keep you posted..
manujosephv said:
I did what you suggested.. and the phone is not rebooting as of now... I'll run the OS for a couple of days..and see what happens.. i'll keep you posted..
Click to expand...
Click to collapse
Guess what... That worked... My phones been running without bootloop till now.. :good:
Everytime I reboot, my heartbeat increases.. but it comes through smoothly at the end.. thanks a lot..
P.S - Completely off the topic.. Mimicry ROM is giving me insane battery life.. Running the phone more than 1 day without charging.. :laugh: