How to identify userdata partition on an unrooted Android device? - General Questions and Answers

Hi all,
I was trying to identify userdata partition after
- adb shell
- cat /proc/partitions
on an unrooted Oneplus 2.
Here below was the result.
How to identify which one is userdata partition?
Thanks in advance.
Cheers,
Wen
Code:
major minor #blocks name
179 0 15388672 mmcblk0
179 1 81920 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 128 mmcblk0p3
179 4 128 mmcblk0p4
179 5 1 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 128 mmcblk0p7
179 8 1536 mmcblk0p8
179 9 1 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 256 mmcblk0p12
179 13 256 mmcblk0p13
179 14 1 mmcblk0p14
179 15 1 mmcblk0p15
179 16 8 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 8096 mmcblk0p22
179 23 16192 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 1024 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 96 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 1024 mmcblk0p30
179 31 500 mmcblk0p31
259 0 500 mmcblk0p32
259 1 512 mmcblk0p33
259 2 512 mmcblk0p34
259 3 65536 mmcblk0p35
259 4 65536 mmcblk0p36
259 5 32768 mmcblk0p37
259 6 1024 mmcblk0p38
259 7 512 mmcblk0p39
259 8 512 mmcblk0p40
259 9 262144 mmcblk0p41
259 10 2621440 mmcblk0p42
259 11 11980783 mmcblk0p43
179 32 4096 mmcblk0rpmb

If you have an eMMC internal storage you can see names and partitions at same time:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/

xXx yYy said:
If you have an eMMC internal storage you can see names and partitions at same time:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
Click to expand...
Click to collapse
Thanks for your reply.
After
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
It returns
Code:
/dev/block/platform/msm_sdcc.1/by-name/: Permission denied
How to resolve it?
Thanks.

Android must be root to successfully run the cmd.

xXx yYy said:
Android must be root to successfully run the cmd.
Click to expand...
Click to collapse
Thanks for your reply.
I just rooted the device.
But after
Code:
adb root
It returns
Code:
adbd cannot run as root in production builds
How to solve it?
Thanks in advance.

No way.

Related

[Q] Which /dev/block is /system? P5100

All,
When I explore the device for the system image to pull using DD, I am not sure which one contains the fs to be mounted as /system. Basically trying to extract system.img from the stock Rom..
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 20480 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 716800 mmcblk0p7
259 0 20480 mmcblk0p8
259 1 1433600 mmcblk0p9
259 2 27787247 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
Code:
# ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name

[Q] I need help understanding partitions

