yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 Pro Guides, News, & Discussion] giacomowrc:
Good evenig, I've a few question about the msm tool.

I've a chinese op7 pro (GM1910) with international rom and root. Now I'm selling my device and I've back to stock.

I downloaded the MSM tool for AA (international) device, is it correct? Is it fully compatible with my GM1910?

My device don't stay in EDL mode for more of 10 sec, but if i always keep pressed both volume keys the device stays in EDL mode.

What I'm thinking to do is going in EDL mode and always keeping keys pressed, open MSM tool, release the keys and after press start. In this way I've not to rush the procedure.

I checked with a test, in this way MSM tool says that device is connected.

At this point I release the keys and I've 10 second to press start, before it disconnect.

Is it all correct?
[OnePlus 7 Pro Guides, News, & Discussion] Bobthahog:
I used the tool in this thread and flashed a global ROM onto my T-Mobile OnePlus 7 pro and turned it into a dual SIM. So right now I have it rooted with TWRP but if I ever go to sell it I'm going to keep it as a T-Mobile model but with dual SIM.

https://xdaforums.com/oneplus-7-pro/how-to/tool-tool-one-driversunlocktwrpfactory-t3930862
[OnePlus 7 Pro Guides, News, & Discussion] thedeadfish59:
IDK if its solvable or not, but suddenly my op7pro crashed and wasnt turning on, managed to go on EDL using key combo, its not flashing completely, giving SHA256 error, and ends with failing, tried almost all msmtool, device stays this way, phone was unrooted, bootloader locked, gm-1910 chinese, with international installed

however, download gets completed if i uncheck SHA256 check, but it never boots, feeling pissed, am sorry to mention you but any thoughts or comments on this @Some_Random_Username ?

My issue is kinda similar with this guy https://forums.oneplus.com/threads/...no-button-response-at-all-sha256-fail.1175413

With SHA check:View attachment 5153381

Without SHA check, but never boots up

View attachment 5153405
[OnePlus 7 Pro Guides, News, & Discussion] ayesse:
The SHA256 error means that the package is corrupted. Click "Verify" and check if it's ok, if it's not you have to download it again
[OnePlus 7 Pro Guides, News, & Discussion] thedeadfish59:
haha, nah its not that mate, i did verify, did SMT mode too (ik very well that will f up my IMEI), no luck, and do check the link i provided there, the guy who faced same issue too :)

Add: My Internet speed is decent and stable enough, 70Mbps, and i downloaded almost all msmtool available for guacamole, but same result with all of em
[OnePlus 7 Pro Guides, News, & Discussion] Some_Random_Username:
Added OOS 10.3.7/10.0.10 MSM tools

Sorry no idea, you may need an RMA
[OnePlus 7 Pro Guides, News, & Discussion] H4X0R46:
Am I the only one beginning the think OnePlus abandoned this device early in it's life cycle?
[OnePlus 7 Pro Guides, News, & Discussion] thedeadfish59:
Understandable, thanks for replying!
[OnePlus 7 Pro Guides, News, & Discussion] zyguo:
Why can't see this thread
[OnePlus 7 Pro Guides, News, & Discussion] priyabratsahoo021:
View attachment 5211599

it stays like that for 10 - 15min....please help
[OnePlus 7 Pro Guides, News, & Discussion] Soumy1234:
Is there a way to only flash the boot partition with this tool/edl mode? My OP7P only boots to BL and isn't detected by fastboot. I want to retain or at least extract my data so I was hoping to flash a stock boot img to then boot twrp hopefully.
[OnePlus 7 Pro Guides, News, & Discussion] Some_Random_Username:
Unfortunately this tool does not allow to flash only boot partition.
[OnePlus 7 Pro Guides, News, & Discussion] Soumy1234:
Dang. Thank you nonetheless.
[OnePlus 7 Pro Guides, News, & Discussion] 1poweruser1:
thanks for the tool

