hmmm I am using 20D and CM11 Snapshot 12 and have no issues, just that after first boot brigthness is very low, but after turning screen off and on again the brightness is working well. I just would use 4.2.2 base to get more recent recoverys. I am just wondering if there is a different between radio versions or so. Was not able to get an overview over all different parts included in different bases....
[RECOVERY][v500] TWRP 2.8.6.0 touch recovery [2015-03-27]
- Thread starter Rick Roll
- Start date
Those firmware flashable zips only replace the bootloader and aboot. No radio.
You'll get brightness issues when you're using the 4.4.2 base
how come you dont get this issue on stock lg rom with 4.4.2 base?
@Rick Roll, can you add support for f2fs both in recovery and in your kernel? Our tab would be even more fast having data and cache formatted in f2fs. Thank you.
Sent from my LG-D405n using XDA Free mobile app
Sent from my LG-D405n using XDA Free mobile app
Ok just want to confirm something because I don't want a brick 
. I am currently on 4.4.2 20d firmware, if I use DD command to get the 10A aboot will I be able to flash this TWRP without problems other than the brightness issue !? Or is it more advisable to downgrade ? Because downgrading with the tool seems much more lengthy process. In other words why would anyone downgrade whole firmware if they can just downgrade the aboot partition !?
. I am currently on 4.4.2 20d firmware, if I use DD command to get the 10A aboot will I be able to flash this TWRP without problems other than the brightness issue !? Or is it more advisable to downgrade ? Because downgrading with the tool seems much more lengthy process. In other words why would anyone downgrade whole firmware if they can just downgrade the aboot partition !?
If you can get the custom recovery installed by only downgrading aboot, then that is all you need to do. Once you have the custom recovery, you can switch between bootloaders with a flashable zip file without needing the flash the entire stock image.
Yes, all you need to do is have the older aboot.img from the 4.2.2 stock Rom in order to install a custom recovery. The older aboot is the only one that is loki exploitable.
Yes, all you need to do is have the older aboot.img from the 4.2.2 stock Rom in order to install a custom recovery. The older aboot is the only one that is loki exploitable.
Last edited:
I just downgraded my Gpad to 4.2.2 to flash the pack man rom and needed a recovery. Came here, took the img file and flashed it using flashify and everything went smooth. So my question is what is this loki vulnerability mentioned in the first post. Why do we even need it?
Loki is built into flashify.. It's a tool used to bypass the locked bootloader.
So I just installed 2.8.5.0(twrp flashable zip version) on 20d firmware and no brightness issue in twrp, only the splash screen is dim but it recovers to full brightness in the actual recovery.
你自己能不能编辑TWRP呢？可以的话，这个有可能有用。https://crowdin.com/project/twrp-manager/zh-CN
I'm no developer, but would these strings on that page help someone be able to use TWRP in Chinese?
Sent from my LG-V500 using XDA Free mobile app
大部分用 Gpad 8.3 的人在美国。应该不会有很多人需要用中文的TWRP。我的电脑太老。而且，虽然不是菜鸟，我也不会编译。你的英文还好吗？可不可以用一个攻略？如果你要pm我，我也许更能帮助你。
Translation Edit: Most people who use the gpad 8.3 are in America and wouldn't need to use TWRP in Chinese. I'm not a noob, but my computer is to old and I'm no developer either. How is your English? Are you able to follow a walk-through/tutorial? If you want to pm me, I may be able to be of more assistance.
Sent from my LG-V500 using XDA Free mobile app
Last edited:
Guys, please talk English on XDA.
Sent from my LG-V500 running CM12
Sent from my LG-V500 running CM12
Screen stays on bug
Is there any progress towards fixing the bug whereby the screen remains on regardless of TWRP settings?
It works as it should with other devices.
Is there any progress towards fixing the bug whereby the screen remains on regardless of TWRP settings?
It works as it should with other devices.
TeamWin has just pushed out TWRP 2.8.6.0. It doesn't look like there are big changes, except for the pattern lock. Most of them are bugfixes.
I'm curious what extra patches are required to fix the source code to make TWRP work for the v500. Since the official source is actually for palman devices. Do I just need to replace "palman" with "awifi" in a Makefile or something? Changes to BoardConfig.mk?
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone