Database Users

Almost Full Nougat TWRP flashable zip

I say ALMOST because you must have either used the manual (adb) method to upgrade to Nougat, or flashed the v30b_update.zip to use this. If you are on MM, this will more than likely brick your phone.
OK, so after testing, here is the complete Nougat zip. It is every partition from the v30b KDZ except boot, system, and recovery (obviously), so you keep TWRP. This has the modem, tz, and rpm partitions. If you flashed the other zips that I posted with the individual partitions, no worries, reflashing them does not hurt anything, and I am not going to make yet another zip. Some people may want to just flash the minimal needed to get to Nougat so they can restore MM TWRP backups if they need / feel like it.
You can dirty flash this on top of my v30b_update.zip, but you are better off doing a factory reset (full wipe). I could have included the wipe in the zip, but this way -- YOU can decide.
Also, you MUST have an H901. Not an H900, not an F600, not a BMW, or Audi, or Toyota. Again, if you have anything other than an H901, this will brick your phone.
This fixes the front facing camera issue with 4x3 5mp (it was the aboot partition that solved that FYI). Can't say what else it may have fixed that I didn't even know was broken. I also can't say what functionality may be LOST -- that is why I am posting this.
If you flash this, and suddenly something doesn't work that used to, please post in this thread. Same goes if something suddenly STARTS working.
Download here
SHA1: b1ac20a6eaccf2dfbd22c09886ddcd03ab638ec3
If you want to be able to revert to MM, then you need to make a FULL backup of your phone, and I don't mean with TWRP.
* adb reboot recovery
* adb shell
# this will give you a list of all the partitions
* ls /dev/block/bootdevice/by-name
* exit
# You then need to backup all the partitions
* adb pull /dev/block/bootdevice/by-name/<just go through them in order> <name of partiton>.img
# example
* adb pull /dev/block/bootdevice/by-name/aboot aboot.img
* adb pull /dev/block/bootdevice/by-name/modemst1 modemst1.img
# do this for EVERY partition
# you will need 64gigs of space on your PC to hold everything even if the phone is empty since dd stores zeros.
# Now, if you ever want to revert, you do the reverse, and just flash each one of these with dd and you will be right back to where you are.
-- Brian

reserved

reserved #2

Awesome!! full Naugat... so when is debloated version coming? I tried to debloat, but even removing non essential T-Mobile apps gives me bootlloop, or if you can tell me which apps are safe to remove will be a huge help ...
Thanks for you work man only active developer for H901, and I know you have allot on your plate but you are our only hope... Cheers!!

A full debloat is a very tedious process, so it is bottom of the barrel. If someone else doesn't jump in, I will eventually release one though.
-- Brian

Thanks again! Just installed. Tested the only thing I encountered on the update.zip and it is confirmed fixed with this.
Keep up the good work! :thumbup:
---------- Post added at 11:22 AM ---------- Previous post was at 11:19 AM ----------
zeexhan said:
Awesome!! full Naugat... so when is debloated version coming? I tried to debloat, but even removing non essential T-Mobile apps gives me bootlloop, or if you can tell me which apps are safe to remove will be a huge help ...
Thanks for you work man only active developer for H901, and I know you have allot on your plate but you are our only hope... Cheers!!
Click to expand...
Click to collapse
I've removed all the Tmobile apps that I don't want or need and I haven't gotten any bootloops.
Just have to remove that apps entire folder. Also removed some Google apps I didnt want.

so...this does not include the N modem then? and the first update.zip does? cause i thought i saw the first update.zip it say flashing modem..

Please disregard, thank you

Is these fix front camera
Sent from my LG-H818 using XDA-Developers Legacy app

sumitverma1 said:
Is these fix front camera
Sent from my LG-H818 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes this will fix the front facing camera bug that was mentioned in the update.zip thread.

I notice this seems to include a RPM partition. So do we need to flash your add-on.zip still for the nougat power management? It sounds like all we need now is update.zip and this along with SuperSU ? Awesome work btw. My battery life overnight after flashing this was 1 percent loss with WiFi and Bluetooth on. You should combine your update and this camera/misc fix zip together.

First post updated to answer that and some other questions.
-- Brian

