Develop Bugs

Galaxy Nexus keeps rebooting

Today when i got home i turned on Wifi and suddenly my phone went into a boot loop.. It doesnt get past the "Google" logo at the beginning and just keeps rebooting every 5 seconds.. I have tried doing a hardreset restoring to factory settings but that didnt work.. It is rooted.
Can anyone help me fix this?:/

What Rom/Kernel are you on? Can you get it into download mode? Have you tried restoring a Nandroid? Have you tried a fresh install?

I had the CM9 3/29 nightly running. Had the phone in desktop mode all night. This morning it started rebooting after coming to the home screen, and then situation is getting worse, it reboots after every boot. I had a good CM9 nandroid back up, restored and still doing the same thing.
CM9 nightly, no separate kernel, just some tweaks and was @1350 under performance.
Can there be some hardware damage?
Help please!!
---------- Post added at 09:54 AM ---------- Previous post was at 09:51 AM ----------
Phyxius said:
Today when i got home i turned on Wifi and suddenly my phone went into a boot loop.. It doesnt get past the "Google" logo at the beginning and just keeps rebooting every 5 seconds.. I have tried doing a hardreset restoring to factory settings but that didnt work.. It is rooted.
Can anyone help me fix this?:/
Click to expand...
Click to collapse
Was your phone continuously on, and got hot by any chance?

Don't run performance governor. Also just do a full wipe system and data and flash a known stable CM9 build. That should get you up and running.

Sdobron said:
Don't run performance governor. Also just do a full wipe system and data and flash a known stable CM9 build. That should get you up and running.
Click to expand...
Click to collapse
Done, no go there. One thing I am noticing is a "pop" sound just before it reboots

This happened to me 2 months ago. The way I fixed it was by putting it into download mode and flashing 4.0.1 YAKJU via the ODIN file found on the Samsung German website. Phone has been good ever since. *knock on wood*
EDIT: BTW, after that, I updated to 4.0.2 OTA normally, and since then, I've been manually updating because I rooted my phone.
Sent from my Galaxy Nexus using XDA App

wiki_warren said:
This happened to me 2 months ago. The way I fixed it was by putting it into download mode and flashing 4.0.1 YAKJU via the ODIN file found on the Samsung German website. Phone has been good ever since. *knock on wood*
EDIT: BTW, after that, I updated to 4.0.2 OTA normally, and since then, I've been manually updating because I rooted my phone.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Yes thats the only way to do it.
Installed the rootkit 5.6 and downloaded the 4.0.4 into the corresponding folder.
Sure wiped my phone completely, but I don't have a $600 paper weight.
Thanks all!

Can't connect to Sprint service

I was running CM10 yesterday and decided to flash on screen nav buttons after i had updated to the latest CM10 nightly build, everything was working fine. I created a nandroid backup before flashing the buttons and decided the buttons werent for me a few minutes after flashing so i restored back. The restore was probably corrupt or something cause i had a lot of my settings there still but many of my apps were gone and it felt wrong so i flashed CM10 after wiping everything, clean flash.
That's when the problems started... I couldn't get any cell service and logged into sprint.com to see if i could maybe reactivate it there but the site was under maintenance last night. Today I woke up and tried to activate it but failed. Flashed CM10 a few times still no signal, flashed back to stock using this http://forum.xda-developers.com/showthread.php?t=1737859 and still no signal. When i apply the OTA update and the phone restarts com.android.phone has stopped keeps looping.
Any ideas or should i reset the binary counter and take it into the Sprint store?

hvuong said:
I was running CM10 yesterday and decided to flash on screen nav buttons after i had updated to the latest CM10 nightly build, everything was working fine. I created a nandroid backup before flashing the buttons and decided the buttons werent for me a few minutes after flashing so i restored back. The restore was probably corrupt or something cause i had a lot of my settings there still but many of my apps were gone and it felt wrong so i flashed CM10 after wiping everything, clean flash.
That's when the problems started... I couldn't get any cell service and logged into sprint.com to see if i could maybe reactivate it there but the site was under maintenance last night. Today I woke up and tried to activate it but failed. Flashed CM10 a few times still no signal, flashed back to stock using this http://forum.xda-developers.com/showthread.php?t=1737859 and still no signal. When i apply the OTA update and the phone restarts com.android.phone has stopped keeps looping.
Any ideas or should i reset the binary counter and take it into the Sprint store?
Click to expand...
Click to collapse
Flash back to stock in Odin preferably. And do ##72786# in the dialer. No need to take the ota's. Just grab the newest modem from the forums here. Especially on an aosp based Rom.taking the full ota is pointless

