Database Users

{HELP} Unable to Change ext4 to f2fs

Update: i Fixed it by myself. Thanks
Hello! i am new here. i have samsung galaxy s3 neo i9300i. updated to android 4.4 with TWRP installed. i wanted to flash cm 12.1 rom by "Rox". but he wrote in order to flash one need to change the partition from ext4 to f2fs which i followed but didn't find in TWRP wipe>advanced>change partition there are others but not f2fs. because of this problem i have flashed the ROM & GApps & they both flashed successfully but when i rebooted the system, download mode appears. did rebooted several times but the problem was still there. plz help me. i want CM 12.1. THANKS

WTF.... Well, guy, you needn't to convert partitions, you only have to wipe data, dalvik and cache and flash ROM & Gapps.
If you want to convert, convert only data and cache... idk why you haven't this options... Well, I never converted this files, and CM12.1 is working fine.

not working
MarcusBS said:
WTF.... Well, guy, you needn't to convert partitions, you only have to wipe data, dalvik and cache and flash ROM & Gapps.
If you want to convert, convert only data and cache... idk why you haven't this options... Well, I never converted this files, and CM12.1 is working fine.
Click to expand...
Click to collapse
i tried but when i flashed, its stuck in the download mode. just like Rox wrote i did that. nothing more.

Did it by myself...
The problem with my phone was the TWRP 2.7.1.0, + due to root ota updates not worked, so i downloaded another rom 4.3, flashed it, updated to kitkat (ota), flashed TWRP 2.8.5, flashed the rom (cm 12.1 by rox), flashed the gApps... now it's working... Thanks...

F2FS - recovery not compatible?

I was trying to convert my system, data and cache to F2FS but after the conversion I can't use Data anymore (apparently it cannot mount data and system anymore).
Could be a problem LinkedIn to the grarak modded 3.0.2 I'm using for Exodus 6?
Any feedback is welcome!

Up

Most probably as the official one from twrp supports f2fs natively.
I would recommend to go back to official twrp convert to f2fs properly from there and then flash the modified one, do this if you are brave enough, i havent tried this method but it should work. If all fails stay on ext4 till garak or twrp updates their twrp versions.

Thanks for you answer... I thought the same... I'll try as the new phone will come and let you know...

IlD4nX said:
I was trying to convert my system, data and cache to F2FS but after the conversion I can't use Data anymore (apparently it cannot mount data and system anymore).
Could be a problem LinkedIn to the grarak modded 3.0.2 I'm using for Exodus 6?
Any feedback is welcome!
Click to expand...
Click to collapse
I got the same error for my Redmi Note 3 ... tried 3.0.0.0, 3.0.2.2, but nothing. then a guy suggested this:
https://www.androidfilehost.com/?fid=24591000424943818
and it worked. Now I can't boot on f2fs, just trying to make it work on 6.0.1 Mokee rom

ONEPLUS 5 Bootloop after flashing Lineage OS 14.1

Hello Guys,
I have been using xXx NoLimits 4.8 rom that is based on Oxygyn 4.5.15 ( android version 7.1.1) and now I would like to try Lineage 14.1.
I have TWRP 3.2.1 Blue Spark V8.61.
I wiped Data, Cache, System and Dalvik and flashed Lineage 14.1 and then flashed the addon supersu 64bit and then wipe dalvik and cache again and rebooted but the phone never booted into system. It kept on rebooting to the recovery or stuck in a bootloop.
I removed the PIN before I flashed Lineage 14.1 and my data partition is NOT encrypted
Any idea on what I am missing here?
Thanks

I had the same problem and I can't remember where I got the file from. But u flash it and the bootloop is gone this is what worked for me.

