Related
Hi, first of all, my setup is Franco's kernel r53 and stock ROM.
So, uhm, I was using my phone normally, without problems, then I turned the phone off and wanted to turn back on, but the screen was just black. When I connect it to PC, it shows the battery charging logo. I can access Bootloader and recovery.
I did Nandroid backup when before flashing Faux's kernel (before Franco's).
Should I flash stock kernel, or what? Please help, thanks.
Restore your backup
Thanks for you super-fast reply!
Did it and it's working again.
One more question though, what could have caused it? The only different thing I did than usual, is that I set my Max CPU Frequency to 1088MHz.
So i have been using Android L pv-79 Developer preview since it first came out flashing updates and kernels without an issue. Today i flashed a newer kernel by defconoi switched on intelli thermal and uv by 75, everything was running normal for hours. I take my phone out of my pocket and its on the google boot logo. Tried booting into recovery but it still stuck on the google boot logo. So i fast booted cam recovery nothing happened then i fast booted the 4.4.4 stock image successfully and I'm still stuck.. some assistance on this matter would be really helpful. Need to fix this before work.
Thanks
Edit: Fastbooted 4.2.2 and still the same issue.
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
I spent two days faffing with putting files into the dload folder and flashing before ota options appeared, and now I'm on 585. I've found the battery life to be pretty poor compared to 193 which is where I was before, and I've messed around with all the battery life increasing options.. Really not fussed with what version I'm on as long as I get a good battery life - used to get up to two days - now, after coming off the charger at 6 am, I'm lucky if it's got power left at 10 pm! Any thoughts as to which 636 rom might be best for battery life?
Thanks!
I'm using b585 as well and the battery life is really the worst among all the roms so far. The best battery life I think is still b211 but that would mean change back to marshmallow.
plain_white said:
I'm using b585 as well and the battery life is really the worst among all the roms so far. The best battery life I think is still b211 but that would mean change back to marshmallow.
Click to expand...
Click to collapse
I can live with that!
Now trying to downgrade using the info and file found on here: http://consumer.huawei.com/sg/support/mobile-phones/mate8-sg-sup.htm
I have put the rollback update.app file in and flashed it from powered off, leaving my phone now saying it is on NXT-L29C636B500 as expected, but then when copying over and trying to flash NXT-L29C636B211 - or any other emui 4 rom - the update fails and the build number now shows as NXT-L29C900B500. I wonder if there is there a stable rollback rom from B585?
EDIT: I'm currently installing B330 - so it seems you can't just flash any old thing.. maybe I can go back to 211 from this?
EDIT: BALLS. Seems that downgrading to B330 ends up with an eRecovery screen where it tries to download a new recovery.. hmm - what to do next.
EDIT: Factory reset and back on B330! Now trying the rollback from there to 211
EDIT: Oh. I think that kills it. Now not booting at all and none of the button combinations do anything.. Don't use the rollback when you are on B330 guys
There is a glimmer of hope..
I had a very similar problem... It seems that Rollback patch only works if you install it from Nougat...
If you try to install from any other version, It'll brick your phone.
So, once you install a downgraded version, you cannot downgrade it more.. until you reach Nougat again.
I bricked my phone, and I tried a lot of things to unbrick it, flashed many roms (FYI: I even not had the bootloader unlocked, on fastboot FRP locked and Phone Locked).
And the unique thing that worked for me is there:
https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
When you unbrick your phone with the "Factory Firmware", I recommend you to flash using the B330 build.
I made my account just for helping you.
Don Kronos said:
I had a very similar problem... It seems that Rollback patch only works if you install it from Nougat...
If you try to install from any other version, It'll brick your phone.
So, once you install a downgraded version, you cannot downgrade it more.. until you reach Nougat again.
I bricked my phone, and I tried a lot of things to unbrick it, flashed many roms (FYI: I even not had the bootloader unlocked, on fastboot FRP locked and Phone Locked).
And the unique thing that worked for me is there:
https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
When you unbrick your phone with the "Factory Firmware", I recommend you to flash using the B330 build.
I made my account just for helping you.
Click to expand...
Click to collapse
Wow. Thanks! I'll try this tomorrow when I have all the tools on my work pc!
Don Kronos said:
I had a very similar problem... It seems that Rollback patch only works if you install it from Nougat...
If you try to install from any other version, It'll brick your phone.
So, once you install a downgraded version, you cannot downgrade it more.. until you reach Nougat again.
I bricked my phone, and I tried a lot of things to unbrick it, flashed many roms (FYI: I even not had the bootloader unlocked, on fastboot FRP locked and Phone Locked).
And the unique thing that worked for me is there:
https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
When you unbrick your phone with the "Factory Firmware", I recommend you to flash using the B330 build.
I made my account just for helping you.
Click to expand...
Click to collapse
After first trying several other things like the Knife tool, or just flashing over extracted Nougat images, I used the DC Phoenix tool v39 using B585.
It failed.
Then I tried it using B330.
That failed too...
Then I tried v35 using B330. It mostly worked, and I started getting excited.. but on rebooting, it tried and failed to download the eRecovery.
At that point I then put in the SD card with B330 in the dload folder, held in all the buttons and the updater appeared.
It seemed to get stuck at 5% but carried on,
It seemed to get stuck at 19%.. but carried on,
It got all the way to 99%..
And failed.
But then it rebooted - the animated logo popped up and it booted through into B330!!! :laugh: Thank you so much!!
Phew. Now not really wanting to go through all that again, but at the same time not wanting to be on EMUI 4.1 or 5 for the sake of a better battery life!
Post #3 in https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775 indicates that the NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_A ndroid_6.0_EMUI_4.0_DC_UNL.dgtks linked to the post will set the phone back to an android 4.3 base? Would it be possible do we think, to flash that through DC, and then be able to put an EMUI 4 rom like B211 on it?
Or should I do the sensible thing and leave it well alone now!
Bearded_1 said:
Phew. Now not really wanting to go through all that again, but at the same time not wanting to be on EMUI 4.1 or 5 for the sake of a better battery life!
Post #3 in https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775 indicates that the NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_A ndroid_6.0_EMUI_4.0_DC_UNL.dgtks linked to the post will set the phone back to an android 4.3 base? Would it be possible do we think, to flash that through DC, and then be able to put an EMUI 4 rom like B211 on it?
Or should I do the sensible thing and leave it well alone now!
Click to expand...
Click to collapse
You're supposed to do it first, with DC phoenix install first the NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_A ndroid_6.0_EMUI_4.0_DC_UNL.dgtks, it will rebuild all partitions and basic configurations that were lost and tried to recover flashing with other stock roms, and finally unbrick the phone..
And you start with android 4.3, but it is apparently of internal use by Huawei technicians. It has apps for testing many things like sound, processor, memory, storage, display, etc. And after that, you can now flash any stock rom without any problems...
FOR THE RECORD, my phone is almost 2 years old and since the upgrades of EMUI 4.1, it had a very high battery consumption. When I upgraded to EMUI 5, the thing was worse, in 5 or 6 hours of inactivity, the battery drained from 100% to 0%. As the problems started after the updates, I did not think it was related to a hardware problem.
But now that I unbricked my phone, and installed EMUI 4.1; my phone lasted only 4 hours ... from 100% to 70% in four hours and the battery was sometimes drained from 70% to 0% in seconds. So, I replaced the battery, when I opened the phone I realized that the battery was badly damaged. Now my phone (in EMUI 4.1 B330) lasts two days of inactivity and up to six hours of screen, like when I bought it.
Don Kronos said:
You're supposed to do it first, with DC phoenix install first the NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_A ndroid_6.0_EMUI_4.0_DC_UNL.dgtks, it will rebuild all partitions and basic configurations that were lost and tried to recover flashing with other stock roms, and finally unbrick the phone..
And you start with android 4.3, but it is apparently of internal use by Huawei technicians. It has apps for testing many things like sound, processor, memory, storage, display, etc. And after that, you can now flash any stock rom without any problems...
FOR THE RECORD, my phone is almost 2 years old and since the upgrades of EMUI 4.1, it had a very high battery consumption. When I upgraded to EMUI 5, the thing was worse, in 5 or 6 hours of inactivity, the battery drained from 100% to 0%. As the problems started after the updates, I did not think it was related to a hardware problem.
But now that I unbricked my phone, and installed EMUI 4.1; my phone lasted only 4 hours ... from 100% to 70% in four hours and the battery was sometimes drained from 70% to 0% in seconds. So, I replaced the battery, when I opened the phone I realized that the battery was badly damaged. Now my phone (in EMUI 4.1 B330) lasts two days of inactivity and up to six hours of screen, like when I bought it.
Click to expand...
Click to collapse
Huh. I've only had mine since Christmas - still, something to consider for the future. I have all the tools if it comes to that. Thanks for the advice!
Hello again
I was just looking around and came across this poster.
They claim to that B585 could give really good battery life.
This is person only loses about 20% battery in over two hours of heavy usage. @•XPLOITZ•
What's interesting is that unlike some other nougat users, he doesn't have test keys present anyway in the about phone menu.
https://forum.xda-developers.com/showpost.php?p=72852397&postcount=2402
Hello guys
I was on b14 custom stock rom,i had no problems at all.
Upgraded to dotos oreo with the required bootstack and modem and stuff with oki twrp labs.
But my battery acts weird after that.When it reach 35% it can drop to 27% in 20 seconds and than stay on 27% for like 5 or 10 minutes,then it drops from 26% to 19% in 10 or 20 seconds,and again it stays at 19% for a couple of minutes.Then when i shut down my phone and try to turn it on,it says i need to charge my device and it turns off again.Then i try to boot in twrp,and that succees,when in twrp it shows battery 0% but the phone keep remaining on.
Also when i put on charger,it charge that same amount of lost,like 10%,in 10 seconds.
But when ther is no OS installed(all partitions wiped) and i boot in twrp,adn put it on charger...it charges fine,no big gapps.
When there is a OS installed and it drops less than 30%,this acting happens again
I did calibrations,clean flashes,all i could.
Note that this happend when i switched to dotos,so it cant be bad battery,because 10 minutes earlier everything was fine.
Can the problem be on EFS,Persist Partition? if yes,how can i solve this? Can the problem be in the sys folder? I do think some of these 3 has to do with it
I think it got vendor/system problems.Sometimes it also dont boot the system,or random bootloops
I did full EDL flash ( G oreo b02),booted and set up.
Now i flashed twrp treble nfound,wiped all partitions,and did edl vendor flash.I booted twrp and it tells my data is encrypted,i went to wipe,selected data partition...and it says the partition is emmc,also the same on system partition...how is this possible? Ofcourse i know how to get back to ext4,but i want to know why now it says emmc.Also before i booted because of vendor flash,battery was 22%.When i did the flash and booted in twrp the battry was 26%.
Definattely ( lol bad english in text) something wrong here,instead of the easy claims they say the battery is bad
I have had the same problem. Performed EDL Nougat B12 stock via EDL. Now no more isssues with battery. I am on 2017G.
doesnt work for me,this acting only happens when a rom(OS) is installed.
With all partitions wiped,i can charge fine in twrp.
My battery was on 100%,i did full wipe,rebooted in twrp (stil 100%) and flashed dotos+gapps+kernel.After the flashing battery sit on 96%.
Not good,something wrong
Now it drained from 30% to 18% in 1 minute,and now its stuck on 18% for 10minutes+ or longer.
If I put on charger now,it charge the same amount I lost in that minute , in like 2minutes or less
Don't know what is going on here
@Predatorhaze: Are you absolutely sure that your battery isn't going bad? I ran the same setup as you for a few days, I got none of the behavior you've described. It's normal for TWRP to sometimes show 50%, just ignore it. I've seen this in every TWRP build I've tried on my A7, regardless of installed ROM, bootstack, etc.
If you go back to stock does this behavior stop?
Another thing, I ditched DotOS because it can only be rooted with Magisk, and I have an intense dislike of Magisk. And I have an A2017U, whereas you have a G. Not sure how much difference that would make.
AnonVendetta said:
@Predatorhaze: Are you absolutely sure that your battery isn't going bad? I ran the same setup as you for a few days, I got none of the behavior you've described. It's normal for TWRP to sometimes show 50%, just ignore it. I've seen this in every TWRP build I've tried on my A7, regardless of installed ROM, bootstack, etc.
If you go back to stock does this behavior stop?
Another thing, I ditched DotOS because it can only be rooted with Magisk, and I have an intense dislike of Magisk. And I have an A2017U, whereas you have a G. Not sure how much difference that would make.
Click to expand...
Click to collapse
that 50% is just a bug.everyone got this.
And this happened when i switch to dotos.1 hour before that everything was fine.
So you believe a battery can be broken due the flashing? it happened on los uni bootstack oki twrp dotos and swifty kernel.
now my phone connected to pc on usb,phone is turned on,stays on and battery says 0% hahaha ,this is getting funny
what does this do? Button to disable the eMMC write protection (disemmcwp)
i have read this somewehre :
Now I'm not saying that's what's happening, but I noticed these phones get really hot flashing deodexed roms. And just wondering if this could be a possibility, that the emmc chips are getting hot and breaking solder points.
My battery can act weird when i use intense gpu resources (heavy videogame)
@Predatorhaze: No, I don't think flashing will break a battery. What I was trying to say is that your battery might have been slowly going bad even before you flashed DotOS. Batteries generally don't fail overnight, it takes time. Unfortunately I have no way for you to test further so you will have to look into this on your own. How old is the phone? The longer you have had it, the more likely that the battery needs to be replaced.
AnonVendetta said:
@Predatorhaze: No, I don't think flashing will break a battery. What I was trying to say is that your battery might have been slowly going bad even before you flashed DotOS. Batteries generally don't fail overnight, it takes time. Unfortunately I have no way for you to test further so you will have to look into this on your own. How old is the phone? The longer you have had it, the more likely that the battery needs to be replaced.
Click to expand...
Click to collapse
Phone 1 year old.My battery wasn't going bad,it happen direct when I flashed dotos.(botstack+patch splash screen)
I'm on los14 and it looks like the problem is gone.Or not,at least it got a little better
I think its related to vendor,cus i have many times issues with vendor partition for example in deleting and creating.Once, i deleted the vendor partition,rebooted twrp and the vendor was gone.I installed other twrp,boot it,and the vendor was back/still ther.
Also when all partitions are wiped,it charge normal...all ok
In accub,it's still 2800mah...but sometimes it show 3600mah.How more cycles i charge,how higher the estimated mah goes up
By the way,i NEVER charge at night ( while sleep),also never drop it less than 10%
Somethign screwd up my battery,maybe some solder point on motherboard
Where is this folder for? vendor/lib64/.... ( note that i have not a vendor partition active) can i delete it?
@Predatorhaze: I would suggest clean flashing the earliest stock Nougat EDL you can find for A2017G (B19 for A2017U, but that wont work for you). Then unlock bootloader again (if necessary), reinstall TWRP, and try your tests again. I have often found that flashing a stock EDL fixes many issues I previously encountered. I prefer Nougat because it is more stable (for me) than Oreo/Pie. B32 is the baseline EDL package that I use.
Try to avoid flashing other bootstacks/modems unless you absolutely have to (like LOS bootstack). B32 bootstack boots all AOSP/LOS Nougat ROMs, and can also boot any Oreo ROM as long as it isnt based on Treble and doesnt have a vendor partition. Of course with N bootstack there will be issues with dual SIM and camera 2 API/HDR, but I dont use those, so no issues there. And B32 bootstack doesnt have the system partition read-only issue. All stock bootstacks based on B35 and higher seem to have this last issue, LOS bootstacks dont but then there is no EDL with the hardware buttons.
And before I forget, dont try to use @Oki's custom TWRP with an N bootstack, it probably wont work (didnt for me when I tried it once). Stick to official TWRP, or @NFound's TWRP 3.2.1-7.
AnonVendetta said:
@Predatorhaze: I would suggest clean flashing the earliest stock Nougat EDL you can find for A2017G (B19 for A2017U, but that wont work for you). Then unlock bootloader again (if necessary), reinstall TWRP, and try your tests again. I have often found that flashing a stock EDL fixes many issues I previously encountered. I prefer Nougat because it is more stable (for me) than Oreo/Pie. B32 is the baseline EDL package that I use.
Try to avoid flashing other bootstacks/modems unless you absolutely have to (like LOS bootstack). B32 bootstack boots all AOSP/LOS Nougat ROMs, and can also boot any Oreo ROM as long as it isnt based on Treble and doesnt have a vendor partition. Of course with N bootstack there will be issues with dual SIM and camera 2 API/HDR, but I dont use those, so no issues there. And B32 bootstack doesnt have the system partition read-only issue. All stock bootstacks based on B35 and higher seem to have this last issue, LOS bootstacks dont but then there is no EDL with the hardware buttons.
And before I forget, dont try to use @Oki's custom TWRP with an N bootstack, it probably wont work (didnt for me when I tried it once). Stick to official TWRP, or @NFound's TWRP 3.2.1-7.
Click to expand...
Click to collapse
I'm on nuclearom,problem look gone.4 hours sot,could be 6 probably.Also didn't notice any weird drain.Thanks.
I think it was due vendor partition issues,or the vendor has a bug.
I can remember it took months they find out the headphone jack CPU bug,after many complains..so I would not look weird if they find a bug in vendor...