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.

HELP: Phone locks up and dies at random

I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!

Sounds like a warranty replavement to me.
Caution swyping! Read at your own risk.

TheSopranos16 said:
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Click to expand...
Click to collapse
What kernel are you running? And are you OC/UV?
If so, try a different kernel (like speedmod k13e) that doesn't have OC/UV option. Black screen is usually a UV setting problem.
If it's not the case, warranty?
EDIT: Have you flashed over different ROM with lagfix/ OC/UV enabled?

Right now I'm running lastest Cog 4 with the included kernel (which doesn't support UV). I was OC but once I had this issue I reset the clocks to stock but then it happened again. Before I installed Cog 4 I flashed stock and master cleared...

1. Did u restore any data using TiBu when u flashed the ROM? Did u happen to restore any system data?
2. Did u put on any kind of under volting?
Flash any ROM, say Firefly, and use it for a day or two without restoring any of ur apps, and see if the issue is coming up again.
If yes, try changing kernel, say to onix, and keep on for a day or two see if the issue is recurring.
Just to be sure, can u do this:
1. Revert to stock
2. Format internal SD (similar to master clear to clear out SD card; I never did a master clear so far, only this)
3. Copy the ROM u want to use to SD
4. Flash Firefly 3.0 (this formats all system partitions, so no need to master clear)
Firefly has hardcore's kernel by default, and this kernel does not apply lagfix by default. Same with onix kernel too, and this is the reason I am recommending this combination of ROM and kernels. I use onix cos I have some wifi issues on hardcore's kernel.
5. Do NOT restore of ur data or apps

I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...

TheSopranos16 said:
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
Click to expand...
Click to collapse
I would NOT recommend ANY system data, except for contacts storage. This is the only one system data I personally found not to cause any issues.
Its easier to connect BT and wifi again, than go through the pain restoring this data sometimes creates. I faced issues with my phone not being paired to my car when I tried to restore bluetooth settings. It shows my car, but doesn't pair. I had to restart phone, delete the connection, and then reconnect. I found it easier to add back, than restore and go through all this trouble.
This time, pls try to refrain from restoring any of ur data from TiBu and a day's run for the ROM and see how it goes. If it goes well, u can restore data. But, before u restore data, I would recommend taking a nandroid backup just in case restoring apps starts creating issues again. This could save some time by getting u back to current state with no apps, instead of flashing all over again.

Before doing any of those things, I would check out your IMEI number and compare it to the one in this link,
http://www.captivateforums.com/sams...random-shutdown-issues-on-att-captivate-1272/
I dont pay for any warranty through AT&T, but I brought my phone in to a device replacement center and they replaced mine with a brand new phone!
Its worth a shot if you ask me.

My phone is completely freaking out software-wise :/

So, about 2 or 3 days ago I downgraded back to Froyo from the latest Gingerbread leak (too many bugs.) I did so with GTG's Ulimate unbrick, and then I flashed the pre-rooted/ pre-CWM stock ROM to it. I updated to the latest UCKH1 to be up to date, and then I restored a backup I made in ROM Manager a few weeks back. After that, I restored all my apps with Titanium backup. Now on to the issues. First time around my phone literally crapped out software-wise. It was literally force closing everything, texting wouldn't work, the Advanced power menu was gone except for Power Off. That only started after a full day of use with no issues whatsoever. It was completely random. Well late last night, I factory reset and put my apps back on again. Well I woke up this morning to find that my phone's suddenly being dumb again. Except this time the only issues that I know of are, the Advanced power menu's gone except for Power Off, and the home button will not function AT ALL. If anyone has any idea what's going on, or how I can resolve this, please lend a hand.

Kevinr678 said:
So, about 2 or 3 days ago I downgraded back to Froyo from the latest Gingerbread leak (too many bugs.) I did so with GTG's Ulimate unbrick, and then I flashed the pre-rooted/ pre-CWM stock ROM to it. I updated to the latest UCKH1 to be up to date, and then I restored a backup I made in ROM Manager a few weeks back. After that, I restored all my apps with Titanium backup. Now on to the issues. First time around my phone literally crapped out software-wise. It was literally force closing everything, texting wouldn't work, the Advanced power menu was gone except for Power Off. That only started after a full day of use with no issues whatsoever. It was completely random. Well late last night, I factory reset and put my apps back on again. Well I woke up this morning to find that my phone's suddenly being dumb again. Except this time the only issues that I know of are, the Advanced power menu's gone except for Power Off, and the home button will not function AT ALL. If anyone has any idea what's going on, or how I can resolve this, please lend a hand.
Click to expand...
Click to collapse
It sound like every time you encountered a problem it was after restoring your app with TiBu. Are you just restoring apps or apps&data? See how your phone runs without restoring apps. Try restoring apps(without data) and see what happens, or just manually download apps again. Could be a problem with data from the apps.

bigfau said:
It sound like every time you encountered a problem it was after restoring your app with TiBu. Are you just restoring apps or apps&data? See how your phone runs without restoring apps. Try restoring apps(without data) and see what happens, or just manually download apps again. Could be a problem with data from the apps.
Click to expand...
Click to collapse
I was wondering the same. I have indeed been restoring apps with data. Didn't want to lose my Cut the Rope progress But, they may end up being my problem. I've always gotten away without issues, so I guess it's about time for one to happen, haha. I'll try it out after work today and post how it goes.