Please make sure to update us...

billard412 said:
Flash back to stock in Odin preferably. And do ##72786# in the dialer. No need to take the ota's. Just grab the newest modem from the forums here. Especially on an aosp based Rom.taking the full ota is pointless
Click to expand...
Click to collapse
Don't mean to hijack the thread, but do you or anyone else know of any negative effects using this code? I've been working on my MIUI port for a while and this often happens to me (no signal, can't send sms etc)
Flashing back to a TW Rom and using the code has always worked, but idk if there's anything bad about using this like 3-4 times a week
Sent from my SPH-L710 using Tapatalk 2

billard412 said:
Flash back to stock in Odin preferably. And do ##72786# in the dialer. No need to take the ota's. Just grab the newest modem from the forums here. Especially on an aosp based Rom.taking the full ota is pointless
Click to expand...
Click to collapse
After I flash stock with Odin everything is fine, except for the cell service. Whenever the phone restarts by me or OTA update i get the com.android.phone has stopped loop. After typing your code in the dialer the phone restarted after flashing a screen, couldnt catch what it said. after the phone booted it started the com.android.phone loop again... I think ill just take it to sprint tonight before they close unless you guys have any other ideas

hvuong said:
After I flash stock with Odin everything is fine, except for the cell service. Whenever the phone restarts by me or OTA update i get the com.android.phone has stopped loop. After typing your code in the dialer the phone restarted after flashing a screen, couldnt catch what it said. after the phone booted it started the com.android.phone loop again... I think ill just take it to sprint tonight before they close unless you guys have any other ideas
Click to expand...
Click to collapse
Wipe everything before the Odin flash including /system and immediately after wipe data/factory reset before it boots.
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
fergie716 said:
Don't mean to hijack the thread, but do you or anyone else know of any negative effects using this code? I've been working on my MIUI port for a while and this often happens to me (no signal, can't send sms etc)
Flashing back to a TW Rom and using the code has always worked, but idk if there's anything bad about using this like 3-4 times a week
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Don't think so I do it often too. Don't think it hurts anything tho

billard412 said:
Wipe everything before the Odin flash including /system and immediately after wipe data/factory reset before it boots.
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
Don't think so I do it often too. Don't think it hurts anything tho
Click to expand...
Click to collapse
Thanks.. I've been Googling it and found some stuff on the Sprint forums the other day. I'll enter it when my 3G seems to lag a bit lol. Always provides a boost
Sent from my SPH-L710 using Tapatalk 2

I got it repaired at the Sprint store. They replaced the board after flashing didnt work for them either. It was probably the radio he said

ya cuz he dont no u ****ed wit it. i bet he didnt no wat he was doing and the sprint store wasnt necessary. my $.02

Music Stops with Screen Off (F460K)

Hey guys I've had this issue where regardless of what music app I use, a few seconds after I turn my screen off (i.e. lock the device) the music will stop playing until I turn it back on.
Anyone have any idea why? I'm on version 10e (latest according to PC Suite and OTA Checker), and I'm stock unrooted.
Other than that the phone's been amazing and blazing fast, even outspeeding my M8 GPE sometimes
Sent from my LG G3 Cat.6 using Tapatalk

Also, when charging, this problem doesn't occur. This further adds to the mystery...
Also, it happens if I have music local or streaming, so that rules out network issues.
Sent from my LG G3 Cat.6 using Tapatalk

UPDATE: OK so after messing with about every single setting on the phone, I tried switching it back to Dalvik. Fixed everything 100%. Whole phone is faster, from opening apps to web pages.
Very strange... Not sure why there would be so much ART incompatibility, but I guess it's 4.4.2 and not .3 or .4. If anyone else has has this problem (including an inability to wake the phone up without a few tries), check your RunTime. I'm hoping it'll be better next update, but for now this'll have to do.
Sent from my LG G3 Cat.6 using Tapatalk

SolarTrans said:
UPDATE: OK so after messing with about every single setting on the phone, I tried switching it back to Dalvik. Fixed everything 100%. Whole phone is faster, from opening apps to web pages.
Very strange... Not sure why there would be so much ART incompatibility, but I guess it's 4.4.2 and not .3 or .4. If anyone else has has this problem (including an inability to wake the phone up without a few tries), check your RunTime. I'm hoping it'll be better next update, but for now this'll have to do.
Sent from my LG G3 Cat.6 using Tapatalk
Click to expand...
Click to collapse
Hi there!
I have exactly the same problem since I updated the phone to Lollipop (D85520A) but before that I didn't have that problem. Firstly I found this when I updated to D85519H and then I performed another update to the current version (D85520A) and it didn't help. The smartphone is way better, but this problem is really ennoying me.
ART is not available on Lollipop and my phone went only for one day to ART mode and it was a pain in the ass (when I still had 4.4.2) and then I switched back to normal.
I am thinking about to a factory reset and reinstall Android 5.0 on CSE mode AGAIN and see what happens, but I think it won't help at all.
Do you have any idea of what could I do in order to solve this problem?
Thank you in advance.

Fixed
Hi there!
Just a short update.
Like I mentioned before, I got this problem when I updated my phone with the new Lollipop FW (D85519H) and then I tried to perform another update using the D85520A but the problem was still there. So I believe that the update didn't fix the issue from the previous update so I performed another clean update using the same last one and the problem disappeared.
Thank you anyway.

juansavage said:
Hi there!
Just a short update.
Like I mentioned before, I got this problem when I updated my phone with the new Lollipop FW (D85519H) and then I tried to perform another update using the D85520A but the problem was still there. So I believe that the update didn't fix the issue from the previous update so I performed another clean update using the same last one and the problem disappeared.
Thank you anyway.
Click to expand...
Click to collapse
I have the same problem. What do you mean by "clean update"?

ZHENURIK said:
I have the same problem. What do you mean by "clean update"?
Click to expand...
Click to collapse
Probably CSE flash with this method: http://forum.xda-developers.com/showthread.php?t=2785089

Frequent freezes and hangs after rooting and installing twrp

So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!

aclays said:
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
Click to expand...
Click to collapse
What model?(network)

aclays said:
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
Click to expand...
Click to collapse
go install a custom rom like jasmineROM or EmotionOS, straight up stock can sometimes be unstable when you are rooted.

ziggy71 said:
What model?(network)
Click to expand...
Click to collapse
Verizon SM-N910V retail
weard1212 said:
go install a custom rom like jasmineROM or EmotionOS, straight up stock can sometimes be unstable when you are rooted.
Click to expand...
Click to collapse
I can't even get it stable on full stock. I Odin'd in the Full Firmware for CPF3 in this thread: [Firmware] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU2CPF3] by hsbadr which overwrote TWRP and seemingly removed all traces of rooting, yet the instability is still there.
It occasionally is giving me the error "System process stopped", occasionally is rebooting entirely, there have been a few times where it wouldn't boot up at all. I had to pull the battery and leave it out for 5-10 minutes to get it to boot. I'm running out of ideas on what to flash over to fix it. Is it possible that the Kernel I installed while rooted is causing problems? The full firmware for CPF3 should have overwritten it, correct?

aclays said:
Verizon SM-N910V retail
I can't even get it stable on full stock. I Odin'd in the Full Firmware for CPF3 in this thread: [Firmware] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU2CPF3] by hsbadr which overwrote TWRP and seemingly removed all traces of rooting, yet the instability is still there.
It occasionally is giving me the error "System process stopped", occasionally is rebooting entirely, there have been a few times where it wouldn't boot up at all. I had to pull the battery and leave it out for 5-10 minutes to get it to boot. I'm running out of ideas on what to flash over to fix it. Is it possible that the Kernel I installed while rooted is causing problems? The full firmware for CPF3 should have overwritten it, correct?
Click to expand...
Click to collapse
I've had some issues myself. I originally used paul pizz PJ2, which is an awesome rom. Gives you stability of stock, but feel of custom. I then went to PL1 and EmotionOS. After a few days, I noticed, reduced connectivity, camera wouldn't focus, and button reassignments. So, I just wiped cache and Dalvik, stuck in boot loop. I downloaded the newest EmotionOS. Wiped everything, installed it. boot loop. So I did a another wipe and installed the deodexed Ricks ROM V2. So far so good, but it has only been a day. If you do a full retail firmware flash, that should fix your issues. If you did a full firmware, then yes, it would be overwritten. Try going back to 5.1.1 PA1 full firmware flash. Then you could allow the phone to take the OTA if you wish. But, that should fix the issue. If not let me know. And I will keep you informed of the new rom. Also, if you have a card reader, check your sd. Take anything that you want off of it, and wipe it as well. These Notes are finicky.

