Develop Bugs

Some ROMs are'nt flashing

Okay, lemme get this clear that I'm not a pro in all this stuff. Infact, I'm a total idiot.
I have tried to flash a lot of ROMs on my Moto G5 (cedric) but only 3 of them have worked, namely:
1) Pixel Expirience 7.1.2
2) Ressurection Remix 7.1.2
3) Viper OS 7.1.2
I don't know whats the problem and whether it is with my phone or the ROMs. Also, even after i used these ROMs, the apps which need root access weren't working and yes i did select the Root Access setting to ADB only(cause thats was the only option other than Off). Plz help me guys.....

Astitva_ said:
Okay, lemme get this clear that I'm not a pro in all this stuff. Infact, I'm a total idiot.
I have tried to flash a lot of ROMs on my Moto G5 (cedric) but only 3 of them have worked, namely:
1) Pixel Expirience 7.1.2
2) Ressurection Remix 7.1.2
3) Viper OS 7.1.2
I don't know whats the problem and whether it is with my phone or the ROMs. Also, even after i used these ROMs, the apps which need root access weren't working and yes i did select the Root Access setting to ADB only(cause thats was the only option other than Off). Plz help me guys.....
Click to expand...
Click to collapse
First you need to say how you have done the flashing of roms and which rom didn't flash, or what error you got while installing the rom. And second is you need to install magisk manager to gain root access with twrp, by enabling the root access in developer option won't give you root access you need to install it via twrp.

riyan65 said:
First you need to say how you have done the flashing of roms and which rom didn't flash, or what error you got while installing the rom. And second is you need to install magisk manager to gain root access with twrp, by enabling the root access in developer option won't give you root access you need to install it via twrp.
Click to expand...
Click to collapse
I tried flashing them through TWRP. They all were based on Oreo 8.1. I tried Lineage, Invicta, Viper, RR and pixel expirience. As for the error, i don't really know what error it was but Lineage and RR were stuck on the boot loader and the rest just didnt flash.....

Astitva_ said:
I tried flashing them through TWRP. They all were based on Oreo 8.1. I tried Lineage, Invicta, Viper, RR and pixel expirience. As for the error, i don't really know what error it was but Lineage and RR were stuck on the boot loader and the rest just didnt flash.....
Click to expand...
Click to collapse
Chance are you are using the wrong twrp
64bit roms require you to use the 64bit twrp
See the first post of the lineageos thread for the 64bit twrp
Or you can test out the 64bit twrp that uses my encryption edits
https://forum.xda-developers.com/g5/help/help-testing-build-twrp-arm64-t3874472
If you want to root flash the latest version of Magisk and then install the magisk manager app manually if it's not installed

TheFixItMan said:
Chance are you are using the wrong twrp
64bit roms require you to use the 64bit twrp
See the first post of the lineageos thread for the 64bit twrp
Or you can test out the 64bit twrp that uses my encryption edits
https://forum.xda-developers.com/g5/help/help-testing-build-twrp-arm64-t3874472
If you want to root flash the latest version of Magisk and then install the magisk manager app manually if it's not installed
Click to expand...
Click to collapse
I'm sorry but i didn't get what you said. I'm really sorry but I'm really a noob. I would like it if you helped me out a bit....

Astitva_ said:
I'm sorry but i didn't get what you said. I'm really sorry but I'm really a noob. I would like it if you helped me out a bit....
Click to expand...
Click to collapse
All custom oero roms for this device are 64 bit
You need to flash them with a twrp that has been compiled for 64bit twrp use
My official twrp is for 32bit roms only and will not flash 64bit roms - you will get error 7 or I think error 256 or something like that
Flash the 64bit twrp if you want to flash 64bit custom roms - process is the same as if flashing the official twrp via fastboot but you obviously use the 64bit twrp image instead
As mentioned link to 64bit twrp is on the lineageos 15.1 thread first page or try the version in the link I posted in previous post

