Database Info

Firerats + Data2ext Complete Installation Guide: Now works with Sense roms!

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.

Booting from external SD [CM]

UPDATE: This can't be used with CM10 Alpha 4 (or later) as it is due to the new partitioning system.
____
I made this thing time ago and I thought to share.
What it does is to boot a stock ROM from the external SD card. It's nothing special, I simply changed few things here and there. I did it because I needed a stock ROM for a couple of minutes and this was the faster way to get it.
I'm using CM and I made this with that in mind, so, don't use while using a stock ROM. It won't mess your current setup, but it won't work.
You need to change kernel to boot the stock ROM (reboot recovery > flash zip. Simple and fast). That's because, as you probably now, kernels made for stock ROMs are not compatible with CM.
Prepare you SD card
You need first to repartition your external SD like this:
Code:
1° partition (mmcblk1p1): FAT - it will be the usual external SD
2° partition (mmcblk1p2): ext4 - /system (make it around 300MB big, 254MB will be more or less the space used)
3° partition (mmcblk1p3): ext4 - /data
I can't help you with this, I did it with adb and parted (the command is available in CWM). Look for instructions on the web, it's full of guides out there. Your external SD card is /dev/block/mmcblk1 (mmcblk0 is the internal one).
If you'll use the zip linked to flash the ROM, the two partitions (mmcblk1p2 and mmcblk1p3) will be automatically converted, unless they are already two ext4/ext3/ext2 partitions.
It shouldn't matter which kernel you are currently using and it should be safe flashing it, the only important thing is to have three partitions. If mmcblk1p2 or mmcblk1p3 are not detected, the installation will be aborted (it means that your SD card is not partitioned). Nothing else will be touched.
If you don't want to use the zip, mount mmbclk1p2 and copy the ROM there.
/dbdata will be the usual one (it's not used in CM. This will also makes Samsung apps a lot faster when using a slow SD card), same for /cache.
The flashable ROM is a stock XXLE4 + su/Superuser.apk.
How to use the additional ROM
To use the ROM on your SD, flash kernel-stock-SD.zip (see below) from recovery.
To go back to the real ROM you have to flash its kernel. Here below you can find CM10 Alpha 2 kernel, flashable from recovery. If you have doubts, reflash the entire ROM, it won't wipe your data.
I only mentioned CM10 because it's what I'm using, but this thing should work with CM9 too.
Things to know
I built the kernel using the latest Samsung sources with inbuilt ext4 support (and ext3/ext2 compatibility). Nothing else was changes, so I think there's no need to publish the sources, they are available here.
I attached the tools I use to unpack/repack boot images (they are a modified version of skin1980's tools):
Code:
./unpack.pl boot.img
./repack.sh [gz|lzma|bzip2|xz]
To see the changes I made, compare "out/android" with the stock XXLE4 ramdisk and the other two directories with CM10 boot.img ramdisk.
I changed recovery.fstab accordingly, but I can't tell you if flashing stuff from CWM while using the additional ROM will work as expected. You should read the updater-script to know it for sure.
I can only tell you that dhiru's builds will be flashed into the real /system partition and not your SD card.
Backups should work too, but I didn't try.
Of course, performances depends on your SD card. Mine is not that good I think, I took it from an old phone and I really don't know anything about it. The ROM is still usable, but apps that intensely use databases are slow (not Samsung apps, those will use /dbdata). Maybe disabling journaling will help (search for more info).
The Galaxy SL screen will last more than usual because I intentionally added a delay (3 seconds, SD cards are detected after a while) and of course because of the slower load.
Please, use this if you have some experience.
Note: dual booting two ROMs with a single kernel is possible, but only if they use the same kernel image. See this and this.
Downloads
XXLE4-CWM.zip: CWM flashable ROM
kernel-stock-SD.zip: kernel to boot the ROM from the external SD, flashable from recovery
kernel-CM10-Alpha2.zip: CM10 Alpha 2 kernel, flashable from recovery

Wow ! thats dualboot for i9003 ! sweet gud to see development back in action

Good work.
The class of an SD card can be misleading. It is only a measure of the sequential Write access and that doesn't tell the whole story. Class 10 cards are great for cameras and applications that write or read sequential data, such as saving a picture and transferring a file. They are not so good for random access which is what the Android OS does when operating. In fact the random access speed for class 10 cards is lower than class 4 or 6 cards. From what I have seen, the sweet spot for smartphones is class 6.

Awesome. Only if we could achieve dual boot without flashing kernel everytime. But anyways awesome guide. Thanks.
Reminded me of dual booting of maemo and android on my brother's n900.

Whats the benefits of dual boot? I heard about it but i dont have an idea

juztinlee said:
Whats the benefits of dual boot? I heard about it but i dont have an idea
Click to expand...
Click to collapse
Dual Booting means you can have two OS's (here firmware) on the phone at the same time. You can choose on which you want to go. This, besides being awesomely cool, is really helpful in many scenarios.

But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin

^But this can be useful when you have to go for a long trip and want to record videos which only our stock rom is capable of doing good. Thanks to the developer.
Also, if anyone can, please tell me what is the possibility we can create a dualboot kernel like siyah kernel?

vishal24387 said:
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
Click to expand...
Click to collapse
I didn't say dual boot
Creating a single kernel for ICS/JB and GB is not possible, or at least not an easy thing.
CyanogenMod is using newer graphic drivers not compatible with GB. I tried to use my CM10 kernel with GB, just to see what could happen. Well, it works, but with no hardware rendering as expected. It doesn't mean "it's laggy", it's painfully slow. And if we'll have the 3.0 kernel working, I guess this will be even more difficult.
The only option I think is kexecing an additional kernel, but kexec is hard to implement.
However I dual booted CM10 and CM9 (SD) with a single kernel (there are traces of this in my unpack/repack tools), I simply added an additional "cpio.gz" inside the boot.img. There's an additional boot reason that we never use, so we can use it to choose the corrent "cpio.gz" by parsing /proc/cmdline. The only problem is that you need to boot the ROM first and the reboot, because to get the other boot reason you have to run this:
Code:
reboot arm11_fota #or arm9_fota
(if you are using a stock ROM and try to reboot with the command above, you'll see weird stuff, but nothing should happen to your phone. I did it once.).
Maybe there's something else possible, but dual booting never interested me. As I said, I did it because I needed it.
You can do a lot of things, I even stored a ROM in a subdirectory in /data and use it from there (=> fast).
santoshsadani009 said:
^But this can be useful when you have to go for a long trip and want to record videos which only our stock rom is capable of doing good. Thanks to the developer.
Also, if anyone can, please tell me what is the possibility we can create a dualboot kernel like siyah kernel?
Click to expand...
Click to collapse
I don't know how exactly dual booting with this kernel works. I actually don't know how usually dual booting is implemented in Android.
I just looked at it. It allows you dualbooting only two ICS+ ROMs (so no GB), it automatically creates an hidden partition, automatically stores the ROM there, provides additional tools in CWM and other nice things.
I guess is something possible, but don't expect it from me. As I said, I'm not interested in dual booting and this thing requires time and knowledge.

loSconosciuto said:
I didn't say dual boot
Creating a single kernel for ICS/JB and GB is not possible, or at least not an easy thing.
CyanogenMod is using newer graphic drivers not compatible with GB. I tried to use my CM10 kernel with GB, just to see what could happen. Well, it works, but with no hardware rendering as expected. It doesn't mean "it's laggy", it's painfully slow. And if we'll have the 3.0 kernel working, I guess this will be even more difficult.
The only option I think is kexecing an additional kernel, but kexec is hard to implement.
However I dual booted CM10 and CM9 (SD) with a single kernel (there are traces of this in my unpack/repack tools), I simply added an additional "cpio.gz" inside the boot.img. There's an additional boot reason that we never use, so we can use it to choose the corrent "cpio.gz" by parsing /proc/cmdline. The only problem is that you need to boot the ROM first and the reboot, because to get the other boot reason you have to run this:
Code:
reboot arm11_fota #or arm9_fota
(if you are using a stock ROM and try to reboot with the command above, you'll see weird stuff, but nothing should happen to your phone. I did it once.).
Maybe there's something else possible, but dual booting never interested me. As I said, I did it because I needed it.
You can do a lot of things, I even stored a ROM in a subdirectory in /data and use it from there (=> fast).
I don't know how exactly dual booting with this kernel works. I actually don't know how usually dual booting is implemented in Android.
I just looked at it. It allows you dualbooting only two ICS+ ROMs (so no GB), it automatically creates an hidden partition, automatically stores the ROM there, provides additional tools in CWM and other nice things.
I guess is something possible, but don't expect it from me. As I said, I'm not interested in dual booting and this thing requires time and knowledge.
Click to expand...
Click to collapse
so that means we can dualboot cm9/10 with miui v4 . right ? since they both use the same kernel

vishal24387 said:
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
Click to expand...
Click to collapse
Ya a Universal kernel will do the trick.If later then we can achieve dual boot then the people who were holding back from CM9 or CM10 can flash that for features and a stock rom for stability and camera.

shriomman said:
so that means we can dualboot cm9/10 with miui v4 . right ? since they both use the same kernel
Click to expand...
Click to collapse
As long as the kernel is the same, yes.
If you want, here you can find the unpacked boot.img I (probably) used to dual boot CM10 and CM9 (SD).
There's no zImage in there, use the one you prefer, CM10 and CM9 are using the same kernel.
EDIT:
I almost forgot. "out/ramdisk/2ndROM" is for the ROM stored in your SD card, so you have to adjust the mount points there (already done in the one linked). "out/ramdisk/android" should be the "stock" ramdisk.
recovery will work only for the primary ROM in this case, maybe with some scripting you can make it works for both the ROMs, but I won't do it (if it's something possible).
The tools I posted will automatically take care of the additional ramdisk.

Possible to fix the download links? I want to boot rom from SD card since my internal is corrupted...

nick0016 said:
Possible to fix the download links? I want to boot rom from SD card since my internal is corrupted...
Click to expand...
Click to collapse
I don't know what happened to the links, probably I deleted the files by mistake on dev-host. Sadly I no longer have them and I currently don't have the time to make them again.
Anyway, I suggest you to follow other guides in order to replace only the corrupted memory instead (we have two different memories). This one for example, but there are other guides probably.

Thanks for your answer, problem is that my "device" memory is corrupted (as in read only).
I did the SD / USB storage swap but still have the problem that I cannot run/remove/install. So I need a ROM that loads completely from the external SD card and also uses it for data/storage...
I can flash a rom/kernel without problems, but changing version makes it only worse because the data does not get erased (background/applications/settings.... stays the same everytime, even after a wipe from the recovery).
If it helps I would love to pay/donate money to you as a thanks for your help and effort because the phone itself is working fine (except the corrupted memory of course) and would like to use it again

nick0016 said:
Thanks for your answer, problem is that my "device" memory is corrupted (as in read only).
I did the SD / USB storage swap but still have the problem that I cannot run/remove/install. So I need a ROM that loads completely from the external SD card and also uses it for data/storage...
I can flash a rom/kernel without problems, but changing version makes it only worse because the data does not get erased (background/applications/settings.... stays the same everytime, even after a wipe from the recovery).
If it helps I would love to pay/donate money to you as a thanks for your help and effort because the phone itself is working fine (except the corrupted memory of course) and would like to use it again
Click to expand...
Click to collapse
The guide I linked is fine then.
It explains how to repartition your SD card and the script Dipu K attached to his post is to use the newly created partition inside your external SD for /data. It's not to swap internal and external SD.
As I said, we have two memories, /data is in one, /system, kernel and other things are in the other memory. The corrupted one must be the one which holds /data.
Try to do as explained in the guide, if the problem persists, I'll see what I can do to help.

I followed the guide and got the Device memory replaced (data partition). Problem is now it is stuck in at boot because the partition is empty.... and when I copy the files from the corrupted data partition it boots fine but get message that I must wipe my data or the system will be unstable (which is correct because I get then flooded with unexpected errors which make it unusable). But formatting data partition gives stuck @ samsung boot logo??
So I need to get the "factory" data files from somewhere... I am running stock KPE ROM with BAM kernel (for init.d support).
Is it possible to extract the data partition from the stock rom?!

nick0016 said:
I followed the guide and got the Device memory replaced (data partition). Problem is now it is stuck in at boot because the partition is empty.... and when I copy the files from the corrupted data partition it boots fine but get message that I must wipe my data or the system will be unstable (which is correct because I get then flooded with unexpected errors which make it unusable). But formatting data partition gives stuck @ samsung boot logo??
So I need to get the "factory" data files from somewhere... I am running stock KPE ROM with BAM kernel (for init.d support).
Is it possible to extract the data partition from the stock rom?!
Click to expand...
Click to collapse
The content of /data is generated, there's nothing like what you asking for.
Maybe the problem is that the script posted in the guide copies the content of the old /data partition to the new partition inside the SD card. Wiping data shouldn't work because the path to the SD card is not specified.
Try the script attached. I zipped it to be able to upload it here, but it's not flashable. Since you've been able to follow the guide I assume you know how to use adb.
Wipe the content of the data partition you created inside you SD card (/dev/block/mmcblk1p2). You could reformat it with make_ext4fs, use a computer and so on. What's important is that it's ext4 formatted.
While in recovery, run:
Code:
adb shell mount /system
adb shell mkdir -p /system/etc/init.d/
adb push [I]PATH_TO[/I]/remount_data /system/etc/init.d/
adb shell chmod 777 /system/etc/init.d/remount_data
I'm sorry, but I currently don't have much free time to help more than this. With no logs or access to the device it's really hard for me to know what's the problem.

[MOD] Data2SD (Enhanced) - I/O Fix

At the suggestion of several users, I am forking the previous thread. I am planning on supporting several ROMs and this is the best course to keep everything organized and provide support.
What is this?
Background:
The speed of the flash memory in the Transformer line of tablets is very poor. This is very apparent when installing or updating applications from the Play Store, copying files over USB, or using an app that caches lots of data like a web browser. The tablet will hiccup and stutter due to the I/O bottleneck. Running Androbench shows random write speeds averaging less than .2MB/sec.
The workaround:
Utilizing a fast, class 10 microSD card, we can move the /data partition to something significantly faster. The /data partition is where apps are installed to and where they store their configuration information and data. By redirecting /data to these fast microSD cards, we eliminate this bottleneck from our devices. With a properly fast card, users have reported a complete elimination of I/O related hiccups and system freezes. I have based my enhancements on the initial work by TweakerL on the Transformer Prime. Credit to fordwolden to porting his work to the Infinity.
The enhancements:
Previous implementations of this mod had the internal data partition mounted to /data2, with the media subfolder (your internal user storage) only available via root apps. There were symlinks set up at /sdcardi, etc, but these still required root permission to access. This is due to permissions on the /data partition and applies to both /data and /data2. Google gets around this by creating a "virtual" sdcard that points to /data/media. I have created a second "virtual" sdcard that points to /data2/media. This mod creates the scenario below:
/data = ext4 partition on microSD (fast)
/data2 = ext4 partition on internal storage (slow)
New changes:
/data/media -> Virtual SD Card Daemon -> /storage/sdcard0
/data2/media -> Virtual SD Card Daemon -> /storage/sdcardi
/sdcardi -> Symlink -> /storage/sdcardi
/mnt/sdcardi -> Symlink -> /storage/sdcardi
/storage/sdcardi is the virtual SD card for the internal storage. You should see all the files you had saved to this space before using data2sd. These files should be accessibly by any standard non-root Android app.
Note to kernel developers: This mod is more than just changes to the kernel. In order for the internal storage to be properly mounted at /storage/sdcardi, I have modded the Virtual SD Card Daemon that comes with Android. The stock binary is /system/bin/sdcard. I made a copy, modified it using a hex editor, called it /system/bin/sdcardi, and included it in my flashable zips. If you wish to make a data2sd version of your kernel, you must include this file in your zip. Additionally, be sure to add the "service sdcardi" line to your init.cardhu.rc that I have in mine.
Installation
Requirements
1) Class 10 microSD, at least 8gb
2) A computer with card reader
3) Partitioning software. Recommended: gparted LiveCD
Instructions
1) Decide how big you want to make the ext4 partition for /data. Remember, this is going to be the space for installing applications AND the /sdcard space that games will use the cache their extra data. Kindle books, Dropbox files, pics from the camera WILL ALL GO HERE. Personally, I decided to make the ext4 partition the whole 64gb of my card.
The ext4 partition has to be partition #2 on the microSD card. Why? This is to give people with large cards the option of creating a FAT32 or NTFS area as partition #1. This allows the card to be read by a Windows or Mac computer using a card reader. I use my tablet as my card reader with the USB cable, so I wasn't worried about this. I used gparted to create a small 8mb unformatted partition as partition #1, then a second 64gb partition to fill the rest of the card. I formatted this second partition in ext4.
2) Format your microSD card - Download Gparted Live CD (http://goo.gl/dJQAu) and use Imgburn (http://goo.gl/33MY9) to write to disc. Boot to Gparted using your CD after setting the CD as the primary boot device in your BIOS. Once in Gparted, create the 2 partitions described above, the first partition is Fat32, the second partition is ext4 or ext2. Set both partitions to type: Primary.
3) Insert microSD into tablet and flash any data2sd kernel for your ROM. (Note: Flashing any ROM will overwrite your data2sd kernel. You will have to re-flash the data2sd kernel if you change ROM or even upgrade your current one) After booting back into Android, you should be greeted with the Setup Wizard. Remember, this is a fresh /data partition, so it's a clean slate. It's a good idea to take a TitaniumBackup** ahead of time. I am experimenting with ways to make the transition more painless.
**Note about taking a TitaniumBackup before switching to data2sd. After the conversion, your internal storage will be mounted to /sdcardi. By default, TitaniumBackup looks for previous backups in /sdcard not in /sdcardi. You have two choices. Copy the TitaniumBackup folder from /sdcardi to /sdcard and restart the app, or change the backup location to /sdcardi/TitaniumBackup in the app preferences. Either of these options should work fine.
Optional: Verify data2sd is working. Pick any method you like:
a) Open a file explorer such as Root Explorer, ES, etc. You should see /sdcard and /sdcardi and be able to browse the files within. /sdcard is your ext4 partion on the microSD while /sdcardi is the internal storage. You should able to copy data between them.
b) Download "Androbench" app from the market and run "micro" sdcard check, if you see 0.4mb/sec or more in random write you're on data2sd.
c) Power off your device, remove your microSD card, then power back on your device. You should received an error message "Encryption unsuccessful". Insert microSD and reboot to fix.
Uninstallation
Don't like data2sd? Just flash a non-data2sd kernel using recovery and when you boot back into Android your /data will be on the internal storage. This could also be accomplished by flashing your ROM on top of itself without wiping.
Troubleshooting
1) Grab the mount-data2sd.zip from the second post.
2) Boot into TWRP and flash the mount-data2sd.zip. This will mount the microSD as /data in recovery. It will allow us to wipe it, format, etc using recovery.
3) Wipe "Internal Storage". This will erase the entire ext4 partition on your microSD.
4) Flash ROM
5) Flash data2sd kernel for ROM
*CAUTION*: If you don't flash mount-data2sd.zip before your wipe, you will be wiping your internal memory.
Download data2SD kernels
These are flashable zips. It will disable journaling on the microSD ext4 partition. You do not have to do this manually! Flash these after flashing the ROM.
CyanogenMOD 10.1 - beta2: http://d-h.st/rOe (Based on 4-2 nightly and may behave unexpectedly on other builds)
CleanROM 3.2.2: http://d-h.st/sCa - WORKS WITH CleanROM 3.3!
clemsynTFUniversalCyano650GPUFsyncver3: http://d-h.st/duw
ClemsynTFUniversalStock: http://d-h.st/IBm
clemsynTFUniversal650GPUver7 (Stock/CleanROM): http://d-h.st/S4k

