Database Info

[RECOVERY][3.2.3-0][fujisan]Unofficial TWRP recovery for Axon M

First, let me apologize for the rough guide I'm going to deliver I'll clean this up in due time.
1.) Let's get some files downloaded. So here is a guide by @deadman96385 that details Qfil and the actual process of flashing.
2.) Let's incorporate that into my guide
* You'll choose the programmer from my TWRP folder
* You'll choose the rawprogram0.xml from my TWRP folder
3.) Time to flash....just press Download there's nothing else to do.
4.) Boot into recovery...do I need to explain how?
* Warning* Do not flash Magisk requires a separate boot.img I haven't made it just yet.

So with all this, what is the next step in the process for custom rom installs? Waiting on mine in the mail so I can begin looking into everything as well, sadly I picked the att variant so it looks like things will be more difficult for me.

good work @Unjustified Dev And @deadman96385

ff7cloudsnobody said:
So with all this, what is the next step in the process for custom rom installs? Waiting on mine in the mail so I can begin looking into everything as well, sadly I picked the att variant so it looks like things will be more difficult for me.
Click to expand...
Click to collapse
Roms won't be ready any time soon this was just a preliminary step. And what do you mean by more difficult? I have the att version.

Unjustified Dev said:
Roms won't be ready any time soon this was just a preliminary step. And what do you mean by more difficult? I have the att version.
Click to expand...
Click to collapse
From what I've been reading up on, it had looked like the AT&T variant was more difficult to get through than the others. I could be wrong though. But thanks for this breakthrough!

ff7cloudsnobody said:
From what I've been reading up on, it had looked like the AT&T variant was more difficult to get through than the others. I could be wrong though. But thanks for this breakthrough!
Click to expand...
Click to collapse
I don't know about the other variants. Each firmware is signed so I can't test their Roms, but I used their updated 8.1 proprietary files to build Lineage.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my G8142 using Tapatalk

Unjustified Dev said:
I don't know about the other variants. Each firmware is signed so I can't test their Roms, but I used their updated 8.1 proprietary files to build Lineage.
Click to expand...
Click to collapse
Does going the old "data wipe then flash boot img without encryption" not work anymore? If so then my bad, been a while since I've worked with a phone that is locked down with signed firmware. Was looking into doing that right now.
Edit: And I don't mean via flashboot because first boot should cause it to resign

AT&T
Unjustified Dev said:
Roms won't be ready any time soon this was just a preliminary step. And what do you mean by more difficult? I have the att version.
Click to expand...
Click to collapse
Hello!
Thank you for the first ray of light Please, can you answer some questions?
1) As far as I know, AT&T version of Z999 has locked bootloader. Have you tried this TWRP with AT&T Z999 (not T-mob, China or Russian)?
2) As far as I know, AT&T version of Z999 has non-standard EDL mode and until now there was only one tool capable of flashing it, "Uni-Android Tool" for $49. The usual QFIL doesn't see 9008 COM-port on this phone. So, how does your TWRP gets flashed? Or is the included "firehose" an already patched one for AT&T Z999?
3) If all of these works, can root be (some day) obtained with locked bootloader?
I live in a country with GSM 900\1800, UMTS 2100 & LTE B3 & B20, so right now my Z999 is useless as a mobile device & works only as a small tablet. The root is totally necessary for me to unlock additional bands & I have faith in You
Thanks once again,
WBR - Draco.

Drakosha said:
Hello!
Thank you for the first ray of light Please, can you answer some questions?
1) As far as I know, AT&T version of Z999 has locked bootloader. Have you tried this TWRP with AT&T Z999 (not T-mob, China or Russian)?
2) As far as I know, AT&T version of Z999 has non-standard EDL mode and until now there was only one tool capable of flashing it, "Uni-Android Tool" for $49. The usual QFIL doesn't see 9008 COM-port on this phone. So, how does your TWRP gets flashed? Or is the included "firehose" an already patched one for AT&T Z999?
3) If all of these works, can root be (some day) obtained with locked bootloader?
I live in a country with GSM 900\1800, UMTS 2100 & LTE B3 & B20, so right now my Z999 is useless as a mobile device & works only as a small tablet. The root is totally necessary for me to unlock additional bands & I have faith in You
Thanks once again,
WBR - Draco.
Click to expand...
Click to collapse
1.) I have the att variant
2.) The all have edl mode I sniffed the firehose from uniandroid and had a friend reconstruct it to get it working. And the usual qfil does see the phone. You're more than likely in dfu mode and not edl. Uniandroid can send the phone from dfu to edl. You can adb reboot to edl to get in 9008. The issue was the programmer was incorrect.
3.) Root can probably be obtained I just had no interest. I'll look into it later if I have time. Also I'm not sure if you can unlock more bands never looked into that before.
Sent from my G8142 using Tapatalk