fidzi_1981 said:
Hello Guys,
I have been using xXx NoLimits 4.8 rom that is based on Oxygyn 4.5.15 ( android version 7.1.1) and now I would like to try Lineage 14.1.
I have TWRP 3.2.1 Blue Spark V8.61.
I wiped Data, Cache, System and Dalvik and flashed Lineage 14.1 and then flashed the addon supersu 64bit and then wipe dalvik and cache again and rebooted but the phone never booted into system. It kept on rebooting to the recovery or stuck in a bootloop.
I removed the PIN before I flashed Lineage 14.1 and my data partition is NOT encrypted
Any idea on what I am missing here?
Thanks
Click to expand...
Click to collapse
NOT encrypted mean you're decrypted? So with supersu you don't need to flash no verity, but instead of supersu try magisk and the no verity

Thanks
rolozombie said:
I had the same problem and I can't remember where I got the file from. But u flash it and the bootloop is gone this is what worked for me.
Click to expand...
Click to collapse
Thanks. This worked!
I have been researching the issue and I found out that since my DATA partition is decrypted and Lineage OS is an encrypted rom then bootloop occurs.

Thanks
Hitman478™ said:
NOT encrypted mean you're decrypted? So with supersu you don't need to flash no verity, but instead of supersu try magisk and the no verity
Click to expand...
Click to collapse
Correct. I meant to say that my data partition is decrypted.
What I ended up doing is flashing supersu addon from Lineage website followed by Magisk and then flashed no verity and everything works well so far
I also tried flashing supersu addon followed by no verity and it works too ( I wanted to give it a shot in case I decided I did not want to use magisk)
Thanks again for the tip!

[FIX][8.1][Treble]Decryption Unsuccessful and TWRP Internal Storage 0MB

