Hi,
after flashing a custom ROM which did not work as expected, I got "E: unable to mount ..." errors.
After investigating I formated the preload and mounted preload manually in the recovery.
Somehow my SCARD now shows additional "/0" in the path to the data, leading to data being unable to be found.
e.g. to the download folder is now located in SDCARD/0/0/0/DOWNLOAD.
I assume this happened when mounting the preload or other folders maually?!
How can I get this back?
I do not tink this is realted to any ROM or device, but I am on OMNIRom 4.4.4, CWM 5.5., GTAB 7510 Wifi
Thanks
xdatroxx
"Preload" seems to be A system partition, secondary for preloaded system apps, so you really should not be mounting that to SDCARD (internal storage) unless it's unused by the roms and you know what your doing/want that partition for personal use.
If the rom gave you that error(unable to mount..) right after installing it then I would not recommend the ROM.
Can you access SDcard eg. use the files?
sdcard should normally be seen as:
/sdcard
or:
/storage/emulated/0(or legacy)
you can mount the partitions correctly but you have to find the right partition layout for your gtab.
Related
Can someone please explain to me how to correct is problem? I'm new to installing roms and rooting. I'm using clockwork.
No app2sd partition found. Skipping format of /sd-ext.
Get rom manager app from market and flash clockwork recovery, then partition your sd card to get an ext.
Or do this with amon ra recovery.
Sent from my HTC
Thanks for the advice. I been trying to install cyanogenmod 6 on my evo. Are there any specific setting of an 8g sdcard and do i still need to install a ENGbootloader if i partition my card?
No app2sd partition found. Skipping format of /sd-ext.
--Installing: SDCARD: /clockworkmod/download/mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-supersonic-signed.zip
Finding update package...
Opening update package...
Installing update...
Welcome to Cyanogenmod-6.0.0-Supersonic!
assert failed: getprop("ro.bootloader") =="0.76.2000"
getprop("ro.bootloader")=="0.79.0000"
E: Error in /sdcard/clockworkmod/download/mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-Supersonic-signed.zip
(status 7)
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue
im having the same time of problem! help
Solution for No app2sd partition found. Skipping format of /sd-ext
Hi,
Background:
I have a beloved ZTE BLADE.
Had a new 8 GB Class6 microSD card.
I don't have external SD card reader!
Goal: To partition SD card with FAT32 and ext2 partition to use app2sd feature.
Problem: ClockWork 3.0.1.4 (CW) can't do partitioning. (Exactly it say it is done, but after it can't find ext partition.)
Message is: No app2sd partition found. Skipping format of /sd-ext
Solution:
1. adb shell - (There are some guide for beginner how to do this.)
2. umount /dev/block/mmcblk0p1 (or else parted will crash. Also fdisk can't write partition table because of used partition on same device!)
3. fdisk /dev/block/mmcblk0 partition to fat+ext2 Don't forget to write it at end!
4 Manually make ext2 fs:
#mkfs.ext2 /dev/block/mmcblk0p1
5. Manual mount of ext2 partition. ( Or else you will faced with error message later. CW will not se the EXT2 partition !!! )
Error message if you skip this step:
No app2sd partition found. Skipping format of /sd-ext.
# mount /dev/block/mmcblk0p2 /sd-ext
6. Umount ext.
# umount /dev/block/mmcblk0p2
Tadamm! Voala...
CW will be able to format EXT partition and mount it.
The trick was manual umount FAT partition + manual mount ext2.
Regards,
Robert Szabo
No known solution (so far) for Nook Color
This weird problem is showing up when I am using Clockwork to prepare my Nook Color for installing an Android installation. It is appearing pretty consistently right now.
I have looked at various solutions:
1. Creating an ext partition on the SD card
This involves going to the Advanced selection on Clockwork and partitioning the SD card. This is a bad idea, because it (obviously) wipes the SD card completely, removing Clockwork and making the SD card un- bootable. As a result, you cannot do anything else with Clockwork (including, of course, any flashing!).
2. Attempting to create an app2sd partition on the Clockwork SD
I noticed that the Clockwork image, when placed on an 8 GB SD card, leaves about 380 Mb of unallocated space. Using EASUS I attempted to allocate some space for a partition called "app2sd". I do not know if this would have solved the problem, because ASUS is unable to create the partition. When you do the Apply in EASUS, it acts like it is creating the new partition, but then it reverts everything back to unallocated.
3. Searching for solutions on the Net
This is a waste of time, because most of the solutions people have given are either not for SD cards with Clockwork on them, or they presume that you already have a flashed and running installation and suggest using an installed Clockwork in order to create the partition. Since I am trying to get it to work properly on a Clockwork SD, these solutions do not help.
What is needed is either a Clockwork installation procedure that places an app3sd partition on the SD card when the image is put on, or a way to place an app2sd partition on the card after the Clocwork image is put on it.
This of course assumes that the app2sd partition is even needed on the Clockwork SD. If it isn't, then could somene please tell me so that I ccan forget about this problem?
Otherwise, does anyone know of a way to get this partition on a Clockwork SD card?
Thanks in advance for any information...
before putting the ROM preferred to do this: put the original CWM / + volume buttons and power / do 2 wipe / replace the modified CWM / do the other 2 in advanced wipe / format system / install the ROM favorite / and you're ok .
* doing so I have solved this problem.
So I just finished putting the final tweak on a re-install of Vegan Ginger. My previous install had some issues with long boot times and the Gallery was not synchronizing with my Picasa Web Photos. The last step in the process was wiping the external SDcard which was complaining from Ginger since I formatted originally to FAT32 on my PC and was unsure of the "preferred" format for Android/Gingerbread. So I went into settings, and under sdcard2 selected "Erase". I then attempted to mount and got some errors regarding the sdcard was empty or not formatted, so I selected "Format". I attempted to re-mount again and got the same error. So I figured that I would give the CWM format a try and rebooted into CWM. I then selected "format sd-ext" and CWM complained that apps2sd did not exist. I then rebooted the tablet through the CWM main menu.
Somehow in this process my internal sdcard was formatted!
The next boot, Vegan Ginger displayed the G Tab Devs and Vegan Launch screen but would boot loop about 5 times until the screen went black.
I was able to boot into ClockWorkMod (CWM) and attempts to mount /data or /sdcard result in:
mount /sdcard
Code:
Can't mount /sdcard
Can't mount /dev/block/mmcblk3p1 (or /dev/block/mmcblk2p1)
(No such file or directory)
mount /data
Code:
Can't mount DATA:!
Can't mount /dev/block/mmcblk3p1 (or /dev/block/mmcblk2p1)
(No such file or directory)
I attempted to do a restore through CWM which resulted in a failure.
Any suggestions on how to get back to a running system? My guess is the following:
format data
format sdcard
The following information would be very helpful:
Is there any chance recovering the current system?
Is it possible to do a "system snapshot" of my tablet to avoid this issue in the future?
What is the preferred Android external SD card format?
Thanks!
Run nvflash from the dev section. There is nothing there to save anymore
I had this same issue with a 32gb micro sdcard formatted in fat32. After finally getting things back in order with nvflash/wipe/reload, Im hesitant to try again. Any idea on the cause or how to prevent it from happening?
brianafischer said:
Is it possible to do a "system snapshot" of my tablet to avoid this issue in the future?
Click to expand...
Click to collapse
In CWM, do a backup (this is the nandroid backup mentioned often here on xda)
When you boot into android, copy the backup file OFF the device, and onto a desktop PC, or a USB flash drive - anywhere but onto any storage that is on the gtab.
Repeat both those steps any time you're about to make major changes, or do any formatting, or otherwise play with sharp objects near your gtab.
When you screw the pooch, you can always copy your latest backup back to the backup directory on the gtab, and then restore from CWM. You may need to nvflash first to get the thing into some sane state, of course. But you'll have the image which will save lots of setup time after...
Hello!
I am running rooted stock Android 2.3 on LG E405 (no working 4.x ROMs exist for the device)
I have two questions:
1) What is the shell command to manually make android allow the PC to mount androids' (internal) partition as USB-drive? (I cannot think of right keywords to google this one up - please help!)
2) How does android determine which partition is which (i.e. which one to remount for the PC when connecting in "USB storage" mode), beside vold.fstab and init.rc? On android 2.3 that info is not in "framework-res.apk", so where is it? In the partition table itself?
Please help me search the forums for an answer. ANY advise is much appreciated!
This is why I ask:
I had switched data partition with internal sdcard partition.
Here's how:
Phone had a very small "/data" partition on /dev/block/mmcblk0p21 and large internal "/sdcard" partition on mmcblk0p20
So I reformatted mmcblk0p20 (ex-sdcard partition) into EXT4 and mmcblk0p21 (ex-data partition) into FAT32
Then I changed init.rc to mount mmcblk0p20 as /data type EXT4 and mmcblk0p21 as /sdcard type VFAT (mounting /sdcard was commented out in stock init.rc for some reason). This required modifying my boot image.
I have also set correct partition number in vold.fstab:
[#]dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.3/mmc_host[/#]
So basicly I now have a large /data partition and small internal /sdcard.
I'm able install up to a gigabyte of APKs and it works fine.
However, when I connect to my PC via USB into "USB Storage" mode, the phone seems to still try to unmount what was previously sdcard partition (/dev/block/mmcblk0p20), instead of what is NOW an sdcard partition (/dev/block/mmcblk0p21)
I can still send files to the phone via wi-fi and ADB, but the ability to mount it directly would be nice.
If I accidentally select "erase internal sdcard" from storage menu, that will also most likely erase what is now my /data partition, softbricking the phone.
The "factory reset" option will probably only corrupt the sdcard.
There may be other problems with that.
I am also interested in mounting the data partition in this way. Does anyone know how to do it?
I have an old Oneplus one that I would like to get working to recover some data. The phone is stuck in a bootloop. This happened out of nowhere one day while charging. I was running CM 11. I can still access twrp(version 3.0.2-0) and i can enter fastboot. The various partitions are as follows Boot(16MB), System(733MB), Data(OMB). The 0 MB in data in odd. Also the storage doesnt mount. Whenever i try to format data it says, "Failed to mount '/data'(invalid argument), unable to recreate /data/media folder, unable to mount storage". If i try to repair or change the file system, it says the same thing. Any help would be appreciated. Thanks.
Hi all.
I'm trying to make a last backup of the stock Android of my Swift 2x before flashing LineageOS. But TWRP (version 3.3.0-0) Seems unable to use the /data partition. I got various messages like:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid Argument)
I tried to format the partition: Wipe -> advanced wipe -> repair or change filesystem -> change filesystem -> ext4 but it didn't change anything.
What's wrong? What can I do?
Thanks a lot for any hint.
bumping this thread as I also ran into this issue.
When using TWRP, the data and system partitions can't be mounted. they also show up as being 0mb in size.
Because of this, no backups can be made and a full system wipe also yields errors.
What I did was change the filesystem to ext2 and then change it back again to ext4.
Doing this at least allowed me to flash crdroid, but making backups still doesn't work.
Whenever i go into TWRP again, it's the same thing again: unable to mount and partitions show up as 0 mb in size.
Anyone know what's causing this?
Wileyfox encrypts there data when you factory reset your device or after youve rooted your device .To get around this you need to do a factory reset using stock recovery once thats done then turn off the device. Then using minimum adb and fastboot type (fastboot boot twrp.img) that will boot your already installed twrp now erase data internal storage etc you'll notice you can finally delete stock os youll see internal storage is showing mbs available again etc worked for me perfectly.