Database Info

Can't install TWRP in Android 9

I was running stock OOS with Android 8.1 with the normal TWRP and Magisk working. When the OOS 9 got out, I installed the full OTA through TWRP (dirty flash) and everything went perfectly, with no problems whatsoever, but I lost TWRP and Magisk, of course.
Now in Android 9 I can't seem to reinstall TWRP (I'm trying with the latest bluespark): I can boot TWRP from fastboot and install Magisk, everything is fine, Magisk works great. However, when I try to install the TWRP zip (through the fastboot loaded TWRP), the phone freezes at the bootloader warning and doesn't boot (and I have to reinstall the full OTA zip to get the phone working again). Or, some other times, it reboots always to the recovery and never to the OS. Any ideas on how to solve this? Thanks in advance.

What version of bluespark are you using ?? v2

Glsoto said:
What version of bluespark are you using ?? v2
Click to expand...
Click to collapse
9.85v2

first fastboot boot twrp.img, the install twrp.zip , reboot recovery and then magisk..

I also tried to fastboot boot blu_spark twrp V2 IMG.... This ended in a black screen. I used the latest official twrp without a problem on pie.

Glsoto said:
first fastboot boot twrp.img, the install twrp.zip , reboot recovery and then magisk..
Click to expand...
Click to collapse
Thanks! Did it in that exact order and now everything works. I was forgetting to reboot the recovery before installing Magisk.

don't flash magisk on the temporary TWRP

Hexyl said:
I also tried to fastboot boot blu_spark twrp V2 IMG.... This ended in a black screen. I used the latest official twrp without a problem on pie.
Click to expand...
Click to collapse
Cuz of kernel panic. When you boot into twrp after fastboot command - unplag your cable from pc when the command is done, then disable mtp, connect to pc and re-enable mtp.
Dont forget to click thanks
And yeah, use blu spark's TWRP, not official one

Came here from google.
Glsoto said:
first fastboot boot twrp.img, the install twrp.zip , reboot recovery and then magisk..
Click to expand...
Click to collapse
This procedure didn't work for me, for some reason "fastboot boot twrp.img" was leading to black screen.
What worked for me was
1) Boot to fastboot
2) fastboot flash twrpXXX.img
3) Without rebooting, select recovery from fastboot's bootloader menu
4) If you are able to boot in twrp this time, then flash blu spark twrp.
5) Reboot
6) Try to reboot in recovery as usual
If all worked well, you should see twrp recovery.
Cheers.

Alekcander said:
Came here from google.
This procedure didn't work for me, for some reason "fastboot boot twrp.img" was leading to black screen.
What worked for me was
1) Boot to fastboot
2) fastboot flash twrpXXX.img
3) Without rebooting, select recovery from fastboot's bootloader menu
4) If you are able to boot in twrp this time, then flash blu spark twrp.
5) Reboot
6) Try to reboot in recovery as usual
If all worked well, you should see twrp recovery.
Cheers.
Click to expand...
Click to collapse
Hi
I have same problem ... after installing twrp i have black scream. twrp doesnt boot
I trying to use this method but cmd give me ]
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I have restored phone with msn download
OnePlus is again unlocked
I have this problem sins i tried to install magisk and after reboot my op doesn't boot to OS with crash error
any ideas ?

jasiorr said:
Hi
I have same problem ... after installing twrp i have black scream. twrp doesnt boot
I trying to use this method but cmd give me ]
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I have restored phone with msn download
OnePlus is again unlocked
I have this problem sins i tried to install magisk and after reboot my op doesn't boot to OS with crash error
any ideas ?
Click to expand...
Click to collapse
You need to Fastboot boot twrp. Img

