Database Info

Can't install custom ROMs. Help!!!

Few days earlier I had to use MSM tool as my OP6 only went to Crash Dump mode everytime.
So after flashing the tool, everything went back to normal, but since then I can't get any custom ROM to install on my phone. whenever I do flash the rom and then twrp, I reboot to recovery for flashing gapps, it takes me to fastboot mode instead and never boots.
Evidently, I have installed Omni, Havoc and all the other roms before. What can the problem be? Any help please?

I supposed you read the instructions and flashed to both slots? Or did you do like most and skip a few steps?

Hi!
I am in the same situation : MSM tool and then I can no longer install custom rom. Have you resolved the problem ?
Thanks !

julienbdx said:
Hi!
I am in the same situation : MSM tool and then I can no longer install custom rom. Have you resolved the problem ?
Thanks !
Click to expand...
Click to collapse
Did you flash oos to both slots? Like the comment above yours tells him to.

People need to read. This already been discussed over and over.

I didn't understand in the previous post that it is OOS that need to be flash twice, not the custom rom. Thanks whizeguy !

The OP6 is my first device with this A / B. I read a lot about this A / B and I think I understand it. But I'm going to install this ROM https://forum.xda-developers.com/o...eally so stupid? Can some one help me please?

Have you tried the new Blue Spark TWRP?

RheinPirat said:
The OP6 is my first device with this A / B. I read a lot about this A / B and I think I understand it. But I'm going to install this ROM https://forum.xda-developers.com/o... and twrp a second time and flash gapps
Done.
Click to expand...
Click to collapse

Blunts47 said:
Why are you trying to wipe twice lol
Steps:
Wipe data, system, dalvik.
Reboot recovery. Flash ROM and twrp
Reboot twrp and the slot auto switches then flash rom and twrp a second time and flash gapps
Done.
Click to expand...
Click to collapse
If i boot in to twrp, flash the rom and twrp, go to reboot -> recovery: the screen stays black and does not reboot in to recovery.
I tried twrp-3.2.3-1-enchilada and twrp-3.2.3-x_blu_spark_v9.86_op6
After hours of trying, the phone booted one time the new rom. Now i'm back on the stock rom, because OP of the ROM listed features which are not included.

Mi Mix 3 bootloop

