[RECOVERY][v500] TWRP 2.8.6.0 touch recovery [2015-03-27]

[uzi2]

2.8.5.0 released!

The screen won't turn off with this version. The settings are there to adjust the time-out, but it stays on. Even the power button doesn't turn off the screen - just initiates the lock.

 

[Deltadroid]

The screen won't turn off with this version. The settings are there to adjust the time-out, but it stays on. Even the power button doesn't turn off the screen - just initiates the lock.

Ate you using 4.2.2 or 4.4.2 firmware base?

 

[uzi2]

Ate you using 4.2.2 or 4.4.2 firmware base?

4.2.2

 

[[email protected]@tz]

Little OT, how can I check if I use 4.4.2 or 4.2.2 base?

Gesendet von meinem LG-V500 mit Tapatalk

 

[Deltadroid]

Little OT, how can I check if I use 4.4.2 or 4.2.2 base?

Gesendet von meinem LG-V500 mit Tapatalk

If you are using stock CM 11 or 12 and don't have any brightness problems (dark screen), then you have a 4.2.2 base.

If you are using Red Kernel or Mani Kernel and don't have any brightness problems (dark screen), then you have a 4.4.2 base.

 

[auleu]

whats the differences between these builds and http://forum.xda-developers.com/showthread.php?t=2551499 ?

 

[Deltadroid]

whats the differences between these builds and http://forum.xda-developers.com/showthread.php?t=2551499 ?

This version supports automatic updates for cm12.

 

[auleu]

This version supports automatic updates for cm12.

what method is the more recent one for flashing a recovery? i have v500 with locked bootloader running latest official kitkat 20d version and currently rooted with towelroot.

 

[Deltadroid]

what method is the more recent one for flashing a recovery? i have v500 with locked bootloader running latest official kitkat 20d version and currently rooted with towelroot.

With 20d, your aboot partition is not loki exploitable. Your choice is to either downgrade with lg tool 2014 to 10a firmware, or use the dd command to overwrite your current aboot with the aboot from 10a. Then you can use a program like Flashify to install a custom recovery.

Note that stock cm requires 10a bootloader, or you will have brightness issues with the stock cm kernel. This can be fixed by installing the red or mani kernel on top of stock cm.

 

[auleu]

With 20d, your aboot partition is not loki exploitable. Your choice is to either downgrade with lg tool 2014 to 10a firmware, or use the dd command to overwrite your current aboot with the aboot from 10a. Then you can use a program like Flashify to install a custom recovery.

Note that stock cm requires 10a bootloader, or you will have brightness issues with the stock cm kernel. This can be fixed by installing the red or mani kernel on top of stock cm.

what exactly is this brightness issue? in the other threads i saw people got to install a recovery from a script that you only need to change a value in a .bat. i didnt saw any downgrades necesary.
where can i see what version of bootloader i have?

 

[Deltadroid]

If you have 20d software, then you have 20d bootloader.

The brightness issue is that the brightness is very low. It's still usable.

Yes, that bat script is what I'm talking about. It uses the dd command to overwrite the aboot to 10a version.

 

[uzi2]

The screen won't turn off with this version. The settings are there to adjust the time-out, but it stays on. Even the power button doesn't turn off the screen - just initiates the lock.

Ate you using 4.2.2 or 4.4.2 firmware base?

This thread seems to have been a bit sidetracked with the bootloader questions.
Yes I'm using 4.2.2 base. Is this relevant to the TWRP screen issue or are people on 4.4.2 base seeing the same problem?

 

[auleu]

If you have 20d software, then you have 20d bootloader.

The brightness issue is that the brightness is very low. It's still usable.

Yes, that bat script is what I'm talking about. It uses the dd command to overwrite the aboot to 10a version.

so youre recommanding a downgrade first then install recovery from flashify rather than using the script ? is the brightness issue levels the same as with stock lg rom ? or are the levels even lower?

 

[Deltadroid]

Once you have a custom recovery installed, you can easily switch between firmware bases with a flashable zip.

I'm just saying that if you want to get automatic updates from a stock cm 12 Rom, then you probably want the 10a firmware. Else you will have to install a custom kernel after every update to fix the brightness. The brightness level will be extremely low without it. Much lower then stock levels.

---------- Post added at 04:16 PM ---------- Previous post was at 03:49 PM ----------

This thread seems to have been a bit sidetracked with the bootloader questions.
Yes I'm using 4.2.2 base. Is this relevant to the TWRP screen issue or are people on 4.4.2 base seeing the same problem?

I have never had the screen time out in recovery mode before. I'm using 4.2.2.

 

