I've seen a couple of threads that explain how I ended up where I am I think, but nothing so far on how to get out of it. So, any advice?
I updated to the 209 nightly the usual way (emmc install via clockwork recovery after wiping cache and dalvik) and it booted, started loading my home screen and clock widget, and then crashed completely and rebooted. Repeatedly.
I tried fixing permissions. I tried downgrading my version to 207, I tried upgrading to 210 and later 211. It either freezes or reboots.
After reading that the latest version of superuser needed to be installed before updating nightlies to avoid this type of problem and that it tied into overclocking, I was able to get into my nook by quickly going to the overclock settings and taking my max cpu down to 600 before it had a chance to lock and reboot. Yay right?
But the second I reboot, I have the same problem unless I race to undo the overclock again. Anything I can do to fix this? Or am I screwed and need to find an old backup or start from scratch again?
Verizon G2 - stock rom, rooted and had OTA updates blocked for at least 5 months.. 4.2.2 ver 11a build JDQ39B
restarted phone the other day and it would boot and you would briefly see your home screen and then boot loop to the white verizon logo screen. Every other time it looped, it would not show the home screen, just a blank screen. I did get it to boot to safe mode and unistalled a few apps I thought might be problems,,, didn't help. I discovered that if I quickly tapped the home screen in that brief 2 seconds during the loop, it would boot.
I really hate to undo tether, un-root and factory reset. I hate to go through updates and re-root and hack tether but I will as last resort.
Any thoughts on cause or suggestions?
Thanx
check lgocat for logs and try to eliminate the cause that way.
check kmesh in logs, dunno exact wording, but it also says something about boot there.
Use a tool like android tuner or something similar to disable startup stuff and try to eliminate that way
Weird G2 bootloop - got a fix?
Thanks for suggestions, I will give them a try.
Weird G2 bootloop - got a fix?
bachera said:
check lgocat for logs and try to eliminate the cause that way.
check kmesh in logs, dunno exact wording, but it also says something about boot there.
Use a tool like android tuner or something similar to disable startup stuff and try to eliminate that way
Click to expand...
Click to collapse
I didn't find any lgocat or kmesh folders/files anywhere
still stumped
r9ball said:
I didn't find any lgocat or kmesh folders/files anywhere
still stumped
Click to expand...
Click to collapse
try any logging tool from playstore. also try searching on how to obtain those logs. probably requires root. mind warrantee ofcourse.
at which point I would do a total complete clean install. that eliminates software issues. still there and you did not restore anything/install anything then its hardware.
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
Hey I'm getting some unusual battery drain all of a sudden. Yesterday I had pretty intense use and lost 50% over 6 hours or so. Today I've had much less use and lost 40% in 2 hours.
Also this morning, I got the notification that 34.3.A.0.206 is available. Is it possibly that notification, or maybe something else causing the issue. I haven't installed anything new, but I did update apps in the play store. The battery usage says it's the Android System doing it though.
Did some digging, and it looks like pm-service and logd are running crazy, burning battery and CPU cycles. I'm having trouble finding out what pm-service is, but it may be power management or peripheral management. I can't find settings for logd levels, and I haven't checked my log at yet to see what it's writing.
dmesg shows countless entries of
IPC_RTR: msm_ipc_router_bind: pm-service Do not have permissions
But I can't figure out how to fix it or what it is. Any ideas?
it your phone getting hot?
some services my glitch and get stuck on ram and drain battery
install a ram and cache cleaner app and restart your phone multiple times, i hope you will fix it
Kianush said:
it your phone getting hot?
some services my glitch and get stuck on ram and drain battery
install a ram and cache cleaner app and restart your phone multiple times, i hope you will fix it
Click to expand...
Click to collapse
It is, and I think it's because pm-service was stuck in an error loop, and logd was tracking it, between the two using 40-50% of my CPU non-stop. I'm fiddling with restoring old system backups to see if I can fix it. It may be related to a botched magisk 12->13.1 upgrade, or a failed OTA update.
voilsb said:
It is, and I think it's because pm-service was stuck in an error loop, and logd was tracking it, between the two using 40-50% of my CPU non-stop. I'm fiddling with restoring old system backups to see if I can fix it. It may be related to a botched magisk 12->13.1 upgrade, or a failed OTA update.
Click to expand...
Click to collapse
yeah it might be
also most of the times a corrupt media file makes media storage getting stuck and phone getting hot...so you might wanna check that before restoring everything
I think it's related to this (https://forum.xda-developers.com/oneplus-3/help/ob-9-qmifw-log-spam-t3521248) because it happened after I restored a backup in twrp. I'm currently dirty flashing my firmware in flashtool
Dirty flash seems to have fixed it. Perhaps the problem is in how TWRP does backup restores.
voilsb said:
Dirty flash seems to have fixed it. Perhaps the problem is in how TWRP does backup restores.
Click to expand...
Click to collapse
I'm not allowed to give anymore 'thanks' today, so I will do it manually! Thanks for sharing this help, I noticed this problem too, but had no idea how to fix
qvmuhuuxz said:
I'm not allowed to give anymore 'thanks' today, so I will do it manually! Thanks for sharing this help, I noticed this problem too, but had no idea how to fix
Click to expand...
Click to collapse
That's exactly why I was walk thru my steps, even if I'm not getting replies. Just in case someone else has the same problems.
BTW, my logcat showed the same error spamming as that thread, which led me to try that fix.
E/QMI_FW (634): xport_reg Failed for service_id=0x35 version=0x1001 on 10
Sent from my SM-T700 using Tapatalk
voilsb said:
That's exactly why I was walk thru my steps, even if I'm not getting replies. Just in case someone else has the same problems.
BTW, my logcat showed the same error spamming as that thread, which led me to try that fix.
E/QMI_FW (634): xport_reg Failed for service_id=0x35 version=0x1001 on 10
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
Now that we have a TWRP that supports nougat's decryption, I can encrypt.
But can we still dirtyflash if we are encrypted?
I see this, so I think it's possible - https://www.reddit.com/r/Nexus5/comments/2zdtqo/dirty_flashing_with_encryption/
"Disable screenlock. Set it to none. Device will still be encrypted, just the password will be set to default which enables the dirty flash to work. When everything is updated. Set a screenlock password again."