Database Users

How to flash TWRP and Root Moto X Style on Marshmallow

I am using moto x style and unlocked bootloader with 'Windroid Universal Android Toolkit' v2.5 but cannot flash TWRP and root this apl. Today I tried flash TWRP and then root but after showing 'Congratulation' pop up,my phone stucked on 'No command' page. I tried twice and same result. Later i check there is either no TWRP or root by SuperSU. And i see youtube video and and read many XDA forum and comments and most of the users says the phone stuck on M logo page when reboot after the root process. And all says its a issue with Marshmallow. And most of the xda posts and youtube video are made during 5.1.1 so there is no problem in that video during flash TWRP and root. So i need a seamless process to flash TWRP and root on Marshmallow so that it doesnot stuck on M logo. And I dont want to downgrade to L for root. And unluckily if it stuck M logo thwn what to do to go back to home screen?Thank you.

http://forum.xda-developers.com/moto-x-style/general/guide-how-to-root-pure-style-t3503958

Look in my sig...

It's in my signature... There are multiple links to what your looking for and other threads, if you are on computer they should be immediately below the message, if you're in the XDA app you have to look in the user profile (don't think it's possible in Tapatalk though).
http://forum.xda-developers.com/moto-x-style/general/guide-how-to-root-pure-style-t3503958

acejavelin said:
It's in my signature... There are multiple links to what your looking for and other threads, if you are on computer they should be immediately below the message, if you're in the XDA app you have to look in the user profile (don't think it's possible in Tapatalk though).
http://forum.xda-developers.com/moto-x-style/general/guide-how-to-root-pure-style-t3503958
Click to expand...
Click to collapse
My build no is 24.49-18-4. So is this process suitable for this build no? And still i dont flash TWRP. I tried with "Windroid Universal Android Toolkit app" to flash TWRP. though it showed a 'Successful' pop up but it didn't. Can I go with any old process to flash TWRP or u have a new process?

Atanu Mukherjee said:
My build no is 24.49-18-4. So is this process suitable for this build no? And still i dont flash TWRP. I tried with "Windroid Universal Android Toolkit app" to flash TWRP. though it showed a 'Successful' pop up but it didn't. Can I go with any old process to flash TWRP or u have a new process?
Click to expand...
Click to collapse
Step 1 - Stop using toolkits! They rarely work right on modern Android devices. With the Moto the only safe, reliable way to root is manually.
I don't know what the 'old way' is to flash TWRP your referring to here... I recommend one time booting twrp with "fastboot boot twrp.img" command (replace twrp.img with your actual twrp image file) then perform a backup to the SD card or USB OTG device and put it away for safe keeping. Then flash twrp either with twrp you have booted, or manually with "fastboot flash recovery twrp.img"
The rooting method I linked before is valid for all Marshmallow builds, if you have Lollipop or Nougat you need to find a different method.

acejavelin said:
Step 1 - Stop using toolkits! They rarely work right on modern Android devices. With the Moto the only safe, reliable way to root is manually.
I don't know what the 'old way' is to flash TWRP your referring to here... I recommend one time booting twrp with "fastboot boot twrp.img" command (replace twrp.img with your actual twrp image file) then perform a backup to the SD card or USB OTG device and put it away for safe keeping. Then flash twrp either with twrp you have booted, or manually with "fastboot flash recovery twrp.img"
The rooting method I linked before is valid for all Marshmallow builds, if you have Lollipop or Nougat you need to find a different method.
Click to expand...
Click to collapse
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I am saying about this official method which is on twrp.me site. And after typing 'fastboot reboot' what I have to do to go home page? Sorry to ask u so many things. Actually I am totally new in this thing and very much worry after facing issues 2-3 times. And thank u very much for fast reply.
One more ques, I have unlocked bootloader with that "Windroid Universal Android Toolkit". Now in fastboot it shows 'bootloader unlocked,code 3' is that ok? As u say toolkit doesnot work on modern devices.

Atanu Mukherjee said:
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I am saying about this official method which is on twrp.me site. And after typing 'fastboot reboot' what I have to do to go home page? Sorry to ask u so many things. Actually I am totally new in this thing and very much worry after facing issues 2-3 times. And thank u very much for fast reply.
One more ques, I have unlocked bootloader with that "Windroid Universal Android Toolkit". Now in fastboot it shows 'bootloader unlocked,code 3' is that ok? As u say toolkit doesnot work on modern devices.
Click to expand...
Click to collapse
So Moto is a tad different... After you flash recovery, do not reboot with fastboot, instead use the Vol Dn key select Recovery and press Power to start it. When the splash screen comes up, allow changes to system, then I the TWRP main menu select Reboot - Recovery, the device will start TWRP again and it should be "locked" in. From there perform the rooting.

acejavelin said:
So Moto is a tad different... After you flash recovery, do not reboot with fastboot, instead use the Vol Dn key select Recovery and press Power to start it. When the splash screen comes up, allow changes to system, then I the TWRP main menu select Reboot - Recovery, the device will start TWRP again and it should be "locked" in. From there perform the rooting.
Click to expand...
Click to collapse
That mean after typing fastboot flash recovery twrp.img press enter and then i can plug off the usb keeping my device on fastboot then changes to recovery and do the rest?
Btw suppose if i dont want to root it at that time,then what i do? I mean just after flash recovery how to go to home screen without rooting?
And when i want to perform root process later,after installing SuperSU zip if I press power button and vol down then may I go to twrp recovery or ph stock recovery?

