Database Info

[OP7][OOS 10.3.8 GM57AA & .0.10GM57BA] 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 and OP6 and OP6T, here are the EDL packages (also known as MSM tool or unbrick tool) that can revive a bricked OnePlus 7.
They can also be used to rollback your phone to a previous release of OOS.
You can download the following versions:
GM57AA tools (International firmware):
ANDROID 9:
9.5.6
9.5.7
9.5.8
ANDROID 10:
10.0.1
10.0.2
10.0.3
10.3.0
10.3.1
10.3.2
10.3.5
10.3.6
10.3.7
10.3.8
Mirror for first and last MSMs per Android version: https://onepluscommunityserver.com/
GM57BA tools (European firmware):
ANDROID 9:
9.5.6
9.5.7
9.5.8
ANDROID 10:
10.0.2
10.0.3
10.0.4
10.0.5
10.0.7
10.0.8
10.0.9
10.0.10
Mirror for first and last MSMs per Android version: https://onepluscommunityserver.com/
It supports GM1900, GM1901, GM1903 and GM1905 models.
You can upgrade to newer versions of OOS using files linked in thread https://forum.xda-developers.com/oneplus-7/how-to/oneplus-7-repo-oxygen-os-builds-t3937152 originally made by @SkandaH
Instructions:
Power your device off
Maintain volume up and volume down keys to get into Qualcomm EDL mode.
Launch MsmDownloadTool V4.0.exe.
Click on Enum to be sure your device is detected and press Start.
Wait ~300 seconds
Enjoy your brand new device
FAQ:
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.
My device doesn't stay in EDL mode for more than 10 seconds
Some units can have this problem and there isn't a lot of things to do to fix that, except being fast after plugging your phone to your computer.
EDIT 7th August 2019: There is apparently a "one-off" solution to this problem available at https://forum.xda-developers.com/showpost.php?p=80021106&postcount=21 . I would like to investigate more on that but sadly don't own the device so can't confirm it.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked in first part of this FAQ.
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.
Credits:
@SkandaH for inspiration in writing
@headsh0t95 for suggesting me to request an access to upload files on AndroidFileHost a few months ago for my previous threads
@AndroidFileHost for the hosting
OnePlus for the device and OS

Reserved

Reserved

Credits:
@SkandaH for inspiration in writing
@headsh0t95 for suggesting me to request an access to upload files on AndroidFileHost a few months ago for my previous threads
@AndroidFileHost for the hosting
Votton for providing a server as an alternative mirror
OnePlus for the device and OS

THIS IS AMAZING! Thank you so much. Worked like charm. No need for installing extra drivers under Windows 10 or going through some other script madness. Really smooth and easy. Thanks!
Just got my OP7 yesterday and accidentally bricked it by formatting the vendor partition in TWRP. So I was searching for an Unbrick tool but there was none.
Thank god that you uploaded this just last night and saved my OP7 from an early death
In order to get the EU firmware back I simply have to flash the OxygenOS for my region and that's it, right? - Worked via TWRP
Another question though: I can create files on data when I am on the phone and I can also copy files over via USB-OTG. However when I try to push files via adb it tells me that the partition is read-only. Any idea how to fix this?

Cool it's also almost the latest version. I think I can close the other thread now.

devnerd said:
THIS IS AMAZING! Thank you so much. Worked like charm. No need for installing extra drivers under Windows 10 or going through some other script madness. Really smooth and easy. Thanks!
Just got my OP7 yesterday and accidentally bricked it by formatting the vendor partition in TWRP. So I was searching for an Unbrick tool but there was none.
Thank god that you uploaded this just last night and saved my OP7 from an early death
In order to get the EU firmware back I simply have to flash the OxygenOS for my region and that's it, right? - Worked via TWRP
Another question though: I can create files on data when I am on the phone and I can also copy files over via USB-OTG. However when I try to push files via adb it tells me that the partition is read-only. Any idea how to fix this?
Click to expand...
Click to collapse
Hi, I sadly have no idea about how to fix the adb push thing

Thanks for the response thiugh. I fixed it yesterdy evening.
First I tried to update the system to the EU version via local upgrade but it didn't let me as I was already on a "newer" version. So it interestingly classifies the Global version newer as the EU version for somehow.
So I went for TWRP and flashed the EU version to both slots (not even sure if that was necessary). After a reboot I was back on the EU version and also the adb push worked again. So not sure what was done to the data partition during the update, but it just worked

