[RECOVERY][KERNELs] Recovery and Kernel for F2FS 31/03/14 - Nexus 4 Original Android Development

Recovery and Kernels for F2FS
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.
Instructions:
I tested this procedure with SlimKat so my advice is to start with a working SlimKat rom or another rom that is reported to work good.
We have to Format our memory with F2FS. We need a "special" TWRP and a compatible kernel.
Compatible Kernel:
MiRaGeKernel-mako-F2FS-140331.zip
SlimKernel-mako-F2FS-140331.zip
(All credits to authors. I have only made them compatible with F2FS)
Download compatible Kernel
Download "special" TWRP openrecovery-twrp-2.7.0.0-mako-F2FS.img
Copy Kernel on Phone
Flash Kernel with your current Recovery
Flash "special" TWRP with Fastboot
Reboot in Recovery
Go to Wipe Menu and press Format Data (The Big BUTTON!) (You will LOSE all your Data! Music, Movies etc!!)
Reboot
(Recovery has a RED back button to remember you that you are using the F2FS recovery!)
Enjoy
Phone is snappy and smooth with F2FS.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To go back:
- Flash a "normal" recovery
- Flash your previous kernel
- Format Data
(Required commit)

legolas93 said:
Recovery and Kernels for F2FS
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.
Instructions:
I tested this procedure with SlimKat so my advice is to start with a working SlimKat rom or another rom that is reported to work good.
We have to Format our memory with F2FS. We need a "special" TWRP and a compatible kernel.
Compatible Kernel:
MiRaGeKernel-mako-F2FS-140331.zip
SlimKernel-mako-F2FS-140331.zip
(All credits to authors. I have only made them compatible with F2FS)
Download compatible Kernel
Download "special" TWRP openrecovery-twrp-2.7.0.0-mako-F2FS.img
Copy Kernel on Phone
Flash Kernel with your current Recovery
Flash "special" TWRP with Fastboot
Reboot in Recovery
Go to Wipe Menu and press Format Data (The Big BUTTON!) (You will LOSE all your Data! Music, Movies etc!!)
Reboot
(Recovery has a RED back button to remember you that you are using the F2FS recovery!)
Enjoy
Apart from Benchmarks phone is snappy and smooth.
To go back:
- Flash a "normal" recovery
- Flash your previous kernel
- Format Data
(Required commit)
Click to expand...
Click to collapse
whtz the benefit of this, plz

abir099 said:
whtz the benefit of this, plz
Click to expand...
Click to collapse
It's built specifically for flash storage, including FS level TRIM which executes the command during every commit and doesn't need to rely on Android's native TRIM which only TRIMs during screen off. It's much faster based on current implementations and etc. The only downside is that F2FS isn't considered "stable" yet. This is why there's not a lot of devices on the market has F2FS out of the box. The only one I know is the Moto X and G.
deltatux

Also work with my HellsDoctor and @ak 's one.

@legolas93 are you going to release an ALL-F2FS version like you did for the nexus 7 2012?

Doesn't seem to have done anything. I followed the op. Running ak newest kernel. Got the right twrp with red back button. Went to wipe went to format typed yes. Operation completes very quickly. Reboot and everything seems to be the same ie all items are still on SD card.
How do I tell if this worked?
Sent from my Nexus 4 using Tapatalk 2

jmtjr278 said:
Doesn't seem to have done anything. I followed the op. Running ak newest kernel. Got the right twrp with red back button. Went to wipe went to format typed yes. Operation completes very quickly. Reboot and everything seems to be the same ie all items are still on SD card.
How do I tell if this worked?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
it worked when there's no data left on your internal, maybe try to wipe data again, and post recovery.log

@legolas93 Did you ported F2FS from which version of Linux?

jmtjr278 said:
Doesn't seem to have done anything. I followed the op. Running ak newest kernel. Got the right twrp with red back button. Went to wipe went to format typed yes. Operation completes very quickly. Reboot and everything seems to be the same ie all items are still on SD card.
How do I tell if this worked?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
This happens to me too. Some installed apps FC after doing this, though.
It is like TWRP does nothing to the phone. Factory resets or classical wiping don't do anything, either.

--

PatrickMac said:
@legolas93 are you going to release an ALL-F2FS version like you did for the nexus 7 2012?
Click to expand...
Click to collapse
I don't think that All-F2FS make us gain a big benefit and we will lose support of all ROMs...etc..
I think it's better to stay with only /data as F2FS in this case, so we can use all ROMs with a very small pain.
jmtjr278 said:
Doesn't seem to have done anything. I followed the op. Running ak newest kernel. Got the right twrp with red back button. Went to wipe went to format typed yes. Operation completes very quickly. Reboot and everything seems to be the same ie all items are still on SD card.
How do I tell if this worked?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Try to follow the procedure flashing one of the two kernel on first post. When you are ok try to flash ak over it!
Use DiskInfo to see if all went good!
guimendes said:
@legolas93 Did you ported F2FS from which version of Linux?
Click to expand...
Click to collapse
It's mainly a dennes54 kernel-work. We are around Linux 3.10+ level..

@legolas93 could you maybe upload another compatible kernel? Seems like these only work for AOSP ROMs and not CAF.... Hellscore's CM kernel (http://d-h.st/u6o) would be awesome ☺
Sent from my Nexus 7 using Tapatalk

