General :: SD 2nd Partition Doesn't Work - MiniTool Partition Wizard?
Oct 19, 2012
I'm have been trying to create a second partition on my sd card using miniTool Partition Wizard.But in the end I never get a 2nd partition but just a smaller first one.My approach is as follows:
insert empty SD card (FAT32, 4GB)
open miniTool Partition Wizard
right click on SD card - "Move/Resize"
choose 1gb for unallocated space after - click ok
right click on 2nd partition and choose "create"
create 2nd partition with FAT32/Ext2/Ext3 (tried all options already) and "primary" and Cluster 4KB - click ok
Afterwards my SD card is still shown as one partition, but this has just 1gb less capacity then before.Neither the Wizard nor the phone detects the 2nd partition then.
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 - )
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?
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.
I have bought a cheap chinese phone that had a 4g rom. 512mb is mapped to data as p3 and p4 is mapped to internal storage which is 2g.
I have managed to work out how to delete partition4 and extend partition3 as they follow on from each other. However how do I remove all links to it in the system as it still tries to mount it on boot even though it isn't there.
I have removed the line from vold.fstab and that just crashed the external and internal sdcards and the storage section inside the system settings.
I am trying to create an sd-ext partiton so I can move applications and backup to that partition on my 4GB external SD card.
I've got ROM Manager 126.96.36.199 but when I select Partiton SD card it reboots and tries to reformat but I don't see anything on the Card just a LOST.DIR folder. I can't read the system messages when in Recovery mode cos it all happens so fast.
I tried via ADB and booted into recovery and selected the option to partition manually but still nothing. I reformatted the card with FAT32. Nothing.
I am having some issues with my Verizon Samsung Galaxy Tab SCH-i800. So the first issue is i tried to install a stock ROM to fix a corrupted cache partition. Now it tries to boot US Cellular. As of this moment the error i get when i put the device in recovery mode goes as follows:
E:failed to mount /cache (No such file or directory) E:Can't mount /cache/recovery/command # MANUAL MODE # E:failed to mount /cache (No such file or directory) E:Can't mount /cache/recovery/recovery_kernel_log [code]....
I am wondering if i can just create a new partition on a new SD card? i bought this device on ebay a couple weeks ago and i don't want to continue attempting sketchy leads for fear of hard bricking it. I am very good with performing commands via command prompt if that is necessary, also i have access to an Ubuntu 12.4 computer if that would make things easier? Also as far as i know this is equipped with android Froyo and the issue developed after the previous user attempted to update.
I have rooted my xolo a500s IPS using farmaroot but when I tried to mount system r/w for pushing some apps and removing some on system partition but it is not mounting because of that i cant make changes on system.how can I mount system partition
my verizon galaxy tab 7 (sch-1800) doesn't boot, it freezes on samsung splash. I already restored the stock rom, but it doesn't change anything. if i try to restore default with recovery mode, it says E:failed to mount cache.
how can i trace my recovery partitions all stuff, work ,process etc.? I want to know what is going on while i am entering to recovery. Because this partition is encrypted and i hope i can get some info from this trace stuff for reading the file system of the partition. My tablet running Android 4.0.3, Rooted.
I own a Galaxy Note (GT-N7000). Suddenly the IMEI went null/null and baseband unknown. Tried many things to recover from this but nothing seemed to work. I left the phone with the latest stock rom (Jellybean 4.1.2)
I then installed EFS Professional (rooting the phone first and installing BusyBox) and could connect to the phone with EFS Pro. I tried doing baseband and IEMI repair, and though the log showed it had successfully restores from .bak files in /efs partition, IMEI and baseband were still null.
So then I totally screwed it, hitting the "format EFS partition" by mistake (it was 3am by then) and didn't make a backup first. The phone wouldn't boot, so I flashed the latest stock rom again and now it continually loops when showing the Samsung logo when I turn it on. I can turn it on in download mode and recovery mode. When on recovery mode, it says /efs partition not found so I guess that makes sense.
The question here would be: is there any way I can fix it without sending it to service? Some options that sound possible:
- Flash the phone with some other custom ROM that would repartition the whole phone, thus creating an /efs partition again
- Use some nice software to recover the /efs partition
I'm sure that if a service can fix it, there should be a way I could do it as well.
I know my IMEI number (it's in the sticker on the back of the phone) so there should be a way to restore it into de efs partition, right?
If my understanding is correct, tools such as CWM Installer and RecoverX are made so that users with locked bootloaders will have the privilege of using ClockWorkMod recovery. I myself used these tools. However, now that I have unlocked my bootloader, I want to remove the CWM they installed onto my system partition. I want to know where I can find it and how I can delete it? The reason why I want to get rid of such is because the kernel I'm using now already has CWM and I see no point in keeping a separate one stored on my system partition.
I plan on buying a new 32gb sdcard for my Xperia ray. What i plan to do is letting the phone use most of the space on the sd card but creating a second partition for a different purpose.
The purpose is to use that partition just like a normal windows(ntfs or fat) usb disk and eventually making it bootable for PC's. I carry my usb stick with me that i made bootable via easyboot and installed the tools i need which i wanna get rid of if my phone has the same capabilities.
Questions are -Will a pc recognize that partition as a bootable device and eventually boot? -If yes, will i need to set anything on my android such as usb debugging etc. after connecting? -will that partition be independent from the android partition? (i guess this is a low possibility since the partition is on the sdcard and that is mounted to the android os, but may be android calls the partition sdcard thus not hugging the second partition)
how to resize the system partition on my Sanei N10. I have read quite a fair bit but i am to unsure how to do it. I have downloaded so far livesuit but unfortunately there is only chinese on the Sanei homepage. As much as i understand i need some file from them.So far i have stock rom and the device is rooted.
This is my first attempt towards creating a zip file to update the kernel using Clockworkmod Recovery (v188.8.131.52) on a Galaxy Nexus phone. My repeated attempts to flash the boot.img to the phone failed. I checked the logs to determine the cause of problem and I'm getting the "can't find boot partitionscript aborted" error that is causing the update to fail.
I see many asking how to partition the SD card on android tablet.. but I don't know why do they want to do that? Does it have effects on performance of the tablet? If so, I would like to do it too May I know if there are any risks in doing this? like losing data ?
I am using HTC explorer and a few other android devices. The main problem I face while flashing new roms is the lack of space in System partition! Is there any way to decrease the space of /data and add it to /system? Then I can use int2ext or m2sd script to move /data to /sdext!
I just rooted my brand new TD Hongmi,when i reboot to recovery and try to install the trwp .zip file i get the following message
Error: Partition table not match Installation aborted.
This message occurs when i try to flash anything from the stock recovery..I cannot flash the recovery .img file through moble uncle either, after flashing and rebooting to recovery, the stock recovery loads.
resize the system partition of an Android JB 4.2.2 on cubieboard?
I need more room (it's only 512MB) to install apps.
Well, the APP disk space (nand partition) is very small and the internal "sdcard" too big.
When I install a few applications the space runs out and the system becomes unstable.
I need to increase the nand and decrease internal sdcard to gain more room to my apps...
Well, I started the process by using the tools:
1) To unpack/repack: imgRePacker_204 2) The image ROM: sun7i_android_sugar-cubieboard2-8192cu.img (Android 4.2.2) 3) To burn to flash: PhoenixSuit1.0.6 unpacking the ROM creates a folder named sun7i_android_sugar-cubieboard2-8192cu.img.dump
So, somewhere in internet I see to change the sys_partition.fex file, and search the system nand partition:
Code: ;------------------------------>mmcblk0p8/nande [partition] name = data size = 1048576 user_type = 0x2 so, I change 1048576 to 2097152 (2097152 * 1024 = 2GB)
1) In installed android, the system has only 512MB and not 1GB as show. 2) By increasing this value, nothing happens when I repack back to IMG and flash to the nand.
(all unpak, change, pack, flash process is fine ! )