Reboot loop on ADP1.5H r3 - G1 Android Development

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.

Related

What...? System Checking?

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

Display / menus freezing and / or disappearing, system apps force closing

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.

Help needed; random black screens

For the past few days, my phone has been acting up pretty badly. On the rare occasions that it finishes booting (usually gets to the CM boot animation and stays there), it will then only work for a short time before either I press the lock button to wake the device, but the screen stays black, or occasionally the screen will go black while I'm actually using the phone. The only way I have managed to get the phone working again is pulling the battery and restarting, and hoping it will boot this time.
It seems to do the black screen thing particularly frequently when text messages are received, but it's not ONLY when they are received.
It started when I flashed the latest kernel posted in the Evervolv thread [here: http://forum.xda-developers.com/showpost.php?p=41359720&postcount=183]. My current rom is CM10 build #6. Once this started happening, I restored a nandroid backup I had made a few weeks ago. At first I only restored the "boot" partition, and when that didn't help I restored the "system" and "boot" partitions. That still didn't work, so I flashed the Garuda kernel v5. That also did no good.
Is my only option re-flashing my ROM? I'm a little reluctant because that would mean losing all my apps etc. and having to restore them. I guess I could try a full nandroid restore first.
But before I go too drastic and potentially lose data, does anyone have any other suggestions as to what may be the cause?
I also have Mounts2SD installed (from Play Store) in case that's relevant.
EDIT: Could I flash the ROM without wiping and thus keep my installed apps and data?
A logcat would help.. In the meantime, install the" app2zip" app from the play store.. It allows you to make flashable zips of installed apps.. Also, try to find "zipme" by jrummy.. That app lets you make a flashables of apps, app data, system data, Bluetooth pairing info, Wi-Fi info, n much more.. And just to have covered all the bases, try reflashing the full rom...
ғг๏๓ ҭђє ғเรђ™
I'm cautious about speaking too soon, but last night I fixed permissions in recovery and it hasn't black screened or rebooted since so I'm hopeful it may be Ok now. Thanks so much for the suggestions though, I'll be sure to look into those options in case something else goes wrong or else if this problem isn't actually fixed.
Edit: oh and I had tried to get a logcat but once it black screened it wouldn't respond to adb

Random reboots mostly after unlocking, am I the only one getting them?

Sometimes I unlock my phone and the screen remains black, then the phone reboots but weirdly it doesn't ask for the SIM pin number. Other times I notice the phone reboots by itself and I notice it because obviously the screen lights up during the boot animation. This happens very rarely, so far it has happened about 3 to 5 times in a couple of months but it's still mega annoying when it happens.
Does it happen only to me? Is there any way to troubleshoot this issue?
MarkMRL said:
Sometimes I unlock my phone and the screen remains black, then the phone reboots but weirdly it doesn't ask for the SIM pin number. Other times I notice the phone reboots by itself and I notice it because obviously the screen lights up during the boot animation. This happens very rarely, so far it has happened about 3 to 5 times in a couple of months but it's still mega annoying when it happens.
Does it happen only to me? Is there any way to troubleshoot this issue?
Click to expand...
Click to collapse
If you provide some logs then maybe someone can see what is happening....
Or even basic information, like the configuration and setup of your device.
Right, forgot my configuration. I have an unbranded Z3 on latest Lollipop (but I recall I had a reboot also on Kitkat), no root, no weird apps like task killers or antivirus or anything like that. Sometimes it just does a reboot by itself, but doesn't ask for pin number so it's not a full reboot.
How do I provide logs again?
Info
MarkMRL said:
Right, forgot my configuration. I have an unbranded Z3 on latest Lollipop (but I recall I had a reboot also on Kitkat), no root, no weird apps like task killers or antivirus or anything like that. Sometimes it just does a reboot by itself, but doesn't ask for pin number so it's not a full reboot.
How do I provide logs again?
Click to expand...
Click to collapse
Factory Reset can solve ur problem /based on personal experience
I did that already less than two months ago and I refuse to believe I have to factory reset this thing every month to get stable operation. Also I'm not even rooted and I haven't messed with the system itself so why would I need to factory reset? Factory reset implies that there is something that has changed and needs to be re-set, and I haven't changed anything special that would require such a drastic solution. Not having done anything special, the issue would come back sooner or later if I don't spot the real cause.
Anyway, in diagnostics I have 21 application incidents for systemUI... Could it be caused by a bugged theme? Does this happen to anyone else?
Today I had two and I had another one last week. A off these were weird half reboots like I described above. I only noticed one because I was at my desk and the phone lighted up for the boot animation.
These reboots show up in diagnostics (phone info menu) as system events. Can you please check out if you have any system events and post here? I want to know if this is a widespread problem. Post here if you have any and also if you have a solution or way to troubleshoot.
Nobody at all? Really?

Why does my Google Pixel randomly reboot?

Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
marf3 said:
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
Click to expand...
Click to collapse
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
pradctgign said:
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
Click to expand...
Click to collapse
I noticed problems with my ear speaker as well. And i cant make phone calls. The phone doent respond anymore when i try to.
Same problem after android 8.0 update
If you have installed the latest Google phone/dialer app, that is likely the problem, was for me.
Find the app in settings and uninstall,it will roll back to a previous version and hopefully fix your issues.
Sent from my Pixel using Tapatalk
My pixel does the same thing, ever since I updated to 8.0, have you tried doing a factory reset? I haven't done it yet, I have been uninstalling apps for the last couple of days, when it is in safe mode it works good, but when it's not, it freezes and restarts. I'm going to try uninstalling the latest version on google dialer to see if it helps.
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
droid4lif3 said:
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
Click to expand...
Click to collapse
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
wrong place sry
Had this on my pixel xl. I was on the 8.1 beta.
factory reset, rolled back to 8.0
8.1 ota official
haven't had a reboot in over a week now
Murrzeak said:
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
Click to expand...
Click to collapse
Yea, the issue is back, has been for about 2 weeks. This phone is really starting to be a pain in the ass, I can't believe that it happens so often. Did you do a warranty fix?
That's a pity. Yes, I did. Got the device roughly two and a half weeks ago. Flashed 8.0 and then sideloaded 8.1 right away. Knock on wood, all good. But there's still a report every other day in Buganiser of a phone even on 8.1 doing this.
Got mine at release. November 16. Google won't replace it either. I have a one pixel brick
I have the same problem. However, it is not frequent enough on Android P beta. But as soon as I go back to the stable build, it starts to do the same thing. Did you guys have any luck resolving this or should I send it back to the vendor I bought it from. They won't replace the device in Pakistan but may be will fix it in some manner.

Categories

Resources