Question Super-Hard Bricked OnePlus 9 - OnePlus 9

I have an extremely big problem, maybe someone could help me here?
So today I tried to flash diffrent OOS version on my OnePlus 9, I did it with fastboot, after the command "fastboot reboot fastboot" the screen on the phone went blank and there was a sound on the computer as if the phone was still connecting and disconnecting. Now, the phone does not respond to the buttons, the charger, I cannot enter the fastboot, only the EDL mode works, but I cannot use the MSM because it does not detect the phone, I get the "sahara communication failed" notification all the time, previously the same MSM version was working.
Probably the most important thing is that it turned out that the OOS I tried to flash was actually ColorOS, I didn't pay attention to it, I don't know how it happened.
I feel like an idiot, I'm afraid that I will not save this phone myself and that the repair service will also not accept it under warranty, any suggestions?

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

Rayekk said:
I have an extremely big problem, maybe someone could help me here?
So today I tried to flash diffrent OOS version on my OnePlus 9, I did it with fastboot, after the command "fastboot reboot fastboot" the screen on the phone went blank and there was a sound on the computer as if the phone was still connecting and disconnecting. Now, the phone does not respond to the buttons, the charger, I cannot enter the fastboot, only the EDL mode works, but I cannot use the MSM because it does not detect the phone, I get the "sahara communication failed" notification all the time, previously the same MSM version was working.
Probably the most important thing is that it turned out that the OOS I tried to flash was actually ColorOS, I didn't pay attention to it, I don't know how it happened.
I feel like an idiot, I'm afraid that I will not save this phone myself and that the repair service will also not accept it under warranty, any suggestions?
Click to expand...
Click to collapse
See link below. Worked for me I was in same position.

ctonylee1965 said:
See link below. Worked for me I was in same position.
Click to expand...
Click to collapse
Thank you very much! Tbh I can't understand how and why it works, but it worked!

Rayekk said:
Thank you very much! Tbh I can't understand how and why it works, but it worked!
Click to expand...
Click to collapse
Make sure you look at the rest of the instructions to get back on global from Indian.

Rayekk said:
Thank you very much! Tbh I can't understand how and why it works, but it worked!
Click to expand...
Click to collapse
Brother what is your phone model is it Chinese (Le2110)? or another model ?

bro i have the same issues , did u found any solution & can you help me plz

See if these steps work for you: (last post)
Display becomes unresponsive after OOS 12 update
I upgraded my OnePlus 9 LE2115 from OOS 11 to OOS 12, and every time the phone reboots after completing the update, the touch screen is completely unresponsive, so it stays stuck at the lock screen forever. I upgraded from OOS 11.2.10.10 to OOS...
forum.xda-developers.com

Hey, i have hardbricked my OnePlus 9 and now i have the connect and disconnect-problem in the EDL-Mode. My Model is a Lahaina and i hope it is the same like a Lemonade or a OnePlus 9. I was on the latest Android 12 for the OP 9 before it gets bricked. How i bricked my phone: First i have unlocked the Bootloader and after that i was trying to boot into TWRP. The bootscreen from TWRP comes and the screen gets black and then into boot dump mode. okay, then i installed this: https://forum.xda-developers.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/unread and the message <awaiting any device> shows up and i disconnected my phone. After that my phone just shows black and on the pc it just shows up the "QDLoader" (yes, the driver is installed) . How i could bring my phone back to life and fix the partitionproblem/connect & disconnect problem. The MSM just shows "Status of Connection: N/A" and "Waiting for device". I am using an Laptop with Windows 10 on it and an intel chipset.
I think i have killed the partitioning of the oneplus by downgrading from A 12 to A 11. Thanks for your help. By the way: I have downloaded the MSM with Indian OS and I have still the same problem.

I´ve got exactly the same situation and problem as DerBaLu841... Anything to do for now or is the OP9 finally hard bricked now..?

kischde said:
I´ve got exactly the same situation and problem as DerBaLu841... Anything to do for now or is the OP9 finally hard bricked now..?
Click to expand...
Click to collapse
Check this out:
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

