Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[RECOVERY] TWRP 2.6.3.1 V510 Palman LG G Pad 8.3 GPE

OP djkinetic

11th December 2013, 08:38 PM   |  #1  
First thanks to drgravy who compiled this TWRP build for the LG G Pad 8.3 GPE (V510); device name Palman, a link to the official TWRP download page will be posted once the appropriate section for (Palman) has been created.

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

Phone look:

Tablet look:



CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks

CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks

CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks

Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.

Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.

DISCLAIMER:
I nor anyone else is responsible for what you do to your device.
but if something goes wrong I will do my best to help


Download:

TWRP 2.6.3.1 V510 Palman

How to flash:

Since this is a GPE Tab simply boot your device into fastboot. Easiest way is to do adb reboot bootloader.
Once booted into the bootloader simply issue this command:

fastboot flash recovery palman.img

Once done reboot into recovery and you should be greeted with TWRP.

CREDITS:

@Dees_Troy and team win for this wonderful recovery
Last edited by djkinetic; 11th December 2013 at 08:40 PM.
The Following 7 Users Say Thank You to djkinetic For This Useful Post: [ View ]
12th December 2013, 08:55 AM   |  #2  
Senior Member
USA
Thanks Meter: 305
 
1,710 posts
Join Date:Joined: Jun 2007
More
Confirmed working on GPE version.

Unlocok bootloader and flash recovery or you can just do "fastboot boot palman.img" and it will boot in recovery without flashing it (so you get to keep stock recovery in case you need to run an OTA later).
13th December 2013, 11:19 AM   |  #3  
lasset's Avatar
Senior Member
Flag Malmo
Thanks Meter: 21
 
202 posts
Join Date:Joined: Jan 2005
More
Hi

I get the message "Waiting for the device", so how get the device in fastboot mode?

Thanks[COLOR="Silver"]

---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
Last edited by lasset; 13th December 2013 at 11:20 AM. Reason: Dubble message
13th December 2013, 03:36 PM   |  #4  
SnowPluralism's Avatar
Recognized Contributor
Flag Inside Your Mind
Thanks Meter: 1,394
 
1,677 posts
Join Date:Joined: Jan 2012
More
Enable usb debugging or check if u have drivers

Enviado do meu GT-I9300 através de Tapatalk
14th December 2013, 05:10 PM   |  #5  
Senior Member
Thanks Meter: 93
 
514 posts
Join Date:Joined: Feb 2011
Quote:
Originally Posted by Ver3go

Enable usb debugging or check if u have drivers

Enviado do meu GT-I9300 através de Tapatalk

Sorry for the dumb question, but where do I get the drivers for the GPE? I used Dalingrin's easy root script for the LGE, but "adb shell" doesn't work with that minimal adb, so I'm assuming I need to grab a different driver?

UPDATE: Still looking for the drivers. I downloaded the latest ADT and had it install the Google USB Driver, but still neither "adb shell" nor "fastboot devices" works properly. Just to answer the obvious question, yes, I've enabled USB Debugging in Developer Options. Any thoughts on how I can get past this hurdle so that I can get to a point where I can root a GPE device?

UPDATE 2: Okay, I figured it out and have GPE all nice and rooted now! Basically just follow the instructions to root a Nexus 5 but use the recovery image on this thread and you should be golden!
Last edited by SCWells72; 15th December 2013 at 10:14 PM.
17th December 2013, 10:30 PM   |  #6  
Senior Member
Thanks Meter: 93
 
514 posts
Join Date:Joined: Feb 2011
The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:

Quote:

This package is for "palman" devices; this is a "v 500".

Is there any easy way to fix that?
Last edited by SCWells72; 17th December 2013 at 10:38 PM.
17th December 2013, 11:32 PM   |  #7  
Senior Member
Flag Grand Prairie, TX
Thanks Meter: 56
 
111 posts
Join Date:Joined: Jun 2013
More
Quote:
Originally Posted by SCWells72

The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:



Is there any easy way to fix that?

I might have an easy answer for you, give me a few minutes to try it out first.

---------- Post added at 04:32 PM ---------- Previous post was at 04:06 PM ----------

Quote:
Originally Posted by SCWells72

The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:



Is there any easy way to fix that?

I think you can do this two ways, flash back to the stock recovery, or just run the stock recovery once from the bootloader. Flashing back to the stock recovery is probably the safest option, however I have an idea if you don't want to have to go back and forth.

Disclaimer, I'm an NOT expert with this so it may not work.....
Ok, for either option you'll need the stock recovery. You can download it from HERE (Stolen from AutoPrime's post).

I recommend putting the update ZIP and recovery image file in a folder of your root path (for me "C:\android\")

Here's my idea, have fastboot just boot the stock recovery once.

Make sure ADB debugging is enabled in "Developer Options"

Connect your USB cable and run

Code:
adb reboot bootloader
Your tablet should reboot and your should see the bootloader screen, once you see the screen run

Code:
fastboot boot C:\android\17-recovery.img
fastboot should show you progress indicator and once it is finished your tablet should see a red exclamation mark. press the power button and then the vol. up button. This should show options 1. Reboot System 2. ADB Sideload, use the volume keys to select adb sideload then press the power key to select.

then
Code:
adb sideload C:\android\a0bd45922b5958a38acef76f577f527268ef90db.signed-KRT16O.L004_user-KOT49H.L004_user_update.zip
I think it will work, not sure if it will keep TWRP or overwrite it. Like I said earlier, I'm not an expert.
The Following User Says Thank You to Mixinitup4Christ For This Useful Post: [ View ]
18th December 2013, 12:29 AM   |  #8  
katsika's Avatar
Senior Member
Flag Athens
Thanks Meter: 52
 
217 posts
Join Date:Joined: Oct 2013
More
Quote:
Originally Posted by SCWells72

The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:



Is there any easy way to fix that?

OTA updates are not working with a custom recovery like twrp. Either flash back to stock or wait for the developers to compile and release the updates as zip packages that you can flash from the custom recovery menu. Look what a developer said about this here http://forum.xda-developers.com/show...4&postcount=31
18th December 2013, 04:33 AM   |  #9  
Archon810's Avatar
Senior Member
Flag San Francisco
Thanks Meter: 74
 
370 posts
Join Date:Joined: Feb 2010
More
I flashed TWRP after applying the latest OTA 4.4.2, and now it won't boot - just reboots into TWRP and has all kinds of errors about not being able to mount /data.

Any ideas for recovering from this?

Screenshot when trying to factory reset: http://i.imgur.com/Zyf1507.jpg

Edit: Had TWRP reformat /data, still nothing.
Last edited by Archon810; 18th December 2013 at 04:51 AM.
18th December 2013, 05:18 AM   |  #10  
Quote:
Originally Posted by Archon810

I flashed TWRP after applying the latest OTA 4.4.2, and now it won't boot - just reboots into TWRP and has all kinds of errors about not being able to mount /data.

Any ideas for recovering from this?

Screenshot when trying to factory reset: http://i.imgur.com/Zyf1507.jpg

Edit: Had TWRP reformat /data, still nothing.

Odd, I flashed the 4.4.2 OTA after restoring stock recovery, it updated then after the updated I flashed TWRP back, and am having no such issue.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes