[KERNEL] ezV2020 Kernel [PIE][OREO][Stock] - LG V20 ROMs, Kernels, Recoveries, & Other Developm

Info
This is a stock based kernel with basic fixes only, i.e static screen fix and added color controls. A pure stock experience without any further enhancements. It is a one-off release, although I may fork it and add some minor features later in a new version. This version will stay fully stock with fixes only.
Why this? In my case custom kernels caused some negative issues. For example I like to connect my second device to my TV using a usbc hdmi dock. This would not work on custom kernels without problems, but does on stock, so I decided to fix this. Others have also reported performance issues I wasn't aware of. Hopefully these are fixed also.
Features
Stock kernel based on US996 Oreo sources (20f)
Dirty Santa fixs applied - Static screen on boot fixed & dual sim issue.
RCTD/Triton - disabled
KCAL added - color controls to fix image retention issue
DYNAMIC FSYNC - faster write speeds due to less error checking thus increasing performance. Toggle on/off in kernel manager.
Boeffla Wakelock Blocker - This does nothing in itself - it just shows a list of wakelocks in your kernel manager that you can now disable.
USB Mass Storage Enabled for DriveDroid.
Installation:
Back up your current boot in TWRP if you wish to easily go back to your current boot.img.
Flash *.zip in TWRP.
No need now to flash magisk as was the case with the beta version.
Downloads
OREO
https://androidfilehost.com/?w=files&flid=309696
PIE
Downloads for : LG V20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Credits
@AndDiSa and @nathanchance , for helping me get started with compiling.
@askermk2000 - for providing the source code for the fixes. I would not be able to provide this without his work.

Reserved

Thanks for this ?
2 questions.
1)
> ForceEncryption" and "dm(avb)verity" removed
What do you mean by this? This can be set by Magisk, do you mean that this sets it to off or removes the ability to set it completely.
2)
> Magisk 20.4 included (for now)
Why is this, I guessing it's related to question one.
I have an official unlocked US996 so I am hesitant to test this but I will post here if I do.

Parasol_Monsters said:
Thanks for this
2 questions.
1)
> ForceEncryption" and "dm(avb)verity" removed
What do you mean by this? This can be set by Magisk, do you mean that this sets it to off or removes the ability to set it completely.
2)
> Magisk 20.4 included (for now)
Why is this, I guessing it's related to question one.
I have an official unlocked US996 so I am hesitant to test this but I will post here if I do.
Click to expand...
Click to collapse
1. Set to off, both.
2. Why is it included....just for convenience. If anyone needs it removed you can just use the magisk uninstaller.
I see no reason why it won't work on official unlock us996 now that I think of it. Give it a try and let us know. Just backup your current boot first.

I'm running it tonight on my H910 with a stock-based but heavily modified Oreo ROM. Switched from MK2000 2.1 beta 34 for the evaluation. Seems to be running fine as far as I can tell so far.
I'll update my status after some run-time. US996 is the same hardware as H910 so the kernels should be fairly interchangeable with similar OS versions.
It's also a best practice to clear cache in TWRP after switching kernels so you may want to add that to your install instructions.

I am wondering if anyone would like to volunteer to test the dual sim functionality of the H990DS. DM me if you would, tks.

hi for the h990 I just flash the us996 version?
cause thats what I did with my h990ss & Its stuck on lg logo

sharon1122 said:
hi for the h990 I just flash the us996 version?
cause thats what I did with my h990ss & Its stuck on lg logo
Click to expand...
Click to collapse
No, you must restore your origional boot partition now.
Please read the OP in full. The thread title states it is for US996 only for the moment.

Hey, I got an H990DS and willing to test for you. Just tell me what you need

@ezzony..can u plz guide me on using Toolchain as i wanted to build the kernel for h918 for MIUI 11ported from MI5 to Fix WIFI driver not loading
...which toolchain are u using plz guide
As i tried Linaro as well as Uber ...both failed to build zimge
I am building using mk2000 source
MI5 uses WLAN as system module in dir system/vendor/lib/modules/qca_cld_wlan.ko
Where as the module is built-in kernel in case of h918
Sir plz guide me fixing the issue ...thanks

pawar21 said:
@ezzony..can u plz guide me on using Toolchain as i wanted to build the kernel for h918 for MIUI 11ported from MI5 to Fix WIFI driver not loading
...which toolchain are u using plz guide
As i tried Linaro as well as Uber ...both failed to build zimge
I am building using mk2000 source
Click to expand...
Click to collapse
I was unable to build mk2000 using the toolchain that was said to be used to build it. You will have to ask the mk2000 dev. I would be curious to know this as well because I tried a few versions of Linaro including the one he said he used but it always failed. I built mine from the original LG source.
Lets leave that there as it's a bit off topic for this thread. Contact me by DM if you have any further query in relation to your issue.

ezzony said:
I was unable to build mk2000 using the toolchain that was said to be used to build it.
Thank u for prompt response n sorry for being off topic
Click to expand...
Click to collapse

pawar21 said:
ezzony said:
I was unable to build mk2000 using the toolchain that was said to be used to build it.
Thank u for prompt response n sorry for being off topic
Click to expand...
Click to collapse
Oh no problem. Btw I'm a noob at this so my knowledge is limited at this stage. I do have a suggestion for you though, I'll DM you.
Click to expand...
Click to collapse

This kernel is not for the H910, I know that; however, I've been testing it heavily for the past 2 days without any major issues. On my H910 though, it corrupts the MicroSD card; It gives me a "fix your SD Card" error and crashes if I try to fix it by formatting the card. I went back to the original BOOT partition and the MicroSD card works fine. As of now, it works pretty much the same as the mk2000 version 2.2. I have installed.
I probably shouldn't be giving any feedback as this kernel is not for the H910, but I want to make sure whether the "card fix issue" is an isolated situation or not. If it is, then there shouldn't be any compromises when testing it on the H910 as well.

