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
Related
sorry if I'm wrong section but I have a bad English.
I'm trying to do the dump file boot.img most beautiful gi others from a huawei ascend G330 (u8825-1) and do not know what these files contain what it helpful. who can help me to understand what they contain and to identify the boot thanks
Code:
[email protected]:~$ adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ # su
130|[email protected]:/ # cat /proc/mtd
dev: size erasesize name
[email protected]:/ #
127|[email protected]:/ # cat /proc/emmc
/proc/emmc: No such file or directory
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 20 mmcblk0p1
179 2 300 mmcblk0p2
179 3 133120 mmcblk0p3
179 4 1 mmcblk0p4
179 5 12288 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 20480 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 196608 mmcblk0p15
179 16 81920 mmcblk0p16
179 17 524288 mmcblk0p17
179 18 655360 mmcblk0p18
179 19 2154496 mmcblk0p19
179 32 7822336 mmcblk1
179 33 7818240 mmcblk1p1
sorry again for my bad English.
boot.img is the kernel of ur phone..
Sent from my GT-B5512 using xda app-developers app
pavan_19 said:
boot.img is the kernel of ur phone..
Sent from my GT-B5512 using xda app-developers app
Click to expand...
Click to collapse
excuse can be more clear and explain how to make the dump file to img
Sorry dude no idea about that..
Sent from my GT-B5512 using xda app-developers app
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!
Hello all!
Say, I've noticed the 2.55Ghz Overclock Kernel has been essentially abandoned && no longer works on the latest update.. I've been looking into creating my own custom Kernel that apply's the same essential overclock but supports the latest updates (91~).
My question is if anyone either knows which partition the kernel is on, or how I can go about figuring that out.
If anyone has a updated Rooted Kernel they are willing to dump and post i'd be more than happy to have a go at it; rather than have me figure it out.
Anyways, I've learned that the /proc/ folder lacks both emmc and mtd partition tables... So after doing some digging i've got all the mmcblk partition names and sizes, but god only knows which one is the Kernel. All I really need is the Kernel, but any other information is more than welcomed.
Thank you to anyone who can help!
Code:
major minor #blocks name
179 0 15267840 mmcblk0
179 1 8192 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 786432 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 786432 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 32768 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 13551616 mmcblk0p12
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 7761920 mmcblk1
179 49 7757824 mmcblk1p1
Second question:
Is it safe to install Cyanogenmod on the shield? I can't seem to really find anything about the shield with CM on it. I know there is a built in ROM dumper that labels all the partitions so if that works it would also solve the first question.
Thanks.
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
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.