I'm hoping someone can help me out here. I've been trying for hours to restore my OnePlus 8T with the global MSM tool and I keep getting the Sahara communication failed error over and over again. My drivers are successfully installed and I've tried 5 different USB ports and 3 different types of cables and nothing works. I've tried rebooting my PC multiple times, and 2 out of the 3 cables I've used are official OnePlus cables.
My phone stuck in edl.
Is there a possibility to get my phone back to life?
For me, I've been receiving this err when trying to use msm inside a windows kvm virtual machine with usb passthrough enabled...
When I switch to a normal windows install, no more errors.
So, it has been rumored that an usb 2.0 port works better than 3.0 for this.
Also check whether your tool fits your device or not. Log shows your tool is for T-Mobile version, do you have a kb2007?
If you do have a kb2007, I can confirm that MsmTools from here [ https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180981/ ] works.
Also check this [ https://forum.xda-developers.com/t/...-global-version-with-msmdownloadtool.4495057/ ] if you want global OOS instead of TMO's older version installed.
You can also try to press power button for a long time like 30s to reboot your device (still into edl mode but might fix some random errors).
IAAxl said:
For me, I've been receiving this err when trying to use msm inside a windows kvm virtual machine with usb passthrough enabled...
When I switch to a normal windows install, no more errors.
So, it has been rumored that an usb 2.0 port works better than 3.0 for this.
Also check whether your tool fits your device or not. Log shows your tool is for T-Mobile version, do you have a kb2007?
If you do have a kb2007, I can confirm that MsmTools from here [ https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180981/ ] works.
Also check this [ https://forum.xda-developers.com/t/...-global-version-with-msmdownloadtool.4495057/ ] if you want global OOS instead of TMO's older version installed.
You can also try to press power button for a long time like 30s to reboot your device (still into edl mode but might fix some random errors).
Click to expand...
Click to collapse
new error "unsupported target h2, Preload Param" appeared
BladeForm said:
new error "unsupported target h2, Preload Param" appeared
Click to expand...
Click to collapse
That means you're using worng version msmtool.
In the log it shows that you're trying to flash kebabt_15_O.01_210121, which means TMO version rom.
But your device (aka target to flash) is "h2" version, not TMO version. So the error comes out.
ARE YOH SURE YOU'RE HOLDING A T-MOBILE 8T???
I don't know exactly what "h2" stands for, but definitely not TMO, for I have a TMO 8T and the target code is "TMO".
Tell me how do you get this phone. I doubt"h2" might stand for Chinese version but I'm not sure.
If you want to cross-flash other region's rom, you must modify the msmtool manually.
And this might help if your phone isn't Chinese brand (aka kb2000).
[SOLVED] Unbrick hard-bricked OP 8T
Hello people, unfortunately, I bricked my phone and am stuck trying to unbrick it. How the bricking happened: I bricked my OP 8T when I tried to update my OS from Lineage OS 18.1 (Android 11) to 19.1 (Android 12) following this guide: Official...
forum.xda-developers.com
If your phone do is Chinese brand, XDA can't provide you a suitable msmtool because that version runs a Chinese-only system. You have to find it yourself.
If you find it, you do can cross-flash it to global version with the method provided below:
[Guide] Convert locked OnePlus 8T TMO to Global version with MsmDownloadTool
This can: Bypass TMO flash lock as it uses 9008 EDL. Remove TMO sim lock and oem lock as you will be using global rom. Convert your KB2007 (KB09CB) to KB2005 (KB05AA) as much as possible. (Although you're using the latest KB2005 firmware, any...
forum.xda-developers.com
IAAxl said:
That means you're using worng version msmtool.
In the log it shows that you're trying to flash kebabt_15_O.01_210121, which means TMO version rom.
But your device (aka target to flash) is "h2" version, not TMO version. So the error comes out.
ARE YOH SURE YOU'RE HOLDING A T-MOBILE 8T???
I don't know exactly what "h2" stands for, but definitely not TMO, for I have a TMO 8T and the target code is "TMO".
Tell me how do you get this phone. I doubt"h2" might stand for Chinese version but I'm not sure.
If you want to cross-flash other region's rom, you must modify the msmtool manually.
Click to expand...
Click to collapse
I made a typo, I don't have T-MOBILE
BladeForm said:
I made a typo, I don't have T-MOBILE
Click to expand...
Click to collapse
Then stop using TMO version msmtool.
Go get the version that matches your device.
Your log file shows you're using TMO msmtool. This will never work.
IAAxl said:
Then stop using TMO version msmtool.
Go get the version that matches your device.
Your log file shows you're using TMO msmtool. This will never work.
Click to expand...
Click to collapse
flashed through msm to the system does not load, the bootloader is closed
Is there a possibility to get my phone back to life?
Not enough info...
BladeForm said:
flashed through msm
Click to expand...
Click to collapse
Does the flash succeed? What version of msm tool did you use?
BladeForm said:
the system does not load
Click to expand...
Click to collapse
Any error message? Please describe how you get this and what did you do exactly.
BladeForm said:
the bootloader is closed
Click to expand...
Click to collapse
Is this differs from the status before flash? By saying closed, do you mean fastboot flash is locked?
BladeForm said:
Is there a possibility to get my phone back to life?
Click to expand...
Click to collapse
Hard to say. If your device has no failure hardware, the chance is good. But you should provide more info so that others could tell.
Related
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 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
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
my one plus 9 LE2119 has been dead when i unlock with umt if any one have flash file please send me..
hello brother did you find the files?
OnePlus 9/9 Pro have their respective MSM Tools to unbrick.
shadabkiani said:
OnePlus 9/9 Pro have their respective MSM Tools to unbrick.
Click to expand...
Click to collapse
Do you have this model?
Kumail2233 said:
Do you have this model?
Click to expand...
Click to collapse
I have OnePlus LE2110 (Chinese variant). But it gets the update for LE2115 (Global/NA variant). I use MSM Tool for Global.
Did it give device mismatch error in msm tool? What tool are you using
Kumail2233 said:
Did it give device mismatch error in msm tool? What tool are you using
Click to expand...
Click to collapse
No. Although my device is LE2110, but OTA updates automatically get the updates for LE2115. So I can use MSM Global Tool for LE2115 too, and I don't have to convert or anything.
In your case, maybe this will work to convert:
Convert T-Mobile OnePlus 9 to Global (or other) firmware
** USE THIS AT YOUR OWN RISK. ** READ THROUGH THE STEPS BEFORE ATTEMPTING. IF AT ANY POINT WHILE READING THESE STEPS YOU GET CONFUSED, YOU PROBABLY SHOULDN'T ATTEMPT THIS. ** BACKUP YOUR FILES AND APP DATA AS THIS WILL WIPE YOUR PHONE. ** BACKUP...
forum.xda-developers.com
Use at your own risk though. I haven't done this, and I take no responsibility.
shadabkiani said:
No. Although my device is LE2110, but OTA updates automatically get the updates for LE2115. So I can use MSM Global Tool for LE2115 too, and I don't have to convert or anything.
In your case, maybe this will work to convert:
Convert T-Mobile OnePlus 9 to Global (or other) firmware
** USE THIS AT YOUR OWN RISK. ** READ THROUGH THE STEPS BEFORE ATTEMPTING. IF AT ANY POINT WHILE READING THESE STEPS YOU GET CONFUSED, YOU PROBABLY SHOULDN'T ATTEMPT THIS. ** BACKUP YOUR FILES AND APP DATA AS THIS WILL WIPE YOUR PHONE. ** BACKUP...
forum.xda-developers.com
Use at your own risk though. I haven't done this, and I take no responsibility.
Click to expand...
Click to collapse
This didn't work brother and the phone gets bricked. I got is fixed from some local shop who bought around 300 pieces of this model and had the stock files. They said the sim will not work and you can't update.
Kumail2233 said:
This didn't work brother and the phone gets bricked. I got is fixed from some local shop who bought around 300 pieces of this model and had the stock files. They said the sim will not work and you can't update.
Click to expand...
Click to collapse
I really have no idea. Never heard of LE2119 variant. How about you unlock bootloader and then install custom ROMs? They are way better than OOS. I would personally suggest crDroid or Nameless. They have tons of features and are stable.
shadabkiani said:
I really have no idea. Never heard of LE2119 variant. How about you unlock bootloader and then install custom ROMs? They are way better than OOS. I would personally suggest crDroid or Nameless. They have tons of features and are stable.
Click to expand...
Click to collapse
I'm afraid that it won't boot and I'll have to take it to the shop again. The signal is also locked but the Phone software is perfect while running A11 Stock
Kumail2233 said:
I'm afraid that it won't boot and I'll have to take it to the shop again. The signal is also locked but the Phone software is perfect while running A11 Stock
Click to expand...
Click to collapse
Ok. If you wanna go the safe way, download Oxygen Updater app from Play Store. Then download incremental firmware zip from there and try to update through System Update's Local Update option. If it's not compatible, the system just would not flash it at all.
shadabkiani said:
Ok. If you wanna go the safe way, download Oxygen Updater app from Play Store. Then download incremental firmware zip from there and try to update through System Update's Local Update option. If it's not compatible, the system just would not flash it at all.
Click to expand...
Click to collapse
I downloaded the update but it won't install. Installation failed
Kumail2233 said:
I downloaded the update but it won't install. Installation failed
Click to expand...
Click to collapse
Then I'm afraid I can't suggest anything else. You have to experiment on your own.
shadabkiani said:
Then I'm afraid I can't suggest anything else. You have to experiment on your own.
Click to expand...
Click to collapse
can I make a msm tool for this model?
Kumail2233 said:
can I make a msm tool for this model?
Click to expand...
Click to collapse
Are you a developer? Even if you are, you would have to be an employee at OnePlus to know what goes on in MSM Tool. If you really wanna experiment, I suggest you unlock bootloader and try custom ROMs. At least unlock bootloader and see if you can do that. There would be no harm. In T-Mobile variants, you can't unlock the bootloader simply, it asks for unlock token and you have to wait a few days. So, if you can unlock bootloader the simple way, there would be hope that this device isn't doesn't have freaky security like T-Mobile.
i can fix this device they basically killed by flashing wrong img & now its not able to take stock file if anyone have device in hand to test then DM me I'll build file for this.
Make sure i need full info
and it's may not done in 1st attempt