Good day all,
for some time, i have been using the Mi Mix 3 CN version with Xiaomi.EU weekly Rom and i loved it.
Today, I decided to try install the Unofficial PE Rom witch can be found here (https://treble.andro.plus/pe.html)
I Followed these instructions (https://www.getdroidtips.com/pixel-experience-rom-xiaomi-mi-mix-3/)
For some reason i decided to do a full wipe ie. ;
Dalvik/ART Cache
Data
Internal Storage
Cache
System
I went to install PE ROM and upon completion, i was boot-looping and rebooting into TWRP Recovery 3.2.3-1205 for MIX 3 --by wzsx150.
In a panic, i tried reinstalling the weekly ROM again by doing the same steps above, and behold i am still getting the same problem.
Would someone please help me out here as for this is my only phone and need to get it back up and running.
Thanks in advance.

neilgeaney1 said:
Good day all,
for some time, i have been using the Mi Mix 3 CN version with Xiaomi.EU weekly Rom and i loved it.
Today, I decided to try install the Unofficial PE Rom witch can be found here (https://treble.andro.plus/pe.html)
I Followed these instructions (https://www.getdroidtips.com/pixel-experience-rom-xiaomi-mi-mix-3/)
For some reason i decided to do a full wipe ie. ;
Dalvik/ART Cache
Data
Internal Storage
Cache
System
I went to install PE ROM and upon completion, i was boot-looping and rebooting into TWRP Recovery 3.2.3-1205 for MIX 3 --by wzsx150.
In a panic, i tried reinstalling the weekly ROM again by doing the same steps above, and behold i am still getting the same problem.
Would someone please help me out here as for this is my only phone and need to get it back up and running.
Thanks in advance.
Click to expand...
Click to collapse
Going from one rom to another requires you to remove encryption so format data

Mackay53 said:
Going from one rom to another requires you to remove encryption so format data
Click to expand...
Click to collapse
Cheers for the advice, got it up and running back on the weekly :good:
What is the correct procedure to get it running on the PE ROM?
Regards

neilgeaney1 said:
Cheers for the advice, got it up and running back on the weekly :good:
What is the correct procedure to get it running on the PE ROM?
Regards
Click to expand...
Click to collapse
1. Flash the China dev vendor.img, or the full China Dev ROM, or Xiaomi EU (works ok with PE)
2. Install PE zip
3. Quick Wipe and format 'yes' in twrp
4. Flash Magisk
That's how I do it for all ROMs and GSI and works fine.
You'll get the China dev vendor IMG from the link on post one of the PE thread. You can flash it with twrp.
Always recommend to use the vendor IMG from China Dev instead of EU, especially with the GSI ROMs.

are you on global?
In twrp: factory reset then format data (hit yes to accept).
Reboot phone and reenter twrp.
Connect to computer and transfer xiaomi.eu rom onto root of device (I suspect any would work but I happen to have used 10.2.2.0.PEECNXM_v10-9 which is believe was xiaomi.eu stable release), pixel experience ROM zip and magisk-v17.3mod4mimix3
Flash the xiaomi.eu rom first then without rebooting or any formatting or factory resetting immediately flash the PE ROM zip and then magisk 17.3.
Once those three files are flashed via twrp go to wipe and the factory reset then format data again
this always works for me
thanks to @homer.ali

Works for the Mi Mix 3 coming from MIUI 11 EU
raven213 said:
Flash the xiaomi.eu rom first then without rebooting or any formatting or factory resetting immediately flash the PE ROM zip and then magisk 17.3.
Once those three files are flashed via twrp go to wipe and the factory reset then format data again
Click to expand...
Click to collapse
Thank you so much for these instructions. Coming from Global MIUI 11, I tried to figure out how to install PE for the last 2 days and every time I ended up being stuck in a bootloop. So far, I tried to install Resurrection Remix, Lineage OS and Evolution X without success.
Your instructions solved this issue. BTW: the only working version of TWRP for me was twrp-3.2.3-8-perseus-mauronofrio. After flashing this version, I was able to install the latest TWRP.
this always works for me
Click to expand...
Click to collapse
Do you (or anyone else in this thread) know whether these steps [install order: xiaomi.eu, rom, magisk | then: factory reset + wipe data] work for other custom roms on the Mi Mix 3 as well? >> Short answer: no. Tried it for the above roms. I always end up in TWRP (or bootloop) after flashing either way (the official or the on I 've tried here).

@chromanju did you solve this problem?

Problem with running non-MIUI roms

I'm not able to run any non-MIUI rom (LOS or AOSP - it doesn't matter). I have TWRP 3.3.0.0 and latest MIUI firmware installed, When I'm flashing the rom (rom+gapps to be precise), the process finishes successfully but I'm stuck on ROM boot animation forever. What could go wrong?
Edit: I'm wiping data+system+cache of course.

watchoutbehindyou said:
I'm not able to run any non-MIUI rom (LOS or AOSP - it doesn't matter). I have TWRP 3.3.0.0 and latest MIUI firmware installed, When I'm flashing the rom (rom+gapps to be precise), the process finishes successfully but I'm stuck on ROM boot animation forever. What could go wrong?
Edit: I'm wiping data+system+cache of course.
Click to expand...
Click to collapse
You need to pick the "format" option and wipe complete internal storage
Your issue is due to encryption which was done by the miui rom

malimukk said:
You need to pick the "format" option and wipe complete internal storage
Your issue is due to encryption which was done by the miui rom
Click to expand...
Click to collapse
Yes, I did it. I did the format option when you have to type "yes". Process of flashing goes fine but rom is stuck on the boot animation for 7-8 minutes (maybe more). It looks like that encryption is the problem because MIUI roms are loading fine, but I wiped literally EVERYTHING, with format internal storage included.
Maybe I should try with different TWRP?
I'm a little afraid to go for the older version because I've already flashed 3.3.0.0...

watchoutbehindyou said:
Yes, I did it. I did the format option when you have to type "yes". Process of flashing goes fine but rom is stuck on the boot animation for 7-8 minutes (maybe more). It looks like that encryption is the problem because MIUI roms are loading fine, but I wiped literally EVERYTHING, with format internal storage included.
Maybe I should try with different TWRP?
I'm a little afraid to go for the older version because I've already flashed 3.3.0.0...
Click to expand...
Click to collapse
The TWRP version should be fine. Then another potential issue at this moment would be if you are flashing on the latest version of MIUI. Or more precisely, the latest firmware and vendor version..
Perhaps you can try to flash the firmware from MIUI 9.2.28 Developer version. Then Format and install a custom rom.
Good luck!

watchoutbehindyou said:
I'm not able to run any non-MIUI rom (LOS or AOSP - it doesn't matter). I have TWRP 3.3.0.0 and latest MIUI firmware installed, When I'm flashing the rom (rom+gapps to be precise), the process finishes successfully but I'm stuck on ROM boot animation forever. What could go wrong?
Edit: I'm wiping data+system+cache of course.
Click to expand...
Click to collapse
Try the earlier Miui versions eg. 9.3.28. The latest caused mine to show the bootlogo indefinitely!
The rest of your procedure should be fine!

Great!
kleinholzinferno said:
Try the earlier Miui versions eg. 9.3.28. The latest caused mine to show the bootlogo indefinitely!
The rest of your procedure should be fine!
Click to expand...
Click to collapse
Thank you! Had the same problem and your solution worked for me just fine

Sd card not used

Hello,
I am running PixysOS rom on my Honor 6X (BLN-AL20) since some months and I am actually satisfied of the stability and usability of the Rom.
Actually I can't convince the device to use the installed as card to store pictures, videos etc.
The SD card is recognised and listed under memory but the system is not using it.
Is there any workaround to fix this problem?
Thanks,
Andrea.
Sent from my BLN-AL20 using Tapatalk

Anybody out there?
Sent from my BLN-AL20 using Tapatalk

Sephiroth79 said:
Anybody out there?
Sent from my BLN-AL20 using Tapatalk
Click to expand...
Click to collapse
for me my internal storage is not detected. only sd card is main storage. seems like its a bug and never gonna fixed. there is no perfect android 9 os out there. so better go to emui 8 and use cyclox kernel.

Sephiroth79 said:
Hello,
I am running PixysOS rom on my Honor 6X (BLN-AL20) since some months and I am actually satisfied of the stability and usability of the Rom.
Actually I can't convince the device to use the installed as card to store pictures, videos etc.
The SD card is recognised and listed under memory but the system is not using it.
Is there any workaround to fix this problem?
Thanks,
Andrea.
Click to expand...
Click to collapse
By what I read in the thread of DotOS, that's a bug that should had be fixed in latest builds... Are you using latest version or not?
Anyway every Pie ROM/GSI I tried seems to read microSD, eject it and re-read once again immediately after booting to OS, on every single boot. Then, there are systems that keep reading the microSD (as AEX, Descendant...) and allows modifications, reading files, basically everything you should be able to do with a microSD, and systems that just keep it ejected (like DotOS did on old builds). Saw other users reporting that on the thread. Look for "microSD" in DotOS thread to read latest comments about, there you could find a solution. By how things sound at the moment, my only advice is to move on another system.

Thanks for your reply. Could you suggest me a proper and stable rom?

Sephiroth79 said:
Thanks for your reply. Could you suggest me a proper and stable rom?
Click to expand...
Click to collapse
Nothing hard to do man. We use to thank others with the appropriate button, for next times.
Anyway since that we're not talking 'bout different devices but we share the same phone, i feel to strongly recommend ya the Descendant GSI project by Dil3mm4.. It's a fork of Phh AOSP project but with sone very good extras. I never used a system smooth like this one, really impressive. It has a decent amount of customizations options (not at levels like RROS in example, but too much is too much IMHO), great battery management, fluid transitions and great compatibility with Huawei devices (it's a GSI, but the dev has a P8 Lite at the moment, so he knows how to make things working on Huawei).
Give it a shot, you can always go back to stock with HuRUpdater in just 5 minutes. And in case you'd like to try more, remember to take a look into Treble section here on XDA. Every arm64 a-only GSI is good to be flashed on our device, but before flashing just look if other users owning a Huawei device have already tried it or not. I say this simply because many GSIs are actually not working thanks to our vendor compatibility, so make things without hurry and nothing can go wrong

Used appropriate "thanks button" this time...eheh
Any tutorial on how to install the Descendant GSI rom starting from PixysOs with Askuccio's TWRP?

Sephiroth79 said:
Used appropriate "thanks button" this time...eheh
Any tutorial on how to install the Descendant GSI rom starting from PixysOs with Askuccio's TWRP?
Click to expand...
Click to collapse
Well there isn't a dedicated tutorial for every ROM/GSI you're starting from, overall because a clean flash is strongly recommended (especially when you switch from a ROM to a GSI) - you can dirty flash Descendant updates or other GSIs based on phhusson trees without problems, but in this case you've already modified your device kernel and other stuff with a custom ROM, so it's better to start from scratch in way to avoid useless wastes of time running to repairs with hurry.
The faster and safest way to do this is:
1) restore stock OS with HuRUpdater and let it boot (i saw that you already own Askuccio's TWRP, i always had to use Elemental TWRP from KingOfMezi in way to use HuRU without errors, but apart this Askuccio's TWRP works for flashing everything you'd need);
2) following steps listed in Descendant OP, flash the system image through fastboot or through TWRP, then reboot to TWRP once again and wipe ONLY /cache and /dalvikART partitions;
3) factory reset through stock recovery and let the system boot (yeah, you'll have to reflash stock recovery once again before reflashing TWRP - again.
4) flash all the rest you'd like to flash (GApps, Magisk, ecc.)
By default, /data partition remains encrypted after performing factory reset with stock recovery, and so with TWRP you won't be able to perform full backups, but you can also choose to run with /data decrypted. The method isn't supported by the developer, but works like a charm (personally tested about 3 versions of the GSI ago, worked). You just have to flash "disable dm verity" script during the process, but you can know more by reading about it here.
Happy flashing

