[GUIDE] Making Dump Files Out of Android Device Partitions

Search This thread

gza036

Member
Jan 24, 2014
19
1
i am sure it won't wipe userdata at all! yes.. if you try google it you'll be sure.. never odin flashed a phone?
anyway.. if you try to do that on a booted up phone from terminal you might get more intresting stdout/stderr.

i still am quite sure you cannot do that because it's bigger then 4gb.. which is the max supported for the fat32 fs on the micro sd ( given the sd is formatted this way - before i said ext4 which instead is fine..)so try to see if the sd has this fs and then change it and retry.. the only option i can think of

I am well aware of fat32 file size limits. The first thing I did was format the MicroSD to NTFS, so that is not the issue.
I like sending it straight to PC better anyways.
Both of the methods use dd, I don't think dd cares where it is sending the data, the result is the same either way. Therefore, the problem is not the microSD card. Let's forget about the microSD card lol.
Does anyone know why dd would be returning lseek value too large for defined data type
I get I/O errors and then process halts with lseek value too large for defined data type
 
Last edited:

Wuby986

Senior Member
Oct 18, 2013
2,144
2,440
I have used odin, but probably also executed factory reset.
I am well aware of fat32 file size limits. The first thing I did was format the MicroSD to NTFS, so that is not the issue.
I like sending it straight to PC better anyways.
Both of the methods use dd, I don't think dd cares where it is sending the data, the result is the same either way. Therefore, the problem is not the microSD card. Let's forget about the microSD card lol.
Does anyone know why dd would be returning lseek value too large for defined data type
I get I/O errors and then process halts with lseek value too large for defined data type

found this..
http://xdaforums.com/showthread.php?p=26030990#post26030990
on post n° 12 he says he managed to overcome that by changing version of busybox.. last attempt, then i call myself out! lool
 
  • Like
Reactions: gza036

gza036

Member
Jan 24, 2014
19
1
found this..
http://xdaforums.com/showthread.php?p=26030990#post26030990
on post n° 12 he says he managed to overcome that by changing version of busybox.. last attempt, then i call myself out! lool

edit: exactly right

---------- Post added at 12:54 PM ---------- Previous post was at 12:35 PM ----------

[/COLOR]
found this..
http://xdaforums.com/showthread.php?p=26030990#post26030990
on post n° 12 he says he managed to overcome that by changing version of busybox.. last attempt, then i call myself out! lool

In those instructions:
# chmod 755 /data/local/tmp/busybox
# /data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p14

which partition are they editing here?
I imagine it might not be the same one on the S5, so the friendly name would be useful
 
Last edited:

Miles Prower

Senior Member
Jul 19, 2010
62
9
Paris
www.ps3linux.fr
Hello! I'm trying to clone a few android tablets for a classroom (Samsung T535); I thought at first of doing a Nandroid backup of one then copy it over to the other devices, but there's no working custom recovery for that model. I'm not sure on how to proceed with that, and just dumping parts of the original system and dd'ing on the other tablets could be a potential solution (or a fast way to having a collection of bricks, maybe?). All tablets are running the same base firmware and are identical. I've installed some apps on one, tweaked it (custom host file, etc), and would like to carry that over to the other ones.

Here's the partition table:

Code:
shell@matisselte:/dev/block/platform/msm_sdcc.1/by-name $ ls -al               
lrwxrwxrwx root     root              2014-11-09 04:41 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              2014-11-09 04:41 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              2014-11-09 04:41 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root     root              2014-11-09 04:41 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              2014-11-09 04:41 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root     root              2014-11-09 04:41 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              2014-11-09 04:41 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              2014-11-09 04:41 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              2014-11-09 04:41 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              2014-11-09 04:41 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root     root              2014-11-09 04:41 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root     root              2014-11-09 04:41 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root     root              2014-11-09 04:41 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              2014-11-09 04:41 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              2014-11-09 04:41 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root     root              2014-11-09 04:41 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              2014-11-09 04:41 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              2014-11-09 04:41 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root     root              2014-11-09 04:41 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root     root              2014-11-09 04:41 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              2014-11-09 04:41 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              2014-11-09 04:41 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              2014-11-09 04:41 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root     root              2014-11-09 04:41 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root     root              2014-11-09 04:41 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              2014-11-09 04:41 userdata -> /dev/block/mmcblk0p26