Merazomo said:
This kernel is not for the H910, I know that; however, I've been testing it heavily for the past 2 days without any major issues. On my H910 though, it corrupts the MicroSD card; It gives me a "fix your SD Card" error and crashes if I try to fix it by formatting the card. I went back to the original BOOT partition and the MicroSD card works fine. As of now, it works pretty much the same as the mk2000 version 2.2. I have installed.
I probably shouldn't be giving any feedback as this kernel is not for the H910, but I want to make sure whether the "card fix issue" is an isolated situation or not. If it is, then there shouldn't be any compromises when testing it on the H910 as well.
Click to expand...
Click to collapse
The difference between us996 and h910 kernel are minuscule, if fact the differences' are more like 'setting's' than anything fundamental. I recall seeing something about 'crypto sd card' in the config files for the H910 so I'd be 99.9 percent certain the issues is caused by this not being included in the us996 version.
I was waiting for some feedback before I compiled the rest of the variant's ( in case there were any issues or I thought to add something more) but I'll do H910 to make sure this issue with the sd card is fixed. I'll be putting it in a flashable zip this time, perhaps you wouldn't mind testing it for me before I release it fully. I'll send you the dl link by dm in any case when it's done, hopefully later today.

ezzony said:
The difference between us996 and h910 kernel are minuscule, if fact the differences' are more like 'setting's' than anything fundamental. I recall seeing something about 'crypto sd card' in the config files for the H910 so I'd be 99.9 percent certain the issues is caused by this not being included in the us996 version.
I was waiting for some feedback before I compiled the rest of the variant's ( in case there were any issues or I thought to add something more) but I'll do H910 to make sure this issue with the sd card is fixed. I'll be putting it in a flashable zip this time, perhaps you wouldn't mind testing it for me before I release it fully. I'll send you the dl link by dm in any case when it's done, hopefully later today.
Click to expand...
Click to collapse
I restored my TWRP backed-up BOOT partition and my MicroSD card worked again. I then flashed the "ezV2020_us996_beta1" image from TWRP, and got the same "SD corrupted tap to fix" message as before. Went back to TWRP and installed the "H910_ezV2020_beta_1.0" zip file, followed by Magisk, then wiped davlik/cache and rebooted. I'm still getting the "SD corrupted tap to fix", and Magisk uninstalled from my phone and won't install through TWRP or manually from the Manager anymore. I had to restore the boot, system, and data partitions from a TWRP backup to get everything up and running again. I should have mentioned I'm using Alpha Omega Oreo, but since it's a Stock ROM, I assumed it was compatible.

Merazomo said:
I restored my TWRP backed-up BOOT partition and my MicroSD card worked again. I then flashed the "ezV2020_us996_beta1" image from TWRP, and got the same "SD corrupted tap to fix" message as before. Went back to TWRP and installed the "H910_ezV2020_beta_1.0" zip file, followed by Magisk, then wiped davlik/cache and rebooted. I'm still getting the "SD corrupted tap to fix", and Magisk uninstalled from my phone and won't install through TWRP or manually from the Manager anymore. I had to restore the boot, system, and data partitions from a TWRP backup to get everything up and running again. I should have mentioned I'm using Alpha Omega Oreo, but since it's a Stock ROM, I assumed it was compatible.
Click to expand...
Click to collapse
Sorry this has caused you a headache.
I have looked into this and can say with certainty that the issue is that your SD card is formatted in a type that is not supported by stock kernel i.e most likely exFat. Support for exFat would have been added to the custom kernel you were using. I have tested this myself by formatting a spare sd card in exFat and got the same 'corrupted' error. My own SD card is formatted in Fat32 and works fine with ezv2020. Therefore anyone who does not use exFat SD card will not experience any problem.
I do not know what caused the Magisk problem but it can be a bit funny sometimes. Glad you kept a backup handy.

H910 version is up, link in OP. It is a flashable zip this time, not an .img. Flash Magisk and wipe davlik/cache before rebooting.

ezzony said:
Sorry this has caused you a headache.
I have looked into this and can say with certainty that the issue is that your SD card is formatted in a type that is not supported by stock kernel i.e most likely exFat. Support for exFat would have been added to the custom kernel you were using. I have tested this myself by formatting a spare sd card in exFat and got the same 'corrupted' error. My own SD card is formatted in Fat32 and works fine with ezv2020. Therefore anyone who does not use exFat SD card will not experience any problem.
I do not know what caused the Magisk problem but it can be a bit funny sometimes. Glad you kept a backup handy.
Click to expand...
Click to collapse
No worries. That's what testing is for. I've almost bricked my phone hundreds of times, so I'm used to restoring to stock and rooting again. And yes, I always format my MicroSD cards as exFat; I have a few 6GB mkv Movies on my card, so I kind of have to.
But unless I'm mistaken, the Stock kernel of the V20 should be able to use exFat. As I stated before, I've been on the brink of rendering my phone useless for messing around trying MODs and stuff many times. The only constant has been my MicroSD card formatted as exFat; I've ended up with a Stock H910 on Nougat and Oreo plenty of times without removing the card, and it's always readable. I don't want to state that as a fact because it's been a while since I've fully returned to Stock and re-rooted, but that's what I remember, my exFat formatted card working with Stock unrooted Nougat and Oreo. Maybe someone can confirm that, and if I'm wrong, then I'm sorry.

Merazomo said:
No worries. That's what testing is for. I've almost bricked my phone hundreds of times, so I'm used to restoring to stock and rooting again. And yes, I always format my MicroSD cards as exFat; I have a few 6GB mkv Movies on my card, so I kind of have to.
But unless I'm mistaken, the Stock kernel of the V20 should be able to use exFat. As I stated before, I've been on the brink of rendering my phone useless for messing around trying MODs and stuff many times. The only constant has been my MicroSD card formatted as exFat; I've ended up with a Stock H910 on Nougat and Oreo plenty of times without removing the card, and it's always readable. I don't want to state that as a fact because it's been a while since I've fully returned to Stock and re-rooted, but that's what I remember, my exFat formatted card working with Stock unrooted Nougat and Oreo. Maybe someone can confirm that, and if I'm wrong, then I'm sorry.
Click to expand...
Click to collapse
It seems it was me that was mistaken. Well I said I was only 99.9% certain
I have fixed the issue. Could you confirm when you have a chance. Also wiping davlik cache seems to cause a weird issue after reinstalling Magisk. I tried again by just just flashing Magisk and that was fine, so don't wipe.
I'll update US996 when I have a chance.

