Develop Bugs

How to set device tampered back to false?

I will explain how to set the device tampered back to "false" on the Wileyfox Swift.
Required:
7z
WFS.7z (https://drive.google.com/file/d/0B6Ge199bCD5_NF9RWGhVLVhxajA/view?usp=sharing)
Windows 7 or 8
Driver Signature Enforcement disabled
Step 1: Brick the device on purpose
Hold Volume Up button+Volume Down button while plugging in USB
You should be see QHS_USB BULK in Device Manager
S
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Step 3 : Install QPST provided in WFS.7z
I think its pretty straight forward
Step 4: Flash Firmware
Open QFil
Select Port and choose your device if not already chosen
Select Flat Build
Programmer Path must be prog_emmc_firehose_8916.mbn in the Maincode folder from WFS.7z
Build Path should automatically appear
Hit load XML.
Click rawprogram_upgrade.xml
Click patch0.xml
Click Download
Once done remove and reinsert battery
Step 5: Verify Tampered:False
boot into fastboot
type the following:
fastboot oem device-info
and it should say Device tampered : false and Device Unlock : False
NB: If you get a SaharaDownload fail or something just remove battery and USB for 5 seconds. Plug battery in. Then plug USB in.
NB: I do not accept any responsibility for damaged devices or anything. You point your finger at me and I will laugh at you
If it works don't hesitate to donate me a cup of coffee
PayPal : [email protected]

yasteellutch said:
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Click to expand...
Click to collapse
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".

I don't think ur swift is bricked

when puting battery in jut get the screen "wileyfox"; recovery does not start (vol- and pwr) but fastboot mode ist working (vol+ and pwr). so it's not bricked?
so I repeat step 1 but still in windows 7 device manager having "Other Devices -> Android" with no yellow triangle.

I get SaharaDownload fail. Removing battary is useless. What else can i try? Thanks in advance

Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download

yasteellutch said:
Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download
Click to expand...
Click to collapse
I try and try do it again but i have only got sahara fail again and again.....

void2000 said:
I try and try do it again but i have only got sahara fail again and again.....
Click to expand...
Click to collapse
Upload a screenshot

yasteellutch said:
Upload a screenshot
Click to expand...
Click to collapse
Probably I have to use a special cable?

See it gets the SharaVersion right so I'm guessing that phone is in a correct state. The problem there could be that it didn't decompress properly. Maybe the integrity of your decompressed WFS.7z is not intact. Go to Android One(2nd Gen) dedicated page. I got help there. I guess all you need is to look there.

Maybe u didn't installQPSt right or the driver is a issue. I flashed stock like 3 days ago and it works perfectly

cyaneo said:
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".
Click to expand...
Click to collapse
Hey @cyaneo. If you still have the Yellow Android triangle this is because your drivers aren't installed correctly. I tried it. But that also means your fastboot is working.

Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?

void2000 said:
Probably I have to use a special cable?
Click to expand...
Click to collapse
Hi,
This is my first post. (active lurker previously) hopefully its not too late.
In my experience on other device running 8916, a sahara failure can be overcame by holding the power button when entering download mode. (E.g: if you enter download mode by pressing and holding vol+/- simultaneously and plugging in usb cable, try holding the power button as well when you plug in the cable). This is normally a result of battery too low.

After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop

Pak0St said:
After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop
Click to expand...
Click to collapse
Lol I agree. This baby took some hits. I clocked it to 1.6 at stable. At 1.9 she became instable and started crashing #YeahITakeRisks

xfile087 said:
Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?
Click to expand...
Click to collapse
Of course there is. Don't get me wrong I understand your point. But you need to remember there are log files and a bunch of other stuff lying around if you fastboot. When you use QFil it basically rewrites all the partitions thus no logs. I returned my first Swift with the IMEI issue and they gave me a new one in a week

Hi,
my Swift is also Bricked.... that means no bootloader boot or etc. i tried to flash the phone with this method but no success. my error with QFIL is this
COM Port number:20
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
bei QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
bei QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Thanks for response

Error
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse

vadimnew said:
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse
Click to expand...
Click to collapse
You made a mistake @vadimnew

[OPN105G][OOS TMO BE88CB] Unbrick tool to restore your device to OxygenOS

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, 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 N10 bought from T-Mobile.
As this is a carrier specific MSM, it will only work with BE2028 model with build tag BE88CB
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

I need this for the T-Mobile Variant.
- Works great! Thanks.

I learned a ton of hard lessons with this device. My maiden voyage of custom ROM and hackery. Now, unfortunately, I have to resort to a power greater than my own mind to restore my little N10 5G to sanity. Thank you for this post, and wish me luck,
Click to expand...
Click to collapse

Will the above work on the TMobile varent?

mbl1979 said:
Will the above work on the TMobile varent?
Click to expand...
Click to collapse
Duh

una ar oem aluna solucion

Can i use this to downgrade from 11 to 10..?

Fr4n©\<y said:
Can i use this to downgrade from 11 to 10..?
Click to expand...
Click to collapse
Yes. Moreover when boot to Android 10 and connect to WiFi it can be updated back to Android 11 ( through native update interface, did not check but got a prompt )

@Some_Random_Username
What if I have Unlocked Bootloader + TWRP + patched boot - will unbrick flashing restore these partitions to factory defaults ?
Will I lose bootloader unlock after flashing ?
Thank you

.

Testing

Would this also work on the Metro version?

[OPN105G][OOS METRO BE88CF] Unbrick tool to restore your device to OxygenOS

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, 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 N10 bought from Metro by T-Mobile.
As this is a carrier specific MSM, it will only work with BE2025 model with build tag BE88CF
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

Thank you.

I used it yesterday after I screwed up my Nord N10 5g. I hadn't used msn since last year on another device I sold, so had to be real careful getting back in the saddle.
It worked fine - no issues - except it took 500 seconds not just 300 - lol.

So I got everything downloaded and installed once I get the nord in edl mode it shows as bulk driver I tried to install the cab through driver update and my pc doesn't see it what can I do to fix that

The URL with links to files doesnt seem to have the current version of BE2028 - T-Mobile - 11.0.1.BE88CB
D:

the problem i encountered was it showing up as unknown usb device (device descriptor request failed) in device manager

Hi, I have bricked my Nord N10 Metro PCS while installing magisk patched boot. The phone is stuck in fastboot mode. Kindly assists. Do you have the T Mobile Android 11 Firmware? I was on Android 11 with August security patch

umaga2012 said:
Hi, I have bricked my Nord N10 Metro PCS while installing magisk patched boot. The phone is stuck in fastboot mode. Kindly assists. Do you have the T Mobile Android 11 Firmware? I was on Android 11 with August security patch
Click to expand...
Click to collapse
If you bricked it, then you have to unbrick using the provided tool here, it's only android 10, though. Afterwards you must do OTA.

andreas__ said:
If you bricked it, then you have to unbrick using the provided tool here, it's only android 10, though. Afterwards you must do OTA.
Click to expand...
Click to collapse
You've saved my life brother. The tool has worked perfectly. I am able to update to A11 via OTA

Some_Random_Username said:
Reserved
Click to expand...
Click to collapse
Bro on behalf on all us dumbasses slash semi noobs I thank you

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 N10 bought from Metro by T-Mobile.
As this is a carrier specific MSM, it will only work with BE2025 model with build tag BE88CF
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:
Votton for providing a server as an alternative mirror
OnePlus for the device and OS
Click to expand...
Click to collapse
Hello. I have OnePlus Nord N10 5G model BE2029 and cannot get it unbricked. MSMTool fails with error "Param failed". Can you point me to the right ROM, I have been struggling whole day and still no luck.

My friend, I don't know how to thank you for this. After the update that I did on my phone about 1 month ago, I have been going crazy with having problems sending texts and making calls whether on 5G or 4G. I got together with oneplus customer service today to revert back the OS, for me and it was no help. This has been perfect!!!! thank you so much!!!

My OPN105G is forever stuck on "waiting for device" in both status of communication and status of last communication... i tried like over 20 times. the device manager shows it fine as 9008.

Hello quick question,,, will this lock my bootloader?

Nathan1616 said:
Hello quick question,,, will this lock my bootloader?
Click to expand...
Click to collapse
Yes. It puts you back to default stock.
As long as you have your unlock.bin file, you can unlock your bootloader again though.

Spent four hours trying volume buttons and adb method. Nope... Don't waste your time. This works for I'm assuming 1 out of every nobody on planet Earth.
Your browser is not able to display this video.

MSM has readback function which can grab stock boot for patching

works likea charm much love and thanks from barberton . ohio

Question Completely Bricked! Someone help

One plus 9pr complete brick. Cannot access fastboot or recovery. Will not turn on and when I plug in only shows a connect a chargwer screen. It is charged. I cannot get msm tool to connect either.

What led up to this point?

We'll need more info than this:
Are you using a Windows computer?
Is it Windows 10?
Have you plugged in USB via USB port on the computer or USB hub? (Should always plug directly into the computer)
Windows 10 has driver signature checks on by default, the Qualcomm drivers are not signed so you need to disable signing before trying to use MSM tool : https://www.tenforums.com/tutorials...river-signature-enforcement-windows-10-a.html (I usually use option 2, BCDEdit)
Here's the Qualcomm EDL drivers : https://www.androidfilehost.com/?fid=14943124697586335873
You need to press both VOL buttons and POWER to get into EDL mode, make sure you choose the correct assignment from the top "TARGET" dropdown in the MSM tool too and make sure it's the correct MSM tool for your region/phone. They're all available from here
There's a decent guide here
There's a video here for OnePlus 8/8 Pro but it's the same technique (remember to give him a like if he helps you out ) :
If the MSM tool doesn't show "CONNECTED" on any COM port then keep the cable connected and try rebooting the phone back into EDL mode again, it will eventually show up.

Question Bricked flashing Lineage and MSM will not work

Long story short, I was having tons of bugs in A12 from camera rebooting phone to not receiving phone calls so I decided to flash LOS 18.1 and ended up bricking my device presumably because I didn't downgrade to OOS11 beforehand. Currently, I can only enter fastboot and LOS recovery. MSM tool will not read my device at all. I can see it in device manager as some extremely generic QUS...... device and when I try to update the drivers, it crashes. I have tried USB-C, USB 3.2, USB-3, and what is presumably a USB 2.0 port to no avail. Is there anyway to flash OOS 11 from fastboot?

Use these drivers for the Qualcomm device, reboot the phone with both volume buttons and power.
Then try the MSM tool (remember to choose the regional version on the top), don't connect via a USB hub, connect directly to your computer (I usually find USB 2 is better than USB 3
If you get an error in the MSM Tools when you try to flash then reboot the phone back into EDL mode while the MSM tool is still open and attempting to flash, it'll usually pick up properly after the reboot.
If you still have problems then try disabling driver signature verification : https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/

djsubterrain said:
Use these drivers for the Qualcomm device, reboot the phone with both volume buttons and power.
Click to expand...
Click to collapse
SWEET BABY JESUS THANK YOU FOR THIS
I was trying to do this with the 64-bit drivers and was consistently seeing "Param preload failed" after 9 seconds exactly.

ddxBrandon said:
SWEET BABY JESUS THANK YOU FOR THIS
I was trying to do this with the 64-bit drivers and was consistently seeing "Param preload failed" after 9 seconds exactly.
Click to expand...
Click to collapse
Up and running again?

djsubterrain said:
Up and running again?
Click to expand...
Click to collapse
I had the LE2127 unlocked and rooted (after learning about the MSM tool, the model differences, modem headaches, etc.)
My ultimate goal was to flash Lineage on it and use a custom kernel for battery life. But apparently I'd have to re-flash T-Mobile's firmware version NON-HLOS.BIN after every OTA, and frankly that's a pain in the ass.
I was trying to use the T-Mo MSM tool to get it back to stock locked, but that was stopping me. Finally got it done. T-Mo wouldn't take the phone back. Got a Pixel 6. The 9 Pro is on "free" promo anyway, so I might start messing with it more, or sell it / donate it to a developer.

Send it back to oneplus they have tools even better than msm.

djsubterrain said:
Use these drivers for the Qualcomm device, reboot the phone with both volume buttons and power.
Then try the MSM tool (remember to choose the regional version on the top), don't connect via a USB hub, connect directly to your computer (I usually find USB 2 is better than USB 3
If you get an error in the MSM Tools when you try to flash then reboot the phone back into EDL mode while the MSM tool is still open and attempting to flash, it'll usually pick up properly after the reboot.
If you still have problems then try disabling driver signature verification : https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Click to expand...
Click to collapse
Your instructions worked for Windows 11. I had to reboot with driver signature verification disabled in order for MSM tool to recognize the phone as connected.
Thank you.