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,
Related
Add these two zips I quickly put together to swap between 3.0.0.5 and 3.0.1.0 recovery on the same SD Card. This way if you want to test images for 2.2 Froyo you can quickly turn your SD into 3.0.0.5 and if you want to test for CM7 you can flash to 3.0.1.0 on the fly!!!
If you have any questions just ask. Please limit your questions to ONLY this topic.
xboxexpert said:
Add these two zips I quickly put together to swap between 3.0.0.5 and 3.0.1.0 recovery on the same SD Card. This way if you want to test images for 2.2 Froyo you can quickly turn your SD into 3.0.0.5 and if you want to test for CM7 you can flash to 3.0.1.0 on the fly!!!
If you have any questions just ask. Please limit your questions to ONLY this topic.
Click to expand...
Click to collapse
I would think once you have 3.0.1.0 then you should be all set for 2.2 (ext3 FS) or CM7 (ext4 FS) as 3.0.1.0 supports both while 3.0.0.5 only supports ext3 thus why it won't work with CM7 as has ext4 FS...
Perhaps I'm mistaken when you say CWR 3.0.1.0 recovery for SDcard... I'm thinking you want this to write to SDcard??? If so then this seems wrong... your uRamdisk has /etc/recovery.fstab
# mount point fstype device [device2] [fstype2]
/boot vfat /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p5 NULL ext3
/data ext4 /dev/block/mmcblk0p6 NULL ext3
/cache ext4 /dev/block/mmcblk0p7 NULL ext3
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2 NULL ext3
This will write to EMMC Not SDcard... to have recovery write to SDcard you need this file to be;
# CWR 3.0.1.0 SDcard uRecRam: /etc/recovery.fstab
# mount point fstype device [device2] [fstype2]
/boot vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk1p2 NULL ext3
/data ext4 /dev/block/mmcblk1p3 NULL ext3
/cache ext4 /dev/block/mmcblk0p7 NULL ext3
/emmc vfat /dev/block/mmcblk1p4
/sdcard vfat /dev/block/mmcblk1p4 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p4 NULL ext3
If you are just making an Sdcard that can be used to install to EMMC then sorry for commenting... but this is available in a number of different places while CWR 3.0.1.0 for Sdcard installs still doesn't exist thus why I was looking for someone to replace that file a couple days ago...
jtbnet said:
Perhaps I'm mistaken when you say CWR 3.0.1.0 recovery for SDcard... I'm thinking you want this to write to SDcard??? If so then this seems wrong... your uRamdisk has /etc/recovery.fstab
# mount point fstype device [device2] [fstype2]
/boot vfat /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p5 NULL ext3
/data ext4 /dev/block/mmcblk0p6 NULL ext3
/cache ext4 /dev/block/mmcblk0p7 NULL ext3
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2 NULL ext3
This will write to EMMC Not SDcard... to have recovery write to SDcard you need this file to be;
# CWR 3.0.1.0 SDcard uRecRam: /etc/recovery.fstab
# mount point fstype device [device2] [fstype2]
/boot vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk1p2 NULL ext3
/data ext4 /dev/block/mmcblk1p3 NULL ext3
/cache ext4 /dev/block/mmcblk0p7 NULL ext3
/emmc vfat /dev/block/mmcblk1p4
/sdcard vfat /dev/block/mmcblk1p4 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p4 NULL ext3
If you are just making an Sdcard that can be used to install to EMMC then sorry for commenting... but this is available in a number of different places while CWR 3.0.1.0 for Sdcard installs still doesn't exist thus why I was looking for someone to replace that file a couple days ago...
Click to expand...
Click to collapse
If you put these files on a SD card and boot to lets say 3.0.0.5 and flash the 3.0.1.0 it will write the files to the SDCARD and your sdcard will now boot into 3.0.1.0 recovery and you will have a 3.0.1.0 sdcard. Let me know if you understand. I think i'm explaining it correctly.
So just to be clear and state the obvious - these zip files update the recovery version on the bootable SD card and do not write anything to the eMMC recovery area. Is that correct?
faceman66 said:
So just to be clear and state the obvious - these zip files update the recovery version on the bootable SD card and do not write anything to the eMMC recovery area. Is that correct?
Click to expand...
Click to collapse
Yes I believe you are correct. Place both files on the recovery SD and when you want to flash with 3.0.0.5 for like he said "FROYO" , just flash the 3.0.5.0.zip and it will replace the recovery kernel and ramdisk. And when you feel like flashing CM7, just flash the zip for 3.0.1.0 and "vice versa" as xboxexpert said.
xboxexpert said:
If you put these files on a SD card and boot to lets say 3.0.0.5 and flash the 3.0.1.0 it will write the files to the SDCARD and your sdcard will now boot into 3.0.1.0 recovery and you will have a 3.0.1.0 sdcard. Let me know if you understand. I think i'm explaining it correctly.
Click to expand...
Click to collapse
Okay... so you are putting standard CWR 3.0.1.0 on the sdcard that can then be used to flash updates to EMMC as defined by your recovery.fstab... I guess the point being for folks who don't want flash CWR directly on EMMC so as to retain stock recovery...
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!
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
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