[RECOVERY] [TWRP 2.8.0.0] [v500] [9-11-2014]

[Scionero]

Thank you, thank you, thank you!! I've been searching for hours how to do this. Your way is so dang simple and worked immediately.

 

[Meakii]

Dim screen

Hi all. I've scanned over many many pages in this thread and can't find an actual answer... Since flashing 2.8.00 whenever I power on or reboot the screen dims on the LG logo so dark I can barely see anything at all. This continues all the way through bootanimation until I turn my screen off and on again. I've tried flashing back to the 2.7 versions but still the same thing remains. Has anybody found a fix at all for this? Thanks in advance. :good:

 

[json30]

read my previous post , use that link

 

[Meakii]

read my previous post , use that link

Thanks I did that but it just flatly refused to boot to recovery from recovery. Instead booting into the ROM. So had to use kdz method back to 4.2.2 and start again. Now that have done that though and upgraded TWRP from 2.6 > 2.7 > 2.8 and just flashed latest Liquidsmooth nightly my dim light boot has disappeared. Took a while to get there but the end result worked out. :good:

Edit: I think because I went back to 4.2.2 and skipped stock 4.4.2 instead to LiquidSmooth 4.4.4 I managed to have sidestep the dimming issue. Hope that helps anyone with the same issue.

 

[TF666]

Links dead

File host seems to be dead. Can you please reupload 4.4.2-v500-TWRP_2.8.0.0-recovery.zip? I'm on stock and cannot install CM11 no matter what I do. Thanks.

 

[json30]

@Drgravy can you make a build from 2.8.1.0. twrp site have this build but like always is for v510 aka palman, and thank for previous builds.

 

[BigK]

v500-TWRP_2.8.1.0-recovery.zip

@Drgravy can you make a build from 2.8.1.0. twrp site have this build but like always is for v510 aka palman, and thank for previous builds.

I replace the recover.img file inside the previous version with the latest one. It works for me.

 

[json30]

@BigK thanks for your intention, but this solution is no go. If you want to update cm to another built you are not able to do this because one error message about your tablet being v510 (palman)version not v500.

 

[MetalMonkey]

I replace the recover.img file inside the previous version with the latest one. It works for me.

Appreciate the effort to update this, but the img is broken for 2.8.1.0 because it hoses the id of the device to palman instead of v500. The 2.8.0.0 previously offered does work tho.

Thanks

 

[BigK]

I'm not sure why it works on mine (pic) :|
@json30, @MetalMonkey: I had the error about wrong id of the device to palman instead of v500 when upgrading to 2.8.0.1. I think they've fixed it in 2.8.1.0!?

 

[json30]

@BigK to install new version of twrp (2.8.1.0) it is possible with procedure described few post up, but when you try to update CM11 OTA you are stopped with that error message.

---------- Post added at 06:14 AM ---------- Previous post was at 06:11 AM ----------

that is because IMG file is again for v510 (palman) tablet, and is promoted as awifi tablet (thing I do not understand why)

 

[ckret]

@Drgravy
can build twrp 2.8.2.0 for us? ty

 

[ecsnead69]

Has anyone installed this with Flashify?

Sent from my LG-VS980 using Tapatalk

 

[Deltadroid]

Has anyone installed this with Flashify?

Sent from my LG-VS980 using Tapatalk

The description of Flashify says that it supports automatic loki support, although I have never tried using Flashify.

So, if you have to lokify the recovery image first with loki_tool, then you might as well flash the recovery.lok file with loki_tool also.

But, the recovery installation script in the twrp package provided here will automatically lokify the recovery image and install the recovery.lok file if you flash it with any custom recovery.

 

[leardinet]

please help me to install on my recovey g pad 4.4.2 V50020d .
V50020_aboot_twrp_v2.zip not work
even changing V50020b in V50020d
I'm going crazy

 

[Zeljko1234]

I would like to change /data to f2fs. According OP, should be possible since 2.7.0.0 but even I'm using 2.8.0.0 I don't have that option. Should I go back to 2.7.1.0?

 

[owenjm]

Help -- no adb, no recovery after flash

Hi,

So, I'm embarrassed, but I managed to clearly flash the wrong recovery from recovery -- I flashed the main linked recovery from TWRP 2.7 over the 4.4.2 base (stupidly thinking that the instructions below the link applied to the link above them). And now I seem to have lost both recovery and ADB support, and my tablet won't shutdown (it just reboots on power off) ... this seems fairly bad!

Does anyone have any suggestions? I've never encountered this situation before, and as the GPad doesn't have a fastboot mode I seem a little stuck for means of getting the right recovery back onto it ...!

Any help or advice would be greatly appreciated at this point

 

[Zeljko1234]

Flashify maybe?

 

[owenjm]

Flashify maybe?

Sadly, no ... flashify just uses your builtin recovery to do the flashing, it seems -- not much use if your inbuilt recovery doesn't work

I've also tried CM's flash_image via wireless ADB (the only way I've managed to get adb working), but that gives me a very imformative "failed with error: -1" on the recovery img files I've tried so far ...

Any other thoughts? Really don't want to have to go through the whole LG software restore and root again (if I can even remember how to do it after all this time ...!)

---------- Post added at 10:17 AM ---------- Previous post was at 09:56 AM ----------

Sadly, no ... flashify just uses your builtin recovery to do the flashing, it seems -- not much use if your inbuilt recovery doesn't work

Update: Flashify doesn't work, but Rasher does. However, now I need a recovery.img file that works (I've tried TWRP's official one, but that still won't boot -- I get a "boot certification verify" error on the boot screen) ...

 

[Deltadroid]

Sadly, no ... flashify just uses your builtin recovery to do the flashing, it seems -- not much use if your inbuilt recovery doesn't work

I've also tried CM's flash_image via wireless ADB (the only way I've managed to get adb working), but that gives me a very imformative "failed with error: -1" on the recovery img files I've tried so far ...

Any other thoughts? Really don't want to have to go through the whole LG software restore and root again (if I can even remember how to do it after all this time ...!)

---------- Post added at 10:17 AM ---------- Previous post was at 09:56 AM ----------



Update: Flashify doesn't work, but Rasher does. However, now I need a recovery.img file that works (I've tried TWRP's official one, but that still won't boot -- I get a "boot certification verify" error on the boot screen) ...

I think you need to patch the recovery.img to recovery.lok with the loki_tool before you are able to flash it with Flashify or Rasher. Although, the description of Flashify does mention that it is supposed to have automatic loki support (whatever that means).

Using a Terminal Emulator, you should be able to patch the recovery.img (to create recovery.lok) and also install it through loki_tool. Take a look at the CWM thread in this section which has step by step instructions for doing this.