Related
FIX AVAILABLE!!
I bought my TF about 15 days ago, rooted it and installed CWM recovery, and it was running just great. Then, the ICS update came along and i just waited for the CWM package to update mine. No problems in the update process, but the random reboots started happening, so i thought the problem was that i updated without wiping, so i did this. No dice, still getting (not so) random reboots. So, i thought maybe it was the CWM package. I downgraded to HC via NVFlash, then let it update via FOTA. Even then, the random reboots persisted. Then, i noticed the tablet never rebooted while in use, but only while in deep sleep state. The "No Sleep" widget is the current workaround, but then, you risk getting a SOD.
So, from what i could gather until now, the following things are NOT the cause for the RRs:
1. Updating without wiping.
2. Updating via CWM.
3. Rooting.
Well, i got really sick of this problem, so it's time to do something about it. I am trying to gather as much info as possible to try and narrow down the possible cause for the random reboots, so i need everyone that is facing the same issue to give me the following info:
1. Serial number of your Transformer
2. Firmware region (TW, US or WW)
3. Logcat before the reboot
For number 3, you need to open Terminal Emulator, and do this:
# su -
# logcat > /sdcard/logcat.txt
Then you just turn off the screen and let your tablet go to deep sleep. After it reboots, post here the info above and attach logcat.txt.
Please, only use this thread to post the info i asked. Thanks!
Update: Some users contacted ASUS and it seems they are aware of the problem. A fix is supposed to released soon, in the form of another OTA update.
Update2: Very good knews for rooted users. The test13 version of guevor's kernel is able to let the TF deep sleep and not reboot. Link to his thread:
http://forum.xda-developers.com/showthread.php?t=1565519
THANK YOU, GUEVOR!
Good idea. Mine just randomly shuts down during sleep, as opposed to rebooting. Shall I contribute too?
Have you tried a factory reset?
Balor said:
Good idea. Mine just randomly shuts down during sleep, as opposed to rebooting. Shall I contribute too?
Click to expand...
Click to collapse
Yes, please.
Sent from my Transformer TF101 using XDA Premium HD app
Can´t give you a logcat yet but here's my TF101 info:
FOTA to ICS 2 days ago and started random reboot's... Not Rooted (never has), no service/app/etc.. killer, but i did disable all of ASUS crapware on the Apps manager.
I was able to caught one of the reboots (it's freeze on the ASUS logo) and when i hard reboot it, during boot sequence appear some message saying that was finalizing update (this was after the FOTA and after other 2 random reboots. I did reboot the device after the update at least twice before experiencing the 1st Random Reboot).
info:
S/N: B90KAS146231
WW (Build Number IML74K.WW_epad-9.2.1.11-20120221)
Kernel: 2.6.39.4-00002-g2977a0d » [email protected]#1
as soon i have the Log i will post.
Hope this help somehow
baseballfanz said:
Have you tried a factory reset?
Click to expand...
Click to collapse
Every kind of update method that you can think of was tried. In that case, yes, it was wiped. Several times, in fact.
Please, post just what i asked. I want this info to investigate the issue. Post on another thread if you want to share theories or something else.
Sent from my Transformer TF101 using XDA Premium HD app
Mine was never rooted, 100% stock, took the ICS OTA on Friday moring, ran great all day, I woke up Saturday morning (I had docked it and put the doc on the charger friday night when I went to bed) and it was stuck in a boot loop. Now I'm looking at how to NVFLASH it back to honey comb to recover it, might as well root it now.
Les
still waiting to freeze or reboot ... for now 493K of logcat
Sent from my Transformer TF101 using Tapatalk
This is going to be a problem in the kernel like it has been on previous releases. When kernel source is released then the kernel devs will fix it and then asus will fix it. My SODs are caused by a kernel panic so until we get an updated kernel we need to get asus to release source.
I am mostly a longtime lurker/user of XDA but I thought I should contribute to this thread.
Bone Stock 16g TF101-A1, Refurb purchased last week from online vendor. Still getting used to the tablet format but I also purchased a TF101 Dock.
I noticed yesterday that I had a couple of random re-boots. Didn't know if it was related to an update or why this particular tablet was "refurbished." About 7 hours ago, this morning, I got multiple re-boots. Splash screen then power off and on again. I saw at least 15 re-boots before I started looking around for solutions. I tried the stock rom (downloaded from Asus) and re-boot to recovery w/o any success. Re-booted and wiped (hard reset) multiple times as well.
Still no complete boot but I had two separate and distinct paths that displayed:
1. it would boot with an android bot asking for a password and the keyboard displayed
2. It would cold boot into the "Start" screen like a normal set up.
I did manage to get the recovery started only to reach the bot with the exclamation point and no further progress at recovery.
In either case, typing a password of any kind did nothing, and hitting start and beginning the set up process did nothing but continue the re-boots/splash screen/power up/power down.
Finally connected to my laptop and it succeed in a complete boot and I was able to set up and connect to my wireless. It did not re-boot for several moments and I was able to observe the "About" page from the settings. I was still running
HTK75.US_epad-8.6.5.21-20111216
I also noticed that it was actively downloading a "firmware update" I went through several more re-boots until it finished the download and then I installed the firmware w/o any further trouble. In watching the download, I noticed re-boots at 31%, 32%, 41% "download completion", and one or two more before it fully downloaded. Of course, it did re-boot upon completion of the upgrade.
I am now running Android version: 4.0.3 Build number: IML74K.US_epad-9.2.1.11-20110221
Everything has been stable for an hour or so of moderate use including installation of multiple apps.
FWIW, I think that the reason my problem started is that I had my WiFi set to turn off when screen is off. I believe my incomplete download started the re-boots and my settings "may" have contributed to the incomplete downloads that started the rest of my issues.
Thanks to all of the "regulars" around here that are busy helping us customize our devices. This may not be my first post, but I think I have less than 5 posts right now. Hope this helps in discovering the causes of the re-boots.
ICS OTA on Saturday, 2 reboots already, stock rom, 100% original, Italy. Should i contact Asus?
msaraiva said:
I bought my TF about 15 days ago, rooted it and installed CWM recovery, and it was running just great. Then, the ICS update came along and i just waited for the CWM package to update mine. No problems in the update process, but the random reboots started happening, so i thought the problem was that i update without wiping, so i did this. No dice, still getting (not so) random reboots. So, i thought maybe it was the CWM package. I downgraded to HC via NVFlash, then let it update via FOTA. Even then, the random reboots persisted. Then, i noticed the tablet never rebooted while in use, but only while in deep sleep state. The "No Sleep" widget is the current workaround, but then, you risk getting a SOD.
So, from what i could gather until now, the following things are NOT the cause for the RRs:
1. Updating without wiping.
2. Updating via CWM.
3. Rooting.
Well, i got really sick of this problem, so it's time to do something about it. I am trying to gather as much info as possible to try and narrow down the possible cause for the random reboots, so i need everyone that is facing the same issue to give me the following info:
1. Serial number of your Transformer
2. Firmware region (TW, US or WW)
3. Logcat before the reboot
For number 3, you need to open Terminal Emulator, and do this:
# su -
# logcat > /sdcard/logcat.txt
Then you just turn off the screen and let your tablet go to deep sleep. After it reboots, post here the info above and attach logcat.txt.
Please, only use this thread to post the info i asked. Thanks!
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
So... if you do the ful update via CWM there are no problems?
Sent from my Transformer TF101 using Tapatalk
Just Once
I have experienced a single random reboot since applying the OTA ICS upgrade to my US B70 TF101.
That was then...
Now the tablet is virtually unuseable. Not only are there random reboots, but lags and freezes ad nauseum. I am NOT a happy camper
I don't believe this has been mentioned before.
I just saw my device go into random reboot in sleep. However, this time the device completed the boot up sequence instead of getting stuck on the Asus loading screen...
All I did different was changing WIFI sleep policy from "never" to "on during sleep", which I don't think is the cause of the change.. I guess it all depends on luck weather the device gets stuck or complete the boot up sequence.
So perhaps the problem is caused by a combination of a bug in the deep sleep state and the CPU governor?... This is purely my speculation.
jparity said:
I don't believe this has been mentioned before.
I just saw my device go into random reboot in sleep. However, this time the device completed the boot up sequence instead of getting stuck on the Asus loading screen...
All I did different was changing WIFI sleep policy from "never" to "on during sleep", which I don't think is the cause of the change.. I guess it all depends on luck weather the device gets stuck or complete the boot up sequence.
So perhaps the problem is caused by a combination of a bug in the deep sleep state and the CPU governor?... This is purely my speculation.
Click to expand...
Click to collapse
My device never gets stuck in the ASUS logo, it always completes the boot process, and the wifi policy is the default one, so i don't think it's related to it. But it's probably something to do with the kernel and deep sleep state. Even with the wifi policy set to never turn off, the device enters DS.
Sent from my GT-I9100 using XDA App
reboot cant have anything to do with the apps (like google earth) as those will simply FC on fault and are not capable of taking system down. this must be a kernel or driver issue.
transformer prime got ota update recently that was supposed to fix reboots and it contained new wifi driver. so possibly this is something to do with wifi.
my wifi sleep policy setting is to be always on when on power and sleep when screen is off on battery.
never had a reboot when plugged in, had a few always on battery power - so it might be related to wifi beign powered on in sleep to do periodical email check. just a guess.
I am running stock unrooted atm. I reverted back from rooted to stock before the ota update.
I generally get one random reboot each day. They happen when my transformer is in sleep mode always. It'll be st next to me asleep and then I notice the screen turn on and it is rebooting. My "Keep Wi-Fi on during sleep" is set to "Always".
I removed root as I wanted to see what stock performance was like. Apart from these reboots I'm totally happy.
2.6.39.4 and WW_9.2.1.11
Not sure how much help that'll be to others, but there you go.
I had these random reboots aswell on my device but since yesterday morning it stopped.
- Removed SetCPU
- Forced 2D rendering to the GPU.
Still testing it but so far no reboots
Stock ICS + Root
Getting the same exact thing, froze during boot up one time.
Running S/N BBO
Tossed a ticket into Asus letting them know, hopefully I get a response back soon.
I had random reboots the first day after updating,
but have set
1. the wifi to be off when the screen is turned off (in wifi settings), and
2. have turned off the location service that uses your wifi to aid positioning (in location settings).
and this seems to have stopped the reboots.
Hope this helps someone.
I am facing so many frequent reboots from past few hours. I have not made any changes to rom or kernel. Till yesterday everything was fine.
sangalaviral said:
I am facing so many frequent reboots from past few hours. I have not made any changes to rom or kernel. Till yesterday everything was fine.
Click to expand...
Click to collapse
it might be caused by an app, boot into safe mode and see if persist.
it could be battery issue, try with another.
Hi!
Rom: CM12 20150320
Recovery: CWM 6051 touch
Bootloader: MAKOZ30f (if that helps)
About a week ago i unlocked and flashed my nexus 4 to CM12. After that the phone has worked well until today. The phone was acting a bit laggy, so I thought a reboot would be nice. However, after the reboot it only gets past the first google screen. After that it gets stuck in a weird animation (see picture) I have never seen before for about 5 minutes, and after that the screen just shows a black image (completely black but you can see the screen is still on). This repeats when I retry. I can still enter bootloader and recovery.
Any idea why this happened? And how to fix? I guess a reset (or reflash?) could solve it, but it would be nice if that was not necessary. =)
I made two observations during the day, related?
-some app prompted for some CM12 updates, but I had no time to deal with them at the time so I just closed the app.
-while playing music from spotify while working, the sound lagged for a second at a time, about one time per hour.
Thanks in advance! Let me know if there are details missing!
albinhj said:
Hi!
Rom: CM12 20150320
Recovery: CWM 6051 touch
Bootloader: MAKOZ30f (if that helps)
About a week ago i unlocked and flashed my nexus 4 to CM12. After that the phone has worked well until today. The phone was acting a bit laggy, so I thought a reboot would be nice. However, after the reboot it only gets past the first google screen. After that it gets stuck in a weird animation (see picture) I have never seen before for about 5 minutes, and after that the screen just shows a black image (completely black but you can see the screen is still on). This repeats when I retry. I can still enter bootloader and recovery.
Any idea why this happened? And how to fix? I guess a reset (or reflash?) could solve it, but it would be nice if that was not necessary. =)
I made two observations during the day, related?
-some app prompted for some CM12 updates, but I had no time to deal with them at the time so I just closed the app.
-while playing music from spotify while working, the sound lagged for a second at a time, about one time per hour.
Thanks in advance! Let me know if there are details missing!
Click to expand...
Click to collapse
Flash stock image from google... maybe some stuff from CM12 go wrong...
Not use CWM recovery...better TWRP...this is updated.
After upgrading to Andriod N on the 6p, many of us have been plagued by the Bootloop of Death and/or random reboots. Some have tried RMAs, have purchased new devices or moved to backup devices. Huawei has claimed software is the culprit and Google has stated that it's the hardware. Personally I've tried a clean install of the ROM, Dirty flashing the ROM, clearing the caches, etc.
Nothing has worked... Until now!
I'm days in without a single random reboot or Bootloop.
This advice is provided without warranty or any guarantee that it'll work for you but it may work.
I'm not a developer and I've not tried multiple devices.
Steps:
*Note I'm on the latest Pure Nexus build.
1. If you're currently stuck in a Bootloop, then leave your 6p to Bootloop until it actually starts or until the battery dies. If it starts skip to step 3.
2. If it Bootloops, then intervene occasionally by getting the device to boot into the bootloader (Hold down power and volume down). Once there, attempt to reboot recovery. It'll probably keep Bootlooping but occasionally the device will start up.
3. Once your 6p starts, download the ElementalX apk from the Google Play Store. Don't do anything else. I've only tried this app so it's the only one that I recommend for this "fix".
4. Download the ElementalX kernel through the ElementalX app and follow the prompts in order to install the kernel. Allow it to reboot. *You may be able to complete the following steps with the stock kernel.
5. Once your device has rebooted, open the ElementalX app and click the leaf icon in order to enable power saving. This will lower your CPU's freq, GPU's freq, and most importantly, it will disable the BIG CPU cluster.
After these steps were completed I haven't experienced any random rebooting or Bootloops. Yes, this ”fix" hobbles your device but it is still quite functional. I think that on Nougat the constant switching between the two processor clusters causes random restarts and Bootlooping.
There may be an alternative that will allow you to disable the little CPU cluster instead and not lower the GPU performance. I've not tried any other methods yet.
Specs added thanks to @510jungleboy
Nexus 6p 128 GB
ROM: Pure Nexus 7.1.2 r6
Kernel: ElementalX
Bootloader: Unlocked
Recovery: TWRP
Warranty: Expired
Please comment with results.
Multiple people have reported getting the boot loop of death while on Marshmallow. I think the idea that Nougat is causing the problem was discredited long ago, the fact that its a hardware issue with these phones is widely accepted and that the age of the phone is much more of a factor than the operating system you are running. Most of these phones are experiencing the boot loop of death shortly after the warranty expires, when the phone is 12-14 months old. Your phone is generating less heat since you ramped down the CPU which is likely why it isn't currently bootlooping.
Well...
jhs39 said:
Multiple people have reported getting the boot loop of death while on Marshmallow. I think the idea that Nougat is causing the problem was discredited long ago, the fact that its a hardware issue with these phones is widely accepted and that the age of the phone is much more of a factor than the operating system you are running. Most of these phones are experiencing the boot loop of death shortly after the warranty expires, when the phone is 12-14 months old. Your phone is generating less heat since you ramped down the CPU which is likely why it isn't currently bootlooping.
Click to expand...
Click to collapse
You may be right but I didn't notice any Bootloops or random reboots until I upgraded to Nougat. After putting this "fix" in place my device still gets pretty warm under load but it doesn't exhibit random reboots or Bootloops... Heat didn't seem to be the issue since my phone would reboot into a Bootloop while just sitting on my desk at work with only background tasks running. Regardless, this workaround works for me and it may work for others.
Mine just reboots over and over, for days and days, my bootloader is locked and usb debugging is off.
HOW would one install APk from playstore if their phone can't even load up, aka bootloop of death ? You need to be more specific , like locked bootloader , unlock bootloader ..etc.... smh
Once battery dies what i have to do? (my phone dies two hours ago when I was with a 3% of charge and its bootlooping over and over) Full charge? Another thing?
Note:
1)I'm on the latest Pure Nexus build, stock kernel, unlocked bootloader
2)When i connect to the charger one hour ago the phone shows battery charge mode but stills bootlooping. I'm waiting to battery dies
jhs39 said:
Multiple people have reported getting the boot loop of death while on Marshmallow. I think the idea that Nougat is causing the problem was discredited long ago, the fact that its a hardware issue with these phones is widely accepted and that the age of the phone is much more of a factor than the operating system you are running. Most of these phones are experiencing the boot loop of death shortly after the warranty expires, when the phone is 12-14 months old. Your phone is generating less heat since you ramped down the CPU which is likely why it isn't currently bootlooping.
Click to expand...
Click to collapse
510jungleboy said:
HOW would one install APk from playstore if their phone can't even load up, aka bootloop of death ? You need to be more specific , like locked bootloader , unlock bootloader ..etc.... smh
Click to expand...
Click to collapse
Sorry that I wasn't more specific. My bootloader is unlocked and I'm rooted. Users may not need to be in order to get back the device's functionality.
It's a shot in the dark but if a user that is having the Bootlooping issue follows my steps, then they may get back up and running. I've yet to have another random reboot or a Bootloop since...
RyomaEchizen said:
Once battery dies what i have to do? (my phone dies two hours ago when I was with a 3% of charge and its bootlooping over and over) Full charge? Another thing?
Note:
1)I'm on the latest Pure Nexus build, stock kernel, unlocked bootloader
2)When i connect to the charger one hour ago the phone shows battery charge mode but stills bootlooping. I'm waiting to battery dies
Click to expand...
Click to collapse
Since it's died, you'll need to power it on once it's charged for a while. When you power on and it starts Bootlooping, boot into the bootloader and follow my steps. If it Bootloops continuously, boot into the bootloader again and try to get into recovery. It will probably continue to Bootloop. That's what happened to me. I'd come back to it from time to time, boot to the bootloader, prompt it boot to recovery... over and over again. Eventually, it would fully boot up instead (not into recovery).
If it starts DON'T check messages or try to use your phone normally. Instead, follow the steps. Seriously. I made that mistake over and over again.
FYI: This process can take a looong time. Not days but sometimes it was hours until I figured my solution out. I don't know exactly how long it takes because I'd leave the phone Bootlooping and come back to it later in the day.
Many thanks!
Its work for my nexus 6p too
My nexus work normal in interval 1-5% of charge. If charge increase 11% - bootloop...
After enable powersave elementalx, charging to 100% and work well
I have a smartphone. Automatically went into reboot, but did not boot. It constantly reboots. First, the test is reflected that I've been unlocked by the bootloader, and then the Google inscription, and after that the smartphone reloads again. The recovery menu does not enter.
Thanks! Finally something that worked! The big cluster is indeed the problem. I had the porblem that the phone freezes and gets stuck in the bootloop when the battery is above 10-12%. I guess that the cpu disables the big cluster when you are underneath that threshhold(?).
One big problem I am still facing is that I can't reboot my phone and I have to make it discharge until I can boot it up again. Do you have have something that prevents that?
Big thanks again!
Still bootloops
haieb said:
Thanks! Finally something that worked! The big cluster is indeed the problem. I had the porblem that the phone freezes and gets stuck in the bootloop when the battery is above 10-12%. I guess that the cpu disables the big cluster when you are underneath that threshhold(?).
One big problem I am still facing is that I can't reboot my phone and I have to make it discharge until I can boot it up again. Do you have have something that prevents that?
Big thanks again!
Click to expand...
Click to collapse
I followed all the steps but my Nexus 6P still bootloops after crossing 10% charging. Is it possible for you to share your Kernel Manager settings screenshots please?
I too began to experience the boot loop issue literally 8 days after my warranty expired which was 11 days ago today! Have tried flashing several factory images from MM to N and even a saved backup I made from day 1 of having the phone. This method of disabling the big cluster thru ExK has definitely been the furthest I have gotten. Me and my friend(da guy) did find out that in order for the phone to boot up at all, the battery has to be at approx. 6% or lower. In that time is when you must quickly download ExK and activate power saver mode. I just called Huawei support and they did absolutely nothing to help me in this manner. I really do hope that this lawsuit wins in our favor. Speaking of which, does anybody know where we can check for status of this current litigation?
Update: Ordered a new battery and installed it... still bootlooping. This is very frustrating as i have been forced to use my ancient Moto Droid X2 as my daily
I wonder if someone could compile a kernel that always disables the big cluster for those with bootloop problems. Then you could just flash the kernel and not have to try repeatedly to get the phone to boot long enough to install the app.
Sent from my Galaxy S8 using Tapatalk
inneyeseakay said:
I wonder if someone could compile a kernel that always disables the big cluster for those with bootloop problems. Then you could just flash the kernel and not have to try repeatedly to get the phone to boot long enough to install the app.
Sent from my Galaxy S8 using Tapatalk
Click to expand...
Click to collapse
is this possible?
headcreepz said:
is this possible?
Click to expand...
Click to collapse
I'll have to look into kernel building, but I'd imagine if you built a kernel that had powersaving as the default profile, it would work.
Got into recovery long enough to flash pure Nexus and root, but haven't been able to get it to boot yet.
Looking forward to one day being able to use it again. ?
Sent from my Galaxy S8 using Tapatalk
A little help!
nicotinic said:
After upgrading to Andriod N on the 6p, many of us have been plagued by the Bootloop of Death and/or random reboots. Some have tried RMAs, have purchased new devices or moved to backup devices. Huawei has claimed software is the culprit and Google has stated that it's the hardware. Personally I've tried a clean install of the ROM, Dirty flashing the ROM, clearing the caches, etc.
Nothing has worked... Until now!
I'm days in without a single random reboot or Bootloop.
This advice is provided without warranty or any guarantee that it'll work for you but it may work.
I'm not a developer and I've not tried multiple devices.
Steps:
*Note I'm on the latest Pure Nexus build.
1. If you're currently stuck in a Bootloop, then leave your 6p to Bootloop until it actually starts or until the battery dies. If it starts skip to step 3.
2. If it Bootloops, then intervene occasionally by getting the device to boot into the bootloader (Hold down power and volume down). Once there, attempt to reboot recovery. It'll probably keep Bootlooping but occasionally the device will start up.
3. Once your 6p starts, download the ElementalX apk from the Google Play Store. Don't do anything else. I've only tried this app so it's the only one that I recommend for this "fix".
4. Download the ElementalX kernel through the ElementalX app and follow the prompts in order to install the kernel. Allow it to reboot. *You may be able to complete the following steps with the stock kernel.
5. Once your device has rebooted, open the ElementalX app and click the leaf icon in order to enable power saving. This will lower your CPU's freq, GPU's freq, and most importantly, it will disable the BIG CPU cluster.
After these steps were completed I haven't experienced any random rebooting or Bootloops. Yes, this ”fix" hobbles your device but it is still quite functional. I think that on Nougat the constant switching between the two processor clusters causes random restarts and Bootlooping.
There may be an alternative that will allow you to disable the little CPU cluster instead and not lower the GPU performance. I've not tried any other methods yet.
Specs added thanks to @510jungleboy
Nexus 6p 128 GB
ROM: Pure Nexus 7.1.2 r6
Kernel: ElementalX
Bootloader: Unlocked
Recovery: TWRP
Warranty: Expired
Please comment with results.
Click to expand...
Click to collapse
I really want this to work. Can you please share your settings? I'm not getting passed 10-12% charge. It makes a loud noise and bootloop till around 6% but runs fine if it's below 10%. I can watch videos and listen to music
Same issue !
haieb said:
Thanks! Finally something that worked! The big cluster is indeed the problem. I had the porblem that the phone freezes and gets stuck in the bootloop when the battery is above 10-12%. I guess that the cpu disables the big cluster when you are underneath that threshhold(?).
One big problem I am still facing is that I can't reboot my phone and I have to make it discharge until I can boot it up again. Do you have have something that prevents that?
Big thanks again!
Click to expand...
Click to collapse
Did u ever figure it out? Also can u show me some screenshots of your settings?
Got mine up and running!! [emoji41]
Here are my settings:
Sent from my Galaxy S8 using Tapatalk
Hi all,
For the last 3/4 weeks my Moto X Style XT1572 has been randomly rebooting, usually this is when it is not in use and either in my pocket or desk.
I was running AICP and tried a couple of factory resets. This did not help.
I then factory reset and installed Dirty Unicorns (last weekly). Again this hasn't helped. No overclocking, undervolting, just stock kernels and I have tried handbag kernel.
Still rebooting.
Anything else I can try before throwing it in the bin?
Motorola are not interested in repairing due to unlocking the BL.
Thanks
rowlers said:
Hi all,
Anything else I can try before throwing it in the bin?
Motorola are not interested in repairing due to unlocking the BL.
Thanks
Click to expand...
Click to collapse
Flash the newest stock 6.0.1.
Without botloader, gpt, no oem commands(don't lock BL).
You need stock system to recognize: hardware or software problem.
I was going to say that my wife's MXPE has been doing the same thing with multiple random reboots and losing constantly losing all her Bluetooth pairings. But her phone is completely unrooted and OEM Marshmallow OS.
I seem to have resolved the issue by using the Chill governor. Fingers crossed, but I've not had a reboot for 2 days now...
radon222 said:
I was going to say that my wife's MXPE has been doing the same thing with multiple random reboots and losing constantly losing all her Bluetooth pairings. But her phone is completely unrooted and OEM Marshmallow OS.
Click to expand...
Click to collapse
Mine is doing the exact same: random reboots and it loses all Bluetooth pairings and have to redo them. Running TruePure ROM but nothing else so far.
I did a Dalvik/Cache wipe and it calmed down a bit now, it randomly reboots about 1-2 times a week (over it doing it 1-2 times a day) and when it does reboot, so far, it hasn't lost the Bluetooth pairings yet.
Gonna see if I can go back to stock and install the latest updates and then take it from there, when I get a chance to.
JustLok said:
Mine is doing the exact same: random reboots and it loses all Bluetooth pairings and have to redo them. Running TruePure ROM but nothing else so far.
I did a Dalvik/Cache wipe and it calmed down a bit now, it randomly reboots about 1-2 times a week (over it doing it 1-2 times a day) and when it does reboot, so far, it hasn't lost the Bluetooth pairings yet.
Gonna see if I can go back to stock and install the latest updates and then take it from there, when I get a chance to.
Click to expand...
Click to collapse
Moto X Style , Android 6.0 , Not rooted, pure stock, exact same symptoms as you guys with the random reboots while not in use , losing Bluetooth pairings... Did a factory reset, didn't change a thing. Sometimes, I can get 2 days without reboots, then have 2 in the same hour the next day. It sucks. I'm hoping the Nougat update will fix this, if it ever gets released for my version...
Got 1 doing the same stuff, all stock, gets warm, reboot itselfs, wrong date and time, and no bt pairing
Mine is still doing it too. Not as bad as it was but at least once per day, when idle, sleeping it just reboots for no apparent reason. Not ROM, Kernel and I have factory reset.