Recovery
I made a flashable zip to help the recovery console understand our modification. By default, if you go into recovery and do a factory reset, it is formatting the /data partition on the internal storage. The issue same applies to nandroids. We may be using the second partition of our microSD card for /data, but the recovery does not know this. It will look to the internal /data partition during backup and restores.
This zip does not make any modifications to your tablet or copy any files. It simply updates your recovery mount points. The changes are temporary and are lost during the next reboot. You will need to flash it each time you boot into recovery.
After flashing this zip you will be able to:
1) Wipe data / Factory reset. The /data partition on the microSD will be wiped
2) Backup and restore nandroids. The /data partition on the microSD will be backed up or restored.
3) Choose "Flash zip from internal sdcard" and browse the files on the internal storage
4) Access and flash zips from the microSD storage. Choose "Flash zip from internal sdcard" and notice the !microSD folder at the top. This is a symlink that will kick you over to the microSD storage. This !microSD folder appears on your internal storage after you flash this zip for the first time. It remains unless you delete it. Even so, next time you enter recovery this !microSD symlink will not go anywhere until you flash this zip.
Please report your experience with this.
http://d-h.st/pPe

This one too.

So this is basically flashable on CleanRom 2.3 right? Only thing wrong is that it doesn't show up in windows over USB? I can live with that as long as apps can read it in the Android OS itself.

can I use flash this on cleanrom 2.3 to diasable journalling on my ext4 partition

Diogenes5 said:
So this is basically flashable on CleanRom 2.3 right? Only thing wrong is that it doesn't show up in windows over USB? I can live with that as long as apps can read it in the Android OS itself.
Click to expand...
Click to collapse
Nope. This has changes to framework-res.apk which is ROM specific. I will post a CleanROM 2.3 version in a few minutes for you guys.

Thanks - Appreciate your hard work
---------- Post added at 08:46 PM ---------- Previous post was at 08:37 PM ----------
wow that was fast-thanks
---------- Post added at 08:58 PM ---------- Previous post was at 08:46 PM ----------
i was getting 6000 with clemsyn -I got low 5000's with this new mod

clownberg said:
i was getting 6000 with clemsyn -I got low 5000's with this new mod
Click to expand...
Click to collapse
This is not clemsyn's kernel, this is the stock CleanROM 2.3 kernel. I will mod clemsyn's latest kernel and post it for you.

Mistar Muffin said:
This is not clemsyn's kernel, this is the stock CleanROM 2.3 kernel. I will mod clemsyn's latest kernel and post it for you.
Click to expand...
Click to collapse
Unable to have it work with cleanrom. Boot loop

titou00075 said:
Unable to have it work with cleanrom. Boot loop
Click to expand...
Click to collapse
Use recovery to wipe the /cache partition. Due to the changes in framework-res.apk this may be necessary if you aren't coming from a completely clean install of a ROM.
I just booted to recovery and wiped my microSD /data partition. I also wiped /cache and /system. I installed CleanROM 2.3 and in the same recovery session I flashed the clemsynTF700ver22GPU650VC-data2sd kernel and it booted right up.