jasiorr said:
Hi
I have same problem ... after installing twrp i have black scream. twrp doesnt boot
I trying to use this method but cmd give me ]
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I have restored phone with msn download
OnePlus is again unlocked
I have this problem sins i tried to install magisk and after reboot my op doesn't boot to OS with crash error
any ideas ?
Click to expand...
Click to collapse
yldlj said:
You need to Fastboot boot twrp. Img
Click to expand...
Click to collapse
Alekcander said:
Came here from google.
This procedure didn't work for me, for some reason "fastboot boot twrp.img" was leading to black screen.
What worked for me was
1) Boot to fastboot
2) fastboot flash twrpXXX.img
3) Without rebooting, select recovery from fastboot's bootloader menu
4) If you are able to boot in twrp this time, then flash blu spark twrp.
5) Reboot
6) Try to reboot in recovery as usual
If all worked well, you should see twrp recovery.
Cheers.
Click to expand...
Click to collapse
I have the same problem as Alekcander
When I try to use command ,, fastboot boot twrp-xxx.img nothing happens. I mean mobile restart as always but there is only black screen and notification diode shine white ...
Also Alekcander method doesn't work:
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I tried official twrp and is the same , I tried to disconnect from usb when mobile is restarting also nothing ...
so again ... I have restored phone with msn download -> unlock bootloader...
i have this issue sins i tried to install magisk and after reboot my OP6 doesn't boot to OS and give crash error
any other ideas ?

Solved I have to update system to more recently version. Why twrp doesn't work with oxygen is 5.1.5 ?

I cant get TWRP to "stick" on my new pixel - following lineage directions

Got my pixel from swappa the other day. So far I:
1. Unlocked the bootloader
2. temporarily booted into TWRP 3.3.0-0 (3.3.1-0 wouldnt let me format for some reason)
3. Installed the most current microG lineage build. (and then also flashed magisk 19.3 immediately after)
It boots into lineage, but when I boot into recovery, it gives me the lineage recovery. Since when does lineage wipe out twrp?
I tried sideloading over adb and also right through the temporary twrp, but it doesnt make a difference. Also - in lineage, I see no sign of magisk - which is normally there after installing a rom and then magisk.
I also tried the twrp-pixel installer.zip, which also did NOTHING.
Am I missing something? This is my first phone with the weird dual partitions - is that why its so weird? Ive never had this problem before.
EDIT: Also when trying to flash twrp via fastboot it gives me
"(bootloader) Flashing active slot "_a"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 1.016s"

Hi mate, here's a link regarding the lineage recovery thing. It may explain some of what you have occurring.
https://lineageos.org/Changelog-19/
I had twrp on my pixel a while back and it was sticking so not sure what that's all about. If you have booted twrp.img, flashed ROM, flashed twrp zip and rebooted it should be on both slots. You may need to activate root in Dev options to get root up and running, been a while since used it so that might not be accurate as currently on Q.

after flashing a rom you need to flash the twrp-pixel installer.zip right after. Then reboot into recovery (dont need to fastboot since the zip installs twrp to the boot.img ramdisk) to switch slots (switches automatically). Back in recovery you can install magisk.

Devices with A/B partitions do not have a recovery partition. What we think of as recovery is actually part of the boot.img file. When you update the OS, you update the boot.img. The TWRP installer .zip finds and unpacks the boot.img, then modifies it to make the device load TWRP instead of stock recovery. By default, the TWRP installer installs to both A & B partitions. If you screw something up (like flashing the wrong version of TWRP, for example) and put yourself into a bootloop, you can often recover by simply flashing the original boot.img file with fastboot flash boot boot.img .
Here's an article which was written by XDA to help explain the differences in how A/B phones work, and the ramifications for us flashers:
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/

Unable to flash TWRP. Lost Recovery, OS and only have unlocked bootloader.

