Database Users

Razr M keeps rebooting

I was wondering if anyone could help me figure out why my phone keeps rebooting. I've tried stock 4.1.1, stock 4.2.2, pacman, carbon, CM10.1, aokp and they all seem to reboot. The reboots are pretty random but I can pretty much always get it to reboot within 30 minutes if I'm playing some sort of audio or video. Also when I turn my screen on (from sleep) it flashes this weird screen (see attached image).

rocksolidsr said:
I was wondering if anyone could help me figure out why my phone keeps rebooting. I've tried stock 4.1.1, stock 4.2.2, pacman, carbon, CM10.1, aokp and they all seem to reboot. The reboots are pretty random but I can pretty much always get it to reboot within 30 minutes if I'm playing some sort of audio or video. Also when I turn my screen on (from sleep) it flashes this weird screen (see attached image).
Click to expand...
Click to collapse
could be a ROM/Kernel pairing. have you tried wiping system/data/internal storage - reboot recovery, then flashing a new ROM?
the static screen is common on custom 4.2.2 ROMs, but it's usually a quick flash. I don't get any random reboots though.

I've tried many different rom's along with the Vanquishkitties kernal but still random reboots

I noticed my phone acting weird, specifically it would not play any audio, I noticed this because when I was in the dialer it was going really slow. Then I tried to play some notifications and none worked. I rebooted my phone and all seemed ok, I've attached two logs the first one being while audio would not work and the second after the reboot. I'm not really sure what to look for in the logs but thought someone here might.

This might be something...
E/AudioStreamOutALSA( 300): pcm_write returned error -5, trying to recover
Or this, just a warning though...
W/AudioTrack( 692): obtainBuffer timed out (is the CPU pegged?) 0x63d72108 name=0x6user=00001000, server=00000000
Sent from my Nexus 7 using Tapatalk HD

Just noticed that when in the dialer and the phone starts working very slow, if I turn the sound all the way off, the phone becomes responsive

two more logcats for anyone interested in helping this time one is when trying to use google voice actions, I actually get an error message that says can't open microphone and the other is when someone called me and I did not have any ringtone but I answered and I could not hear them and they could not hear me, shortly after my phone rebooted, I did not catch the reboot in the logcat.
Also when it reboots it doesn't reboot all the way it boots to the boot logo screen and then hangs and I have to hold all three buttons until it reboots again, is there a way to get it to just reboot on its own?
After the reboot everything seems to be fine until I experience the same issues again

Which ROM are you on right now? That sounds like a kernel level issue
Sent from my XT907 using Tapatalk 4 Beta

I'm currently using CARBON-JB-NIGHTLY-20130712-0020 and kernel [email protected]
but i've experienced this issue with every ROM / kernel i've tried even the stock ones.

rocksolidsr said:
I'm currently using CARBON-JB-NIGHTLY-20130712-0020 and kernel [email protected]
but i've experienced this issue with every ROM / kernel i've tried even the stock ones.
Click to expand...
Click to collapse
Has your issue been resolved? I am almost facing the same issues of random rebooting with my phone and was searching for a solution....

Did anyone ever find a fix for this?
Stock rooted 4.1.2 with some frozen bloatware and a GSM-specific build.prop file. I get several random reboots per day. Has upgrading to KK fixed this for anyone?

5318008 said:
Did anyone ever find a fix for this?
Stock rooted 4.1.2 with some frozen bloatware and a GSM-specific build.prop file. I get several random reboots per day. Has upgrading to KK fixed this for anyone?
Click to expand...
Click to collapse
Im having this issue and Im on kitkat.

[Q] Phone keeps rebooting and cannot update PRL, Firmware (sleep of death)

I updated my phone to a DeathStalker (MF9?) ROM and I have two constant issues:
1. I can no longer update my PRL, Profile or Firmware, etc. It keeps telling me my session is in progress and to try again later.
2. Occasionally my phone randomly reboots.
3. When I click the power button to wake the phone the phone goes into sleep of death forcing me to reboot or it doesn't wake and reboots on its own.
No idea what's causing these issues or how to fix them. I updated to Deathstalker from an old (June 2013) ROM and think it might have to do with firmware or something

