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
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?
Kay, backstory. I bricked my phone, and MSM for the Global didn't work. I used the op9 pro indian MSM, and that worked, so now I'm with the incorrect firmware. OTA won't work, for whatever reason, so what should I do? No bootloader unlocking, not doing that stuff again
You can try fastboot image. You can find one around here. Otherwise, root, download full zip via OOS Updater and do a local update.
Twrp is also working for our device now, at least mostly.
gorilla p said:
You can try fastboot image. You can find one around here. Otherwise, root, download full zip via OOS Updater and do a local update.
Twrp is also working for our device now, at least mostly.
Click to expand...
Click to collapse
I would, but I don't wanna unlock bootloader
winterfoxx said:
I would, but I don't wanna unlock bootloader
Click to expand...
Click to collapse
I don't think there is a way to get back to global without
XxBigBuckxX said:
I don't think there is a way to get back to global without
Click to expand...
Click to collapse
I pulled it off, and am working on a comprehensive unbricking guide. Thanks!
winterfoxx said:
I pulled it off, and am working on a comprehensive unbricking guide. Thanks!
Click to expand...
Click to collapse
is it ready im in the same boat and curious on how you did it?
YourLocalDund33 said:
is it ready im in the same boat and curious on how you did it?
Click to expand...
Click to collapse
Yes, sorry about the late reply, here:
Global/US unbricking guide.
Global/US OnePlus 9 Unbricking Guide Tested and used on a LE2115 variant device. YOU SHOULDN'T USE THIS GUIDE UNLESS YOU ARE ABSOLUTELY SURE YOUR PHONE IS BRICKED. PLEASE TRY POWER COMBOS FIRST! THERE ARE NO GUARANTEES, AND THIS SHOULD BE A LAST...
forum.xda-developers.com
Okay so I was finally able to flash back to the tmobile firmware using msm tool
I'm testing everything out now but it seems fine still had to trick it into thinking it was the IN variant.
XxBigBuckxX said:
I'm testing everything out now but it seems fine still had to trick it into thinking it was the IN variant.
Click to expand...
Click to collapse
How exactly did you trick it?
JimmyJurner said:
How exactly did you trick it?
Click to expand...
Click to collapse
You download the msm tool you need and oppo_decrypt to extract the .ops file. Then there will be a file created called settings.xml and you just need to edit that file and add one line to the bottom in-between <SupportMultiTarget> , run oppo tool again to put it one big .ops file, So more so not trick it but just add support to for the IN model. Until I can figure out how to make it change on the actually device this is the best I can come up with. This is only if you are having trouble using your original msm tool and having to use the Indian Pro version. Its solved all my issues.
XML:
<Target ID="3" Desc="India" />
Hello all, after lurking here for a while, I found something that's making me post.
I have a carrier locked OP9. I just received the update to Android 12, and it has broken critical features. (Particularly not being able to stop apps from being closed accidentally!)
I have looked at Lineage OS in the past, and the process to get the LE2117's bootloader unlocked was... complicated.
However, while trying to fix other problems, rooting around in the developer options, I noticed that "unlock bootloader" was actually toggleable!
I think I have an unlocked bootloader now, but it's on android 12, and all the guides for rooting and installing a custom MOD for this phone say you must revert to android 11 before anything else.
So what now? Am I waiting for lineageOS 19 to come out, because that's the one based on android 12? I'm new to custom roms, and don't get the coding side of how all this works. (But I'm pretty determined to figure this out.)
Thanks for any help or advice you've got!
each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!
Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.
dark_sable said:
Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.
Click to expand...
Click to collapse
I am pretty sure there is root for 12. All you need to do is dump the payload from the 12 update OnePlus let's loose, and patch it with magisk and flash it via fastboot. Via bootloader it is easy I am using a TMobile OnePlus 9. All you need to do is revert back to 11 via a msm tool. There is a post here for that. After downgrading to unlock your bootloader is easy only takes time. There is a post for it I don't remember all the details but all you have to do is get you imei code and email OnePlus. Soon they will sent you a code to fastboot flash to unlock the bootloader. After that most of these 12 work for us on our model phone. I am using evolution x. It tells me every day I can go to 12 .
funkybear34 said:
each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!
Click to expand...
Click to collapse
Yes yes they do.
I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.
JimmyL216 said:
I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.
Click to expand...
Click to collapse
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.
EtherealRemnant said:
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.
Click to expand...
Click to collapse
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode
JimmyL216 said:
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode
Click to expand...
Click to collapse
What worked for me was shutting the phone off, removing my case, holding both volume up and down, then plugging the phone in. The screen won't show anything, you have to look at the MSM Tool and see that it's connected to know you did it right. Both times I tried it worked perfectly.
You can also use adb reboot edl if you can get the thing to boot and have USB debugging turned on.
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.
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