RedSkull23 said:
Well there isn't a dedicated tutorial for every ROM/GSI you're starting from, overall because a clean flash is strongly recommended (especially when you switch from a ROM to a GSI) - you can dirty flash Descendant updates or other GSIs based on phhusson trees without problems, but in this case you've already modified your device kernel and other stuff with a custom ROM, so it's better to start from scratch in way to avoid useless wastes of time running to repairs with hurry.
The faster and safest way to do this is:
1) restore stock OS with HuRUpdater and let it boot (i saw that you already own Askuccio's TWRP, i always had to use Elemental TWRP from KingOfMezi in way to use HuRU without errors, but apart this Askuccio's TWRP works for flashing everything you'd need);
2) following steps listed in Descendant OP, flash the system image through fastboot or through TWRP, then reboot to TWRP once again and wipe ONLY /cache and /dalvikART partitions;
3) factory reset through stock recovery and let the system boot (yeah, you'll have to reflash stock recovery once again before reflashing TWRP - again.
4) flash all the rest you'd like to flash (GApps, Magisk, ecc.)
By default, /data partition remains encrypted after performing factory reset with stock recovery, and so with TWRP you won't be able to perform full backups, but you can also choose to run with /data decrypted. The method isn't supported by the developer, but works like a charm (personally tested about 3 versions of the GSI ago, worked). You just have to flash "disable dm verity" script during the process, but you can know more by reading about it here.
Happy flashing
Click to expand...
Click to collapse
Point 1: I have to download stock fw using Huawei firmware finder and I have to use Askuccio's TWRP to flash HuRupdater on the device. Do I have to choose a custom recovery or I have to let HuRupdater flash stock recovery too?
Point 2: you are saying I have to wipe cache/dalviw partitions using TWRP so I have to flash TWRP after flashing and booting stock fw?

