Hi!
When I go to the advanced -> show logs in our freshly ported cwm, it says:
Can't format unknown volume: /external sd
Can't format unknown volume: /mmc
What can cause these errors? I think it's just a small thing. Please help! :fingers-crossed:
sNaiL094 said:
Hi!
When I go to the advanced -> show logs in our freshly ported cwm, it says:
Can't format unknown volume: /external sd
Can't format unknown volume: /mmc
What can cause these errors? I think it's just a small thing. Please help! :fingers-crossed:
Click to expand...
Click to collapse
As far as i can tell this is a tiny fstab issue in here
https://bitbucket.org/Astrali/devic...6b399ffcc2f1728ae534/recovery.fstab?at=master
there is no entry for external SD
neither there is one for mmc
But this should not affect a backup/install of system boot recovery userdata cache or anything other you might need to flash a rom.
i got a failure message in my recovery about missing external_sd aswell on my Faea F2S
on my Faea F1 i fixed this by adding this line to recovery.fstab:
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
which is same line as entry for
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
cause /sdcard is my /external_sd
my internal sdcard is this one:
/sdcard1 vfat /dev/block/mmcblk0p20
PLEASE DONT COPY MY ENTRYS TO YOUR FSTAB!
if you dislike the warning in the log you could duplicate the entry of your /sdcard with /external_sd
Greets - Astrali
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...
Can some confirm if I understand correctly
As I understand internal GS2 memory is divided into several partitions:
/dev/block/mmcblk0p9 on /system type ext4
/dev/block/mmcblk0p7 on /cache type ext4
/dev/block/mmcblk0p1 on /efs type ext4
nil on /sys/kernel/debug type debugfs
/dev/block/mmcblk0p10 on /data type ext4
/dev/block/mmcblk0p4 on /mnt/.lfs type j4fs
/dev/block/vold/179:11 on /mnt/sdcard type vfat
So as I understand in CWM recovery:
format data formats dev/block/mmcblk0p10 on /data type ext4
format system formats /dev/block/mmcblk0p9 on /system type ext4
format cache formats /dev/block/mmcblk0p7 on /cache type ext4
wipe data / factory reset - on stock deletes everything from dir /data or just some files from dir /data
wipe cash - deletes all files from from /cache or just some files from dir /cache
wipe dalvik- deletes all files from from /data/dalvik-cache or just some files from dir /data/dalvik-cache
format /sdcard formats /dev/block/vold/179:11 on /mnt/sdcard type vfat ????
format /emmc formats what????
In what partition is bootloader?
In what partition is kernel?
In what partition is CWM recovery?
Where are located download mode (home+down+power) system/files?
From recent experience I understood that nandroid is not doing backup of all partitions. EFS partition is not backed up.
What else is not backed up and what partitions are backed up?
What partition is backed up in nandroid boot.img file?
Don't mess with them until you really know what you are doing
if bootloader gets messed up then its a brick
I really don't want to have problem and that's why I'm asking.
When you know simple basics it much safer to change ROM's
Well, if you'd search before asking questions, you'd have the information already.
Basically:
Code:
0 '/tmp' 'ramdisk' '(null)' '(null)' 0
1 '/efs' 'ext4' '/dev/block/mmcblk0p1' '(null)' 0
2 '/boot' 'emmc' '/dev/block/mmcblk0p2' '(null)' 0
3 '/recovery' 'emmc' '/dev/block/mmcblk0p6' '(null)' 0
4 '/cache' 'ext4' '/dev/block/mmcblk0p7' '(null)' 0
5 '/system' 'ext4' '/dev/block/mmcblk0p9' '(null)' 0
6 '/data' 'ext4' '/dev/block/mmcblk0p10' '(null)' -16384
7 '/preload' 'ext4' '/dev/block/mmcblk0p12' '(null)' 0
' 0 '/sdcard' 'vfat' '/dev/block/mmcblk1p1' '/dev/block/mmcblk1
9 '/sdcard1' 'vfat' '/dev/block/mmcblk0p11' '(null)' 0
Bootloader is in p2 and p3.
Kernel is in p5.
Recovery is inside the kernel.
Download mode (home+down+power) system/files is in initramfs (also kernel, basically).
Boot.img file contains the kernel if I remember correctly.
If you're concerned about partitions, back them all up with dd. However, be careful goes without saying
Sure I was looking, but short and simple answer couldn't find
Thanx
And additional questions:
So if /system (/dev/block/mmcblk0p9) is deleted, then phone still should be able to boot into download or recovery mode? (because Bootloader is in p2 and p3; Kernel is in p5.)
Can it be that in boot.img is packed p2, p3, p5 partitions?
/system comes with the ROM, so yes - you can delete it and still have recovery.
Why don't you extract the boot.img and see what's in it?
Sure I've tried to extract but..
In phone "Nandroid browser" can't open
In windows "unyaffs" says "broken image file"
In windows "DiskInternals Linux Reader" also not working
If you search you will find the post that shows how to extract on SGS2 and tools required .
jje
limmes said:
In what partition is bootloader?
In what partition is kernel?
In what partition is CWM recovery?boot.img file?
Click to expand...
Click to collapse
i always formats system and boot in cwm 4.x.x but since 5.x.x only system is present, meaning formating boot is good but is more dangerous for all users to access.
formating system solves many issues.
Is anyone using it?
Any problems so far?
How does it work? Any links to official documentation would be appreciated.
In linux in a full disk encryption setup, you have a plaintext /boot partition with the kernel and then your / is fully encrypted.
In ICS we have these partitions:
dev/block/mmcblk0p9 --- /system
/dev/block/mmcblk0p7 --- /cache
/dev/block/mmcblk0p1 --- /efs
/dev/block/mmcblk0p10 --- /data
/dev/block/vold/179:11 --- /mnt/sdcard
/dev/block/vold/179:17 --- /mnt/sdcard/external_sd
Which of these get encrypted in ICS?
The documentation from support.google.com/ics/nexus/bin/answer.py?hl=en&answer=2381815 says:
You can encrypt all the data on your phone: Google Accounts, application data, music and other media, downloaded information, and so on.
Click to expand...
Click to collapse
This seems to point out that it's only /data
And what about CWM? Does recovery boot still work? Will it still ask for a password so that it can access /mnt/sdcard?
bump... anyone?
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 guys,
My Huawei MediaPad T2 7.0 Pro (PLE-701L) only allows FAT format for external SDcard. I looked at its kernel, and in fstab.qcom, I found this:
Code:
/devices/soc.0/7864900.sdhci/mmc_host /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd
and in /system/etc/vold.fstab,
Code:
dev_mount sdcard /storage/sdcard1 auto /devices/msm_sdcc.2/mmc_host
I changed vfat to ext4 in in fstab.qcom of kernel, and repacked boot.img to boot on the fly in bootloader. It booted but did not recognize ext4 formatted external SDcard just as usual.
Do I have any points that I missed? Hope someone will give me some insights... Thanks in advance.
Q