Is there anyone out there that can help the members of the LG Optimus L5 II unlock there bootloader?
here is our phone on GSM
http://www.gsmarena.com/lg_optimus_l5_ii_e460-5293.php
the device is mt6575
the device is locked by LG.
As far as i understand the uboot partition is where the security check is comming from.
I cannot use spflash tool as it does not see my device.
so my question is this.
the LG optimus L3 II have managed to unlock there bootloader using an aboot img fro the LG optimus L5
could we replace our uboot img with the L3 II aboot img?
alternatively could we use a uboot img from another mt6575 device
my partition table is as follows
Code:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
ebr2 0x0000000000080000 0x0000000000100000 2 /dev/block/mmcblk0
misc2 0x0000000000800000 0x0000000000180000 2 /dev/block/mmcblk0
pmt 0x0000000000400000 0x0000000000980000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000d80000 2 /dev/block/mmcblk0
seccfg 0x0000000000080000 0x0000000001080000 2 /dev/block/mmcblk0
uboot 0x0000000000080000 0x0000000001100000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000001180000 2 /dev/block/mmcblk0
recovery 0x0000000000700000 0x0000000001780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000001e80000 2 /dev/block/mmcblk0p2
misc 0x0000000000080000 0x0000000002480000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000002500000 2 /dev/block/mmcblk0
expdb 0x0000000000100000 0x0000000002800000 2 /dev/block/mmcblk0
persist_lg 0x0000000000800000 0x0000000002900000 2 /dev/block/mmcblk0p3
persist 0x0000000000600000 0x0000000003100000 2 /dev/block/mmcblk0p4
mpt 0x0000000001600000 0x0000000003700000 2 /dev/block/mmcblk0p5
lgfota 0x0000000000a00000 0x0000000004d00000 2 /dev/block/mmcblk0
swap 0x0000000000a00000 0x0000000005700000 2 /dev/block/mmcblk0p6
rct 0x0000000000100000 0x0000000006100000 2 /dev/block/mmcblk0
android 0x0000000043c00000 0x0000000006200000 2 /dev/block/mmcblk0p7
cache 0x0000000013600000 0x0000000049e00000 2 /dev/block/mmcblk0p8
usrdata 0x0000000088700000 0x000000005d400000 2 /dev/block/mmcblk0p9
fat 0x0000000000b00000 0x00000000e5b00000 2 /dev/block/mmcblk0p10
bmtpool 0x0000000000a00000 0x00000000ff9f0050 2 /dev/block/mmcblk0
how would I dd uboot partition if it is on the same block as others.
I thank you for your help in advanced.
slipsystem said:
Is there anyone out there that can help the members of the LG Optimus L5 II unlock there bootloader?
here is our phone on GSM
http://www.gsmarena.com/lg_optimus_l5_ii_e460-5293.php
the device is mt6575
the device is locked by LG.
As far as i understand the uboot partition is where the security check is comming from.
I cannot use spflash tool as it does not see my device.
so my question is this.
the LG optimus L3 II have managed to unlock there bootloader using an aboot img fro the LG optimus L5
could we replace our uboot img with the L3 II aboot img?
alternatively could we use a uboot img from another mt6575 device
my partition table is as follows
Code:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
ebr2 0x0000000000080000 0x0000000000100000 2 /dev/block/mmcblk0
misc2 0x0000000000800000 0x0000000000180000 2 /dev/block/mmcblk0
pmt 0x0000000000400000 0x0000000000980000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000d80000 2 /dev/block/mmcblk0
seccfg 0x0000000000080000 0x0000000001080000 2 /dev/block/mmcblk0
uboot 0x0000000000080000 0x0000000001100000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000001180000 2 /dev/block/mmcblk0
recovery 0x0000000000700000 0x0000000001780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000001e80000 2 /dev/block/mmcblk0p2
misc 0x0000000000080000 0x0000000002480000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000002500000 2 /dev/block/mmcblk0
expdb 0x0000000000100000 0x0000000002800000 2 /dev/block/mmcblk0
persist_lg 0x0000000000800000 0x0000000002900000 2 /dev/block/mmcblk0p3
persist 0x0000000000600000 0x0000000003100000 2 /dev/block/mmcblk0p4
mpt 0x0000000001600000 0x0000000003700000 2 /dev/block/mmcblk0p5
lgfota 0x0000000000a00000 0x0000000004d00000 2 /dev/block/mmcblk0
swap 0x0000000000a00000 0x0000000005700000 2 /dev/block/mmcblk0p6
rct 0x0000000000100000 0x0000000006100000 2 /dev/block/mmcblk0
android 0x0000000043c00000 0x0000000006200000 2 /dev/block/mmcblk0p7
cache 0x0000000013600000 0x0000000049e00000 2 /dev/block/mmcblk0p8
usrdata 0x0000000088700000 0x000000005d400000 2 /dev/block/mmcblk0p9
fat 0x0000000000b00000 0x00000000e5b00000 2 /dev/block/mmcblk0p10
bmtpool 0x0000000000a00000 0x00000000ff9f0050 2 /dev/block/mmcblk0
how would I dd uboot partition if it is on the same block as others.
I thank you for your help in advanced.
Click to expand...
Click to collapse
Ofcourse SPFlash can see the device - use COM port mode instead of USB, and You should put the phone in BL mode + installed LG United mobile driver etc. I have all the partitions in IMG files from my E440 - L4II, even if you make a dump of the uboot partition i think its not possible to remove the security, the cause: it is a binary, to do so, you need the source code of the bootloader... Or at least that's what I think it is... I may be wrong for the last one. Now about using uboot from another device: NO, never. uboot does a lot of the initialization of the system's hardware: RIL, Radio chips, LCD, keys, cameras, self-tests and so on, since the motherboards in different phones are different, the configuration of the bootloader is supposed to be, too.
So did anyone unlock the BL on the E455 ?
ghatothkach said:
So did anyone unlock the BL on the E455 ?
Click to expand...
Click to collapse
Yes, I have unlocked bootloader for E455 model.
Also I have beta CWM for this model (backup worked)
But I very bad speak english and don't have many post on this forum that post link on file.
please help
i have a kazam trooper x4.5 i tried to do system update over ota but it fails but don't no why i have found this log file
Starting recovery on Thu Aug 28 10:05:19 2014
Partition Information:
preloader 0x0000000000600000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000001d80000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0
sec_ro 0x0000000000040000 0x0000000002980000 2 /dev/block/mmcblk0
misc 0x0000000000080000 0x00000000029c0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000002a40000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000002d40000 2 /dev/block/mmcblk0
android 0x0000000028a00000 0x0000000003740000 2 /dev/block/mmcblk0p4
cache 0x0000000017800000 0x000000002c140000 2 /dev/block/mmcblk0p5
usrdata 0x0000000052c00000 0x0000000043940000 2 /dev/block/mmcblk0p6
fat 0x0000000051440000 0x0000000096540000 2 /dev/block/mmcblk0p7
bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p5 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk0p7 0
7 /system ext4 /dev/block/mmcblk0p4 (null) 0
I:no boot messages
locale is [(null)]
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 854)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
installing_text: (1 x 1 @ 1896)
erasing_text: (1 x 1 @ 1599)
no_command_text: (1 x 1 @ 1599)
error_text: (1 x 1 @ 1599)
Ielta package path name: /data/data/com.redbend.dmClient/files/vdm_update
I:Setting recovery boot...
I:boot.command=boot-recovery
I:boot.recovery=recovery
I:chilid return code:62I:Resetting recovery boot...
I:boot.command=
I:boot.recovery=
I:local update package not exist /sdcard/update-gmobi.zip
I:android_reboot(ANDROID_RB_RESTART)
Rebooting...
Hi there,
I'm sorry but we don't have a forum dedicated to your phone, so you cant post your question in generaql forum for Q&A:
> General discussion > Questions and Answers
or
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck
Thanks
please help
i have a kazam trooper x4.5 i tried to do system update over ota but it fails but don't no why i have found this log file
Starting recovery on Thu Aug 28 10:05:19 2014
Partition Information:
preloader 0x0000000000600000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000001d80000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0
sec_ro 0x0000000000040000 0x0000000002980000 2 /dev/block/mmcblk0
misc 0x0000000000080000 0x00000000029c0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000002a40000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000002d40000 2 /dev/block/mmcblk0
android 0x0000000028a00000 0x0000000003740000 2 /dev/block/mmcblk0p4
cache 0x0000000017800000 0x000000002c140000 2 /dev/block/mmcblk0p5
usrdata 0x0000000052c00000 0x0000000043940000 2 /dev/block/mmcblk0p6
fat 0x0000000051440000 0x0000000096540000 2 /dev/block/mmcblk0p7
bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p5 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk0p7 0
7 /system ext4 /dev/block/mmcblk0p4 (null) 0
I:no boot messages
locale is [(null)]
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 854)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
installing_text: (1 x 1 @ 1896)
erasing_text: (1 x 1 @ 1599)
no_command_text: (1 x 1 @ 1599)
error_text: (1 x 1 @ 1599)
Ielta package path name: /data/data/com.redbend.dmClient/files/vdm_update
I:Setting recovery boot...
I:boot.command=boot-recovery
I:boot.recovery=recovery
I:chilid return code:62I:Resetting recovery boot...
I:boot.command=
I:boot.recovery=
I:local update package not exist /sdcard/update-gmobi.zip
I:android_reboot(ANDROID_RB_RESTART)
Rebooting...
Good day,
I confess, I bricked my device and require assistance in fixing it. I should shoot myself in the foot for not making complete firmware backup
Background:
I altered a partition size and using adb fdisk and after the device reboot, my tablet doesn't want to boot. When I connect charger, no charging animation.
When I connect device to PC via USB, Windows still pics up the device for a few seconds.
Current situation and what I have available:
I have used SP Flash Tool and it can still communicate with the device, I just cannot use MTK Droid Tools any more since device cannot load adb.
The stock firmware is not avail for download on Fondi's website (although the firmware for the T702 is) and I emailed them and they only offered me a link to download the user guide.
The tabled has MT6582 (MT6582 S00) chip and uses a scatter file to map the partition layout for SP Flash Tool to "download" the firmware to it.
I've looked online for scatter files matching the chip but based on the info I have of the original partition layout, there are some discrepancies and i'm a bit cautious in using that/those files to format the partitions.
Before my tablet brick, I did manage to connect it to my PC and opened MTK Droid Tools which collected some info about the tab and partitions, and it saved the info to it's log file which I can still access.
I also used a scatter file I got online for the same chip to in SP Flash Tools to "read back" (rom dump) the data on the phones memory (all partitions) and have this 2GB file (ROM_0) and based on quick searches using Hex Edit, confirmed that it did indeed get the files stored in the partitions.
Requirement:
I need help creating a scatter file from using MTK Droid Tools' partition info in log file and extracting the info stored in partitions (using Hex Edit) in the rom dup so that I can format the tablet's memory and restore the data inside the partitions. This should take me back to the point before I messed around with the partitions and tablet should be working again
Here's the log file from MTK Droid Tools:
17/10/14 10:22:46 -----------Start------------ v2.5.3 (1390155029) 19.01.2014 18:10:29
17/10/14 10:22:47 UserLanguage =English
17/10/14 10:22:51 * daemon not running. starting it now on port 5037 *
17/10/14 10:22:51 * daemon started successfully *
17/10/14 10:22:57 Last version v2.5.3
17/10/14 10:22:57 Maked 1387564576
17/10/14 10:22:57 URL http://dfiles.ru/files/ne1gnposp
17/10/14 10:23:07
--->>> Connect to device <<<---
17/10/14 10:23:07 /data/local/tmp/zzz/recovery: No such file or directory
17/10/14 10:23:08 lrwxrwxrwx 1 root root 28 Oct 17 10:21 /data/local/tmp/zzz/busybox -> /data/local/tmp/zzz/recovery
17/10/14 10:23:08 /system/etc/firmware/modem_1_wg_n.img
17/10/14 10:23:08 MT6582_S00
17/10/14 10:23:08 3+0 records out
17/10/14 10:23:08 12 bytes (12B) copied, 0.016154 seconds, 742B/s
17/10/14 10:23:08 Hardware : MT6582
17/10/14 10:23:08 Part_Name Size StartAddr Type MapTo
17/10/14 10:23:08 preloader 0x0000000001400000 0x0000000000000000 2 /dev/misc-sd
17/10/14 10:23:08 mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
17/10/14 10:23:08 ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
17/10/14 10:23:08 pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0
17/10/14 10:23:08 nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0
17/10/14 10:23:08 protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2
17/10/14 10:23:08 protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3
17/10/14 10:23:08 seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0
17/10/14 10:23:08 uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0
17/10/14 10:23:08 bootimg 0x0000000000600000 0x0000000001d80000 2 /dev/block/mmcblk0
17/10/14 10:23:08 recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0
17/10/14 10:23:08 sec_ro 0x0000000000600000 0x0000000002980000 2 /dev/block/mmcblk0p4
17/10/14 10:23:08 misc 0x0000000000080000 0x0000000002f80000 2 /dev/block/mmcblk0
17/10/14 10:23:08 logo 0x0000000000300000 0x0000000003000000 2 /dev/block/mmcblk0
17/10/14 10:23:08 ebr2 0x0000000000080000 0x0000000003300000 2 /dev/block/mmcblk0
17/10/14 10:23:08 expdb 0x0000000000a00000 0x0000000003380000 2 /dev/block/mmcblk0
17/10/14 10:23:08 android 0x000000002bc00000 0x0000000003d80000 2 /dev/block/mmcblk0p5
17/10/14 10:23:08 cache 0x0000000007e00000 0x000000002f980000 2 /dev/block/mmcblk0p6
17/10/14 10:23:08 usrdata 0x0000000040000000 0x0000000037780000 2 /dev/block/mmcblk0p7
17/10/14 10:23:08 fat 0x000000006d5a0000 0x0000000077780000 2 /dev/block/mmcblk0p8
17/10/14 10:23:08 bmtpool 0x0000000001500000 0x00000000febf00a8 2 /dev/block/mmcblk0
17/10/14 10:23:08 Part_Nameartition name you should open;
17/10/14 10:23:08 Size:size of partition
17/10/14 10:23:08 StartAddr:Start Address of partition;
17/10/14 10:23:08 Type:Type of partition(MTD=1,EMMC=2)
17/10/14 10:23:08 MapTo:actual device you operate
17/10/14 10:23:08 rootfs on / type rootfs (ro,relatime)
17/10/14 10:23:08 tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
17/10/14 10:23:08 devpts on /dev/pts type devpts (rw,relatime,mode=600)
17/10/14 10:23:08 proc on /proc type proc (rw,relatime)
17/10/14 10:23:08 sysfs on /sys type sysfs (rw,relatime)
17/10/14 10:23:08 none on /acct type cgroup (rw,relatime,cpuacct)
17/10/14 10:23:08 tmpfs on /mnt/secure type tmpfs (rw,relatime,mode=700)
17/10/14 10:23:08 tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
17/10/14 10:23:08 tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
17/10/14 10:23:08 none on /dev/cpuctl type cgroup (rw,relatime,cpu)
17/10/14 10:23:08 /[email protected] on /system type ext4 (ro,noatime,noauto_da_alloc,commit=1,data=ordered)
17/10/14 10:23:08 /[email protected] on /data type ext4 (rw,nosuid,nodev,noatime,discard,noauto_da_alloc,d ata=ordered)
17/10/14 10:23:08 /[email protected] on /cache type ext4 (rw,nosuid,nodev,noatime,discard,noauto_da_alloc,d ata=ordered)
17/10/14 10:23:08 /[email protected]_f on /protect_f type ext4 (rw,nosuid,nodev,noatime,nodelalloc,noauto_da_allo c,commit=1,data=ordered)
17/10/14 10:23:08 /[email protected]_s on /protect_s type ext4 (rw,nosuid,nodev,noatime,nodelalloc,noauto_da_allo c,commit=1,data=ordered)
17/10/14 10:23:08 /dev/block/loop0 on /mnt/cd-rom type iso9660 (ro,relatime)
17/10/14 10:23:09 Model : T708B
17/10/14 10:23:09 Build number : ALPS.JB5.TABLET.MP.V1
17/10/14 10:23:09 Build date UTC : 20140813-145255
17/10/14 10:23:09 Android v : 4.2.2
17/10/14 10:23:09 ls: /system/recovery-from-boot.p: No such file or directory
17/10/14 10:23:09 Kernel v : 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Wed Aug 13 22:49:11 CST 2014
17/10/14 10:23:09 --- ROOT Shell
17/10/14 10:23:09 LCD Driver IC : 1-tf070mc124_dsi
17/10/14 10:23:09 drwxrwxrwx 2 root root 4096 Oct 17 10:21 zzz
17/10/14 10:23:09 Baseband v: MOLY.WR8.W1315.MD.WG.MP.V12, 2014/05/29 15:20
17/10/14 11:15:27 --- Disconnect from device
I'm sure I cannot attach nor print the rom dump as the file is about 2GB big.
If you require more info then I would be happy to provide.
I really appreciate any help.
Tnx.
UPDATE
I added ".img" to the ROM_0 dump I mentioned above and used SP Flash Tool's "Write Memory" option to write the file to EMMC starting at address 0x0 till the length of the file.
This took my tab back to the point after I changed the partitions.
The Fondi is now powering up (screen switches on), charging and I can get into the recovery, fastboot mode and normal boot. Only thing is it is stuck on logo during normal mode. I believe this is due to partition changes.
I'm now looking for a way to reverse the partition changes I made...
There are plenty of tools that backup a selection of "top-level" partitions (system, data, etc) but is there any way to dump and restore the entire EMMC?
Can EMMC Raw Tool by unbrickandroid.com or HDDRawCopy by hddguru.com be used to reliably backup and restore the ~ entire ~ EMMC of a Samsung Galaxy Note 5 SM-920C?
If you wish to be terse, a link to a thread on the state of play of EMMC backups would also be appreciated.
The Android filesystem is substantially more compartmentalized than that of most desktop operating systems, and the tools to make backups reflect that. Some backup only user data, some include apps with that, some include the system with that, some include EFS with that, some include every hidden partition with that and some can backup sector-by-sector. To increase confusion, exactly what apps or methods include isn't obvious. The NANDroid backup standard which is regularly referred to doesn't appear to be a single standard but a portmanteau for a group of generally related methods which are frequently not interchangable due to proprietary formats in which files are stored. And so further.
A typical Android filesystem might include these partitions:
Code:
Part_Name Size StartAddr Type MapTo Region
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd BOOT_1
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0 USER
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1 USER
pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0 USER
nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0 USER
protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2 USER
protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3 USER
seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0 USER
uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0 USER
bootimg 0x0000000001000000 0x0000000001d80000 2 /dev/block/mmcblk0 USER
recovery 0x0000000001000000 0x0000000002d80000 2 /dev/block/mmcblk0 USER
sec_ro 0x0000000000600000 0x0000000003d80000 2 /dev/block/mmcblk0p4 USER
misc 0x0000000000080000 0x0000000004380000 2 /dev/block/mmcblk0 USER
logo 0x0000000000300000 0x0000000004400000 2 /dev/block/mmcblk0 USER
expdb 0x0000000000a00000 0x0000000004700000 2 /dev/block/mmcblk0 USER
tee1 0x0000000000500000 0x0000000005100000 2 /dev/block/mmcblk0 USER
tee2 0x0000000000500000 0x0000000005600000 2 /dev/block/mmcblk0 USER
kb 0x0000000000100000 0x0000000005b00000 2 /dev/block/mmcblk0 USER
dkb 0x0000000000100000 0x0000000005c00000 2 /dev/block/mmcblk0 USER
android 0x0000000080000000 0x0000000005d00000 2 /dev/block/mmcblk0p5 USER
cache 0x0000000010000000 0x0000000085d00000 2 /dev/block/mmcblk0p6 USER
usrdata 0x000000030ce00000 0x0000000095d00000 2 /dev/block/mmcblk0p7 USER
bmtpool 0x0000000001500000 0x0000000001500000 2 /dev/block/mmcblk0 USER
What is actually included in a TWRP or CWM backup?