Database Info

Reboot loop on ADP1.5H r3

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.

to stop Verizon from forcing update

to stop Verizon from forcing update
Use Titanium to freeze com.smithmico
i lost root because vz forced the update so i reinstalled .5 oem then used revoluton to unlock boot in stall SU installed .9 radio seems to work well rebboted it pop saying .9 would start download in 26 secs i stoped it from installing
i remembered reading about smithmicro and OTA so i froze it so far n more pushed OTA ...
your mielage may vary

Or just delete it completely. Not needed and is in my top 10 list of things to remove via tb.

Could you tell me exactly how you reinstalled .5 after having .9 already on the phone?

http://www.multiupload.com/WES9PABEQF
rename it PG05IMG.zip copy to sd card reboot do power volume restart it should do it itself don't shutdown until it is completley finished.

I did that but it won't downgrade. It says I have the newest version installed so it won't flash the "older .5" version. Any suggestions?

Make you rename it pull battery two button restart and it will load .5 I had no issues
Sent from my ADR6400L using Tapatalk

davwman said:
Or just delete it completely. Not needed and is in my top 10 list of things to remove via tb.
Click to expand...
Click to collapse
Is that uninstall com.smithmicro.DM 1.0.0 ? Is this the right thing to uninstall for no OTA? Thanks
If so, I think I will uninstall this before I flash the new radio. What do ya think?

i don't see that file... on a side note, i updated the radio this morning and still no message to update so not sure if i'm in the clear or not

so what does com.smithmirco actually do? is it just an updater?

My phone seems to be stuck in the process. I can't locate a p50IMG on the SD card and before I can even open Titanium my phone starts to power down and tries to install the update, but fails. Any ideas?
---------- Post added at 01:51 AM ---------- Previous post was at 12:57 AM ----------
Finally think I figured it out for my situation. As soon as home screen loaded I opened up TasKiller, killed everything. Repeated that 4 times so that everything loading up with the phone was killed before it would reboot the phone. Went to app drawer and made a shortcut for Titanium right next to TasKiller. After this I went in and killed all apps again.
Now let's freeze some things via Titanium so it doesn't try to reboot to install an OTA. First I froze com.smithmicro, next I froze HTC DM. After these two I let the phone go while I messed around for a few minutes, after this I turned airplane back off. I checked TasKiller and noticed that an app MCC_OTA had opened, fearing this may be the cause I killed all apps again and went in to Titanium and froze this.
15 minutes later and I've had no issues with cell/data service. I can get into the market, update apps, receiving gmail/email, and Facebook working fine.

Pender1 said:
so what does com.smithmirco actually do? is it just an updater?
Click to expand...
Click to collapse
I am not trying to be an alarmist, but a description from Smithmicro's site sounds strangely similar to the description on the Carrier IQ site. I will let you be the judge.
"Device Management Suite™ (DM Suite) is a standards-based server solution for mobile device management, enabling mobile operators to remotely customize, provision, configure, and diagnose mobile device settings."
http://www.smithmicro.com/products/device-management-suite.aspx

Still running strong, no problems and no force OTA attempts.

Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
It got to the android man screen and got stuck there. Again pulled the battery and rebooted in to recover. Wipe Davlik cache and regular cache, rebooted and phone appears to be back to normal.
Rooted running Team Gingerbreaton ROM. This is the second time in the last few months that the forced OTA has tried to run itself.

CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
Click to expand...
Click to collapse
Happened to me this morning too. Good thing the phone sits next to my bed (use it as an alarm) and woke me up since I would have oversleep without it. Of course, I lost two hours of sleep because of it since I couldn't get it working in my half-sleep state and just stayed up because I didn't want to be late to work.
I need a real alarm clock.

CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
.
Click to expand...
Click to collapse
Happened to me as well. Up at 4:30 roughly with nothing working. Cleared cache as suggested and phone is now powered up but no longer showing 3g or 4g, simply 1x so something is still wrong. Have to get ready for work at this point and will have to do some more digging.

CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery ... Wipe Davlik cache and regular cache, rebooted and phone appears to be back to normal.
Click to expand...
Click to collapse
Thanks for that. I was losing my mind this morning. Woke up, grabbed phone, and it had the sad Android screen with the Exclamation triangle. Felt like Anakin at the end of Ep. III for a bit. Did a search for "Block update" and came to this thread. Now to flash a non-Verizon ROM so I don't have to go through that again.

Just got another OTA notification this morning, was able to delay it... WTF? I'm rooted running a custom ROM and it's still trying to push this updated.

Just an FYI, if you get the update. Revolutionary root no longer works.

I woke up to my phone stuck on the black screen with the little Android man also. I pulled the battery, powered up and quickly restarted into recovery. Then I factory reset from recovery and after that I re-flashed my shift ROM and all is good so far. *knocks on wood* Anyone think its the new radio I flashed that prompted this or did they push everyone??

zx12dak said:
I woke up to my phone stuck on the black screen with the little Android man also. I pulled the battery, powered up and quickly restarted into recovery. Then I factory reset from recovery and after that I re-flashed my shift ROM and all is good so far. *knocks on wood* Anyone think its the new radio I flashed that prompted this or did they push everyone??
Click to expand...
Click to collapse
I had the same issue -- I received the update even though I had not accepted or checked for it. Took my phone out of my bag at work and saw I was at the Android man and exclamation point screen.
I wiped cache and wiped Dalvik cache, and the update stopped. I did flash the new radios though for the .9 update and have been sitting fine on 4G for the last two hours.

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.

[Q] 5113 Locking up and Strange Behavior

My neighbor's 5113 is having some strange issues I hope I can get some insight on. I've worked with a lot of Samsung phones and am very familiar with flashing, Odin, etc but have not worked with a tablet before.
First, it has 4.2.2 on it. I tried the stock software update function and it says it's up to date. Is that true? Is 4.2.2 the latest official for this device?
Second, It's having lock up issues (see below) so I thought I would "Clear Cache" in stock recovery. It starts going through the process and then errors out. It just flashes ERROR and then goes back to the stock recovery screen. I've never seen that before. Any ideas?
Lastly and most importantly, it locks up regularly. It will lock up with the screen on (although it seems to take longer to lock up with the screen on with some motion.) When the screen goes off it will lock up quickly, normally within 5 minutes and it even locks up when charging up. The charging animation stops and you have to hold the power button for 10 seconds to get it to come back to life. It's very strange. It even seems to freeze when it's off. It won't just start by pushing the power button for a couple of seconds, you have to hold it for 10 seconds until the charging animation pops up and then push the power button for a couple of seconds.
I haven't reset to factory specs because she has a ton of info on the thing and I'm afraid if it errors out clearing cache, what might it do if I try a factory reset?
Thoughts?
Thanks for the help.
UPDATE: I did a factory reset via stock recovery and it did delete all the data. It still will not let me clear cache though. It still locks up whenever the screen goes dark. It will lock up in just a couple of minutes.
Very frustrating.

I would try flashing the stock firmware and see if that clears up the locking problem, after a day or so I would flash CM11 with gapps and take it from there.
After running stock rooted before flashing CM11 do a nandroid b/u just in case it acts up. CM11 IS SUPER stable, have run it on my P5113 for several years starting with cm10.
CM12 is still buggy don't trust it.
Pp.

PanchoPlanet said:
I would try flashing the stock firmware and see if that clears up the locking problem,
Click to expand...
Click to collapse
Thank you very much PanchoPlanet. I factory reset and reloaded stock firmware several times but it would still lock up as soon as it went to sleep. And I still could not wipe cache. Very strange. I went so far as to not set up any accounts and make sure it didn't download any software updates to make sure it wasn't some update that was causing issues.
It would still lock up even when it was off and just supposed to be charging the battery! So I really think it's memory is trashed.
But I would be more than open to listen to any other ideas.
Thanks.

Maybe there could be other issues that you are not aware of, like the tab having been dropped or liquid damage or even voodoo, who knows.
Sometimes people don't disclose all the details.
Pp.

PanchoPlanet said:
Maybe there could be other issues that you are not aware of, like the tab having been dropped or liquid damage or even voodoo, who knows.
Sometimes people don't disclose all the details.
Pp.
Click to expand...
Click to collapse
It looks to be in perfect shape. But in any event, if something like that happened then it's toast anyway.

Yeah, especially the voodoo. Lol.
Pp.

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.