Related
Hey guys since i dint see any stock roms here, i decided to make one thats possible to flash from twrp, its 100% stock nothing added nothing taken from original rom, no firmaware files in rom zip.
I have the the US Asus Zenfone 4 pro , tested ONLY ON THIS DEVICE DO NOT FLASH IT ON ANY OTHER ZENFONE YOU HAVE BEEN WARN!!
How to Flash:
1.Unlock Bootloader Via Official App
2.Flash TWRP
3:Swipe to allow modifications to system VERY IMPORTANT! flash noverity.zip just incase you get stuck in a bootlooop.
4lace zip on your sdcard/internal Storage
5:Wipe Data/System
6:Flash rom zip (Ignore "unknow command error" after flashing, i need to cleanup the update script )
7.Reboot to system
I followed these step and rom flashed fine.
I might try and do some other things with this phone, be advised i haven't tinker with android in a very very long time.
ROM Download LINKS:
OREO-WW-15.0410.1803.51.zip
Change log:
1.Security patch update
2.Improve touch sensitivity
3.Fix launcher home page folder cannot be changed
4.Fix play to/MI Box porject not full screen issue
5.Fix randomly auto reboot issue
6.Fix status bar icon to show more obviously
7.Fix audio issue in 3rd party APPs
OREO-WW-15.0410.1802.34 If you flash this you will need to flash 15.0410.1803.51 right after or you wont have audio and videos will lag.
WW-14.2610.1801.51_ROM
Change Log: January Security Updates
WW-14.2610.1712.45_ROM
Thanks Dude! Now I cant root it safe, without worrying about not having a recovery
No problem!, This will also allow people that unlocked bootloader before getting the latest ota, to be on the latest software update, il keep making these as asus releases future updates for our phones.
Added Latest WW-14.2610.1801.51 update enjoy guys.
rafyvitto said:
Added Latest WW-14.2610.1801.51 update enjoy guys.
Click to expand...
Click to collapse
Thanks dude...and sorry to ask...but can you do one with the oreo update? Thank
As soon as someone posts the oreo ota zip i will, haven't gotten the update on my phone yet ;/.
ok guys i have a working flashable OREO! but videos are lagging because i havent been able to flash the firmware files need to dig deeper into this, before releasing it, give me some time guys, also twrp is unable to decrypt OREO internal data so thats another issue, but this one si out of my league shakalaca will need to update our recovery to decryot oreo data, il upload the current rom if anyone is willinf to flash it with the current issues, let me know.
Here's a screenshot of about screen.
Proof of root on oreo
Hi.Can I update my firmware if bootloader is unlocked and root is installed?If so, how?
You want to upgrade to oreo? Or just update your current firmware?
Just wondering.Are phones updated when the bootloader is unlocked?
Yes you can update phones with unlock bootloader's, if you want official updates you need the stock recovery, the twrp flashable roms i made will give you stock recovery.
Where is the stock recovery to take?
Flash any of the twrp stock roms i made and it will give you stock recovery.
Download firmware from the official website of asus, install it via twrp
and I get stock recovery with the new firmware???You don't know when to do an unofficial unlock of the bootloader?
rafyvitto said:
ok guys i have a working flashable OREO! but videos are lagging because i havent been able to flash the firmware files need to dig deeper into this, before releasing it, give me some time guys, also twrp is unable to decrypt OREO internal data so thats another issue, but this one si out of my league shakalaca will need to update our recovery to decryot oreo data, il upload the current rom if anyone is willinf to flash it with the current issues, let me know.
Click to expand...
Click to collapse
Hi. I flashed the stock rom you uploaded because I accidentally lost mine... aside from audio/video lag issues, audio from calls were also unable to hear. Will patiently wait for your stock rom with firmware files. thaaaaanks
Go into recovery and flash the official oreo zip this will flash firmware files and fix no audio/video lag issues.
rafyvitto said:
Go into recovery and flash the official oreo zip this will flash firmware files and fix no audio/video lag issues.
Click to expand...
Click to collapse
:'(
Groundz said:
:'(
Click to expand...
Click to collapse
If you flash my oreo zip with no firmware and boot it up, this will give you stock recovery, which you will need to flash the stock oreo zip , and ofcourse you will need to reflash twrp after.
Samsung Galaxy Note 5 N920A (noblelteatt)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.08-B01
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 3.2.1 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
Flashable zip:
Flash using Safestrap recovery or FlashFire.
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
Flashable zip:
Flash using Safestrap recovery or FlashFire.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again.
DOWNLOADS:
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY NOTE 5 N920A (NOBLELTEATT)
LATEST FILE: Safestrap-4.08-B01-NOBLELTEATT-SS-FF-flashable.zip
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode, DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery.
@Alexander6 for testing.
CHANGELOG:
4.08-B01 [2019-03-27]
- TWRP updated to 3.2.3.
- Fix reboot function.
- Theme clean up.
- Fix datamedia mount.
- Add hijack-backup during image flashing.
- Major code clean up
- Initial release.
BUGS:
- ROM-slots not working for now.
Hello, thanks alot for hard work, and providing the way to install TWRP in LOCKED BL and play something with it, and also with clear instructions very easy and simple way to use,.
Yes i personally tested. 100% working without any bug,
Video s00n,.
In last claps for my English too,. ???
Keep it up @afaneh92
afaneh92 said:
Samsung Galaxy Note 5 N920A
Special Thanks To
@Hashcode,
@Alexander6 for testing.
Click to expand...
Click to collapse
I found this and recommended testers try for rooting BL rev 4 devices.
Is this designed for a particular OS version? Will it work with LP or MM then?
Delgoth said:
I found this and recommended testers try for rooting BL rev 4 devices.
Is this designed for a particular OS version? Will it work with LP or MM then?
Click to expand...
Click to collapse
I think MM has no root yet!
this can work over LP (5.1.1) and combo firmware too.
Im releasing a 5.1.1 ROM that work over any BL rev for verizon variant soon. maybe you can test it when I have luck uploading it.
afaneh92 said:
I think MM has no root yet!
this can work over LP (5.1.1) and combo firmware too.
Im releasing a 5.1.1 ROM that work over any BL rev for verizon variant soon. maybe you can test it when I have luck uploading it.
Click to expand...
Click to collapse
We do have a temporal root on the first full MM build for BL rev 4. Using the greyhat root console with the dirtyc0w-able kernel, we can get root commands ran. With a some further tweaking of the code we could get it more stable albeit not permanent yet.
Please PM me please on how you propose to make that rom. Are you able to add to the combination system image to make it workable?
Delgoth said:
We do have a temporal root on the first full MM build for BL rev 4. Using the greyhat root console with the dirtyc0w-able kernel, we can get root commands ran. With a some further tweaking of the code we could get it more stable albeit not permanent yet.
Please PM me please on how you propose to make that rom. Are you able to add to the combination system image to make it workable?
Click to expand...
Click to collapse
ROM uploaded but give me some time to post the instructions with details.
flashing non combo system.img over combo BL will end with non bootable device and will check for system rev, the hack is to keep the system header and flash the ROM as custom zip not to write the system.img and to add some libs from the combo system to make it bootable.
Will link you later with all things. and with the new safestrap build.
afaneh92 said:
ROM uploaded but give me some time to post the instructions with details.
flashing non combo system.img over combo BL will end with non bootable device and will check for system rev, the hack is to keep the system header and flash the ROM as custom zip not to write the system.img and to add some libs from the combo system to make it bootable.
Will link you later with all things. and with the new safestrap build.
Click to expand...
Click to collapse
That sounds great. The combo BL I have for sw rev 3 will allow you to flash the whole Odin stock AP tar from rev 2 or rev 1 because those were LP based builds. I guess it just didn't check signatures. Because it even allowed me to flash a rev 2 sboot and technically downgrade even.
All I had to do was first flash the rev3 BL and CP I have, and then boot straight back to download and then any of 5.1 builds (AP file) would flash no problem.
I guess we dont have a real eng sboot for rev 4 yet.
Delgoth said:
That sounds great. The combo BL I have for sw rev 3 will allow you to flash the whole Odin stock AP tar from rev 2 or rev 1 because those were LP based builds. I guess it just didn't check signatures. Because it even allowed me to flash a rev 2 sboot and technically downgrade even.
All I had to do was first flash the rev3 BL and CP I have, and then boot straight back to download and then any of 5.1 builds (AP file) would flash no problem.
I guess we dont have a real eng sboot for rev 4 yet.
Click to expand...
Click to collapse
Here we go
https://forum.xda-developers.com/verizon-galaxy-note5/development/rom-noble-rom-aoj3-v1-0-t3940543
Hello , i am on version N920AUCS5ERA2 .does this work fine with this version ?
Hello!
There's a guide already on XDA that covers this matter but in a general way and for all devices. That guide was based on the general info you may find on the original installation guide by @topjohnwu. So, all credits go to him.
Anyway, since there ins't a TWRP Recovery for Mi A3 (yet) and since I believe that many of you don't know about this, Iv'e decided to share here the steps I've done in order to root Mi A3.
NOTE: Now that we already have a working TWRP available for Mi A3, to root it you can now simply follow THESE steps after unlocking the bootloader.The guide present on this thread, of course, works as well, so I'll leave it here for those of you who don't want to permanently install TWRP to your device.
1 - Unlock the bootloader (if you haven't done it already...beware that this will erase all of your user data). To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(after rebooting, boot the phone again into fastboot mode)
Code:
fastboot flashing unlock_critical
(for full unlock)
2 - Download Mi A3 stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your phone internal (or external) memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...we never know if we don't need to use it again in the future...you know, to restore the stock boot.img, aka revert to stock...)
If, for your current build, there isn't a stock boot.img released yet, you may get one yourselves. How? READ THIS.EU Build boot images:
---Android 9---For all of you currently on 10.3.7.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 10.3.8.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 10.3.9.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 10.3.11.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 10.3.12.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 10.3.14.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 10.3.15.0 (EU) build, you may download stock boot.img HERE.---Android 10---For all of you currently on 11.0.1.0 (EU) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)For all of you currently on 11.0.2.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 11.0.3.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 11.0.5.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 11.0.6.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 11.0.8.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 11.0.9.0 (EU) build, you may download stock boot.img HERE.---Android 11---
For all of you currently on 12.0.2.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 12.0.3.0 (EU) build, you may download stock boot.img HERE. (thanks to @lucoz )For all of you currently on 12.0.5.0 (EU) build, you may download stock boot.img HERE.For all of you currently on 12.0.6.0 (EU) build, you may download stock boot.img HERE.
Global Build boot images:
---Android 9---For all of you currently on 10.3.8.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)For all of you currently on 10.3.14.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)---Android 10---For all of you currently on 11.0.7.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)For all of you currently on 11.0.11.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)For all of you currently on 11.0.14.0 (Global) build, you may download stock boot.img HERE. (thanks to @Sapper Morton)For all of you currently on 11.0.15.0 (Global) build, you may download stock boot.img HERE.For all of you currently on 11.0.22.0 (Global) build, you may download stock boot.img HERE.---Android 11---For all of you currently on 12.0.3.0 (Global) build, you may download stock boot.img HERE.For all of you currently on 12.0.4.0 (Global) build, you may download stock boot.img HERE.For all of you currently on 12.0.6.0 (Global) build, you may download stock boot.img HERE.For all of you currently on 12.0.7.0 (Global) build, you may download stock boot.img HERE.For all of you currently on 12.0.8.0 (Global) build, you may download stock boot.img HERE.For all of you currently on 12.0.9.0 (Global) build, you may download stock boot.img HERE.For all of you currently on 12.0.11.0 (Global) build, you may download stock boot.img HERE.
3 - Download latest Magisk Manager from HERE and install it on your phone
4 - Open Magisk Manager App and press:
Install
Install (again)
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
5 - Copy the patched boot image from your device to your PC
Store it on the same folder where you have adb and fastboot
If you can’t find it via MTP, you can pull the file with ADB
Code:
adb pull /sdcard/Download/magisk_patched.img
6 - Uninstall Magisk Manager App from your phone (I'm not sure if this is really needed but I've done it anyway...)
7 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
Code:
adb reboot bootloader
Code:
fastboot erase boot
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot continue
(THIS IS IMPORTANT! USE CONTINUE INSTEAD OF REBOOT! You have been warned!!!)
8 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
9 - Enjoy!
All credits goes to topjohnwu and it's incredible work with Magisk.
I cannot be responsible if you turn your phone into a brick. Your phone, your choices, your responsibility!
Thanks!
Been waiting for someone to create a cannonical guide of how to root this phone.
Saw someone with magisk who had WiFi problems, WiFi works ok you?
Also one would assume it disables the OTA update feature, probably better write it.
sirzarmo said:
Saw someone with magisk who had WiFi problems, WiFi works ok you?
Click to expand...
Click to collapse
WiFi problems appears when you flash boot not from your ROM build. Use only the same boot.img to the build number of ROM.
sirzarmo said:
Also one would assume it disables the OTA update feature, probably better write it.
Click to expand...
Click to collapse
It is. But you can still update via Magisk if you don`t touch system partitions. Else - flash manualy.
Wow,
Thank's a lot!
As you said, I didn't know this way to root a device.
sirzarmo said:
Saw someone with magisk who had WiFi problems, WiFi works ok you?
Click to expand...
Click to collapse
That someone was me. But, I believe that happened because I've used boot.img from 10.3.4.0 branch on GitHub (instead of using boot.img from 10.3.5.0 branch) and, also, I've used "fastboot reboot" command instead of "fastboot continue". As soon as the 10.3.5.0 branch appeared online I've decided to test this method again and it worked, that's why I've decided to share this with all community.
sirzarmo said:
Also one would assume it disables the OTA update feature, probably better write it.
Click to expand...
Click to collapse
I don't think it will disable OTA feature. Probably, as soon as a new OTA comes out it will be installed on Slot A (because up until now there's only been one update and it was installed on slot B...so everyone should now be on firmware V10.3.5.0 running on Slot B). So, if I'm not mistaken, the "worst" thing that could happen is to lose root (since the update will be installed on Slot A and boot.img on that Slot is still the stock one).
Cheers!
Typhus_ said:
Cheers!
Click to expand...
Click to collapse
Why thank you dear, I'll root now if so.
Hello!
Well, in fact, this method breaks OTA. It downloads but it doesn't install.
My guess is we need to flash stock boot.img and then apply the OTA update and then patch the new boot.img again.
I've noticed a new boot.img on GitHub today, hopefully it will be the correct one.
Typhus_ said:
Hello!
Well, in fact, this method breaks OTA. It downloads but it doesn't install.
Click to expand...
Click to collapse
You can simply follow this guide, if you do not touch system partitions.
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md#devices-with-ab-partitions
Tried it already. It ain't possible because of 2 reasons:
1 - The supposly boot.img backup doesn't exist. Probably Magisk only does it if installed through TWRP and not by patching boot.img
2 - The OTA package fails to install. "A problem has occurred"...while trying to initiate the install.
Enviado do meu Mi A3 através do Tapatalk
When do you think twrp will be released for mi a3?
okay so I installed FDE magisk module now my phone is stuck at the bootscreen. Someone got a stock rom for me ?
You can change slot through fastboot. It will erase all user data (factory reset) but it's better than the phone not booting.
The other possible solution, I've sent you a PM (because external link).
fastboot --set-active=a (or b if you're now on a)
Enviado do meu Mi A3 através do Tapatalk
An offcial stock rom wouldve fixed my problem in no time. I changed the partition and got to a menu where I could chosse to factory reset but its been sitting on formatting data for like half hour...
drozo8o8 said:
An offcial stock rom wouldve fixed my problem in no time. I changed the partition and got to a menu where I could chosse to factory reset but its been sitting on formatting data for like half hour...
Click to expand...
Click to collapse
It should be quite fast...guess you're out of luck for the time being my friend.
By the way, you've used fastboot reboot or fastboot continue after changing slot?
It should be fastboot reboot
Enviado do meu Mi A3 através do Tapatalk
all i need is a proper flash all.bat since oyu gave me the OTA update link with a payload.bin which I extracted with payload_dumper
Typhus_ said:
Tried it already. It ain't possible because of 2 reasons:
1 - The supposly boot.img backup doesn't exist. Probably Magisk only does it if installed through TWRP and not by patching boot.img
Click to expand...
Click to collapse
Manualy patch boot.img in MM and you'll get backup.
This method is useful in Mi CC 9e. Thx
hello, install v10.3.5.0 over v10.3.7.0, now I don't have wifi and the sound does not work, instructions to fix it please ?, I am using the google translator to write here, thanks
You'll have to change slot and boot on that slot. You'll lose all your user data but the phone will boot ok and receive latest OTA. Either that or you have to wait for someone to dump you a stock 10.3.7.0 boot.img in order to fix those issues. On GitHub there isn't a boot.img for latest build yet.
Enviado do meu Mi A3 através do Tapatalk
Typhus_ said:
You'll have to change slot and boot on that slot. You'll lose all your user data but the phone will boot ok and receive latest OTA. Either that or you have to wait for someone to dump you a stock 10.3.7.0 boot.img in order to fix those issues. On GitHub there isn't a boot.img for latest build yet.
Enviado do meu Mi A3 através do Tapatalk
Click to expand...
Click to collapse
Fixed, THANKS YOU very much
Hello Everyone
I have a Xa1 Ultra phone (G3223)
After 3 full days of searching how can i root my phone i have come to the conclusión that is not posible because of these failed attemps :
1.- My firmware stock versión (working property) its 48.1.A.2.109 i couldnt find any custom kernel nor recovery that Works with this firmware and because of that i cant flash it, so i cant root it.
2.- I could not find and older versión of firmware that had a custom boot.img or recovery.img so i could not downgrade my phone to root it.
3.-There's only 1 post i found on this forum that had a working custom kernel and recovery to be able to root a xa1 ultra Xperia, but his stock firmware versión was 48.1.A.2.50 so as it does not matched mine any attemp to flash it got me a bootloop
So in resume is there anyway i could rot my xa1 ultra phone or all of my assumptions on my researchs are correct?
my stock firmware is G3223_48.1.A.2.109 is there any way i can root it?
Thanks in advance for any information about the subject
The furthest I got is to the conclusion that we need to downgrade to firmware G3223_48.1.A.2.101, there's a working magisk install for that.
I can't get the firmware anywhere and this forum is basically a cemetery.
Mighty_Rearranger said:
The furthest I got is to the conclusion that we need to downgrade to firmware G3223_48.1.A.2.101, there's a working magisk install for that.
I can't get the firmware anywhere and this forum is basically a cemetery.
Click to expand...
Click to collapse
Haven't tested but I found this >> G3223_48.1.A.2.101 https://drive.google.com/file/d/1-oCN7am9nL5TiDQs5uUdLGtW2zEoSVpq/view
It was listed midway through this website >>> https://www.martview-forum.com/thre...-version-firmware-ftf-lock-remove-file.23366/
The .101 downgrade went fine with flashtool, but the TWRP package I found on the janjan thread just boot loops. In fact, anything that I try ends in bootlooping, even fastboot booting an extracted kernel without modification (extracted with either AIK or flashtool).
I think this phone will be impossible to root unless we find the original 48.1.A.2.50 software.
Mighty_Rearranger said:
The .101 downgrade went fine with flashtool, but the TWRP package I found on the janjan thread just boot loops. In fact, anything that I try ends in bootlooping, even fastboot booting an extracted kernel without modification (extracted with either AIK or flashtool).
I think this phone will be impossible to root unless we find the original 48.1.A.2.50 software.
Click to expand...
Click to collapse
After flashing TWRP did you immediately factory reset? [Flash TWRP, reboot into TWRP, Wipe]. With other devices I've had issues occur if I did not remember to.
Soooo does anyone have a damn clue how to restore this piece of crap of phone to stock?
Without FHLoader error or Sahara error?
Currently running LinageOS (Android 13) with Linage Recovery.
Thinking about throwing this piece of garbage out of the window.
Best regards, slyn.
Returning from custom to stock ROM always involves a risk of bricking the phone. Generally I say "if you want a custom ROM, forget about stock after that". But normally a RUI4 .ofp flash with OppoRealme-OFP-Flash should work. I say "should". But there's not RUI4 .ofp file for RMX3363 as far as I know.
Perhaps you can extract .img files from F06 OTA payload.bin (for your region) and flash them with fastbootd (do a backup with QFILhelper before) because LOS 20 A13 is based on F06 firmware. After that and before rebooting, flash the last LOS recovery, reboot in recovery and perform a factory reset. Finally, reboot the system.
This has worked for me in the past to return from LOS 19 to C13 stock (.img files extracted from .ofp, not OTA update). But I have never tested from LOS 20 to stock F06 with .img extracted from OTA update.
The difference is that you don't have a super.img file in the OTA, but you have the my_xxxxxxxx.img files so maybe it can work, idk.
Best regards, eno.