Which partitions should I dump to do that? I'm guessing at least system and userdata, but I'm not sure what the other do. Any help?
 

Aenadon

Senior Member
May 14, 2014
398
147
Geheimstadt
Hello! I'm trying to clone a few android tablets for a classroom (Samsung T535); I thought at first of doing a Nandroid backup of one then copy it [...]
Which partitions should I dump to do that? I'm guessing at least system and userdata, but I'm not sure what the other do. Any help?

If all of them are Samsung T535, don't copy system (well they have the same system after all, don't they?)
My guess is that userdata should be enough, and bricks should not occur as it is the same hardware.

I'm not sure if it is stated somewhere in this thread, but for transferring that image to the other devices you must reboot to bootloader and then flash the image via fastboot from adb tools (fastboot flash userdata yourimagefilename.img)
 
Last edited:

w1nst0n sm1th

Senior Member
Feb 3, 2016
95
30
trying to dump the 12GB userdata partition, dev/block/mmcblk0p26
This phone is stuck in a bootloop and getting I/O errors when I run dd on this partition, so I add conv=sync,noerror
Code:
dd if=/dev/block/mmcblk0p26 of=/storage/sdcard1/userdata.img conv=sync,noerror

it gets past some of the errors (there are just a few at the beginning) but after around 2GB it stops with
Code:
lseek: Value too large for defined data type

I read that^ could have something to do with trying to go over 2GB with a program not compiled for "large file support"

But, I trie1d to dump the entire 16GB internal memory, mmcblk0
and it makes it to 3.46 GB before it shows that error. I can also successfully dump the full 12GB partition on another working identical phone ( both sprint s5, TWRP recovery v2.8.6.0, android 5.0)
:confused:
The command is incomplete. I don't know if it will solve the issue but you should add a few stuff :
1. 'bs=1024k' ==> Thats the block size you copy/paste in one single step.
2. You should gunzip becouse a raw copy is very space consuming. You can extract it later with 7zip on windows or gunzip on linux system before converting it with ext2simg and flashing it with fastboot to restore [android ext4 is not a standard ext4 linux partition, for what i understand ; at least working for me].

So it should be like this :
sudo -c dd bs=1024 conv=sync,noerror if=/dev/block/mmcblk0p26 | gzip -c > /storage/sdcard1/userdata.img.gz

Hope this help.

---------- Post added at 11:25 PM ---------- Previous post was at 11:15 PM ----------

Hello! I'm trying to clone a few android tablets for a classroom (Samsung T535); I thought at first of doing a Nandroid backup of one then copy it over to the other devices, but there's no working custom recovery for that model. I'm not sure on how to proceed with that, and just dumping parts of the original system and dd'ing on the other tablets could be a potential solution (or a fast way to having a collection of bricks, maybe?). All tablets are running the same base firmware and are identical. I've installed some apps on one, tweaked it (custom host file, etc), and would like to carry that over to the other ones.

Here's the partition table:

Code:
shell@matisselte:/dev/block/platform/msm_sdcc.1/by-name $ ls -al               
lrwxrwxrwx root     root              2014-11-09 04:41 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              2014-11-09 04:41 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              2014-11-09 04:41 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root     root              2014-11-09 04:41 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              2014-11-09 04:41 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root     root              2014-11-09 04:41 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              2014-11-09 04:41 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              2014-11-09 04:41 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              2014-11-09 04:41 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              2014-11-09 04:41 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root     root              2014-11-09 04:41 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root     root              2014-11-09 04:41 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root     root              2014-11-09 04:41 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              2014-11-09 04:41 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              2014-11-09 04:41 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root     root              2014-11-09 04:41 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              2014-11-09 04:41 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              2014-11-09 04:41 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root     root              2014-11-09 04:41 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root     root              2014-11-09 04:41 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              2014-11-09 04:41 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              2014-11-09 04:41 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              2014-11-09 04:41 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root     root              2014-11-09 04:41 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root     root              2014-11-09 04:41 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              2014-11-09 04:41 userdata -> /dev/block/mmcblk0p26