May be a stupid question but do you still need TWO primary partitions on the SD card (i.e., first is FAT32 while second is Ext4 and used by the mod)? If this isn't necessary or not possible, should the recovery (i.e., installation) files be placed in internal storage?
Forgot to mention I'm using Windows 7 MTP and CleanROM 2.3

Mistar Muffin said:
Use recovery to wipe the /cache partition. Due to the changes in framework-res.apk this may be necessary if you aren't coming from a completely clean install of a ROM.
I just booted to recovery and wiped my microSD /data partition. I also wiped /cache and /system. I installed CleanROM 2.3 and in the same recovery session I flashed the clemsynTF700ver22GPU650VC-data2sd kernel and it booted right up.
Click to expand...
Click to collapse
Ok thanks. Will do:thumbup:

Your Awesome, Thank you!

cheers
Thanks Gonna try this.
done the work install all three files in the OP, however it is taking a long time to boot....Can someone give me an idea as to how long this normally take onn first bootup after a fresh install?
please advise
tyfoxx

Couldyou make one for blackbean? i tried thecm 1029,but it doesnt boot. Would greatly appreciate it.

Sweet
I just ran every shortcut I could think of:
I used Mini partition tool to reduce reduce my 32 gig fat down to 16 gigs & then created a 16 gig ext4 partition.
Wiped everything in twrp and re flashed Clean 2.3 then the new zip.
All I can say is WOW.

