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 and regular OP7TPRO here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus 7T Pro 5G McLaren bought from T-Mobile.
They can also be used to rollback your phone to a previous release of OOS if for some reason you want to go back to an older firmware
It will only work with 5G T-Mobile variant HD1925
You can download the following versions:
ANDROID 10:
10.0.13 HD61CB
10.0.16 HD61CB
10.0.19 HD61CB
10.0.27 HD61CB
10.0.34 HD61CB
10.0.35 HD61CB
10.0.36 HD61CB
10.0.39 HD61CB
10.0.40 HD61CB
10.0.41 HD61CB
10.0.42 HD61CB
Mirror for first and last MSMs: https://onepluscommunityserver.com/
ANDROID 11:
11.0.1.5 HD61CB
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
Specific to 10.0.27 and up
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 T-MO if it hasn't been automatically.
Power your device off.
Maintain volume up and volume down keys to get into Qualcomm EDL mode.
Plug your device to your computer using stock OnePlus cable.
Click on Enum to be sure your device is detected and press Start.
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Will this fix OTAs I couldn't receive after unlocking bootloader?
Yes. Mind it will however wipe all of your internal storage and relock bootloader automatically (but you shouldn't have to reapply for an unlock token if your bootloader was unlocked previously).
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.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.
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:
@omariscal1019 for getting 10.0.27 version from OnePlus
@a63548 for getting 10.0.19 version from OnePlus
An anonymous user for unblocking situation with OnePlus CS (they kept sending package meant for 7T T-Mobile)
@jhofseth for decryption of 10.0.19 tool
@xian1243 and @omariscal1019 for testing 10.0.13 version, @twinnfamous for testing 10.0.13 and 10.0.16 versions, @ntzrmtthihu777 for testing 10.0.13 , 10.0.16 and 10.0.19 versions, @DanDroidOS for testing 10.0.19 version, and @me2151 for testing 11.0.1.5 version.
@Titokhan for being a friend and providing inspiration in writing
@headsh0t95 for being a friend and suggesting me to request an access to upload files on AndroidFileHost now one year ago for my previous threads
@AndroidFileHost for the hosting
OnePlus for the device and OS
Related: [HD1925] [OP7TPROTMO] reserve.img dumps OTA fixer from @ntzrmtthihu777 for folks that want to get OTAs if they unlock their phone after using MSM tool
Woooooo!!! Let's hope it's the real deal. Downloading now so I can root in a bit
It's real and was tested extensively. We also used them to complete our reserve.img collection.
Nice work! I refuse to go any further than bootloader unlocking until I had a tested MSM recovery. Can't tell you how many times those saved my butt with previous 1+ phones.
I apologise in advance, but I do not see a link for the msm tool to flash zips in this post ? Can someone please link a copy of the correct msm tool so we can download it, please and thank you if there is a adb command that I'd have to run instead of msm tool please help me by listing a small guide of how to do it thanks
Excuse my lack of knowledge on the subject. Is this what we've been waiting for? I'm guessing no or very little experimenting was being done because nobody wanted to destroy their phone. But if I understanding correctly this will work like the one for the 6T only difference is we can't flash a global firmware (for the moment) if you royally f**k up this will save you. With this tool it should make experimenting with the device a lot less of an issue?
Justingaribay7 said:
I apologise in advance, but I do not see a link for the msm tool to flash zips in this post ? Can someone please link a copy of the correct msm tool so we can download it, please and thank you if there is a adb command that I'd have to run instead of msm tool please help me by listing a small guide of how to do it thanks
Click to expand...
Click to collapse
There's a button that has them all listed. There's three versions.
Joe199799 said:
Excuse my lack of knowledge on the subject. Is this what we've been waiting for? I'm guessing no or very little experimenting was being done because nobody wanted to destroy their phone. But if I understanding correctly this will work like the one for the 6T only difference is we can't flash a global firmware (for the moment) if you royally f**k up this will save you. With this tool it should make experimenting with the device a lot less of an issue?
Click to expand...
Click to collapse
More or less, but there simply is no global firmware for us to
convert to for this device (they could create one, I suppose).
This tool will fix just about any sort of brick we may encounter
during normal experimentation.
ntzrmtthihu777 said:
There's a button that has them all listed. There's three versions.
More or less, but there simply is no global firmware for us to
convert to for this device (they could create one, I suppose).
This tool will fix just about any sort of brick we may encounter
during normal experimentation.
Click to expand...
Click to collapse
I guessing there's a strong possibility of a global conversion hindering 5G?
I'm just glad there's a tool available to people that want to modify their phones and don't end up with a 900$ paperweight in the event something goes wrong.
Damn, I can't believe I didn't even think about unzipping the whole file lol figured it was just the phone firmware on those links , because there was only software versions listed haha thanks for your help guys! figured it out, download whatever version you want to flash, unzip file accordingly, all the proper files you'll need will be in the extracted folder install directions above, thanks again!!!
You sir are a lifesaver! I was having too many issues with my phone after some of the tweaks, and was stuck on the .16 software version. Now I'm updated to .19 and ready to break the phone again!
One plus 7T 5G Mclaren pro T-Mobile
OMG, I just used this tool and it worked. I can't believe it. Thank you so much. I thought my device was toasted.
Any chance of updating the post to include the latest update 10.0.25?
adit07 said:
Any chance of updating the post to include the latest update 10.0.25?
Click to expand...
Click to collapse
Might happen, might not.
If it doesn't happen this however won't be an issue as you can rollback anyway by using.
Mind that I don't make these tools so don't have any control on how they could be updated
What if you connect your phone and it does not even show up as the bulk driver in device manager. I have literally bricked it to the point that only edl mode shows up. Can anyone please show me the light?
djohnson1618 said:
What if you connect your phone and it does not even show up as the bulk driver in device manager. I have literally bricked it to the point that only edl mode shows up. Can anyone please show me the light?
Click to expand...
Click to collapse
While booting up the phone hold I believe volume up and plug it in while doing that it should just remain on a black screen after that open msmtool and see if it's connected if it is then do what you would normally do for msmtool. It took me a couple of tries to get it to recognize with this phone compared to my 6T
Lost
Does anyone know what it should say once I press Enum
djohnson1618 said:
Does anyone know what it should say once I press Enum
Click to expand...
Click to collapse
Read the OP carefully.
So My One Plus One 7t Pro Mclaren edition (TMO) is bricked beyond belief. It only reboots into Fastboot mode. From CMD when ADB devices command is typed in it says no devices found. When I look in device manager when connected it says Android Bootloader Interface it does not show any of the drivers to update. I tried using MSM. My phone does not make a connection. Can anyone offer any assistance to help me get this phone back and working? Or am I just stuck with an expensive paperweight.
djohnson1618 said:
So My One Plus One 7t Pro Mclaren edition (TMO) is bricked beyond belief. It only reboots into Fastboot mode. From CMD when ADB devices command is typed in it says no devices found. When I look in device manager when connected it says Android Bootloader Interface it does not show any of the drivers to update. I tried using MSM. My phone does not make a connection. Can anyone offer any assistance to help me get this phone back and working? Or am I just stuck with an expensive paperweight.
Click to expand...
Click to collapse
As said in the OP, you need to turn your device off and enter in Qualcomm EDL mode.
Maintain power button until your device screen goes off, wait 20 seconds, maintain volume up and down keys, plug your device to your computer using OnePlus original cable and use MSM tool.
Related
From what little bit of reading I have done it looks as if the MSM Tool is the oneplus version of odin. Is that correct? If it is where can <i get my fat little fingers on it from a site we can trust, I can't seem to find it here on XDA.
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 and OP Nord here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus 8T.
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:
KB05AA tools (international firmware):
ANDROID 11:
OOS 11.0
OOS 11.0.1.2
OOS 11.0.4.5
OOS 11.0.5.6
OOS 11.0.7.9
Mirror for first and last MSMs: https://onepluscommunityserver.com/
KB05BA tools (european firmware):
ANDROID 11:
OOS 11.0
OOS 11.0.1.2
OOS 11.0.4.5
OOS 11.0.5.6
OOS 11.0.7.10
Mirror for first and last MSMs: https://onepluscommunityserver.com/
KB05DA tools (indian firmware):
ANDROID 11:
OOS 11.0
OOS 11.0.1.2
OOS 11.0.4.5
OOS 11.0.5.6
OOS 11.0.7.9
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Tips:
While crossflashing does not seem to break your /persist unlike on 8-series, it is advised that you back it up before attemting to do so as fingerprint reader may give an error related to enrollment issue. You can do so by using dd if=/mnt/vendor/persist of=/sdcard/persist.img (you must have root access, which is not something I'm going to explain here) and moving it to your computer/cloud.
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.
Click on Target button and select O2 while using global tool or India while using indian tool or EU when using european tool.
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 ~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 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.
Why is my device getting in Qualcomm crashdump mode in spite of a successful download?
Your unit was most likely manufactured after March 9th 2021, see https://forum.xda-developers.com/t/...ice-to-oxygenos.4180837/page-14#post-84789741 for reference. You therefore need to use HydrogenOS 11.0.7.12 MSM to recover your device linked at https://www.oneplusbbs.com/thread-5886794-1.html (mirrored at https://mega.nz/file/O8UySbgR#cXGlHkdA_7CYEhKIrek9zzAEwJ7Vx1D5BZdemnPlvGE by @pikatenor ). Getting new OxygenOS MSM tools is nowadays impossible unless you own the device it is meant for, so OP will not be updated to add new OxygenOS MSM tools allowing to workaround this issue. Feel however free to reach out to me in DM if you would like to get told how to maximise your chances to obtain one.
Credits:
@viperbjk for KB05AA and KB05BA OOS 11.0 files
@LLStarks for KB05AA OOS 11.0.1.2 file
@FullOfHell for testing 11.0 KB05AA tool and downgrade possibility
Votton for providing a server as an alternative mirror
OnePlus for the device and OS
Click to expand...
Click to collapse
Hmm android 12 i cant find ;-;
Kenora_I said:
Hmm android 12 i cant find ;-;
Click to expand...
Click to collapse
Hi, I am unsure how above post of mine relates to this thread, as this is Nord N200 forum (post is about 8T). Not to mention N200 (and 8T) didn't receive A12 yet.
I believe they were trying to guide me as to what they had been able to locate at this point.
alarmdude9 said:
I believe they were trying to guide me as to what they had been able to locate at this point.
Click to expand...
Click to collapse
Well, that makes sense. Sorry Im not a OP user 0~0
My post above has for the NORD too so.
Kenora_I said:
My post above has for the NORD too so.
Click to expand...
Click to collapse
The OnePlus Nord and OnePlus Nord N200 5G are different devices.
I don't think there's MSM tool for N200
Please upload this tool if you have it so i can fix my phone .. at this point t-mobile, metro pcs and god knows what they all were able not only to fix their phone but install the unlocked rom without the bloatware .. Honestly i don't get why OP refuses to release this .. or maybe they have but its not posted here ..
So if you bought your phone from oneplus.com and have the unbricking tool .. please upload it or tell me how you managed to fix your phone
Contact OnePlus support, and request a remote session to repair your phone.
If they set one up, they'll send you a link to download the MSMDownload Tools ahead of time.
So far everyone with unlocked version has been told to mail their phone in, rather than doing the remote session. Once someone gets the remote session, they'll be able to upload the MSMDownload Tools.
edale1 said:
Contact OnePlus support, and request a remote session to repair your phone.
If they set one up, they'll send you a link to download the MSMDownload Tools ahead of time.
So far everyone with unlocked version has been told to mail their phone in, rather than doing the remote session. Once someone gets the remote session, they'll be able to upload the MSMDownload Tools.
Click to expand...
Click to collapse
already went thru that and instead of sending my phone in chose to wait for the tool.. looks like i made a huge mistake and now is too late to send it in ... but thanks for suggesting
Also waiting for an ops for the unlocked variant - I have a theory that converts between variants without unlocking BL, but without the ops it can't be verified.
I believe One Plus is not releasing their MSM tool specifically because it could be used to convert variants to unlocked / retail. They have refused multiple board members, myself included, to utilize the tool to remotely fix broken devices.
Dimitrimem, check the unbrick thread for my instructions on how to fix phones using fastboot and a super.img or fastbootd and the OTA.
Un-bricking my Nord N200
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system...
forum.xda-developers.com
oCAPTCHA said:
I believe One Plus is not releasing their MSM tool specifically because it could be used to convert variants to unlocked / retail. They have refused multiple board members, myself included, to utilize the tool to remotely fix broken devices.
Dimitrimem, check the unbrick thread for my instructions on how to fix phones using fastboot and a super.img or fastbootd and the OTA.
Un-bricking my Nord N200
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system...
forum.xda-developers.com
Click to expand...
Click to collapse
Bootloader is locked so fastboot is not an option ..
Do you have the unlock code bin file?
If so do the following, because booting in fastboot itself will give you an error saying you cannot unlock the bootloader, you most boot into recovery, fastboot is not recovery it's considered the master recovery Incase if the Android recovery fails or you flashed the wrong file to the wrong partition.
Winnower Amber said:
Do you have the unlock code bin file?
Click to expand...
Click to collapse
I don't
You'll need to give that information. Check the box, your serial number should be on it.
Does Android recovery work?
Winnower Amber said:
You'll need to give that information. Check the box, your serial number should be on it.
Click to expand...
Click to collapse
I threw the box away .. let me see if I can find it in my mail with oneplus
Winnower Amber said:
You'll need to give that information. Check the box, your serial number should be on it.
Click to expand...
Click to collapse
The only thing I have from my mail with oneplus is the IMEI number from the form they made me fill in for the remote session only that later on they told me they don't have the files(msm) for my phone
If IMEI and serial number are the same let me know and I'll post thst here
The most you could do is get the unlock code bin. Then wait 7 days for a reply, flash your device with the TMobile msm, and then follow the TMobile to oem, that should do it.
If you need to reach me for stuff like this, I am available on discord via the xda,
Winnower Amber said:
Does Android recovery work?
Click to expand...
Click to collapse
From the screen itself. No it boots back to the error .. but I was able to get into recovery by pressing volume up and down
Winnower Amber said:
The most you could do is get the unlock code bin. Then wait 7 days for a reply, flash your device with the TMobile msm, and then follow the TMobile to oem, that should do it.
Click to expand...
Click to collapse
I have the fully paid variant.. so I don't need the unlock code... That's t-mobile.. my bootloader is locked or OEM is locked
Your phone comes preloaded with an emergency boot chip called Qualcomm download mode. Use the TMobile msm tool to flash your device back to factory, then you can essentially do what you need. To get back to oem.
I keep forgetting to quote reply I hate this lol.
Winnower Amber said:
Your phone comes preloaded with an emergency boot chip called Qualcomm download mode. Use the TMobile msm tool to flash your device back to factory, then you can essentially do what you need. To get back to oem.
Click to expand...
Click to collapse
My phone does not work with the MSM tool for TMobile... already tried that ( others already tried it so I'm not alone)
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 is the EDL package (also known as MSM tool or unbrick tool) that can revive a bricked OnePlus Nord N200.
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
DE17AA tools (global firmware):
ANDROID 11:
OOS 11.0.3
Mirror: 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:
@drfsupercenter for testing 11.0.3 version on his device
OnePlus for the device and OS
I can confirm this works for the "unlocked" version that I bought at Best Buy. Thanks for posting!
Here is a question
Can I convert T-Mobile version to global this way?
mingkee said:
Here is a question
Can I convert T-Mobile version to global this way?
Click to expand...
Click to collapse
No, you can't convert T-Mobile variant to unlocked one with this tool.
Some_Random_Username said:
No, you can't convert T-Mobile variant to unlocked one with this tool.
Click to expand...
Click to collapse
The scenario is like 8T.
I remember somebody alter the project code to cross flash.
I have to find out
Wait... We finally got MSMTools for the Unlocked variant? When'd/How'd this happen?
THANK YOU!!!! My paperweight is a phone again!
edale1 said:
Wait... We finally got MSMTools for the Unlocked variant? When'd/How'd this happen?
Click to expand...
Click to collapse
I bricked my phone messing with it after the recent update they pushed out to official phones which broke 5g. Maybe more people than I did, I was pretty happy until then.
edale1 said:
Wait... We finally got MSMTools for the Unlocked variant? When'd/How'd this happen?
Click to expand...
Click to collapse
I don't know how he got it, but it does work.
mingkee said:
Here is a question
Can I convert T-Mobile version to global this way?
Click to expand...
Click to collapse
I'd imagine it would be the same as when I tried to flash the T-Mobile MSMTool to my unlocked phone. It just said wrong model and wouldn't continue.
It seems like oneplus finally released the msmtool for global/unlocked version.
Follow this guide to flash global/international unlocked firmware to metro/tmo version with locked bootloader (convert metro/tmo version to an unlocked international/global version):
Flash international ROM to Tmobile/Metro w/ locked bootloader
MAJOR UPDATE: Managed to flash Global stock rom to the MetroPCS variant Pros: Stock Oneplus and everything works Cons: OEM unlock is still greyed out Before you go any further: THERE IS NO ROOT FOR THIS DEVICE WITH A LOCKED BOOTLOADER (YET)...
forum.xda-developers.com
Basically, you need to change a few lines inside "settings.xml" about the project id so that it would not complain about non-matching project id/wrong model when cross flashing global rom to metro/tmo hardware.
After crossflashing global rom to metro/tmo verion of hardware, it can then take international ota so it will behave exactly like the unlocked version.
The only difference is about unlocking bootloader, and you will still need to go through the oneplus/T-Mobile portal to request the bootloader unlock bin to unlock the bootloader, while the true unlocked version doesn't need.
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 is the EDL package (also known as MSM tool or unbrick tool) that can revive a bricked OnePlus Nord N200.
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
DE17AA tools (global firmware):
ANDROID 11:
OOS 11.0.3
Mirror: 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:
@drfsupercenter for testing 11.0.3 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
great thanks lol
googlephoneFKLenAsh said:
It seems like oneplus finally released the msmtool for global/unlocked version.
Follow this guide to flash global/international unlocked firmware to metro/tmo version with locked bootloader (convert metro/tmo version to an unlocked international/global version):
Flash international ROM to Tmobile/Metro w/ locked bootloader
MAJOR UPDATE: Managed to flash Global stock rom to the MetroPCS variant Pros: Stock Oneplus and everything works Cons: OEM unlock is still greyed out Before you go any further: THERE IS NO ROOT FOR THIS DEVICE WITH A LOCKED BOOTLOADER (YET)...
forum.xda-developers.com
Basically, you need to change a few lines inside "settings.xml" about the project id so that it would not complain about non-matching project id/wrong model when cross flashing global rom to metro/tmo hardware.
After crossflashing global rom to metro/tmo verion of hardware, it can then take international ota so it will behave exactly like the unlocked version.
The only difference is about unlocking bootloader, and you will still need to go through the oneplus/T-Mobile portal to request the bootloader unlock bin to unlock the bootloader, while the true unlocked version doesn't need.
Click to expand...
Click to collapse
I changed everything related to project ID and everything in that post, but mine still says
{
"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"
}
justauserthatusesaphone said:
I changed everything related to project ID and everything in that post, but mine still says
View attachment 5652955
Click to expand...
Click to collapse
The project code should be for N200 not other models
mingkee said:
The project code should be for N200 not other models
Click to expand...
Click to collapse
That's what I put.
I even control+f'd it for anything that says "2083c" or "ID" and "project", yet it still somehow got that error.
justauserthatusesaphone said:
I changed everything related to project ID and everything in that post, but mine still says
View attachment 5652955
Click to expand...
Click to collapse
Open up settings.xml from the Global decrypted folder and change the following 5 values to match the settings.xml from Metro and hit save
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
googlephoneFKLenAsh said:
Open up settings.xml from the Global decrypted folder and change the following 5 values to match the settings.xml from Metro and hit save
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
Click to expand...
Click to collapse
ok i'll do that in a bit and i'll probably release it here.
googlephoneFKLenAsh said:
Open up settings.xml from the Global decrypted folder and change the following 5 values to match the settings.xml from Metro and hit save
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
Click to expand...
Click to collapse
well
okay i give up
justauserthatusesaphone said:
View attachment 5653443
well
okay i give up
Click to expand...
Click to collapse
You didn't follow the instructions correctly.
Re-read the instructions, especially the editing project id step.
The error message mentioned "image 2083c", which means there are lines from 2083c ops not replaced with values from 20818 ops yet.
You need to replace all those lines:
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
in the settings.xml from unlocked 2083c ops with the values in the settings.xml from metro/tmo 20818 ops. (better to use copy&paste to avoid typos).
Also you need to copy the modified unlocked/global ops to the msmtool folder of the metro/tmo version and replace the original metro/tmo ops.
I believe 2083c is the unlocked version and 20818 is the metro/tmo version.
googlephoneFKLenAsh said:
You didn't follow the instructions correctly.
Re-read the instructions, especially the editing project id step.
The error message mentioned "image 2083c", which means there are lines from 2083c ops not replaced with values from 20818 ops yet.
You need to replace all those lines:
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
in the settings.xml from unlocked 2083c ops with the values in the settings.xml from metro/tmo 20818 ops. (better to use copy&paste to avoid typos).
Also you need to copy the modified unlocked/global ops to the msmtool folder of the metro/tmo version and replace the original metro/tmo ops.
I believe 2083c is the unlocked version and 20818 is the metro/tmo version.
Click to expand...
Click to collapse
I can't tell what's wrong.
XML:
<BasicInfo Project="20818" TargetName="SM4350" Version="dre8t_10_O.05_210713" MemoryName="ufs" GrowLastPartToFillDisk="true" LogEnable="false" LogPositionIndex="-1" DelayStartTime="0" UseGPT="true" CheckImage="false" CheckHwVersion="false" NeedUsbDownload="true" BackupPart="false" BackupPartId="" ChipType="1" FactoryID="20818US" MinToolVersion="5.0.3" SupportHwID="false" SupportRfID="false" SupportPrjID="false" CheckRfVersion="false" CheckProjectVersion="false" SkipImgSHA256Check="true" ParamVersion="1" SkipParamProcess="false" ModelVerifyVersion="0" ModelVerifyPrjName="" SkipCheckHWVerByCustFlag="false" DefaultCleanFRP="true" FrpPartitionLabel="frp" CarrierID="0" AutoDetectDDR="false" DPPackingVer="0" ProjectSoftwareIDSupport="false" ATOBuild="false" SkipMultiImageIdentify="true" RandomPadding="anxKohPaJKUq2kVPIbXgD7RXNa96iUeGFZa1GzbYH6OIorf7RCneJCCgkJlSlN" ModelVerifyRandom="RG8sc2EUOj51TeCw" ModelVerifyHashToken="F9417334897C488DEA1DA5AC787906F743E85C17B47EB9669FFE96F11529D33C" Applicant="Unknown" Hostname="rd-build-77" BuildTime="1631716601" ApplicantIP="not sure if this is sensitive" />
Everything you listed is changed, the unlocked ops is also put into the tmobile msm
for example, here's the tmobile one
XML:
<BasicInfo Project="20818" TargetName="SM4350" Version="dre8t_10_O.05_210713" MemoryName="ufs" GrowLastPartToFillDisk="true" LogEnable="false" LogPositionIndex="-1" DelayStartTime="0" UseGPT="true" CheckImage="false" CheckHwVersion="false" NeedUsbDownload="true" BackupPart="false" BackupPartId="" ChipType="1" FactoryID="20818US" MinToolVersion="5.0.3" SupportHwID="false" SupportRfID="false" SupportPrjID="false" CheckRfVersion="false" CheckProjectVersion="false" SkipImgSHA256Check="true" ParamVersion="1" SkipParamProcess="false" ModelVerifyVersion="0" ModelVerifyPrjName="" SkipCheckHWVerByCustFlag="false" DefaultCleanFRP="true" FrpPartitionLabel="frp" CarrierID="1" CarrierNoneEnable="true" AutoDetectDDR="false" DPPackingVer="0" ProjectSoftwareIDSupport="false" ATOBuild="false" SkipMultiImageIdentify="true" RandomPadding="CQLTBL0oxs4BM2pdtK1y8Q1rvzgUtd033KWDfU1dM3mh3bKuwJs4jrtcqa6iB7lERIP4kOf5RRmS16MxPDz74tjvRq" ModelVerifyRandom="RG8sc2EUOj51TeCw" ModelVerifyHashToken="F9417334897C488DEA1DA5AC787906F743E85C17B47EB9669FFE96F11529D33C" Applicant="Unknown" Hostname="rd-build-74" BuildTime="1626183302" ApplicantIP="eeeeeeee" />
You are a godsend. Thank you so much, this is exactly what I needed!!
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
AndyYan said:
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
Click to expand...
Click to collapse
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
PsYk0n4uT said:
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
Click to expand...
Click to collapse
Try prepending 0s?
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
PsYk0n4uT said:
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
Click to expand...
Click to collapse
Tried adding zero on front and back of serial it just tells me invalid serial
PsYk0n4uT said:
Tried adding zero on front and back of serial it just tells me invalid serial
Click to expand...
Click to collapse
Chatting with OnePlus hasn't yielded anything so far
Just a tip, because in my infinite forgetfulness I wasted an hour last night trying to figure out why I was getting the error, fastboot could not open target HAL.
Remember that you must request the unlock code from fastboot, not fastbootd. Which is what you will boot into if you issue adb reboot fastboot.
So here's a quick step by step.
1.Enable usb debugging. 2. Connect your device and allow access for the computer. My device asks if I want it to charge or transfer files. Select transfer files/Android auto and then use adb start-server. May have to unplug the USB cable and reconnect. Select "always allow this device/PC".
3. Issue "adb devices" to make sure your connected.it should list your device by it's serial number. If not then try unplugging the device and revoke adb authorizations in dev options and toggle USB debugging off and back on, may even need to reboot the device to get it to connect after doing this.
4. If your device is listed under devices go ahead and issue "adb reboot fastboot"
5. Once rebooted issue "fastboot devices" and make sure the device is listed again.(If not listed make sure you have your driver's installed correctly and fastboot is installed correctly, may need to install Android SDK into same folder as fastboot)
6.You can select English or whatever language if you want but it doesn't seem necessary.You are in fastbootd mode you will see if you DO select a language.
So from here issue"fastboot reboot bootloader" device will reboot and you will have scrollable option at the top beginning with a big green START at the top. This is regular fastboot And where you wanna be to get your unlock code for submitting to Oppo for your unlock token.
7. Issue "fastboot oem get_unlock_code"
8. It should return the info you need, you will also need your IMEI number when submitting so be sure to copy that down.
you can copy and paste the unlock code into notepad or Word and delete out the extra stuff so your left with just the two lines of your unlock code as one single contiguous string of numbers.
8. Go to the link listed by OP and submit the required info. And wait for what seems like forever.
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
PsYk0n4uT said:
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
Click to expand...
Click to collapse
Simply "adb reboot bootloader". You won't need fastbootd until GSIs (which I already did ofc).
Thanks, definitely a quicker way to get to fastboot. I guess I wasn't sure if you could reboot directly. Seems maybe I was confusing an older device where you had to reboot to fastboot then "fastboot reboot fastboot" to get to fastbootd for a whole different reason.
This one goes directly to fastbootd when you "adb reboot fastboot"
Nice catch.
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
I'm not really sure to be honest, this is my first OnePlus device and just trying to contribute anything I can to get the N20 section up and going as I make progress with the device.
Just a quick search though turns up this and maybe it could be of use if you can still access the bootloader.
the current image(boot/recovery) have been destroyed
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip. After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g...
forum.xda-developers.com
Someone mentions extracting the boot.img from stock image and flashing it. I would imagine it should work for you if the stock firmware can be found and circumstances are similar. Maybe at least a start. Wish I could be of more help, maybe someone else can chime in that knows more.
Try Linux, maybe a live dist. if your on a windows machine that won't recognize it just to get it into a state that you can work with it again.
Just an idea, I don't want to steer you wrong as i still have a lot to learn
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsettinghav
Click to expand...
Click to collapse
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
Click to expand...
Click to collapse
I want to try and help but I'm so new it's sketchy I don't want to say something and get bashed
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Fyi according to a recently made friend who also had the 7 digit serial issue, they were told by OnePlus their dev team is working on an OTA update that will resolve the serial number issues. I'm not sure how that's going to work but I saw the email between them and Oppo support
I guess this must be a widespread issue that they feel is cheaper to invest the amount of money it takes for r&d to come up with a fix than it was to replace a few devices or attempt to do remote repairs.
But this also makes me wonder what avenue they will take to correct the issue.
Also I wonder if someone with the right skillset could gather enough bootloader unlock codes along with the unlock tokens, serial, IMEI, pcba etc.. maybe the algorithm their using to generate the codes could be broken. I'm no crypto expert or math genius either, but if we have the variables to the equation minus one but have the answer, isn't this pretty simple almost pre-algebra?
I mean I guess their not worried about enough people being brave enough to give out sensitive info like that. But maybe Im just ignorant of the complexity of these algorithms.
64 digit key on one end
T-Mobile bought sprint and they have T-Mobile sims no. But I understand that sprint is still a somewhat seperate company (tried to buy a T-Mobile phone and it would not activate on my sprint account. So I bought this from the sprint side of the T-Mobile site so I knew it would work but I assume this is a sprint phone and not a T-Mobile phone so this method would not work.
Can anyone confirm this?
PsYk0n4uT said:
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Click to expand...
Click to collapse
okay peep theres a way i put my oneplus into efu mode, hold both vol up and down then put usb c in continue to hold u should hear PC recognize it
So, before i do it, would deleting the modemst1/modemst2 partitions still let me bypass the t-mobile sim lock and let me unlock the phone like it did on the old oneplus phones?
Flashed a patched boot.img and lost modems. Anyone willing to post the modems? Are they device specific like a device partition?
Sim locked and trying to recover. No radios are working
They let a lot of problems go on. Explain to me why their software is locked. It's pretty easy to actually understand what happened OnePlus is trying to charge us money to go to support people to get our phones taken care of but that's silly to even think of.
maamdroid said:
Explain to me why their software is locked. It's pretty easy to actually understand what happened OnePlus is trying to charge us money to go to support people to get our phones taken care of.
Click to expand...
Click to collapse
What is locked?
Both bootloader and edl are unlocked ( bootloader unlockable via adb ? ) You don't have to contact customer support or anything?
Rstment ^m^ said:
What is locked?
Both bootloader and edl are unlocked ( bootloader unlockable via adb ? ) You don't have to contact customer support or anything?
Click to expand...
Click to collapse
MSM tool to recover from any serious error
Appreciative said:
MSM tool to recover from any serious error
Click to expand...
Click to collapse
Is this a MediateK phone?
I might be wrong then, I am assuming Qualcomm edl is usually unlocked?
Rstment ^m^ said:
Is this a MediateK phone?
I might be wrong then, I am assuming Qualcomm edl is usually unlocked?
Click to expand...
Click to collapse
SnapDragon 8g1. The 10 pro has edl test points and the 10T can boot into edl as well. But without an MSM tool, it's not worth the trouble. They require live authentication to sign the download and install. People are able to bypass the initial login for the msm tool but the next step has not been defeated yet. At least not publicly on xda.
My understanding is the tool verifies login and then gets a key to sign with. There is some speculation that it may use multiple checks during the flash so one key isn't enough. There was also mention that the msm tool binds to the Mac address of your nic and will fail if it's not on the whitelist.
That means you must send your phone back to OP if you brick outside of what fastboot can handle. I returned the 10T to get a 9P. While preparing to send it back, I locked the 10T bootloader back up before swapping boot images so I sent them back a brick on accident. . But, that's the problem. It's that easy and you're without a phone for a few weeks. I've also read that OP handles China different in that they charge for certain services. There was recently a development in the "edl tool" thread where someone from China was unbricked remotely but that agent had a valid login to sign the install.
I am planning to hop over to Nothing Phone after my 9P dies. I certainly won't be back to OP as long as they ship that ColorOS "OxygenOS" hybrid garbage and no MSM tool. With an MSM, we would at least get good rom development to have a better/real OOS experience.
Also, I've been with OnePlus for years. Until recently, I haven't had to use their customer service since they merged with Oppo. It got much worse. OnePlus is dead
Appreciative said:
SnapDragon 8g1. The 10 pro has edl test points and the 10T can boot into edl as well. But without an MSM tool, it's not worth the trouble. They require live authentication to sign the download and install. People are able to bypass the initial login for the msm tool but the next step has not been defeated yet. At least not publicly on xda.
My understanding is the tool verifies login and then gets a key to sign with. There is some speculation that it may use multiple checks during the flash so one key isn't enough. There was also mention that the msm tool binds to the Mac address of your nic and will fail if it's not on the whitelist.
That means you must send your phone back to OP if you brick outside of what fastboot can handle. I returned the 10T to get a 9P. While preparing to send it back, I locked the 10T bootloader back up before swapping boot images so I sent them back a brick on accident. . But, that's the problem. It's that easy and you're without a phone for a few weeks. I've also read that OP handles China different in that they charge for certain services. There was recently a development in the "edl tool" thread where someone from China was unbricked remotely but that agent had a valid login to sign the install.
I am planning to hop over to Nothing Phone after my 9P dies. I certainly won't be back to OP as long as they ship that ColorOS "OxygenOS" hybrid garbage and no MSM tool. With an MSM, we would at least get good rom development to have a better/real OOS experience.
Also, I've been with OnePlus for years. Until recently, I haven't had to use their customer service since they merged with Oppo. It got much worse. OnePlus is dead
Click to expand...
Click to collapse
Wow thanks for the explanation... Never owned OP and just assumed they'd offer access EDL / bootloader unlike other manufacturers...
Doss nothing phone offer edl access without third party approvals? Current Nothing phone is bad pairing of hardware... definitely not on my list unless there's access to edl?
Rstment ^m^ said:
Wow thanks for the explanation... Never owned OP and just assumed they'd offer access EDL / bootloader unlike other manufacturers...
Doss nothing phone offer edl access without third party approvals? Current Nothing phone is bad pairing of hardware... definitely not on my list unless there's access to edl?
Click to expand...
Click to collapse
I'm not positive about NP edl mode. I do know they have a method to unbrick available, using fastboot and critical unlock to flash any/all partitions if I remember right. And the full source tree is also available. It's also 'believed' that Nothing will make reasonable efforts for developers because of Carl Pei. It is believed he was the main reason for OP's dev friendly nature prior to 2020/oppo merge/his departure.
I wrote to Nothing and asked them to provide us dev friendly devices so we can fall in love and get our friends and family on Nothing devices just like we did with OnePlus. They replied and said they look forward to making the device of our dreams in the future.
I know they need a little time to see what works and what sells. I want to support but it won't be the NP1. Maybe the 2 for support. I imagine my 9p will last a good while, my 5T is still a great phone after all these years. It can even play cod mobile still