Which partitions should I dump to do that? I'm guessing at least system and userdata, but I'm not sure what the other do. Any help?
If you modified the android system with stuff like Superuser.apk, busybox,... and want to retore to other device with installed apks, you must backup both system and userdata partition.

If system is not modified... well you should not even be able to run dd, i think.
But in case you can, userdata backup is sufficient.

Use ext2simg [see android-tools in debian/ubuntu] to convert the image in proper flashable image in order to use fastboot or it will not work.
 
  • Like
Reactions: quakze

gza036

Member
Jan 24, 2014
19
1
The command is incomplete. I don't know if it will solve the issue but you should add a few stuff :
1. 'bs=1024k' ==> Thats the block size you copy/paste in one single step.
2. You should gunzip becouse a raw copy is very space consuming. You can extract it later with 7zip on windows or gunzip on linux system before converting it with ext2simg and flashing it with fastboot to restore [android ext4 is not a standard ext4 linux partition, for what i understand ; at least working for me].

So it should be like this :
sudo -c dd bs=1024 conv=sync,noerror if=/dev/block/mmcblk0p26 | gzip -c > /storage/sdcard1/userdata.img.gz
I ended up using bs=4096
interesting idea about gunzip
what fixed the problem with the errors was updating busybox
 

droid_god

Senior Member
May 1, 2015
906
149
lucknow
ofcoarse, i actually had a project going where it detects all partitions(modems, boot.img, system etc..) that archives itself into a .zip
it was going well until i did something in the script, now it only works on the s3 :p it shall be continued one day!
hi bro

thanka for the great guide. Bui i ws just imagining that can the system.img dump be used as a backup and flashed through fastboot using

fastboot flash syatem system.img

and will this be a happy ending. not a bootlope.

reason of asking such question is
my system folder is 1.60gb
and the system.img is 1.76gb

and i cant access the system.img in pc uaing any img mounting software. including one given in the guide to mount it.

i use lg max(x160)
lollipop stock 5.0.0
 
Last edited:

Ricky Divjakovski

Recognized Developer / Inactive RC
Feb 4, 2013
5,255
7,676
28
Sydney
hi bro

thanka for the great guide. Bui i ws just imagining that can the system.img dump be used as a backup and flashed through fastboot using

fastboot flash syatem system.img

and will this be a happy ending. not a bootlope.

reason of asking such question is
my system folder is 1.60gb
and the system.img is 1.76gb

and i cant access the system.img in pc uaing any img mounting software. including one given in the guide to mount it.

i use lg max(x160)
lollipop stock 5.0.0

well use the dd method(dd if=/dev/block/SYSTEMBLOCK or /sdcard/system.img), make a shell script to run in recovery to do the opposite in recovery
Code:
#!/tmp/bash 

#provided you have bash binary extracted to /tmp with correct permissions
#provided you did a factory reset prior

dd if=/sdcard/system.img /dev/block/SYSTEMBLOCK
exit

your /system partition will rebuild /data and /cache on boot
 

aa39

Member
Jul 30, 2015
15
2
how to dump boot0 and boot 1 on those phone not show boot0 and 1 on adb????
sdfgsdfdsfdsfds.JPG

plz help guys
my phone desire816 dual sim-a5dug
 

aa39

Member
Jul 30, 2015
15
2
What exactly are you trying to do with those files. What do you need them for?

Sent from my Nexus 7 using XDA Free mobile app

tnx for reply
i need it for emmc programing or j-tag purpose so can guys i need help i need boot0 and boot 1 badly
in mtk phone i can give boot 1 and boot 2 but in qualcomm phone not show boot0 and boot1

