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.

rooted moto g lollipop system ui has stopped no stock launcher... PLEASE HELP!!

hi all,
i stupidly decided to root my moto g - i say 'stupidly' bc i clearly didn't have the knowledge to have that much power... it was working fine for several weeks & then it started having issues booting & charging if i accidentally let the battery get too low. that happened a couple times & i was able to get it working again by charging it in different ways (wall, computer) & letting it alone for a day or so. but then the other day i turned it on & i got the 'Unfortunately System UI has stopped working' & gave me the option to click 'I'm feeling lucky.' once pressed the phone would boot up (though it took much longer than usual) & when it finally did, i'd get various messages such as 'exchange services has stopped,' motorola notifications has stopped,' 'System UI has stopped' - basically everything has stopped & they just kept popping up & then the phone would freeze. before the phone would freeze, in between messages, i could still get into my apps & other parts of my phone, but it would always eventually freeze after a few minutes (or less). i tried various troubleshooting techniques (reboot in recovery, factory reset, etc) which eventually led to doing a hard factory reset. unfortunately, i believe at some point before all the problems started i must have deleted some system things i shouldn't have, including the stock launcher (i was using Buzz Launcher) so now it's returned to factory but missing some vital components.
here's the current state of my phone: it will boot up (though it takes much longer than usual) but as soon as it does i get the message 'unfortunately, system UI has stopped,' 'exchange services has stopped,' 'motorola notification has stopped,' & 'System UI has stopped' again. when i click on 'ok' for that last message, i get the flash of a weird red window & then just a black screen that shows the (correct) time, battery level & phone signal in the upper right corner but it's frozen. before it freezes completely, the only thing i can get into/click anyway is the status bar at the top but the window doesn't even drop down. so the phone is basically booted up but useless.
i've done tons of research & looked into using a toolkit or flashing android/moto stock but i'm using a Chromebook & nothing is compatible with it that i've found so far. & i'm not even sure how to get into the phone via a Chromebook, if it's possible.
PLEASE HELP!! i'm getting desperate. can't afford to buy a new phone right now & i really need this thing to work again.
SHORT STORY: Moto G, System UI has stopped, missing some vital stock stuff, phone boots up, no launcher, Chromebook, last system i was using was Lollipop
does anyone have any idea...? also, keep in mind i'm clearly not as knowledgeable about this stuff as most of you or i never would've gotten myself into this situation. so keep your responses as if responding to Android/Moto G for Dummies. ;-P Thanks!!

Flash a custom ROM via custom recovery

Check out CM11/12. I have the boost 3g version with Blisspop (CM12) and it works great.
Also, if you created a backup before you went root you might try restoring it instead of factory reset.

Make a wipe, or reflash the rom

Chromebook
thanks for the replies guys but my issue is trying to do any of the above from a CHROMEBOOK. in order to flash a ROM though, I need to install the Motorola android device driver & I've yet to find one that's compatible with Chromebook - I'm not sure there is one... anyone have any experience in flashing ROM or any other Moto G fixes from a CHROMEBOOK? thanks.

Can u still access your recovery?

[Q] Many problems with new s6

So I bought the S6, new, never been opened, sealed etc, let it charge the proceeded to turn it on. Then comes the welcome bit and startup, this is where it went tits up. Apparently everything stopped responding, google maps stopped responding, voice commands stopped responding, etc. Thought nothing of it, skipped through everything, got into home screen and then "Touchwiz has stopped responding". So naturally I though oh dear. Oh, it also started restarting on it's own randomly as well, I tried booting in safe mode, disabling things, that didn't work, sometimes it would even get in a bootloop, loop 3 times and then start.
I tried updating it, didn't work, tried flashing it with "G920FXXU3QOLD_G920FH3G3QOJ1_G920FXXU3QOJB_HOME", problems still persist. It's currently on 5.1.1, it wont update in settings, just starts downloading more than 1.2gb's of downloads then says "Software update has stopped responding".
Tried samsungs live chat, was awful, they didn't present any useful information.
I'm wondering if it's just 5.1.1 being awful, because when I boot to the system recovery menu thing where it has the blue screen with android logo, then has yellow exclamation mark, that doesn't reboot on it's own at all. Never reboots in download mode either. Phone is not rooted, knox hasn't been tripped or anything, so I'm left clueless. What do I do? Bought this phone, what, 4 days ago ish. Came here yesterday. My question is, if I flash it with idk, a 6.0.1 update in odin or something, will that fix the problems?

Hi,
It seems to me that you have a defective device, you can either try reflashing the stock firmware and then factory resetting, I believe that it really is a software issue, but as it's brand new (as you stated), you can return it to the store and get another one.
There are quite a few guides to flashing stock firmware back, hope you can do it .
All the best,
~Lord
Sent from my SM-G920I using Tapatalk

Bootloop, frequent crashes, unable to boot with stock ROM sometimes on OnePlus One

Hi,
My brother has a 64GB OnePlus One which has never had its bootloader unlocked, and therefore never has run any custom ROM outside of OnePlus' Cyanogen distribution.
After (and this is most likely a coincidence) it had been dropped, it started frequently freezing, then crashing. Sometimes, the phone would switch off and never attempt to start up again after these crashes.
Now, Android crashes within minutes of turning the phone on. It requires several power cycles for the phone to even start up again – it usually crashes at the Cyanogen logo or never reaches it, staying at the OnePlus logo indefinitely until it is switched off by holding the power button.
He would prefer if he did not lose any of his data stored on the Internal Storage, but I might be able to back it up before.
What I don't understand is that I can only find reports of these issues in custom ROMs, not the stock ROM.
The phone was running the latest stock ROM.
Is there a fix available?

I seem to have the same issues. Stock phone, fully updated with official ROMs.

Holy Crap, Something Scary Just Happened After Reboot!

I had flashed @foreverloco Marshmallow BrEaKdOwN ROM earlier and used TB to uninstall some bloat like Facebook, Google Music, Microsoft Office stuff then I restart. When it boots back up I get a "Unfortunately system UI has stopped" notice and choose the "OK" option to make it go away. It keeps popping up and then the screen starts to flash on and off on the lock screen. As I'm trying to hit the power button and try to go into recovery there's these text messages at the bottom end of the screen saying things like, "Yeah, like that'll work again" and "I haz control now" and "Virus detected". WTF? I manage to boot it into recovery now.
I have no clue why that happened. I haven't downloaded anything from any unofficial source since I flashed the ROM besides the flat bar module on xposed. I'm going to do another full wipe, internal storage included, and flash another ROM thru OTG.
Update: I went back to @rmarinella N5 Express. Everything looks good. No freaky messages. I'm going to configure everything back to the way I like it and report back to see how things are going.
Update #2: Things looking good. I configured everything I wanted after flash. Things look stable and normal, not getting any error messages. Now I'm going to install my TB apps and see if that all goes well.

The things that it says on the lockscreen are apart of the rom

[email protected] said:
The things that it says on the lockscreen are apart of the rom
Click to expand...
Click to collapse
Thank god for that. Damn thing had me getting paranoid like a mofo.