CM7 crash then boot loop 16gb SD - Droid Incredible Q&A, Help & Troubleshooting

I flashed #11 and I'm getting random shut downs and a boot loop. I have a 16gb sd, and when I take it out and the battery and boot it, it boots up. I put the sd back in after it boots up and it does the random shut down again and back into loop.
Is anyone else having this issue.

Might Wanna Try A New Rom, I'm Not Having Any Problems
(Yes I Have A 16GB SD Card)

I got 12 and I'll try that in the morning.
Sent from my Htc Incredible using XDA App

Then it sounds like it is a problem with the card? You should format the card using SD-association's tool.
http://www.sdcard.org/consumers/formatter_3

captain_planet said:
I flashed #11 and I'm getting random shut downs and a boot loop. I have a 16gb sd, and when I take it out and the battery and boot it, it boots up. I put the sd back in after it boots up and it does the random shut down again and back into loop.
Is anyone else having this issue.
Click to expand...
Click to collapse
try reformatting your sd card to fat32.......wipe data/cache/dalvik......then reinstall.

My card is fat32 and I did a fresh reformat before installing cm7 a few days ago
Sent from my Htc Incredible using XDA App

captain_planet said:
I flashed #11 and I'm getting random shut downs and a boot loop. I have a 16gb sd, and when I take it out and the battery and boot it, it boots up. I put the sd back in after it boots up and it does the random shut down again and back into loop.
Is anyone else having this issue.
Click to expand...
Click to collapse
**UPDATE**
I have since tried reformatting again and installing CM7 #12 and my phone no longer loops upon bootup, however I still get random reboots. Sometimes the frequency of said reboots are within 10-15 minutes of each other, sometimes it takes a few hours, no rhyme or reason that I can tell.
I do remember when I first got my INC that where I was at the time, in cincinnati, my signal was poor and my phone would reboot from time to time and I assumed it was because of some sort of miscommunication issue. However, where I am now, my signal is fine and I have never had an issue with it no matter where I go.
What could be causing these random reboots and is anyone else suffering the same problem with any of the nightlies that are coming out?

No problems here with my CM7 nightly with a 16gb card. What kernel are you running? Just the default CM7 one?

yes, default kernel. also, no setcpu or anything like it.

One more note. I'm running omgb right now and I don't get any looping or random reboots. It has to be something in cm7 that conflicts with either my SD card or my phone's internal memory or radio. This is the only reason I can muster up.
Sent from my Htc Incredible using XDA App

I was having this problem with a 16GB san disk. I kept having to do a battery pull to stop the loop, and it ended up killing my phone (no power/charging from batteries, cords, anything).
I just got a replacement phone today, permrooted with gfree (SIMLOCK off), flashed CM7, and was having the issue again within 15 minutes. I took out my SD card and put in a freshly formatted 8GB sd. So far so good. I'm going to format the 16 and try it again.
Interestingly, I didn't have this problem until around the time I turned SIMLOCK off. Anyone think this could be a reason for CM to crash and loop?

Related

What just happened?

I've been running CM 6.0.2 and I recently purchased a new SD card. I formatted the card to FAT32 and installed all the files from the old card onto the new one. When I rebooted my phone it didn't read the card as being mounted so I turned it off, took out the card, put in the old one, and turned it on again. I got stuck in a boot loop at the CM splash screen. I had a backup of Virtuous that I have used once or twice before so I went into clockwork and tried to restore it. This is where it gets interesting.
I rebooted and found myself still stuck in the CM boot loop. I pulled the battery after a few minutes, booted back into the recovery and wiped the cache and data. I restored Virtuous again and the same thing happened. I also have a backup of stock Froyo that I have used a few times. This time it got stuck in a boot loop on the quietly brilliant screen after going through to the Droid splash screen.
I still had the .zip for CM that I have been running for the last week or so and tried installing it from clockwork. Sure enough I got the CM boot loop again. I decided to try the stock Froyo one more time and got THAT boot loop and then I tried Virtuous again and now all seems to be well. I have absolutely no idea what happened but if anyone else has any ideas I would love to hear them. That was not something I would like to experience again.

My SD Card causes the phone to freeze