As the tittle says, this is my current workaround for issues that happened after most people update their AOSP based ROMs after 3rd July 2018.
Decryption Unsuccessful
Q: Why does this happens ?
A: There's some weird issues with the latest AOSP based ROM that makes encrypted ext4 based data partition unable to be decrypted in both system and older version of TWRP if you're encrypted before (intentionally or unintentionally). This however doesn't apply to F2FS and unencrypted ext4 data partition.
Q: How do I solve this ?
A: There's 2 ways you can do to solve this issue.
The best way and the most recommended way is to repartition your data into F2FS. However it does require you to do a backup beforehand since this will wipe everything in your internal storage.
1. Backup your internal storage from TWRP (either to a SD card or PC via ABD)
2. Format it by going into TWRP and select Format and choose "wipe data"
3. Type "yes" and let the process end.
4. Flash your ROM and GApps.
5. Finish the setup without setting any screen lock so that it doesn't encrypt your data partition.
-Or-
The other way does is to install a custom kernel is made after 20 July 2018
List of kernel that can boot successfully without the need to wipe /data :
-Xenial b25x or newer
-Revolt EAS-R13
(Got kernel that works and doesn't show up here? TELL ME, I'll add it to my list for everyone's reference)
Link for the working TWRP that can detect Internal Storage :
Jairus' modded TWRP
https://androidfilehost.com/?fid=5862345805528049168
Or you can look up Orange Fox recovery
(link will be added soon)

Good Stuff Also This Happened to me while i was using the Android P DP3 i tried twrp and redwolf and was the same i flashed the Orange Fox and it worked

Does this twrp can flash both treble and non treble ROM?

eko_epe said:
Does this twrp can flash both treble and non treble ROM?
Click to expand...
Click to collapse
Yes, it does

AkmalWarrior said:
Yes, it does
Click to expand...
Click to collapse
Ok i'll try. Thanks

As the OP said, OrangeFox TWRP Recovery (R6-Beta) can decrypt encrypted data partitions.

DarthJabba9 said:
As the OP said, OrangeFox TWRP Recovery (R6-Beta) can decrypt encrypted data partitions.
Click to expand...
Click to collapse
TWRP and redwolf too (find on telegram)
Envoyé de mon Redmi Note 4 en utilisant Tapatalk

DarthJabba9 said:
As the OP said, OrangeFox TWRP Recovery (R6-Beta) can decrypt encrypted data partitions.
Click to expand...
Click to collapse
*Only in recovery, not in boot. The only way to fix decryption unsuccessful on boot is to either repartition data to F2FS or flash a custom kernel that's made after 20 July. List on working kernels is on main thread.

First I tried orange fox beta and it showed my internal storage
Then I flashed the RR endless
But the encryption was still there
Then I tried the twrp from this thread and flashed rom with latest xenial
And it worked no problem
Thank you

How for steps come from nougat Rom up to Oreo, should i flash xenial kernel directly after the ROM flashed? i want flash Aicp Oreo currently i'm on Los14.1

DarksTor said:
How for steps come from nougat Rom up to Oreo, should i flash xenial kernel directly after the ROM flashed? i want flash Aicp Oreo currently i'm on Los14.1
Click to expand...
Click to collapse
Sine you are using nougat i recommend to format data (wipes internal storage) so take a backup if you want
And I have also seen users reporting bugs about aicp oreo on telegram so try some other ROMs like resurrection remix,screwd,lineage os extended,aex ........
All oreo Roms are now treble
So use treble twrp
And treble magisk

antony felix said:
Sine you are using nougat i recommend to format data (wipes internal storage) so take a backup if you want
And I have also seen users reporting bugs about aicp oreo on telegram so try some other ROMs like resurrection remix,screwd,lineage os extended,aex ........
All oreo Roms are now treble
So use treble twrp
And treble magisk
Click to expand...
Click to collapse
Thanks,So i must format internal too,. It's ok but how if i want to comeback use nougat..? I hear who's downgrade after using oreo will get "encryption was interrupted" on any nougat los/aosp base rom,should be format internal for working back the devices..
I think by this thread shared we get solution for who's want to downgrade from oreo without facing encryption issue enytime for oreo back to nougat or vice

DarksTor said:
How for steps come from nougat Rom up to Oreo, should i flash xenial kernel directly after the ROM flashed? i want flash Aicp Oreo currently i'm on Los14.1
Click to expand...
Click to collapse
Flash the rom and test it out if you can boot it. I think most rom now have native support for ext4 based data partition.
If you can't boot however, try one of the kernel listed on the OP.

What if i flash Jairus' modded TWRP from fastboot? Does it solve the encryption problem without losing all the data? Also does it work on non-treble roms?

AkmalWarrior said:
Flash the rom and test it out if you can boot it. I think most rom now have native support for ext4 based data partition.
If you can't boot however, try one of the kernel listed on the OP.
Click to expand...
Click to collapse
Finally i can confirm for fixed "encryption was interrupted" by changing data partition into F2FS, yes i think it's only way to get free from that, i'v been test it back to back from oreo down to nougat or vice, no worry anymore
Below screenshot for oreo left side and nougat in right

ngydna said:
What if i flash Jairus' modded TWRP from fastboot? Does it solve the encryption problem without losing all the data? Also does it work on non-treble roms?
Click to expand...
Click to collapse
Read the OP, the recovery only help you boot into recovery and format your data partition or flash a custom kernel to allow you to boot into system as this issue does affect some older version of TWRP recovery. The recovery alone can't help you boot into system.

I took out my sdcard and did format data on the internal storage and now i can't mount my sdcard. Didn't think about the fact that removing the encryption on the internal storage would make it unable to recognize the encryption on the sdcard afterwards. Is there any way to fix this? Or did I just screw myself?
---------- Post added at 01:53 PM ---------- Previous post was at 01:00 PM ----------
When I reinstalled the rom and tried to boot it still asks me for my password which still works even though I can't boot because it says that the data is corrupted. But the encryption key should still be stored somewhere apparently. There must be a way to use it to decrypt the sdcard.

Bootloop from Gapps (How to change partition back?) (ftfs tools?)

I changed my partitions to ext4 but it wont let me change my data partition back to f2fs, on account of TWRP not supporting f2fs tools... Im not sure if that would even solve the problem though. It seems flashing TO ext4 has helped some people bypass the open gapps bootloop and also removing the sim and using a terminal command to change build.prop… but none of these helped me.
I am running Omnirom 9.0 and it runs nice, fast and smooth without gapps, the problem only happens after flashing gapps and after that is just stays on the OMNI boot animation.
So far I've tried pico, nano, micro ARM 9.0
edit: now that I look at it, gapps mounts /persist and /system... so im just overall confused since the rom is running fine..