Develop Bugs

fail installing Magisk

I'm trying to install magisk on MiA2Lite with january update but I fail.
I've tried
- Zip installation (Magisk Manager -> download .zip) but when I reboot on TWRP i don't find zip, all folders seems empty
- upgrade boot image: the upgrade semmes works well but when I restart MiA2Lite and I open Magisk Manager I alway see "Magisk is not installed" ed if I tap on INSTALL Magisk Manager propose: "download zip or upgrade boot img"..
the option "direct install (recommended)" dosn't apear to me

IO13 said:
I'm trying to install magisk on MiA2Lite with january update but I fail.
I've tried
- Zip installation (Magisk Manager -> download .zip) but when I reboot on TWRP i don't find zip, all folders seems empty
- upgrade boot image: the upgrade semmes works well but when I restart MiA2Lite and I open Magisk Manager I alway see "Magisk is not installed" ed if I tap on INSTALL Magisk Manager propose: "download zip or upgrade boot img"..
the option "direct install (recommended)" dosn't apear to me
Click to expand...
Click to collapse
If you want to install magisk from TWRP:
-Put the magisk.zip on your fastboot folder,
-Boot to TWRP and connect the phone to your PC, then use this code :
Code:
adb push ./magisk.zip /sdcard
-Now, you will be able to see magisk.zip on the Install section of your TWRP. Make sure to rename the magisk installation zip to "magisk.zip"
If you want to install without TWRP:
-Get patched_boot.img for 10.0.3.0 here: https://forum.xda-developers.com/mi...hed-boot-img-v10-30-0-january-update-t3891331
-Put the img in your fastboot folder, shutdown your phone.
-Go into fastboot mode on your phone (hold Vol- and Power)
-Connect phone to PC and write this on ADB:
Code:
fastboot boot patched_boot.img
-Let it download the img to the phone then unplug and wait for it to boot.
-Install Magisk Manager and tap Install->Direct Install
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:

marstonpear said:
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
Click to expand...
Click to collapse
I assure you that if I would have preferred to find the information myself rather than wait for some kind user to answer me. Unfortunately it is not so simple, there are many double posts with information missing (you imagine a new user who wants to try to install the GCam, there are several posts on the subject with redundant or sometimes opposite information, there are two posts on how to install Magisk without losing the OTA, they are almost identical but in one there is written that with Pie no longer works, in the other no ..). Look for an info here with the search function is anything but simple so thank you for answering me so exhaustively!

marstonpear said:
If you want to install magisk from TWRP:
-Put the magisk.zip on your fastboot folder,
-Boot to TWRP and connect the phone to your PC, then use this code :
Code:
adb push ./magisk.zip /sdcard
-Now, you will be able to see magisk.zip on the Install section of your TWRP. Make sure to rename the magisk installation zip to "magisk.zip"
If you want to install without TWRP:
-Get patched_boot.img for 10.0.3.0 here: https://forum.xda-developers.com/mi...hed-boot-img-v10-30-0-january-update-t3891331
-Put the img in your fastboot folder, shutdown your phone.
-Go into fastboot mode on your phone (hold Vol- and Power)
-Connect phone to PC and write this on ADB:
Code:
fastboot boot patched_boot.img
-Let it download the img to the phone then unplug and wait for it to boot.
-Install Magisk Manager and tap Install->Direct Install
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
Click to expand...
Click to collapse
Bro.. i'd like to ask
So the diffrence/concept is , if
- with twrp we dont need patched boot.img
- without twrp (we need patched boot img)
Are we can flash stock rom via twrp? So dont need fastboot anymore? At least fastboot for emergency case only
And last why right now is so much step in order doing mod, last time i doing mod with my samsung galaxy grand 2, the key is only how to install custom recovery (cwm or twrp) , from that recovery if we want to install custom rom or root , just download zip , flash from custom recovery, enjoy.... Simple
Why in this phone not like that, especially install GSI rom ( which still im not clearly about GSI and difference with custom rom)