TheFixItMan said:
All custom oero roms for this device are 64 bit
You need to flash them with a twrp that has been compiled for 64bit twrp use
My official twrp is for 32bit roms only and will not flash 64bit roms - you will get error 7 or I think error 256 or something like that
Flash the 64bit twrp if you want to flash 64bit custom roms - process is the same as if flashing the official twrp via fastboot but you obviously use the 64bit twrp image instead
As mentioned link to 64bit twrp is on the lineageos 15.1 thread first page or try the version in the link I posted in previous post
Click to expand...
Click to collapse
So, I can directly flash the new twrp like i flash the roms right?? Also, what can i do for project treble in my phone...i mean, i cant find redwolf for moto g5(cedric)

Astitva_ said:
So, I can directly flash the new twrp like i flash the roms right?? Also, what can i do for project treble in my phone...i mean, i cant find redwolf for moto g5(cedric)
Click to expand...
Click to collapse
You flash twrp via fastboot commands
fastboot flash recovery recovery.img
Although it is technically possible to flash twrp via twrp if you select image flash & select recovery as the image you are flashing but I'd stick with the fastboot method
I don't own this device anymore so no idea about files that are no longer available

TheFixItMan said:
You flash twrp via fastboot commands
fastboot flash recovery recovery.img
Although it is technically possible to flash twrp via twrp if you select image flash & select recovery as the image you are flashing but I'd stick with the fastboot method
I don't own this device anymore so no idea about files that are no longer available
Click to expand...
Click to collapse
Okay, so i flashed the twrp...but still therom isnt flashing....should i upload the rom so that you can see it?

basically;
if a rom has [64bit] in the title, then it's 64 bit, if it is then you need a 64bit recovery which you can easily find on the forum. you dont even need to know what that means.

Astitva_ said:
Okay, so i flashed the twrp...but still therom isnt flashing....should i upload the rom so that you can see it?
Click to expand...
Click to collapse
Just link to the rom on xda and give the twrp error
The rom either isn't for this device eg you are trying to flash a moto g5 plus or s rom or you are using the wrong twrp or you haven't formatted system data cache before flashing the rom

Pixel 3a XL soft #BRICK - please help

On my way to installing LineageOS I tried to downgrade Android version 11 -> 10. Unfortunately I used the WRONG INCOMPATIBLE firmware files from google's website (I think for 3 XL), that's why I have a brick now. ''Device is corrupt and no bootup possible.''
Access to Fastboot and STOCK Recovery Mode is possible.
Bootloader is Locked Now (it *was* unlocked before for flashing the firmware)
ADB is not working (since I'm getting stuck on ''google'' symbol when booting up I can't go to Developer Settings)
Factory Preset from Recovery Mode fails: ''can't send spi messages.'' Same Brick occurs.
With No Access to ADB (is it possible to set up from fastboot mode without enabling it in den Developer Options?) I can't try stuff.
And with the bootloader locked no way to flash a new Rom right?
I have NO IDEA what to do next, any IDEAS??
Thank you!!
#brick

Since you can get to recovery you should download the latest ota and sideload it from recovery.

https://developers.google.com/android/images
you should flash the stock image from recovery. Basically unzip it all and just run "flash-all.bat"

41rw4lk said:
Since you can get to recovery you should download the latest ota and sideload it from recovery.
Click to expand...
Click to collapse
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?

dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse
You need the BL unlocked to flash unsigned/unofficial images, so make sure yours is unlocked. That being said, I'm not sure how solid twrp is for our device, I've never tried it. Twrp was/is a little iffy for android 10 never mind 11. Most around here just use fastboot to do what needs to be done. Most of it is pretty quick and painless, and twrp is not really necessary.

dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.

teemothay said:
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.
Click to expand...
Click to collapse
Unlike most of the LineageOS Tutorials out there is used the Custom Recovery from Lineage to install LIneageOS! It was super easy, a few ADB commands and here it is. No Root, no TWRP whatsoever.
Follow wiki lineageos devices website instructions. Here you may also find the recovery data.
Thx guys/girls!

dadu1257 said:
Unlike most of the LineageOS Tutorials out there is used the Custom Recovery from Lineage to install LIneageOS! It was super easy, a few ADB commands and here it is. No Root, no TWRP whatsoever.
Follow wiki lineageos devices website instructions. Here you may also find the recovery data.
Thx guys/girls!
Click to expand...
Click to collapse
Cool. No more soft brick for you :good: Congrats on sorting things out. :highfive:

BUT I still cannot install TWRP Recovery on LineageOS 17. I am getting the same problem as quoted below.
I want to perform Nandroid Backups, any other way to that if TWRP doesn't want me? Maybe with a Magisk Root and some app from F Droid?
?
thanks
dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse

dadu1257 said:
BUT I still cannot install TWRP Recovery on LineageOS 17. I am getting the same problem as quoted below.
I want to perform Nandroid Backups, any other way to that if TWRP doesn't want me? Maybe with a Magisk Root and some app from F Droid?
?
thanks
Click to expand...
Click to collapse
Twrp doesn't work very well on android 10 and above, there is a twrp install guide around here, but not much has come from it. When was the last time anyone actually made and used a nandroid backup? Not that backups aren't important, but that's a little antiquated. Besides, most are really trying to backup data, which is a shared partition on A/B devices. Generally, restoring data on A/B devices causes more problems than anything. Most data backups can be done with an app and/or making a backup of your internal storage. As for more sensitive things like your persist partition and whatnot, you can always use the 'dd' command to back those partitions up.
I should clarify, restoring nand backups of data causes more problems on A/B devices, apps that restore data and settings tend to handle it better.

Now having a different problem
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
When I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed.
I am stuck in Fastboot now.
How can I get out of that?
I used the boot.img from the google firmware android 10 I built Lineage on. Should I use a boot.img from LineageOS .zip? Is there anything like this?
What is dm-verity?
Can I get to my previous unrooted device?
I have a Pixel 3aXL with LineageOS 17
''bootslot: b
enter reason: error boot prepare''

dadu1257 said:
Now having a different problem
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
When I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed.
I am stuck in Fastboot now.
How can I get out of that?
I used the boot.img from the google firmware android 10 I built Lineage on. Should I use a boot.img from LineageOS .zip? Is there anything like this?
What is dm-verity?
Can I get to my previous unrooted device?
I have a Pixel 3aXL with LineageOS 17
''bootslot: b
enter reason: error boot prepare''
Click to expand...
Click to collapse
Reflash the boot.img from Los17 to get back to proper boot up, then patch Los17 boot.img and flash that to have root.

41rw4lk said:
Reflash the boot.img from Los17 to get back to proper boot up, then patch Los17 boot.img and flash that to have root.
Click to expand...
Click to collapse
Where is the boot.img from Lineage? There is no such file in the Lineage folder I downloaded.

dadu1257 said:
Where is the boot.img from Lineage? There is no such file in the Lineage folder I downloaded.
Click to expand...
Click to collapse
A lot of devs wil upload the boot.img separately when they upload the rom, so wherever you downloaded Los from check there. If you just have a payload.bin file in your zip, you can always dump it and grab the boot.img there. You could always just reflash Los period to get boot back, then us 'dd' command to backup your own boot.img.

custom recovery for lineageos 17 based on android 10?
teemothay said:
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.
Click to expand...
Click to collapse
thanks!
I got Lineage 17 w/ Magisk root running now and want to perform a full NANDroid Backup.
After some research it seems crucial to have a custom recovery like TWRP for that. There is the online nandroid thing - but I would need CWM or anything like this to restore?!
So my question is
a) is there another custom recovery (compatible with Pixel 3a XL w/ lineage 17 based on android 10) I can install and perform Nandroid backup with?
b) any other solution to perform this backup and restore? I heard there are cmd commands for that as well , but I'm a noobie not so sure to do that.
of course there are several apps out there to backup data.. but I don't trust ''any'' app to get root permission. In F Droid I couldn't find what I was looking for.
thank you for help!

TWRP with android 10!

Has anyone else figured out how to get TWRP 3.5.2 on the Pixel 3 XL along with android 10 latest build?
I have successfully done it and I'm going to try the same method for android 11 as well.
If not I am willing to write up an install guide and share the TWRP Recovery for it as well.
i couldn't find any info here other then loads of people saying it does not work yet.

I'd like a guide, I'm trying to do exactly that by running through various guides and keep hitting walls that force me to back to reflashing the stock rom to try again.