ziggy71 said:
I've had some issues myself. I originally used paul pizz PJ2, which is an awesome rom. Gives you stability of stock, but feel of custom. I then went to PL1 and EmotionOS. After a few days, I noticed, reduced connectivity, camera wouldn't focus, and button reassignments. So, I just wiped cache and Dalvik, stuck in boot loop. I downloaded the newest EmotionOS. Wiped everything, installed it. boot loop. So I did a another wipe and installed the deodexed Ricks ROM V2. So far so good, but it has only been a day. If you do a full retail firmware flash, that should fix your issues. If you did a full firmware, then yes, it would be overwritten. Try going back to 5.1.1 PA1 full firmware flash. Then you could allow the phone to take the OTA if you wish. But, that should fix the issue. If not let me know. And I will keep you informed of the new rom. Also, if you have a card reader, check your sd. Take anything that you want off of it, and wipe it as well. These Notes are finicky.
Click to expand...
Click to collapse
So I did actually go back to stock 5.1.1 and successfully take the 6.0.1 OTA, the issue didn't resolve. At that point I flashed the full stock CPF3, still no changes.
A new thing has popped up too. When I try to boot into recovery it says it's installing an update, then after about 5 minutes it goes to a black screen and nothing happens. I end up having to pull the battery to restart it. Discovered that when I tried to go clear all the caches and such before flashing CPF3, and it is still doing the same thing after flashing CPF3. I thought that by flashing the full firmware for CPF3 it would solve that.