Restored everything. Works great no more stalls and stable so far. Hope it stays this way. Now to focus on battery life.
Sent from my HTC Ruby using xda app-developers app

Diogenes5 said:
Restored everything. Works great no more stalls and stable so far. Hope it stays this way. Now to focus on battery life.
Sent from my HTC Ruby using xda app-developers app
Click to expand...
Click to collapse
Glad it's working! I've prepared a little treat for everyone to make our recovery lives a little easier. Need to test a few more things before I post!

I'm running CleanROM 2.3 and ClemsynTF700ver22GPU650VC (awesome combo, btw). If I want to use this MOD, should I need to flash first CleanROM-2.3-data2sd.zip and later ClemsynTF700ver22GPU650VC-data2sd.zip, right? Of course, also, formating my microSD using ext4.

Awesome work here Mistar!!!! Thank you so very much for this!!! Gonna replace my SanDisk 32gb Class 4 card with a SanDisk 64gb Class 10 before I run this on CleanRom. I'm super excited about this mod!!!!!! Thanks a million!!!!!!
Sent from my EVO 4G LTE using xda premium

[Q&A] 2 GB External Data -- Hefe Hook Kernel and others

The Hefe Hook kernel allows you to mount a partition of your microSD as /data, getting 2 GB (or more) for your apps and their data.
Please ask your questions here about installation, use, or general approach.

This is great @jeffsf and can u show me how to re-partition the "real internal" storage? I mean expanding the /system since u put the /data out of it. Thanks man
Sent from my GT-N7000 using Tapatalk 2

daothanhduy1996 said:
This is great @jeffsf can u show me how to re-partition the "real internal" storage? I mean expanding the /system since u put the /data out of it.
Click to expand...
Click to collapse
Yes, you've hit on another of the reasons I've been exploring using the microSD for "live" storage. It's one thing to use potentially slow storage for photos that you basically write once or "app to SD" where you read the APK at boot time, make sure your ODEX in the Davlik cache is good, then generally read from the internal-flash cache. It is another when that memory is being read and written "constantly" when your phone is running.
The good thing is that once /data is not part of the internal flash filesystem, you don't have to worry about one ROM (kernel) thinking it begins at one place and another saying it starts at another. Previously, if one ROM had one /system size and another and a different one, the next partition, /data, would look to be corrupt when you swapped ROMs.
As a warning, not all users have fast microSD cards. Some that say "Class 10" on them really are dogs, especially for small reads/writes. The "Class" ratings are for sustained writes, as you would have with a camera recording video. If your ROM is "external /data" only, or even defaults to that, be prepared for a slew of "Your ROMs sucks. It is so slow." complaints.
You'll also need a way to automate formatting the card. It can be done on the phone, as long as you aren't trying to preserve any data.
As I recall, the layout of the MTD partitions is done in drivers/mtd/onenand/samsung_galaxys4g.h I would be careful not to move the partition boundary for efs, as you'd have to move the data it contains in your updater script. Repeating the warning about not moving the boot and recovery partitions is probably a good idea as well!
Your build tree may need some of these values, or at least think it needs some of these values. For example, device/samsung/aries-common from the CyanogenMod/cm-11.0 (KitKat) branch calls out NAND page sizes, partition sizes, and flash block sizes. I haven't looked in detail at your build tree so I can't comment on how it might handle things differently than the CyanogenMod one.

