If I remember correctly, there is an apk version of AKT 1.6 hidden somewhere in one of those AKT threads from the OnePlus3 section. That'll make installation easier if you can find it.
Another similar alternative is the Magisk module LKT. I have used both AKT and LKT and found no noticeable difference in battery life between them, but that may vary based on your usage.
Also, if you are currently using an LG OEM battery, then you might want to consider looking at getting one of those 4100/4200 mAh Lithium Polymer batteries made by various brands such as Perfine, MaxxxJuice, Shenmz, and Taeozi. They are the same size as the OEM battery but actually have a higher capacity. Some of them have been mentioned in this battery search thread.
Okay. Glad u av been able to root. So after u download android Alpha 8.0 rom. I believe u will have a smooth sail. But for a safe installation:
1. Get the latest TWRP and flash the recovery from Twrp.
2. Format data. System, data, cache. Or go through Alpha rom 8.0 thread and follow the steps. U will be fine after flashing. Everything works here with me. I'm also on MTN Nigeria.... Battery life too is okay. Though i have ordered one of those 4100 mah battery.
Its not really LG, blame US carriers and their love of sodomizing their customers. AT&T and Sprint explicitly chose not to release stock ROM, and Sprint/T-Mobile increment ARB. Manufacturer hands the base device to the carrier, and the carrier decide what security features they want to enable. It could be worse, American Samsung flagship are practically impenetrable, the S7 was only rooted because an engineering firmware was leaked, but it had serious performance issues and minor side effects. The Verizon Pixel is locked tight as well, as with Verizon phone in general historically.
But generally, the only model to avoid is LS997 because only a tiny number of them floating around are still rootable, and even rooted you're restricted as hell because you're stuck using the ancient ZV6 modem. H918 has a slightly more involved rooting process, but once you're done its set and forget. Anti Rollback is only ever an issue if you need to go back to a pre-ARB version to root, and with the H918 that's not the case.
S tier: F800/Korean. First in line for OTA, last to get support dropped.
A tier: US996 (free market). Official bootloader unlock
B tier: US996 (carrier), VS995, H910, H915. Fully flashable to US996 bloat-free firmware, can take US996 modem firmware without losing signal. Some people reported signal issues with crossflashing on the H910/H915, but it easily could just be user errors. The H915 has official KDZ, and the H910 can just flash a custom made return to stock package even if it doesn't have an official KDZ.
C tier: H918. Roundabout methods required compared to DirtySanta compatible models.
D tier: H910PR/etc.... Unpopular models from "literally who?" countries, dual SIM models. It might work, or it might not. Dual SIM model seems to have issues due to the hardware difference, and there's no dev with the actual phone.
E tier: Rootable LS997.
F tier: Unrootable LS997
As for the FM Radio thing, its enabled/disabled kernel side. A lot of people reported losing FM Radio after rooting and installing a custom kernel in the early days threads because its built from the US996 source tree. Its well known at this point that hardware/mobo wise all single SIM V20 are equal (refurbished American V20 popping up with F800 coded mobo), just a difference in software and eFuse pop. Hence some model can take cross flashed modem well, and some can't. It might actually be just software, because the V30 had an early Nougat firmware for the US998 that could be flashed onto any carrier device and modem would work fine. You can then upgrade from this version to any later firmware, and modem will still continue to work, even if straight flashing newer firmware doesn't.
Yeah H910PR is a pain, it's my current phone that i bought online with a Claro firmware
You can still unlock , root , and install custom roms on this device with H910, H915, US996 methiods, one major issue that i'm facing is just i can't install any custom kernels.
i dunno maybe there's just something wrong with how i root my device, i haven't looked much further into it because i fear i might break my device, H910 method worked tho
Okay. Glad u av been able to root. So after u download android Alpha 8.0 rom. I believe u will have a smooth sail. But for a safe installation:
1. Get the latest TWRP and flash the recovery from Twrp.
2. Format data. System, data, cache. Or go through Alpha rom 8.0 thread and follow the steps. U will be fine after flashing. Everything works here with me. I'm also on MTN Nigeria.... Battery life too is okay. Though i have ordered one of those 4100 mah battery.
Yeah H910PR is a pain, it's my current phone that i bought online with a Claro firmware
You can still unlock , root , and install custom roms on this device with H910, H915, US996 methiods, one major issue that i'm facing is just i can't install any custom kernels.
i dunno maybe there's just something wrong with how i root my device, i haven't looked much further into it because i fear i might break my device, H910 method worked tho
Guys, So i thought this was normal but i guess it isn't.
After i used dirty santa to unlock my phone, i noticed a warning message at boot. Now i had read that there was going to be a warning message from the aboot at boot so i thought it was normal until i saw how that warning actually looks like from this Thread.
Guys, So i thought this was normal but i guess it isn't.
After i used dirty santa to unlock my phone, i noticed a warning message at boot. Now i had read that there was going to be a warning message from the aboot at boot so i thought it was normal until i saw how that warning actually looks like from this Thread.
Hmmm...Mine boots alright. Apart from some app/process crashes and also the device deciding to go crazy on me last time when it was on 5% battery and when i connect the charger, it will constantly connect and disconnect and the screen's back light would go from high to dim over and over until i turned the device off and charged, i think it's okay
After i rooted? I installed a stock Oreo rom that was provided from a rooting thread (rooted 20h)
I did a little backread and regarding on the warning sign being static i thought that was normal, maybe there is something wrong with how i root
But i followed the instructions carefully for like, three times already but same results.
So it's tiring to go back and do it all over again
Can't be troubled to do a screenshot but I just did this for you on my rooted bootloader unlocked device and everything showed up false just likes yours. On the fastboot screen on your device there is a red label on the top of the screen, I think that indicates security is off. You won't see this red otherwise.
Can't be troubled to do a screenshot but I just did this for you on my rooted bootloader unlocked device and everything showed up false just likes yours. On the fastboot screen on your device there is a red label on the top of the screen, I think that indicates security is off. You won't see this red otherwise.
Cool. One thing that bugs me is that, mine doesn't show a readable text with a single triangle at the top, instead, it's shows a scrambled text with about 4 or more triangles. I posted a screenshot a few pages back. I was told the scrambled text started after the Oreo update. But here's the case my device is on Nougat. It has been on Nougat since I received it.
Unless its a US996, no V20 can be bootloader unlocked. The DirtySanta method simply flashes the leaked Engineering Bootloader, which doesn't check for signature at all. Its like changing the lock so it opens to any key vs removing the lock altogether.
As for the scrambled text, its because of the engineering bootloader. Flash a custom kernel and it'll sort itself out. Alternatively, put your hand over the light sensor, then turn off the screen. Keep it there and turn it back on, it'll fix itself until the next restart
Unless its a US996, no V20 can be bootloader unlocked. The DirtySanta method simply flashes the leaked Engineering Bootloader, which doesn't check for signature at all. Its like changing the lock so it opens to any key vs removing the lock altogether.
As for the scrambled text, its because of the engineering bootloader. Flash a custom kernel and it'll sort itself out. Alternatively, put your hand over the light sensor, then turn off the screen. Keep it there and turn it back on, it'll fix itself until the next restart
The scrambled bootloader is caused by the same reason as the boot static. The engineering aboot was taken from a prototype device, and there was some changes between then and release. You can adjust the value in the kernel to compensate, but you can't fix it in laf and aboot. I've had it happened once flashing a H910 package onto a LS997 to see if the radio works, its just a general kernel/aboot incompatibility issue as far as I know. Flashing a US996 based KDZ (minus aboot and maybe modem) should fix the issue.