i booted op7 in edl (connect cable while holding vol+ and vol- with phone off), installed edl drivers with a windows update search (they show up as additional updates in win10) and ran msmtoolkit

when "download complete" showed up in msm i pressed stop

after the phone rebooted i ran a local os update with latest ota full zip

i unlocked the bootloader by going to developer settings and enabling oem unlock then booted the phone in bootloader (vol- and power) and unlocked with

fastboot oem unlock

i noticed that everything gets flashed to slot_a and since I wanted to flash lineage i ran

fastboot getvar current-slot
fastboot --set-active=_b

if it doesnt work try

fastboot --set-active=b

so when i booted twrp

fastboot boot twrp.img

i pressed "format data" and lineage flashed to slot a
[OnePlus 7 Pro Guides, News, & Discussion] Some_Random_Username:
Added OOS 10.3.8 (global) MSM
[OnePlus 7 Pro Guides, News, & Discussion] Fateh Ahmed:
Can I use the global 10.3.8 msm package on my Eu Gm1913 op7p?

if yes, is it safe to do so?
[OnePlus 7 Pro Guides, News, & Discussion] Tnbh9:
when you will add Android 11 to msm tool?
[OnePlus 7 Pro Guides, News, & Discussion] HippoMan:
I only have limited access to a Windows PC, and I'm wondering: has anyone found a way to get the unbrick module for 10.3.8 (i.e., guacamole_21_P.32_210127.zip) to be flashable via linux instead of via the Windows-based MSM tool? I don't want to have to purchase a Windows machine simply to use for very infrequent unbricking of my Android device, and I don't want to have to purchase something like Parallels and then also purchase a Windows license.

Also, I tried this under wine a while ago, and it didn't work.

Thank you very much.
[OnePlus 7 Pro Guides, News, & Discussion] Toutatis_:
Linux user here. I tried using MSM tool on a Windows 10 VM, I managed to get the phone recognized while booted in EDL mode but for some reasons I keep getting the "Sahara Communication Failed, Please try again after power off phobe (PBL:6)" error after clicking on "Start".

Tried switching between USB 2 and 3 ports in the VM settings, holding Volume Up + Volume Down buttons for a longer period of time (~20 seconds), to no avail. I never got the actual restore process starting after 10 or 15 attempts, always the same error.

Maybe that's a VM limitation.
[OnePlus 7 Pro Guides, News, & Discussion] teflon252:
bro use bootcamp..and Windows 10 is free man...download it from Microsoft...skip serial...and do what u gotta do...i do ALL my modding on my MacBook Pro...
[OnePlus 7 Pro Guides, News, & Discussion] neogodless:
Nevermind.
[OnePlus 7 Pro Guides, News, & Discussion] HippoMan:
Thank you very much. However, there is no such thing as Bootcamp under Linux, and I don't want to buy a Mac.

I'll figure out some sort of dual boot thing for Linux. I wish I didn't have to do this, simply to reflash my hosed OnePlus 7Pro every now and then, but I guess it's the only option.
[OnePlus 7 Pro Guides, News, & Discussion] neogodless:
This started because of bugs in 11.0.0.2, and I miss 10.3.8 and hope to find a way back. You can probably skip the long explanation of how I ended up here...

Spoiler content hidden.

So now I'm trying to get the MSM tool to work on my GM1915 US/International OnePlus 7 Pro in EDL mode. Took a while but at this point I am able to start the MSM process, enum my COM port as "Qualcomm HS-USB QDLoader 9008" ... but I tried to use this 10.3.8 installer from the first post here, and I get an error message after the first few steps of the process that "Device not match image." Do I need a 11.0.0.2 image / MSM install tool instead? I don't really want to go back to 11, but I could probably deal with it for now, and then maybe I can make a working Magisk image?

EDIT: OK yes I think the OP here omits GM1915. I found a T-Mobile Stock MSM tool and installed that. I am going through setup now - I think this is Android 9 / Oxygen OS 10? Not what I want the phone to land out, but hopefully there's a clear path from there to 10.3.8? -- Yeah this is OOS 9.5.10.GM31CB (Android 9) and... since it's T-Mobile-ized now, my SIM does not work. So I'll have to figure out how to re-International-ize this. (It was done before I bought it on used.)