itzik2sh said:
Hi
I hope I don't ask anything silly, but please let me know if any of my assumptions is wrong :
1. I take FBi's251's AOKP milestone 6 (ICS 4.0.4)
2. 8GB SDCard was formatted to FAT32 (4GB) and EXT3 (4GB) using TWRP kernel
(Beastmode's proton kernel to be exact).
3. I would flash this kernel and it would move apps and their data to the sd-ext
without any special additions.
Thanks. I read the thread, but unfortunately 8GB SD is what i have and I think it should be enough.
Thanks again.
P.S - it's for 2 guys I already sold them my SGS4Gs. I want them to be happy...
Click to expand...
Click to collapse
AOKP should be fine. I haven't tried it recently, but it was the tree in which I did the early Hefe Kernel development.
As I understand it, you have a microSD with
partition 1: 4 GB FAT32
partition 2: 4 GB ext3
So that can work, but will need some tweaking of the init-on-fs.sh script. I intentionally didn't use the second partition as so many scripts gobble that up as sd-ext and do who knows what to it.
My first preference would be to reformat the cards, perhaps:
6 GB FAT32
1 MB ext2/3/4 (Yes, 1 MB, a sliver, choice of ext2, ext3, ext4 up to you)
2 GB ext4
since then the script will work without modification and if they install a third-party script that uses the second partition, it won't corrupt their data.
If you were to keep the formatting the way that it is now, you'd need to edit the mount commands in the script to look something like:
Code:
/system/xbin/busybox umount /data
/system/xbin/busybox mount -t ext3 -o noatime /dev/block/mmcblk0p2 /data
(removing the sd-ext mount)
I'm not sure what your expectations are, but all that the kernel and that script will do is mount a different disk partition on /data -- you need to manually move the data over (or restore from something like Titanium Backup). There may be some trickery in renaming that could be used with TWRP backups to restore from data.yaffs2.win to the new /data partition, but I haven't tried that at all.

Hi Jeff
Thanks for your quick reply, and sorry again for not seeing the Q&A thread.
I think making it :
partition 1: 4 GB FAT32 (sdcard)
partition 2: 2 GB ext3 (sd-ext)
partition 3: 2 GB ext3 (data)
partition 4: 1 MB (spare)
would be better and handle data as well. don't you think ?
Would it be worth doing with a "Team" micro-SD card (class 6 I believe) ?
Thanks.

I haven't tried a Class 6 card, but my gut feeling is that it will be dicey. I didn't "commit" to using /data on microSD until I had tried it for several days using Titanium Backup's ability to move both apps and app data to the external card. I would try that first, especially as the phones in question aren't going to be in your hands (I consider you an expert user, able to manage things outside the UI with ease).
I've attached some testing I did a while ago with Transcend and SanDisk cards. When you look at them, realize that the speed scale changes between them. I have a feeling that the real "performance" on a device is going to be related to relatively small reads and writes, not the ability to stream video to the card. I also don't know much about the Team brand, but I found that even some well-known brands didn't have the performance of the Transcend or SanDisk in the same category.
However you configure your cards, I would definitely recommend a journaling filesystem of some sort. I've had my microSD come loose inside the phone. The journal will at least help to reduce any filesystem corruption should that happen.
You don't need the fourth partition -- I have it there to be able to keep rsync backups for fast ROM swapping.
.

Regarding the apps data, have you tried exploring the Mount2SD script ?
sent from me

I've tried a couple of the scripts out there in the past. Since backing up my data is very important to me, I trust the scripts in Titanium Backup to work well with its backup/restore strategies.
Mounts2SD looks like it has gotten a lot more sophisticated than it was when I tried it in the past. It sounds like something worth trying in its current state. At a quick glance (and not looking at the code), I'd personally make some different choices about features; enabling journaling, and being concerned about why lost+found was filling up (things should only appear there if the file system is found to be corrupt).

[Q&A] [MOD] SD-EXT Boot MOD - CM12

Q&A for [MOD] SD-EXT Boot MOD - CM12
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD] SD-EXT Boot MOD - CM12. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

I do not know how to use this mod who can help me ?

I do not know how to use this mod who can help me ?

Encryption Unsuccessful Message
I tried both mod1, 2, and 3. Each time I load my rom, load the BOOT-MOD-3.zip, and then my apps (PA Gapps).
I keep getting a Encryption unsuccessful message. Also to note, during the initial boot, it only preps/installs 12-14 apps and not the 70+ that usually need to be done when I don't run the move mod.
Any ideas?