bla.tiga said:
Bro.. i'd like to ask
So the diffrence/concept is , if
- with twrp we dont need patched boot.img
- without twrp (we need patched boot img)
Are we can flash stock rom via twrp? So dont need fastboot anymore? At least fastboot for emergency case only
And last why right now is so much step in order doing mod, last time i doing mod with my samsung galaxy grand 2, the key is only how to install custom recovery (cwm or twrp) , from that recovery if we want to install custom rom or root , just download zip , flash from custom recovery, enjoy.... Simple
Why in this phone not like that, especially install GSI rom ( which still im not clearly about GSI and difference with custom rom)
Click to expand...
Click to collapse
You can't flash stock ROM with TWRP, unless you use a backup of your own stock ROM, then you can recover your backup to install stock. Also you're talking about 6 yr old phone. Many things have changed since then on Android lol. GSI means Generic System Image which means that these roms should be able too boot on every device with treble support. Instead of creating a rom from scratch for every device, they just make a GSI and that can be installed on every GSI supported (project treble enabled) phone. You can still install TWRP and flash what you want. But beware you might have issues and Mi A2 Lite doesn't have any custom ROMs yet, because it is project treble enabled. You can use GSIs for now but most of them lag so I stick with stock. You can try modding the stock rom with magisk etc. :good:

marstonpear said:
You can't flash stock ROM with TWRP, unless you use a backup of your own stock ROM, then you can recover your backup to install stock. Also you're talking about 6 yr old phone. Many things have changed since then on Android lol. GSI means Generic System Image which means that these roms should be able too boot on every device with treble support. Instead of creating a rom from scratch for every device, they just make a GSI and that can be installed on every GSI supported (project treble enabled) phone. You can still install TWRP and flash what you want. But beware you might have issues and Mi A2 Lite doesn't have any custom ROMs yet, because it is project treble enabled. You can use GSIs for now but most of them lag so I stick with stock. You can try modding the stock rom with magisk etc. :good:
Click to expand...
Click to collapse
Oh i see.. thanks for the explanation... Gathering information in xda is bit confusing lol
Okay one more thing to be clear, right now im on oreo august security patch V 9.6.6.0 ODLMIFF
I want to install twrp and flash magisk (do i need downgrade to 9.6.4.0?) , if i succeed install both of that, and i want upgrade rom to pie or upper version via fastbot flash, i need to remove twrp and magisk, or just directly flash with mi flash??

[guide] OTA update when rooted ( revert to non-rooted , update—>root again)

