Database Info

[Q] Random Reboots Since 4.4.3

Anyone else?

Fully stock? Do a factory reset from stock recovery.. Should fix it. If you're on a custom rom, do a clean flash. (wiping everything except data)
- Sent from an IceCold Hammerhead!

Thx for the advice.
But was wondering if anyone else is getting them.
I'm trying a few things to fix it as I never had a reboot since I owned the phone in November last year, until 4.4.3
At the moment I'm trying an older radio, but it's hard to pin since my last try of using a 4.4.2 kernel kept me up for 35 hours before it happened again.

got an rma replacement.. still happening

meangreenie said:
got an rma replacement.. still happening
Click to expand...
Click to collapse
Did you restore a nandroid on it or anything?

rootSU said:
Did you restore a nandroid on it or anything?
Click to expand...
Click to collapse
no, is completely fresh
tried everything under the sun over the last month.. factory image installs, running safe mode, no apps installed, new Google account... ect ect
can't stop a soft reboot occurring every 2 or 3 days.. I use to have 'up times' of over a month on 4.4

meangreenie said:
no, is completely fresh
tried everything under the sun over the last month.. factory image installs, running safe mode, no apps installed, new Google account... ect ect
can't stop a soft reboot occurring every 2 or 3 days.. I use to have 'up times' of over a month on 4.4
Click to expand...
Click to collapse
Upgrade to 4.4.4 and see if it sorts out?? You get random reboots even when the phone is in safe mode?

vin4yak said:
Upgrade to 4.4.4 and see if it sorts out?? You get random reboots even when the phone is in safe mode?
Click to expand...
Click to collapse
I'm on 4.4.4.. op was posted when 4.4.3 was out.
I know it's weird, i was very surprised to see my new replacement do it too a little a while a go
.. shrugs

meangreenie said:
I'm on 4.4.4.. op was posted when 4.4.3 was out.
I know it's weird, i was very surprised to see my new replacement do it too a little a while a go
.. shrugs
Click to expand...
Click to collapse
Perform a factory reset and see if it sorts things out??
I'm assuming you're stock, unrooted??

still suffering from this
i have noticed that if location is not set to off, it's much better, where it can run for over a week at time
as soon as i turn location off, I'm lucky to get much over 30 hours before it soft reboots
going back to 4.4 it is completely stable as it always was

[Q] Can Only Boot to Recovery

About 30 minutes ago my phone was working fine, the last thing I remember doing was sending a text. A few minutes later I look down at my phone and notice it is in recovery. At this point I'm confused wondering how it got there, but figure it's whatever and reboot into system. It reboots back into recovery and at this point I'm kinda freaking out. I do a backup, wipe, and restore from a backup ~2 weeks ago. Again, rebooting just causes my phone to go into recovery.
Earlier today there was a notification on my phone about an update but I just ignored it as I didn't have time to deal with it. I assume that it automatically was applied and that is what caused this problem.
edit: If you have this problem, try this: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508

Same thing just happened to me.
I turned off OTA from earlier today and also removed the notification using AppOps and now I can't boot to anything but TWRP

nest75068 said:
Same thing just happened to me.
I turned off OTA from earlier today and also removed the notification using AppOps and now I can't boot to anything but TWRP
Click to expand...
Click to collapse
I'm about to try this, http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508, if it works I'll let you know.

elguy said:
I'm about to try this, http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508, if it works I'll let you know.
Click to expand...
Click to collapse
Was coming here to say this worked - I was already doing this.
I'm back up and running again.
Not sure wtf caused the issue - I didn't take the OTA and have been fine on the phone all day until just now

nest75068 said:
Was coming here to say this worked - I was already doing this.
I'm back up and running again.
Not sure wtf caused the issue - I didn't take the OTA and have been fine on the phone all day until just now
Click to expand...
Click to collapse
Yeah, worked me too. Not sure what happened either, phone says its still on KVT49L.D85010d.

Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over

gpgon said:
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
Click to expand...
Click to collapse
I was the same - the zip file fixed my issue - didn't have to start over

Gotta love XDA.. i was getting ready for bed.. saw a bright light, it was my phone. Same thing as mentioned. only rooted and bumped. Have been denying the OTA. Even did the hidden menu trick, but still got notifications for some reason. Flashing the ZIP showed success; trying to restore my back up now.

esoteric1311 said:
Gotta love XDA.. i was getting ready for bed.. saw a bright light, it was my phone. Same thing as mentioned. only rooted and bumped. Have been denying the OTA. Even did the hidden menu trick, but still got notifications for some reason. Flashing the ZIP showed success; trying to restore my back up now.
Click to expand...
Click to collapse
Once you flash the zip you shouldn't need to restore. I just clicked on reboot system and was back in