Great!
Unjustified Dev said:
1.) I have the att variant
2.) The all have edl mode I sniffed the firehose from uniandroid and had a friend reconstruct it to get it working. And the usual qfil does see the phone. You're more than likely in dfu mode and not edl. Uniandroid can send the phone from dfu to edl. You can adb reboot to edl to get in 9008. The issue was the programmer was incorrect.
3.) Root can probably be obtained I just had no interest. I'll look into it later if I have time. Also I'm not sure if you can unlock more bands never looked into that before.
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
Thanks for the answers! Wonderful news, the ability to flash AT&T phone with QFill changes everything. As for the bands, I've seen a lot of articles on how to unlock Qualcomm phones with NV editor, and had success with several Nexus-es & LG's. Let's hope that after (if...) root is obtained, one of the methods works. It will literally breath the new life into this phone & will make it useful everywhere in the world.
WBR, Draco.

Just an FYI, only running this didn't work for me, I changed the img to recovery.img and used the firehose with the stock files, I edited the boot though to remove secure boot.

Root
Unjustified Dev said:
* Warning* Do not flash Magisk requires a separate boot.img I haven't made it just yet.
Click to expand...
Click to collapse
Hello!
Any news on root or, perhaps, some ROM like Lineage?
WBR, Draco.

Any News?
So I tried flashing my bricked Axon M with the provided firehose file, and using provided B37 firmware, but I keep getting an error associated with "userdata.img is 0 bytes!" and if I delete the file, I then get an error stating "userdata.img could not be found!" any ideas?

ehsan96696 said:
So I tried flashing my bricked Axon M with the provided firehose file, and using provided B37 firmware, but I keep getting an error associated with "userdata.img is 0 bytes!" and if I delete the file, I then get an error stating "userdata.img could not be found!" any ideas?
Click to expand...
Click to collapse
Edit rawprogram0.xml where it says userdata.img edit it to be "" basically telling qfil don't flash it. Alternatively use miflash
Sent from my G8142 using Tapatalk

Unjustified Dev said:
Edit rawprogram0.xml where it says userdata.img edit it to be "" basically telling qfil don't flash it. Alternatively use miflash
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
Thanks, I did get past that error, but now it is stuck at https://imgur.com/YzyzPNP

ehsan96696 said:
Thanks, I did get past that error, but now it is stuck at
Click to expand...
Click to collapse
Use miflash
Sent from my G8142 using Tapatalk

Unjustified Dev said:
Use miflash
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
How? Whenever I pick the folder with the firmware it just sais "couldn't find flash script"

rawprogram0.xml
ehsan96696 said:
How? Whenever I pick the folder with the firmware it just sais "couldn't find flash script"
Click to expand...
Click to collapse
Here, just use the attached rawprogram0.xml (AT&T B37) with QFil

Drakosha said:
Here, just use the attached rawprogram0.xml (AT&T B37) with QFil
Click to expand...
Click to collapse
Tried as specified and it gets stuck here: https://imgur.com/xMynQ3h

ehsan96696 said:
Tried as specified and it gets stuck here: https://imgur.com/xMynQ3h
Click to expand...
Click to collapse
Do you have spaces in your username? Put firehose programmer file inside the firmware folder, and put the whole folder in C:\Z999 (without any spaces or long filenames). Run Qfil as admin. And never flash phones from DESKTOP...

Question SM-A326U Combination Firmware

US Combination Firmware link for Galaxy A32 5G
Supposedly you can FRP bypass or OEM unlock based on what I've heard
Google Drive - Virus scan warning
drive.google.com

TypicalGellert said:
US Combination Firmware link for Galaxy A32 5G
Supposedly you can FRP bypass or OEM unlock based on what I've heard
Google Drive - Virus scan warning
drive.google.com
Click to expand...
Click to collapse
Have you tested this approach? If yes, then can you provide instruction.
TIA

furballi said:
Have you tested this approach? If yes, then can you provide instruction.
TIA
Click to expand...
Click to collapse
I tried last night but it wouldn't flash Odin kept failing it, so I'm going to try to find a different combo Firmware and re-up with the new link to it once I know the new one works.... In the meantime y'all could try that to see if you get a different result with flashing it

TypicalGellert said:
I tried last night but it wouldn't flash Odin kept failing it, so I'm going to try to find a different combo Firmware and re-up with the new link to it once I know the new one works.... In the meantime y'all could try that to see if you get a different result with flashing it
Click to expand...
Click to collapse
I am also going to try using Frija to download the TMK version which is apparently another US unlocked variant Firmware to see if that might flash and go from there

TypicalGellert said:
I am also going to try using Frija to download the TMK version which is apparently another US unlocked variant Firmware to see if that might flash and go from there
Click to expand...
Click to collapse
Thanks. Will post if I find a solution.
T Mo and Samsung are not playing nice. I was able to completely remove the T Mo app with the Samsung A21, but no luck with the A32 5G (using ADB). Also removed over 200 junk apps from the A32 5G. My goal was to get it as bare-bone as the A21. Yet the A32 still pull about 1.3 GB of RAM vs. 930 MB for the A21, with the major difference being Android 11 vs. Android 10. Apparently, the claim about better memory management in Android 11 does not pan out in actual use. The Android 6 in my ZTE V8 Pro is lightning fast compared to Android 11.
Most people are not aware of the tremendous amount of spyware that are hidden on these Samsung phones (Amazon, Microsoft, etc). The OS is free, but informed users should have the option to easily remove these junk apps with a few keystrokes.