KaosKreationz said:
Has anyone else figured out how to get TWRP 3.5.2 on the Pixel 3 XL along with android 10 latest build?
I have successfully done it and I'm going to try the same method for android 11 as well.
If not I am willing to write up an install guide and share the TWRP Recovery for it as well.
i couldn't find any info here other then loads of people saying it does not work yet.
Click to expand...
Click to collapse
sorry, not sure why the quote split to a different reply.
Anyway... what I'm trying to do:
Pixel 3 XL - Stock ROM of Android 10 (latest) Aug 2020
--can fastboot to TWRP
--can seemingly install ElementalX-P3-2.17 kernel (which based on all I've read is required for LZMA & TWRP)
--can install Magisk v23
--Attempting to install TWRP 3.5.2-10-Crosshatch seems to fail with various errors or bootloops wether using "TWRP install zip" or TWRP image.
...about the only thing I haven't tried yet is installing TWRP image to the boot partition, but feel that would cause a brick.

teknomedic said:
sorry, not sure why the quote split to a different reply.
Anyway... what I'm trying to do:
Pixel 3 XL - Stock ROM of Android 10 (latest) Aug 2020
--can fastboot to TWRP
--can seemingly install ElementalX-P3-2.17 kernel (which based on all I've read is required for LZMA & TWRP)
--can install Magisk v23
--Attempting to install TWRP 3.5.2-10-Crosshatch seems to fail with various errors or bootloops wether using "TWRP install zip" or TWRP image.
...about the only thing I haven't tried yet is installing TWRP image to the boot partition, but feel that would cause a brick.
Click to expand...
Click to collapse
I used kirsekura if I’m spelling it right the 1.55 kernel. It seemed to allow terp in for recovery.

OnePlus 7T India, 11.0.9.1, booting only to recovery / fastboot after incorrect Magisk update

I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk Canary version. There was an Update to Magisk which I accidentally installed with OTA option instead of full. Now my phone is not booting. It goes into original recovery mode or fastboot only. How can I recover from this? I tried to flash the magisk patched image file and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!

Problem solved but don't know how. I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.

jesrani said:
Problem solved but don't know how. I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.
Click to expand...
Click to collapse
Most likely changed slot accidentally when it crashed and then corrected on multiple interventions

HueyT said:
Most likely changed slot accidentally when it crashed and then corrected on multiple interventions
Click to expand...
Click to collapse
Hi. I am again having same problem. I updated Magisk Manager and Magisk and some other apps and phone was not booting. After many tries it again booted but all the modules in Magisk were off. So I switched them on and rebooted the phone and now it is just not booting. I tried to use Tool All In One to flash a TWRP but now there is no recovery. The phone is either not booting (stuck on Circle dot rotating) or just going into fastboot, does not go into recovery. I was on OOS11. I tried flashing original recovery through the tool but it fails. Any way out of this mess??

jesrani said:
Hi. I am again having same problem. I updated Magisk Manager and Magisk and some other apps and phone was not booting. After many tries it again booted but all the modules in Magisk were off. So I switched them on and rebooted the phone and now it is just not booting. I tried to use Tool All In One to flash a TWRP but now there is no recovery. The phone is either not booting (stuck on Circle dot rotating) or just going into fastboot, does not go into recovery. I was on OOS11. I tried flashing original recovery through the tool but it fails. Any way out of this mess??
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
This will wipe your data. Otherwise, you can try manually fastboot flash each individual files of oos11 rom:
⭐[ROM][STOCK] 11.0.9.1-GLOBAL-OnePlus7TOxygen_14.O.35_GLO_0350_2206171459-FASTBOOT
Created my own FASTBOOT Rom can anybody test this out, to see if it works please? Used to "Restore the Firmware" on your phone or when bricked you cannot downgrade or upgrade with FASTBOOT Roms, you must be on the same (Firmware Update Global...
forum.xda-developers.com

HueyT said:
This will wipe your data. Otherwise, you can try manually fastboot flash each individual files of oos11 rom:
Click to expand...
Click to collapse
Thanks. I managed to boot the phone but having root problems. After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.
I am on OOS11.09.1

jesrani said:
Thanks. I managed to boot the phone but having root problems. After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.
I am on OOS11.09.1
Click to expand...
Click to collapse
[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc Note: DISABLE...
forum.xda-developers.com

HueyT said:
[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc Note: DISABLE...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi. I already used these boot images but I was still having a problem. I had flashed the stock image to both partitions and then the Magisk patched image also but either I was not rooted or Magisk App not working. Finally got things to work by installing TWRP to partition a I believe. I changed active partition to a and then flashed the twrp recovery. Again changed active to b and booted and had root. I had to install Magisk Canary 25210 version only as other versions did not install. After checking on net it seems this version is faulty. So I installed Magisk Delta, then installed Magisk using Direct Install option, rebooted, checked regular Magisk Manager and showed the same Magisk version. Removed all modules from old Magisk Manager and unstalled the app. Setup Magisk Delta modules, hide, SuList as well as apps like LSPosed, HMA etc and now everything is working again.
I still am not very sure where the recovery is installed, on partition a or b? And if a difference recovery is installed on each partition what happens? I am pretty sure I had not installed TWRP on partition b. I am also assuming that once I set a partition as active and flash a recovery in fastboot that recovery is flashed to that partition, is this correct? Things are working but I don't know if the phone will go to recovery mode from system, I have not tried that. So I am not very clear yet but still got things to work.

jesrani said:
Hi. I already used these boot images but I was still having a problem. I had flashed the stock image to both partitions and then the Magisk patched image also but either I was not rooted or Magisk App not working. Finally got things to work by installing TWRP to partition a I believe. I changed active partition to a and then flashed the twrp recovery. Again changed active to b and booted and had root. I had to install Magisk Canary 25210 version only as other versions did not install. After checking on net it seems this version is faulty. So I installed Magisk Delta, then installed Magisk using Direct Install option, rebooted, checked regular Magisk Manager and showed the same Magisk version. Removed all modules from old Magisk Manager and unstalled the app. Setup Magisk Delta modules, hide, SuList as well as apps like LSPosed, HMA etc and now everything is working again.
I still am not very sure where the recovery is installed, on partition a or b? And if a difference recovery is installed on each partition what happens? I am pretty sure I had not installed TWRP on partition b. I am also assuming that once I set a partition as active and flash a recovery in fastboot that recovery is flashed to that partition, is this correct? Things are working but I don't know if the phone will go to recovery mode from system, I have not tried that. So I am not very clear yet but still got things to work
Click to expand...
Click to collapse

Only data partition is shared. All else have both A and B parts

Question TWRP flashing method

Hi all,
I have recently shifted from Samsung A52S to Onpelus 9 PRO.
I'm now a bit confused about flashing method....
I mean :
on Samsung devices, you have to use ODIN ( that is a Fastboot replacement tool ) in order to flash the TWRP and then, on TWRP, you can freely flash any new custom ROM or any other img files, by simply press "INSTALL" button instad of ADB sideload commands.
If I well understood, in order to flash this custom ROM, I have to do that through Fastboot commands before and through TWRP ADB sideload commands after......
My question is : may I flash boot.img / vendor_boot.img / dtbo.img and ROM zip directly through TWRP "INSTALL" button instead ???
If not, can someone kindly explain which is the reason why ?
Sorry for this noob question but I'm doing my first step into Oneplus and I don't want to do a mess.....
Many thanks for the help !

I personally been wanting to know why we no longer can simply flash custom roms via TWRP like we use to. I do believe its got to do with the way the A/B partition works however that does not really answers why we can't just flash via TWRP. Unfortunately, I have not been able to find the answer so I am interested too on why we can't simply flash custom roms in TWRP and have to resort in sideloading or via fastboot. I would think flashing via a zip in TWRP will have less user errors compare to using a command line to do your flashing.
Saying that, I have been flashing via fastboot since I got this phone and even though its a longer process, it only takes a few more minutes.

twrp is not even fully adapted for android 12 or 13 (but who needs twrp anymore?)
I prefer to flash via fastbootd
(is less work for me)

best way is the magisk install

ChrisFeiveel84 said:
twrp is not even fully adapted for android 12 or 13 (but who needs twrp anymore?)
Click to expand...
Click to collapse
twrp is still the only way to backup the whole rom
it exist a non official version for 12/13

TWRP is the best tool to recover files when the OS does not boot. Since there is no ROM or kernel out there that recommend or uses TWRP for flashing. There is little reason to use TWRP unless is for file recovery. This is in respective to OP 9.