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.
Related
I got a cheap chinese phone Jiayu G2+ (MTK6577) model and I'm trying to learn the partitions of this device. I guess it doesn't help that I'm just starting to learn the inner workings of android in general. Trying to port CWM / TWRP to this phone. I've managed to done some of this work with the help of the BGCNGM's unpacker scripts, unfortunately, CWM isn't reading some partitions correctly so it's unable to perform nandroid backup and gets stuck at "backing up boot image".
It doesn't look like the device uses MTD, get empty when I go cat /proc/mtd
so when I executed cat /proc/partitions, this is what i get
Code:
major minor #blocks name
179 0 3792000 mmcblk0
179 1 1 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 524288 mmcblk0p3
179 4 524288 mmcblk0p4
179 5 2661376 mmcblk0p5
179 6 45280 mmcblk0p6
179 64 1024 mmcblk0boot1
179 32 1024 mmcblk0boot0
179 96 15637504 mmcblk1
179 97 15636480 mmcblk1p1
It looks like mmcblk1 is my 16GB microsd card.
Doing a ls -la in my root directory, I can find the mapps of mmcblk0
Code:
[email protected] -> /dev/block/mmcblk0p1
[email protected]_ro -> /dev/block/mmcblk0p2
[email protected] -> /dev/block/mmcblk0p3
[email protected] -> /dev/block/mmcblk0p4
[email protected] -> /dev/block/mmcblk0p5
[email protected] -> /dev/block/mmcblk0p6
So what's left is mmcblk0boot1 and mmcblk0boot2, logical guess is that these are boot related partitions. But not exactly sure how to read these though.
Here's a copy of the recovery.fstab from the original rom's recovery.img
Code:
# mount point fstype device [device2]
/boot emmc boot
/cache ext4 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p5
/misc emmc misc
/recovery emmc recovery
/sdcard vfat /dev/block/mmcblk0p6
/sdcard2 vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk0p3
As I mentioned earlier, I'm unable to perform CWM backup most likely because CWM can't find the boot, misc, and recovery.
1. Does anyone have any idea how I can find these partitions?
2. So it looks like my /system partition (lives under 512mb partition /dev/block/mmcblk0p3) whenever I do a dd export of system.img, the file IS 512mb. But when I flash the rom using SP Flash Tool, the original firmware image for system.img is around 200 megs. So I'm assuming this is a full partition copy? Is there anyway I can export this without the dead space? Looking into ROM development.
Thanks for any tips and guides.
Hi
I have acer liquid gallant duo with mt6575 and this is my layout partion
[email protected]:/ # cat proc/partitions
major minor #blocks name
179 0 3807232 mmcblk0
179 1 1 mmcblk0p1
179 2 524288 mmcblk0p2
179 3 1048576 mmcblk0p3
179 4 1676400 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 524288 mmcblk0p6
179 16 1024 mmcblk0boot1
179 8 1024 mmcblk0boot0
179 24 15339520 mmcblk1
179 25 15335424 mmcblk1p1
Click to expand...
Click to collapse
This is my configuration for mod recovery
# mount point fstype device [device2]
/boot emmc /boot
/cache ext4 /dev/block/mmcblk0p2
/data ext4 /dev/block/mmcblk0p3
/misc emmc /dev/misc ---> i have add /dev/
/recovery emmc /recovery
/emmc ext4 /dev/block/mmcblk0p4
/system ext4 /dev/block/mmcblk0p6
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
Click to expand...
Click to collapse
Misc is ok now....
Same problem of you i not can backup boot and recovery.
Kaiyoti said:
As I mentioned earlier, I'm unable to perform CWM backup most likely because CWM can't find the boot, misc, and recovery.
1. Does anyone have any idea how I can find these partitions?
2. So it looks like my /system partition (lives under 512mb partition /dev/block/mmcblk0p3) whenever I do a dd export of system.img, the file IS 512mb. But when I flash the rom using SP Flash Tool, the original firmware image for system.img is around 200 megs. So I'm assuming this is a full partition copy? Is there anyway I can export this without the dead space? Looking into ROM development.
Thanks for any tips and guides.
Click to expand...
Click to collapse
Hey, did you get anywhere with this? I've just picked up a Jiayu G2+ and after looking around at the dearth of development around it, I thought about having a go at porting CM to this, and see about getting the battery life improved. But with no CWM to backup, install and recover, makes this a bit risky.
If not, although this would be my first handset hacking from scratch, perhaps we can figure this out.
Start with output of below in Terminal Emulator.
Code:
cat /proc/dumchar_info
From my G3, maybe is the same...
Or use Ameer's Online Nandroid Backup with the JIAYU G3 patch.... test if is working for you.
Code:
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000004000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000008000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000408000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000908000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000928000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000000988000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000f88000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000001588000 2 /dev/block/mmcblk0p2
misc 0x0000000000060000 0x0000000001b88000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001be8000 2 /dev/block/mmcblk0
expdb 0x0000000000200000 0x0000000001ee8000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x00000000020e8000 2 /dev/block/mmcblk0p3
cache 0x0000000020100000 0x00000000221e8000 2 /dev/block/mmcblk0p4
usrdata 0x00000000a2800000 0x00000000422e8000 2 /dev/block/mmcblk0p5
fat 0x0000000001018000 0x00000000e4ae8000 2 /dev/block/mmcblk0p6
bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0
Salu2
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...
Hi
can anybody share partition layout for xperia c c2305
can somebody post the output of cat /proc/dumchar_info?
botioni said:
can somebody post the output of cat /proc/dumchar_info?
Click to expand...
Click to collapse
no...LOL
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000600000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0
s1sbl 0x0000000000040000 0x0000000002120000 2 /dev/block/mmcblk0
ta 0x0000000000200000 0x0000000002160000 2 /dev/block/mmcblk0
ltalabel 0x0000000001000000 0x0000000002360000 2 /dev/block/mmcblk0p4
uboot 0x0000000000060000 0x0000000003360000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000033c0000 2 /dev/block/mmcblk0
recovery 0x0000000000700000 0x00000000039c0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000040c0000 2 /dev/block/mmcblk0p5
misc 0x0000000000080000 0x00000000046c0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000004740000 2 /dev/block/mmcblk0
ebr2 0x0000000000080000 0x0000000004a40000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000004ac0000 2 /dev/block/mmcblk0
nrstdata 0x0000000000600000 0x00000000054c0000 2 /dev/block/mmcblk0p6
android 0x000000004b000000 0x0000000005ac0000 2 /dev/block/mmcblk0p7
cache 0x0000000007e00000 0x0000000050ac0000 2 /dev/block/mmcblk0p8
usrdata 0x0000000040000000 0x00000000588c0000 2 /dev/block/mmcblk0p9
fat 0x000000004f0c0000 0x00000000988c0000 2 /dev/block/mmcblk0p10
bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0
Part_Nameartition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
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?