Laos101 said:
I updated my phone to a DeathStalker (MF9?) ROM and I have two constant issues:
1. I can no longer update my PRL, Profile or Firmware, etc. It keeps telling me my session is in progress and to try again later.
2. Occasionally my phone randomly reboots.
3. When I click the power button to wake the phone the phone goes into sleep of death forcing me to reboot or it doesn't wake and reboots on its own.
No idea what's causing these issues or how to fix them. I updated to Deathstalker from an old (June 2013) ROM and think it might have to do with firmware or something
Click to expand...
Click to collapse
could just be a bad DL try to dl the rom again and do a clean wipe and reflash.....if the issue persists try a different rom to see if its rom related (also there have been alot of issues with MF9 since its release)

Laos101 said:
I updated my phone to a DeathStalker (MF9?) ROM and I have two constant issues:
1. I can no longer update my PRL, Profile or Firmware, etc. It keeps telling me my session is in progress and to try again later.
2. Occasionally my phone randomly reboots.
3. When I click the power button to wake the phone the phone goes into sleep of death forcing me to reboot or it doesn't wake and reboots on its own.
No idea what's causing these issues or how to fix them. I updated to Deathstalker from an old (June 2013) ROM and think it might have to do with firmware or something
Click to expand...
Click to collapse
You should literally ask this in the thread. You will get more help there. But if im not mistaken the developers for deathstalker took out the function to update prl and profile and also the fact that is "almost" a rom ported to our device it wouldnt have that function. Also it the reboots and death sleep could be kernel related.

ROMANTiC KiD said:
You should literally ask this in the thread. You will get more help there. But if im not mistaken the developers for deathstalker took out the function to update prl and profile and also the fact that is "almost" a rom ported to our device it wouldnt have that function. Also it the reboots and death sleep could be kernel related.
Click to expand...
Click to collapse
Right, so this issue is not mutually exclusive to any ROM. All recent MF9 / MDL ROMs I have tried (3 in total) have this issue and so on. I've made posts about this but they sadly went unanswered
Not sure if PRL was disabled by that dev but it's a possibility
Kernel is always whatever is thrown into the ROM so I'm not sure how to proceed and nobody else appears to be having these issues.

Laos101 said:
Right, so this issue is not mutually exclusive to any ROM. All recent MF9 / MDL ROMs I have tried (3 in total) have this issue and so on. I've made posts about this but they sadly went unanswered
Not sure if PRL was disabled by that dev but it's a possibility
Kernel is always whatever is thrown into the ROM so I'm not sure how to proceed and nobody else appears to be having these issues.
Click to expand...
Click to collapse
Well that this happen when your running pure stock? If it does could be hardware problem.
Well you can just download any kernel of your choice in the original development. And just flash but make sure you make a backup and chose the right kernel. Well thats because phone handle kernels differently. It wont be the same for each phone. Just like us we wont have the same experience on each same event or changes. Get me?

MF9 has nothing to do with it. MF9 works great and updates PRL as it should. If it doesn't work in the ROM you are using than its the ROM. Usually you will find the best help for a rom related problem in the rom thread. I see you have plenty of posts to post in the development section so I would start there.

[Q] power button longpress menu does not pop up

Hello all,
My apologies if this is a common issue. I have searched but the only old thread about it is the following:
http://forum.xda-developers.com/showthread.php?t=2190960
and no real answer was suggested there, which is why I am asking it again.
So the issue is the same as in that previous thread: quite often, when I longpress the power button, the menu (to shut down, put it on vibrate mode, ...) does not pop up. The only way to get it back is to hold the power button until the phone shuts down, and then reboot the phone, after which it works again (for god knows how long).
I was rooted (with stock rom) before 4.3, but lost my root when updating to 4.3, so I was on stock ROM without root when the problem first appeared. Now yesterday I rooted again and flashed paranoid android ROM (first factory reset, clearing cache and dalvik cache), but the problem remains.
In that old thread one member solved the problem by flashing the stock kernel, however I have never flashed another kernel so I doubt the kernel is the problem?
If anybody knows the issue and a way to solve it, please let me know, it would be greatly appreciated.
Thanks,
Maarten

You did flash a kernel when you flashed the rom
Wayne Tech Nexus

