Hello
Initially I have an IMEI of 0000000. with ROM A107FXXU8CUG1 android 11
I installed TWRP twrp-3.7.0_11-0-a10.
I fixed E:[libfs_mgr] could not be mounted with:
mke2fs /dev/block/mmcblk0p5
mount -w -t ext4/dev/block/mmcblk0p5
with TWRP
How to solve my problem that '/metadata' mount failed (invalid argument). knowing that
mke2fs /dev/block/mmcblk0p14
mount -w -t ext4//dev/block/mmcblk0p14
do not work ?
Thanks
metadata partition is used for encryption, just ignore.
aIecxs said:
metadata partition is used for encryption, just ignore.
Click to expand...
Click to collapse
Thanks
Related
Hello , im trying to mount emmc partitions (other that system) eg recovery , but its always saying that no such device can some please let me know how to mount a emmc partiiton or perhaps view its contents?:
Command: mount -o rw -t emmc /dev/bloc/mmcblk0p10 /test
BTW there is no MTD on device
Thanks,
Hi xda !
I have a big problem with the CWM build for my Galaxy Young GT-S6310.
I have builded CWM 6.0.3.2 with the default recovery.fstab from stock recovery:
Code:
/boot emmc /dev/block/mmcblk0p8
/system ext4 /dev/block/mmcblk0p21
/data ext4 /dev/block/mmcblk0p24 length=-16384
/cache ext4 /dev/block/mmcblk0p22
/recovery emmc /dev/block/mmcblk0p13
/efs ext4 /dev/block/mmcblk0p16
/modem emmc /dev/block/mmcblk0p3
/preload ext4 /dev/block/mmcblk0p23
[/ocde]
and everything is working great, but how You can see the sdcard is missing, so I did adb shell & mount and there is what I have for internal sdcard and extsdcard
[code]
Internal sdcard:
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,gro
up_id=1023,default_permissions,allow_other 0 0
External SDcard:
/dev/block/vold/179:33 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,no
atime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepa
ge=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
and added it into fstab ( The internal sdcard with fuseblk, but without the rw..... lines ), but when I boot up the recovery, I have this
Code:
E: can't mout /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
and can't mount any partition, system, cache ecc...
What can I do ? Any suggestions ?
Solved by my self
Moving my device configs to CM10.2 introduced this weird bug on ClockWordMod. The recovery fails to mount EXT4 partitions (cache, data, system). Every other partition is recognized and vold can mount and access the sdcards in Android (flashed with older/working recovery compiled from the same files). My guess is that the fstab file is written correctly and put in the right place.
All configuration options are the same as my CM10.1 codebase. The CM10.1 CWM was working fine and was able to mount all partitions. In CM10.2 I moved everything to unified fstab, so I'm guessing I screwed up something in the configs. I'm getting "Error mounting /system!" everytime I try to mount it manually. This is a pastebin of the fstab file. Through adb I'm getting this:
Code:
~ # mount -a
mount: mounting /dev/block/cache on /cache failed: Invalid argument
mount: mounting /dev/block/data on /data failed: Invalid argument
mount: mounting /dev/block/system on /system failed: Invalid argument
Code:
~ # mount -t ext4 /dev/block/system /system
mount: mounting /dev/block/system on /system failed: Invalid argument
Any ideas?
Hi every one.
My phone is Micromax a58, jellybeen 4.2.2, ubifs filesystem, another filesystem in my device is yaffs2.
I need help to port ext4 ROM updater-script to yaffs2 and make it flashable in my device. I had tried & edited many times ext4 ROM updater-script as yaffs2. But it won't flash in my device
Mounting all points but only userdata portion was not mounting. It say
mount /data userdata
Failed to mount /dev/block/mtdblock16 on /data: Device or resource busy
mtd mount of userdata failed: Device or resource busy
This is problem. So please any on know how to make it mount and flashable via "ctr recovery".
Please help me.
Thank you.
bunny125 said:
Hi every one.
My phone is Micromax a58, jellybeen 4.2.2, ubifs filesystem, another filesystem in my device is yaffs2.
I need help to port ext4 ROM updater-script to yaffs2 and make it flashable in my device. I had tried & edited many times ext4 ROM updater-script as yaffs2. But it won't flash in my device
Mounting all points but only userdata portion was not mounting. It say
mount /data userdata
Failed to mount /dev/block/mtdblock16 on /data: Device or resource busy
mtd mount of userdata failed: Device or resource busy
This is problem. So please any on know how to make it mount and flashable via "ctr recovery".
Please help me.
Thank you.
Click to expand...
Click to collapse
So do you want the mounting point in updater-script to format it as yaffs2 and mount it? So for example in the updater-script we could add a couple lins to format the partition as yaffs2 and then mount it but it could potentially brick NAND memory (only a motherboard replacement could save you there). Or do you want the updater-script to be yaffs2?
I am sorry if I am asking too many questions but for me, it is unclear.
Thanks for responding.
I created updater-script yaffs2 it is mounting system. But not mounting userdata. It say
mount /data userdata
Failed to mount /dev/block/mtdblock16 on /data: Device or resource busy
mtd mount of userdata failed: Device or resource busy
I want to mount my data in yaffa2. And make flash on my device.
And yes I wat yaffs2 updater-script.
bunny125 said:
Thanks for responding.
I created updater-script yaffs2 it is mounting system. But not mounting userdata. It say
mount /data userdata
Failed to mount /dev/block/mtdblock16 on /data: Device or resource busy
mtd mount of userdata failed: Device or resource busy
I want to mount my data in yaffa2. And make flash on my device.
And yes I wat yaffs2 updater-script.
Click to expand...
Click to collapse
Then, instead of "mount /data", put "mount -t yaffs2 /data".
Hopefully that works and hit thanks if it did .
Thank you. It's helped.
bunny125 said:
Thank you. It's helped.
Click to expand...
Click to collapse
YAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYYYYYYYYYYYYYYYYYYYYYY!!!!!!!!!!!!!!!!! Hopefully the ROM will work bro!
Hi,
I am trying to mount ext4 image in android recovery using below command,
#mount -o loop -t ext4 /mnt/test.img /sdcard/
i am getting the following error,
mount: losetup failed 1
Can someone help me to understand what is wrong with this approach?
Regards,
Abdul