Sephiroth79 said:
Point 1: I have to download stock fw using Huawei firmware finder and I have to use Askuccio's TWRP to flash HuRupdater on the device. Do I have to choose a custom recovery or I have to let HuRupdater flash stock recovery too?
Point 2: you are saying I have to wipe cache/dalviw partitions using TWRP so I have to flash TWRP after flashing and booting stock fw?
Click to expand...
Click to collapse
To me flashing HuRU with Askuccio TWRP never worked, as said above, so i'd suggest you to look for ElementalTWRP in way to have a custom recovery that can flash HuRU with no problems. Secondarily, in way to avoid confusion, just start from stock and do a fastboot flash of Descendant, reboot to OS and let it boot. Once set, flash TWRP and flash GApps, then wipe just /cache and /dalvik and reboot one last time. Then you can do anything you want.

RedSkull23 said:
To me flashing HuRU with Askuccio TWRP never worked, as said above, so i'd suggest you to look for ElementalTWRP in way to have a custom recovery that can flash HuRU with no problems. Secondarily, in way to avoid confusion, just start from stock and do a fastboot flash of Descendant, reboot to OS and let it boot. Once set, flash TWRP and flash GApps, then wipe just /cache and /dalvik and reboot one last time. Then you can do anything you want.
Click to expand...
Click to collapse
Ok, I'll put elemental TWRP recovery in the same directory in order to let HuRU flash it together with the stock firmware.
Edit: can't find elemental twrp download link