DerBaLu841 said:
Check this out:
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
Click to expand...
Click to collapse
Hi! Have you telegram? Can I ask to you help with the method you posted?

Related

Question My oneplus 9 le2110 stuck in EDL mode

I try all commands and procedure like volume+/- and power button all things but still screen is black and when i connect it to pc in manager it show me qualcomm 9008..
And when i flash it with msm tool oneplus 9 msm tool india it always show me error
Wrong suggestion, so I edited it out. Good luck unbricking
noname122414 said:
Wrong suggestion, so I edited it out. Good luck unbricking
Click to expand...
Click to collapse
How?
I saw in another post that you are aware of your chinese version. So you probably already tried flashing this version ( https://forum.xda-developers.com/t/official-oneplus-9-oxygen-to-color-and-back.4256457/ ) just patch the to Oxygen again on the chinese version.
How i can patch i told my phone is stuck in Edl mode hard brick
So no fastboot commands are working? Fastboot devices says nothing? Say what you tried, and your current situation in as much detail as possible. People can only help you when they understand what happened and what is still possible to do.
Brother my device is stuck in Edl mode because when i connect to pc it show me qualcomm 9008 in device manager..
I tried all Fastboot commands, power + , power - button & power button but nothing happened still device stuck in Edl mode and also msm tools of india doesn't work
Did you ever get a good flash from msm tool? If not try the original chinese version phone came with.
Also you can try holding power button until phone reboots but nothing to boot too will just go back to edl.
Y
nujackk said:
Did you ever get a good flash from msm tool? If not try the original chinese version phone came with.
Also you can try holding power button until phone reboots but nothing to boot too will just go back to edl.
Click to expand...
Click to collapse
Yes i use msm tools many time on another devices it works but on this case it doesn't work on oneplus 9
Wolverine619 said:
Y
Yes i use msm tools many time on another devices it works but on this case it doesn't work on oneplus 9
Click to expand...
Click to collapse
Sorry bud, if you can't get a good flash with msm you're stuck far as i know.
nujackk said:
Sorry bud, if you can't get a good flash with msm you're stuck far as i know.
Click to expand...
Click to collapse
Do you told me about solution?
My phone battery was 100% when it's stuck in Edl mode any idea for 100% to 0%?
Holding the power button an unreasonable long time always worked for me did it with 6 and 7pro. Even if it goes back to edl if you have msm ready and waiting for device v when it reboots to edl should pick it up and begin flash
nujackk said:
Holding the power button an unreasonable long time always worked for me did it with 6 and 7pro. Even if it goes back to edl if you have msm ready and waiting for device v when it reboots to edl should pick it up and begin flash
Click to expand...
Click to collapse
See brother
I see what you mean. Not sure what sahara error state is. Not sure you'll be able to fix that on your own. You may need to contact oneplus see if they can help. They tend to be willing to help in most cases. But may cost you since I'm sure this wouldn't be covered under warranty.
sahara error usually happens when you flash the wrong firmware.
noname122414 said:
sahara error usually happens when you flash the wrong firmware.
Click to expand...
Click to collapse
Can anyone tell me how to fix it?
Did you try everything what's written here? https://blog.hovatek.com/how-to-fix-sahara-fail-error-in-qfil/ when nothing there first with your problem then write here again.
noname122414 said:
Did you try everything what's written here? https://blog.hovatek.com/how-to-fix-sahara-fail-error-in-qfil/ when nothing there first with your problem then write here again.
Click to expand...
Click to collapse
I don't have file's for oneplus 9
Any one know how to extract .ops file of Msm tool
Wolverine619 said:
I don't have file's for oneplus 9
Any one know how to extract .ops file of Msm tool
Click to expand...
Click to collapse
"Payload dumper 64" can get the files for you that's an application there is also a python script which does the same.
I personally used "payload dumper 64" then flashed the files vis fastboot to recover 2 Chinese variant until now( you have to use the right rom which is normally used to switch from Chinese rom to Oxygen)
This is just how I recovered the phones.
Edit: sorry it's late you are probably looking for the msm download tool files, I probably messed things up

The device does not run on black screen

Greetings to all
After flash rom on fastboot and rebooting the device, the device entered the recovery, but the recovery is not working just black screen
I have pressed the power button and volume down button for a long time but nothing works
Currently the device is completely damaged!!!
I want to get into the bootloader in any way
Power up and connect to a Windows PC, what does the device manager display?
ULTRAJC said:
Power up and connect to a Windows PC, what does the device manager display?
Click to expand...
Click to collapse
I was trying to connect it to a Mac
It is now connected to a Windows device and the device recognizes it
""Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0412_SN10E679A""
twuijri said:
I was trying to connect it to a Mac
It is now connected to a Windows device and the device recognizes it
""Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0412_SN10E679A""
Click to expand...
Click to collapse
I'm not sure what your ROM installation process was, however at this point sounds like you need to use the MSM tool and recover your phone.
Unbrick tool to restore your device to OxygenOS <-- Use this thread.
Also from that thread:
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update.
Click to expand...
Click to collapse
Drivers are in that thread.
Screen will be blank / off during this process when you are in this mode (what you are seeing). At least that is what I believe you are describing / seeing.
OhioYJ said:
I'm not sure what your ROM installation process was, however at this point sounds like you need to use the MSM tool and recover your phone.
Unbrick tool to restore your device to OxygenOS <-- Use this thread.
Also from that thread:
Drivers are in that thread.
Screen will be blank / off during this process when you are in this mode (what you are seeing). At least that is what I believe you are describing / seeing.
Click to expand...
Click to collapse
Thank you, the device has come back to life after using ""MsmDownloadTool Global_KB05AA"" my phone ""oneplus 8T KB2000""
After the device worked, I ran into another problem ""QUALCOMM CrashDump Mode""
Is there a MsmDownloadTool for China devices oneplus 8T KB2000?
I'm so sorry for the problems I'm raising but I need help
Thank you for your time and help in solving other people's problems
twuijri said:
Thank you, the device has come back to life after using ""MsmDownloadTool Global_KB05AA"" my phone ""oneplus 8T KB2000""
After the device worked, I ran into another problem ""QUALCOMM CrashDump Mode""
Is there a MsmDownloadTool for China devices oneplus 8T KB2000?
I'm so sorry for the problems I'm raising but I need help
Thank you for your time and help in solving other people's problems
Click to expand...
Click to collapse
Some_Random_Username said:
Why is my device getting in Qualcomm crashdump mode in spite of a successful download?
Your unit was most likely manufactured after March 9th 2021, see https://forum.xda-developers.com/t/...ice-to-oxygenos.4180837/page-14#post-84789741 for reference. You therefore need to use HydrogenOS 11.0.7.12 MSM to recover your device linked at https://www.oneplusbbs.com/thread-5886794-1.html (mirrored at https://mega.nz/file/O8UySbgR#cXGlHkdA_7CYEhKIrek9zzAEwJ7Vx1D5BZdemnPlvGE by @pikatenor ). Getting new OxygenOS MSM tools is nowadays impossible unless you own the device it is meant for, so OP will not be updated to add new OxygenOS MSM tools allowing to workaround this issue. Feel however free to reach out to me in DM if you would like to get told how to maximise your chances to obtain one.
Click to expand...
Click to collapse
Thank you from the heart. I read the entire topic and tried all the methods. It took me 10 hours to work
I was so frustrated that I thought about buying a new device
Only 10 hours after knowing the solution of MsmDownloadTool There was a whole day after the device died
Thank you, thank you for everything you do to serve others
""All user from XDA ULTRAJC & OhioYJ""
The device has returned to work

Oneplus 8T HARD BRICKED ! HELP !!!

Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.
alp47470 said:
Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.
Click to expand...
Click to collapse
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk
LR7875 said:
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk
Click to expand...
Click to collapse
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
does the computer even detect your device? what name of the device does it show up
alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation
LinhBT said:
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation
Click to expand...
Click to collapse
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.
just a long shot, as i am on a 5t not the 8, but has windoze perhaps updated and "fixed" the usb driver on your behalf?
my 5t was invisible after unlocking, until i forced windoze to update the driver to an unsigned (working) version
[EOL][11.0][OFFICIAL] LineageOS 18.1 for Oneplus 5 & 5T
Is there anybody out there!🤭
forum.xda-developers.com
alp47470 said:
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.
Click to expand...
Click to collapse
That's a total different device state, it's on Diag mode, not EDL mode. Try to turn off the device COMPLETELY, then either using hardkeys ( VOL + VOL - press and hold at the same time, plug in cable ) or use Deep-Fash cable to put the device into correct EDL 9008 mode.
So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.
alp47470 said:
So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.
Click to expand...
Click to collapse
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.
BillGoss said:
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.
Click to expand...
Click to collapse
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot
Thanks for sharing that - much appreciated.
alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel.
Click to expand...
Click to collapse
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate
LinhBT said:
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate
Click to expand...
Click to collapse
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly identical also have same EDL points on motherboard. Same positioning too.
alp47470 said:
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly idenical also have same EDL points on motherboard. Same positioning too.
Click to expand...
Click to collapse
Ah I see, same here when I 1st try the Testpoint trick few years back, scary as hell cuz that was the only phone I had at that time ))))
Btw, yes, 9R and 8T shares almost everything besides of SOC's name ( Snap870 in fact is Snap865 OCing ). That's why I told u to use the MSM Tool of 9R port ROM for 8T, it passes almost every errors u may face when using MSM of 8T itself!
alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot
Click to expand...
Click to collapse
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!
NZX-DeSiGN said:
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!
Click to expand...
Click to collapse
Here.. hope it helps

