I'm currently running OOS 9.5.13 with arter97's kernel. I converted the data partition to f2fs and it have been very stable for me. Can anyone tell me if the stock OOS kernel still supports f2fs? I suspect it does since I was temporarily running the stock kernel after the 9.5.13 OTA, and didn't get any errors from apps trying to access data on the phone.
Not interested in formatting my data partition, and if it does not support it, I will just wait for an updated kernel before going to 10.
NotATreoFan said:
I'm currently running OOS 9.5.13 with arter97's kernel. I converted the data partition to f2fs and it have been very stable for me. Can anyone tell me if the stock OOS kernel still supports f2fs? I suspect it does since I was temporarily running the stock kernel after the 9.5.13 OTA, and didn't get any errors from apps trying to access data on the phone.
Not interested in formatting my data partition, and if it does not support it, I will just wait for an updated kernel before going to 10.
Click to expand...
Click to collapse
It's working fine. I'm on f2fs Android 10 stock kernel. Waiting for arter kernel as well.
keaheng said:
It's working fine. I'm on f2fs Android 10 stock kernel. Waiting for arter kernel as well.
Click to expand...
Click to collapse
Thanks! That's what I was hoping for.
keaheng said:
It's working fine. I'm on f2fs Android 10 stock kernel. Waiting for arter kernel as well.
Click to expand...
Click to collapse
How????? IS there any guide to convert to f2fs? I tried and tried and it never works no matter what guide I've used.
I have TWRP, convert data partition to f2fs, all from a fresh wipe. I installed oos and it never boots; always into recovery. FOR YEARS. EVEN ON MY OP5T. The guide is clearly not working for me and never has.
JhinCuatro said:
How????? IS there any guide to convert to f2fs? I tried and tried and it never works no matter what guide I've used.
I have TWRP, convert data partition to f2fs, all from a fresh wipe. I installed oos and it never boots; always into recovery. FOR YEARS. EVEN ON MY OP5T. The guide is clearly not working for me and never has.
Click to expand...
Click to collapse
Did you install OOS after converting to f2fs? You cannot convert without a clean install after.
NotATreoFan said:
Did you install OOS after converting to f2fs? You cannot convert without a clean install after.
Click to expand...
Click to collapse
Tried that (via twrp i guess?). Only reboots to recovery. Already wasted hours, and I assumed the guide was supposed to pretty much actually say what to do, which it clearly doesn't if another oos installation was needed after (which i already did anyway..)
Guess f2fs will only be worth considering in the next few years; not worth all the problems just for a marginal increase in performance on an alreasy fast phone.
Format Data, reboot to TWRP, convert to f2fs, install OOS OTA, reboot. If you wind up in stock recovery, do a factory reset from there, and then it will boot.
Sent from my GM1915 using Tapatalk
Related
I can't figure this out for the life of me.
I grabbed the latest weekly for the find7op from the official site, but I can never get past the boot animation.
Running the c7-00011 firmware, F2FS on /data and /cache, no custom kernel or gapps or anything that might make it hang.
Am I missing something here?
JJohnson1988 said:
I can't figure this out for the life of me.
I grabbed the latest weekly for the find7op from the official site, but I can never get past the boot animation.
Running the c7-00011 firmware, F2FS on /data and /cache, no custom kernel or gapps or anything that might make it hang.
Am I missing something here?
Click to expand...
Click to collapse
omnirom doesnt support f2fs
convert to ext4 data chace n system to make omni rom boot up
Minions_Army said:
omnirom doesnt support f2fs
convert to ext4 data chace n system to make omni rom boot up
Click to expand...
Click to collapse
Really? I figured everything supported it by now. Well, I'll try again some other day then.
Thanks for the prompt reply.
Whenever I try to return to stock EMUI 5.0.1 from Lineage OS 14.1 with my TWRP backup, it just stays at the boot screen that says "Honor" and doesn't continue past that point. I was wondering why this happens and what I can do to fix this since I want to return back to stock without doing the painful dload method. I currently have TWRP 3.1.1-0 OpenKirin Edition, the same version I used to make the backup too.
Which LineageOS ROM do you have, OpenKirin's or HassanMirza01's..?
RedSkull23 said:
Which LineageOS ROM do you have, OpenKirin's or HassanMirza01's..?
Click to expand...
Click to collapse
I have the one by HassanMirza01
SenyorMauricio said:
I have the one by HassanMirza01
Click to expand...
Click to collapse
Did you already formatted data partition back to ext4 before trying to restore the backup? Hassan's roms are f2fs based, so you won't be able to restore an ext4 based rom over f2fs
RedSkull23 said:
Which LineageOS ROM do you have, OpenKirin's or HassanMirza01's..?
Click to expand...
Click to collapse
RedSkull23 said:
Did you already formatted data partition back to ext4 before trying to restore the backup? Hassan's roms are f2fs based, so you won't be able to restore an ext4 based rom over f2fs
Click to expand...
Click to collapse
Should I do that before restoring the backup? I've done it after restoring the backup, and it doesn't do anything but mess up TWRP's permissions.
RedSkull23 said:
Did you already formatted data partition back to ext4 before trying to restore the backup? Hassan's roms are f2fs based, so you won't be able to restore an ext4 based rom over f2fs
Click to expand...
Click to collapse
It booted up whenever I changed it back to ext4, but it comes up with a screen saying "Unencryption Unsuccessful" whenever I boot up. I click on reset phone, and it brings back to TWRP. This even happens if I reset the phone via TWRP. I'm not sure if this process would work if I restored the stock recovery, but I'm not sure if I want to find out.
SenyorMauricio said:
It booted up whenever I changed it back to ext4, but it comes up with a screen saying "Unencryption Unsuccessful" whenever I boot up. I click on reset phone, and it brings back to TWRP. This even happens if I reset the phone via TWRP. I'm not sure if this process would work if I restored the stock recovery, but I'm not sure if I want to find out.
Click to expand...
Click to collapse
Whenever I formatted data through the stock e-Recovery (the stock portion of the recovery that stays even with TWRP), it booted up perfectly fine! Thanks for all your help!
SenyorMauricio said:
Whenever I formatted data through the stock e-Recovery (the stock portion of the recovery that stays even with TWRP), it booted up perfectly fine! Thanks for all your help!
Click to expand...
Click to collapse
Nice one dude
I have successfully decrypted my essential phone using the dm verity disabler by zackptg. Need to test it some more, but twrp boots after flashing it, instantly.it doesn't have that lag
jacksummers said:
I have successfully decrypted my essential phone using the dm verity disabler by zackptg. Need to test it some more, but twrp boots after flashing it, instantly.it doesn't have that lag
Click to expand...
Click to collapse
were u rooted before or not? did u have to format everything in twrp?
edit it actually works!!!!!! I'm unencrypted...i can go into twrp while a pin is set....i can flash magisk with first boot of a rom and it boots...!!!!!
This is a huge advancement. I didn't think it worked until I booted into twrp. And it was instantaneous.so before I flashed the dm verity decryption zip, I did indeed wipe everything on both slots, then mounted system in twrp and flashed the zip, then I flashed the ROM.i will be switching back to stock to test if it stays decrypted later today. I'm running a gsi,(benzo ROM+ all my own customizations)rooted,with all the trimmings) the same mentality will have to follow, but it will be interesting to see how it goes with flashing stock fresh. I imagine restoring my nandroid will be fine and stay decrypted, but probably will have to flash stock, then after setup, back to twrp, wipe factory reset and flash the dm verity decryption zip..I think, I gotta just do it to be sure. Anyone who does this should share notes and that will help the community.
Here is a good question, wtf can I do to have lte again. ever since pie official, I lost lte.phone drops to 3g during calls only. I discovered this while searching for a fix for my volte. Hence,, switching to gsi's because they don't have volte and neither does my stock, even with fresh installs.i have t mobile.all the betas it worked fine.
Here's the thread folks
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Thanks to Zackptg
jacksummers said:
This is a huge advancement. I didn't think it worked until I booted into twrp. And it was instantaneous.so before I flashed the dm verity decryption zip, I did indeed wipe everything on both slots, then mounted system in twrp and flashed the zip, then I flashed the ROM.i will be switching back to stock to test if it stays decrypted later today. I'm running a gsi,(benzo ROM+ all my own customizations)rooted,with all the trimmings) the same mentality will have to follow, but it will be interesting to see how it goes with flashing stock fresh. I imagine restoring my nandroid will be fine and stay decrypted, but probably will have to flash stock, then after setup, back to twrp, wipe factory reset and flash the dm verity decryption zip..I think, I gotta just do it to be sure. Anyone who does this should share notes and that will help the community.
Here is a good question, wtf can I do to have lte again. ever since pie official, I lost lte.phone drops to 3g during calls only. I discovered this while searching for a fix for my volte. Hence,, switching to gsi's because they don't have volte and neither does my stock, even with fresh installs.i have t mobile.all the betas it worked fine.
Click to expand...
Click to collapse
How did u get wifi to work on gsi..for me i can seem to get it working..and im using the last 8.1 vendor....for the lte go into dialer and *#*#4636#*#* and change the lte/utms/cdma setting around until u get it
Tech_Savvy said:
How did u get wifi to work on gsi..for me i can seem to get it working..and im using the last 8.1 vendor....for the lte go into dialer and *#*#4636#*#* and change the lte/utms/cdma setting around until u get it
Click to expand...
Click to collapse
I have found that after booting up a gsi, factory reset it. Then be sure not to root with magisk. Every time I tried it killed my data and wifi. Use phhhsuperuser ab zip. I think I may have had to flash my modem.img a time as well after the initial install.
And yeah I got it kinda, still no lte. I'm gonna try a modem img from the pie firmware..I think it is the problem
Has anyone had success in decrypting on stock? I cant get it and then i lose touch with the phone booted up. So in other words do not try to decrypt stock. U will wreck your phone and the only way to fix it is to flash stock via fastboot AND adb sideload. One or the other doesnt fix it for some reason. Has to be both.
jacksummers said:
Has anyone had success in decrypting on stock? I cant get it and then i lose touch with the phone booted up. So in other words do not try to decrypt stock. U will wreck your phone and the only way to fix it is to flash stock via fastboot AND adb sideload. One or the other doesnt fix it for some reason. Has to be both.
Click to expand...
Click to collapse
Were you trying on stock oreo or pie?
governmentissuejoe said:
Were you trying on stock oreo or pie?
Click to expand...
Click to collapse
Both
jacksummers said:
Both
Click to expand...
Click to collapse
I tried it on stock Oreo and it works.
governmentissuejoe said:
I tried it on stock Oreo and it works.
Click to expand...
Click to collapse
Ok cool, I was worried I did this as a fluke. What was the steps u did?
jacksummers said:
Ok cool, I was worried I did this as a fluke. What was the steps u did?
Click to expand...
Click to collapse
So these are all the steps I took to get it to work. All of these steps may or may not be necessary. I used aer0zer0's stock dump for the lastest release of oreo and flashed the wipe all bat. It did its thing and wiped and flashed on both slots. I booted into the rom and finished initial setup and enabled adb in developer settings. I rebooted to bootloader and flashed twrp to inactive slot. I booted into recovery and selected the format data option and typed yes. I rebooted to bootloader and reflashed twrp. When I booted into recovery I transferred the stockboot.img, magisk 17.1 zip, and disable encryption zip to the phone. I flashed the stockboot.img to the boot partition. I then flashed the disable encryption zip. I then mounted the system partition and flashed the magisk zip. Finally, I rebooted into the rom and set pin and fingerprint. I installed EX Kernel Manager and created a backup of the decrypted magisked boot.img just in case. I flashed twrp through ex kernel manager and rebooted to recovery. Everything stayed decrypted. I flashed my newly created boot.img backup and booted back to my rom. Thats it. I hope I remembered everything. I hope this helps. Again, I do not know if all the steps I took are required but it worked for me.
I'm not able to run any non-MIUI rom (LOS or AOSP - it doesn't matter). I have TWRP 3.3.0.0 and latest MIUI firmware installed, When I'm flashing the rom (rom+gapps to be precise), the process finishes successfully but I'm stuck on ROM boot animation forever. What could go wrong?
Edit: I'm wiping data+system+cache of course.
watchoutbehindyou said:
I'm not able to run any non-MIUI rom (LOS or AOSP - it doesn't matter). I have TWRP 3.3.0.0 and latest MIUI firmware installed, When I'm flashing the rom (rom+gapps to be precise), the process finishes successfully but I'm stuck on ROM boot animation forever. What could go wrong?
Edit: I'm wiping data+system+cache of course.
Click to expand...
Click to collapse
You need to pick the "format" option and wipe complete internal storage
Your issue is due to encryption which was done by the miui rom
malimukk said:
You need to pick the "format" option and wipe complete internal storage
Your issue is due to encryption which was done by the miui rom
Click to expand...
Click to collapse
Yes, I did it. I did the format option when you have to type "yes". Process of flashing goes fine but rom is stuck on the boot animation for 7-8 minutes (maybe more). It looks like that encryption is the problem because MIUI roms are loading fine, but I wiped literally EVERYTHING, with format internal storage included.
Maybe I should try with different TWRP?
I'm a little afraid to go for the older version because I've already flashed 3.3.0.0...
watchoutbehindyou said:
Yes, I did it. I did the format option when you have to type "yes". Process of flashing goes fine but rom is stuck on the boot animation for 7-8 minutes (maybe more). It looks like that encryption is the problem because MIUI roms are loading fine, but I wiped literally EVERYTHING, with format internal storage included.
Maybe I should try with different TWRP?
I'm a little afraid to go for the older version because I've already flashed 3.3.0.0...
Click to expand...
Click to collapse
The TWRP version should be fine. Then another potential issue at this moment would be if you are flashing on the latest version of MIUI. Or more precisely, the latest firmware and vendor version..
Perhaps you can try to flash the firmware from MIUI 9.2.28 Developer version. Then Format and install a custom rom.
Good luck!
watchoutbehindyou said:
I'm not able to run any non-MIUI rom (LOS or AOSP - it doesn't matter). I have TWRP 3.3.0.0 and latest MIUI firmware installed, When I'm flashing the rom (rom+gapps to be precise), the process finishes successfully but I'm stuck on ROM boot animation forever. What could go wrong?
Edit: I'm wiping data+system+cache of course.
Click to expand...
Click to collapse
Try the earlier Miui versions eg. 9.3.28. The latest caused mine to show the bootlogo indefinitely!
The rest of your procedure should be fine!
Great!
kleinholzinferno said:
Try the earlier Miui versions eg. 9.3.28. The latest caused mine to show the bootlogo indefinitely!
The rest of your procedure should be fine!
Click to expand...
Click to collapse
Thank you! Had the same problem and your solution worked for me just fine
I break my system a lot (currently testing which of my favorite Xposed modules work with Pie) . I've had to set up from scratch like 6 times in the past week. Every TWRP restore results in a boot loop, both custom and stock. Has anyone made it work and, if so, how? It surprises me that our TWRP is official if it can't restore a backup.
Encrypted?
arkansawdave74 said:
I break my system a lot (currently testing which of my favorite Xposed modules work with Pie) . I've had to set up from scratch like 6 times in the past week. Every TWRP restore results in a boot loop, both custom and stock. Has anyone made it work and, if so, how? It surprises me that our TWRP is official if it can't restore a backup.
Click to expand...
Click to collapse
I'm having the same problem. This is my first a/b device and everything I thought I knew after flashing ROMs for years just doesn't seem to work on this architecture. Like you said twrp backup restore always results in a bootloop. Also any full custom ROMs I've tried appear to overwrite twrp and install its own recovery. Even gsi's don't boot and then twrp freezes and back to stock I go. This thing has me stumped.
Skippy12359 said:
I'm having the same problem. This is my first a/b device and everything I thought I knew after flashing ROMs for years just doesn't seem to work on this architecture. Like you said twrp backup restore always results in a bootloop. Also any full custom ROMs I've tried appear to overwrite twrp and install its own recovery. Even gsi's don't boot and then twrp freezes and back to stock I go. This thing has me stumped.
Click to expand...
Click to collapse
I noticed when installing RR that it actually needs that Lineage recovery to factory reset after the install. A TWRP factory reset wouldn't help it, and it wouldn"t boot after the install. Funny how they try so hard to stop us tinkerers, then steal all our cool ideas for their stock ROMs. I see Linux phones in my future.
I wonder if a factory reset with that Lineage recovery would help after a TWRP restore? Next time I may try that.
Damn! I just got it. I'm typing this on a restored crDroid Official. The boot.img is in ramdisk, so only backup system and data. Yay!
WoKoschekk said:
Encrypted?
Click to expand...
Click to collapse
Just saw this. No. I had flashed dm-verity. Good thinking.
arkansawdave74 said:
Damn! I just got it. I'm typing this on a restored crDroid Official. The boot.img is in ramdisk, so only backup system and data. Yay!
Click to expand...
Click to collapse
So your saying because recovery is in the boot image that we need only to backup system and data and then a restore of same will not go into a bootloop? That would mean the problem has been backing up and then restoring the boot image. System as root and no recovery partition is just hard to grasp at this point. For me restoring data in a backup of stock results in twrp error 255.
Skippy12359 said:
So your saying because recovery is in the boot image that we need only to backup system and data and then a restore of same will not go into a bootloop? That would mean the problem has been backing up and then restoring the boot image. System as root and no recovery partition is just hard to grasp at this point. For me restoring data in a backup of stock results in twrp error 255.
Click to expand...
Click to collapse
I spoke too soon. This was the 1st time I'd flashed dm-verity on the install. That's why it worked. It won't work if /data is encrypted. I just made a backup with boot as well and it restored fine.
arkansawdave74 said:
I spoke too soon. This was the 1st time I'd flashed dm-verity on the install. That's why it worked. It won't work if /data is encrypted. I just made a backup with boot as well and it restored fine.
Click to expand...
Click to collapse
Which version of dm- verify are you using and what steps did you take to get crdroid to boot?
Skippy12359 said:
Which version of dm- verify are you using and what steps did you take to get crdroid to boot?
Click to expand...
Click to collapse
I'm not sure where I got it Or else I would link you. But this is the one I'm using this one. I flashed it after formatting /data and also after installing the ROM. One of those is proper, but I couldn't remember. I think it's supposed to be after you install, but before 1st boot.
https://www.mediafire.com/download/uxldj5okanllfza
arkansawdave74 said:
I'm not sure where I got it Or else I would link you. But this is the one I'm using this one. I flashed it after formatting /data and also after installing the ROM. One of those is proper, but I couldn't remember. I think it's supposed to be after you install, but before 1st boot.
https://www.mediafire.com/download/uxldj5okanllfza
Click to expand...
Click to collapse
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Skippy12359 said:
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Click to expand...
Click to collapse
Yup. I've restored it twice and made another with boot included and it booted as well. I hope it works with RR too, but I've got a helluva headache. I may stop messing with it for now.
Oh, I had wiped dalvic (actually ART), system, and data. I don't think boot was an option during wipe.
You know, I've only had one device before thar force encrypted, and back then, TWRP couldn't decrypt /data except by formatting. Now it can. That's why I didn't suspect it was an encryption issue.
I was still using a Galaxy S5 with crDroid 7.1.2 built by me until last week. It died, may it rest in peace.
Skippy12359 said:
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Click to expand...
Click to collapse
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
arkansawdave74 said:
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
Click to expand...
Click to collapse
My goal was to have twrp backup of stock pie which is really great in my opinion and also be able to flash Q gsi's like I do on my Moto g6. So far any backup restore of stock just bootloops and any gsi just hangs at boot logo or boots back to recovery.
arkansawdave74 said:
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
Click to expand...
Click to collapse
It does appear to be an encryption issue with a stock rom TWRP backup restore not booting. Formatting data in TWRP and rebooting always results in a bootloop. Until I can format data to remove encryption and get it to boot and the security setting says it's not encrypted, I don't think a backup will ever boot. Out of ideas at this point.
Skippy12359 said:
It does appear to be an encryption issue with a stock rom TWRP backup restore not booting. Formatting data in TWRP and rebooting always results in a bootloop. Until I can format data to remove encryption and get it to boot and the security setting says it's not encrypted, I don't think a backup will ever boot. Out of ideas at this point.
Click to expand...
Click to collapse
For stock, I wonder if you could boot TWRP after all those fastboot commands and flash dm-verity before booting stock. You may be able to keep stock from encrypting. I don't know for sure though.