Atanu Mukherjee said:
That mean after typing fastboot flash recovery twrp.img press enter and then i can plug off the usb keeping my device on fastboot then changes to recovery and do the rest?
Btw suppose if i dont want to root it at that time,then what i do? I mean just after flash recovery how to go to home screen without rooting?
And when i want to perform root process later,after installing SuperSU zip if I press power button and vol down then may I go to twrp recovery or ph stock recovery?
Click to expand...
Click to collapse
OK... I'm confused, why are you unlocking and installing twrp if your not going root or flash a custom ROM?

acejavelin said:
OK... I'm confused, why are you unlocking and installing twrp if your not going root or flash a custom ROM?
Click to expand...
Click to collapse
I will definately do so. I also want to use CM14.1 but i want to do so step by step. Actually after facing issues 2-3 times i am little bit worry now. That is true. So hesitate to perform both at a single time.

Atanu Mukherjee said:
I will definately do so. I also want to use CM14.1 but i want to do so step by step. Actually after facing issues 2-3 times i am little bit worry now. That is true. So hesitate to perform both at a single time.
Click to expand...
Click to collapse
You don't need to root if your going CM, flash TWRP, backup, and flash CM. You don't need to over complicate it.
If you boot (not flash) TWRP and backup then get a copy to safe place there is little risk of anything going wrong.

acejavelin said:
You don't need to root if your going CM, flash TWRP, backup, and flash CM. You don't need to over complicate it.
If you boot (not flash) TWRP and backup then get a copy to safe place there is little risk of anything going wrong.
Click to expand...
Click to collapse
Ok. But is there any regular chance of going wrong during flash TWRP or flash CM? I backed up all internal important data to external sd card and when I perform these process I just remove that sd from phone.
You pls tell me how to go to home screen after flashing TWRP?
And if I need to root it later then also what to do then? I mean if then I press power and vol minus then will I get TWRP recovery to root it or it will be redirectred to phone custom recovery?

Atanu Mukherjee said:
Ok. But is there any regular chance of going wrong during flash TWRP or flash CM? I backed up all internal important data to external sd card and when I perform these process I just remove that sd from phone.
You pls tell me how to go to home screen after flashing TWRP?
And if I need to root it later then also what to do then? I mean if then I press power and vol minus then will I get TWRP recovery to root it or it will be redirectred to phone custom recovery?
Click to expand...
Click to collapse
There is always a chance of something going wrong, no one can guarantee everything will be fine. We have had people do everything perfectly but something happens and it's bricked... It's rare but does happen.
After you flash TWRP in the bootloader, press Vol Dn until it says Recovery and press power to start it, after several seconds you will get a screen that will ask if it can write to system, select yes, the next screen will be the TWRP home screen.
Once you flash TWRP, your stock recovery is gone, but you access it the same way... Power off, press and hold PWR+Vol Dn and in the bootloader menu select Recovery and press power.

acejavelin said:
There is always a chance of something going wrong, no one can guarantee everything will be fine. We have had people do everything perfectly but something happens and it's bricked... It's rare but does happen.
After you flash TWRP in the bootloader, press Vol Dn until it says Recovery and press power to start it, after several seconds you will get a screen that will ask if it can write to system, select yes, the next screen will be the TWRP home screen.
Once you flash TWRP, your stock recovery is gone, but you access it the same way... Power off, press and hold PWR+Vol Dn and in the bootloader menu select Recovery and press power.
Click to expand...
Click to collapse
Thank you very much for your kind guidance and quick reply. I will perform this may be tomorrow and then inform you. If it is bricked or stucked in any stage/page then is there any instant process to go back to safety?

acejavelin said:
There is always a chance of something going wrong, no one can guarantee everything will be fine. We have had people do everything perfectly but something happens and it's bricked... It's rare but does happen.
After you flash TWRP in the bootloader, press Vol Dn until it says Recovery and press power to start it, after several seconds you will get a screen that will ask if it can write to system, select yes, the next screen will be the TWRP home screen.
Once you flash TWRP, your stock recovery is gone, but you access it the same way... Power off, press and hold PWR+Vol Dn and in the bootloader menu select Recovery and press power.
Click to expand...
Click to collapse
I am listing here only the commands,u just tell me is this ok?
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery twrp.img
fastboot boot twrp.img
Will these commands directly take me to twrp page?
And here I put a pic of the twrp page. If I dont want to root it then what to do? Click reboot option or anything else to do?

Atanu Mukherjee said:
I am listing here only the commands,u just tell me is this ok?
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery twrp.img
fastboot boot twrp.img
Will these commands directly take me to twrp page?
And here I put a pic of the twrp page. If I dont want to root it then what to do? Click reboot option or anything else to do?
Click to expand...
Click to collapse
Your last two are redundant, either flash or boot, you don't have to do both, but each has a purpose... Flash is permanent, boot is transient and will disappear on a reboot.
Boot TWRP first, the first time it will not take you to the main page initially but show you a notification page asking if you want allow it to make changes to the system or keep it read-only, this time only do not allow changes... Then the main screen of TWRP will be displayed and you should do a full backup of all partitions to the SD card.
Flash will just write the recovery partition, it doesn't start anything, you select recovery from the fastboot menu to start it.

acejavelin said:
Your last two are redundant, either flash or boot, you don't have to do both, but each has a purpose... Flash is permanent, boot is transient and will disappear on a reboot.
Boot TWRP first, the first time it will not take you to the main page initially but show you a notification page asking if you want allow it to make changes to the system or keep it read-only, this time only do not allow changes... Then the main screen of TWRP will be displayed and you should do a full backup of all partitions to the SD card.
Flash will just write the recovery partition, it doesn't start anything, you select recovery from the fastboot menu to start it.
Click to expand...
Click to collapse
So after "fastboot boot twrp.img" i have to allow to make changes and have to do a nandroid backup. After that will I get option to "Reboot?"
And later when I went to recovery I will get twrp page instead of stock recovery? 1st I think I should flash cm13 then root then upgrade to 14.1 bcz still a feel little worry to root it on stock rom.