Bricked My phone, cant get into FastbootD to fix it

So i recently wanted to root my OOS 12 oneplus nord, and i bricked it..
i cant get into fastbootD, Recovery, or anything at all except fastboot, the device is detected as Android bootloader interface in device manager, i have tried using: msm tool, flashing normal rom (error: partition not found and Flashing is not allowed for critical partition)
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Azeld said:
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Click to expand...
Click to collapse
As I said, msm didn’t work for me
Hafted said:
As I said, msm didn’t work for me
Click to expand...
Click to collapse
may be need to reinstall drivers? should be displayed differently in the device manager than Android bootloader interface.
gorro8 said:
may be need to reinstall drivers?
Click to expand...
Click to collapse
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Hafted said:
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Click to expand...
Click to collapse
what do you do to enter the edl mode?
what cable are you using?
gorro8 said:
what do you do to enter the edl mode?
what cable are you using?
Click to expand...
Click to collapse
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
download the correct drivers and replace them in the device manager
gorro8 said:
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I’ll try that and give you an update, Ty!
worth trying another USB port too, even if they are supposed to be the exact same. Same thing happened with my laptop, tried another (presumably identical) USB port and it works first time, every time
Hafted said:
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
Click to expand...
Click to collapse
1st, u really should find the exact drivers. But also very important to remember booting your PC into Test Mode with Driver Signature Enforcement OFF - BEFORE installing the EDL 9008 Drivers for your device.
Besides, after you press and hold both Vol buttons, u should plug the device in IMMEDIATELY, not waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Hey, so after some time (I got a new phone by now) I managed to fix it, turns out that i had to instantly put in the cable, just like how LinhBT Said
LinhBT said:
waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Click to expand...
Click to collapse
Here is something that might work for unbricking and/or getting in to EDL-mode:
Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.
Hello, friends. So I am here following this exact tutorial : https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ I currently am stuck there @pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$...
forum.xda-developers.com

Question [HELP!] Needing to flash OP9 back to stock, but I have some issues...

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!

Categories

Resources