Hello,
While playing around with custom roms, I bricked my device when returning to the stock rom. I cannot seem to find the correct MSM tool for my device. I can only find instruction Indian or Global variant, but not for the European variant.
How can I get the tools I needed for the European Oneplus 9?
bleuthoot said:
Hello,
While playing around with custom roms, I bricked my device when returning to the stock rom. I cannot seem to find the correct MSM tool for my device. I can only find instruction Indian or Global variant, but not for the European variant.
How can I get the tools I needed for the European Oneplus 9?
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
From what I'm seeing unless there is one in a thread there isn't one available. Better to wait for an msm recovery tool prior to flashing though. Guess you know that now.
mattie_49 said:
Index of /list/Unbrick_Tools
From what I'm seeing unless there is one in a thread there isn't one available. Better to wait for an msm recovery tool prior to flashing though. Guess you know that now.
Click to expand...
Click to collapse
Well, too bad for me. I will send it for repair.
Thanks for the info.
bleuthoot said:
Well, too bad for me. I will send it for repair.
Thanks for the info.
Click to expand...
Click to collapse
Better yet they will do a remote session as long as you have a PC. They will download factory msm for Eu to your desktop and repair.
mattie_49 said:
Better yet they will do a remote session as long as you have a PC. They will download factory msm for Eu to your desktop and repair.
Click to expand...
Click to collapse
Do I have to ask OnePlus support that?
I have asked them if they could provide me the MSM files, but they wanted me to send it instead.
So should I ask tehm to do a remote session instead and where exactly do I have to do that.
bleuthoot said:
Do I have to ask OnePlus support that?
I have asked them if they could provide me the MSM files, but they wanted me to send it instead.
So should I ask tehm to do a remote session instead and where exactly do I have to do that.
Click to expand...
Click to collapse
Save you much time and none away from device. The do a remote session. I'd def ask for that. And you plug into the PC through adb and they will do the rest.
bleuthoot said:
Do I have to ask OnePlus support that?
I have asked them if they could provide me the MSM files, but they wanted me to send it instead.
So should I ask tehm to do a remote session instead and where exactly do I have to do that.
Click to expand...
Click to collapse
There's a way to do it. I had the same issue two days ago.
Flashing with the MSM Tool for the Indian variant of the OP9 Pro and checking "Lite firehouse".
Once recovered, you could use the MSM Tool for your device.
If you need any of these tools, they're posted, let me look for them and update this reply.
zborn said:
There's a way to do it. I had the same issue two days ago.
Flashing with the MSM Tool for the Indian variant of the OP9 Pro and checking "Lite firehouse".
Once recovered, you could use the MSM Tool for your device.
If you need any of these tools, they're posted, let me look for them and update this reply.
Click to expand...
Click to collapse
If you can find them, gladly.
I have been searching for them for several hours without any result.
bleuthoot said:
If you can find them, gladly.
I have been searching for them for several hours without any result.
Click to expand...
Click to collapse
None of the MSM tools are going to work from the Indian version. I tried all of them. Your build is going to need to be flashed with temp TWRP and the OS build from OP support website. Once that happens, you have to do an OTA update before reboot so the Indian partition can be overwritten. That's the only thing that worked for me.
MSM cannot recognize your phone aka. Sahara Connection error? Check this.
Hi! Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore. I tried everything, from different MSM tools to this thread. Nothing. Then, Deus ex Machina, @flameteam recommended me to try...
forum.xda-developers.com
bleuthoot said:
If you can find them, gladly.
I have been searching for them for several hours without any result.
Click to expand...
Click to collapse
You can find the tool here https://forum.xda-developers.com/t/oneplus-9-pro-oxygen-os-india-msmdownloadtool.4270589/
letscheckitout said:
You can find the tool here https://forum.xda-developers.com/t/oneplus-9-pro-oxygen-os-india-msmdownloadtool.4270589/
Click to expand...
Click to collapse
I wouldn't use the pro tool. That doesn't work. I tried.
ctonylee1965 said:
I wouldn't use the pro tool. That doesn't work. I tried.
Click to expand...
Click to collapse
I was stuck with Sahara communication error from yesterday, tried mutiple drivers,cables and OP9 MSM Global,EU tool. did not work.
I downloaded the OP9 Pro India MSM tool, flashed the OS with Lite Firehouse, and then used the OP9 indian MSM tool to get back.
So use this tool as a stop gap, After the first boot use which ever tool you want to get back.
I had tons of problems until I used the right Qualcomm drivers. Nothing would flash - even the Indian Pro ROM, until I got that straightened out. I was then able to flash the T-Mo MSM without having to mess with India.
I kept getting the Param Preload failure.
Uninstall the old Qualcomm drivers and delete them. Put your phone into EDL and have it redetect the device. Then update the drivers with these.
https://onepluscommunityserver.com/list/Unbrick_Tools/Qualcomm%20drivers.7z
Biggest difference I saw right away in MSM was it switched from COM10 to COM3. Then everything worked properly.
Give it a go.
letscheckitout said:
I was stuck with Sahara communication error from yesterday, tried mutiple drivers,cables and OP9 MSM Global,EU tool. did not work.
I downloaded the OP9 Pro India MSM tool, flashed the OS with Lite Firehouse, and then used the OP9 indian MSM tool to get back.
So use this tool as a stop gap, After the first boot use which ever tool you want to get back.
Click to expand...
Click to collapse
when using india msm from 9 pro it gives me unsupoorted model EU
The problem is that when i use the eu op9pro msm tool i get a working device but without sim cards working. ANy help?
Tepes4 said:
when using india msm from 9 pro it gives me unsupoorted model EU
The problem is that when i use the eu op9pro msm tool i get a working device but without sim cards working. ANy help?
Click to expand...
Click to collapse
Found a solution?I have same experienced with you yesterday.
My step is, after done flash op9pro, i flash op9 india msmtool.
After that, i use oxygen updater and set my phone to EU. Then I download oos stable full for EU using oxygen updater.
Then I flash it using local upgrade.
Done.
Everything looks good as at today.
lockmunk said:
My step is, after done flash op9pro, i flash op9 india msmtool.
Click to expand...
Click to collapse
I tried this also, but India tool still give me unsupported model EU
I used this OP9p file:
lemonadep_22_E.05_210324.ops
OP9p EU
after OP9 India
lemonade_22_I.07_210412
before I used also the India OP9p and used local update to OP9 EU
Android 11 works fine, but if i update to any Android 12 my touchscreen is complete dead
Even in recovery
henno88 said:
I tried this also, but India tool still give me unsupported model EU
I used this OP9p file:
lemonadep_22_E.05_210324.ops
OP9p EU
after OP9 India
lemonade_22_I.07_210412
before I used also the India OP9p and used local update to OP9 EU
Android 11 works fine, but if i update to any Android 12 my touchscreen is complete dead
Even in recovery
Click to expand...
Click to collapse
i found firmware for op9 EU here. but don't know whether it works.
but need to have premium account to download it
ROM OnePlus 9 | [Official]-[Updated] add the 10/19/2021 on Needrom
lockmunk said:
i found firmware for op9 EU here. but don't know whether it works.
but need to have premium account to download it
ROM OnePlus 9 | [Official]-[Updated] add the 10/19/2021 on Needrom
Click to expand...
Click to collapse
Not working
It is for QPST and there are missing files
Maybe someone need it....
File on MEGA
mega.nz
henno88 said:
Maybe someone need it....
File on MEGA
mega.nz
Click to expand...
Click to collapse
did you success flash using this file in qpst?
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
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.
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 like any other MSM Tool, click the dropdown in the left and switch to IN.
This isn't a technical support thread, there are plenty of threads around here for the MSM Tool and the issues that arise when trying to use it. As you can see, I didn't have to use the lite firehose even but most people seem to have problems if they don't so just do what worked for you before.
Also, this is not for people who haven't flashed their global variant with the Indian 9 Pro variant. I'm not responsible if you mess up your device by flashing it to a real Indian 9 Pro or under any other circumstances!
EDIT: Also, I tested it just now, and this successfully updated to 11.2.10.10 and then C.48 with working touchscreen using the stock OTA updater!
EDIT2: I can also confirm that the original global MSM Tool works again after flashing this so my device was 100% returned to a stock global unit.
Mod Edit: Links Removed
Thread closed at OP request
i'm figuring why my OP9 can't boot to slot A and instead my device boots only to slot B. forcing a boot to slot A via fastboot, just puts he device into EDL mode and can be restarted in slot B.
i'm trying to figure this out when I came across this app in G-Play "Treble Info." The app now reports that the required image - system-arm64-ab.img.xz is missing.
Treble Check app reports that - Your device does not support Project Treble.
current device OS is oxygen Os 12.1 (LE211_11_C60).
is there a fix for this? TIA
Have you tried using the MSM Tool? If the MSM Tool won't work or can't fix it, you may have to send it in for service.
EtherealRemnant said:
Have you tried using the MSM Tool? If the MSM Tool won't work or can't fix it, you may have to send it in for service.
Click to expand...
Click to collapse
have not tried the MSMtool yet. that would probably the only way to fix it. i just want to check if anybody have encountered the same problem.
BTW i just downgraded to Oxygen 11 and treble check is still reporting the same problem.
thanks.