Hi,
After reflashing the PDS to get my partitions back to normal, I can now flash roms again. Unfortunately my internal memory card is at the moment borked and after an entire evening spent trying to fix it, it seems an impossible task. I can see my external SD fine, but trying to mount the emmc in recovery comes up with Error mounting /emmc.
Anyone have any good advice they can give me to solve this? I was going to try and reflash the original SBF (yeah, I know how dodgy that can be but I am desperate) from this superthread: http://forum.xda-developers.com/showthread.php?t=1125944 but the feds have put a stop to that...file sharing sites just don't let you get as many downloads these days!
So...any help, please?
there are other links for stock sbf. only flash 4.5.91, not 4.5.140. keep searching around.
Sent from my MB860 using XDA
el_venga said:
there are other links for stock sbf. only flash 4.5.91, not 4.5.140. keep searching around.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
That's the AT&T one isn't it though? My phone is a UK Orange handset (well it was, I've long since sim unlocked it )
Would this brick my Atrix? I know there is a risk already on handsets that are actually AT&T so don't want to raise the risk even more.
Surely there must be an easier way to get my internal memory card back to working order than SBFing?
Bump... Anyone know of a better way of rescuing my emmc partition?
You'll need adb type this and the post what the output is
adb shell
# cat /proc/partitions
# fdisk /dev/block/mmcblk0
p
q
rickwyatt said:
You'll need adb type this and the post what the output is
adb shell
# cat /proc/partitions
# fdisk /dev/block/mmcblk0
p
q
Click to expand...
Click to collapse
Hi there,
Thanks so much for getting back to me on this, sorry about the delay, only just got back in, despite the beers I have managed to navigate the cmd line
Ok, so my output is this:
1|[email protected]:/ $ su
su
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2048 loop0
253 0 98304 zram0
179 0 15541760 mmcblk0
179 1 3584 mmcblk0p1
179 2 512 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 327680 mmcblk0p12
179 13 786432 mmcblk0p13
179 14 20480 mmcblk0p14
179 15 655360 mmcblk0p15
179 16 2097152 mmcblk0p16
179 17 353280 mmcblk0p17
179 18 11233792 mmcblk0p18
179 32 7772160 mmcblk1
179 33 7771136 mmcblk1p1
[email protected]:/ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 1942720.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): ←[6np
p
Disk /dev/block/mmcblk0: 15.9 GB, 15914762240 bytes
1 heads, 16 sectors/track, 1942720 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 512 3584 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 513 576 512 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 577 832 2048 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 833 1937856 15496192 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 897 1024 1024 83 Linux
/dev/block/mmcblk0p6 1025 1088 512 83 Linux
/dev/block/mmcblk0p7 1089 1152 512 83 Linux
/dev/block/mmcblk0p8 1153 1280 1024 83 Linux
/dev/block/mmcblk0p9 1281 1536 2048 83 Linux
/dev/block/mmcblk0p10 1537 2560 8192 83 Linux
/dev/block/mmcblk0p11 2561 3584 8192 83 Linux
/dev/block/mmcblk0p12 3585 44544 327680 83 Linux
/dev/block/mmcblk0p13 44545 142848 786432 83 Linux
/dev/block/mmcblk0p14 142849 145408 20480 83 Linux
/dev/block/mmcblk0p15 145409 227328 655360 83 Linux
/dev/block/mmcblk0p16 227329 489472 2097152 83 Linux
/dev/block/mmcblk0p17 489473 533632 353280 83 Linux
/dev/block/mmcblk0p18 533633 1937856 11233792 83 Linux
Command (m for help): ←[6nq
q
[email protected]:/ #
Bump...
I can help but you must be careful I take no responsibility if I brick your phone now that bits over you will need to be connected to a computer then type this
rickwyatt said:
I can help but you must be careful I take no responsibility if I brick your phone now that bits over you will need to be connected to a computer then type this
Click to expand...
Click to collapse
Hey, thanks...this is for my internal SD though, so should I simply drop the -ext from the # umount sdcard line?
Just enter mke2fs /dev/block/mmcblk0p18 it should wipe your internal sdcard
Ok...it simply says mke2fs: can't open '/dev/block/': ls a directory
what am i doing wrong?
rickwyatt said:
Just enter mke2fs /dev/block/mmcblk0p18 it should wipe your internal sdcard
Click to expand...
Click to collapse
sorry, scratch that, it says:
mke2fs: lseek: value too large for defined data type
Any ideas?
Would mke3fs work to upgrade to ext3?
Type this in adb busybox mkfs.vfat /dev/block/mmcblk0p18
it just goes through a whole list of adb commands but doesn't seem to do anything, am I doing it incorrectly?
I have the same issue with my atrix. Unable to mount or use /emmc . Posting my recovery log for your reference. Any help or advice would be appreciated. Already tried reflashing the TWIZ recovery and the ROM but no luck.
Starting recovery on Wed Aug 1 05:48:04 2012
Loading volume table...
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p11 (null)
2 /cache ext4 /dev/block/mmcblk0p15 NULL
3 /data ext4 /dev/block/mmcblk0p16 NULL
4 /sdc vfat /dev/block/mmcblk1p1 (null)
5 /emmc vfat /dev/block/mmcblk0p18 (null)
6 /system ext4 /dev/block/mmcblk0p12 NULL
7 /recovery emmc /dev/block/mmcblk0p10 (null)
8 /osh ext3 /dev/block/mmcblk0p13 (null)
9 /preinstall ext3 /dev/block/mmcblk0p17 (null)
I:Internal path defined: '/emmc'
I:External path defined: '/sdc'
Pixel format: 540x960 @ 16bpp
Pixel format: BGR_565
framebuffer: fd 4 (540 x 960)
I:=> Installing busybox into /sbin
ln: /sbin/mke2fs: File exists
ln: /sbin/sh: File exists
ln: /sbin/tune2fs: File exists
I:=> Linking mtab
I:=> Getting locations
Wevice does not support /proc/emmc
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
I:'data' was 'ext4' now set to 'ext3'
I:'cache' was 'ext4' now set to 'ext3'
I:=> Created /sdc folder.
I:=> Created /osh folder.
* Verifying partition sizes...
E:Unable to mount '/emmc' (tw_mount)
E:Unable to mount '/emmc' (tw_mount)
du: /emmc/.android_secure: No such file or directory
E:Unable to mount '/osh' (tw_mount)
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p12 | ext4 | 327680 | 267096 | 1 | f |
| data | /dev/block/mmcblk0p16 | ext3 | 2097152 | 1204136 | 1 | f |
| boot | /dev/block/mmcblk0p11 | emmc | 8192 | 8192 | 0 | i |
| recovery | /dev/block/mmcblk0p10 | emmc | 8192 | 8192 | 0 | i |
| cache | /dev/block/mmcblk0p15 | ext3 | 655360 | 80816 | 1 | f |
| sdc | /dev/block/mmcblk1p1 | vfat | 15628288 | 11597696 | 1 | n |
| emmc | /dev/block/mmcblk0p18 | vfat | 11233792 | 0 | 1 | n |
| andsec | /emmc | vfat | 0 | 0 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | | 0 | 0 | 1 | f |
| osh | /dev/block/mmcblk0p13 | ext3 | 786432 | 0 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
Sent from my MB860 using Tapatalk 2
same problem with atrix 2
Hi guys, with my atrix 2 (me865) i have same problem, when i run cat /proc/partitions
output is:
179 0 7757824 mmcblk1
179 1 128 mmcblk1p1
179 2 512 mmcblk1p2
179 3 512 mmcblk1p3
179 4 512 mmcblk1p4
179 5 512 mmcblk1p5
179 6 512 mmcblk1p6
179 7 4096 mmcblk1p7 pds
179 8 512 mmcblk1p8
179 9 512 mmcblk1p9
179 10 1024 mmcblk1p10
179 11 2048 mmcblk1p11
179 12 512 mmcblk1p12
179 13 512 mmcblk1p13
179 14 4096 mmcblk1p14
179 15 8192 mmcblk1p15 boot
179 16 9216 mmcblk1p16 recovery
179 17 12288 mmcblk1p17 cdrom
179 18 512 mmcblk1p18 misc
179 19 512 mmcblk1p19 cid
179 20 4096 mmcblk1p20 kpanic
179 21 491520 mmcblk1p21 system
179 22 716800 mmcblk1p22 cache
179 23 282624 mmcblk1p23 preinstall
179 24 1368064 mmcblk1p24 webtop
179 25 4845440 mmcblk1p25 userdata
179 26 128 mmcblk1p26
179 64 1024 mmcblk1boot1
179 32 1024 mmcblk1boot0
179 96 31074304 mmcblk0
179 97 31070208 mmcblk0p1
how i can identify what block i need wipe with fdisk command?
at atrix 2 bootloader is locked, is the problem? Can i try this method?
qwerfv said:
Hi guys, with my atrix 2 (me865) i have same problem, when i run cat /proc/partitions
output is:
179 0 7757824 mmcblk1
179 1 128 mmcblk1p1
179 2 512 mmcblk1p2
179 3 512 mmcblk1p3
179 4 512 mmcblk1p4
179 5 512 mmcblk1p5
179 6 512 mmcblk1p6
179 7 4096 mmcblk1p7 pds
179 8 512 mmcblk1p8
179 9 512 mmcblk1p9
179 10 1024 mmcblk1p10
179 11 2048 mmcblk1p11
179 12 512 mmcblk1p12
179 13 512 mmcblk1p13
179 14 4096 mmcblk1p14
179 15 8192 mmcblk1p15 boot
179 16 9216 mmcblk1p16 recovery
179 17 12288 mmcblk1p17 cdrom
179 18 512 mmcblk1p18 misc
179 19 512 mmcblk1p19 cid
179 20 4096 mmcblk1p20 kpanic
179 21 491520 mmcblk1p21 system
179 22 716800 mmcblk1p22 cache
179 23 282624 mmcblk1p23 preinstall
179 24 1368064 mmcblk1p24 webtop
179 25 4845440 mmcblk1p25 userdata
179 26 128 mmcblk1p26
179 64 1024 mmcblk1boot1
179 32 1024 mmcblk1boot0
179 96 31074304 mmcblk0
179 97 31070208 mmcblk0p1
how i can identify what block i need wipe with fdisk command?
at atrix 2 bootloader is locked, is the problem? Can i try this method?
Click to expand...
Click to collapse
You're posting in the wrong section. Please go to Atrix 2 forum.
Thank you.
Related
a dev from Google Play contacted me asking for the "partion layout" for my Galaxy player 5. He replied to my usage data my device sent to him via my email. Can anyone help me help this guy? Much Appreciated
What my device apparently sent to him
This email doesn't contain any personal information.
It only contains technical information needed to improve the quality of the backup on your device.
Your help is very appreciated!
-- TECHNICAL INFORMATION --
Device detected as:
Commercial name: YP-G70
Technical name: YP-G70
Searched patch filename: partlayout4nandroid.YP-G70
Information from Android system
Device brand: samsung
Device technical name: YP-G70
Device commercial name: YP-G70
Device board name: YP-G70
Device hardware name: smdkc110
Firmware version: UEKI8
Android SDK: 10
Partition Table:
major minor #blocks name
7 0 9387 loop0
7 1 3150 loop1
179 0 7757824 mmcblk0
179 1 1 mmcblk0p1
179 5 256 mmcblk0p5
179 6 256 mmcblk0p6
179 7 1280 mmcblk0p7
259 0 1280 mmcblk0p8
259 1 5120 mmcblk0p9
259 2 10240 mmcblk0p10
259 3 7680 mmcblk0p11
259 4 7680 mmcblk0p12
259 5 296960 mmcblk0p13
259 6 137216 mmcblk0p14
259 7 65536 mmcblk0p15
259 8 1970176 mmcblk0p16
259 9 5252096 mmcblk0p17
179 8 31166976 mmcblk1
179 9 31162880 mmcblk1p1
254 0 9387 dm-0
254 1 3150 dm-1
THE MESSAGE HE SENT AS A REPLY
to me
Information about your device is rare on the internet. Would you be able to direct me to a place where I can obtain information about partition layout for that device?
Thanks,
(His name)
Sent from my Xperia Pro
any devs see this let me know if you have any info =)
Sent from my YP-G70 using Tapatalk 2
You could always do a mount command in an adb shell, and send the output but I think he wants all the partitions right?
Sent from my Nexus 7 using Tapatalk HD
zaclimon said:
You could always do a mount command in an adb shell, and send the output but I think he wants all the partitions right?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
no idea lol
LordZilo said:
no idea lol
Click to expand...
Click to collapse
As root (adb or emulator)
Code:
fdisk -l /dev/block/mmcblk0
mount
That's about all the information there is.
Meticulus said:
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 969728 7757792 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p5 9 40 256 83 Linux
/dev/block/mmcblk0p6 45 76 256 83 Linux
/dev/block/mmcblk0p7 81 240 1280 83 Linux
/dev/block/mmcblk0p8 245 404 1280 83 Linux
/dev/block/mmcblk0p9 409 1048 5120 83 Linux
/dev/block/mmcblk0p10 1053 2332 10240 83 Linux
/dev/block/mmcblk0p11 2337 3296 7680 83 Linux
/dev/block/mmcblk0p12 3301 4260 7680 83 Linux
/dev/block/mmcblk0p13 4265 41384 296960 83 Linux
/dev/block/mmcblk0p14 41389 58540 137216 83 Linux
/dev/block/mmcblk0p15 58545 66736 65536 83 Linux
/dev/block/mmcblk0p16 66741 313012 1970176 83 Linux
/dev/block/mmcblk0p17 313017 969528 5252096 83 Linux
Click to expand...
Click to collapse
This is the one (from another thread) that I used to repartition mine
thanks
I have some difficulties understanding partitions' layout of my phone. (Huawei G6-U10 ***NOT*** rooted yet)
As spec:
4 GB Internal Memory
|__ 2 GB reserved
|__ 2 GB Internal Storage
|__ Memory android option menu shows ~2 GB total (1,91 GB) but only ~1 GB (1,03 GB) available.If I connect my phone through MTP it shows as internal memory just a partition of ~ 1 GB (994 MB)
32 GB external SD
Code:
major minor #blocks name
7 1 9387 loop1
7 2 16664 loop2
7 3 10427 loop3
7 4 15624 loop4
253 0 196608 zram0
179 0 3866624 mmcblk0
179 1 512 mmcblk0p1
179 2 32 mmcblk0p2
179 3 32 mmcblk0p3
179 4 500 mmcblk0p4
179 5 500 mmcblk0p5
179 6 5592 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 65536 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 98304 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 1 mmcblk0p13
179 14 8 mmcblk0p14
179 15 32768 mmcblk0p15
179 16 65536 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 12288 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 262144 mmcblk0p20
179 21 196608 mmcblk0p21
179 22 4096 mmcblk0p22
179 23 1048576 mmcblk0p23
179 24 1048576 mmcblk0p24
179 25 974831 mmcblk0p25
179 32 2048 mmcblk0rpmb
179 64 30748672 mmcblk1
179 65 30744576 mmcblk1p1
254 1 9387 dm-1
254 4 15624 dm-4
254 2 16663 dm-2
254 3 10426 dm-3
Then I listed partition symlink by name
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p6
bkbootup -> /dev/block/mmcblk0p16
boot -> /dev/block/mmcblk0p18
cache -> /dev/block/mmcblk0p21
cust -> /dev/block/mmcblk0p20
fsc -> /dev/block/mmcblk0p13
fsg -> /dev/block/mmcblk0p12
grow -> /dev/block/mmcblk0p25
log -> /dev/block/mmcblk0p15
misc -> /dev/block/mmcblk0p22
modem -> /dev/block/mmcblk0p11
modemst1 -> /dev/block/mmcblk0p9
modemst2 -> /dev/block/mmcblk0p10
oeminfo -> /dev/block/mmcblk0p8
pad -> /dev/block/mmcblk0p7
persist -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p19
rpm -> /dev/block/mmcblk0p4
sbl1 -> /dev/block/mmcblk0p1
sdi -> /dev/block/mmcblk0p2
ssd -> /dev/block/mmcblk0p14
system -> /dev/block/mmcblk0p23
tz -> /dev/block/mmcblk0p5
userdata -> /dev/block/mmcblk0p24
Assuming a blocksize of 1024, I can see that sizes of mmcblk0p23 (/system) and mmcblk0p24 (/userdata) are 1 GB each.
1) The space unavailable from internal storage, is the /userdata partition?
2) Of the 2 GB Android doesn't show at all, 1 is obviously occupied by /system, but if the sum of all the other partitions on the first block device (except /userdata and /system) is equal to ~1,67 GB, how can it resides on the 1 GB remaining space?
3)What's the /grow mountpoint?
1 Day, 30 views, 7th page and no reply.
Have I made any mistake? Wrong category? Questions are unclear?
Bump.
Another bump.
I fear people stop reading this thread after the title, because they think it's the same old "I don't know what partitions and mountpoints are and don't want to document about it".
Please read the questions.
When I look inside /dev/block, I see a lot of partitions on mmcblk0 (and I have confirmed, just to be certain, the combined size of all partitions almost exactly equals the size of mmcblk0 on its own):
Code:
~ # ls mmcblk0*
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p20
mmcblk0p21
mmcblk0p22
mmcblk0p23
mmcblk0p24
mmcblk0p25
mmcblk0p26
mmcblk0p27
mmcblk0p28
mmcblk0p29
mmcblk0p3
mmcblk0p30
mmcblk0p31
mmcblk0p32
mmcblk0p33
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
What is even more bizarre is I get even more partitions listed when I use fdisk:
Code:
~ # fdisk -l -u /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2432 MB, 2432696320 bytes
1 heads, 16 sectors/track, 296960 cylinders, total 4751360 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 1000 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1001 1128 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 1129 10128 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 10129 4751358 2370615 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p6 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p7 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p8 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p9 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p10 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p11 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p12 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p13 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p14 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p15 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p16 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p17 163328 163839 256 76 Unknown
/dev/block/mmcblk0p18 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p19 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p20 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p21 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p22 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p23 196096 196607 256 73 Unknown
/dev/block/mmcblk0p24 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p25 200704 1835006 817151+ 83 Linux
/dev/block/mmcblk0p26 1835008 3833854 999423+ 83 Linux
/dev/block/mmcblk0p27 3833856 4095998 131071+ 83 Linux
/dev/block/mmcblk0p28 4096000 4452350 178175+ 83 Linux
/dev/block/mmcblk0p29 4452352 4456446 2047+ 33 Unknown
/dev/block/mmcblk0p30 4456448 4504942 24247+ 19 Unknown
/dev/block/mmcblk0p31 4504944 4505085 71 90 Unknown
/dev/block/mmcblk0p32 4505087 4505598 256 23 Unknown
/dev/block/mmcblk0p33 4505600 4702191 98296 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p34 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p35 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p36 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p37 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p38 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p39 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p40 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p41 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p42 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p43 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p44 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p45 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p46 163328 163839 256 76 Unknown
/dev/block/mmcblk0p47 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p48 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p49 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p50 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p51 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p52 196096 196607 256 73 Unknown
/dev/block/mmcblk0p53 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p54 200704 1835006 817151+ 83 Linux
/dev/block/mmcblk0p55 1835008 3833854 999423+ 83 Linux
/dev/block/mmcblk0p56 3833856 4095998 131071+ 83 Linux
/dev/block/mmcblk0p57 4096000 4452350 178175+ 83 Linux
/dev/block/mmcblk0p58 4452352 4456446 2047+ 33 Unknown
/dev/block/mmcblk0p59 4456448 4504942 24247+ 19 Unknown
/dev/block/mmcblk0p60 4504944 4505085 71 90 Unknown
Partition table entries are not in disk order
The thing is, those extra partitions don't seem to be in use. Running mount only lists the following partitions as mounted somewhere (irrelevant mounts excluded from the output)
Code:
/dev/block/mmcblk0p25 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p30 /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
What are all these extra partitions for?
Is this specific to my particular device (HTC One V, with firmware for Cricket Wireless), or do all Android devices have this sheer number partitions?
I installed CM 12.1 (Android 5.1.1) on my Meizu MX4 Ubuntu (16GB internal storage)
Internal storage (User) in CM is shown as 775MB (Used: 617M, free: 158.0M), but DiskInfo indicates: Data (userdata) mmcblk0p16, Used: 11,7GB, free 131MB
Diskinfo seems to show the right size (16GB minus Android-data etc), but I cannot access this space within my internal storage in cm to check the 11,7GB used (could be some ubuntu files or zip-files from flashing).
Anyone an idea how I can access the full userdata partition and how i can tell cm to show/use it?
Partition results from terminal:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 3136 loop0
179 0 15388672 mmcblk0
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 256 mmcblk0p5
179 6 384 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 6144 mmcblk0p9
179 10 512 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 10624 mmcblk0p13
179 14 2113536 mmcblk0p14
179 15 720896 mmcblk0p15
179 16 12439040 mmcblk0p16 => (userdata -> /dev/block/mmcblk0p16)
179 17 16384 mmcblk0p17
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
253 0 3136 dm-0
[email protected]:/ # du -hs /
1.2G /
: df
Filesystem Size Used Free Blksize
/dev 946.1M 64.0K 946.0M 4096
/sys/fs/cgroup 946.1M 20.0K 946.0M 4096
/mnt/asec 946.1M 0.0K 946.1M 4096
/mnt/obb 946.1M 0.0K 946.1M 4096
/storage/emulated 946.1M 0.0K 946.1M 4096
/system 1.2G 479.3M 791.6M 4096
/data 774.9M 616.9M 158.0M 4096 (=> userdata)
/cache 681.9M 808.0K 681.1M 4096
/protect_f 4.8M 56.0K 4.8M 4096
/protect_s 4.8M 52.0K 4.8M 4096
/mnt/secure/asec 774.9M 616.9M 158.0M 4096
/mnt/shell/emulated 774.9M 616.9M 158.0M 4096
/mnt/asec/mz.guitar 3.0M 1.8M 1.2M 4096
I have exactly the same issue with my MX4 and a CM13 image.
Did you find a solution ?
cm_ubu said:
I installed CM 12.1 (Android 5.1.1) on my Meizu MX4 Ubuntu (16GB internal storage)
Internal storage (User) in CM is shown as 775MB (Used: 617M, free: 158.0M), but DiskInfo indicates: Data (userdata) mmcblk0p16, Used: 11,7GB, free 131MB
Diskinfo seems to show the right size (16GB minus Android-data etc), but I cannot access this space within my internal storage in cm to check the 11,7GB used (could be some ubuntu files or zip-files from flashing).
Anyone an idea how I can access the full userdata partition and how i can tell cm to show/use it?
Partition results from terminal:
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 3136 loop0
179 0 15388672 mmcblk0
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 256 mmcblk0p5
179 6 384 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 6144 mmcblk0p9
179 10 512 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 10624 mmcblk0p13
179 14 2113536 mmcblk0p14
179 15 720896 mmcblk0p15
179 16 12439040 mmcblk0p16 => (userdata -> /dev/block/mmcblk0p16)
179 17 16384 mmcblk0p17
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
253 0 3136 dm-0
[email protected]:/ # du -hs /
1.2G /
: df
Filesystem Size Used Free Blksize
/dev 946.1M 64.0K 946.0M 4096
/sys/fs/cgroup 946.1M 20.0K 946.0M 4096
/mnt/asec 946.1M 0.0K 946.1M 4096
/mnt/obb 946.1M 0.0K 946.1M 4096
/storage/emulated 946.1M 0.0K 946.1M 4096
/system 1.2G 479.3M 791.6M 4096
/data 774.9M 616.9M 158.0M 4096 (=> userdata)
/cache 681.9M 808.0K 681.1M 4096
/protect_f 4.8M 56.0K 4.8M 4096
/protect_s 4.8M 52.0K 4.8M 4096
/mnt/secure/asec 774.9M 616.9M 158.0M 4096
/mnt/shell/emulated 774.9M 616.9M 158.0M 4096
/mnt/asec/mz.guitar 3.0M 1.8M 1.2M 4096
Click to expand...
Click to collapse
Solved
I deleted all, played around with adb parted and formatting (fastboot and adb), installed android, deleted all again, installed CM and now it works. I dont know exactly where the error was, but this way you probably can also solve the problem. Good luck!
PS: I am really disappointed from ubuntu phone. CM is exactly what I expected from ubuntu, it is great!!
i was trying to flash lineageOS 13.0 on driod razr xt912 using safestrap 3.75 right after that flash open gapp but couldn't due to low storage error of system partition so i decided to increase system memory . After googling found two way of doing , 1st parted , 2nd fdisk. After getting in error in parted so i switch to fdisk . Below are the steps i did please correct me
1) connected phone in safetrap 3.75 recovery to pc. CONNECTION WAS SUCCESSFUL . took backup of /system and /data from safetrap 3.75.
adb root
adb shell
# cat /etc/fstab
/dev/block/mmcblk1p25 /sdcard vfat rw
/sdcard-ext vfat rw
/dev/block/mmcblk1p24-orig /data ext3 rw
/dev/block/mmcblk1p21-orig /cache ext3 rw
/dev/block/mmcblk1p20-orig /system ext3 rw
/dev/block/mmcblk1p23 /osh ext3 rw
/dev/block/mmcblk1p20-orig /systemorig ext3 rw
/dev/block/mmcblk1p25 /ss vfat rw
# cat /proc/partitions
179 0 15564800 mmcblk1
179 1 128 mmcblk1p1
179 2 512 mmcblk1p2
179 3 512 mmcblk1p3
179 4 1 mmcblk1p4
179 5 512 mmcblk1p5
179 6 128 mmcblk1p6
179 7 4096 mmcblk1p7 pds
179 8 512 mmcblk1p8 utags
179 9 1024 mmcblk1p9
179 10 2048 mmcblk1p10
179 11 512 mmcblk1p11
179 12 512 mmcblk1p12
179 13 4096 mmcblk1p13
179 14 8192 mmcblk1p14 boot
179 15 9216 mmcblk1p15 recovery
179 16 217088 mmcblk1p16 cdrom
179 17 512 mmcblk1p17 misc
179 18 512 mmcblk1p18 cid
179 19 4096 mmcblk1p19 kpanic
179 20 655360 mmcblk1p20 system
179 21 1048576 mmcblk1p21 cache
179 22 622592 mmcblk1p22 preinstall
179 23 1364992 mmcblk1p23 webtop
179 24 3203072 mmcblk1p24 userdata
179 25 8401792 mmcblk1p25 emstorage
179 26 128 mmcblk1p26
179 64 2048 mmcblk1boot1
179 32 2048 mmcblk1boot0
# /sbin/fdisk /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 15.9 GB, 15938355200 bytes
16 heads, 16 sectors/track, 121600 cylinders, total 31129600 sectors
Units = sectors of 1 * 512 = 512 bytes
u (unit to sector )
p
Device Boot Start End Blocks Id System
block/mmcblk1p1 * 256 511 128 83 Linux
block/mmcblk1p2 1024 2047 512 83 Linux
block/mmcblk1p3 2048 3071 512 83 Linux
block/mmcblk1p4 3072 31105023 15550976 5 Extended
block/mmcblk1p5 4096 5119 512 83 Linux
block/mmcblk1p6 5120 5375 128 83 Linux
block/mmcblk1p7 6144 14335 4096 83 Linux
block/mmcblk1p8 14336 15359 512 83 Linux
block/mmcblk1p9 16384 18431 1024 83 Linux
block/mmcblk1p10 18432 22527 2048 83 Linux
block/mmcblk1p11 22528 23551 512 83 Linux
block/mmcblk1p12 23552 24575 512 83 Linux
block/mmcblk1p13 24576 32767 4096 83 Linux
block/mmcblk1p14 32768 49151 8192 83 Linux
block/mmcblk1p15 49152 67583 9216 83 Linux
block/mmcblk1p16 67584 501759 217088 83 Linux
block/mmcblk1p17 501760 502783 512 83 Linux
block/mmcblk1p18 502784 503807 512 83 Linux
block/mmcblk1p19 503808 511999 4096 83 Linux
block/mmcblk1p20 512000 1822719 655360 83 Linux
block/mmcblk1p21 1822720 3919871 1048576 83 Linux
block/mmcblk1p22 3919872 5165055 622592 83 Linux
block/mmcblk1p23 5165056 7895039 1364992 83 Linux
block/mmcblk1p24 7895040 14301183 3203072 83 Linux
block/mmcblk1p25 14301184 31104767 8401792 83 Linux
block/mmcblk1p26 31104768 31105023 128 83 Linux
2) i decide to make changes in (20-25)'s partition ( system to +3072M, cache to +1024M, preinstall to +1S, webtop to +1S, userdata to +3072M, emstorage to +8102M). But in order to make changes in (20-25)'s i had to delete 26's partitions but after creating new table starting and ending sector of 26's partitions remains the same . Also after i knew that safetrap 3.75 does not use preinstall, webtop for stock slot so i change them to +1S SECTORE.
d 26
d 25
d 24
d 23
d 22
d 21
d 20
3) after creating the new partitions. Table as follows
P
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 * 256 511 128 83 Linux
/dev/block/mmcblk1p2 1024 2047 512 83 Linux
/dev/block/mmcblk1p3 2048 3071 512 83 Linux
/dev/block/mmcblk1p4 3072 31105023 15550976 5 Extended
/dev/block/mmcblk1p5 4096 5119 512 83 Linux
/dev/block/mmcblk1p6 5120 5375 128 83 Linux
/dev/block/mmcblk1p7 6144 14335 4096 83 Linux
/dev/block/mmcblk1p8 14336 15359 512 83 Linux
/dev/block/mmcblk1p9 16384 18431 1024 83 Linux
/dev/block/mmcblk1p10 18432 22527 2048 83 Linux
/dev/block/mmcblk1p11 22528 23551 512 83 Linux
/dev/block/mmcblk1p12 23552 24575 512 83 Linux
/dev/block/mmcblk1p13 24576 32767 4096 83 Linux
/dev/block/mmcblk1p14 32768 49151 8192 83 Linux
/dev/block/mmcblk1p15 49152 67583 9216 83 Linux
/dev/block/mmcblk1p16 67584 501759 217088 83 Linux
/dev/block/mmcblk1p17 501760 502783 512 83 Linux
/dev/block/mmcblk1p18 502784 503807 512 83 Linux
/dev/block/mmcblk1p19 503808 511999 4096 83 Linux
/dev/block/mmcblk1p20 512016 6512016 3000000+ 83 Linux
/dev/block/mmcblk1p21 6512033 8512033 1000000+ 83 Linux
/dev/block/mmcblk1p22 8512050 8512052 1+ 83 Linux
/dev/block/mmcblk1p23 8512069 8512071 1+ 83 Linux
/dev/block/mmcblk1p24 8512088 14512088 3000000+ 83 Linux
/dev/block/mmcblk1p25 14512105 31104751 8296323+ 83 Linux
/dev/block/mmcblk1p26 31104768 31105023 128 83 Linux
w (writing)
recreating table successful
q (quit)
# mke2fs -t ext3 /dev/block/mmcblk1p20
# mke2fs -t ext3 /dev/block/mmcblk1p21
# mke2fs -t ext3 /dev/block/mmcblk1p22
# mke2fs -t ext3 /dev/block/mmcblk1p23
# mke2fs -t ext3 /dev/block/mmcblk1p24
# mkdosfs /dev/block/mmcblk1p25
#mount /dev/block/mmcblk1p20 /system/
#mount /dev/block/mmcblk1p21 /cache/
#mount /dev/block/mmcblk1p24 /data/
#mount /dev/block/mmcblk1p25 /sdcard/
# mount /dev/block/mmcblk1p25 /ss/
# mount /dev/block/mmcblk1p25 /and-sec/
4) after that wiped cache, data , andriod secure, data, webtop, system.
5) restored backup of /system and /data /
6) reboot the system
7) after Motorola logo "M" got error
ap fastboot flash mode [boot failure]
0A.77
eMMC Info: Size 16g
to return to normal mode - first press power key to power down
device is LOCKED, Status Code:0
battery ok
ok to program
Connect USB
Data cable
Invalid CG OTV [CG: system]: Invalid SP Data
Invalid CG HAB [CG: system, status: 0X004E]
Invalid CG OTV [CG: system]
8) i had to use RSD LITE to flash VRZ_XT912_9.8.2O-72_VZW-16-5_1FF.xml to boot normally.
9) after booting i check for changes i made , f**k system returns back to default partition table.
QUESTIONS
1) where do i go wrong
2) does i have to also make change in "ebr" or "mbr" after changing partitions size
4) does it relate to preinstall and webtop which i left to +1S SECTOR
5)does lineageOS 13.0 need /osh (webtop partitions) because i was flashing saw it searching for /osh for mount
6)does to safe to left the preinstall and webtop to +1S SECTOR