Awesome mate I liked f2fs; better storage performance and handling. But only thing holding me back is fewer kernels supporting this filesystem. Can you make matr1x kernel supporting this f2fs?

Thanks. My device is not yet rooted, gonna root it soon. So my question is, after finishing rooting and flashing slimkat like I planned to, can I use the f2fs like instructed or do I need to do anything else?

So anyone can tell me what's the advantage? I read it but didn't get it.

Don't work.... always on ext4 and data not formated... My kernel support f2fs.

barome said:
Don't work.... always on ext4 and data not formated... My kernel support f2fs.
Click to expand...
Click to collapse
Do you mean it does not work with HellsDoctor?
Sent from my AOSP on Mako using Tapatalk
---------- Post added at 06:26 PM ---------- Previous post was at 06:23 PM ----------
@legolas93 Is there a modified CWM recovery image with F2FS support added for this device?
Sent from my AOSP on Mako using Tapatalk

halfbytecode said:
Do you mean it does not work with HellsDoctor?
Sent from my AOSP on Mako using Tapatalk
---------- Post added at 06:26 PM ---------- Previous post was at 06:23 PM ----------
Is there a modified CWM recovery image with F2FS support added for this device?
Sent from my AOSP on Mako using Tapatalk
Click to expand...
Click to collapse
Hells Doctor is comptaible F2FS but this recovery doesn't format data at all... And always ext4 of course

barome said:
Don't work.... always on ext4 and data not formated... My kernel support f2fs.
Click to expand...
Click to collapse
It worked for me. My data was formated. I tried it with the kernels provided in the OP. Your kernel stuck at the bootanimation. So I guess your implementation is different from legolas kernel mods.

PatrickMac said:
It worked for me. My data was formated. I tried it with the kernels provided in the OP. Your kernel stuck at the bootanimation. So I guess your implementation is different from legolas kernel mods.
Click to expand...
Click to collapse
Hmmm... Maybe... I committed same change as @ak so xGenesis must not work too.

Related

[ROM][All-F2FS] OmniROM with All-F2FS support [30/03/14]

