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.

CM 4.2.11.1 Camera and Home Screen issues

Firstly I'd like to thank PSYCHO13OI on the #cyanogenmod IRC channel for spending quite a bit of his time helping me out. I thought I might just throw my problem out there.
I received my new HTC Magic a few days ago, but spent quite a few days prior researching different ROMs.
I've got a 32A that came from 3 Australia.
Firstly, a summary of what I originally did.
After receiving my phone and playing around with the original ROM;
1) I fastbooted into: recovery-RA-sapphire-v1.5.2H.img.
2) I wiped data, and wiped a non-existant ext partition.
3) I partitioned the SD card using 32MB swap-size and a 256MB ext partition. Further I used ext2 -> ext3.
4) Loaded and flashed the following in order:
- DRC83_base_defanged
- update-cm-4.2.11.1-signed
5) Rebooted.
After 30 minutes of the original boot splash screen, I took the battery out (I couldn't, and still can't, figure out how to hard power off) and re-fastbooted into the recovery image.
6) I reperformed steps 1-4, this time actually flashing the kernel port: bc-4.2.11.1-ebi1-signed. I also repartitioned the SD card using a swap size of 256MB and ext partition of 1024MB and went from ext2 -> ext3 -> ext4.
7) Rebooted again.
8) When I get to the "Touch the android to begin." screen, I got this error message:
Sorry!
The process com.android.
phone has stopped unexpectedly. Please try again.
My only option is to force close which still allows me to touch the android and proceed as normal. Otherwise, everything seemed fine and dandy.
A few days later I decided to try using the Camera and Camcorder apps. This caused a reboot. This did not happen on the original ROM.
After the reboot I noticed that the home screen hung after trying to swipe my home screen. This eventually lead to the error message (after 10 seconds or so):
Sorry!
Activity Home(in process
android.process.acore) is not
responding.
I was prompted with the option to either force close or wait. Choosing either will restore complete functionality in 20-30 seconds.
Now this happens after every reboot (and I'm uncertain whether or not it is related to the Camera issue).
Trying to fix both issues, I repeated the flashing process, this time wiping the dalvik-cache as well.
Still no go. I've made the logcats of the first boot after reflashing CM 4.2.11.1 as well as a reboot. I have also linked my last_kmsg after rebooting due to the Camera app crash.
1st Boot: http://pastebin.com/m356cf97e
Reboot: http://pastebin.com/m69a15127
last_kmsg: http://pastebin.com/m76c42ee6
This camera issue is touched on here: http://code.google.com/p/cyanogenmod/issues/detail?id=792
As for the Camera issue, similar to the OP in the above thread, I only have issues when on battery power. However, I do not have any issues in other apps that utilize the camera such as barcode readers.
Things I have not tried:
- Another CM version.
- Wiping battery information or anything else other than data/ext partition/dalvik-cache.
- Reflashing an original ROM (which I did not backup - my friend's Magic is coming in the next week or so, so I'll grab his image).
Hopefully I've documented everything important (and perhaps trivial). I'm open to any suggestions.
EDIT: Some things I forgot to mention.
- 8GB Class 4 SD card
- Added details to my original post about partition sizes/types.

It seems I was wrong about rebooting only in the default Camera and Camcorder apps as I just recently experienced a reboot on the Barcode Scanner app.

Perhaps try an older version of cm. I had more stability on some of the older releases

What would be one of the more stable versions?

i always find CM has better themes and mods "BUT" the rom is laggy. in fact, amon's rom is fast and clean but not much of any theming. wasted.

scyzerd said:
What would be one of the more stable versions?
Click to expand...
Click to collapse
i'm back to 4.2.9.1 atm because it's a little less buggy. something like that or 4.2.8.1 or 7.1 maybe? go for the .1 versions because they will contain bug fixes for any known issues in the first release at that number...

I have that problem too... but I don't get it as often now. maybe once in a blue moon.....
there is two things I notice that when the reboot happens in the camera mode.
1) there are too much tasks running (you can notice it because the phone runs a little laggy, or if you check Taskskiller and the memory running low)
2) the audible selection is turn on
so now I watch taskskiller before I used the camera and reboot deson't happen that often, specially with the audible selection turn off.
let me know if you guy discover some other fix....