So my big new question as I scour the forums... is it possible for someone with no T-Mobile SIM to SIM unlock this phone once more? *sigh* what a day.
[OnePlus 7 Pro Guides, News, & Discussion] neogodless:
<snip>

Ugh so I followed this thread on T-Mobile to International conversion which worked for that purpose, but my phone still says NO SIM CARD. Apparently going from International to T-Mobile firmware somehow re-locks it to a T-Mobile SIM??! :cautious::cry:

EDIT: I was able to run the June 2019 thread's MSM T-Mobile to International and it worked like a charm. My SIM started working again, and it offered me the 10.3.8 update which is what I'm on now. Great success!
[OnePlus 7 Pro Guides, News, & Discussion] freecity01:
Thanks for sharing your experience. I was having the exact same issue with my t-mobile variant of the OP7P and your post saved me!!
[OnePlus 7 Pro Guides, News, & Discussion] Justinpfla407:
what \\\\\\

can you please tell me which t mobile tool you used?
[OnePlus 7 Pro Guides, News, & Discussion] TermoZour:
How did you get the Qualcomm driver to install? In my case after I right click on the device in Device Manager and select the folde with the .cab file, Windows says it can't find any driver for my device.

If I untick "Include subfolders" then it tells me "The location you specified does not contain any .INF files".

If I unarchive the .cab in a folder and pick that, it tells me "Windows found drivers but encountered an error. The system cannot find the file specified."

On another note, after using some setup.exe for the qualcomm driver I found online, it detected my device as QDLoader 9008 but the MSM tool would get stuck at "param preload" for over 600 seconds!! Clicking stop won't actually stop the device and I am unable to quit MSM tool. I have to restart Windows in order to try again.

What's wrong here?

EDIT: After 5 hours of painstakingly trying to bring my phone back to life I found what the issue was. THE DRIVERS.

I tried to use the MSM tool on my Windows PC with drivers found online. As I've said before, I couldn't install the driver linked in this thread.

By chance I tried another Windows PC (with version OLDER than 20H2 - can't remember exactly which) and it offered to install Qualcomm driver from Windows Update. It detected my phone correctly and the process was done in about 10 minutes. I got my phone back!

If there is any way to pack that driver so I can share it here for others to use, let me know! I'd be more than happy to share another driver which worked in my case.
[OnePlus 7 Pro Guides, News, & Discussion] dialfonzo:
Started my journey by installing LineageOS 18.1 and then tried to install TWRP which at one point deleted my recovery and i was in a loop...

Many thanks for this post / software / solution it UnBricked my device
[OnePlus 7 Pro Guides, News, & Discussion] 5star02707:
Thanks, tried the fastboot method and that just got me in to a bootloop so had to use MSM tools for a complete reset. Again thanks for this ;) Always saves my OP devices
[OnePlus 7 Pro Guides, News, & Discussion] didymus:
Man, I am trying to install OOS 10.3.8, but the *only* thing I can get the phone recognized as by my computer is `Kedacom USB Device` via the driver suggested by Window's Update. I can't get Device Manager to even recognize any of the "Qualcom" ones. I unpacked the cab too.

Anyway, I guess I'm going to just research `Kedacom` in this thread and hope I misspelled it the first time, lol.
[OnePlus 7 Pro Guides, News, & Discussion] mobilityguy:
I just bought a GM1915 7 Pro on Swappa. The seller did me the "favor" of upgrading to OOS 11, and I've been trying to do anything that would get me back to OOS 10 since 11 just keeps serving up one bug after another. Nothing I've tried so far has worked.

TWRP... 3.5.2 and 3.5.0 won't boot through fastboot, just sticks on the "fastboot mode" screen until I fastboot reboot back to system. So, no TWRP.