need help
 

CVAngelo

Senior Member
Mar 24, 2015
1,014
392
Praia
investincv.blogspot.com
tnx for reply
i need it for emmc programing or j-tag purpose so can guys i need help i need boot0 and boot 1 badly
in mtk phone i can give boot 1 and boot 2 but in qualcomm phone not show boot0 and boot1

need help
You may have better luck asking this question on an XDA thread that's related to Jtag or your phone model. Just do a search of XDA. Or if you have a box, go to the online forum for that box, or perhaps visit GSM Forum. I doubt the typical user of this forum is doing Jtags.

Sent from my Nexus 7 using XDA Free mobile app
 
  • Like
Reactions: aa39

aa39

Member
Jul 30, 2015
15
2
You may have better luck asking this question on an XDA thread that's related to Jtag or your phone model. Just do a search of XDA. Or if you have a box, go to the online forum for that box, or perhaps visit GSM Forum. I doubt the typical user of this forum is doing Jtags.

Sent from my Nexus 7 using XDA Free mobile app

yes i know but jtager dont use adb(need some one master on adb thing) so i need to know there are anyother way to get boot0-boot1 via adb???
 

droid_god

Senior Member
May 1, 2015
906
149
lucknow
well use the dd method(dd if=/dev/block/SYSTEMBLOCK or /sdcard/system.img), make a shell script to run in recovery to do the opposite in recovery
Code:
#!/tmp/bash 

#provided you have bash binary extracted to /tmp with correct permissions
#provided you did a factory reset prior

dd if=/sdcard/system.img /dev/block/SYSTEMBLOCK
exit

your /system partition will rebuild /data and /cache on boot

thanks for ansering.


i got that.

but just to tell you i have no commands in stock recovery. and no cuatom recovery is avilable for my device.