I flashed this new add-on or full partition zip
cleared my Dalvik cache and my regular cache and well I didn't fell like re entering all my mods and settings so I didn't do the full wipe. noticed the new boot loader right away can pause boot now lol. I didn't have the camera bug but am wondering how this latest zip will do with my battery some one posted it helped there overnight only running 1% will post if I find more things it affected "can't hurt things" and I'm happy with the mods N 7.0 can run so I'm even deleting my MM 6.0 BACKUPS. No need to have that option anymore. I do wonder about kernels, the old sound mod, and https://forum.xda-developers.com/tm...-msm-8992-cpu-io-ram-interactive-gov-t3351478

Any plans to track down where the rollback counter is getting incremented and remove that part?

@famewolf anti-rollback version wasn't incremented even if you took the OTA or flashed the KDZ. It was version 2 on MM, and it is still version 2.
I have no idea why people are having a problem flashing back to v20L (it passes the rollback check in LG UP -- but then fails later in the flash). Makes no sense....
-- Brian

runningnak3d said:
@famewolf anti-rollback version wasn't incremented even if you took the OTA or flashed the KDZ. It was version 2 on MM, and it is still version 2.
I have no idea why people are having a problem flashing back to v20L (it passes the rollback check in LG UP -- but then fails later in the flash). Makes no sense....
-- Brian
Click to expand...
Click to collapse
Ok, I'll chalk it up to my friend trying to go back to MM without restoring all partitions then because you made it clear a normal restore wasn't gonna do it. I think they tried using flashfire. I'm not upgraded yet.

Will this fix the battery drain issue or is it the same as flashing the fix?

Could you make a fix for just the front facing camera for those who flashed the update.zip and don't want to re-reset and flash?

@k00lguy105 I dunno. Some people were getting better battery life, others worse. Try it -- you can always revert.
@xxcmb3k3xx It was the aboot partition that fixed the camera. The thing is, I don't know the consequences of flashing JUST the aboot without all the other boot loader partitions. I will make you a zip if you want to try it, but I can tell you now that aboot is not something you want to mess with without 100% certainty of the outcome. I was convinced that the 808 could always be recovered with the SD card, but aboot is the one part of the boot process that will turn your phone into an unrecoverable brick.
If you don't want to wipe, then don't -- it is safe to dirty flash this. I only recommend wiping because that way you are guaranteed to not have problems. At least wipe cache, and as I said above, if bad comes to worse you can always revert.
-- Brian

runningnak3d said:
@k00lguy105 I dunno. Some people were getting better battery life, others worse. Try it -- you can always revert.
@xxcmb3k3xx It was the aboot partition that fixed the camera. The thing is, I don't know the consequences of flashing JUST the aboot without all the other boot loader partitions. I will make you a zip if you want to try it, but I can tell you now that aboot is not something you want to mess with without 100% certainty of the outcome. I was convinced that the 808 could always be recovered with the SD card, but aboot is the one part of the boot process that will turn your phone into an unrecoverable brick.
If you don't want to wipe, then don't -- it is safe to dirty flash this. I only recommend wiping because that way you are guaranteed to not have problems. At least wipe cache, and as I said above, if bad comes to worse you can always revert.
-- Brian
Click to expand...
Click to collapse
I just dirty flashed and everything seems to be working fine, I'll update for battery later.

[SOFTWARE UPDATE] A2017U - B35 Rolling out

Software Update: Axon 7 (A2017U) owners... Within the next 48 hours, an update will bring a security patch to your device. Bluebourne and KRACK vulnerabilities will be remedied with this patch.
https://community.zteusa.com/discussion/52369/software-update-axon-7-a2017u-now-on-b35

DrakenFX said:
Software Update: Axon 7 (A2017U) owners... Within the next 48 hours, an update will bring a security patch to your device. Bluebourne and KRACK vulnerabilities will be remedied with this patch.
https://community.zteusa.com/discussion/52369/software-update-axon-7-a2017u-now-on-b35
Click to expand...
Click to collapse
Which is the patch date? G B09 has the December 1 patch, just wanted to know which one fixes this stuff