Sephiroth79 said:
Ok, I'll put elemental TWRP recovery in the same directory in order to let HuRU flash it together with the stock firmware.
Edit: can't find elemental twrp download link
Click to expand...
Click to collapse
Good, i usually do that later just in case the system prompts to factory reset before booting, but it's up to you. Here's the link anyway https://mega.nz/#!a81EDZAR!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk

Using fw finder I downloaded the fw named: BLN-AL30C00B541 (8.0.0.541) FULLOTA-MF 2018.12.27
Clicking on download give me some choices:
- update.zip (1.74 GB)
- BLN-Al20_all_cn/update_full_BLN-AL20_all_cn.zip (643 MB)
Already downloaded both of them and can't find any of the files required from HurUpdater to run. Do I have to use an extractor?
EditOne: used Huawei Update Extractor gives an error on the update.app extracted from the update.zip archive and works on the same file extracted from BLN-Al20_all_cn/update_full_BLN-AL20_all_cn.zip
Edit2: just realized I don't need to extract anything but still can't find update_data_public and update_all_hw files

That is because it's Chinese build and as you just noticed some update packages are assembled in a slightly different manner, so some package misses one if not two useful zips. Would you mind to switch to India variant? Nothing changes in performance nor in features, plus if you'd only use the firmware as a base to get to other ROMs/GSIs, it really doesn't matter (but i can offer better assistance since that i'm more experienced with India variant other than China). FYI in this thread https://forum.xda-developers.com/honor-6x/how-to/french-language-t3938592/ i've already guided an user to obtain India variant, but it's really simple:
in TEAM MT site (google for "team mt online firmware database", the first result you get is what you need), look for build "BLN-L22HNC675CUSTC675D1B510" - you'll obtain 4 results. Download the package dated 2018.07.19, it is the better one. From here you just have to follow instructions in HwOTA thread, renaming the three packages as suggested in OP and choosing to debrand during the process to BLN-L22 region/variant (don't remember if it happens anyway since that the firmware is India variant but it's a thing that doesn't give hassles).

how to know if it's a bootloop?

hello i was upgrading from stock 9.0.7 to 9.0.9, my bootloader is unlocked and twrp is a permanent one, the phone is also rooted. i wiped system then flashed the 9.0.9 then flashed the 4.0.4 twrp, rebooted into twrp, flashed latest magisk, rebooted into twrp and then pressed reboot into system. the phone is encrypted. the booting animation has been on for 20-30 minutes at this point. is it a bootloop? why what did i do wrong? thanks

