Database Users

[OP8T][OOS TMO KB09CB] Unbrick tool to restore your device to OxygenOS

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, OP8Pro, OP Nord and regular OP8T here is the EDL package (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus 8T bought from T-Mobile USA (also known as OnePlus 8T + 5G).
You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
You can download the following versions:
KB09CB (T-Mobile firmware):
ANDROID 11:
OOS 11.1.0.2
OOS 11.0.1.3
OOS 11.0.4.6
OOS 11.0.5.7
OOS 11.0.6.8
OOS 11.0.7.9
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
Windows 7 users may use MsmDownloadTool V4.0_Win7.exe instead, but it hasn't been tested.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button (this is done so that device will be "captured" automatically by tool instead of going back to normal boot after 10 seconds)
Power your device off.
Let it cool down for one minute.
Hold both volumes in to get in Qualcomm EDL mode and the screen will stay black. While holding, plug in the USB cable from your phone to your computer. Let volumes go alter plugged in.
Wait some time (should not be longer than ~400 seconds).
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected when I click on "Enum" button
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61, all credits to @Shadow12347 for finding it out.
Credits:
@LLStarks for helping in getting 11.1.0.2, 11.0.4.6, 11.0.5.7 and 11.0.7.9 versions and performing 11.1.0.2 flash on his own device (see screenshot)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OnePlus for the device and OS

Do we need to have sim unlock? I'm dying to unlock this thing lol

freddienuxx said:
Do we need to have sim unlock? I'm dying to unlock this thing lol
Click to expand...
Click to collapse
You don't need to be SIM unlocked to use that tool, also as a reminder it's just to flash back T-Mobile stock.

Some_Random_Username said:
You don't need to be SIM unlocked to use that tool, also as a reminder it's just to flash back T-Mobile stock.
Click to expand...
Click to collapse
If we sim unlock. Could we use the other guide for a global conversation

cammykool said:
If we sim unlock. Could we use the other guide for a global conversation
Click to expand...
Click to collapse
No.

Some_Random_Username said:
No.
Click to expand...
Click to collapse
I thought previous versions allowed cross flashing therefore unlocking the sim on T-Mobile or at least allowing bootloader unlocking without sim unlock.
Sent from my OnePlus KB2007 using XDA Labs

jwarrior319 said:
I thought previous versions allowed cross flashing therefore unlocking the sim on T-Mobile or at least allowing bootloader unlocking without sim unlock.
Sent from my OnePlus KB2007 using XDA Labs
Click to expand...
Click to collapse
I assumed they meant "Will we be able to use unlocked units MSM tools if we SIM unlock the T-Mobile unit".

Some_Random_Username said:
I assumed they meant "Will we be able to use unlocked units MSM tools if we SIM unlock the T-Mobile unit".
Click to expand...
Click to collapse
So is there a way to crossflash without unlocking the bootloader first? My carrier brick walled me on sim unlock which is required for bootloader unlock (T-Mobile). If mobbdeep would open up again it would be ideal but probably be a few months.
Sent from my OnePlus KB2007 using XDA Labs

Now waiting for conversation, from T-Mobile to International/regular OS, hope it happens fast and without the need of a unlocked Bootloader since OP site is drunk

jwarrior319 said:
So is there a way to crossflash without unlocking the bootloader first? My carrier brick walled me on sim unlock which is required for bootloader unlock (T-Mobile). If mobbdeep would open up again it would be ideal but probably be a few months.
Click to expand...
Click to collapse
I believe a conversion without having to unlock bootloader first is unlikely. And if that happens I don't think it will be by EDL.

jwarrior319 said:
So is there a way to crossflash without unlocking the bootloader first? My carrier brick walled me on sim unlock which is required for bootloader unlock (T-Mobile). If mobbdeep would open up again it would be ideal but probably be a few months.
Click to expand...
Click to collapse
Hold up I'll DM you what I told another user on how I got mine unlocked. I forgot to mention I have a military account, but I don't think they noticed that the first time.

i keep getting "automatic detection of ddr failed"
Sent from my OnePlus KB2007 using XDA Labs

Some_Random_Username said:
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, OP8Pro, OP Nord and regular OP8T here is the EDL package (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus 8T bought from T-Mobile USA (also known as OnePlus 8T + 5G).
You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
You can download the following versions:
KB09CB (T-Mobile firmware):
ANDROID 11:
OOS 11.0
Instructions:
Launch MsmDownloadTool V4.0.exe.
Windows 7 users may use MsmDownloadTool V4.0_Win7.exe instead, but it hasn't been tested.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button (this is done so that device will be "captured" automatically by tool instead of going back to normal boot after 10 seconds)
Power your device off.
Let it cool down for one minute.
Hold both volumes in to get in Qualcomm EDL mode and the screen will stay black. While holding, plug in the USB cable from your phone to your computer. Let volumes go alter plugged in.
Wait some time (should not be longer than ~400 seconds).
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected when I click on "Enum" button
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61, all credits to @Shadow12347 for finding it out.
Credits:
@LLStarks for helping in getting 11.0 version and performing flash on his own device (see screenshot)
OnePlus for the device and OS
Click to expand...
Click to collapse
WHOO! That was quick! Thanks for this! Downloading now! :good:

Is there instruction on converting T-Mob to global international variant?

zeusofyork said:
Hold up I'll DM you what I told another user on how I got mine unlocked. I forgot to mention I have a military account, but I don't think they noticed that the first time.
Click to expand...
Click to collapse
Any chance you would send me the infor as well? It would be much appreciated.

Sheradrax said:
Any chance you would send me the infor as well? It would be much appreciated.
Click to expand...
Click to collapse
I bought mine 8T today and just asked on twitter and they did it no questions asked. Even while financed.

I got my sim unlocked ,but do I need bootloader unlock before I can convert to international?

kenbrownstone said:
I got my sim unlocked ,but do I need bootloader unlock before I can convert to international?
Click to expand...
Click to collapse
Currently, yes.
https://forum.xda-developers.com/oneplus-8t/how-to/guide-tmo-variant-conversion-t4188491/page17
Sent from my OnePlus 8T using XDA Labs

TechOut said:
I bought mine 8T today and just asked on twitter and they did it no questions asked. Even while financed.
Click to expand...
Click to collapse
I was able to get it done on twitter as well with a few tries to all of their support methods that I didn't have to call for lol

I used to work for tmobile the other way to do the unlock 100% is to be on a business account have the line active for minimum 3days so the system can register you phone to the business line and then you should be able to do the unlock. I'm krazysmokezalot! (Yeah yeah I got banned??) I used to do the unlocks for the OnePlus 7pro back then. I think I have a buddy of mine still working at the same store I worked at, I'll see if he can do is the favor for us I'm getting this phone tomorrow morning I'm sending this LG Wing back. It was a cool phone but man it's a ghost town in that forum ?

[OP8][OOS VIS 68CE] Unbrick tool to restore your device to OxygenOS

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, OP8Pro, OP Nord and OP 8T here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus 8 bought from Visible.
It will only work with Visible variant IN2015 with build tag IN68CE
You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
You can download the following versions:
ANDROID 10:
OOS 10.5.4
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Click on Target button and select Verizon.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
OnePlus for the device and OS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Please note this is a blind release, I haven't been able to find anyone with a Visible variant to test it unlike T-Mobile and Verizon

I can confirm that your release of the visible variant works, and thank God for that! I found it via "thecustomdroid" linking all of the OnePlus 8 variants together on one page (with credit ). I didn't realize that model IN2015 (apparently) doesn't mean IN2015, so I started dumping every ROM I could find onto this thing attempting to get on anything that was not-stock. And every time it failed, every qualcomm crash dump, etc. etc., I was able to successfully MSM back to "Go" thanks to this.
Moral of the story, Visible uses a special OnePlus 8 and this definitely works to get you back when you try to shove a square, global peg into a round, visible hole.

Some_Random_Username said:
Please note this is a blind release, I haven't been able to find anyone with a Visible variant to test it unlike T-Mobile and Verizon
Click to expand...
Click to collapse
I am one of the unfortunate souls cursed with the Visible variant. I have used this MSM tool a couple of times to recover from failed boots after rooting and flashing.
I bought it open box on eBay where nothing related to Visible was disclosed by the volume phone reseller. To be fair, unless they knew something about this model, there is no physical indication on the phone that it is not a standard Oneplus 8.
I only discovered it after closing my eBay return request because it was listed as a 256gb but only 128gb. The first software update to A11 from the latest available, year old 10.5.4 release was announced for this week (April 23).
The device has no carrier bloatware or even carrier specific software apparent. I fail to understand this model's existence especially since it is not the same as the Verizon specific millimeter wave 5g model, is not SIM or bootloader locked (I'm rooted and use a TMo MVNO), and I question how many units Visible can sell of this model.
Has anyone figured out if any file changes can be made so Oxygen updater will see this as a regular IN2015? With Visible's A11 release a couple of days away, I will give OOS 11 a test drive before I try any more fastboot flashing.
I will likely try out AOSP, Pixel Experience or something else less likely to keep me a year behind in the future. For all I know this will be Visible's only OP8 update. I am on Sep 1, 2020 security patch with Android 10.5.4. Oneplus has OP7 models running more recent software than this.

The alleged Android 11 release date for this hobbled hardware will be a week late tomorrow. Nadda. Still on year old 10.5.4 with September security patch. Older Oneplus models have more current OOS. Verizon/Visible is the worst at phone support. Would have been better off with a 7T or if the pristine 7 Pro I bought (for less) had not had a blocked IMEI.
Despite being rooted I cannot even flash any A11 ROM until I have a bootable OOS 11 as base. I am rooted and fastboot flashed 10.5.11 global which booted but would not recognize my SIM. Setting Oxygen Updater to OP8 (non Visible) I was able to download OOS 11 but after seemingly successful flashing it would not boot.
Overpaid for this abandoned oddball. Wonder if I can find a Octopus box guru who can convert it.

Finally!
Now on Oxygen 11.10.0, March 2021 security update (better than September) and Magisk patched.
When the OOS11 files for the MSM tool are available I can try out some other ROMs at some point and see if I can fastboot flash OOS international version working on this thing. Also ordered an EDL cable since it took me hours to get into EDL mode the last time I needed to MSM to 10.5.4.

Pixel 4 EDL

Most of the EDL related posts I've found are in relation to the Pixel 3. Since I've now encountered the EDL issue with my Pixel 4, and there doesn't seem to be a place for it yet, figured I'd get one started here.
There's nothing I can point to that could have caused the issue. Phone was working fine when I went to bed, and when I woke up, it had become a brick overnight. Restarting didn't help at all. Phone remains in EDL, confirmed by connecting to my PC. I was running the Android 12 Beta, though I don't believe it to be a contributing factor.
I'm assuming a catastrophic hardware failure at this point.

Have you already tried using the Pixel Repair Tool? It was specifically designed to work with Rescue Mode which is similar to EDL. Maybe a reflash is necessary.

V0latyle said:
Have you already tried using the Pixel Repair Tool? It was specifically designed to work with Rescue Mode which is similar to EDL. Maybe a reflash is necessary.
Click to expand...
Click to collapse
You need to have access to the Recovery Menu to be able to use the Pixel Repair Tool, specifically entering the Recovery mode. EDL is not the same.

@Amon Darthir are you able to get into bootloader? Hold volume down, then hold power button until phone restarts.
Is your bootloader unlocked? I'd try using the Android Flash tool and reflash all partitions.

sadly my 4xl has the same problem, it seems to be a serious bug from Google and needs to be fixed. Phone can't access Fastboot mode or Recovery mode, it can only stay in 9008 mode. This situation happened when I tried to update android 12 version but failed. Hope to have help from the developer, because there will be many people facing the same situation.

V0latyle said:
@Amon Darthir are you able to get into bootloader? Hold volume down, then hold power button until phone restarts.
Is your bootloader unlocked? I'd try using the Android Flash tool and reflash all partitions.
Click to expand...
Click to collapse
Like Jojo said, EDL is not the same. The EDL is a layer BELOW the what we know as the bootloader. This is the bootloaders bootloader. If you are booting to the EDL, it's because the bootloader is likely corrupted. You can't boot to Fastboot, or what you'd think of as the normal Bootloader.
Essentially, without being Qualcomm, there's nothing you can do. (Unless you want to replace your main board for ~$450).
The issue is being tracked here, but support from Google is nearly non-existent.

Amon Darthir said:
Like Jojo said, EDL is not the same. The EDL is a layer BELOW the what we know as the bootloader. This is the bootloaders bootloader. If you are booting to the EDL, it's because the bootloader is likely corrupted. You can't boot to Fastboot, or what you'd think of as the normal Bootloader.
Essentially, without being Qualcomm, there's nothing you can do. (Unless you want to replace your main board for ~$450).
The issue is being tracked here, but support from Google is nearly non-existent.
Click to expand...
Click to collapse
I see, thanks

Hey!
I am glad I came up to this as I believe I may have a solution for you guys!!!!
V0latyle said:
I see, thanks
Click to expand...
Click to collapse

*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")​or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode(like QFIL).
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
I would recommend using this one: generic > Pixel > EU > Commercial > pixel_Free and use that file, as this one is from an unlocked Pixel I believe
Though I didn't test them so they may just not work at all.

So these are some of my posts for some folks which had same problem, phone stuck at 9008 mode.
I have a lot of interest on this because I am working on a way to unlock any Google Pixel form it's career(which I already did), including the boot loader(which I am currently working on).
I am posting all of that on the Pixel 4 XL forums though.
The situation is this:
EDL mode is like a recovery mode which is available on any Qualcomm device, and it's the primary bootloader.
When the phone boots, it triggers the secondary bootloader(which is the one carriers lock, and it's this one you usually unlock when you want to flash stuff to your phone, like TWRP).
The idea behind this mode is to allow devs to use this to force flash firmware to get the device back and running in case Fastboot and ADB weren't available(basically, to solve the problem you guys are having).
In my case this is useful because I can use it to flash the unlocked firmware from Google and them unlock my phone (my phone is working perfectly on Android 12), and them flash stuff to it.
So if any of you guys try this, let me know how it went!

#mcl said:
*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")​or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode(like QFIL).
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
Click to expand...
Click to collapse
I no longer have my device, as I was able to wallop Google Support enough over the issue that they agreed to RMA the device, however, I'm curious how this would actually work.
The device only boots to EDL, so ADB isn't an option, neither is Fastboot. From what I've seen and understand, without a proper Firehose file, and an image from Qualcomm or Google themselves, there's basically no way to flash the device back to a working state (assuming it even can be).
Are there actual FULL Pixel images available, with bootloader and Android? (They sound to be packaged together). This would seem to be a very serious set of files to have out in the wild... (Which is part of the problem. No one has been able to find those images, otherwise, many would have tried using QPST already)

Amon Darthir said:
I no longer have my device, as I was able to wallop Google Support enough over the issue that they agreed to RMA the device, however, I'm curious how this would actually work.
The device only boots to EDL, so ADB isn't an option, neither is Fastboot. From what I've seen and understand, without a proper Firehose file, and an image from Qualcomm or Google themselves, there's basically no way to flash the device back to a working state (assuming it even can be).
Are there actual FULL Pixel images available, with bootloader and Android? (They sound to be packaged together). This would seem to be a very serious set of files to have out in the wild... (Which is part of the problem. No one has been able to find those images, otherwise, many would have tried using QPST already)
Click to expand...
Click to collapse
So let me explain.
From what I know you can download the firmware directly from Google from here.
For the firehose file, it's the one I send on 2 message. If you open Qualcomm QPST tool, and go to the download menu you will find a place to insert the phone image, though you can only put an image with an specific file system, the same as the files I shared. From what I saw on the web, you just need to flash that file.
If you use QFIL however, you will need and XML file as well.
I believe they are the firmware/Firehose files but I am not sure.

The IssueTracker updated today, with what appears to be an official response from Google:
"This issue occurred due to the natural lifecycle of a memory component. Memory components have a predefined lifecycle based on consumer use cases over time. The recommended solution is an out of warranty repair or replacement..."
Click to expand...
Click to collapse
So we now know that the issue is indeed a hardware fault, and that it is a fault in one of the memory components as suspected.
What's curious still is that these devices are encountering this issue, while much older devices continue to work. Wonder what the difference is.

Amon Darthir said:
The IssueTracker updated today, with what appears to be an official response from Google:
So we now know that the issue is indeed a hardware fault, and that it is a fault in one of the memory components as suspected.
What's curious still is that these devices are encountering this issue, while much older devices continue to work. Wonder what the difference is.
Click to expand...
Click to collapse
Hey!
That's a possible case, though I don't believe that for a few reasons:
1) Even though some components are consumable(like battery and SSD), RAM isn't one of them.
2) For a RAM to fail there is usually a cause, like working on extremely high frequencies, high temperatures and so on which obviously doesn't happen on a phone unless you leave it burning under the sun.
3) How many cases of faulty RAM modules did you see on the web, I didn't see any yet(at least not on phones)
So unless the user overheated its phone or drop it from an airplane XD, it seems to be a hard excuse for the problem.
I don't believe that there is a hardware failure, but I am not a phone engineer so I can't guarantee.
Anyway, if someone finds the cause please let me know

#mcl said:
Hey!
That's a possible case, though I don't believe that for a few reasons:
1) Even though some components are consumable(like battery and SSD), RAM isn't one of them.
2) For a RAM to fail there is usually a cause, like working on extremely high frequencies, high temperatures and so on which obviously doesn't happen on a phone unless you leave it burning under the sun.
3) How many cases of faulty RAM modules did you see on the web, I didn't see any yet(at least not on phones)
So unless the user overheated its phone or drop it from an airplane XD, it seems to be a hard excuse for the problem.
I don't believe that there is a hardware failure, but I am not a phone engineer so I can't guarantee.
Anyway, if someone finds the cause please let me know
Click to expand...
Click to collapse
Never said it was the RAM. It's likely the memory component that the bootloader is on, which is part of what has been speculated. I doubt my "memory component" the only thing they were referring to was RAM.

Amon Darthir said:
Never said it was the RAM. It's likely the memory component that the bootloader is on, which is part of what has been speculated. I doubt my "memory component" the only thing they were referring to was RAM.
Click to expand...
Click to collapse
The bootloader is on the SSD of the phone I think, and it doesn't fail as well, at least no so often...

#mcl said:
You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
I would recommend using this one: generic > Pixel > EU > Commercial > pixel_Free and use that file, as this one is from an unlocked Pixel I believe
Though I didn't test them so they may just not work at all.
Click to expand...
Click to collapse
Sorry for bumping this old thread.
Like quite a few other reports I could find on the Internet, my Pixel 4 XL bricked itself overnight as well...Happy to come across your posts and interested in trying these files out.
Right now I can confirm that my phone is stuck in the EDL mode as I can see "QUALCOMM HS-USB QDLOADER 9008 COMx" in Device Manager when connected to a Windows computer, and I do see the phone in QPST Configuration, that says something like "QCP-XXX Sahara download".
However, unlike most QPST tutorials I found online (including the one you posted), the port status in QPST Configuration does not say "Enabled", but rather showing a half-way green progress bar all the time. I've tried to wait for about one hour just in case, and reinstalling the Qualcomm driver, restarting the computer etc. but nothing changed.
And if I just ignored that and go straight to flashing anyway, I couldn't get it to work with the MDN files you posted. QFIL would need a .xml file which is not included. Software Download reports an error message of "could not open the programmer file" (by this I was using the EU/.../pixel_free one).
Not sure what does it mean by "could not open" - is it the .mdn file is invalid, or it's just not the right file for this particular phone?

I suppose nobody has been able to use what @#mcl has posted back in 2021 to work? And the natural lifecycle of a memory component is only 3 years? That sucks.

Hi!
Yeah unfortunately there is close to nothing about this, probably because it's very low-level programming, and for security and economical reason Qualcomm won't share this kind of information. Only someone that work inside Qualcomm may have access to the needed files and documentation.
ObsidianTheRed said:
I wanted to confirm that removing com.google.android.apps.work.oobconfig as detailed in mcl's original post worked on a Verizon carrier-locked Pixel 5. Awesome!
Click to expand...
Click to collapse
bodayw said:
Sorry for bumping this old thread.
Like quite a few other reports I could find on the Internet, my Pixel 4 XL bricked itself overnight as well...Happy to come across your posts and interested in trying these files out.
Right now I can confirm that my phone is stuck in the EDL mode as I can see "QUALCOMM HS-USB QDLOADER 9008 COMx" in Device Manager when connected to a Windows computer, and I do see the phone in QPST Configuration, that says something like "QCP-XXX Sahara download".
However, unlike most QPST tutorials I found online (including the one you posted), the port status in QPST Configuration does not say "Enabled", but rather showing a half-way green progress bar all the time. I've tried to wait for about one hour just in case, and reinstalling the Qualcomm driver, restarting the computer etc. but nothing changed.
And if I just ignored that and go straight to flashing anyway, I couldn't get it to work with the MDN files you posted. QFIL would need a .xml file which is not included. Software Download reports an error message of "could not open the programmer file" (by this I was using the EU/.../pixel_free one).
Not sure what does it mean by "could not open" - is it the .mdn file is invalid, or it's just not the right file for this particular phone?
Click to expand...
Click to collapse
I still didn't gave up on any of the projects (the EDL thing and the unlock SIM & Booloader), but due to high complexity of those projects, the fact that I have a quite busy life which leaves me with very little time to bring live to these projects and that I am basically alone, means they will probably take some time.
Maybe try searching using different search engines, and try being very specific like "MBN file pixel 4".
Hope you find a solution to your problem!

[GUIDE] Unlock Verizon OnePlus 8 5G UW (IN2019) bootloader

Disclaimer​While I will assist with any issues resulting from this guide, I disclaim all responsibility and cannot be held accountable for any consequences caused by the use or misuse of this tool or process. This method also will wipe your phone, so please back up your data. I also will disclaim any understanding as to why exactly this works, since this method was developed by someone else, I am just listing the instructions on how to use it. With that being said, understand your personal limits and read this entire guide before starting.
Preface​I have seen dozens of posts asking for a Bootloader unlocking method for the OnePlus 8 5G UW (IN2019) and thanks to the attributed users at the end of this post, a method has been found. I will document the most straightforward way to unlock the bootloader here so you can install custom OSes, TWRP, and Magisk.
Part I: Prerequisites and initial setup​To follow this guide you will need
A Windows PC (running 7+)
Latest MsmDownloadTool and stock firmware for the OnePlus IN2019 - Link
OnePlus 8 IN2019 with latest stock software update and USB cable
Latest version of platform-tools - Link
The bootloader unlock.ops file - Link
Plug your phone into your PC using a USB 2.0 port (this is important, USB 3.0 has given me a lot of issues and just doesn’t seem to work all the time) and ensure USB debugging is enabled.
Extract the downloaded platform-tools zip and open the platform-tools folder in a command prompt, and Run adb devices and makes sure your device appears in the list.
Next, extract the OnePlus_8_Verizon_OxygenOS_11.0.zip and open up the MsmDownloadTool V4.0.exe inside the instantnoodlev_15_O.01_210110 folder.
When the application opens, select “Others” under the User type dropdown and hit next. Leave this window and the platform-tools command prompt open.
Spoiler: Command Prompt
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Spoiler: MsmDownloadTool setup
Part II: Entering Qualcomm EDL mode and installing correct QDLoader Driver​In this section we will install the correct drivers to utilize Qualcomm's Emergency Download (EDL) mode. When you are in EDL mode, your phone screen will be completely black and it will only exit if you complete a flash or unplug it from your PC and hold volume up, volume down and power. To enter EDL mode from a powered off state, hold volume up and volume down and connect your phone to your PC.​1. Return to the platform-tools command prompt, and type adb reboot edl and wait. Your phone should disconnect from the computer and then reconnect.
2. Open Device manager, and check for the device “Qualcomm HS-USB QDLoader 9008” or “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” - if you see “Qualcomm HS-USB QDLoader 9008” under Ports (COM and LPT), skip to part III. If you see “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” under Other Devices with a yellow triangle, then proceed to step 3.
Spoiler: QUSB_BULK_CID:xxxx_SN:xxxxxxxx (Proceed to Step 3)
Spoiler: Qualcomm HS-USB QDLoader 9008 (Skip to Part III)
3.
Spoiler: Windows 11
Open Settings, Go to Windows Update and Check for updates. After, Click Advanced options, Optional Updates and drop down “Driver Updates” Locate “Qualcomm Incorporated - Ports - 3/25/2016 12:00:00 AM - 2.1.2.2” in the list, and install it.
Spoiler: Windows 10
On Windows 10 - Open Settings, Go to Update & Security, Check for updates, Click “View Optional Updates” and select “Qualcomm Incorporated - Ports - 3/25/2016 12:00:00 AM - 2.1.2.2” and install it.
This should install the correct driver, replacing “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” with "Qualcomm HS-USB QDLoader 9008" in device manager.
Spoiler: Correctly Installed Driver
Part III: Flash Stock Firmware​In this section, we will flash the stock IN2019 Android 11 firmware. If you have any trouble with this process refer to the original guide on how to do this here.​1. Return to MsmDownloaderTool and hit the Enum button. In the list, it should list the COM Port associated with the device. The status of connection should read “Connected”
Spoiler: MsmDownloadTool Connected
2. Click the “Start” button. This will flash the stock firmware, wiping your data. Make sure you have backed your data up at this point. It will take a few minutes, usually ~300 seconds. Once it completes, it will reboot into factory default android.
3. Close MsmDownloadertool and once you are back to android, unplug your phone and power it off.
Part IV: Unlock the bootloader​In this section, we will flash the unlockable firmware and unlock the device for good.​1. Inside the directory with MsmDownloaderTool V4.0.exe, there should be a file called “instantnoodlev_15_O.01_210110.ops”. Remove it from the directory, either by deleting it or moving it to another folder. Then take the unlock.ops file downloaded earlier, and drag it into the directory. It should be in the same folder as MsmDownloaderTool.
Spoiler: Directory before unlock.ops
Spoiler: Directory after unlock.ops
2. Reopen MsmDownloaderTool V4.0.exe and like before, select “Others” in the drop down, and click next. Leave the window open.
3. Hold in the Volume up and down buttons, then plug your phone back in. Keep holding the buttons until your phone connects to your PC as "Qualcomm HS-USB QDLoader 9008", like before. Check device manager to ensure that it’s connected correctly as a COM port. If it boots to android, power it off and try again.
4. Return to MsmDownloaderTool and click Enum. Make sure the phone is still displayed in the list under the associated COM Port.
5. Click start. The flashing should take about 15 seconds, and when complete, your phone should restart. It will display a message at boot saying “<!> The device is corrupt..” Do not panic, this is normal.
6. Unplug your phone and hold Volume Up, Volume Down and Power until the device reboots and let go once it shows the OnePlus Logo and “Fastboot Mode”. You should arrive at a screen that has “Start” in big green letters at the top, and “Fastboot mode” below it, with the very last item saying “Device state - Locked” in red text.
7. Plug your phone back into your computer, and open device manager. Look for the “Kedacom USB Device” category with “Android Bootloader Interface” under it. If this device is present, skip to step 9. If this device is not, proceed to step 8.
8. Go back to Windows Update, Check for updates again, go into Optional Updates and install “Google, Inc. - Other hardware - Android Bootloader Interface”
Spoiler: Optional Driver
Check device manager to ensure “Android Bootloader Interface” is present under Kedacom USB Device.
Spoiler: Kedacom USB Device
9. Return to your command prompt window open in platform-tools, and run fastboot devices and ensure your device is in the list.
10. Finally, run the command fastboot flashing unlock and on your phone, it should prompt you to confirm unlocking the bootloader. Once complete, it should reboot into Android.
11. Shut the phone off again, and then Hold Volume Up, Volume Down, and Power and let go when the OnePlus logo and “Fastboot mode” shows up on screen. If the final item in the list says “Device State - Unlocked”, Congrats! You have successfully unlocked your bootloader. You can follow your custom OS’s installation guide from here.
Part V: Troubleshooting, Notes, and Attributions​
Spoiler: If your MSM tool gets stuck on "Sahara communcation failed" when trying to flash.
Unplug your phone, and hold Power, Volume Up, and Volume Down. It should reboot into fastboot mode. Using the volume keys, navigate to the "Power off" option and hit the power button to confirm. Then holding Volume Up and Down, plug your phone back into your PC and try flashing again.
Any attempt to use MsmDownloadTool after the unlock will cause the device
to become locked again. You can unlock again by repeating the steps above.
Attempting the unlock process while running android 10 will result in a
crash at bootup. Update your phone to the latest update before starting.
USB 3.0 has thrown some obtuse errors when trying to use this process, so I highly recommend using a USB 2.0 port if possible.
If you want to flash back to stock firmware again (relock bootloader), you have to first flash this file (stock.ops) and then flash the bundled stock firmware. It will give a mismatch error if you do not.
You can only have one .ops file in the MsmDownloadTool directory at a time. You'll get an error if there are multiple files.
If for some reason, you run into an issue or skip a step by accident, leave a comment and I will try to help as much as possible. This is my first XDA guide and I just wanted to compile something that would have saved me hours of trial and error.
Attributions:​@Whoareyou for providing the method and unlock.ops to me originally. He pretty much got the ball rolling for me.
@retryfail / https://retry.abort.fail for creating the unlock.ops and providing the original guide, this would absolutely not be possible without his work.
@Some_Random_Username for the MsmDownloadTool tutorial and resources.
https://onepluscommunityserver.com (hosted by Votton, maintained by @Some_Random_Username and AnonymousWP) for providing the stock firmware and MsmDownloadTool

The unlock.ops link doesn't work?!?

7eregrine said:
The unlock.ops link doesn't work?!?
Click to expand...
Click to collapse
It does. If you already have Android 11, just save and store your phone data, factory reset, boot into EDL, connect and start the tool. If it runs an error, DONT stop the download. Press the POWER + VOLUME UP + VOLUME DOWN buttons at the same time and hold it until it reconnects. It takes a few seconds. Once it reconnects you should see it fully load. I didn't see the need for stock firmware file unless I needed to reflash my stock after ****ing up (I bricked it once or twice), and tbh it's not even the one I used to reset my phone. I just unlocked my BL a few hours ago. It works, I promise

7eregrine said:
The unlock.ops link doesn't work?!?
Click to expand...
Click to collapse
Right click the link and open in new window, than refresh the blank page it opens. That will trigger the download.

GloomyHat14 said:
It does. If you already have Android 11, just save and store your phone data, factory reset, boot into EDL, connect and start the tool. If it runs an error, DONT stop the download. Press the POWER + VOLUME UP + VOLUME DOWN buttons at the same time and hold it until it reconnects. It takes a few seconds. Once it reconnects you should see it fully load. I didn't see the need for stock firmware file unless I needed to reflash my stock after ****ing up (I bricked it once or twice), and tbh it's not even the one I used to reset my phone. I just unlocked my BL a few hours ago. It works, I promise
Click to expand...
Click to collapse
Did you follow the guide while unlocking your bootloader and if so, do you have any feedback for the guide? This is my first guide so I just wanted to hear any potential criticism.

Mason220 said:
Did you follow the guide while unlocking your bootloader and if so, do you have any feedback for the guide? This is my first guide so I just wanted to hear any potential criticism.
Click to expand...
Click to collapse
It worked for me. It was straightforward, and it was really easy to figure out. I kept getting an error during the parameter update when I used the included firmware, so I just flashed the Unlock.ops file and carried on. I had a dumb moment bc I didnt actually read it fully at first, so I freaked out and thought that I'd bricked it lmao. But all in all, it was good man. Good instructions, and you gave examples that helped me out when I was confused. Good job! Well worth the wait

This replaces the VZW abl/xbl with ones from one of the unlockable variants? Impressive that it works this way...

AndyYan said:
This replaces the VZW abl/xbl with ones from one of the unlockable variants? Impressive that it works this way...
Click to expand...
Click to collapse
From my understanding, it messes with the param essentially tricking the phone into thinking it's not from Verizon.

Mason220 said:
From my understanding, it messes with the param essentially tricking the phone into thinking it's not from Verizon.
Click to expand...
Click to collapse
Fantastic! Actually I have a OnePlus 8 T-mobile. Did you modify the Msmdownloadtool to allow this process going? Can you help allow msmdownloadtool to flash global roms to the T-mobile/ Verizon variant so that we maybe can unlock the second sim function?

dlhxr said:
Fantastic! Actually I have a OnePlus 8 T-mobile. Did you modify the Msmdownloadtool to allow this process going? Can you help allow msmdownloadtool to flash global roms to the T-mobile/ Verizon variant so that we maybe can unlock the second sim function?
Click to expand...
Click to collapse
The MsmDownloadTool did not need to be modified at all, you just had to swap the included .ops file (Stock firmware) with the unlock.ops in the directory, and it'll flash it on. As for the second question, I'm not really sure how I could help. If really would like my help, I'd be happy to assist, just contact me on Discord (Mason.#6969) or Telegram (message me on xda and i'll give it to you).

Thanks guys. I'll be trying this soon.

7eregrine said:
Thanks guys. I'll be trying this soon.
Click to expand...
Click to collapse
Please share your findings when you are successful.

Does this process replace verizon rom with global stock rom?

Does this process replace verizon rom with global stock rom?
I am on OnePlus 8 5G UW (Verizon) using a different network operator.

Zombify01 said:
Does this process replace verizon rom with global stock rom?
I am on OnePlus 8 5G UW (Verizon) using a different network operator.
Click to expand...
Click to collapse
No. It just unlocks the bootloader so installing a different ROM is possible. What you install is up to you.

Mason220 said:
No. It just unlocks the bootloader so installing a different ROM is possible. What you install is up to you.
Click to expand...
Click to collapse
+1

is there any way to change from verizon rom to global rom..?

Can we use with another Sim when flashed custom Rom?? Anyone know??

nhonpiseth said:
Can we use with another Sim when flashed custom Rom?? Anyone know??
Click to expand...
Click to collapse
Yes. As long as your device is unlocked (60 days after initial purchase from Verizon) then it will work with any SIM.

Royk504 said:
is there any way to change from verizon rom to global rom..?
Click to expand...
Click to collapse
I did this while trying to get the camera working. I think you can flash the global rom using the stuff from this guide

[GUIDE] OnePlus 8 5G ..TMobile..(IN2017) bootloader unlock instant

Disclaimer
While I will assist with any issues resulting from this guide, I disclaim all responsibility and cannot be held accountable for any consequences caused by the use or misuse of this tool or process. This method also will wipe your phone, so please back up your data. I also will disclaim any understanding as to why exactly this works, since this method was developed by someone else, I am just listing the instructions on how to use it. With that being said, understand your personal limits and read this entire guide before starting.
Thanks to the attributed users at the end of this post, to find this method we are waiting for years...
METHOD 1:
Part 1: Requirements:
• To follow this guide you will need
A Windows PC
• Latest MsmDownloadTool for Oneplus IN2017 - Link
• Latest version of platform-tools - Link
• The bootloader unlock.ops file - Link
Plug your phone into your PC using a USB 2.0 port (this is important, USB 3.0 has given me a lot of issues and just doesn’t seem to work all the time) and ensure USB debugging is enabled.
Extract the downloaded platform-tools zip and open the platform-tools folder in a command prompt, and Run adb devices and makes sure your device appears in the list.
Next, extract the instantnoodlet_15_O.16_201001.zip and open up the MsmDownloadTool V4.0.exe inside the instantnoodlet_15_O.16_201001 folder.
When the application opens, select “Others” under the User type dropdown and hit next. Leave this window and the platform-tools command prompt open.
Part II: Entering Qualcomm EDL mode and installing correct QDLoader Driver
Part III: Flash Stock Firmware
In this section, we will flash the stock IN2017 Android 10 firmware.
Click the “Start” button in Msmtool. This will flash the stock firmware, wiping your data. Make sure you have backed your data up at this point. It will take a few minutes, usually ~300 seconds. Once it completes, it will reboot into factory default android 10.
Close MsmDownloadertool and once you are back to android, unplug your phone and power it off.
Part IV: Unlock the bootloader
In this section, we will flash the unlockable firmware and unlock the device for good.
1. Inside the directory with MsmDownloaderTool V4.0.exe, there should be a file called “instantnoodlet_15_O.16_201001.ops”. Remove it from the directory, either by deleting it or moving it to another folder. Then take the unlock.ops file downloaded earlier, and drag it into the directory and rename it to instantnoodlet_15_O.16_201001.ops . It should be in the same folder as MsmDownloaderTool.
2. Reopen MsmDownloaderTool V4.0.exe and like before, select “Others” in the drop down, and click next. Leave the window open.
3. Hold in the Volume up and down buttons, then plug your phone back in. Keep holding the buttons until your phone connects to your PC as "Qualcomm HS-USB QDLoader 9008", like before. Check device manager to ensure that it’s connected correctly as a COM port. If it boots to android, power it off and try again.
4. Return to MsmDownloaderTool. Make sure the phone is still displayed in the list under the associated COM Port.
5. Click start. The flashing should take about 15 seconds, and when complete, your phone should restart. It will display a message at boot saying “<!> The device is corrupt..” Do not panic, this is normal.
6. Unplug your phone and hold Volume Up, Volume Down and Power until the device reboots and let go once it shows the OnePlus Logo and “Fastboot Mode”. You should arrive at a screen that has “Start” in big green letters at the top, and “Fastboot mode” below it, with the very last item saying “Device state - Locked” in red text.
Plug your phone back into your computer.
7. Return to your command prompt window open in platform-tools, and run fastboot devices and ensure your device is in the list.
8. Finally, run the command "fastboot flashing unlock", it should prompt you to confirm unlocking the bootloader. Once complete, it should reboot into Android.
9. Shut the phone off again, and then Hold Volume Up, Volume Down, and Power and let go when the OnePlus logo and “Fastboot mode” shows up on screen. If the final item in the list says “Device State - Unlocked”, Congrats! You have successfully unlocked your bootloader. You can follow your custom OS’s installation guide from here.
If you want to flash back to stock firmware again (relock bootloader), you have to first flash this file (stock.ops) and then flash the bundled stock firmware. It will give a mismatch error if you do not.

So this is essentially the same as the IN2019 guide, just with the IN2017? Sounds neat.

Did anyone tried on Oneplus 8 IN 2017, Is it working

MohmmadUzairKhan said:
Did anyone tried on Oneplus 8 IN 2017, Is it working
Click to expand...
Click to collapse
Yes...i converted mine IN2017 without token..also using dual sims now

badshah99 said:
Yes...i converted mine IN2017 without token..also using dual sims now
Click to expand...
Click to collapse
you converted that ROM into which rom ?
did you follow this method?
Which files you flash? share those files link in PM or here

Share that file link which you flashed in local update? to convert dual sim

First flash tmobile msm 15.O.16_201001
Then global EU fastboot rom 10.5.9
Then ota update

badshah99 said:
First flash tmobile msm 15.O.16_201001
Then global EU fastboot rom 10.5.9
Then ota update
Click to expand...
Click to collapse
OTA update which rom?
EU or any other zip file?
your are using dual sim in which rom? OOS 11
share that file link which you used in OTA upgarde

15.I.40 downgrade OTA

badshah99 said:
15.I.40 downgrade OTA
Click to expand...
Click to collapse
File link?

MohmmadUzairKhan said:
File link?
Click to expand...
Click to collapse
[OnePlus 8][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com

Dude good job

Now make a new guide on XDA to convert method to dual sim.

MohmmadUzairKhan said:
File link?
Click to expand...
Click to collapse
MohmmadUzairKhan said:
Now make a new guide on XDA to convert method to dual sim.
Click to expand...
Click to collapse
Its already there..also given on youtube

badshah99 said:
Its already there..also given on youtube,
Click to expand...
Click to collapse
,....

Does dual sim work on OOS 12 or OOS 13 beta?

finally! Good job man! Will try it asap. Hope dual sim functioning
edit2: works, I went to the T mobile rom and check allow oem unlock first and then msmdownload the unlock.ops
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
edit1:not working yet...trying to figure it out

dlhxr said:
finally! Good job man! Will try it asap. Hope dual sim functioning
edit2: works, I went to the T mobile rom and check allow oem unlock first and then msmdownload the unlock.ops
View attachment 5755213
edit1:not working yet...trying to figure it out
View attachment 5755203
Click to expand...
Click to collapse
flash again tmobile msm and try again..it will work

dlhxr said:
finally! Good job man! Will try it asap. Hope dual sim functioning
edit2: works, I went to the T mobile rom and check allow oem unlock first and then msmdownload the unlock.ops
View attachment 5755213
edit1:not working yet...trying to figure it out
View attachment 5755203
Click to expand...
Click to collapse
First Enable OEM Unlocking in developer options.

badshah99 said:
flash again tmobile msm and try again..it will work
Click to expand...
Click to collapse
yes. it works after I check allow oem unlocking before flashing the unlock.ops.
and dual sim works on oxygen 11, confirmed using my op 8 pro sim tray.
I see to prevent breaking the dual sim functionality, I have to use custom rom with magisk dual sim patch. But I see the custom roms are now based on oos 12. Can I flash oos 12 first and then to custom rom? will it break dual sim function?