Hi, so the Android 12 beta soft bricked my OP9 and im stuck in pin verification loop. Im trying to revert back to Android 11 using MSMDownloadTool but every time i press start when the phone is connected in EDL mode, it returns "Param preload error" after about 10s. I tried different ports, i tried reinstalling all the drivers but then every time i hit the param preload error. I dont know what to do about it. I have european OP9 model (or i at least think so) but the downgrade is availible only in T-Mobile or India versions. Is that the problem, should i wait for european?
Is there perhaps simpler way to reset the OP9 back to Android 11 since it still boots up and its not hard bricked?
Try fastboot flashing a ROM using a flashall.
Press start on msm first. So you see waiting on phone. Then reboot to edl mode.
It only works on the first few seconds of edl otherwise always fails.
Where did you get the MSMtool, and will you share it?
XNine said:
Where did you get the MSMtool, and will you share it?
Click to expand...
Click to collapse
OnePlus 9 11.2.22.2 (T-Mobile) MSM Download Tool
Oxygen OS 11.2.22.2.LE54CB (T-Mobile) Download: https://drive.google.com/file/d/1-5RC9f8es6ZrwpYKKQBMmw5gW-rzDSfZ/view?usp=sharing Size: 2.92 GB MD5: b6fc004c81d311109f66cceb3f375862
forum.xda-developers.com
This is for t-mobile version.
MSM tools are region/brand specific
Related
Hello XDA Members,
Please help me i have hard bricked oneplus 8 IN2017 Tmobile while installing Custom pixel Experience ROM
and now MSM tool Unbrick tool not working its shows download complete but phone is not booting after showing oneplus logo phone goes to EDL mode.
also i am not able to flash stock fastboot rom because bootloader is locked. Please help me how to unbrick this phone
Try MSM again, on a different PC and with a different USB cable *if* you can.
Aside from that contact OnePlus.
Was this your first time using MS download tool? Have you succesfully flashed to stock with MSM before?
yes i have used msm many times and tried on different PCs nothing is working
msm tool shows successfully download complete and now i am receiving this error (PIC attached)
i think i have messed up partitions.
Hi all,
After en epic failure of rooting process my OnePlus 8T is bricked: no bootloader, no fastboot, no recovery, nothing. The phone screen stays black and power button has no effect.
However, it can enter EDL mode and is recognized as "Qualcomm HS-USB Diagnostics 900E" in in Windows device manager. So I should be able to use MSMDownload Tool to (try to) unbrick my phone.
Just one problem: I don't really know if my phone is EU version or Global version.
In its back, its written "Model: KB2003" so it should be EU version right? But before bricking it, I've tried to flash Global version... which bricked it (I don't know if that's the reason or if I made an other mistake but...).
Do you know how can I guess the region of my OnePlus 8T?
And if I flash Global version with MSMDownload Tool while I have an EU phone (or inverse), is it dangerous?
Thanks a lot for your help!
KB2003 is the EU version. So best to use the EU MSM tool.
Hi @Qnorsten
Well, I tought my phone was Global so I used Global MSM... The process was a bit weird:
- Global MSM Download Tool restored my phone on Android 11
- once on Android home several updates have been found and one of these updates was KB2005_11_***** (and after this update my phone was recognized as "Model: KB2005" :]
- but after remaining updates (I think there were 5 or 6 consecutive updates) my phone is now on KB2003_11_C.33 and recognized as "Model: KB2003"
So this OP8T has been restored on Global OS, then updated on US OS and finally returned to EU OS :]
Weird but it's a good ending
CrissaegrimRusk said:
Hi @Qnorsten
Well, I tought my phone was Global so I used Global MSM... The process was a bit weird:
- Global MSM Download Tool restored my phone on Android 11
- once on Android home several updates have been found and one of these updates was KB2005_11_***** (and after this update my phone was recognized as "Model: KB2005" :]
- but after remaining updates (I think there were 5 or 6 consecutive updates) my phone is now on KB2003_11_C.33 and recognized as "Model: KB2003"
So this OP8T has been restored on Global OS, then updated on US OS and finally returned to EU OS :]
Weird but it's a good ending
Click to expand...
Click to collapse
A bit strange, but as long as it worked for you everything is fine I guess
Qnorsten said:
A bit strange, but as long as it worked for you everything is fine I guess
Click to expand...
Click to collapse
Yes definitely I really though my phone was dead.
When I set it to EDL mode, it stayed in this mode only 12 seconds then switched to "Qualcomm HS-USB Diagnostics 900E" state.
I tried to run MSMDownload Tool during these 12 seconds (I knew the process was longer than 12 seconds but as my phone seemed dead I guessed maybe the bootloader could be restored during these 12 seconds).
But starting the process allowed the phone to stay "stuck" in EDL mode.
Good experience. But now I won't try to root my phone once again.
I can't seem to get past the image verification on msmtool, ive read previous phones like op6t had patched msmdownloadtool for this. I have tried all qualcomm drivers (qcser.inf/Installer-10037.3/10039.2). I cant get into bootloader otherwise I would flash fastboot rom.
I'm using windows 10 (64x), oneplus original red cable for this, I've tried all msmtool versions for global, europe and india and they're all stuck on the same error message. The device was bought in europe and has the a2003 model number. Please help me out
vvnpyr said:
I can't seem to get past the image verification on msmtool, ive read previous phones like op6t had patched msmdownloadtool for this. I have tried all qualcomm drivers (qcser.inf/Installer-10037.3/10039.2). I cant get into bootloader otherwise I would flash fastboot rom.
I'm using windows 10 (64x), oneplus original red cable for this, I've tried all msmtool versions for global, europe and india and they're all stuck on the same error message. The device was bought in europe and has the a2003 model number. Please help me out
Click to expand...
Click to collapse
see this thread:
[OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
So i tried to flash some firmware for a custom rom with enhanced fastboot. afterwards the phone booted into EDL mode and only EDL mode. i cant get bootloader, fastboot, recovery, or even system boot. before when this has happened msm tool worked well, but now ive tried 4 diff msm tool repacks, 2 diff versions of QFIL. MSM tool gets stuck on "start download firehose binary". then errors out to "sahara communication failed". QFIL errors to "qdssloader fail" or "924 sahara protocol error" and " qsahara server fail". the github edl utility reports "sahara in unknown mode, resetting". ive tried many cmd utilities, python utilities, qualcomm utilities, etc. idk if its completely gone or if there is a way to save it such as switching boot slots without fastboot? i have tried the EDL python utility and it says process completed on boot slot switching but still the same EDL only boot and unresponsive flashing attempts. i have tried like 30 different methods and 2 OSes to try and remedy this issue. i also have telegram and discord for one on one help: @rivapeeva riva!#0451
Have you tried the Indian MSM tool? I thought I was boned when I was messing with my phone a couple of weeks ago, and that was the only thing that worked for me.
riva! said:
So i tried to flash some firmware for a custom rom with enhanced fastboot. afterwards the phone booted into EDL mode and only EDL mode. i cant get bootloader, fastboot, recovery, or even system boot. before when this has happened msm tool worked well, but now ive tried 4 diff msm tool repacks, 2 diff versions of QFIL. MSM tool gets stuck on "start download firehose binary". then errors out to "sahara communication failed". QFIL errors to "qdssloader fail" or "924 sahara protocol error" and " qsahara server fail". the github edl utility reports "sahara in unknown mode, resetting". ive tried many cmd utilities, python utilities, qualcomm utilities, etc. idk if its completely gone or if there is a way to save it such as switching boot slots without fastboot? i have tried the EDL python utility and it says process completed on boot slot switching but still the same EDL only boot and unresponsive flashing attempts. i have tried like 30 different methods and 2 OSes to try and remedy this issue. i also have telegram and discord for one on one help: @rivapeeva riva!#0451
Click to expand...
Click to collapse
Are you TMobile or global 9?
Frosthaxx said:
Are you TMobile or global 9?
Click to expand...
Click to collapse
tmobile
posar said:
Have you tried the Indian MSM tool? I thought I was boned when I was messing with my phone a couple of weeks ago, and that was the only thing that worked for me.
Click to expand...
Click to collapse
i tried the UE tool, the indian tool, the na tool, the tmobile tool, and the conversion tool.
riva! said:
i tried the UE tool, the indian tool, the na tool, the tmobile tool, and the conversion tool.
Click to expand...
Click to collapse
Indian msm tool works on lite Firehose. Then use TMobile India mod and you can from there do what you need to do. Caution however. Doing the Indian trick makes your bootloader to the Indian bootloader but all functions will still work. You just can't use normal msms anymore
Unfortunately the bricking your describing is what happened to me because I goofed something. But I was able to get back using this to TMobile India after Indian. Then using the bootloader unlock guide in TMobile.a few update scenarios, then eventually evolution x. Unless someone has a better way there's not much written about this situation. I had to figure it out myself
IF ANYONE needs info on how i managed to fix this, please dm me or add my socials. If you flashed the wrong xbl/xbl_config files and now your sahara/firehose doesnt work, feel free to reach out. it took me 4 days straight of surfing and downloading and trial and error.
Unfortunately I don't think my issue can be fixed. There isn't anything specifically on fixing Indian region bootloader. Once that's done I think it's sol but it still works normal. I had to however because my brick also wasn't reading the USB either. It was a very odd situation. And I've modded and given advice on multiple phones. I'm glad you got yours working though. Doesn't bother me though
Phone works and the India mod get me back where needed. But others that haven't flashed the Indian msm tool could benefit from your find
Trying to flash my friend's phone back to stock but having some issues, you might have seen twixyfig's post in the OnePlus 9 Pro threads, but it's a regular OP9 and not the Pro.
Anyways, I have been trying to flash to working condition but MSM won't help. It keeps saying "No valid trg ID" and "Param preload" for a while now. This happened because we tried to root the phone but failed. The bootloader is unlocked, and fastboot works too.
TIA.
Whenever you post asking for help, always make sure to add as many details as possible. Your phone model, variant, current firmware, the tool you are using, the tools you used before, the steps you took before you started facing issues, every detail you can possibly tell. Only then someone might be able to help.
shadabkiani said:
Whenever you post asking for help, always make sure to add as many details as possible. Your phone model, variant, current firmware, the tool you are using, the tools you used before, the steps you took before you started facing issues, every detail you can possibly tell. Only then someone might be able to help.
Click to expand...
Click to collapse
So its a oneplus 9 (Chinese model), before it got bricked it was on android 12, we tried MSM V5.1.89 and CMD, cmd said " No boot.img found "
twixyfig said:
So its a oneplus 9 (Chinese model), before it got bricked it was on android 12, we tried MSM V5.1.89 and CMD, cmd said " No boot.img found "
Click to expand...
Click to collapse
Download the MSM Tool (Global) from this link. Global works on Chinese variant (LE2110) too. Have proper drivers OnePlus drivers installed. Turn off your phone and set it aside, do not connect to PC yet. Run the MSM Tool exe file. Once its loaded, click Start and it should wait for device. Now on your phone, hold vol+ and vol- buttons (no power button), and connect the cable to phone. This will make the phone enter EDL mode. The PC would recognize the device (USB plugged in sound) but phone screen would still be black. On MSM, the flashing would start and would be done in about 4-5 mins. Good luck.
shadabkiani said:
Download the MSM Tool (Global) from this link. Global works on Chinese variant (LE2110) too. Have proper drivers OnePlus drivers installed. Turn off your phone and set it aside, do not connect to PC yet. Run the MSM Tool exe file. Once its loaded, click Start and it should wait for device. Now on your phone, hold vol+ and vol- buttons (no power button), and connect the cable to phone. This will make the phone enter EDL mode. The PC would recognize the device (USB plugged in sound) but phone screen would still be black. On MSM, the flashing would start and would be done in about 4-5 mins. Good luck.
Click to expand...
Click to collapse
Thanks! Im gonna try this today and give you an update when something happens
twixyfig said:
Thanks! Im gonna try this today and give you an update when something happens
Click to expand...
Click to collapse
I think you were trying Indian MSM Tool. That might be the problem.
When your open MSM Tool, choose Others as login.
Write me in dm and I will help you, I think I can solve your problem
you can download OP9PRO India MSM tool(OnePlus_9_Pro_India_OxygenOS_11.2.4.4) and
1.unzip OP9Pro India ROM and download to your phone(select the firhose chebox)
2.if you success to download it,your phone will restart to the OOS.
3.Login your Google account and unlock OEM,then reboot your phone
4. install "Oxygen Updater", VERSION 5.7.3,you can find it on github.
5.download OOS for OP9 , archive name is "1797d47ddef0fca1411fb006b9c7a1a7ba33d818.zip"
6.enter the oxygen updater,and flash "1797d47ddef0fca1411fb006b9c7a1a7ba33d818.zip" to your phone
7.reboot and fixed!
PS: my english is so suck,try to read it!
good luck!