@seth wellington
Try formatting data them reboot system. That should get you booted up.
Never wipe system or vendor on these devices and always when flashing a rom flash TWRP installer zip or you won't have twrp because of where recovery is located which is same place as boot.img and it has to be installed when flashing a rom or update to a rom or it won't be present.
How I flash OOS on my once T-Mobile now converted international/global OnePlus 6t.
Boot TWRP
Flash OOS global 10.3.6
Flash TWRP installer
Flash finalize
Format data
Reboot system
How I install a rom on my converted OnePlus 6t. This installation process varies depending on whether or not whatever rom I'm installing comes with gapps and or TWRP and of course you don't want to install global OOS on another model device. Since I converted my T-Mobile OnePlus 6t using guide and msm tool I now use global or international OnePlus 6t roms, firmware... Example Pixel Experience rom installation:
Boot TWRP
Flash OOS 10.3.6 global from repo xda thread
Flash Pixel Experience rom
Flash TWRP installer zip
Flash finalize zip
Format data
Reboot system.
Start to set up device then at some point enable developer options and usb debugging and doable any lock screen and boot twrp and flash magisk for root and reboot system. That is how I install a rom that has gapps but not twrp included in rom zip. Finalize can he found with a quick search on xda. It copies firmware to other slot on your AB partition device so that you don't have to. Saves 5-6 minutes and works great.
Edit
What you could have done is just flash your updated OOS , flash TWRP installer zip, reboot recovery, flash magisk, reboot system. That's what I would have done updating OOS ..
Hope this helps.
Sent from my OnePlus6T using XDA Labs

flash713 said:
@seth wellington
Try formatting data them reboot system. That should get you booted up.
Never wipe system or vendor on these devices and always when flashing a rom flash TWRP installer zip or you won't have twrp because of where recovery is located which is same place as boot.img and it has to be installed when flashing a rom or update to a rom or it won't be present.
How I flash OOS on my once T-Mobile now converted international/global OnePlus 6t.
Boot TWRP
Flash OOS global 10.3.6
Flash TWRP installer
Flash finalize
Format data
Reboot system
How I install a rom on my converted OnePlus 6t. This installation process varies depending on whether or not whatever rom I'm installing comes with gapps and or TWRP and of course you don't want to install global OOS on another model device. Since I converted my T-Mobile OnePlus 6t using guide and msm tool I now use global or international OnePlus 6t roms, firmware... Example Pixel Experience rom installation:
Boot TWRP
Flash OOS 10.3.6 global from repo xda thread
Flash Pixel Experience rom
Flash TWRP installer zip
Flash finalize zip
Format data
Reboot system.
Start to set up device then at some point enable developer options and usb debugging and doable any lock screen and boot twrp and flash magisk for root and reboot system. That is how I install a rom that has gapps but not twrp included in rom zip. Finalize can he found with a quick search on xda. It copies firmware to other slot on your AB partition device so that you don't have to. Saves 5-6 minutes and works great.
Edit
What you could have done is just flash your updated OOS , flash TWRP installer zip, reboot recovery, flash magisk, reboot system. That's what I would have done updating OOS ..
Hope this helps.
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
Thank you very much for your reply. Unfortunately I couldn't wait for that long and I had to do something right then. After some attempts I also lost my twrp and was left without a functioning recovery, so I had to look for help and some people helped me go through unbricking through the msm tool.
The thing is i just really want to always flash clean so that the phone doesn't lag and works properly, I had no idea you shouldn't wipe system... The guide that I followed said that when updating oxygen manually you have to wipe system so I thought nothing would go wrong. I still don't know what caused a bootloop since that guide was a verified one. Thanks a lot for your help. So if I'm reading it correctly, you have to do the wipes after you've installed the system, not before?

