Related
This is a custom recovery based on Cyanogen's recovery source with a lot of things added by me. The purpose of this recovery is to avoid using adb by accessing all features directly from the menu.
This recovery is for the HTC Tattoo only, if you have a :
- HTC Dream/G1 you should go here.
- HTC Magic/MT3G you should go here.
- HTC Hero you should go here.
- HTC Sprint Hero you should go here.
- HTC Nexus One you should go here.
- HTC Eris you should go here.
Use the DPAD (up+down) to navigate through the menu, press the DPAD to select items. Use the Volume-down key to go back to a previous menu.
Always check recovery.log before posting your issues!
Please make sure that your ROM supports apps2sd if you plan to use the ext-features! (/system/sd MUST be available in the ROM)
Ext4 is currently NOT supported (will add it as soon as I get an .29 Tattoo kernel compiled)
Features
full ADB access in recovery mode
Awesome Care-Bear version! (Blame packetlss for talking me into it )
Busybox v1.15.3
Kernel with ext3 support (NO Ext4 support)
HW-Key navigation (DPAD + Volume-key) option
Extended menu :
Reboot system now :: reboot your phone
USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
Backup/Restore
Nand backup :: Make a Nand backup, the following partitions are NOT included :
Recovery (to avoid restoring old version)
Cache (no need to backup imo)
Misc (no need to backup imo + restore issues on some phones)
Splash1+2 (no need to backup imo + restore issues on some phones)
Nand + ext backup :: Make a Nand + ext backup
Nand restore :: Restore a Nand backup
BART backup :: Make a BART backup (Nand + ext)
BART restore :: Restore latest BART backup
Flash zip from sdcard :: Flash a zip update file from your sdcard
Wipe
Wipe data/factory reset :: Wipe /data and /cache
Wipe Dalvik-cache :: Wipe Dalvik-cache both on /data and ext
Wipe SD:ext partition : Wipe the ext partition on your sdcard
Wipe battery stats : Wipe the battery stats in /data
Wipe rotate settings : Wipe the sensor settings in /data
Partition sdcard
Partition SD :: Interactive SD partitioning
Repair SD:ext :: Repair the ext partition
SD:ext2 to ext3 :: Convert ext2 to ext3
Other
Fix apk uid mismatches :: Does extacly that
Move apps+dalv to SD :: Moves all apps and Dalvik-cache to sdcard (This will NOT enable apps2sd!)
Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
Power off :: Powers off your phone
Scripts available via adb :
Nandroid v2.2.1 : enter "nandroid-mobile.sh" to start.
BART v1.0.1 (Backup and Restore Tool) : enter "utility" to start.
switchrom.sh V1.1 : enter "switchrom" or "u" to start.
sdparted v0.6 : enter "sdparted" to start.
Download
ALWAYS check the md5sum to make sure the zip isn't corrupted.
Click on the Mirror-link if you don't like rapidshare
Latest :
recovery-RA-tattoo-v1.6.2.img (Click here to download from a Mirror) - MD5Sum: 2d5de7a560ff6ae8db83042be87028cd
Special thanks to :
eyegor for testing and providing the needed info to make this recovery, Thanks!!
packetlss for all the hours of support and awesome coding skills, THANKS man ^^, donate to Haiti
Koushik Dutta for the unyaffs binary code fix and help ^^
Cyanogen for his dedicated work! , buy him a beer!
JesusFreke for his awesome JFv1.43's recovery , donate
pensive for adding awesome features to Nandroid
Bkmo for his utility script!
Devsk for his switchrom script!
51dusty for his sdparted script!
k4str0 for his fix_permissions v2.03 update.
Devsk, Dumfuq, Overground for creating BART
rikupw for the ideas and toggle_ums script.
http://www.androidspin.com for hosting ^^
Amon_RA said:
This is a custom recovery based on Cyanogen's recovery source with a lot of things added by me. The purpose of this recovery is to avoid using adb by accessing all features directly from the menu.
This recovery is for the HTC Tattoo only, if you have a :
- HTC Dream/G1 you should go here.
- HTC Magic/MT3G you should go here.
- HTC Hero you should go here.
- HTC Sprint Hero you should go here.
- HTC Nexus One you should go here.
- HTC Eris you should go here.
Use the DPAD (up+down) to navigate through the menu, press the DPAD to select items. Use the Volume-down key to go back to a previous menu.
Always check recovery.log before posting your issues!
Please make sure that your ROM supports apps2sd if you plan to use the ext-features! (/system/sd MUST be available in the ROM)
Ext4 is currently NOT supported (will add it as soon as I get an .29 Tattoo kernel compiled)
Features
full ADB access in recovery mode
Awesome Care-Bear version! (Blame packetlss for talking me into it )
Busybox v1.15.3
Kernel with ext3 support (NO Ext4 support)
HW-Key navigation (DPAD + Volume-key) option
Extended menu :
Reboot system now :: reboot your phone
USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
Backup/Restore
Nand backup :: Make a Nand backup, the following partitions are NOT included :
Recovery (to avoid restoring old version)
Cache (no need to backup imo)
Misc (no need to backup imo + restore issues on some phones)
Splash1+2 (no need to backup imo + restore issues on some phones)
Nand + ext backup :: Make a Nand + ext backup
Nand restore :: Restore a Nand backup
BART backup :: Make a BART backup (Nand + ext)
BART restore :: Restore latest BART backup
Flash zip from sdcard :: Flash a zip update file from your sdcard
Wipe
Wipe data/factory reset :: Wipe /data and /cache
Wipe Dalvik-cache :: Wipe Dalvik-cache both on /data and ext
Wipe SD:ext partition : Wipe the ext partition on your sdcard
Wipe battery stats : Wipe the battery stats in /data
Wipe rotate settings : Wipe the sensor settings in /data
Partition sdcard
Partition SD :: Interactive SD partitioning
Repair SD:ext :: Repair the ext partition
SD:ext2 to ext3 :: Convert ext2 to ext3
Other
Fix apk uid mismatches :: Does extacly that
Move apps+dalv to SD :: Moves all apps and Dalvik-cache to sdcard (This will NOT enable apps2sd!)
Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
Power off :: Powers off your phone
Scripts available via adb :
Nandroid v2.2.1 : enter "nandroid-mobile.sh" to start.
BART v1.0.1 (Backup and Restore Tool) : enter "utility" to start.
switchrom.sh V1.1 : enter "switchrom" or "u" to start.
sdparted v0.6 : enter "sdparted" to start.
Download
ALWAYS check the md5sum to make sure the zip isn't corrupted.
Click on the Mirror-link if you don't like rapidshare
Latest :
recovery-RA-tattoo-v1.6.2.img (Click here to download from a Mirror) - MD5Sum: 2d5de7a560ff6ae8db83042be87028cd
Special thanks to :
packetlss for all the hours of support and awesome coding skills, THANKS man ^^, donate to Haiti
Koushik Dutta for the unyaffs binary code fix and help ^^
Cyanogen for his dedicated work! , buy him a beer!
JesusFreke for his awesome JFv1.43's recovery , donate
pensive for adding awesome features to Nandroid
Bkmo for his utility script!
Devsk for his switchrom script!
51dusty for his sdparted script!
k4str0 for his fix_permissions v2.03 update.
Devsk, Dumfuq, Overground for creating BART
rikupw for the ideas and toggle_ums script.
http://www.androidspin.com for hosting ^^
Click to expand...
Click to collapse
Amon, thank you for this. i use your roms on my magic and was hoping you will develop for the tattoo sometime soon
thanks
Thank You Amon_RA
Thanks. It works great.
But I did get this message while flasshing:
Code:
# /data/local/bin/flash_image recovery /sdcard/recovery.img
/data/local/bin/flash_image recovery /sdcard/recovery.img
mtd: read error at 0x00000000 (Cannot allocate memory)
mtd: read error at 0x00020000 (Cannot allocate memory)
mtd: read error at 0x00040000 (Cannot allocate memory)
mtd: read error at 0x00060000 (Cannot allocate memory)
flashing recovery from /sdcard/recovery.img
#
Big thanks!!!
As always, you are the best.
Thanks again for your hard work.
Thanks...you are the man
Thank you very very much!!
Nice work!
It works like a charm...Amon-RA...take care of us please
respect.. it works
thank you Amon_Ra
Marsdroid
Thanks Man.
Nice Work.
Amon_RA! I thought I'd never see you in the Tattoo Development Community!
All we need now is a CyanogenMOD port...
Will download and flash that recovery in a sec.
EDIT: Flashed and currently playing around in it. Nice HTC Logo!
all done it works fine!!!
just a question: I've done a nandroid backup with the previous recovery by maverix and now I did another one with this new recovery...did the last overwrite the first? or do I need to remove the first someway? thank you
okok I found the nandroid directory into the sd and removed the previous backup ordering them by date
Nandroid backup+ext in adb mode only?
Coburn64 said:
Amon_RA! I thought I'd never see you in the Tattoo Development Community!
All we need now is a CyanogenMOD port...
Will download and flash that recovery in a sec.
EDIT: Flashed and currently playing around in it. Nice HTC Logo!
Click to expand...
Click to collapse
Well, you can thank me for that!
I thought that we needed a proper recovery for our beloved tattoo, and decided to contact the recovery master - Amon_RA.. To my surprise he was very eager to help, and without hesitation jumped to making a recovery!
I gave him all the info he asked for, tested a few versions and finally he made a version that you can use now
I hope you guys like it!
Thank you Amon_RA!
Thank you eyegor too
Maybe a custom 2.1 rom is not too far
Well, if Amon_RA was so helpful, maybe other devs would be too, and we just need to ask them...
You're welcome HTCDevil
cheers
Amon_RA
thanks loads, when i posted that mock up screenshot on twitter and you said 'shouldnt be too difficult' i thought that would be it..
but here we are and its done, what a result .. thanks indeed.. ( now what about version 1.7 for the g1 like myself and manup encouraged? . lol lol...)
..
i love you
what's partitioning for ?
with latest roms we don't need it to have roms on sdcard
OK, I'm going to stop polluting other threads with my stuff.
This should help make sure I can keep up on the discussions and provide support for people trying to use my ZIPs and/or scripts.
NOTE: This version requires JACs kernel and init.d mods. Flash his stuff, then flash mine. All this will be integrated at some point and any other dev is welcome to integrate my stuff with theirs.
In addition to the JAC kernel, you need an ext partition on the EXTERNAL SD card. DO NOT USE ROM MANAGER TO PARTITION. You will get into a boot loop and will have to Odin back to stock. For partitioning, you may use "adb shell" in clockwork recovery, an old G1/Mytouch with Amon-Ra/Clockwork, a computer with a card reader and GPartd, Paragon, etc.. If you do it with fdisk, don't forget to format the partitions, here are some sample commands.
This will format an ext2 partition.
Code:
/system/bin/mke2fs /dev/block/mmcblk1p2
Convert from ext2 to ext3
Code:
/system/bin/tune2fs -j /dev/block/mmcblk1p2
Convert ext3 to ext4
Code:
/system/bin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk1p2
fsck, any ext version. Do this when you are done converting between types.
Code:
/system/bin/e2fsck -fpDC0 /dev/block/mmcblk1p2
For all of the above, make sure the partition isn't mounted with "mount". You also have to have already flashed either this ZIP, or my e2fsprogs-ext4 ZIP for the files to be installed in /system/bin.
This version will clean up older versions that I know about. It will remove any use of the playlogos hack, and the older version of my script that JAC included in his kernel.
Quadrant - 1722. I have also not seen any lag from this change. I've tried some apps that make heavy use of the database, and so far it's performing quite well. If you do see problems, I suggest fsck on the ext partition, and perhaps formatting it, to ensure it's nice and clean.
Please note that benchmark results will vary based on a large number of factors beyond my control. Try with a clean phone, no background apps. A faster SD card will help as well. I am using an older Transcend 8GB Class 6 that I used to use on my G1. It doesn't help that the free Quadrant tests lots of stuff, not just activity on /data/data and such.
To see if it's working, open a shell and type "mount". You should see entries like this:
Code:
/dev/block/mmcblk1p2 on /sd-ext type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk1p2 on /data/dalvik-cache type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk1p2 on /data/data type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
Added data-only ZIP and the disable/revert ZIP.
Added auto-partition ZIP to create 1GB ext3 partition automatically. Note that this will delete ALL SD contents.
Added old-style enable-dc2sd for users of the auto-partition script. Do not use for JAC kernels, use the current dc2sd instead.
Changelog:
8/9/2010: Added loopback style version, should find prior versions and remove them, copying your data from the /sd-ext partition.
v2.
Compatibility fix for JAC -6 kernel.
v1.
Added e2fsprogs w/ext4 support to the ZIP
Better integration with init.d layout
On boot fsck to ensure that the ext partition is kept clean
Automatically copy files if /data has larger directories than /sd-ext
Test versions that should fix busybox to work with the newer JAC kernels. -loop uses the loopback filesystem method (RyanZA style). The other one is for an ext partition on the external SD card.
Feel free to post direct links or links to the kernel thread.
For some reason, the convetr to ext4 command isnt working for me.
Just says "Tune2fs 1.41.6" then back at # prompt
GREAT RESOURCE - Deserves a sticky just for the conversion syntax
EDIT: Maybe not, it said mounted as an ext3 before, now it says ext4
EDIT2: SUCCESS!!!!! EXT4 gives a major boost to the Quadrant score - 1531. WAY better than the~1100 i was getting before. Stupid G1 didnt actually convert ext3 to ext4, even though it said it did. Thanks!
Not that I'm stressin over Quadrant scores, but I just dropped ~100 (previous was 1497) after flashing this. Ah well.
Hmmm, before applying this script, I was just using JAC's v5 kernel, which worked fine, but after applying the OP's script, I cant backup in Clockwork (again lol).
It doesnt seem to mount /data and /datadata, as it only backs up /system and errors out on the other two. Any idea why?
EDIT: The error is really random, Ive now had 2 successful backups, 2-3 that failed due to mount issues, and 2-3 that failed due to MD5 issues. I would like to narrow down the possibilities, and I attempted a restore to stock, rooted, and then used JAC's kernel, same issue occurs (did not use your newest script). That being said, I dont think its your script. (stumped)
When converting to ext4 it said "please run e2fsck on the filesystem"
EDIT: Ran "mount" and it shows same messages you do. So it worked
LovellKid said:
When converting to ext4 it said "please run e2fsck on the filesystem"
EDIT: Ran "mount" and it shows same messages you do. So it worked
Click to expand...
Click to collapse
It's supposed to say that. Do it.
Glad it's working for some of you. As for nandroid, no idea. I'll install jac latest and check it out. Can't think of much I could have done to it though, I can't mod the ramdisk this way.
+1 on the nandroid, I went back and tried and couldnt. Also, tried to flash anamolous deodexed ROM and wouldnt. Gave errors e: cant mount /dev/block etc and failed. Could this be related?
LovellKid said:
+1 on the nandroid, I went back and tried and couldnt. Also, tried to flash anamolous deodexed ROM and wouldnt. Gave errors e: cant mount /dev/block etc and failed. Could this be related?
Click to expand...
Click to collapse
I doubt it, my stuff doesn't run in recovery, at least I don't think it will. I've never seen it run. I'll look into it, but it sounds like the jac mod might have an issue with nandroid right now.
There was a similar issue on the g1 with cm6. I wonder if that fix will work here...
Could you also post the Just DATA, and revert scripts in this thread please
Also, what would be the proper flashing order for just data?
1. JAC init.d
2. reverse
3. Just data
Or do I have to flash init.d, apply kernel, then reboot and flash reverse then just data?
The_Chrome_Coyote said:
Could you also post the Just DATA, and revert scripts in this thread please
Also, what would be the proper flashing order for just data?
1. JAC init.d
2. reverse
3. Just data
Or do I have to flash init.d, apply kernel, then reboot and flash reverse then just data?
Click to expand...
Click to collapse
Added revert and data-only to the OP.
If you don't have any sd-ext hack installed right now:
1. JAC init.d
2. data-only ZIP
3. reboot to download mode and flash the JAC kernel
If you already have dc2sd installed:
1. Revert ZIP
2. JAC init.d ZIP
3. Data-only ZIP
4. reboot to download mode and flash the JAC kernel
If you already have the kernel and the JAC init.d:
1. Revert ZIP
2. Data-only ZIP
I am trying to revert this fix, so I can try the new hack involving a virtual EXT2 partition. I tried the revert, and I manually deleted the a2sd and dc2sd files in init.d, but it rebuilds data when I reboot. ANy ideas?
zimphishmonger said:
I am trying to revert this fix, so I can try the new hack involving a virtual EXT2 partition. I tried the revert, and I manually deleted the a2sd and dc2sd files in init.d, but it rebuilds data when I reboot. ANy ideas?
Click to expand...
Click to collapse
You likely have a script in /system/etc/init.d doing it, or you didn't clean the old playlogos stuff up.
FWIW, I'm working on a similar way of doing it, but with ext4 and a proper init script. I don't like using ext2 for this stuff, too easy to corrupt it.
Does your new loop script require an sdcard with ext 4 partition or does it use the internal sd card?
ttabbal said:
You likely have a script in /system/etc/init.d doing it, or you didn't clean the old playlogos stuff up.
FWIW, I'm working on a similar way of doing it, but with ext4 and a proper init script. I don't like using ext2 for this stuff, too easy to corrupt it.
Click to expand...
Click to collapse
Thanks for your work! I found your dc2-loop-v1 script. Will play w/ that until you come out w/ something better. Is EXT2 really that fragile in terms of corruption when it is virtualized within a journaled file system (which I believe RFS is)
frank707 said:
Does your new loop script require an sdcard with ext 4 partition or does it use the internal sd card?
Click to expand...
Click to collapse
This loop version doesn't use an ext partition. Just the loopback mount. It will copy the files from an ext partition if you have applied that hack.
zimphishmonger said:
Thanks for your work! I found your dc2-loop-v1 script. Will play w/ that until you come out w/ something better. Is EXT2 really that fragile in terms of corruption when it is virtualized within a journaled file system (which I believe RFS is)
Click to expand...
Click to collapse
Most file system journals don't help with the data just the structure. Rfs rides on vfat, so I doubt it's worth much that way.
Gave the dc2-loop script a shot, to convert from the /SD-EXT method to this new ext4 container method. It creates the container correctly, but never seems to copy everything over. All my apps act as if i've never started them up, so Data isnt getting copied over correctly.
EDIT: Tried again, the dc2-loop script def doesnt work, and I have no idea why. It looks perfect (code-wise), but for whatever reason doesnt end up working properly
can't get your loop script working. every other one i have been able to run flawlessly. i just flashed the oc kernel by jac. any further instructions or pre reqs?
This is a modified CWM-based recovery for the Motorola Atrix 4G. It is based on my own custom code forked from the CyanogenMod team's recovery. The major changes I have made include full support for dual SD cards, support for webtop partitions (SD card and internal) and changes to Nandroid backup/restore for this phone's additional partitions.
Some highlights include:
Dual SD card support
ADB support
USB Mass Storage support
Nandroid additions/changes
ext3/4 formatting
Unified kernel for international users
Probably others
This recovery is only for UNLOCKED devices. It is intended to be flashed directly to the recovery partition. Additionally, I have an AT&T phone so that is the kernel I am using. I doubt the memory issue would matter in recovery mode but testing from UNLOCKED international users would be appreciated. UPDATE: Initial indications are it works fine on UNLOCKED international phones. Versions for different tegraparts have also been compiled. UPDATE 2: Unified kernel patch has been applied. Choose whatever color you prefer regardless of phone version!
UNLOCKED users can flash this recovery using:
Code:
moto-fastboot devices
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-atrix5.img
Example from my phone:
Code:
$ moto-fastboot devices
TA20700KXH fastboot
$ moto-fastboot erase recovery
erasing 'recovery'... OKAY [ 0.741s]
$ moto-fastboot flash recovery recovery.img
sending 'recovery' (4780 KB)... OKAY [ 0.490s]
writing 'recovery'... OKAY [ 0.544s]
This is posted in a DEVELOPER forum and is being released to help further the development of Android for the Motorola Atrix 4G. I have personally tested this on my phone but YOU assume full responsibility for any damage incurred to YOUR phone!
Click to expand...
Click to collapse
ALL USERS
Orange 5.0.2.7-atrix5 / ZIP version.
MD5 aebe29124d8c6d6c4b9873bd9ea4ca3b / 1f9a1d6fc83610e5c7c8f2d60e489b69
Cyan 5.0.2.7-atrix5 / ZIP version.
MD5 eb44b910983434d3996383098dff53b6 / 91365993488a9ae060b22c8b820d1c5b
Light green 5.0.2.7-atrix5 / ZIP version.
MD5 e7c7ec152e9e3269ef2ab1ce99b8943e / 1e720c8760898549226a10d4776f5077
Dark green 5.0.2.7-atrix5 / ZIP version.
MD5 c8a4438e5889d5e681a754555c40bc51 / 121d8d9102eac3ed24f1e0be6f8cd5d1
Blue 5.0.2.7-atrix5 / ZIP version.
MD5 9a1fd3c8796d2e768b54d39143c17ea3 / 9059c0c37fd2c547ec8508c893986815
Red 5.0.2.7-atrix5 / ZIP version.
MD5 036a9d9cc390a6071011d4d50b008875 / aa069d1aed20c5cbd13b2098b6a88975
Original ROM Manager installable zip thanks to SolidHelix. You must still be UNLOCKED to use them.
Source is here.
A few notes:
The capacitive buttons can be used to navigate as well. Back is back, search is select. Menu and home are up and down.
The "osh" partition is webtop. It is the largest by far and will take some time to backup. Nandroid is not frozen!
The "sd-ext" partition is an ext3/4 partition on your external SD card. Veterans will know this as apps2sd and data2sd from other phones. The only use I'm aware of on our phone currently is Sogarth's webtop2sd.
Thanks to:
Koush and the CM team for CWM
Everyone who has made unlocking the Atrix possible
** Changelog **
2011-11-14 (5.0.2.7-atrix5):
Minor bugfix release mostly
Added the ability to convert an ext3 partition to ext4 under advanced. Shouldn't break anything, but it is experimental.
2011-09-24 (5.0.2.3-atrix4.1):
Fix an issue with using ext4 formatting on stock ROMs
2011-09-23 (5.0.2.3-atrix4):
Updated to CWR5 base source.
The blue version is now the new CWR5 color. Old blue is gone. New photos welcome!
2011-09-17 (4.0.1.5-atrix3.3):
Unified kernel patch from eval-
New kernel to fix the stuck at "Entering Android Recovery" prompt. Big thanks to bamastang for helping test this.
Added a verify option to the backup and restore menu.
Renamed internal SD card mount point to /emmc and external is now /sdcard (this is largely cosmetic).
Merged in the CM7 device config when building the recovery image (again, just cosmetic).
Merged in miscellaneous fixes from the official CWM. Version 5 will be merged in once its ready.
2011-08-17 (4.0.1.5-atrix3.2):
Added 0MB option to ext3 partition size under External SD card partitioning which removes any ext3 partitions from the card (choose 0MB ext3/0MB swap to have only a FAT32 partition).
Added a red build to the mix.
Updated the update-binary in the CWM zips to be tailored for this phone.
Minor fixes to sdparted (log file related mostly).
2011-08-14 (4.0.1.4-atrix3.1):
Swap kernels to re-enable soft keys. Ext4 support should still work.
Fix for external SD card partitioning (internal is not supported).
CWM zip changed slightly.
2011-08-12 (4.0.1.4-atrix3):
Experimental ext4 support. Thanks to SolidHelix for testing it.
Fix for restoring large yaffs2 images (greater than 10,000 objects).
Tweak to the SD card space check before starting Nandroid backup.
Miscellaneous minor bugfixes and tweaks.
2011-08-07 (4.0.1.4-atrix2):
User is now prompted to wipe sd-ext (webtop2sd) on "Wipe data/factory reset".
User is now prompted to backup or restore webtop (/osh and /sd-ext) during Nandroid.
Four alternate colors created.
Versions for different tegraparts (international phones) created.
2011-08-05 (4.0.1.4-atrix1):
Initial release
Screenshots
Thanks to DarkSim2o9 for the following screenshots:
Orange
Cyan
Blue
Light green
Dark green
Red
Known Issues
sd-ext (webtop2sd) is inadvertently wiped on "Wipe data/factory reset". Next version will make this optional. Fixed in -atrix2.
Miscellaneous
If you'd like ROM Manager to see this recovery as "official" you can try XCellPhoneSalesRep's suggestion posted here.
Alternately, you can try dcarpenter85's suggestion here.
For issues with recovery not sticking or crashing, see here:
Thanks to mrinehart93 for pointing this out.
The system runs /system/etc/install-recovery.sh on boot with the stock rom. On boot it checks the recovery partition for some update and with CWM installed decides to reflash the stock recovery over it. Rename or delete the file and the CWM should stick.
Click to expand...
Click to collapse
Old versions
You can browse and download old versions here.
If I currently have tenfar's latest recovery, is it worth installing this one?
xploited said:
If I currently have tenfar's latest recovery, is it worth installing this one?
Click to expand...
Click to collapse
yes..Nandroid support
ok.. for some reason I can not enter recovery with Tenfar's or this CWM... I can enter it when plugged into AC using the Root Manager CWM.. Any ideas? I always get stuck at the "Entering Android Recovery Mode" screen and that is it... Any help would be greatly appreciated.
bamastang said:
ok.. for some reason I can not enter recovery with Tenfar's or this CWM... I can enter it when plugged into AC using the Root Manager CWM.. Any ideas? I always get stuck at the "Entering Android Recovery Mode" screen and that is it... Any help would be greatly appreciated.
Click to expand...
Click to collapse
were you using Tenfar's old version.
I had at one-point tried using the old version... after trying to flash the new version and having the problem. I flashed the new version I believe right after unlocking (first time flashing the CWM) It had never worked on my phone unless I used the ROM Manager version. I was hoping this would take care of the issue since I did the erase recovery and flashed this...
munchy_cool said:
yes..Nandroid support
Click to expand...
Click to collapse
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App
bamastang said:
I had at one-point tried using the old version... after trying to flash the new version and having the problem. I flashed the new version I believe right after unlocking (first time flashing the CWM) It had never worked on my phone unless I used the ROM Manager version. I was hoping this would take care of the issue since I did the erase recovery and flashed this...
Click to expand...
Click to collapse
Hmm not sure I've experienced that. Do you have install-recovery.sh in /system/etc? Maybe it's conflicting
Javi97100 said:
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Very interested in this as well. The big problem (only problem iirc) with Tenfar's is its inability to properly backup and restore the PDS partition.
If this release gives us all of the features of the official CWM, I will be ecstatic!!!
DK
Javi97100 said:
So, backup and restore is COMPLETELY working on this recovery?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
It should be from my tests, but you should also test it.
romracer said:
It should be from my tests, but you should also test it.
Click to expand...
Click to collapse
I have several backups of my PDS partition. I am very busy tonight, but was planning on spending tomorrow re-building my laptop. So while I'm doing that I'll do a backup, wipe, and restore to see what happens and report back.
DK
DeathKoil said:
Very interested in this as well. The big problem (only problem iirc) with Tenfar's is its inability to properly backup and restore the PDS partition.
If this release gives us all of the features of the official CWM, I will be ecstatic!!!
DK
Click to expand...
Click to collapse
PDS is definitely backed up. It's not restored by default, just as a wimax partition is not on those devices that have them. It is available under Advanced Restore but you should help test it and have a separate backup just in case.
Backup early and backup often.
romracer said:
Hmm not sure I've experienced that. Do you have install-recovery.sh in /system/etc? Maybe it's conflicting
Click to expand...
Click to collapse
The only install-recovery.sh I had was in the /etc not in the /system/etc
I don't know if there is something missing that CWM is dependant on or what. But like I said if I use the one from ROM manager which is 4.0.1.4 I can boot into recover with the plugged in via AC.
Bug during backup?
So I am starting my backup of my phone using this recovery.
I booted into recovery, chose "Backup and Restore", then chose "Backup", and finally told it to makeup to the external card.
Here is my output:
CWM-based Recovery v4.0.1.4-atrix1
SD Card Space free: 4331MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
Backing up .android-secure...
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Backing up osh...
Backing up pds...
Generating md5 sum...
Backup complete!
It seems somewhere in the backup code it tries to backup the contents of the SD-Card (external), but the mount point is referenced as "sd-ext" instead of "sdcard-ext".
This isn't a big deal for me at all, as I only have videos and music on the external card - both of which I have copies of on my PC. For some people, they may want to be able to backup the external card as well.
Edit: In the advanced restore options there is also an option to restore the external sdcard, but it is against referenced as the mount point "sd-ext" instead of sdcard-ext".
Like I said, I'll wipe the phone clean tomorrow and test restore it then make a new post with the results.
So far so good!!
DK
bamastang said:
The only install-recovery.sh I had was in the /etc not in the /system/etc
I don't know if there is something missing that CWM is dependant on or what. But like I said if I use the one from ROM manager which is 4.0.1.4 I can boot into recover with the plugged in via AC.
Click to expand...
Click to collapse
Boot regularly and then in Settings enable USB Debugging. From a command prompt, "adb devices" should show your phone. From there, "adb reboot recovery" and wait 10-20 seconds.
Does that get you into recovery? Does the "Motorola Dual Core" boot image change at all when you try to boot into recovery? Like to a little Android guy with a yellow hazard sign?
The "plugged into AC" recovery is just a hijack of the normal system, so if your phone boots normally I'm not surprised that method works.
DeathKoil said:
So I am starting my backup of my phone using this recovery.
I booted into recovery, chose "Backup and Restore", then chose "Backup", and finally told it to makeup to the external card.
Here is my output:
CWM-based Recovery v4.0.1.4-atrix1
SD Card Space free: 4331MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
Backing up .android-secure...
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Backing up osh...
Backing up pds...
Generating md5 sum...
Backup complete!
It seems somewhere in the backup code it tries to backup the contents of the SD-Card (external), but the mount point is referenced as "sd-ext" instead of "sdcard-ext".
This isn't a big deal for me at all, as I only have videos and music on the external card - both of which I have copies of on my PC. For some people, they may want to be able to backup the external card as well.
DK
Click to expand...
Click to collapse
"sd-ext" refers to an ext3 partition on the external SD card. On other phones, this is used for crap like "data2sd" and "apps2sd". On our phones, the only current use I've seen of this is for Sogarth's webtop2sd.
Standard CWM does not backup SD card contents (it backs up to them) so there is no support for that in mine. I could consider adding it eventually.
You will see references to "sdcard-ext" in my recovery if you do something like Apply update.zip and then choose External SD card (look at the path it shows you for update.zip on the confirm screen).
I used to get issues to wipe data in the original 4.0.1.4
Is data wipie fixed in this custom recovery?
guidoido004 said:
I used to get issues to wipe data in the original 4.0.1.4
Is data wipie fixed in this custom recovery?
Click to expand...
Click to collapse
Yes. I have personally tested this particular item a few times. mke2fs from Koush's CWM segfaults, but I have supplied a working one.
Will you be including international support?
[MOD][RECOVERY] All-F2FS for GT-I9190|GT-I9192|GT-I9195 [TWRP 2.8.6.0 & Philz Touch]
Hi!
Here I'll try to explain how to use F2FS partitions on your Galaxy S4 Mini.
This is for "All-F2FS" that mean that /system, /cache, /data and /external SD are formatted with F2FS, keep in mind that this can work only with a compatible kernel and ROM.
About F2FS
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk (Hangul: 김재극) 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.
Samsung chose a log-structured file system approach, which it adapted to newer forms of storage. F2FS also remedies some known issues of the older log structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. Because a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), Samsung also added various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms.
Warning
* You agree to use this MOD/Guide on you own risk and I don't take any responsability if you encounter any issue or if your personal data is lost
Requirements
Your S4 Mini, GT-I9190 or GT-I9195 or GT-I9192 (serrano3g, serranolte, serranods)
An external MicroSD card or a PC (for backup/restore)
Preinstalling Steps
Backup of your personal data to an external SD card or PC (photo, music, ringtones, etc).
Make a full nandroid (just in case that you want to rollback to EXT4) and copy to your PC.
Download and copy to your External SD Card TWRP or Philz Touch with full F2FS support. (Downloads on Second Post)
Download and copy to your External SD Card latest version of f4ktion kernel or use one with All-F2FS support.
Download and copy to your External SD Card CarbonROM with F2FS support, or you can test on your favorite ROM, take in mind that using F2FS on External SD Cards will require F2FS support on your ROM of minivold for vold managed volumes. (Downloads on Second Post)
How can you test your favorite ROM?
I'll include this time CarbonROM with support for F2FS, on upcoming builds you'll need to edit manually the updater-script.
You need to edit updater-script on the zip file, you need to change the following:
Look for:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
And change it for:
Code:
run_program("/sbin/busybox", "mount", "/system");
Look for:
Code:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
And change it for:
Code:
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/system");
Installation Steps (Clean Install)
1) Install your favorite recovery and reboot to recovery.
For TWRP
1.1) Go to Settings and select "Force data and cache wipe functions to use F2FS" and if you want F2FS support on /System partition, select "Include system partition"
1.2) Now go to Wipe menu and select Format Data and type "yes" (Warning this will format Data partition and your Internal Storage, so please don't forget to make a backup of your personal data)
1.3) Optional, select Advanced Wipe menu and check System and Cache partitions to convert to F2FS respectively.
For Philz Touch
1.1) Go to Mounts and Storage and select "toggle f2fs <-> ext4 migration"
1.2) Select format /data and confirm, now select format /data and /data/media (/sd, confirm, choose f2fs option and confirm again.
1.3) Optional, you can select format /system and format /cache to convert to F2FS respectively.
2) Install your ROM as usual, then flash your GApps and f4ktion kernel in this order.
3) Restore your personal data to your internal SD Card.
If you don't want to make a clean install, you can convert /data partition to F2FS using and restoring a /data nandroid backup.
Installation Steps (Restoring /Data partition)
1) Install your favorite recovery and reboot to recovery.
For TWRP
1.1) Make a nandroid of /data partition.
1.2) Go to Settings and select "Force data and cache wipe functions to use F2FS" and if you want F2FS support on /System partition, select "Include system partition"
1.3) Now go to Wipe menu and select Advanced Wipe menu and check Data, swipe to confirm wipe.
1.4) You can restore your /data nandroid now.
1.5) Optional, you can select format /system and format /cache to convert to F2FS respectively and install a new ROM.
For Philz Touch
1.1) Make a custom nandroid of /data partition.
1.2) Go to Mounts and Storage and select "toggle f2fs <-> ext4 migration"
1.3) Select format /data and confirm, now select format /data and /data/media (/sd, confirm, choose f2fs option and confirm again.
1.4) You can restore your /data nandroid now.
1.5) Optional, you can select format /system and format /cache to convert to F2FS respectively and install a new ROM.
How to check if you have correctly formatted partitions to F2FS?
Through terminal do:
Code:
su
mount | grep f2fs
Through adb do:
Code:
adb shell
su
mount | grep f2fs
Also you can check F2FS's status by doing:
Code:
cat /sys/kernel/debug/f2fs/status
Or just install DiskInfo app
Credits
@Dees_Troy for TWRP
@ktoonsez for F2FS mod
@Phil3759 for Philz Touch
TWRP 2.8.1.0 F2FS MOD
GT-I9190
GT-I9192
GT-I9195
Philz Touch F2FS
GT-I9190
GT-I9192
GT-I9195
F4k said:
Look for:
Code:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
And change it for:
Code:
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
Do I need to do this part if I want to keep my system partition as Ext4 but wanted my data and cache partition as F2fs?
Thanks in advance
Envoyé de mon unknown en utilisant Tapatalk
Darktitor said:
Do I need to do this part if I want to keep my system partition as Ext4 but wanted my data and cache partition as F2fs?
Thanks in advance
Envoyé de mon unknown en utilisant Tapatalk
Click to expand...
Click to collapse
This step is if you want /system partition as f2fs, you can use f2fs on whatever you want.
If you don't edit updater-script, your /system partition will be formatted as ext4
Just a quick question, is this Carbon in this post the same as the latest build you have just released? Or is this one with an altered updater-script?
Phenom2122 said:
Just a quick question, is this Carbon in this post the same as the latest build you have just released? Or is this one with an altered updater-script?
Click to expand...
Click to collapse
It's the same but with modified updater-script, this version will format /system partition as f2fs, the one on Carbon's thread as ext4.
All formatted f2fs and everything flashed and running smoothly thanks f4k
Sent from my GT-I9195 using XDA Premium 4 mobile app
From now on we should unzip the rom file and change tha script to have f2fs?
Hope random reboots to stop..
Everything fine with clean install.. One bug tha colors in recent calls with tha black theme
Στάλθηκε από το GT-I9195 μου χρησιμοποιώντας Tapatalk
@F4k nice splash screen you have in your twrp recovery, also glad you added the "force wipe to use f2fs option " this way I can use the twrp themes without the need for additional changes to it.
Sent from my GT-I9195 using Tapatalk
Since doing a format of /data and /data/media Philz works correctly the first time with settings in mnt/shell/emulated/0/clockworkmod. After doing a reboot into recovery later, suddenly it has created a mnt/shell/emulated/0/0/clockworkmod and it seems to be randomly reading settings from either location ie. sometimes it will correctly launch Aroma, sometimes it wont. This is a very strange error because I went back to one of the older Philz versions and the same problem persists.
Will try out TWRP now.
can I format /system with f2fs and then just make a restore? or I have to install a new rom?
chacox said:
can I format /system with f2fs and then just make a restore? or I have to install a new rom?
Click to expand...
Click to collapse
You can try it, I tested several combinations restoring nandroid backups and they worked fine.
But I suggest you to made a full nandroid just un case.
Sent from my GT-I9190
F4k said:
You can try it, I tested several combinations restoring nandroid backups and they worked fine.
But I suggest you to made a full nandroid just un case.
Sent from my GT-I9190
Click to expand...
Click to collapse
ok, I will try right now! and Ill let you know if it works in that way, thanks for your great job!
update: yeah it worked in that way! I have f2fs in every partition! thanks
Does FSFS support symlinks?
If so, how to access FSFS formatted sdcards on /storage/sdcardX directly w/o fuse layer on top?
aguaz said:
Does FSFS support symlinks?
If so, how to access FSFS formatted sdcards on /storage/sdcardX directly w/o fuse layer on top?
Click to expand...
Click to collapse
To use F2FS on external sd cards, ROM needs to have F2FS support on minivold for vold managed volumes, my CarbonROM builds support it.
External storages are vold managed volumes, this is my external sd card formatted as F2FS:
Code:
/dev/block/vold/179:33 on /mnt/media_rw/sdcard1 type f2fs (rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,background_gc=off,user_xattr,inline_xattr,acl,active_logs=2
F4k said:
External storages are vold managed volumes, this is my external sd card formatted as F2FS:
Code:
/dev/block/vold/179:33 on /mnt/media_rw/sdcard1 type f2fs (rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,background_gc=off,user_xattr,inline_xattr,acl,active_logs=2
Click to expand...
Click to collapse
My understanding is that the mount point on /mnt/media_rw/sdcard1 is for internal use only. Apps however use the additional mount point on /storage/scdard1 . This mount point has a fuse layer on top, which prevents the use of symlinks on eg ext4 formatted cards. (see here: http://forum.xda-developers.com/showthread.php?t=1442729)
So I'm wondering if F2FS can be accessed by apps natively w/o fuse layer in order to use symlinks. That is of course assuming F2FS supports symlinks itself.
Recovery doesn't seem to support encrypted partitions properly (acts like they don't exist), also some weird input glitches... Doing more testing...
After using TWRP for a while I decided to go back to Philz, this time without reformatting or restoring any old settings. Everything is working perfectly now, something crazy must have happened with my old settings, I suspect with 'Sd Card Target'.
Thank you very much for this F4k. Besides the addition of F2fs support, previously the latest version available to us was 6.41.6, very nice to have such an up to date version now I seriously would donate if I had the means to, and as soon as I actually have some money in my bank account for a change I definitely will be doing so
dulemars said:
Recovery doesn't seem to support encrypted partitions properly (acts like they don't exist), also some weird input glitches... Doing more testing...
Click to expand...
Click to collapse
I don't added crypto support yet to TWRP
i've a problem with system partition.
i use twrp recovery. i've do a clean install format data, i've cheked in Advanced Wipe System and Cache partitions to convert to F2FS, wiped system and cache, i've install last cyanogen nightly and... in diskinfo data is f2fs, cache is f2fs but system is ext4.... why? what's wrong?
thanks
TWRP 3.0.1-0 with "All-F2FS" support
I have modified the standard TWRP recovery to work with F2FS partitions.
This is different from the previous recoveries that i published.
This is for "All-F2FS" that mean that /system, /cache and /data are formatted with F2FS.
Keep in mind that this can work only with a compatible kernel.
What is F2FS?
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.
Download:
Zeus-Kernel.zip (CM12.1) - Here
Zeus-Kernel-MM.zip ( MM ) - Here
recovery-sprout-F2FS-All.img - Here
TWRP 3.0.1-0 Latest - Here
Changelogs:
-29/10/15: Initial Release
-02/04/15 : TWRP 3.0.1-0 Release
To switch your /system, /cache and /data partitions to F2FS follow instructions:
You need:
-Two files you can download above.
-A Android One (Sprout4) device obviously.
-Patience and Time.
Steps:
Flash this recovery with Fastboot (Maybe Flashify, Your wish)
Reboot in new recovery
Backup your /system , /data
(a) Go to Wipe, then Advanced Wipe, Select /System.
(b) Click on "Repair or Change File System"
(c) Click on "Change File System" option
(d) Select F2FS then Swipe to Change.
Repeat steps (a) to (d) with /data and /cache as you did with /system.
Now come back to main screen and go to "Settings"
Select "Use rm -rf instead of formatting."
Go to Restore menu and restore your previously backed up data.
Now Flash the Kernel zip provided above.
Reboot.
Done.
It's easier than it seems.
To restore partitions to stock:
Backup /system and /data
Change File System to EXT4.
Go to Restore menu and restore /system and /data again.
XDA:DevDB Information
[RECOVERY][All-F2FS] TWRP 3.0.1-0 with All-F2FS support, Tool/Utility for the OEM Cross Device Development
Contributors
Swapnil Solanki
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.0.1-0
Stable Release Date: 2016-04-02
Created 2015-10-30
Last Updated 2016-04-02
Reserved
Reserved
Yay......
It's here..
Thanks sir...
Thanks I got it resolved..
In the Meantime I'll keep mashing Thanks button...
Could you make a flashable zip for the recovery? Thanks!
vjtigas said:
Could you make a flashable zip for the recovery? Thanks!
Click to expand...
Click to collapse
Sure I'll make it soon.
Keep mashing thanks button
Regards.
so this change our system ext4 to f2fs?
my question
if i flash stock or custom rom (Kk,L,M) still on f2fs or back to ext4?
f2fs have great performance i think..
edit : i used sprout8,does it wipe my data/media storage?
Minions_Army said:
so this change our system ext4 to f2fs?
my question
if i flash stock or custom rom (Kk,L,M) still on f2fs or back to ext4?
f2fs have great performance i think..
edit : i used sprout8,does it wipe my data/media storage?
Click to expand...
Click to collapse
This doesn't change it. It just gives support for it.
No. (Misunderstood your question.)
He said it's for sprout4, but I think it don't wipe that.
vjtigas said:
This doesn't change it. It just gives support for it.
I don't think so.
He said it's or sprout4, but I think don't it wipes that.
Click to expand...
Click to collapse
wait for Op explain this
:cheers
hi i am using my sd card as adapted internal storage on android m. will this recovery detect any zip placed on this card? if no how to push the zip to my phone
vjtigas said:
Could you make a flashable zip for the recovery? Thanks!
Click to expand...
Click to collapse
Well I made a flashable zip
https://www.androidfilehost.com/?fid=24052804347850387
---------- Post added at 10:47 AM ---------- Previous post was at 10:45 AM ----------
austinpinto said:
hi i am using my sd card as adapted internal storage on android m. will this recovery detect any zip placed on this card? if no how to push the zip to my phone
Click to expand...
Click to collapse
No recovery is made to detect card formatted as Internal Storage as it encrypts it. To flash zip, you can put it in /data/media folder or OEM folder or simply use adb sideload from PC
Minions_Army said:
so this change our system ext4 to f2fs?
my question
if i flash stock or custom rom (Kk,L,M) still on f2fs or back to ext4?
f2fs have great performance i think..
edit : i used sprout8,does it wipe my data/media storage?
Click to expand...
Click to collapse
Yeah, it'll allow you to change the filesystems to F2FS.
It should still be F2FS after flashing KK ROMs. But LP and MM ROMs include an EXT4 image in their zips, so flashing MM or LP ROMs will convert the system partition to EXT4. Data and cache will stay as EXT4.
Formatting data always wipe /data/media. Wiping data with sprout8 recovery keeps /data/media, but as OP says that this is for sprout 4, it'll either not work with sprout8 (not sure) or wipe /data/media if you wipe /data.
hp5942 said:
Well I made a flashable zip
https://www.androidfilehost.com/?fid=24052804347850387
---------- Post added at 10:47 AM ---------- Previous post was at 10:45 AM ----------
No recovery is made to detect card formatted as Internal Storage as it encrypts it. To flash zip, you can put it in /data/media folder or OEM folder or simply use adb sideload from PC
Click to expand...
Click to collapse
i have the drivers for the phone but when i do adb sideload on pc when phone is in this recovery nothing hapends.
are there any other drivers that i must install?
i installed the google usb driver from google
austinpinto said:
i have the drivers for the phone but when i do adb sideload on pc when phone is in this recovery nothing hapends.
are there any other drivers that i must install?
i installed the google usb driver from google
Click to expand...
Click to collapse
Try reinstalling driver while device is in recovery. I had to install it twice on Win10
Hope that helps
I'm not sure where I'm going wrong. After I converted to f2fs, TWRP straight up refused to mount /system, /data and /cache.
I had to convert it back to ext4 before TWRP would mount them. Can anybody help me out?
I'm using cm13 beta2 having 3.10.92 Zeus kernel n 2.8.7.0 twrp recovery so do I need to change kernel after chnging system file to f2fs ...?
harsh. said:
I'm using cm13 beta2 having 3.10.92 Zeus kernel n 2.8.7.0 twrp recovery so do I need to change kernel after chnging system file to f2fs ...?
Click to expand...
Click to collapse
I think Zeus is the only kernel for sprout that supports f2fs. Your safest bet would be to install the latest Zeus(4.5) kernel.
If I flash the flashable zip uploaded by @hp5942, then, will the /system, /cache & /data to f2fs?
krittin98 said:
If I flash the flashable zip uploaded by @hp5942, then, will the /system, /cache & /data to f2fs?
Click to expand...
Click to collapse
No you'll have to do that yourself manually. Recovery is flashed to support mounting of F2FS. Follow instructions given at the beginning of thread and don't forget to flash Zeus kernel given at beginning of thread (mm of lollipop specific depending on your rom). Happy Flashing
I'm unable to take backup as not enough space can I flash system ROM n gapps from SD card after F2FS?
Sent from my Micromax AQ4501 using Tapatalk