Some_Random_Username said:
FAQ:
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 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.
My device doesn't stay in EDL mode for more than 10 seconds
Some units can have this problem and there isn't a lot of things to do to fix that, except being fast after plugging your phone to your computer.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked in first part of this FAQ.
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.
Click to expand...
Click to collapse
Hello friends, automatic restart solution after 10 seconds when connecting EDL mode to use MsmDownloadTool:
https://forum.xda-developers.com/showpost.php?p=80021106&postcount=21

tURkOsANsE said:
Hello friends, automatic restart solution after 10 seconds when connecting EDL mode to use MsmDownloadTool:
https://forum.xda-developers.com/showpost.php?p=80021106&postcount=21
Click to expand...
Click to collapse
Updated FAQ to include it, thanks for pointing it out

Added OOS 9.5.8 GM57AA unbrick tool

So how i understand this make my device how "of box"?
Where security? If i lost my phone 14yo boy can make MY device HIS...
WTF OP...

3a6ygb said:
So how i understand this make my device how "of box"?
Where security? If i lost my phone 14yo boy can make MY device HIS...
WTF OP...
Click to expand...
Click to collapse
Lol. Security means your data isn't visible for 14yo boy because of encryption blabla. Nobody said it's security if he is able to steal your phone and format the storage with your personal data.

Kollachi said:
Lol. Security means your data isn't visible for 14yo boy because of encryption blabla. Nobody said it's security if he is able to steal your phone and format the storage with your personal data.
Click to expand...
Click to collapse
Thx
Ok. But it really make full format all phone?
If i use this msm rom i have clear device without user data, without frp etc?

3a6ygb said:
Thx
Ok. But it really make full format all phone?
If i use this msm rom i have clear device without user data, without frp etc?
Click to expand...
Click to collapse
Yes, it wipes everything off your device and make it like the first day of unboxing. But you can do the same by going into android settings and make a factory reset.

I need msm download tool for latest oxygen os 10.0.1 ,is anyone is here who give me the link of it for oneplus 7?

Prinçe çharming ap said:
I need msm download tool for latest oxygen os 10.0.1 ,is anyone is here who give me the link of it for oneplus 7?
Click to expand...
Click to collapse
For OOS 10.0.1 there is no version. Use the latest 9.5.8 to get back on pie then update to stable 10.0.1 or stay on pie :good:
Sent from my OnePlus7 using XDA Labs

GraveDigger176 said:
For OOS 10.0.1 there is no version. Use the latest 9.5.8 to get back on pie then update to stable 10.0.1 or stay on pie :good:
Click to expand...
Click to collapse
I already have that version of msm tool but i want it for android 10.

Prinçe çharming ap said:
I already have that version of msm tool but i want it for android 10.
Click to expand...
Click to collapse
There is no version for Android 10 as far as I know
Sent from my OnePlus7 using XDA Labs

GraveDigger176 said:
There is no version for Android 10 as far as I know
Click to expand...
Click to collapse
Do u know how to extract .ops file of msm tool?

Question Phone Hard Bricked in EDL mode

Hey!
Soooooo, I tried to update my OS to the most recent while rooted, but I accidentally locked my boot loader, bricked the software, tried to unbrick it, then later got hard bricked in EDL mode. I have tried using the MSM tool for the global version of the Oneplus 9 but it always ended up saying that the image didn't match or something (IDK the thing was in F’ing Chinese). This hard brick has gotten so bad that I cant even hold Vol up + Power to hard restart it. The screen just doesn't come on any more but is still recognized by my computer as a Qualcomm device. Does anyone know of a fix that doesn't include installing the Indian loader?
Model # LE2115 (OP9 Global)

I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for you.

chinbags said:
I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for you.
Click to expand...
Click to collapse
I had to do the same thing. I am using a LE2113 and managed to brick my phone in a way where only EDL could save it. I came from the latest OOS (colorOS) firmware and tried to flash LineageOS when everything went south. I tried to use the Oneplus 9 EU MSM tool but this one did not work for me. Since there is no official EU MSM for the LE2113 the only way I could repair it was by using the EU OnePlus 9 pro msm firmware. It only worked with the "use lite firehose" option for me. After that was done I unlocked the bootloader once again and flashed OOS (Android 11) for OnePlus 9 again. This was the way I got the original firmware back on my device although I do not think it would've been possible to relock the bootloader at this point.
Straight after that I once again flashed lineage and everything is working fine now. Certainly a shady approach but it is the end result that counts I'd say.