seth wellington said:
Thank you very much for your reply. Unfortunately I couldn't wait for that long and I had to do something right then. After some attempts I also lost my twrp and was left without a functioning recovery, so I had to look for help and some people helped me go through unbricking through the msm tool.
The thing is i just really want to always flash clean so that the phone doesn't lag and works properly, I had no idea you shouldn't wipe system... The guide that I followed said that when updating oxygen manually you have to wipe system so I thought nothing would go wrong. I still don't know what caused a bootloop since that guide was a verified one. Thanks a lot for your help. So if I'm reading it correctly, you have to do the wipes after you've installed the system, not before?
Click to expand...
Click to collapse
Quit a few pretty well known developers here on xda (AOSiP op is one and there are more) say not to wipe system or vendor in their first posts of their custom rom threads. The way I describe how I install works 100% always and is the cleanest possible installation. Formatting data when installing a new rom at the end of install process does all the wiping needed to make sure nothing is left from the past and everything is clean. I used to wipe various partitions but on other devices. The install directions I use are originally from the PiXeN rom developers op. I've been flashing roms since the Nexus S days. Not saying that means anything other than I'm kinda old now. ? But that install process has never failed me once and I've flashed I'm sure hundreds of times on this device.. When I update i just flashing the updated rom over current and don't wipe anything then flashing twrp installer zip, reboot recovery flash magisk reboot system or if gapps are needed when I reboot recovery flash gapps..Unless it's a major OS update that's always worked for me.
Possibly not formatting data caused boot loop.. I know when going from OOS to AOSP rom format data is mandatory or it won't boot system.. I never flash magisk during initial flash. I always boot system first then at some point boot twrp and flash magisk. Try that next round and see if it turns out better. The whole AB partition deal made me feel like I was really old and retarded.
If I was updating OOS I would boot recovery, flash OOS, flash twrp installer zip reboot recovery, flash magisk, reboot system. Check out the finalize script xda thread. There are two here. The original person who made finalize has a thread and another user has another finalize thread. I believe in guides section of OnePlus 6t. With Android there are always more than a few ways to achieve something you know ... But what I post here is what I've been doing and I've flashed 400-500 times at least on this device.
Sent from my OnePlus6T using XDA Labs

@flash713
I totally trust you and respect anything you say and recommend me to do. Thanks a lot for all the instructions and clarification. I've been into android far less time than you — only since oneplus one. I'm extremely bad with tech but even with that phone j somehow managed to get bootloops or half-bricks ten times less than with the oneplus 6. And back then in 2015 I was way more enthusiastic: flashing twice a month loads and loads of roms. Of course it wasn't my personal achievement, I was still simply following detailed and carefully written instructions on forums on how to flash a particular rom in a particular way, but hey, at least I somehow managed it.
Now in this case I'm assuming it's the a/b partitions they've introduced that have completely changed the process and ways of flashing to the point that I stick to the guides and still get bootloops lol. That unbricking process was a huge stress for me, I don't think I'm going to touch anything in my phone for a while now. And I'm on the latest 10.3.6 oxygen so it's alright. Thank you for your help buddy

seth wellington said:
@flash713
I totally trust you and respect anything you say and recommend me to do. Thanks a lot for all the instructions and clarification. I've been into android far less time than you — only since oneplus one. I'm extremely bad with tech but even with that phone j somehow managed to get bootloops or half-bricks ten times less than with the oneplus 6. And back then in 2015 I was way more enthusiastic: flashing twice a month loads and loads of roms. Of course it wasn't my personal achievement, I was still simply following detailed and carefully written instructions on forums on how to flash a particular rom in a particular way, but hey, at least I somehow managed it.
Now in this case I'm assuming it's the a/b partitions they've introduced that have completely changed the process and ways of flashing to the point that I stick to the guides and still get bootloops lol. That unbricking process was a huge stress for me, I don't think I'm going to touch anything in my phone for a while now. And I'm on the latest 10.3.6 oxygen so it's alright. Thank you for your help buddy
Click to expand...
Click to collapse
Np. My real first name is Seth. Haha. Cool name btw. I just installed OOS 10.3.7 on my 6t. I was notified of the update yesterday via oxygen updater app from play store. Good handy app to have. I would have never known 10.3.7 was out or at least not so soon if it wasn't for that app. I believe it auto notified me too. I don't remember setting it up. Android has changed soooo much you know.. I love my OnePlus 6t though. Definitely one of my most favorite devices I've ever used. What's new today is gone at some point and replaced with "better.." lol. Not always better imo anyway. Glad I could help. Feel free to message me any time. Good day to you.