I bought a t mobile one plus 7 pro - version gm31cb-on 9.5.10 before I read about the hassle it can be compared to an unbranded phone. The bootloader is unlocked.
I tried the msm tool to go to international version but it got stuck on parameter preload so I decided to try to root and get rid of the tmobile flash screen later.
long story shortened, the phone is stuck on the warning screen.
Pressing buttons, I can get it into fastboot but adb doesnt see the phone to flash/push anything.
If I try to boot into recovery, it sticks at the warning screen.
can I somehow get adb to see the phone in fastboot mode?
do you know if i need a certain os/file so i can get past the parameter preload with msm?
i followed the steps in the msm tutorial.
if msm sees the phone and it gets to parameter preload does it mean it is not a driver issue but maybe the wrong software?
Any advice is appreciated.
thank you for your time and expertise
Marc
through fastboot
I am using the universal fastboot and adb tool and trying to flash boot twrp and start over
current error: failed remote recovery a no such partition
after fastboot --set-active=b
same error
update 2
somehow, after simply trying over and over i got twrp on partition a
i think i will stay here until a kind member can direct me to an img that will work
thank you
marcadamf said:
I bought a t mobile one plus 7 pro - version gm31cb-on 9.5.10 before I read about the hassle it can be compared to an unbranded phone. The bootloader is unlocked.
I tried the msm tool to go to international version but it got stuck on parameter preload so I decided to try to root and get rid of the tmobile flash screen later.
long story shortened, the phone is stuck on the warning screen.
Pressing buttons, I can get it into fastboot but adb doesnt see the phone to flash/push anything.
If I try to boot into recovery, it sticks at the warning screen.
can I somehow get adb to see the phone in fastboot mode?
do you know if i need a certain os/file so i can get past the parameter preload with msm?
i followed the steps in the msm tutorial.
if msm sees the phone and it gets to parameter preload does it mean it is not a driver issue but maybe the wrong software?
Any advice is appreciated.
thank you for your time and expertise
Marc
Click to expand...
Click to collapse
You just need to update Qualcomm drivers.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
blas4me said:
You just need to update Qualcomm drivers.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Click to expand...
Click to collapse
doing so now...
thank you for the help.
I somehow got it up and rooted.
will msm work while rooted or mess up root?
I have a gm1915 wich is not listed in the link for the drivers? any thoughts?
These should work. As for MSM tools use the international version.
If you can't shut off device, hold power + Vup for about 10 seconds without being connected to a power source. If your fast enough, keep device plugged, and just press Vdown, to boot recovery.
https://drive.google.com/file/d/1JoHF6RF1THVn3pQWywaJz2URGTPxL2pH/view
not sure where you are at right now, but i installed a wrong os version (android 10 on my phone with pie on it). It would only boot into fasdtboot screen no matter what I did or tried. Could not get adb to recognize it, had no twrp or rom installed correctly. No way to fix it, could not use MSM tool as phone had to be able to be shutoff, which mine couldn't. never recognized it due to that. tried drivers to no avail. not really many answers out there, til I found out about fastboot roms.
check out this page: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
* IMPORTANT: in above link, remember to only download the OS version that fits your phone previously. DO NOT try to update your phone to a different version using that method. Also this method will NOT work on a branded phone, so if your phone is originally a T-Mobile phone then unfortunately this is not a solution for ya.
You may also want to check out this page as well: https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/
I hope this helps. The Fastboot Rom solution worked for me, it saved me from throwing my phone in the trash. I ran the bat file and it did the rest.
Related
Hi everyone,
after a whole day spent try to fix my oneplus 6, now the roblem is that the fastboot is not working anymore. it gets stuck at the starting point with the oneplus logo and the writing Fastboot Mode.
Just to explain better, i rooted my phone but, trying to fix an audio problem, i did something wrong (probavly wiping all datas with twrp) and the phone got stuck at the Fastboot mode (opposite problem that i have now). After i fixed this (flashing manually every partitions) the phone is working again, but i realised that, by mistake, i used the oxygen 9.0.11 for oneplus 6T. So i tried to go to the Fastboot Mode but it gets stuck at that point. I also see that the phone is not rooted anymore.
I installed again Adb and fastboot but it doesn't fix the problem.
Just to give other random informations, the boot loader is still unlocked and i can't lock it.
As you can see i'm totally not an expert. I just wanted to root my oneplus 6 to increase the volume of the headphones.
Anyone that can help me?
Thanks
Pipp8888 said:
Hi everyone,
after a whole day spent try to fix my oneplus 6, now the roblem is that the fastboot is not working anymore. it gets stuck at the starting point with the oneplus logo and the writing Fastboot Mode.
Just to explain better, i rooted my phone but, trying to fix an audio problem, i did something wrong (probavly wiping all datas with twrp) and the phone got stuck at the Fastboot mode (opposite problem that i have now). After i fixed this (flashing manually every partitions) the phone is working again, but i realised that, by mistake, i used the oxygen 9.0.11 for oneplus 6T. So i tried to go to the Fastboot Mode but it gets stuck at that point. I also see that the phone is not rooted anymore.
I installed again Adb and fastboot but it doesn't fix the problem.
Just to give other random informations, the boot loader is still unlocked and i can't lock it.
As you can see i'm totally not an expert. I just wanted to root my oneplus 6 to increase the volume of the headphones.
Anyone that can help me?
Thanks
Click to expand...
Click to collapse
Try: https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
The idea is to boot it in download mode. You'll need the Qualcomm drivers, msm download tool, and oos full rom. Run the tool as administrator.
Pipp8888 said:
Hi everyone,
after a whole day spent try to fix my oneplus 6, now the roblem is that the fastboot is not working anymore. it gets stuck at the starting point with the oneplus logo and the writing Fastboot Mode.
Just to explain better, i rooted my phone but, trying to fix an audio problem, i did something wrong (probavly wiping all datas with twrp) and the phone got stuck at the Fastboot mode (opposite problem that i have now). After i fixed this (flashing manually every partitions) the phone is working again, but i realised that, by mistake, i used the oxygen 9.0.11 for oneplus 6T. So i tried to go to the Fastboot Mode but it gets stuck at that point. I also see that the phone is not rooted anymore.
I installed again Adb and fastboot but it doesn't fix the problem.
Just to give other random informations, the boot loader is still unlocked and i can't lock it.
As you can see i'm totally not an expert. I just wanted to root my oneplus 6 to increase the volume of the headphones.
Anyone that can help me?
Thanks
Click to expand...
Click to collapse
Fastboot require Android SDK(Software Development Kit) and different USB drivers for windows computer may be that's the reason why your Fastboot is not working.
To Root your oneplus 6 :
https://www.theandroidsoul.com/oneplus-6-root/
msm download tool doesn't recognise my phone, and i tried to install the quualcom drivers but my pc whem i try to install it, it says that my phone already has the best drivers.
Pipp8888 said:
msm download tool doesn't recognise my phone, and i tried to install the quualcom drivers but my pc whem i try to install it, it says that my phone already has the best drivers.
Click to expand...
Click to collapse
Maybe uninstall those drivers, reboot pc and reinstall the New ones.
thejase said:
Maybe uninstall those drivers, reboot pc and reinstall the New ones.
Click to expand...
Click to collapse
How can I uninstall the old drivers? Thanks
Pipp8888 said:
How can I uninstall the old drivers? Thanks
Click to expand...
Click to collapse
https://www.drivethelife.com/window...remove-driver-on-windows-10-8-7-xp-vista.html
i unistalled all drivers with Driver Takent. The only driver detected is ADB whem i connect the phone. The Device Manager still recognise my phone in the Usb Devices section as "OnePlus" and still doesn't let me upgrade to the qualcomm drivers.
FINALLY PROBLEM SOLVED with qualcomm drivers!!!! Thank you gus for the big help.
Last question: should i keep useing now the qualcomm drivers? thanks
Pipp8888 said:
FINALLY PROBLEM SOLVED with qualcomm drivers!!!! Thank you gus for the big help.
Last question: should i keep useing now the qualcomm drivers? thanks
Click to expand...
Click to collapse
If it works, yes ofc.
Long story short converted my phone from TMO to global. Went to relock bootloader but didn't flash the global rom from Oxygen updater and had to MSM back to TMobile. I have all the latest drivers installed and all the latest tools. My pC detects my phone when its booted but when I go into Fastboot I can't send commands to it. ADB Devices runs and says the list but does not show the device number. Sending a command comes back as device not found. If I unplug the phone my pC makes the disconnect sound. There's no sign of my phone in device manager but when I go down to the tool bar I can find Android device attached via USB.
I spent 2 hours already trying to get this to work and I'm out of ideas. I've even googled it and tried everything there. My last thought is to MSM again in hopes that it resets something
Smallsmx3 said:
Long story short converted my phone from TMO to global. Went to relock bootloader but didn't flash the global rom from Oxygen updater and had to MSM back to TMobile. I have all the latest drivers installed and all the latest tools. My pC detects my phone when its booted but when I go into Fastboot I can't send commands to it. ADB Devices runs and says the list but does not show the device number. Sending a command comes back as device not found. If I unplug the phone my pC makes the disconnect sound. There's no sign of my phone in device manager but when I go down to the tool bar I can find Android device attached via USB.
I spent 2 hours already trying to get this to work and I'm out of ideas. I've even googled it and tried everything there. My last thought is to MSM again in hopes that it resets something
Click to expand...
Click to collapse
Update: Looks like I'm good to go. Phone is connected again. B Now when I try to unlock my bootloader I can't flash the unlock token I get an t error cannot load unlock_token.bin
Got it all figured out!
Smallsmx3 said:
Got it all figured out!
Click to expand...
Click to collapse
What did you do for PC to see phone in fastboot mode? I have the same thing where it cannot see in fastboot mode
Arr6 said:
What did you do for PC to see phone in fastboot mode? I have the same thing where it cannot see in fastboot mode
Click to expand...
Click to collapse
Honestly I was typing in adb devices instead of fastboot devices. So I think my computer was detecting it. I did reinstall drivers that I got from the OnePlus site. I made allot of dumb errors
Hi,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.
I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.
After trying to restore stock OOS and rebooting fastboot my phone is now stuck in Qualcomm Crashdump mode. I have MSMDownloadTool installed but it won't open, it just opens a windows saying "Program has been started" after executing it.
I also can't reboot to the bootloader, the phone just turns on or off.
What to do?
From my rather long post in https://forum.xda-developers.com/t/...your-device-to-oxygenos.4180837/post-86563159 :
"connect the phone to the PC whilst it's still in CrashDump mode and then press Pwr + Vol Up until the phone buzzes and then hold Vol Up + Vol Dn and MSM will then connect."
Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.
petrolblue said:
Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.
Click to expand...
Click to collapse
The delete/create logical commands are in the thread OP, but you have to tap on "click to show" button.
Note that fastbootd is not the same as fastboot. And you need to be in that mode to avoid the "critical" warning and to be able to do the logical partitions stuff.
So, after massively failing to update my 8T I am stuck in a bootloop with a bit of Crash dump [dm-verity device corrupted force dump].
I am still able to access fastboot but that is it. I can't get adb working, when I attempt to enter recovery mode all I get is a black screen, MSM is not able to find my phone/I can't get my phone to enter EDL (been trying for about 5 hours now).
I feel so defeated by this can anyone help me?
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.
Angilias37 said:
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.
Click to expand...
Click to collapse
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see the option to update the driver.
PS: you may need to flash boot, DTBO, and recovery in fastboot first before you can use fastbootd to flash the other partitions for the fastboot method.
BillGoss said:
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see l the option to update the driver.
Click to expand...
Click to collapse
Right but where's the update? From everything that I can find it is the most updated version
Angilias37 said:
Right but where's the update? From everything that I can find it is the most updated version
Click to expand...
Click to collapse
I use the driver (Qualcomm HS-USB QDLoader 9008) from https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008
OK
BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Ok I take back what I said! That link with the CMDs worked!
I really don't know what I did differently, probably skipped a step or something, but I was able to reset my phone!
Still unsure what is going on with the drivers but the crisis has been averted!
Thank you BillGoss! You are incredibly helpful!
Hey all!
Where do I start...? My apologies if my explanation is all over the place. I'll try to skip out all the parts that doesn't matter. Here it goes.
I wiped out my phone entirely to the point where there is only fastboot available. No recovery either. Storage is completely empty. Then, I found this guide: https://forum.xda-developers.com/t/restore-oneplus-9-to-stock-via-fastboot-commands.4265153/ and followed it through until step 5 where I can no longer flash anything further because I get this:
D:\adb>fastboot flash product product.img
Invalid sparse file format at header magic
Sending sparse 'product' 1/6 (262120 KB) OKAY [ 5.937s]
Writing 'product' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Click to expand...
Click to collapse
I then tried what was mentioned on the note about switching partition between a/b (I was on B, then switched to A): Still the same error. So, I went looking for other guides and found this: https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/. I downloaded everything, but the MSM tool kept giving me a "Packed image not exist!" error. I did some digging on that too and found it was supposed to be in the same directory as certain files (I can't remember), so I dragged this to my adb tools folder and still got the same error. I gave up on this method.
Then, I remember finding somewhere about merging all the partitions into one or something of the sort but lost the link. It was also for an older OnePlus model so I wasn't sure if it would've worked anyway.
SO ANYWAY, here I am at a loss. A few things I also want to mention that I've tried if it might help any:
Booted Windows with driver signature enforcement disabled
Tried booting into recovery and it was just black
Flashed twrp but touch wasn't working for some reason
Was able to load into twrp where I could toggle between ADB/fastboot mode, but freezes if I decide to reboot into system (which brings me to twrp's main menu)
Referenced back to the first guide and found a script that Slikkster2k made for powershell, but I think it just continues despite failing on the same step thus making it unsuccessful (not Slikkster's issue of course)
Attempted to find a way to sideload a stock rom.zip but was unsuccessful
All of my adb drivers and OnePlus drivers are up to date
My bootloader is unlocked
I know there's a way to fix this phone because it can still boot. I just don't have enough knowledge or experience so I tend to get lost on certain tutorials/guides. Any help would be appreciated.
Model: LE2110
First of all, you need to provide us with the model of your OP9
Is it Tmobile LE2117? or else? Please check.
zh_eco said:
First of all, you need to provide us with the model of your OP9
Is it Tmobile LE2117? or else? Please check.
Click to expand...
Click to collapse
Right! Of all the things I mentioned, I forgot to list that.
My model is LE2110. Unlocked.
try using the MSM tool in the sticky above.
just make sure you are in EDL mode and that your OnePlus has enought battery power.
Try to use OP9 Pro Indian MSM Tool to get your phone working.
Then flash Indian OP9 MSM Tool..
Unfortunatly I can't find the the MSM tools now as the link is now.
However, you can also give this one a try :
[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...
forum.xda-developers.com
jmadiaga said:
try using the MSM tool in the sticky above.
just make sure you are in EDL mode and that your OnePlus has enought battery power.
Click to expand...
Click to collapse
I cannot reboot into EDL mode. I forgot how I got up to the part where I could toggle between adb/fastboot so I couldn't reproduce it.
lyx91 said:
I cannot reboot into EDL mode. I forgot how I got up to the part where I could toggle between adb/fastboot so I couldn't reproduce it.
Click to expand...
Click to collapse
Simple. To boot EDL you need to do the folowing, then flash using MSM Tool.
Open the MSM app, select 'Others', and next.
Once you're in the flashing window do the following:
1-plug the usb cable to the phone.
2-plug your phone to the cable and very quickly hold volume + and - and power button.
3-Once you see 'Connected' on the flashing window, Release the buttons.
4-Click on start before the device gets connected (sometimes issues with usb3.0)
To fix Sahara Communication Error:
Simply while the phone is plugged in, hold volume + and - and power button (all at once) till the the device gets disconnected, and then it'll show 'Connected', after that then release the buttons.
Alright. I got everything working and my phone is now back up and running again. Thanks so much!
So now my next question is if my phone is on an Indian ROM now or global? How would I check?
lyx91 said:
Alright. I got everything working and my phone is now back up and running again. Thanks so much!
So now my next question is if my phone is on an Indian ROM now or global? How would I check?
Click to expand...
Click to collapse
Download Oxygen Updater from the Play Store:
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com
Then Procced till the step where you choose your device name and model.
If the device name was put by default as 'OnePlus 9' then it is Global ROM
If the device name was put by default as 'OnePlus 9 IN' then it is Indian ROM
If the device name was put by default as 'OnePlus 9 EU' then it is European ROM
Alright. Just OnePlus 9 was selected so I'm on Global. Thank you so much for your help!
sometimes there's this thing about spoonfeeding too.
but hey, you got your phone back so congrats.