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.
Related
I know i777 does not officially have SlimKat so I apologize if it's not appropriate to ask this question.
I'm using SlimKat 2.6 RC2 from 9100 forum and got one problem. My internal storage goes haywire out of no where. It does that I have ~300MB available but I've only used up around 200 MB to include cache data. The bar on top of the screen shows that I still got plenty of space left. I tried clearing everything and even re-flash but nothing help.
After a full re-flash it would be fine, but as soon as I install an app, the available internal memory would drop.
Any help is greatly appreciated it. Thank you!
I'm on the same rom as you, so I just checked my storage: sorry to report that mine is working fine - and I think yours is also. When you wipe in recovery, you must format /system, along with the other stuff (if you aren't already doing that).
My advice would be to use a file explorer and manually check what you have filling up your phone. If you were recently on a stock rom I would manually delete the preload folder (the only danger in doing that is it might corrupt a backup of a stock rom, if you have one. If you don't have that type of backup, delete away), or even something like this app can help: https://play.google.com/store/apps/details?id=com.cleanmaster.mguard
Yes, You need to format system from Recovery and that should fix that, by the way do you install this rom with CWM or TWRP?? Because my i777 with kitkat the phone keeps rebooting itself i dont know why
Thanks!
juanqui1893 said:
...do you install this rom with CWM or TWRP??
Click to expand...
Click to collapse
I use TWRP for KK, have never had a problem at all.
Render Broken Kernel??
juanqui1893 said:
Render Broken Kernel??
Click to expand...
Click to collapse
Yes, it's currently the only kernel that will work on ported KK roms.
SteveMurphy said:
Yes, it's currently the only kernel that will work on ported KK roms.
Click to expand...
Click to collapse
Ok, I wanna port Celeriter rom 4.4.2 for i9100 to my i777, do you think that this procedure can brick my phone??
Regards!
juanqui1893 said:
Ok, I wanna port Celeriter rom 4.4.2 for i9100 to my i777, do you think that this procedure can brick my phone??
Regards!
Click to expand...
Click to collapse
You shouldn't have any trouble porting that rom, but because it's based on CM and not Slim, you can't use Renders' Slim kernel. I would suggest the TWRP CM version, only because I've not used the CWM version personally, but you shouldn't have any issues. Just make sure you follow the OP instructions and use the gapp package they suggest.
SteveMurphy said:
You shouldn't have any trouble porting that rom, but because it's based on CM and not Slim, you can't use Renders' Slim kernel. I would suggest the TWRP CM version, only because I've not used the CWM version personally, but you shouldn't have any issues. Just make sure you follow the OP instructions and use the gapp package they suggest.
Click to expand...
Click to collapse
AOcP announce the update to final version , As soon as they publicate the rom I'll flash that rom, cause I like Celeriter and Resurrection Remix, both kitkat, but Its based on AOSP and Celeriter is based on CM11 with RenderBroken I guess it will work fine, but lets try lol
Thanks for your help!
SteveMurphy said:
I'm on the same rom as you, so I just checked my storage: sorry to report that mine is working fine - and I think yours is also. When you wipe in recovery, you must format /system, along with the other stuff (if you aren't already doing that).
My advice would be to use a file explorer and manually check what you have filling up your phone. If you were recently on a stock rom I would manually delete the preload folder (the only danger in doing that is it might corrupt a backup of a stock rom, if you have one. If you don't have that type of backup, delete away), or even something like this app can help: https://play.google.com/store/apps/details?id=com.cleanmaster.mguard
Click to expand...
Click to collapse
Thanks for the help. If you look at the screen shot I included, the top bar says there's still plenty of room left. So, in actuality, the phone is almost empty with the exception of the 2 apps I installed (SuperSU and TiBu). Maybe there's just bad remnant of previous ROMs. I came from AoCP to SlimKat.
Anyhow, I reflash the rom again without using MrCook's wipe script and pretty much wipe and format everything that's possible. The phone is somehow working normally now *finger crossed*. I think the problem is the /data. MrCook's script doesn't format /data, and I never had to format data, only /system. But this time, I include /data with all the formatings. But who knows, it could be something else.
Thanks again.
Edit: I take it back, I just looked over mr-cook's wipe script and the script does format /data...so not sure what's the problem was.
Edit 2: Just in case anybody is reading this thread. Don't use mr-cook's wipe script for SlimKat 2.6, wipe and format everything manually. I just tried again with the RC3 and mr-cook's wipe script didn't clear everything so my internal storage was still filled up from previous ROM. Just FYI.
juanqui1893 said:
Yes, You need to format system from Recovery and that should fix that, by the way do you install this rom with CWM or TWRP?? Because my i777 with kitkat the phone keeps rebooting itself i dont know why
Thanks!
Click to expand...
Click to collapse
Formatting /system didn't help, I format /system every time I flash new ROM. But to your question, I'm using Render's TWRP and do not get any reboot so far.
So let me get this straight, and please quote me; we can actually flash ROMs from the i9100 forum as long as steps are taken to manually format partitions? Cause man, I've just been dying to give SlimKat a whirl on my i777, along with checking out other ROMs there. The i777 just doesn't seem to be as popular as its counterpart.
Sent from my SGH-I777 using XDA Premium 4 mobile app
CyanJustice said:
So let me get this straight, and please quote me; we can actually flash ROMs from the i9100 forum as long as steps are taken to manually format partitions? Cause man, I've just been dying to give SlimKat a whirl on my i777, along with checking out other ROMs there. The i777 just doesn't seem to be as popular as its counterpart.
Sent from my SGH-I777 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's as straight as it can be from me. I have i777 and is using SlimKat 2.6 RC3 weeklies with RenderBroken's kernel right now. I don't know about others but I have to manually wipe it. Also, I'm using TWRP when I do the wipes so I'm not sure if mr-cook's wipe script works differently with TWRP and CWM or not. Either way, manually wipe everything with TWRP is my way of doing it now.
And hmm, I don't know about ROMs but SlimKat works, and you need RenderBroken's kernel for it to work completely because 9100 doesn't have the same buttons as i777.
wolftou said:
I don't know about ROMs but SlimKat works, and you need RenderBroken's kernel for it to work completely because 9100 doesn't have the same buttons as i777.
Click to expand...
Click to collapse
This is true, but the real reason you can only use Renders' slim kernel on SlimKat is because they use different ramdisks: no other kernel will work on that rom.
For other i9100 KK roms, his TWRP and CWM kernels work, so for those not based on Slim you can use whichever you prefer.
SteveMurphy said:
This is true, but the real reason you can only use Renders' slim kernel on SlimKat is because they use different ramdisks: no other kernel will work on that rom.
For other i9100 KK roms, his TWRP and CWM kernels work, so for those not based on Slim you can use whichever you prefer.
Click to expand...
Click to collapse
Great! So hey, help me out; which partitions do I have to wipe exactly, in which order? A chronological how-to would get my thanks for sure. SlimKat has always been my favorite ROM.
Sent from my SGH-I777 using XDA Premium 4 mobile app
CyanJustice said:
...which partitions do I have to wipe exactly, in which order?
Click to expand...
Click to collapse
You only need to manually format /system when installing other roms, along with the usual factory reset/wipe data stuff. As long as you install a rom after you format system, the order doesn't matter.
Example, you could format system first then factory reset - the order is irrelevant. What the system format is doing is removing the current system installed on the device (the OS). All a factory reset does is restore the current rom to basic factory settings - it doesn't erase anything in terms of the OS.
That's why formatting /system (especially when changing bases) is so important; it prepares the device for the new rom you install by allowing a clean install every time.
SteveMurphy said:
You only need to manually format /system when installing other roms, along with the usual factory reset/wipe data stuff. As long as you install a rom after you format system, the order doesn't matter.
Example, you could format system first then factory reset - the order is irrelevant. What the system format is doing is removing the current system installed on the device (the OS). All a factory reset does is restore the current rom to basic factory settings - it doesn't erase anything in terms of the OS.
That's why formatting /system (especially when changing bases) is so important; it prepares the device for the new rom you install by allowing a clean install every time.
Click to expand...
Click to collapse
Cool, thanks for the info! You guys generally like SlimKat? Is the memory usage better CM or Omni?
Sent from my SGH-I777 using XDA Premium 4 mobile app
CyanJustice said:
Cool, thanks for the info! You guys generally like SlimKat? Is the memory usage better CM or Omni?
Click to expand...
Click to collapse
Try all 3 and decide which one you prefer; we all like different things in our roms.
I may try and port slimkat over tonight, you think people would like that?
Sent from my SGH-I777 using XDA Premium 4 mobile app
CyanJustice said:
I may try and port slimkat over tonight, you think people would like that?
Sent from my SGH-I777 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The Slim team doesn't approve of ports, I'm afraid you'd get shut down. I think people would like it, but I'd advise against posting it.
The workaround would be to build your own version from source, with additions from other roms. That way it isn't a straight port.
CyanJustice said:
I may try and port slimkat over tonight, you think people would like that?
Sent from my SGH-I777 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You know, if you're capable, I'd say just join the Slim Team. They discontinued i777 probably because of lack of device or developer. So if you can port/dev, why not just join the team and head up the i777 development. And since the i9100 and i777 is practically the same device, it wouldn't be too hard to work with the i9100 dev team. Just a thought.
I'm using the SlimKat 3 with Render's latest CWM test kernel and everything is working well so far.
The Nexus 7, Nexus 5, Moto G, and Moto X all have f2fs support in some kind. It has made a fast improvement on my N7. Was wondering if any devs want to form a team to build up f2fs support for our device.
Would be willing to help.
Sent from my KFTHWI using xda app-developers app
Dude, come into #lg-g2 and ask. Hours of activity are pretty similar to how #lg-optimus-g were back this time last year.
Sent from my LG Optimus G using XDA Premium 4 mobile app
http://forum.xda-developers.com/showthread.php?t=2764480
Looks like they got F2FS working on the E975. No idea if its possible to take this and monkeywrench it for the E970, but its nice progress!
I hope the F2FS interest for this device doesn't die here. I've tested it out on the Nexus 7 and it basically made the device a whole new, usable experience. I would love to see the benefits that our aging geebs can get from it to extend their lifespan and usability.
nygfan760 said:
The Nexus 7, Nexus 5, Moto G, and Moto X all have f2fs support in some kind. It has made a fast improvement on my N7. Was wondering if any devs want to form a team to build up f2fs support for our device.
Click to expand...
Click to collapse
My TWRP build and AK kernel both support it. I've tried it and I think it worked.
Sent from my LG Optimus G using Tapatalk
brothaedhung said:
My TWRP build and AK kernel both support it. I've tried it and I think it worked.
Sent from my LG Optimus G using Tapatalk
Click to expand...
Click to collapse
I had no idea. That's awesome! I checked the TWRP and, sure enough, it can format f2fs. Any chance you can build a version of your PAC rom that does f2fs-all (except, of course, external sd)? I'd be happy to test it!
Level99 said:
I had no idea. That's awesome! I checked the TWRP and, sure enough, it can format f2fs. Any chance you can build a version of your PAC rom that does f2fs-all (except, of course, external sd)? I'd be happy to test it!
Click to expand...
Click to collapse
For the ROM, I think you just have to edit the updater-script to format system as F2FS instead of ext4. Haven't tried it yet, but I will tonight if I have time.
There's playstore apps that will do it too.
I've successfully formatted system F2FS, but haven't tried data yet since I think you lose everything when you format?
brothaedhung said:
For the ROM, I think you just have to edit the updater-script to format system as F2FS instead of ext4. Haven't tried it yet, but I will tonight if I have time.
There's playstore apps that will do it too.
I've successfully formatted system F2FS, but haven't tried data yet since I think you lose everything when you format?
Click to expand...
Click to collapse
Yeah, it does. I tried your rom with system as ext4 and data as f2fs and it popped up with the encrypted storage dialog and there was no way to get around it. I figure the kernel may only support f2fs for system right now.
I'll try manually changing the updater script for f2fs for system. I got one of the apps for f2fs conversion but it only currently supports nexus 4, 5, and 7. I emailed to request support be added for e970.
Sent from my LG Optimus G using XDA Premium 4 mobile app
Level99 said:
Yeah, it does. I tried your rom with system as ext4 and data as f2fs and it popped up with the encrypted storage dialog and there was no way to get around it. I figure the kernel may only support f2fs for system right now.
I'll try manually changing the updater script for f2fs for system. I got one of the apps for f2fs conversion but it only currently supports nexus 4, 5, and 7. I emailed to request support be added for e970.
Sent from my LG Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
also let me try making an updated TWRP build. I read somewhere about issues with data f2fs on early 2.7.1 builds.
brothaedhung said:
also let me try making an updated TWRP build. I read somewhere about issues with data f2fs on early 2.7.1 builds.
Click to expand...
Click to collapse
Alright, thanks. I tried changing the ext4 to f2fs and it failed to flash. Will keep tinkering but I did see another method that involved backing up the system, data, and cache partitions, and then restoring while enabling a TWRP option forcing the restores to restore as f2fs. Don't know if that's also something that can be added when you make the new TWRP build.
Level99 said:
Alright, thanks. I tried changing the ext4 to f2fs and it failed to flash. Will keep tinkering but I did see another method that involved backing up the system, data, and cache partitions, and then restoring while enabling a TWRP option forcing the restores to restore as f2fs. Don't know if that's also something that can be added when you make the new TWRP build.
Click to expand...
Click to collapse
Did you ever attempt this? Is there some roadblock that prevents our geeb from utilizing F2FS? I feel as though the interest in F2FS died down almost immediately lol
topdawg7793 said:
Did you ever attempt this? Is there some roadblock that prevents our geeb from utilizing F2FS? I feel as though the interest in F2FS died down almost immediately lol
Click to expand...
Click to collapse
The latest TWRP I had access to on the geeb did not have an option to force restore to F2FS. We'd need an update to the recovery that adds it, and even then, not sure it will work.
My main these days is a Moto G 4G LTE and, considering the specs, it should not be as snappy and responsive as it is. F2FS really does seem to add new life to middling device hardware, so I can't imagine what it would do to the geeb with its previous flagship specs.
Level99 said:
The latest TWRP I had access to on the geeb did not have an option to force restore to F2FS. We'd need an update to the recovery that adds it, and even then, not sure it will work.
My main these days is a Moto G 4G LTE and, considering the specs, it should not be as snappy and responsive as it is. F2FS really does seem to add new life to middling device hardware, so I can't imagine what it would do to the geeb with its previous flagship specs.
Click to expand...
Click to collapse
Ah, I see. The ramdisk needs to know what partitions are f2fs too right? All that stuff goes above what I'm capable of lol
topdawg7793 said:
Ah, I see. The ramdisk needs to know what partitions are f2fs too right? All that stuff goes above what I'm capable of lol
Click to expand...
Click to collapse
I built a ROM with a modified ramdisk and updater script. It flashes but doesn't get past the boot animation.
brothaedhung said:
I built a ROM with a modified ramdisk and updater script. It flashes but doesn't get past the boot animation.
Click to expand...
Click to collapse
Hmm..The only thing I can think of that could cause that is maybe the ROM didn't compile properly.
The key is to flash the rom, and kernel, and whatever, then afterwards format /data and /cache as f2fs using TWRP.
@brothaedhung do you have an F2FS kernel I can test?
nygfan760 said:
The key is to flash the rom, and kernel, and whatever, then afterwards format /data and /cache as f2fs using TWRP.
@brothaedhung do you have an F2FS kernel I can test?
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/61238/
brothaedhung said:
I built a ROM with a modified ramdisk and updater script. It flashes but doesn't get past the boot animation.
Click to expand...
Click to collapse
Have you tried this with the new TWRP?
topdawg7793 said:
Have you tried this with the new TWRP?
Click to expand...
Click to collapse
Not the one I built a couple of days ago, but I did with the fixed 2.7.1 that correctly formatted f2fs.
brothaedhung said:
Not the one I built a couple of days ago, but I did with the fixed 2.7.1 that correctly formatted f2fs.
Click to expand...
Click to collapse
Hmm okay. We'll only see a noticeable performance gain if the system partition is f2fs right? I doubt we'll gain much with just the data and cache being f2fs.
I used F2FS file system on data and cache partition and now its like i have a nexus 6p there is little to no UI lag or even any delay in opening apps.
Used to use F2FS on my previous devices(lg g2, Galaxy S2 and Xperia Z ultra) and man the effect was noticeable from day1, so tried it on this device and guess what it works flawlessly.
Here is a thread for comparition between F2FS vs EXT4(the default one).
So here is guide for you guys its Highly dangerous setup so please follow this if you know how to restore a SoftBrick status.
Caution:--
ONLY FOR CM13 and N based roms which support F2FS, If used on OOS3 or H2OS(mm) it will result in not converting the data/cache partition properly and will end up 0mb partition because of modified twrp used for these roms and you wont be able to be mount your internal memory too.
Backup backup backup. Make sure you take a backup and save it on your pc before performing the steps.
Things you can do to make your life easier:--
Clean flashing of rom is highly recommended but you can try dirty too as it does not touch the system partition but still clean is preferred.
Use ZipMe app to make a zip file for your apps so that installing all those apps becomes easier if coming from clean flash.
Full backup of your internal memory files as this setup formats even your internal memory even if you select only the data partion.
Best stay on stock kernel as there is no mention of any cm13 custom kernel to have f2fs support. They may have but in any thread of these i couldnt find f2fs word anywhere. So stay stock.
Rom compatibility/tried on:--
Exodus.
All cm13 based roms work flawlessly.
LineageOS14
Kernel compatibility:--
Darkbeast
Stock kernel or the one provided by default by the rom.
Yarpin's kernel.
Benschold kernel.
Note:- Please this method has worked on F2FS supported roms only before following any of it make sure your rom developer has incorporated f2fs support in his/her rom.
Steps:--
Use revert2lollipop to revert back to lollipop firmware if you are on OOS3/H2OS and wanna try f2fs.
Download and upgrade your twrp version to latest.
Copy the .img file to your root folder and reboot to twrp select--->Install-->Install images button-->select the new .img file you copied and reboot to recovery.
Format everything including your internal memory.
Go to advance wipe and select cache partition and select repair and change file system, once there select change file system and change it to f2fs and swipe. Images.
Repeat the above step for data partition.
Go to twrp settings and tick rm -rf, this will make your device retain your f2fs system after clean flash of some roms.
Reboot your recovery once and copy back all your data back to your internal memory.
Flash the required modem for your rom and clean flash your rom for the best bug free experience.
Benefit!
PS:- Please if someone daring does use this on another rom and if everything works flawlessly then please post about it, i will add it compatible roms/kernels.
Press thanks if it worked for you and do post about any improvements you saw.
Credits:-
@Androguide.fr
@ opt devs for awesome roms.
@ jrummy Apps for zipme app.
Seems rock solid for me! I'm running AICP Nightlies .... Running great! Getting it all set back up but no issues at all.
jbarcus81 said:
Seems rock solid for me! I'm running AICP Nightlies .... Running great! Getting it all set back up but no issues at all.
Click to expand...
Click to collapse
Ohhh great will add aicp in the compatible ROMs.
BTW are you on stock aicp kernel?
So we need stock kernel
isoladisegnata said:
So we need stock kernel
Click to expand...
Click to collapse
Yeah for now, since for f2fs roms to work properly the kernel also needs to support the file system and no custom kernel has f2fs as a feature mentioned in their list. I couldnt find anything related to f2fs even with the search function, will update the thread if f2fs support is confirmed by the devs of the respective kernels.
chintu1234 said:
Ohhh great will add aicp in the compatible ROMs.
BTW are you on stock aicp kernel?
Click to expand...
Click to collapse
Yeah.. Not using any kernel other than what's built into AICP from the OP.. :highfive:
Added yarpin's kernel to the compatible kernels.
Using AOKP with stock kernel perfectly! Thanks for this OP and also for sharing the ZipMe app! Which is amazing, Didnt work for me on CM13 though but love the idea! JRummy devs make the best apps
Can i use titanium backup to app+data?
isoladisegnata said:
Can i use titanium backup to app+data?
Click to expand...
Click to collapse
Yes you can.
A noob questions:
- How do I put my data in internal sd...?
. I save the internal memory sd on pc before
. will format everything including internal memory.
. change cache and data partition in F2FS...
when I reboot in twrp.. how do I put all data in sd card?..with ROM ..Modem etc..?
is it possible? if I connect the phone to usb..I'll see internal memory?
isoladisegnata said:
A noob questions:
- How do I put my data in internal sd...?
. I save the internal memory sd on pc before
. will format everything including internal memory.
. change cache and data partition in F2FS...
when I reboot in twrp.. how do I put all data in sd card?..with ROM ..Modem etc..?
is it possible? if I connect the phone to usb..I'll see internal memory?
Click to expand...
Click to collapse
Yeah if you connect to PC after conversion you will be able to access your memory as you used to with default system.
Just make sure to wipe system,data,cache,dalvic,internal before going any further for good measure.
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
boulder96 said:
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
Click to expand...
Click to collapse
how it compare with ext4? u see the different?
Sent from my ONE A2003 using XDA-Developers mobile app
Tatsuya_ said:
how it compare with ext4? u see the different?
Sent from my ONE A2003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Honestly I wouldn't notice a difference unless you put 2 phones running ext4 and f2fs side by side for comparison. But if I were to really force an answer out from myself I would say that app opening and switching times are greatly reduced.
you really deserved more thanks for this guide.. keep it up and great work!
boulder96 said:
f2fs for data and cache on 19/04 Unofficial Temasek's CM13 by Benschold and Benschold's Custom Kernel v3.3 working flawlessly here. So far haven't noticed anything yet, but will report back if anything happens!
Click to expand...
Click to collapse
Nice! thanks for reporting, will add to OP.
Works great with Exodus ROM !!!
very good. Thank you very much. wonder why only cache and data? What about the system partition?
rakieta said:
very good. Thank you very much. wonder why only cache and data? What about the system partition?
Click to expand...
Click to collapse
It really isnt needed because in system partition most of the time only read function is done while data and cache constantly need read/write functions to be performed so you wont notice anything different if you format system to f2fs.
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.
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.