Hi!
Partitioned my 32GB sdcard, and put CM10.2 on it, but when I check it I have only about 400mb of space or something like that. I had the same amount of space on a 4GB sdcard I used before. Why am I not able to use up the rest of the GB's?! Can someone tell me how to fix it, I don't know if I'm partitioning wrong or doing something wrong, but I want to be able to have lots of extra space for music, apps, etc. Please help! Thanks!!!
I believe you used a low level utility like dd or similar to flash an image onto a partition.
You need to run fsck on that partition, then run resize2fs to expand the ext2/3/4 partition.
Let's say your partition is /dev/block/mmcblk1p1
You would do (in a terminal):
adb reboot recovery
adb shell
# umount /dev/block/mmcblk1p1
# e2fsck /dev/block/mmcblk1p1
# resize2fs /dev/block/mmcblk1p1
After that, your partition will get expanded to whatever size you made it.
It takes a while so be patient. The larger the partition, the longer it will take.
Zenile said:
Hi!
Partitioned my 32GB sdcard, and put CM10.2 on it, but when I check it I have only about 400mb of space or something like that. I had the same amount of space on a 4GB sdcard I used before. Why am I not able to use up the rest of the GB's?! Can someone tell me how to fix it, I don't know if I'm partitioning wrong or doing something wrong, but I want to be able to have lots of extra space for music, apps, etc. Please help! Thanks!!!
Click to expand...
Click to collapse
if you got a prebaked image of a bootable cm card from somewhere, then it usually has 4 partitions on it that were set to the sizes the author of the card specified.
/boot
/system
/data
/sdcard
You would need to put the card in a PC, and use a disk partitioning utility to resize the partitions
some of the images include additional flash files that you install to expand the card's partitions for you. (succulent's), but
you have to do it as you install for the first time.
I prefer to build the card empty first, and load the boot files and zips manually.
linux tools like gparted, Parted Magic , booting from a live USB or CD work pretty well.
Windows based ones like Easus Partition master, or Paragon, not so good.
Mini Tool partition wizard (windows/free) sometimes works
this looks to be a decent write up
http://www.mobileread.com/forums/showthread.php?t=202660
mikeataol said:
...
I prefer to build the card empty first, and load the boot files and zips manually.
linux tools like gparted, Parted Magic , booting from a live USB or CD work pretty well.
Windows based ones like Easus Partition master, or Paragon, not so good.
Mini Tool partition wizard (windows/free) sometimes works
this looks to be a decent write up
http://www.mobileread.com/forums/showthread.php?t=202660
Click to expand...
Click to collapse
The write-up is also posted on XDA at http://forum.xda-developers.com/showthread.php?t=2098419. It was written back in the days of CM10.1, so to use it for CM10.2 or CM11:
Obtain the boot files: MLO, u-boot.bin, and flashing_boot.img -- as well as the files boot.img and recovery.img, from the /boot partition of the pre-made SD CM image. Make sure that MLO is the first file to copy to the freshly made /boot partition.
Substitute in the appropriate ROM and Gapps zip files corresponding to the particular CM build of interest.
This is a framework to help "boot" Android from the external SD card.
[size=+3]Motivation:[/size]
I started this because I would like to have Xposed Framework installed in my STS, but I do not want to take ANY risks of bootloop modifying internal system partition. This way I made this framework to allow me to "boot" a copy of Android resident in the external SD card, so that in case of bootloop, I simple eject the SD card and boot from internal Android.
[size=+3]News:[/size]
{new} - 2014/07/29 - New Sys2sdManager V2, supporting ROM ramdisks (custom ROMs), and some bugfixes. Please install, "unhook" and then "hook" again the sys2sd framework for the changes to take effect. There is a new recovery too, so choose the menu option to install the recovery package.
{new} - 2014/07/29 - First CM9 ROM for the STS (alpha stage). Please read the #2 topic for details.
{new} - 2014/07/28 - I am working on a port of CM9 for the Sony Tablet S using the sys2sd framework.
[size=+3]How it works[/size]
First, you must partition your external SD card, and then clone system and data from internal to external sdcard.
Next, during the normal boot process, the framework intercepts the process, test for the existence of the previously prepared external SD card, and if found it pauses the internal boot process, mounts /data and /system partition from the SD card, and then resumes the boot process.
[size=+3]Features[/size]
- Boot Android from external SD card (mount SYSTEM and DATA from external SD card).
- Functional recovery framework, using adapted TWRP from Motorola Xoom tablet.
- The recovery package can reside in internal or external storage.
- Recovery wait time with LED notification and triggering via hardware keypress.
- Can boot other versions of Android compatible with the stock STS ramdisk (custom ROMs).
- (work in progress): can boot other versions of Android with alternative ramdisk.
[size=+3]Bootloop Safety[/size]
- Only hook into 1 internal system script: /system/etc/install-recovery.sh (or install-recovery2.sh if present)
- With no external SD card present, the internal boot process takes precedence unmodified.
- /data and /system residing in external SD card, so if one mess the external /data ou /system directory, the bootloop will be limited to booting from the external sdcard.
- Working recovery: you can apply zip or backup and restore (tested!) your external SD card data and system partion. All modifications in data and system will be limited to the external SD card.
[size=+3]Limitations[/size]
- All modifications must work with the stock STS kernel. No custom kernels until kexec or unlocked bootloader.
- Write speed of the SD card.
[size=+3]Requisites[/size]
- Rooted Android 4.0.3 Sony Tablet S.
- busybox installed in /system/xbin, containing the functions: mount, tar, gzip, awk, sed. I recommend Stericson Busybox Installer on the Play Store. {new} If you do not have buysybox, the installer will install one for you.
- External SD card of size 8Gb or more, SD or Microsd. See the Drawbacks section for speed class information.
- Partitioning software to partition the external SD card. I recommend Mini Tool Partition Wizard for Windows, or GParted for Linux.
[size=+3]Drawbacks[/size]
[size=+2]Speed[/size]
Because the STS will be running Android from the external SD card (system and data), this framework heavly depends on the SD card read and write speed for disk IO.
I have tested the framework with the following SD card classes:
App loading, closing, and file IO:
Microsd class 4: damn slow browsing
Microsd class 6: slow
Microsd class 10: fast, like internal storage
Gaming:
Microsd class 4: slow loading times, gaming normal
Microsd class 6: slow loading times, gaming normal
Microsd class 10: normal
Boot process:
+20 to 40 seconds delay
[size=+3]How it works - Technical details[/size]
[size=+1]The framework executes the following steps during the boot from sd process[/size]
- Intercepts the internal Android boot process via the /system/etc/install_recovery script, then looks for the special partitioned external sdcard, and if not found resumes the normal Android boot process. Otherwise, keep executing.
- Stops the normal Android boot process, stopping all init services.
- Try to soft boot into recovery (explained bellow) if got user keypress. If the recovery process was not started, the framework resumes execution.
- Umount /data and /system from the internal flash storage.
- Mount /data and /system from the external SD card partitions.
- Restart all services and resume boot
[size=+1]The framework executes the following steps during the recovery start process[/size]
- Searches for a recovery package (recovery.tgz), in the external and internal storage system partition. If not found, cancels the recovery start process.
- If recovery package found, blinks the notification LED (blue color) and waits for user keypress to enter recovery. The recovery can also be triggered by a special recovery file present in the /cache/recovey directory (boot, command or extendedcommand files).
- If the user press some key in the wait interval or any special file are found then the recovery process continues. Otherwise, cancels the process.
- Stop all init services
- Decompress the recovery package, like a recovery ramdisk
- Umount all file systems, including internal and external storage, DM and Vold volumes.
- Soft boot the recovery Ramdisk using CHROOT busybox command
- Note: if you want to build your own alternative recovery package, special care must be taken for the /system and /data partitions in the /etc/recovery.fstab recovery file.
[size=+1]External SD card partitioning[/size]
- I recommend that the partitions in the external SD card be aligned to 4MB boundaries (8192 blocks).
- The internal /data and /system can be mirrored manualy using the following commands:
Code:
#### mount external /system in /mnt/newsys
#### mount external /data in /mnt/newdat
busybox mount -o remount,rw /
busybox mkdir -p /mnt/newsys
busybox mkdir -p /mnt/newdat
busybox mount /dev/block/mmcblk1p2 /mnt/newsys
busybox mount /dev/block/mmcblk1p3 /mnt/newdat
#### copy files
cd /system ; busybox cp -a * /mnt/newsys
cd /data ; busybox cp -a * /mnt/newdat
busybox umount /mnt/newsys
busybox umount /mnt/newdat
[size=+3]Getting started[/size]
1) Get an external SD Card and partition/format it
2) Install sys2sd into STS
3) Clone internal data and system to external SD card
4) Boot STS with external SD card inserted
5) Identify the internal and external system (important)
6) Install recovery in external SD card
[size=+1]1) Get an external SD Card and partition/format it[/size]
You must parition your external SD card before using this framework. I recommend you to use "Mini Tool Partition Wizard" for Windows, or "GParted" for Linux. I like to use fdisk for Linux, too.
I recommend that the partitions in the external SD card be aligned to 4MB boundaries (8192 blocks) for maximal write speed.
All partitions must be primary partitions. You must create 3 partitions:
- 1: Type fat32/vfat. This will be your "external sdcard" by the point of view of the Android or Recovery. The "internal sdcard" will stay the same, at the internal flash storage.
- 2: Type ext4 (without journal if you have the option). This will be your "/system" partition (system apps and Android core). For your information, the internal system for 4.0.3 Sony firmware takes about 300Mb, so this must be somewhat bigger, like 400Mb or more. I use 1Gb, in preparation for custom ROMs.
- 3: Type ext4 (without journal if possible). This will be your "/data" partition (user apps and data). Mine is 4Gb larger.
Do not forget to format the partitions after partitioning. Do not forget to save modifications in the Partitioning software (press the apply button).
Performance tips:
- If your Partitioning software has the option, use partitions starting/aligned in 4Mb boundaries (multiple of 8192 blocks), for maximal write speeds. In the Mini Tool Wizard, use MB alignment.
Code:
Disk /dev/block/mmcblk1: 15.9 GB, 15931539456 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 8192 2105344 1048576+ 83 Linux
/dev/block/mmcblk1p2 2113536 10510336 4198400+ 83 Linux
/dev/block/mmcblk1p3 10518528 12615680 1048576+ 83 Linux
- Avoid to use ext2, because it was so damn slow in my tests.
- If your Partitioning software has the option, disable ext4 journaling, because it makes the external SD card wears fast.
- If possible, mark the ext4 partitions with stripe-write=1024 blocks and stride=256 blocks.
In linux, you can use:
Code:
mkfs.ext4 -E stride=256,stripe-width=1024 -O ^has_journal /dev/mmcblk0p2
[size=+1]2) Install sys2sd into STS[/size]
Get the Sys2sd Manager, decompress it in a folder, put the partitioned SD Card in the tablet, and then run run_windows.bat (run_linux.sh is work in progress).
In the menu, choose:
- Install / Install Sys2sd and busybox
- Install / Unhook sys2sd (if previusly hooked)
- Install / Hook sys2sd into System
[size=+1]3) Clone internal data and system to external SD card[/size]
With the partioned SD Card inserted into the Tablet, enter the Sys2sd Manager, and choose:
- Clone / Clone System and Data
[size=+1]4) Boot STS with external SD card inserted[/size]
In the Sys2sd Manager, choose:
- Advanced / Reboot device
[size=+1]5) Identify the internal and external system[/size]
- If you successfuly cloned the internal Android to external SD card, it will be hard to guess if you are running the internal or external Android, because it will apear the same.
- The best way to avoid this is to change something (wallpaper, icons disposition, etc) to help identify internal and external SD card boot
- Boot into internal Android and take note of the changes (icons, wallpaper)
- Boot into external Android and compare the changes
- Take care to uniquely identify booth systems, to help prevent unwanted changes to the internal system
[size=+1]6) Install recovery in external SD card[/size]
Boot into the external Android, and in the Sys2sd Manager, choose:
- Recovery / Install Recovery
[size=+3]FAQ - Frequently Asked Questions[/size]
(Q) What is this?
(A) This is a framework to help soft boot Android from the external SD card on the Sony Tablet S (STS)?
(Q) What is soft boot?
(A) It means that it is a hook in the booting process of the internal Android, using the same Kernel e RAMDRIVE. It is not a "boot from the SD card" like supported on some devices.
(Q) How to unninstall?
(A) Remove /system/xbin/sys2sd file.
(Q) Can I boot a custom Kernel?
(A) No, until we have kexec, unlocked bootloader, or other way of executing/flashing a custom kernel.
(Q) Can I boot a custom ROM?
(A) Yes, but the ROM must be made compatible to the STS hardware, and use the stock Kernel. Simply flash the ROM into the external SD card system partition using recovery.
(Q) How secure is the Recovery module?
(A) Totaly secure. It is bounded to the external data and system partitions presents in the external SD card, so it is impossible to make changes to the internal data and system partitions. The cache, primary SD card and secondary SD card partitions will be shared between the Android versions.
(Q) How about the "Android SD card"?
(A) The "Android SD card" (do not confuse this with the internal or external storage), also know as /sdcard directory, will be the same for the internal and SD card Android versions. You can keep your books, music, videos and other data here, like you do now. Also you can place your Recovery backups here.
(Q) How about the "Android second SD card"?
(A) The "Android second SD card" will be stored on the first partition of the external SD card, and it will be visible to booth internal and SD card Android versions, depending of the Apps support for a secondary SD card. You can place your Recovery backups here also.
(Q) On Android, will apps transfered to SD card work?
(A) Probably not, because you will have two Android versions running on the same device using a shared "Android SD card". Keep the apps installed on the data partition of each Android version.
(Q) How about the Sony extra partitions?
(A) All the /configs, /dataapp, /vendor and other Sony partitions are necessary to boot the Internal stock Android. DO NOT wipe, format, clean, exclude none of the internal partitions, on the risk of a bootloop and device brick.
(Q) Can I copy the contents of the data and system in the external SD card back to the internal storage?
(A) No. It is too risk.
(Q) The Android running from the SD card is too slow.
(A) Take a faster, or class 10 SD card. Mine is running fine.
(Q) Your recovery sucks. Can I create an alternative recovery?
(A) Take my Recovery as a template.
(Q) Can I start recovery from the command line?
(A)
Code:
sys2sd recoveryctl start /path/to/recovery.tgz
(Q) Can I make a dual recovery?
(A) Yes.
Code:
File: /system/recovery/start_recovery
-----
#!/system/bin/sh
# $1 can be: vol_down, vol_up, power, internal
if [ "$1" = "vol_down" ] ; then
/system/xbin/sys2sd recoveryctl start /system/recovery/twrp.tgz
exit $?
fi
if [ "$1" = "vol_up" ] ; then
/system/xbin/sys2sd recoveryctl start /system/recovery/cwm.tgz
exit $?
fi
/system/xbin/sys2sd recoveryctl start /system/recovery/default.tgz
exit $?
(Q) How to enter Recovery?
(A) See the next question.
(Q) What is the blinking blue LED during boot?
(A) It is the notification to enter Recovery. During the blue LED blinking, press a key (volume or power) to enter Recovery - after this, the LED will pulse green to indicate it will enter Recovery, or pulse red to indicate it will NOT enter Recovery.
(Q) The clone command fails with a message of "target device not found"?
(A) Is the SD Card inserted into the tablet, partitioned and formated? Are the partitions primary partitions? Have you pressed the apply button on the partitioning software?
[size=+3]TODO[/size]
- run_linux.sh in the Sys2sd Manager
- Guide on how to make custom recovery module
- Guide on how to make custom ROM ramdisk and entry points
- (done) Guide on how to make a dual recovery
[size=+3]Introduction[/size]
This is an Unofficial CyanogenMod 9.0 port for the Sony Tablet S.
[size=+3]Working[/size]
- Display (hw accelerated)
- Touch screen
- Lock screen
- Power button
- Adjustable display brightness
- Settings App (some parts are not working)
- ADB
[size=+3]Not working[/size]
- Front camera
- Rear camera
- Volume buttons
- Audio
- GPS
- Sensors
- Wifi
- Internal SD Card
- External SD Card
- USB mtp / storage
- USB host
[size=+3]How to install[/size]
1) Install the latest sys2sd framework and get it working on an SD Card
2) Install the recovery on sys2sd
3) Download the latest flashable zip on this thread and put it on the Internal or External SD Card on the Sony Tablet S
4) Reboot into recovery (sys2sd Recovery, NOT Stock recovery)
5) {optional} Make a backup of system and data
6) Flash the downloaded zip
7) Wipe data
8) Reboot system
Please note that the changes will be limited to the Android present on the external SD Card. No changes will be made to the internal Android. Reboot and eject the SD Card to boot into internal Android.
[size=+3]Downloads[/size]
This is the flashable zip for the CM9 version:
{latest} cm9-20140729T212846.zip, 144MB
http://www.mediafire.com/download/9wha2vgie4cbqro/cm9-20140729T212846.zip
[size=+3]Warnings[/size]
DO NOT flash any of this zip using the Stock Recovery, on the risk of a device brick.
Use always the sys2sd recovery (press a key during the flashing blue LED).
RESERVED for future use 2
RESERVED for future use 3
RESERVED for future use 4
What does a blue flashing light mean?
I'm not sure but in apps it means Facebook notifications
KnightOdin said:
I'm not sure but in apps it means Facebook notifications
Click to expand...
Click to collapse
No its not even booted yet. the boot animation gets stuck, then this blue light apears
Jure220 said:
What does a blue flashing light mean?
Click to expand...
Click to collapse
The flashing blue light is the notification to press a key to enter Recovery.
Anyway, I am actually working on a port of CyanogenMod 9 using this framework.
Bazoocaze said:
Anyway, I am actually working on a port of CyanogenMod 9 using this framework.
Click to expand...
Click to collapse
Tell me if you need any help, I would be glad to help you I think we have the same goal we follow.
Edit: Check the PM
Sent from my Xperia Z2 using Tapatalk
Wow :good: This is great! Thank you so much
It really is slow with a class 4 sd card??
limax182 said:
...
Click to expand...
Click to collapse
Hi,
I am glad you are trying to use the framework.
1) "without journal" is only available if you format ext4 using the command line mkfs.ext4 on a Linux system. I am working on a way to format from the Sys2sdManager, so do not worry about this option for now.
2) Same problem. For now, choose to align to MB in the Mini Tool Parition Wizard and you will be ok.
Clone System:
Sorry for the incomplete instructions. The clone option expects the SD card to be inserted into the tablet sdcard slot.
ERROR: Target device /dev/block/mmcblk1p2 not found
Click to expand...
Click to collapse
- Is the SD Card inserted into the tablet?
- Is the SD Card really partitioned? Have you pressed the "apply" button in Mini Tool Partition Wizard?
Bazoocaze said:
Hi,
I am glad you are trying to use the framework....
Click to expand...
Click to collapse
Finally installed the external Android. The problem was I made all the 3 partitions as Logical but today I made them Primary and it worked!
Now when I tried to install Xposed it gives me this message:
View attachment 2874253
Thanks for your help!
Sorry for bad english
Oh, my. I completely forgot to say that the partitions need to be primary. I will update the first post. Thank you.
About the fault in the Xposed installer, that is a know issue in the Xposed FAQ.
This post have the workaround for that:
http://forum.xda-developers.com/showpost.php?p=52292102&postcount=7
limax182 said:
Finally installed the external Android. The problem was I made all the 3 partitions as Logical but today I made them Primary and it worked!
Now when I tried to install Xposed it gives me this message:
View attachment 2874253
Thanks for your help!
Sorry for bad english
Click to expand...
Click to collapse
Bazoocaze said:
Oh, my. I completely forgot to say that the partitions need to be primary. I will update the first post. Thank you.
About the fault in the Xposed installer, that is a know issue in the Xposed FAQ.
This post have the workaround for that:
http://forum.xda-developers.com/showpost.php?p=52292102&postcount=7
Click to expand...
Click to collapse
Totally awesome work, working on kexec to support your work.
Sent from my Sony Tablet S using Tapatalk
smgdev said:
Totally awesome work, working on kexec to support your work.
Sent from my Sony Tablet S using Tapatalk
Click to expand...
Click to collapse
Wow, man! Nice to know that.
Do you think it will soon be possible to put CM9 on the internal storage after getting kexec worked on with a few fixes? This is just way too awesome to handle and we're finally going somewhere.
Funny enough, this isn't in the development thread.
I've tried this framework but I seem to be getting issues.
I've got around some errors regarding mounting but it seems that the recovery can touch the /cache partition causing it to have the wrong permissions or something, I had to factory reset to get the /cache partition to be reformatted.
Anyway, after all of the things after and before, I've finally got this thing working, the only problem now is that the ROM is stuck in a bootloop or something (staying in the boot animation, I think it did dim slightly after 10-20 minutes).
I'm using an 8GB class 4 SD card.
@Bazoocaze let me know if anything has to be done. And also let me know if you have knowledge about kernels, I am already working on kexec.
Sent from my Sony Tablet S using Tapatalk
Hello
The following guide will explain how to free your File System root partition by moving most of your apps/games to a new partition on your external SD Card.
I recommend to use at least a Class-10 SD-HC SD Card.
I've checked the following on my ZTE Nubia Z7 Mini, but AFAIK it should be working with all Z7's versions.
(please report if you can... )
IMPORTANT!
NEVER use custom TWRP recovery ver 2.8.1 (maybe 2.8.0.... latest 2.8.3) for re-partition microSD card in this phone!
When you try to perform this operation will be erase INTERNAL phone memory instead mircoSD, GPT partition table will be damaged and your's device turn into a Hard brick.
If you have not made a backup EFS+NV of your device, it may happen that it is impossible to recover and it will turn into iPods
Thank you @Harwest
1. Backup your 64gb SD card to PC.
2. Via PC - use MiniTool Partition Wizard to create 2 partitions on your SD card.
one partition should be formatted as exFat and will be your data partition (and so will be the largest!)
second directory should be EXT4 and will be your new system partition (all apps will be installed to this partition-will see that later)
my settings are - 54gb for exFAT partition 1, and the rest for the EXT4 partition.
3. after you've done all partitioning etc, insert the SD card to your phone.
4. go to Settings --> About Phone --> Storage --> Choose Primary Storage --> SD CARD
5. restart your phone.
6. Install "Link2SD" from Google Play.
7. when you first open the App, it will ask you which type of 2nd partition you have, choose EXT4, afterwards restart phone (it will ask you to do so).
8. open Link2SD and filter the list by "ON INTERNAL" and start moving applications by choosing the app you want to move and choose "Create Link". now make sure you check all 3 checkboxes (or 4 if you have the paid version on L2SD).
you'll see that your original system partition is getting bigger! that's all
Enjoy!
Thank for this info
tnx for the info.
i used a slightly different approach:
1. repartion the internal sdcard. (enlarged the 'userdata' partition to 11.7GB, shrunk the 'grow' (internal storage) partition to 1GB).
2. go to Settings --> About Phone --> Storage --> Choose Primary Storage --> SD CARD (== external sdcard)
so apps have 11.7GB, external storage is the full size of de sdcard (here 64GB).
done.
---
Per request a tutorial:
WARNING: DANGEROUS.
you can brick your device!
I do not know if this tutorial works with a rom other than stock (or stock based; i.e.: cuoco92). Because of the built in option to set external sd as primary storage. The partition tool should work on all z7 mini and z7 max.
What will this tutorial do?
Repartition tool:
it will :
backup your partitions (in a backup folder).
change the 'userdata' partition size to the given value
change the 'storage' (called: 'grow') partition (internal sd / sdcard0) to the size left on the internal sd.
i.e.: default 'userdata' = 2GB, 'storage' = 10GB, total 12GB. When giving 11GB to the repartition tool the new layout will be: 'userdata' 11GB, 'storage' 1GB, total 12GB.
Change primary storage in ROM:
The setting 'change primary storage to SD card will change symlinks in the rom from /storage/sdcard0 to /storage/sdcard1. Result is that every app in the rom thinks sdcard1 is sdcard0.
I do not know if other roms (i.e.: Mokee / CM11) have this built in option.
The tutorial:
Preparations:
MAKE A BACKUP OF EVERYTHING AND COPY TO A COMPUTER (or external SD).
Internal storage will be backuped by the tool (and restored). But for performance empty it.
external storage will not be emptied (make a backup to be safe).
clean install is highly recommended, but not necessary.
installed rom will NOT be wiped. You can boot normally after the procedure.
CWM recovery mandatory.
adb access to the phone (so install drivers etc).
Step1: Using the resize tool (resizeZ7_1024.Rayures.v01.zip):
Repartition Internal SD (z7 Mini and z7 Max):
reboot phone to recovery
i.e.: "adb reboot recovery"
unzip the zip
run RUN.bat
or: open 'command window' in the folder and run RUN.bat
select 1 (backup - delete - rebuild)
give size for 'userdata' partition
(Z7 mini: max = 11GB). 12GB gives no usable partition. 1GB internal data partition left, which i think is needed
done
notes:
just always use the 1 option and MAKE SURE the backup has been created! When the backup is missing or broken you WILL brick.
this thread also has a lot about the partition tool, use the search.
Step2: Set external SD as primary
Boot phone.
Go to: Settings --> About Phone --> Storage --> Choose Primary Storage --> SD CARD
reboot phone
done
The tool: resizeZ7_1024.Rayures.v01.zip (5.48 MB):
original from official nubia forum:
http://bbs.nubia.cn/
my changes:
-translated to English
-enhanced recognition of phone model
-added a 'partition info' option (to see the current partition layout)
tnx to:
-all the xda people who already used the tool in: <thread>
-original dev of the tool
Have an addition to this tutorial ? please do so via PM.
rayures said:
tnx for the info.
i used a slightly different approach:
1. repartion the internal sdcard. (enlarged the 'userdata' partition to 11.7GB, shrunk the 'grow' (internal storage) partition to 1GB).
2. go to Settings --> About Phone --> Storage --> Choose Primary Storage --> SD CARD (== external sdcard)
so apps have 11.7GB, external storage is the full size of de sdcard (here 64GB).
done.
Click to expand...
Click to collapse
Yea, I know that way , but I think it's more risky than my method...
repartitioning your internal memory can cause some trouble later on upgrades etc...
but thanks anyway, If you can, post a detailed guide so people can use your method also. :good:
Hi guys!
NEVER use custom TWRP recovery ver 2.8.1 (maybe 2.8.0.... latest 2.8.3) for re-partition microSD card in this phone!
When you try to perform this operation will be erase INTERNAL phone memory instead mircoSD, GPT partition table will be damaged and your's device turn into a Hard brick.
If you have not made a backup EFS+NV of your device, it may happen that it is impossible to recover and it will turn into iPods
Best way for repartitioning Nubia Z7 mini?
OK, but which is the best and most save way for repartitioning Nubia Z7 mini? Which custom ROMs are compatible with this mod and advisable? Thanks for your help!
tie-fighter said:
OK, but which is the best and most save way for repartitioning Nubia Z7 mini? Which custom ROMs are compatible with this mod and advisable? Thanks for your help!
Click to expand...
Click to collapse
Best & safe method for repartition microSD card:
Use a laptop/computer with a card reader and software like as "MiniTool Partition Wizard Home Edition" (freeware) http://www.partitionwizard.com/free-partition-manager.html
Insert to cardreader with your's sdcard, run "Partition Wizard", select existing partition on sdcard and press "Resize/Move".
Resize partition so that the end is left free space volume approx 1....2....3Gb (as you wish).
After that select free space and press "Create", create new primary partition, format EXT2 or EXT3.
Press "Apply" for start all process.
Resize procedure of existing partition is safe, nothing is lost. But just in case you can pray, drink or smoke:laugh:
Im struggling with this, although seems easier, i think I am doing something wrong.
fbloise said:
Im struggling with this, although seems easier, i think I am doing something wrong.
Click to expand...
Click to collapse
you don't need to struggle..
Just do the safe method on post #1, follow exactly the steps I wrote and you'll be OK.
if you have any specific question please post it here. :good:
I've used the ripartition method wit an EXT4 and a exFat on my 32 gb memory.
Link2SD goes very well also with the CM12 rom.
Just few questions ...
1 - Should I format the entire system for a clean reinstall of the ROM, what would happened to the programs in ext4 partition? Should I've to re-install them or they remain stored or should I do some other action?
2 - If I'll change memory ... I've to copy the program with linux, right?
lelepanz said:
I've used the ripartition method wit an EXT4 and a exFat on my 32 gb memory.
Link2SD goes very well also with the CM12 rom.
Just few questions ...
1 - Should I format the entire system for a clean reinstall of the ROM, what would happened to the programs in ext4 partition? Should I've to re-install them or they remain stored or should I do some other action?
2 - If I'll change memory ... I've to copy the program with linux, right?
Click to expand...
Click to collapse
1. I think the best way is to use MODACO titanium backup and after rom is replaced, to restore the apps.
other method is to use Link2SD to move the apps back to phone memory (not all of them..) and then use TB same as above...
2. you can just use any partition manager software in order to copy the partitions as it. try to use Gparted live, I think it's the most clean way..
please report back what was working best for you
thanks!