TypicalGellert said:
I tried last night but it wouldn't flash Odin kept failing it, so I'm going to try to find a different combo Firmware and re-up with the new link to it once I know the new one works.... In the meantime y'all could try that to see if you get a different result with flashing it
Click to expand...
Click to collapse
I'm new to this device and still figuring things out. Meanwhile, came across this post that gives different versions of Odin to try with. https://www.droidwin.com/create-samsung-combination-firmware-flash-it-via-odin/

TypicalGellert said:
I tried last night but it wouldn't flash Odin kept failing it, so I'm going to try to find a different combo Firmware and re-up with the new link to it once I know the new one works.... In the meantime y'all could try that to see if you get a different result with flashing it
Click to expand...
Click to collapse
You have to use a patched version of Odin.

TypicalGellert said:
I am also going to try using Frija to download the TMK version which is apparently another US unlocked variant Firmware to see if that might flash and go from there
Click to expand...
Click to collapse
TMK is T-Mobile not unlocked varient.

Crossflashing to unlocked/bloat-free firmware works just fine.

gamer765 said:
Crossflashing to unlocked/bloat-free firmware works just fine.
Click to expand...
Click to collapse
More info please? Were you able to flash a different firmware on a Tmobile device and unlock bootloader with it?
If yes, can you confirm that the phone works fine and give the rest of us step by step instructions?

gamer765 said:
Crossflashing to unlocked/bloat-free firmware works just fine.
Click to expand...
Click to collapse
Did you crossflash to A326U1 XAA firmware?
how did you managed to do that without unlock bootloader

financeledger said:
Did you crossflash to A326U1 XAA firmware?
how did you managed to do that without unlock bootloader
Click to expand...
Click to collapse
ODIN, You never have to be bootloader unlocked for that on Samsung Devices.

hyelton said:
ODIN, You never have to be bootloader unlocked for that on Samsung Devices.
Click to expand...
Click to collapse
then i am missing something i am trying with Odin to flash the A326u1 XAA and get only fail.
pressing Volumey kesyw while inserting usb i never get into DL mode for flashing

Don't PM me please.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

gamer765 said:
Don't PM me please.
Click to expand...
Click to collapse
Wont get pms if you share info
Did you use combination from this thread?

Did nothing special, same procedure as with all other Samsung phones. Flash U1 firmware on top of U firmware. Don't see what's so difficult about it. @hyelton also mentioned how he did it as well.

gamer765 said:
Did nothing special, same procedure as with all other Samsung phones. Flash U1 firmware on top of U firmware. Don't see what's so difficult about it. @hyelton also mentioned how he did it as well.
Click to expand...
Click to collapse
newb here just wanted to make sure it was same steps thanks for that

(OS11/Sprint/SPR)
(OS11/MetroPCS/TMK)
(OS11/US Cellular/USC)
(OS11/T-Mobile/TMB)