nest75068 said:
Once you flash the zip you shouldn't need to restore. I just clicked on reboot system and was back in
Click to expand...
Click to collapse
Well i had to restore the newest back up, because I restored an old back up to see of it would reboot correctly. All works fine now. Still very weird.

gpgon said:
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
Click to expand...
Click to collapse
I mean I still have Root and TWRP, I might have factory reset in my panic last night before finding the fix above. Probably the cause of losing all my apps and data

ATTT Forced UPDATE
It would appear after cruising the forums this morning that ATT forced an update to all users last night. It happened to me and many others like yourself. even people that had turned off updates in the hidden menu. It is total crap and not to happy about it obviously. good thing it sent me into a boot loop, and @autoprime zip fixed me up, even though i was back up on stock rooted, I took this opportunity to move over to the PoweruserV1 international rom to attempt to keep this from happening again. Luckily our DEVS are getting development moving and soon this will be a thing of the past....

I froze Software Update with TB and did not get auto updated last night and have not gotten any new nags today. I did try to update yesterday and got the stuck in TWRP thing and flashed the fix to get back working.

KennyG123 said:
I froze Software Update with TB and did not get auto updated last night and have not gotten any new nags today. I did try to update yesterday and got the stuck in TWRP thing and flashed the fix to get back working.
Click to expand...
Click to collapse
whats the name of the apk to freeze? Thanks

Just adding to this, that it was 'forced' onto me as well, and also sent me to soft brick loop (TWRP), so I'm having to use the get out of jail thread. THANKS LG!! YOU GUYS ROCK!!! (#[email protected]%&*!!!!) This is the LAST time I trust another corporate BS liar's announcement that they care about the 'community' and are going to try and be nice 'from here on out'. Moving forward, it will be NEXUS and nothing else for me.

esoteric1311 said:
whats the name of the apk to freeze? Thanks
Click to expand...
Click to collapse
It is called Software Update in TB. I only have it frozen since last night so hopefully this does the trick...it also removes update option from settings FYI.

Anyone else have this happen again last night? Phone was fine at 5am, woke up at 8:30 to recovery. Flashed the same zip and now it's all fine again.

Freeze software update with titanium backup so your phone doesn't try to install the update agian

wow att and their updates f*** with everything, currently having a locked s4 with old firm of mf3. i plan on upgrading my device but on the fence with all this lock down bs. switching to tmobile seems like a decent option...... so confused and undecided

How to stop lollipop from installing automatically?

I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.

Secret Menu
I went to the dialer keypad and typed in 3845#*850#, the 850 is my model number. Change it to your model # and secret menu will appear. Tap on WLAN settings and it will show OTA updates and pick disable. That's it. Worked for me.

Did that but the phone will still try to install. The reason I know is because my phone will be boot looping in twrp. At first I thought I did something crazy until this morning I saw a message saying phone will install update and will reboot in 10 seconds. Good thing is that I have the boot loop fix zip file in my sdcard.

I kept having this happen to me as well, even after disabling the option in the secret menu. I ended up installing the 855 minus 5 ROM.

I actually had that happen as well. My whole system was gone and stuck in twrp. I downloaded the copy of the 10f stock file and the zip fix file. Thought everything was good, then the update popped up again in the notifation bar, so I made a backup in twrp and tried disabling notifications. The next morning it started to auto install and it failed. Stuck in twrp again, ran my backup then disabled notifications again. Haven't seen the update again in the notifications. Hopefully it won't come back.

Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850

So I tried Titanium Backup. Couldn't figure out how to do it. I also noticed I couldn't send or receive MMS pics. Did some searching and on Google Play, there is an app called Disable Service. Download the app, open it, click on system at the top, scroll down to Google Play Services and click on it. Scroll down to SystemUpdateService and uncheck the box. I also went down to software update and unchecked all 3 of those boxes. Restart your phone and you're done. I also re enabled the setting in the secret menu. Now my pics come through again and the update disappeared when I restarted the phone.

Can the OTA be undone?
auky said:
I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.
Click to expand...
Click to collapse
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.

jkovacs89 said:
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.
Click to expand...
Click to collapse
I'm afraid you wont be able to go back to rooted kitkat without having to clean install as there is no root for Lollipop yet.

aybarrap1 said:
Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850
Click to expand...
Click to collapse
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.

