yashsingh1/xdaforums huggingface dataset:
[OnePlus 9 Pro] Appreciative:
Sim unlock is not a requirement for this device but it's good you have it already.

Using the Tmo->Eu conversion bypasses the need for unlock.bin but again, it's good that you have that coming as well.

The simplest way is to use the Tmo->Eu MSM conversion tool and then Oxygen Updater over to global if you want to do that instead of stay on Eu. Either way, using the conversion tool is the way.

From my current understanding, the only real functional difference from Eu vs Global is the latest update speed. I've read that Global was getting the latest updates first. Others report they're available on Eu also and the app was caching old results. I can't be sure on that as I stayed on Eu and I stay on Android 11 (11.2.10.10) but that's what I've read. Hopefully someone else will have additional information on any technical differences. I've been fine using Eu on Tmo/USA.

Since you're interested in going to the latest version, Oos13, you won't need to flash the modem back in as that was fixed for oos13.

You should definitely backup your efs and modemst1/2 partitions before you do anything else.

Open MSM, press F8, select the partitions you want to backup, password is "oneplus". Press read back and they will be stored in C:\ root.

It is advised to unlock bootloader on Android 11 before updating to any other version. I unlocked bootloader and rooted with Magisk on A11 right away. Using the MSM tool to readback boot_a and adb push it onto device. Then having magisk apk patch that boot_a. In my case, by unlocking bootloader and then taking OTA, I retain L1 drm. If I take OTA and then unlock bootloader, I lose L1 drm.

Temp unroot, take the OTA, magisk install to inactive slot, repeat until you're at the firmware you want. Check replies at the back end of this thread: https://xdaforums.com/t/convert-your-t-mobile-le2127-to-eu-via-msm-no-unlock-bin-needed.4272837/

for which OTA route others are taking to get to oos13
[OnePlus 9 Pro] dctinc12:
To convert your physical T-Mobile sim to an e sim

Go to the home screen. to open the menu, swipe up on the screen.

scroll to the right, choose settings

scroll down choose connections.

choose a sim card manager.

choose sim 1.

choose convert to eSIM

chooses OK.
[OnePlus 9 Pro] Nowaker:
Thank you @Appreciative for explaining this. I'm very appreciative of your help. ;)

Global/EU thing is now clear to me. Speaking of unlocking the bootloader, I have more to ask.

So I'm already on LE2127_11_C.21 which is the latest version available to me. I'm actually unsure what OxygenOS version it is. "About device" says Android 12, security update November 5, 2022. There is no indication what OOS version it is anywhere in the settings. Is it OOS 12 or OOS 13?

Anyway, I upgraded all the way to LE2127_11_C.21 after I received the phone. Should I downgrade to the original OOS11 ? And how, given full OTA images for LE2127 are nowhere to be found?

Should I follow the instructions in OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)? Like I said before, all guides cover "how" but barely ever "why" or "when", and that one is no different.

Why is it important? What are the consequences of losing?
[OnePlus 9 Pro] Appreciative:
Android 12 shipped by OnePlus is oos12. Same for 11/13 and any other. All oos12 is android 12 but not all android 12 is oos. For all OnePlus devices, it's OOS (or ColorOS).

