I just made a system change, and when I rebooted my phone, it went to the boot animation, but looped it over and over again. I thought, "oh dammmm, I forgot to make a nandroid!" I began preparing for the worst. I decided to get up and go to the kitchen to get coffee. I came back about 4 minutes later, and it was still doing the boot animation. I picked up the phone take take the back cover off, and then the lockscreen came on. Wooohoo!! My lucky day. Time to buy a lottery ticket!
Moral of the story: Maybe it's not stuck...maybe just give it 5 minutes.
Ever happen to anyone else?
P.S. I made the assumption that since it took so long with the bootup, that the sytem rejected my change and was taking so long to reset it. However, the font change took. All is good in g2x-land today.
Mine takes a long time to boot the first time after I clear the Dalvik cache. Its normal and the more apps you have installed the longer it will take to rebuild the Dalvik cache. Check out this article:
http://www.shahz.net/android/what-is-dalvik-cache.html
I have a feeling that a lot of "boot loops" that are posted about on here are not boot loops at all, but its just the phone rebuilding the Dalvik cache after a wipe.
This was actually several boots after my nightly install. I had probably rebooted 4-5 times since the initial bootup because I flashed a gps fix, changed resolution, etc.
I was changing the clockopia font. I have experienced bootloops (or what I thought were bootloops) previously from doing this, and I would pull the battery and try again. But I see that I need to be more patient, heh.
Related
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Are you doing Apps to SD? It could be your card.
Did you move any caches?
Do you have any nandroid backups? (just fastboot flash if so)
Did you recently try to update to anything and fail?
Try to use the update.zip again. If that doesn't work then start over from scrap.
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Wipe worked for me. It was sticking on the Android flash screen, but worked after the wipe.
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
In answer to binary: yeah I do apps on SD but I've been doing that since ADP1.1, so I doubt the card is the problem. Didn't move any caches. Yeah I have a nandroid backup, and all the updates I did went smoothly. I had the whole system working for about 2 days until this happened (probably, because this was the first time I rebooted since installing Contact Owner, though I can't really remember that 100%)
bsander said:
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
Click to expand...
Click to collapse
Contact Owner caused my phone to go into a reboot loop, but that was on the 5.02H build. I haven't had the guts to try it on JF1.5 or 1.5Hr3. If you look through the market comments for Contact Owner you'll see quite a few complaints of the same issue.
Hi there,
And sorry for reviving this old thread. I am the developer of Contact Owner an I kinda need your help in debugging this issue. I got a small number of messages from users of custom builds a while ago (about a month or two) but thought it was an issue with those builds.
Now it came back to bite me in the ass, as it seems the HTC builds in various countries (Canada, Sweden, South Africa) have the same issue: the phone goes into a reboot loop. I've tried (and failed) to install a custom build on my dev phone (almost bricked it) so I'm going to ask nicely if someone is willing to debug the issue for me. Please, please, please!
All that's needed is to install and run Contact Owner and if the device goes into a reboot loop, simply attach it to USB, run 'adb logcat' and then post the output. To recover from the reboot loop, simply start in 'safe mode' (hold Menu down while booting) and then uninstall Contact Owner.
I suspect the problem lies in SQLite, because I've seen similar complaints from Klaxon users and that app also sets the alarm message (which then ends up in a SQLite db, I guess). The Alarm Clock app that comes with Android also does that but I imagine it's because the message set by Alarm Clock is always short and has no newlines. I also don't think the issue is in Dalvik code, because the device should not crash if managed code causes an error.
TIA,
Paranoid Android.
I have had a problem occur a couple of times today that has never happened before. I have an extended battery installed(3500mAh). After 2 hours of not using the phone this morning after I pulled it from the charger I noticed the battery was down to 86% when it should have been still at 95% or higher. About an hour after that I went to make a call and the phone would not unlock. In fact it would not respond to any gesture or button push. I had to pull the battery to get it to boot up again. That freezing up has happened twice today. Once with the extended battery and once with the stock battery. Should I wipe the data and start all over again? Or is there another solution?
Have you installed any new programs recently?
No nothing for a couple of weeks now.
Still having a lot of freezes. Should I go to the security settings and tell it to do a factory reset and then start over again with rooting and customizing?
just out of curiosity did you reinstall the location services?
No. The only things I added back in after the last flash were the ringtone trimmer, sound recorder, and the sprint tv.
one thing that I noticed when I had my phone hooked up to ddms looking at the debug log I had a RSS reader app that was add supported and every 30 seconds it would search for and dowload a new add. once I got rid of that app it seemed to help.
another thing that really helped was I downloaded an app called "overclock" it let me set my CPU to 528 when the screen was active really helping with the speed and how fluid the scroll in menu's is, but it also lets you set it to like 128 when the screen is off. seems to really help with battery life as well.
What is throwing me for a loop is that the phone sleeps like it is supposed and I have verified this with spare parts show I am not sure why all of a sudden the battery is draining much faster than before. As far as the lockups, they are just temporary freezes, it locks and I have to remove the battery to get it to reboot.
Well I wiped the data then flashed to the newest sprint rom(1.56) and then rooted again. I then wiped data again and then flashed to fresh 1.1 and installed my apps and setup my home screens. So far no problems and it seems to run a lot faster and smoother.
Quick off-topic question:
When you say "wipe your data" does that mean you rm the /data directory? Or what? Just curious
No. I used Wipe in the recovery screen.
i just did a upgrade on my hero too from fresh 1.0 to 1.1
when you select wipe data from recovery mode, besides wiping data with option 1, do you choose option 2 as well ? wipe dev something. i wasnt sure what the 2nd wipe option is for, so i did the first option only and it only took 2 sec to complete that step. my phone is up and running with fresh 1.1 without any issues, so did i do it rite ? just outta curiosity
The second one is the cache. I think it gets rebuilt anyway on the first boot with fresh installed.
So I moved some crap from system app (Bloatware) to my sdcard and rebooted and now I'm stuck at system checking.
Am I sol?
Did you do a backup first?
Nope of course not ROFL.
Okay I'm good it booted. What a scare!
"System Checking" means "you're screwed" in Korean. The phone will either reboot itself back to stock or you'll have to do a hard reset to revive it. It's happened to me three times.
yeah happened to me yesterday and ended up with a factory reset phone.
i wish someone would shed some light on this and the conditions by which it happens. This phone is full of mysteries from random reboots to factory resets.
I just wiped and installed EagleBlood, hoping it will do better (at least until CM7 is in good working order).
I thinks it's a corruption issue. Two times I was playing with settings (Bluetooth profiles, changing icons) and the phone started acting weird and I got "System Checking..." when I restarted it. The good news is that I can now completely load my apps and configurations in less than an hour.
happened to me yesterday, but I didn't let to finishing "checking". I pull the battery out and restarted the system. No factory reset or anything. the system booted nicely the second time. so next time you might want to do the same
Happened to me last week, and I wound up having to do a reset.
ikithme said:
So I moved some crap from system app (Bloatware) to my sdcard and rebooted and now I'm stuck at system checking.
Am I sol?
Click to expand...
Click to collapse
Glad to hear t booted.
What apps did you move?
this happened to me yesterday. not rooted. my phone did a random reboot earlier in the day and i noticed one of my alarms didnt go off so i powered down, turned back on and it gave me the system checking message. after like 3 mins it booted up fine.
uploder said:
this happened to me yesterday. not rooted. my phone did a random reboot earlier in the day and i noticed one of my alarms didnt go off so i powered down, turned back on and it gave me the system checking message. after like 3 mins it booted up fine.
Click to expand...
Click to collapse
I haven't seen this not to say it hasn't happened without me knowing but my guess is if the phone reboots or crashes and then at startup it notices a filesystem error or some corruption is when it throws that up. If it can fix it, it does (people who reboot fine) and when it can't you're hosed.
Think of it like if you have a desktop and you pull the cord. It will try to recover but depending on the state it was in it might not be able to.
ikithme said:
So I moved some crap from system app (Bloatware) to my sdcard and rebooted and now I'm stuck at system checking.
Am I sol?
Click to expand...
Click to collapse
my phone only did that after i did super one click and i figured it just verified new files or something. im still up and running great. i have 5 backups. can never be too careful
I notice mine does system checking if I forget to mount the /system filesystem back to read only before a reboot!
Happened to me last night, except i was not so lucky. the phone kept rebooting and never get to pass the LG start up screen. Tried the hard key reset and it showed a message of "S/W Upgrade, Please Wait"
Phone t-mobile, they're gonna send me a replacement phone, less the back cover. As soon as the new phone was on its way, I tried to hard key flash again and this time it worked.
But, I am still gonna return this POS and hope the new one can perform better.
Had this happen this morning. I had used the Quick Boot app to reboot my phone, and after it reset I had "system checking" for a few minutes, followed by an infinite bootloop!
Fortunately I had installed ClockworkMod Recovery yesterday and made a nandroid backup, so after restoring that I was back in business.
I will no longer use Quick Boot though. It seems to shutdown the phone unsafely.
Sent from my LG-P999 using XDA App
I've been searching this form for an hour or two now and still haven't found my issue, so here goes.
Just got an HTC Inspire 4G off of ebay and it arrived today.
The seller had mentioned that the phone was freezing / rebooting, but I figured.. that's because he's not running cm7, right?
Charged and booted up the phone and it turns out that the problem was a little worse than I first expected. I only experienced occasional freezing, and it only rebooted once, but there is a worse problem.
The phone loaded up fine, looked good, but tapping around on the home screen I got messages alerting me that system apps (htc sense, launcher, and even com.android.phone) had stopped responding or had shut down.
I hit the menu and go to settings. I scroll down the list and the entire list goes black. I hit home and it goes to a home screen, but with no launcher or icons. Basically, every few taps, the interface goes out. If you are on a menu it blacks out, if you are at home or press home after the menu blacks out you will get anywhere from pieces of icons / widgets to just a blank desktop. The live wallpaper even keeps going, but all of the interactive stuff quits. The disappearing menus didn't usually give app closed messages, they just went black. The home screen only gave app closed messages sometimes.
I thought this was a software problem, so I managed to root the phone and flash cm7. Everything booted good, but it still had the same problem of weird disappearing menus and home interfaces. I went ahead and flashed gapps and got the little intro thing about setting up my Inspire 4g that starts when you first boot your phone. I clicked through that but when it gets to connect wifi, the phone entirely freezes and I have to pull the battery.
I flashed inspiremod and nothing changed, tho that's for something else, so I'm not sure that's entirely relevant, but I was trying everything I could think of.
I'm definitely no expert on hardware, but it almost sounds like a ram problem, like it doesn't have enough to keep all of the interface going all the time and shuts it down or shuts parts of it down to work.. but I don't want to believe that. I'm really hoping that it's a software problem.
I got the phone at a good price and it came with an otterbox, so I won't be too disappointed if I can't get it fully functional, but it would still be a bummer.
Any help / advice / suggestions appreciated. Thanks, guys!
EDIT: I cleared the cache / dalvik cache before flashing / reflashing cm7, which I did once or twice
EDIT 2: Now if I leave it on the intro screen where it freezes it reboots after a minute or so. Gonna try flashing a different mod.. see if that helps.
That was a long post. But it was good, you gave a lot of info.
The cm7 zip that you downloaded, check the md5 checksum, make sureit matches whatever is in the op (first page) or wherever the md5 is, maybe where you downloaded it from. If it doesn't, download again.
Then,
from recovery,
Wipe data/factory reset.
Wipe dalvik
Format all partitions(except sd card)
Flash zip/rom.
Check if it works. If not, try using it without the sd card. If not, come back and report.
Sent from a dream.
Thanks for the reply and suggestions.
I check the md5, and it's good. I just did a factory reset and wiped cache and dalvik.. I'm unsure what you mean by format all partitions except sd card. I don't think I know how to do this with clockworkmod.
Started up without sd card and it still has the same problem. Looks great until I touch the screen, then everything disappears except the wallpaper.
Reboot in recovery and do it from there. You'll find format all partitions at the bottom... well, maybe. Cwm has an option to reboot in recovery, and I think if you press and hold the power button, select reboot and it will also ask you if you wantto boot into recovery. Cant remember if cm7 has it, it should.
After you wiped those, flash the rom. Stay in recovery and search for fix.permissions. Reboot.
Sent from a dream.
Just did that and re-flashed cm7, but the phone was still having the same problems.
I then repeated the process with a MIUI ICS rom and it seemingly worked for a little bit. I got a "Maps has stopped working" message, but I was able to slide back and forth through the home screens, and the menu came up. After I tapped though the menu a bit it started being weird again, but with MIUI the weirdness is different. It looked like the screen was divided up into 20 something smaller screens tiled across the display with messed up looking bits of screen in them.. weird..
If you are wiping correctly then I am out of ideas. I would say try a GB rom, however that is a strange issue and just might be a hardware problem. Tough, Im not sure.
Sent from a dream.
I've tried cm7, which is 2.3, and I've tried a 4.0.4 MIUI build and one other sense rom that didn't work well at all.
I'm wiping and flashing the same as I did on my LG p509, which works beautifully with cm7.
If it is hardware, hopefully it's something simple like the battery, and not bad RAM or anything serious..
Maybe if I keep at it I'll get it.
Thanks for all the suggestions!
Np. Keep us updated.
Sent from a dream.
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
awkwardcheesecake said:
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
Click to expand...
Click to collapse
Have you tried changing out the sd card? Having a bad sd card can cause all inds of odd issues
I booted it without an sd card before and couldn't tell the difference, but it had a lot more issues than just freezing then.
I haven't tried it since those other issues have stopped. I'll try that when I get home from work.
IDK Which is causing this and am trying to figure out how I can find the culprit, but my Edge has suddenly begun locking up and completely freezing where if left alone like that it hot reboots, it had to of been a recent app I installed in the past 12 hours cause wasn't it doing it last night.
How can I figure this out to see what the last processed app was before the lock up and battery pull.
Seriously I've pulled my battery at least 6 times today and it's driving me insane. Went and uninstalled a few recently installed app's but still am suffering.
Bout ready to break something if something doesn't change. LoL! I can't even be up from a fresh reboot for a couple minutes without it locking up.
Wished I knew about this awful lag beforehand, would've waited for the Note Edge 2. I don't get how a Note 3 can out perform a Note 4 Edge.
Not really an edge problem. Specific to your piece.
If you've already uninstalled the recently installed apps, then next step would be clearing cache from recovery.
If that doesn't work, then looks like it will have to be a factory reset. Do backup first.
If rooted with a custom recovery, wipe cache and dalvik and see.
arbit12 said:
Not really an edge problem. Specific to your piece.
If you've already uninstalled the recently installed apps, then next step would be clearing cache from recovery.
If that doesn't work, then looks like it will have to be a factory reset. Do backup first.
If rooted with a custom recovery, wipe cache and dalvik and see.
Click to expand...
Click to collapse
I may just do a cache cleaning then a dirty flash, see if that gets rid of the problem or if it still presists to remain present.
Oddly enough if started acting up when I uninstalled SetCPU, now I'm looking for a more up-to-date CPU Tweaker/Tuner.
May also delete the Android folder on my external sd card, since I've been cleaning up and cutting back on a lot of app's, uninstalling a few everyday, installed a bunch from a backup, then been weeding them out.
Recovery > Wiping Dalvik Cache, System and Cache then dirty flashing the rom all over again seemed to work and allow me to keep all my app's and stuff.
It turns out I think it was the Xposed Module Power Nap. Uninstalled it and no more lockups.