My Zte axon 7 for last few days has been mostly stuck on a red led for until the battery dies then I plug it in and it boots normal and functions good for 20 mins until it freezes with a red led and I have to do it all over again. I was in TWRP running linage os and it still froze in TWRP which I was suprised. Has anyone else had this issue because I'm not finding much on the internet for it.
sonic1337 said:
My Zte axon 7 for last few days has been mostly stuck on a red led for until the battery dies then I plug it in and it boots normal and functions good for 20 mins until it freezes with a red led and I have to do it all over again. I was in TWRP running linage os and it still froze in TWRP which I was suprised. Has anyone else had this issue because I'm not finding much on the internet for it.
Click to expand...
Click to collapse
yes,me.Also on 10% phone shut down,then i try to turn it on and it says i need to charge my battery,i ignore it.Then i try to boot in TWRP and that works.
Also vendor partition issues,other time on boot its gone,other time in reboot its back
calibration issues also here that i noticed,what more users have but not aware about
Have you found a work around for this to prevent it from happening or to make it work longer. I do not know what causes it. I hesitate to format cause I got some pictures. But I will if it comes to it.
sonic1337 said:
Have you found a work around for this to prevent it from happening or to make it work longer. I do not know what causes it. I hesitate to format cause I got some pictures. But I will if it comes to it.
Click to expand...
Click to collapse
Try to flash latest official twrp trough fastboot or edl.If it worked boot in twrp and try to backup your photos to PC/laptop.
Then I advice you start over.Also delete the vendor partitions.
Please report back here when the twrp flash and backup to pc succeeded
Predatorhaze said:
Try to flash latest official twrp trough fastboot or edl.If it worked boot in twrp and try to backup your photos to PC/laptop.
Then I advice you start over.Also delete the vendor partitions.
Please report back here when the twrp flash and backup to pc succeeded
Click to expand...
Click to collapse
I will try doing this, unfortantly luck isn't on my side for this. In short I did this process 1 year ago forgetting how to do it, as well as I am now on windows 8.1 (previous Wind 7) and the drivers are very hard to get working as when the phone previously worked it would be hard to get it to detect the phpne using Usb 2.0. Just send me a tut on how to flash Lastest version of TWRP and ill do it. Also how do I clear the Vendor partions? I mainly had the intention to set this phpne up once and never come back to all this so thats why I have nothing ready for this.
Also what if it freezes while i'm usimg TWRP? I had that happen to me before
Predatorhaze said:
Try to flash latest official twrp trough fastboot or edl.If it worked boot in twrp and try to backup your photos to PC/laptop.
Then I advice you start over.Also delete the vendor partitions.
Please report back here when the twrp flash and backup to pc succeeded
Click to expand...
Click to collapse
Is this the method you used to fix it?
sonic1337 said:
Is this the method you used to fix it?
Click to expand...
Click to collapse
yes,and then reverted back to los 14.
I have same problems now again,with the rebooting,power loss,fake 0 battery capacity.
i dont know what the cause is,but for me it happen only with vendor partition installed with los15 bootstack etc
im trying to fix it again
Predatorhaze said:
yes,and then reverted back to los 14.
I have same problems now again,with the rebooting,power loss,fake 0 battery capacity.
i dont know what the cause is,but for me it happen only with vendor partition installed with los15 bootstack etc
im trying to fix it again
Click to expand...
Click to collapse
Ok what i'm going to do is erase the entire device, flash TWRP then the default Rom and see if it still happens.
sonic1337 said:
Ok what i'm going to do is erase the entire device, flash TWRP then the default Rom and see if it still happens.
Click to expand...
Click to collapse
u mean stock rom? what i did was ersing everything,also the vendor partition.I rebooted sometimes in twrp to make sure everything is gone and all partitions are on default size.And im glad i did this because the vendor partition showed up again after some reboot in twrp.
Then i installed everything for los14.1 (bootstack and modem) and flashed nuclearom (all default).Ive run some cycles on that and my problems were all solved.Battery calibration was also normal and good
Same issue, more details, with year old B32 system
Just want to add, having same issue. When phone is unplugged, battery starts draining quickly, in fifteen minutes reaching 70%. IF it reaches that far. Usually, battery just jumps from any % to 0! and shuts off, even from 100% charge sometimes, and can't restart phone until I plug it in. When plugged in, it shows wherever it shut down, for example if it shut down at 76% on charging it shows 76%.
Looking at posts above, I wiped everything, including data and media, did a complete reflash to B32 stock image by DrakenFX that I did literally a year ago. STILL same issue remains, battery starts discharging very quickly, then from 95% skips to 0! and shuts off.
Hope this is helpful to anyone dealing with this issue.
vereshchagin said:
Just want to add, having same issue. When phone is unplugged, battery starts draining quickly, in fifteen minutes reaching 70%. IF it reaches that far. Usually, battery just jumps from any % to 0! and shuts off, even from 100% charge sometimes, and can't restart phone until I plug it in. When plugged in, it shows wherever it shut down, for example if it shut down at 76% on charging it shows 76%.
Looking at posts above, I wiped everything, including data and media, did a complete reflash to B32 stock image by DrakenFX that I did literally a year ago. STILL same issue remains, battery starts discharging very quickly, then from 95% skips to 0! and shuts off.
Hope this is helpful to anyone dealing with this issue.
Click to expand...
Click to collapse
that must be your battery. Install Ampere, and disconnect the phone while it is at 100%. See how much voltage it reports. If it says it's at ~95% and has less than 4.3V then it's definitely just a very bad battery with high internal resistance, this causes it to drop voltage easily once a load is applied, and the phone detects the low voltage and shuts off to prevent bad stuff from happening
Does the phone look like it's warped somewhere? Your battery might be bloating
Related
Hi,
I have a SMN910F rooted on stock kitkat downloaded from sammobiles, also having TWRP and a few xposed modules. A couple of weeks back after my phone's battery died, I couldn't get it past the samsung logo when trying to reboot after connecting the charger. I suspected a s/w malfunctioning and performed a clean flash, rooted again and installed TWRP. It has been working fine since then until the battery ran empty again this morning. The same problem seems to occur again now. On a normal reboot it works just fine.
I have tried removing sd card and trying, restarting through TWRP and connecting to PC for the restart and none of these helped. I bought the phone from UK and have now moved to India so am not sure if I can claim warranty even if I managed to reset the Knox counter to 0.
I came across a similar thread for i9300 where the asker says he had an empty /efs folder. Is that likely to cause this problem and how can I check the /efs on my system now without factory reset. I'm having to reconfigure the phone with every factory reset and is tiresome. Also if /efs was the problem should the clean flash last time not have fixed it?
Thanks in advance,
Vish
Vishwa308 said:
Hi,
I have a SMN910F rooted on stock kitkat downloaded from sammobiles, also having TWRP and a few xposed modules. A couple of weeks back after my phone's battery died, I couldn't get it past the samsung logo when trying to reboot after connecting the charger. I suspected a s/w malfunctioning and performed a clean flash, rooted again and installed TWRP. It has been working fine since then until the battery ran empty again this morning. The same problem seems to occur again now. On a normal reboot it works just fine.
I have tried removing sd card and trying, restarting through TWRP and connecting to PC for the restart and none of these helped. I bought the phone from UK and have now moved to India so am not sure if I can claim warranty even if I managed to reset the Knox counter to 0.
I came across a similar thread for i9300 where the asker says he had an empty /efs folder. Is that likely to cause this problem and how can I check the /efs on my system now without factory reset. I'm having to reconfigure the phone with every factory reset and is tiresome. Also if /efs was the problem should the clean flash last time not have fixed it?
Thanks in advance,
Vish
Click to expand...
Click to collapse
Go to download mode by pressing and holding volume down+home+power, then try flashing the stock firmware again, or if you want boot to recovery first and wipe cache and dalvik and try to boot it again, if not go back to step 1, cheers:fingers-crossed:
Thanks for your reply. I have done it and it's now back to working condition.
But worried that this is continuing to happen every time my battery drains out.:silly:
Vishwa308 said:
Thanks for your reply. I have done it and it's now back to working condition.
But worried that this is continuing to happen every time my battery drains out.:silly:
Click to expand...
Click to collapse
Good to hear mate, you should try calibrating your battery also, use your phone until it reaches 15%, then charge it to 100%, reboot into recovery wipe caches, boot it again, and let it on the charger 20-30 min after its fully charge, and repeat step 1, keep doing this as much as you can, your battery will calibrate and it will improve in longevity, cheers:fingers-crossed::highfive:
Thanks mate. Will do that!!
Sent from my SM-N910F using XDA Free mobile app
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??
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
raz_il_dio said:
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
Click to expand...
Click to collapse
This advice doesn't work with my phone even with holding the buttons for 30 secs and more. For rebooting I can only wait until the battery is completely drained. With little hope for another way shortening time to the next reboot any help is appreciated.
Same here...experiencing the same prob...
Same problem.
Sent from my Redmi Note 4 using Tapatalk
smallcapsicum said:
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Click to expand...
Click to collapse
Sounds like you need your motherboard replaced i had the same issues on marshmallow thought the nougat update would fix it but realized it was a hardware fault not software..left it in store to get fixed and on repair sheet it said faulty motherboard..
Sent from my SM-G935F using XDA-Developers Legacy app
As i know some S7 have motherboard hardware problem, mine has too, what help? warranty and they replaced motherboard. But if you root, you can say good bye to warranty, they look at knox first with this problem.
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...
The title says it all. I was having issues with errors and apps not responding or force closing, So I thought in would wipe the cache and Dalvik cache in TWRP, just in case there was something corrupted. Upon reboot, my battery life stayed at 65% when full charged, but would eventually charge to 100% when it was being used while charging. Now the batter dies in a very short amount of time! It happened, like that! No slow degradation, just boom! And it was done. Anyone have any ideas, or seen something similar with their Tab A 10.1?
ShadNuke said:
The title says it all. I was having issues with errors and apps not responding or force closing, So I thought in would wipe the cache and Dalvik cache in TWRP, just in case there was something corrupted. Upon reboot, my battery life stayed at 65% when full charged, but would eventually charge to 100% when it was being used while charging. Now the batter dies in a very short amount of time! It happened, like that! No slow degradation, just boom! And it was done. Anyone have any ideas, or seen something similar with their Tab A 10.1?
Click to expand...
Click to collapse
I always wipe cache/dalvik when dirty flashing my rom updates and never had that problem.
I'm guessing you have a bad battery, otherwise it wouldn't have behaved as you described. If you're lucky it's just a glitch - try a few charge cycles :fingers-crossed:
ShadNuke said:
The title says it all. I was having issues with errors and apps not responding or force closing, So I thought in would wipe the cache and Dalvik cache in TWRP, just in case there was something corrupted. Upon reboot, my battery life stayed at 65% when full charged, but would eventually charge to 100% when it was being used while charging. Now the batter dies in a very short amount of time! It happened, like that! No slow degradation, just boom! And it was done. Anyone have any ideas, or seen something similar with their Tab A 10.1?
Click to expand...
Click to collapse
It could be that something other than cache is corrupted. I'd try a factory reset after making sure OEM is enable in dev mode. In my experience, batteries don't go bad all of a sudden. Or, better yet, restore from TWRP backup. You do have a backup, don't you?
lewmur said:
It could be that something other than cache is corrupted. I'd try a factory reset after making sure OEM is enable in dev mode. In my experience, batteries don't go bad all of a sudden. Or, better yet, restore from TWRP backup. You do have a backup, don't you?
Click to expand...
Click to collapse
Never had a back up. All I did was root the tablet when root was first achieved a couple years ago. Should I try a system reset through TWRP or through the tablet itself? I ran it through the system, and lost root, and supposedly shouldn't have. Would I just be better off loading a new ROM through TWRP off the SD card? I'm sure I could find a stock OEM ROM on here somewhere, now at least. When I rooted the tablet, there was no aftermarket anything... Just the ability to root the device.
ShadNuke said:
Never had a back up. All I did was root the tablet when root was first achieved a couple years ago. Should I try a system reset through TWRP or through the tablet itself? I ran it through the system, and lost root, and supposedly shouldn't have. Would I just be better off loading a new ROM through TWRP off the SD card? I'm sure I could find a stock OEM ROM on here somewhere, now at least. When I rooted the tablet, there was no aftermarket anything... Just the ability to root the device.
Click to expand...
Click to collapse
Rule of thumb, flash stock ROMs via odin and custom ROMs via TWRP. My choice would be a custom ROM and then BACKUP!!!:laugh:
edit: If you rooted the device a long time ago, that means you haven't been getting any updates. You may well be clear back on Android 6 while the latest custom ROMs are 10 and the latest stock is 8.1. You can get the latest stock with Frija, which is a free download.
I'll have to take a look on my SD card, I recall using Titanium backup, so I'll have to check. Do you have any recommendations? Warranty is gone, so I'll likely install a new ROM, I usually do once it's up anyway
I only browse Reddit, Facebook, a couple other social media apps and I'll play the odd game.