I tried this with Euphoria and I keep getting System UI has stopped. Any ideas on what might be the problem?
[KERNEL] Nexus 5 F2FS
- Thread starter dennes544
- Start date
I tried this with Euphoria and I keep getting System UI has stopped. Any ideas on what might be the problem?
Connect the phone to a computer and using a terminal emulator/command prompt on the computer run the following command in the same directory as adb:
Code:
adb shell "mount|grep f2fs|grep -oe /userdata -oe /system -oe /cache"OR
Via a terminal emulator app on the phone run:
Code:
mount|grep f2fs|grep -oe /data -oe /system -oe /cacheYou should get the result:
/data
/cache
(/cache may appear twice)
If /cache or /data is missing it means that the missing one is not formatted as f2fs.
It could be the /cache partition.
Anybody found a 5.1.1 dummy kernel yet? Trying to flash Chroma (5.1.1) and get system FC using a 5.1 dummy kernel and Elemental X. And yes both Data and Cache are F2FS
Try here:
https://basketbuild.com/devs/Cl3Kener/HAMMERHEAD/F2FS
Some of these are deprecated. I can't remember which one is the latest as Cl3Kener's rom includes a working F2FS ramdisk so I don't have to flash a ramdisk prior to flashing a kernel. Extracting it from his Optipop rom might be another avenue.
EDIT - the kernels in the above folders may not work with the latest up-to-date ROMs. Quite likely, they won't
Last edited:
And the kernel has an F2FS ramdisk? Hence no need for a F2FS dummy kernel like Elemental X requires? I'll give it a shot.
---------- Post added at 12:12 AM ---------- Previous post was at 12:06 AM ----------
What makes you think these are 5.1.1? I only see 5.1
I'll play around with a few things and give you a more definitive answer but it will have to be a little bit later.
Well I just tried and while it did boot NFC service kept force closing making the ROM unusable.
I tried some things and got the similar. You *may* have better luck extracting the boot.img from the latest optipop but that could also be hit or miss.
Alright guys,
after some months of ext4, I decided to go back to f2fs. But it doesn´t seem to work, and I don´t know whose (ROM, Kernel, Recovery, me?) fault it is:
I tried to convert data and cache as follows:
1. Flashed the stock 5.1 image to have a clean base
2. rooted and installed latest TWRP (2.8.6.1)
3. went to recovery, factory reset, then converted data and cache to f2fs via the advanced wipe menu
4. reboot recovery
5. back in recovery again, went to asvanced wipe and checked, data and cache was indeed f2fs
6. connected my Nexus 5 to my computer, copied ROM and Kernel to it and flashed them.
7. rebooted device, set the rom up
8. rebooted to recovery (after setting up everything)
9. in recovery I went to advanced wipe and then to cache and data, and tadaa, file system was stated as ext4.
Is this just a displaying problem in TWRP (data/cache are f2fs, but TWRP displays it wrong?) or did the converting process fail/was reverted? I tried several ROMS (CleanCore, Chroma, Optipop) and Kernels (CodeBlue and Uber), but the result was always the same.
after some months of ext4, I decided to go back to f2fs. But it doesn´t seem to work, and I don´t know whose (ROM, Kernel, Recovery, me?) fault it is:
I tried to convert data and cache as follows:
1. Flashed the stock 5.1 image to have a clean base
2. rooted and installed latest TWRP (2.8.6.1)
3. went to recovery, factory reset, then converted data and cache to f2fs via the advanced wipe menu
4. reboot recovery
5. back in recovery again, went to asvanced wipe and checked, data and cache was indeed f2fs
6. connected my Nexus 5 to my computer, copied ROM and Kernel to it and flashed them.
7. rebooted device, set the rom up
8. rebooted to recovery (after setting up everything)
9. in recovery I went to advanced wipe and then to cache and data, and tadaa, file system was stated as ext4.
Is this just a displaying problem in TWRP (data/cache are f2fs, but TWRP displays it wrong?) or did the converting process fail/was reverted? I tried several ROMS (CleanCore, Chroma, Optipop) and Kernels (CodeBlue and Uber), but the result was always the same.
Try twrp 2.5.x.x. I think since, 2.6, it has bugs
Sent from my Nexus 5 using XDA Free mobile app
The thing is, rom zip's nowadays flash a .dat or .img that carries the partition format and data, so flashing the zip converts it.
A possible workarround might be to flash the rom, perform a nandroid backup of cache and data (or data only, cache does not matter), copy it to pc, convert partitions, rename the backup files from ext4 to f2fs, copy them back, and restore the data.
Did that, also tried with TWRP 2.8.5.2, but data and cache are still changing again to ext4. Im near absolute distress....
at what point do they change?
I mean, if you flash the rom, it is logical for them to change (the .zip formats them).
Now, if you flash no more zips, and do as i say, WHEN do they change?
Restoring the nandroid (correctly renamed) changes nothing, and if it is incorrectly renamed, it will complain.
I did as you said:
1. factory image (clean base)
2. root & TWRP
3. flashed Chroma Rom, Gapps and CodeBlue
4. made a nadroid backup
5. copied backup to PC, renamed "ext4" in data/cache-backup names to f2fs (also the md5 files)
6. converted data/cache to f2fs in recovery, reboot recovery
7. copied backup files back to the phone, restored cache and data
8. reboot the system
9. after setup of Google account etc. I rebooted to recovery again, and now cache and data were labelled as ext4 in the advanced wipe section.
What am I doing wrong? Is there a guide I can follow, so that it just works (also with the newer .dat or .img files you mentioned)?
I would repeat the process, double checking that the format remains F2FS after each step.
Also, do you have f2fs support in your kernel? If so, it might need to be flashed after the partitions are already f2fs (if not, you need to add support).
Also, do you have f2fs support in your kernel? If so, it might need to be flashed after the partitions are already f2fs (if not, you need to add support).
Did the double chek after every step, It´s changing when I first boot up the ROM and then go back to recovery.
I thought CodeBlue had support for cache and data on f2fs.
So how should I try it? Flash CodeBlue again after I restored the backup? I already did that, doesn´t keep t from changing back to ext4 after first bootup....
mm, then i would:
1. factory image (clean base)
2. root & TWRP
3. flashed Chroma Rom, Gapps and CodeBlue
3.a boot rom, configure first boot setup
3.b reboot recovery
3.c wipe caches
4. nadroid backup (/data only)
5. copy backup to PC, renamed "ext4" in data-backup name to f2fs (also the md5 files)
6. converted data/cache to f2fs in recovery, reboot recovery
6.a check it is still F2FS
6.b flash codeblue again
7. copy backup files back to the phone, restore data
7.a check it is still F2FS
7.b reboot recovery and re-check /data and /cache are still F2FS
8. reboot the system
9. after setup of Google account etc. I rebooted to recovery again, and now cache and data were labelled as ext4 in the advanced wipe section.
If that still fails, either your rom, kernel, of the gods, wont do F2FS
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
46F2FS (born Flash-Friendly File System) - file system, focused on the use of flash memory, and now it on the Nexus 5!
Attention! Erases all data, including those from the /data/media! Save the data to a computer
1.Boot in FastBoot
2.Flash recovery http://d-h.st/vFQ
3.Boot in recovery
4.Goto Wipe-> Format Data-> enter 'yes' and click go
5.Flash firmware through sideload(AOSP, Stock, Cm) // If already installed you may skip this
6.1.Flash kernel(FOR CM) http://d-h.st/Bqa
6.2.Flash kernel(FOR AOSP(Stock too) http://d-h.st/7V8
6.3.Flash kernel(FOR Purity) http://d-h.st/2Yz
7.Reboot in and go through the setting
Code:ANOTHER KERNELS [LIST=1] [*] [URL="http://forum.xda-developers.com/showpost.php?p=50947848&postcount=102"]Franco kernel F2FS[/URL] [*] [URL="http://forum.xda-developers.com/showthread.php?t=2524557"]Bricked Kernel[/URL] [/LIST]
Code:OLD KERNELS(CM) [LIST=1] [*] [url]http://d-h.st/Snw[/url] 03-03-2014 [*] [url]http://d-h.st/kGE[/url] 03-05-2014 [*] [url]http://d-h.st/aWU[/url] 03-17-2014 [*] [url]http://d-h.st/GvP[/url] 03-27-2104 [/LIST]
Code:OLD KERNELS(AOSP) [LIST=1] [*] [url]http://d-h.st/6w5[/url] 03-06-2014 [*] [url]http://d-h.st/GCb[/url] 03-27-2014 [/LIST]
Code:OLD RECOVERY's [LIST=1] [*] [url]http://d-h.st/X8v[/url] 03-03-2014 [*] [url]http://d-h.st/p7u[/url] 03-08-2014 [*] [url]http://d-h.st/sbk[/url] 03-17-2014 [*] [url]http://d-h.st/a0x[/url] 03-27-2014 [/LIST]
For Developers
AOSP-F2FS kernel
CyanogenMode-F2FS kernel
Purity-F2FS kernel
Device patches
https://github.com/dennes544/androi...mmit/da7287a70eda7363b28013ac15e8cc899ef0b0a3
https://github.com/dennes544/androi...mmit/534542f9fc89107afba2cb967ac40fed032f6e7f
https://github.com/dennes544/androi...mmit/a947b29ed4fead6618e358cdc0314916639fa024
https://github.com/dennes544/androi...mmit/b1dd255793efdc5dcce4ca60e725c406acc7e868
https://github.com/dennes544/androi...mmit/01584fdec616856da33a47e4f07e0bdf40d0f03a
AND use this patch for f2fs-tools
f2fs-tools you can take here
And use ONLY omnirom's recovery(because only omnirom's recovery have "inline_xattr" patch)
Support me Buy me a juice Click!27For clearification, the kernels I maintain are not intended for day to day usage. My goal is to bring as much of Jaegeuk Kim's native linux f2fs code to the android kernel. This is a hobby. I'm just trying to do something productive while learning more.
Change Log:
- Added r47
- Clean up post
- Added r46
- Created nightlies-f2fs github branch
- Added r44 with flush_merge enabledCode:$ git clone -b nightlies-f2fs https://github.com/koe1974/hammerhead.git $ make franco_f2fs_defconfig $ make
- All data moved to github
- Created git repository koe1974 on github
- Attached patches as one tar.gz
- Merged more original source code into android port source code
- Updated to r37 including patched f2fs for debugging
- Attached patch to update f2fs with Jaegeuk Kim's dev repository commits
- Replaced patch for r35 with patch for r36
- Updated to r36
- Attached Bonnie++ benchmark results as graphs
- Attached r35 patch file to post
- Updated to with r35
- Added F2FS to r34 kernel source
- Modified fstab.hammerhead in ramdisk
Notes:
- AOSP ROM support only
- NO CM ROM support
- I don't take requests
- Thanks appreciated
Follow the directions in the OP.
( Download r47 )
( Download r46 )
( Download r44 )
( Download r38 )
( Download r37 )
( Download r36 )
( Download r35 )
( Download r34 )18Just before anyone jumps into this headfirst, make sure you understand what it is, as the OP is a bit spartan.
http://en.wikipedia.org/wiki/F2FS9Be very careful when using f2fs... Basically it's very very fast, BUT you are stuck with it. You can't flash other kernels, and you can flash only certain roms that support f2fs, otherwise the rom reformats the system partition to ext4. I had this on my galaxy s3, and it got me in tons of trouble when I tried to flash anything to it. I had to go back to stock twice and restore my efs partition... It's a lot of work basically.
New posts
-
Question Does Redmi Note 10S (Rosemary) support seamless system updates?- Latest: tasdikbyousuf