Atanu Mukherjee said:
So after "fastboot boot twrp.img" i have to allow to make changes and have to do a nandroid backup. After that will I get option to "Reboot?"
And later when I went to recovery I will get twrp page instead of stock recovery? 1st I think I should flash cm13 then root then upgrade to 14.1 bcz still a feel little worry to root it on stock rom.
Click to expand...
Click to collapse
No, almost every part of what your saying is wrong...
Boot twrp and do not allow changes first time and backup. This will give a clean backup to restore from if things go badly.
After this is complete, in TWRP go to Reboot menu and select Bootloader, flash TWRP, do not reboot but use the bootloader menu to start TWRP. This time allow it to make changes to system. At the main menu if twrp go to Reboot - Recovery the device will restart and TWRP will load automatically, this step will lock in twrp so the stock OS doesn't replace it.
You only need to root stock rom, you don't need to root CM roms as they are already rooted (there are a few roms that are not pre-rooted but they are rare and none of the ones your talking about). As far as CM 13 vs 14.1 I can't really help you but from I've read both are stable enough for a daily driver device.

acejavelin said:
No, almost every part of what your saying is wrong...
Boot twrp and do not allow changes first time and backup. This will give a clean backup to restore from if things go badly.
After this is complete, in TWRP go to Reboot menu and select Bootloader, flash TWRP, do not reboot but use the bootloader menu to start TWRP. This time allow it to make changes to system. At the main menu if twrp go to Reboot - Recovery the device will restart and TWRP will load automatically, this step will lock in twrp so the stock OS doesn't replace it.
You only need to root stock rom, you don't need to root CM roms as they are already rooted (there are a few roms that are not pre-rooted but they are rare and none of the ones your talking about). As far as CM 13 vs 14.1 I can't really help you but from I've read both are stable enough for a daily driver device.
Click to expand...
Click to collapse
After typing 'fastboot flash recovery twrp.img' i switch to recovery and select it. But it shows recovery failed,bla bla in red colour. I tried 3 times but same result. What to do? now again when I go to the recovery,i see still it is the stock recovery.

Help please can't see my phone in adb

I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?

forgot something
looks like i skipped this part . Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.Is there anything i can do?

videodave1 said:
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
Click to expand...
Click to collapse
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.

WOW thank you so much'
Arju said:
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
Click to expand...
Click to collapse
I was able to flash twrp i'll try the rest when i get home from work

sideloading stock img
videodave1 said:
I was able to flash twrp i'll try the rest when i get home from work
Click to expand...
Click to collapse
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?

zip file
videodave1 said:
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
Click to expand...
Click to collapse
When i try i get invalid file format. This is using a zip i got from Essential.

Stuck twrp says no os installed . But i did learn how to push files.

just trying to get back to stock now 

videodave1 said:
just trying to get back to stock now 
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681

thanks been there tried the Oreo beta that is what i was on when i started and tried the 1st build before the betas i get an error on both i'll try to download them on another pc my phone does show up when i type fastboot devices now just need an os now .

Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.

thanks everyone.

videodave1 said:
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
Click to expand...
Click to collapse
No problem. Thank you very much for the donation, that was really kind of you. Hey I'm sure you'll get the hang of it before android P drops. you did figure out what went wrong all by yourself so get a hold of the right boot.img and the rest is exactly as how you did it in the first place but flash the boot.img before magisk. Let me know if you want to give it a dive again.

I'm on 8.1 boot loader unlocked and ready to try to root again .Thanks for the help

This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much

avocom said:
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
Click to expand...
Click to collapse
Even though your phone does not show up its there wipe everything.Fallow what Arju said in his post.I got back to stock then took the 8.1 update i'm not rooted but my bootloader is still unlocked.Oh make sure you unlock critical

videodave1 said:
Fallow what Arju said in his post.
Click to expand...
Click to collapse
Thanks for coming back to me. I really appreciate it.
Arju said:
Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too.
Click to expand...
Click to collapse
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks

avocom said:
Thanks for coming back to me. I really appreciate it.
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
Click to expand...
Click to collapse
are you able to get to the bootloader menu? where it says start on the top.

Arju said:
are you able to get to the bootloader menu? where it says start on the top.
Click to expand...
Click to collapse
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks

avocom said:
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
Click to expand...
Click to collapse
What you need to understand is that twrp will not stick after you flash it. This device does not have a recovery partition and that's why you replace the boot partition with twrp and while you're in twrp you need to flash the boot.img back and whatever mods on top of that such as kernel etc.. If you flash a rom then it will replace the twrp with the boot.img found in the rom zip.
So now we need the computer to recognize you device. Could you unplug the cable and change the usb port on you computer. connect your phone while you're in the bootloader menu where it says start on the top.
The use use fastboot command: fastboot devices
See if the computer recognizes you device.

Nokia 5 unable to install Recovery

So I gave my IMEI, serial number and $5 to someone on the internet, and in return I got an email attachment to flash to my phone. So I did, and it unlocked the bootloader. Strangely enough, now I'm getting a stupid yellow message that my device is unlocked and can't be trusted, and it's a bit of a roundabout way to get into bootloader or recovery. One ONLY works with buttons, the other ONLY with adb.
Ok, never mind, so I tried installing both the 3.1.1. and 3.2.1 of TWRP custom recovery, but I am unable to boot into it to make it stick. On top of that, my phone now says "encrypted"? WTF?
Clearly this latest incarnation of Nokia is a bunch of asswipes, offering us Sophie's choice instead of just unlocking the damn things from the start, so there's no point in asking them for help, but I'd expect members here would be able to help?
Any ideas how to proceed? Is there a factory ROM somewhere? This is 7.1.2. by the way, I'm not interested in updating. Come to think of it, I hate this so-called "progress" with convoluted "security" and whatnot. Just give me the damn phone and go away, Google+Nokia. Stick your "features" up ya clacker.

1. Okk first you jeed to go this link and download official recovery for nokia 5 running android 8.1 oreo
https://drive.google.com/file/d/1Cl1...w?usp=drivesdk
2. Rename it to twrp and give the command to flash the recovery.
3. After give command fastboot flash recovery twrp.img. Give the command fastboot boot twrp.img
And boooom you enter in official twrp

Jitender Baloda said:
1. Okk first you jeed to go this link and download official recovery for nokia 5 running android 8.1 oreo
https://drive.google.com/file/d/1Cl1...w?usp=drivesdk
2. Rename it to twrp and give the command to flash the recovery.
3. After give command fastboot flash recovery twrp.img. Give the command fastboot boot twrp.img
And boooom you enter in official twrp
Click to expand...
Click to collapse
Link broken. File doesn't exist

Try this
https://drive.google.com/file/d/1Cl1yV7tV_VsIC3XIWlCIJXmFfdDZGUbG/view?usp=drivesdk

Err... no, not quite.
1. Your link is (was) dead, but in any case I'd be wary of installing something stashed in a private Google drive folder... Thanks, but no thanks.
2. I have several versions of TWRP, that's not a problem.
3. I know the correct commands (yours are not), that's not a problem.
And boom - no, you don't end up in TWRP. You end up in system, because it overwrites the TWRP automatically UNLESS you reboot to it immediately after flashing, and THIS is the problem.
It turns out that Nokia needs to be plugged into CHARGER, not the PC, then holding Vol+ and Power button combination will do it. It took me more than a dozen tries, but it worked in the end.

Hi, I had the same problem. I've unlocked bootloader and I successfully installed TWRP and I can go to recovery but the problem is I can't boot the system as it stucks on download mode. Can you help?

Press volume up+volume down+power button at the same time for 7-8 second.

Stuck on "Fastboot Mode" screen

I stupidly tried using franco's app to flash cleanKernel on my rooted phone on 9.0.11, it failed of course and now can't boot my phone. I'm able to fastboot boot twrp.img but I'm not sure what is needed next. I've downloaded the full 9.0.11 ota file thinking something in it (or all of it) needs to be flashed from twrp. Afraid to do anything at this point for fear of losing data. Any tips are appreciated.
I've downloaded mauronofrio's rom-stock-fastboot utility but see he says it will clear data. I'm assuming all the .bat files will do this. Any way to avoid clearing internal storage?

soundneedle said:
From bootloader screen, using fastboot boot twrp.zip results in OP going to "Fastboot Mode" screen...and staying there. The zip is pushed to the phone but won't boot into TWRP. This started after I stupidly tried using franco's app to flash cleanKernel on my rooted phone. It failed of course and now can't boot my phone. My phone recently updated itself to 9.0.11, fyi.
Any ideas on how to fix this boot issue? Is it just a matter of flashing something from the full ota 9.0.11 file---some img file or something?
Click to expand...
Click to collapse
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?

I was able to recover...thank god. Just used mauronofrio's flash utility. Removed the "-w" flag from the flash-all.bat file and all is good.

Stuck on Fastboot Mode screen once I run fastboot boot twrp.img
bp328i said:
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
Click to expand...
Click to collapse
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s

Is the twrp.img even being flashed
SimmoMaz said:
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Click to expand...
Click to collapse
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing

SimmoMaz said:
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
Click to expand...
Click to collapse
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...

TWRP isn't there
lilbrat said:
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
Click to expand...
Click to collapse
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S

SimmoMaz said:
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
Click to expand...
Click to collapse
Ok.. are you using the latest TWRP? If you want in the guide section you can you the msmdow like ad tools to reset you phone to stock, and retry again..

THIS. I have the exact same issue. In short, I have the T-mobile version, and was able to unlock successfully. I am using twrp-3.2.3-0, and I have the img and zip in the same folder, same way Techibee does on Youtube. I then type "fastboot boot twrp-3.2.3-0-fajita.img", I get the "OKAY... OKAY... Booting... Finished" response in console. Then, the Fastboot screen appears and never leaves. I have done this 3 times now. I kept tweaking the process, but I'm nervous to keep debugging.

Stuck (
Hello guys,
I wanted to overclock my 6t global. so i had unlocked the bootloader then flashed the twrp. In twrp i firstly reset the os to factory setting and then i flash magisk and smurf kernel. but when i reboot after this my phone is stuck on the phone unlocked message.
ive tried flashing magisk only and then boot, it works. but when i flash smurf kernel i get stuck . why this happening plz help (

Stuck in Bootloader with Magisk, Boots Correctly Without Magisk

Phone: A6010
OOS: 9.0.17
TWRP: twrp-3.2.3-x_blu_spark_v9.91_op6
Magisk: Magisk-v19.3
PC OS: Manjaro Linux with Android SDK tools
Hello folks. This issue started happening last night. I rebooted the phone (hold down Power button, hit Restart), but when it rebooted, it stayed on the "bootloader unlocked" warning screen for a long time, and would then enter the bootloader. This has never happened before, even after the latest OTA update to 9.0.17 (after which the phone was successfully re-rooted following these instructions.)
If "Power Off" was selected, the screen would turn off without the corresponding buzz from the internal vibrator to show that the phone was powered down. Instead, it would reboot into Fastboot mode and then into the bootloader.
I've tried the following steps to troubleshoot:
1. fastboot boot twrp-3.2.3-x_blu_spark_v9.91_op6.img
adb sideload twrp-3.2.3-x_blu_spark_v9.91_op6.zip and reboot into recovery
adb sideload Magisk-v19.3.zip
Result: stuck at "bootloader unlocked" warning screen & enters bootloader
2. Tried the same steps in #1 but with Magisk v19.4 and 20.0. Same result.
3. Same steps in #1 but flashed Magisk-uninstaller-20191011.zip as the final step. Result, phone boots up correctly but without root.
4. Rebooted into bootloader
fastboot boot twrp-3.3.1-8-fajita.img
copied the same file to phone & Advanced -> Install Recovery Ramdisk -> twrp-3.3.1-8-fajita.img
reboot into Recovery & adb sideload Magisk-v19.4.zip
Same result as before, stuck at warning screen and then into bootloader.
5. Re-did #3 i.e. back to twrp-3.2.3-x_blu_spark_v9.91_op6 and uninstalled Magisk. Phone once again boots up correctly but without root. This is where I am now.
The phone can successfully boot to Recovery from Bootloader. I also tried to power down the phone from Recovery mode, which it did correctly (with corresponding vibrator buzz), but when powered back on would go back to "warning screen"/bootloader issue when Magisk was still installed.
Without Magisk, the phone powers down correctly, boots up correctly, and reboots correctly albeit all without root.
At this point, i've no idea what's going on or how to proceed further. There are some threads discussing MsmDownloadTool but the latest version available is for 9.0.16 in this thread, which i think can't be used for 9.0.17.
Suggestions on how to proceed would be most appreciated. Thank you in advance for your time.

SkyLukewalker said:
Phone: A6010
OOS: 9.0.17
TWRP: twrp-3.2.3-x_blu_spark_v9.91_op6
Magisk: Magisk-v19.3
PC OS: Manjaro Linux with Android SDK tools
Hello folks. This issue started happening last night. I rebooted the phone (hold down Power button, hit Restart), but when it rebooted, it stayed on the "bootloader unlocked" warning screen for a long time, and would then enter the bootloader. This has never happened before, even after the latest OTA update to 9.0.17 (after which the phone was successfully re-rooted following these instructions.)
If "Power Off" was selected, the screen would turn off without the corresponding buzz from the internal vibrator to show that the phone was powered down. Instead, it would reboot into Fastboot mode and then into the bootloader.
I've tried the following steps to troubleshoot:
1. fastboot boot twrp-3.2.3-x_blu_spark_v9.91_op6.img
adb sideload twrp-3.2.3-x_blu_spark_v9.91_op6.zip and reboot into recovery
adb sideload Magisk-v19.3.zip
Result: stuck at "bootloader unlocked" warning screen & enters bootloader
2. Tried the same steps in #1 but with Magisk v19.4 and 20.0. Same result.
3. Same steps in #1 but flashed Magisk-uninstaller-20191011.zip as the final step. Result, phone boots up correctly but without root.
4. Rebooted into bootloader
fastboot boot twrp-3.3.1-8-fajita.img
copied the same file to phone & Advanced -> Install Recovery Ramdisk -> twrp-3.3.1-8-fajita.img
reboot into Recovery & adb sideload Magisk-v19.4.zip
Same result as before, stuck at warning screen and then into bootloader.
5. Re-did #3 i.e. back to twrp-3.2.3-x_blu_spark_v9.91_op6 and uninstalled Magisk. Phone once again boots up correctly but without root. This is where I am now.
The phone can successfully boot to Recovery from Bootloader. I also tried to power down the phone from Recovery mode, which it did correctly (with corresponding vibrator buzz), but when powered back on would go back to "warning screen"/bootloader issue when Magisk was still installed.
Without Magisk, the phone powers down correctly, boots up correctly, and reboots correctly albeit all without root.
At this point, i've no idea what's going on or how to proceed further. There are some threads discussing MsmDownloadTool but the latest version available is for 9.0.16 in this thread, which i think can't be used for 9.0.17.
Suggestions on how to proceed would be most appreciated. Thank you in advance for your time.
Click to expand...
Click to collapse
MSM is your way to go. It will downgrade your phone to 9.0.17 and lock your Bootloader. After that you can unlock it and take the OTA Again. You will lose all your Data. Another thing you can try is to Format Data in TWRP. That will also cause you to loose all your Data but you might be able to boot up with Root.

Mannan Qamar said:
MSM is your way to go. It will downgrade your phone to 9.0.17 and lock your Bootloader. After that you can unlock it and take the OTA Again. You will lose all your Data. Another thing you can try is to Format Data in TWRP. That will also cause you to loose all your Data but you might be able to boot up with Root.
Click to expand...
Click to collapse
Thank you for the reply.
At this point, I'm kinda resigned to losing all data, so i did a backup this morning. However, I need my phone to be functional over this weekend, and will do as you have suggested on Monday after another backup.
Will start with the Format Data in TWRP method first, since i'm running Linux and have to setup a VM with USB passthrough to run Win7 and Msm.
Just to confirm, since i'm already running 9.0.17, is it okay simply to use MsmDownloadTool v4.0.59 if it comes to that? Thanks in advance.
On a sidenote, since data loss is inevitable, once it's confirmed that the phone boots up correctly with root and stock OOS, it may just be worth moving to LOS16 thereafter.

Mannan Qamar said:
MSM is your way to go. It will downgrade your phone to 9.0.17 and lock your Bootloader. After that you can unlock it and take the OTA Again. You will lose all your Data. Another thing you can try is to Format Data in TWRP. That will also cause you to loose all your Data but you might be able to boot up with Root.
Click to expand...
Click to collapse
I had time today, and tried Format Data. Didn't work. Installing Magisk landed the phone in the same error screen.
So the Win7 VM was fired up and the instructions for Msm were followed. The phone is recognized and the drivers were successfully installed, showing up as Qualcomm HS-USB QDLoader 9008 (COM3)
However, when MsmDownloadTool V4.0.59 -- 9.0.16 was launched and Start was pressed, the operation times out with the message "Sahara Communication Failed. Please try again after power off phone."
This is despite powering off using the normal method within OOS itself, or powering off from within TWRP.
Not sure how to proceed. Please help?

SkyLukewalker said:
I had time today, and tried Format Data. Didn't work. Installing Magisk landed the phone in the same error screen.
So the Win7 VM was fired up and the instructions for Msm were followed. The phone is recognized and the drivers were successfully installed, showing up as Qualcomm HS-USB QDLoader 9008 (COM3)
However, when MsmDownloadTool V4.0.59 -- 9.0.16 was launched and Start was pressed, the operation times out with the message "Sahara Communication Failed. Please try again after power off phone."
This is despite powering off using the normal method within OOS itself, or powering off from within TWRP.
Not sure how to proceed. Please help?
Click to expand...
Click to collapse
Could be an issue with the VM. I'd also try to change USB Port or try another Cable.

SkyLukewalker said:
Phone: A6010
OOS: 9.0.17
TWRP: twrp-3.2.3-x_blu_spark_v9.91_op6
Magisk: Magisk-v19.3
PC OS: Manjaro Linux with Android SDK tools
Hello folks. This issue started happening last night. I rebooted the phone (hold down Power button, hit Restart), but when it rebooted, it stayed on the "bootloader unlocked" warning screen for a long time, and would then enter the bootloader. This has never happened before, even after the latest OTA update to 9.0.17 (after which the phone was successfully re-rooted following these instructions.)
If "Power Off" was selected, the screen would turn off without the corresponding buzz from the internal vibrator to show that the phone was powered down. Instead, it would reboot into Fastboot mode and then into the bootloader.
I've tried the following steps to troubleshoot:
1. fastboot boot twrp-3.2.3-x_blu_spark_v9.91_op6.img
adb sideload twrp-3.2.3-x_blu_spark_v9.91_op6.zip and reboot into recovery
adb sideload Magisk-v19.3.zip
Result: stuck at "bootloader unlocked" warning screen & enters bootloader
2. Tried the same steps in #1 but with Magisk v19.4 and 20.0. Same result.
3. Same steps in #1 but flashed Magisk-uninstaller-20191011.zip as the final step. Result, phone boots up correctly but without root.
4. Rebooted into bootloader
fastboot boot twrp-3.3.1-8-fajita.img
copied the same file to phone & Advanced -> Install Recovery Ramdisk -> twrp-3.3.1-8-fajita.img
reboot into Recovery & adb sideload Magisk-v19.4.zip
Same result as before, stuck at warning screen and then into bootloader.
5. Re-did #3 i.e. back to twrp-3.2.3-x_blu_spark_v9.91_op6 and uninstalled Magisk. Phone once again boots up correctly but without root. This is where I am now.
The phone can successfully boot to Recovery from Bootloader. I also tried to power down the phone from Recovery mode, which it did correctly (with corresponding vibrator buzz), but when powered back on would go back to "warning screen"/bootloader issue when Magisk was still installed.
Without Magisk, the phone powers down correctly, boots up correctly, and reboots correctly albeit all without root.
At this point, i've no idea what's going on or how to proceed further. There are some threads discussing MsmDownloadTool but the latest version available is for 9.0.16 in this thread, which i think can't be used for 9.0.17.
Suggestions on how to proceed would be most appreciated. Thank you in advance for your time.
Click to expand...
Click to collapse
Why are you using TWRP from OP6 so old too? Here for OP6T there is newer https://github.com/engstk/android_device_oneplus_fajita/releases/tag/v9.101

elSkelet said:
Why are you using TWRP from OP6 so old too? Here for OP6T there is newer https://github.com/engstk/android_device_oneplus_fajita/releases/tag/v9.101
Click to expand...
Click to collapse
I have updated to the latest TWRP as you have mentioned. The issue still persists when Magisk is installed. Once again, Magisk had to be uninstalled before the phone would boot up properly.
Mannan Qamar said:
Could be an issue with the VM. I'd also try to change USB Port or try another Cable.
Click to expand...
Click to collapse
I tried with 2 different USB ports today. Tomorrow i will reboot the VM, remove the driver, let it re-discover and install the driver from MS (i installed a pre-downloaded driver today) and try again. The cable is the original one that came with the phone, and another one will need to be purchased if the efforts fail. Hopefully it is just the VM acting funny.

SkyLukewalker said:
I have updated to the latest TWRP as you have mentioned. The issue still persists when Magisk is installed. Once again, Magisk had to be uninstalled before the phone would boot up properly.
I tried with 2 different USB ports today. Tomorrow i will reboot the VM, remove the driver, let it re-discover and install the driver from MS (i installed a pre-downloaded driver today) and try again. The cable is the original one that came with the phone, and another one will need to be purchased if the efforts fail. Hopefully it is just the VM acting funny.
Click to expand...
Click to collapse
No that won't be necessary. As the drivers can't be downloaded from MS. Is your phone able to reboot to Recovery? i.e. do you have TWRP Installed? If so, then flash Latest OOS ZIP and TWRP Installer, Reboot and repeat the two above steps. After that Format Data and Reboot. This should allow you to boot up. After that, proceed to root as you normally would. Also, I'd look into getting a Windows Laptop if it doesn't work. As MSM is known to have issues with VM.

Mannan Qamar said:
No that won't be necessary. As the drivers can't be downloaded from MS. Is your phone able to reboot to Recovery? i.e. do you have TWRP Installed? If so, then flash Latest OOS ZIP and TWRP Installer, Reboot and repeat the two above steps. After that Format Data and Reboot. This should allow you to boot up. After that, proceed to root as you normally would. Also, I'd look into getting a Windows Laptop if it doesn't work. As MSM is known to have issues with VM.
Click to expand...
Click to collapse
Yes, i have twrp-3.3.1-x_blu_spark_v9.101_op6t currently installed without Magisk. Will do as you have said tomorrow, since i have also downloaded the full 9.0.17 OOS zip file.
Since budget is very tight at the moment, i will look into borrowing a Windows PC/laptop for awhile to use Msm if the other methods don't work.

SkyLukewalker said:
Yes, i have twrp-3.3.1-x_blu_spark_v9.101_op6t currently installed without Magisk. Will do as you have said tomorrow, since i have also downloaded the full 9.0.17 OOS zip file.
Since budget is very tight at the moment, i will look into borrowing a Windows PC/laptop for awhile to use Msm if the other methods don't work.
Click to expand...
Click to collapse
Wait, wouldn't flashing back to 9.0.17 lock your bootloader? Then you can't enable OEM unlocking, which means you can't unlock the bootloader. You would need to flash MSM 9.0.11 to enable OEM unlocking, then unlock the bootloader before proceeding further. I'm no expert, just thought I'd mention it. Best of luck!!
Sent from my ONEPLUS A6013 using Tapatalk

xRogerxC said:
Wait, wouldn't flashing back to 9.0.17 lock your bootloader? Then you can't enable OEM unlocking, which means you can't unlock the bootloader. You would need to flash MSM 9.0.11 to enable OEM unlocking, then unlock the bootloader before proceeding further. I'm no expert, just thought I'd mention it. Best of luck!!
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Didn't seem to be an issue, worked correctly and the bootloader remained unlocked.
Mannan Qamar said:
... Is your phone able to reboot to Recovery? i.e. do you have TWRP Installed? If so, then flash Latest OOS ZIP and TWRP Installer, Reboot and repeat the two above steps. After that Format Data and Reboot. This should allow you to boot up. After that, proceed to root as you normally would. ...
Click to expand...
Click to collapse
This worked, and now the phone is booted up into the system WITH Magisk 19.4 installed. Thank you very much! I didn't have to use Msm.
The steps for anyone else facing the same issue that i did:
Reboot into Recovery. This can be done via long-press power button in System and pressing Recovery if TWRP is already installed, or adb reboot bootloader to reboot into the bootloader, and fastboot boot recoveryImage_Filename.img (in my case, it was twrp-3.3.1-x_blu_spark_v9.101_op6t.img)
Enter password/pattern to unlock
Advanced -> ADB Sideload -> adb sideload OOSimage_Filename.zip (in my case, it was OnePlus6TOxygen_34_OTA_024_all_1909112343_d5b1905.zip)
Back
ADB Sideload -> adb sideload TWRPzipFile_Filename.zip (in my case, it was twrp-3.3.1-x_blu_spark_v9.101_op6t.zip)
Back -> Back Arrow
Reboot -> Recovery, and wait for phone to reboot into Recovery
Enter password/pattern to unlock
Advanced -> ADB Sideload -> adb sideload OOSimage_Filename.zip
Back
ADB Sideload -> adb sideload TWRPzipFile_Filename.zip
Back -> Back Arrow
Wipe -> Format Data -> type "yes" and click the blue tick "Enter" key on keyboard.
Back Arrow to Main Screen -> Reboot -> Recovery, and wait for phone to reboot into Recovery
Enter password/pattern to unlock
Advanced -> ADB Sideload -> adb sideload MagiskInstaller.zip (in my case, it was Magisk-v19.4.zip)
Back -> Back Arrow
Reboot -> Power Off to completely power down.
Long-press power button to boot the phone. The issue of being stuck at the bootloader unlocked warning screen was gone. The phone booted into System with Magisk Root installed and working.
Later today, I will install LOS16 with Magisk and report back on how that went. Once again, much gratitude and appreciation to Mannan Qamar for the solution!

SkyLukewalker said:
Didn't seem to be an issue, worked correctly and the bootloader remained unlocked.
This worked, and now the phone is booted up into the system WITH Magisk 19.4 installed. Thank you very much! I didn't have to use Msm.
The steps for anyone else facing the same issue that i did:
Reboot into Recovery. This can be done via long-press power button in System and pressing Recovery if TWRP is already installed, or adb reboot bootloader to reboot into the bootloader, and fastboot boot recoveryImage_Filename.img (in my case, it was twrp-3.3.1-x_blu_spark_v9.101_op6t.img)
Enter password/pattern to unlock
Advanced -> ADB Sideload -> adb sideload OOSimage_Filename.zip (in my case, it was OnePlus6TOxygen_34_OTA_024_all_1909112343_d5b1905.zip)
Back
ADB Sideload -> adb sideload TWRPzipFile_Filename.zip (in my case, it was twrp-3.3.1-x_blu_spark_v9.101_op6t.zip)
Back -> Back Arrow
Reboot -> Recovery, and wait for phone to reboot into Recovery
Enter password/pattern to unlock
Advanced -> ADB Sideload -> adb sideload OOSimage_Filename.zip
Back
ADB Sideload -> adb sideload TWRPzipFile_Filename.zip
Back -> Back Arrow
Wipe -> Format Data -> type "yes" and click the blue tick "Enter" key on keyboard.
Back Arrow to Main Screen -> Reboot -> Recovery, and wait for phone to reboot into Recovery
Enter password/pattern to unlock
Advanced -> ADB Sideload -> adb sideload MagiskInstaller.zip (in my case, it was Magisk-v19.4.zip)
Back -> Back Arrow
Reboot -> Power Off to completely power down.
Long-press power button to boot the phone. The issue of being stuck at the bootloader unlocked warning screen was gone. The phone booted into System with Magisk Root installed and working.
Later today, I will install LOS16 with Magisk and report back on how that went. Once again, much gratitude and appreciation to Mannan Qamar for the solution!
Click to expand...
Click to collapse
Glad to know it worked. MSM should be a last resort but most people use it as a first option to Nuke their phone. And if you want help on installing ROMs, don't hesitate to ask.

Mannan Qamar said:
Glad to know it worked. MSM should be a last resort but most people use it as a first option to Nuke their phone. And if you want help on installing ROMs, don't hesitate to ask.
Click to expand...
Click to collapse
LOS16 was installed successfully with Magisk and i spent nearly 7 hours setting up the phone since opbackup could not be seen by OnePlus Switch, and i had to do everything manually.
Suddenly the screen started flashing all sorts of colours. I rebooted, and the same problem came back, i.e. stuck at the warning screen.
So, i used the instructions you provided and got OOS 9.0.17 booted back up with Magisk 19.4. However, when i try to connect to the phone via USB, even with debugging enabled, the internal storage cannot be read. Says "enable MTP." This is also happening in TWRP even after disabling and re-enabling MTP.
How do i get the phone to see the internal storage again? Please help.

SkyLukewalker said:
LOS16 was installed successfully with Magisk and i spent nearly 7 hours setting up the phone since opbackup could not be seen by OnePlus Switch, and i had to do everything manually.
Suddenly the screen started flashing all sorts of colours. I rebooted, and the same problem came back, i.e. stuck at the warning screen.
So, i used the instructions you provided and got OOS 9.0.17 booted back up with Magisk 19.4. However, when i try to connect to the phone via USB, even with debugging enabled, the internal storage cannot be read. Says "enable MTP." This is also happening in TWRP even after disabling and re-enabling MTP.
How do i get the phone to see the internal storage again? Please help.
Click to expand...
Click to collapse
Format Data in TWRP. For some weird reason, Internal Storage gets messed up after flashing OOS. And the screen issue might have been a Magisk Module or some other error. Maybe an issue with the ROM. I'd certainly try another ROM

Mannan Qamar said:
Format Data in TWRP. For some weird reason, Internal Storage gets messed up after flashing OOS. And the screen issue might have been a Magisk Module or some other error. Maybe an issue with the ROM. I'd certainly try another ROM
Click to expand...
Click to collapse
I'm going to do the whole process all over again, just to be sure, and try to copy the necessary files over to internal storage before flashing Magisk. Will update once the process gets there. I'm going back to rooted OOS for now because nearly 7 hours of setup is not fun in the least for a daily driver phone.

Mannan Qamar said:
Format Data in TWRP. For some weird reason, Internal Storage gets messed up after flashing OOS. And the screen issue might have been a Magisk Module or some other error. Maybe an issue with the ROM. I'd certainly try another ROM
Click to expand...
Click to collapse
I managed to copy over the files in TWRP, with internal storage showing up as Internal Storage (A6013). However, once booted into system, it now shows up as Internal Shared Storage (A6010) with nothing in it. Using the phone's File Manager, the copied files do not show up either.
But going back to TWRP, Internal Storage shows up correctly with the copied files. Did Format Data in TWRP and rebooted into system. Still the same issue. Please help?
Edit: tried doing the same method all over again. This time, the MTP error shows up in TWRP also. Can't see anything anymore.

SkyLukewalker said:
I managed to copy over the files in TWRP, with internal storage showing up as Internal Storage (A6013). However, once booted into system, it now shows up as Internal Shared Storage (A6010) with nothing in it. Using the phone's File Manager, the copied files do not show up either.
But going back to TWRP, Internal Storage shows up correctly with the copied files. Did Format Data in TWRP and rebooted into system. Still the same issue. Please help?
Edit: tried doing the same method all over again. This time, the MTP error shows up in TWRP also. Can't see anything anymore.
Click to expand...
Click to collapse
Well. In such a case MSM is the way to go. I'd recommend using a Windows Laptop. Although as a last resort if try the Fastboot ROMs before MSM. Search OP6T Fastboot ROMs

Mannan Qamar said:
Well. In such a case MSM is the way to go. I'd recommend using a Windows Laptop. Although as a last resort if try the Fastboot ROMs before MSM. Search OP6T Fastboot ROMs
Click to expand...
Click to collapse
I found this thread and downloaded the appropriate Fastboot ROM (9.0.17). Just a couple of questions:
1. do i need to do the persist partition step?
2. where in TWRP do i have to go to do adb push and adb shell?

SkyLukewalker said:
I found this thread and downloaded the appropriate Fastboot ROM (9.0.17). Just a couple of questions:
1. do i need to do the persist partition step?
2. where in TWRP do i have to go to do adb push and adb shell?
Click to expand...
Click to collapse
Those things are not necessary. Just unzip and use the Flasher in the archive. The default one should be sufficient. The others aren't needed.

Mannan Qamar said:
Those things are not necessary. Just unzip and use the Flasher in the archive. The default one should be sufficient. The others aren't needed.
Click to expand...
Click to collapse
Hopefully it works from the VM. Otherwise i will have to do it manually from Linux terminal. Thank you for the advice. Will report tomorrow when the process is done.