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

[ckret]

2.8 is up for our device too http://techerrata.com/browse/twrp2/awifi

thanks flashed via flashify
working like a charm

 

[json30]

same here,

flashed via flashify and now testing, the dimming on screen at boot in recovery time, seems to got away.

Edit

after I was able to restore a backup previously made with 2.7.1.0, first trouble is with CM nightly updates, it seems that update directly from Android with reboot in recovery and automated flashing is no go.

The error is like this with the latest CM update (20140911) "Error executing updater binary in zip ...." and a path to file an also this "Error installing zip file " and again a path to file.

And it seems neither from TWRP with install command doesn't work.


I think the culprit is flashify app that passes this "palman" info to the update script from cyanogenmod.


EDIT

And neither in 2.7.1.0 (made with flashify) will not work now. same error with "palman" device.

I will try to go back to 2.7.1.0 with flashify

Upon inspection it seems the scrip witch is responsable to pass all the variable at reboot to install procedure is culpable. The message witch take me to this is "This package is for "v500" devices; this is a "palman".
I do not know why it see my table to be a v510 when it is v500 model (and twrp 2.7.1.0 sees like v500).

This file was OK in TWRP 2.7.1.0 with direct update from Android

EDIT

Now got to go back (all ready in update recovery from LG desktop app

 

[Hibble]

I tried the official dd method from teamw.in to flash 2.8, but whenever I wanna try to access recovery I am hanging at the boot screen.

I am on Cyanogenmod and also tried to flash back to 2.7.1, but no success at all..
Does anyone has a hint for me?

 

[legmando33]

I tried the official dd method from teamw.in to flash 2.8, but whenever I wanna try to access recovery I am hanging at the boot screen.

I am on Cyanogenmod and also tried to flash back to 2.7.1, but no success at all..
Does anyone has a hint for me?

Same happened to me as well. I had to return to stock with lg tool and re-root all over again.

Edit: today is my second day owning this tablet.lol

 

[Drgravy]

hope to have some new 2.8.0.0 TWRP builds done tonight if time permits
so... please be patient

 

[jonup]

I updated with Flashify and was able to boot into recovery, however I didn't do much more in there. So for those of you that are having problem flashing ROMs, I cannot guarantee it is working, but recovery did flash fine on my end and it is operational. @json13, did you wipe system/data before trying to flash the ROM? It is a known issue that you need to unmount system or simply reboot recovery after full wipe. The upside, mounting and unmounting system forces to purse deleted data and in effect acts as a nice nand trim.
On the other hand if it was a dirty flash and you were unable to flash then it is a problem with recovery.

Also, I've used Flashify to update recovery every since the first working TWRP recovery for our tablet and haven't had any issue. Unless CM doesn't play well with Flashify, I wouldn't blame it on Flashify for bad recovery.

 

[legmando33]

I updated with Flashify and was able to boot into recovery, however I didn't do much more in there. So for those of you that are having problem flashing ROMs, I cannot guarantee it is working, but recovery did flash fine on my end and it is operational. @json13, did you wipe system/data before trying to flash the ROM? It is a known issue that you need to unmount system or simply reboot recovery after full wipe. The upside, mounting and unmounting system forces to purse deleted data and in effect acts as a nice nand trim.
On the other hand if it was a dirty flash and you were unable to flash then it is a problem with recovery.

Also, I've used Flashify to update recovery every since the first working TWRP recovery for our tablet and haven't had any issue. Unless CM doesn't play well with Flashify, I wouldn't blame it on Flashify for bad recovery.

It seems as if the recovery.img is for palman or something like that, even though file says awifi. I flashed the recovery twice. It is bootable but Anything v500 doesn't flash. Fails.

 

[Drgravy]

OP updated with new builds for both bootloader Enjoy

 

[jonup]

It seems as if the recovery.img is for palman or something like that, even though file says awifi. I flashed the recovery twice. It is bootable but Anything v500 doesn't flash. Fails.

OP updated with new builds for both bootloader Enjoy

The one in my link clearly works with slimkat. @json30 Obviously I am flashing a ROM in the picture below. Reflashed my ROM just to double check.

 

[json30]

@jonup Flashing 2.8.0.0 was OK from flashify , but when I was trying to get any cm update directly from android or from install procedure from TWRP was a no go because "palman"error. So hence my idea of flashify to be the culprit. But it seems it was the build of TWRP from the download link. I will try the new link and report here.

---------- Post added at 03:00 PM ---------- Previous post was at 02:49 PM ----------

it seems there is no new build on TWRP server ( http://techerrata.com/browse/twrp2/awifi) because the date of build for 2.8.0.0 is ''2014-09-10 2:12:57 PDT'' not a a date after 11 September , so where is the new build of this

 

[json30]

now with the report.
link from first post (zip file of TWRP) it seems to work, update of CM from android is working . All seems to be OK, apart a slow boot at first time after update of TWRP, nothing else to mention now.

---------- Post added at 04:45 PM ---------- Previous post was at 04:12 PM ----------

another report from 2.8.0.0 TWRP

1. It seems if you have a usb connected (for charging purposes) and you make a reboot from android or from TWRP you get a boot loop.
2. Booting time in 2.8.0.0. for me was way more long. Exactly at error message it take like an eternity to pass to boot animation from CM 11.
3. key combination to hard reset vol down + power + vol up and again power do not get you in a reboot, it left you with same error on upper left corner and with last message from LG routine to hard reset.

so for this reasons I will get back to 2.7.1.0 for now

 

[BigK]

There is v2.8.0.1 out at http://techerrata.com/browse/twrp2/awifi

Is it ok if I replace recovery.img with the new img file and flash it in recovery mode?

 

[json30]

It is possible to work but I do not know for sure this. my bet for a good install of a new recovery file from thecherrata servers is with Flashify.

but on front page on TWRP site for build 2.8.0.0 the only new info is this :

What's new in 2.8.0.0:

Fix a bug that caused weird graphics and touch issues

none of the issues witch I had with this build was mentioned at solved.

 

[json30]

Report from 2.8.0.1


flashed img file from http://techerrata.com with flashify, reboot in recovery, wipe data,cache, dalvik, reboot system, screen was so dim I need to guess where are things on screen to configure'it.
I was able to restore a nandroid backup with a CM 11 from 12 september.
I will wait a new nightly to try update from android to see if it works now.

the good

-Boot loop with usb connected is gone.
-Slow boot time is gone
-Now it seems we are able to backup recovery partition also in a nandroid backup

 

[json30]

Like I was saying in previous post when update was offered I will try to update from android or from TWRP .
So today one nightly for CM 11 was on update sever, and I try to make the update, but..........no go, neither from Android or directly from TWRP.
Error message is about my tablet being a "palman" device not V500. so the update could not be applied.

Now I am back to 2.7.1.0 from first post on this threat, with this recovery update is working OK from Android
4.4.2-v500-TWRP_2.7.1.0-recovery.zip

 

[Drgravy]

Like I was saying in previous post when update was offered I will try to update from android or from TWRP .
So today one nightly for CM 11 was on update sever, and I try to make the update, but..........no go, neither from Android or directly from TWRP.
Error message is about my tablet being a "palman" device not V500. so the update could not be applied.

Now I am back to 2.7.1.0 from first post on this threat, with this recovery update is working OK from Android
4.4.2-v500-TWRP_2.7.1.0-recovery.zip

The TWRP builds that you find here: http://techerrata.com/browse/twrp2/awifi have the wrong Board naming

The ones in the OP are right
just make sure and grab the right one for the right bootloader

 

[superbar]

Why cant i flash using flashify, everytime it reboots it stuck in logo screen with boot secure error, boot certification verified

Flashed the img file or the zip file from OP but still couldnt get twrp to work

 

[json30]

@Drgravy, thanks for suggestions, with 2.8.0.0 from OP. I flashed from TWRP with install and my experience with this version is this:

Yes it works to update CM11 from within Android via openscript
But, boot times is way much more compared with 2.7.1.0 and also reboot in recovery.

What I do not understand is how the TWRP team doesn't change the files from theirs servers with correct ones.

 

[jonup]

@Drgravy, thanks for suggestions, with 2.8.0.0 from OP. I flashed from TWRP with install and my experience with this version is this:

Yes it works to update CM11 from within Android via openscript
But, boot times is way much more compared with 2.7.1.0 and also reboot in recovery.

What I do not understand is how the TWRP team doesn't change the files from theirs servers with correct ones.

I have 0 issues with the files from the twrp site. My guess is CM messed up something as usual trying to differentiate themselves from AOSP.

 

[json30]

@jonup you try to update CM 11 from within Android with TWRP from their site ?