Related
TL;DR: I have flashed the stock 4.2.1 image through fastboot, and yet my n7 wifi still reboots continuously at the google screen with the little unlocked lock.
Background: I have had the device for about 3 months, no real problems with it before this. I was reading yesterday night and i fell asleep, and thus instead of being on my desk all night the device was under a blanket. When i woke up, I opened the cover and found it on the google screen with the lock. It was warm, but not incredibly so. I thought it was weird that it had rebooted and apparently frozen, but i held down the power to turn it off. when i turned it back on, it started the google screen, then went black, then started the google screen again. Seems like there may be some sort of a kernel issue that is keeping it from booting. The next thing i did was to go into recovery (had CWM at this point, and it was rooted as well but that's a moot point if i can't get into the system.) and i did a backup, then wiped data and did a restore from the backup that i had just made. after rebooting, it made it all the way into the system, and seemed ok. I set it down, and a few moments later it turned off and started doing the loopy google screen thing again. Next, I went into recovery and wiped data/factory reset, and tried to boot up. no luck, still looping. Next, i grabbed the 4.0 toolkit from the dev section and tried to flash the stock recovery from that, but it was proving troublesome so i just downloaded the image myself and fastbooted then replaced cwm with the stock recovery, wiped everything, and flashed the 4.2.1 image. that should have worked, from what i understand, but no, still being loopy. I re-wiped and flashed, tried 4.1.2 instead, that didn't work, and i re-did 4.2.1. after flashing 4.2.1 and then leaving it boot looping for a little while, i noticed that it sometimes made it into the boot animation and then the animation froze and it rebooted and looped more. after a few more tries, powering it off, leaving it for a few min, and powering it on again, it booted all the way to the welcome screen to pick a language and then froze. some number of loops later, it made it all the way to picking a wifi network and froze. I have yet to make it past that point. Thinking it may help, i fastbooted CWM onto the device, so i have a more capable recovery now. I am now going to look into pushing a non stock rom to the device to see if that will help at all.
Any ideas on what on earth could have caused this? Was it just that the device was a little warmer than usual for a while?
Any ideas on how i can fix this? Much appreciated!
Lastly, should i consider looking at sending it back to google? I didn't think there was anything wrong with the hardware, but i'm not sure.
Thanks!
Update: After leaving the system repeating it's loopy boot thing for about 45 min, it seems to have finally booted into the system, and has yet to reboot again. I have no idea why this happened in the first case, nor why this finally worked in the end, but so far it seems ok.
More: Ok, so it still seems to be looping a lot. I have no idea why still. I'm having trouble getting it to boot back into the system, so hopefully something helps fix this.
Ok, so a day later it seems to have settled down such that there's very little looping on the google logo screen any more; now it just tends to randomly reboot when in use. this is quite frustrating, but seems more similar to what others have reported to be the case with 4.2.1. oddly, i never had these reboot issues before it decided to fail the first time, so i'm not sure if this is just because ii'm on 4.2.1. I may look at flashing back to 4.1.2 and staying there, i suppose it can't hurt. does anyone else have any ideas as to what could be going on?
So i rebooted my phone today, because screen didn't shut of when in call, but after reboot, phone is stuck at 4 color dots. I tried all bunch of stuff, but to summarize, i did wipe everything with fastboot and flashed stock 4.4.2 and 4.4.0 with fastboot/toolkit/flash-all.bat....and while every flash seems to finish ok, i still can't boot device (i waited 30 minutes on 4 color dots)
Any idea what the problem could be?
tnx
teva said:
So i rebooted my phone today, because screen didn't shut of when in call, but after reboot, phone is stuck at 4 color dots. I tried all bunch of stuff, but to summarize, i did wipe everything with fastboot and flashed stock 4.4.2 and 4.4.0 with fastboot/toolkit/flash-all.bat....and while every flash seems to finish ok, i still can't boot device (i waited 30 minutes on 4 color dots)
Any idea what the problem could be?
tnx
Click to expand...
Click to collapse
When you said you wiped everything, did that include the system partition as well?
Sent from my Nexus 7 (2013)
Yes...everything cleared, with toolkit and manually with fastboot.
Funny thing...i just tried flashing stock 4.2.2 and everything went ok. Phone booted to OS and after some poking around i did OTA to 4.3. Now, i'm stuck again at X boot screen. I read some users have this problem, but i just don't understand why this happens on "empty/cleared" phone.
Try to mess arround with some app that changes screen values, like brightness, saturation, etc. Fauxclock has this feature and supports presets, such as Franco.kernel app.
I know one member that could run 4.2.2 but nothing higher because his imei was blank. Does your phone have a valid imei #?
teva said:
Yes...everything cleared, with toolkit and manually with fastboot.
Funny thing...i just tried flashing stock 4.2.2 and everything went ok. Phone booted to OS and after some poking around i did OTA to 4.3. Now, i'm stuck again at X boot screen. I read some users have this problem, but i just don't understand why this happens on "empty/cleared" phone.
Click to expand...
Click to collapse
Sounds a lot like the same problem I'm having here...
http://forum.xda-developers.com/showthread.php?t=2590357
teva said:
So i rebooted my phone today, because screen didn't shut of when in call, but after reboot, phone is stuck at 4 color dots. I tried all bunch of stuff, but to summarize, i did wipe everything with fastboot and flashed stock 4.4.2 and 4.4.0 with fastboot/toolkit/flash-all.bat....and while every flash seems to finish ok, i still can't boot device (i waited 30 minutes on 4 color dots)
Any idea what the problem could be?
tnx
Click to expand...
Click to collapse
When I flashed 4.3, I couldn't get past the "X" boot screen. I wiped cache using recovery, it worked for me.
Try this guide
http://forum.xda-developers.com/showthread.php?t=2010312
On my i747 I installed Omni ROM 4.4.3-20140620-d2lte-HOMEMADE. After install and reboot I noticed the load time was in excess of five minutes from the moment the Omni logo splash appears. Is this normal? I can't be sure but I think each boot takes longer, (so tired right now). Any suggestions?
I am experiencing the same. I flashed to my SPH-l710 using the latest from http://forum.xda-developers.com/showthread.php?t=2591298.
I would love to go back to using this rom. I absolutely love it miles above CM but the boot time is easily in excess of 10 minutes.
exarkun631 said:
On my i747 I installed Omni ROM 4.4.3-20140620-d2lte-HOMEMADE. After install and reboot I noticed the load time was in excess of five minutes from the moment the Omni logo splash appears. Is this normal? I can't be sure but I think each boot takes longer, (so tired right now). Any suggestions?
Click to expand...
Click to collapse
Talk to whomever provided the build, as that is not an officially supported device (in addition to not being present at dl.omnirom.org - the HOMEMADE part of the filename is a dead giveaway).
First bootup after installation is always long - if subsequent boots are long there's a problem though.
It is normal if it is your first boot after flashing new rom...
It just that the Android is installing (preparing apps for first use)
The same will happen when you clear Dalvik cache or change runtime from Dalvik to ART.
If it is the same on second and other boot then it is problem with your rom
Dodgy apps (or heaps of apps) can cause that too. Is it still slow if you do a factory reset ? (do a backup before hand so you can restore all your data). As pointed out above if you do a factory reset the initial boot will still be slow
Thanks everyone. I went ahead and wiped the drive then installed CM11 for the i747 (d2att) and all is well with booting. One day I will check out omnirom again because the features are just insane!
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.
I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.
But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).
But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.
Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?
Please, Thanks
EDIT
Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
Sounds to me like there''s something physically wrong with the phone, probably the battery. Time for a new one anyway. Lithium batteries degrade with use. After ~500 charge cycles it'll have lost upwards of 20% of its original capacity and might show other signs of wearing out like inconsistent voltages. After 2 years of use, you'll be well beyond 500 cycles. A new battery off eBay is pretty cheap, and some sellers include the needed tools.Go to ifixit.com for a tear-down guide. A hair drier can help soften up the adhesive. The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.
If it's not the battery giving you woes, I don't know what it could be.
And FYI, the whole "optimizing app" thing is the OS rebuilding the cache. When you flash your GAPPs package or a zipped Titanium backup it has to build the cache for the new apps. Same as when you do the "wipe Dalvik and cache" part of standard flashing procedure to avoid conflicts. In order for apps to load quickly, Android stores a lot of the necessary data in cache, so when you clear it or have new apps, it has to rebuild the cache. On Lollipop this takes a loooooooong time because of the way ART works.
Planterz said:
The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.
If it's not the battery giving you woes, I don't know what it could be.
Click to expand...
Click to collapse
How can i be completely sure that it's the battery which needs to be replaced? The battery shows charge. When i plug in and boot up it shows enough battery power left.
Currently, without external power it does not go past the google screen on boot. When i plug in power while device is off, the battery meter shows just a little depletion from full charge. When turned on, battery level is 82 %
After all , all this hardware mess up can be the consequence of a bad cm flash ?
the whole "optimizing app" thing is the OS rebuilding the cache.
Click to expand...
Click to collapse
I know this. Earlier it was happening on each boot. Now it seemed to be stopped.
By any chance did you have your phone charging while flashing and booting up your ROM?
ChainFires Son said:
By any chance did you have your phone charging while flashing and booting up your ROM?
Click to expand...
Click to collapse
May be? But not the the first time
Nezam said:
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.
I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.
But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).
But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.
Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?
Please, Thanks
EDIT
Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
Click to expand...
Click to collapse
Exactly same problem is started with my Nexus 4 ... I really wonder, what is causing this. Meanwhile, have it sorted for you ? is that hardware (Battery) issue?
Nezam said:
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself...
Click to expand...
Click to collapse
I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.
Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.
Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.
Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.
This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
shazR00t said:
I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.
Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.
Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.
Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.
This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
Click to expand...
Click to collapse
Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
I also got the same problem. I thought this is battery problem, so I replaced the battery but problem still there. I thought this is problem of lollipop, never installed CM or anything. It is always running stock android. After that I even downgrade to Kitkat stock version still it is not working. One more thing I noticed is If I don't unlock the device than it will be powered on, but as soon as I unlock it and if it is not plugged in to charger it will be switched off. Any suggestion what should I do?
I have the same thing for several month now.
Always thought it is the dying battery.
theminikiller said:
Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
Click to expand...
Click to collapse
Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems
Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
shazR00t said:
Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems
Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
Click to expand...
Click to collapse
When you flashed the factory image did you do it via fastboot or by flashing a zip file. If you used the zip file I would suggest you do it with fastboot.
theminikiller said:
When you flashed the factory image did you do it via fastboot or by flashing a zip file. If you used the zip file I would suggest you do it with fastboot.
Click to expand...
Click to collapse
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Yeah, I meant flashing each of the image files. If you did that then u don't have any other suggestions.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 20:42 ---------- Previous post was at 20:41 ----------
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Yeah, I meant flashing each of the images. If you did that then I don't have any other suggestions.
Sent from my Nexus 4 using Tapatalk
I m too facing the similar issues. Phone is getting turned off suddenly when not charging, on charging it is working fine. i have done factory reset and also done factory image reset to 5.1.0. i m still facing the same issues. I don't think so it is related to battery. if anyone have the solution then please let me know.
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Try the very basic flash technique by double clicking the flash-all.bat. It's not the same as flashing the imgs one by one.
Battery is the issue. Get it changed. I also faced same problem, and visited LG service center and they changed the battery. Phone working fine now.
gautam.is.sharma said:
Battery is the issue. Get it changed. I also faced same problem, and visited LG service center and they changed the battery. Phone working fine now.
Click to expand...
Click to collapse
Ok so Battery was the problem!! Got it changed, phone working fine now. Thanx all!
Ok guys i confirm that this is a battery issue. I took it to the service center and the guy temporarily replaced battery to show me issue solved... But... there i saw another issue due to which i did not buy the battery. I saw half the touchscreen not working (including the navigation buttons ). The guy at the center told its a h/w issue and i would have to spend 7K on it so i left my phone dead for now. The Question is ... can this be a s/w issue.. or result of bad flash which can solve on reflashing ??
same problem with my nexus ,but one thing i noticed that the phone does not power off while in recovery...Any idea??
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