aclays said:
So I did actually go back to stock 5.1.1 and successfully take the 6.0.1 OTA, the issue didn't resolve. At that point I flashed the full stock CPF3, still no changes.
A new thing has popped up too. When I try to boot into recovery it says it's installing an update, then after about 5 minutes it goes to a black screen and nothing happens. I end up having to pull the battery to restart it. Discovered that when I tried to go clear all the caches and such before flashing CPF3, and it is still doing the same thing after flashing CPF3. I thought that by flashing the full firmware for CPF3 it would solve that.
Click to expand...
Click to collapse
So you are full stock? Does the update issue happen on the stock recovery?

ziggy71 said:
So you are full stock? Does the update issue happen on the stock recovery?
Click to expand...
Click to collapse
Yep it did. So I think I've actually fixed it now. I thought that flashing the full firmware would also flash the boot loader and modem, but I Odin'd both of those in and so far so good! It did the whole updating thing again just like before this time, but when it was done it actually loaded up recovery like it was supposed to. So at that point I wiped the cache, factory reset, then used Odin to flash in the boot loader and modem for CPF3 that I found in that thread.
I've been using my phone and installing things for a couple hours now and haven't had a single hang. Before I did this, it would hang very quickly. Maybe I'll get brave and try rooting and whatnot again later, but for now I'm just going to back off for a bit. Thanks for the help!

And so much for that. It was more stable than it had been in ages so I started installing all my apps and whatnot, now it's just as unstable as it used to be, just took a couple days to happen. I'm running out of ideas

Upgraded to Oreo yesterday, rebooting randomly...

