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, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T and Nord N10 5G here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N100.
You should 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
Please note that on N10 crossflashing regional builds is no longer possible by EDL, flash is tied to device project ID. I therefore expect same to happen on N100. For reference EU devices project ID is 20883 while international devices project ID is 20881.
BE81AA tools (global firmware):
ANDROID 10:
OOS 10.5.3
OOS 10.5.5
Mirror for first and last MSMs: https://onepluscommunityserver.com/
BE83BA tools (european firmware):
ANDROID 10:
OOS 10.5.2
OOS 10.5.6
OOS 10.5.7
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.
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.
How can I check my device project ID?
Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.
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:
@lsthps for testing 10.5.2 BA version on his device
OnePlus for the device and OS
Reserved
Worked great, thank you! Just one click and the device is back to life. Awesome!
Added MSM tool for global build (10.5.3 BE81AA).
So basically you can't flash convert a branded N100 to global software?
rafe83 said:
So basically you can't flash convert a branded N100 to global software?
Click to expand...
Click to collapse
Correct, you can't do that with this tool.
However, OnePlus 8 and 8T T-Mobile versions users have been able to flash global software via fastbootd, so if you're lucky enough same may eventually work for N100.
Do you happen to have the Metro branded MSM tool?
craznazn said:
Do you happen to have the Metro branded MSM tool?
Click to expand...
Click to collapse
Unfortunately no but feel free to DM me so that I can tell you how you can try to obtain it.
Added OOS 10.5.6 MSM (EU only)
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, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T and Nord N10 5G here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N100.
You should 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
Please note that on N10 crossflashing regional builds is no longer possible by EDL, flash is tied to device project ID. I therefore expect same to happen on N100. For reference EU devices project ID is 20883 while international devices project ID is 20881.
BE81AA tools (global firmware):
ANDROID 10:
OOS 10.5.3
Mirror for first and last MSMs: https://onepluscommunityserver.com/
BE83BA tools (european firmware):
ANDROID 10:
OOS 10.5.2
OOS 10.5.6
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.
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.
How can I check my device project ID?
Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.
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:
@lsthps for testing 10.5.2 BA version on his device
Votton for providing a server as an alternative mirror
OnePlus for the device and OS
Click to expand...
Click to collapse
Can you add OOS 10.5.7?
Added OOS 10.5.7 (EU) and 10.5.5 (global) MSMs
yandere2016 said:
Can you add OOS 10.5.7?
Click to expand...
Click to collapse
Fyi you don't need latest version to unbrick your device, I just post them for the convenience of restoring to a newer build
So I've been trying to root my device and bricked it by using a process that won't work on my HD1907 T-Mobile Variant. Tried a few different methods and finally was able to get ADB/Fastboot to recognize my device as an "Android Device" by installing the OnePlus drivers for my phone. Well, now it's not working at all. Can't turn off the phone to get it into EDL since it just automatically boots up on it's own, but I can get it back into Fastboot mode. What sux is that I can't seem to get ADB to recognize the device anymore. Also, I haven't been able to use this method since my device shows up in Device Manager as an "Android Device", not the "QHUSB_BULK" that you mentioned in the post. Any tips on getting this method to work? Should I be able to just uninstall the OnePlus drivers and Install the Qualcomm drivers instead? Is there a way to get ADB to recognize my device and then try to flash a stock OS to the device that way?
Please, any advice would really be greatly appreciated.
Thanks, you are a lifesaver! I got myself into a weird position when trying to install Magisk (flashed the wrong boot.img) and this saved me. I got my phone from Amazon (listed as "OnePlus Nord N100 Midnight Frost Unlocked Smartphone, 4GB+64GB, US Version, Model BE2011") and although it was not the T Mobile variant, the pre-installed image lacked the ability to flash a local update (the gear icon was absent in settings -> system -> system updates). Now I have flashed stock Oxygen OS and all is well. As a side question, any clue what kind of weird build it may have shipped with?
can someone commen msmdownloader for realme x50 pro i downloaded other and they jist down wprk.
is it good for model BE2013?
THIS SAVED ME!
I just bought Nord N100 BE2011 from Best Buy (in California US)
I made the same mistake of extracting the updated boot.img 10.5.7 and patching it with Magisk without updating the rest of the system first. So the Boot partition was updated to 10.5.7 while the Oxygen OS and other modules were still on the stock 10.5.3
While the phone was rooted and I was able to install apps and google play etc.. the Phone and Voicemail Functions died with UI Error (SOFT BRICK)
This MSM Tool worked,
I did as the OP says, Download the File above (2.4 gb)
I downloaded the qualcomm drivers first from https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
then boot to edl using adb command:
adb reboot edl
Check to see if phone shows up in device manager as QDLOADER 9008. It is under COM ports
Then unplug the phone leaving it in EDL mode and run the MSM tool
when executing the MSM application it will prompt for login select: "other" from drop down
once the MSM program shows up plug in the phone
It should indicate that it is connected
press start.
On first attempt i received Error and followed the OP:
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.
(to get it out of edl mode and into fastboot hold power and vol-up)
This worked and the download took 5 minutes.
Phone rebooted to factory settings (after being bricked) and I can receive calls
Cheers,
Alex
Hi,
Can I use this tool for Locked by Metro phone?
I received the Android 11 update and Wifi stopped working perfectly with constant drops. My version is EU, so I used this tutorial to revert to Adroid 10 and Global, and it worked perfectly.
Hi, could you add this unbrick tool for the oneplus nord ce 5G ? thanks
Related
I'm opening this topic because i was having a serious headache to solve my problem. You can find several tutorials on how to unbrick Xiaomi smartphones, but when the bootloader is locked it's another story. First of all, sorry for my english, i used Google Translator. That's said, lets go.
I bought my RN7 and it came with an UNLOCKED BOOTLOADER, GLOBAL version, and i decided to give a full wipe and LOCK the bootloader. That's when my headache started. After flashing using MiFlash and locking my device, when it booted, this message appeared: "This MIUI version can't be installed on this device". To my despair, the bootloader was blocked and i was unable to even install a custom recovery to try to reverse the situation. I spent an entire day without stop, searching on web how to solve this problem, even tried EDL mode + QFIL or EDL mode + MiFlash, but the same message remained when i tried to start my device: "This MIUI version can't be installed on this device ". For a few moments i thought i had lost my phone. Suddenly i remembered my Redmi Note 7 it came with a UNLOCKED BOOTLOADER, then i remembered something else: with an unlocked bootloader, you can install ROMs from all regions (China, Russia, Europe, India, etc). After trying the EDL + QFIL method with an CHINESE ROM, my device started.
In short: the seller gave me a Redmi Note 7 from CHINA region saying it was GLOBAL, he must have unlocked the bootloader himself and installed a global ROM to trick me, even the RN7 box says GLOBAL VERSION. When i tried to lock bootloader and wipe, the global ROM was not compatible because my device was Chinese, not Global, and the message "This MIUI version can't be installed on this device" appeared. Above i inform my steps and i hope it helps many people who are going through the same situation as me, without further ado, follow all the steps EXACTLY in the same way and sequence, as there may be a problem if they try one step before the other:
Pre Requisites:
- Download QFIL
- Download Redmi Note 7 "firehose" (or your device version), in case RN7 lavender is the file "prog_emmc_firehose_Sdm660_ddr.mbn"
- Download and extract a ROM for the region you want to test (chinese ROM in my case, search on Google "chinese image redmi note 7")
NOTE: remembering that the ROM and region may vary, if yours does not work in China, try in another region that will probably work
Steps:
1 - Install QFIL
2 - Move the extracted ROM image folder (after you extract the rom, will appear a folder like "lavender_images_V12.0.1.0.QFGCNXM_20200714.0000.00_10.0_cn", for example) to the QFIL "Bin" directory (eg "C:\Program Files (x86)\QPST\bin")
3 - Copy the firehose file (prog_emmc_firehose_Sdm660_ddr.mbn) to the extracted ROM/images folder (ex: "C:\Program Files (x86)\QPST\bin\lavender_images_V12.0.1.0.QFGCNXM_20200714.0000.00_10.0_cn\images")
4 - Open QFIL AS AN ADMINISTRATOR
5 - Select Build Type: Flat Build, Programmer Path: select firehose file (prog_emmc_firehose_Sdm660_ddr.mbn), click on "Load XML" and select the XML files that will appear (in my case "rawprogram0" and then "patch0")
6 - At this point, you will have to enable EDL mode on your smartphone, you will have to open, disconnect the battery and cause a type of short for the computer recognize the smartphone on USB port
NOTE: please search for a video that teach how to do this, unfortunately i can't post videos here. Also, open the device manager of the computer and keep an eye on the session of "COM and LTP ports" so that when the device is shorted and you connect the USB cable on PC, it will appears there
7 - Click on the "Download" button and wait for the procedure to be completed
NOTE: if you have an error such as "sahara fail, download fail", it was due to not having performed the steps in that order. Follow step by step the way i told you, if you connect to EDL before opening QFIL it can go wrong, or not run as an administrator.
That's it, i hope it helps a lot of people, unfortunately i can't help more than that because i'm not an expert, i just showed my step by step to get me out of this situation. If you don't have a Redmi Note 7, have another device on the same line, you can try these same steps, only with another firehose file and another ROM, to see if it works. Don't give up, you manage to unbrick you device!
Hope this helps!
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, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T, regular OPN10 5G and regular OPN100 here is the EDL package (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N100 bought from T-Mobile.
As this is a carrier specific MSM, it will only work with BE2012 model with build tag BE82CB
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.8
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.
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
Reserved
This is excellent. But, is there any way to extract a payload.bin or boot.img from these unbrick tools?
I'm searching for a way to root BE2012 / BE82CB on this 10.5.8 software.
bouyakasha said:
This is excellent. But, is there any way to extract a payload.bin or boot.img from these unbrick tools?
I'm searching for a way to root BE2012 / BE82CB on this 10.5.8 software.
Click to expand...
Click to collapse
You should be able to use https://github.com/bkerler/oppo_decrypt
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, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T, regular OPN10 5G and regular OPN100 here is the EDL package (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N100 bought from Metro by T-Mobile.
As this is a carrier specific MSM, it will only work with BE2015 model with build tag BE82CF
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.8
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.
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:
@absoluteparanoia for 10.5.8 MSM
OnePlus for the device and OS
Reserved
HI.
Can i Use another firmware(Global or EU)?
Thanks.
Today I decided to update Android 11. As my phone has been notifying me of system update every day. Updating went fine. I started rooting by downloading 11 Ota update for Europe. Magisk created patched file and i flashed file, like I did with Android 10.
This is where problems came: My phone will boot to somekind os where I have only two options when pressing power button(Power off and restart). Nothing on the screen, only power button menu works. So I did flash original 11 boot file and same thing happens. Only power button works.
To the topic: I did try this but some how my phone just wont go to EDL Mode. I have tried couple different drivers. MSMDownload tool won't find any thing. And Yes QDLOADER 9008 driver is installed. Only place I can use the phone is fastboot mode, atleast device manager finds it. If I boot anything else no connection.
I'm happy that my unlocked Nokia 6.1 still works. So I have no hurry, maybe some day someone releases working TWRP for this and I can flash something else to replace this Oxygen OS.
Edit: I finally managed to restore one of those restore images. Why it was not working before. Me and stupid com-ports. MsmDownloadTool should have changeable com-port setting or working autodetection.
Thank you sooo much I accidentally soft bricked my phone but got it working with this mthod!
When I use `adb reboot edl` - my BE2015 just restarts itself.
Any idea why I can't get into EDL mode?
Super legit!! I had rooted one phone then bricked it trying to put lineage on, then bricked another phone of the same model. This program came in clutch!! Only thing is I had to buy a windows laptop just to use it, but I got a 30;return policy
And I'm still gonna root these and try again.
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, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T, regular OPN10 5G and regular OPN100 here is the EDL package (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N100 bought from Metro by T-Mobile.
As this is a carrier specific MSM, it will only work with BE2015 model with build tag BE82CF
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.8
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.
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:
@absoluteparanoia for 10.5.8 MSM
Votton for providing a server as an alternative mirror
OnePlus for the device and OS
Click to expand...
Click to collapse
what if i do all of said steps. and my phone isnt detecting in edl mode i have a one plus nord n100 globally unlocked but i have access to recovery ... can i reinstall the boot img somehow .. thanks
For me I was able to get into edl thru twrp recovery. Just go boot twrp from recovery, then go to the reboot menu and select the option reboot in edl and if that don't work you can also use the adb command "adb reboot edl" if you unmount/disable the MTP.
The 3/2022 update from F(x)tec says it will be mere weeks to delivery, still nothing here!
Moderators emailed me after my last rant in another section - to you, I cannot reply from that email because the service only receives.
If there really is no activity on this device, at least periodically update the forum with a sticky with a dated status. Sure, I'm probably the only one who comes back in hopes of seeing some activity, but in case there are others, it is the least you can do. If the device is dead before arrival, say so!
When (if) this arrives, I plan to explore the different ROMS. F(x)Tec promised there would be at least three available: Ubuntu Touch, LineageOS, and Stock. I chose Ubuntu Touch, but I want to (safely) switch ROMS. While I am a developer, I have zero experience with Android development, so I can't whip it up myself. I need instructions, options, etc.
Will there be a TWRP or equivalent recovery? Can I back-up and restore the system without messing directly with ADB and fastboot? Does the Lineage team have any progress reports on porting to this device? Do they have one to work on? Will Stock be Android 12L? What other teams are creating or porting ROMS to this device? Will there be continued attention and updates for a few years? Will GSI ROMS work on this? Which variety?
Once again, I took this chance based on my perceived reputation of XDA. This is your phone, designed for geeks like me. Show me I am not playing a fool.
If it makes you feel better, upon arrival, I plan on porting as many of the different Android flavours as I can over to the Pro1X, along with sources. This includes TWRP.
My tracking number says it's currently in Alaska.
I just got mine and already broke it lul.
My fault for not taking a full backup image before messing with it.
@snortphome its not easily possible to brick this device.
Did you do the full recovery reflash using the provided EDL images?
Pro1X - Stock Android OS (Build Number: v2.1.2_20220707)
NEW Version of guide here Below the original text:(above inserted by EskeRahn) If youre reading this, it seems like you miss the good old Android OS or youve accidentally fried your PrawnX already! Dont worry! We have your back. The link below is the full build of the Pro1X stock Android OS (v2.1...
community.fxtec.com
To flash using EDL and Linux:
Install EDL-Tool by berkele
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
Put Pro¹ X in EDL mode using `adb reboot edl` when you got adb available. Else
Pro¹-X needs to be put in EDL mode manually. Hold power and vol + and vol - During boot and release all after android logo flashes up shortly and goes into a dark screen second. If it stays dark after you removed the combo, Prawn is in EDL mode.
If it is booting or showing fastboot, redo. I needed 5 tries first.
Check if the usb connected Pro¹ X is in EDL mode using lsusb, it should show:
`Bus 003 Device 011: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)`
Then become root or do the following with sudo each:
```
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram_unsparse0.xml patch0.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram1.xml patch1.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram2.xml patch2.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram3.xml patch3.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram4.xml patch4.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram5.xml patch5.xml .
```
If any of the commands get stuck, redo the finger combo and enter EDL again.
I did not need to do that since all went well with original cable and Pro¹ X not touched during flash.
reboot prawn with
`edl --loader=prog_firehose_ddr.elf reset reboot`
F(x)tec will release flashing instruction using Qulcomms QFIL software on windows soon.
Above method is what testers used to install new firmware versions while no OTA mechanism was available.
eltmosen said:
@snortphome its not easily possible to brick this device.
Did you do the full recovery reflash using the provided EDL images?
Pro1X - Stock Android OS (Build Number: v2.1.2_20220707)
NEW Version of guide here Below the original text:(above inserted by EskeRahn) If youre reading this, it seems like you miss the good old Android OS or youve accidentally fried your PrawnX already! Dont worry! We have your back. The link below is the full build of the Pro1X stock Android OS (v2.1...
community.fxtec.com
To flash using EDL and Linux:
Install EDL-Tool by berkele
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
Put Pro¹ X in EDL mode using `adb reboot edl` when you got adb available. Else
Pro¹-X needs to be put in EDL mode manually. Hold power and vol + and vol - During boot and release all after android logo flashes up shortly and goes into a dark screen second. If it stays dark after you removed the combo, Prawn is in EDL mode.
If it is booting or showing fastboot, redo. I needed 5 tries first.
Check if the usb connected Pro¹ X is in EDL mode using lsusb, it should show:
`Bus 003 Device 011: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)`
Then become root or do the following with sudo each:
```
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram_unsparse0.xml patch0.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram1.xml patch1.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram2.xml patch2.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram3.xml patch3.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram4.xml patch4.xml .
edl --loader=prog_firehose_ddr.elf --memory=ufs qfil rawprogram5.xml patch5.xml .
```
If any of the commands get stuck, redo the finger combo and enter EDL again.
I did not need to do that since all went well with original cable and Pro¹ X not touched during flash.
reboot prawn with
`edl --loader=prog_firehose_ddr.elf reset reboot`
F(x)tec will release flashing instruction using Qulcomms QFIL software on windows soon.
Above method is what testers used to install new firmware versions while no OTA mechanism was available.
Click to expand...
Click to collapse
Hi, thank you very much for your thorough instructions!
I'm sure they will be very helpful to both me when I mess something up more in the future and to others! I was not aware that EDL mode was existant, I was solely using fastboot.
As for me, it wasn't fully bricked, I still had the stock recovery (boot_a and boot_b were flashed over), and after a bit of hunting around, I found a google drive link (on the thread you linked, actually!) for the stock android on the fxtec community forums, as well as links to Ubuntu touch and SailfishOS builds which I was able to flash and achieve a usable operating environment.
I'm now having quite a lot of fun with this phone!
I got mine in my hands now. It already comes bootloader unlocked.
blackknightavalon said:
I got mine in my hands now. It already comes bootloader unlocked.
Click to expand...
Click to collapse
Have fun! And backup your persist partition to not loose the attestation keys by chance.
eltmosen said:
Have fun! And backup your persist partition to not loose the attestation keys by chance.
Click to expand...
Click to collapse
I've lost count of how many soft bricks I've had to fix on OnePlus devices alone. As long as I can back up my internal storage I'll be just fine.
abtekk said:
If it makes you feel better, upon arrival, I plan on porting as many of the different Android flavours as I can over to the Pro1X, along with sources. This includes TWRP.
Click to expand...
Click to collapse
It does. I'm hoping I like the phone and it lasts for years. I don't expect to replace my Pixel 6, and I want to see what all these other os's do.
After trying to flash TWRP (by following this guide: https://www.thecustomdroid.com/root-oneplus-6t-guide/ ) my device would no longer boot to the OS,but (stock) recovery and fastboot modes worked, so I tried to fix it by flashing some Android 9 roms from https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-6t.3862516/ , and flashing a stock Android 10 boot.img (for some reason).
But my attemps at fixing it by flashing only made things worse, my current situation is as follows:
Device: Oneplus 6T (6/128)
Version (either Global or T-Mobile): Unsure
OxygenOS Version: Unsure, only know that it is Android 9
Bootloader: Unlocked
- Neither Recovery mode nor TWRP work
- Bootloader and Baseband versions show as empty
- I can only access Fastboot mode and EDL mode
- A power outage left my main pc (which had the drivers, permissions and backup i had been using, and need, to do this) a burning mess
- I´m currently using an old desktop computer i had stored (which has Windows 7), but it fails to recognize my device.
- I have installed and tried multiple versions of the Qualcomm, Oneplus, Adb and Android drivers, but it never recognizes it
- Windows doesnt allow me to manually select the drivers for the Unknown device as ¨the specified folder doesnt contain a software driver compatible with this device¨
- By searching the system and internet it always says that ¨the best software driver for this device is already installed¨
- Both of the above were tried with a disabled driver signature requirement
- When using it on the other PC, the msm download tool, it always said that the image didnt match the device, no matter which of the 13 versions I tried
- On my current PC, the msm download tool doesnt detect my device
I implore anyone that can provide any help or advise to do so, as I´ve already spent an entire week scouring the Internet (including the Oneplus and XDA forums) for any solution, but so far, nothing has worked. Have a good day and thank you for reading my post.
Hey man.
I'm a dude with no OnePlus 6T but have a OnePlus Nord N10. But I do know the really bad punch-in-the-gut feeling of not having a device work at all.
What does "fastboot reboot bootloader" show?? (Does your phone reboot to the bootloader upon that command being ran?)
Also did you try to flash the stock Android 9 boot.img that your device was updated to?
As for the MSM download tool, the last replies I've seen show that some people trying that on Win11 recently have got it working.
Also check if these work? https://www.thecustomdroid.com/oneplus-6-6t-unbrick-guide/
How to Unbrick Your OnePlus 6T When All Else Fails
When flashing files through TWRP, ADB, or Fastboot, there's a slight chance for things to go wrong. Whether it's user error related or something else entirely, it's always good to have a backup plan. In most cases, you'll be dealing with a semi-brick or soft-brick, which can usually be solved by...
oneplus.gadgethacks.com
Sorry if it sounds stupid but I want to try to help.
I really hope your phone gets fixed, man. Good luck!