Nullifii said:
Hey!
Soooooo, I tried to update my OS to the most recent while rooted, but I accidentally locked my boot loader, bricked the software, tried to unbrick it, then later got hard bricked in EDL mode. I have tried using the MSM tool for the global version of the Oneplus 9 but it always ended up saying that the image didn't match or something (IDK the thing was in F’ing Chinese). This hard brick has gotten so bad that I cant even hold Vol up + Power to hard restart it. The screen just doesn't come on any more but is still recognized by my computer as a Qualcomm device. Does anyone know of a fix that doesn't include installing the Indian loader?
Model # LE2115 (OP9 Global)
Click to expand...
Click to collapse
That's not Chinese version m8 le2110 is, I bricked mine , I flashed it with global version , now it says it le2115 lol after OTA update to android 12 ??

jab5555 said:
That's not Chinese version m8 le2110 is, I bricked mine , I flashed it with global version , now it says it le2115 lol after OTA update to android 12 ??
Click to expand...
Click to collapse
That's the thing though. I had the LE2115 MSM tool but it was in Chinese for some reason I have a LE2115 phone as well but it said that the files didn't match up. Maybe they uploaded the wrong variant to the website? None of the tools that I had downloaded were in English, all in Chinese.

chinbags said:
I had a whole weekend of this a few weeks ago, none of the OP9 MSM tools worked but for some reason the OP 9 Pro Global tool worked. The catch was that my phone was now formatted as a 'Pro' Variant and wasn't functional. But at this stage the correct MSM tool for my variant (LE2110) would now recognise it so I was able to restore the phone using that.
This was a long way around the problem so maybe consider it as a very last resort, someone else might have a more direct route to recorvery for y
Click to expand...
Click to collapse

File folder on MEGA
mega.nz
This what I used m8, got it off OP when they tried to remote flash my phone , couldn't do it on AMD Ryzen, done on my old pc, driver issue lol, good luck m8

Question [SOLVED] Can anyone help me unbrick? I have tried lite firehose, MSM for global, MSM for Indian 9 Pro, none work

I modded the global MSM so that it will flash to this frankenphone.
All of those stuck on Indian firmware, rejoice! I modded the global MSM!
Long story short, I bricked my device today, had to use the Indian 9 Pro firmware to fix it as the global MSM wasn't recognizing it, and was very frustrated I couldn't go back to full global firmware. I figured out how to fix this. Just use it...
forum.xda-developers.com
EDIT: For anyone else trying this and getting unsupported target O2, click the Target dropdown and change it to India. It's a device mismatch that can be overridden that way. It's flashing now and I'm sure it will work fine.
EDIT2: Yeah, that worked fine. To get back to global and get a working phone, follow the steps here: https://forum.xda-developers.com/t/...ection-error-check-this.4308601/post-86528671
TWRP has been updated since that guide was made and no longer has you select between A/B partitions to format and it will give you errors on partitions when you flash but it does work regardless and boots up fine with full working radio.
When it's back up and running, if you don't plan to go straight to a custom ROM, turn USB debugging back on, reboot to fastboot, boot (don't flash) TWRP again, and use this copy partitions script to make sure both partitions have the same software.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Now you should be good to go (until the next time this insanely finicky device decides it doesn't want to cooperate). I have not figured out how to make it actually be recognized as the global device that it is, if anyone knows how to do that, please let me know. It is now recognized as an Indian 9 Pro variant which means I have to use the Indian 9 Pro MSM and go through this headache any time it decides to be a pain.
Original post: So I have an LE2115 and was doing some testing for a ROM dev. He asked me to flash Lineage to see if something worked there, I flashed the recovery, it booted back to fastboot. Tried flashing it again, same thing. Tried the global fastboot stock flash that's pinned here and that seemed to go okay until it rebooted, from there I had a black screen.
Fired up my global MSM tool which has always worked before, Sahara error. Got it back into EDL again, checked lite firehose, device not match image... Tried Indian 9 Pro MSM and it says unsupported target.
Am I just completely hosed here or is there something else I can do? I'm not new to ROM flashing, been doing it since the HTC Hero in 2009 and long before that with Windows Mobile 5 on my PPC-6700 and this is the first time I have what appears to be a totally bricked device so any help would be greatly appreciated.
It doesn't do anything but go to EDL.

Question Stuck at OnePlus logo, can anyone provide the OxygenOS stock ROM?

Hi,
While trying to root the OnePlus Nord CE 2 5G (European Edition), I managed to mess up my phone completely by flashing wrong files to the phone using fastboot.
I recieved the A13 update, and I think I flashed the wrong boot.img and some other mismatching files using fastboot. I know, it's the first time I attempted this and probably a beginners mistake. Shame on me.
The phone is stuck at the bootloader (I think), because it's not going past the boot logo from OnePlus.
I tried searching online and the OnePlus support pages for the original OxygenOS image to perform a full recovery, but I have been unsuccessful.
Can anyone provide this image or provide some guidance how I would be able to make it workable again?
Thank you in advance!