This is my first post on xda, and I'm pretty much a noob. So I hope I'm posting this in the correct section, if not please feel free to correct me if I'm wrong.
I'm trying my hand at some developing and have a couple questions I'm hoping someone can help me with.
The goal is Cyanogenmod 10.2 on my LG Lucid VS840. Currently I'm using an unofficial CM10 ROM Android version 4.1.2 (Not my work)
Partition Information? I'm unsure how to convert the information from the /proc/partitions file into something I can use for my BoardConfig.mk file as follows
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
My device does not have a /proc/mtd file. I do have the /proc/partitions file as follows
major minor #blocks name
7 0 7308 loop0
7 1 2111 loop1
179 0 7577600 mmcblk0
179 1 32768 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 73728 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 24576 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 1048576 mmcblk0p26
179 27 270336 mmcblk0p27
179 28 1622016 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 4194304 mmcblk0p30
179 31 5120 mmcblk0p31
179 32 15637504 mmcblk1
179 33 15633408 mmcblk1p1
254 0 7308 dm-0
254 1 2110 dm-1
I believe this is the proper fix for the message:
Need size of filesystem
+ '[' 1 -ne 0 ']'
+ exit 4
error: failed to build /home/ben/vs840/out/target/product/vs840/userdata.img from /home/ben/vs840/out/target/product/vs840/data
make: *** [/home/ben/vs840/out/target/product/vs840/userdata.img] Error 1
make: *** Deleting file `/home/ben/vs840/out/target/product/vs840/userdata.img'
make: *** Waiting for unfinished jobs....
Someone please help me! Thanks to everyone in advance!

What to do with all these partitions?

Not sure whether this is the right place, but oh well.
So I"m trying to port cyanogenmod 11 to the Moto G 2014 (codename Titan) (should I have posted this on the cyanogenmod forums? Couldn't find a section that looked even remotely relevant).
I'm trying to fill in this section of BoardConfig.mk:
Code:
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
I don't have a /proc/mtd, but /proc/partitions seems to have what I'm looking for.
However, it's contents is as follows:
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 1012 mmcblk0p4
179 5 200 mmcblk0p5
179 6 400 mmcblk0p6
179 7 32 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2332 mmcblk0p10
179 11 1012 mmcblk0p11
179 12 200 mmcblk0p12
179 13 400 mmcblk0p13
179 14 32 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1052 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 488 mmcblk0p19
179 20 32 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 1 mmcblk0p22
179 23 8 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 128 mmcblk0p25
179 26 3072 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 4096 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10200 mmcblk0p31
259 0 10280 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 546944 mmcblk0p35
259 4 1130496 mmcblk0p36
259 5 8192 mmcblk0p37
259 6 5774208 mmcblk0p38
179 32 2048 mmcblk0rpmb
W-why is there 39 partitions...?

[Q] Getting The Sizes of Partitions

When editing the part of BoardConfig.mk file how can I find the partition sizes?
Code:
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 41943040
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8388608
BOARD_FLASH_BLOCK_SIZE := 131072
It says proc/mtd but I don't have mtd, emmc or dumchar_info. How can I get them?Here is my proc/partitions;
Code:
[email protected]:~$ adb shell cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 8192 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 8192 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 40960 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 73728 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1236992 mmcblk0p22
179 23 311296 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 16384 mmcblk0p25
179 26 8192 mmcblk0p26
179 27 9445376 mmcblk0p27
179 28 3694592 mmcblk0p28
179 32 512 mmcblk0rpmb

[Q] How to dump files from a bootloader-locked Moto G ?

OK, so I found this post http://forum.xda-developers.com/showthread.php?t=2450045 and thought I would make the attempt. Even though the prerequisites say " Rooted Device " I went thru the steps. This is what I ended up with :
1|[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 512 mmcblk0p4
179 5 200 mmcblk0p5
179 6 400 mmcblk0p6
179 7 32 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2332 mmcblk0p10
179 11 512 mmcblk0p11
179 12 200 mmcblk0p12
179 13 400 mmcblk0p13
179 14 32 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1052 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 512 mmcblk0p19
179 20 8 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 1 mmcblk0p22
179 23 8 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 128 mmcblk0p25
179 26 3072 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 4096 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10240 mmcblk0p31
259 0 10240 mmcblk0p32
259 1 546944 mmcblk0p33
259 2 1130496 mmcblk0p34
259 3 8192 mmcblk0p35
259 4 5791616 mmcblk0p36
179 32 512 mmcblk0rpmb
179 64 31166976 mmcblk1
179 65 31165952 mmcblk1p1
[email protected]:/ $
For background info, this device is a Cricket XT1045. Not unlockable thru Motorola site.
I see on another site that someone managed to dump a ROM from this device : CRICKET_XT1045_4.4.4_KXB21.14-L1.45_cid16_CFC.xml.zip - FileFactory.
What partition from those listed above do I pull from the device ?
Any guidance will be greatly appreciated.
CRICKET_XT1045_4.4.4_KXB21.14-L1.45_cid16_CFC.xml.zip was not dumped by someone - it's a Motorola Factory Firmware Image.
The following command will dump the entire system partition.
adb pull /system​
If you want Kernel or Recovery you need root, but those are included in the above factory firmware image.
Thanks for the help, but that command < adb pull/system > only gave me a list of other adb commands.
Now, if I follow you, with the ROM mentioned being directly from Motorola, does that mean that an individual cannot dump his/her personal ROM ?
My goal in all of this is to compare a stock ROM with the bootloader locked against that same ROM having an unlocked bootloader.
And I want to dump my specific ROM to search thru it in an attempt to find my unique " unlock data " string.
I got my feet wet in hex editing during my FTA days. This is quite a bit more detailed, but with Motorola unable to unlock Cricket-branded devices, I have to try.
Hell-On-Wheels said:
Thanks for the help, but that command < adb pull/system > only gave me a list of other adb commands.
Click to expand...
Click to collapse
There should be a space between pull and /system.
lost101 said:
There should be a space between pull and /system.
Click to expand...
Click to collapse
Thanks, but holy moly ! that is alot of output.
I saw a few files that look promising > /firmware, /permissions, /DeviceAuthApp. I saw peregrine mentioned a couple times.
Which of these folders contains the actual 4.4.4 operating system ?
You just dumped the 'System' partition - you are looking at the operating system. There are other partitions that relate to the functioning of Android, and your 'holy grail' could well be located there. More info here: http://forum.xda-developers.com/showthread.php?t=2540799

Categories

Resources