OmniROM with "All-F2FS" support​
I have modified OmniROM to work with F2FS partitions. All credits for the ROM to OmniROM guys.
This is for "All-F2FS" that mean that /system, /cache and /data are formatted with F2FS.
This is needed to switch to "All-F2FS".
ROM contains my Kernel with "All-F2FS" support and other goodies.
Ported sl[aou]b from Linux 3.4
Ported timer and workqueue from Linux 3.4
Ported random from Linux 3.13-rc4
Ported rwsem from Linux 3.11
Kernel NEON Mode
Etc..Etc..
Added GPU OC (Franco way..)
Added Toggle for FSYNC
Revert CPU OC things (We don't need it and it was a bit dirty..)
One of the goodies of my kernel is that i was able to reclaim more 18MB of RAM for Android. As you can see in Settings we are now at 993MB.
MultiROM isn't supported as now because i need to patch it to work with "new" ram.
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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
omni-4.4.2-20140329-grouper-NIGHTLY-F2FS: Here
omni-4.4.2-20140312-grouper-NIGHTLY-F2FS: Here
You need a recovery with "All-F2FS" support. So..
To use this ROM read the instructions Here!
Hope i dind't any errors writing this down. I personally tested this procedure.
Enjoy.
First thank you for the rom. Will you update this rom on a weekly basis?
Hey thanks. Will try it today when I get time. Will give feedback, hope u update it at least once every two weeks.
Sent from my Nexus 7 using Tapatalk
Wow.
Held off installing on my Sprint S4 but this looks like the perfect thing to try on my tablet. TYVM.
Can u pls upload somewhere? Media fire is so slow and that is when the download actually starts which it rarely does. Can u upload on g drive or anywhere better like zippyshare.
Sent from my Nexus 7 using Tapatalk
Hi, I have installed this rom and seems to work very fine. But I have only one problem. When i try to install Xposed Framework this message appears. This is related to Rom or SU problem? Thanks
Hey, just flashed the ROM. Followed the procedure point to point except I also flashed ur legokernel and superuser zip cause omni ROM isn't rooted from default and then I formatted everything. Now I rebooted and its stuck on Google logo.
Sent from my GT-I9000 using Tapatalk
Any chance we can get a AOSPAL all-f2fs build? It is the #1 smoothest fastest trouble free ROM I have ever tried on my N7. Please?
http://forum.xda-developers.com/showthread.php?t=2636893
Ya I'm hoping for a AOSPAL ALL-F2FS support as well. This is my current daily driver and might be the one I stick with. Its vary smooth, stable and fast. Also nicely customizable as well.
bhu1 said:
Hey, just flashed the ROM. Followed the procedure point to point except I also flashed ur legokernel and superuser zip cause omni ROM isn't rooted from default and then I formatted everything. Now I rebooted and its stuck on Google logo.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
this was an issue for me as well. i restored the stock nexus 7 software and tried starting from pretty much complete scratch. i'm afraid to reboot because of that, but will give it a shot.
on a related note, i've gotten a system message saying that there's an update for omni-4.4.2-20140313-grouper-NIGHTLY.zip
are updates to be turned off until there's an F2FS update available?
edit: just rebooted, everything rebooted nicely.
wiredout46 said:
are updates to be turned off until there's an F2FS update available?
Click to expand...
Click to collapse
Yes turn them off for now.
I discovered the problem with my procedure. I was using the gapps recommended by omni team that I use with the regular omni ROM, the ones from the PA gapps thread. Those were the problem. Also, Lego kernel isn't working with this ROM, N7 gets stuck on Google logo.
Edit: after a second series of flashes I have came to realise that actually the gapps were also the fine. Its the Lego Kernel that was messing things up. Tried the M-kernel f2fs and that also isn't working and is resulting in a freeze at Google logo. Now I am just gonna give up on kernels and just flash omni ROM, gapps and superusers.
Sent from my GT-I9000 using Tapatalk
bhu1 said:
I discovered the problem with my procedure. I was using the gapps recommended by omni team that I use with the regular omni ROM, the ones from the PA gapps thread. Those were the problem. Also, Lego kernel isn't working with this ROM, N7 gets stuck on Google logo.
Edit: after a second series of flashes I have came to realise that actually the gapps were also the fine. Its the Lego Kernel that was messing things up. Tried the M-kernel f2fs and that also isn't working and is resulting in a freeze at Google logo. Now I am just gonna give up on kernels and just flash omni ROM, gapps and superusers.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
same with xperience.
all i want is doubletap2wake:cyclops:
---------- Post added at 05:26 PM ---------- Previous post was at 05:00 PM ----------
gorneman said:
Hi, I have installed this rom and seems to work very fine. But I have only one problem. When i try to install Xposed Framework this message appears. This is related to Rom or SU problem? Thanks
Click to expand...
Click to collapse
in for an answer on this.
bhu1 said:
I discovered the problem with my procedure. I was using the gapps recommended by omni team that I use with the regular omni ROM, the ones from the PA gapps thread. Those were the problem. Also, Lego kernel isn't working with this ROM, N7 gets stuck on Google logo.
Edit: after a second series of flashes I have came to realise that actually the gapps were also the fine. Its the Lego Kernel that was messing things up. Tried the M-kernel f2fs and that also isn't working and is resulting in a freeze at Google logo. Now I am just gonna give up on kernels and just flash omni ROM, gapps and superusers.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
As has been said before legokernel and m-kernel and all the other kernels as far as I know are NOT ALL-F2FS supported yet. They are only F2FS on the data partition. This OmniROM will not work with those kernels until someone can modify them to work with ALL the partitions formatted to F2FS file system a.k.a ALL-F2FS. No one has done that yet...
Sent from my Nexus 7 using Tapatalk
I flashed rom with Pa Gapps and i am stuck at google screen also. Any advice?
Deleted
Thanks for the rom. Overall the n7 has become much snappier than it used to be. Is there anyway to revert the theme of the playstore back to the stock theme? I don't like it. Some texts are not readable
Sent from my Nexus 7 using Tapatalk
rlivin said:
I flashed rom with Pa Gapps and i am stuck at google screen also. Any advice?
Click to expand...
Click to collapse
i did the same and got the same result, flashed slim aio gapps and it worked perfectly fine.
Thanks for the rom, it is great!
smoother the stock omni rom
gorneman said:
Hi, I have installed this rom and seems to work very fine. But I have only one problem. When i try to install Xposed Framework this message appears. This is related to Rom or SU problem? Thanks
Click to expand...
Click to collapse
I've never had experience with this filesystem but have had similar messages when using inbuilt superuser on their ROMs.
I would suggest using the latest SuperSu as it's complaining it can't use the mount and copy commands which do need root.
Sent from my Nexus 7

[MOD] MultiROM v33b

Introduction
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is one-of-a-kind multi-boot mod for Oneplus One. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
You can install it either from MultiROM Manager app or from this guide:
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM - download the ZIP file from second post and flash it in recovery.
Modified recovery - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.​
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.​
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.​
3. Firefox OS
Firefox OS is just another Android ROM from MultiROM's point of view, so add it as if it were Android​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/KINGbabasula/android_kernel_oneplus_msm8974
MultiROM device tree - https://github.com/KINGbabasula/android_device_oneplus_bacon​
Thanks a lot to Tasssadar for creating this awesome utility.
Thanks to ATMOSF3AR for his Oneplus One template
XDA:DevDB Information
MultiROM, Tool/Utility for the OnePlus One
Contributors
KINGbabasula
Source Code: https://github.com/Tasssadar/multirom
Version Information
Status: Stable
Current Stable Version: 33
Created 2014-08-02
Last Updated 2016-04-17
Reserved
Downloads
1. Main downloads
MultiROM: Zip
Modified recovery (based on TWRP): recovery.img
Kernel with kexec hardboot patch:
Supported kernels: AK, Furnace
You need to have kernel with kexec-hardboot patch only in primary ROM
Nicely ask your kernel developer to merge this https://github.com/KINGbabasula/and...mmit/af5ef3d76f863f02c51cf860702b01536620ebf5.​
3. Uninstaller
MultiROM uninstaller: Zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.​
Reserved
FAQ and other notes
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.​
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.​
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.​
Where can I find files from other ROMs?
http://forum.xda-developers.com/showpost.php?p=58563378&postcount=1864​
Can I have different versions of Android working alongside? How to use KitKat and Lollipop at the same time?
Yes. The systems are separated.
guide on Kitakt + Lollipop: http://forum.xda-developers.com/one...ips-tricks-t3027926/post58776196#post58776196​
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.​
The boot animation shows after a few seconds on primary ROMs, why?
Because the framebuffer gets blanked for a few seconds after it gets closed by MultiROM.​
Can I use MultiROM without root?
Yes, if you don't use MultiROM Manager app but flash everything manually​
Will I get OTAs when I have MultiROM installed? Do I lose secondary ROMs after an OTA?
Probably not, you will have to install them manually and you'll have to reinstall MultiROM
No, you won't lose secondary ROMs​
My secondary ROM doesn't boot, what should I do?
Probably you forgot to inject current boot sector once, MultiROM didn't run, so /data SELinux context is set to secondary ROMs that are in /data/media so secondary /system has /data contexts.
Go into recovery Advanced > MultiROM > List ROMs > Choose the non booting ROM > Run restorecon
This will fix SELinux contexts and the ROM will boot again​
Help Videos
Install MultiROM
Install OxygenOS as secondary ROM
Amazing, thank you bro!
Amazing! Reserved for impressions!
Woot !!!!!!! Donation incoming, as promised
Also, what kernel is yours based on ?
And finally, is it compatible with official multirom manager ?
Edit : Donation done : 2D0766769R4457313
bud77 said:
Woot !!!!!!! Donation incoming, as promised
Also, what kernel is yours based on ?
And finally, is it compatible with official multirom manager ?
Click to expand...
Click to collapse
My kernel is cm11 (not cm11s)with kexec. So it won't work on cm11s, Paranoid android and cm11s based roms.
Tomorrow is the last time I'll use pc before leaving so I may add support in multirom manager and build an unofficial version of the app because it's not officially supported
Thanks, again !
Did you try to get in touch with @Tasssadar for the frame buffer issue ?
bud77 said:
Thanks, again !
Did you try to get in touch with @Tasssadar for the frame buffer issue ?
Click to expand...
Click to collapse
I tried on hangouts but I guess he doesn't use it. I think I should port a few things from TWRP into MultiROM because it seems they use the same way of rendering images.
Thank you very much for your efforts,
That is really nice to have, am looking forward to use it. If the Multirom Manager app is usable here, will it be possible to install Ubuntu Touch or has it first to be ported to this phone? Just asking because I always wanted to try out Ubuntu...
dansou901 said:
That is really nice to have, am looking forward to use it. If the Multirom Manager app is usable here, will it be possible to install Ubuntu Touch or has it first to be ported to this phone? Just asking because I always wanted to try out Ubuntu...
Click to expand...
Click to collapse
First we need a working ubuntu touch port. I don't think it will be too hard to do. The opo is very similar to nexus 5
nfl46 said:
Anyone got everything up and running yet? Attempting to install MR now.
Click to expand...
Click to collapse
I'm just about to start doing this...
---------- Post added at 04:32 PM ---------- Previous post was at 04:12 PM ----------
OK, multibooting ColorOS and MIUI doesn't work, will continue testing with other ROMs...
---------- Post added at 04:37 PM ---------- Previous post was at 04:32 PM ----------
And another thing... For me boot menu is visible...
dansou901 said:
I'm just about to start doing this...
---------- Post added at 04:32 PM ---------- Previous post was at 04:12 PM ----------
OK, multibooting ColorOS and MIUI doesn't work, will continue testing with other ROMs...
Click to expand...
Click to collapse
That's because you need a kernel with kexec hardboot patch in secondary rom too. So you need a special kernel for color os and a special one for miui. You may try instlling the rom choosing "share kernel" option so it will use main rom kernel which has kexec
dansou901 said:
I'm just about to start doing this...
---------- Post added at 04:32 PM ---------- Previous post was at 04:12 PM ----------
OK, multibooting ColorOS and MIUI doesn't work, will continue testing with other ROMs...
---------- Post added at 04:37 PM ---------- Previous post was at 04:32 PM ----------
And another thing... For me boot menu is visible...
Click to expand...
Click to collapse
WHAT! I have black screen :|
KINGbabasula said:
WHAT! I have black screen :|
Click to expand...
Click to collapse
Maybe it is because you have CM 11 kernel installed? With ColorOS kernel it works...
dansou901 said:
Maybe it is because you have CM 11 kernel installed? With ColorOS kernel it works...
Click to expand...
Click to collapse
Surely I have something wrong in the kernel. Thanks for telling me that
If I try to share kernel between ColorOS and MIUI, MIUI won't boot (black screen after selecting it from the boot menu)...
dansou901 said:
If I try to share kernel between ColorOS and MIUI, MIUI won't boot (black screen after selecting it from the boot menu)...
Click to expand...
Click to collapse
Well that's expected because they use different kernels. The solution is to compile miui kernel with kexec patch and color os kernel with kexec patch. I tried only cm based roms. I'm on cm11 and I can boot slim and mahdi sharing kernel
OK, so we have to find kernel sources from Color OS and MIUI for this to work...

[Online v13] Blitz Rom v13[Base XenonHD + DarkNel Kernel = Very Good battery life]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well here I bring this XenonHD rom on this terminal base, the name comes according to the rom as it has made the rom is faster than lightning. (Sorry for mi English!!!)
Disclaimer: Only you are responsible for your device/ and anybody elses you've used..​
OFFICIAL SITE SUPPORT IN ENGLISH AND SPANISH!!!
V13​
REQUIRED THE 3 WIPES
Compiled from the source XenonHD
Updated firmware to day 20/02/2015
Liteada the fullest.
Darknel Kernel AOSP-CM12 rev.3.v.0.0.5. Official kernel thread (in English and Spanish Support) More information about the kernel HERE
New gapps minimum , just enough to run the play and optimized the app store services google for less consumption .
Nova Launcher
New Font : Helvetica, thank you @latenightchameleon
CameraNext Modded, thank you @abhi08638
Theme RRO
MaxxAudio.
Performance Tweaks in init.d and build.prop
IMPORTANT : When installing the rom install zip from UKM for sypnase and lower sypnase playstore app , if you see that the minimum frequency to 268mhz not go to the hotplug section and change the mpdecision by MSM_MPDECISION accept change and lower the minimum to 268mhz, and ready to accept those changes.
Instructions:
1. Download Zip
2. Go into Recovery. Backup System/Data/Cache
3. Wipe Everything Except Internal SD
4. Flash Rom and Gapps (optional add-ons also)
5. Reboot and Enjoy!
MAKE YOUR DONATION HERE​
Download:
Blitz Rom v13
Blitz Rom v12
Blitz Rom v11 EXT4
Blitz Rom v10 F2FS
Blitz Rom v10 EXT4
Blitz Rom v8 F2FS
Blitz Rom v8 EXT4
Blitz Rom v7 F2FS
Blitz Rom v7 EXT4
Blitz Rom v6 F2FS
Blitz Rom v6 EXT4
MIRROR
Credits:
@ak
Cyanogenmod
AndroPlus
To all who trust in darksideteam
My github
Signature rom
Firrrrst much alohas bradah for this
Sent from my One A0001 using Tapatalk
Well Got to be second... Will be checking it out...
Sent from my iPad using Tapatalk
Love to try kernel out but hard time with links they all look lock logined and all got ROM DL but want kernel sep also much alohas
Sent from my One A0001 using Tapatalk
Kernel only official site
ART runtime
Great ROM!..can ART runtime be enabled on this ROM? Cant find it in developer tools
Treid installing ext4 but no go error in begin binary error FYI really want to give this a drive kernel is sick
Sent from my One A0001 using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:47 PM ----------
Sbong what version did you flash and what recovery are u using thanks
Sent from my One A0001 using Tapatalk
Great ROM and amazing kernel!!! Nice to see you here friend.
---------- Post added at 03:05 AM ---------- Previous post was at 02:59 AM ----------
sbong said:
Great ROM!..can ART runtime be enabled on this ROM? Cant find it in developer tools
Click to expand...
Click to collapse
No ART friend. Dalvik is super optimized here. I have long been using this ROM and KERNEL combo and it is amazing!!! Test because you will not regret.
Redownloaded and same thing updater binary failed in install FYI
Sent from my One A0001 using Tapatalk
Working flawlessly since day 0. The best rom I've tried for my Oneplus and the Darknel kernel is also a Must Have!
d13guit0 said:
Working flawlessly since day 0. The best rom I've tried for my Oneplus and the Darknel kernel is also a Must Have!
Click to expand...
Click to collapse
Couldn't see where to translate. I only read engles'. What rom do you prefer? ANd what gapps do I flash with this? Thanks for any help thrown my way!
these are my results with the rom
rayandreas said:
Couldn't see where to translate. I only read engles'. What rom do you prefer? ANd what gapps do I flash with this? Thanks for any help thrown my way!
Click to expand...
Click to collapse
I use f2fs version and flash any gapps do you prefer
What version are you using ext or f2fs
Sent from my One A0001 using Tapatalk
f2fs right now [emoji6]
Do you have to do anything g different from the reg ext4 never used f2fs before lol much alohas
Really want to try but got error with ext4 oh what recovery you running too
Sent from my One A0001 using Tapatalk
d13guit0 said:
f2fs right now [emoji6]
Click to expand...
Click to collapse
I am only getting to the one + screen after booting up and I have let it sit for over 10 min. I did everything told in OP. wiped everything except internal sd. Am I doing something wrong?
otisman said:
Do you have to do anything g different from the reg ext4 never used f2fs before lol much alohas
Really want to try but got error with ext4 oh what recovery you running too
Sent from my One A0001 using Tapatalk
Click to expand...
Click to collapse
I'm using Philz recovery modded by @ak to work with f2fs. U need to flash everything with usb-otg, sideload or fastboot because you'll wipe data partition.
The procedure is:
Flash modded f2fs recovery & reboot recovery
Go to wipe and format option / Custom Format Option and click toggle f2fs <-> ext4 migration.
Format /system and choose f2fs option
Format /data (any f2fs or ext option is showed)
Format /cache and choose f2fs option
Format /data and /data/media (sdcard) and choose f2fs option
Flash rom and UKM
Reboot
Install synapse from play store to manage Darknel Kernel
Enjoy the speed of Blitz [emoji12]
Nameless has removed ART in runtime selection under developer setting.
Will try this rom soon.
So happy that we are given so much gifts every week.
Sent from my A0001 using Tapatalk
personally I don't find necessary art runtime because dalvik is very optimized in this rom. Also we'll have android L soon and everything will change [emoji16]
I think Darknel kernel included into Blitz v6 is rev.1.v.0.1.7 but there's an updated rev.1.v.0.2.1 version in the official team site

[ROM][6.0][Shamu][OCT 14] Euphoria-OS 2.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[B][COLOR="Red"][CENTER]Your warranty is now void. JK, this is NEXUS no voided warranties here![/COLOR][/B]
I am not responsible for bricked devices,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.[/CENTER]
Please note the following:
Sound and video play back work flawlessly.
Kernel does not force encryption and will format all data if you flash on top of a forced encryption kernel. This means you must backup all internal and SD storage onto a PC. It will wipe data, downloads, pictures, everything!
Report Bugs Here!
Installation instructions
Installing Euphoria-OS for the first time, or coming from another ROM:
- Make sure you're running a proper working ClockworkMod-Recovery/Team Win Recovery Project - WITH SELINUX SUPPORT!
- Copy GApps, Kernel, SuperSU, and ROM ZIP to your SDCard
- If you are running an encrypted kernel, your data will be encrypted on first boot
- If you are running an unencrypted kernel, your data will remain unencrypted
- Boot into Recovery
- Be sure you're on the latest bootloader and radio for M
- DO A DATA WIPE / FACTORY RESET
- Flash Euphoria-OS zip from SDCard
- Flash GApps zip from SDCard
-If you want root you will need to flash a permissive kernel, then flash SuperSu
- Reboot
- Don't restore system data using Titanium Backup!
Upgrading from an earlier version:
- Copy the ROM ZIP to your SDCard
- Boot into Recovery
- Flash the ROM zip from SDCard
- Reboot
Features
*AOSP 6.0 Marshmallow Base
*DT2W
*DT2Sleep on Nav Bar
*Quick Settings
*Brightness Slider
*4 Tiles Per Row
*Quick Pulldown
*Vibrate on tile touch
*LED Lights
Rom Reviews
https://www.youtube.com/watch?v=cLi1yXeGBcE - thanks Mike Barrett
https://www.youtube.com/watch?v=mojXg1zU8YM - thanks @Cm9aphla
Known Issues
Thanks to:
First and most important thanks to Mahdi786
manelscout4life
Moose0704
teeseeuu
dr87
blazze11 - for bootanimation and drawables
TechXero for letting us use his server
eurochild - for providing us awesome graphics
hellsgod - for providing hells as our kernel base
Imoseyon
flar2
Slim-Roms
CM
Donor List
Thanks for the Donations (random order):
@zmeeed1
@oak
@schoolsux
@OrionBG
@androidfilesharing
@Phamwich
@old_fart
@Mauijpm
@itsmmm
@fegone
@captiv123
Follow Us!
Github
PushBullet
Downloads
AndroidFileHost
Euphoria Kernel
XDA:DevDB Information
Euphoria-OS, ROM for the Nexus 6
Contributors
dsmitty166, Mahdi786, manelscout4life, teeseeuu, eurochild
Source Code: https://github.com/Euphoria-OS
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Beta
Current Stable Version: 2.0
Created 2014-11-27
Last Updated 2015-10-16
Changelog
Changelog- Latest Version
Changelog Full
Frequently Asked Questions:
**How do I upgrade to 5.1**
- If you are coming from any 5.0.x ROM, or 5.1 other than Euphoria, it is suggested that you flash the latest radio and bootloader.
- If you are coming from Euphoria 5.1 you can dirty flash, if coming from ANYTHING else you must clean flash.
1. Download euphoria 5.1, a 5.1 set of gapps, and any radio or bootloader
2. Reboot into recovery
3. Wipe data
4. Flash radio and bootloader
6. Flash ROM and gapps
5. Reboot
** I have terrible battery **
Check your device for wake locks, if it's Google services then:
1. Disable keep awake and wake up in privacy gaurd.
2. In disable service app, disable the usual configfetchservice and configservice. Leave system update service enabled
** I have no voice on calls **
Please update to the latest appropriate radio
** I can't use Google Now Launcher **
Seems there's a bug with compatibility with banks gapps, use another for now
** I can't install any cm12 themes **
You probably flashed a kernel that breaks theme compatibility. Please use the included or a supported kernel, or ask your kernel dev to update his ramdisk
** I have problem XXX **
Can you replicate it after a clean flash? Honestly, most bugs that you are experiencing come from dirty flashing, or user configuration.
Reserved
Reviews:
https://www.youtube.com/watch?v=cLi1yXeGBcE
Awesome it's here great rom for n4 n5 opo and now n6.
Sent from my Nexus 6 using Tapatalk
I flashed the rom earlier today and first thing I noticed is that the sound and notifications option in the settings crashes when opened.
mhsbrian said:
I flashed the rom earlier today and first thing I noticed is that the sound and notifications option in the settings crashes when opened.
Click to expand...
Click to collapse
Have you done a full wipe? No issues here at all. What did you all flash? More details please.
Awesome. One question. So far, the most confusing aspect of this device is def the whole encryption thing. So I'm on stock now, rooted, running twrp, encrypted (cuz I never unencrypted). So if I flash this ROM, will it wipe my data? And if so, would I then be unencrypted?
Thanks
You don't buy a Mustang for the gas mileage.
Yay! I will flash this one
When you say do a data wipe or be stuck at boot, does that mean "fastboot erase userdata" type of wipe?
---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------
when it says wipe data or youll be stuck at boot does that mean fastboot erase userdata?
pathtologos said:
Awesome. One question. So far, the most confusing aspect of this device is def the whole encryption thing. So I'm on stock now, rooted, running twrp, encrypted (cuz I never unencrypted). So if I flash this ROM, will it wipe my data? And if so, would I then be unencrypted?
Thanks
You don't buy a Mustang for the gas mileage.
Click to expand...
Click to collapse
Yes, if you flash on top of a force-encrypted kernel it will format all data, internal and external. Then you will still be encrypted. First you need to flash the unencrypted kernel, format all user data, and then you can flash this and be unencrypted.
hackahero said:
When you say do a data wipe or be stuck at boot, does that mean "fastboot erase userdata" type of wipe?
---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------
when it says wipe data or youll be stuck at boot does that mean fastboot erase userdata?
Click to expand...
Click to collapse
You only have to do that if you are flashing the unencrypted kernel.
Data wipe in TWRP is needed if coming from a different ROM or STOCK.
A tip to decrypting if you don't really understand is to BACKUP your SD card to the computer. It will erase everything on your device. Pictures, downloads etc.
dsmitty166 said:
Yes, if you flash on top of a force-encrypted kernel it will format all data, internal and external. Then you will still be encrypted. First you need to flash the unencrypted kernel, format all user data, and then you can flash this and be unencrypted.
Click to expand...
Click to collapse
OK, let's say b4 I even flash the ROM, I follow steps in the thread around here to unencrypt, as long as I flash Roms and kernels that DO NOT force encrypt, then I won't have to worry about getting data wiped again in the future, and I'll always be unencrypted?
Thanks for your help man.
You don't buy a Mustang for the gas mileage.
BoOsT said:
A tip to decrypting if you don't really understand is to BACKUP your SD card to the computer. It will erase everything on your device. Pictures, downloads etc.
Click to expand...
Click to collapse
Thanks, added this to the OP
pathtologos said:
OK, let's say b4 I even flash the ROM, I follow steps in the thread around here to unencrypt, as long as I flash Roms and kernels that DO NOT force encrypt, then I won't have to worry about getting data wiped again in the future, and I'll always be unencrypted?
Thanks for your help man.
You don't buy a Mustang for the gas mileage.
Click to expand...
Click to collapse
That is correct!
This is starting to make more sense now. haha ty smitty
So Far So Good on the Rom. I'm Glad you are on LRX21V. I'm curious to see if it will cure some of the LRX21O issues!
Great app for enabling percent battery, until it's included. https://play.google.com/store/apps/details?id=de.kroegerama.android4batpercent
Is video recording working with the camera?
crashercarlton said:
So Far So Good on the Rom. I'm Glad you are on LRX21V. I'm curious to see if it will cure some of the LRX21O issues!
Click to expand...
Click to collapse
V is just the build number bump when they pushed android TV.
Edit: You can see the change logs here http://www.androidpolice.com/2014/1...uild-from-5-0-0_r2-lrx21m-to-5-0-0_r5-lrx21q/
Sent from my Nexus 6 using XDA Free mobile app

[TWRP][ 3.2.3-0 ALE ][ All Versions Huawei P8Lite Alice] - [ 18:59 18-02-2019 ]

[TWRP][ 3.2.3-0 ALE ][ All Versions Huawei P8 Lite Alice]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Based on TWRP 3.2.3 from @MrTapok(4PDA) ( all credits to him ) i mounted TWRP 3.2.3-0 ALE for P8 Lite Alice.
I have done some change and fix the random reboot after 20m, default language is English.
It have the same "Face" then previous one. ( TWRP 3.1.1-0 )
TWRP.3.1.1-2 have double touch to activate like TWRP 3.2.3.
Change log:
27-01-2019 TWRP.3.2.3 now can flash default ROM update.zip file.
18-02-2019 TWRP.3.2.3 now can flash Recovery2 image
Zips below are:
RECOVERY.zip<-LINK - Can be flashed in recovery as stock recovery and in recovery2 as ERecovery
NO.ERECOVERY.zip<- LINK - Can be flashed in recovery and recovery2 as only stock recovery (NO ERecovery mode)
TWRP.3.2.3.ALE.zip - Can be flashed in recovery and recovery2
Boot in recovery: phone off, press vol+ and power at same time
Boot in recovery2: phone off, plug USB on phone and PC, press vol+ and power at same time
Enjoy it!
Thanks to all contributors that helps developing TWRP for P8 Lite:
@surdu_petru, @Dees_Troy, @XePeleato, @OldDroid, TeamWin, @MrTapok(4PDA)
If you like it press thanks and let your comment!
.
Did you base on their sources on github?
I'm not sure if they aren't a bit too old... Does your TWRP support f2fs filesystem and there isn't a reboot issue?
dominj97 said:
Did you base on their sources on github?
I'm not sure if they aren't a bit too old... Does your TWRP support f2fs filesystem and there isn't a reboot issue?
Click to expand...
Click to collapse
No, i dind´t base on their source. I use Twrp 3.1.0-2 structure and Honor 4x main files from TWRP 31.1-0.
I don´t find any reboot issue ...
And yes, it support f2fs filesystem but your kernel must suport it to to use it!
persona78 said:
No, i dind´t base on their source. I use Twrp 3.1.0-2 structure and Honor 4x main files from TWRP 31.1-0.
I don´t find any reboot issue ...
And yes, it support f2fs filesystem but your kernel must suport it to to use it!
Click to expand...
Click to collapse
Yes I know and there are two roms with f2fs support (made by openkirin team ofcourse).
Older version from surdu_petru had a reboot issue during making a backup
Since I installed this recovery, RROS does not work any better and some apps whatsapp does not open anymore
dominj97 said:
Yes I know and there are two roms with f2fs support (made by openkirin team ofcourse).
Older version from surdu_petru had a reboot issue during making a backup
Click to expand...
Click to collapse
I try to format cache and data to f2fs file system and images did not accept this format. Better luck with you.
.
Giuseppe300715 said:
Since I installed this recovery, RROS does not work any better and some apps whatsapp does not open anymore
Click to expand...
Click to collapse
ehm it's recovery. It shouldn't have impact on system unless you did there something.
---------- Post added at 03:36 PM ---------- Previous post was at 03:31 PM ----------
persona78 said:
I try to format cache and data to f2fs file system and images did not accept this format. Better luck with you.
.
Click to expand...
Click to collapse
And you tried rros or los 14.1? Surdu_petru added f2fs support only in nougat kernel
I was using both with /data and /cache in f2fs... well actually on los 14.1 only /data.
Giuseppe300715 said:
Since I installed this recovery, RROS does not work any better and some apps whatsapp does not open anymore
Click to expand...
Click to collapse
The recovery interfering with whatsapp ??? -_-
You know how recovery works, right? If you don´t have done nothing to data and cache, recovery can´t do anything to the apps, right? Is like a Bios in PC, only works if you call it!
.
dominj97 said:
ehm it's recovery. It shouldn't have impact on system unless you did there something.
---------- Post added at 03:36 PM ---------- Previous post was at 03:31 PM ----------
And you tried rros or los 14.1? Surdu_petru added f2fs support only in nougat kernel
I was using both with /data and /cache in f2fs... well actually on los 14.1 only /data.
Click to expand...
Click to collapse
I try in default ROM and is ANdroid 6.
You get more performance in ROM if you format cache to f2fs, it have more read write procedures.
.
persona78 said:
I try in default ROM and is ANdroid 6.
You get more performance in ROM if you format cache to f2fs, it have more read write procedures.
.
Click to expand...
Click to collapse
You said earlier that kernel has to support it
And well you know now that stock kernel doesn't have f2fs support [emoji14]
Sent from my ALE-L21 using Tapatalk
dominj97 said:
You said earlier that kernel has to support it
And well you know now that stock kernel doesn't have f2fs support [emoji14]
Sent from my ALE-L21 using Tapatalk
Click to expand...
Click to collapse
I edited the boot, to try
.
persona78 said:
I edited the boot, to try i only don't know that stock images don't allow that format
.
Click to expand...
Click to collapse
Well if it was possible to make it working on 7.x it's also possible to make it working on 6.0
Sources are on github, but it needs some work and openkirin is working on 7.x now.
dominj97 said:
You said earlier that kernel has to support it
And well you know now that stock kernel doesn't have f2fs support [emoji14]
Sent from my ALE-L21 using Tapatalk
Click to expand...
Click to collapse
Hi!
There was a issue in f2fs formating option, is fixed now!
.
persona78 said:
Hi!
There was a issue in f2fs formating option, is fixed now!
.
Click to expand...
Click to collapse
Make a changelog post too, or write in in the op post Can B600 have f2fs?
D1stRU3T0R said:
Make a changelog post too, or write in in the op post Can B600 have f2fs?
Click to expand...
Click to collapse
Hi!
I only found this issue by using f2fs file format, i don´t know if there is more issues!
And NO, B600 can´t suport f2fs file format, i try it even changing boot.img
.
@persona78
I had this error when I was flashing rros. It flashed without any problem anyway.
Btw. F2FS is working as it's supposed to
dominj97 said:
@persona78
I had this error when I was flashing rros. It flashed without any problem anyway.
Btw. F2FS is working as it's supposed to
View attachment 4156944
Click to expand...
Click to collapse
Some info i think... ?
dominj97 said:
@persona78
I had this error when I was flashing rros. It flashed without any problem anyway.
Btw. F2FS is working as it's supposed to
View attachment 4156944
Click to expand...
Click to collapse
To avoid any issues, you can use now the new update of OpenKirin TWRP 3.1.1-0
Regards,
updated!
Change log:
small issues fixed
add parted tool
update busybox to Busybox v1.26.2-Stericson
@D1stRU3T0R
Hi!
Have you try this version since the last time?
.

Categories

Resources