Since you are rooted, you probably found out the OTA update won’t install.
after 3 % it crashes, and no update is installed.
So this is what I did to get the latest update:
step 1: remove root access;
- reboot and hold volume down to get into fastboot mode
- connect to pc, and load original boot.img , I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
- I connected to LMSA, to make a backup, and download the new rom.
- I went to fastboot mode again and flashed the boot by using the command “fastboot flash boot boot.img ( the “old/current” one, not the one from the downloaded new image”
“fastboot reboot”
Step 2:
so the phone booted, and I ran the update again. This time I had no issues installing it.
Step 3:
i extracted the new Boot.img from the rom downloaded by LMSA
I re patched the new boot.img with magisk, rebooted again, and and the update was complete.
this was done on the eu g8 power , for update qpe30.79.124 , but i guess this will work on all versions since the process is the same ...
for people reading this, and don’t have root / want root, just read this thread:

Confirming success with this. I downloaded the whole ZIP, extracted boot.img and used Magisk App's built-in feature to mod the boot img. Afterward, I reflashed boot partition via fastboot. Thanks, all!

Success on Sophia RETUS 80-51-5. Flashed 80-51-3 stock boot with fastboot, took update, extracted BOOT from 80-51-5, modified with Magisk and flashed the mod with fastboot. Back up and running.

I have twrp installed. Will this work?

No, I don't believe so.
3dekstron said:
I have twrp installed. Will this work?
Click to expand...
Click to collapse
As far as I know you will also have to flash the stock recovery before updating... not sure if the recovery has to match the stock rom build, like the boot.img does. You could also flash the entire latest stock rom using LMSA to update.

pjottrr said:
Since you are rooted, you probably found out the OTA update won’t install.
after 3 % it crashes, and no update is installed.
So this is what I did to get the latest update:
step 1: remove root access;
- reboot and hold volume down to get into fastboot mode
- connect to pc, and load original boot.img , I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
- I connected to LMSA, to make a backup, and download the new rom.
- I went to fastboot mode again and flashed the boot by using the command “fastboot flash boot boot.img ( the “old/current” one, not the one from the downloaded new image”
“fastboot reboot”
Click to expand...
Click to collapse
What does this mean (from above) and what results are to be expected?
I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
Click to expand...
Click to collapse
I'm guessing that a fail is expected since original boot.img is no longer installed (ie, rather the patched version is installed). Hopefully someone can elaborate

Also in the case of the Magisk systemless root method, will OTA announcements occur even though they can't be installed without first unrooting?

I wonder if there is not a few steps that could be cut off and streamlined this method, for example why isnt uninstalling magisk enough, since magisk restores the boot.img, also it backs up the original boot.img so instead of going through the whole LMSA thing it can be just copied to storage and flashed in fastboot, right?

TaZeR369 said:
I wonder if there is not a few steps that could be cut off and streamlined this method, for example why isnt uninstalling magisk enough, since magisk restores the boot.img, also it backs up the original boot.img so instead of going through the whole LMSA thing it can be just copied to storage and flashed in fastboot, right?
Click to expand...
Click to collapse
I just did that with a sofia retus phone on Android 11 for the new security update.
RPM31.Q1-54-13 to RPMS31.Q1-54-13-2.
1. Uninstall all Magisk modules and reboot
2. Uninstall Magisk and hit restore image
3. Uninstall Magisk completely and phone reboots
4. Accept OTA update (nervously)
5. Patch boot image with Magisk
6. Flash patched image with minimal adb and fastboot
7. Success!
this process does replace vanced youtube with factory youtube and youtube music, but it's easy to just replace them again in vanced manager.

Question Failed to install Magisk patched image

Hi, guys. The patched imaged failed, and the detail is as follows. I am really confused and any comments are welcomed.
device: Redmi K40
Magisk version: v22.0, v22.1, v23.0 report the same behavior
MIUI: xiaomi.eu_multi_HMK40_POCOF3_21.12.8_v12-12-fastboot
Here's what I have done (following the docs)
1. unlock bootloader, turn usb debug on.
2. flush the brand-new MIUI rom as above.
3. installmagisk version xfrom the official github apk, where x represents v22.0, v22.1 or v23.0, withinstalled: N/A, A/B: yes, Ramdisk: Yes, SAR: yes
4. copy theboot.imgto the phone and patch it in magisk. The los is available here.
5. use.\platform-tools-windows\fastboot.exe flash boot patched_img.imgand.\platform-tools-windows\fastboot.exe flash vbmeta --disable-verity --disable-verification .\images\vbmeta.img, then reboot.
6. when I enter the magisk app again, it is the same as before, i.e.,installed: n/awithinstallbutton still showingselect and patch a file, nothing changed.
I wonder if anyone met the same problem when installing magisk on redmi K40, or could you give some suggestions on how to install it? I tried many available tutorials but all ended with the above problem.

i believe you need twrp or other custom recovery installed to install magisk. you haven't mentioned twrp at all so i'm assuming you don't have it? i mean, yes, you can patch the boot.img but i think you still need twrp installed - someone will correct if i'm wrong.
boot your device into fastboot mode, plug in to pc and open adb fastboot cmd box, type 'fastboot devices' and hit enter. if a serial key shows up, you're connected.
Download lastest official twrp from here (alioth is the name or our device).
Download lastest magisk manager from here and rename the .apk file extension to .zip, for example: Magisk-v24.1.apk → Magisk-v24.1.zip
1. the simplest way is to boot to twrp using cmd 'fastboot boot twrp.img' [or whatever your twrp.img is named to] with the twrp.img in adb fastboot folder (usually on C drive root)
2. install twrp 'Preferred Installation Method: Once booted, navigate to the Advanced > Flash Current TWRP option. This will install the TWRP image you just booted permanently to the device.'
3. flash magisk zip in twrp and DESELECT 'Inject twrp after install' if you have that option (sorry to be vague but i haven't updated in a while and it may now be different.
4. boot to system, you'll find a link in apps for magisk app to finish installing magisk manager.
Hope this makes sense, it's 4.50am and i'm about to go bed!! sorry if it's not correct at all...

may be you can use "fastboot reboot fastboot" at first

flash your magisk.apk as zip in recovery (rename it to .zip and flash using recovery)

Hi, guys. @SamantaSync, @eee625, @reg66, thanks for the reply!
I followed your suggestions to use TWRP to install magisk, but I met another problem. Here is what I have done.
1. I boot from TWRP: fastboot boot twrp.img.
2. After entering into TWRP, I found that the "internal storage 0mb", thus I found another method to make it readable. In short, I first change the "data" partition to "ext2" format and then change back to "ext4". This makes the internal storage readblae (around 200gb).
3. After this step, I tried to make TWRP permanent, thus I use "advance" section's "flush current TWRP".
4. Finally, I reboot the device. But found that my device keep reboot into the recovery.
Though I could still boot externally from TWRP, in normal mode, it just boot into the main recovery forever. Is my device becoming brick in this case?

You probably had a kind of encryption (fingerprint + PIN/or Password). Removing those would allow memory to be read.
Also, Twrp has to be kkk's. Not Vasi, Not any other. Kkk's TWRP supports a12 but still doesn't decrypt, and that's why we remove lock.
You should've asked dude before doing anything that might lead to making a brand know flash again.
I think now you should flash from scratch and go one by one. TWRP will root your rom just fine.

AreuMiFan said:
Hi, guys. @SamantaSync, @eee625, @reg66, thanks for the reply!
I followed your suggestions to use TWRP to install magisk, but I met another problem. Here is what I have done.
1. I boot from TWRP: fastboot boot twrp.img.
2. After entering into TWRP, I found that the "internal storage 0mb", thus I found another method to make it readable. In short, I first change the "data" partition to "ext2" format and then change back to "ext4". This makes the internal storage readblae (around 200gb).
3. After this step, I tried to make TWRP permanent, thus I use "advance" section's "flush current TWRP".
4. Finally, I reboot the device. But found that my device keep reboot into the recovery.
Though I could still boot externally from TWRP, in normal mode, it just boot into the main recovery forever. Is my device becoming brick in this case?
Click to expand...
Click to collapse
To solve this,just format you data and reflash boot.img

Hi, @laid1995 ,@eee625, thanks for the reply. Following your guide, I made it.
I succesffully flashed magisk in, and I found the problem is that I am using android 12, and I need magisk >= v24.0.
btw, I found two weird problems and want to share with you guys. In magisk>=24, we need safetynet-fix module to pass the safetynet-check. I finished this following the official guide (1. enable Zygisk 2.enforce denylist, where the denylist contains google-play Store & google-play service 3.install safetynet-fix module). I validate this in the YASNAC app, which shows that I passed all the checks.
Howvever, I found that
1. Everytime I added Google-play service to denylist, after reboot, it escapes from the denylist. But the google-play Store will not escape.
2. I could not install google-native apps in Google-play, like Chrome, but I can still install other non-native apps.
I wonder if you guys have ever met this problem?

AreuMiFan said:
Hi, @laid1995 ,@eee625, thanks for the reply. Following your guide, I made it.
I succesffully flashed magisk in, and I found the problem is that I am using android 12, and I need magisk >= v24.0.
btw, I found two weird problems and want to share with you guys. In magisk>=24, we need safetynet-fix module to pass the safetynet-check. I finished this following the official guide (1. enable Zygisk 2.enforce denylist, where the denylist contains google-play Store & google-play service 3.install safetynet-fix module). I validate this in the YASNAC app, which shows that I passed all the checks.
Howvever, I found that
1. Everytime I added Google-play service to denylist, after reboot, it escapes from the denylist. But the google-play Store will not escape.
2. I could not install google-native apps in Google-play, like Chrome, but I can still install other non-native apps.
I wonder if you guys have ever met this problem?
Click to expand...
Click to collapse
I havent met this yet

eee625 said:
I havent met this yet
Click to expand...
Click to collapse
Hi reuMiFan.
Neither did I :/ since I don't really need for safetynet to pass. I hope you find a solution bud. You just need to dig a little more about it. I'm sure you'll work it out.

Question [RESOLVED] Bootloop after flashing Magisk after miui 14 update

Hello! As written in the title, i updated my already rooted poco f3 to the latest miui 14.0.7 (european rom) and then proceded to flash magisk. I followed everything to a T (extract boot from payload, patch in magisk, check partitions) and flashed it in fastboot. The terminal said "flashed to boot_a succesfully" so i rebooted. After unlocking the phone though, just a few seconds later it starts reooting on its own and prompts me to the miui recovery. I tried flashing the patched boot image both to boot_a and boot_b after this error, but it keeps happening.
Any help? i just don't want to lose my data.
EDIT: Thankfully i made it. The error was caused by a magisk module, so in the adb shell just run magisk --remove-modules and the error should be solved. Info from https://topjohnwu.github.io/Magisk/...debugging,and automatically reboot the device.

Would it work again if i flashed the stock boot image?

Pillow fan said:
Would it work again if i flashed the stock boot image?
Click to expand...
Click to collapse
Yes, or you can reflash the ROM.zip (without data-format of course)
OrangeFox Recovery has a Magisk Module Manager built-in and lets you disable/remove individual Modules.
Otherwise, you can simply put an empty file called "disable" or "remove", into /data/adb/modules/your_module_here/
On the next boot, Magisk will take action accordingly.
Also, maybe this is easier for you, but you can simply use a TWRP / OrangeFox Backup of the boot-partition, to patch Magisk.
Then you can rename the Magisk-patched Boot.img back into "boot.emmc.win", put it into Backup folder and replace with original Boot backup file, and restore with TWRP/OF.
Doesn't require a PC.

Question Best TWRP installation tutorial thread/video for Poco F3?

I am trying to Unlock my bootloader, Install TWRP then install Magisk for the customizations. I connected my Mi Account on my phone, and I have to wait 5 more days from the 7 days wait period. Meanwhile I was wondering If there were any simple tutorials for Installing TWRP out here, or any specific channel/video you guys would recommend for my phone. which I can watch and prepare myself, while I wait.
I checked YouTube, there are a few good tutorials there, but they each do a slightly different method, or they mention that all the Xiaomi phones will have the same method but go on to mention that "for this specific X phone you will have to do slightly differently" and that's where It gets confusing.
I don't want to end up bricking my phone in the process, that's why I was looking to ask directly in the forums so I can get more relevant suggestions, rather than just watching a YouTube follow along video which the channel owner doesn't check comments on.
Any suggestions, recommendations welcome

Suggestion before flashing the ROM you need to read the whole page of the ROM because it's the number one thing that people missed up and bricking their phone because they don't read the whole post. Also backup your data.

percharnel said:
Suggestion before flashing the ROM you need to read the whole page of the ROM because it's the number one thing that people missed up and bricking their phone because they don't read the whole post. Also backup your data.
Click to expand...
Click to collapse
I'm just tryna install Magisk as the end goal. No plans for ROM currently. But thanks for the suggestion nontheless. Something to keep in mind in case I change my mind later

My advice for you is as follows:
Let TWRP go and don't use OpenGApps.
Use the things that are working flawlessly.
Take LOS Recovery instead of mighty, but outdated TWRP,
Take MindTheGApps instead of highly customizable OpenGApps.
(Think about LOS as your custom ROM).
I used to use both together with my Mi 8. But installing LOS, the recovery and GApps on my Poco F3 was possible within round about an hour. All this went well, while I watched Netflix and cuddled a beautiful woman on her Sofa. By the way - I had to install ADB and divers on her Surface Laptop at first.

Hi,
You could check out My Beginners guide post:
Also a Very important Note, "NEVER RE-LOCK YOUR BOOLOADER" with a custom recovery or Custom Rom installed, as this will BRICK your device and you will have to pay to get it unbricked.
The Re-lock could happen when you use the MIFlash Tool and select "Clean all and Lock".

.

SDK Platform Tools (ADB & Fastboot): https://developer.android.com/tools/releases/platform-tools
Xiaomi USB Driver: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
(link source: https://developer.android.com/studio/run/oem-usb)
OrangeFox Recovery: https://orangefox.download/device/alioth
Notes:
-During BL-Unlock, your phone will auto. factory reset.
-Unlike on many AOSP-ROMs, using a Custom Recovery on MIUI will cause OTAs to not work anymore as the MIUI Update relies on MIUI Recovery. Instead you have to manually flash each MIUI-update in your Custom Recovery.
-I'm suggesting OrangeFox Recovery, because it never failed me personally, and because it's simply much more modern than TWRP.
-On MIUI, Magisk (by default) will cause you to fail Google SafetyNet, which means Banking Apps, Netflix, and many other apps won't work. You will have to spoof Attestation to "Basic" by using a Magisk Module that changes the fingerprint. And you'll have to hide Magisk from Play Services (.gms and .gms.unstable specifically) and user-apps that check for Magisk/Root.
Boot to Fastboot Mode (Power + Vol Down),
extract "recovery.img" from OrangeFox.zip,
Open Terminal inside Platform-Tools folder and do "fastboot boot <path_to_recovery.img>"
To install OrangeFox, go to its Menu and tap "Install current Recovery" (something along those lines)
To install Magisk, you can rename Magisk.apk to Magisk.zip and flash it in Custom Recovery (only TWRP or OrangeFox!, other recoveries may not be able to install anything other than the ROM ZIP file). It's the easy method of getting Magisk, however flashing Magisk.zip in Recovery isn't supported anymore by TopJohnWu.
Recommended way is to obtain the boot.img and patch it with the Magisk App. I personally do a Boot Backup with OrangeFox Recovery, patch the backup file, and restore the magisk-patched Boot file with OFox.
My break is over, so I'll have to cut here, but I think I have my socials linked in my profile. if you need more help you can message me privately on TG

cyanGalaxy said:
SDK Platform Tools (ADB & Fastboot): https://developer.android.com/tools/releases/platform-tools
Xiaomi USB Driver: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
(link source: https://developer.android.com/studio/run/oem-usb)
OrangeFox Recovery: https://orangefox.download/device/alioth
Notes:
-During BL-Unlock, your phone will auto. factory reset.
-Unlike on many AOSP-ROMs, using a Custom Recovery on MIUI will cause OTAs to not work anymore as the MIUI Update relies on MIUI Recovery. Instead you have to manually flash each MIUI-update in your Custom Recovery.
-I'm suggesting OrangeFox Recovery, because it never failed me personally, and because it's simply much more modern than TWRP.
-On MIUI, Magisk (by default) will cause you to fail Google SafetyNet, which means Banking Apps, Netflix, and many other apps won't work. You will have to spoof Attestation to "Basic" by using a Magisk Module that changes the fingerprint. And you'll have to hide Magisk from Play Services (.gms and .gms.unstable specifically) and user-apps that check for Magisk/Root.
Boot to Fastboot Mode (Power + Vol Down),
extract "recovery.img" from OrangeFox.zip,
Open Terminal inside Platform-Tools folder and do "fastboot boot <path_to_recovery.img>"
To install OrangeFox, go to its Menu and tap "Install current Recovery" (something along those lines)
To install Magisk, you can rename Magisk.apk to Magisk.zip and flash it in Custom Recovery (only TWRP or OrangeFox!, other recoveries may not be able to install anything other than the ROM ZIP file). It's the easy method of getting Magisk, however flashing Magisk.zip in Recovery isn't supported anymore by TopJohnWu.
Recommended way is to obtain the boot.img and patch it with the Magisk App. I personally do a Boot Backup with OrangeFox Recovery, patch the backup file, and restore the magisk-patched Boot file with OFox.
My break is over, so I'll have to cut here, but I think I have my socials linked in my profile. if you need more help you can message me privately on TG
Click to expand...
Click to collapse
I'm considering to switch from latest TWRP 3.7.0_9-0 to OFR R11.1_3_A12 on my old dipper. But that dosn't play a role here, because I have some general questions about it that are the same for alioth.
Just want to try it out and see, if it's really so much better than TWRP like lots of people tried to tell me in the last years...
So may I ask you some vital questions?
1. From what I understood, it should be possible to flash OFR easily through my already installed TWRP on the device, right?
2. Which decryption methods does the A12-Branch of OFR support? A12 only or A11+A12 so that it's possible to dirty flash from A11 to 12?
3. In OFR there's an inbuild (and easy to handle?) direct management of the preinstalled Apps, right? This could be avery interesting feature for me, especially with regards to the slowly dying OpenGApps-Project that was imho the best way to customize GApps over the last few years...

If you are a visual learner just watch them carefully, watch the suggestions above they work great, works perfectly on OFOX too