First of all
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
You must have TWRP Recovery with F2FS support.
As far as I know, multirom-twrp works (but keep in mind to not add multirom support patch on M ROMs) or use
twrp-2.8.7.0-mako_f2fs_otg_multi.zip for flashable zip by @txuki2005 or either extract img file from it and flash using fastboot or
openrecovery-twrp-2.7.0.0-mako-All-F2FS.img for fastboot image from CallMeAldy thread (in this thread you can also find script to do all formatting for you, but if you want to have more control just continue with my guide it's also place where I found F2FS description at). It's also possible to auto-convert to f2fs using Quanta Tweaks app for Quanta Kernel users.
Few things to know before starting:
Kernel and rom must support f2fs, if it doesn't your device will stop on lockscreen asking for unknown password, for list of supported kernels and roms I'd suggest going to CallMeAldy thread again but I will add some more supported kernels here
Always do a backup (despite different filesystems it is possible to restore your /data)
If you made a backup copy it somewhere else before you continue because there's a risk your internal storage including your previously made backup will vanish
rm -rf is a linux command that removes files without making changes to partitions filesystem (you can see the difference in step2 in restore guide)
Format removes files and changes filesystem usually to default if not specified (which is ext4) (you can see the difference in step3 in restore guide)
Formatting /system as f2fs will cause device to not boot, probably bootloader doesn't recognize it even if supported in kernel
Step by step guide starts here:
Make a backup and copy it on other storage than phone, copy your internal storage files as well if you wish to keep them!
{
"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"
}
[*]Got to TWRP settings menu and make sure 'Use rm -rf instead formatting' is DISABLED
[*]Go to TWRP Wipe menu and select Advanced wipe settings
[*]Select desired partitions ONE at a time - /data and /cache then continue to "repair or change filesystem"
[*]Then go to Change File System (mine says it's already f2fs in Current File system line on top, if you didn't do this before, it will say ext4)
[*]Verify your partition is f2fs by checking Current file system line on top that said ext4 before is now saying f2fs. If it's still ext4 you probably forgot to uncheck step 2.
[*]If you made it for /data first then repeat steps 5 and 6 for /cache and vice versa
[*]If both partitions are f2fs now, ENABLE 'Use rm -rf instead formatting'
[*] Install your ROM and Kernel
If you wish to restore your /data from previous installation
Go to TWRP settings menu and make sure 'Use rm -rf instead formatting' is ENABLED
Go to TWRP restore menu and select your backup (if it's empty after changing to f2fs then better you've done as I advised to copy backup from phone somewhere else). If it's working you will see confirmation and "Removing all files" under partition that is being restored. It will not change filesystem back to ext4.
To compare when 'Use rm -rf instead formatting' is DISABLED it will say "Formatting using mkfs.ext4" function and partitions will be back again ext4
Kernels and ROMs supporting f2fs
with Android Marshmallow 6.0
Quanta V9 M and newer (it's possible to auto-convert to f2fs using Quanta Tweaks app with this kernel)
TaUrUs R37 and newer
if you know about more kernels supporting it, let me know
ROMs (Marshmallow):
Chroma - probably will need other kernel from above
PureNexus Project
SAOSP - Simple AOSP
with older Android releases
They can be found in CallMeAldy thread post #2 and #3
thanks for this great post
Nice post! You can add also that you have to possibility to convert directly to F2FS using Quanta Tweaks. (if one uses Quanta) That said, the current version's converter is broken but will be fixed in the next release.
Also add simple aosp ROM, data and cache.
Everytime I do this, my sd card is wiped and I have nothing. No system to boot or files. But it is changed to f2fs. So I need to use Nexus Toolkit to flash Factory Image. And then I am in loop because then my card is ext4. Do you know where is problem? Thanks.
Filip1092 said:
Everytime I do this, my sd card is wiped and I have nothing. No system to boot or files. But it is changed to f2fs. So I need to use Nexus Toolkit to flash Factory Image. And then I am in loop because then my card is ext4. Do you know where is problem? Thanks.
Click to expand...
Click to collapse
Every time you flash a non-F2FS ROM to the /system partition it will reformat the /system partition to ext4. So, unless you have an F2FS compatible ROM, you should only format the /cache and /data partitions as F2FS. The format process is different from a "wipe", so you will lose all of the files stored on /data/media (a.k.a. sdcard0 or " internal storage") when you convert the /data partition to F2FS.
What if I'm already coming from a f2fs ROM and I want to change it to another ROM that supports f2fs and also to change the kernel with another f2fs one?
Do you know how to do full-f2fs installation(format /system as f2fs as well)? Is it better performance than just /data
and /cache being f2fs?Thank you.
e2fsck and badblocks can't recognize f2fs partitions
every time my nexus 4 still in bootloop, i try repairing data partition with "adb shell e2fsck -ycftv /dev/block/mmcblk0p23" and it founds many badblocks after that i can reboot my phone properly. but the problem is that other badblocks appears after some days of use, so i still doing the same thing to reboot my phone until i did this command : "mke2fs -c -c -T ext4 -L DATA /dev/block/mmcblk0p23" but the problem persists so i tried to move to f2fs partition but the is that badblocks and e2fsck can't recognize this file system in case of badblocks problem........ please help me, i didn't find a good solution ....
andy0777 said:
Do you know how to do full-f2fs installation(format /system as f2fs as well)? Is it better performance than just /data
and /cache being f2fs?Thank you.
Click to expand...
Click to collapse
No. System partition is read only and the are no big differences between ext4 and f2fs in read speed.
TheArt. said:
No. System partition is read only and the are no big differences between ext4 and f2fs in read speed.
Click to expand...
Click to collapse
I see. Thanks.
Thanks for this guide. I successfully installed Chroma ROM (Download link) with Banks G Apps (Download link) and the Taurus for Marshmallow AOSP Kernel (TaUrUs-Mallow-AOSP-mr1-Mako-R39_anykernel.zip) - (Download link).
General process was to flash the recovery you mention, follow your instructions, do a factory reset and wipe system. Flash the Chroma rom. Wipe cache and dalvik cache, flash the kernel. Wipe cache and dalvik again. Flash Gapps, reboot.
I know some of it was probably overkill, but it worked first time Only hiccup was that "Use rm -rf instead of formatting" was disabled when I booted to recovery, and I mis-read the instructions, so I accidentally *enabled* it rather than leaving it disabled. But once I realised the mistake it was quick and easy.
EDIT: Solved
TheArt. said:
EDIT: Solved
Click to expand...
Click to collapse
Sorry, didn't have time to respond, what was the issue? Was it recovery version?
I was using unofficial twrp3.0.0 and I had problems because my backup hadn't the cache partition so /cache returned to ext4, don't know how and why. And I also flashed the rom after converting to f2fs and before restoring. I shouldn't have done that. Eventually I managed to keep my data from Krenux ext4 to Krenux f2fs.
Urgently help
Hello I want the partition back to f2fs from ext4 but no recovery anymore and with fastboot recovery.img can not boot
I have an Axon 10 Pro and have a Custom TWRP installed with Fastboot then restarted the file system from f2fs to ext4 and now I can not get help to Recovery Biite anymore:crying::crying:
Related
*** This MOD only works with phones with working internal SD ***
*** DO NOT FLASH THIS IF YOU ARE AFRAID OF EXPERIENCING BOOTLOOPS ***
To those of you who have not been following the Encryption Unsuccessful thread: http://forum.xda-developers.com/showthread.php?t=1447303, Several weeks ago I proposed a workaround to reduce the possibility of crippling our phones with the infamous EU bug of ICS: http://forum.xda-developers.com/showpost.php?p=26593304&postcount=632
In short, the idea is to force ICS to use /data on the external micro SD instead of the internal. In this way I hope the EU bug will corrupt the external SD (fixable by reformatting it using a card reader on a PC) instead of the internal. In addition, we may be able to reproduce the EU bug and obtain some nice logcats for helping our great devs at finding and hopefully fixing the bug. Besides, I'd rather break a 10USD micro SD card than a 300USD captivate.
The idea is simple so is the "solution". I've developed some scripts that take as input any ICS ROM (tested with CM9, AOKP and MIUIv4) and modify it to use /data on the external SD. I've installed my modified CM9 running with /data on a partitioned 8GB SanDisk class 4 SD card with good performance. BTW, a faster SD does not imply faster performance in this setup, because the way Android uses /data: http://forum.xda-developers.com/showthread.php?t=1005633
Considering that the modified ICS does not mount /data on the internal SD and mounts the external SD FAT partition as /sdcard, it does not even require the internal 16GB FAT partition... in theory it is less likely that the EU bug will kill the internal SD, but no one knows for a fact. Moreover, the internal SD card FAT partition gets mounted as /emmc, but you can unmount it from Settings>Storage just to be on the safe side.
I've been using the modified CM9 for some time and it works great. Some testers have also helped. Off course YMMV. Please do not report bugs to the developers of CM9 (AOKP or MIUI) if you use this mod because this is not official.
Read carefully before proceeding:
*** Disclaimer: Usual disclaimer applies here as well... you use this at your own risk, I am not responsible for anything that happens to any of your devices. You assume all responsibility when using this ROM. ***
To install this you need a micro SD card with enough space for two partitions (1GB for /data + all the space you need for music, photos, videos, games, etc. on /sdcard)
First, partition a micro SD card using a PC. Create two primary partitions (not logical) in this exact order:
a FAT32 partition that will be mounted as /sdcard: the SD card capacity - 1GB (or more if you have many apps)
an EXT4 partition that will be mounted as /data: 1GB (or more if you have many apps)
There are many programs to partition SD cards. I have used the Disk Utility included with Ubuntu 12.04. I don't have Windows, but some people reported that this may help: http://forum.xda-developers.com/wiki/SD_card_partitioning
Optional Insert the partitioned SD card in your phone and boot whatever Android you have to check if it works. On CM7 the external FAT32 partition should be mounted as /emmc and the EXT4 as /sd-ext
*** Disclaimer: I've flashed the modified CM9 from CM7.2, CM9 and MIUIv4, so I have no idea if other combinations will work ***
Now follow these steps:
1) Ensure you are on GB Bootloaders and you have a recent CWM recovery (tested with CM7)
2) Verify that the 3 button combo works for booting in CWM. Otherwise STOP here and read more about flashing ROMs.
3) Download the modified ICS: CM9.1 or AOKP b40
4) Download Gapps for ICS: http://goo.im/gapps/
5) Copy the two files to the FAT partition of the partitioned micro SD card using your PC and insert it into your phone.
6) Boot your phone to CWM
7) Wipe data/factory reset, wipe cache, wipe dalvik cache under advanced
8) Flash Rom (install zip from sdcard->choose zip from internal card), it will bootloop because of the new mount points.
9) Remove the battery and reboot into recovery using the 3 button combo
10) Flash Rom again. Note that now the internal SD and external SD are reversed. (install zip from sdcard->choose zip from SD card)
11) Flash Gapps: http://goo.im/gapps/
12) After some minutes (2 to 5) ICS will be ready
This is the output of the mount command after booting:
{
"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"
}
*** Please DO NOT report bugs to the developers of CM9, AOKP, Devil or Semaphore kernels if you use this mod because this is not official. ***
All credits to:
- the CyanogenMod team
- the AOKP team
- DerTeufel1980 (for the Devil kernel and his detailed instructions about how to modify the kernel)
- stratosk (for the Semaphore kernel and his instructions about how to compile the kernel)
- all the people who have tested this mod
---
Changelog:
8/29/2012:
CM9.1
8/11/2021:
CM9 stable!!!!
7/19/2012:
CM9 RC2. I will update only when RC/stable versions are released.
7/18/2012:
Kernels removed.
7/17/2012:
Updated Semaphore Kernel (1.2.6)
7/16/2012:
Updated Devil Kernel (1.0.0-rc3)
7/11/2012:
Updated Devil Kernel (0.98.3)
7/3/2012:
Added link to the most recent CM9 nightly (automatically patched and uploaded)
7/1/2012:
Updated Devil Kernel (0.92)
Updated CM9
6/29/2012:
Added Semaphore Kernel. Thanks stratosk!
Added AOKP b40
Updated CM9
6/20/2012:
Added Devil3 Kernel. Thanks DerTeufel1980!
6/19/2012:
Updated CM9
6/16/2012:
New script for modifying any CM9 ROM. Updates are easy!
6/14/2012:
Initial release based on a recompiled CM9
--
IF I HAVE HELPED YOU IN ANY WAY, PLEASE THANK ME or DONATE: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=AQF82UCZ9AF6L
* reserved *
* reserved *
Thank you!!
Sent from my SGH-I897 using xda premium
azunino said:
... In theory it is possible to extract from a boot.img file the init.rc file with the mappings and modify it, but I have not idea how (some help please reversing https://github.com/CyanogenMod/android_device_samsung_aries-common/blob/gingerbread/mkshbootimg.py ?). Well, if we can solve that, I can write a shell script to convert any(?) ICS based ROM/kernel and modify it to use /data on the external SD.
Click to expand...
Click to collapse
Perhaps this would be of some help?:
HOWTO: Unpack, Edit, and Re-Pack Boot Images
visionlogic said:
Perhaps this would be of some help?:
HOWTO: Unpack, Edit, and Re-Pack Boot Images
Click to expand...
Click to collapse
Thanks, but I've tried that. It seems SGS devices use a slightly different format. I'll keep reading about it until I find a way to unpack/repack the images.
I saw "Other kernel will not work" so it seems that you have compiled a modified kernel to change the mount points ? If so I think it's also very promising to be a solution to build a CM to use with broken internal storage...
I'm using stock-based roms with modified kernels but I couldn't manage to repack a working CM compatible kernel...
Fishmanzero said:
I saw "Other kernel will not work" so it seems that you have compiled a modified kernel to change the mount points ? If so I think it's also very promising to be a solution to build a CM to use with broken internal storage...
I'm using stock-based roms with modified kernels but I couldn't manage to repack a working CM compatible kernel...
Click to expand...
Click to collapse
That is correct. I modified the files that contain the mount points and the updater.sh. The problem with these files is that they are packed together in a ramdisk (ext2 filesystem image), recovery and with the kernel in a boot.img file. Therefore, it is not trivial to modify them to work with any kernel/ICS ROM.
Yesterday, after hours of reading hexadecimal boot.img files... I wrote a python script to unpack a boot.img file and extract from it the kernel, ramdisk and recovery ramdisk. These ramdisks are easy to modify (cpio format), so right now I'm testing a shell script that takes as input any ICS based ROM (or kernel) and modifies it to use /data as my modded CM9. In other words, things are getting interesting ;-)
Once I finish the script It would be very easy to change mount points as you wish because they will be no longer hardwired in each ROM/kernel. So... let your imagination fly.
Updated OP. Now I can automatically convert CM9 and AOKP to use /data on the external SD.
I'm extending the script to handle kernel updates. BTW, some of them seem to use a different boot.img format.
but we can not automatically convert CM9 and AOP to use / data on the external SD. instruction will be for us?
I will post the scripts, but first I have to make them more user friendly and add some error handling code
Sent from my SGH-I897 using XDA
I wait impatiently, when will it be?
Just to clarify, to those that used this trick in the past (other phones) and got the encryption unsuccessful bug, what happened was, their external sd card got unusable by the phone, but formatting it with a card reader was all it took to bring it back.
I expect that a good look at these corrupt sd cards would bring good insight to solve the problem.
Sent from my SGH-I897 using XDA
manolis said:
I wait impatiently, when will it be?
Click to expand...
Click to collapse
during the weekend
manolis said:
I wait impatiently, when will it be?
Click to expand...
Click to collapse
nice
Updated to the CM9 nightly that has some important fixes (WiFi, location)
azunino said:
Updated to the CM9 nightly that has some important fixes (WiFi, location)
Click to expand...
Click to collapse
Thank you, you good man!
Question, if I use this and want to revert back, will I able to return to kk4 stock?
takeoutttt said:
Question, if I use this and want to revert back, will I able to return to kk4 stock?
Click to expand...
Click to collapse
Yes. You can revert to any ROM.
Sent from my SGH-I897 using XDA
azunino said:
Updated to the CM9 nightly that has some important fixes (WiFi, location)
Click to expand...
Click to collapse
When will the new NIGHTLY?
ROM and this can be done to install from external SD http://forum.xda-developers.com/showthread.php?t=1625619
Sup!
The problem is, that after i install ROMs via NAND+ext i cannot simply use it, because after rebooting it shows htc logo and then screen goes black.
I used only NAND roms before, because my sd card always failed to create an EXT partition on it.
But idk why, few days ago i noticed that while wiping, it didn't skip EXT partition like always, so i created one via TWRP recovery and tried to install some roms on ext.
I've done several full-wipes etc, but always it succeeds with installation, and then it goes black screen on rebooting.
What can be the problem? I thought it might be boot.img-related, but same thing occurs in 2nd rom i try to install.
I don't want to go back to old NAND rom, so if you guys could help me out, i would be really happy.
I spent several hours looking for a solution, but no positive results..
Also, i had a problem in trying to reanimate my phone via Fastboot/ADB; simply because i don't know how to proceed from bootloader to fastboot to get my phone connected with pc commands...
I tried to flash this and that ROMs.
Regards!
you could try;
changing recovery (eg 4ext), i always seem to have trouble with twrp flashing sboot, 4ext works ok
increase sboot or boot size
format ext4 with 4ext recovery
not used fastboot much, there is a tutorial here http://forum.xda-developers.com/showthread.php?t=2277112
hope this helps
if not post your setup, partition sizes etc.
Thanks for reply Robbie!
Firstly, i cannot find 4EXT recovery to flash it straight from PC :/ Any other recommended recovery's?
Secondly, not sure if i understand sboot and boot resizing correctly.
Also, when i flash TWRP for example, in config file when i change system ya[/B ] to 280mb is it enough? I mean, when i change size via HD2Toolkit, it automatically applies CWM...
http://goo.im/devs/Xylograph/Various/Recoveries/NAND
flash it using existing recovery
in later versions of clk you can easily resize your partitions, sometimes increasing boot partition may solve booting problems.
eg black lk from here http://www.mediafire.com/download/n0aa6qv88t3n1sv/black_lk_20130506-Ex-TWRP_2_5_0_5.zip
extract it, browse to leoimg.nbh using hd2 toolkit "install custom NBH/NB RUU" and install.
Then flash 4ext using the included recovery.
Profit?
Robbie P said:
http://goo.im/devs/Xylograph/Various/Recoveries/NAND
flash it using existing recovery
in later versions of clk you can easily resize your partitions, sometimes increasing boot partition may solve booting problems.
eg black lk from here http://www.mediafire.com/download/n0aa6qv88t3n1sv/black_lk_20130506-Ex-TWRP_2_5_0_5.zip
extract it, browse to leoimg.nbh using hd2 toolkit "install custom NBH/NB RUU" and install.
Then flash 4ext using the included recovery.
Profit?
Click to expand...
Click to collapse
Never thought of going to CLK though
Okay, i have clk now.
So i need to put 4ext zip into SD card throught TWRP usb plugging, and then install it straight from twrp?
Update!
I flashed 4EXT, althought i had strange code message after flashing it:
Code:
Writing recovery partition...
All done.
Updating partition details...
E:Failed to mount '/system' (MTD)
Partition details updated
Anyway, it seems to load w/o problems
Whats my point... i noticed, that i have ext2 partition on my phone, not ext4.
Can it cause black screen problem?
What to do now?
(So many questions..)
~EDIT~
i used built-in partitioning to get EXT4 partition, then installed tytung's rom again, ofc succeed etc.
But after reboot i see htc logo for 1 sec, then black screen ... sigh
ZathuraPL said:
Update!
I flashed 4EXT, althought i had strange code message after flashing it:
Code:
Writing recovery partition...
All done.
Updating partition details...
E:Failed to mount '/system' (MTD)
Partition details updated
Anyway, it seems to load w/o problems
Whats my point... i noticed, that i have ext2 partition on my phone, not ext4.
Can it cause black screen problem?
What to do now?
(So many questions..)
~EDIT~
i used built-in partitioning to get EXT4 partition, then installed tytung's rom again, ofc succeed etc.
But after reboot i see htc logo for 1 sec, then black screen ... sigh
Click to expand...
Click to collapse
You need yaffs2 for nand for android to work
lolerpro8 said:
You need yaffs2 for nand for android to work
Click to expand...
Click to collapse
Okay, but... how to...get it ?
~EDIT~
Reflashed SlimRom with ext, but it hangs on htc logo again..
ZathuraPL said:
Okay, but... how to...get it ?
~EDIT~
Reflashed SlimRom with ext, but it hangs on htc logo again..
Click to expand...
Click to collapse
so, what are your partition sizes, nand and sdcard?
remember, if using nand with data on ext, you can afford a huge 350mb system partition or more since your data (apps and stuff) is on your ext4 sdcard partition.
Please provide details
Robbie P said:
so, what are your partition sizes, nand and sdcard?
remember, if using nand with data on ext, you can afford a huge 350mb system partition or more since your data (apps and stuff) is on your ext4 sdcard partition.
Please provide details
Click to expand...
Click to collapse
Here it goes!
recovery 8
boot 5
misc 1
system 235
userdata 157
sboot 10
cache 5
+ i have 2gb ext4
SlimRom requires about 210 system partition, so i set 235.
ZathuraPL said:
Here it goes!
recovery 8
boot 5
misc 1
system 235
userdata 157
sboot 10
cache 5
+ i have 2gb ext4
SlimRom requires about 210 system partition, so i set 235.
Click to expand...
Click to collapse
increase system to 350mb and reinstall "nand with dataonext" and see
Robbie P said:
increase system to 350mb and reinstall "nand with dataonext" and see
Click to expand...
Click to collapse
htc
...
...
SLIMbean
...
...
...
so far it went past htc logo, but it keeps showin me SLIMbean animation
humm..
~EDIT~
i went to setup wizard, but it kept crashing. I forgot to flash gapps as in thread...sigh.
wiped system partition, flashed gapps, and now booting.
Hopefully it will get to work now!
edit2:
htc logo for about 5 minutes already
EDIT3:
i fully wiped phone, reflashed rom and gapps, it booted (waited like 15min though), but i have some strange problems with going through setup wizard again.
Mainly it stops working after few minutes, and it launches again and again. Sometimes i make till wifi/gmail sync, but for example it keeps obtaining wifi for like minute, in meanwhile Calendar Memore stops working... then it freezes, stops working, and from beginning...Once i made it through Google GPS localization.
The ****...?
Okay, after wipe and reflash, i faced same situation, but not sure why, Setup Wizard after 10 minutes of struggling allowed me to finish setup :highfive:
I still received "Calendar Storage has stopped working" every 10 seconds, so i cleared cashe of it in settings, seems to be solved.
Now, the only issues i face are:
- my phone shows me no internal storage at all...
In settings > apps, Internal storage bar is all grey without any numbers, also i cannot even update Nova Launcher because of insufficient space.
It would be quite sad to have my phone finally working, but with no storage to install basic apps like facebook, etc
-as i want to reboot my phone, it popped Setup Wizard again... WHAT THE!
Please help me with these problems...! :laugh:
EDIT:
i googled ''a bit'', and tried to copy busybox from /system/xbin to /system/bin, but i see no positive results..
Problem has changed.
Another update, but now quite positive.
After reflashing Slimrom and tytung's one over n over, i tried to flash tytung's 4.2.2, well, it succeeded.
Now i have 1,2gb of internal free memory, and it all seem to work flawlessly.
No idea why previous 2 roms didnt work 100%'ly :/
I think i won't do anything now, i am happy to have 4.2.2 features now, after 1 years of being stuck with 4.1.2
Anyways, big thanks for you Robbie. You are my life-saver once again!!!
Have a good night y'all, yawn
###EDIT###
Rom runs smoothly, i have 1,2Gb of internal memory, but my Google Play tells me "No connection. Retry" everytime i open it
Which means i canno't update/download anything.
Tried clearing cache,data,force stop,reboots, still no profits >.< im not into factory reset again though..
_____ EDIT _____
After wake up, around 1 hour of previous usage, i had black screen... rebooted -> Setup Wizard (although no errors or fCloses, only again no internal memory )
ZathuraPL said:
After wake up, around 1 hour of previous usage, i had black screen... rebooted -> Setup Wizard (although no errors or fCloses, only again no internal memory )
Click to expand...
Click to collapse
it sounds like your ext4 partition (/data) is not being recognised.
Since you have to reflash, try deleting all partitions and format whole card with official formatter, then set up your ext4 partition again, use recovery to format it.
Try install again.
What is your sd card make, and class?
Robbie P said:
it sounds like your ext4 partition (/data) is not being recognised.
Since you have to reflash, try deleting all partitions and format whole card with official formatter, then set up your ext4 partition again, use recovery to format it.
Try install again.
What is your sd card make, and class?
Click to expand...
Click to collapse
hold on, gonna plug it through 4ext and try to format
Will edit when im done
_____________________________
Done formatting
{
"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"
}
Also created 2 ext4 partitions (who will forbid lol) 1,5 and 1gb.
Now will flash SlimRom and gApps, i will update again as i get some new info
Robbie P said:
What is your sd card make, and class?
Click to expand...
Click to collapse
about sd card? umm, i think it's SanDisk, but what class... i don't remember.
UPDATE.
I hope that system will survive the night without problems..
Everything runs quite good, i have problems with syncing contacts, but i think i will bypass it.
I connected to Google Play, i have 1,2 Gb of internal memory, so this is positive.
One problem is that when i try to install apps from GPlay, blue bar keeps running infinitely... like something blocks apps from installing.
Gonna try uninstalling GPlay updates, maybe it will help..
Will update again tomorrow!
UPDATE.
Nope.
Again, after about an hour, system started cutting me off more and more processes, so i rebooted, and then i had infinite Cyanogenmod boot animation...
I think im gonna try freaking 4.1.2 with DoE or Nand...
This sd card makes me wanna break this phone into puzzles
PACman 1.2 doesnt work with Ext , but on NAND i have only 197mb of free internal storage after fresh install I wish i could increase this
I was considering attempting to use the f2fs filesystem that is discussed in original android development but I'm a bit confused with what to do to load a new rom. Can anyone explain if it will work with the purity rom and what I need to do to get it working? Or also let me know if its not possible.
Yes, I have used Purity with F2FS, but this filesystem is unstable because the system hangs usually (I have also tried with SlimKat and RastaKat with same hangs copying many files).
Basically:
- You must flash "twrp-unofficial-2.7.1.0-f2fs.img" as a normal recovery and change /data, /cache and /system (optional) to F2FS.
You will find this option under Wipe -> Advanced Wipe, then select only one partition and press the "Repair or Change File System" button for change to F2FS. Use Wipe -> Format Data also (you will lost data in /sdcard).
- Install Purity ROM (if /system is converted to F2FS, you must use "convert2F2FS.jar" for modify ROM zip and must install this new ROM).
- If /system is F2FS, install "KTManta_F2FS-26-06-2014-ALLF2FS.zip" Kernel or "KTManta_F2FS-26-06-2014_CACHE_DATA_PARTITIONS.zip" else.
patzzz said:
Yes, I have used Purity with F2FS, but this filesystem is unstable because the system hangs usually (I have also tried with SlimKat and RastaKat with same hangs copying many files).
Basically:
- You must flash "twrp-unofficial-2.7.1.0-f2fs.img" as a normal recovery and change /data, /cache and /system (optional) to F2FS.
You will find this option under Wipe -> Advanced Wipe, then select only one partition and press the "Repair or Change File System" button for change to F2FS. Use Wipe -> Format Data also (you will lost data in /sdcard).
- Install Purity ROM (if /system is converted to F2FS, you must use "convert2F2FS.jar" for modify ROM zip and must install this new ROM).
- If /system is F2FS, install "KTManta_F2FS-26-06-2014-ALLF2FS.zip" Kernel or "KTManta_F2FS-26-06-2014_CACHE_DATA_PARTITIONS.zip" else.
Click to expand...
Click to collapse
Where do you get convert2F2FS.jar?
Using f2fs with omnirom. All partition were formatted with f2fs. Having no issue with last update. You will find all resources in my thread
Internal Memory Repartition
Hey guys, after a very long time I show you the way to repartition your internal memory (EMMC).
You can modify partitions as you want, increase data partition to install more apps, increase internal storage for media files...
It's based on a little Linux binary called Parted, it's a part of CWM/TWRP recovery ramdisk.
This means that you can repartition in any recovery of any 4.2/4.3/4.4 ROM.
==========WARNING==========
Operations on EMMC partitions could be EXTREMELY DANGEROUS if you don't understand well what you do.
If you touch wrong partitions (CSPSA, EFS, SBLs...) you can lose your IMEI or hardbrick your device (in this case only JTAG can save you) so...
READ CAREFULLY!!!!!
Responsibility is all yours, but if you follow well this guide you will not risk anything.
Stock partition table is designed to be used in stock ROM, since it uses preload partition to store some system apps and needs bigger system (ROM is heavier than CM-based ones) and bigger cache partitions (more system apps=more dalvik-cache).
This mod is compatible with any ROM except stock and stock-based.
This is the stock partition table:
{
"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"
}
You can touch ONLY:
Kernel2
SYSTEM
DATAFS
CACHEFS
HIDDEN
FOTA
UMS
Kernel2 is the backup of stock kernel, we don't need it.
SYSTEM is the /system partition (where the ROM is installed/stored).
DATAFS is /data partition (default 1.97 GB where are stored installed apps, Android settings, contacts, messages... User data).
CACHEFS is /cache partition (art/dalvik-cache is stored here, together with recovery logs/temporary files. In stock ROM here is stored also CSC. If you repartition to the minimum (at least 5 MB needed for recovery) you need to put dalvik.vm.dexopt.data-only=1 flag in system/build.prop
HIDDEN is /preload partition (some Samsung TouchWiz system apps are stored here and symlinked with /system/app. This is a swap partition on MIUI v5, CM10.2 and all CM11/Omni 4.4 builds (these 4.4 before 15 June), also every custom ROM based on Canjica device tree 4.3/4.4 (always before 15 June), resize it to the minimum (128 KB to format it as EXT2).
FOTA is Firmware Over The Air, so is needed to get OTA updates while on stock ROM, can be directly deleted.
UMS is the internal storage (3.96 GB one), you can repartition this to have less/more space, or repartition to the minimum (8 MB or less, you will need to swap internal/external storages).
Parted commands useful for us:
rm (to delete a partition)
mkpart primary (to make a partition)
format (to format a partition, only in ext2)
name (to rename a partition)
For an extended list/explanation of commands, type "help" without quotes
Let's go!
First make a nandroid backup of your current ROM, to be restored after repartition
If you touch UMS you will lose all the content of /sdcard (internal storage), so make a backup first!
You need a Linux distro or Windows with ADB configured.
Reboot device in recovery and connect to USB, then open ADB and write:
Code:
adb shell
parted /dev/block/mmcblk0
You can choose to display partitions as Gigabytes, Megabytes, Kilobytes (suggested), or Bytes by "unit **" command, where ** can be gb/mb/kb or b
Now type "print" to display partition table.
Parted create new partitions by following "Number", for example SYSTEM is 3, CACHEFS is 4 and DATAFS is 5 (for other partitions is the same), so when you create new partitions, you need to make them in order!! For example:
SYSTEM is 3 and its size is from 105906KB to 747635KB
CACHEFS is 4 and its size is from 2895118KB to 3215983KB
DATAFS is 5 and its size is from 747635KB to 2895118KB
The "end" of a partition is the "start" of the next partition
As you can see, DATAFS is between SYSTEM and CACHEFS. This means that after you create SYSTEM, you need to calculate new DATAFS size that you want and then first create CACHEFS (at the end of calculated DATAFS size) then create DATAFS from the end of SYSTEM to the start of CACHEFS.
To understand more:
We will resize now CACHEFS from 320864 KB to 5000 KB gaining 315864 KB for DATAFS:
Unmount /cache from recovery first!
Code:
rm 4 (to delete CACHEFS)
rm 5 (to delete DATAFS)
calculate now the new size of DATAFS, in this case add 315864 KB to DATAFS end: 2895118+315864=3210982 KB
calculate now the new end of CACHEFS, in this case add 5000 KB to 3210982 KB: 3210982+5000=3260982 KB
mkpart primary 3210982 (end of DATAFS and start of CACHEFS) 3260982 (end of CACHEFS, start of the next partition)
Now we made a new partition, its number is 4. Do: name 4 CACHEFS
It's time to make new DATAFS partition: from the end of SYSTEM to the start of CACHEFS
mkpart primary 747635 (end of SYSTEM and start of DATAFS) 3210982 (end of DATAFS and start of CACHEFS)
New partition has number 5, name it DATAFS by name 5 DATAFS
Basically the method is this, you can apply it to partitions listed above.
Remember to reboot recovery, go in Mounts and storage then (depending on what partitions you touched in Parted, excluding /preload) do the appropriate formats after repartition. Now you're ready to restore your nandroid backup (needs to have less size than new partitions) or install a ROM.
I suggest an useful program to check partition size on Android, Partition Table
If you touch HIDDEN partition and you are on 4.2 ROM or 4.4 builds after 15 June:
Code:
format
y
9
ext2
If you repartition UMS to the minimum, you will need to swap internal and external storages (MicroSD card will be the new internal storage):
On 4.2 open system/etc/vold.fstab and replace the content with this:
Code:
# MicroSD as internal storage
dev_mount sdcard0 /storage/sdcard0 auto /devices/sdi0/mmc_host/mmc1/mmc1
# UMS as external storage
dev_mount sdcard1 /storage/sdcard1 8 /devices/sdi2/mmc_host/mmc0/mmc0 nonremovable,encryptable
# usbdisk
dev_mount usbdisk0 /storage/usbdisk0 auto /devices/platform/msm_hsusb_host.0
On 4.3 ROMs open system/build.prop and add these lines at the end of the file:
Code:
persist.sys.vold.switchexternal=1
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
On 4.4 ROMs just open NovaThor Settings and enable "Swap Storages"
To restore original partition table flash stock ROM through Odin with "Repartition" enabled and correct PIT file for your model, in attachment (extract zip), soon CHN pits too
I know that it's difficult to understand well the first times, but think at me that I developed this method, a lot of testing and bricks on bricks
If you found this useful, you can support me at least by pressing "Thanks" or considering to offer me a beer, a coffee... Any kind of support will be very appreciated
Reserved for "The PIT Zone" (soon available!)
Reserved
Another reserved just in case!!
So, I want to shrink UMS (let's say by 1GB) and use it in DATAFS.
What would be the command sequence?
Thank you,
Tasos
tasosf said:
So, I want to shrink UMS (let's say by 1GB) and use it in DATAFS.
What would be the command sequence?
Thank you,
Tasos
Click to expand...
Click to collapse
All what you should know it's wrote in the OP.
You can make our way... rm anything after Kernel2, calculate datafs+1024MB more and make again all partitions, name and format them. Read again and well the OP for clarifications, it's all wrote there
Inviato dal mio GT-I9505
I didnt found any info about it in OP so i ask:
Every partition made using this guide will be formatted as ext2? Ext2 is worse than ext4 so probably it will affect performance, am i right about it?
Command "format" didnt work for me
Instead i used "mkfs <number> ext2" (however it asks about number and filesystem later) and i think "mkpartfs primary ext2 <start> <end>" could be the easiest as it create partition and format it in the same moment so its not needed to remember later
ch3mn3y said:
Command "format" didnt work for me
Instead i used "mkfs <number> ext2" (however it asks about number and filesystem later) and i think "mkpartfs primary ext2 <start> <end>" could be the easiest as it create partition and format it in the same moment so its not needed to remember later
Click to expand...
Click to collapse
Format didn't work for me either. I formatted everything through TWRP to ext4.
So, this method works! I now have 3GB for data so to have all the apps installed in the internal storage and not the internal sd card (ums). This way all apps are faster because ums is formatted as fat 32 in order to be recognised on Windows.
One tricky thing was that you have to mkpart from low numbers to high, regardless if you leave for a moment organ intermediate megabytes. The system always gives the next available number to the partition you make. It may not make sense how I try to explain it, but keep it in mind when you try it.
Sent from my GT-I9070 using XDA Free mobile app
I do exactly opposite thing as made smaller DATAFS, SYSTEM and CACHEFS to have bigger UMS. Its googd that Kernel2, HIDDEN and Fota are after "more" important partitions, so we can get rid of them and get lot of space
tasosf said:
The system always gives the next available number to the partition you make. It may not make sense how I try to explain it, but keep it in mind when you try it.
Click to expand...
Click to collapse
Yep, its important to not make mistakes, coz who wants to do something few times?
ch3mn3y said:
I do exactly opposite thing as made smaller DATAFS, SYSTEM and CACHEFS to have bigger UMS. Its googd that Kernel2, HIDDEN and Fota are after "more" important partitions, so we can get rid of them and get lot of space
Click to expand...
Click to collapse
How come you want to have bigger UMS? Not all apps can be installed there and DATAFS gets full very easily. Also, it's fat32 which creates some problems by itself.
Sent from my GT-I9070 using XDA Free mobile app
I just dont use this phone as my primary and as i have xplay for games i dont need to have lots of apps on it. Additionaly i have only 4gb sdcard for it, so my internal memory is now bigger than external
Sent using TF300T - CyanogenMod 11.0/GRIMLOCK (F2FS)
i'd really like to repartition my phone's memory but i fear i'm gonna screw everything up
i see a coming soon "pit zone" in the second post, does that mean that there is an automatic way to repartition the internal memory without directly using commands?
If u knows how to make pit file after repartitioning its probably possible to use odin to repartition
Sent using GT-i9070 - VanirAOSP
You need to use "format" command in ext2 only for HIDDEN partition that it's unneeded on custom ROMs.
For other partitions (SYSTEM, CACHEFS, DATAFS) format through recovery mode (automatically formatted in ext4), and for UMS through Android.
Yes, the PIT zone will have PIT files ready to be flashed to autorepartition along with a kernel that brings you CWM recovery to install/restore your ROM after repartition.
Inviato dal mio GT-I9505
AntaresOne said:
You need to use "format" command in ext2 only for HIDDEN partition that it's unneeded on custom ROMs.
For other partitions (SYSTEM, CACHEFS, DATAFS) format through recovery mode (automatically formatted in ext4), and for UMS through Android.
Yes, the PIT zone will have PIT files ready to be flashed to autorepartition along with a kernel that brings you CWM recovery to install/restore your ROM after repartition.
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
i will definitely wait for the pit files then all i'm looking for is to get rid of those useless partitions like FOTA, Kernel2 etc. just to have more space on the internal memory for apps
TheSteve87 said:
i will definitely wait for the pit files then all i'm looking for is to get rid of those useless partitions like FOTA, Kernel2 etc. just to have more space on the internal memory for apps
Click to expand...
Click to collapse
Completely agree mate. Also HIDDEN, you don't need it on CM/CM-based custom ROMs
Inviato dal mio GT-I9505
I really have to say this guide is just A-W-E-S-O-M-E
The process is not that easy but very well explained
A complicated by well explained method for partition........But i am a bit afraid to use .... Can u help out with the step for my issue...?
My Phone: S Advance
(Rooted with the help of http://forum.xda-developers.com/showthread.php?t=2087424)
RAM= 768 MB RAM,
ROM= 2 GB //*Note phone shows this as device storage, Pl correct if I am wrong*//
Internal=16 GB (user available=11.31 GB), //*Note phone shows this as USB storage, Pl correct if I am wrong*//
external micro SD card = Nil
I want to increase the RAM Or ROM so that my mobile should not lags/hangs
I feel that mobile is slow mainly due to less RAM......pl correct if I am wrong
I want to use the the 1GB/2GB/3GB/4GB out of Internal 16 GB to increase the size of ROM from 2GB to 3GB/4GB or RAM from 768 MB to 1GB/2GB/3GB/4GB more.....
Pl help me out with the specific steps.....
Thanks a lot @AntaresOne
@anil.xda
Yes, just 768 MB of RAM is one of the biggest performance limiting factors of this phone but sadly you can't just "increase it". You'll have to use something like a zRAM or a SWAP script. But this is just a workaround - and it too has some drawbacks I think.
Sent from my GT-I9070
i got a HD2 and sent it to a store so they will install android on it, they did and it returned with a nice rom, fast and nice looking.
the only problem is that the phone shows that he dosn't have any internal storage, i cant download any apps or recive SMS or any thing like that.
the guy in the store cant fix it ( T__T) and he said (after a few times he sent it to the lab back and forward) that it should work now and if it dosn't he will give me the money back...
well it most be a fixable problem so if you guys could help me that will be great.. im not really good at this stuff so its difficult for me to learn it online.
What rom did they install? look in settings/about phone
If you pay someone to install android, it should work, so a refund might be appropriate.
Robbie P said:
What rom did they install? look in settings/about phone
If you pay someone to install android, it should work, so a refund might be appropriate.
Click to expand...
Click to collapse
i write the categories i think may be related in ''about phone'':
Karnel version:
2.6.32_tytung_ics_r3.6
Build number:
IMM76L (NexusHD2-ics-cm9-HWAV3.0b) [DataOnEXT]
and of course i will recive my money back..
yoniaialon said:
i write the categories i think may be related in ''about phone'':
Karnel version:
2.6.32_tytung_ics_r3.6
Build number:
IMM76L (NexusHD2-ics-cm9-HWAV3.0b) [DataOnEXT]
and of course i will recive my money back..
Click to expand...
Click to collapse
Nice ICS rom
It seems that the rom is not using the ext4 partition for memory as it should (DataOnEXT). What bootloader is installed? On startup immediately press either the end-call button (if magldr is bootloader, you should get a menu) or the back button (if clk is bootloader, you should get a menu)
I pressed the end-call botton right after startup and got a boot manu so i guess magldr is bootloader..
go to magldr menu/8. ad recovery, it should boot your recovery, and tell us what recovery name and version you have installed. Also all information it gives regarding your sd card partitions, size etc.
Robbie P said:
go to magldr menu/8. ad recovery, it should boot your recovery, and tell us what recovery name and version you have installed. Also all information it gives regarding your sd card partitions, size etc.
Click to expand...
Click to collapse
i chose the AD recovery and another manu apeared, it says CWM Touch beta 8 by munJeni
here is a pic:
{
"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"
}
where do i fint the rest of the information you asked for?
I haven't used that recovery, what does the advanced menu show?
Robbie P said:
I haven't used that recovery, what does the advanced menu show?
Click to expand...
Click to collapse
-Reboot Recovery
-Wipe Dalvik Cache
-Wipe Battary Cache
-Report Error
-Key Test
-Show log
-Partition SD Card
-Fix Premissions
those are all the option in the Advanced menu.
what does partition sdcard show?
And in the previous menu, what does mounts and storage show?
Questions questions I know, sorry
Robbie P said:
I haven't used that recovery, what does the advanced menu show?
Click to expand...
Click to collapse
Robbie P said:
what does partition sdcard show?
And in the previous menu, what does mounts and storage show?
Questions questions I know, sorry
Click to expand...
Click to collapse
Mount and storage:
-mount /boot
-unmount /cache
-mount /data
-mount /sdcard
-mount /system
-mount /sd-ext
-format /boot
-format /cache
-format /data
-format /sdcard
-format /system
-format /sd-ext
-mount USB storage
----------------------------------------
Partition SD card:
-128m
-256m
-512m
-1024m
-2048m
-4096m
---------------------------------------
ask as much as you want xD
I might be wrong, but I think you need to re-format your sd-ext partition, using the option in mounts and storage. It needs to be formatted to ext4, and I am sure that the recovery you have supports ext4 format.
Just a quick question, every time you boot the rom, do you have to go through the setup, language, wifi, time zone etc?
Robbie P said:
I might be wrong, but I think you need to re-format your sd-ext partition, using the option in mounts and storage. It needs to be formatted to ext4, and I am sure that the recovery you have supports ext4 format.
Just a quick question, every time you boot the rom, do you have to go through the setup, language, wifi, time zone etc?
Click to expand...
Click to collapse
yes i do... how did you know?
i thought it was because of the lack of internal storage...
so i need to re-format the sd-ext partition?
yoniaialon said:
yes i do... how did you know?
i thought it was because of the lack of internal storage...
so i need to re-format the sd-ext partition?
Click to expand...
Click to collapse
give it a go, can't hurt. Then reboot the rom and report back:fingers-crossed::fingers-crossed::fingers-crossed:
Robbie P said:
give it a go, can't hurt. Then reboot the rom and report back:fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Tytung is using the NativeSD data folder for DataOnExt (same as my script);
I'd say it's likely that whoever installed the ROM partitioned/changed the sdcard after installing thus removing this folder:
If the ROM has a terminal emulator app:
su
mkdir -p /NativeSD/NexusHD2-ICS/data
If not install a recovery with a terminal (Extended TWRP for example)
mount => sd-ext
advanced => terminal
mkdir -p /sd-ext/NexusHD2-ICS/data
Or you could use adb or reinstall the ROM.
Robbie P said:
give it a go, can't hurt. Then reboot the rom and report back:fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Didn't worked...
HypoTurtle said:
Tytung is using the NativeSD data folder for DataOnExt (same as my script);
I'd say it's likely that whoever installed the ROM partitioned/changed the sdcard after installing thus removing this folder:
If the ROM has a terminal emulator app:
su
mkdir -p /NativeSD/NexusHD2-ICS/data
If not install a recovery with a terminal (Extended TWRP for example)
mount => sd-ext
advanced => terminal
mkdir -p /sd-ext/NexusHD2-ICS/data
Or you could use adb or reinstall the ROM.
Click to expand...
Click to collapse
i dont know how to do those things.. if u could explain it step by step it would be great....:fingers-crossed:
rather than explaining, if I have time I will post a flashable zip with that code in it.:fingers-crossed:
Robbie P said:
rather than explaining, if I have time I will post a flashable zip with that code in it.:fingers-crossed:
Click to expand...
Click to collapse
so in the meanwhile.. how do i fix the phone?
yoniaialon said:
so in the meanwhile.. how do i fix the phone?
Click to expand...
Click to collapse
Sorry, forgot about this
I am working today, will try and post a flashable zip this evening.
Ok, put the attached zip onto your sdcard by either using a microsd card reader or using the usb cable and choose to copy files to/from your computer from the running rom.
Then go to magldr > ad recovery and install the test.zip from sdcard, you should get some text followed by update completed.
Restart the rom, set it up, reboot, profit?