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.
Does anyone know where I can find the CWM Recovery for the viper?
Sent from my LG-P999 using XDA
Bump
Sent from my LG-P999 using XDA
You can install the recoveries for the vs840 or the ms840 (lucid and connect respectively) through ROM Manager since all the sprint reps say they have the same coding but so far I haven't been able to do much other than boot into CWM. I can't make backups as it won't mount /system and when I manually mount /system for it it seems to backup but then the files just disappear :/ By the way you wouldn't happen to know the partition # of the recovery partition would you? I have a vague table laid out but it may not be 100% accurate so that info would help, or just let me know how to get into the bootloader/fastboot if you know how.
P.S. here's the table I've gotten so far with the file layouts (not 100% sure what files correspond to each partition)
Code:
/dev/block/mmcblk0p1 >IMAGE/MODEM*
/dev/block/mmcblk0p12 >Gaspra,LostFound,WCN1314_qcom_wlan_nv.bin,qcom
/dev/block/mmcblk0p14 >image/*.MBN
/dev/block/mmcblk0p22 >lost+found/,lpass/,mdm/,modem/
/dev/block/mmcblk0p23 >lost+found/
/dev/block/mmcblk0p27 >app/,bin/,build.prop,etc/,fonts/,framework/,lib/,media/,recovery/,sounds/,tts/,usbautorun.iso,usr/,xbin/ (/ ?)
/dev/block/mmcblk0p28 >lost+found/,recovery/
/dev/block/mmcblk0p29 >amit/,anr/,app/,app-private/,backup/,dalvik-cache/,data/,dontpanic/,fonta/,gesture/,img/,lgdrm/,local/,logger/,lost+found/,misc/,property/,qcks/,radio/,secure/,shared/,sutest/,system/,time/,tombstones/,wiper/,wmdrm/,wpstiles/ (/SYSTEM)
/dev/block/mmcblk0p30 >lost+found/
/dev/block/mmcblk0p31 >MPT_*,aat_result.txt,acc_calibration.dat,enable/,lost+found/,pid/,started/
Rom Development?
My wife just upgraded her EVO for this phone. I was able to find the rooting method with the superoneclick, and it worked slick. I was able to remove the sprint apps like NBA and NASCAR... but was looking for any custom rom. I had ICS running on her EVO, and since this comes with GB... I hate to go backwards. Is there anyone working on rom development for this phone yet?
some get me a dump of the stock recovey please
Also do
Code:
adb shell
Code:
cat proc/mounts
and
Code:
cat proc/partitions
Sounds like the viper has a different mount for system than its cousins.
In terminal emulator:
df to get list of partitions, if possible, and mount each on a temporary directory with loop options.. Hopefully the stock kernel supports fs wraps..
Just barely got this phone for my fiance, and I'm waiting for someone to nail this sucker to the wall.. Hopefully someone can come up with a working recovery..
Hope the above helps, because if you can df on su, especially with the -a option, if I remember right, it tells you the file systems used on each part.
Maybe once stuff settles down (because hectic is an understatement at this particular point irl, lol), I can jump in and be of more help, but right now.. It's just not the best time as I'm trying to keep a roof over our heads here..
Good luck all!
-----
Sent from my phone
using my finger... ;-)
-----
this needs testing and I still need the above mentions.
http://d-h.st/GFZ
# df -a
Filesystem Size Used Free Blksize
-a: No such file or directory
# df
Filesystem Size Used Free Blksize
/dev 400M 48K 399M 4096
/mnt/asec 400M 0K 400M 4096
/mnt/obb 400M 0K 400M 4096
# df
Filesystem Size Used Free Blksize
/dev 400M 48K 399M 4096 /mnt/asec 400M 0K 400M 4096
/mnt/obb 400M 0K 400M 4096
/mnt/extasec 400M 0K 400M 4096
/mnt/extobb 400M 0K 400M 4096 /system 1009M 348M 661M 4096
/tombstones 71M 4M 67M 4096 /firmware 1G 28M 1G 32768
/data 1G 579M 1G 4096 /persist 7M 4M 3M 4096
/cache 314M 5M 309M 4096 /LGE_RC 4M 24K 4M 4096
/mpt 15M 9M 6M 1024 /system/etc/firmware/misc_mdm 199M 22M 177M 4096 /mnt/sdcard 14G 4G 9G 32768
/mnt/secure/asec 14G 4G 9G 32768 /mnt/asec/com.droidemu.game.lite-1 12M 10M 1M 4096 /mnt/asec/com.diotasoft.spark-1 28M 26M 1M 4096
/mnt/asec/com.nelphy.android.heavenhell-1 32M 30M 1M 4096
/mnt/asec/com.mojang.minecraftpe.demo-1 8M 6M 1M 4096
#
Here are the proc/ results
Code:
# cat proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extasec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extobb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p27 /system ext4 rw,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p22 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p29 /data ext4 rw,nosuid,nodev,noatime,resuid=1000,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p30 /LGE_RC ext4 rw,nosuid,nodev,relatime,barrier=1,data=writeback 0 0
/dev/block/mmcblk0p31 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p14 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.droidemu.game.lite-2 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.mojang.minecraftpe.demo-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.nelphy.android.heavenhell-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.diotasoft.spark-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/com.nelphy.android.crazyshuttle-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
# cat proc/partitions
major minor #blocks name
7 0 12506 loop0
7 1 8348 loop1
7 2 33296 loop2
7 3 29138 loop3
7 4 28098 loop4
179 0 3780608 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 1024 mmcblk0p26
179 27 1048576 mmcblk0p27
179 28 327680 mmcblk0p28
179 29 1843200 mmcblk0p29
179 30 5120 mmcblk0p30
179 31 16384 mmcblk0p31
259 0 5120 mmcblk0p32
179 32 15558144 mmcblk1
179 33 15554048 mmcblk1p1
254 0 12505 dm-0
254 1 8347 dm-1
254 2 33295 dm-2
254 3 29137 dm-3
254 4 28098 dcode
?
sooo did you guys manage to find a cwm recovery?
im a total noob and i managed to root this phone but now i cant find a recovery :/ im still in GB
Hello,
I have a SM-P600 (32G) with failed factory reset that left the device soft-bricked so that booting to Download and recovery works, but OS-booting leaves the device freezed after boot animations (With stock-ROM). Flashing new recovery programs work and below results are from ABD Shell with CWM recovery flashed to the device.
Below are results from /proc/mounts, /partitions and /devices. It seems that NAND block device or its partitions are not listed in results.
I was wondering what can be the reasons for this behavior, and what can be done in order to get the NAND device back online?
Is there a way to manually re-initialize the device? Or some debugging tips to narrow down the problem?
Your help will be much appreciated if I manage to get this brick back alive without buying a new system board for it.
ADB cat /proc/mounts
~ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,relatime,discard,journal_checksum,j
ournal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,relatime,discard,journal_checksum,
journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
~ #
ADB cat /proc/partitions
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 4096 mmcblk0p12
259 5 20480 mmcblk0p13
259 6 4096 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 20480 mmcblk0p16
259 9 12288 mmcblk0p17
259 10 4096 mmcblk0p18
259 11 204800 mmcblk0p19
259 12 2465792 mmcblk0p20
259 13 27709440 mmcblk0p21
179 24 512 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179 32 30948352 mmcblk1
179 33 30944256 mmcblk1p1
~ #
ADB cat /proc/devices
Block devices:
1 ramdisk
259 blkext
7 loop
8 sd
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
254 device-mapper
~ #
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!!