How To Guide [FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA

[ehieie23]

there is triangle o

Fastboot or adb?

I had a bricked phone and followed the guide linked above, that's all I got

So u have installed Qualcomm drivers and launched MSM?

What about bootloader is it unlocked?

there is triangle on my qualcom wd device in device manager so i run driver booster and then it install a driver then triangle is gone the problem is i cant able to shut down my phone it is continue looping without showing screen i am able to detect it cause pc making sound plug and unplug..if my phone is rebooting how can i able to go in edl cause to go in edl phone have to be turned off. also thing happen cause i am flashing this fastboot stock rom got to the part where it is saying waiting for device after halfish progress and then my device bricked.also bootloader is unlocked.

 

[tiraminaz]

there is triangle o

there is triangle on my qualcom wd device in device manager so i run driver booster and then it install a driver then triangle is gone the problem is i cant able to shut down my phone it is continue looping without showing screen i am able to detect it cause pc making sound plug and unplug..if my phone is rebooting how can i able to go in edl cause to go in edl phone have to be turned off. also thing happen cause i am flashing this fastboot stock rom got to the part where it is saying waiting for device after halfish progress and then my device bricked.also bootloader is unlocked.

Try power and vol up for at least 15 sec, maybe it will vibrate

After phone is turn off use power + vol down then u should be in fastboot mode and should be able to connect via adb tools

 

[ehieie23]

Try power and vol up for at least 15 sec, maybe it will vibrate

After phone is turn off use power + vol down then u should be in fastboot mode and should be able to connect via adb tools

pressed it for 60 sec no vibrations tried different button combo also. should i try anything else or send it to repair center.

 

[tiraminaz]

pressed it for 60 sec no vibrations tried different button combo also. should i try anything else or send it to repair center.

Fully charged think u have to play around or send it in, i would charge it over night to be sure battery is full

Try power it off with guides from different android sites

Boot it into fastboot mode

And get drivers and all that ready

If it is your first bricked then the panic is there just been there a month ago

Pretty sure O+ can help but if it will cost you i do not know

 

[ehieie23]

Fully charged think u have to play around or send it in, i would charge it over night to be sure battery is full

Try power it off with guides from different android sites

Boot it into fastboot mode

And get drivers and all that ready

If it is your first bricked then the panic is there just been there a month ago

Pretty sure O+ can help but if it will cost you i do not know

what if i wait till my oneplus battery dies so that than i can use edl mode

 

[EtherealRemnant]

had to flash india pro fw with msm tool then unlock bootloader flash twrp then flash global with twrp then flash with global non pro fw with different msm tool package.

Can you tell me how you did this? Even after flashing global 11.2.10.10 downloaded direct from OnePlus with TWRP, my device is still recognized as an Indian 9 Pro by the global MSM so it won't flash. I absolutely cannot get this thing back to stock. I can get global 9 firmware on it but I want it to go back to being recognized as a global 9.

 

[go17lyonjon]

Can you tell me how you did this? Even after flashing global 11.2.10.10 downloaded direct from OnePlus with TWRP, my device is still recognized as an Indian 9 Pro by the global MSM so it won't flash. I absolutely cannot get this thing back to stock. I can get global 9 firmware on it but I want it to go back to being recognized as a global 9.

sorry man. I don't really know how to be helpful here. I was extremely greatful to even be able to fix my stuff after I EDL hard bricked after I flashed what was provided In this thread. Samsung is better about this kind of stuff, really disappointed in OnePlus because Odin seems far better than the msm tool :/ maybe try finding a flashable zip rom for global idk if you can flash the roms meant for msm tool using twrp. I'm not sure but I think home_csc is the partition you need to change in order for it to be recognized as global variant. I don't even have twrp anymore because I'm on Android 12 after taking an OTA. And my recovery is in chinese lol. Also I don't have a working PC right now, so I can't tell you what files I flashed by checking my PC for firmware files

 

[EtherealRemnant]

sorry man. I don't really know how to be helpful here. I was extremely greatful to even be able to fix my stuff after I EDL hard bricked after I flashed what was provided In this thread. Samsung is better about this kind of stuff, really disappointed in OnePlus because Odin seems far better than the msm tool :/ maybe try finding a flashable zip rom for global idk if you can flash the roms meant for msm tool using twrp. I'm not sure but I think home_csc is the partition you need to change in order for it to be recognized as global variant. I don't even have twrp anymore because I'm on Android 12 after taking an OTA. And my recovery is in chinese lol. Also I don't have a working PC right now, so I can't tell you what files I flashed by checking my PC for firmware files

Thanks for taking the time to respond to me, it's been a long day...

I can't believe there is no way for me to fix this. I tried the T-Mobile OP9 conversion MSM thinking that it would ignore the device type and nope, recognizes it as IN and refuses to continue.

I used the T-Mo to global fastboot conversion tool to make myself my own fastboot flasher that works and flashes 11.2.10.10 so I guess it's not the end of the world because it takes about as long to use the Indian MSM and then use the fastboot script as it did when I was using the global MSM and then updating to 11.2.10.10 anyway but man, I would really like to be able to get rid of my device thinking it's an Indian unit...

This is my first OnePlus and likely my last. I wish that there was more development on the Pixel side of things though. Samsung devices = locked bootloader and I really hate Samsung's software. The OnePlus seemed perfect and it was great until today when I saw just how wrong things can go, even when you do everything the way you're told to. All I did was flash the lineage recovery. When that failed to boot, bye bye OS and then I tried this script and I ended up in EDL mode with a device that wasn't recognized... Never in my coming up on 13 years of messing with Android phones have I had anything so ridiculous happen.

 

[go17lyonjon]

Thanks for taking the time to respond to me, it's been a long day...

I can't believe there is no way for me to fix this. I tried the T-Mobile OP9 conversion MSM thinking that it would ignore the device type and nope, recognizes it as IN and refuses to continue.

I used the T-Mo to global fastboot conversion tool to make myself my own fastboot flasher that works and flashes 11.2.10.10 so I guess it's not the end of the world because it takes about as long to use the Indian MSM and then use the fastboot script as it did when I was using the global MSM and then updating to 11.2.10.10 anyway but man, I would really like to be able to get rid of my device thinking it's an Indian unit...

This is my first OnePlus and likely my last. I wish that there was more development on the Pixel side of things though. Samsung devices = locked bootloader and I really hate Samsung's software. The OnePlus seemed perfect and it was great until today when I saw just how wrong things can go, even when you do everything the way you're told to. All I did was flash the lineage recovery. When that failed to boot, bye bye OS and then I tried this script and I ended up in EDL mode with a device that wasn't recognized... Never in my coming up on 13 years of messing with Android phones have I had anything so ridiculous happen.

I had an exynos(in usa, I got lucky) galaxy S7 before my OnePlus 9 so bootloader wasn't a problem. I kind of regretted not getting a pixel 6 but $450 for a new OnePlus 9 seemed like a steal.
I thought I remembered reading somewhere that OnePlus support may remote into your pc to help with firmware issues but I don't really know for sure. If you were able to use the T-Mobile conversation maybe try flashing using the T-Mobile version of msm tool then flashing global but could make things worst idk lol. Gl.... Hope you get you figure it out cause this **** is definitely stressful. I am satisfied with my phone now though, as long as I don't do some dumb **** with modding it and bricking again lol. All I need from root is systemless hosts adaway and vanced YouTube

 

[EtherealRemnant]

I had an exynos(in usa, I got lucky) galaxy S7 before my OnePlus 9 so bootloader wasn't a problem. I kind of regretted not getting a pixel 6 but $450 for a new OnePlus 9 seemed like a steal.
I thought I remembered reading somewhere that OnePlus support may remote into your pc to help with firmware issues but I don't really know for sure. If you were able to use the T-Mobile conversation maybe try flashing using the T-Mobile version of msm tool then flashing global but could make things worst idk lol. Gl.... Hope you get you figure it out cause this **** is definitely stressful. I am satisfied with my phone now though, as long as I don't do some dumb **** with modding it and bricking again lol. All I need from root is systemless hosts adaway and vanced YouTube

The T-Mobile conversion is really just a fastboot script that flashes all the partitions in the proper way, something this script failed to do. I took out all the files it came with and replaced them with the files from 11.2.10.10.

What is really bothering me is that I can't seem to get OOS 12 to work. The touch screen doesn't work and it's thinking I have dual SIM so despite the fact I'm flashing the correct file for my LE2115, it's still acting like it's an Indian variant. Now I guess I don't have a choice but to run a custom ROM if I want to be able to use Android 12 and that has me really pissed off. I guess I'll grab the OTA for OOS 12 and see if this fastboot script will work... Fingers crossed. Ugh. If I can get it to OOS 12 and root it so I can disable the CPU throttle, I'll be fine until I can replace this piece of garbage in the fall with a Pixel 7.

 

[go17lyonjon]

The T-Mobile conversion is really just a fastboot script that flashes all the partitions in the proper way, something this script failed to do. I took out all the files it came with and replaced them with the files from 11.2.10.10.

What is really bothering me is that I can't seem to get OOS 12 to work. The touch screen doesn't work and it's thinking I have dual SIM so despite the fact I'm flashing the correct file for my LE2115, it's still acting like it's an Indian variant. Now I guess I don't have a choice but to run a custom ROM if I want to be able to use Android 12 and that has me really pissed off. I guess I'll grab the OTA for OOS 12 and see if this fastboot script will work... Fingers crossed. Ugh. If I can get it to OOS 12 and root it so I can disable the CPU throttle, I'll be fine until I can replace this piece of garbage in the fall with a Pixel 7.

Really sorry if me saying I flashed the India pro firmware screwed you over, it was the only way I could get out of EDL mode. All I can really think is try to find global version flashable zip somewhere on here. I would avoid Android 12 till you get your stuff fixed idk if you can downgrade or not. I don't think twrp is updated for oos12 but I haven't checked in a long time

 

[EtherealRemnant]

Really sorry if me saying I flashed the India pro firmware screwed you over, it was the only way I could get out of EDL mode. All I can really think is try to find global version flashable zip somewhere on here. I would avoid Android 12 till you get your stuff fixed idk if you can downgrade or not. I don't think twrp is updated for oos12 but I haven't checked in a long time

Yeah there was no way that my device was going to flash with anything else either. For some reason the 9 Pro MSM doesn't run the same checks that the other MSMs do to verify it's flashing the correct device. If it wasn't for the 9 Pro MSM I would have had a total brick.

Also, my idea to flash OOS 12 indeed won't work. There are a bunch of extra images I don't know what to do with in this one... I guess I'm just going to have to go back to a custom ROM.

 

[go17lyonjon]

Yeah there was no way that my device was going to flash with anything else either. For some reason the 9 Pro MSM doesn't run the same checks that the other MSMs do to verify it's flashing the correct device. If it wasn't for the 9 Pro MSM I would have had a total brick.

Also, my idea to flash OOS 12 indeed won't work. There are a bunch of extra images I don't know what to do with in this one... I guess I'm just going to have to go back to a custom ROM.

Try flashing one of these in TWRP https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/ and see if it boots up with working touchscreen and see if it's recognized as global or as eu version ect i think after I did that I could flash using msmtool. That's how I got rid of the black dot at the top of my screen due to pro firmware

 

[EtherealRemnant]

Try flashing one of these in TWRP https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/ and see if it boots up with working touchscreen and see if it's recognized as global or as eu version ect

yeah that's what I did the first time after the Indian MSM but I used the 11.2.10.10 instead of c48 and when I used the OTA updater to go to c48, it booted up with no touch screen and messed up networking.

This last time I used Oxygen Updater to choose the OnePlus 9 c48 full OTA and used the local upgrade function and it did the same thing.

I think my device is hosed as far as stock ROMs go until I can get it back to proper global.

 

[go17lyonjon]

yeah that's what I did the first time after the Indian MSM but I used the 11.2.10.10 instead of c48 and when I used the OTA updater to go to c48, it booted up with no touch screen and messed up networking.

This last time I used Oxygen Updater to choose the OnePlus 9 c48 full OTA and used the local upgrade function and it did the same thing.

I think my device is hosed as far as stock ROMs go until I can get it back to proper global.

Such a dumb problem that doesn't make logical sense.... :/ GL. I'm happy with my OnePlus 9 for now. $450 I can't complain. flagship CPU, solid amount of ram and storage, for half the cost of a flagship. I can get a phone I own and 2+ years of service for what some people spend on an iphone every year. Bootloader locked galaxy S3 -> htc one m9 -> exynos galaxy S7 -> OnePlus 9
It's so nice this thing goes from 0 to full in like 30 mins

 

[EtherealRemnant]

Such a dumb problem that doesn't make logical sense.... :/ GL. I'm happy with my OnePlus 9 for now. $450 I can't complain. flagship CPU, solid amount of ram and storage, for half the cost of a flagship. I can get a phone I own and 2+ years of service for what some people spend on an iphone every year. Bootloader locked galaxy S3 -> htc one m9 -> exynos galaxy S7 -> OnePlus 9
It's so nice this thing goes from 0 to full in like 30 mins

Yeah I *was* happy with it....... I'm currently flashing MSM again because a custom ROM wouldn't take either. Flashed recovery, installed ROM, dropped me right back to the bootloader. When trying my script to get a bootable OS again, it complained that all the partitions were gone! I'm getting it back to 11.2.10.10 and I'm done for the day, been at this for hours upon hours now and I'm totally flummoxed how everything seems to go totally wrong in close to the worst possible way.

 

[AtreyC]

@EtherealRemnant, Hey men, we are on same boat, I've make a new thread for our problem.

here

 

[cbrown666]

Thank you for sharing this.But It brick my device.After double click "fastboot flash slot all_b",phone goes into edl mode.Using msmdownload tool for lemonade shows sahara connection error.After using msmdownload tool for lemonadep then using msmdownload tool for lemonade phone survives.My model is oneplus 9 in china model,which is LE2110.

 

[liver20]

My op9 le2110 hard bricked not image, not vibrate... MSM tool With global and india give me Sahara error...
Any?

 

[Vmo x]

My op9 le2110 hard bricked not image, not vibrate... MSM tool With global and india give me Sahara error...
Any?

The latest global MSM tool will work try entering EDL mode by pressing down volume up and down while connecting the USB cable. Not sure if holding power button is necessary but if you have the right drivers installed you'll be able to flash successfully, the PC drivers is what causes errors if you haven't updated. I think in OP there is a link to Universal drivers but I recommend looking for a source of drivers only for the oneplus 9, HS-USB QDLoader 9008 is the Correct driver you need to install for PC to recognize phone properly in EDL mode. When you run MSM tool be very patient with allowing it to load and start u properly before flashing. Make sure you select target if you mess up just keep trying you'll get it eventually.