Using Odin Patched 3B v3.14.1 and I’m receiving a truncate message stating the following:
sw rev check fail [vbmeta[fused 2 > bi
I’m using the SM-A326U1 for Product Code TMB from April 19, 2021. The phone now boots up with a blue screen ”An error has occurred while updating the device software”. Any suggestions?
CSC seems to fail at boot.img per Odin
CSC_HOME fails at preloader.img
——— Update ——-
Flashed latest TMK using Patched Odin 3.14.1 and the device is functional again.

tavella said:
Using Odin Patched 3B v3.14.1 and I’m receiving a truncate message stating the following:
sw rev check fail [vbmeta[fused 2 > bi
I’m using the SM-A326U1 for Product Code TMB from April 19, 2021. The phone now boots up with a blue screen ”An error has occurred while updating the device software”. Any suggestions?
CSC seems to fail at boot.img per Odin
CSC_HOME fails at preloader.img
Click to expand...
Click to collapse
bricked im on the same roadif you find way out let me know
edit : just debricked real easy using odin 3b patch last version and A326USQU2AUD9_A326UOYN2AUD9_TMB

How To Guide 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 Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!

Enjoy it I struggled for a week. The result is ridiculous but successful

_MartyMan_ said:
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 Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!
Click to expand...
Click to collapse
Yes !! thanks @flameteam. My Oneplus 9 EU was really super hard bricked (turned to the "dark side") with no display whatsoever. I went for the EU package and the phone came back to life !!
This was the only way as some other download tool dedicated for the Oneplus 9 didn't work. Gave me "Sahara error. (with Windows 7, 10, different USB cables etc)
And , yes as strange as it sounds my Oneplus 9 now runs the OP9 Pro firmware ?!?!.
But this gave me the chance to install the stock OTA for Oneplus 9. It seems to work.
The question is if a full stock OTA OP9 actually cleaned out any trace of the previous Pro version ?

Big Update. my phone is coming back and free again )i think) No warranty, just wild QoL issues with the 9, it seems.
Im still very happy to get it back .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yo i love you bro.....seriously you are the fkkkng mannnn omg

josc002 said:
Yes !! thanks @flameteam. My Oneplus 9 EU was really super hard bricked (turned to the "dark side") with no display whatsoever. I went for the EU package and the phone came back to life !!
This was the only way as some other download tool dedicated for the Oneplus 9 didn't work. Gave me "Sahara error. (with Windows 7, 10, different USB cables etc)
And , yes as strange as it sounds my Oneplus 9 now runs the OP9 Pro firmware ?!?!.
But this gave me the chance to install the stock OTA for Oneplus 9. It seems to work.
The question is if a full stock OTA OP9 actually cleaned out any trace of the previous Pro version ?
Click to expand...
Click to collapse
yes cleaning msm tool

The Indian version of MSM was able to restore my phone, but now I cant install any OTAs without bricking it. How did you get it back to a Global rom after the MSM retore?

I was finally able to unbrick by using this method after days of troubleshooting, but now how in the hell do I get the OnePlus 9 firmware back onto it? I've downloaded different (full zip) ota's, moved to root storage, and when I go to system settings --> local upgrade, the updates do not show up there. I tried flashing via TWRP and I believe it booted to inactive slot (where update was applied) and bootlooped. Eventually it booted back into slot A with OP9Pro firmware. I thought maybe I could use global msm tool for OP9 but the thread that says "UPDATED" downloads and then fails to open. So far only msm tool I have gotten to work for my phone was for the Indian OP9Pro variant.

_MartyMan_ said:
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 Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!
Click to expand...
Click to collapse
you still bricked foooo??? adb reboot edl launch msm tool in thank me lataaaa

Hallelujah!!!! IT WORKED!!!!!!!!! I've been bricked for a month!!

The question now is how do i get back to global? Any ideas?

Anyone???

YES

Got back to global. Took me a day to figure it out. Enable OEM Unlock and USB debugging. I flashed temp TWRP, installed the OS Zip file from OnePlus support site. Rebooted into recovery, formatted and wiped system. Booted into global. This installation is in SLOT B. Slot A will still have horrible Indian Rom (only horrible because it shouldn't be installed on my Global Unlocked Phone, no disrespect to my Indian brothers.) Note when logging in for the first time let global do its OTA update before you do anything else, especially before you reboot. The Indian version is installed in slot A. REBOOT after OTA installed. Don't reboot before OTA does its thing. This will ensure Slot A has a clean installation. I made the mistake of rebooting before the OTA and I could not do anything with slot A. Relock the bootloader, it will wipe and you will boot into a pristine Global OS 11.2.8.8 Rom.

lrod55 said:
I was finally able to unbrick by using this method after days of troubleshooting, but now how in the hell do I get the OnePlus 9 firmware back onto it? I've downloaded different (full zip) ota's, moved to root storage, and when I go to system settings --> local upgrade, the updates do not show up there. I tried flashing via TWRP and I believe it booted to inactive slot (where update was applied) and bootlooped. Eventually it booted back into slot A with OP9Pro firmware. I thought maybe I could use global msm tool for OP9 but the thread that says "UPDATED" downloads and then fails to open. So far only msm tool I have gotten to work for my phone was for the Indian OP9Pro variant.
Click to expand...
Click to collapse
See above. I figured it out.

Ok. this worked for me... I was able to save my LE2110 from being hard bricked. THANK YOU.
Now, has anyone been able to go back to the non-Pro software?
If so, how did you do it?

zborn said:
Ok. this worked for me... I was able to save my LE2110 from being hard bricked. THANK YOU.
Now, has anyone been able to go back to the non-Pro software?
If so, how did you do it?
Click to expand...
Click to collapse
See my response above.

ctonylee1965 said:
See my response above.
Click to expand...
Click to collapse
That didn't work for me. I just MSMed back to 9 firmware

lrod55 said:
I was finally able to unbrick by using this method after days of troubleshooting, but now how in the hell do I get the OnePlus 9 firmware back onto it? I've downloaded different (full zip) ota's, moved to root storage, and when I go to system settings --> local upgrade, the updates do not show up there. I tried flashing via TWRP and I believe it booted to inactive slot (where update was applied) and bootlooped. Eventually it booted back into slot A with OP9Pro firmware. I thought maybe I could use global msm tool for OP9 but the thread that says "UPDATED" downloads and then fails to open. So far only msm tool I have gotten to work for my phone was for the Indian OP9Pro variant.
Click to expand...
Click to collapse
I hard bricked my oneplus 9 first time and was panicking. Luckily I found this thread and your answer. You guys saved me hours and days of fixing this, most important of all, I can't tell me wife that I trashed a $800 phone after bought it a couple days ago. I was able to get my phone back into EU version using the MSM tool, lost my IMEI # and sim card won't work, So I was able to switch back to global after following your instruction. Thank you.

_MartyMan_ said:
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 Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!
Click to expand...
Click to collapse
How did you do it? I am trying this method, but MSM tool gives me this error:

Question Touchscreen doesn't work after update to LE2113_11.C.47 [SOLVED]

I'm looking for a captain who could help me find solution. Like "EtherealRemnant" in his post, Im not able to get OOS 12 work on my OP9.
EtherealRemnant post:
https://forum.xda-developers.com/t/...p9-stock-oos-11-2-2-2aa.4275727/post-86854951
Like "everyone" I've something messed up with TWRP boot and ended up with MSM tool. Cause I have LE2113 I have to use India MSM for 9Pro.
Then I use downgrade package to get stock OOS on my OP9, then use oficial way to update OOS, till highest A11. But whenever I use update to LE2113_11.C.47 it ended up with frozen/not working touch screen. Not just in OS but also in TWRP and stock recovery. I´ve tried also connect USB mouse, but with no successs.
My question, is there a way how to update to OOS (A12) without get freezed touchscreen?
EDIT:
Whole problem was in usage of wrong MSM (INDIAN OP9pro, EU OP9pro). So if you want to recover yours OP9 (EU) LE2113, you have to use MSM tool from allenjthomsen (Thank you!).
More abotu this tool here

I was able to get my device back to stock software by modding the MSM Tool for global but then I gave it to someone else to try to help them and it didn't work. I have sent a PM to the person who mods these images for some help.
Have you tried using the full install zip for BA using the system updater? I didn't actually try that before I messed around with the MSM Tool. Put this in the root of your storage and go to updater and do the local upgrade.
https://otafsg-cost-az.coloros.com/OnePlus9_EEA/OnePlus9Oxygen_22.E.13_GLO_0130_2111112104/patch/amazone2/GLO/OnePlus9Oxygen/OnePlus9Oxygen_22.E.13_GLO_0130_2111112104/OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
It seems like what is happening is even after you get it back to stock software, there is a flag somewhere that's designating the device as an Indian 9 Pro. Once I got the modified global MSM Tool I made to flash my phone, the problem stopped because my phone was fully global again and I've been back on OOS 12 C.48 since Saturday evening (for better or worse, OOS 12 has a lot of issues but I don't want to risk another brick for awhile, especially since I'm not sure that the mod I made actually worked and it wasn't just some freak coincidence that let me flash back).

Thank you for your reply, the link you've send is downloading:
OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
I've presume that is for Global version, or is for EU version also?
EDIT:
Last try was:
MSM - OnePlus_9_Pro_EU_OxygenOS_11.2.2.2
Then update to:
OnePlus 9 Oxygen OS 11.2.10.10.LE25BA (EU)
- OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
Then, two options:
Oxygen updater -> C.47 ->Touchscreen death
OTA update -> OxygenOS 12.0 (C.48) (EU)
- OnePlus9Oxygen_22.E.11_OTA_0110_all_2107082125_downgrade_09b1a0a810824761.zip ->Touchscreen death
Im starting to be little bit despered, where is the problem. I've tried lost of combination but still no luck...

AtreyC said:
Thank you for your reply, the link you've send is downloading:
OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
I've presume that is for Global version, or is for EU version also?
EDIT:
Last try was:
MSM - OnePlus_9_Pro_EU_OxygenOS_11.2.2.2
Then update to:
OnePlus 9 Oxygen OS 11.2.10.10.LE25BA (EU)
- OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
Then, two options:
Oxygen updater -> C.47 ->Touchscreen death
OTA update -> OxygenOS 12.0 (C.48) (EU)
- OnePlus9Oxygen_22.E.11_OTA_0110_all_2107082125_downgrade_09b1a0a810824761.zip ->Touchscreen death
Im starting to be little bit despered, where is the problem. I've tried lost of combination but still no luck...
Click to expand...
Click to collapse
The same thing happened to me 2 days before and the conclusion was to use stock Android 11 or any custom ROM.

AtreyC said:
Thank you for your reply, the link you've send is downloading:
OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
I've presume that is for Global version, or is for EU version also?
EDIT:
Last try was:
MSM - OnePlus_9_Pro_EU_OxygenOS_11.2.2.2
Then update to:
OnePlus 9 Oxygen OS 11.2.10.10.LE25BA (EU)
- OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
Then, two options:
Oxygen updater -> C.47 ->Touchscreen death
OTA update -> OxygenOS 12.0 (C.48) (EU)
- OnePlus9Oxygen_22.E.11_OTA_0110_all_2107082125_downgrade_09b1a0a810824761.zip ->Touchscreen death
Im starting to be little bit despered, where is the problem. I've tried lost of combination but still no luck...
Click to expand...
Click to collapse
The link I sent you is the full stock EU image.

AtreyC said:
I'm looking for a captain who could help me find solution. Like "EtherealRemnant" in his post, Im not able to get OOS 12 work on my OP9.
EtherealRemnant post:
https://forum.xda-developers.com/t/...p9-stock-oos-11-2-2-2aa.4275727/post-86854951
Like "everyone" I've something messed up with TWRP boot and ended up with MSM tool. Cause I have LE2113 I have to use India MSM for 9Pro.
Then I use downgrade package to get stock OOS on my OP9, then use oficial way to update OOS, till highest A11. But whenever I use update to LE2113_11.C.47 it ended up with frozen/not working touch screen. Not just in OS but also in TWRP and stock recovery. I´ve tried also connect USB mouse, but with no successs.
My question, is there a way how to update to OOS (A12) without get freezed touchscreen?
Click to expand...
Click to collapse
Did you unlock the bootloader before you upgraded, the frozen non working touchscreen only happened when I upgraded with an unlocked bootloader. If you havent already try to MSM back to stock and then upgrade to OOS12 before you unlock the bootloader

jshinn1 said:
Did you unlock the bootloader before you upgraded, the frozen non working touchscreen only happened when I upgraded with an unlocked bootloader. If you havent already try to MSM back to stock and then upgrade to OOS12 before you unlock the bootloader
Click to expand...
Click to collapse
The broken touchscreen happened to me with a locked bootloader too. I know this because I was on 11.2.10.10 after spending hours figuring out how to get it back on full global firmware and I made the conscious decision not to mess with a custom ROM anymore after updating to 11.2.10.10 before I chose to use the OTA to upgrade to C.48 so I didn't unlock the bootloader. Then I ended up having to do the MSM again when my touchscreen didn't work.

EtherealRemnant said:
The broken touchscreen happened to me with a locked bootloader too. I know this because I was on 11.2.10.10 after spending hours figuring out how to get it back on full global firmware and I made the conscious decision not to mess with a custom ROM anymore after updating to 11.2.10.10 before I chose to use the OTA to upgrade to C.48 so I didn't unlock the bootloader. Then I ended up having to do the MSM again when my touchscreen didn't work.
Click to expand...
Click to collapse
Hmmm Im definitely no expert but if that doesn't work then hopefully somebody else can chime in with a solution.

jshinn1 said:
Hmmm Im definitely no expert but if that doesn't work then hopefully somebody else can chime in with a solution.
Click to expand...
Click to collapse
The only thing that worked for me was getting back to the stock global firmware with the MSM Tool. I modded the MSM Tool to do this since I was stuck on the India 9 Pro software and it worked for whatever reason but I had someone else try it and it didn't work for them and asking someone who knows about the MSM Tool, my fix shouldn't have worked for me either, so I took it down so as not to mislead anyone. As you can see though, OOS 12 is running fine.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

@jshinn1 When I install MSM for OP9pro on my OP9, I've unlock bootloader to install downgrade for OP9 via TWRP. Then I try to update via OTAs, downloaded from Oxygen updater, or xda sources. Result is still same, death touch after install Android 12 update.
I've also tried swaping slots (A,B) in TWRP during install, no result.
So far only MSM capable unbrick my OP9 was Indian 9Pro and EU 9Pro. But in the end same result death touch.

I was able to fix it by modifying the settings.xml in the T-Mobile msm, I haven't had anyone else try but it's worked multiple times on my own. I can provide the link if anyone is interested. It's for the OP9 T-Mobile but I can easily change it to global if needed.

Sound promising, can you change it not to Global, but to EU (2113)?

Okay I will try it on my device and if all looks good report back with a download link.

XxBigBuckxX said:
I was able to fix it by modifying the settings.xml in the T-Mobile msm, I haven't had anyone else try but it's worked multiple times on my own. I can provide the link if anyone is interested. It's for the OP9 T-Mobile but I can easily change it to global if needed.
Click to expand...
Click to collapse
Can I ask how you did this? I modified the settings.xml on the global ROM to IN and it flashed mine that was stuck as an Indian 9 Pro but then failed params when I gave it to someone else and I haven't wanted to risk being stuck on IN firmware again to troubleshoot it. In my case all I did was change the Desc from O2 to IN and that did it but I gave it to someone with a T-Mobile device also flashed with Indian 9 Pro software and it didn't work... Figured it must be a fluke that it worked for me.

Problem SOLVED, see my edit in first post. Thank you all for participation.

AtreyC said:
Problem SOLVED, see my edit in first post. Thank you all for participation.
Click to expand...
Click to collapse
Glad you figured it out

How To Guide [Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)

This method is outdated. You must use this method or you will run into problems.
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
**I forgot that OnePlus screwed up the wiping script on 11.2.10.10 so after discovering I couldn't root my device, I have attached 11.2.4.4 that is modded to flash to Indian variants as well. It works on my device in the same manner described in this post. If you use 11.2.10.10, you won't be able to unlock the bootloader and have a working phone, it will kick you to recovery with an error message and you can wipe system cache and it will act like it's booting but it never will. Only flash 11.2.10.10 if you are planning to stay with a locked bootloader or if you're going to OOS 12.**
I found this updated MSM Tool and figured that people would appreciate it.
Source of updated MSM Tool: https://yun.daxiaamu.com/OnePlus_Roms/一加9/9008线刷救砖包氧OS 11.2.10.10/
As an added bonus, I added multi-target support. If you have flashed your global OnePlus 9 with Indian firmware, this package may help you get back to global software. I have tested it by intentionally flashing my global 9 to India 9 Pro firmware again and I can confirm that it does work. Choose India in the Target dropdown box.
As for the settings for flashing Indian firmware back to global, I was getting the dreaded "device not match image" until I left sha256 checked and use lite firehose *unchecked*. I know this flies in the face of normal convention and I'm sure this will lead to some people having Sahara errors and I unfortunately don't know how to fix that. I would assume that when you have a device that's actually booting that you shouldn't need the lite firehose anyway. It wouldn't surprise me if some people find that they need a different combo. In order to get the OP9P firmware (which I also modified with multi-target to force it to flash to global because it wouldn't do it without the mod) to flash my global unit so I could test this, I had to uncheck Sha256 check and I left use lite firehose checked, so try playing with different combos instead of just declaring it doesn't work and please report which combos worked for your device so others can see.
It's honestly a real headache when you have to flash the Indian 9 Pro firmware because it breaks the ability to go to OOS12 unless you can flash back with the global MSM and clear whatever flag is being set that makes it think it's an Indian 9 Pro so having a tool available to be able to go back to global firmware should be a great boon for those of us who have a serial flashing problem lol.
Pro tip: Start the app and click Start before you connect your phone so it's already looking for the device when it reboots. You can use adb reboot edl to go right to edl mode rather than having to use the obnoxious key combo. If the process fails, press and hold volume up and power until the phone reboots to the OS and you can try again.
Screenshot of success:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
11.2.10.10:
3.56 GB file on MEGA
mega.nz
11.2.4.4: https://mega.nz/file/ZWtGxTSb#UZ6aSOR2UTYrCao2fQNJ1IN5LSxPNBOxzel1kihnnJs
EDIT: I just tested this a second time, taking my device back to Indian 9 Pro and then using this MSM again. It flashed exactly the same way, giving me the device not match image error until I left Sha256 checked and unchecked use lite firehose.
EDIT 2: See ** message at the top.

*deleted*

Thank you! I'll try it as soon as i need to MSM again

Hey guys.
After bricking my phone and getting into a eternal looping black screen with no hopes to solve it but to send it over to repair, I tried what @EtherealRemnant told me and it did work!!
1st the Indian MSM for OP9Pro and then this patched MSM.
When I ran the MSM tool I just did exactly what the post says. Checked sha256 and unchecked "Lite Firehouse" just like in the pic below and it just worked. I used the Vol+ and Vol- key combo pressed while plugging the Original OnePlus 9 USB-C cable to get to EDL mode after flashing the OP9PRO and skipping the initial config in order to get to EDL again and flash the magical MSM .ops file provided.
Thanks again for this

Hi, i have a good story.
My Oneplus 9 LE2110 got hardbricked some weeks ago and i wasn't able to find any MSM working for my device, until i found that the 9 Pro India MSM worked and i recovered my phone. But somehow, after flashing the normal OP9 firmware (through recovery because of global/india/europe MSM not working), and updating to OOS12 by OTA, my touchscreen just wasn't working on it, just was working on OOS11 and A12 custom roms. I decided to use Nameless but i just couldn't live thinking that OOS12 (and probably next updates) would never work again on my phone.
So eventually i found your post, tried your patched MSM and... IT WORKED AT THE FIRST TRY! my phone woke up on global OOS, i updated to latest A11 and installed OOS12 through OTA and my device (and touchscreen) are working perfectly! Thank you for your work!
If anybody has a bricked LE2110 with no screen, or you can't find any MSM working on your phone, just try this one. Thanks again @EtherealRemnant

@blosk It makes me so happy to see people benefiting from this! I originally made it for myself but when people started messaging me for help, I figured it was time to share. You are the third person in the last few days that I know of who had success!

Thank you for this @EtherealRemnant It is just what I needed.

EtherealRemnant said:
@blosk It makes me so happy to see people benefiting from this! I originally made it for myself but when people started messaging me for help, I figured it was time to share. You are the third person in the last few days that I know of who had success!
Click to expand...
Click to collapse
When I try to use either msm it gives me the Param preload device does not match image error I tried all the options switch around (sha256, lite firehose)

stez827 said:
When I try to use either msm it gives me the Param preload device does not match image error I tried all the options switch around (sha256, lite firehose)
Click to expand...
Click to collapse
Are you selecting the correct option in the dropdown?
If you are flashing a global unit that is still running global software, choose O2 in the dropdown. If you are flashing a global or other unit that was flashed with Indian 9 Pro, choose India in the dropdown.
Flashing India only seems to work with Sha256 checked and lite firehose unchecked so far.
Try changing the target to global as well just in case. Also try it with no target selected.
There is not a lot of troubleshooting that can be done here but you can try flashing an India OTA to get Indian firmware on both slots and see if that works. You can also try the oldest version India downgrade package and see if that helps.
If these ideas don't work, I don't know what to tell you. You're the first who couldn't get it to work so far. I have three PMs in my box from people who used the tool and haven't posted in this thread.

EtherealRemnant said:
Are you selecting the correct option in the dropdown?
If you are flashing a global unit that is still running global software, choose O2 in the dropdown. If you are flashing a global or other unit that was flashed with Indian 9 Pro, choose India in the dropdown.
Flashing India only seems to work with Sha256 checked and lite firehose unchecked so far.
Try changing the target to global as well just in case. Also try it with no target selected.
There is not a lot of troubleshooting that can be done here but you can try flashing an India OTA to get Indian firmware on both slots and see if that works. You can also try the oldest version India downgrade package and see if that helps.
If these ideas don't work, I don't know what to tell you. You're the first who couldn't get it to work so far. I have three PMs in my box from people who used the tool and haven't posted in this thread.
Click to expand...
Click to collapse
I tried all those trouble shooting steps none of which worked my phone is a T-Mobile OnePlus 9 but I bricked it when trying to convert to global but was able to bring it back with the Indian 9 pro msm then flash global it's after that and have been running nameless for a while now but now I need to update to c.48 to stay up to date with nameless could my phone being an le2117 not and le2115 have made an actual difference even though there is no hardware difference

stez827 said:
I tried all those trouble shooting steps none of which worked my phone is a T-Mobile OnePlus 9 but I bricked it when trying to convert to global but was able to bring it back with the Indian 9 pro msm then flash global it's after that and have been running nameless for a while now but now I need to update to c.48 to stay up to date with nameless could my phone being an le2117 not and le2115 have made an actual difference even though there is no hardware difference
Click to expand...
Click to collapse
It could if it's recognizing it as a T-Mobile model. I can modify a tool to flash T-Mobile models but it will take me a bit because it's a huge file to upload.

EtherealRemnant said:
It could if it's recognizing it as a T-Mobile model. I can modify a tool to flash T-Mobile models but it will take me a bit because it's a huge file to upload.
Click to expand...
Click to collapse
That would be awesome don't be in any rush I may not be able to tinker with my phone today as I really need it to be working even if it's on an outdated version of nameless but it would be amazing if you could do that

stez827 said:
That would be awesome don't be in any rush I may not be able to tinker with my phone today as I really need it to be working even if it's on an outdated version of nameless but it would be amazing if you could do that
Click to expand...
Click to collapse
Is the error saying unsupported target at all? If it's not I don't think it will make a difference but I don't mind doing the mod regardless.

EtherealRemnant said:
Is the error saying unsupported target at all? If it's not I don't think it will make a difference but I don't mind doing the mod regardless.
Click to expand...
Click to collapse
It says device does not match image not unsupported target

It's also possible that Nameless changed something that is causing the device not to be recognized correctly. If you flash the 9 Pro MSM and then immediately use the modded MSM it should work in theory but I don't have any experience with these T-Mobile models.

EtherealRemnant said:
It's also possible that Nameless changed something that is causing the device not to be recognized correctly. If you flash the 9 Pro MSM and then immediately use the modded MSM it should work in theory but I don't have any experience with these T-Mobile models.
Click to expand...
Click to collapse
When I first tried it that's what I did flashed India 9 pro msm then tried the fix msm but no luck and it being a T-Mobile model theoretically shouldn't make a difference as it's the same hardware just a different model number

stez827 said:
When I first tried it that's what I did flashed India 9 pro msm then tried the fix msm but no luck and it being a T-Mobile model theoretically shouldn't make a difference as it's the same hardware just a different model number
Click to expand...
Click to collapse
Well you're the first person this hasn't worked for so I'm grasping at straws trying to figure out why.

EtherealRemnant said:
Well you're the first person this hasn't worked for so I'm grasping at straws trying to figure out why.
Click to expand...
Click to collapse
Yeah oh something else I have done is I originally used to EU9pro MSM but that seems to be very unlikely to have done anything as I used the Indian 9pro MSM

stez827 said:
Yeah oh something else I have done is I originally used to EU9pro MSM but that seems to be very unlikely to have done anything as I used the Indian 9pro MSM
Click to expand...
Click to collapse
Yeah I doubt that's the issue. It's strange that you're not getting unsupported target on either selection in the drop-down though. You should get it on the O2 for sure since you used the India MSM last.

EtherealRemnant said:
Yeah I doubt that's the issue. It's strange that you're not getting unsupported target on either selection in the drop-down though. You should get it on the O2 for sure since you used the India MSM last.
Click to expand...
Click to collapse
Oh I get unsupported target on O2 but not India sorry