Sorry to hear about your phone. From my knowledge, the A13 firmware hasn't been shared yet. You could try your luck contacting OnePlus support. Otherwise you'll just have to wait until someone shares it, but that could take quite a while.

@mr_munch, thank you for your reply. I'll reach out to OnePlus support.

GeneratedUnique said:
@mr_munch, thank you for your reply. I'll reach out to OnePlus support.
Click to expand...
Click to collapse
Have you have any luck? Looks like they released a rollback package that includes the A.13 boot image as part of their Android 12 beta program. Maybe that could help you out if you still need it: https://community.oneplus.com/thread?id=1110424001643544581

Hi @mr_munch,
Unfortunately, so far no luck.
I've reached out to OnePlus support, they asked me to go to one of their service centres, called The Phone Lab in the Netherlands. They tried to flash the phone with the original ROM. It's now giving the error message "the serial is not match" while booting up. According to them this is due to a hard brick and I had to file a case with OnePlus support, but haven't heard anything yet.
I'll keep you posted.
Thank you for all the help!

Hi,
OnePlus repaired the phone, by replacing the motherboard/soc, all under the warranty. Luckily, I got a working phone back.
Thank you all for your support.

GeneratedUnique said:
Hi,
While trying to root the OnePlus Nord CE 2 5G (European Edition), I managed to mess up my phone completely by flashing wrong files to the phone using fastboot.
I recieved the A13 update, and I think I flashed the wrong boot.img and some other mismatching files using fastboot. I know, it's the first time I attempted this and probably a beginners mistake. Shame on me.
The phone is stuck at the bootloader (I think), because it's not going past the boot logo from OnePlus.
I tried searching online and the OnePlus support pages for the original OxygenOS image to perform a full recovery, but I have been unsuccessful.
Can anyone provide this image or provide some guidance how I would be able to make it workable again?
Thank you in advance!
Click to expand...
Click to collapse
Hi,
Same issue here with OnePlus Nord CE 2 5G (European Edition), I'm stuck on the boot logo (the three dots turning around) after flashing boot.img.
A11 update,
I tried to flash stock boot.img but no luck,
I tried a factory reset via TWRP, I tried to flash via fastboot stock firmare following this guide: https://www.getdroidtips.com/oneplu...nstall-Stock-Firmware-on-OnePlus-Nord-CE-2-5G
I don't know what to do to get it working. Do you have any advice?

...sorry, I posted to the wrong device board

Question Easiest/best way to get to stock Android 13?

So I've got a TMobile OnePlus 9 that's been converted to the global ROM. From here what's the easiest way to get updated to stock OxygenOS Android 13? When I run the system update in settings it'll update to Android 12 but the phone says that there's no sim card in. Am I doing something wrong? I don't mind unlocking the bootloader and flaking a recovery if there's a stock rooted zip I can flash.

I've tried myself but updating anything to 12 and up my touchscreen stops working, but using the TMobile India modded MSM should work getting to the global rom "but now realizing it was cuz I used something else to recover from a brick" but here
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com

th
underworld737 said:
I've tried myself but updating anything to 12 and up my touchscreen stops working, but using the TMobile India modded MSM should work getting to the global rom "but now realizing it was cuz I used something else to recover from a brick" but here
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
Click to expand...
Click to collapse
thanks I'll ck it out

this doesn't work for my device le2119 the mod fix zip throws an error unsupported device eu. I made the mistake of activating slot b. is there any way of switching back without fastboot. all I get is a black screen no matter what button combo I press. I can only get edl and I'd rather not flash the eu msm again.

paulb1977 said:
this doesn't work for my device le2119 the mod fix zip throws an error unsupported device eu. I made the mistake of activating slot b. is there any way of switching back without fastboot. all I get is a black screen no matter what button combo I press. I can only get edl and I'd rather not flash the eu msm again.
Click to expand...
Click to collapse
ive gotten the same error too, im on 11.2.10.10, but cant upgrade to OOS12/13 without the touchscreen breaking/dual sim bug, i forgot the link to the 9 pro india msm to flash it with, but ive tried flashing one that was 9 pro and kept getting "device not match image", no clue why

I just read somewhere that downgrading to 11.2.2.2 may work but only place I can find that firmware is on some Chinese site. I can flash the eu pro version all day long. but now I tried flashing an India mod firmware with no success and reflasjed eu again but phone is stuck at 0% power and all I get is a bootloop