i can use fastboot mode.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 353
    Use:
    The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares.


    Pr-requirement:
    - Rooted device.
    - Knowledge of how to use adb or Terminal Emulator.

    The first step of making dump files out of device partitions is to locate its mounting points..!!
    So in our tutorial, we will make it in 2 sections. Section 1 for how to get mounting points, and section 2 for how to get partition dumped..
    Keep in mind that this is xda-university; so my target is to show beginners how to do that manually, without the aid of any tool, so they can get the concept behind it.. OK let's begin..!!

    Section 1:
    Getting mounting points
    There are several methods to achieve this, but we will discuss the easiest methods that give efficient information about the partition that you want to know its mounting point.
    All these methods will be described using adb shell.

    Way #1
    Code:
    adb shell
    cat /proc/partitions
    This one needs from you to figure out which block belong to which partition name.!!

    2ds4ujd.png


    Way #2
    Code:
    adb shell
    ls -al /dev/block/platform/[B][COLOR="Blue"]dw_mmc[/COLOR][/B]/by-name
    This one will give you info about the dev block names WITH their familiar names (i.e, boot, recovery, system... etc)

    rsg20h.png

    This command is not universal between devices, and you will need to gather its pieces (/dev/block/platform/dw_mmc/by-name).
    How?
    - In your device, use any explorer that can get you to the device root (personally I use ES Explorer, by pressing on "/" on navigation bar).
    - Go to "/dev/block/platform/" folder
    - Here you will see some files and folders, we need to open folders and search for the folder called "by-name" inside one of them; in my situation it was "dw_mmc" folder which has the folder "by-name" inside it.
    - At the end, my targeted piece info will be (/dev/block/platform/dw_mmc/by-name)
    - Now open adb shell and put that command..


    Way #3
    By pushing parted binary to /system/bin folder and run it (you can find it in attachment).
    Code:
    adb remount
    adb shell "su" "" "mount -o remount,rw /system"
    adb push parted /system/bin/parted
    adb shell
    chmod 0755 /system/bin/parted
    parted /dev/block/[B][COLOR="Blue"]mmcblk0[/COLOR][/B]
    print

    11t5x7c.png

    Here, your mounting points will start with /dev/block/mmcblk0p* where (*) is the number shown in the table above for each partition.
    example:
    The hidden partition mounting point will be mmcblk0p10
    The radio partition mounting point will be mmcblk0p7
    The system partition mounting point will be mmcblk0p9
    The recovery partition mounting point will be mmcblk0p6

    and so on

    Don't forget to "quit" the parted action after grasping your device mounting points.

    N.B:
    - You may need to run first:
    Code:
    adb shell
    cat /proc/partitions
    to know what is the initial name for your device partition.. In the example above, it was mmcblk0.

    wbaufd.png

    - Also to be able to do adb push to /system partition for parted binary, you will need insecure boot.img used in your ROM or adbd insecure installed in your device (Check this thread for that app), or just push parted binary manually by any root explorer and then fix permissions to rwxr-xr-x (755).

    ***​

    Section 2:
    Dumping ROM partition
    After locating the mounting point of the partition you want to dump, open adb shell command prompt and type:
    Code:
    adb shell
    su
    dd if=[B][COLOR="Blue"]/yourMountingPoint[/COLOR][/B] of=[B][COLOR="Green"]/yourDestination[/COLOR][COLOR="Red"]/partitionType[/COLOR][/B]
    Let's say I want to take a dump out of system partition from above example. So the adb commands will be:
    Code:
    adb shell
    su
    dd if=[B][COLOR="Blue"]/dev/block/mmcblk0p9[/COLOR][/B] of=[B][COLOR="Green"]/sdcard[/COLOR][COLOR="Red"]/system.img[/COLOR][/B]
    This may take a while to complete the dumping process, depending on the size of your dumped partition; so be patient..

    Note:
    If the partition is formatted as ext3/4 then the dumped partition will have .img as an extension.
    Other partition dumps have different extensions; examples:
    • radio.bin
    • param.lfs
    • Sbl.bin
    • zImage (without extension)

    ***​

    Optional:
    Read Partition Image
    After dumping an image from android partition, you can mount it to extract a particular file for sharing, or the whole dump content in case the ROM chief wants to make a ROM out of dump files..
    For Linux Users:
    - Open terminal and type:
    Code:
    su -
    mkdir -p /mnt/disk
    mount -o loop [B][COLOR="Red"]yourImage.img[/COLOR][/B] /mnt/disk
    cd /mnt/disk
    ls -l

    For Windows Users:
    - Download LinuxReader from this site here.
    - Open it -> Drives -> Mount Image -> Then choose your dumped image and hit Mount. A new driver will appear that contains all files inside the dumped image called "Linux native Volume 1". Just double click it to get inside the dumped image.

    2roj2f4.png


    2dhbhxd.png


    I hope you will find this tutorial beneficial,,,
    Yours;

    115
    Actions Explanation

    ★ Tutorial Legends ★

    In this post, I will try to explain the use of each binary used in the tutorial, so you can make sense of each action taken.

    #1
    Code:
    adb shell
    Run remote shell interactively, as if you are in linux terminal.

    #2
    Code:
    cat /proc/partitions
    cat binary is used to concatenate file(s) and print them to standard output display. In our example, it prints the content of partitions file which is found in proc folder to screen display.

    #3
    Code:
    ls -al /dev/block/platform/dw_mmc/by-name
    ls binary is used to list directory contents.
    -al is the used option for ls which means to include entries that started with "." in long listing format. There are a lot of options for ls binary. You can always print ls --h to display help menu for other options available.

    #4
    Code:
    adb remount
    Remounts the /system partition on the device read / write. This has been disabled in some devices (those with secure boot image); so you need to make sure that you have patched adbd that can run this command effectively.

    #5
    Code:
    su
    Used to get super-user privilege.


    #6
    Code:
    mount -o remount,[B][COLOR="Red"]rw[/COLOR][/B] /system
    Specific command to mount the /system partition on the device read / write (rw).
    If you change rw to ro, you will get /system partition mounted as read only.

    #7
    Code:
    adb push parted /system/bin/parted
    adb push is used to copy file/dir from your local computer to android device. The usual format is adb push <local> <remote>

    #8
    Code:
    chmod 0755 /system/bin/parted
    chmod binary is used to set permissions for the specified file/dir.
    The number after chmod is the permission used. See the next box for better understanding of chmod formatting:
    Code:
    [CENTER][B][COLOR="Red"]----------------
    | CHMOD SCHEME |
    ----------------[/COLOR][/B][/CENTER]
              [B] r     w     x[/B]
               [B]4     2     1    [COLOR="Green"]= 7 (Full Permissions)[/COLOR][/B]
    
      User    ( )   ( )   ( )   [B][COLOR="Green"]--> 2nd digit[/COLOR][/B]
      Group   ( )   ( )   ( )   [B][COLOR="Green"]--> 3rd digit[/COLOR][/B]
      Other   ( )   ( )   ( )   [B][COLOR="Green"]--> 4th digit[/COLOR][/B]
    
      Special UID   GID   STK
              ( )   ( )   ( )   [B][COLOR="Green"]--> 1st digit, ignored on most cases or put 0[/COLOR][/B]
    In the above example, it is set to 0755 which means the following scheme:
    Code:
              [B] r     w     x[/B]
               [B]4     2     1[/B]
    
      User    ([B][COLOR="Red"]*[/COLOR][/B])   ([B][COLOR="Red"]*[/COLOR][/B])   ([B][COLOR="Red"]*[/COLOR][/B])   [B][COLOR="Green"]--> This equals to 7 (rwx)[/COLOR][/B]
      Group   ([B][COLOR="Red"]*[/COLOR][/B])   ( )   ([B][COLOR="Red"]*[/COLOR][/B])   [B][COLOR="Green"]--> This equals to 5 (r-x)[/COLOR][/B]
      Other   ([B][COLOR="Red"]*[/COLOR][/B])   ( )   ([B][COLOR="Red"]*[/COLOR][/B])   [B][COLOR="Green"]--> This equals to 5 (r-x)[/COLOR][/B]
    
      Special UID   GID   STK
              ( )   ( )   ( )   [B][COLOR="Green"]--> This equals to 0 (---)[/COLOR][/B]
    As you can see, if you said 0755, it will be as same as saying ---rwxr-xr-x

    #9
    Code:
    dd if=/dev/block/mmcblk0p9 of=/sdcard/system.img
    dd binary is used to copy a file with converting and formatting.
    if means input file; here we pointed to the whole partition, not specific file.
    of means outputting file to specific destination path; here it is to sdcard with system.img name.

    #10
    Code:
    mkdir -p /mnt/disk
    mkdir binary is used to make folder dir.
    -p is mkdir option which means to create folder with sub-folder at the same time. Here we want to create mnt folder that contains disk sub-folder in it. If the folder and or sub-folder(s) are already exists, it will not give error but nothing will be created.

    #11
    Code:
    mount -o loop yourImage.img /mnt/disk
    This is linux way to mount images into specific directory (/mnt/disk in this example).

    #12
    Code:
    cd /mnt/disk
    cd used to get inside specific dir path.

    #13
    Code:
    ls -l
    ls binary is used to list directory contents as described above.
    -l is the used option for ls which means to list contents in long listing format.


    Cheers
    11
    another way to get common names

    on way #2, I've often used:
    Code:
    cat /proc/emmc
    on a few devices to reveal similar info.

    Rob
    5
    can i able to mount boot.img in android itself...actually i wanted to extract boot.img frm mobile without any tools or without the help of PC...if there be any possibilities..??

    if you mean extract to modify boot.img, then I don't think there is away to do that from device itself in the moment..
    if you mean dumping boot.img then yes you can, just install terminal emulator from Google play and you can run adb shell commands directly from the device
    4
    can i able to mount boot.img in android itself...actually i wanted to extract boot.img frm mobile without any tools or without the help of PC...if there be any possibilities..??