Magisk... won't install because there's no boot.img to modify in the OTA package. So, no root.

MSM/EDL.. fails because it never gets past the "preparing..." state (I waited two hours). Even after all that time in the blank screen EDL mode it still boots back to OOS 11. So, no clean restore. I'd almost prefer if it bricked at this point.

I just came across this thread and noticed the T-Mobile 1915 variant is not in the list of models supported by the unbrick tool. Other people have said that they used it but it turned their 1915 to the international model, and they had SIM card problems.

I should be able to get this phone SIM unlocked by T-Mobile - I'm a long time customer. My question - if I SIM unlock and use the international MSM tool, will I end up with a working phone running 10.3.8 that supports my T-Mobile SIM? Will I be able to restore the system and data partitions of my daily driver OP7 Pro and end up with a functional duplicate of my main phone?

I thought OnePlus was supposed to be friendly to this kind of operation. I never had a problem with my OP3T or my other OP7 Pro which is still on 10.3.8. Has OOS 11 locked people out of modding their OnePlus phones?
[OnePlus 7 Pro Guides, News, & Discussion] mobilityguy:
OK, no responses to my questions yet, so I'll ask the most important question by itself. I'm trying to boot a custom recovery so I can do something - anything - with this GM1915.

I've downloaded TWRP 3.5.0 and 3.5.2 for the device, and the Lineage custom recovery. I have the bootloader unlocked and USB debugging set.

I boot into Fastboot, get the usual Fastboot screen , and on my PC I type "fastboot boot {recovery}.img.

The PC says "downloading boot.img...".

The phone displays the words "Fastboot mode" and the OnePlus logo, and a few seconds later reboots into OOS.

What am I doing wrong? The phone is useless to me if I can't install anything.

Thanks.
[OnePlus 7 Pro Guides, News, & Discussion] Hyperling:
I've been getting this same "The system cannot find the file specified" problem from Device Manager and FINALLY figured out how to get up-to-date Windows 10 to work!!

Assuming the device is already plugged into the computer in EDL mode:

After the prompt gets the error from trying to load the cab file it will offer to search Windows Update to find a driver. After one or two of saying "Yes, please search" in Device Manager it will open the Windows Update section of Windows Settings and there's a little "Optional Updates" section that's collapsed. If you go to it, it offers this driver:

View attachment 5413865

Check the box for the driver, allow Windows Update to install it, then Device Manager should properly have the Qualcomm device under Ports instead of Other Devices. MSM should now recognize the device and be able to flash it!

View attachment 5413863

I finally have my device working again!! :D

View attachment 5413867
[OnePlus 7 Pro Guides, News, & Discussion] -=Guybrush=-:
I've searched for them everywhere to no avail: are there MsmDownloadTool packages for the OnePlus 7 Pro 5G too? I have scoured the latest 10.0.10 OxygenOS OTA rom, extracted the contents from payload.bin and then tried to understand if there is a way to build an .ops package from there but unfortunately it doesn't seem a feasible way to follow. I have to say that OnePlus modding is quite poorly documented and that's a pity considered how unlocking the bootloader is easy for example. Just to make things even worse, the 7 Pro 5G has the worst support overall, more or less zero. :( Thanks in advance for your help.
[OnePlus 7 Pro Guides, News, & Discussion] -=Guybrush=-:
Just to better explain what I was looking forward, I know how to make a search and I had already found the thread with the recovery package for the guacamoleg (OP 7 Pro 5G) but it's an old package, on Pie while I was on R and I fear downgrading (though through EDL) could make things even worse.

I've also found this extremely useful repository containing unbrick packages for many (if not all the recent ones) OnePlus models BUT, given that OnePlus provides only OTA packages, I'm sure that a way to build those EDL recovery packages from them should certainly exist and knowing it would be of great help generally speaking.
[OnePlus 7 Pro Guides, News, & Discussion] HippoMan:
Has anyone been able to get the OOS 10.3.8 MsmDownloadTool working with a Windows VM running under Linux ubuntu 20 virtualbox ?

