Related
This thread serves as a guide to install both firerats and data2ext mods on a single rom and have them work simultaneously.
I do not take any credit for the creation of any files mentioned or attached, nor methods for the installation of each individual mod, nor roms, gapps, or otherwise mentioned content. All credit goes to those who created each mod, rom, gapps, and the methods for installing each individually. I only claim responsibility for my own research and the order and hierarchy of steps below that combine these incredible feats of development into a working system of internal storage expansion and space management.
Even though it is impossible to brick your phone using the guide below, I am not responsible if you break your device, because you have willfully chosen on your own to void your warranty by rooting your phone and installing the mods mentioned below.
To make firerats work with data2ext simultaneously, follow these over-detailed instructions EXACTLY. This is written so that anyone who has never held a smartphone in their lives can understand and do this right the first time, so those of you that know what you're doing, sorry about the length, but it should be pretty easy for you.
Note: I've uploaded some pertinent files from the following steps and added all links to all files needed so you don't have to go find them yourself. I did not include any roms, gapps, or the freespace app from the Play Store(just download from your phone, or from the link in step 6d). Links for all necessary files are in their respective steps below. The only links to a rom or gapps are for ICS. Otherwise you'll have to find and use your own downloaded roms and the correct gapps for your rom. If you would rather use the links below to download the files instead of using the ones I provided, be my guest.
I've updated this guide to make installation much easier and work with Sense roms!
Now on to the good stuff!!
Steps 1 through 7a are written for you to collect the files necessary, and to prepare your phone, sd card, and recovery for the correct method of installation of the collected files.
Steps 8 through 10 are to install the mods.
Preparation
1. Be sure to start from scratch!!! This means an UNPARTITIONED, FULLY WIPED sd card, fully wiped and rooted phone, and fully wiped recovery. Fresh file downloads for roms, gapps, and other mods you like wouldn't hurt either. If your phone is not rooted, go here, it's the best and easiest root method I've found.
1a. If you already have a partitioned sd card, insert it into your computer via a microsd adapter or other means(you cannot use your phone for this; it will not recognize that it's partitioned), delete the partitions and wipe the card using partition management software on your computer. I recommend EASEUS Partition Manager 9.1.1 Home Edition(Windows users only). If you use this program, after you delete partitions on your sd card, you will be left with unallocated space. Create a partition that takes up the entire unallocated space and set it as a Primary and FAT32 file system(remember, only do this to your sd card, NOT THE C: DRIVE!!!!).
2. Boot to recovery(hold down home, press and release power, then release home once recovery shows up)
2a. Be sure you have a recovery that supports flashing unsigned .zip files. If your recovery does not support flashing unsigned .zip files, flash a rom and then the corresponding gapps that are signed(cyanogenmod roms and gapps are the easiest way to go), boot into rom, sign in, download rom manager from Market/Play Store, open rom manager, flash clockworkmod recovery, and boot to recovery.
3. Make sure you are using latest 5.5.0.4 recovery, found here.
3a. If you are not already using the 5.5.0.4, flash the 5.5.0.4.zip in your current recovery(or follow the instructions from step 2a if you cannot flash unsigned .zip files) and reboot back into recovery.
4. In your new recovery, make sure you wipe everything, and go to advanced>partition SD card. Choose whatever size you want to have as internal storage(the 'M' means Megabyte, if you didn't already know...). I use 1024M or 2048M(i.e. 1Gb or 2Gb), depending on what mood I'm in, but it works with any of them. Then choose 0M swap size and wait for it to process.
5. Wipe everything once again(just to be safe), including sd-ext, and place your rom and preferred gapps on sd card, along with any other flashable modifications you like to use(I use the sd card speed boost, which can be found here. 2048Kb works best for my card, a 16Gb Class 4).
Note: For ICS users only! I use official, larger ICS gapps, found here(download the one next to 4.0.X, the link will be: '20120429'). The smaller gapps, as well as the current best ICS rom, can be found in whoshotjr2006's thread, here.
6. Make sure you have the latest firerats(1.5.8), which can be found here.
6a. Don't use any of the alphas or betas. Just 1.5.8. Download only the recovery-v1.5.8-CustomMTD_S.zip and boot-v1.5.8-CustomMTD_S.zip and place on sd card. Create a .txt file named 'mtdpartmap' and type 'mtd XXX XX'. These X's represent the size in numbers that you want your /system and /cache partition sizes to be, and therefore will not actually be used. See step 6b or 6c, depending on what rom you'll be using, for information on how to determine the correct partition sizes/numbers to use. DON'T KEEP THE X's IN THE FILE! REPLACE THEM WITH THE NUMBERS YOU WILL USE AFTER YOU DETERMINE WHAT YOUR /SYSTEM AND /CACHE SIZES SHOULD BE!
6b. For ICS users: If you are using the official, larger gapps, type 'mtd 190 60' into the text file and save to sd card. If you are using smaller gapps, type 'mtd 190 30'. Proceed to step 7.
6c. For Non-ICS users: To find out what numbers to replace the X's with in your mtdpartmap.txt, first wipe everything and install only the rom and gapps you'll be using this mod with. Then boot into rom, sign in, and follow step 6d. After you do this, however, you will need to repeat steps 5 and 6a, then proceed to step 7.
6d. You can download 'freespace' from the Play Store, which needs root access, and will show you the total size and space remaining for each of the /system, /data, /cache, /sdcard, and /ext partitions, so you can change the numbers in your mtdpartmap file to what you want the /system and /cache to be that best suits the rom you want to flash. The first number after 'mtd' is for the /system partition, the second number is for /cache. You can't change the /data, because it is dependent on what you set the system and cache sizes to, and will be set to what you partitioned the sd card to anyways. Also, keep at least a 5Mb allowance over what you need for both /system and /cache partitions as you will run into force closing problems if there is no breathing room, especially for the /cache partition.
7. The data2ext thread and .zip file can be found here.
7a. Download the unCoRrUpTeD_data2extV2.2.zip at the bottom of the post and place on sd card. DO NOT FLASH!!!
Summary of what should be accomplished after following steps 1 through 7a: You should now be using CWM Recovery 5.5.0.4, have a partitioned sd card, wiped everything, and placed the boot-v1.5.8-CustomMTD_S.zip, recovery-v1.5.8-CustomMTD_S.zip, unCoRrUpTeD_data2extV2.2.zip, mtdpartmap.txt, the rom and correct gapps, as well as any other mods you want to use onto your sd card. If all of this is true, move to step 8. If not, go back and find what you missed.
The Installation Process
8. Flash recovery-v1.5.8-CustomMTD_S.zip, then under mounts and storage, wipe /system, /cache, and /data in that order.
8a. Reboot to recovery(go to advanced>reboot recovery).
9. Flash rom, gapps, and whatever other mods you have or like, then flash boot-v1.5.8-CustomMTD_S.zip, then unCoRrUpTeD_data2extV2.2.zip, and reboot.
Note: the firerats installation thread for the HeroCDMA says to flash boot-v1.5.8-CustomMTD_S.zip after anything that changes the kernel specifications, but the unCoRrUpTeD_data2extV2.2.zip does not change these. The thread also says that adb is necessary to reboot; it's not. After wiping /system, /cache, and /data, just go to advanced>reboot recovery. It will work just fine, I promise. Newer recoveries don't need to use adb for this step.
10. Reboot immediately after signing in for data2ext to take effect.
That's it! You're all done! Set up your phone the way you want and start installing apps!
Summary of steps 1 through 10: By now, you should be using 5.5.0.4 recovery, have a partitioned sd card, have placed all necessary files, your rom, gapps, and other mods onto your sd card, flashed the correct files in the correct order and rebooted, signed in, and rebooted after signing in. You should now be looking at the home screen(or lockscreen) of your rom, and if you check storage from settings, you should see internal storage showing the size you partitioned the sd card to be in step 4.
Hopefully this wasn't too confusing...good luck!
If you have any questions, don't hesitate to post in this thread!
Thanks, great guide! Wish I had it back when I had my first experience...
Speaking as per my own experience:
I ended up using the latest Firerats (dunno if its an alpha or beta) since I found myself flashing different ROM's and ROM updates quite a bit, for me it didn't require the use of a boot flash, rom works fine for me (spare some thoughts on this?, maybe just not required for the Alpha/Beta as abandoned work)...
Side note:
If you dont want to download an app to flash from the market to find out the space your rom is going to use for /system (at least, and for fresh install only), simply unzip your ROM and GApps to the same directory and right click and view the properties, this is its uncompressed size, and using a 4Mb buffer my self (Id recommend 8Mb just to be safe for most), Its normally right on the money for SOD or Size On Disk...
Hammerfest said:
Thanks, great guide! Wish I had it back when I had my first experience...
Speaking as per my own experience:
I ended up using the latest Firerats (dunno if its an alpha or beta) since I found myself flashing different ROM's and ROM updates quite a bit, for me it didn't require the use of a boot flash, rom works fine for me (spare some thoughts on this?, maybe just not required for the Alpha/Beta as abandoned work)...
Side note:
If you dont want to download an app to flash from the market to find out the space your rom is going to use for /system (at least, and for fresh install only), simply unzip your ROM and GApps to the same directory and right click and view the properties, this is its uncompressed size, and using a 4Mb buffer my self (Id recommend 8Mb just to be safe for most), Its normally right on the money for SOD or Size On Disk...
Click to expand...
Click to collapse
What version of firerats are you using? And I agree with you about the unzip method, and would have included that, but I wanted it to be as easy as possible for people who don't know what they're doing, and usually, 'an app for that' is the best way to go. Not saying it isn't easy to unzip, check the size, and rezip, I just thought an app that checks it for you would have less possibility of confusion. It does make the process a bit longer, yes, but at least people don't have to mess with the file at all.
On my own side note: After the several hours spent writing, rewording, adding, changing, and moving things around in this guide, I'm pleased to say it's 100% complete. No further changes that I can see happening.
goliath714 said:
What version of firerats are you using? And I agree with you about the unzip method, and would have included that, but I wanted it to be as easy as possible for people who don't know what they're doing, and usually, 'an app for that' is the best way to go. Not saying it isn't easy to unzip, check the size, and rezip, I just thought an app that checks it for you would have less possibility of confusion. It does make the process a bit longer, yes, but at least people don't have to mess with the file at all.
On my own side note: After the several hours spent writing, rewording, adding, changing, and moving things around in this guide, I'm pleased to say it's 100% complete. No further changes that I can see happening.
Click to expand...
Click to collapse
I think 1.59 alpha... after a system crash a few months ago, i havent had the need to re-bookmark the firerats mediafire folder... I really should, and seeing as most file share hosts are closing down or restricting free access to files I really should re-download and archive them... god knows how many things I have lost because of the MAFIAA fiasco's...
Yeah that might be a good idea. Personally I've never used any alphas or betas so I really don't have any input for them lol
Sent from my HeroC using XDA
Bumping my own thread...lets get some more views for this thing! If you haven't tried it yet, or have questions about it, or simply don't know what it does, send me a message or post on this thread! It's really a very useful mod for those of you that use or like installing lots of apps...
Thanks for the guide to this. The only problem I may seem to have is that when I follow all your steps at 11b this is what I get:
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p2s apparently in use by the system; will not make a filesystem here!
Is that correct? Or am I doing something wrong?
I see no reason to use both scripts combined. The data2ext you can have 2048mb/2gb That should be more than enough space for all your apps. Although this is a good write up I see a lot of conflict with using both mods together. One or the other should do. I'd recommend data2ext. You can create a 2048 partition and it will run just fine on a class 4 or better sd. Anything lower and you might suffer glitches like screen freezing, apps missing,lock up's and reboots. If you have a stock sd or a higher capacity sd but without a class rating or class 2 then I recommend firerats mod. Also you could very well run both of these mods and have not one problem whatsoever so it just user experience and preference I'm referring to.
#Root-Hack_Mod*Always\=LTE
Hmoobphajej said:
Thanks for the guide to this. The only problem I may seem to have is that when I follow all your steps at 11b this is what I get:
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p2s apparently in use by the system; will not make a filesystem here!
Is that correct? Or am I doing something wrong?
Click to expand...
Click to collapse
You have to unmout the partition first.
#Root-Hack_Mod*Always\=LTE
App2sd
Yea, I got that too, is it not working for you.
If not, add "/system/etc/init.d/40data2ext --enable" That made it work for me. Don't add "".
after reboot and the memory still hasn't change then go back in to terminal manager and add the above line and then reboot, should work then, never got firerats to play nice with the script, so i just use data2sd
laie1472 said:
I see no reason to use both scripts combined. The data2ext you can have 2048mb/2gb That should be more than enough space for all your apps. Although this is a good write up I see a lot of conflict with using both mods together. One or the other should do. I'd recommend data2ext. You can create a 2048 partition and it will run just fine on a class 4 or better sd. Anything lower and you might suffer glitches like screen freezing, apps missing,lock up's and reboots. If you have a stock sd or a higher capacity sd but without a class rating or class 2 then I recommend firerats mod. Also you could very well run both of these mods and have not one problem whatsoever so it just user experience and preference I'm referring to.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
That's all true, but the reason I combined both is to customize the /system and /cache partitions, while still allowing my 2gb data partition to work. This way I have control over what size I want each partition to be.
goliath714 said:
That's all true, but the reason I combined both is to customize the /system and /cache partitions, while still allowing my 2gb data partition to work. This way I have control over what size I want each partition to be.
Click to expand...
Click to collapse
You can still achieve that without the combination of both mods.
#Root-Hack_Mod*Always\=LTE
In step 11 you said to reboot into rom immediately after flashing data2ext2-v7.zip and open terminal emulator. But terminal emulator isn't preinstalled in my rom. Is it ok to install it from play store after I flash data2ext2-v7.zip or this is not right?
fforward72 said:
In step 11 you said to reboot into rom immediately after flashing data2ext2-v7.zip and open terminal emulator. But terminal emulator isn't preinstalled in my rom. Is it ok to install it from play store after I flash data2ext2-v7.zip or this is not right?
Click to expand...
Click to collapse
You can install from the market
Sent from my HERO200 using xda app-developers app
ajrty33 said:
You can install from the market
Sent from my HERO200 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot!
laie1472 said:
You can still achieve that without the combination of both mods.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
How? The firerats mod allows you to change the /system and /cache partition sizes, but from what I can find, data2ext only applies the /ext partition to the /data partition to make the phone utilize the /ext partition as /data, and doesn't allow for modification of the /system and /cache partitions.
Updated
Edit: Updated again to fix minor wording issues and make links much prettier!
Can I use twrp recovery on this firerats. Or is it only the provided cwm recovery ?
Sent from my HERO200
So I flashed this data2ext on my desire, the phone recognized my ext partition as internal memory, but, I can't install any apps, I always get the message "application not installed".
Any ideas?
dankdank11 said:
Can I use twrp recovery on this firerats. Or is it only the provided cwm recovery ?
Click to expand...
Click to collapse
Firerats has nothing to do with recovery. It's about resizing partitions. Recovery functions on a level above, so whatever you do with firerats won't affect it. TWRP is a great recovery program.
Tux2609 said:
So I flashed this data2ext on my desire, the phone recognized my ext partition as internal memory, but, I can't install any apps, I always get the message "application not installed". Any ideas?
Click to expand...
Click to collapse
Try again. Go through the instructions verbatim, as outlined. I wouldn't deviate in any way.
Hello everyone
This is CWM-Zip script to repartition our N7100 to gain 1.9 GB more for user data partition.
This script is originally from http://forum.xda-developers.com/galaxy-s3/development/guide-extra-1-3-gb-user-data-t2762594 It’s for GT-i9300. Made by @forumber2 :good:. Thanks to him, without his easy simple script, I wouldn’t be able to port this script.
This is how Samsung partitioned N7100
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After running the script
Please note that this script is not suitable to ROMs that require storing big files in CACHE and PRELOAD or HIDDEN, notably Official ROMs, as you can see that CACHE and PRELOAD got shrank.
I’m not sure if there are some custom ROMs that store files in CACHE and PRELOAD, so check the ROMs installation zip first before using this repartition script. Check by reading update-binary in META-INF and observing folder structure inside the zip file.
I’m using DN3 v5+ and it doesn’t store any files.
I checked Omega v29, it doesn't use PRELOAD to store files, even wiping it before install.
X-Treme v2.1 is safe to install, even wiping PRELOAD before install.
BIG UPDATE 1
For some ROMs like Phoenix ROM requires storing data to PRELOAD, but not CACHE.
Use partition script "Repartition_N7100_16GB_PreloadStockSize587MB.zip" instead of "Repartition_N7100_16GB.zip"
It will partition PRELOAD to size of Stock 587 MBs.
CACHE remains 100 MBs, and SYSTEM remains around 2 GBs. GAINED USERDATA FREE SPACE IS AROUND 1328 MBs.
If your ROM .zip installer doesn't store files in PRELOAD, use "Repartition_N7100_16GB.zip" instead.
FYI, Big CACHE partition is used to store official Samsung OTA updates file, if you are on custom ROMs, then you can’t use Samsung OTA updates anyway. Big cache partition is practically waste of free space, but it is still required for Google Play APK downloads. (Max Google Play APK size is 50 MBs) In fact, Google Play apk downloads are stored in /data/com.android.providers.downloads/files/, cache partition is used to store apk downloads in old Android version. This script will partition CACHE with size of 100 MBs. For any Google Play apps that are bigger than 50 MB, they will use expansion files called .obb to help, those obb are stored in "Internal SD Card/Android/obb".
Samsung Apps APK downloads sometimes can be seen large to something like 300 MBs, but these APK downloads are stored in "/data/data/com.sec.android.app.samsungapps/files" So it won't break Samsung Apps downloads.
PRELOAD or HIDDEN is used to store Samsung crap stuffs like ringtones, Wonders of Nature video, starter beautiful images, VODB folder that is used for S-Pen stroke recognition. When user make a factory reset, all data in internal sd card gets deleted, then stuffs in PRELOAD gets copy to internal sd card. That’s why after factory reset Wonder of Nature video comes back.
ALL USERDATA AND INSTALLED OS ARE GOING TO BE REMOVED, SO BACKUP FIRST!
So let’s get started. You will use "Repartition_N7100_16GB.zip OR Repartition_N7100_16GB_PreloadStockSize587MB.zip OR in the attachment
1.Backup of course, if you don’t do System Nandroid backup, be sure to have ROM installer zip ready in external sd card, if you do Nandroid backup or Titanium Backup, make sure to back up to external sd card because this process will erase internal sd card too.You may backup your internal sd card to external sd card, USB-OTG, or Windows PC.
2.You need to use PhilZ Recovery, it doesn’t work with TWRP, TWRP lacks of “parted” binary required for repartitioning.
I personally used PhilZ Touch 6.25.0 on my N7100. 6.41.6 reported to work as well.
3.Install the ZIP and the script will run, after it finished, it will reboot recovery again.
4.We are not done yet, this script still has some bug that formatted partition can’t be mounted. You can see that you can’t mount some partitions or maybe all, weird.
5.We need to fix mount problem manually by go to Mounts and Storage, then format System, Data, Cache, Preload or Hidden one by one, then go to Power Option and reboot recovery once. DO NOT FORMAT BOOT, MODEM, STORAGE/SDCARD1 (external sd card).
6.We have repartition successfully. Now restore data, install ROMs.
How to restore original stock partition table.
You will need to do this if you want to install stock official firmware.
1 - Download "Odin3_v3.07_with_PIT_16GB_GT-N7100.zip" and extract it somewhere
2 - Download any stock ROM from sammobile.com or samsung-updates.com and unzip it.
2 - Open Odin, click "PIT" button and select " PIT_N7100_16GB_20121102.pit"
3 - Click "PDA" and select official ROM that you've downloaded
4 - Click "Start"
5 - After installation, phone will be stuck at bootanimation, don't panic.
6 - Pull out battery, boot to recovery (you can see some mount errors, don't worry)
7 - Select "wipe data/factory reset" in recovery menu
8 - Select "reboot system now"
I recently update 4.3 MJ5 to 4.4.2 ND3 bootloader via odin successfully, just to inform that after repartition, bootloader update still works. If it fails, make sure to try new usb cable. Mine failed first time because of bad usb cable.
See ND 4.4.2 bootloader here http://forum.xda-developers.com/showthread.php?t=2472270 CTRL+F in the thread and find bootloader.
For some people who curious how to output partition table in Terminal.
First you need to install "parted" binary to /system/bin/
parted binary is in attachment,
then use these command in terminal
su
parted /dev/block/mmcblk0
print
Also programs to show partition tables in Google Play can't show partitions offsets, but this command could.
UPDATE 15/10/2014
I found out that in fact, Google Play apk downloads are stored in /data/com.android.providers.downloads/files/, cache partition is used to store apk downloads in old Android version.
UPDATE 24/10/2015
I also uploaded a new partition script cwm-zip file for AOSP users that will repartition system to size of 1 GB, preload 15 mb, cache 100 mb.
This will gain 3 GB of more userdata space.
Please note that once you have repartition with Repartition AOSP N7100 System 1 GB.zip
You will not be able to install Touchwiz based ROM, Touchwiz based ROMs are bigger than 1 GB.
You will have to repartition again with Repartition_N7100_16GB.zip OR Repartition_N7100_16GB_PreloadStockSize587MB.zip, note that all userdata will be deleted.
Note that I personally don't use Note 2 anymore, but this script should work. It's just simple script editing from previous files.
1 GB system partitioning for AOSP/CM is not working as
psndna88, AGNI kernel maker, tests
"it seems we cannot change SYSTEM size, else the bootloader boots only into download mode"
Thanks a lot. I will try it later.
I did repartition my device about a year ago, but I did it manually and used parted program that comes with cwm recovery. The process is fairly simple if you are familiar with unixlike OS'es. The advantage of parted us that you can resize /system partition too (CM11 requires just 400 mb on /system, and default is 1800mb).
I just tried it. It all went fine. Thanks!
My question is, can we have more space, or this is the max we can have?
I guess some space must be reserved though, so the phone can work properly.
steff195 said:
I just tried it. It all went fine. Thanks!
My question is, can we have more space, or this is the max we can have?
I guess some space must be reserved though, so the phone can work properly.
Click to expand...
Click to collapse
Yes we can have just a little bit more space. You may try to shrink cache partition to 60 mbs, shrink preload to 4 mb. That would gain 54 mbs only. I configured cache and preload to be bigger than this for safety purpose. Maybe it will be use to store small files in the future. We also need to keep the number of partitions to be the same as stock one, else everything will malfunction. I still have no ideas what does OTA and TOMBSTONES do.
Sent from my GT-N7100 using XDA Free mobile app
great guide, will try
reminds me of the htc days when we could s off and flash various hboots to increase/decrease various partitions
so, this will accomodate all current custom roms ? edit - just read your warning to check : thanks:
ninekaw9 said:
Yes we can have just a little bit more space. You may try to shrink cache partition to 60 mbs, shrink preload to 4 mb. That would gain 54 mbs only. I configured cache and preload to be bigger than this for safety purpose. Maybe it will be use to store small files in the future. We also need to keep the number of partitions to be the same as stock one, else everything will malfunction. I still have no ideas what does OTA and TOMBSTONES do.
Sent from my GT-N7100 using XDA Free mobile app
Click to expand...
Click to collapse
Then I'll just leave it this way. Don't want my phone to malfunction if I push this to the extreme.
Thanks again!
steff195 said:
Then I'll just leave it this way. Don't want my phone to malfunction if I push this to the extreme.
Thanks again!
Click to expand...
Click to collapse
only a small problem, it does not format anything and says that there is no sim inside, I sincerely hope that you manage to solve the problem ....
also the modem is not installed ...
I saw your post on the DN3 V5+ thread which led me... Seems to be a great concept, especially considering that one of the first things I do upon flashing a stock-based rom is to delete most Sammy things on it.
I understand that you need Philz to flash this; will the latest V6.41.4 do?
Also, do you know of anyway to save all system settings so as to restore them later? I can backup apps and their data but not the stock system settings themselves.
Can we increase system partition???
I need more space in system......
ulkika said:
only a small problem, it does not format anything and says that there is no sim inside, I sincerely hope that you manage to solve the problem ....
also the modem is not installed ...
Click to expand...
Click to collapse
Man, I tried via Philz 6.41.6, since it was recommended in OP. I usually use TWRP, had a nandroid backup of everything including Modem made with TWRP which I placed on external card.
Had the mounting problem after flashing script and rebooting recovery, but I manually solved them, as described in 1st post. Then reflashed TWRP and restored my nandroid from external card. Then also restored my internal sd files (music, games obb, etc) which I saved on pc.
I have no error, I have ND3 modem present, all fine, phone works as before. And 12.1gb total space instead of 10.4 which I had before.
Thanks again!:good:
ulkika said:
only a small problem, it does not format anything and says that there is no sim inside, I sincerely hope that you manage to solve the problem ....
also the modem is not installed ...
Click to expand...
Click to collapse
How come your modem firmware is gone?
Have you try installing ROMs again, most rom installer will flash modem firmware.
My script doesn't touch modem partition at all.
Just partition cache and after that, see the partition table.
Rickav said:
I saw your post on the DN3 V5+ thread which led me... Seems to be a great concept, especially considering that one of the first things I do upon flashing a stock-based rom is to delete most Sammy things on it.
I understand that you need Philz to flash this; will the latest V6.41.4 do?
Also, do you know of anyway to save all system settings so as to restore them later? I can backup apps and their data but not the stock system settings themselves.
Click to expand...
Click to collapse
steff195 used Philz 6.41.6, and it worked.
Well, DN3 v5+ update-script has the commands to delete Android Setting Database on install.
Because you restore data first, then flash DN3v5+ which triggering deletion of Android Setting Database.
So you have to backup android setting database using titanium backup before repartition, then restore after repartition.
Or after repartitioning, install DN3 v5+ first, then restore data using nandroid.
I also have weird problem after deleting Android Setting Database on DN3 v5+. New setting generated is really courrupted. It breaks home button, notification toggles expanding, lock screen, and much more. Everybody else seem to be fine of android setting database regeneration. Weird.
MBariya said:
Can we increase system partition???
I need more space in system......
Click to expand...
Click to collapse
Yes you can.
Extract my .zip script, then open the updater-binary with your favorite text editor, I prefer Notepad++.
Find these line
parted /dev/block/mmcblk0 mkpart primary 168MB 270MB -> CACHE
parted /dev/block/mmcblk0 mkpart primary 270MB 2417MB -> SYSTEM
parted /dev/block/mmcblk0 mkpart primary 2417MB 2432MB -> HIDDEN
parted /dev/block/mmcblk0 mkpart primary 2432MB 2440MB -> OTA
parted /dev/block/mmcblk0 mkpart primary 2440MB 15.8GB -> USERDATA
It is pretty easy to understand indeed, first number after word "primary" is the start offset of the partition, second one is the end.
You may change those number. But remember that CACHE partition must always be bigger than 50 MBs to store google play apk download. Google stated that google play apk max size is 50 mb, bigger than that will use .obb to help.
I recommend you to keep OTA size 8 MB, cause I don't know what it does.
HIDDEN can be shrink up to 5 MB I doubt. I suspect that shrink up to 4 MB can cause issue, I don't know if you set size for 4 MB, will it exceed minimum partition size required.
However, numbers in red can't be changed, they must be 168MB and 15.8 GB the same.
And do not change order of partitions, and there must be 5 partitions. You can't remove HIDDEN and OTA, else partition order and number will wrong, and I think a lot of things will break, including recovery.
After you modified the script. Zip them and put in your phone and flash! :laugh:
philz_touch_6.41.6-n7100.zip.md5 but the problem is that not format data,i solve whith reinstall nd3 and after root and restore system but the patch is not functionally at my device.
---------- Post added at 11:50 AM ---------- Previous post was at 11:45 AM ----------
ninekaw9 said:
How come your modem firmware is gone?
Have you try installing ROMs again, most rom installer will flash modem firmware.
My script doesn't touch modem partition at all.
Just partition cache and after that, see the partition table.
Click to expand...
Click to collapse
I do not know what happens because of it, I can not see the pictures because you do not know how to send to you but that happens on the screen while doing the second restart to do manually format the system tells me that the memory is not formatted.
then I tried to reinstall the old rom and told me that he could not find the modem, it does not restart no line present it tell insert telephone card ... in the end I had to reinstall ND3, before I tried it with the pit from you and given after but not without changing anything in the system memory space....
ulkika said:
philz_touch_6.41.6-n7100.zip.md5 but the problem is that not format data,i solve whith reinstall nd3 and after root and restore system but the patch is not functionally at my device.
---------- Post added at 11:50 AM ---------- Previous post was at 11:45 AM ----------
I do not know what happens because of it, I can not see the pictures because you do not know how to send to you but that happens on the screen while doing the second restart to do manually format the system tells me that the memory is not formatted.
then I tried to reinstall the old rom and told me that he could not find the modem, it does not restart no line present it tell insert telephone card ... in the end I had to reinstall ND3, before I tried it with the pit from you and given after but not without changing anything in the system memory space....
Click to expand...
Click to collapse
I am very confused with your language. After you used my script, did you go to "Mounts and Storage", then format SYSTEM DATA CACHE PRELOAD?
only an other question,i use x-treme rom 2.1 is possible that is the problem...
ulkika said:
only an other question,i use x-treme rom 2.1 is possible that is the problem...
Click to expand...
Click to collapse
I'm downloading it and will diagnose the installation file.
ninekaw9 said:
I am very confused with your language. After you used my script, did you go to "Mounts and Storage", then format SYSTEM DATA CACHE PRELOAD?
Click to expand...
Click to collapse
after reboot of first install, is impossible for me format prelod .system and cache....
ulkika said:
after reboot of first install, is impossible for me format prelod .system and cache....
Click to expand...
Click to collapse
Try this Philz Touch version. It is the version that I used to repartition on my device.
I'm still downloading your ROM, mediafire is quite slow today.
TURBO DATA - Get an 8GB Data-Partition!
Use SD-EXT as new Data partition
presented by
~~~~~~~~ delta-roh ~~~~~~~~
HIT THANKS for delta-roh (1st post) And, please, don't forget to Rate this Thread - thank you!
You love your Sensation, but:
The 1 GB of the data partition limits you?
You don't like Link2SD?
You don't want to use the to SDCard feature?
You don't want to use data2sd or similar scripts?
You are afraid of broken links?
Then this is the Turbo for your HTC Sensation
Features of TURBO DATA
Version 3.01 (release date 01st Nov 2016)
new corrected error in cpio to support 2nd level subdirectories
new Mod for Ivanich CM11 to get Data on SD-Ext, but have Dalvik internally (FAST!!!) - refer to Post 2
Version 3.00 (release date 29th Mar 2015)
new now my Delta-Roh cpio.bat is integrated
new Delta-Roh cpio without cygwin! - all tools integrated als always
new No need of Windows 8.1 administrative rights (as for cygwin)!
new Now manual changes can be done to all scripts of the ramdisk
new Very easy handling!
new This version now also supports ViperS-Roms!
new If you like, you can download only the Delta-Roh cpio package (see below)
Version 2.02 (release date 02nd Mar 2015)
new now also handles .img (boot-Image files)
new added loop for performing patterns more flexible
new added patch check - exit if no pattern was found
new added ramdisk size check
Version 1.04 (release date 21st Feb 2015)
First Version by delta-roh
new handles normal flashable zip, that include a boot.img
new works fully automatically
new support of command line call
new Drag+Drop support
new A lot of checks to make the procedure safe
new Writes a logfile parallel to the screen output
new Does not change your original zip
new the resulting zip can be flashed directly
Click to expand...
Click to collapse
Idea:
Our beloved Sensation comes only with 1 GB of available internal memory and that is too less to work, even if you don't install a lot of games. When I tried several thinks (app2sd, app2sd-ext, Link2SD etc.) I recognized, that modern SD-Cards are very fast and our Sennsation has got a very good interface to suppport high speeds. Even better, the SD-Cards of SanDisk (SanDisk Extreme Pro, SanDisk Extreme Plus and SanDisk Extreme) are even faster, than the internal memory. Therefore I got the idea, to make a seperate external SD partition (SD-Ext) to the new Data partition. It works flawlessly and fast. But how does it work? The first step of the Android startup process is to mount the boot image and to mount a ramdisk, that is part of the boot image. In this ramdisk you will find the mount table for the primary partitions - it is called fstab.pyramid. Here you will find, that the data partition is mounted to /dev/block/platform/msm_sdcc.1/by-name/userdata or to /dev/block/mmcblk0p23. The only thing to do is, to change this to /dev/block/mmcblk1p2, which is the second partition of the SD-Card.
The attached ZIP now contains a Batch file together with all necessary tools to do this job for you completely automatically. It extracts the boot.img file from your flashable zip, extracts the kernel and the ramdisk.gz, unpacks the ramdisk, patches the fstab.pyramid as described above, repacks the ramdisk, repacks the boot.img, makes a copy of the original flashable zip, exchanges the boot.img in this new zip - done! You have got a new flashable zip, that will mount the second SD-Card partition as your new data partition. I do this with an 8 GB sd-ext partition and therefore now have got a Sensation with 8 GB of available internal memory - no need to care about memory or tools like Link2SD any longer!
Click to expand...
Click to collapse
Installation:
Take these steps:
the attached zip contains the batch and all needed utilities
extract the directory tree in the zip to a location on your Windows harddisk
place your flashable zip or boot-Image in the main directory which also contains this batch
open a cmd-windows by clicking "Start here.bat"
call "MakeNewImage" with your flashable zip or boot-Image: MakeNewImage <your-rom-or-image.zip>
or
just Drag+Drop your flashable zip or boot-Image to MakeNewImage.bat
after processing you will find the new flashable zip or boot-Image in the subdir "new"
all original parts (boot.img, kernel, ramdisk(.gz)) are in the subdir "original"
all new parts (boot.img, kernel, ramdisk(.gz) and your new flashable zip) will be in the subdir "new"
if you call the batch another time (or Drag&Drop a new image to MakeNewImage.bat, the complete subdirs will be deleted before processing the new fashable zip; the batch will then create the directories again with the new parts
if you like, you can make additional changes to the fstab.pyramid or init.rc ...
Click to expand...
Click to collapse
YOU MUST READ THIS OR YOU WILL BRICK YOUR DEVICE:
You have to know this - read carefully:
Tested with a lot of CM11 and CM12 Roms
It will only work for fashable zips that contain a boot.img, like @SultanXDA CM11, @ivanich CM12, @shantur CM12 - it will NOT work e.g. for @mike1986 Android Revolution, as this does not contain a boot.img.
ViperS 5.2.1 / Viper 5.3.0 do not work at the moment.
You should only make your sd-ext to the new /data partition if you have got a highspeed sd-card e.g. SanDisk Extreme-series; otherwise it will work, but your Sensation will slow down.
You need a sd-ext partition on your sd-card as second (!) partition (/dev/block/mmcblk1p2); create it within the recovery or use e.g. MiniTool Partition Wizzard and create a first partition as primary fat-formated and a second partition as primary ext4 formated. IF YOU HAVE NOT A SECOND PARTITION, YOUR DEVICE WILL NOT BOOT!
This is ONLY for the HTC Sensation/XE; it can work also for flashable images of other devices, but then you have to make your changes to fstab and/or init.rc manually!
After flashing the new image the /data partition will be created on the second SD-Card partition (sd-ext).
After booting for the first time you can restore a backup by using e.g. Titanium.
If you want to look at /data within the recovery you have to mount sd-ext and then flash the Aroma Filemanager; there you can see the complete data partition by browsing to sd-ext.
You can make a nandroid backup within the recovery. Note, that the sd-ext tar file is your (new) data partition.
If you want to go back, then just flash a nandroid of a former backup or flash a not patched zip and make a clean installation.
If your rom thread provides a seperate zip for the kernel, then have a look at the provided zip! If it contains a boot.img, then it has to be patched at first by using MakeNewImage.bat in the same way as with a complete rom. If the kernel zip does not contain a boot.img but only the kernel, then you can flash it directly.
If you want to wipe Dalvik-Cache you can't do it with the "wipe Dalvik"-command in Recovery; instead go into Recovery, mount sd-ext, flash the Aroma Filemanager or use the TWRP-Filemanager, navigate to the directory sd-ext (your new /data) and delete the directory dalvik-cache.
You can not restore a data partition from a former installation to sd-ext, because the tar file also stores the partition name and, therefore, does not restore a data file to the sd-ext partition, even it you rename the backup file. As said before: Make a clean installation and then restore via e.g. Titanium.
Click to expand...
Click to collapse
Thanks:
Special thanks to:
carliv (http://forum.xda-developers.com/member.php?u=5186178)
for mkbootimg.exe (https://github.com/bgcngm/mtk-tools)
GnuWin32 (http://gnuwin32.sourceforge.net/packages.html)
for sed.exe and grep.exe (libiconv2.dll, libintl3.dll, pcre3.dll, regex2.dll)
Igor Pavlov (http://www.7-zip.de/)
for 7z.exe and 7z.dll
Karl M. Syring (http://unxutils.sourceforge.net/)
for dd.exe, gzip.exe, od.exe, printf.exe, rm.exe, sha1sum.exe, tee.exe
@danishaznita for testing the first version
Click to expand...
Click to collapse
USE IT AT YOUR OWN RISK - NO SUPPORT! READ SECTION 'MUST READ' ABOVE CAREFULLY!
DOWNLOAD TURBO DATA MOD V3.01
DOWNLOAD Delta-Roh cpio Package V1.51 (already integrated in Turbo Data Mod)
If you like my work, press
THANKS for delta-roh
And, please, don't forget to rate this thread - thank you!
If you want to use my work, please don't ask for permission, but leave my headers in my files, make a reference to me in your thread and respect the other persons in the thanks section, if you use their tools.
copyright by delta-roh 2016
Reserved
Mod for Delta-Roh MakeNewImage-V3.01
EXPLICITLY for Ivanich CM11 ONLY!!!
This mod mounts a sd-ext partition to /data and leaves the dalvik-cache on the internal
memory. Therefore you will get e.g. an 4 GByte (depends ob your sd-ext partition size) data
partition and the original 1.1 GByte internal memory as additional and fast memory for
the dalvik cache. This is the fastest way regarding the porformance of the Sensation.
Installation:
- Download and extract "Delta-Roh MakeNewImage"
- start "MakeNewImage.bat" with "cm-11-20160810-UNOFFICIAL-pyramid.zip"
- answer the question "Do you want to auto-patch fstab [y/n]" with "n" (no) - don't close the command box!
- an explorer will open in the subdir of the new ramdisk, now do the following mods:
--- override the existing "init.rc" with the new one from this zip (Download below)
--- override the existing "fstab.pyramid" with the new one from this zip (Download below)
--- create a new directory "data0" in addition to the already existing data directory
--- copy/paste (press Ctrl-C then Ctrl-V) the file "data.attrib"
--- rename the new file ("data - Copy.attrib" or named similar) to "data0.attrib"
--- now you can close the Explorer and answer the question "Manual changes finished [y/n]" with "y" (yes)
Now you will get a "sdext_cm-11-20160810-UNOFFICIAL-pyramid.zip" that can be flashed.
NOTE: You will need a sd-ext partition on your sd-card.
DOWNLOAD Ivanich CM11 DATA MOD
I think this a great idea, many thanks. I've been wanted to do it the since you mentioned the other day, I wanted a new phone too xD Well I did it today and then just seen your post. I did it on PC though (Linux) and mounted userdata as dalvik-cache so easy to wipe and maybe quicker loading (in theory). I may have mounted it differently to you (see screenshot), and are your attributes/flags the same?
hinxnz said:
I think this a great idea, many thanks. I've been wanted to do it the since you mentioned the other day, I wanted a new phone too xD Well I did it today and then just seen your post. I did it on PC though (Linux) and mounted userdata as dalvik-cache so easy to wipe and maybe quicker loading (in theory). I may have mounted it differently to you (see screenshot), and are your attributes/flags the same?
Click to expand...
Click to collapse
My Turbo Data mounts sd-ext to data (same to you) but don't mounts the old data to the dalvik-cache, because I have a SanDisk Extreme Plus and it is faster than the internal memory xD
BTW, my batch works completely with Windows and even without cygwin. At the moment I am working at a cpio batch that works with Windows without elevated rights and without cygwin as well...... xD
Question: what did you do to mount dalvik-cache to the original data partition? And which Filesystem manager did you use in the screen shots?
delta-roh said:
My Turbo Data mounts sd-ext to data (same to you) but don't mounts the old data to the dalvik-cache, because I have a SanDisk Extreme Plus and it is faster than the internal memory xD
BTW, my batch works completely with Windows and even without cygwin. At the moment I am working at a cpio batch that works with Windows without elevated rights and without cygwin as well...... xD
Question: what did you do to mount dalvik-cache to the original data partition? And which Filesystem manager did you use in the screen shots?
Click to expand...
Click to collapse
Yeah I must have the same SDcard as you by the sounds of it xD have so for ages and probably the reason I've been using Mounts2SD for so long but yeah got sick of it not working as expected as CM12/Android 5.x matures. Thanks to your idea/earlier post though and a bit of mucking around with it as I did have a few hiccups, eg. offset ramdisk address, all went well in the end and is quite a simple process once the know how. Over the time of using M2SD I felt like write speeds were slower (not actually tested but just how it felt) hence the reason why I use the f2fs file system on the sd-ext and I didn't want to leave my internal data partition all alone and unused. I was deciding and still am really for what to use it for, first ideas was for private storage or for app data but then I thought Dalvik-cache could be good because wiping it would be easier without modifying recovery or applying a script. I did this all on native linux (ubuntu) with a few binaries added, I was thinking of making a flashable zip to do the whole process if possible and I think it is but would be a bit of experimenting process and don't really have the time as yet and also you have got this underway already, so I probably wont. I don't mind posting the binaries I used and what I did if it will help, maybe you'd be into creating a version that doesn’t require a PC. The file manager I'm using is FX File Explorer (pro), I only just switched to it, well bout a month ago and I find it a good alternative to ES or Root explorer, it also has the material design theme which goes nicely with CM12 and has 90% of all the necessary features I need. I mounted internal data with fstab which I've attached for you and I've linked the /data/dalvik-cache/arm directory to it. You can name the internal data partition to whatever you like too.
This also could be good for those that corrupted their data partition too that was caused by the twrp recovery version from their site (not ivanich's version).
This is also good because I don't have to link things like Googles Drive cache to sd-ext anymore, for example it caches a copy into data say from a ROM downloaded with it.
Edit: Just checked my SDcard and it older than yours and probably not as quick but mines a 32Gb SanDisk Ultra SDHC-I and works fast enough for now.
hinxnz said:
Yeah I must have the same SDcard as you by the sounds of it xD have so for ages and probably the reason I've been using Mounts2SD for so long but yeah got sick of it not working as expected as CM12/Android 5.x matures. Thanks to your idea/earlier post though and a bit of mucking around with it as I did have a few hiccups, eg. offset ramdisk address, all went well in the end and is quite a simple process once the know how. Over the time of using M2SD I felt like write speeds were slower (not actually tested but just how it felt) hence the reason why I use the f2fs file system on the sd-ext and I didn't want to leave my internal data partition all alone and unused. I was deciding and still am really for what to use it for, first ideas was for private storage or for app data but then I thought Dalvik-cache could be good because wiping it would be easier without modifying recovery or applying a script. I did this all on native linux (ubuntu) with a few binaries added, I was thinking of making a flashable zip to do the whole process if possible and I think it is but would be a bit of experimenting process and don't really have the time as yet and also you have got this underway already, so I probably wont. I don't mind posting the binaries I used and what I did if it will help, maybe you'd be into creating a version that doesn’t require a PC. The file manager I'm using is FX File Explorer (pro), I only just switched to it, well bout a month ago and I find it a good alternative to ES or Root explorer, it also has the material design theme which goes nicely with CM12 and has 90% of all the necessary features I need. I mounted internal data with fstab which I've attached for you and I've linked the /data/dalvik-cache/arm directory to it. You can name the internal data partition to whatever you like too.
This also could be good for those that corrupted their data partition too that was caused by the twrp recovery version from their site (not ivanich's version).
This is also good because I don't have to link things like Googles Drive cache to sd-ext anymore, for example it caches a copy into data say from a ROM downloaded with it.
Click to expand...
Click to collapse
You mounted userdata to /dalvik-cache and I suppose you then changed the init.rc to link the dalvik-cache to /dalvik-cache - right?
delta-roh said:
You mounted userdata to /dalvik-cache and I suppose you then changed the init.rc to link the dalvik-cache to /dalvik-cache - right?
Click to expand...
Click to collapse
Yes that is correct.
Code:
# symlink dalvik-cache to internal location
symlink /dalvik-cache/arm /data/dalvik-cache/arm
hinxnz said:
Yes that is correct.
Code:
# symlink dalvik-cache to internal location
symlink /data/dalvik-cache/arm /dalvik-cache/arm
Click to expand...
Click to collapse
Why not this way?
Code:
symlink /data/dalvik-cache /dalvik-cache
delta-roh said:
Why not this way?
Code:
symlink /data/dalvik-cache /dalvik-cache
Click to expand...
Click to collapse
I did it this way because in the past, I've had issues with linking dalvik-cache to other locations due to SELinux but only on later versions of Android 5.x though.
But then again I haven't tried this approach with this configuration yet.
thanks delta roh..
so, at least how much R/W speed that need run this?
based on Sandisk Extreme spec, min speed is around 60MB/s for read. is it correct?
phan_tom said:
thanks delta roh..
so, at least how much R/W speed that need run this?
based on Sandisk Extreme spec, min speed is around 60MB/s for read. is it correct?
Click to expand...
Click to collapse
Sandisk Extreme is the highest u can go , i think any Class 10 sdcard can handle this , but with a little lower speed
Sent from my Note 2
phan_tom said:
thanks delta roh..
so, at least how much R/W speed that need run this?
based on Sandisk Extreme spec, min speed is around 60MB/s for read. is it correct?
Click to expand...
Click to collapse
The internal memory (original /data) has got about 30 MB/s read and about 15 MB/s write speed. The card has to match these values. But the speed declarations of the cards are allways higher, than they are in real life! A SanDisk Extreme matches these speeds in real live. The Extreme Plus and Pro are better and will give you REAL FUN!
Just try it - to have a Senni with e.g. 8GB internal memory is awesome!
danishaznita said:
Sandisk Extreme is the highest u can go , i think any Class 10 sdcard can handle this , but with a little lower speed
Sent from my Note 2
Click to expand...
Click to collapse
Right! Having 8GB of internal memory and no mem-problems any more is also worth a little bit less speed (in the case you got no SanDisk Extreme). BTW: Thank you for testing the pre-releases and did you try the release 1.04?
Unfortunately,
Your method does NOT suits me fine - extremely laggy and slow.
I have tried it with the latest ivanich CM11 and CM12 builds.
I have preliminary made an 8Gb ext4 partition on my 32GB class 10 MicroSD card.
I always set governor to intellidemand, clock to 1242MHz and use cfq for I/O.
Will test Links2SD method now.
Nevertheless,
keep up the good work!
ChimeyJimmey said:
Unfortunately,
Your method does NOT suits me fine - extremely laggy and slow.
I have tried it with the latest ivanich CM11 and CM12 builds.
I have preliminary made an 8Gb ext4 partition on my 32GB class 10 MicroSD card.
I always set governor to intellidemand, clock to 1242MHz and use cfq for I/O.
Will test Links2SD method now.
Nevertheless,
keep up the good work!
Click to expand...
Click to collapse
I tried the CM12 build of ivanich and it has got an extrem low performance of the runtime environment (in Antutu 77 compared to Sultans CM11 with 900) and I tested it with dalvik-cache in the data partition and not on sdext. It seems as if the runtime system was compiled with debug options.
delta-roh said:
I tried the CM12 build of ivanich and it has got an extrem low performance of the runtime environment (in Antutu 77 compared to Sultans CM11 with 900) and I tested it with dalvik-cache in the data partition and not on sdext. It seems as if the runtime system was compiled with debug options.
Click to expand...
Click to collapse
Huh I just downloaded Antutu from playstore to test myself, still on the same configuration and my score is way higher than you got on CM12 and even higher than your CM11 score, only ran the benchmark once so it not like the highest out of several either on stock frequency, governor, scheduler etc.
Will it work on viper sense5.0 and what if my mcard crashes because sometimes it stops working and I have to format my mcard. So what if it crashes will it affect my senny
cutejerk420 said:
Will it work on viper sense5.0 and what if my mcard crashes because sometimes it stops working and I have to format my mcard. So what if it crashes will it affect my senny
Click to expand...
Click to collapse
Nobody is able to answer these questions. Normally SD-Cards are absolutely stable. Make a regular nandroid backup e.g. every day.
hinxnz said:
Huh I just downloaded Antutu from playstore to test myself, still on the same configuration and my score is way higher than you got on CM12 and even higher than your CM11 score, only ran the benchmark once so it not like the highest out of several either on stock frequency, governor, scheduler etc.
Click to expand...
Click to collapse
Remarkable! Please post your configuration - do you use F2FS and on which partitions?
delta-roh said:
Remarkable! Please post your configuration - do you use F2FS and on which partitions?
Click to expand...
Click to collapse
I use f2fs on sd-ext and ext4 on userdata, I use the fstab which I posted earlier and added the symlink to init.rc, on line 319 to be exact xD
Unpacking, repacking and making boot image was done on Linux, not sure if that would make a difference though.
Good day!
So i was wondering, is there a way to repartition the oneplus one system partition so that it takes some space from the /sdcard partition (like 1gb extra) so it would allow for bigger gapps files and maybe even android 12/13?
Maybe if someone would make a repartition script (like some exynos 7870 devices) that would open so much possibilities.
Have a good day and thanks!
vinnievh said:
Good day!
So i was wondering, is there a way to repartition the oneplus one system partition so that it takes some space from the /sdcard partition (like 1gb extra) so it would allow for bigger gapps files and maybe even android 12/13?
Maybe if someone would make a repartition script (like some exynos 7870 devices) that would open so much possibilities.
Have a good day and thanks!
Click to expand...
Click to collapse
[GUIDE][WORK IN PROGRESS]Oneplus one - resize system partition and maybe even more
WARNING!!! Everyone is responsible for the proper functioning of their device. This guide is the result of personal experiments and I'm not responsible for any damage caused to your device as a result of improper use of its contents...
forum.xda-developers.com
Hi all...
Just wandering if anyone new how to resize the system partition of a galaxy a53?
Need to make it larger to fit files onto it but not able to delete bloatware or anything for some reason using all the recommended processes. And to be honest having larger system partition would probably just be useful anyway.
My phone is rooted. I'm not fussed about having to refresh ect. And I have TWRP flashed and Stock Rom.
Please help lol
TWRP should automatically resize your system partition.
When you're installing the ROM, make sure you format /data then /system before installing.
It does, but i want to make the partition larger so i can add files to the system partition once the rom is flashed and phone is set up to be used.
At the moment it say 6GB partition and only the rom fits onto the partition and there isnt any room to add extra files. so im looking to make the partition say 10GB to give myself some wiggle room to play with.
i Have 128GB in total so can spare some extra GB's lol