• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[DEV] thread on LG G Pad 7.0/8.0/10.1

Search This thread

paperWastage

Senior Member
Mar 18, 2009
1,000
496
NJ
Thought I'll create a thread for developers on LG G Pad 7.0/8.0/10.1

I'll try to keep it updated as best as I can. If I forget/get to busy, PM me and tell me what to change

Help Wanted:
If you own a LG G Pad 8.0/10.1, mind doing the following things? It'll help with kernel development/porting CM11/other ROMs


  • Dump partition list/info : instructions
  • Dump /system/build.prop
Possibly need root for stuff below
  • Dump aboot, boot and recovery partition : need partition list first before posting instructions. probably instructions below will continue to work
    Code:
    dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
    
    dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
    
    dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img

 
Last edited:

Hammerhand.17

Senior Member
May 29, 2010
607
107
Winterfell
Thought I'll create a thread for developers on LG G Pad 7.0/8.0/10.1

I'll try to keep it updated as best as I can. If I forget/get to busy, PM me and tell me what to change

Help Wanted:
If you own a LG G Pad 7.0/8.0/10.1, mind doing the following things? It'll help with kernel development/porting CM11/other ROMs


  • Dump partition list/info : instructions
  • Dump /system/build.prop
Possibly need root for stuff below
  • Dump aboot, boot and recovery partition : need partition list first before posting instructions. probably instructions below will continue to work
    Code:
    dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
    
    dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
    
    dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img



Hi, I own a G pad 7.0. It seems that I am the only one in the world :) I'm gonna try to help a little:

1. Dump partition:

-lrwxrwxrwx root root 1970-03-05 03:01 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-03-05 03:01 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-03-05 03:01 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-03-05 03:01 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-03-05 03:01 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-03-05 03:01 cust -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-03-05 03:01 drm -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-03-05 03:01 eksst -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-03-05 03:01 encrypt -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-03-05 03:01 factory -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-03-05 03:01 fota -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-03-05 03:01 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-03-05 03:01 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-03-05 03:01 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-03-05 03:01 laf -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-03-05 03:01 misc -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-03-05 03:01 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-03-05 03:01 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-03-05 03:01 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-03-05 03:01 mpt -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-03-05 03:01 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-03-05 03:01 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-03-05 03:01 rct -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-03-05 03:01 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-03-05 03:01 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-03-05 03:01 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-03-05 03:01 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-03-05 03:01 sbl1b -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-03-05 03:01 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-03-05 03:01 sns -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-03-05 03:01 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-03-05 03:01 system -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-03-05 03:01 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-03-05 03:01 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-03-05 03:01 userdata -> /dev/block/mmcblk0p34

- Dump build.prop, boot, aboot and recovery:

http://www37.zippyshare.com/v/4146966/file.html
http://www37.zippyshare.com/v/66268524/file.html
http://www37.zippyshare.com/v/51126864/file.html
http://www37.zippyshare.com/v/44186789/file.html
http://www37.zippyshare.com/v/85458029/file.html


I think for now nothing can be done with it (there is no recovery yet). I hope something can be done.
 

paperWastage

Senior Member
Mar 18, 2009
1,000
496
NJ
Hi, I own a G pad 7.0. It seems that I am the only one in the world :) I'm gonna try to help a little:

1. Dump partition:

-lrwxrwxrwx root root 1970-03-05 03:01 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-03-05 03:01 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-03-05 03:01 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-03-05 03:01 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-03-05 03:01 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-03-05 03:01 cust -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-03-05 03:01 drm -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-03-05 03:01 eksst -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-03-05 03:01 encrypt -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-03-05 03:01 factory -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-03-05 03:01 fota -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-03-05 03:01 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-03-05 03:01 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-03-05 03:01 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-03-05 03:01 laf -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-03-05 03:01 misc -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-03-05 03:01 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-03-05 03:01 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-03-05 03:01 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-03-05 03:01 mpt -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-03-05 03:01 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-03-05 03:01 persist -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-03-05 03:01 rct -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-03-05 03:01 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-03-05 03:01 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-03-05 03:01 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-03-05 03:01 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-03-05 03:01 sbl1b -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-03-05 03:01 sdi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-03-05 03:01 sns -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-03-05 03:01 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-03-05 03:01 system -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-03-05 03:01 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-03-05 03:01 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-03-05 03:01 userdata -> /dev/block/mmcblk0p34