When I run in this environment, the program doesn't see the device being connected via the USB port.

In Linux itself, the machine can easily see the device via fastboot and adb.

If anyone has gotten MsmDownloadTool to work in a virtual Windows environment running under Linux, could you post step-by-step instructions of how you got that to work? If not with virtualbox, perhaps with a different VM manager?

Thank you very much.
[OnePlus 7 Pro Guides, News, & Discussion] blas4me:
You can do everything from command-line in Linux. I've done it a couple of times, you'll have to google the commands, I lost a auto script that I made. If you hold volume up+down, should put you in Diag mode. It's been a while for me, but I think I was able to use MSM with wine, it only needed DiretX drivers to run, and wine can handle that. If you can extract the payload.bin from OOS stock, you can use those img's to restore your phone from a hard brick. You could take a look here. https://www.getdroidtips.com/unbrick-oneplus-device/
[OnePlus 7 Pro Guides, News, & Discussion] budakthegil:
oneplus 7pro GM1915 is what version to use..already try international n europe not work..eror device mismatch or device not match
[OnePlus 7 Pro Guides, News, & Discussion] Some_Random_Username:
Added OOS 11.0.5.1 MSM tool to OP.
[OnePlus 7 Pro Guides, News, & Discussion] hammered58:
I tried it, works good!
[OnePlus 7 Pro Guides, News, & Discussion] Tnbh9:
No Mirror found in android file host please help
[Pixel C Q&A, Help & Troubleshooting] JustDarren:
Hi all,

I've seemed to have bricked my Pixel C. I tried flashing the stock ROM after installing LineageOS.

I wiped everything using fastboot (recovery, data, system, bootloader, cache, etc) and now I am just stuck with fastboot.

When I try and use

fastboot boot twrp.img

, I get the following:

creating boot image...
creating boot image - 12974080 bytes
Sending 'boot.img' (12670 KB) OKAY [ 0.320s]
Booting FAILED (remote: 'image verification failed')
fastboot: error: Command failed

If I try and flash recovery using

fastboot flash recovery twrp.img

, I get the following:

Sending 'recovery' (12668 KB) OKAY [ 0.347s]
Writing 'recovery' FAILED (remote: 'unsupported command')
fastboot: error: Command failed

I did have this error before, but I had TWRP and used fwtool to fix it. But I have no OS, no recovery and I am getting these issues with fastboot.

I have tried various cables, my drivers are up to date and my software is up to date. I have also tried flashing the stock image from Google but that just does the following:

Sending 'bootloader' (16384 KB) OKAY [ 0.445s]
Writing 'bootloader' FAILED (remote: 'unsupported command')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.016s
--------------------------------------------
Bootloader Version...: ***********************************************************
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.010s]
Checking 'version-bootloader' FAILED

Device version-bootloader is '***********************************************************'.
Update requires 'Google_Smaug.7900.139.0'.

fastboot: error: requirements not met!
Press any key to exit...

Is this tablet totally bricked or can anyone help me out?

Thanks
[Pixel C Q&A, Help & Troubleshooting] rhmanoa:
Hi, can you give more details on how you proceeded
[Pixel C Q&A, Help & Troubleshooting] tschmid:
Have you tried this?

https://download.dirtyunicorns.com/?device=dragon

Google smaug vendor image

Gesendet von meinem Nexus 6P mit Tapatalk
[Pixel C Q&A, Help & Troubleshooting] JustDarren:
Doesn't work. It's not the image that's the issue anyway, its the command being unrecognized:

Sending 'bootloader' (16384 KB) OKAY [ 0.438s]
Writing 'bootloader' FAILED (remote: 'unsupported command')
fastboot: error: Command failed
[Pixel C Q&A, Help & Troubleshooting] matonka007:
Bricked.

I solved same problem but I was able to boot system and used this in adb:

fwtool vbnv write dev_boot_fastboot_full_cap 1

