I'm formatting the data partition and because internal memory has to be erased every time I do so , I wanted to know Which is faster of the two types f2fs or Ext4 , Is there any difference between them in day to day use ?
Zezo9009 said:
I'm formatting the data partition and because internal memory has to be erased every time I do so , I wanted to know Which is faster of the two types f2fs or Ext4 , Is there any difference between them in day to day use ?
Click to expand...
Click to collapse
I'm not a tech geek but from experience, I know that for P2, f2fs is the way to go as ROMs tend to have better compatibility hence, better performance and less bugs.
alirazaagha said:
I'm not a tech geek but from experience, I know that for P2, f2fs is the way to go as ROMs tend to have better compatibility hence, better performance and less bugs.
Click to expand...
Click to collapse
How do i do that can u explain?
Currently on Havoc os 3.2 with Magisk 20.4 and recovery twrp 3.4 . How can I ?
suvam69 said:
How do i do that can u explain?
Currently on Havoc os 3.2 with Magisk 20.4 and recovery twrp 3.4 . How can I ?
Click to expand...
Click to collapse
Can you share download link for havoc os v3.2 to me?
suvam69 said:
How do i do that can u explain?
Currently on Havoc os 3.2 with Magisk 20.4 and recovery twrp 3.4 . How can I ?
Click to expand...
Click to collapse
It's a very simple process but take a backup of your necessary data inside internal memory as it will remove it all.
# Enter into latest twrp recovery. Take system/data backup if needed and click on Wipe.
# Select Advanced Wipe Settings
# Select Data and click on Repair or Change File System
# Select Change File System
# Now different data formats will be shown. Select f2fs and a warning will be shown for erasing data. Just go with it and reboot into recovery for installation again.
I've problems with LOS 17 so I figured I'd try f2fs before giving up. However having data and cache as f2fs gives me a bootloop with LOS.
Any ideas why that might be ?
Bipo said:
I've problems with LOS 17 so I figured I'd try f2fs before giving up. However having data and cache as f2fs gives me a bootloop with LOS.
Any ideas why that might be ?
Click to expand...
Click to collapse
Reflash stockrom again,
then flash official twrp from their site.
Wipe everything and before installing LOS
flash recommended twrp from LOS official rom tread.
Stock is using f2fs by default (at least for me it was).
I might be wrong but you should not change cache partition to f2fs only data (if it's not on f2fs after flasing stock).
alirazaagha said:
I'm not a tech geek but from experience, I know that for P2, f2fs is the way to go as ROMs tend to have better compatibility hence, better performance and less bugs.
Click to expand...
Click to collapse
I feel the same way, it's snappier on it.
A10 roms are on f2fs. If you ever want to flash a pie rom you have to wipe everything. And start from scratch
F2fs is the way to go imo
Related
Yes, I have don't the searches, and tried a ton of stuff including formatting portions. Seems this is working on the international version, and most nexus devices. Is the a thread that might help, or has anyone heard success stories with our device.
I really hate starting new threads, but sgh-i747 seems not to have the information out there for ways to getbf2fs working for data, cache, AND system.
Thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
Information on F2FS
There is some information in the Quantum thread starting with http://forum.xda-developers.com/showpost.php?p=53958476&postcount=17136 and several of the posts following it. I tried to get the ROM running but never could get the kernel to boot.
drbmm said:
There is some information in the Quantum thread starting with http://forum.xda-developers.com/showpost.php?p=53958476&postcount=17136 and several of the posts following it. I tried to get the ROM running but never could get the kernel to boot.
Click to expand...
Click to collapse
Same here.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Yes, I have don't the searches, and tried a ton of stuff including formatting portions. Seems this is working on the international version, and most nexus devices. Is the a thread that might help, or has anyone heard success stories with our device.
I really hate starting new threads, but sgh-i747 seems not to have the information out there for ways to getbf2fs working for data, cache, AND system.
Click to expand...
Click to collapse
Same question here, I can't even find the option to format data partition in f2fs. I installed latest version of TWRP (2.7.1.0) and I looked in Advanced wipes menu, I selected "Change filesystem" option and it showed me the filesystem choice menu, but I only get the option to use ext2, ext3, ext4 or fat, no f2fs option. I also tried with Philz recovery but I see no option for f2fs in it too.
Nico3d3 said:
Same question here, I can't even find the option to format data partition in f2fs. I installed latest version of TWRP (2.7.1.0) and I looked in Advanced wipes menu, I selected "Change filesystem" option and it showed me the filesystem choice menu, but I only get the option to use ext2, ext3, ext4 or fat, no f2fs option. I also tried with Philz recovery but I see no option for f2fs in it too.
Click to expand...
Click to collapse
philz has the option in mount advanced format and you have to toggle ext4-f2fs.
decronic has an successful method for the N5 and has been helpful in supplying tools to convert a rom f2fs and attempting to get me off the ground but the kernel seems to fail on my attempts.
here is a flashable zip to format system, data, and cache for the d2LTE devices. It will completely wipe the internals of the phone so be sure to have an external sd card prepared for your next steps.
"https://www.dropbox.com/s/4beylkg0gvhgitv/Format-All-Partitions-to-F2FS-d2lte.zip">https://www.dropbox.com/s/4beylkg0gvhgitv/Format-All-Partitions-to-F2FS-d2lte.zip
please keep me posted as I would really like to use the full potential of this device.
aircooledbusses said:
please keep me posted as I would really like to use the full potential of this device.
Click to expand...
Click to collapse
Will try when I come back from work. Supposedly CM11 is supported right out of the box, if you use newer than 06/30 version.
I'm attempting to make it work now. I installed Philz Recovery 6.48 instead of 6.26 and I now have the f2fs option. I tried formatting all partitions to f2fs (sytem, data and cache) and I modified the updater script, using the instructions in Quantum Kernel thread, but it failed to boot (won't go past boot splash screen). Now, I'll try to only format /data and /cache partitions.
Edit: using only f2fs on /data and /cache, it won't go past the boot animation. It's a pain in the ass for now, nothing's working.
Nico3d3 said:
I'm attempting to make it work now. I installed Philz Recovery 6.48 instead of 6.26 and I now have the f2fs option. I tried formatting all partitions to f2fs (sytem, data and cache) and I modified the updater script, using the instructions in Quantum Kernel thread, but it failed to boot (won't go past boot splash screen). Now, I'll try to only format /data and /cache partitions.
Edit: using only f2fs on /data and /cache, it won't go past the boot animation. It's a pain in the ass for now, nothing's working.[/QUOTE
try just data. cache always failed for me regardless of the kernel
Click to expand...
Click to collapse
It successfully booted by using f2fs only on /data but it stopped dead in its track, when it showed a screen telling me that encryption is unsucsessful and that I need to perform a factory reset. Looks like there's really no way at all to make it work. Flashing a different kernel didn't change anything.
Nico3d3 said:
It successfully booted by using f2fs only on /data but it stopped dead in its track, when it showed a screen telling me that encryption is unsucsessful and that I need to perform a factory reset. Looks like there's really no way at all to make it work. Flashing a different kernel didn't change anything.
Click to expand...
Click to collapse
No, there is a way. I'm not sure how to get system to stick. S3 mini has it, nexus devices, and others. it will happen soon I'm sure.
Sent from my Nexus 7 using XDA Premium 4 mobile app
thanks for ur efforts.
(trollin).
err on the side of kindness
http://review.cyanogenmod.org/#/c/68382/ maybe we'll be able to get it with what they added on the latest nightly
Quantum 5.2
Has anybody been able to get F2fs working on their s3? I have been experimenting for hours. So far ive gotten an infinite bootlogo formatting to f2fs and installing quantum 5.2. if i convert quantum 5.2 rom to f2fs and install it gets stuck on gimme pwncakes picture (kernel)
Edit: also getting the encryption error when formatting data only
f41lbl0g said:
Has anybody been able to get F2fs working on their s3? I have been experimenting for hours. So far ive gotten an infinite bootlogo formatting to f2fs and installing quantum 5.2. if i convert quantum 5.2 rom to f2fs and install it gets stuck on gimme pwncakes picture (kernel)
Edit: also getting the encryption error when formatting data only
Click to expand...
Click to collapse
Haven't managed to get it working yet.
I tried flashing a recent CM nightly (with the default kernel) in vanilla CWM, Philz Touch CWM, and TWRP and no luck with any of them. Flashing the Format-All-Partitions zip doesn't seem to work, and if I use the F2FS format options already included in Philz Touch, I am never able to mount /system afterwards. I didn't even have the option to switch to the new file system in TWRP.
So I'm not too sure what's going on. Is it a recovery issue? Or is our device somehow permanently limited to what file systems we can choose from? I'm out of ideas at this point.
f2fs s3
Theres barely any roms or kernels that support f2fs for the d2att s3. I think it has to do something with the compatibility of the rom. Pwncakes has said that his kernel does support f2fs, but im confused whether the rom supports f2fs. Also, most of the tools for f2fs are for the nexus devices, so there might be some error in the compatibility of them. Other devices like the i9300 have kernels that support f2fs as well as dualbooting, but it hasn't picked up for the d2att yet.
I'm not positive, but I think the kernel can be either-or, but the ROM can only be one or the other. So the ROM will have to be made specifically for f2fs.
compatibility
Major kernels such as Kt747, leankernel and QuantumKernel all support f2fs, but theres no compatible rom to go with it. I would love the speed boost of f2fs on my phone if it were possible.
The interesting thing is I tried the F2FS ROM converter tool that was posted in the Quantum thread. The output zip looked like it did in fact have some changes to reflect support for the file system, but I still couldn't get past the kernel image on boot with TWRP. With Philz Touch, I was still unable to mount /system after flashing the ROM.
Sent from my SAMSUNG-SGH-I747
I have a feeling that the slimkat rom will work with f2fs. Im going to try it out along with quantum kernel or kt747
f41lbl0g said:
I have a feeling that the slimkat rom will work with f2fs. Im going to try it out along with quantum kernel or kt747
Click to expand...
Click to collapse
please post back your progress. Device maintainer said that it has something to do with the Fstab that is preventing it from working for us.
my expirience with Dechronic's rom converter is that it makes use of a modified boot image. I fear the one I have is too old to working with so I am sort of stuck waiting for a further development. its a shame too, I have a spare S3 I can be a little risky with.
Would it be possible to format the file system on this tablet for use with F2FS and how would I go by doing so if yes?
Grizzly6117 said:
Would it be possible to format the file system on this tablet for use with F2FS and how would I go by doing so if yes?
Click to expand...
Click to collapse
You'd need a custom Kernel.....I'm not aware of one that supports F2FS but can I ask a dumb question....why? There's still no Stable release out yet is there?
Yes. In addition to a F2FS enabled custom kernel, you would require an enabled custom recovery.
My SkyHigh kernel has in built F2FS support but never tested
UpInTheAir said:
Yes. In addition to a F2FS enabled custom kernel, you would require an enabled custom recovery.
My SkyHigh kernel has in built F2FS support but never tested
Click to expand...
Click to collapse
Yeah, I know by my post that I made my self to be clueless on things like this just wanted to see if people have already tested on this for this, I'm considering changing one of the ROMs to f2fs and test your kernel for f2fs compatibility, I'm just worried about bricking as I am on contract with this device but I don't see why I couldn't recover everything flashing stock with Samsung kies
F2FS
I managed to convert SuperSamsung v2 to F2FS by using a F2FS converter script I got from the Nexus 7 side of the forums and used your latest SkyHighKernel to boot into F2FS succesfully
EDIT: Feels snappier and less stutter, the major improvement atm is App Loading times
Grizzly6117 said:
I managed to convert SuperSamsung v2 to F2FS by using a F2FS converter script I got from the Nexus 7 side of the forums and used your latest SkyHighKernel to boot into F2FS succesfully
EDIT: Feels snappier and less stutter, the major improvement atm is App Loading times
Click to expand...
Click to collapse
Sweet. Can you please link to the script thread, and did you need to modify it for our device partition table?
UpInTheAir said:
Sweet. Can you please link to the script thread, and did you need to modify it for our device partition table?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2731666
Thats the Script I used, didnt change anything, but during the process when it asks what boot.img to use, you can select to use your own, and I simply just pulled it from your Kernel and placed into the folder directory, but I did flash the kernel zip anyway once flashing the ROM, I changed System and Cache to F2FS first, flashed ROM etc. then rebooted recovery and converted Data to F2FS, which wipes everything on internel Memory, so i kept my backup of everything on my External SD
Grizzly6117 said:
http://forum.xda-developers.com/showthread.php?t=2731666
Thats the Script I used, didnt change anything, but during the process when it asks what boot.img to use, you can select to use your own, and I simply just pulled it from your Kernel and placed into the folder directory, but I did flash the kernel zip anyway once flashing the ROM, I changed System and Cache to F2FS first, flashed ROM etc. then rebooted recovery and converted Data to F2FS, which wipes everything on internel Memory, so i kept my backup of everything on my External SD
Click to expand...
Click to collapse
Good stuff. Glad the kernel worked so far.
I clean flashed the Nougat beta 8 on FreedomOS CE 1.11 which is based on OOS beta 7) and I still have ext4 as my filesystem.
The thing works fine except I get serious lags during gaming. I am not sure if this is because of ext4 but I would love to try out F2FS.
Is there any way I can get to F2FS with minimal effort?
Or do I just have to clean flash 3.2.8, factory reset and then flash the beta?
I am basically looking for a better idea than above, if one exists.
Thanks!
mharis05 said:
l
The thing works fine except I get serious lags during gaming. I am not sure if this is because of ext4 but I would love to try out F2FS.
Click to expand...
Click to collapse
i am 100% sure that the lag you are facing is definitely not due to ext4.
If this game lags on ext4 then this game will also lag on f2fs
JumboMan said:
i am 100% sure that the lag you are facing is definitely not due to ext4.
If this game lags on ext4 then this game will also lag on f2fs
Click to expand...
Click to collapse
Acknowledged.
Can you advise if I still want to get F2Fs anyway?
mharis05 said:
Acknowledged.
Can you advise if I still want to get F2Fs anyway?
Click to expand...
Click to collapse
I will not advise converting partition to f2fs cause there will be no noticeable gain.
and converting partition to f2fs is lot of work. it requires backup of all stuff to pc , formatting whole partition.
And to use f2fs you have to flash custom kernel.
And even after doing this it will give Little to no benefit in real life usage.
===
in short if you are happy with current setup then keep as it is. but if you want to play with fire then go ahead.
mharis05 said:
Acknowledged.
Can you advise if I still want to get F2Fs anyway?
Click to expand...
Click to collapse
to get f2fs you'll have to wipe the partition you're converting,
get modified TWRP .28 , and in recovery go to advanced wipe, select data (or system) and then got to Repair or change File System.. in there select change file system, and there choose f2fs, after it's done go back to advanced wipe and wipe data ...repeat if you also want system (or internal storage) to be f2fs... DO It at you're OwnRisk
JumboMan said:
I will not advise converting partition to f2fs cause there will be no noticeable gain.
and converting partition to f2fs is lot of work. it requires backup of all stuff to pc , formatting whole partition.
And to use f2fs you have to flash custom kernel.
And even after doing this it will give Little to no benefit in real life usage.
===
in short if you are happy with current setup then keep as it is. but if you want to play with fire then go ahead.
Click to expand...
Click to collapse
Strange, I understand that a lot of people exaggerate when it comes to their phone's performance and battery, quite a few users reported noticeable difference after switching partitions.
Maybe because of the whole data wiping the phone got snappier and they mistook it for filesystem performance.
Also, I also read a few places that OOS 3.2.8 came with f2fs as default, i.e. if you factory reset, you can get f2fs with the stock kernel.
theduke7 said:
to get f2fs you'll have to wipe the partition you're converting,
get modified TWRP .28 , and in recovery go to advanced wipe, select data (or system) and then got to Repair or change File System.. in there select change file system, and there choose f2fs, after it's done go back to advanced wipe and wipe data ...repeat if you also want system (or internal storage) to be f2fs... DO It at you're OwnRisk
Click to expand...
Click to collapse
I already have TWRP .28 so that can be marked done.
I was reluctant on converting the partition using TWRP in the anticipation that it might give me a bootloop or something since I am on the Nougat beta which may not be too happy with TWRP filesystem conversion.
Can you tell if this should work on Nougat beta or you want me to try myself :silly:
mharis05 said:
Also, I also read a few places that OOS 3.2.8 came with f2fs as default, i.e. if you factory reset, you can get f2fs with the stock kernel.
Click to expand...
Click to collapse
No.
Stock kernel on oos 328 doesn't support f2fs. for f2fs you have to flash custom kernel like elementalx, blu_spark, etc.
JumboMan said:
No.
Stock kernel on oos 328 doesn't support f2fs. for f2fs you have to flash custom kernel like elementalx, blu_spark, etc.
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...m-and-how-to-get-it-on-your-oneplus-3.474072/
See the forum above, F2FS is supported by the Community builds with stock kernel..
mharis05 said:
https://forums.oneplus.net/threads/...m-and-how-to-get-it-on-your-oneplus-3.474072/
See the forum above, F2FS is supported by the Community builds with stock kernel..
Click to expand...
Click to collapse
community builds are different from stock oos.
latest community builds support f2fs but not oos
Also, don't forget that stock OB8 only has support for F2FS on the /data partition, not the other partitions.
mharis05 said:
I already have TWRP .28 so that can be marked done.
I was reluctant on converting the partition using TWRP in the anticipation that it might give me a bootloop or something since I am on the Nougat beta which may not be too happy with TWRP filesystem conversion.
Can you tell if this should work on Nougat beta or you want me to try myself :silly:
Click to expand...
Click to collapse
yes it should work N Beta , but as mentioned above in another comment the N beta supports f2fs only on data so only convert the data partition...
you wont get bootloop as long as you stay on TWRP .28, i did get a bootloop when i flashed the official TWRP, actually i got a black screen then bootloop (was a bad situation)...so stay at ..28 as long as you're on Nougat and/or with the N beta firmware( because some CM roms require you to have the N beta firmware) other versions of TWRP are not compatible with N beta firmware
you'll get an extra messege about dm-verity ilike the one about the unlocked bootloader but that's normal.
if you want to go back you need to 1st convert the data back to ext4 , then flash the oos 3.2.6 (or above 3.2.7 or 3.2.8) firmware and modem (firmware only available on the forums) and then wipe everything then flash official TWRP then reboot back to recovery (official twrp) then follow the regular flashing procedures.(i prefer doing 1 more wipe on official TWRP), also after a full wipe that includes internal storage you need to reboot back to recovery (not system) then copy the required files back to internal storage and flash
mharis05 said:
I clean flashed the Nougat beta 8 on FreedomOS CE 1.11 which is based on OOS beta 7) and I still have ext4 as my filesystem.
The thing works fine except I get serious lags during gaming. I am not sure if this is because of ext4 but I would love to try out F2FS.
Is there any way I can get to F2FS with minimal effort?
Or do I just have to clean flash 3.2.8, factory reset and then flash the beta?
I am basically looking for a better idea than above, if one exists.
Thanks!
Click to expand...
Click to collapse
you should wait for the official 7.0 from oneplus. like I am. if you gain f2fs system, there won't be any performance improvement or whatsoever.
Backup your data and do factory reset you'll get f2fs. In my experience my OP3 feels snappier. Cold start of apps are improved.
Wiped the /data partition using TWRP (28) without selecting System or internal storage.
Now /data partition is f2fs - which is the intended partition as per OnePlus.
Thread can be closed.
So, I unlocked my bootloader and wanted to flash Lineage OS, but my phone had a different opinion.
I went into TWRP and tried to format data, but I'm getting
Code:
Formatting Data using mkfs.f2fs...
mkfs.f2fs -t 0 -r 16384 /dev/block/mmcblk0p56
process ended with ERROR: 1
Unable to wipe Data.
Unable to format to remove encryption.
I've tried repairing the data partition, changing the filesystem, nothing works...
Any ideas as to what might be wrong, or how to fix it?
Thanks
todorare said:
So, I unlocked my bootloader and wanted to flash Lineage OS, but my phone had a different opinion.
I went into TWRP and tried to format data, but I'm getting
I've tried repairing the data partition, changing the filesystem, nothing works...
Any ideas as to what might be wrong, or how to fix it?
Thanks
Click to expand...
Click to collapse
Which recovery are u using ?
Armaty said:
Which recovery are u using ?
Click to expand...
Click to collapse
I was using TWRP, but I somehow managed to fix it using Redwolf. Have no idea what happened, but it's ok now.
Hello, I encountered the exact same issue with same origin...
Do you remember what you did to sort this out ?
thanks
(I posted in another thread, before finding yours)
You should check the f2fs kernel workaround guide .
Your problem is due to using incompatible twrp .
Read the guide you'll get around the problem .
0101chaitanya said:
You should check the f2fs kernel workaround guide .
Your problem is due to using incompatible twrp .
Read the guide you'll get around the problem .
Click to expand...
Click to collapse
Thanks... well that's weird, because I downloaded the TWRP recovery linked in LineageOs kuntao install page and I'm coming from stock...
Anyway I just solved my issue by installing Redwolf recovery :
There I could format /data.
I installed crdroid + gapps, but got a "Encryption Unsuccessful" on reboot.
I changed /data from f2fs to ext4 and could reboot properly.
Phone is working good. (I can't get fingerprint reader to unlock my crdroid rom but that's another story and maybe normal limitation, I'll check).
eljuggy said:
Thanks... well that's weird, because I downloaded the TWRP recovery linked in LineageOs kuntao install page and I'm coming from stock...
Anyway I just solved my issue by installing Redwolf recovery :
There I could format /data.
I installed crdroid + gapps, but got a "Encryption Unsuccessful" on reboot.
I changed /data from f2fs to ext4 and could reboot properly.
Phone is working good. (I can't get fingerprint reader to unlock my crdroid rom but that's another story and maybe normal limitation, I'll check).
Click to expand...
Click to collapse
If you ever need to format data just use official build from twrp.me. The one from Lineage wiki has some problems for now. Redwolf is probably based on official one, that's why you succeded.
The thing is that you need to use it ONLY to format /data partition and then switch back to Lineage one before flashing system zip. Known problem, wiki is just a little misguiding here.
Hello. Same problem here, not solved with RedWolf, neither official TWRP.
I've just followed the guide about lineage 15.1 and I really don't know how/if proceed.
Any help would be really appreciated
trespass23 said:
Hello. Same problem here, not solved with RedWolf, neither official TWRP.
I've just followed the guide about lineage 15.1 and I really don't know how/if proceed.
Any help would be really appreciated
Click to expand...
Click to collapse
Update: after closing and run again RedWolf, tap to Format data, magically it worked. I don't know why but thats'it.
Thanks.
this issue seems to pop-up now and then.
just to make it easier for future users coming across this issue. I had explained the issue here in the following post and how to fix it.
just scroll down till it says: "so for those that would like to switch to f2fs but for some reason end up in "black screen with blue led and the phone vibrates".
it applys to the same /data issue.
page 25 off official lineageos 8.1 thread:
https://forum.xda-developers.com/lenovo-p2/development/rom-lineageos-15-1-p2-t3814361/page25
What kind of recovery is recovery-oneplus7t-3.4.2-10.0-b26.img? is it the chinese TWRP one?
altojd said:
What kind of recovery is recovery-oneplus7t-3.4.2-10.0-b26.img? is it the chinese TWRP one?
Click to expand...
Click to collapse
Yes
Where did you find it ?
Any idea why after flashing recovery-oneplus7t-3.4.2-10.0-b26.img (chinese twrp) being in recovery mode i don't see ANYTHING in sdcard?
altojd said:
Any idea why after flashing recovery-oneplus7t-3.4.2-10.0-b26.img (chinese twrp) being in recovery mode i don't see ANYTHING in sdcard?
Click to expand...
Click to collapse
Please could you pm the link to this recovery please l think flashing this recovery will format your data because it changes the file system which is why it works
a g bell said:
Please could you pm the link to this recovery please l think flashing this recovery will format your data because it changes the file system which is why it works
Click to expand...
Click to collapse
i found this recovery in msm extended telegram chat.
the installation did not format my data since i have all my apps working and i can see the entire internal storage when i connect the phone to pc.
I have this recovery on my device for a later time in case I decide to move away from OOS so I can't speak to experience...BUT:
My understanding is due to decryption/recovery on this device the chinese recovery will work BUT the limitations are that if you are on OOS currently you cannot decrypt storage, HENCE you will not see anything in TWRP (again that is my understanding). After backing up the device and wiping the data partition at minimum (most custom roms seem to require us to fastboot wipe our partitions from instructions ive read)... then we can use this version of recovery for custom roms.
I think the major difference between this one and the official version here is of course the unofficial nature of this twrp but also the chinese twrp will let you flash (not boot) the recovery image without issue so we can still USE OOS OR flash custom roms without things going...wrong?...I plan to wait until the A11 OOS upgrade before I make a decision. After learning about how 1P botched the recovery keys + partition issues with the A10 launch I think its just better to see how development goes AFTER the new year maybe
Hmm l was of the understanding that if you format using the chinese recovery all will work on oos will see what's what and report back as soon as l find it and flash it
So flashed Chinese twrp couldn't mount data until l formatted data using it then l could see everything in storage but it reverted after a reboot and would need formatting again to see storage also it seems much more functional that the mauronofrio twrp but the decryption issue is still an issue for me at least. It's ashame nobody is working on this to give us a better twrp.
a g bell said:
Hmm l was of the understanding that if you format using the chinese recovery all will work on oos will see what's what and report back as soon as l find it and flash it
So flashed Chinese twrp couldn't mount data until l formatted data using it then l could see everything in storage but it reverted after a reboot and would need formatting again to see storage also it seems much more functional that the mauronofrio twrp but the decryption issue is still an issue for me at least. It's ashame nobody is working on this to give us a better twrp.
Click to expand...
Click to collapse
What's "this"? And what do you mean nobody?
Check twrp gerrit and github and you'll see lots of progress. Fastbootd has been implemented, and dynamic partitions are pretty much handled now. Only significant thing would be decryption, but let's hope Android 11 fixes this as Google once again has changed things regarding to keystore.
Lossyx said:
What's "this"? And what do you mean nobody?
Check twrp gerrit and github and you'll see lots of progress. Fastbootd has been implemented, and dynamic partitions are pretty much handled now. Only significant thing would be decryption, but let's hope Android 11 fixes this as Google once again has changed things regarding to keystore.
Click to expand...
Click to collapse
Ok l stand corrected just wondering why mauronofrio hasn't released an update or updated his thread. So OnePlus have to implement changes to keystore with Android 11 so they might fix it ?