As the title says, phone has randomly rebooted
... twice in the last few minutes, both times I had picture in picture going while sending a text...has anyone else experienced this? Also, the boot time is amazingly fast at least!
Chris

cswee1932 said:
As the title says, phone has randomly rebooted
... twice in the last few minutes, both times I had picture in picture going while sending a text...has anyone else experienced this? Also, the boot time is amazingly fast at least!
Chris
Click to expand...
Click to collapse
Did you do a wipe when you flashed or just update? If you just did an update, I would try to reinstall and let it wipe the device.

Yup. I'm experiencing this as well. Happened to me twice yesterday. Maybe try a factory reset?
Sent from my Pixel XL using Tapatalk

Having the same issue did a complete factory install with the stock image.
Then rooted not sure if that is causing my issues but, is anyone else stock not rooted having random reboots?

I've had 3 reboots since jumping on Oreo. Did my update the clean way through a factory reset and flashing a factory image. Stock, unrooted.

humdrum2009 said:
Having the same issue did a complete factory install with the stock image.
Then rooted not sure if that is causing my issues but, is anyone else stock not rooted having random reboots?
Click to expand...
Click to collapse
Stock, updated via ota... Having 5 to 6 reboots per hour. Google is sending a replacement phone.

Maybe you have to do a factory reset.

Reason why i havent upgraded. Still on a rock solid nougat until google fix all this problems. Maybe 8.1 or so. Seem like reboot is a common problem with the pixel,. All thread about orea theres someone talking about his reboot problem in many different sites.

jerryhou85 said:
Maybe you have to do a factory reset.
Click to expand...
Click to collapse
Did that too. It is even rebooting in safe mode after a factory reset Hence the return...

sandibhatt said:
Did that too. It is even rebooting in safe mode after a factory reset Hence the return...
Click to expand...
Click to collapse
That sounds much like a hardware failure... :crying:

I had random reboots too coming from DP4 to FInal. No more random reboots since I flashed the factory images

Is 8.0 the version that is the start of the new OS updating system? I wonder if the partitioning is getting all screwed up? I think I'll stay on 7.1.2 for a bit longer till this gets ironed out.
Sent from my Pixel XL using Tapatalk

Stock, bootloader unlocked, Oreo by OTA, and 1 random reboot and 1 random power off
Sent from my sailfish using XDA Labs

Not gonna upgrade to Oreo.
Is there such a way?

nabbed said:
Not gonna upgrade to Oreo.
Is there such a way?
Click to expand...
Click to collapse
Just don't download the OTA till they send out a patch. That's what I'm doing.
Sent from my Pixel XL using Tapatalk

when i first updated to oreo and rooted it, i ran into the rebooting issues some of you are experiencing. i think the root of my issue was busybox. i did a clean install of oreo again the other day and rooted, but didnt put busybox on the phone. phone ran fine for a day, so i tried giving busybox another go. the reboot issues came back. hope this helps

Mine only reboots randomly if I have YouTube picture in picture enabled once I disabled it I haven't had any reboots maybe try to disable that

Just did the update a couple hours ago and so far so good. Picture in picture works too. Stock, GPE on VZW, no root or anything.
Sent from my Pixel XL using Tapatalk

Guys, anyone still getting random on persistent reboots on Oreo with Pixel (XL)? I'm doing my second factory reset atm and monitoring these two threads on buganiser - 1, 2. Basically people started getting reboots after upgrading to Oreo and one notable common thing is: 'Sense Key : Hardware Error [current]' which Google reps assigned to the threads read as hardware issue (probably with Toshiba's memory chips being prone to overflow/overload (?)). They haven't answered my question why is it only happening on Oreo though. I REALLY don't want to go through the warranty process again only to get a device with the same problem as I still believe it can be fixed in 8.1. Is there anyone who had similar issues that got fixed with the 8.1 Beta? Cheers!

I'm experiencing the random reboots too.
Oct. 8.0, Magisk, Root
I almost missed an alarm due to this, so I think I may go back to Nougat. Not only does it reboot, but it gets stuck in the boot screen. If I hold Power and reboot, it comes up though.