bin8636 said:
I do not know how to use this mod who can help me ?
Click to expand...
Click to collapse
Use google to find how to create a sd-ext, there are many guides.
sillysuliman said:
I tried both mod1, 2, and 3. Each time I load my rom, load the BOOT-MOD-3.zip, and then my apps (PA Gapps).
I keep getting a Encryption unsuccessful message. Also to note, during the initial boot, it only preps/installs 12-14 apps and not the 70+ that usually need to be done when I don't run the move mod.
Any ideas?
Click to expand...
Click to collapse
You need to wipe all partitions except sdcard in recovery, flash rom, gapps, then mod.
When you update rom, flash rom then mod again, that's it.
SD-ext needs to be a second primary partition formatted in ext4 (or f2fs if using cm12/cm12.1).
Note: New versions uploaded. Now supports all ivanich's ROMs (cm11,cm12,cm12.1).

@hinxnz: great mod, thx!
Working great for me, but I got 2 questions:
1) I flashed the newest cm12.1 two days ago and flashed your mod (all in SD except dalvic) afterwards. Now you uploaded a New Version compatible with all ivanich Roms. Does your update make any differences for me with cm12.1? Should I reflash?
2) You just said that the mod should be flashed after gapps, I did it the other way round. Does it matter? Got no problems so far.
Sent from my Sensation using XDA Free mobile app

Tommyfirebird said:
@hinxnz : great mod, thx!
Working great for me, but I got 2 questions:
1) I flashed the newest cm12.1 two days ago and flashed your mod (all in SD except dalvic) afterwards. Now you uploaded a New Version compatible with all ivanich Roms. Does your update make any differences for me with cm12.1? Should I reflash?
2) You just said that the mod should be flashed after gapps, I did it the other way round. Does it matter? Got no problems so far.
Sent from my Sensation using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't matter in what order, as long as the mod is flashed after ROM because it edits ramdisk in the kernel.
Your fine with the version you have, it will act the same. You can flash the newer version when you update your ROM.

Problem with storage size
Thanks very much for the mod.
I wanted to use "All Data excl. Dalvik-Cache" and ivanichs cm 12.1 with 4ext recovery.
I was using delta-roh method on my previous installation.
I wiped all partitions except SD card. clean install the rom, then pico gapps and then this mod. Then i install my backups with titanium backup and it started to say storage is full.
When I checked the storage it was still showin 1.15gb and it was full. But installed app size was showing 2gb. I wast able to get sms because of the storage was full.
Am I missing something with the installation method?
Thanks is advance for the replies.

How can I check free/used space on idata?
Sent from my Sensation using XDA Free mobile app

Same problem
Hey guys, I'm having the same problem than AKAndrew41. It gives me encryption unsuccessful screen after reboot. It keeps loading at bootloop and can't enter recovery neither. Can you help me?
Thank you!

sicko40 said:
Hey guys, I'm having the same problem than AKAndrew41. It gives me encryption unsuccessful screen after reboot. It keeps loading at bootloop and can't enter recovery neither. Can you help me?
Thank you!
Click to expand...
Click to collapse
Hi, I flashed boot.img (this file I unzipped from ivanich ROM 18.04.2015 ROM) from the computer with adb and flashed ivanich ROM 18.04.2015 from TWRP ivanich. It's helped.
Sent from my Sensation using XDA Free mobile app

Tommyfirebird said:
How can I check free/used space on idata?
Sent from my Sensation using XDA Free mobile app
Click to expand...
Click to collapse
You could use a root file explorer and check the properties of /idata or just enter code below into a terminal emulator. To enable terminal in cm12, goto developer options and enable local terminal.
Code:
df /idata
sicko40 said:
Hey guys, I'm having the same problem than AKAndrew41. It gives me encryption unsuccessful screen after reboot. It keeps loading at bootloop and can't enter recovery neither. Can you help me?
Thank you!
Click to expand...
Click to collapse
To enter recovery pull battery out, then reinsert it. Hold down volume down button while powering up device and it will enter bootloader, which then you can enter recovery by selecting recovery.
You must have a second primary partition (sd-ext) of your sdcard formatted as ext4 (or you can choose to use f2fs if using cm12 or cm12.1).
If your formatting your whole sdcard instead of shrinking your fat32 partition, then you need to create the first partition (fat32) first and then the second (ext4 or f2fs), otherwise they will be labelled wrong.
CM11 doesn't support f2fs, so if you format it as f2fs on CM11, you will get an encryption error and same goes I guess if you format a partition in ext2 or ext3 because it's not configured in fstab.
Did you try flashing ROM and then mod again, maybe it was a bad flash, it can happen.

I'm using your MOD Plus V3 with 2 f2fs partitions at the moment, which I created with GParted.
What does TWRP do when wiping sd-ext in recovery? If I need to wipe both is there any posibility without using GParted?
And similar, what is backuped by TWRP when doing a backup of sd-ext?

Multi swap
Hi there,
I love the work you've been doing on the sensation and I'm glad to still be using it 4 years on with the latest CM12.1. I have a problem with lagginess after multiple attempts to install CM12.1 and your boot mod v1.2. It seems to be an issue relating to the memory and swap, and I noticed running the cat /proc/swaps shows BOTH /dev/block/zram0 AND the data partition. Removing the zram0 by using the swapoff command speeds the phone up loads. Is there a permanent fix though to persist after reboots?
Thanks,
Keith

geekshow said:
Hi there,
I love the work you've been doing on the sensation and I'm glad to still be using it 4 years on with the latest CM12.1. I have a problem with lagginess after multiple attempts to install CM12.1 and your boot mod v1.2. It seems to be an issue relating to the memory and swap, and I noticed running the cat /proc/swaps shows BOTH /dev/block/zram0 AND the data partition. Removing the zram0 by using the swapoff command speeds the phone up loads. Is there a permanent fix though to persist after reboots?
Thanks,
Keith
Click to expand...
Click to collapse
Hi Keith, zram shouldn't be active, my mod disables it in fstab.pyramid, found in the root directory.
I don't know why it's activated on your side, maybe an app or init.d script.
To disable it, you could use an init.d script.
Code:
#!/sbin/sh
# Disable ZRAM
swapoff /dev/block/zram0

