Related
So I've been reading and just trying to verify if I'm using the T-Mobile version of oneplus 8i can't install the betas? If I'm wrong can someone point me to the correct version to install? We just got beta 3
goast said:
So I've been reading and just trying to verify if I'm using the T-Mobile version of oneplus 8i can't install the betas? If I'm wrong can someone point me to the correct version to install? We just got beta 3
Click to expand...
Click to collapse
The T-Mobile software removes the ability to install update from local storage. You would have to convert to Global to be able to install the betas. I am running a T-Mobile OP8, converted to Global, running beta 3 no issues.
Global Version
stompysan said:
The T-Mobile software removes the ability to install update from local storage. You would have to convert to Global to be able to install the betas. I am running a T-Mobile OP8, converted to Global, running beta 3 no issues.
Click to expand...
Click to collapse
Do you have a link as to where i can get Global version or steps for getting it ?
j1232 said:
Do you have a link as to where i can get Global version or steps for getting it ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8/how-to/guide-convert-to-global-t4105885
Make sure to read everything on the thread. Pull an image of your persist and your modem before flashing global. Some people lose network and/or FP, though having those two files can typically repair them pretty easily. If something bad happens during the conversion, you can use MSM to go back to T-Mobile firmware, but that doesn't fix your FP reader. That's why grabbing the persist is most important. You can do both from booting TWRP. Back up the modem directly in TWRP, and use adb shell along with "dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img" to make an image of the persist. Once on global, you can simply install the update through the local upgrade process and go from there. From what I have read, you do lose 5G SA. I don't know if this is still valid on the latest beta or not, but it is something to note.
stompysan said:
https://forum.xda-developers.com/oneplus-8/how-to/guide-convert-to-global-t4105885
Make sure to read everything on the thread. Pull an image of your persist and your modem before flashing global. Some people lose network and/or FP, though having those two files can typically repair them pretty easily. If something bad happens during the conversion, you can use MSM to go back to T-Mobile firmware, but that doesn't fix your FP reader. That's why grabbing the persist is most important. You can do both from booting TWRP. Back up the modem directly in TWRP, and use adb shell along with "dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img" to make an image of the persist. Once on global, you can simply install the update through the local upgrade process and go from there. From what I have read, you do lose 5G SA. I don't know if this is still valid on the latest beta or not, but it is something to note.
Click to expand...
Click to collapse
How can one tell of phone is using 5g SA on OB3?
crazynapkinman said:
How can one tell of phone is using 5g SA on OB3?
Click to expand...
Click to collapse
Using a program like LTE Discovery will tell you. In my case, it indicates I am connected to NR NSA 5G. I have not ever seen my phone go to SA 5G since converting, and I do live in an SA location and have connected while on T-Mobile software. See screenshot.
Mine says 5G NR
crazynapkinman said:
Mine says 5G NR
Click to expand...
Click to collapse
I have noticed it takes some fiddling with WiFi to get it to display network type. The 5G detection is still a WIP. There are probably other apps that may work better, but I am just used to using LTE Discovery over the years.
I'm also on a tmobile converted to global phone. Using Beta 3 and getting random errors with the sim card where phone says "no sim". Happens 1-2 times per day. Only way to fix is to reboot or eject the sim and reinsert. Either way, back to full bars for a few hours. I backed up modem and persist, but I don't think the Android 10 modem will work on Android 11. Also, can't flash because TWRP doesn't work on Android 11 yet. Very frustrating, looks like lots of reports of this happening on Oneplus 8 phones (Tmobile and unlocked) on here and oneplus forums. No solution found!
xxBrun0xx said:
I'm also on a tmobile converted to global phone. Using Beta 3 and getting random errors with the sim card where phone says "no sim". Happens 1-2 times per day. Only way to fix is to reboot or eject the sim and reinsert. Either way, back to full bars for a few hours. I backed up modem and persist, but I don't think the Android 10 modem will work on Android 11. Also, can't flash because TWRP doesn't work on Android 11 yet. Very frustrating, looks like lots of reports of this happening on Oneplus 8 phones (Tmobile and unlocked) on here and oneplus forums. No solution found!
Click to expand...
Click to collapse
I have Sprint sim and this is not happening.
Is Reliance JIO working on Oneplus 8T?
I have unlocked Tmobile OP 8T ( KB 2007) and it's not working for me.
5ud0 said:
Is Reliance JIO working on Oneplus 8T?
I have unlocked Tmobile OP 8T ( KB 2007) and it's not working for me.
Click to expand...
Click to collapse
It is working perfectly fine, although my device model number is KB2001.
You may have to flash the Indian firmware to make it work.
TheMystic said:
It is working perfectly fine, although my device model number is KB2001.
You may have to flash the Indian firmware to make it work.
Click to expand...
Click to collapse
Unfortunately nothing is working for me
Tried all 3 versions of oxygen os. It's working in my op 6t but not in op8t
5ud0 said:
Unfortunately nothing is working for me
Tried all 3 versions of oxygen os. It's working in my op 6t but not in op8t
Click to expand...
Click to collapse
I had the same problem on a Samsung S8+ (purchased abroad).
The solution was to flash the local firmware and everything worked after that.
You are probably flashing the OS. I'm saying you have to flash the FIRMWARE (which is different from the OS).
Someone who has a custom recovery installed may be able to help you.
TheMystic said:
I had the same problem on a Samsung S8+ (purchased abroad).
The solution was to flash the local firmware and everything worked after that.
You are probably flashing the OS. I'm saying you have to flash the FIRMWARE (which is different from the OS).
Someone who has a custom recovery installed may be able to help you.
Click to expand...
Click to collapse
Cool, Thanks for letting me know. I will look it up. If you have any threads that can help me, I would really appreciate that
Update: Just a clarification mate, by flashing firmware, do you mean flashing the global rom from fastboot? If so, that is how I flashed global rom on my T-Mobile. All the articles when I search for flashing firmware is pointing to the flashing from fastboot which is what I did.
5ud0 said:
Cool, Thanks for letting me know. I will look it up. If you have any threads that can help me, I would really appreciate that
Update: Just a clarification mate, by flashing firmware, do you mean flashing the global rom from fastboot? If so, that is how I flashed global rom on my T-Mobile. All the articles when I search for flashing firmware is pointing to the flashing from fastboot which is what I did.
Click to expand...
Click to collapse
8T is a very new device, and I don't think the required files are available yet. As far as I know, even TWRP isn't available yet for this device.
Once a custom recovery is available, someone who has the KB2001 model may be able to extract the required files and pack them in a flashable zip. It is these files that are primarily what distinguishes one model number from another.
This is NOT the OS/ ROM. The Firmware contains the modem and other driver files to support the telecom bands/ spectrum (among others) used in a specific region. I'm afraid you have to wait for now, as there is unlikely to be an immediate solution now.
You can try at the service centre though. They may be able to help here (although very unlikely).
the only reason why I converted to global is for faster updates, then OnePlus released oxygenos 12 and all my reasoning was gone. How do i go back?
Do the same but with this MSM tool
I recently have problem switching to global version and had to return to tmobile and used this.
Thread 'OnePlus 9 11.2.22.2 (T-Mobile) MSM Download Tool' https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/
Use the T-Mo MSM tool then apply any updates that T-Mo pushes down.
I tried this MSM tool to see if it would help me finally get my updates to A12, but it seems like something's borked and I wind up getting the same 506MB update that claims to be c.16 but winds up being 11.2.8.8. Just a heads up, you may not get back up to date!
Gabiru05 said:
Do the same but with this MSM tool
I recently have problem switching to global version and had to return to tmobile and used this.
Thread 'OnePlus 9 11.2.22.2 (T-Mobile) MSM Download Tool' https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/
Click to expand...
Click to collapse
RockfordRocksAHD said:
I tried this MSM tool to see if it would help me finally get my updates to A12, but it seems like something's borked and I wind up getting the same 506MB update that claims to be c.16 but winds up being 11.2.8.8. Just a heads up, you may not get back up to date!
Click to expand...
Click to collapse
Yes after updated this patch you will get another update notification Wich is complete of 4.8 gb.
Gabiru05 said:
Yes after updated this patch you will get another update notification Wich is complete of 4.8 gb.
Click to expand...
Click to collapse
It's been like 3 days now lol. Is it just really that slow to get the next patch? My phone still says up to date.
RockfordRocksAHD said:
It's been like 3 days now lol. Is it just really that slow to get the next patch? My phone still says up to date.
Click to expand...
Click to collapse
Humm something strange because in my case when I bought my op9 tmobile it updated to android 12 also oxygen. then I wanted to switch to the global version and bricked my phone by this reason I went back to install using that msm that I told you to the tmobile version again and got all update from android 11 to latest android 12 and all normal.
You really shouldn't convert back. T-Mobile gets the slowest updates by far and there is no downside to running global or EU firmware on it.
EtherealRemnant said:
You really shouldn't convert back. T-Mobile gets the slowest updates by far and there is no downside to running global or EU firmware on it.
Click to expand...
Click to collapse
Hello Ethereal I am agree with you but probably the only reason to return to the tmobile version would be to unlock the SIM in case it has not been done or it presents a problem in the global version marking dual sim which is my case currently.
I'm also gonna trade in my phone through T-Mobile, I assume they'll still let me do it with global firmware?
EtherealRemnant said:
You really shouldn't convert back. T-Mobile gets the slowest updates by far and there is no downside to running global or EU firmware on it.
Click to expand...
Click to collapse
Do you know how can I solve problem Wich show me dual sim after switch to global room but my phone show le1125 Wich is na version. I am confuse
Gabiru05 said:
Do you know how can I solve problem Wich show me dual sim after switch to global room but my phone show le1125 Wich is na version. I am confuse
Click to expand...
Click to collapse
You can install the Magisk fix to fix that.
[TMO] OOS/COS DATA FIX
TO CLARIFY THIS IS A ROOT ONLY FIX After gaining root install given module. Data is now retained. Even after reboot(s). No empty slot or waiting. Issue is TMO variant is showing multi sim. So props were added to make it like a conversion to...
forum.xda-developers.com
I use this on my global 9 to fix the issue in India and China firmwares.
Gabiru05 said:
Humm something strange because in my case when I bought my op9 tmobile it updated to android 12 also oxygen. then I wanted to switch to the global version and bricked my phone by this reason I went back to install using that msm that I told you to the tmobile version again and got all update from android 11 to latest android 12 and all normal.
Click to expand...
Click to collapse
I actually contacted T-Mobile about it and they seem baffled, so much so they tried talking to OnePlus about it and OnePlus told them my device is supposed to have 11, which I know it's not. Something feels ****y here
EtherealRemnant said:
You can install the Magisk fix to fix that.
[TMO] OOS/COS DATA FIX
TO CLARIFY THIS IS A ROOT ONLY FIX After gaining root install given module. Data is now retained. Even after reboot(s). No empty slot or waiting. Issue is TMO variant is showing multi sim. So props were added to make it like a conversion to...
forum.xda-developers.com
I use this on my global 9 to fix the issue in India and China firmwares.
Click to expand...
Click to collapse
If I was to switch to Global FW, is there a non-root way to fix the SIM issue? I use banking apps and a few Niantic games on my phone and they don't like root
RockfordRocksAHD said:
If I was to switch to Global FW, is there a non-root way to fix the SIM issue? I use banking apps and a few Niantic games on my phone and they don't like root
Click to expand...
Click to collapse
No, there's not, but I have been successful at hiding root from every app that I have tried to hide it from so it's a moot point for me.
It seems strange that the global NA ROM is having that issue though because the global ROM isn't a dual SIM ROM. EU, IN, and CN are dual SIM but global/NA is not. I guess maybe it's because the T-Mobile variant is technically dual SIM with it just disabled?
RockfordRocksAHD said:
I actually contacted T-Mobile about it and they seem baffled, so much so they tried talking to OnePlus about it and OnePlus told them my device is supposed to have 11, which I know it's not. Something feels ****y here
Click to expand...
Click to collapse
Really strange.
RockfordRocksAHD said:
I actually contacted T-Mobile about it and they seem baffled, so much so they tried talking to OnePlus about it and OnePlus told them my device is supposed to have 11, which I know it's not. Something feels ****y here
Click to expand...
Click to collapse
I'm having the same exact issue
Did you ever get it resolved?
AaronRamlochan said:
I'm having the same exact issue
Did you ever get it resolved?
Click to expand...
Click to collapse
No, unfortunately. I used a guide on here to bypass the greyed out OEM Unlocking switch in Developer settings and requested my unlock code from OnePlus so I could root on global A12 and use the Dual Sim fix. It's really a complicated mess for a rather nice phone.
Oem unlocking token code missing,how to collect token code or without code how to unlock oem unlock ? OnePlus 9 5g le2117
Hello.
So basically, I have a T-Mobile OnePlus 9 (LE2117). I went through that whole ordeal of having that global conversion script brick then phone and then bring it back to life using the India 9 Pro MSM. I tried a bunch of stuff, eventually gave up and contacted OnePlus support to get to a working T-Mobile MSM tool.
When the T-Mobile MSM they used did its thing, it went back to the T-Mobile software, however there are two issues with it:
1. The pink T-Mobile splash screen doesn't show up on boot but instead a black one that just says "android" shows up (see attached image)
2. The software updates button is grayed out and cannot be hit
The original T-Mobile MSM you can find online also works now, but it still results in this same issue.
I ended up using the global conversion MSM on OOS 11 and a custom rom for a few months each, both of which worked perfectly, but this is still an issue that is here after using the T-Mobile MSM again.
Is there any good way of fixing this issue? I do have quite a few of the important partitions backed up if those are necessary.
Thanks!
BGW#10 said:
Hello.
So basically, I have a T-Mobile OnePlus 9 (LE2117). I went through that whole ordeal of having that global conversion script brick then phone and then bring it back to life using the India 9 Pro MSM. I tried a bunch of stuff, eventually gave up and contacted OnePlus support to get to a working T-Mobile MSM tool.
When the T-Mobile MSM they used did its thing, it went back to the T-Mobile software, however there are two issues with it:
1. The pink T-Mobile splash screen doesn't show up on boot but instead a black one that just says "android" shows up (see attached image)
2. The software updates button is grayed out and cannot be hit
The original T-Mobile MSM you can find online also works now, but it still results in this same issue.
I ended up using the global conversion MSM on OOS 11 and a custom rom for a few months each, both of which worked perfectly, but this is still an issue that is here after using the T-Mobile MSM again.
Is there any good way of fixing this issue? I do have quite a few of the important partitions backed up if those are necessary.
Thanks!
Click to expand...
Click to collapse
Can u use op9 to global conversion msm with any problem
rizzmughal said:
Can u use op9 to global conversion msm with any problem
Click to expand...
Click to collapse
If you are talking about the T-Mobile to Global conversion MSM, yes.
BGW#10 said:
If you are talking about the T-Mobile to Global conversion MSM, yes.
Click to expand...
Click to collapse
Did u update to oos12 were there anyproblems u face in that
rizzmughal said:
Did u update to oos12 were there anyproblems u face in that
Click to expand...
Click to collapse
The dual sim/no service bug. I am aware of the root fix, but I was looking to get the T-Mobile software working normally again.
BGW#10 said:
The dual sim/no service bug. I am aware of the root fix, but I was looking to get the T-Mobile software working normally again.
Click to expand...
Click to collapse
What is the target id for ur device is it india or tmo
rizzmughal said:
What is the target id for ur device is it india or tmo
Click to expand...
Click to collapse
I would say that it is tmo because the T-Mobile msm tools works no problem.
I bought my now rooted 6A via Aliexpress, and I live in Canada.
Current version is TQ1A.230205.002.
Looking through past updates, this is the first time they've singled out "Canada" for a specific update... Which version should I be patching/flashing, given that my phone came from overseas (but has the NA bands)?
13.0.0 (TQ2A.230305.008.E1, Mar 2023)
OR
13.0.0 (TQ2A.230305.008.F1, Mar 2023, WINDTRE/Canada)
From what I can see, Windtre is a specific carrier. I would go with The standard version for unlocked phones. If that's wrong then the process should abort itself before making any changes
The specific versions seem to be based on carriers. Wind Tre looks like an Italian carrier, so I'd guess the "Canada" applies for use with all Canadian carriers. Or, it may be based on some regulatory difference. Google sucks at transparency. But, the specific versions come and go, so I'd guess they're all about something which didn't get integrated into the mainline code in time, so they had to create a special version.
I would go with the WINDTRE/Canada version. You're rooted, so you could always switch if you have trouble.
azthemansays said:
I bought my now rooted 6A via Aliexpress, and I live in Canada.
Current version is TQ1A.230205.002.
Looking through past updates, this is the first time they've singled out "Canada" for a specific update... Which version should I be patching/flashing, given that my phone came from overseas (but has the NA bands)?
13.0.0 (TQ2A.230305.008.E1, Mar 2023)
OR
13.0.0 (TQ2A.230305.008.F1, Mar 2023, WINDTRE/Canada)
Click to expand...
Click to collapse
Or if it is the wrong one you can just flash right over it with the Canadian one. But I really think that is for a French or Italian Canadian carrier that you don't subscribe to.
motolio said:
From what I can see, Windtre is a specific French Canadian carrier.
Click to expand...
Click to collapse
Really, where'd you find that? I just found links to an Italian carrier. Windtre isn't listed in Wikipedia's list.
motolio said:
Italian Canadian
Click to expand...
Click to collapse
That's a new one.
mike.s said:
The specific versions seem to be based on carriers. Wind Tre looks like an Italian carrier, so I'd guess the "Canada" applies for use with all Canadian carriers. Or, it may be based on some regulatory difference. Google sucks at transparency. But, the specific versions come and go, so I'd guess they're all about something which didn't get integrated into the mainline code in time, so they had to create a special version.
I would go with the WINDTRE/Canada version. You're rooted, so you could always switch if you have trouble.
Click to expand...
Click to collapse
motolio said:
Or if it is the wrong one you can just flash right over it with the Canadian one. But I really think that is for a French or Italian Canadian carrier that you don't subscribe to.
Click to expand...
Click to collapse
Okay I'll patch both of them first, then I'll see what sticks, thanks!
Follow up question: how do you do a nandroid backup?
I went to find TWRP and apparently boot.img is now part of the recovery partition so it won't work?
Can I just boot to TWRP using adb/fastboot from my computer to make the backup?
Just got this phone recently, so I haven't had the need to backup + update until now... Plus the whole "patching the security exploit" thing.
Dude, I would not start with the Windtre one. Sounds like it could just be a striped down/limited version. It looks like that rom might specifically limit access to specific bands that Windtre doesn't allow their customers to access.
I found this on Reddit about the pixel 7:
Google "even limited the band bandwidth on NR, like 20mhz for N3
It isn't a huge problem, unless some operator add/remove bandwidth on a certain NR band
This is the case with WINDTRE (Italy, 222-88): they recently added 20mhz to their N78 spectrum (before it was max 40mhz on some regions, others 20mhz, now every region is 60mhz) and now you can't use their N78 at all
Why?
Because on their carrier policy, WindTre SIMs can use only 40mhz, 20mhz and 40+20mhz on N78 (last case is NR CA, not 60mhz)
It's really great to have a 900€ phone (Pixel 7 Pro) that can't connect to N78 thanks to Google "
Good luck. Let us know how it goes!
mike.s said:
Really, where'd you find that? I just found links to an Italian carrier. Windtre isn't listed in Wikipedia's list.
That's a new one.
Click to expand...
Click to collapse
Lol. Word
azthemansays said:
Okay I'll patch both of them first, then I'll see what sticks, thanks!
Follow up question: how do you do a nandroid backup?
I went to find TWRP and apparently boot.img is now part of the recovery partition so it won't work?
Can I just boot to TWRP using adb/fastboot from my computer to make the backup?
Just got this phone recently, so I haven't had the need to backup + update until now... Plus the whole "patching the security exploit" thing.
Click to expand...
Click to collapse
If you find a good back up process, lemme know. I need a good recovery option, too.
I did find this elaborate process on Reddit: I HAVE NEVER TRIED IT.
https://www.reddit.com/r/GooglePixel/comments/ovlnbj/_/h7akg6l
motolio said:
Good luck. Let us know how it goes!
Click to expand...
Click to collapse
You guys had me worried, and couldn't even get the phone to get the update notification (to check the version of the update).
But when I was looking at downloading the two versions on Google's ROM depository I noticed that you can directly update the phone through Chrome on my desktop???
Man, has tech changed since my last phone (Mi A1 on Oreo)...
It ended up flashing the Global ROM, so the Italian/Canadian one wouldn't have worked.
Gave up on backing up my phone, so I just exported/uploaded the settings for my launcher + AOSP mods + a couple of others then just went for it.
Thanks again for the assistance!
azthemansays said:
I noticed that you can directly update the phone through Chrome on my desktop???
Click to expand...
Click to collapse
Hope does this work? I've never encountered that option
motolio said:
Hope does this work? I've never encountered that option
Click to expand...
Click to collapse
Android flash tool: https://developers.google.com/android/images
Just scroll down to the image you want and click "flash" next to it
It'll give you instructions, as well as help you with the drivers if Chrome can't detect the phone, then will reboot it into bootloader, then recovery, then back to normal boot into an updated phone.
Make sure to check that the drivers for recovery/bootloader modes are already installed by booting into them beforehand... Otherwise you'll have a small panic as I did and have to boot your phone again manually by holding the power + volume down keys for 30ish seconds (until it reboots) due to Chrome not detecting your phone.
I'd also suggest using a back USB port on your mobo rather than plugging it into any of the front USB headers.
*screen shots below are from my phone
azthemansays said:
Android flash tool: https://developers.google.com/android/images
Just scroll down to the image you want and click "flash" next to it
It'll give you instructions, as well as help you with the drivers if Chrome can't detect the phone, then will reboot it into bootloader, then recovery, then back to normal boot into an updated phone.
Make sure to check that the drivers for recovery/bootloader modes are already installed by booting into them beforehand... Otherwise you'll have a small panic as I did and have to boot your phone again manually by holding the power + volume down keys for 30ish seconds (until it reboots) due to Chrome not detecting your phone.
I'd also suggest using a back USB port on your mobo rather than plugging it into any of the front USB headers.
*screen shots below are from my phone
Click to expand...
Click to collapse
Oh wow. Thanks! I had no idea about this. I'll give it a try next time I have time to phone out!
Thanks again
azthemansays said:
It ended up flashing the Global ROM, so the Italian/Canadian one wouldn't have worked.
Click to expand...
Click to collapse
??? The flash tool should install whichever image you choose. I've never tried picking a completely wrong one, but I suspect it does have a simple check that at least you're flashing for the correct platform (e.g. Pixel 6a).
The carrier versions are what gets sent as an OTA update via the particular carrier(s). It's not clear how you determined that the carrier specific one "wouldn't have worked." I suspect either would boot and "work", although the incorrect one may not take full advantage of the carrier's capabilities or may experience minor issues. Google has never provided guidance on exactly what types of differences there are.
mike.s said:
??? The flash tool should install whichever image you choose. I've never tried picking a completely wrong one, but I suspect it does have a simple check that at least you're flashing for the correct platform (e.g. Pixel 6a).
The carrier versions are what gets sent as an OTA update via the particular carrier(s). It's not clear how you determined that the carrier specific one "wouldn't have worked." I suspect either would boot and "work", although the incorrect one may not take full advantage of the carrier's capabilities or may experience minor issues. Google has never provided guidance on exactly what types of differences there are.
Click to expand...
Click to collapse
All I know is that I didn't get a warning, the global ROM's bands are working with my carrier's (Public Mobile - a subsidiary of Telus) after being flashed, and as you've stated Google hasn't been open with the differences... so I'm going to err on the side of caution (and international compatibility) and stick with what works.
I may revisit it if I travel inter-provincially and discover issues with coverage, but the US bands are what are compatible with what's used in Ontario.