(To make this more confusing, OnePlus for some reason, labels the oos12 packages as _11_C.xx but it's not Android 11. That is why most of the forum mentions them by C.xx and for oos13, F.xx)

You are on oos12.

Follow the conversion thread, you won't need that thread you posted unless you brick and want to go back to stock Tmo firmware to start over again clean. The one I posted is the one you'll use.

When you use the MSM tool, you'll automatically go back to Android 11 early version. It's advised to unlock bootloader from Android 11 for two reasons. One is what I mentioned about my situation. I lose L1 drm by unlocking right after the msm conversion tool but I regain L1 drm after taking the OTA to 11.2.10.10. The other reason is for people without their unlock token. You've already submitted to OnePlus website so this may not affect you. For those who converted to Eu to bypass the unlock.bin token from OnePlus, they NEED to unlock the bootloader on A11 because the bypass is gone/fixed in Android 12/13. They require the unlock.bin if they didn't unlock bootloader in A11.

After you do the MSM Eu->Tmo tool (https://xdaforums.com/t/convert-your-t-mobile-le2127-to-eu-via-msm-no-unlock-bin-needed.4272837/), you will be on Android 11, OOS11, 11.2.3.3 - You can unlock the bootloader there without the token or wait for your token and unlock it later.

After you MSM, you'll start in a clean Android/OOS 11 state. Then you get oxygen updater from play store and update to oos12 and then oos13.

Looking in the back pages of the thread above, you will see which route people take to get there. I BELIEVE it is to take the local upgrade to C.65 (oos12) and then F.16 (oos13).

Losing L1 drm is typically from losing Device Certification. When that happens, google pay, Netflix, Disney+ and other apps that require certification may not work at all or diminished.

If you get to oos13 and have lost L1 drm, do not panic, you have some options to get it back since you'll be rooting along the way. The standard approach is using USNF (universal safetynet fix) module in Magisk. There is a thread a few posts down that's labeled wrong, it's labeled as a question but it's a how-to GooglePay/cts passing (https://xdaforums.com/t/oos13-gpay-cts-profile-fix-for-unlocked-bootloader.4525423/)
[OnePlus 9 Pro] Nowaker:
Thanks again, @Appreciative!

So by you saying that, it means I can use the MSM tool you linked without having to unlock the bootloader beforehand. Is that correct?

And then I should be able to pick NA or EU, and it won't really matter, right? Since after I MSM the phone, it identifies itself as LE2125 while previously it was LE2127?

Ah. The SafetyNet, ctsProfile, and all that stuff. I didn't know it also goes by L1 DRM name. Thanks for clarifying.

I think everything is clear to me to the point of MSMing the phone, which turns it into LE2123 (EU). Can you confirm these are the steps to get there?

1. Starting from LE2127_11_C.21 (current firmware - OOS12 / Android 12 / T-Mobile)

2. Use the MSM TMo->EU conversion tool which downgrades the phone to Android 11, OOS11, 11.2.3.3, identified as LE2123 (EU)

3. Unlock bootloader.

But now what? When and how exactly do I do things with Magisk? I did the extract-boot.img-patch-and-flash process multiple times on OnePlus 8, OnePlus 8T, OnePlus 9 Pro (Global). It's easy. But it appears things get tricky here on OP9P LE2127 T-Mobile version, so I'd like some clarification.

Am I supposed to patch boot.img with Magisk App? But what do I extract the boot.img from at this stage?
[OnePlus 9 Pro] Appreciative:
To be clear, L1 drm is a separate thing from Safetynet and CTS. L1 dropping to L3 is a result of "insecure device". When you unlock the bootloader, the device is detected as modified. That state fails safetynet. A byproduct of that is DRM drops down to L3. L3 means apps like Netflix will only work in SD quality, if at all. Some apps won't even open or show up in play store when device is not certified. L1/L3/Safetynet/cts aren't exactly interchangeable even tho I kinda made it sound that way. Just in the context that when you are not passing safetynet, a byproduct is you lose L1 drm, because of the device certification not passing.

Yes, you can use the MSM conversion tool without the bootloader being unlocked.

MSM Tmo->Eu conversion tool.

Unlock bootloader.

Download Oxygen Updater in play store.

Root with Magisk.

I pull my boot image using the MSM tool readback as mentioned above, after the conversion and before I take the OTA.

MSM->F8->boot_a and see it in C:

Then I adb push C:\boot_a.img to /sdcard/

Magisk patch the just-pushed boot image.

Temp boot that boot image with:

fastboot boot boot magisk-patched-boot.img

That will temporarily boot you with root. You have to finish the magisk install from here.

Then I reboot and ensure phone is rooted properly.

I download the OTA and let it install. Do not let it reboot after the OTA is finished. You need to go back to magisk and temp unroot by pressing "uninstall magisk" and choose "restore images". Then choose the option for 'flash to other slot OTA'.

This information is based on me going from 11 early to 11 later. There may be some changes for 12/13 that someone else can chime in on.

Alternatively, you can wait to root until later.

Things really aren't tricky on this model. It's actually pretty smooth with the conversion tool. * At least for 11 in my experience. Someone else will have to help you more for 12->13 as I haven't done that. My oxygen updater currently shows release version LE2123_11_F.72 (Eu) or LE2125_11_F.17 (global)

Both of which are oos13. I don't know if it's possible to jump from 11 to 13. I've only read reports of going to 12 and then 13 but I don't read much of 12/13 as I'm staying on 11
[OnePlus 9 Pro] Nowaker:
OK, cool. So after following the guide, I still should look "secure" for everything, right? On my old OnePlus 9 Pro LE2125, I'm passing SafetyNet, and my GPay works - even though I have Magisk and root. (And use my old phone via `scrcpy` because I broke its display lol)

OK, sounds good. Thank you.

Just to clarify: by saying "download the OTA", do you mean using the system-provided update tool, or are we talking about downloading LE2125_11_F.16 from Oxygen Updater?

You also made me learn about "install to inactive slot" - https://topjohnwu.github.io/Magisk/ota.html. I wasn't aware it existed. I applied any OTA updates in the past manually. Download full OTA, extract boot.img, patch it with Magisk, flash OTA and patched boot. Like a fresh install. Also explains why I barely ever upgraded.
[OnePlus 9 Pro] Appreciative:
Well that's where we can both be unsure. I've read that you should go to 12 (c.xx) and then 13 (f.xx) using Oxygen Updater. However, I used the built in system updater ota to get from 11.2.3.3 to 11.2.10.10 myself. I believe you are supposed to use the oxygen updater apk from play store to get to 13 but for that ... someone else will have to clarify exactly which way to get to 12/13. It is for sure covered in this forum, I just have no reason to remember it as I'm staying on 11.

Even if you decide to root later instead of earlier on and Magisk uninstall each time, you can use MSM to readback the boot image and send it over for patching. It's not a big hassle.

After the conversion, you won't have mobile service until you either get to oos13 or flash the modem (modem_a/b not modemst1/2) back in . Don't panic if you see no signal right after Eu conversion is my point
[OnePlus 9 Pro] Appreciative:
Either way, you should install USNF magisk module and clear cache of google apps to get or stay device certified. That is outlined in the thread I linked above for oos13.

This device has a lot of pros. We can have root and unlocked bootloader, pass safetynet and retain L1 drm, doesn't require sim unlock to unlock bootloader (only needs minor bypass for the OEM unlocking the toggle), unlock.bin bypass with Crazazn's conversion tool, ability to flash over to other firmware regions, and good custom rom and mod support
[OnePlus 9 Pro] Nowaker:
For the record - my current One Plus 9 Pro LE2125 (not the new one LE2127 I just purchased) has Android 11, OOS 11.2.7.7.LE15AA. It's rooted and passes all SafetyNet and stuff, and I don't have any extra Magisk modules.

Are you saying it's upgrading to newer versions of Android / OxygenOS that enhances security, and requires us to use extra Magisk modules to hide the fact our bootloader is unlocked?
[OnePlus 9 Pro] Appreciative:
I'm not saying that but it's probably a fair deduction. I had the same experience as you when I took OTA to 11.2.10.10, I was certified still. Prior to that (11.2.3.3.), I was not certified when bootloader unlocked. I keep usnf module installed just for extra assurance. Although, in some cases on our devices, it will be required to pass safetynet. There's a whole thread-in-thread on the hit&miss nature of some people losing certification and others keeping it, supposedly on the same exact set ups. Then I experienced it myself on the 10T. It sounds like it's more necessary on oos13 but I can't be sure.

As a side note, I'm still very tempted to try oos13. I've heard it's really smooth on this phone. Please let me know how you feel about it. Especially in comparison to oos11
[OnePlus 9 Pro] Nowaker:
I will. I'm collecting information on all the steps, before I start doing it. I think I'm ready but it's also a matter of available time to sit down and do it. With busy life, I don't know if it's going to be tomorrow, or some evening next week.

Note however I'm a pretty non-standard Android user. I keep thing my way. I always use Nova Launcher - which automatically keeps a lot of new features away for me. I may not really experience any difference once my things are in. All I really care about is AdAway and Vanced for stress-free experience, a fully functional Android Auto for driving, Google Photos and Nextcloud for photo backups, and that's about it.
[OnePlus 9 Pro] Appreciative:
I've read Android Auto is broken after Android 11, not sure what fixes are available however. I've read tons of people having issues with AA after upgrade to 12. Not OnePlus specific, I've read about samsung, Realme, asus rog and others all not connecting after Android 11. I think it might be something to do with AA going away. May be something to look into before heading to 13 if it's a must-have for you.

I have AA set up as well. The only issue is when I do screen2auto, to get the icon in my headunit to open s2a, I must uninstall AA update, connect to my car, then upgrade back to latest AA. Then I'm able to cast/mirror my screen to my navigation screen. The kids like to watch youtube videos and whatnot while we are on the road. Or, if they bring their tablets, I use VPN Hotspot for bypassing the Tmo throttle of 600kbps on hotspot connected devices. They can youtube their choice for the rest of the ride. (Playing iSpy, find the colored car, count the diesel trucks etc only lasts for about 15 mins)

I also use Vanced. I tried ReVanced but it started glitching my screen out. I'll give them some time to fix their bugs before I head over to it. It's kinda cool because you can (must) patch in/out the features you want on whatever youtube apk you want. It's still a bit early based on the bugs I experienced but I am sure it'll get better over time
[OnePlus 9 Pro] o muerte:
I'm not sure if this works for the 9 pro (I'm researching conversion of a t-mo model that I'm thinking of ordering ATM) but on my 7T I always take the option to download the full update image (usually like ~2GB) and install to the inactive slot, then you just inatall magisk to the inactive before rebooting. That lets you skip the uninstall bit and allows you to roll back to the current rooted state if there're any problems with the update. It's a bigger download than an OTA patch but it's fewer steps altogether.
[OnePlus 9 Pro] AKZADRAN:
Can you

Can you please give me the link to Tmo to eu MSM tool that you mentioned without needing the unlock.bin? I am looking for that from a week but no luck
[OnePlus 9 Pro] Appreciative:
TMO-EU-MSMConversion-v1.0.zip | by craznazn for OnePlus 9 Pro

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

In this thread:

Convert your T-Mobile (LE2127) to EU via MSM, No unlock.bin needed!

*** Use this at your very own risk. *** You will lose all data *** Backup your working modemst1/2 and persist. If you lose these for any reason, it's unique to your device and not recoverable if you didn't back up (via MSM or other people). ***...

xdaforums.com

Unlock bootloader on oos11 after conversion and before updating to 12/13/14. Flash tmo modem in after each update if you're in the US
[Samsung Galaxy S22] krriis:
Hello,

On 10/24 I upgraded my S22 to A13 and since then I have had some annoying problem with it.

Every few hours there is a problem with the gyroscope/accelerometer on my phone. When I hold the phone vertically, the screen rotates horizontally (and vice versa). When I restart the phone, the problem goes away for a few hours. The problem is in all over the phone, but the easiest way for me to detect it is by turning on the camera (the icons are in the wrong orientation).

I did a hard reset twice. I have flashed the phone after odin (two times) and nothing helped - the problem keeps coming back.

I didn't drop my phone or hit with it, so it's more likely a software problem (especially since the problem disappears after a reboot).

I also checked the diagnostic options available from the phone menu and there is always information that the sensors are working properly, even when is not a true. Test in hidden menu (*#0*#) also show "PASS".

Also the November update did not bring any improvement. Yesterday I did second flash after odin, with november system - nothing helped again.

I have no more ideas what I can do to fix this. :( I suspect that sending the phone to the service will end up the same - the service will upload the software again and say that the problem is solved, and it will not be true...

Bug report as well but they not helped me yet.

Have any of you encountered this problem and managed to solve it?
[HTC Excalibur] ammarr:
I came across this really interesting app (KTPocketLaunch2). Basically it allows you to type the name of the app, and it incrementally finds the app in your start menu. As soon as it finds a match, it launches the app. I ran into a bit of trouble earlier on (key matching was off for the number keys), but you can reassign them in the Keyswap.ini file. There's an example on the site and a readme for it.

Oh and it can also act as a task manager, i.e. can switch to open apps, kill them etc.

This seems to be the quickest way to launch an app. Anyone else tried it? Also, I cant seem to get the mapping for 'a' to work. Any idea how to fix that?
[Samsung Galaxy S10 Questions & Answers] helpmys10please:
View attachment 5775833View attachment 5775835The only time my screen changes from this is when it occasionally reads "KERNEL PANIC" rather than "User push reset keys for 7 secs."

I've gone through a lot of discussions and videos. I've tried battery removal, Odin, button shortcuts, and even ram dumps.

I've tried flashing firmware on three separate PCs, but I keep getting the same error. I am unable to boot into recovery mode at all. I only have the standard Android stock firmware, and all I see The SAMSUNG GALAXY S10 SECURED BY KNOX POWERED BY ANDROID is the phone I'm using. I'm stuck in a similar loop right now. I am powerless; there are no animations or charging. I've tried so many things that I even tried booting my computer into recovery mode.

Heres the ram dump.
[Samsung Galaxy S10 Questions & Answers] meric57:
Hello helpmys10please, on your captures you don't see much would be good to make readable captures thank you.

Your S 10 you flash with official rom and your S10 which model SM-G9XX F or U or others, to know if it is reconditioned with a chip region outside EU the update or flashed an official EU rom will be a failure.

https://www.droidwin.com/samsung-stuck-in-ss-rdx-watchdog-reset-mode/
[Samsung Galaxy S10 Questions & Answers] helpmys10please:
Doesn't work I've tried this article yesterday for it.
[Google Pixel Watch] Tcukcufc:
What's the latest versions the watch should be running.

Mine says Android 11 and security update is 1st July 22.

Is this correct or is there later versions?
[Google Pixel Watch] DoobyDroid:
It's correct same on mine , it's wear os 3.5 latest build so all good
[Google Pixel Watch] joderme:
Should we be getting a December update? I'm on Verizon and still waiting.
[Google Pixel Watch] kpjimmy:
I got my update when I got the December update on my Pixel 7 two nights ago. (12/5/22) I am on Tmo in the US.
[Google Pixel Watch] fred2546:
I just updated my 6 Pro. My watch "up to date" still shows Android V 11, July 1, 2022.
[Google Pixel Watch] Nekromantik:
try connecting to Wifi and then going to update page and press the tick on the screen like 6 times. takes a while to get it to update
[Google Pixel Watch] GuyInDogSuit:
I don't see a tick on my screen though.
[Google Pixel Watch] fred2546:
No Tick here either.
[Google Pixel Watch] DoobyDroid:
Yer I didn't get the tick bit lol , but if you follow 9to5google
[Google Pixel Watch] fred2546:
That did it - it required being placed on the charger in my case. Here's a screenshot I captured. I had tapped that little icon before but probably not persistent enough.

View attachment 5780443
[Google Pixel Watch] Mouarfff:
Hello,

My watch started the update by itself (i didn't tap the icon as in the video), and it has freesed, now it doesn't start anymore.

The screen stay black, the green light at the back blink super fast when i move it, then stop after about 2sec.

Am-i the only one with this issue? Any idea how to fixe it?

Edit : i found a way, i needed to do a hard reboot :

How to fix a Pixel Watch with the black screen of death

This morning, I woke up to a bit of a troubling situation. Right as I was ready to leave the house, I went to my bedside table as I do every single day and I grabbed my earbuds, my phone, and my watch. As I situated my things in my pockets and onto my wrist,...

chromeunboxed.com
[Android Auto General] myabc:
hello. half page is occupated. please is possible deactivated? thanks
[Samsung Galaxy S22 Ultra] AbuOmar2040:
Is anyone can help to solve it?

(Samsung Member)

View attachment 5775987
[Samsung Galaxy S22 Ultra] butchieboy:
Says right there server error.
[Samsung Galaxy S22 Ultra] AbuOmar2040:
I used another samsung phone and the Samsung member is work but in Galaxy S22 ultra no
[Samsung Galaxy S22 Ultra] Village_Idiot:
I've gotten this error too. It seems to be a backend problem. It occurrs when my phone switches from a browser to the Samsung Members app. Which browser do you use? I use Microsoft Edge. It's happened while using my Tab S7 too.
[Samsung Galaxy S22 Ultra] AbuOmar2040:
i use chrome
[Samsung Galaxy S22 Ultra] Village_Idiot:
Both Chrome and Edge use the same engine. Try Samsung Internet and see what happens.
[Samsung Galaxy S22 Ultra] AbuOmar2040:
My problem is with Samsung Member .I used other phone with same account it is work but with Galaxy s22 ultra is no .
[Samsung Galaxy S22 Ultra] Village_Idiot:
I have the same problem. It happens when I am browsing using Edge and I click on a link that takes me to Samsung. It tries to open Samsung Members but gives me that same error. I also got it using the Samsung Shop app.
[Touch Pro, Fuze General] shinook69:
noob question recently flashed natf 2.2 rom now individual contact ring tones not working. Please help
[Google Pixel 7 Pro] amunarjoh:
Anybody else being forced to reboot due to fingerprint scanner, Google feed or any other function misbehaving?

Due to issues with fingerprint recognition, I am forced to reboot several times every day.

As well as Google feed is acting up, and displaying a blank canvas when I swipe left on home screen.

I use standard Pixel launcher, not beta release system.

Any suggestions?

(Yes, I have done a full system reset. I have cleared cache),😀
[Redmi Note 11 Pro+ 5G (peux)/POCO X4 Pro 5G (veux)] radmir:
Any ideas how to fix nfc on 11E PRO?