I 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 that is mounted to /SDCARD. Sda9 is not getting mounted. And I cannot find out what the type of disk is.
Or better: where do I find a description of the internal disk setup of the lemax2?
thanks in advance for your feedback,
Walter
wvtienen said:
I 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 that is mounted to /SDCARD. Sda9 is not getting mounted. And I cannot find out what the type of disk is.
Or better: where do I find a description of the internal disk setup of the lemax2?
thanks in advance for your feedback,
Walter
Click to expand...
Click to collapse
Heyyo, EUI ROM chinese versions have a lot of bloatware that get their own partition...
The easiest solution is to do a format data via TWRP. It corrects the data partition and gives you full access to it again.
Doing a data wipe via TWRP does not solve the issue. Only formatting data partition does.
ThE_MarD said:
...
Doing a data wipe via TWRP does not solve the issue. Only formatting data partition does.
Click to expand...
Click to collapse
Thanks for the feedback.
I did do a format of data; that solved an issue with the data partition only showing 10gb, not 25gb.
So the situation I am showing is after the data format.
After the format there is still the sda disk of which no partition is mounted and the dm-0 data partition of 25gb.
Walter
Ah for that then I'm not too sure. Might be a question that is better suited to one of the skilled developers of ROMs as I have only tinkered
Related
Hello,
I can't figure what is exactly meaning the Partition Sdcard values in CWM.
I have an i9000, with 8Gb of flash. Some are system reserved. Available is around 6Gb.
When i run CWM, i can partition my sdcard, but i don't see what means the possible values (for 256 to 4096).
This is obviously not ruling the space left on /sdcard mountpoint (i partition to 2048, i still have nearly 6Gb available)... So what exactly means partition sdcard from CWM ??
Thank you, i can't find an answer, and i dislike, when flashing rom, following commands i don't really master (generally a partition SD 2048 / SWAP 256 or SWAP 0).
grv'
bump, sorry !
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?
Welcome to nookie cloner. This app makes a fully bootable sdcard copy of your on device ROM in a single click. For example, you may still be using CyanogenMod 7 as your nook colors default ROM and would like to test out the latest kit kat/ CyanogenMod 11 nightly. With this app you could make a fully bootable sdcard backup of CyanogenMod 7 with all of your data and apps and then install CyanogenMod 11. You would then effectively have a dual boot of cm 11 along with your old cm 7 install including all data and apps. It also works in reverse so the contents of a bootable sdcard can be flashed back as your main ROM. As far as I have tested this app should work for all nook color ROMs, even stock. Bellow information on the way this app formats sdcards can be found. I'm in the process of making changes specified by Steven676. In the meantime this app is still completely functional. If you find it useful or appreciate my work then please give the thanks button a press
Download Nookie Cloner alpha 1: https://dl.dropboxusercontent.com/u/46535328/Nookiecloner-A1.apk
Info:
Partition layout:
mmcblk1p1 - boot / fat32 size: 100 MB
mmcblk1p2 - system / ext4 size: 500 MB
mmcblk1p3 - data / ext4 size: 1000 MB
mmcblk1p4 - extended partition
mmcblk1p5 - cache / ext4 size: 400 MB
mmcblk1p6 - sdcard storage / fat32 size: whatever is leftover
Current bugs that I'm working to fix:
When the stock ROM is booted from an sdcard it doesn't mount the right fat partition so you only get 100 mb of external storage
Thanks:
Fattire - for the original idea.
racks11479 - For some essential ARM tools used in the process.
Disclaimer: I can not be held responsible for any "bad" things that happen to your nook, data, etc... because you choose to use this app on your device. To your comfort though, I have used this app for a while and have not experienced any serious implosions or explosions as of yet
rootfan said:
Welcome to nookie cloner. This app makes the creation of bootable sdcards possible right on your nook with a single click. It also works in reverse by cloning the contents of a bootable sdcard onto your devices internal storage.
Click to expand...
Click to collapse
Cool, thanks for picking up this idea and running with it!
Is source available somewhere?
Partition layout:
mmcblk1p1 - boot / fat32 size: 100 MB
mmcblk1p2 - system / ext4 size: 500 MB
mmcblk1p3 - data / ext4 size: 1000 MB
mmcblk1p4 - extended partition
mmcblk1p5 - cache / ext4 size: 400 MB
mmcblk1p6 - sdcard storage / fat32 size: whatever is leftover
Click to expand...
Click to collapse
This isn't a good partition layout, though -- both /system and /data are too small for future-proofing. I'd suggest at least 640 MB for /system (for the pending eMMC repartitioning, we're kicking around 768 MB) and 2 GB for /data. For performance reasons, you also want all the partitions (except for /boot, which is fixed in place because of first-stage bootloader limitations) to start on a 4MB boundary, though you may need to fiddle a bit with your tools to achieve this.
See the discussion on eMMC repartitioning in the dev thread beginning here for more information, particularly the bits on units and extended partition packing.
Also, you do not need a cache partition on SD card -- the ROMs and recoveries will not use it.
rootfan said:
Current bugs that I'm working to fix:
Stock ROM does not mount the sdcard partition properly. If it asks you to format the card on boot don't do it as it formats the bootable card in its entirety.
I think 4.3 doesn't mount the card properly but it should be an easy fix.
Click to expand...
Click to collapse
Honestly, the original idea was to only do this with install-location-agnostic builds (like CM11 builds from May 16 or later) -- with these, the ROM automatically figures out where everything is and you don't need to fiddle with the initramfs. If you are going to support modifying earlier builds to change the install location, please detect install-location-agnostic builds and leave them untouched.
steven676 said:
Cool, thanks for picking up this idea and running with it!
Is source available somewhere?
This isn't a good partition layout, though -- both /system and /data are too small for future-proofing. I'd suggest at least 640 MB for /system (for the pending eMMC repartitioning, we're kicking around 768 MB) and 2 GB for /data. For performance reasons, you also want all the partitions (except for /boot, which is fixed in place because of first-stage bootloader limitations) to start on a 4MB boundary, though you may need to fiddle a bit with your tools to achieve this.
See the discussion on eMMC repartitioning in the dev thread beginning here for more information, particularly the bits on units and extended partition packing.
Also, you do not need a cache partition on SD card -- the ROMs and recoveries will not use it.
Honestly, the original idea was to only do this with install-location-agnostic builds (like CM11 builds from May 16 or later) -- with these, the ROM automatically figures out where everything is and you don't need to fiddle with the initramfs. If you are going to support modifying earlier builds to change the install location, please detect install-location-agnostic builds and leave them untouched.
Click to expand...
Click to collapse
Thanks for the advice Steven. I'll try to get your suggestions implemented soon as possible. The way the app currently functions allows for the creation of bootable sdcards as far back as the stock froyo ROM. My noted bug is simply that the fat partition at mmcblk1p6 is not mounted properly. The sdcard is eaither not mounted at all (my fault) or the boot partition is mounted as the external sdcard. Perhaps it would simply be better to expand the boot partition for use as sd storage. I'll still modify it though so the new partition agnostic ROMS are not changed.
rootfan said:
My noted bug is simply that the fat partition at mmcblk1p6 is not mounted properly. The sdcard is eaither not mounted at all (my fault) or the boot partition is mounted as the external sdcard.
Click to expand...
Click to collapse
Look at /system/etc/vold.fstab (releases older than 4.3) or fstab.encore in the initramfs (4.3+); you can specify which partition of the SD card to use there.
Hi,
I have a client's tablet that shows up with "0.00 mb" of free internal storage. The device is not rooted but I can flash the device through standard recovery. Unfortunately completely re-flashing the device isn't an option.
I tried moving busybox from /system/xbin to /system/bin but that did not help.
I checked mount, and /data is not mounted. Is there some kind of check I can perform?
What are reasons why the data partition is not mounted from one day to another?
I can't find a file like /dev/block/mmcblk0p8 or similar that I could try to mount.
Any ideas what I can try?
thanks for your help,
Jan
Bump and additionally:
What app (on a non-root tablet) could possibly corrupt the data partition so that /dev/block/data is gone?
Best regards,
Jan
When i was uploading new rom, partitions connect to one. Many roms have a problems with this. Second partition has a 0MB size. I try upload stock rom by flashtool and no results. I want to restore original size. How I can do this? My phone is sony xperia lt30p.
What ROM have you flashed? Have you done a clean install, means having wiped existing Android OS before?
What's the name of the mentioned 0MB partition?
BTW:
Android comes with standard partitons as
/boot
/system
/recovery
/data
/cache
/misc
and their sizes basically are hardcoded.
Never have noticed, heard or read that when a ROM gets flashed a partition with size of 0MB will be created.
Name se
jwoegerbauer said:
What ROM have you flashed? Have you done a clean install, means having wiped existing Android OS before?
What's the name of the mentioned 0MB partition?
BTW:
Android comes with standard partitons as
/boot
/system
/recovery
/data
/cache
/misc
and their sizes basically are hardcoded.
Never have noticed, heard or read that when a ROM gets flashed a partition with size of 0MB will be created.
Click to expand...
Click to collapse
The name second partition is ,,sdcard". Tt isn't sdcard it is internal memory for photos and the like things
jareczex said:
Name se
The name second partition is ,,sdcard". Tt isn't sdcard it is internal memory for photos and the like things
Click to expand...
Click to collapse
Don't confuse /sdard and sdcard.
With regards to /sdcard:
This is NOT a partition on the internal storage memory of the device but rather the ( external ) SD card.
With regards to sdcard:
This simply is a symbolic link to device's /data/media partition what is mounted as /storage/emulated/0
And How i Can restore default memory this partition? Partition with external sdcard has other name.
OK it's the partition named /data/media you're referring to.
If a partitition shows 0MB ( can't get mounted ) then this is because it probably is encrypted. Hence decrypt it. The common method is to perform a Factory Reset. If you've TWRP installed / at your fingertips then decrypting also can be done with TWRP.
This phone is other than many phones
For me, everything you post is crazy stuff: I can not understand what the problem really is.
Since Android is on the market, it has more or less the same partition layout as shown above. And I'm pretty sure your phone has this, too.
I mean about problem, when i am installing rom, show me comunicat ,,Error instaling zip file 'external_sd/android9 sony t/open_gapps-arm-9.0-pico-20201114.zip" and i wanna get rid of this problem, across restore this partition. Do you know, what i have a mean?
My last 2 cents here: Open Gapps isn't a ROM. It's merely a suite of re-compiled Google apps.
FYI: I no longer participate this thread. I hope for you others jump in.
ok, thank you for your help. Information for other people: I can't install apps on this roms, so i want to restore this partition