Hey people
Using Oxygen 2.0 RC7
Recovery Amon Ra
Phone HTC Desire PVT4 S-ON
I've had some trouble with my SD card I think.
I always sync my songs from spotify for the offline mode. And after a couple of hours i try to enter gallery but my phone freezes, when I press the ON button I see my buttons interact, but the screen is black? It's laggy as hell, ive tried everything. I wiped everything, reflashed and then it worked. But after 2 hours of using the phone it started to hang again..
Sooo i downloaded Rom manager and tried the filepermission thing, that runs a test. And now I'm running the phone without any problems. But I think that I will have a problem by tonight..
Do you guys know the problem?
Unrooted the phone... everything was normal, but when I started using things that are on the SD card it goes black. And I have to pull the battery... this never happened before rooting...
Tried another sd card now, hope it doesnt happen. The other I used maybe was broken or something? Only had it for 2-3 months.. my phone

Rooted HTC Desire boot loop every three days

Hi. When I first rooted my Desire, I flashed a MIUI rom without having noticed that I needed to create a partition on SD card. What happened is that the phone booted normally, I was going through start settings and suddently it went into boot loop.
Had to remove sd card and use a card reader to copy another rom on it.
I got Oxygen 1.0.4 because it didn't need an ext partition, it also went into boot loop at first but then started, was a little unstable at first but then worked nicely. Only every three days, the cpu would go to 100% and doesn't go back to normal unless I reboot the phone.
Then I got Oxygen 2.0 RC7, thinking it would solve the issue. This time no issue whatsoever after flashing. Everything went normally. No cpu issues, but every three days, the phone goes instantly into boot loop. Only way to restart the phone is to remove battery.
Thank you for your help and suggestions.
BTW, you don't need to create ext partition with MIUI. Are you wiping all data when you're flashing new roms?
Yes I am wiping all data and cache

Seems like a boot loop condition