Kevinr678 said:
I was wondering the same. I have indeed been restoring apps with data. Didn't want to lose my Cut the Rope progress But, they may end up being my problem. I've always gotten away without issues, so I guess it's about time for one to happen, haha. I'll try it out after work today and post how it goes.
Click to expand...
Click to collapse
Most likely the problem lies with the backups being from a GB rom and now you are trying to put them an a Froyo rom. Probably saves it differently or something.

They tell you "Not" to use the backups from Titanium as they can cause issues, I reinstalled back to Stock Froyo as well running the latest UCKH1, When you do the Update to UCKH1 my advice is to go to Settings: Privacy: and do a Factory reset to fix the clock problem The clock will appear screwed up and will correct itself even when it's on Automatic Mode. Otherwise all is fine downgrading from GB Rom. Install all normal apps as usual, Screw Titanium my advice is just save the .apk file for the app in a Folder on your External SD Card, that's my quick way of reinstalling all my apps back regardless of losing settings.

you can also use tibu to restore single apps with data, you can try the ones you want to save progress and see if it causes issues. just stay away from system apps

I've never ha a problem with TitBU, as long as I restored "missing apps & data" ONLY!

same here, regardless of android version or even restoring on a different device. the only time i have seen issues is when i accidentally hit restore all apps with data, including system apps. thats when i got the constant fc and crashing

bigfau said:
Most likely the problem lies with the backups being from a GB rom and now you are trying to put them an a Froyo rom. Probably saves it differently or something.
Click to expand...
Click to collapse
You know, now that I think about it I actually made a backup from UCKJ2. That's more than likely my problem. Funny how I'm looking for all these complicated things and it ends up being something easy. Haven't restored anything, so I'll wait a day or two and see if everything stays like it should, and then I'll restore only what's needed to ensure it stays that way. Sorry it took so long to respond, had work, haha. Thanks guys all the responses were much appreciated.

Kevinr678 said:
You know, now that I think about it I actually made a backup from UCKJ2. That's more than likely my problem. Funny how I'm looking for all these complicated things and it ends up being something easy. Haven't restored anything, so I'll wait a day or two and see if everything stays like it should, and then I'll restore only what's needed to ensure it stays that way. Sorry it took so long to respond, had work, haha. Thanks guys all the responses were much appreciated.
Click to expand...
Click to collapse
You should be alright as long as you don't restore data. I think. Lol
Sent from my SAMSUNG-SGH-I997 using Tapatalk

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.

New ROM w/o Reset

I have been running CleanROM Seven for sometime without any problem or issues. In the last few weeks it has been glitching something awful! The screen blinks whenever I try to load an app or really do anything at all. Sometimes it blinks between the old and the new screen (like when swiping from page to page I'll see the page I was on and the page I am going to back and forth very quickly). Other times I see vertical stripes that alternate from the screen and black bars.
Restarting the phone worked for a while and then it stopped working, so I reflashed the ROM and that worked for a week or so and now it's back. I really, really, really want to avoid any kind of reset that involves the removal of my contacts or anything of that nature (I always back up before a reset, and I always end up missing stuff like contacts that I had). Either a fix to this problem or a ROM that I can flash without having to reset would be great.

Pard68 said:
I have been running CleanROM Seven for sometime without any problem or issues. In the last few weeks it has been glitching something awful! The screen blinks whenever I try to load an app or really do anything at all. Sometimes it blinks between the old and the new screen (like when swiping from page to page I'll see the page I was on and the page I am going to back and forth very quickly). Other times I see vertical stripes that alternate from the screen and black bars.
Restarting the phone worked for a while and then it stopped working, so I reflashed the ROM and that worked for a week or so and now it's back. I really, really, really want to avoid any kind of reset that involves the removal of my contacts or anything of that nature (I always back up before a reset, and I always end up missing stuff like contacts that I had). Either a fix to this problem or a ROM that I can flash without having to reset would be great.
Click to expand...
Click to collapse
You can't really flash a new ROM without wiping because then you'd face a whole new set of issues.
If you're missing contacts, back them all up to Google through settings/accounts/Google/check contacts. That will help you avoid anything with contacts.
For apps, back them up with titanium backup, but only backup user apps and data. Do not backup system data or apps as this will cause issues as well.
My suggestion would be to do these things I've suggested, then nandroid backup, then wipe and flash bonestock. Its probably the stablest ROM around. Also the developer is really awesome and keeps up with most of the stuff.
Outside of that stuff, I can't really help you. Unfortunately there's not a safe way to flash without wiping.
Sent from my SCH-I535 using Tapatalk 4
If I've helped, please hit the thanks button

Just wipe all roms recommend it for a reason dont be lazy
Sent from my SGH-T889 using Tapatalk 4

Pard68 said:
I have been running CleanROM Seven for sometime without any problem or issues. In the last few weeks it has been glitching something awful! The screen blinks whenever I try to load an app or really do anything at all. Sometimes it blinks between the old and the new screen (like when swiping from page to page I'll see the page I was on and the page I am going to back and forth very quickly). Other times I see vertical stripes that alternate from the screen and black bars.
Restarting the phone worked for a while and then it stopped working, so I reflashed the ROM and that worked for a week or so and now it's back. I really, really, really want to avoid any kind of reset that involves the removal of my contacts or anything of that nature (I always back up before a reset, and I always end up missing stuff like contacts that I had). Either a fix to this problem or a ROM that I can flash without having to reset would be great.
Click to expand...
Click to collapse
the reason why we recommend that you wipe the device is that one rom might have features that won't work on another rom. there are other things that end up happening.