You must somehow boot recovery and flash system. Without recovery you are screwed.
[Pixel C Q&A, Help & Troubleshooting] JustDarren:
Yeah. I have been searching for hours but it seems impossible without recovery.
[Pixel C Q&A, Help & Troubleshooting] tschmid:
Tried this?

https://xdaforums.com/pixel-c/help/bootloader-reports-unlocked-unable-to-t3483513

Gesendet von meinem Nexus 6P mit Tapatalk

---------- Post added at 06:13 PM ---------- Previous post was at 06:11 PM ----------

And this?

https://xdaforums.com/pixel-c/help/flash-factory-image-t3599367/amp/

Gesendet von meinem Nexus 6P mit Tapatalk
[Pixel C Q&A, Help & Troubleshooting] JustDarren:
Yes but with no joy.

Fastboot doesn't work at all so I cannot even boot to recovery. Therefore, I am unable to use ADB to fix fastboot
[Pixel C Q&A, Help & Troubleshooting] tschmid:
Sad, maybee this?

https://xdaforums.com/pixel-c/help/flashing-to-stock-android-npd90g-twrp-t3424863

Gesendet von meinem Nexus 6P mit Tapatalk
[Pixel C Q&A, Help & Troubleshooting] JustDarren:
Doesn't work. But AGAIN... I cannot access recovery for ADB
[Pixel C Q&A, Help & Troubleshooting] tschmid:
Sorry no more ideas

Gesendet von meinem Nexus 6P mit Tapatalk
[Pixel C Q&A, Help & Troubleshooting] matonka007:
Are you sure that your BL is unlocked? Try to lock it and unlock it again.

FAILED (remote: 'image verification failed')

This error looks like it can not boot unsigned image. But I do not know why.
[Pixel C Q&A, Help & Troubleshooting] JustDarren:
Bootloader is definitely unlocked. I have tried locking and unlocking multiple times
[Pixel C Q&A, Help & Troubleshooting] TheInitialCommand:
This is a longshot, but I was getting very similar errors trying to do anything. All this happened on a Windows 10 Laptop using the Google Drivers. I tried it again on a Mac Book Pro running Catalina and it worked just fine with latest platform tools.

Perhaps you want to try a Linux or Mac if you have access to one, or try a Linux live edition on your current machine, something like this:

https://ubuntu.com/tutorials/try-ubuntu-before-you-install#1-getting-started

Just worth a shot. Still an awesome tablet to lose just yet. Hope it is not too late for you.
[Pixel C Q&A, Help & Troubleshooting] JustDarren:
Thanks for the suggestion. I'll give it a go and let you know what happens
[Pixel C Q&A, Help & Troubleshooting] TheInitialCommand:
Good luck!
[Pixel C Q&A, Help & Troubleshooting] JustDarren:
No joy. Still getting unknown command. Even tried manually erasing and formatting the partitions with no luck. Thanks for the suggestion though.

Really bummed out because I still love this tablet. Shame I bricked it ?
[Pixel C Q&A, Help & Troubleshooting] golvellius:
I have similar problem ..

you need to extract the rom zip file, inside you have img files ...

a) you need tablet in fastboot mode . i have made the process in linux. also i have downloaded this rom

ryu-opm8.190605.005-factory-25b457f3.zip downloaded from google.

b) Tablet needs to be unlocked .. for that you need to do fastboot oem unlock .. and after you return to fastboot mode.

And here you have my steps ..

All made in linux but if you use windows remove the command "sudo" it ahould work

1) sudo fastboot flash bootloader bootloader-dragon-google_smaug.7900.139.0.img

2) sudo fastboot reboot bootloader

3) sudo fastboot flash boot boot.img

4) sudo fastboot flash cache cache.img

5) sudo fastboot flash recovery recovery.img

6) sudo fastboot flash system system.img

7) sudo fastboot flash vendor vendor.img

8) restart the tabler pressing button.

Check if these works for you ..

bye