Related
For those who don't know what F2FS is, check these links out:
General info
Benchmarks
Warnings
1. Make sure you have a standard kernel for backup that uses ext4 just in case. If anything goes wrong, just install the backup kernel and reboot to recovery.
2. You will have to wipe your /data and /cache partitions for this. Basically factory reset.
3. For 2, you could try to backup data and restore after formatting. I haven't tried this but I could work.
Instructions to format /cache and /data as F2FS:
1. Boot into recovery
2. Install this kernel with F2FS CWM recovery
3. Reboot to recovery again
4. Go to 'Mounts and Storage'
5. Enable "toggle f2fs <-> ext4 migration"
6. Format /data and /cache to F2FS
7. Reboot
And now you have F2FS on /data and /cache :]
To install a new ROM that is not F2FS compatible, edit the updater-script as follows:
1. Replace strings
"mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");"
with string
"run_program("/sbin/busybox", "mount", "/system");"
2. Replace string
"format("ext4", "EMMC", "/dev/block/mmcblk0p3", "0", "/system");"
with string
"run_program("/sbin/mkfs.f2fs", "/dev/block/mmcblk0p3");"
Note: this string needs this patch in ROM
3. Add string
"run_program("/sbin/busybox", "mount", "/data");"
after strings
"run_program("/sbin/mkfs.f2fs", "/dev/block/mmcblk0p3");"
"run_program("/sbin/busybox", "mount", "/system");"
4. Add string
"unmount("/data");"
before string
unmount("/system");
what the benefit of this?
@up
if you read the links you will understand...
Seems faster... and using much more the /cache partition...
zipperX said:
what the benefit of this?
Click to expand...
Click to collapse
Read the first 2 links, mainly the 2nd one. It delivers better I/O performance than what ext4 has to offer.
monstro78 said:
@up
if you read the links you will understand...
Seems faster... and using much more the /cache partition...
Click to expand...
Click to collapse
It uses more /cache because it is a log-based filesystem
For install rom updates, the steps from install this kernel is always format data and cache?
Thanks by advance.
AtEExll
Sent from my GT-I8160 powered by CyanogenMod 11
AtEExll said:
For install rom updates, the steps from install this kernel is always format data and cache?
Thanks by advance.
AtEExll
Sent from my GT-I8160 powered by CyanogenMod 11
Click to expand...
Click to collapse
if you have already formatted to f2fs before, all you have to do is install this kernel again after installing the rom.
@zwliew Only /data for now? How about /system too?
exodius48 said:
@zwliew Only /data for now? How about /system too?
Click to expand...
Click to collapse
i'll work on it. probably have it done within a few days :]
when I try to format my cache partition I always get an error, that formatting was not possible.
also now im not able anymore to write on my /system partition. installing zips and restoring backups are always cancelled... sh***
S.AMU said:
when I try to format my cache partition I always get an error, that formatting was not possible.
also now im not able anymore to write on my /system partition. installing zips and restoring backups are always cancelled... sh***
Click to expand...
Click to collapse
Try re-partioning using this technique http://forum.xda-developers.com/showthread.php?t=2596521
or reflashing via ODIN.
zwliew said:
2. Install this kernel with F2FS CWM recovery
Click to expand...
Click to collapse
Hello! Where I can download separated F2FS CWM image?
ChronoMonochrome said:
Hello! Where I can download separated F2FS CWM image?
Click to expand...
Click to collapse
i believe we don't have separate recovery and boot partitions
zwliew said:
i believe we don't have separate recovery and boot partitions
Click to expand...
Click to collapse
I meant *.cpio image.
ChronoMonochrome said:
I meant *.cpio image.
Click to expand...
Click to collapse
lol i didn't think someone would want that. anyway i don't have it anymore.
zwliew said:
lol i didn't think someone would want that. anyway i don't have it anymore.
Click to expand...
Click to collapse
Is there any way to getting *.cpio image except compiling it from source? I can't extract initramfs from your kernel with f2fs support because it's compiled with LZ4 compression.
zwliew said:
anyway i don't have it anymore.
Click to expand...
Click to collapse
But why f2fs support hasn't been added in your newest kernel releases? it's unstable?
It's possible to format /system as F2FS also or not at the moment ?
No way ??!!!
And: can i use this Kernel for formatting F2FS on my codinap Device ?? Or that will be a brick ?
Many Thanks !!
EDIT 05 September 2014: Added fstab.hammerhead formatted for f2fs-all and f2fs-data for those who wish to manually replace the ramdisk's fstab.hammerhead in a kernel to mount the partitions as f2fs.
NOTE: This will only work on kernels that have f2fs tools commited to their kernel image. Make sure the kernel you wish to modify has F2FS support otherwise it WILL NOT WORK!
22 July 2014: Made changes to the Android Kitchen to retain the USB stick mount.
16 July 2014 If you have used any previous version of F2FS ROM CONVERTER prior to the date, please update to the latest version in the links below to correct major errors, to put more fault checks in place and provide better instructions for non Nexus 5 devices to use. Version number is in the Window Title from v0.3.
First off I have to say that I did not create any of these tools but rather I brought them together and I modified them to make it straight forward and easier to format the partitions as F2FS, make a ROM F2FS-ALL and modify a kernel for F2FS-ALL or just F2FS-DATA.
I would suggest you click on each link and click Thanks for each of them.
Thanks and links to the original authors and software.
Hammerhead FSTAB files formatted for F2FS-ALL and F2FS-DATA
Note1: Rename the desired file to fstab.hammerhead to replace the exisiting one in the ramdisk.
Note2: Use Android Image Kitchen to unpack and repack a kernel file (boot.img) during which you can replace the fstab.hammerhead
Note3: Some kernels' updater-script mounts /system or /data as EXT4. Therefore it needs to be modified from the original and added back to the zip.
e.g. Change mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system"); to run_program("/sbin/busybox", "mount", "/system");
and change mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data"); to run_program("/sbin/busybox", "mount", "/data");
Link: http://d-h.st/l87
Download: follow above link
Thanks: kdh2834
Tool: F2FS and F2FS-ALL kernels modified by kdh2834 with help on how to do it. (Actually it was because of him I can now get my N5 running with a full F2FS-ALL ROM and kernel)
Link: http://forum.xda-developers.com/showpost.php?p=52550395&postcount=1
Thanks: osm0sis
Tool: Android Image Kitchen (for unpacking and repacking a kernel)
Link: http://forum.xda-developers.com/showpost.php?p=36067074&postcount=1
Download my version: http://d-h.st/E74
Thanks: TeamWin
Tool: TWRP recovery for formatting the partitions as F2FS (use the latest version)
Note: It can also show the format of a partition in Wipe -> Advanced Wipe
Link: http://techerrata.com/browse/twrp2/hammerhead
Download follow above link
Thanks: Phil3759 and to rootSU for the Nexus builds
Tool: Philz touch recovery for formatting the partitions as F2FS (use the latest version)
Link: http://forum.xda-developers.com/showpost.php?p=48377548&postcount=1
Download: follow above link
Thanks: legolas93's FormatPartitions.zip
Note: These flashable zips need one of the above recoveries to work
Tool: Flashable zips to format the partitions automatically
Link: http://forum.xda-developers.com/showthread.php?t=2678140
Download my version to format all partitions to F2FS: http://d-h.st/RCz
Download my version to format the data partition to F2FS: http://d-h.st/2AI
Thanks: NABENDU1 for F2FS ROM CONVERTER
Note: Mine has been heavily modified for Nexus 5 phones but can be used by any device
Link: http://forum.xda-developers.com/showpost.php?p=52201672&postcount=1
Tool: F2FS ROM Converter v0.5 to make a flashable ROM with F2FS support.
Download my version: http://d-h.st/Uiq
EDIT: Latest version (v0.5) replaced the AOSP F2FS-ALL kernel (boot-f2fs-all.img) as it was not fully F2FS-ALL compatible. Previous version still had /cache partition as EXT4
EDIT: Latest version (v0.4) has support for Slimkat and similar ROMs that need to mount the /data partition.
Instructions
Note: The following steps can be done in any order EXCEPT that step 1. must be done before step 2.
1. Install one of the recoveries.
Note1: If you are on a stock recovery and your phone is locked you will need to backup everything first!
Note2: There is a flashable zip to lock and unlock the boot loader without formatting (only after initial unlock) and Philz Touch Recovery has a password lock as well if you are concerned about security.
WARNING: Before doing the below step, backup your ROM AND your DATA on your sdcard as it will be formatted!
Suggestion: Do an adb pull.
2. Format the partitions using the flashable zips.
3. Use the Android Image Kitchen I provided to modify a kernel with F2FS support. Drag and drop the boot.img on 1_mod_f2fs_kernel.bat file and just follow the instructions.
The kernel can then be installed by sideloading the zip file (see step 4.) or using fastboot from the bootloader (e.g. fastboot flash boot boot.img)
4. Use the F2FS Converter I provided to convert a ROM to mount the /system with a F2FS partition
The ROMs flashable zip will have to be sideloaded (In Philz Touch go to Install Zip -> Install zip from sideload, / In TWRP click Advanced -> ADB Sideload)
Note1: Only needs to be used with a F2FS-ALL kernel.
Note2: There is an option to use your preferred F2FS-ALL kernel as opposed to the default ones.
EDIT: Added which batch script to drop the image file onto in step 3.
Thanks, makes it easy for lazy people like me. Will use it later and let you know how it went.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Волк said:
Thanks, makes it easy for lazy people like me. Will use it later and let you know how it went.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If I missed anything let me know although I tested it to make sure it worked for myself.
Please remember to do a sdcard backup on to your computer. The backups from the the custom recoveries does not back up the sdcard.
Any devs working on a similar method for sgh-I747?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
aircooledbusses said:
Any devs working on a similar method for sgh-I747?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I found a TWRP recovery that should support f2fs for your i747 here:
http://techerrata.com/browse/twrp2/d2att
Download the latest version.
Or you can use Philz Touch Recovery but it seems like you will need to build it yourself (if you know how)
Backup everything and move the backups to a computer.
And run one of the format tools according to which partitions will have F2FS (only /data f2fs-data OR /system /data & /cache f2fs-all)
I found one kernel that supports F2FS, there are probably others.
http://forum.xda-developers.com/showthread.php?t=2390147
To answer your question: I am not sure. I am just sharing what I did to make my life easier with others.
These tools will not work for your i747 as they are but I will look into what I can modify to make it work for yours and you can tell me if it works.
If you are getting problems I will see what I can do to help if I have the time.
I will post something when I can.
F2FS-ALL Kernels
You can check http://forum.xda-developers.com/google-nexus-5/development/kernel-f2fs-modified-kernels-t2746951 for some kernels.
The CM kernel was modified by me for F2FS-ALL
You can get it here:
http://d-h.st/1rS
I have modified the ElementalX kernel (ElementalX-N5-1.02-cm.zip) to F2FS-ALL.
Original kernel is here:
http://forum.xda-developers.com/showpost.php?p=47286518&postcount=1
Note1: You need to install the CM kernel above first as the Elemental X uses the ramdisk of the current working kernel, which in this case has the fstab.hammerhead with the f2fs information.
Note2: I had to modify the mount command as well in the updater-script from this:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
to this:
run_program("/sbin/busybox", "mount", "/system");
You can get the working ElementalX 1.02cm F2FS-ALL version here:
http://d-h.st/oEt
Chaos Kernel v13.0 July 08 (nightly) F2FS-ALL - http://d-h.st/h3H
nice! this collection of tools might have me finally trying f2fs on my Nexus5...
however, I've set my sights on this kernel http://forum.xda-developers.com/google-nexus-5/development/kernel-t2697951
there seems to be no interest to include f2fs support by default, could I perhaps ask for you to add it and compile? :angel:
I'm currently on stock 4.4.4 and faux kernel. but from what I read faux causes issues on f2fs-all, right? and other kernels I've looked at don't seem attractive enough to me... is there pure 4.4.4 stock with f2fs-all added? ^^ I found only 4.4.2 stock kernel.
Also... if I backup my /data can I restore it later onto f2fs partition? so I don't have to start from scratch and install/update apps?
no biggie, just wondering on this one.
thanks alot! :silly:
GizmoTheGreen said:
nice! this collection of tools might have me finally trying f2fs on my Nexus5...
however, I've set my sights on this kernel http://forum.xda-developers.com/google-nexus-5/development/kernel-t2697951
there seems to be no interest to include f2fs support by default, could I perhaps ask for you to add it and compile? :angel:
I'm currently on stock 4.4.4 and faux kernel. but from what I read faux causes issues on f2fs-all, right? and other kernels I've looked at don't seem attractive enough to me... is there pure 4.4.4 stock with f2fs-all added? ^^ I found only 4.4.2 stock kernel.
Also... if I backup my /data can I restore it later onto f2fs partition? so I don't have to start from scratch and install/update apps?
no biggie, just wondering on this one.
thanks alot! :silly:
Click to expand...
Click to collapse
I will look at that kernel later.
If you backup it up using an adb pull, that's what I did not sure about the custom recovery backups as they usually name the backups according to the format, at least for Philz Touch Recovery.
In regards to the stock 4.4.4 with f2fs-all, I just had up a post about that.
Here it is: http://forum.xda-developers.com/showthread.php?t=2791580
GizmoTheGreen said:
nice! this collection of tools might have me finally trying f2fs on my Nexus5...
however, I've set my sights on this kernel http://forum.xda-developers.com/google-nexus-5/development/kernel-t2697951
there seems to be no interest to include f2fs support by default, could I perhaps ask for you to add it and compile? :angel:
I'm currently on stock 4.4.4 and faux kernel. but from what I read faux causes issues on f2fs-all, right? and other kernels I've looked at don't seem attractive enough to me... is there pure 4.4.4 stock with f2fs-all added? ^^ I found only 4.4.2 stock kernel.
Also... if I backup my /data can I restore it later onto f2fs partition? so I don't have to start from scratch and install/update apps?
no biggie, just wondering on this one.
thanks alot! :silly:
Click to expand...
Click to collapse
Sorry about the kernel but I only change the ramdisk to set which partitions are to boot with F2FS. So if it doesn't already support F2FS I don't know how to add it. I am relatively new to linux and android. I will like to setup a build environment and learn how to build the kernels and ROMs myself but I have been procrastinating as I need to free up some space on a drive.
Some kernels have the support but are not set up to boot the partitions. I am skimming the forums looking for different kernels to try.
At the moment I am using a CM (CAF based) kernel although there are a lot more ASOP kernels. I will try going to stock to try out some of them.
Huge time reduction!
Thank you for your mod.
Thanks for the great tools!
Could you please provide the modified f2fs-all Elemental X kernel you mentioned earlier? You seemed to have forgotten to post it.
mzheng086 said:
Thanks for the great tools!
Could you please provide the modified f2fs-all Elemental X kernel you mentioned earlier? You seemed to have forgotten to post it.
Click to expand...
Click to collapse
It is in post #7 but it is the caf version. Or did you want the AOSP version?
dechronic said:
It is in post #7 but it is the caf version. Or did you want the AOSP version?
Click to expand...
Click to collapse
I might have missed something obvious. In that case, please point it out to me. In post #7, I only see a link to the original thread of Elemental X kernel, and two links to the modified CM11 kernel. But there is no link to modified Elemental X kernel.
mzheng086 said:
I might have missed something obvious. In that case, please point it out to me. In post #7, I only see a link to the original thread of Elemental X kernel, and two links to the modified CM11 kernel. But there is no link to modified Elemental X kernel.
Click to expand...
Click to collapse
Oh shoot you are right. I don't how come I posted the same kernel twice. Uploading it now. I will edit that post and copy the link into the next post once I am done and I also have a link for Chaos-Kernel_v13.0-[07-08]-[11-16]-f2fs-all.zip (nightly) which I will post shortly too.
---Copied from Post #7--
You can get the working ElementalX 1.02cm F2FS-ALL version here:
http://d-h.st/oEt
Chaos Kernel v13.0 July 08 (nightly) - http://d-h.st/h3H
I tried your version of the tools on CharizardX (AOSP) kernel and this 4.4.4 stock rom. http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
it failed to mount my data partition and I got a 128mb temp ramdrive at each boot... not sure what went wrong.
temp booted cwm recovery to reformat back to 4ext and then philz to restore my backup from usb drive, so I'm back at a working system...
edit:working now with your kernelupload in the other thread, but I can't seem to get superuser working, flashing koush's superuser via .zip. also I et a bootloop running antutu... probably kernel. what AOSP kernel do you recommend? I'd love to use faux's but last I heard there was trouble with wifi for some reason...
GizmoTheGreen said:
I tried your version of the tools on CharizardX (AOSP) kernel and this 4.4.4 stock rom. http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
it failed to mount my data partition and I got a 128mb temp ramdrive at each boot... not sure what went wrong.
temp booted cwm recovery to reformat back to 4ext and then philz to restore my backup from usb drive, so I'm back at a working system...
edit:working now with your kernelupload in the other thread, but I can't seem to get superuser working, flashing koush's superuser via .zip. also I et a bootloop running antutu... probably kernel. what AOSP kernel do you recommend? I'd love to use faux's but last I heard there was trouble with wifi for some reason...
Click to expand...
Click to collapse
Honestly, I only just started using F2FS in the last week or so. I haven't tried an AOSP Roms yet to try out the AOSP kernels.
I just downloaded Slimkat as the script mounts the /data partition as well, so I have modify my script to account for that. I will try out some AOSP kernels that I will mod for F2FS-ALL and let you know what I got to work.
dechronic said:
I just downloaded Slimkat as the script mounts the /data partition as well, so I have modify my script to account for that. I will try out some AOSP kernels that I will mod for F2FS-ALL and let you know what I got to work.
Click to expand...
Click to collapse
You should be able to remove that mount if the user already has /data on f2fs, since data isn't normally formatted, and hence fully wiped and unmounted. If the user is migrating to f2fs, then, yes that would need to be changed. Also, ROM scripts format /system to ext4, which has to be removed or changed to the f2fs command.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Волк said:
You should be able to remove that mount if the user already has /data on f2fs, since data isn't normally formatted, and hence fully wiped and unmounted. If the user is migrating to f2fs, then, yes that would need to be changed. Also, ROM scripts format /system to ext4, which has to be removed or changed to the f2fs command.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The script searches for the mount /data command because as was pointed out to me, some ROM scripts mount it. Particularly Slimkat. It only changes it if it finds it. Otherwise it is ignored. If the the ROM is selected to be reconfigured as F2FS-ALL then it looks for any format /system, mount /system and mount /data commands. If is set to reconfigured as F2FS-DATA then only the /data is mounted as F2FS if required by the ROM's updater script
Sent from my Nexus 5 using XDA Free mobile app
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Credits
Phil3759 for his awesome recovery
Koush for having created and maintaining cwm
Cyanogenmod for making all this possible
Android-Andi for helping with aroma issue
XDA:DevDB Information
[bacon][CWM Advanced Edition] PhilZ Touch, Tool/Utility for the ONEPLUS ONE
Contributors
katinatez
Version Information
Status: Stable
Current Stable Version: 6.59.4
Stable Release Date: 2015-09-22
Last Updated 2015-09-22
This is flashable through custom recovery, if you prefer fastboot commands extract recovery.img
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Changelog
Code:
[SIZE="4"]
2015-09-22
Updated 6.59.4
Fixed backup of LOGO partition
2015-09-21
Updated 6.59.3
Added f2fs to system partition
to support 3 partition f2fs backup
2015-05-18
Updated 6.59.2
updated f2fs with Jaegeuk Kim repo
[URL="https://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs.git/log/?h=linux-3.4"]https://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs.git/log/?h=linux-3.4[/URL]
Backup Firmware all 8 partitions, and modem partition named firmware
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware
Compatible backup & restore with unofficial twrp v2.8.6.1 in Philz twrp mode
cm-12.1 kernel
exfat kernel support
f2fs data & cache in fstab
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs rw,noatime,nosuid,nodev,discard,nodiratime,inline_xattr,inline_data,nobarrier,active_logs=4 wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/reserve4
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs rw,noatime,nosuid,nodev,discard,nodiratime,inline_xattr,inline_data,nobarrier,active_logs=4 wait,check
2015-01-31
Updated 6.59.1
switched to cm-12.0 kernel for faster loading
updated recovery.fstab
updated f2fs commits
2014-12-14
6.59.0
add larger font, thanks [user=2661222]@xiaolu[/user]
2014-10-26
6.58.8
Added CM fix for persist partition
Added backup/restore of persist partition
2014-10-13
6.58.7: Source Update and Fixes
merge NTFS sources into recovery
add NTFS check binary (ntfsfix)
compile NTFS binaries as libraries and link them to recovery binary
spares 500Kb space
fix compile error when NTFS is disabled
2014-10-11
Update to developers: v6.58.4
Fixes building errors and issues related to new CyanogenMod changes
2014-10-05
Update 6.58.0
libtouch_gui 1.42
CWM 6.0.5.1
update sources
Fix display turned off on auto dim timer:
Some devices, like Motorola and Nexus, have their screen turned off is brightness is set to 0
add option to define min brightness value at compile time
by default, min brightness value is now 10 instead of 0
2014-09-18
6.57.9
fix install in "Free Browse Mode" from non vold managed volumes
2014-09-14
Update v6.57.8
CWM 6.0.5.1
fix for ROM OTA updates generating two install scripts (openrecovery + extendedcommands)
merge CWM updates to selinux permissions for init services
fix adb for 3.10 kernel
2014-09-13
Faster boot
Fixed usb-otg
Updated F2FS version 3.4.y
2014-09-03
6.57.5
Full F2FS Support
format,mount,read f2fs
Initial Release
2014-08-28
6.57.5
CWM 6.0.5.0
libtouch_gui 1.41
Aroma File Manager fixed
Screenshots fixed
EFS backup
[/SIZE]
DOWNLOADS
Android File Host
I added a couple of more recoveries I built here, but there will be seldom updates if any.
CWM Full Touch recovery now supports aroma file manager loading.
And stock bacon recovery has been updated, it's here for those who want to take it back to stock recovery
Thanks @katinatez
Thanks!
But this recovery can't mount f2fs. The log show
can't mount /data
cant' mount /system
can't mount /cache
And i cannot flash anything.
F2fs support in recovery kernel will be back?
gulp79 said:
Thanks!
But this recovery can't mount f2fs. The log show
can't mount /data
cant' mount /system
can't mount /cache
And i cannot flash anything.
F2fs support in recovery kernel will be back?
Click to expand...
Click to collapse
I was afraid of that, so f2fs is needed in recovery kernel then correct? Need more time at the moment use previous version with ak kernel then.
katinatez said:
I was afraid of that, so f2fs is needed in recovery kernel then correct? Need more time at the moment use previous version with ak kernel then.
Click to expand...
Click to collapse
Yes, is needed in kernel. Btw at the moment you can put 2 versions, until a kernel with aroma and f2fs will be available. Have you tried to ask @ak to add aroma fix to his kernel? Or maybe @Dees_Troy can add f2fs support.
gulp79 said:
Yes, is needed in kernel. Btw at the moment you can put 2 versions, until a kernel with aroma and f2fs will be available. Have you tried to ask @ak to add aroma fix to his kernel? Or maybe @Dees_Troy can add f2fs support.
Click to expand...
Click to collapse
@johnnyslt said he would help patch the f2fs, just give us time.
Del
radzmin said:
Del
Click to expand...
Click to collapse
Don't understand. What is the question?
katinatez said:
Don't understand. What is the question?
Click to expand...
Click to collapse
Me too[emoji12]
By the way, whats the difference? This works on s4 i9505 right?
katinatez said:
This is flashable through custom recovery, if you prefer fastboot commands extract recovery.img
Click to expand...
Click to collapse
Would you detail your fix for Aroma?
Maybe we could patch aroma sources hopefully
Also, please rename your files so that they fit in goo host
Many third party apps rely on the naming to update recovery images
Phil3759 said:
Would you detail your fix for Aroma?
Maybe we could patch aroma sources hopefully
Also, please rename your files so that they fit in goo host
Many third party apps rely on the naming to update recovery images
Click to expand...
Click to collapse
All I did was to follow your instructions to compile with other kernels! But I should have started with twrp kernel instead! I also unpacked Dees_Troy, dr87 , KINGbabasula twrp recoveries because they all loaded aromafm.zip. After comparison I added rpm, tz, aboot into recovery.fstab. Compiled with Dees_Troy twrp kernel & dt.img and success.
Also changing naming convention of zip files. Sorry about that
radzmin said:
Me too[emoji12]
By the way, whats the difference? This works on s4 i9505 right?
Click to expand...
Click to collapse
Will not work on s4, your in one plus one forum.
Bah, time and date still borked. My backups are a mess. Does twrp also have this issue?
Mr Woolf said:
Bah, time and date still borked. My backups are a mess. Does twrp also have this issue?
Click to expand...
Click to collapse
Set up your time in options...
gulp79 said:
Set up your time in options...
Click to expand...
Click to collapse
Tried it mate, won't stick. Time was fine on my s3 using philz - have never managed to get it to work on my OnePlus though.
Mr Woolf said:
Tried it mate, won't stick. Time was fine on my s3 using philz - have never managed to get it to work on my OnePlus though.
Click to expand...
Click to collapse
Try with options, have you enabled battery clock? In the options there are some flag to set. For me works, I've to set up time only after option reset
Mr Woolf said:
Bah, time and date still borked. My backups are a mess. Does twrp also have this issue?
Click to expand...
Click to collapse
Correct settings is time settings/Qualcomm time daemon. That should fix your time.
katinatez said:
All I did was to follow your instructions to compile with other kernels! But I should have started with twrp kernel instead! I also unpacked Dees_Troy, dr87 , KINGbabasula twrp recoveries because they all loaded aromafm.zip. After comparison I added rpm, tz, aboot into recovery.fstab. Compiled with Dees_Troy twrp kernel & dt.img and success.
Also changing naming convention of zip files. Sorry about that
Click to expand...
Click to collapse
:good:
As I thought, the issue is Aroma is no more compatible with many CM kernels
I am not sure about the exact missing part though as I never had an affected device
Hi there!
Today I finally found how to make our codinas' kernels universal, i.e. allow to install kernel on whatever ROM and finally separate recovery from kernel. It's well known, bootloader decides what will be loaded - kernel or recovery. That probably may explain why AnyKernel installer(or other similar) doesn't work on codina, because we can't move recovery partition anywhere.
But there is also a little trick that allow us load recovery and boot.cpio from different partition - https://github.com/ChronoMonochrome/Chrono_Kernel/commit/df9094f1f12618ad9599da266792d6b2f8106170 - just an another approach
Don't worry, we won't touch bootloader at all.
As can be seen, /dev/block/mmcblk0p17 (kernel2 partition) will be used for storing recovery.cpio and boot.cpio. On stock that may not work (I don't know for what exactly uses Kernel2 partition, besides of manually restoring of kernel1 partition. I only know that is almost useless on custom ROMs, and we can use it as we want )
First do some preparations:
Download this kernel and needed recovery/boot scripts(4.4.x.cpio.zip, 4.4.x_f2fs.cpio.zip, etc... 4.4.x.cpio means that it support only ext4) from my google drive (folder ramdisks), unzip recovery (twrp or cwm) and rename to recovery.cpio, then move it to external SD card. Then do it with boot scripts that you've downloaded (e.g. 4.4.x_f2fs.cpio.zip - unzip and rename to boot.cpio)
Well, that all that needs for installation. Read following instruction very carefully, otherwise that may cause brick Keep in mind, all that you do at your own risk! I'm not responsible if you brick your phone!
Installation method:
1) reboot into recovery, plug your phone to your PC, enable adb:
Code:
adb shell
2) Format kernel2 partition to ext4 file system:
Code:
mke2fs -T ext4 /dev/block/mmcblk0p17
Think twice before you hit 'enter' button - wrong command may cause hardbrick!
3) create /ramdisk folder and mount kernel2 partition
Code:
mkdir /ramdisk
mount -t ext4 /dev/block/mmcblk0p17 /ramdisk
move your recovery.cpio and boot.cpio to this folder, give 777 permissions:
Code:
chmod 777 /ramdisk/recovery.cpio
chmod 777 /ramdisk/boot.cpio
4) install downloaded kernel
Now you can change recovery via changing /ramdisk/recovery.cpio - just make a backup of this file, and then replace with one of another recoveries. If you want to install another ROM or change filesystem of partition then replace /ramdisk/boot.cpio with one of needed boot scripts. Don't forget to give 777 permission (probably 644 is enough, but I didn't test it) to both of these files.
This method tested and working on 4.4.x TC ROM + twrp recovery + kernel with full F2FS support.
Well, now it's time to create uncompressed kernel, that may slightly decrease the boot time
@ChronoMonochrome
Thanks. do you mean that kernel2 partition is useless in stock and cyanogenmod firmware?
Is it right that boot loader will read kernel1 partition then it will read system partition? and kernel2 is not necessary for booting?
I have installed new universal kernel (2.5) , so I flashed new ramdisk for 4.4.x , can I roll back to older versions or stock firmware with this ramdisk or I should restore Partition17 backup?
sorset said:
@ChronoMonochrome
Thanks. do you mean that kernel2 partition is useless in stock and cyanogenmod firmware?
Click to expand...
Click to collapse
As it turned out, it's unneeded even on stock. So if you won't restore kernel2 partition, nothing will happen.
Is it right that boot loader will read kernel1 partition then it will read system partition? and kernel2 is not necessary for booting?
I have installed new universal kernel (2.5) , so I flashed new ramdisk for 4.4.x , can I roll back to older versions or stock firmware with this ramdisk or I should restore Partition17 backup?
Click to expand...
Click to collapse
Yes, you can roll back to usual kernels. it doesn't matter what written on kernel2 partition - real kernel or anything else...
ChronoMonochrome said:
As it turned out, it's unneeded even on stock. So if you won't restore kernel2 partition, nothing will happen.
Click to expand...
Click to collapse
Ok, thanks , But why do you mount kernel2 partition inside of OS? As I understand boot.cpio is necessary before booting OS . And inside of OS is just an extra storage! (is that true?)
sorset said:
And inside of OS is just an extra storage! (is that true?)
Click to expand...
Click to collapse
Yes and no, is 16 Mb big enough to be called "storage"? I did it, just to be able replace ramdisks even without booting to recovery. But newest boot scripts doesn't have it.
Ace 2 has 15 - 20 Partitions my Friend
ace2nutzer said:
Ace 2 has 15 - 20 Partitions my Friend
Click to expand...
Click to collapse
And what ? We actually talking about kernel2 partition.
ChronoMonochrome said:
And what ? We actually talking about kernel2 partition.
Click to expand...
Click to collapse
sorry, i meant @sorset
ChronoMonochrome said:
Yes and no, is 16 Mb big enough to be called "storage"? I did it, just to be able replace ramdisks even without booting to recovery. But newest boot scripts doesn't have it.
Click to expand...
Click to collapse
You are right , but I remember days that 1.44MB floppy disk was a large STORAGE and 16MB was HUGE
sry , I have another question , So can I remove its line from fstab to prevent mounting?
I'm confused
boot.img in kernel archive is recovery image that will extract on partition15 (kernel) , but what recovery.cpio exactly is that yu copy on partition17 (kernel2) ?
ace2nutzer said:
Ace 2 has 15 - 20 Partitions my Friend
Click to expand...
Click to collapse
Yes,With counting internal storage , 17 exactly , but thats not the point , I'm afraid.
sorset said:
sry , I have another question , So can I remove its line from fstab to prevent mounting?
Click to expand...
Click to collapse
just redownload bootscripts(kernel/ramdisks), as I said, newest scripts doesn't mount kernel2 partition.
boot.img in kernel archive is recovery image that will extract on partition15 (kernel) , but what recovery.cpio exactly is that yu copy on partition17 (kernel2) ?
Click to expand...
Click to collapse
I don't get it rephrase please
ChronoMonochrome said:
just redownload bootscripts(kernel/ramdisks), as I said, newest scripts doesn't mount kernel2 partition.
I don't get it rephrase please
Click to expand...
Click to collapse
I didn't too
There is an Image named boot.img in kernel flashable zip archive that extracts into partition 15 (named kernel) as I understood is recovery (TWRP or CWM) image and you wont touch linux orginal image , and your modified custom kernel is new modules for linux image that loads while booting (sry, I cant explain fine), So what is recovery.cpio that is in recovery flashable zip image that extracts into partition 17 (named kernel2) ?
sorset said:
as I understood is recovery (TWRP or CWM) image and you wont touch linux orginal image
Click to expand...
Click to collapse
originally kernel + recovery
, and your modified custom kernel is new modules for linux image that loads while booting (sry, I cant explain fine), So what is recovery.cpio that is in recovery flashable zip image that extracts into partition 17 (named kernel2) ?
Click to expand...
Click to collapse
In my mod kernel(mmcblk0p15) and recovery (mmcblk0p17) are splitted.
Thank you. I see.
This is probably the best (and only?) way to rebuild the ramdisk without having to compile anything, which is an excellent base for my NoUMS patches
:good:
<remove>
Hey everyone,
A few days ago, I decided to downgrade from AICP 11 back to 10 (Android 6.0.1 to 5.1.1), wiped everything but internal storage. When flashing, I got an error, saying that the /vendor partition was missing, and indeed, while it existed, I could only mount it forcefully, because the device was busy.
This lead to a complete wipe, as after a reboot, TWRP asked for an encryption password, which I didn't set. Here, I did a factory reset & wiped everything. After that, I tried flashing again (5.1.1), but after it was completed, I got a line, which said "Couldn't unmount /system", which is true, as it's already unmounted. But when I mount it, all the files that are supposed to be installed seem to be there.
When I reboot the device, it gets stuck on the Google logo.
Frankly, I'm afraid to even flash back to stock, so I was hoping that someone more experienced could help me out.
It should be noted, that I still have access to fastboot, and TWRP.
Thanks in advance,
DecentM
How did you force mount /vendor?
Can you clarify where you are seeing these problems? (TWRP or within Android)
Do you have any nandroid backups to test and see if they work?
dmantilal said:
How did you force mount /vendor?
Can you clarify where you are seeing these problems? (TWRP or within Android)
Do you have any nandroid backups to test and see if they work?
Click to expand...
Click to collapse
I used mount -f and umount -f in the TWRP terminal
I see all these problems in TWRP, since I can't boot/get past the initial Google logo.
I do have a nandroid backuip on my laptop (as I had to wipe the tablet clean), but that's currently unavailable for me to use, I'll reply back when I tried it.
I doubt it will work, because it just extracts data to a predefined path, which seems like the same thing an installer zip does.
DecentM said:
I used mount -f and umount -f in the TWRP terminal
I see all these problems in TWRP, since I can't boot/get past the initial Google logo.
I do have a nandroid backuip on my laptop (as I had to wipe the tablet clean), but that's currently unavailable for me to use, I'll reply back when I tried it.
I doubt it will work, because it just extracts data to a predefined path, which seems like the same thing an installer zip does.
Click to expand...
Click to collapse
Why did you need /vendor mounted in TWRP?
I thought flashing used dd (command) or similar to copy the *.img file to the partition (or, more accurately, the block device). If /vendor is mounted during *.img copy, that would most likely cause errors.
dmantilal said:
Why did you need /vendor mounted in TWRP?
I thought flashing used dd (command) or similar to copy the *.img file to the partition (or, more accurately, the block device). If /vendor is mounted during *.img copy, that would most likely cause errors.
Click to expand...
Click to collapse
I mounted it, because when I initially restored the 5.1.1 rom, I got an error, saying that the /vendor partition wasn't mounted.
DecentM said:
I mounted it, because when I initially restored the 5.1.1 rom, I got an error, saying that the /vendor partition wasn't mounted.
Click to expand...
Click to collapse
You are sure it was complaining about "unmounted", rather than "mounted"?
Do these roms include a vendor.img? You may need to flash the stock 5.1.1 vendor.img.
Either way, unless you mkfs'ed or resize2fs'ed the partitions, they should be fine. Full wipe & go.
dmantilal said:
You are sure it was complaining about "unmounted", rather than "mounted"?
Do these roms include a vendor.img? You may need to flash the stock 5.1.1 vendor.img.
Either way, unless you mkfs'ed or resize2fs'ed the partitions, they should be fine. Full wipe & go.
Click to expand...
Click to collapse
I'm not sure.
I already did a full wipe, but it still had issues. I'll try again tomorrow, and report back on how it went.
DecentM said:
I'm not sure.
I already did a full wipe, but it still had issues. I'll try again tomorrow, and report back how it went.
Click to expand...
Click to collapse
Having a mismatched vendor.img could be your problem.
No ROM I know of includes a vendor.img. I think it is a legal issue, like including GApps with a ROM.
dmantilal said:
Having a mismatched vendor.img could be your problem.
No ROM I know of includes a vendor.img. I think it is a legal issue, like including GApps with a ROM.
Click to expand...
Click to collapse
I don't think that the issue is with the vendor image anymore, but with the partitions in general. I always had a mismatched vendor image, as it only results in a modal box after boot.
My problem is again, with the /system partition not being visible to flashable zip files.
Mismatched vendor.img can also cause bootloops and other quirks like battery-charge percentage inaccuracies.