Every time I root with blob v5, I get the sleep of death issue. When I go back to stock blob, everything works fine. Tried this twice and both times root caused sleep of death... any one else having this issue? Am I doing something wrong? A would love to have root, but not of it's causing sleep of death. Any help is appreciated. thanks
Sent from my Transformer TF101 using Tapatalk
Are you using the most recent ASUS update?
The *only* change on the boot.img in the rooted blob is ro.secure=0..e.g., not way it can cause sleep of death.
If you on the other hand use V5 with older than v8.2.3.9, it's likely to cause issues (e.g. I know it causes issues with camera and bluetooth at the very least).
Also, which SKU are you on? E.g. US, WW, CN etc?
My wife's isn't rooted, and hers has done it once so far. Mine did it twice before rooting it, and never since rooting it (blob v5).
Mine hasn't done it and mine is rooted. Blob v5 btw.
I am on the most recent firmware, 8.2.3.9 US... I wonder if one of my root applications is causing the issue. I will reroot and see if it happens before i install apps. Thanks to all for the input.
Sent from my Transformer TF101 using Tapatalk
It happened to me...i was scared as hell..but when I finally got it to wake up..I flash a rom and it hasnt happened since
da-slicksta said:
It happened to me...i was scared as hell..but when I finally got it to wake up..I flash a rom and it hasnt happened since
Click to expand...
Click to collapse
Could it be some system apps run amok, causing high temperature on the transformer and system shut down?
Just a guess, i have had it few times with my nexus one.
WW Edition had this happen once without root. I do not think it is a rooting issue.
So I rerooted and installed my apps (including the root ones - Adfree, root file explorer, titanium backup). The sleep of death happened. I then tried MoDaCo's rom. The sleep of death happened again. I then tried Prime's Rom. So far I havent had a sleep of death.
da-slicksta said:
It happened to me...i was scared as hell..but when I finally got it to wake up..I flash a rom and it hasnt happened since
Click to expand...
Click to collapse
What Rom are you using?
I updated to latest firmware on asus.com then used blob 5 to root. No problems since I rooted or before. Could some explain what the SOD is and what happens...just see people saying they have had it happen but no description.
Sent from my ADR6400L using Tapatalk
Crimton said:
I updated to latest firmware on asus.com then used blob 5 to root. No problems since I rooted or before. Could some explain what the SOD is and what happens...just see people saying they have had it happen but no description.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
It is exactly what it sounds like - the screen goes to sleep and the device never wakes up from it. You have to double long+press power button to power cycle the device fully.
spuniun said:
It is exactly what it sounds like - the screen goes to sleep and the device never wakes up from it. You have to double long+press power button to power cycle the device fully.
Click to expand...
Click to collapse
Guess I'm lucky then, cross my fingers...
Sent from my ADR6400L using Tapatalk
Crimton said:
Guess I'm lucky then, cross my fingers...
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
If you are lucky, so am I.
I had two Eee pads updated to the ltest ASUS firmaware and then rooted B5 . Not a single glitch in 4 days.
Primes rom
I tried stock, Prime and MCR Hr 5, all of them give me SOD even without any additional application.
I have to play music or run pandora if I want to turn off the screen.
Related
I have seen a few threads posted about random reboots and v3.1. However, my wife's Transformer will go into a cycle where it will reboot, then a minute later or less will reboot again, and keep this up for a while (not sure how long exactly).
Don't know if this is related to an incompatible app/setting or something with the OS (3.1). Is there anything I can check/do to try and prevent this?
**Edit......Forgot to mention device is unrooted running stock 3.1.
I'm facing the Sleep of Death on this TF. It was there even on Stock and is there on other ROM's also. My Transformer reboots when in sleep mode
Srikar_NBK said:
I'm facing the Sleep of Death on this TF. It was there even on Stock and is there on other ROM's also. My Transformer reboots when in sleep mode
Click to expand...
Click to collapse
Yep....pretty much the same problem as I'm trying to fix.
*Bump*
Sent from my PC36100 using XDA App
The workaround I posted here has worked thus far for me.
http://forum.xda-developers.com/showthread.php?t=1120185
Though I haven't tried it without root privilege
sassafras
Mine was rebooting like every 10 minutes, running 3.0.1 stock non-rooted. All I did was reset it to factory settings and the problem went away.
kovla said:
Mine was rebooting like every 10 minutes, running 3.0.1 stock non-rooted. All I did was reset it to factory settings and the problem went away.
Click to expand...
Click to collapse
Why are you running 3.0.1? Upgrade to Android 3.1. It's more stable and reliable.
kovla said:
Mine was rebooting like every 10 minutes, running 3.0.1 stock non-rooted. All I did was reset it to factory settings and the problem went away.
Click to expand...
Click to collapse
If I set it to factory is it going to take it back to 3.0? Or just change all the settings back?
factory reset won't rollback the firmware, it just clear all installed apps, caches and set everything to default
I have the latest stock JB installed from the google factory images with simple root v1.0 and clockworkmod recovery 5.0.2.0, and my phone completely freezes from time to time. If I push the power button the screen goes off, but if I push it again, only the buttons light up, so I have to pull out my battery to reset it. It happens more and more and it get's really annoying. I just had a full wipe a couple days ago, and it did the same thing before, but I didn't had any problems like this with ics. Anyone else having similar problems or is my phone getting crazy? Any advice?
It's called sleep of death. Try to flash another kernel see if that works.
Sent from my Nexus S
kwibis said:
It's called sleep of death. Try to flash another kernel see if that works.
Sent from my Nexus S
Click to expand...
Click to collapse
Thx! Didn't know what it was called, now I can look into it!
Good luck!
kwibis said:
It's called sleep of death. Try to flash another kernel see if that works.
Sent from my Nexus S
Click to expand...
Click to collapse
What? He has stock JB, with the stock kernel. There's hardly anything more stable than that....
The graphics driver had been throwing bugs, but the new r6 release had an update so possibly fixed bug. May be the cause of the OP issue
polobunny said:
What? He has stock JB, with the stock kernel. There's hardly anything more stable than that....
Click to expand...
Click to collapse
Haven't had my phone running stock so I cannot tell whether it is very stable. But the problem he described indicates this particular issue. And now bedalus confirms.
Sent from my Nexus S
So recently after updating to 4.1, I have been experiencing random freezes then reboots. I factory reset my tab 3 times and none seem to have fixed it. Also it appears it only happens in performance mode. Has anyone else experienced this? If so, have you found a fix?
Thanks
Sent from my MB860 using xda app-developers app
pfoxdizzle said:
So recently after updating to 4.1, I have been experiencing random freezes then reboots. I factory reset my tab 3 times and none seem to have fixed it. Also it appears it only happens in performance mode. Has anyone else experienced this? If so, have you found a fix?
Thanks
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Did you make any tweaks on the system before your update? I.e. rooted or custom rom system with changing build.prop, MinFree, or anything that basically you can only do after rooting?
No changes. Completely fresh and.un modified tablet
Sent from my MB860 using xda app-developers app
Honestly, I have gotten some and I'm fresh totally stock just got mine. However, I stopped connecting it to dock and uninstalled songza and MX player. Its a shot in the dark but lets see if any reboots, otherwise back to amazon.
pfoxdizzle said:
So recently after updating to 4.1, I have been experiencing random freezes then reboots. I factory reset my tab 3 times and none seem to have fixed it. Also it appears it only happens in performance mode. Has anyone else experienced this? If so, have you found a fix?
Thanks
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I'm curious as to how much RAM your tablet is using after a cold boot in balanced or perf mode.
Mine stays between 579 and 654mb no matter what.
Haven't had a crash or a freeze since the first 3 days of ownership.
Well that's a lie...I had a lot of freezes and crashing with sygic and earlier editions of some browsers.
pfoxdizzle said:
So recently after updating to 4.1, I have been experiencing random freezes then reboots. I factory reset my tab 3 times and none seem to have fixed it. Also it appears it only happens in performance mode. Has anyone else experienced this? If so, have you found a fix?
Thanks
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I thought it was just me. I've been playing The Bard's Tale on it and got the update the same night. I, too, have noticed random reboots where the game will freeze, and then 5 seconds later the tablet is rebooting. I honestly thought it was the game, but since you're saying it happens to you on Performance mode only, and that is exactly where I am as when I am playing the game, maybe it is performance mode and not hte game causing mine as well.
if that is the case, chalk me up for these random reboots as well.
pfoxdizzle said:
No changes. Completely fresh and.un modified tablet
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Mine was far from fresh, but only rooted, no other mods made.
pceasar said:
Honestly, I have gotten some and I'm fresh totally stock just got mine. However, I stopped connecting it to dock and uninstalled songza and MX player. Its a shot in the dark but lets see if any reboots, otherwise back to amazon.
Click to expand...
Click to collapse
I don't think that will help as 1) I have neither of those two apps, and 2) mine happened when I was not connected to a dock at all.
My tablet after JB update, has been getting freezes. Screen is black but lit and I have to reboot :\
Aria807 said:
My tablet after JB update, has been getting freezes. Screen is black but lit and I have to reboot :\
Click to expand...
Click to collapse
To fix this reboot and screen blank out, you guys need to reflash the full version of JB.
buhohitr said:
To fix this reboot and screen blank out, you guys need to reflash the full version of JB.
Click to expand...
Click to collapse
Might not be a bad idea. But a full install won't allow us to use root keeper methods, so we'd then have to wait for a new root method, right?
I'll deal with the idiosyncrasies until i can root JB and then "blob" my pad (I've been dying to say that, can't you tell?).
Sent from my rooted BIONIC running ICS 6.7.247 (!) via Tapatalk 2
johnlgalt said:
Might not be a bad idea. But a full install won't allow us to use root keeper methods, so we'd then have to wait for a new root method, right?
I'll deal with the idiosyncrasies until i can root JB and then "blob" my pad (I've been dying to say that, can't you tell?).
Sent from my rooted BIONIC running ICS 6.7.247 (!) via Tapatalk 2
Click to expand...
Click to collapse
To root a JB locked bootloader=NO, but for unlocked bootloader=YES. Another way to solve the reboot/screen issue and keep root is to downgrade to .30 (full version), root, then OTA root keeper to save root then let the JB OTA upgrade back to JB, then restore root.
buhohitr said:
To root a JB locked bootloader=NO, but for unlocked bootloader=YES. Another way to solve the reboot/screen issue and keep root is to downgrade to .30 (full version), root, then OTA root keeper to save root then let the JB OTA upgrade back to JB, then restore root.
Click to expand...
Click to collapse
That is exactly what I did. I'll test later this evening, but so far it has been a lot snappier *and* no random reboots.
But, I've also not run performance mode either.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
johnlgalt said:
That is exactly what I did. I'll test later this evening, but so far it has been a lot snappier *and* no random reboots.
But, I've also not run performance mode either.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
Click to expand...
Click to collapse
Also highly recommend to install browse2ram, make all your browsers(stock included), kick ass!!!
buhohitr said:
To root a JB locked bootloader=NO, but for unlocked bootloader=YES. Another way to solve the reboot/screen issue and keep root is to downgrade to .30 (full version), root, then OTA root keeper to save root then let the JB OTA upgrade back to JB, then restore root.
Click to expand...
Click to collapse
What's the point of doing this? I was already on .30 to begin with, ran Debugfs rooted .30 and OTA rootkeeper backed up, and I got the OTA update from JB a week later, which had the SOD issue. Why downgrade and upgrade?
Aria807 said:
What's the point of doing this? I was already on .30 to begin with, ran Debugfs rooted .30 and OTA rootkeeper backed up, and I got the OTA update from JB a week later, which had the SOD issue. Why downgrade and upgrade?
Click to expand...
Click to collapse
The point is it's going to solve your random reboot/blank screen issue. Most of people did exactly what you did included myself, but once you are on JB and experiencing reboot and blank screen, you need to reflash because the install did not done correctly some how. If you reflash a full version of JB, it will fixed the issue but then you don't have root, this is not a problem if you're unlocked. So if you still have locked bootloader, you need to downgrade with full version of .30 then re root. when you install a full version it automatically wipe for you so you don't need to wipe before downgrade. Once you have a fresh install of .30, now you can use OTA to upgrade to JB and keeping root.
Ah gotcha. Well in this case, I might as well just unlock my bootloader and flash [ROM][10/3][JB4.1.1] - Stock Root Odex / De-Odex - 10.4.4.16 Base since it's stock based minus bloatware?
Aria807 said:
Ah gotcha. Well in this case, I might as well just unlock my bootloader and flash [ROM][10/3][JB4.1.1] - Stock Root Odex / De-Odex - 10.4.4.16 Base since it's stock based minus bloatware?
Click to expand...
Click to collapse
Sure you could do that, but I'm waiting for Zeus Rom. This rom is amazing with I/O.
Actually, could the problem be the idle clock speed? I don't recall the TF700 having a 51mhz speed. I thought lowest multiplier was 102mhz. Perhaps that's why it is freezing/sod
I'm gonna raise my min clock speed at 102mhz and see if it freezes any more
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
buhohitr said:
To fix this reboot and screen blank out, you guys need to reflash the full version of JB.
Click to expand...
Click to collapse
Well, I had the same issue on ICS stock and custom rom and JB so I don't think this is anything to do with reflashing, but our old friend IO.
Like people have mentioned before ,change the number of background processes to 4.
Ok so it is like this:
I bought my galaxy r here in sweden 1 year and 3 months ago, it was working perfectly for around 1 year.
At the one year mark i started to have some problems with the touchscreen where the phone would feel a pressure in the middle of the screen, to get rid of this i simply locked and unlocked the phone or rubbed a bit with a cloth on the screen.
Recently when I saw there was a cm10.1 rom with nightlies I rooted my phone and later installed the cm10.1 rom. Now the most anoying thing. I have a problem with my battery where the phone just shuts down randomly (mostly when playing games) even though it sometimes have up too 80% battery remaining. Then when I restart the phone it usually have 0% battery left and therefore shuts itself down again, sometimes it restarts with just a 20-30% batteryloss. This have occured more often recently and it shuts itself of 3-4 times a day. I can't remember if it was like this when i was on stock, before I started to flash and root, but i think it was.
A few days ago i flashed stock ics from odin and I confirmed that both of these problems still were there, so i have hard to belive that it is the modding of the software that have caused this.
Do you guys have any suggestions to how i can be able to use my phone normally again?
Im just a poor student so i don't want to waste money on a new phone after just 1 year :/
wipe data and cache..i think after flashing u restore ur data back.
Sent from my GT-I9103 using Tapatalk 4 Beta
Will this help with the battery?
kataria.vikesh said:
wipe data and cache..i think after flashing u restore ur data back.
Sent from my GT-I9103 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Will this help the crashing/battery?
DippN said:
Will this help the crashing/battery?
Click to expand...
Click to collapse
It may be help you but first tell me, are you restoring data from titanium backup or something related to that..??
Also if you want to take backup then take it using Super backup application.
kataria.vikesh said:
It may be help you but first tell me, are you restoring data from titanium backup or something related to that..??
Also if you want to take backup then take it using Super backup application.
Click to expand...
Click to collapse
Nope, im not takeing backup of anything.
And one other thing i forgot to mention earlier, the phone now also thinks it is charging itself evrn when it is not. It think the usb cable is still connected.
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
paKS7 said:
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
Click to expand...
Click to collapse
Im just glad im not alone with this problem, and as you said, its barely unusable without having it plugged in.
DippN said:
Im just glad im not alone with this problem, and as you said, its barely unusable without having it plugged in.
Click to expand...
Click to collapse
paKS7 said:
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
Click to expand...
Click to collapse
Both of you install CM10.1 using Procedure no 2 from OP.
kataria.vikesh said:
Both of you install CM10.1 using Procedure no 2 from OP.
Click to expand...
Click to collapse
Will try that when i get home, thx.
kataria.vikesh said:
Both of you install CM10.1 using Procedure no 2 from OP.
Click to expand...
Click to collapse
Thank you, vikesh! I'll be able to try Procedure II tomorrow afternoon.
paKS7 said:
Thank you, vikesh! I'll be able to try Procedure II tomorrow afternoon.
Click to expand...
Click to collapse
Sadly, I can confirm that this did not change anything.
The problems are still there :/
DippN said:
Sadly, I can confirm that this did not change anything.
The problems are still there :/
Click to expand...
Click to collapse
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
kataria.vikesh said:
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
I'm definitely going to try this, but as it seems now i think it is more about a faulty battery/hardware that software?
Or have these kind of problems been fixed software before?
One other thing, if i have rooted my device, does the root dissappear when i flash stockrom using odin?
DippN said:
I'm definitely going to try this, but as it seems now i think it is more about a faulty battery/hardware that software?
Or have these kind of problems been fixed software before?
One other thing, if i have rooted my device, does the root dissappear when i flash stockrom using odin?
Click to expand...
Click to collapse
May be hardware or software too..when you will vanish all data & cache then Software issue may be gone but if problem still persist, means you have hardware problem.
Also, root will be lost after flashing Stock ROM from ODIN.
I'm able to also confirm, that Procedure II didn't help the problem. I really doubt it is a hardware fault, because of us two having the exact same problem after flashing the same rom.
@Dippn: Do you know which nightly build you used? In my case it was the nightly build "20130405". Also could you check which baseband you are on? (Under About Phone -> Baseband Version) Over here we have i9103NEKI1
The only special thing we did I can think of is flashing a modem file (when we were still on the unofficial cm10.1 without these kind of problems, but massive battery drain), because there was a call problem going on for customers of the austrian provider 3 and CM10.1.
I could analyse the problem a bit more today: It seems as soon as the phone gets busy (for example from the browser loading pages or in DippN's case processing a game), the touch screen gets unresponsive and everything starts to lag and delay or freezes completely until it shuts down the phone. Could be either CPU or RAM related, I guess. I just wonder what caused this, even if the nightly had a faulty kernel, this should be fixed as soon as we flash another ROM, right?
I will be able to try a different ROM on monday. It would be great, if you could report, if the downgrade to GB helped the issue. I'd like to try a different baseband, if you are on the same right now too.
Greetings and thank you so much for trying to help us, vikesh!
paKS7 said:
I'm able to also confirm, that Procedure II didn't help the problem. I really doubt it is a hardware fault, because of us two having the exact same problem after flashing the same rom.
@Dippn: Do you know which nightly build you used? In my case it was the nightly build "20130405". Also could you check which baseband you are on? (Under About Phone -> Baseband Version) Over here we have i9103NEKI1
The only special thing we did I can think of is flashing a modem file (when we were still on the unofficial cm10.1 without these kind of problems, but massive battery drain), because there was a call problem going on for customers of the austrian provider 3 and CM10.1.
I could analyse the problem a bit more today: It seems as soon as the phone gets busy (for example from the browser loading pages or in DippN's case processing a game), the touch screen gets unresponsive and everything starts to lag and delay or freezes completely until it shuts down the phone. Could be either CPU or RAM related, I guess. I just wonder what caused this, even if the nightly had a faulty kernel, this should be fixed as soon as we flash another ROM, right?
I will be able to try a different ROM on monday. It would be great, if you could report, if the downgrade to GB helped the issue. I'd like to try a different baseband, if you are on the same right now too.
Greetings and thank you so much for trying to help us, vikesh!
Click to expand...
Click to collapse
Well, we are not on the same baseband. I'm on I9103XXLQ3.
About the cm verison im not quiet sure, the latest i flashed was "20130406" but since the problem were there the time before that when i flashed cm I cant answer exacly but i have a cm version "20130305" on my desktop and it could be that one that I used.
I never used cm before it was on nightlies so the modem file flashing i dont know anything about.
The thing you mention about that it shuts of when the phone gets busy and touchscreen gets unresponsive I can kind of confirm too.
I will flash GB now, will report back in an hour how it went.
kataria.vikesh said:
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
Are you sure i should do it using v1.87?
I'm having problems finding it and v1.85 seems to be in everyones links.
DippN said:
Are you sure i should do it using v1.87?
I'm having problems finding it and v1.85 seems to be in everyones links.
Click to expand...
Click to collapse
Flashed GB using v1.85 and now I am stuck in bootloop, after 10 sec at the samsung logo it restarts and repeat. >.>
When the phone restarted after the flash and after it says "-updating application" it says:
Installing Multi-CSC
Can't access to '/system/csc/NEE/system/'.
Successfully applied multi-CSC.
I have no idea what this means but could it mean anything?
EDIT: I got it to start by wipe cache and data. (thought i should do that when cwm was installed)
Unfortunately already in the startup options when u write wifi password the touchscreen became very unresponsive and when i after a few min had succeded writing the password the phone shut of when it tried to connect to it! :,(
I can also confirm that it still thinks it is charing when it is not becuase the symbol in the statusbar flicked from battery to charging symbol.
Is there anything else softwarerelated that I can do?
DippN said:
Flashed GB using v1.85 and now I am stuck in bootloop, after 10 sec at the samsung logo it restarts and repeat. >.>
When the phone restarted after the flash and after it says "-updating application" it says:
Installing Multi-CSC
Can't access to '/system/csc/NEE/system/'.
Successfully applied multi-CSC.
I have no idea what this means but could it mean anything?
EDIT: I got it to start by wipe cache and data. (thought i should do that when cwm was installed)
Unfortunately already in the startup options when u write wifi password the touchscreen became very unresponsive and when i after a few min had succeded writing the password the phone shut of when it tried to connect to it! :,(
I can also confirm that it still thinks it is charing when it is not becuase the symbol in the statusbar flicked from battery to charging symbol.
Is there anything else softwarerelated that I can do?
Click to expand...
Click to collapse
Wipe data again.. If possible after wiping data Just reflash the GB.
Hi everyone, I hope someone can help me on that one.
In the last 3-4 weeks, I've seen my Nexus 5 rebooting here and there randomly. He's not stock into a boot loop, he works just fine and then 'pop', I can see it rebooting without reasons.
I'm running stock 5.1.1, kernel 3.4.0-gbebb36b, Build number LMY48B. The phone is rooted manually, no automatic trick.
Does randomly reboots means something? Is there a way to see what happens/what happened like an event viewer in Windows?
Thanks a lot.
You can use 'adb logcat' to see system logs.
a hammerhead wrote this.
pplante19 said:
Hi everyone, I hope someone can help me on that one.
In the last 3-4 weeks, I've seen my Nexus 5 rebooting here and there randomly. He's not stock into a boot loop, he works just fine and then 'pop', I can see it rebooting without reasons.
I'm running stock 5.1.1, kernel 3.4.0-gbebb36b, Build number LMY48B. The phone is rooted manually, no automatic trick.
Does randomly reboots means something? Is there a way to see what happens/what happened like an event viewer in Windows?
Thanks a lot.
Click to expand...
Click to collapse
It will die soon.
Sent from my SM-G920T
ambervals6 said:
It will die soon.
Sent from my SM-G920T
Click to expand...
Click to collapse
Is that a known behaviour to a knwon issue or you're just saying this like that?
pplante19 said:
Is that a known behaviour to a knwon issue or you're just saying this like that?
Click to expand...
Click to collapse
Happened the same to my old nexus 5 before it got stuck in bootloop and I needed a new motherboard.
Sent from my SM-G920T
ambervals6 said:
Happened the same to my old nexus 5 before it got stuck in bootloop and I needed a new motherboard.
Sent from my SM-G920T
Click to expand...
Click to collapse
Ok, thanks for telling me. I'm not yet stuck in a bootloop yet, but I hope it will be ok until the Nexus 5 2015 gets released.
Power button could be playing up. Have you tried completely wiping it clean, fresh install it from Google files and don't root and test it for a week or two in case it's just a software bug somewhere
Sent from my Nexus 5 using Tapatalk
For me it was the power button. But, I could see the power menu appearing sometimes before it powered off. If this is the case, bang the power button to a table side, it actually works Seriously, it does.
Here are others who fixed it by banging it to a table: https://www.reddit.com/r/Nexus5/comments/2rpfuj/nexus_5_broken_power_button_keeps_rebooting/