[uzi2]

I've been doing some testing on the screen time-out issue.
Going back through recent releases, it would appear the bug was introduced with 2.8.2 as 2.8.1 is the most recent version that works as it should.

 

[auleu]

Once you have a custom recovery installed, you can easily switch between firmware bases with a flashable zip.

I'm just saying that if you want to get automatic updates from a stock cm 12 Rom, then you probably want the 10a firmware. Else you will have to install a custom kernel after every update to fix the brightness. The brightness level will be extremely low without it. Much lower then stock levels.

why isnt there an official thread about all of this? seriously for a newcomer like me its hard to gather all of the information necessary to get me up to speed. i only want to update to cm11.

 

[testman86]

@Deltadroid

I have some questions. And I am somehow confused which way to follow.

I got my LG Pad v500 last November, updated to latest Firmware OTA available (520d) and then rooted, flashed TWRP for 4.4.2 aboot and CM11. I have this backlight issue that after first boot in CM 11 Snpashot M12, screen is too dark and I need to switch on/off screen to get a useable screen brightness. As I knew now, I would need a 4.2.2 (510a) aboot version to get better supported CustomRecoverys and CustomRoms, especially if I want to test new CM 12 I need a newer TWRP then the 2.8.0.0 which is available for 4.4.2 aboot. (When I bought the device I just did all OTA and then rooted because I was not knowing that there are differences between this bases and this issues)

You were talking about that it is possible to flash a 10a aboot version if working CustomRecovery is available, like in my case. My problem is if I flash a aboot 10a with my TWRP 2.8.0.0 for 20d base might I run into problems? I think I would need a .zip which will flash the 10a aboot and the proper recovery version at the same time. I know how to use shell in my Ubuntu and adb ist installed, I just do not know how to flash and which versions I should flash

Sorry for my long post, but I have no clue which aboot is "best" and how to flash a proper aboot and recovery at same time... As you can see my device is rooted, unlocked (as said at every boot up) and custom recovery installed.

Just would like to have a "clean" good base to use newest recoverys and ROMs, espcially CM.

Thanks in advance for your help!

 

[Deltadroid]

After you flash the 10a firmware base in the recovery, which contains a new version of aboot, follow these steps exactly:

1) flash latest TWRP (so that the new recovery is installed using your new aboot).
2) reboot the recovery (not into system) so that you reboot into the new recovery you just installed.
3) flash your Rom (so that it installs a new boot (kernel image) against your new aboot.
4) reboot into the system (Android)

The recovery and the kernel image will then be installed using your new aboot BEFORE you try to boot the system.

Otherwise you will get a signature error because a lokified recovery and kernel need to match the currently installed aboot before it will boot properly.

Hope that helps explain it.

---------- Post added at 06:47 PM ---------- Previous post was at 06:25 PM ----------

Use the 4.2.2 firmware base found in the link before, along with twrp 2.8.5.0 in this thread.
http://forum.xda-developers.com/showthread.php?t=2762526

 

[testman86]

Thanks a lot!

I read the whole thread http://forum.xda-developers.com/showthread.php?t=2762526 and got more confused... As I mentioned I am on the latest EU OTA Update 20D right now and as reading in that thread if I would use CWMRecovery I can use my firmware? My point is, which is the "best" way to go or which is the "best" firmware to use? I know understand how to switch between this bases, but as mentioned by you in http://forum.xda-developers.com/showthread.php?t=2762526 the 10A seems to have some troubles, so maybe better use the latest 20D I have from OTA for CM11 or CM12? Would be nice to know among all these .zips from different OTAs US 10B to 20C and so on which is the one which works best

 

[Deltadroid]

The version of TWRP 2.8.5.0 in this thread is for the 4.2.2 base. Also, TWRP 2.8.5.0 is the only recovery that currently supports automatic updates with CM Update tool.

CWM is not affected by the brightness issues, but it is also outdated and doesn't support automatic updates with the CM Update tool.

If you don't mind manually updating and reinstalling a custom kernel after every update, then keeping 20D and CWM 6.0.5.1 is fine.

Both 10a and 20d are fine to use. It all really depends on what you want. The custom kernels require 4.4.2 firmware will give you more updated kernel code. The stock CM kernels require 4.2.2 firmware.

---------- Post added at 11:40 PM ---------- Previous post was at 11:33 PM ----------

10A is 4.2.2 and 20D is 4.4.2. There isn't much difference between 10A, 10B, and 10C. If you decide to go with 4.2.2, then 10A is what CM12 is based on. If you look at the fingerprint in the build.prop in CM12, it identifies the Rom as 10A.