This method is outdated. You must use this method or you will run into problems.
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
**I forgot that OnePlus screwed up the wiping script on 11.2.10.10 so after discovering I couldn't root my device, I have attached 11.2.4.4 that is modded to flash to Indian variants as well. It works on my device in the same manner described in this post. If you use 11.2.10.10, you won't be able to unlock the bootloader and have a working phone, it will kick you to recovery with an error message and you can wipe system cache and it will act like it's booting but it never will. Only flash 11.2.10.10 if you are planning to stay with a locked bootloader or if you're going to OOS 12.**
I found this updated MSM Tool and figured that people would appreciate it.
Source of updated MSM Tool: https://yun.daxiaamu.com/OnePlus_Roms/一加9/9008线刷救砖包氧OS 11.2.10.10/
As an added bonus, I added multi-target support. If you have flashed your global OnePlus 9 with Indian firmware, this package may help you get back to global software. I have tested it by intentionally flashing my global 9 to India 9 Pro firmware again and I can confirm that it does work. Choose India in the Target dropdown box.
As for the settings for flashing Indian firmware back to global, I was getting the dreaded "device not match image" until I left sha256 checked and use lite firehose *unchecked*. I know this flies in the face of normal convention and I'm sure this will lead to some people having Sahara errors and I unfortunately don't know how to fix that. I would assume that when you have a device that's actually booting that you shouldn't need the lite firehose anyway. It wouldn't surprise me if some people find that they need a different combo. In order to get the OP9P firmware (which I also modified with multi-target to force it to flash to global because it wouldn't do it without the mod) to flash my global unit so I could test this, I had to uncheck Sha256 check and I left use lite firehose checked, so try playing with different combos instead of just declaring it doesn't work and please report which combos worked for your device so others can see.
It's honestly a real headache when you have to flash the Indian 9 Pro firmware because it breaks the ability to go to OOS12 unless you can flash back with the global MSM and clear whatever flag is being set that makes it think it's an Indian 9 Pro so having a tool available to be able to go back to global firmware should be a great boon for those of us who have a serial flashing problem lol.
Pro tip: Start the app and click Start before you connect your phone so it's already looking for the device when it reboots. You can use adb reboot edl to go right to edl mode rather than having to use the obnoxious key combo. If the process fails, press and hold volume up and power until the phone reboots to the OS and you can try again.
Screenshot of success:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
11.2.10.10:
3.56 GB file on MEGA
mega.nz
11.2.4.4: https://mega.nz/file/ZWtGxTSb#UZ6aSOR2UTYrCao2fQNJ1IN5LSxPNBOxzel1kihnnJs
EDIT: I just tested this a second time, taking my device back to Indian 9 Pro and then using this MSM again. It flashed exactly the same way, giving me the device not match image error until I left Sha256 checked and unchecked use lite firehose.
EDIT 2: See ** message at the top.
*deleted*
Thank you! I'll try it as soon as i need to MSM again
Hey guys.
After bricking my phone and getting into a eternal looping black screen with no hopes to solve it but to send it over to repair, I tried what @EtherealRemnant told me and it did work!!
1st the Indian MSM for OP9Pro and then this patched MSM.
When I ran the MSM tool I just did exactly what the post says. Checked sha256 and unchecked "Lite Firehouse" just like in the pic below and it just worked. I used the Vol+ and Vol- key combo pressed while plugging the Original OnePlus 9 USB-C cable to get to EDL mode after flashing the OP9PRO and skipping the initial config in order to get to EDL again and flash the magical MSM .ops file provided.
Thanks again for this
Hi, i have a good story.
My Oneplus 9 LE2110 got hardbricked some weeks ago and i wasn't able to find any MSM working for my device, until i found that the 9 Pro India MSM worked and i recovered my phone. But somehow, after flashing the normal OP9 firmware (through recovery because of global/india/europe MSM not working), and updating to OOS12 by OTA, my touchscreen just wasn't working on it, just was working on OOS11 and A12 custom roms. I decided to use Nameless but i just couldn't live thinking that OOS12 (and probably next updates) would never work again on my phone.
So eventually i found your post, tried your patched MSM and... IT WORKED AT THE FIRST TRY! my phone woke up on global OOS, i updated to latest A11 and installed OOS12 through OTA and my device (and touchscreen) are working perfectly! Thank you for your work!
If anybody has a bricked LE2110 with no screen, or you can't find any MSM working on your phone, just try this one. Thanks again @EtherealRemnant
@blosk It makes me so happy to see people benefiting from this! I originally made it for myself but when people started messaging me for help, I figured it was time to share. You are the third person in the last few days that I know of who had success!
Thank you for this @EtherealRemnant It is just what I needed.
EtherealRemnant said:
@blosk It makes me so happy to see people benefiting from this! I originally made it for myself but when people started messaging me for help, I figured it was time to share. You are the third person in the last few days that I know of who had success!
Click to expand...
Click to collapse
When I try to use either msm it gives me the Param preload device does not match image error I tried all the options switch around (sha256, lite firehose)
stez827 said:
When I try to use either msm it gives me the Param preload device does not match image error I tried all the options switch around (sha256, lite firehose)
Click to expand...
Click to collapse
Are you selecting the correct option in the dropdown?
If you are flashing a global unit that is still running global software, choose O2 in the dropdown. If you are flashing a global or other unit that was flashed with Indian 9 Pro, choose India in the dropdown.
Flashing India only seems to work with Sha256 checked and lite firehose unchecked so far.
Try changing the target to global as well just in case. Also try it with no target selected.
There is not a lot of troubleshooting that can be done here but you can try flashing an India OTA to get Indian firmware on both slots and see if that works. You can also try the oldest version India downgrade package and see if that helps.
If these ideas don't work, I don't know what to tell you. You're the first who couldn't get it to work so far. I have three PMs in my box from people who used the tool and haven't posted in this thread.
EtherealRemnant said:
Are you selecting the correct option in the dropdown?
If you are flashing a global unit that is still running global software, choose O2 in the dropdown. If you are flashing a global or other unit that was flashed with Indian 9 Pro, choose India in the dropdown.
Flashing India only seems to work with Sha256 checked and lite firehose unchecked so far.
Try changing the target to global as well just in case. Also try it with no target selected.
There is not a lot of troubleshooting that can be done here but you can try flashing an India OTA to get Indian firmware on both slots and see if that works. You can also try the oldest version India downgrade package and see if that helps.
If these ideas don't work, I don't know what to tell you. You're the first who couldn't get it to work so far. I have three PMs in my box from people who used the tool and haven't posted in this thread.
Click to expand...
Click to collapse
I tried all those trouble shooting steps none of which worked my phone is a T-Mobile OnePlus 9 but I bricked it when trying to convert to global but was able to bring it back with the Indian 9 pro msm then flash global it's after that and have been running nameless for a while now but now I need to update to c.48 to stay up to date with nameless could my phone being an le2117 not and le2115 have made an actual difference even though there is no hardware difference
stez827 said:
I tried all those trouble shooting steps none of which worked my phone is a T-Mobile OnePlus 9 but I bricked it when trying to convert to global but was able to bring it back with the Indian 9 pro msm then flash global it's after that and have been running nameless for a while now but now I need to update to c.48 to stay up to date with nameless could my phone being an le2117 not and le2115 have made an actual difference even though there is no hardware difference
Click to expand...
Click to collapse
It could if it's recognizing it as a T-Mobile model. I can modify a tool to flash T-Mobile models but it will take me a bit because it's a huge file to upload.
EtherealRemnant said:
It could if it's recognizing it as a T-Mobile model. I can modify a tool to flash T-Mobile models but it will take me a bit because it's a huge file to upload.
Click to expand...
Click to collapse
That would be awesome don't be in any rush I may not be able to tinker with my phone today as I really need it to be working even if it's on an outdated version of nameless but it would be amazing if you could do that
stez827 said:
That would be awesome don't be in any rush I may not be able to tinker with my phone today as I really need it to be working even if it's on an outdated version of nameless but it would be amazing if you could do that
Click to expand...
Click to collapse
Is the error saying unsupported target at all? If it's not I don't think it will make a difference but I don't mind doing the mod regardless.
EtherealRemnant said:
Is the error saying unsupported target at all? If it's not I don't think it will make a difference but I don't mind doing the mod regardless.
Click to expand...
Click to collapse
It says device does not match image not unsupported target
It's also possible that Nameless changed something that is causing the device not to be recognized correctly. If you flash the 9 Pro MSM and then immediately use the modded MSM it should work in theory but I don't have any experience with these T-Mobile models.
EtherealRemnant said:
It's also possible that Nameless changed something that is causing the device not to be recognized correctly. If you flash the 9 Pro MSM and then immediately use the modded MSM it should work in theory but I don't have any experience with these T-Mobile models.
Click to expand...
Click to collapse
When I first tried it that's what I did flashed India 9 pro msm then tried the fix msm but no luck and it being a T-Mobile model theoretically shouldn't make a difference as it's the same hardware just a different model number
stez827 said:
When I first tried it that's what I did flashed India 9 pro msm then tried the fix msm but no luck and it being a T-Mobile model theoretically shouldn't make a difference as it's the same hardware just a different model number
Click to expand...
Click to collapse
Well you're the first person this hasn't worked for so I'm grasping at straws trying to figure out why.
EtherealRemnant said:
Well you're the first person this hasn't worked for so I'm grasping at straws trying to figure out why.
Click to expand...
Click to collapse
Yeah oh something else I have done is I originally used to EU9pro MSM but that seems to be very unlikely to have done anything as I used the Indian 9pro MSM
stez827 said:
Yeah oh something else I have done is I originally used to EU9pro MSM but that seems to be very unlikely to have done anything as I used the Indian 9pro MSM
Click to expand...
Click to collapse
Yeah I doubt that's the issue. It's strange that you're not getting unsupported target on either selection in the drop-down though. You should get it on the O2 for sure since you used the India MSM last.
EtherealRemnant said:
Yeah I doubt that's the issue. It's strange that you're not getting unsupported target on either selection in the drop-down though. You should get it on the O2 for sure since you used the India MSM last.
Click to expand...
Click to collapse
Oh I get unsupported target on O2 but not India sorry
Related
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 Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!
Enjoy it I struggled for a week. The result is ridiculous but successful
_MartyMan_ said:
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 Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!
Click to expand...
Click to collapse
Yes !! thanks @flameteam. My Oneplus 9 EU was really super hard bricked (turned to the "dark side") with no display whatsoever. I went for the EU package and the phone came back to life !!
This was the only way as some other download tool dedicated for the Oneplus 9 didn't work. Gave me "Sahara error. (with Windows 7, 10, different USB cables etc)
And , yes as strange as it sounds my Oneplus 9 now runs the OP9 Pro firmware ?!?!.
But this gave me the chance to install the stock OTA for Oneplus 9. It seems to work.
The question is if a full stock OTA OP9 actually cleaned out any trace of the previous Pro version ?
Big Update. my phone is coming back and free again )i think) No warranty, just wild QoL issues with the 9, it seems.
Im still very happy to get it back .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yo i love you bro.....seriously you are the fkkkng mannnn omg
josc002 said:
Yes !! thanks @flameteam. My Oneplus 9 EU was really super hard bricked (turned to the "dark side") with no display whatsoever. I went for the EU package and the phone came back to life !!
This was the only way as some other download tool dedicated for the Oneplus 9 didn't work. Gave me "Sahara error. (with Windows 7, 10, different USB cables etc)
And , yes as strange as it sounds my Oneplus 9 now runs the OP9 Pro firmware ?!?!.
But this gave me the chance to install the stock OTA for Oneplus 9. It seems to work.
The question is if a full stock OTA OP9 actually cleaned out any trace of the previous Pro version ?
Click to expand...
Click to collapse
yes cleaning msm tool
The Indian version of MSM was able to restore my phone, but now I cant install any OTAs without bricking it. How did you get it back to a Global rom after the MSM retore?
I was finally able to unbrick by using this method after days of troubleshooting, but now how in the hell do I get the OnePlus 9 firmware back onto it? I've downloaded different (full zip) ota's, moved to root storage, and when I go to system settings --> local upgrade, the updates do not show up there. I tried flashing via TWRP and I believe it booted to inactive slot (where update was applied) and bootlooped. Eventually it booted back into slot A with OP9Pro firmware. I thought maybe I could use global msm tool for OP9 but the thread that says "UPDATED" downloads and then fails to open. So far only msm tool I have gotten to work for my phone was for the Indian OP9Pro variant.
_MartyMan_ said:
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 Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!
Click to expand...
Click to collapse
you still bricked foooo??? adb reboot edl launch msm tool in thank me lataaaa
Hallelujah!!!! IT WORKED!!!!!!!!! I've been bricked for a month!!
The question now is how do i get back to global? Any ideas?
Anyone???
YES
Got back to global. Took me a day to figure it out. Enable OEM Unlock and USB debugging. I flashed temp TWRP, installed the OS Zip file from OnePlus support site. Rebooted into recovery, formatted and wiped system. Booted into global. This installation is in SLOT B. Slot A will still have horrible Indian Rom (only horrible because it shouldn't be installed on my Global Unlocked Phone, no disrespect to my Indian brothers.) Note when logging in for the first time let global do its OTA update before you do anything else, especially before you reboot. The Indian version is installed in slot A. REBOOT after OTA installed. Don't reboot before OTA does its thing. This will ensure Slot A has a clean installation. I made the mistake of rebooting before the OTA and I could not do anything with slot A. Relock the bootloader, it will wipe and you will boot into a pristine Global OS 11.2.8.8 Rom.
lrod55 said:
I was finally able to unbrick by using this method after days of troubleshooting, but now how in the hell do I get the OnePlus 9 firmware back onto it? I've downloaded different (full zip) ota's, moved to root storage, and when I go to system settings --> local upgrade, the updates do not show up there. I tried flashing via TWRP and I believe it booted to inactive slot (where update was applied) and bootlooped. Eventually it booted back into slot A with OP9Pro firmware. I thought maybe I could use global msm tool for OP9 but the thread that says "UPDATED" downloads and then fails to open. So far only msm tool I have gotten to work for my phone was for the Indian OP9Pro variant.
Click to expand...
Click to collapse
See above. I figured it out.
Ok. this worked for me... I was able to save my LE2110 from being hard bricked. THANK YOU.
Now, has anyone been able to go back to the non-Pro software?
If so, how did you do it?
zborn said:
Ok. this worked for me... I was able to save my LE2110 from being hard bricked. THANK YOU.
Now, has anyone been able to go back to the non-Pro software?
If so, how did you do it?
Click to expand...
Click to collapse
See my response above.
ctonylee1965 said:
See my response above.
Click to expand...
Click to collapse
That didn't work for me. I just MSMed back to 9 firmware
lrod55 said:
I was finally able to unbrick by using this method after days of troubleshooting, but now how in the hell do I get the OnePlus 9 firmware back onto it? I've downloaded different (full zip) ota's, moved to root storage, and when I go to system settings --> local upgrade, the updates do not show up there. I tried flashing via TWRP and I believe it booted to inactive slot (where update was applied) and bootlooped. Eventually it booted back into slot A with OP9Pro firmware. I thought maybe I could use global msm tool for OP9 but the thread that says "UPDATED" downloads and then fails to open. So far only msm tool I have gotten to work for my phone was for the Indian OP9Pro variant.
Click to expand...
Click to collapse
I hard bricked my oneplus 9 first time and was panicking. Luckily I found this thread and your answer. You guys saved me hours and days of fixing this, most important of all, I can't tell me wife that I trashed a $800 phone after bought it a couple days ago. I was able to get my phone back into EU version using the MSM tool, lost my IMEI # and sim card won't work, So I was able to switch back to global after following your instruction. Thank you.
_MartyMan_ said:
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 Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!
Click to expand...
Click to collapse
How did you do it? I am trying this method, but MSM tool gives me this error:
This was a Untested MSM .OPS file for the EU Variant use at your own risk.
This was tested by @lockmunk and verified to be working for the EU varient of the device check post 4 if you want to see proof.
This will fail verification when pressing verify because the msm tools used was originally global msm,i just swapped the ops files so it could be flashed.
This was made using the files linked here : https://forum.xda-developers.com/t/...oneplus-9-le2113-with-msm-tool.4320461/page-2
ANY AND ALL DAMAGE DONE TO YOUR DEVICE AFTER THIS IS NOT MY RESPONSIBILITY.....
I take no responsibility for you hardbricking your device or it becoming nonworking after this......
This is OxygenOS_11.2.7.7.LE25BA firmware as shown in the screenshot in post #4
https://www.mediafire.com/file/gyv5gza7t4ibn7j/OnePlus_9_EU_lemonade_22_E.10_210609.zip/file
PREREQUISITES
MUST HAVE QUALCOMM DRIVER'S INSTALLED (FOR EDL TO WORK!!)
CLICK LINK DOWNLOAD MSM TOOL
UNZIP
CLICK ON MSM TOOL
RUN AS OTHER!!
REBOOT TO EDL.
(POWER OFF)
HOLD BOTH VOLUME UP AND DOWN CONNECT TO PC
WHEN YOU SEE CONNECTED CLICK START AND LET IT RUN DEVICE WILL REBOOT ONCE & DONE!!!
wow this is nice. can someone test it?
dear @allenjthomsen a
Found that MD5 checksum failed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ok I risk myself to tried it out.
and the results is...it REALLY WORKS!!
below is my settings in MSM and about phone
lockmunk said:
dear @allenjthomsen a
Found that MD5 checksum failed
View attachment 5479725
Click to expand...
Click to collapse
It will fail md5 verification because msm tools in this file were originally global i just swapped the ops file.
lockmunk said:
ok I risk myself to tried it out.
and the results is...it REALLY WORKS!!
below is my settings in MSM and about phone
Click to expand...
Click to collapse
this is good im glad it was able to restore your phone to EU
My model is le2110 and a bit afraid of bricking. Anyone tested on 2110?
azizolmez said:
My model is le2110 and a bit afraid of bricking. Anyone tested on 2110?
Click to expand...
Click to collapse
LE2110 is CN and normally comes with Colour OS unless converted to IN firmware. LE2113 is EU. LE2115 is NA/Global.
This info was taken from OP9 community forum.
allenjthomsen said:
LE2110 is CN and normally comes with Colour OS unless converted to IN firmware. LE2113 is EU. LE2115 is NA/Global.
This info was taken from OP9 community forum.
Click to expand...
Click to collapse
Converted oos11 then flashed havoc. Now I want to go back to stock.
Thanks you a lot for making this. Sorry cause i m asking but, can it be done with last 11.2.10.10 too? Thanks xDD
azizolmez said:
Converted oos11 then flashed havoc. Now I want to go back to stock.
Click to expand...
Click to collapse
you can use it with no problem, i have LE2110 too, but i live in Europe. Until now i was using GLOBAL MSM to get OOS and flashing Europe by local update.
Sheldd said:
Thanks you a lot for making this. Sorry cause i m asking but, can it be done with last 11.2.10.10 too? Thanks xDD
Click to expand...
Click to collapse
I'm not sure thats possible unless the msm files could be found like the ones provided in the thread that i linked, best i can say for now is just use the provided msm i made and update via settings to latest firmware.
Sheldd said:
Thanks you a lot for making this. Sorry cause i m asking but, can it be done with last 11.2.10.10 too? Thanks xDD
Click to expand...
Click to collapse
When I try this files, I also on this version. Should be no problem. Then now I updated to 11.2.10.10 without any problem.
allenjthomsen said:
This was a Untested MSM .OPS file for the EU Variant use at your own risk.
This was tested by @lockmunk and verified to be working for the EU varient of the device check post 4 if you want to see proof.
This will fail verification when pressing verify because the msm tools used was originally global msm,i just swapped the ops files so it could be flashed.
This was made using the files linked here : https://forum.xda-developers.com/t/...oneplus-9-le2113-with-msm-tool.4320461/page-2
ANY AND ALL DAMAGE DONE TO YOUR DEVICE AFTER THIS IS NOT MY RESPONSIBILITY.....
I take no responsibility for you hardbricking your device or it becoming nonworking after this......
This is OxygenOS_11.2.7.7.LE25BA firmware as shown in the screenshot in post #4
OnePlus_9_EU_lemonade_22_E.10_210609.zip
drive.google.com
PREREQUISITES
MUST HAVE QUALCOMM DRIVER'S INSTALLED (FOR EDL TO WORK!!)
CLICK LINK DOWNLOAD MSM TOOL
UNZIP
CLICK ON MSM TOOL
RUN AS OTHER!!
REBOOT TO EDL.
(POWER OFF)
HOLD BOTH VOLUME UP AND DOWN CONNECT TO PC
WHEN YOU SEE CONNECTED CLICK START AND LET IT RUN DEVICE WILL REBOOT ONCE & DONE!!!
Click to expand...
Click to collapse
Work fine on my OnePlus 9, thank you for saving my phone
I flashed with MSM Tool to my LE2110 but Model Number doesn't change
isson said:
I flashed with MSM Tool to my LE2110 but Model Number doesn't change
Click to expand...
Click to collapse
based on my experience with OP devices the model number will not change on your device even if you flash a different msm.
isson said:
I flashed with MSM Tool to my LE2110 but Model Number doesn't change
Click to expand...
Click to collapse
The model number wont change by flashing a diferent region rom. Only if you flash the weirdo OOS12 update you will see LE2115 xDD
I flashed with MSM Tool to my LE2110 works very well , but im unchecked all
the model name remain the same too, but no problem finally we have a tool to re-alive our op9
thanks boss
Would this work with the T-Mobile op9? I went that whole India 9pro direction and now my phone can't use the fingerprint sensor or proximity sensor. Any feedback would be great thanks.
I have one question, since supported LTE frequencies is a software limitation, flashing the EU version when we come from global rom change something one le2110 model?
akboy7015 said:
I have one question, since supported LTE frequencies is a software limitation, flashing the EU version when we come from global rom change something one le2110 model?
Click to expand...
Click to collapse
no changement, no change name model remain all perfect as a new model
I attempted to convert my t-mobile oneplus 9 to international firmware by first flashing the Indian firmware.
I mistakenly downloaded the oneplus 9 PRO Indian msm.
I didn't realize this as the file has a very similar name. Lemonade_22.I.07_210412 vs Lemonadep_22_I.07_210412
I've tried everything since then, with no success. I tried to flash the correct oneplus 9 indian msm but it says incorrect device.
So I'm stuck with the oneplus 9 pro Indian firmware and can't get back to indian oneplus 9 firmware....
I have been developing and flashing android devices since the early days of Cyanogenmod... dozens of devices. And guess what? I did EXACTLY the same thing as you.
The link I downloaded from said it was Oneplus 9 firmware, and given the filenames being virtually identical, I never noticed it was the Oneplus 9 PRO firmware.
So don't feel too bad. Even experienced people can make mistakes when trying to flash phones!
I am working on a solution, but so far no luck because:
1. Msm Tool will not flash the Oneplus 9 firmware as it thinks it is the incorrect device (why did it let us flash the incorrect device firmware before???)
2. The bootloader is re-locked and the OEM Unlocking feature is greyed out in Developer options, therefore fastboot can't be used to re-flash the correct firmware.
3. The System Update "local upgrade" feature does not find ZIP files in the root folder and will not allow us to browse to the correct file.
So for now, we are stuck. I think solving #3 will be the solution. If we can make the "local upgrade" work, we should be able to flash the stock firmware ZIP.
@Derek6091 @mightysween did you fix it yet? I had my device screw up so bad today that the only MSM I could use on my global unit was the Indian 9 Pro firmware and I have gotten my device mostly working.
You can see my drama with it and how I finally got it working here.
[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. https://forum.xda-developers.com/t/all-of-those-stuck-on-indian-firmware-rejoice-i-modded-the-global-msm.4442473/ EDIT: For anyone else trying this and getting unsupported...
forum.xda-developers.com
I can get it working with 11.2.10.10 but not OOS 12, in OOS 12 the touchscreen doesn't work and it shows dual SIM icons so it's still doing something that makes it think it's a foreign variant. I ended up just going back to StagOS where I was before everything got mucked up.
Unfortunately the MSMs still see it as an Indian variant so I can only flash the Indian OP9P firmware to it, tried all the other MSMs and none work. I have been reading threads here and people claim they got it back to global but I tried all of the suggestions and none of them restored the device enough to where the global MSM Tool didn't see it as an Indian model and refuse to flash so I think we are stuck with this frankendevice.
@EtherealRemnant Yes I had to do oem unlock while on the Indian firmware. If your phone has the oem unlock greyed out, there's a guide on how to fix that with a simple command line.
Then I unlocked bootloader, flashed lineage recovery then a custom ROM. Haven't tried to get back to stock rom, and I don't think we can.... But I love this rom I'm currently on which is stagos.
Feel free to message me for any questions you may have!
[ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonade][FINAL][08/09/2022]
Hey another day another rom, that's what you might be thinking. but we at stag aim towards elegance. We are learners just like everyone out there, This is small project we have started which helps us learn every single day. Why Stag, you might...
forum.xda-developers.com
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Nice glad you figured it out.
go17lyonjon said:
Nice glad you figured it out.
Click to expand...
Click to collapse
haha yeah I was a dog with a bone, wasn't gonna drop it lol.
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Excellent. How did you do it? I would like to try with the T-Mobile MSM
Derek6091 said:
@EtherealRemnant Yes I had to do oem unlock while on the Indian firmware. If your phone has the oem unlock greyed out, there's a guide on how to fix that with a simple command line.
Then I unlocked bootloader, flashed lineage recovery then a custom ROM. Haven't tried to get back to stock rom, and I don't think we can.... But I love this rom I'm currently on which is stagos.
Feel free to message me for any questions you may have!
[ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonade][FINAL][08/09/2022]
Hey another day another rom, that's what you might be thinking. but we at stag aim towards elegance. We are learners just like everyone out there, This is small project we have started which helps us learn every single day. Why Stag, you might...
forum.xda-developers.com
Click to expand...
Click to collapse
I can't find a working command line fix for the greyed out OEM unlock... which one did you use?
mightysween said:
I can't find a working command line fix for the greyed out OEM unlock... which one did you use?
Click to expand...
Click to collapse
Go to your home screen on your phone and connect to computer with usb debugging and run this command in cmd,
adb shell pm disable-user com.qualcomm.qti.uim
Then go to developer options and oem unlock should be able to toggle.
mightysween said:
Excellent. How did you do it? I would like to try with the T-Mobile MSM
Click to expand...
Click to collapse
You have to use the Oppo Decrypter tools. Decrypt the OPS file and open settings.xml. At the bottom of it there's a Target area. I just edited that to IN instead of O2 and re-packed it.
Derek6091 said:
Go to your home screen on your phone and connect to computer with usb debugging and run this command in cmd,
adb shell pm disable-user com.qualcomm.qti.uim
Then go to developer options and oem unlock should be able to toggle.
Click to expand...
Click to collapse
Perfect... thanks.
EtherealRemnant said:
You have to use the Oppo Decrypter tools. Decrypt the OPS file and open settings.xml. At the bottom of it there's a Target area. I just edited that to IN instead of O2 and re-packed it.
Click to expand...
Click to collapse
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
mightysween said:
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
Click to expand...
Click to collapse
Manually flashing partitions in Fastboot does work, FYI. So it is possible to go back to stock that way once the bootoader is re-unlocked.
I wonder where the "target" data is stored on the actual device. If it is simply a numerical/text value in an accessible partition, seems like it would be pretty easy to make a TWRP flashable that can change it.
mightysween said:
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
Click to expand...
Click to collapse
Strange that it didn't work for you. That was indeed all I changed. Did you change it to what the unsupported target message said your device was? I was comparing the settings between India and global and besides the change of target ID, the target number on India was 3 instead of 1. No idea if that makes a difference though because I didn't try it.
You made sure to re-encrypt and replace the OPS, right?
Also yeah you can flash with fastboot, it doesn't fix that flag though and when I tried to go back to OOS 12 with the messed up flag it thought my device was a dual SIM device so there was no signal and the touchscreen didn't work. Happened twice. With the modified MSM I went back to global and am running OOS 12 right now.
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Do you still have this file ? I flashed the OnePlus 9 pro indian firmware in msm since it's the only thing that worked and I want to go back to global
taintsx said:
Do you still have this file ? I flashed the OnePlus 9 pro indian firmware in msm since it's the only thing that worked and I want to go back to global
Click to expand...
Click to collapse
All you have to do to go back to global is download the full OTA for your device and flash it with the system updater.
EtherealRemnant said:
All you have to do to go back to global is download the full OTA for your device and flash it with the system updater.
Click to expand...
Click to collapse
Yea I tried that and had touchscreen not responding issues
taintsx said:
Yea I tried that and had touchscreen not responding issues
Click to expand...
Click to collapse
Then use the downgrade package. It will wipe your phone again but I will get you back to full OOS11 firmware and that issue won't happen.
EtherealRemnant said:
Then use the downgrade package. It will wipe your phone again but I will get you back to full OOS11 firmware and that issue won't happen.
Click to expand...
Click to collapse
Yea i tried that with
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
downgrade indian version 11.2.5.5 , unfortunately it just tells me it cannot read the file when i attempt to sideload
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 looking for a captain who could help me find solution. Like "EtherealRemnant" in his post, Im not able to get OOS 12 work on my OP9.
EtherealRemnant post:
https://forum.xda-developers.com/t/...p9-stock-oos-11-2-2-2aa.4275727/post-86854951
Like "everyone" I've something messed up with TWRP boot and ended up with MSM tool. Cause I have LE2113 I have to use India MSM for 9Pro.
Then I use downgrade package to get stock OOS on my OP9, then use oficial way to update OOS, till highest A11. But whenever I use update to LE2113_11.C.47 it ended up with frozen/not working touch screen. Not just in OS but also in TWRP and stock recovery. I´ve tried also connect USB mouse, but with no successs.
My question, is there a way how to update to OOS (A12) without get freezed touchscreen?
EDIT:
Whole problem was in usage of wrong MSM (INDIAN OP9pro, EU OP9pro). So if you want to recover yours OP9 (EU) LE2113, you have to use MSM tool from allenjthomsen (Thank you!).
More abotu this tool here
I was able to get my device back to stock software by modding the MSM Tool for global but then I gave it to someone else to try to help them and it didn't work. I have sent a PM to the person who mods these images for some help.
Have you tried using the full install zip for BA using the system updater? I didn't actually try that before I messed around with the MSM Tool. Put this in the root of your storage and go to updater and do the local upgrade.
https://otafsg-cost-az.coloros.com/OnePlus9_EEA/OnePlus9Oxygen_22.E.13_GLO_0130_2111112104/patch/amazone2/GLO/OnePlus9Oxygen/OnePlus9Oxygen_22.E.13_GLO_0130_2111112104/OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
It seems like what is happening is even after you get it back to stock software, there is a flag somewhere that's designating the device as an Indian 9 Pro. Once I got the modified global MSM Tool I made to flash my phone, the problem stopped because my phone was fully global again and I've been back on OOS 12 C.48 since Saturday evening (for better or worse, OOS 12 has a lot of issues but I don't want to risk another brick for awhile, especially since I'm not sure that the mod I made actually worked and it wasn't just some freak coincidence that let me flash back).
Thank you for your reply, the link you've send is downloading:
OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
I've presume that is for Global version, or is for EU version also?
EDIT:
Last try was:
MSM - OnePlus_9_Pro_EU_OxygenOS_11.2.2.2
Then update to:
OnePlus 9 Oxygen OS 11.2.10.10.LE25BA (EU)
- OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
Then, two options:
Oxygen updater -> C.47 ->Touchscreen death
OTA update -> OxygenOS 12.0 (C.48) (EU)
- OnePlus9Oxygen_22.E.11_OTA_0110_all_2107082125_downgrade_09b1a0a810824761.zip ->Touchscreen death
Im starting to be little bit despered, where is the problem. I've tried lost of combination but still no luck...
AtreyC said:
Thank you for your reply, the link you've send is downloading:
OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
I've presume that is for Global version, or is for EU version also?
EDIT:
Last try was:
MSM - OnePlus_9_Pro_EU_OxygenOS_11.2.2.2
Then update to:
OnePlus 9 Oxygen OS 11.2.10.10.LE25BA (EU)
- OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
Then, two options:
Oxygen updater -> C.47 ->Touchscreen death
OTA update -> OxygenOS 12.0 (C.48) (EU)
- OnePlus9Oxygen_22.E.11_OTA_0110_all_2107082125_downgrade_09b1a0a810824761.zip ->Touchscreen death
Im starting to be little bit despered, where is the problem. I've tried lost of combination but still no luck...
Click to expand...
Click to collapse
The same thing happened to me 2 days before and the conclusion was to use stock Android 11 or any custom ROM.
AtreyC said:
Thank you for your reply, the link you've send is downloading:
OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
I've presume that is for Global version, or is for EU version also?
EDIT:
Last try was:
MSM - OnePlus_9_Pro_EU_OxygenOS_11.2.2.2
Then update to:
OnePlus 9 Oxygen OS 11.2.10.10.LE25BA (EU)
- OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
Then, two options:
Oxygen updater -> C.47 ->Touchscreen death
OTA update -> OxygenOS 12.0 (C.48) (EU)
- OnePlus9Oxygen_22.E.11_OTA_0110_all_2107082125_downgrade_09b1a0a810824761.zip ->Touchscreen death
Im starting to be little bit despered, where is the problem. I've tried lost of combination but still no luck...
Click to expand...
Click to collapse
The link I sent you is the full stock EU image.
AtreyC said:
I'm looking for a captain who could help me find solution. Like "EtherealRemnant" in his post, Im not able to get OOS 12 work on my OP9.
EtherealRemnant post:
https://forum.xda-developers.com/t/...p9-stock-oos-11-2-2-2aa.4275727/post-86854951
Like "everyone" I've something messed up with TWRP boot and ended up with MSM tool. Cause I have LE2113 I have to use India MSM for 9Pro.
Then I use downgrade package to get stock OOS on my OP9, then use oficial way to update OOS, till highest A11. But whenever I use update to LE2113_11.C.47 it ended up with frozen/not working touch screen. Not just in OS but also in TWRP and stock recovery. I´ve tried also connect USB mouse, but with no successs.
My question, is there a way how to update to OOS (A12) without get freezed touchscreen?
Click to expand...
Click to collapse
Did you unlock the bootloader before you upgraded, the frozen non working touchscreen only happened when I upgraded with an unlocked bootloader. If you havent already try to MSM back to stock and then upgrade to OOS12 before you unlock the bootloader
jshinn1 said:
Did you unlock the bootloader before you upgraded, the frozen non working touchscreen only happened when I upgraded with an unlocked bootloader. If you havent already try to MSM back to stock and then upgrade to OOS12 before you unlock the bootloader
Click to expand...
Click to collapse
The broken touchscreen happened to me with a locked bootloader too. I know this because I was on 11.2.10.10 after spending hours figuring out how to get it back on full global firmware and I made the conscious decision not to mess with a custom ROM anymore after updating to 11.2.10.10 before I chose to use the OTA to upgrade to C.48 so I didn't unlock the bootloader. Then I ended up having to do the MSM again when my touchscreen didn't work.
EtherealRemnant said:
The broken touchscreen happened to me with a locked bootloader too. I know this because I was on 11.2.10.10 after spending hours figuring out how to get it back on full global firmware and I made the conscious decision not to mess with a custom ROM anymore after updating to 11.2.10.10 before I chose to use the OTA to upgrade to C.48 so I didn't unlock the bootloader. Then I ended up having to do the MSM again when my touchscreen didn't work.
Click to expand...
Click to collapse
Hmmm Im definitely no expert but if that doesn't work then hopefully somebody else can chime in with a solution.
jshinn1 said:
Hmmm Im definitely no expert but if that doesn't work then hopefully somebody else can chime in with a solution.
Click to expand...
Click to collapse
The only thing that worked for me was getting back to the stock global firmware with the MSM Tool. I modded the MSM Tool to do this since I was stuck on the India 9 Pro software and it worked for whatever reason but I had someone else try it and it didn't work for them and asking someone who knows about the MSM Tool, my fix shouldn't have worked for me either, so I took it down so as not to mislead anyone. As you can see though, OOS 12 is running fine.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@jshinn1 When I install MSM for OP9pro on my OP9, I've unlock bootloader to install downgrade for OP9 via TWRP. Then I try to update via OTAs, downloaded from Oxygen updater, or xda sources. Result is still same, death touch after install Android 12 update.
I've also tried swaping slots (A,B) in TWRP during install, no result.
So far only MSM capable unbrick my OP9 was Indian 9Pro and EU 9Pro. But in the end same result death touch.
I was able to fix it by modifying the settings.xml in the T-Mobile msm, I haven't had anyone else try but it's worked multiple times on my own. I can provide the link if anyone is interested. It's for the OP9 T-Mobile but I can easily change it to global if needed.
Sound promising, can you change it not to Global, but to EU (2113)?
Okay I will try it on my device and if all looks good report back with a download link.
XxBigBuckxX said:
I was able to fix it by modifying the settings.xml in the T-Mobile msm, I haven't had anyone else try but it's worked multiple times on my own. I can provide the link if anyone is interested. It's for the OP9 T-Mobile but I can easily change it to global if needed.
Click to expand...
Click to collapse
Can I ask how you did this? I modified the settings.xml on the global ROM to IN and it flashed mine that was stuck as an Indian 9 Pro but then failed params when I gave it to someone else and I haven't wanted to risk being stuck on IN firmware again to troubleshoot it. In my case all I did was change the Desc from O2 to IN and that did it but I gave it to someone with a T-Mobile device also flashed with Indian 9 Pro software and it didn't work... Figured it must be a fluke that it worked for me.
Problem SOLVED, see my edit in first post. Thank you all for participation.
AtreyC said:
Problem SOLVED, see my edit in first post. Thank you all for participation.
Click to expand...
Click to collapse
Glad you figured it out