As many of us have noticed, it is fairly easy to get an "Out of space" message when installing apps on our phones because, for some weird reason, Oppo decided that the storage part of the device should linger in the dark ages, when /userdata and /sdcard were separate partitions and you only had 2GB of data storage, even if your phone was a 32GB model.
Now, imagine that you are running KitKat and would like to try ART. This may be a bad idea as, if your data partition is more than 30% full, you will find that while converting your apps to this new format, Android will run out of space.
At OppoForums, a few bright people started looking into the issue and, of course, there is a way to improve the situation.
If you follow the steps below correctly, you should not run in any trouble. If you do not, however, you may end up spending much more time fixing your phone.
FIRST, THE THANKS SECTION
- Anders tinkered with his device’s partition table until he got to where he had grown the /userdata partition to something useable. Yes, it’s some people’s definition of “play”
- Jousa11 is the first person trying to put a guide together explaining the steps to reproduce Anders’ work. WARNING: I did no get to see said guide as Jousa quickly deleted it due to the risks involved. So, take that in account!
- Rockman for providing the last resort rescue tools in case you brick your phone
- Lucky for providing the WiFi fix
YOU WILL NEED
- An Oppo Find5 phone(!)
- A computer (Windows/Linux/Mac) with adb installed and working
- A USB cable
On your computer:
- [Optional] fastboot
On your phone (SDCard):
- parted + mke2fs + tune2fs
- [Optional] gdisk
You will use parted to work on your partition table; mke2fs and tune2fs to create ext4 filesystems on some of these partitions (parted does not know how to create ext4 partitions)
mmcblk0p21_persist_ext4.img is an image that you need to restore your /persist partition and avoid issues such as non-working WiFi.
openrecovery-twrp-126.96.36.199-find5-TP-patch.img is a patched recovery image. I know: you already have a recovery image if you are going through these steps. However, we are going to wipe it so you want to install this guy before rebooting. Note that if you forget, you can always flash it later using fastboot.
On your computer:
- adb to access your phone recovery, push files to SDCard, reboot...
- [Optional] fastboot. You will only need fastboot if you mess up your recovery partition.
WHAT IF SOMETHING GOES AWFULLY WRONG?
You may “brick” your phone. Apparently it’s near impossible to hard brick your Find5, though. See below.
First, Anders recommends making a backup of your partition table. I didn’t because I felt that if I messed something up, it would be a partitions’ content rather than the partition table but that’s not the wisest approach.
Furthermore, if you are really worried about what stilly error your fat fingers will cause (I know I should be!) you can also backup your partitions.
Backing up your partition table:
On your phone:
gdisk -b /sdcard/gpt.bin /dev/block/mmcblk0
On your phone:
dd if=/dev/block/mmcblk0p<partition id> of=/sdcard/backup-<partition id>.bin
adb pull /sdcard/gpt.bin adb pull /sdcard/backup-<partition id>.bin
OK. So, you've bricked your phone. Now what?
First, you will need Windows. So if you're on a Mac or Linux and have no access to a Windows machine/VM, er..don't brick your phone.
READY ? LET'S GET STARTED
>>>>>>>>>>>> First, Download The Files <<<<<<<<<<<<
On your computer:
UPDATE As dixxa pointed out, mke2fs and tune2fs may already be present on your device. It was not the case for me but you should check first; it seems like a good idea to use existing binaries.
adb reboot recovery adb push parted /sbin adb push mke2fs /sbin adb push tune2fs /sbin
chmod 755 /sbin/parted /sbin/mke2fs /sbin/tune2fs umount /cache umount /sdcard umount /emmc umount /data parted /dev/block/mmcblk0
CAREFUL! Do not delete any partition below 20 or you will enter "Big Oops" territory. I recommend typing carefully and, yes, staying away from copy/paste operations that may swallow a character like, say, the '2' in '20'
Note that the size value I am using here is '4GB' for /userdata (rather than 2GB). I guess you could make /userdata bigger than 4GB, in which case you would have to recompute all the offsets in the commands below(!)
# rm sdcard rm 29 # 28 thru 23 are reserved rm 28 rm 27 rm 26 rm 25 # rm recovery rm 24 # rm misc rm 23 # rm cache rm 22 # rm persist rm 21 # rm data/emmc rm 20 # now, re-create partitions but data is bigger mkpart primary 1325 5421 name 20 userdata mkpart primary 5421 5430 name 21 persist mkpart primary 5430 5967 name 22 cache mkpart primary 5967 5968 name 23 misc mkpart primary 5968 5979 name 24 recovery mkpart primary 5979 6012 name 25 reserve1 mkpart primary 6012 6019 name 26 reserve2 mkpart primary 6019 6028 name 27 reserve3 mkpart primary 6028 6062 name 28 reserve4 mkpart primary 6062MB 100% name 29 sdcard # exit parted shell q
# Notes: # -m 0: no reserved blocks # -c 0: no max mount count # -C -1: no mount count # -i -1: max_int interval between checks mke2fs -t ext4 -m 0 -L userdata /dev/block/mmcblk0p20 tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p20 mke2fs -t ext4 -m 0 -L persist /dev/block/mmcblk0p21 tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p21 mke2fs -t ext4 -m 0 -L cache /dev/block/mmcblk0p22 tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p22 # Hey look it’s an ext4 SDCard! mke2fs -t ext4 -m 0 -L sdcard /dev/block/mmcblk0p29 tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p29 # Actually to avoid errors like unable to write to root of sdcard: mkdosfs -n sdcard -F 32 /dev/block/mmcblk0p29 mount -t vfat /dev/block/mmcblk0p29 /sdcard
# Restore /persist partition mount -t ext4 /dev/block/mmcblk0p29 /sdcard # On computer adb push mmcblk0p21_persist_ext4.img /sdcard/ # On phone dd if=mmcblk0p21_persist_ext4.img of=/dev/block/mmcblk0p21
# Recovery partition: on computer adb push openrecovery-twrp-188.8.131.52-find5-TP-patch.img /sdcard/ # On phone dd if=openrecovery-twrp-184.108.40.206-find5-TP-patch.img of=/dev/block/mmcblk0p24
parted /dev/block/mmcblk0 print
Q: Is this dangerous?
A: Yes. Yes, it is.
Q: Any tip?
A: Yes. Follow these instructions carefully and if something wrong happens, unless you know what you are doing, leave your device alone and come here to ask for help.
Q: Can I hold you responsible for any damage to my phone/etc?
A: As usual, the answer is 'No'
Q: I found an error in your write-up!
A: Please let me know immediately.