Related
I rooted my phone with z4 root. Got Koush's bootstrapper was granted superuser permissions created nandroid backup downloaded liberty 1.5 flashed it without any problems, used it decided I wanted to check out Rubix Focused 1.9 same procedure had no problems flashing it over with bootstrap recovery mode. Decided I wanted to try the Watermarkd theme for it downloaded it transfered to phone no problem followed step by step instructions for this theme and when the phone rebooted BAM stuck at splash screen ( battery is now at about 40% life)
Realized I was going to have to SBF Flash phone downloaded all required tools drivers, the_gift, RSD 4.9 Went to turn phone on it wouldnt turn on. Hook it up to the wall I get the splash screen nothing else. Tried using the home power button search button to factory reset. After doing so same thing even after wiped partition. I can get into the bootloader screen also but it says low batter cannot program. Is the only way to charge my battery enough to SBF Flash it is by using an external charger or cutting the usb and manually charging the battery through the computer? How can I access my nandroid backup? I know there is something that can be done Im just a little to new to know what that is Please Help
Any help is certainly appreciated!
I do believe that there is a way to charge your battery by cutting the USB cord and I'm going to get back to you on that but one thing you really want to watch out for is that from my experiences, the_gift is for system version 2.3.315 (aka bootloader version 30.03) and since you were running liberty 1.5 I'd assume you're on version 2.3.320/2.3.340 (aka bootloader version 30.04). If this is true and you try to flash it you will brick your phone. Make sure you check you're bootloader version and if it is the newer one look for happy_holidays_from_tbh or something similar. Just make sure its for the right bootloader version
He is correct, you need to pay attention to that.
But you could also just charge the battery in a buddys phone and try again. But if you are like me with no friends ( , lol) you could stop by a store somewhere and ask if they could charge your battery for you in a phone for a bit. Usually they are pretty cool about it. Then that way you can try reflash to stock.
If you still had access to CWM, I would have recommended wipe, wipe dalvik, and reflash of liberty. But that is a nogo at this point.
Thanks for the heads up about the SBF file. I will delete the gift since it never registered on my pc when I loaded up rsd 4.9. ( might be the reason why haha)
Charging the battery is where I am at right now, I need to either wait for the external charger i bought off ebay to come in or use my buddys phone. I feel I am going to want to make sure when I do the battery charged I have detailed instructions in order to FLASH my phone. Im hoping when the battery charges I will be okay but as I stated I am new to this rooting thing and am learning everything super fast. Any and all help is truely appreciated.
I flashed kholk's kernel to 2.3.4 HKTW (i know stupid) and i want to reflash the boot.img found in this thread http://forum.xda-developers.com/showthread.php?t=1138092 but when i plug my phone into charge, the charging symbol is a battery with a question mark on it...
any suggestions would be greatly appreciated
Have tried 1.8.3 full sbf flash?
Sent from my MB860 using XDA App
Werbs said:
I flashed kholk's kernel to 2.3.4 HKTW (i know stupid) and i want to reflash the boot.img found in this thread http://forum.xda-developers.com/showthread.php?t=1138092 but when i plug my phone into charge, the charging symbol is a battery with a question mark on it...
any suggestions would be greatly appreciated
Click to expand...
Click to collapse
I agree with trying a 4.1.83 sbf flash, and why in hell would you use that kernel when it's clearly not for 2.3.4?
The battery is too low for the phone to enter rsd protocol and plugging the phone in won't charge it
Werbs said:
The battery is too low for the phone to enter rsd protocol and plugging the phone in won't charge it
Click to expand...
Click to collapse
turn the phone off and then try charging
munchy_cool said:
turn the phone off and then try charging
Click to expand...
Click to collapse
From the wall outlet
It's been about an hour and a half with the phone charging from a wall socket and still noo chance of it booting. When I try entering fast boot it say "battery too low to flash"
well in that case you need to charge your battery on someone else's phone
i did the same thing
install the experimental full rom from http://forum.xda-developers.com/showthread.php?t=1142674 with cwm then charge it should work
troypage1994 said:
install the experimental full rom from http://forum.xda-developers.com/showthread.php?t=1142674 with cwm then charge it should work
Click to expand...
Click to collapse
How do you do that if you can't power the phone on?
not trying to be mean, but it specifically states it DOES NOT work with 183 or 234? why would u have even tried lol..... but yah, you might need to find someone with an atrix. have u tried plugging the phone ins and popping battery at same exact time, sometimes doing that puts in into charge mode while phone is off
Oh my, why do people install kernel's and ROMs without having experience and then panic when it doesn't work out. I agree with munchy_cool, charge it from another phone or buy another battery from the store to at least boot from. These are the risks you take when you run HIGHLY experimental builds.
Hopefully, you're able to get back up and running quickly. I would recommend going back to 1.8.3 and waiting for a stable CM7 ROM or similar before flashing more beta software. If all goes as expected, we might even see an official GB launch from Moto this month. Good luck.
Are you close to an AT&T store where they may let you charge your battery in a phone there?
There is also another option, not sure if anyone tried it on the Atrix, but I remember when Mr Patel from Engadget bricked his Motorola trying to flash a custom ROM on his phone which had low battery, he had to charge the battery by cutting the charger and sticking the wire directly to the battery. Hope someone remembers that ..
here is the link to that pathetic post:-
http://www.engadget.com/2010/09/23/editorial-the-dark-side-of-android-hacking/
PS:- do read how people tell him what an a** he is.
or you could buy/make a dev cable that runs the phone without battery
Werbs said:
I flashed kholk's kernel to 2.3.4 HKTW (i know stupid) and i want to reflash the boot.img found in this thread http://forum.xda-developers.com/showthread.php?t=1138092 but when i plug my phone into charge, the charging symbol is a battery with a question mark on it...
any suggestions would be greatly appreciated
Click to expand...
Click to collapse
HAHAHAHAHAHA, you've been kholked
you said you can power it on long eneought o get to rsd to say low battery.... just flash the boot image for HKTW 2.3.4. have you tried that? does it say battery too low for fastboot?
Sorry, But, my opinion on this is simple. The OP for kholks kernel says specifically, that it is NOT COMPATIBLE with 2.3.4 - so anyone dumb enough to flash it onto a phone running 2.3.4 - well, you deserve what you got lol. Maybe you can just let the battery completely die and hope someone at AT&T takes pity on you. Good luck.
Werbs said:
I flashed kholk's kernel to 2.3.4 HKTW (i know stupid) and i want to reflash the boot.img found in this thread http://forum.xda-developers.com/showthread.php?t=1138092 but when i plug my phone into charge, the charging symbol is a battery with a question mark on it...
any suggestions would be greatly appreciated
Click to expand...
Click to collapse
Hay @Werbs, have you had any luck so far? If so, what worked?
If not, I will try to be helpful here and link the cable that people are referring to that may be able to get you out of the pinch.
Here is the link to the dev cable that will let you flash without a battery in:
http://shop.teamblackhat.info/Factory-style-programming-cable-for-Motorola-FactCable.htm
It shows to be out of stock, but maybe if you message them, they can hook you up.
If you just need someway to charge your battery this is cheaper.
http://www.amazon.com/Amzer-Battery-Charger-Output-Motorola/dp/B004C04Q2M/ref=pd_ys_iyr2
halloo
i bought an used moto x at&t 16
and i found this issue power off at 30% or less and when ever device off and then power on you find that battery show percentage more than it was
wrong percentage...
so if you follow this steps i think it will help you to fix the problem
1) charge to full 100%
2)then download this app called "repair battery life pro" and .... its totally free
3) start the app
4)after it finishes
5)download battery calibration and run it ...also free and dont need root
this how i fixed my problem and i get full day with it ...also when the battery hit 15% run the battery saver app
try this steps i hope it will work with you and give me ur feedback
I will try!
Hope this will work, I'll let you all know. The problem is that my phone has been charging for almost 4 hours and still stuck at 83%. I'll wait till tomorrow to see what happens.
Current Phone
Moto X2 2014 - Unlocked ( NO CARRIER) | XT1095
32GB Model ROOTED
-
-
The battery problem has been happening to since 4 months ago.
This was strange to me as I remember a couple of years back when I had a HTC Evo 4G it lasted a lifetime until it finally gave in to human error; bricked via bad flashing.
Android App Links:
[Battery Life Repair +]
https://play.google.com/store/apps/details?id=com.batterylife.repairbattery&hl=en
[Battery Calibration]
https://play.google.com/store/apps/details?id=com.nema.batterycalibration&hl=en
Dont work for me, my phone turn off at 10%
I can confirmed that this didn't work for me, looks like replacing the battery is the only option you have.
blainer said:
Dont work for me, my phone turn off at 10%
Click to expand...
Click to collapse
did you clear the cash from recovery and turn on the saver on 15%
Clear the cash and run saver at 15 percent
Okay, here's the basic fix (assuming your battery isn't broken)
1. Run your phone until it turns off.
2. While off, recharge phone for 8 hours or overnight
3. While still plugged in, completely boot phone.
4. repeat within 48 hours.
Hold power button down for 8 seconds through out the day to get it to restart with correct battery level and do the same during charge.
just flash the cypher os rom , do clean flashing and then calibrate your battery , after that go for error checking in your battery i swear that battery will never die on 30% or 10% it will completely die on 1%
click thanks button if it works for you people
didn't work here too
Changing my rom from stock rom to custom rom (I use resurrection remix rom) solved this battery issue. My battery always dead on < 1% and never had random shutdown on 30% or such as.
Sent from my XT1095 using Tapatalk
bimasakti85 said:
Changing my rom from stock rom to custom rom (I use resurrection remix rom) solved this battery issue. My battery always dead on < 1% and never had random shutdown on 30% or such as.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
My battery now also dies at 1% but usually jumps from 30% to 1% in 5 seconds xD
Sent from my XT1095 using Tapatalk
Maybe a little off topic but it has to do with the battery. I just bought a wireless charging receiver patch and it works great. However, I noticed it only charges up to 80 percent. But, when I plug in the stock charger it goes from 80 to 100 percent in like a minute? I dont know if it is a battery calibration thing or the fact that the Moto X was never meant to wireless charge and it confused the phone?
Potiential fix!!!
i'm testing a really good theory out on my XT1097 (ATT) running the latest nightly of Lineage.
most people end up unlocking the bootloader with from 4.4.4 - 5.1. this is bundled with a bootloader from 2014/15. this got me thinking, can't i just flash the bootloader from a 6.0 OTA and see if the battery percentage matches perfectly with the OS? after initially flashing the latest possible bootloader (for me, version 61.00, built on 20160824), this actually mirrors the battery percentage of TWRP and when booted into android, and even off-mode charging matches perfectly when booted into android.
i'm going to run this for a week and see if i get any more weird battery reboots at 20-15%, since i know it's not a hardware issue on my end after tediously doing a battery swap on my XT1097.
for those who WANT to try this out right now, grab a copy of a 6.0 OTA for the XT1097 (IF YOU HAVE THE XT1097), doesn't matter what carrier as long as you use the correct zip for the correct model. extract "motoboot.img" and flash it with fastboot.
stock OTAs for XT1097
Code:
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
this may fix the bug for most users, i'll check in every day or so if there's any problems.
Would this work on a XT1096 Verizon? It never officially received marshmallow 6.0 in the US. Will a XT1097 boot loader flash on the XT1096 without bricking it?
TomTheGeek3 said:
i'm testing a really good theory out on my XT1097 (ATT) running the latest nightly of Lineage.
most people end up unlocking the bootloader with from 4.4.4 - 5.1. this is bundled with a bootloader from 2014/15. this got me thinking, can't i just flash the bootloader from a 6.0 OTA and see if the battery percentage matches perfectly with the OS? after initially flashing the latest possible bootloader (for me, version 61.00, built on 20160824), this actually mirrors the battery percentage of TWRP and when booted into android, and even off-mode charging matches perfectly when booted into android.
i'm going to run this for a week and see if i get any more weird battery reboots at 20-15%, since i know it's not a hardware issue on my end after tediously doing a battery swap on my XT1097.
for those who WANT to try this out right now, grab a copy of a 6.0 OTA for the XT1097 (IF YOU HAVE THE XT1097), doesn't matter what carrier as long as you use the correct zip for the correct model. extract "motoboot.img" and flash it with fastboot.
stock OTAs for XT1097
Code:
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
this may fix the bug for most users, i'll check in every day or so if there's any problems.
Click to expand...
Click to collapse
shawndak said:
Would this work on a XT1096 Verizon? It never officially received marshmallow 6.0 in the US. Will a XT1097 boot loader flash on the XT1096 without bricking it?
Click to expand...
Click to collapse
looks like the xt1096 people may be out of luck, since it uses it's own hardware compared to the xt1097. my guess on why this battery issue is happening is because of the fact that the bootloader is designed to talk with the original android version that it supports, which is usually 5.0 and below. until verizon puts out a 6.0 image or if some brave soul decides to fix the bootloader, you're out of luck.
so far my battery issues are minimized to a point where it hiccups once in a blue moon and shuts down, but haven't had a need to bring out my backup battery to get it to boot again. for anyone with the xt1097, my problems have been substantially fixed.
I always thought that the system was having an issue communicating the proper voltage / battery percentage to the updated ROM. Would be nice to see someone fix this! I may actually get rid of the phone because of this annoyance. Its nice to know when your phone will die!
shawndak said:
I always thought that the system was having an issue communicating the proper voltage / battery percentage to the updated ROM. Would be nice to see someone fix this! I may actually get rid of the phone because of this annoyance. Its nice to know when your phone will die!
Click to expand...
Click to collapse
the price we pay for the bleeding edge . i'm really happy with this phone and i probably won't get a new one until this one blows up or something, so hopefully someone figures it out for the verizon folks.
TomTheGeek3 said:
i'm testing a really good theory out on my XT1097 (ATT) running the latest nightly of Lineage.
for those who WANT to try this out right now, grab a copy of a 6.0 OTA for the XT1097 (IF YOU HAVE THE XT1097), doesn't matter what carrier as long as you use the correct zip for the correct model. extract "motoboot.img" and flash it with fastboot.
stock OTAs for XT1097
Code:
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
this may fix the bug for most users, i'll check in every day or so if there's any problems.
Click to expand...
Click to collapse
is this fix reliably working for you ?
For me when i try to flash, its giving pre flash verification failed .
Hello everyone,
my currently verison is nougat 7.1.1 and i have a few probelms
my battery is very bad that is one thing.
when unplugged it from the charger on 100% it goes really fast to 25%
and the second problem is that when i get to 20-30 % the device is shutting down and say that the battery is over.
and i need to plug it to the charger.
downgrade to 6.0.1 wil sove this problems?
and if it wil how can i do it?
i dont have root or unlocked bootlader ,the only way in in the guide Heisenberg's How-To Guide For Beginners
post 11 How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)?
thank you
Roy_Alter said:
Hello everyone,
my currently verison is nougat 7.1.1 and i have a few probelms
my battery is very bad that is one thing.
when unplugged it from the charger on 100% it goes really fast to 25%
and the second problem is that when i get to 20-30 % the device is shutting down and say that the battery is over.
and i need to plug it to the charger.
downgrade to 6.0.1 wil sove this problems?
and if it wil how can i do it?
i dont have root or unlocked bootlader ,the only way in in the guide Heisenberg's How-To Guide For Beginners
post 11 How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)?
thank you
Click to expand...
Click to collapse
Hey... How old is your phone? Your battery has likely degraded over time?!
Downgrading won't fix your issue. I am on 7.1.1 and don't have any issue regarding battery, though of course, the battery life is not as good as it used to when the phone was brand new, but I guess that's normal...
5.1 said:
Hey... How old is your phone? Your battery has likely degraded over time?!
Downgrading won't fix your issue. I am on 7.1.1 and don't have any issue regarding battery, though of course, the battery life is not as good as it used to when the phone was brand new, but I guess that's normal...
Click to expand...
Click to collapse
Hey, umm about 1 year and 2 months
so what can i do to solve the problem with the battery that shut down on 25%?
Roy_Alter said:
Hey, umm about 1 year and 2 months
so what can i do to solve the problem with the battery that shut down on 25%?
Click to expand...
Click to collapse
Wow... 1 year only. Are you sure the phone was brand new and not a refurbished unit? It's strange it shuts down so early. You could try installing "AccuBattery" from the playstore and let it run a few full charges. It will give you an approximative estimation of your battery capacity based on the original capacity versus its actual capacity. Your symptoms in my own opinion is a sign of an early degraded battery. It can happen. Though I haven't really seen this on the N6. I'd try to look for an oem battery and replace it myself, it's easy on the N6.
If you still want to downgrade, backup your internal storage first, because you'll have to unlock the bootloader and it will wow the whole data partition. Flashing an older bootloader, at least downgrading to 5.x may brick your device. I don't know for 7.x > 6.x, but I don't recommend it. Anyway, just flash system.img with fastboot once your bootloader is unlocked. Go in recovery and do a factory reset and you should be good to restart with 6.x Android.
Hoping you'll solve your issue either way... :good:
5.1 said:
Wow... 1 year only. Are you sure the phone was brand new and not a refurbished unit? It's strange it shuts down so early. You could try installing "AccuBattery" from the playstore and let it run a few full charges. It will give you an approximative estimation of your battery capacity based on the original capacity versus its actual capacity. Your symptoms in my own opinion is a sign of an early degraded battery. It can happen. Though I haven't really seen this on the N6. I'd try to look for an oem battery and replace it myself, it's easy on the N6.
If you still want to downgrade, backup your internal storage first, because you'll have to unlock the bootloader and it will wow the whole data partition. Flashing an older bootloader, at least downgrading to 5.x may brick your device. I don't know for 7.x > 6.x, but I don't recommend it. Anyway, just flash system.img with fastboot once your bootloader is unlocked. Go in recovery and do a factory reset and you should be good to restart with 6.x Android.
Hoping you'll solve your issue either way... :good:
Click to expand...
Click to collapse
the probelm i have is a known problem that a lot of other people have
http://venturebeat.com/2016/12/21/google-and-huawei-are-investigating-nexus-6p-early-shutdown-issue/
Roy_Alter said:
the probelm i have is a known problem that a lot of other people have
http://venturebeat.com/2016/12/21/google-and-huawei-are-investigating-nexus-6p-early-shutdown-issue/
Click to expand...
Click to collapse
My bad. I switch between N6 and N6P forum and really thought I was replying to a question in the N6 Q/A forum.
Ok, it's a known issue. People have this problem running 6.x and 7.x.
Since your phone is just 1 year and 2 months old, try to RMA... Sadly, except replacing your battery it's the only option. Some users out of warranty have .Anaged to get a replacement since it's a widespread issue. Have you seen the thread here: https://forum.xda-developers.com/nexus-6p/general/nexus-6p-randomly-shutting-50-youre-t3522911
Sorry for having kind of missguided in the first place.
Good luck...
The early shutdown issue is well known but not the fast discharge after unplugging. At least I've never heard of that being a known issue. I would take the previous poster's advice and install AccuBattery to check your battery health. Some people have definitely experienced a badly degraded battery on the 6P after a year and either RMAd their phone or replaced the battery. Huawei did extend the warranty on the 6P so you might still be able to get RMA or warranty service at a local repair shop. Good luck.
Hello,
I brick my phone, I think I flash it with a wrong modem or something.
I can access Fastboot but not EDL mode.
When I try to reflash with miflash using the exctarcted content of:
A2017_B17_OREO_FULL_EDL.zip or A2017_B13_FULL_EDL
I always get the error : flash_all_lock script is missing.
In fastboot my device is detect by miflash
Is it the good way to unbrick the phone ?
Sombedy can help ?
Regards,
kitkarma said:
Hello,
I brick my phone, I think I flash it with a wrong modem or something.
I can access Fastboot but not EDL mode.
When I try to reflash with miflash using the exctarcted content of:
A2017_B17_OREO_FULL_EDL.zip or A2017_B13_FULL_EDL
I always get the error : flash_all_lock script is missing.
In fastboot my device is detect by miflash
Is it the good way to unbrick the phone ?
Sombedy can help ?
Regards,
Click to expand...
Click to collapse
what whas your setup(bootstacks etc)
I recommend you use axon7tool,and flash twrp trough edl or fastboot.Then boot in twrp and wipe everything,reboot to twrp.Start over
THx for your answer :
I tried to install :
- A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX.zip and the A2017Chinese_OreoModem.zip to install LineageOs.
I cannot boot to twrp cause the phone even with the axon7toolkit always restart with the message "Your device is corrupt".
When in charge it always reboot.
I finally managed to acces to twrp \o/ don't know how actually.
Do you know where can I find a twrp full rom for a2017 ?
Can't find it
Edit : I found updates.zip from another forum.
Know I'mfacing a knex problem when I try to install if :
'This package is for ailsa_ii devices; this is a ""'
When I try to edit the updater script with notepad++ I have got :
'zip file is corrupt'
Any guess ?
Edit2: I succesfuly install the lineageOS after editing the updater script with oreo china modem and universal bootloader.
After reboot I was back to my initial problem : "Your device is corrupt" and the linux ico, if I press power button.
And the worst is : I stil don't know how to boot on twrp...
Any guess ?
kitkarma said:
I finally managed to acces to twrp \o/ don't know how actually.
Do you know where can I find a twrp full rom for a2017 ?
Can't find it
Edit : I found updates.zip from another forum.
Know I'mfacing a knex problem when I try to install if :
'This package is for ailsa_ii devices; this is a ""'
When I try to edit the updater script with notepad++ I have got :
'zip file is corrupt'
Any guess ?
Edit2: I succesfuly install the lineageOS after editing the updater script with oreo china modem and universal bootloader.
After reboot I was back to my initial problem : "Your device is corrupt" and the linux ico, if I press power button.
And the worst is : I stil don't know how to boot on twrp...
Any guess ?
Click to expand...
Click to collapse
powerbutton and volume up?
It only start in a mode with the message : your device is corrupt.
Then i can acces to fastboot mode.
When it start in edl mode (the black mode ?) , the phone is not recognized by adb and miflash
Hello,
I finally got it!
First off all : I wasn't patient enought.
The message I get was just the normal message for the bootloader. I just had to wait 30sec to the phone to start with lineageOS.
I didn't succesfully manage to install a official zte rom so great thank for the work lineageOS.
One last question : This was the phone of my wife. Is lineageOS 15.1 (nightly) stable enough to not expect bug for a year ?
regards,
kitkarma said:
Hello,
I finally got it!
First off all : I wasn't patient enought.
The message I get was just the normal message for the bootloader. I just had to wait 30sec to the phone to start with lineageOS.
I didn't succesfully manage to install a official zte rom so great thank for the work lineageOS.
One last question : This was the phone of my wife. Is lineageOS 15.1 (nightly) stable enough to not expect bug for a year ?
regards,
Click to expand...
Click to collapse
Hell no,not stable.
And welcome on xda axon 7,where we have guides and mentions about this everywhere.
I think Oreo ROMs from nfound are most stable with hellsgate x13 kernel
kitkarma said:
Hello,
I finally got it!
First off all : I wasn't patient enought.
The message I get was just the normal message for the bootloader. I just had to wait 30sec to the phone to start with lineageOS.
I didn't succesfully manage to install a official zte rom so great thank for the work lineageOS.
One last question : This was the phone of my wife. Is lineageOS 15.1 (nightly) stable enough to not expect bug for a year ?
regards,
Click to expand...
Click to collapse
Predatorhaze said:
Hell no,not stable.
And welcome on xda axon 7,where we have guides and mentions about this everywhere.
I think Oreo ROMs from nfound are most stable with hellsgate x13 kernel
Click to expand...
Click to collapse
@Predatorhaze name 5 bugs besides your hit-and-miss battery bug (i.e. only some people have it)
@kitkarma It is, especially the latest unofficial builds. I've been running the same build for months
and the worst i got was "no sim card" twice which was fixed by literally toggling airplane mode on and off
If you'll keep it on LOS, then you should probably install GCam, stock LOS cam is pretty damn bad.
If you want to install a stock ROM you could just get a Chinese EDL package and install it via edl tool (You'll have to install the google apps separately, but they'll work) (It's MiFavor 5.2, very Chinese) or you can get B20 (US Oreo update, AOSP-like) and install it alongside the A2017 modem (You probably downloaded it when you installed LOS).
Choose an username... said:
@Predatorhaze name 5 bugs besides your hit-and-miss battery bug (i.e. only some people have it)
@kitkarma It is, especially the latest unofficial builds. I've been running the same build for months
and the worst i got was "no sim card" twice which was fixed by literally toggling airplane mode on and off
If you'll keep it on LOS, then you should probably install GCam, stock LOS cam is pretty damn bad.
If you want to install a stock ROM you could just get a Chinese EDL package and install it via edl tool (You'll have to install the google apps separately, but they'll work) (It's MiFavor 5.2, very Chinese) or you can get B20 (US Oreo update, AOSP-like) and install it alongside the A2017 modem (You probably downloaded it when you installed LOS).
Click to expand...
Click to collapse
Battery calibration bug,cluster bug,no Dolby atmos,sim card not detected bug, no data second sim,toggling airplane mode f all the sim detects and start act weird.
Predatorhaze said:
Battery calibration bug,cluster bug,no Dolby atmos,sim card not detected bug, no data second sim,toggling airplane mode f all the sim detects and start act weird.
Click to expand...
Click to collapse
last 3 are all the same, no dolby is not a bug lol, battery calibration is your own delusion after i pointed out you could do it
sim 2 data is running just fine
Choose an username... said:
last 3 are all the same, no dolby is not a bug lol, battery calibration is your own delusion after i pointed out you could do it
sim 2 data is running just fine
Click to expand...
Click to collapse
These problems happens random, someone got them,some not.
@Predatorhaze and @Choose an username...: Battery calibration is completely unnecessary, it won't improve battery life or fix anything, you are wasting your time. Here is a link to a statement from one of Google's engineers:
https://www.google.com/amp/s/www.xda-developers.com/google-engineer-debunks-myth-wiping-battery-stats-does-not-improve-battery-life/amp/
I personally have never bought into the battery calibration thing, either before or after reading that article.
AnonVendetta said:
@Predatorhaze and @Choose an username...: Battery calibration is completely unnecessary, it won't improve battery life or fix anything, you are wasting your time. Here is a link to a statement from one of Google's engineers:
https://www.google.com/amp/s/www.xd...tery-stats-does-not-improve-battery-life/amp/
I personally have never bought into the battery calibration thing, either before or after reading that article.
Click to expand...
Click to collapse
Its not about better battery life,but percentages are shown correctly.i stil get 5hours sot
AnonVendetta said:
@Predatorhaze and @Choose an username...: Battery calibration is completely unnecessary, it won't improve battery life or fix anything, you are wasting your time. Here is a link to a statement from one of Google's engineers:
https://www.google.com/amp/s/www.xd...tery-stats-does-not-improve-battery-life/amp/
I personally have never bought into the battery calibration thing, either before or after reading that article.
Click to expand...
Click to collapse
and of course you have to barge in with your infinite wisdom. Battery calibration is useful, if you delete the right file. Deleting batterystats is NOT calibration. There is a file called bms_reset that deletes the ACTUAL calibration files if it contains a "Y". This one really works, and is used for when your phone shuts off unexpectedly and that stuff, not to "improve battery life". It is NOT batterystats.bin and NOBODY HERE even mentioned that file until basically now.
If you swap your battery, there's a good chance that your battery will be messed up (e.g. never charges to more than 90/shuts off at 10/last 10% drains fast).
now there's the other side which is that my man Ter here gets fixed up on whatever you say to him, so after i told him about calibration (took me about 2 days to convince him in fact) he was able to fix his battery entirely and now he's preaching the calibration gospel like it fixes all of your problems. Audio bug? Calibration! Why the hell not!
and of course you have to barge in with your infinite wisdom.
Click to expand...
Click to collapse
Was that an attempt to make yourself seem smarter than everyone else, by talking down on others so you can feel better? If so, it wasn't very effective, had no effect on me. When I post here on XDA, I make an attempt to keep conversations respectful and civilized. And I try to help others by posting what I believe to be useful info.
However, there are times when someone posts something that just jerks my chain, and I have to try my hardest to hold my tongue. Congatulations, you have hit a nerve, I would love to say what I really think of you, but that would just result in intervention by the powers that be. And I will not give you a win by playing into your tactics to elicit a negative response from me. IRL, I am not known as a nice guy, and I have anger issues.
Moving on to more technical things, battery calibration is generally bad because most calibration apps/methods work by deleting batterystats.bin, this file has no effect on the actual percentage that is displayed to the user. Perhaps what you have said works, I will look into it. But I don't feel that I need to, because my battery life is fine and I have never experienced inaccurate #s with either of my A7s.
AnonVendetta said:
Was that an attempt to make yourself seem smarter than everyone else, by talking down on others so you can feel better? If so, it wasn't very effective, had no effect on me. When I post here on XDA, I make an attempt to keep conversations respectful and civilized. And I try to help others by posting what I believe to be useful info.
However, there are times when someone posts something that just jerks my chain, and I have to try my hardest to hold my tongue. Congatulations, you have hit a nerve, I would love to say what I really think of you, but that would just result in intervention by the powers that be. And I will not give you a win by playing into your tactics to elicit a negative response from me. IRL, I am not known as a nice guy, and I have anger issues.
Moving on to more technical things, battery calibration is generally bad because most calibration apps/methods work by deleting batterystats.bin, this file has no effect on the actual percentage that is displayed to the user. Perhaps what you have said works, I will look into it. But I don't feel that I need to, because my battery life is fine and I have never experienced inaccurate #s with either of my A7s.
Click to expand...
Click to collapse
if you dont have problems you should stay away from it.
Calibrating battery does not increase battery life,that is what i know (maybe it does for 3year old battery)
But what me was aiming for was showing correct % in statusbar.Sometimes it drop from 60% to 58% and then it stays on 58% for a longer time period( i think more people got this but are not aware of it)
---------- Post added at 02:53 PM ---------- Previous post was at 02:40 PM ----------
Choose an username... said:
i dont have this folder /sys/module/qpnp_bms/parameters/bms_reset
can you look to see if you have it?
Click to expand...
Click to collapse