- Dump build.prop, boot, aboot and recovery:

http://www37.zippyshare.com/v/4146966/file.html
http://www37.zippyshare.com/v/66268524/file.html
http://www37.zippyshare.com/v/51126864/file.html
http://www37.zippyshare.com/v/44186789/file.html
http://www37.zippyshare.com/v/85458029/file.html


I think for now nothing can be done with it (there is no recovery yet). I hope something can be done.

thanks for this.

@icedmayhem also provided similar files over PM, forgot to post updates here...

anyways, it looks like this device has the patched aboot source code.

loki won't work anymore (loki provides a way for us to bypass the locked bootloader to load non-stock recovery/kernels. This means there isn't an easy way to boot a custom recovery(TWRP) or custom ROM.

Can you check if you can unlock the bootloader? Don't know if LG provides a process to do this easily (for GPE / non-GPE devices)

strings aboot.img | fgrep overlap
The erase group overlaps the max requested for erase
kernel/ramdisk addresses overlap with aboot addresses.
Device tree addresses overlap with aboot addresses.
Boot image buffer address overlaps with aboot addresses.
Signature read buffer address overlaps with aboot addresses.
 
  • Like
Reactions: EuphoricFuzion

idelgado782

Senior Member
Jul 29, 2008
822
152
Union, NJ

Impala126

New member
Aug 15, 2014
3
0
Here's the link to the purpledrake thread. Once you download and install on your computer make sure the gpad USB mode is on ptp mode.

http://forum.xda-developers.com/showthread.php?p=54254055

No matter what, I can never stay away from android for long.

Yup worked like a champ. Turned on air plane mode, then usb debugging and then ptp. But I had to go to a term win on win7 and run bat file from there. wouldn't run with admin rights from windows explore.
 

neo4uo

Senior Member
Nov 27, 2010
943
280
Alabama
Has anyone tried or been successful pulling a factory image file for the LG V410 which is the AT&T G Pad 7.0? I tried the other day but there was not an image on their servers at that time :(
 

Top Liked Posts

  • There are no posts matching your filters.
  • 20
    TWRP Recovery for V410

    Here a copy of TWRP 2.8.1.0 for the V410 built by me.

    To install, unzip and install it to your tablet either via dd or fastboot to the recovery partition.

    Please also say thank you to @savoca for the kernel touch hack that makes TWRP touch work on the V400 / V410 :)
    18
    Progress!!!!!!

    Wow it works with v410 ?, i stuck with the recovery now and team codefire hasn't replied my email yet, let's wait for it.

    Progress!!!!!!


    I managed to boot into CWM :) on my (LG G Pad 7.0) aka (LG v410) aka (e7lte) aka (e7lteatt). Yeap this tablet has more, than anything else.

    I still have to fix the fstab making some parts are not mounting correctly ( ex: /sdcard wont mount. I have to manually mount the partition ).

    Until I can fix I wont publish, I dont want people blaming me for their broken devices. :)

    @bangprovn
    You where in the right path but your recovery image is missing dtb ( Device Tree Blob ) and it has the wrong fstab values. PM me to explain in detail what I did to make it work. Booting recovery from flashboot does not requieres img to be bumped, but if boot from device it still required to be bumped.

    ***People im still a noob at compiling android from source code, so don't expect any custom rom from me... making recovery work is one thing, compiling android complete is another thing. ***
    15
    Not sure if anyone noticed but I posted the Stock ROM over in the Android Development section.

    Also I'm working on a stock based ROM that is de-bloated, deodexed , zip aligned, rooted, etc.
    12
    I have dumped aboot , abootb , boot and recovery.
    here it is.
    Dropbox[dot][com]/s/ski2gwx904bsiqh/Misc.7z?dl=0

    Meanwhile , i was editing framework-res.apk and that has led to the pad being stuck at the at and t logo . Any ideas on how i can boot into stock recovery or adb the stock apk ? I am able to boot into download mode .
    11
    Everything working TWRP - stand by...