Can someone provide a B35 update zip? It's no issue for me to connect to Wi-Fi to install it, but I like to keep offline cached copies of files for recovery purposes, so that I can update even without Internet.
Thanks!
Edit: I have A2017U.

When will the B35 firmware will be available as flashable TWRP zip across a2017 devices?Does it have a improved battery life?

Predatorhaze said:
When will the B35 firmware will be available as flashable TWRP zip across a2017 devices?Does it have a improved battery life?
Click to expand...
Click to collapse
As soon as you make one?
Pretty sure it's available now. Let us know how the battery life is.

I know I asked before, but if someone can post a direct URL link to the B35 update file (whether it be a zip or something else) then it would be much appreciated. I know @DrakenFX released a system and bootstack zip, but I would rather use official files. I can't save an offline copy of the file since I'm not currently rooted, I suspect it is stored in the /cache partition. The file size is close to 700MB. I just want a copy for offline use. Maybe someone with root can capture a copy of the file after it has downloaded, but before the phone reboots to apply it. Or maybe the URL can be sniffed with WireShark or whatever. A B35 full OTA zip is better, but ZTE hasn't posted an SD card update download on the zteusa.com website yet.
Thanks!

I was able to grab the B35 update zip without rooting. I let the updater download the file, then quickly powered off the phone before it had a chance to reboot and install. Then I booted into EDL mode, and used @tennear's Axon7Tool to write TWRP. From TWRP I went to /data/data/com.zte.zdm/files, and grabbed a file called fota_update.zip. Then I reflashed the stock recovery with Axon7Tool, and installed the zip. All went fine. I suspect you can grab any OTA zip this way. Maybe I'll upload a copy of the file later.

If there's any interest in a B35 SL!M➀ aroma-version let me know

raystef66 said:
If there's any interest in a B35 SL!M➀ aroma-version let me know
Click to expand...
Click to collapse
Yes, sir! Very interested in flashing the update through TWRP while maintaining the advantages of stock for the hardware on board.

raystef66 said:
If there's any interest in a B35 SL!M➀ aroma-version let me know
Click to expand...
Click to collapse
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!

amphi66 said:
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!
Click to expand...
Click to collapse
I think you're referring to this one ?
In general, did you see quite some difference before and after ?
You can PM for the tons of frozen stuff you like to get rid off. Think i might work on it these days to have some fun :cyclops:

raystef66 said:
I think you're referring to this one ?
In general, did you see quite some difference before and after ?
You can PM for the tons of frozen stuff you like to get rid off. Think i might work on it these days to have some fun :cyclops:
Click to expand...
Click to collapse
Yes. I downloaded those 'init' files way back last Spring & found them more effective (at least impression-wise) than the AKT stuff. His "Conservative" mod helps w/ battery w/o a noticeable performance hit.
Early on I found the A7 was not happy when some apps were removed & replaced, but functioned OK if they were kept frozen & then replaced. Fortunately there is enough storage & memory that inefficiency does not (so far) cause issues. Sort of like the legacy SubStratum which could (sort of) work as long as system apps were excluded.
I look forward to your "hobby". Thanks

hi.
if i upgarde my A2017u directly from setting>update on my phone, i loose root and twrp or not?

redhou said:
hi.
if i upgarde my A2017u directly from setting>update on my phone, i loose root and twrp or not?
Click to expand...
Click to collapse
If you are using TWRP and/or are rooted, that setting>update will fail due to modified system files. READ & follow directions in post #2 HERE. Data will be saved & TWRP will be upgraded (if req'd).

davisml said:
Yes, sir! Very interested in flashing the update through TWRP while maintaining the advantages of stock for the hardware on board.
Click to expand...
Click to collapse
amphi66 said:
I run Apex Launcher & Magisk on the A2017U Stock, cutomized with a ton of stuff frozen & one of @warBeard_actual's mod. It would be nice to have the Aroma power and ability to "thin" things out. Thanks!
Click to expand...
Click to collapse
Working on it Was harder then our G version stocksystem to make it boot with aroma. Really weird stocksystem...
But i succeeded. Having bootloader changed, twrp build-in and seperate modems, bootanimation changed, build-in battery tweaks, magisk, supersu, fasterUI....all ok now. Just adding some other stuff in next days. Hope to release it in the weekend :cyclops:

amphi66 said:
If you are using TWRP and/or are rooted, that setting>update will fail due to modified system files. READ & follow directions in post #2 HERE. Data will be saved & TWRP will be upgraded (if req'd).
Click to expand...
Click to collapse
the download file start with no probleme using setting>update. i had stoped it.
can i continu ? i had a lot of difficult before root my phone in past and i don't like to loose it

redhou said:
the download file start with no probleme using setting>update. i had stoped it.
can i continu ? i had a lot of difficult before root my phone in past and i don't like to loose it
Click to expand...
Click to collapse
It will download, but the install will simply fail as it checks the system files, but certainly you are free to do as you wish. Good Luck!

raystef66 said:
Working on it Was harder then our G version stocksystem to make it boot with aroma. Really weird stocksystem...
But i succeeded. Having bootloader changed, twrp build-in and seperate modems, bootanimation changed, build-in battery tweaks, magisk, supersu, fasterUI....all ok now. Just adding some other stuff in next days. Hope to release it in the weekend :cyclops:
Click to expand...
Click to collapse
Uploading A2017(U)(N-B35)_AROMA_SL!M¹_DF!NR now Preparing a seperate thread on ROM section. Keeping you updated when ready :good:
EDIT : DONE ! LINK

hi, i am installing the new OTA update but it when my restarts TWRP asks for password to mount and doesn't allow me to install this new OTA update. I entered my phone password which said it decrypted the pkg but then it only opens the TWRP GUI. I tried to install the zip manually but it said it failed.
How can I let the phone install it without TWRP interfering?
Thanks a lot.

lachdanan said:
How can I let the phone install it without TWRP interfering?
Click to expand...
Click to collapse
You can't. Use stock recovery if you insist on OTA, or use DrakenFx's zips to flash from TWRP. The latter is much more convenient.

a2017 brick

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

Stuck on boot

Hi
When I wipe devik, data, cache and system partition using TWRP and reboot, the phone take forever to boot it stuck in LG logo. I don't understand why it stuck when I wipe those partitions. I've tried combination keys to boot in TWRP recovery but it doesn't work. Now I'm stuck. I don't know what to do. My phone is LG G3 (F460L) Android 4.4.2. Please see the photo.

EDIT: I didn't read the system partition thing before answering below... If I'm not completely wrong, your phone can't boot, because there is no system which could be loaded, so your phone is more or less empty, when you wiped the system partition. No more Android 4.4.2 :/ I don't know, why booting into TWRP doesn't work. Maybe you carefully could try to unbrick your phone and reinstall stock rom again.
Hej,
have you ever had booting problems with your phone? I'm in constant bootloop trouble with my D855. Some say it's a battery issue, which I can not confirm since I've tried 4 different ones (including 2 brand new ones). Some others say my mainboard has kind of an unrepairable defect. As I go with this possible explanation, I ordered a new used mainboard from China, hoping for it to arrive in Europe and not beeing fished by the authorities...
I can't say for sure what is the exact issue with my or your phone, the only thing I can tell is that there are tons of posts that can be found on the internet about the G3 having bootloop issues after a couple of years of normal usage. And for most users this came all of a sudden. Believe me, I've invested days of research, uncounted attempts of unbricking my phone (I thought I bricked it somehow, but it wasn't the case) and flashed stock rom and LOS as hard as I could. All ended up in my phone not running stable, crashing and then bootlooping. Sometimes (most of the times) if it's shut down and I want to turn it on, it gets stuck on the LG boot splash screen. It seems that somehow the energy management is not capable of running the phone stable under low voltage, since at least for me the probability of successfull boots slightly rises with a higher state of charge. But I can't take it for granted...
Good luck for you, I will keep reading this thread.

I wipe System Partition which contains Kitkat 4.4.2 but I already flash new ROM (CM13 Unofficial f460) after. There should be CM13 in system partition. I don't know why it can't boot. On the other hand, I can't find official firmware 4.4.2 for F460L (3hours search still no luck). I found only official firmware 6 Marshmallow which I'm afraid I won't be able to root forever if I flash it. I'm really appreciated if you can find one somewhere.

Rexkh said:
I wipe System Partition which contains Kitkat 4.4.2 but I already flash new ROM (CM13 Unofficial f460) after. There should be CM13 in system partition. I don't know why it can't boot. On the other hand, I can't find official firmware 4.4.2 for F460L (3hours search still no luck). I found only official firmware 6 Marshmallow which I'm afraid I won't be able to root forever if I flash it. I'm really appreciated if you can find one somewhere.
Click to expand...
Click to collapse
You could follow the link in this post which leads to a russian site. I saw a 4.4.2 version of Android in there. Good luck!

Thanks. I found official firmware lollipop and flash it. I've been searching for a way to root it but most of the method is for D855. Do you know if F460L Lollipop is rootable?

Rexkh said:
Thanks. I found official firmware lollipop and flash it. I've been searching for a way to root it but most of the method is for D855. Do you know if F460L Lollipop is rootable?
Click to expand...
Click to collapse
You can use the search function within the forums or search engines like startpage. I don't actually own a F460L and I'm not an expert either, so I don't know, how it works exactly. Punchin the keywords "F460L Lollipop root" into startpage.com brought me the following link as first result:
https://forum.xda-developers.com/lg-g3/general/guide-everything-lg-g3-cat-6-f460s-t3542542
Just follow the guide in OPs post

I already try LG One Click Root. It doesn't work. When it reach 45% (Looking for LG Serial Port), the phone restart (normal reboot) and it stay at 45% definitely. I manually reboot to Download Mode, still, 45%. Any suggestion?

Rexkh said:
I already try LG One Click Root. It doesn't work. When it reach 45% (Looking for LG Serial Port), the phone restart (normal reboot) and it stay at 45% definitely. I manually reboot to Download Mode, still, 45%. Any suggestion?
Click to expand...
Click to collapse
Sorry, as I'm on a D855, I don't really know. I rooted via King Root which only works with a specific Android version. I used this guide which helped me a lot: https://www.youtube.com/watch?v=8VOgM3jLas4
It's for the D855 but it could work with the F460 too. In the video description, there is a download link to the specific stock rom version for F400 models. The guide tells you where and what to download and how to install. You could try this and I'll keep reading Good Luck!

note 3 not booting - pls help

[email protected]
thx for taking a look on my Problem
3month old note 3 no root, stock Rom, 3months no Problems,
was last week outside and i guess i was low on battery it was off as i had it in Hand
was loading all the evening and the battery is fully green
it starts, i can see mi logo, it changes to Android with loading dots at the Bottom and then it goes off
tried several times
fastboot is available
and main menu with reboot/wipe data/connect with mi assistant
i already tried:
wipe data - finished with ok (all my data gone) but still same issue
connect with mi assistant - no connecttion to Software
someone any ideas - thanks for any help
greetz

Since you already lost your data, try to flash the ROM again. I don't remember if you can transfer/flash the stock ROM without an unlocked bootloader (I suppose it is locked), if you can at least dirty install it as an update it may work too (google it). Unfortunately, providing more information over unlocking the phone is inappropriate.

GreatApo said:
try to flash the ROM again.
Click to expand...
Click to collapse
How?
GreatApo said:
I don't remember if you can transfer/flash the stock ROM without an unlocked bootloader (I suppose it is locked)
Click to expand...
Click to collapse
yes it locked
GreatApo said:
Unfortunately, providing more information over unlocking the phone is inappropriate.
Click to expand...
Click to collapse
can u pm me please?
u are the onle one who relied to my post
thanks in advance

Since your bootloader is locked, your options are limited.
To expand a little what i mentioned, your best try it may be to try and update the current from from the stock recovery. That may fix a potential corrupted partition. To do so, you can follow the steps of method 2 in this article. However, I am not aware if you can transfer the update.zip in the phone... I suppose that the stock recovery doesn't mount the phone to the PC. Thus, you probably need to try and transfer if through fastboot but that may not be possible too (could check if adb push works or if you can boot a twrp recovery, not flash just boot, but you probably wont be able)...
If you can't do the above steps, you are in a half-brick mode right now with a locked bootloader. Generally, there is no official way to get around this.