ZRAM sorted
Thanks for the reply mate. I installed TWRP (from 4ext) and used it to reformat everything and start from scratch which sorted out the ZRAM0 issue.
After reinstalling ivanich's CM12.1 and your boot mod v1.2 it was much better. I'm still having intermittent lag and slow network speeds so I reverted to CM11 this morning (with your boot mod) to see if it was any quicker. Seems to be much quicker but the lag persists. Weirdly I get the lag most in the settings, and it bombs out sometimes. I'm wondering if it could be to do with my SD card partitions which were created in GParted, not TWRP.
If you've got any ideas of things to check I'm all ears.
Thanks for the kind support!

geekshow said:
Thanks for the reply mate. I installed TWRP (from 4ext) and used it to reformat everything and start from scratch which sorted out the ZRAM0 issue.
After reinstalling ivanich's CM12.1 and your boot mod v1.2 it was much better. I'm still having intermittent lag and slow network speeds so I reverted to CM11 this morning (with your boot mod) to see if it was any quicker. Seems to be much quicker but the lag persists. Weirdly I get the lag most in the settings, and it bombs out sometimes. I'm wondering if it could be to do with my SD card partitions which were created in GParted, not TWRP.
If you've got any ideas of things to check I'm all ears.
Thanks for the kind support!
Click to expand...
Click to collapse
No worries, first try a lower swappiness value by lowering value in /cache/swap.conf, save it and then reboot.
Try 30 or 40, default is 60. See how it goes.
If you still have lag then your memory could be running very low, use an app or init.d script to raise minfree values slighty higher.
I don't think it has to do with your sd partitions, could be your sdcard is a little slow maybe.
You could probably check the partitions in twrp or gparted though.
If you sort it, post what you did :good:

hinxnz said:
No worries, first try a lower swappiness value by lowering value in /cache/swap.conf, save it and then reboot.
Try 30 or 40, default is 60. See how it goes.
If you still have lag then your memory could be running very low, use an app or init.d script to raise minfree values slighty higher.
I don't think it has to do with your sd partitions, could be your sdcard is a little slow maybe.
You could probably check the partitions in twrp or gparted though.
If you sort it, post what you did :good:
Click to expand...
Click to collapse
Update: Blew everything away again and installed cm12.1 fresh without the SD-EXT mod and it runs fast and lag-free. Installed the sd-ext and lagginess came back. :-/
I had previously tried a fresh install with another SD partitioned by TWRP, made no difference to lagginess. Lower swappiness values seemed to have a minor difference but still laggy.
The lagginess seemed to be mostly when loading from disk. Applications in RAM seemed to run fine until they needed to load something. Downloads very slow on WiFi or 3g, titanium backup very slow too. Strange...
It would be nice to get it working but this is a tad baffling. Thanks for your kind support!
Keith

geekshow said:
Update: Blew everything away again and installed cm12.1 fresh without the SD-EXT mod and it runs fast and lag-free. Installed the sd-ext and lagginess came back. :-/
I had previously tried a fresh install with another SD partitioned by TWRP, made no difference to lagginess. Lower swappiness values seemed to have a minor difference but still laggy.
The lagginess seemed to be mostly when loading from disk. Applications in RAM seemed to run fine until they needed to load something. Downloads very slow on WiFi or 3g, titanium backup very slow too. Strange...
It would be nice to get it working but this is a tad baffling. Thanks for your kind support!
Keith
Click to expand...
Click to collapse
Seems to me that your sdcard is not fast enough, what make and kind of card do you have?
SDHC or SDXC and UHS-I or UHS-II
I have a Sandisk Ultra SDHC UHS-I and it's only just fast enough for this mod, I need a faster one really.
I have no issues with download speeds with wifi, not really related to mod though, could be slow at writing to sdcard.
Titanium could be slow due to slower writing speeds on sdcard too as it has to build dalvik-caches on sdcard when restoring apps.
Edit: Can you try BOOT-MOD-1.1.zip, it's the non-plus version. It would be good to know if you still experience lags with it, if you do, then sdcard is not fast enough, otherwise could be something to do with the plus version, cheers.

hinxnz said:
Seems to me that your sdcard is not fast enough, what make and kind of card do you have?
SDHC or SDXC and UHS-I or UHS-II
I have a Sandisk Ultra SDHC UHS-I and it's only just fast enough for this mod, I need a faster one really.
I have no issues with download speeds with wifi, not really related to mod though, could be slow at writing to sdcard.
Titanium could be slow due to slower writing speeds on sdcard too as it has to build dalvik-caches on sdcard when restoring apps.
Edit: Can you try BOOT-MOD-1.1.zip, it's the non-plus version. It would be good to know if you still experience lags with it, if you do, then sdcard is not fast enough, otherwise could be something to do with the plus version, cheers.
Click to expand...
Click to collapse
I'm using a Lexar 32GB class 10 SDHC, had no issues with it. I ran the A1 SD card benchmarking tool and it measured reads of 17 and writes of 11 MB/s. The internal flash reported speeds of 25MB/s read and 7MB/s write by comparison.
I'll try the BOOT-MOD v1.1 and report back...