Hi,
I was on Oxygen OS 10.0.0. Rooted with twrp-3.3.1-4-enchilada and magisk 20.1. (I had used this guide to do it. https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213) Today I downloaded the zip for 10.0.1 from the Oxygen Updater app and tried to flash it like I have done for OOS 9 in the past as usual. I went to recovery (I did not backup), I just wiped my data (not internal storage), cache and system. After that I tried to install the new zip but I got an error. It just said error unable to install. Didn't mention why. I tried flashing the older OOS 10 zip and got the same error.
So I thought I will try flashing on the other slot. I was on slot B. I switched to slot A and got the same error.
So I thought I will try to sideload. When I tried that I got the same error. So I thought I will try to reflash the twrp img itself. I went to fastboot mode and tried runnning this command
fastboot boot twrp-3.3.1-14-enchilada-Q-mauronofrio.img
It showed me this error
Sending 'boot.img' (65536 KB) OKAY [ 1.609s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Now I don't have any recovery at all. I have just the unlocked bootloader and no OS nor recovery. What can I do to flash TWRP again and install either OOS 10.0.1 zip or 10.0.0 zip? Any help will be great.
Thanks

Arnavzz said:
Hi,
I was on Oxygen OS 10.0.0. Rooted with twrp-3.3.1-4-enchilada and magisk 20.1. (I had used this guide to do it. https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213) Today I downloaded the zip for 10.0.1 from the Oxygen Updater app and tried to flash it like I have done for OOS 9 in the past as usual. I went to recovery (I did not backup), I just wiped my data (not internal storage), cache and system. After that I tried to install the new zip but I got an error. It just said error unable to install. Didn't mention why. I tried flashing the older OOS 10 zip and got the same error.
So I thought I will try flashing on the other slot. I was on slot B. I switched to slot A and got the same error.
So I thought I will try to sideload. When I tried that I got the same error. So I thought I will try to reflash the twrp img itself. I went to fastboot mode and tried runnning this command
fastboot boot twrp-3.3.1-14-enchilada-Q-mauronofrio.img
It showed me this error
Sending 'boot.img' (65536 KB) OKAY [ 1.609s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Now I don't have any recovery at all. I have just the unlocked bootloader and no OS nor recovery. What can I do to flash TWRP again and install either OOS 10.0.1 zip or 10.0.0 zip? Any help will be great.
Thanks
Click to expand...
Click to collapse
So basically what happened there is TWRP doesn't boot with the oxygenos 10 bootloader. You will need to use the MSM download tool to unbrick your device.
Sent from my ONEPLUS A6003 using Tapatalk

Kaleshwar said:
So basically what happened there is TWRP doesn't boot with the oxygenos 10 bootloader. You will need to use the MSM download tool to unbrick your device.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
But how is that? I was on stable OOS 10 before rooting following this link https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213. As per this, the first step is to flash twrp and that image did flash back when I did it. Any idea why it doesn't work now?
Also, do you have any links for the MSM download tool and any guide if there is?
Thanks

Arnavzz said:
But how is that? I was on stable OOS 10 before rooting following this link https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213. As per this, the first step is to flash twrp and that image did flash back when I did it. Any idea why it doesn't work now?
Also, do you have any links for the MSM download tool and any guide if there is?
Thanks
Click to expand...
Click to collapse
The problem isn't TWRP it's the bootloader. That's all I know. And for the MSM download tool. See attached link below.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Sent from my ONEPLUS A6003 using Tapatalk

Do not boot the twrp from fastboot it won't work
Just do
Fastboot flash boot twrp.img
Then reboot the device to twrp it will boot to trwp and then flash the new a10 zip and immediately afterwards flash the twrp zip

chintu1234 said:
Do not boot the twrp from fastboot it won't work
Just do
Fastboot flash boot twrp.img
Then reboot the device to twrp it will boot to trwp and then flash the new a10 zip and immediately afterwards flash the twrp zip
Click to expand...
Click to collapse
This doesn't work. It flashes successfully but when I select Reboot Recovery and press the power button, it boots back to the bootloader.

Maybe wrong twrp img
Try the older 3.3.1-12 twrp.img and then try
Also try the following as well
Fastboot flash boot_a twrp.img
Fastboot flash boot_b twrp.img
And try just reboot not reboot to recovery

Kaleshwar said:
The problem isn't TWRP it's the bootloader. That's all I know. And for the MSM download tool. See attached link below.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Thanks so much for that! I have been able to recover the phone using MSM download tool. Now will update to 10 using the phones OTA.
However, I have one question, if I update to OOS 10.0.1, do you think this original post on rooting OOS 10, will work for it? https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 Or do you suggest to not root and wait?

Arnavzz said:
Thanks so much for that! I have been able to recover the phone using MSM download tool. Now will update to 10 using the phones OTA.
However, I have one question, if I update to OOS 10.0.1, do you think this original post on rooting OOS 10, will work for it? https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 Or do you suggest to not root and wait?
Click to expand...
Click to collapse
You can try it . Looks pretty solid.
Sent from my ONEPLUS A6003 using Tapatalk

Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules first to avoid issues (in TWRP if you cannot boot to system. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242)
Update through local update to 10.3.2 is what I prefer to do. Then I do the following.
Reboot to let phone finish whatever. reboot into bootloader.
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img - ( https://sourceforge.net/projects/ma...3.3.1-18-enchilada-Q-mauronofrio.img/download )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3.2 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP (https://sourceforge.net/projects/ma...-enchilada-installer-mauronofrio.zip/download ) or Blu zip (https://github.com/engstk/android_device_oneplus_enchilada/releases)
5. Reboot to recovery
6. Flash Magisk 20.3 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://mega.nz/#!PO5x1bYA!dKq3pbxUdpb16zhuqM_idqvWNLnsu4Ky4IAmYQiQUDw
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853

I had similar situation last evening.
I made the mistake of having a factory reset on rooted 9.0.8 and then trying to flash the 10.0.1
I got the same error, so I had to connect my mobile to my laptop, fastboot to the newest TWRP, flash the TWRP, flash the 9.0.9, flash the 10.0.1, flash magisk 20.x and then everything was working.

xpakage said:
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules
Update through local update 10.3 or current ROM
Reboot
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-16-enchilada-Q-mauronofrio.img - ( https://androidfilehost.com/?fid=4349826312261678088 )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP ( https://androidfilehost.com/?fid=4349826312261678087 ) or Blu zip (https://github.com/engstk/op6/releases/download/r112/blu_spark_r112-oos_op6-op6t_0dd5f9228.zip)
5. Reboot to recovery
6. Flash Magisk 20.1 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://drive.google.com/file/d/1w44cUg815g-H1h_6gObUVPLDTc_dtiMX/view
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Click to expand...
Click to collapse
This worked for me.. Finally. PS - I did in a slightly different order. I installed twrp first, booted into twrp, made sure I was in slot A. If I wasnt, I rebooted to recovery. If I still wasnt I set slot to A manually then rebooted to recovery again. Flashed the stock boot img you linked to boot, then rebooted to recovery slot b (same process I did to get to slot a) then flashed the stock boot img to boot again THEN finally installed magisk. Booted to system, where it hanged a bit, rebooted before getting into android, but booted in just fine after that..
For some reason if you don't flash stock img to slot A (and maybe slot B too, I did this for good measure) before installing magisk everything dies a horrible death and breaks, which can't even be recovered from /boot /system backups..
EDIT: Tried to reboot into recovery, which reverted back to stock for some reason after doing the above steps. So I proceeded to install the bluspark recovery, rebooted into recovery, made sure I was in slot b, made a back up of the boot image, then flashed bluspark kernel. Got stuck at the unlocked bootloader screen. Rebooted into recovery, restored my /boot back. Still stuck when I try to boot into system. Fixed it by booting back into recovery in slot A flashing stock boot img, then into slot b stock boot, then magisk, but also installed bluspark kernel here because I had a feeling I would lose twrp from flashing to stock boot img, and that the issue was caused by twrp (both twrp-3.3.1-16-enchilada-installer-mauronofrio and twrp-3.3.1-x_blu_spark_v9.108_op6 have this issue). Guess what? Turns out I was right. Having twrp breaks everything after you install magisk, so you need to flash the stock boot img before flashing magisk for some reason.. and cant install twrp again unless you dont mind bricking your phone.
EDIT2: F2FS works, just boot into recovery via fastboot (this should be slot b), change /data to f2fs, boot back into fastboot then into recovery again by fastboot (slot b again), flash stock boot img > magisk > bluspark kernel > f2fs_fstab.zip > f2fs_optimize.zip > factory reset/wipe (from twrp before rebooting), done just reboot into system. You of course lose twrp because magisk doesnt like twrp on oos 10.x for some reason, and will need to set everything up again to cause of the wipe. If you dont factory reset/wipe from twrp before booting into system your system will crash and reboot every time you boot into android, then have to do all the steps I listed again.
EDIT3: Never mind, I was wrong, f2fs makes almost all your apps and storage unusable. Not sure if it's cause of the rom (OOS10.3.0) or because we have to flash stock boot.img and get rid of twrp before booting into system. Either way, f2fs has never really been stable or fun to get working so better to stick to ext4.. that few percent performance boost isnt worth it.
EDIT4: This is my last update. After experimenting with different things, bricking my phone, restoring it via fastboot rom, many many times, I've verified the simplest and cleanest way to install magisk.. Do note you wont be able to keep twrp.
Method A - If you already have twrp
Boot recovery into slot a, flash your rom's stock boot.img, then boot into your recovery in slot b (dont boot into slot a recovery because slot a wont have twrp anymore), flash your rom's stock boot.img, magisk and (optional) your kernel of choice (or not) in that order, then you can boot boot into system. That's it.
Method B - If you don't have twrp
Boot into fastboot, and from your cmd/terminal run fastboot flash boot yourtwrp.img (I suggest Mauronofrio's twrp-3.3.1-16-enchilada-Q-mauronofrio.img or newer). Use your volume buttons to select boot into recovery. Make sure your active slot is B, (if it isnt, install twrp (bluspark and Mauronofrio's twrp both work great) by zip, then follow the steps above in method A). Once you've verified you're in slot B flash your rom's stock boot.img, magisk and (optional) your kernel of choice (or not) in that order, then you can boot into system. That's it.
Maybe @mauronofrio or @eng.stk can verify why magisk or twrp bricks the system when you install them together on OOS 10.

not working
sir i follow your steps but phone is stuck on boot i have official version a10 10.3.0 update on 25.12.19
pls tell me how i get root access....

gauravkapoor99150 said:
sir i follow your steps but phone is stuck on boot i have official version a10 10.3.0 update on 25.12.19
pls tell me how i get root access....
Click to expand...
Click to collapse
U need to flash the magisk v22 zip file through the .108 TWRP recovery
Sent from my ONEPLUS A6003 using Tapatalk

RASTAVIPER said:
U need to flash the magisk v22 zip file through the .108 TWRP recovery
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
sir can you send me a link

lemon07r said:
Maybe @mauronofrio or @eng.stk can verify why magisk or twrp bricks the system when you install them together on OOS 10.
Click to expand...
Click to collapse
@mauronofrio wrote the following in his TWRP thread a while ago:
So little update, after some tests i'm sure there is a compatibility problem between twrp and magisk, i was able to get only one of them, so actually i don't know how to proceed, i need to understand if it is a twrp problem or a magisk problem, TWRP is in stand-by for now.
There are not problems on Android Pie, if you need of the twrp on android Q just flash in boot partition the Q .img (fastboot flash boot twrp.img) and then reboot from fastboot in recovery. Before publishing the twrp I had not tested magisk and twrp together.
On Android 10 use only magisk 19.4
Click to expand...
Click to collapse

xpakage said:
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules first to avoid issues (in TWRP if you cannot boot to system. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242)
Update through local update to 10.3.2 is what I prefer to do. Then I do the following.
Reboot to let phone finish whatever. reboot into bootloader.
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img - ( https://sourceforge.net/projects/ma...3.3.1-18-enchilada-Q-mauronofrio.img/download )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3.2 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP (https://sourceforge.net/projects/ma...-enchilada-installer-mauronofrio.zip/download ) or Blu zip (https://github.com/engstk/android_device_oneplus_enchilada/releases)
5. Reboot to recovery
6. Flash Magisk 20.3 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://mega.nz/#!PO5x1bYA!dKq3pbxUdpb16zhuqM_idqvWNLnsu4Ky4IAmYQiQUDw
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Click to expand...
Click to collapse
Basically worked for me, too, with 2 exceptions:
- this tool to remove magisk modules etc. wouldn't be flashed, always ended in an unnamed error; probably the cause for some other problems?
- flashing boot.img (V 10.3.4 from this thread) didn't work for me, I always ended up in twrp's splash screen
- got it solved by dirty flashing the full V 10.3.4 ROM (again from the above thread)
Many thanks once again!

phone reset

how can I reset my phone so it boots. Do I need to fastboot flash oxygenOS or can I just install the zip file through TWRP?
Would fastboot flashing 9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip work?

doctor_whooves said:
how can I reset my phone so it boots. Do I need to fastboot flash oxygenOS or can I just install the zip file through TWRP?
Would fastboot flashing 9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip work?
Click to expand...
Click to collapse
Hard to say, without knowing how your phone got into this (no boot) state. What other things you tried, etc.
Fastboot flashing the (stock fastboot) ROM may work. As you figured, it will restore stock ROM and wipe the device. Can't be installed with TWRP, as far as I know.
If you have (or find the right) full OTA zip, you should be able to flash that with TWRP.

Installing custom ROM (Havoc) from scratch

I am going to give it one more go, before I go mad
On the OnePlus 7Pro.
Dirty flash = without wiping anything?
Clean flash = with wiping, but what?
Going to go back to a full stock mode: https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
Then the following steps;
- Unlock bootloader.
- Get the latest version of havoc: https://sourceforge.net/projects/havoc-os/files/guacamole/
- Get Gapps
- Get TWRP
- Get Magisk
- Reboot and use adb to flash twrp.img
- wipe what? Some variations I have come across, so just asking.
- Flash OOS (some say, but which version).
- Reboot to recovery, or flash custom ROM and TWRP.zip?
- flash custom ROM and TWRP on other slot without wiping anything?
- Reboot to recovery.
- Flash Gapps and Magisk (on slot it is on after last reboot, or doesn't it matter?)
- Reboot system.

Follow these steps. they always worked for me.
1. flash twrp.img using adb
2. sideload twrp using adb sideload
3. reboot recovery
4. format data(one where you type YES)
5. reboot recovery
6. flash oos & twrp
7. reboot recovery
8. flash oos and twrp
9. reboot recovery
10. format data
11. reboot recovery
12. flash rom and twrp
13. reboot recovery
14. flash gapps(if necessary)
15. flash magisk(do remember that some roms require first boot before magisk is flashed)
16. dlash dm verity(if you want to stay decrypted).
17. reboot system

pranacrockz said:
Follow these steps. they always worked for me.
1. flash twrp.img using adb
2. sideload twrp using adb sideload
3. reboot recovery
4. format data(one where you type YES)
5. reboot recovery
6. flash oos & twrp
7. reboot recovery
8. flash oos and twrp
9. reboot recovery
10. format data
11. reboot recovery
12. flash rom and twrp
13. reboot recovery
14. flash gapps(if necessary)
15. flash magisk(do remember that some roms require first boot before magisk is flashed)
16. dlash dm verity(if you want to stay decrypted).
17. reboot system
Click to expand...
Click to collapse
Going to try this later, after being out of the game for a while this new "A/B" stuff is just totally defeating me. I've had to restore the phone with that M2M program, or whatever it is called, like 4 times. Ugh. Really miss the old days.

Do step 4 again(format data) if you are still getting stuck on startup or a bootloop, then reboot. That is what I had to do with my Havoc install to get the ROM to boot.

pranacrockz said:
Follow these steps. they always worked for me.
1. flash twrp.img using adb
2. sideload twrp using adb sideload
3. reboot recovery
4. format data(one where you type YES)
5. reboot recovery
6. flash oos & twrp
7. reboot recovery
8. flash oos and twrp
9. reboot recovery
10. format data
11. reboot recovery
12. flash rom and twrp
13. reboot recovery
14. flash gapps(if necessary)
15. flash magisk(do remember that some roms require first boot before magisk is flashed)
16. dlash dm verity(if you want to stay decrypted).
17. reboot system
Click to expand...
Click to collapse
Why are you using adb twice to install twrp on some nonsense that's unnecessary. All your is open cmd in the folder where you have twrp.img or whatever you named it boot to fastboot
fastboot boot nameoffile.img
Flash twrp installer after it boots and you're done.
And before you try to say that commands doesn't work like everyone I'm going cut you off and let you know that it does no problem cause i always use it. You don't need sideload or flash anything with adb. One simple fastboot command will do it.

pranacrockz said:
Follow these steps. they always worked for me.
1. flash twrp.img using adb
2. sideload twrp using adb sideload (how come sideload again if I used the fastboot command?)
3. reboot recovery
4. format data(one where you type YES)
5. reboot recovery
6. flash oos & twrp
7. reboot recovery
8. flash oos and twrp
9. reboot recovery
10. format data (where I type yes again?)
11. reboot recovery
12. flash rom and twrp
13. reboot recovery
14. flash gapps(if necessary)
15. flash magisk(do remember that some roms require first boot before magisk is flashed)
16. dlash dm verity(if you want to stay decrypted).
17. reboot system
Click to expand...
Click to collapse
Thanks for the reply.
I have a few questions, see above in the quote.
Besides that, when I come from stock, do I need to flash the OOS twice on both slots, and if so, why is that?

Locklear308 said:
Going to try this later, after being out of the game for a while this new "A/B" stuff is just totally defeating me. I've had to restore the phone with that M2M program, or whatever it is called, like 4 times. Ugh. Really miss the old days.
Click to expand...
Click to collapse
Same here

With you guys on the "wow this has become a confusing process" boat.
The thing that gets me is with 100% of tuts, they say format data and then say format data again later when I think they mean wipe data the second time. Am I right?
The process even seems more straight forward following the dual boot twrp tutorial.
I don't have a need to update my custom rom yet so I just would like a clear understanding.
Before someone says "well you've already done it" I fluked it somehow. Lol

dennisb71 said:
Thanks for the reply.
I have a few questions, see above in the quote.
Besides that, when I come from stock, do I need to flash the OOS twice on both slots, and if so, why is that?
Click to expand...
Click to collapse
10. To clarify, yes you have to format(where you type yes)
As far as sideload is concerned, I followed it from a guide written by some dev. But it is not necessary. You may skip it
If coming from stock, you may skip those steps. You just have to ensure that both slots have oos

pranacrockz said:
10. To clarify, yes you have to format(where you type yes)
As far as sideload is concerned, I followed it from a guide written by some dev. But it is not necessary. You may skip it
If coming from stock, you may skip those steps. You just have to ensure that both slots have oos
Click to expand...
Click to collapse
I feel it's gonna be a long weekend again
Wish I could say....here's 20 euro's, please get the ROM running as it should.

pranacrockz said:
Follow these steps. they always worked for me.
1. flash twrp.img using adb
2. sideload twrp using adb sideload
3. reboot recovery
4. format data(one where you type YES)
5. reboot recovery
6. flash oos & twrp
7. reboot recovery
8. flash oos and twrp
9. reboot recovery
10. format data
11. reboot recovery
12. flash rom and twrp
13. reboot recovery
14. flash gapps(if necessary)
15. flash magisk(do remember that some roms require first boot before magisk is flashed)
16. dlash dm verity(if you want to stay decrypted).
17. reboot system
Click to expand...
Click to collapse
I tried the same steps for my onePlus 7 but post flashing oos and twrp and all the steps at step 12 while i try flashing custom rom i.e Pixel experience in my case i get the belowmessage
"Flashing A/B zip to inactive slot B .
To flash additional zips, please reboot recovery to switch to the uploaded slot.
Error installing zip file '/sdcard/PixelExperience_gucamoleb-11.0-20210217-1706-BETA-OFFICIAL.zip'
updating partition details......
...done'"
But while doing step 6 i.e flash oos and twrp despite the below message
"Flashing A/B zip to inactive slot B .
To flash additional zips, please reboot recovery to switch to the uploaded slot"
It gets flashed without issues.
Just to let u know my phone got bricked so i installed the official firmware using the below command.
fastboot -w update images.zip
Any help on this will be appreciated as i m kinda stuck with the stock rom.