I wonder why in the world did you make such a big swap partition, since you have a 32A model you don't need any swap to run the CM ROM. To be honest CM works flawlesly without the SWAP partition on my phone which is also 32A. I have no problems with the homescreen nor the camera. Please try to repartition the SD card so it doesn't use the SWAP partition, you can also ditch the ext partition as the 32A model has more than enough space for applications installation (about 295MB space). Wipe and reinstall from scratch. Enjoy a working CM 4.2.11.1 build, you can even try 4.2.12.2
EDIT: ehhh, and if you encounter an alarm clock bug where the screen doesn't turn on when the alarm goes off, replace the existing alarm application (AlarmClock.apk) with the one provided in release 4.2.9. You lose some functions in the alarm clock but it works

Same problem different ROM
I'm having the same problem on a Rogers Magic 32A using AmonRa's Donut ROM.
The phone reboots after the 1st or 2nd restart of the camera. Plugged in to a charger, I can restart the camera at least 10 times. This isn't surprising since I did a wipe and reinstall the ROM and the problem still occurred with no other apps installed. Very strange.

I have the same problem...No not so much after I start using an other cam app, however the phone still reboots itself.

[SOLVED] LGO3D randomly shuts off.

My newly bought shiny LGO3D phone has a habbit of randomly shutting itself down no matter what ROM / Firmware i have on it.
I've tried stock, king ROM, and a few others. all randomly shutdown. i wouldnt mind if it had rebooted by itself at least it would come back on but it just goes off!
i reach into my pocket -- lo and behold the phone is off!
I've read lots of Optimus2x threads about a similar issue ... some blame the android system and some blame the hardware.
i wonder why there isnt a log in the android system describing an error or whatever?
can anyone help?

maybe your battery is a bit loose?
go stick some strips of paper at the bottom edge of the battery to make sure its nudged tight.
not sure, maybe a possible solution

i think i may have solved this issue...
what i did was this:
install CWM and reboot into the CWM menu.
i deleted everything. cache, delve cache, battery stats, everything thats deletable i did it.
i am currently using king_rom (which was doing the same problem for me to start with) and i can say the phone has been running ok for about 2 days now.
keeping fingers crossed.

usually cache + dalvic + battery states are deleted on every rom flash
if it appears again pull out your sdcard
fixed all reboot issues for me... wonderful to have a phone able to play 3d + record 3d/1080p and cant use a sdcard
hoping the 2.3 update will fix it

Blezz said:
usually cache + dalvic + battery states are deleted on every rom flash
if it appears again pull out your sdcard
fixed all reboot issues for me... wonderful to have a phone able to play 3d + record 3d/1080p and cant use a sdcard
hoping the 2.3 update will fix it
Click to expand...
Click to collapse
i never sacrificed the sdcard though its in there and its working fine.

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] Reverted to WEIRD default settings after random reboot

So hey folks,
This is the most strange issue i've experienced with my OPO so far.. Already had many random reboots since i manually flashed 38R, but this night Bacon screwed things up.
I woke up, seeing my OPO in a boot loop, it was super hot aswell and has drained the whole battery. So i connected my charger, did a reboot.
'Android is upgrading. Optimizing apps.' - OK so far, but only a total of 106 apps (With my last runtime change to ART, it showed 188 apps..). W/e.
Now it comes. Phone boots up - language defaulted. Whole settings reverted to stock. Apps are still there, but data is lost. :crying: Media on phone is untouched.
Suddenly i see these super strange buttons - they are NOT in their usual CM11S-Design!! And i did not change any visual stuff. [Attached Screenshot of notification screen]
Top right button to switch to quick actions does not work anymore, no reaction.
Home button completely not working aswell.
Also if i shut down and charge, the charging animation is completely different and colored instead oft OPO's normal one.
Restart menu back one low-level functionality aswell..only restart and shutdown possible [Attached Screen]
It's like my phone reverted itself to half generic android.
Guys, what the Heck happened?!
I mean, i will prolly just hard reset and reflash my phone later this day, but really.. WTH is this?? Any similar experiences so far? Or any Problem solutions?
Thanks for your time and replies..
Wasnt able to post in OPO Forums so far (server error >.>) but will update this thread if i get more info.
Attached screen shows that Rom status seems normal..