Hi Supporters,
there is a problem with my sdcard under Android 7.1.2 (root=true, adb=possible). The vFat Partition can be used, but the rest is not mounted and can not be used.
mmcblk1p1 vfat 183 GB Status : OK
mmcblk1p2 ext4 16 MB android meta Status: not mounted
mmcblk1p3 ext4 64 GB Status: not mounted (primary) (want to use that partition as adoptable Partition for extra internal memory)
mmcblk1p4 ext4 2 GB Status: not mounted (primary) (want to use that partition as SWAP Partition for extra RAM)
Trying to mount the Partition3 (64 GB) gives the error "mount: mounting /dev/block/mmcblk1p3 on /data/sdwyt2 failed: Invalid argument"
i have the apps "Apps2SD Pro" & "Link2SD" but they can't mount the 3 partitions too.
Does anyone know how i can mount and use the 3 ext4 partitions?
Solution: On devices running Android 7.0-8.1, file-based encryption (FBE) can't be used together with adoptable storage.
https://stackoverflow.com/questions...able-storage-not-available-on-device-with-nat
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...
Hey XDA Community,
I'm running into some troubles with a used Pandigital Novel tablet. I'll give a little history, I loaded a CM7 build, it (eventually) worked great. I started loading up apps, when I got a notification that I was low on disk space. I thought that odd since I replaced the internal micro SD with a 16GB class 10. I checked memory status and it says I have a maximum of 188MB (that's MEGA-bytes) and only 6MB free!
Properties-Storage shows the following:
SD Card
Total Space: 7.4GB
Available space: 7.12GB :good:
Internal storage
Total space: 188MB
Available space: 47.95MB
It looks like your script is searching for a partition file /dev/block/mmcblk1 and there isn't one there. I loaded a partition viewer app (after deleting two other apps to get some space) and it reads as follows:
Mount - None
Partition - /dev/block/mmcblk0
15193.5 MB
Mount - /sdcard
Partition - /dev/block/mmcblk0p1
305.0/7595.0 MB
Mount - None
Partition - /dev/block/mmcblk0p2
7596.7 MB
Mount - None
Partition - /dev/block/mtdblock0
2.0 MB
Mount - None
Partition - /dev/block/mtdblock1
8.0 MB
Mount - None
Partition - /dev/block/mtdblock2
1.0 MB
Mount - None
Partition - /dev/block/mtdblock3
10.0 MB
Mount - /system
Partition - /dev/block/mtdblock5
154.0/200.0 MB
Mount - /cache
Partition - /dev/block/mtdblock6
1.0/100.0 MB
Mount - /data
Partition - /dev/block/mtdblock7
140.0/168.0 MB
I tried moving apps to the SD card, but they fail... not sure why there either. I have a feeling something is really messed up in the partition tables, but I don't have the eye to see what it is or how to fix it. Guessing I need an expert to help me with a script and restore my install from backup or something. I'll keep looking around the forum, just don't want to start trying stuff and brick this thing.
Here's hoping there is a kind soul out there that can give me a hand.
~~JClouseau
Native Mount Data on Ext
Trying to get up the courage (and time) to follow the steps on XDA: Native Mount DataOnEXT. Could take some time, but would be really cool to have a couple gig for data.
So I have searched but can't seem to find what File System format should be for each partition to use this rom. Currently I have:
System - ext4
Cache - ext3
Data - F2FS
ext_sdcard - vfat
ext_data - ext4
ext_system - ext4
dock_sdcard - vfat
I read that the only partition I needed to change to make this rom work was Data to F2FS, but that doesn't seem to be the case.
How the heck do I mount my ext2 partition?
I have an lg stylo (t-mobile) rooted
My system dirs are all under various mmcblk0p#s
My ext sd is either mounted under mmcblk1 mmcblk1p1 or mounted via mount device by name script
All I want to do is get my ext2 partition mounted and visible.
Any help would be highly appreciated.
Hi all,
After having the Smartphone lex821 bricked* and recovering I now only see 10GB on the internal disk.
with adb and
# df -h
...
/dev/block/dm-0 9.7G 5.0G 4.7G 51% /data
/dev/block/dm-0 9.7G 5.0G 4.7G 51% /sdcard
...
# cat /proc/partitions gives (1kB Blocksize):
...
253 0 25536188 dm-0
I understand the dm-0 partition is about 25GB and but the mounted /data or /sdcard only has about 10GB: where did the other 15GB go?
side question:
ps: I also see in the partition table cat /proc/partitions a disk sda of about 25GB
...
8 0 25833472 sda
8 1 8 sda1
...
8 9 25536204 sda9
Is this space usable in any way? Or is this somehow the same as the dm-0 partition (or better: where do I find a description of the internal disk setup of the lemax2?)?
thanks in advance for your feedback,
Walter
* bricked and recovered with the flashone 2.0 tool. No running ...5.8.019s
Great I found the answer/solution myself...
it is here: on www dot androidbrick dot com page leeco-letv-x820-max-2-qdloader-9008-unbrick-twrpguide (sorry: cannot post a link in my message)
step 3 states: After your phone boots, you will see that its storage is abnormally 9.71 GB, to fix this just factory reset your phone choosing the option “Format Virtual SD card”. File system will be restored to normal values.
Indeed formatting the internal storage with TWRP solves the issue (and brings you back to a clean phone...)
Walter