Hey there
No, as in the first post, I have never flashed another kernel on the nexus. Neither did I flash a new radio.
I had not flashed anything yet when the problem started, I only unlocked the bootloader and rooted my phone when I first got it (but it worked a long time without any problems)

Delete this post

Nobody had this issue ?

Found a solution at last!!
wolfway said:
Nobody had this issue ?
Click to expand...
Click to collapse
After quite a long search and a lot of worries, I finally found THE solution...
https://www.youtube.com/watch?v=d8dbrerUacw
how to get out of factory mode for a s4 but it worked on my N7105
- efs/factoryApp/factorymode/ouvrir avec/editeur de texte/ON
- efs/factoryApp/keystr/ouvrir avec/editeur de texte/ON

I have this issue too. I'm using paranoid Android beta 4 with franco kernel and since The moment o rooted my phone this issue started
Sent from my Nexus 4 using XDA Free mobile app

Phone does not start after reboot on jamal2367 ROM, S4 GE Final-R4

Hi all,
I have this annoying issue with [AOSP] Official 4.4.2 - S4 Google Edition - Final-R4 from jamal2367; current baseband installed XXUFNA1.
Problem:
When the phone loses connection, it dies. Then there is no way I can turn it on.
if unplugged from the power: it starts to boot and it dies again, sometimes at the "samsung boot text", sometimes a bit ahead, but it does not go further than the animated logo with 4 coloured bouncing balls (it does not matter how many time I try to restart the phone)
If plugged: it survives the first part of the boot most of the time, but it loops into the animated logo with the 4 coloured bouncing balls and the phone does not start.
Solution:
Every time I have to re-install Android, by:
- deleting Dalvik, Data, System, Cache.
- Install the ROM
- Apply a factory reset
At this point, if connected to the plug, the phone starts, but I have to go through the manual installation process.
This is a bit annoying I have to admin, anyone with this kind of issue, or am I the only one?
A few more info:
Phone was working great with jamal2367 4.3 (don't remember the baseband)
After 4.4 was out I installed it, but it was booting every 5 minutes or so, I decided then to go back to 4.3.
When I went back to 4.3, baseband was changed, but I kept the hold one.
Phone started to have random reboots as well, but once every 3-4 days, so I was ok with it.
4.4 releases were progressing so, after a while I decided to put it back.
I had the problem described above with previous (recent) baseband (like ml6and mj6).
Now I have the latest, but I have got the problem anyway.
A wild guess:
The phone now charges very quickly, I am wondering if the percentage that I see is realistic. Maybe it runs out of battery, which it could explain why the phone dies on reboots, but it does not explain why it loops once plugged in and why it does not turn off normally instead of just dying with a blink of an eye.
mmm that should not be the reason
Another wild guess:
I couldn't target a specific application. Sometimes it dies using fb, sometimes maps, sometimes hangout, sometimes a after a long phone call. The first two have "location" active, but I don't think that the last two are using it.
mmm that should not be the reason either.
A consideration:
I have noticed that once Android is installed, the phone signal is quite good, but then it goes down to one or two lines only. Most of the time I have one line only (in my area) and when it disappear, 6 times out of 7 it dies.
Thanks in advance.
R
PS=I could not post this into "Galaxy S 4 i9505 Android Development"

too long
be sure to flash from zero, wipe everything then flash 4.3
if everything fils go to stock 4.3 or 4.4 TW, then flash 4.4 gpe after

racoonlab said:
PS=I could not post this into "Galaxy S 4 i9505 Android Development"
Click to expand...
Click to collapse
did you try battery calibration?
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care

anu.cool said:
did you try battery calibration?
Click to expand...
Click to collapse
Nope I will give it a try
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care
Click to expand...
Click to collapse
Well, when I delete Dalvik, Data, System and Cache, I do it once I am inside _teamwin recovery_, I can also think about another ROM, but the one from jamal2367 is quite popular and I find it weird that no one else have the same issue.
Thanks for your reply though.
R

Same problem here...
I fixed it by flashing the stock image from samsung, and start all over again with cf_root and recovery. I use CWM, but that dont matter I think.
Loving my 4.4.2 Rom by Danvdh atm!
Good luck!

opticus44 said:
I fixed it by flashing the stock image from samsung, and start all over again with cf_root and recovery. I use CWM, but that dont matter I think.
Loving my 4.4.2 Rom by Danvdh atm!
Good luck!
Click to expand...
Click to collapse
Hi opticus44,
Did you install the stock image through Kies or from any other link? In this latest case, which one?
Thanks,
R

Hi,
you are not alone. we are 2 now.
I have the same problem but the problem stays with samsung stock rom. my phone still reboot random with stock jelly bean.
i use the 4.3 stock rom from this link below, they have high speed host.
http://www.android-hilfe.de/samsung...tes-rollouts-aktuell-xxuemk9.html#post6803655

Xv1nX said:
Hi,
you are not alone. we are 2 now.
I have the same problem but the problem stays with samsung stock rom. my phone still reboot random with stock jelly bean.
i use the 4.3 stock rom from this link below, they have high speed host.
http://www.android-hilfe.de/samsung...tes-rollouts-aktuell-xxuemk9.html#post6803655
Click to expand...
Click to collapse
mmm there must be some way. With the latest R1.1 I cannot even answer a phone call, with Ktoonsez's Kernel, with Alucard's Kernel no button works.
:-O

mmm also installing 4.3 back gives me random reboots. I am wondering if it could a wrong baseband.

it worked perfect for me for some hours. when i deactivated some bloatwares (g. earth, g. music, ...) it crashed and stucks in a loop reboot & crash at googke logo. swipe cache or wait some minutes don`t change anything.
i tried everything, now i have no idea what to do

I installed CyanogenMod and it is more stable. However it cannot do what is supposed to do, make and receives phone calls.
I wonder if it is a baseband issue, now.
R

anu.cool said:
did you try battery calibration?
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care
Click to expand...
Click to collapse
Hi,
What tool do you use for a battery calibration?

racoonlab said:
I installed CyanogenMod and it is more stable. However it cannot do what is supposed to do, make and receives phone calls.
I wonder if it is a baseband issue, now.
R
Click to expand...
Click to collapse
Same issue if I put back Jamal [AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1,mmm, maybe the kernel....

The last thing I can say about it is that also all the sounds are gone. I cannot reproduce any sounds, notifications, alarm etc., it does not work on videos either.

I fix my problem! And I shared the solution here:
http://forum.xda-developers.com/showthread.php?p=49502855

racoonlab said:
Hi opticus44,
Did you install the stock image through Kies or from any other link? In this latest case, which one?
Thanks,
R
Click to expand...
Click to collapse
Sorry, long time since I last checked in. I downloaded official stock image from sammobile and flashed through odin.

same problem here
Hi guys same problem here,
GOOGLE EDITION 4.4.2 installed by Danvdh, Kryten2k35 & Ktoonsez on Galaxy S4 GT-9505 LTE with knox 0x1, and TWRP custom recovery when the battery reaches 0% turns off the phone I put the phone on charge and starts but hangs on colored dots.
How can I fix this?
Thx

Device is shutting itself when I lock it on certain kernels.

Hello,
I have weird issue. When locking the screen (on stock LiquidRemix Kernel, Project K and others) the phone shuts down quietly instead of just going to deep sleep. When I try to pick up and unlock my phone it turn on... All is working fine on Void Kernel as well as on Mint. I tried to go back to stock, but when I flashed custom rom & kernel same issue happened again.
Am I alone with this issue? Do anyone have a possible solution?
Thank you.

radogost said:
Hello,
I have weird issue. When locking the screen (on stock LiquidRemix Kernel, Project K and others) the phone shuts down quietly instead of just going to deep sleep. When I try to pick up and unlock my phone it turn on... All is working fine on Void Kernel as well as on Mint. I tried to go back to stock, but when I flashed custom rom & kernel same issue happened again.
Am I alone with this issue? Do anyone have a possible solution?
Thank you.
Click to expand...
Click to collapse
Happens every single time?
Can you provide logs?
Have you asked in those particular kernel threads?
Edit:
Have you tried locking the phone when music is playing?
When you lock your phone it doesn't go into deep sleep State instantly and doze changes that too.