Related

[TWRP_Recovery_2.8.7.0][Unofficial][quincyatt]

I wanted to post this here since I've been busting my tail on an update for a week now. This WILL flash, Backup & Restore android 4.4 roms! USB mounting, internal & external sdcard mounts as well. There are still a few bugs to work out but give it a go & some feedback. It's still a WIP but plenty stable to use daily for now.
Also anyone interested in flashing the CandyKat sweetener packs, you may now do so with this recovery!!
TWRP 2.8.7.0​
I am not responsible for misuse, bricks, or exploding devices! Flash at your own risk! You can download the zip file & flash it from within your existing recovery & reboot to recovery.
CREDITS: Javelinanddart for fixing mounts, f2fs, & for fixing vibration for 5.0 & up Disconnecktie && Santod040 I have bugged these guys to death to get this working so Please stop in & thank these guys as well. They are a huge part of the success of this! Obviously this couldn't happen without Omniroms Source! And a huge thanks for
Dees_Troy for his guide to compiling twrp recovery!!
TWRP Themes have changed a bit & if you use a them then you'll want to checkout this link.
THEMING TWRP THE NEW WAY!
What's new in 2.8.7.0
- Initial ground work for software drawn keyboard (_that)
- Fix handling of wiping internal storage on datamedia devices (xuefer)
- Allow DataManager to set and read values from the system properties (xuefer)
- Fix crash when taking screenshots on arm64 devices (xuefer)
- Fix error message after an ORS script completes (Dees_Troy)
- Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
- Add system read only option - more details below (Dees_Troy)
- Add resize2fs and GUI option to run resize2fs (Dees_Troy)
- Fix crash loop caused by empty lines in AOSP recovery command file (_that)
- Prevent duplicate page overlays such as multiple lock screens (mdmower)
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won't prompt to install SuperSU and TWRP won't try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don't take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
THEMING?
USE 1080P THEMES
Yeah!!
This is working perfect! Damn I missed TWRP. So freaking sweet!!
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Works well except mount memory
Liwais said:
Works well except mount memory
Click to expand...
Click to collapse
Mounting which partition? Anyone that finds an error or a bug should try posting the recovery log after said error. Don't post the entire log in a post but put it on pastebin or something similar. Having the logs greatly increases the likely hood the issue will be fixed. Thanks.
Liwais said:
Works well except mount memory
Click to expand...
Click to collapse
What do you mean by mount memory? Where you add something from the pc to the sd card & it shows up on the internal when in twrp? The internal sd card mounts when connected to the pc, not the external sd. I don't know if that's how it's suppose to work or not. This is my first twrp attempt and I had to build it from scratch basically. Like Disconnecktie stated, a log may be helpful.
Great work. Missed TWRP. Just had to tick off my internal sd. Panicked when my partition wasn't visible with my ROMs to flash. LOL.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
I had in mind when're in rekaveri not mount the memory to your PC
Maybe this Problem just me, let me know
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
gimmeitorilltell said:
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
Click to expand...
Click to collapse
For some reason (most likely that I'm a dummy, or missed reading somewhere)
Recently my SD card took a poo, so I've been saving to internal memory.
I flashed TWRP. When I look in sdcard I have no files visible. When I am booted into CandyKat I can see my files with my file explorer. Am I missing a valid mount somewhere? When I go to / I don't see a folder called storage, and in my /sdcard all I see is a folder called TWRP which is empty.
THanks!
skearton said:
For some reason (most likely that I'm a dummy, or missed reading somewhere)
Recently my SD card took a poo, so I've been saving to internal memory.
I flashed TWRP. When I look in sdcard I have no files visible. When I am booted into CandyKat I can see my files with my file explorer. Am I missing a valid mount somewhere? When I go to / I don't see a folder called storage, and in my /sdcard all I see is a folder called TWRP which is empty.
THanks!
Click to expand...
Click to collapse
When you are in TWRP recovery are you selecting "Internal SDcard" or "MicroSD card"
Edit: Latest twrp recovery with vibrations enabled!
gimmeitorilltell said:
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
Click to expand...
Click to collapse
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
developweb said:
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
No it was not. I've been waiting on more feedback from the update or any of my twrp builds. Now that I'm aware of it, I'll look into that so we can get it official in Bigbiffs twrp thread. I think it's close enough for him to release it as an official but this is my personal feelings. It'll be a couple days maybe before I get back to it since I've spent the last week concentrating on this, it's time for me to move on to other things for a moment.
Sent from my HTC One Max using Tapatalk!
Newest build is working g sweet gimme. Love how ya added the button vibrate too. So far I've done 3 full wipes/flashes and your twrp has been flawless thanks for bringing this to us gimme.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
developweb said:
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
We can probably keep this here until the bugs are worked out. Have you tried the latest here yet? I don't theme my recovery but I'm willing to so I can get it correct.
Also that may be something you can set in twrp, set a different default path for themes but I'm not 100% sure.
gimmeitorilltell said:
We can probably keep this here until the bugs are worked out. Have you tried the latest here yet? I don't theme my recovery but I'm willing to so I can get it correct.
Also that may be something you can set in twrp, set a different default path for themes but I'm not 100% sure.
Click to expand...
Click to collapse
Default path in latest is correct now. Themes work from the correct directory now (/sdcard/TWRP/theme/ui.zip ) so they won't get deleted. Love button vibration as well! Excellent work.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
developweb said:
Default path in latest is correct now. Themes work from the correct directory now (/sdcard/TWRP/theme/ui.zip ) so they won't get deleted. Love button vibration as well! Excellent work.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
Thank you for the feedback, it is very much appreciated! If you run into anything else, good or bad, Please feel free to give a shout out. I have OCD and with the vibration as an option, well it just was NOT an option to NOT work.. Lol
gimmeitorilltell said:
Thank you for the feedback, it is very much appreciated! If you run into anything else, good or bad, Please feel free to give a shout out. I have OCD and with the vibration as an option, well it just was NOT an option to NOT work.. Lol
Click to expand...
Click to collapse
I tried to install the full aroma rom patch by pollution and it seemed to work but gave com.android.phone error on boot. So I thought easy fix, I'll restore the backup I made with TWRP yesterday and got even more errors. Yes, I factory reset before restoring. It seems that this TWRP is not doing everything like it used to under the 4.2's. I'm going to go back to CWM and restore a CWM backup, regroup, recharge.......and try again from scratch to test this thing out again. Wish me luck.
Liwais said:
I had in mind when're in rekaveri not mount the memory to your PC
Maybe this Problem just me, let me know
Click to expand...
Click to collapse
I'm not sure that I understand what you're saying? The internal sd mounts to the pc once you go into twrp & mount it.
developweb said:
I tried to install the full aroma rom patch by pollution and it seemed to work but gave com.android.phone error on boot. So I thought easy fix, I'll restore the backup I made with TWRP yesterday and got even more errors. Yes, I factory reset before restoring. It seems that this TWRP is not doing everything like it used to under the 4.2's. I'm going to go back to CWM and restore a CWM backup, regroup, recharge.......and try again from scratch to test this thing out again. Wish me luck.
Click to expand...
Click to collapse
Best of luck to ya! I have restored my nandroid with twrp but not in my latest version. I'll give it a try this evening and see what happens on my end. I have not used the aroma installer because I personally would rather not use it. I just use the camera fix from Pollution since I don't have the screen flicker or any other issues with my phone.

[RECOVERY][ALL VARIANTS]Newest philz with OG Clockworkmod theme.

This is the newest philz recovery with an OG clockworkmod theme.
All credits go to invisiblek. I am just posting here with his permission.
http://www.invisiblek.org/recovery/
Grab the img for your device flash with flashify or tool of your choice.
**Temporarily removed the aromafm, graphics issues at this time.**
The aromafm.zip is for aroma file manager. Place zip in /data/media/0/clockworkmod/aromafm/. They zip file will be in the folder with your variant recovery.img
Does it have an option to change partition to f2fs?
Many thanks mate.
Helloworld294 said:
Does it have an option to change partition to f2fs?
Click to expand...
Click to collapse
No it does not.
<•invisiblek> would need f2fs-support in the boot.img's fstab
<•invisiblek> and if recovery thought it'd be a good idea to re-write that, you're going to end up with an un-bumped boot.img
its in his long term plan but its not there right now.
Woow...Thanks to the good work for d855 [emoji6]
God news
This recovery is not support for F400. It's bad news.
can the partitioning menu be added?
I don't see the aroma zip in the d850 folder
Sent from my LG-D850 using Tapatalk
Is this bumped?
Yes its bumped. Aroma pulled while invisiblek fixes graphic issues.
meyerweb said:
Is this bumped?
Click to expand...
Click to collapse
yes
on another note, as stated, aromafm is derped pretty hard on our device, i'm planning to look into fixing it up at some point, but it might be a bit
also i'm in the process of building/uploading a new version (6.58.9.1) which supports the cm updater, expect those to start rolling in shortly
for those interested in the fix: https://github.com/invisiblek/philz_touch_cwm6/commit/bef5775f20854a45ccfd96b1b04bf5ee28fe3af4
Does it support nandroid backup for modem?
@invisiblek
Great news. You are the real hero behind the scenes. Your work for our device is much appreciated mate thank you. We wouldn't have all those unofficial roms to play with until you make something official for us. it is very close I believe.
Sent from my LG-D855 using Tapatalk
Well, tried on my D850 and installed and ran fine, but 2 issues:
1. Can't mount external SD (SanDisk 64Gb in FAT32 but soon going back to ExFat), the path for it is incorrect and no option to change it
2. Installed a Zip file that replaced the kernel and even though it said all went ok it was never installed
Had to flash back the TWRP recovery (even though that one can't read my external_SD either no matter the format) so I can flash the new kernel properly.
Waiting for your next release to test it out.
Sent from my LG-D850 using Tapatalk
Omegadrive said:
Well, tried on my D850 and installed and ran fine, but 2 issues:
1. Can't mount external SD (SanDisk 64Gb in FAT32 but soon going back to ExFat), the path for it is incorrect and no option to change it
2. Installed a Zip file that replaced the kernel and even though it said all went ok it was never installed
Had to flash back the TWRP recovery (even though that one can't read my external_SD either no matter the format) so I can flash the new kernel properly.
Waiting for your next release to test it out.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
Thats odd, I flash kernels just fine and can flash from my sd card. Could you have gotten a bad download possibly.
can't get philz to make back-up
downloaded the latest version, flashed with flashify, rebooted, and when i try to make a back-up of my current rom, all it does is sit at the "checking" when trying to back up to sdcard1
not sure what i did wrong, but isn't working for me
goldsmitht said:
downloaded the latest version, flashed with flashify, rebooted, and when i try to make a back-up of my current rom, all it does is sit at the "checking" when trying to back up to sdcard1
not sure what i did wrong, but isn't working for me
Click to expand...
Click to collapse
bumped;
tried again, and can't get it to do anything after i select make backup. all it does is says "checking" and nothing.
i'm having problems getting 5.0 roms to install correctly, thought this might be the solution.
So what's going on here? Any work in progress? I don't like twrp that much.
Is there a version of philz recovery that will work on lg g3 as990? Can one be created?

[Q&A] [KERNEL][UNOFFICIAL][PERSONAL BUILDS]DorimanX

Q&A for [KERNEL][UNOFFICIAL][PERSONAL BUILDS]DorimanX
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][UNOFFICIAL][PERSONAL BUILDS]DorimanX. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Great to see the rebirth of the best kernel available for the S2! Would love to see TRIM and LP support! Best of luck to the dev
@stelicristi
Will U add Synapse support ?
Wysłane z Cyanofonika 12 beta...
MikiGry said:
@stelicristi
Will U add Synapse support ?
Wysłane z Cyanofonika 12 beta...
Click to expand...
Click to collapse
I have asked him on the development thread too. He seems make a lot of promises become true. Maybe he will be the next active dorimanx developer.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
acydwarp said:
Great to see the rebirth of the best kernel available for the S2! Would love to see TRIM and LP support! Best of luck to the dev
Click to expand...
Click to collapse
Yes, if he does this and also bring ext4 support of SD cards, I will call him a legend or god or whatever he wants.
gsstudios said:
I have asked him on the development thread too. He seems make a lot of promises become true. Maybe he will be the next active dorimanx developer.
Click to expand...
Click to collapse
I'm still new to SII forum but i now sth about this kernel. If he will bring DorimanX kernel to live (not like 'background activity') well..
It will be AWERSONE :
Kernel with tones if costomalizations , still up to date , compatible with all android versions... Unbelivnable!
Wysłane z Cyanofonika 12 beta...
Hi,
I'm on SlimSaber 21/12. I :installed your kernel but I have some troubles with from first installation:
- I got an advise log saying that my partitions are corrupted (I have a resized 1gb /System
- I can't either reinstall the kernel, recovery or ROM because "install zip on /storage/sdcard0" says there are no files (and I can't explore away).
- WiFi does not finish to be enabled (no networks shown).
Did I miss something when I flashed?
Thank you for your effort.
fragel said:
Hi,
I'm on SlimSaber 21/12. I :installed your kernel but I have some troubles with from first installation:
- I got an advise log saying that my partitions are corrupted (I have a resized 1gb /System
- I can't either reinstall the kernel, recovery or ROM because "install zip on /storage/sdcard0" says there are no files (and I can't explore away).
- WiFi does not finish to be enabled (no networks shown).
Did I miss something when I flashed?
Thank you for your effort.
Click to expand...
Click to collapse
Something went wrong with the installation? I would advise you to go into stweaks, go to the 'other' tab and find 'fix data'. Enable it and reboot. Note: Make sure you have a backup of all of your apps!
gsstudios said:
Something went wrong with the installation? I would advise you to go into stweaks, go to the 'other' tab and find 'fix data'. Enable it and reboot. Note: Make sure you have a backup of all of your apps!
Click to expand...
Click to collapse
Thank you.
While installing no errors were shown.
After first booting, the log error about partition corrupted (and the recommendation to go into stweaks to enable "fix data") was shown. I followed the recommendation, but problems remain. Maybe I did not a full clean installation of the kernel? (just wiped cache and dalvik).
First thing I tried was to go back into recovery and reinstall the kernel but, as I said previously, recovery is not able to explore folders (appears as /storage/sdcard0 unmounted, but mounting does not work either) .
Any advise to reinstall the kernel or the same ROM without passing by ODIN?
Need to say that the phone boots and "works" (seems very busy though), but the problems wrote in my previous post are there.
Thanks.
Edit: I forgot saying that when going into STweaks, a message appears at the beginning during a second:"Unexpected error!" and later disappears and goes into the tool as usual.
Edit 2: Reflashed SlimSaber from adb sideload and everything came back. It would be nice if you could indicate some indications in order to do a proper install of this kernel.
fragel said:
Thank you.
While installing no errors were shown.
After first booting, the log error about partition corrupted (and the recommendation to go into stweaks to enable "fix data") was shown. I followed the recommendation, but problems remain. Maybe I did not a full clean installation of the kernel? (just wiped cache and dalvik).
First thing I tried was to go back into recovery and reinstall the kernel but, as I said previously, recovery is not able to explore folders (appears as /storage/sdcard0 unmounted, but mounting does not work either) .
Any advise to reinstall the kernel or the same ROM without passing by ODIN?
Need to say that the phone boots and "works" (seems very busy though), but the problems wrote in my previous post are there.
Thanks.
Edit: I forgot saying that when going into STweaks, a message appears at the beginning during a second:"Unexpected error!" and later disappears and goes into the tool as usual.
Edit 2: Reflashed SlimSaber from adb sideload and everything came back. It would be nice if you could indicate some indications in order to do a proper install of this kernel.
Click to expand...
Click to collapse
I'm glad you solved your problem. To install the kernel properly, follow these steps:
1. Download sgs2kernelwipe by hawker onto your phone(you can find it in gustavo kernel thread).
2. Download the latest version of dorimanx kernel onto your phone
3. Reboot your phone into recovery
4. Install the kernel wipe zip first
5. Then install the kernel
6. Reboot
(Note: I assume you know how to flash everything already so I simplified it).
Also, I advise you to wait until a newer build is released as the current personal build has some problematic bugs.
I was able to install this kernel, but my internal sdcard partition was not detected properly, on sdcard0 there was a 300MB empty partition instead of my 10 gig one.
I'm on the latest Markox CM, had Gustavo's kernel previously and used the kernel cleanup script. Have a modified PIT with bigger data partition and small preload.
After flashing back Gustavo's, everything's fine.
EDIT: forgot to say, my internal sdcard is ext4 formatted
_petike said:
I was able to install this kernel, but my internal sdcard partition was not detected properly, on sdcard0 there was a 300MB empty partition instead of my 10 gig one.
I'm on the latest Markox CM, had Gustavo's kernel previously and used the kernel cleanup script. Have a modified PIT with bigger data partition and small preload.
After flashing back Gustavo's, everything's fine.
EDIT: forgot to say, my internal sdcard is ext4 formatted
Click to expand...
Click to collapse
There are still a lot of issues with the personal build of dorimanx. If you still want to use dorimanx, stick with the unofficial dorimanx by cybernetus. The problem is caused either by the recovery or broken implementation of something.
Cant open STWeaks
Hi! i can't open swteaks app, (root granted) it throw a "unexpected error". Already tried to delete data-cache of the app and wipe cache/dalvik cache of whole rom. Any help? thanks!
jjhaohao said:
Hi! i can't open swteaks app, (root granted) it throw a "unexpected error". Already tried to delete data-cache of the app and wipe cache/dalvik cache of whole rom. Any help? thanks!
Click to expand...
Click to collapse
Which version of personal build are u using.. I have installed build #2 and have no problem with root in my spare s2..
It could be many reason for receiving unexpected error
* Go to settings app and select ->developer options->root access-> Apps
* Check whether u have installed binary after flashing Dorimanx Personal build
* Dont update su app from playstore and use the SU app that came with kernel.
unable to download
Can someone share a working link for builds 2 and 3 please? Thanks
Hey just some quick results about my experience so far with Build 3
I'm on slimsaber 21/12/2014, coming from Cybernetus 10.44v007. It's a fairly new wipe but i've been having major issues with it prior to the personal build of dorimanx.
WiFi password kept being forgotten. This happened 7 or 8 times. I managed to fix it by typing in the password, connecting, selecting "forget network" and then typing it in again.
Battery drain seems comparable to my previous settings, WiFi is significantly faster to connect and unless I'm seeing things, signal seems much stronger too.
I used fstrim (lagfix) and everything went better than expected. Phone responsiveness seems to be through the roof (whether this is trim or something else, its pretty night and day).
So far all stable.
i cani can't move big apps in sd card. what's a problem
ext4
Hello guys,
someone here is using this kernel with ext4 on the internal sd card? As soon as i switch to the kernel, my internal ext4 formated card doesnt get mounted, until i switch to stock kernel again.
Somebody also have ext4 successfull running? Or is it only me with this mount problem?
I hope someone could give a try in LP kernel to full support init.d and swap. Basically, S2 lacks of memory, and I already acomplished the internal<->external memory swap fix, by using apollo's kernel, 'cause it have init.d support. But it lacks the support to OC. DorimanX in that matter, have a well balanced kernel for JB and KK. With the possible LP support we could have a very good balanced performance for our excelent phone, with 4 years old! It's a matter of time...
---------- Post added at 04:51 PM ---------- Previous post was at 04:46 PM ----------
aCIDsLAM said:
Hello guys,
someone here is using this kernel with ext4 on the internal sd card? As soon as i switch to the kernel, my internal ext4 formated card doesnt get mounted, until i switch to stock kernel again.
Somebody also have ext4 successfull running? Or is it only me with this mount problem?
Click to expand...
Click to collapse
Try Paragon's app. Should help you with the support automatically and it's free. But I think DorimanX's kernel already support that filesystem.
It's there any problem If I'll flash V8.44v005 over stock kernel with 3e recovery?
aef-em said:
hi,
I flashed your kernel (Kernel_Dorimanx-V10.44-_15-20_-_27-01) from Kernel_Dorimanx-V10.44v008.
then the stweak stop working. when launching it, all i get is the title bar and that is it.
tried to reset the stweak settings from the recovery, wipe dalvik and cache, and use HawkernelWipeV1.02, and then re-flash.
also tried to reset the superSU permissions for the stweak.
also - maybe i should mention - that lag fix button is greyed out - and says that TRIM is not supported.
what am i doing wrong??
btw the ROM i'm using is the latest cm11 nightly..+ updated superSU and busybox.
BIG thanks for all the good people around here!
Click to expand...
Click to collapse
I am using this kernel with latest nightly (as already with all nightlies since march) without any problem. Maybe redownload and try once more?

Formatting Nexus 6P cache partition to F2FS

So I tried the Flash TWRP recovery version 3.0.3-1 and found out that it can format the cache partition to f2fs without any error. It also persistent across reboot. Been running since morning and don't see any issue with performance. So I see this as big step forward for Nexus 6p phone. My device have data and cache are running on F2FS and with the flash kernel.
ll
minhgi said:
So I tried the Flash TWRP recovery version 3.0.3-1 and found out that it can format the cache partition to f2fs without any error. It also persistent across reboot. Been running since morning and don't see any issue with performance. So I see this as big step forward for Nexus 6p phone. My device have data and cache are running on F2FS and with the flash kernel.
Click to expand...
Click to collapse
where did you get 3.0.3-1 if you don't mind me asking?
And doesn't f2fs not play so well with supersu? And i heard, on the 6p, f2fs isn't any faster than ext4.
Check the flash kernel page at the end of the thread. The Flash had a link that point to his own personal site. It should be located in the TWRP folder. Anyway, I didn't link it directly since he have gone private at the moment.
I am using the latest SuperSu 2.79S3.
Does it work with pure nexus?
minhgi said:
Check the flash kernel page at the end of the thread. The Flash had a link that point to his own personal site. It should be located in the TWRP folder. Anyway, I didn't link it directly since he have gone private at the moment.
I am using the latest SuperSu 2.79S3.
Click to expand...
Click to collapse
His personal site that you directed me to does not have that link. All it has is a link for his kernel. Would you please PM me the exact link?
TrainNanpaMaster said:
His personal site that you directed me to does not have that link. All it has is a link for his kernel. Would you please PM me the exact link?
Click to expand...
Click to collapse
It's definitely there.
Sent from my Nexus 6P using Tapatalk
minhgi said:
It's definitely there.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It's not the official link. Might be an unofficial release.
The Frustrated Indian said:
It's not the official link. Might be an unofficial release.
Click to expand...
Click to collapse
Official TWRP does not support F2FS. You need this version made by The Flash (XDA moderator) in order to use F2FS, along with a ROM and kernel that support it. He's been supporting F2FS TWRP for some time now. That's his personal website.
So /system is useless since it's 'read-only' 99% of the time (this was Flashes findings he posted in his thread, feel free to search it yourself). He did note that he saw significant speed improvements in his testing for /data.
If you do decide to give it a try, you'll probably want to back up all of your data and decrypt your phone by formatting userdata. Older releases of Flashes F2FS TWRP do not support encryption. Even if your pattern/pin/pass is correct TWRP will say it's not and won't let you in. I haven't tried that newest release, but I did on the older ones. Maybe someone else could speak to encryption on 3.0.3-1. Aside from that, converting from F2FS will format your internal SD regardless, even if his TWRP works on encrypted devices. So back up and give it a shot.
Edit: if anyone stumbles upon this, Flashes 3.0.3-1 DOES work on encrypted devices now.
which rom are you on ?
As long as you use flash kernel, you can run any rom besides stock with f2fs. Ive used almost every rom for our phone with f2fs. There are quite a few unofficial versions of twrp that supports f2fs. The 3.0.3.. versions are really slow at restoring nandroid backups for some reason. I use multi rom twrp. I forget the version, its 3.0.2-2 i think.
Cache
It's official. I'm now a BELIEVER.
In F2FS.
I finally took the plunge and converted to it.
To anyone that I showed doubt to in regards to f2fs, I sincerely apologize. It is indeed noticeably faster than ext4. Apps fly open now, everything is glassier, and snappier. There is definitely a profoundly noticeable difference over ext4. In fact, it really feels like I have a new device. The best way I can explain it - is that the phone feels like it's running at a constant 60fps now.
I was able to move my ext4 nandroid over to my freshly partitioned f2fs 6p. This saved HUGE amounts of time setting everything back up. I just had to copy over TWRP backup (and restore) the DCIM folder, as well as my titanium backup folder, along with all the standard rom stuff like gapps, rom, kernel etc.
All in all, I'm extremely impressed with f2fs. On paper, it looks to be only marginally faster than ext4. But in real life, you can definitely see a big difference. Now a believer.
Ok, so I took the plunge into this F2FS thing. I followed this tutorial. Wiped everything including internal cache, converted to f2fs. Now, I'm trying to copy rom and gaaps from pc to phone by mounting system and data but having issues. My pc can see the phone in explorer but can't seem to copy. screenshots below.
Any help would be greatly appreciated.
EDIT: silly me, forgot to reboot the recovery lol.
TrainNanpaMaster said:
It's official. I'm now a BELIEVER.
In F2FS.
I finally took the plunge and converted to it.
To anyone that I showed doubt to in regards to f2fs, I sincerely apologize. It is indeed noticeably faster than ext4. Apps fly open now, everything is glassier, and snappier. There is definitely a profoundly noticeable difference over ext4. In fact, it really feels like I have a new device. The best way I can explain it - is that the phone feels like it's running at a constant 60fps now.
I was able to move my ext4 nandroid over to my freshly partitioned f2fs 6p. This saved HUGE amounts of time setting everything back up. I just had to copy over TWRP backup (and restore) the DCIM folder, as well as my titanium backup folder, along with all the standard rom stuff like gapps, rom, kernel etc.
All in all, I'm extremely impressed with f2fs. On paper, it looks to be only marginally faster than ext4. But in real life, you can definitely see a big difference. Now a believer.
Click to expand...
Click to collapse
Somehow my nandroid backup of lineage os wiped internal storage again (I restored after formatting /data and /cache to f2fs). Ended up doing clean install.
Anyone tried this using custom kernels? whenever i seem to flash a custom kernel nathans TWRP throws the error of either ramdisk unpack failed or recovery busybox problem.
xSilas43 said:
Anyone tried this using custom kernels? whenever i seem to flash a custom kernel nathans TWRP throws the error of either ramdisk unpack failed or recovery busybox problem.
Click to expand...
Click to collapse
I use a kernel that i think is even better than flash kernel (IMO). It's fundamentally identical to Uber kernel, but made by a team member. He also makes uberstock nightlies which is the best ROM in my opinion because it's gcc 6.3.1 and clanged to 3.9.1. Combined with F2FS, and it's pure glassy snappy butter multiplied to power level 9000.
I've literally flashed every single ROM including PureNexus, and these kernel and nightlies absolutely teabag everything I've tried.
Silas i know you know about this already, but The kernels and nightlies can be found here:
https://temp.bbqdroid.org/
TrainNanpaMaster said:
I use a kernel that i think is even better than flash kernel (IMO). It's fundamentally identical to Uber kernel, but made by a team member. He also makes uberstock nightlies which is the best ROM in my opinion because it's gcc 6.3.1 and clanged to 3.9.1. Combined with F2FS, and it's pure glassy snappy butter multiplied to power level 9000.
I've literally flashed every single ROM including PureNexus, and these kernel and nightlies absolutely teabag everything I've tried.
Silas i know you know about this already, but The kernels and nightlies can be found here:
https://temp.bbqdroid.org/
Click to expand...
Click to collapse
yeah that's the kernel i normally use, however, i tried using r48 and r49 still get the same error, i even tried flash's kernel and I'm getting the same error, guess ill just stick with stock kernel for now. Very weird it worked fine for you but not me.
EDIT:
Somehow when i decided to try reflashing except not using SuperSU the kernel was able to flash.
Try a different twrp. The multirom twrp supports f2fs and a few more. Ive tried alot of them and never seen an error like yours.
TrainNanpaMaster said:
I use a kernel that i think is even better than flash kernel (IMO). It's fundamentally identical to Uber kernel, but made by a team member. He also makes uberstock nightlies which is the best ROM in my opinion because it's gcc 6.3.1 and clanged to 3.9.1. Combined with F2FS, and it's pure glassy snappy butter multiplied to power level 9000.
I've literally flashed every single ROM including PureNexus, and these kernel and nightlies absolutely teabag everything I've tried.
Silas i know you know about this already, but The kernels and nightlies can be found here:
https://temp.bbqdroid.org/
Click to expand...
Click to collapse
why is this rom and kernel not on xda???? or maybe i havent spotted it..... it is SUPER SMOOTH, in F2FS it is running amazing... didnt mess with the kernel at all, and this thing is fire!!!!
i42o said:
why is this rom and kernel not on xda???? or maybe i havent spotted it..... it is SUPER SMOOTH, in F2FS it is running amazing... didnt mess with the kernel at all, and this thing is fire!!!!
Click to expand...
Click to collapse
It's fundamentally very similar to Uberstock ROM and kernel.
A lot of people on these forums think Purenexus is the best rom ever. (most likely because the developer really branches out with social media and branding).
They obviously haven't tried this or uberstock.

[UNOFFICIAL] [07/19] TWRP 3.1.1 with F2FS support

Introduction
Hello all, this is my version of TWRP for the Nexus 6P, which includes the ability to convert your /data and /cache partitions to F2FS. This will stay inline with TWRP's changes for the most part, the changes will be listed below.
What in the world is F2FS?
From Wikipedia:
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux 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.
F2FS was designed on a basis of a log-structured file system approach, which it adapted to newer forms of storage. Jaegeuk Kim, the principal F2FS author, has stated that it remedies some known issues of the older log-structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. In addition, since a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), it supports various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms.
Click to expand...
Click to collapse
Before diving into this, I would recommend reading the official F2FS documentation to understand why this may be good for you. This is potentially unstable, F2FS is a file system that is very much in active development. There is a reason that most OEMs go with ext4 out of the box. But I digress, I am NOT here to sell you on F2FS; it makes zero difference to me if you use it or not, I am merely providing you with a tool to do so.
Changelog + differences
Differences:
f2fs-tools bumped to 1.7.0 (Omni's 6.0 branch is on 1.4.0)
TWRP app installation offer disabled by default
Conversion procedure
Download TWRP from the link above
Grab a kernel that supports F2FS (I use my own as I know it works)
Back up any important data as this will wipe your entire internal storage
Boot into the bootloader and flash the recovery
Boot into TWRP and go into Wipe > Advanced Wipe
Select Data and then hit "Change or Repair File System"
Hit Change File System
Choose F2FS and slide to confirm
Repeat the previous three steps for cache
Reboot and move all of your files back over (if restoring through TWRP, make sure to check the option to use rm -rf instead of formatting)
If you have any issues with this, you may need to ask your ROM developer to merge the two commits below.
Bug reports
You are NOT in ANY circumstance to report ANY bugs to the TWRP team.
If you have an issue with flashing something in TWRP, copy the recovery log to your sdcard and post it here.
If swapping to F2FS does not stick, try formatting your data with TWRP (Wipe > Format Data) or fastboot format userdata first.
If your phone does not boot after swapping to F2FS, either your kernel or ROM does not have proper support; post in their thread.
Additionally, check out some of these helpful posts:
https://forum.xda-developers.com/showthread.php?p=70699197
https://forum.xda-developers.com/showthread.php?p=71074016
Adding support to ROM
In order to properly support the initial conversion to F2FS, please add these two commits to your source:
https://github.com/omnirom/android_system_core/commit/1c6700a8fb31c6e314df4f031fa23fa9178c7ca7
https://github.com/omnirom/android_system_vold/commit/c879edb2fecae709f404c2d71c1d47ceac3a325e
The reason some people have issues converting is fs_mgr will try to read the block device as ext4 and destroy the f2fs block. This commit skips that check, allowing F2FS to pass through.
Sources
TWRP is licensed under GPLv3, meaning my changes must be disclosed. I also inline a custom kernel so that source is included as well. I also add in the other repos I modify.
Recovery: https://github.com/nathanchance/android_bootable_recovery/tree/android-7.1
Kernel: https://github.com/nathanchance/angler/tree/7.1.2-flash
Device tree: https://github.com/nathanchance/twrp_device_huawei_angler/tree/android-6.0
f2fs-tools: https://github.com/nathanchance/android_external_f2fs-tools/tree/android-6.0
First!
Thanks for the recovery. Been using it with flash kernel. I see considerable performance improvement in asphalt Xtreme game( idk if its the f2fs or kernel ).
Nice !!! :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Thank you, and thank you for the exemplary GPL compliance. It's noticed and appreciated.
Now this is awesome... On it, will report soon
Much appreciated!
Sent from my Nexus 6P using Tapatalk
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Nitrogen : yes
Somebody must report it and i will update my post.
ThNks
ariefabuzaky said:
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Somebody must report it and i will update my post.
ThNks
Click to expand...
Click to collapse
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Worked perfect! Thanks Flash!!!
I tried this with PN and am now stuck in a boot loop. I flashed the twrp with F2FS support then tried to change the file system followed by installing the latest vendor, latest flashable bootloader+radio, latest pure nexus and gapps, flash kernel, and latest su. Didnt work. Im not stuck in a boot loop I cant get out of. Ive tried every combination of the above. I also tried restoring my backup but that gives me an error. I also tried changing the file system back to ext4. Nothing works. Anyone experience this or have any suggestions?
---------- Post added at 09:09 AM ---------- Previous post was at 08:58 AM ----------
jochem86 said:
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Click to expand...
Click to collapse
Im in the same boat.....what steps did you do to get back to stock?
Data keeps reverting back to ext4 after 1st boot.
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
Mine too....Im stuck in a bootloop. Are you?
Whats also weird is switching too f2fs wiped my storage but once the data reverted back to ext4....my original storage came back too!! Im not sure how or why that is happening either.
I just followed OP and formatted everything first, now i have SAOSP running with flash on f2fs..
Works great, so far it doesn't feel like a huge improvement though..
Sent from my Nexus 6P using XDA-Developers Legacy app
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
What makes you say that?
Back then when I was using Temasek on my Note 3, he incorporate a script that automatically format the system partition to F2FS when flashing his ROM. That is if the system partition is already in f2fs and I think that was pretty amazing but short live. I wonder if other ROM developer could go the same route if formatting F2FS system was popular enough. That would make updating new rom one step easier. Just for thought.
---------- Post added at 09:38 AM ---------- Previous post was at 09:16 AM ----------
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
minhgi said:
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
Click to expand...
Click to collapse
I wish you told this earlier....This is exactly what happened and I had to clean install
NoobInToto said:
I wish you told this earlier....This is exactly what happened and I had to clean install
Click to expand...
Click to collapse
It wouldn't matter though, I get a warning that the backup was made with EXT4 and that backup may not boot unless changed back to it
Iceburn1 said:
What makes you say that?
Click to expand...
Click to collapse
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
Exactly doing the same....
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
That's too bad its not working for you, its working on my side no problem, did you format in twrp if its not sticking? Im on RR with Flash kernel.

Categories

Resources