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!
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,
CM10 recent install from CM9, which was Encrypted for work email.
Read that you can just format the partition and it will install new roms fine.
Within CM10 I can see /ExtSDCard/ and but /SDCard/ aka /emmc/ in CWM wont mount.
Going further down into CWM, emmc wont mount so it looks like it has installed the rom fine as it boots without a physical SD Card inserted? When trying to mount /emmc/ the log shows the following error "Failed to mount /dev/block.mmcblk0p11" which I assume is related.
I would like to mount and format the previously encrypted internal storage, so It could be used as /sdcard/ in CM10 so apps like Camera would work.
Thanks
Edit: Fixed English
Edit: Ok so I have worked out its /dev/block/mmcblk0p11 - cant format it ext4 then mount it using "mount -t ext4 /dev/block/mmcblk0p11 /emmc" but all the 'scheduled' tasks still think its vfat, so as a work around ill just format it as vfat.
This should be easy.... right?
busybox mkfs.vfat /dev/block/mmcblk0p11
Error:
mkfs.vfat: lseek: Value too large for defined data type
Ugh. Help me format this as vfat please
Fixed!:
Had to push a new version of busybox, which allowed vfat over 1gb.
Thanks me!
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?
I have a 2nd ext4 partition on my sdcard that has apps installed on it. After doing a CM update, all those apps are missing and I can't recreate the mount scripts.
When I go into link2sd and try to recreate the mount scripts I get a dialog asking me to choose the filesystem with this path in it:
Code:
/dev/block/mmcblk1p2
I choose ext4, because that is the filesystem of my 2nd partition, and then I get an error:
Code:
mount:'/dev/block/vold/179:66'->'data/sdext2' no such file or directory
I've verified that /data/sdext2 exists. Any help or suggestions are greatly appreciated, thanks.
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