Hi Folks,
I was setting up my "old", rooted and S-Off Incredible for our son to play games when travelling, etc. - it's no longer registered on Verizon's network, but is fine for wireless and downloaded apps.
After charging the battery and installing about 47 app updates today (i.e., it hasn't been booted in awhile), I was tinkering around with adding some apps from Play and it suddenly rebooted. Then, it kept booting at the white HTC logo screen.
So, I pulled the battery and decided to go back to Verizon stock, using the image from here:
http://dinc.does-it.net/Stock_Images/4.08.605.15/
Essentially, I booted into HBOOT, went into CWM Recovery, wiped appropriate storage, then rebooted back into HBOOT after putting the above image onto the root of my SD card. Maybe I don't need to wipe storage for a RUU, but it's habit by now.
HBOOT installed the RUU image after it prompted for a Yes/No and the Incredible booted with that old, "DROID!!" startup (gosh, didn't miss that) and showed the initial lock screen.
I pulled down the lock and started only a few seconds into phone initialization when it rebooted.
Now, it reboots as early as the HTC logo screen or gets to the lockscreen and reboots on its own after a second or two.
Seems like a boot loop, but I just installed a new RUU - so . . . I'm wondering if this is a deeper issue.
Ideas on how to go about fixing this rebooting problem are welcome, please. Is it possible that my half-completed Play install - i.e., just before it began this symptom - crunched a file system that needs to be fixed up?
Thanks,
- ooofest
Do you get any kind of errors wiping data or cache from recovery? The play install wouldn't have botched up the filesystem but the reboot could have led to corruption in /data. The cause of reboot I wouldn't know without logs. Try pulling the logcat during the boot loop which may or may not work on stock. I seem to doubt it as stock doesn't have USB debugging on by default.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Do you get any kind of errors wiping data or cache from recovery? The play install wouldn't have botched up the filesystem but the reboot could have led to corruption in /data. The cause of reboot I wouldn't know without logs. Try pulling the logcat during the boot loop which may or may not work on stock. I seem to doubt it as stock doesn't have USB debugging on by default.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi tiny4579, I had no errors wiping data or cache within CWM that were visible to me. I agree that USB debugging is not likely enabled by default.
If we assume there's a /data corruption as one angle to go with, should I try wiping and reinstalling the RUU again? I could attempt to put on a custom ROM instead, particularly one with USB debugging enabled (if that exists). HBOOT currently shows Locked and S-Off.
Thanks,
- ooofest
ooofest said:
Hi tiny4579, I had no errors wiping data or cache within CWM that were visible to me. I agree that USB debugging is not likely enabled by default.
If we assume there's a /data corruption as one angle to go with, should I try wiping and reinstalling the RUU again? I could attempt to put on a custom ROM instead, particularly one with USB debugging enabled (if that exists). HBOOT currently shows Locked and S-Off.
Thanks,
- ooofest
Click to expand...
Click to collapse
If data wipe was fine I'm not sure. To test USB debugging flash something like cm7. I think it uses an insecure boot.img meaning USB debugging aka adb should be on by default.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
If data wipe was fine I'm not sure. To test USB debugging flash something like cm7. I think it uses an insecure boot.img meaning USB debugging aka adb should be on by default.
Click to expand...
Click to collapse
Using HBOOT 0.92
Installed CWM 5.0.2 via PB31IMG.zip route
Wiped all available storage areas/paths - no errors shown
Installed cyanogenmod 7.2 from the SD card
On bootup, I saw the CM 7.2 boot screen (i.e., a circling arrow) for about one minute, then it rebooted. And rebooted. And rebooted. So, I'm back to rebooting at the HTC logo screen.
Consider me baffled - this phone was working great yesterday until after updating 47 apps (got a "low space" message at one point, started deleting apps while others were still installing) trying to install another app from Play store. Ideas, perhaps?
- ooofest
ooofest said:
Using HBOOT 0.92
Installed CWM 5.0.2 via PB31IMG.zip route
Wiped all available storage areas/paths - no errors shown
Installed cyanogenmod 7.2 from the SD card
On bootup, I saw the CM 7.2 boot screen (i.e., a circling arrow) for about one minute, then it rebooted. And rebooted. And rebooted. So, I'm back to rebooting at the HTC logo screen.
Consider me baffled - this phone was working great yesterday until after updating 47 apps (got a "low space" message at one point, started deleting apps while others were still installing) trying to install another app from Play store. Ideas, perhaps?
- ooofest
Click to expand...
Click to collapse
Phone might be dying. Does it even get past the HTC screen?
Try reinstalling the ROM.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Phone might be dying. Does it even get past the HTC screen?
Try reinstalling the ROM.
Click to expand...
Click to collapse
Yeah, it tends to get beyond the HTC logo screen after a new ROM install, but usually reboots as soon as I see the notification for "preparing internal storage".
Afterwards, it tends to reboot at varying times - sometimes at the HTC logo, other times it gets past OS startup and reboots after a few seconds.
. . .
EDIT: I just rebooted and . . . now it suddenly booted into CM and is working normally. What the heck?!
I'm not a CM person and would like to install another ROM to see what happens after that - do you think the phone EMMC is starting to go, perhaps?
- ooofest
You might want to format the internal emmc and sdcard as the reboots could be related to filesystem. Grab /proc/last_kmsg if you want me to check.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
You might want to format the internal emmc and sdcard as the reboots could be related to filesystem. Grab /proc/last_kmsg if you want me to check.
Click to expand...
Click to collapse
Thanks, I couldn't find a last_kmsg to pull, but I wiped all storage available (including emmc and sdcard), then reinstalled the latest RUU for a test.
Bootup went OK until it rebooted again soon after getting to the Gingerbread lockscreen. Oh well.
I decided to try going back to CM7 since it actually booted after a time, so reapplied CWM 5.0.2 and then started to format storage again. When trying to format /system I got a 5 vibrate error.
I've gone through various combinations of reapplying the RUU, adding CWM, trying to wipe storage, etc. and I keep hitting the 5 vibrate shutdown at various points. I couldn't wipe /system without getting the 5 vibrate issue twice, then it worked the third time, etc.
Just now, I was in CWM and merely navigating the menu to go into "mounts . . ." and it 5 vibrated again. Ow.
My suspicion above keeps coming back to me: is my hardware potentially going?
- ooofest
ooofest said:
Thanks, I couldn't find a last_kmsg to pull, but I wiped all storage available (including emmc and sdcard), then reinstalled the latest RUU for a test.
Bootup went OK until it rebooted again soon after getting to the Gingerbread lockscreen. Oh well.
I decided to try going back to CM7 since it actually booted after a time, so reapplied CWM 5.0.2 and then started to format storage again. When trying to format /system I got a 5 vibrate error.
I've gone through various combinations of reapplying the RUU, adding CWM, trying to wipe storage, etc. and I keep hitting the 5 vibrate shutdown at various points. I couldn't wipe /system without getting the 5 vibrate issue twice, then it worked the third time, etc.
Just now, I was in CWM and merely navigating the menu to go into "mounts . . ." and it 5 vibrated again. Ow.
My suspicion above keeps coming back to me: is my hardware potentially going?
- ooofest
Click to expand...
Click to collapse
Could be the battery going bad. Do you have another battery you could try? Mabey once things start loading it pulls to much power and reboots.
cmlusco said:
Could be the battery going bad. Do you have another battery you could try? Mabey once things start loading it pulls to much power and reboots.
Click to expand...
Click to collapse
Yeah, I started charging again to see if that might help, and I've been booting up with it plugged in, too.
Could a battery still be the problem, even plugged in? That is, would a short of some kind be limiting how much could be drawn from the plug?
Wish I did, but don't have another battery on hand.
- ooofest
ooofest said:
Yeah, I started charging again to see if that might help, and I've been booting up with it plugged in, too.
Could a battery still be the problem, even plugged in? That is, would a short of some kind be limiting how much could be drawn from the plug?
Wish I did, but don't have another battery on hand.
- ooofest
Click to expand...
Click to collapse
Even when plugged in the power is going thru the battery, so it could still be the problem. Just a sugestion, may have nothing to do with it at all.
cmlusco said:
Even when plugged in the power is going thru the battery, so it could still be the problem. Just a sugestion, may have nothing to do with it at all.
Click to expand...
Click to collapse
Interestingly, I let it "cool down" for a bit and charge from the wall instead of USB, then was able to wipe all storage, install CM7 and it booted up fine.
So, I let it sit for a bit longer, wiped again and installed the latest stock RUU. This time, it took longer to boot and came up fine - I now have a relatively stock (except for S-Off) Incredible, again.
From your suggestion, I'll shop for another battery and see if a new one helps to keep the sudden reboots at bay.
Thanks.
- ooofest
Hi Folks,
After working this for some days, my Droid Incredible with AMOLED display still gets into a reboot or boot-loop condition after a random amount of time of continuous use. Almost as if it heats up or something in its memory mgmt is flaky.
It can take new ROMs, recoveries, HBOOTs, radios, etc. - but, regular use just brings up the boot condition too easily, so I can't give it to my kid as a simple gaming device. I tried a new battery in case that might be the issue, but the condition still persists. Pulling the battery and waiting 10+ minutes usually allows it to work again, until the next reboot cycle starts up.
This phone is running the latest RUU and is also S-Off.
So, I'd like to give it away to the first person who requests it.
I'm not offering a trade or purchase, but if someone wants this phone to use/test/etc. with, just PM me and we can plan on a quick dropoff in NY/NJ/CT area or I'll send it to your continental USA address with both batteries and no explicit or implied warranties, guaranties, liabilities or claims of operating performance, etc.
- ooofest

Galaxy S3 shuts down during boot

My Galaxy S3 keeps shutting off during boot. I encountered this problem while running Cmod 11. Was using poweramp playing music off my 64gb exFat microsd card, and suddenly Poweramp encounters "Error too many files" and promptly shuts the phone down. (Poweramp has been giving me strange problems before this, like that error just mentioned, and scanning for changes when there are none, but this is the first time the error caused the phone to shut down).
After rebooting it, The S3 gets to the boot screen and upon opening an app, promptly shuts down again. Further attempts result in the phone shutting off during the boot animation, and finally now the phone simply shuts down right before the boot animation. (note: it doesn't reboot. It turns itself off).
I thought it might be a problem with Cmod, so I wiped everything and using CWM, installed slimkat. Same problem. so I went and installed stock android using Odin, and now I'm back to stock. STILL same problem.
When I have the phone plugged into a computer, it seems to get further than the boot animation before shutting down (sometimes it gets to the lockscreen before shutting down again).
Any idea what's causing this problem? I have no problems with erratic shutdowns during recovery and download mode.
How old is your battery? Might be time to replace it.
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
cheezyphil said:
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
Click to expand...
Click to collapse
They're not as heavy to load.
Was any modification done to your phone (software) about when that started happening?
The s3's been on and off custom roms for a year now
cheezyphil said:
The s3's been on and off custom roms for a year now
Click to expand...
Click to collapse
I mean before it started happening. Or were you on the same ROM/version of that ROM for a while when it happened.
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
cheezyphil said:
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
Click to expand...
Click to collapse
Well if you can get in recovery, I would suggest doing a clean flash. But chances are that it's your battery giving out.
If you want to test, borrow a battery from another S3. I know with T-Mobile you can go to a store and they usually have a device on hand that you can borrow one from to test it out before spending money on it. I imagine you can do this at AT&T stores as well.
had the same problem with my atnt galaxy s3
i have the same problem,,i am using cm12 ryt now,,i tried to put every single rom and same thing happens,,i also brought it back to its stock firmware,,and still the problem occurs... did u find any solution for it,already?
:crying:

Categories

Resources