adosin said:
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.
Click to expand...
Click to collapse
I have NOT received a single nag or download for OTA. I have had these frozen for over two months without seeing any issues in the phone's operations. In fact I waited 10 days after the 10f was released before installing and had no issues.

5.1 update issues

I apologize if this issue has already been addressed but Im beyond frustrated.
Since my OTA update to 5.1, my phone is completely crippled. It randomly powers off about 10 times a day (not a auto restart) and I have to power back up. It will also auto restart another 5 to 7 times a day, when it does this it will get stuck in a loop of trying to boot into the OS and restarting all over again. So it will display "Google" for about 2 seconds and then restart again. This is only stopped by holding down the power button. The best part about this happening is that the phone then thinks its the first time I have powered on since the 5.1 update and will initialize all of my apps, which takes about 5 to 10 min. I have had 5.1 for about a week or so and its been getting worse every day. More power off's and restarts each day.
I should note that I am with T-Mobile and my phone is not rooted. Bone stock
My phone is borderline unusable since the update. Please god somebody help me.........

Flash 5.1 factory images

beekay201 said:
Flash 5.1 factory images
Click to expand...
Click to collapse
Excuse my lack of knowledge, but what good would that do? Didn't I get the factory image when I got my OTA update from Google?

dafababa said:
Excuse my lack of knowledge, but what good would that do? Didn't I get the factory image when I got my OTA update from Google?
Click to expand...
Click to collapse
Basically something wierd went with the update, maybe a file got corrupt, some risidual 5.0 code is there. Who knows.
The best way out is probably to flash 5.1 again like said above although not really explained. This will ensure the entire phone is 5.1 and there isn't some 5.0 risidual code somewhere which is likely causing the problem.
It will flash your entire phone with stock 5.1, no root, custom recovery or kernel or anything, 100% stock. You will lose your data though, so if you can, back it up!
Download the 5.1 stock image here: https://developers.google.com/android/nexus/images#hammerhead
it will say 5.1 next to it, it'll be pretty clear.
Extract the contents after the download and run the flash-all script.

matt4321 said:
Basically something wierd went with the update, maybe a file got corrupt, some risidual 5.0 code is there. Who knows.
The best way out is probably to flash 5.1 again like said above although not really explained. This will ensure the entire phone is 5.1 and there isn't some 5.0 risidual code somewhere which is likely causing the problem.
It will flash your entire phone with stock 5.1, no root, custom recovery or kernel or anything, 100% stock. You will lose your data though, so if you can, back it up!
it will say 5.1 next to it, it'll be pretty clear.
Extract the contents after the download and run the flash-all script.
Click to expand...
Click to collapse
Before I do any of this I want to note that it appears there are many other people who are having the exact same issues as me. Is it possible that the update is just buggy??

dafababa said:
Before I do any of this I want to note that it appears there are many other people who are having the exact same issues as me. Is it possible that the update is just buggy??
Click to expand...
Click to collapse
there are people that are reporting a few issues, mainly the memory leak issue still being present. There are none or very little talking about 7 - 10 random power offs a day. This is very unusual and likely to be a specific issue to you not mainstream.

matt4321 said:
there are people that are reporting a few issues, mainly the memory leak issue still being present. There are none or very little talking about 7 - 10 random power offs a day. This is very unusual and likely to be a specific issue to you not mainstream.
Click to expand...
Click to collapse
Well I just finished flashing 5.1 build LMY47i and i can confirm the problem still exists for me. Im just gonna go back to 5.0.1

dafababa said:
Well I just finished flashing 5.1 build LMY47i and i can confirm the problem still exists for me. Im just gonna go back to 5.0.1
Click to expand...
Click to collapse
I htink you may have a loose power button or a loose contact. i had the same problem. Try to press it in really hard and it should fix the issue.

dafababa said:
Excuse my lack of knowledge, but what good would that do? Didn't I get the factory image when I got my OTA update from Google?
Click to expand...
Click to collapse
OTA update ain't the same as a factory image.

beekay201 said:
OTA update ain't the same as a factory image.
Click to expand...
Click to collapse
I've flashed back to 5.0.1 and still have the problems. I'm going to assume its a power button issue.

chaose said:
I htink you may have a loose power button or a loose contact. i had the same problem. Try to press it in really hard and it should fix the issue.
Click to expand...
Click to collapse
So like how hard?

Recovered from boot loop but constant crashes with older ROM

I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?

I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine

Jst flash a newer modem in recovery

mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.

PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.

Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine

KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.

Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.

Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.

mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.