Related
I've been reading around and mostly want to know everything for this for that time when CM becomes stable.
Anyways:
Do you lose Verizon network functionality? By this I really mean, calls, SMS, SMS, voice mail, and 4G LTE.
When converted...just act like it's the US unlocked model when flashing ROMs? Do I need to flash the Verizon radio?
I'm confused...and the final question..
To convert it requires a SuperCID and then RUU flash, right? I've seen Sprint owners do it and one Verizon owner, but the instructions were all very unclear to me.
Thanks!
Answers are on post #4, tested it out after being sure of how to do this. If you're lazy, click here...
I've converted my VZW branded 10 to U.S Unlocked. I am NOT using the phone on Verizon network, so I can only answer part of your questions.
To convert, I changed my cid to SuperCID (22222222) and flashed the latest stock RUU.exe from HTC.com for U.S Unlocked. Pretty simple.
I can't tell you if the phone would work on Verizon network, but I would assume it would with a radio flash to get the basic things you mentioned working, as outlined in:
http://forum.xda-developers.com/verizon-htc-10/how-to/vzw-how-to-unlocked-model-vzw-t3376743
Haven't yet flashed any non-stock roms, but I can't imagine why this would be a problem. Also the CM thread has some people who flashed the Unlocked firmware on a VZW phone and got CM working.
I haven't and probably will never try, but I see advanced feature breaking after you do this like wifi calling and the like. but ive also heard all that's different is the radio. but theres different settings unlocked and hidden between the two that may give issues also.
so just give it a shot if you really want. the worst that would happen is you would need to switch back to Verizon firmware.
Tested it out...
Tarima said:
I've converted my VZW branded 10 to U.S Unlocked. I am NOT using the phone on Verizon network, so I can only answer part of your questions.
To convert, I changed my cid to SuperCID (22222222) and flashed the latest stock RUU.exe from HTC.com for U.S Unlocked. Pretty simple.
I can't tell you if the phone would work on Verizon network, but I would assume it would with a radio flash to get the basic things you mentioned working, as outlined in:
http://forum.xda-developers.com/verizon-htc-10/how-to/vzw-how-to-unlocked-model-vzw-t3376743
Haven't yet flashed any non-stock roms, but I can't imagine why this would be a problem. Also the CM thread has some people who flashed the Unlocked firmware on a VZW phone and got CM working.
Click to expand...
Click to collapse
afuller42 said:
I haven't and probably will never try, but I see advanced feature breaking after you do this like wifi calling and the like. but ive also heard all that's different is the radio. but theres different settings unlocked and hidden between the two that may give issues also.
so just give it a shot if you really want. the worst that would happen is you would need to switch back to Verizon firmware.
Click to expand...
Click to collapse
Changed my CID to SuperCID (22222222).
Got the latest Unlocked U.S. FW from the HTC Dev site (RUU EXE) and flashed it.
Flashed a Verizon radio in fastboot. (The same one used to make the actual U.S. Unlocked variant work on Verizon)
Flashed TWRP in fastboot.
Formatted my data.
It booted without issue.
Followed this guide (though, on initial boot it showed 4GLTE active BUT no bars (line through them).
After following the guide, I rebooted.
Testing functions:
Calls: Functional and no delays.
SMS: Functional and fast.
MMS: Functional and fast.
Data connection: Functional.
Behavior after reboot: Starts again with the bars crossed off, eventually comes up and working though. Works after that, calls too. Takes about 45 seconds to connect.
Thing to note: It seems as if my signal strength is lessened. Though, this could easily be placebo, weather, etc. It's 1:31AM and I've never paid attention to it before.
Network comes up as 3107 instead of Verizon Wireless.
HTC software updates seem to be broken, it gives a corrupted error. I'm locked/S-OFF, so dunno.
Final deduction: It seems to functional and all, without hiccup most likely. It takes longer to connect than the stock VZW FW does of course, but after the boot it seems fine.
I'm done testing this for now, but if anyone is wondering yeah go for a it. It seems to be fine besides a slower initial connection. Excited for CM to become stable, then I'll play with this some more.
Ariac Konrel said:
Changed my CID to SuperCID (22222222).
Got the latest Unlocked U.S. FW from the HTC Dev site (RUU EXE) and flashed it.
Flashed a Verizon radio in fastboot. (The same one used to make the actual U.S. Unlocked variant work on Verizon)
Flashed TWRP in fastboot.
Formatted my data.
It booted without issue.
Followed this guide (though, on initial boot it showed 4GLTE active BUT no bars (line through them).
After following the guide, I rebooted.
Testing functions:
Calls: Functional and no delays.
SMS: Functional and fast.
MMS: Functional and fast.
Data connection: Functional.
Behavior after reboot: Starts again with the bars crossed off, eventually comes up and working though. Works after that, calls too. Takes about 45 seconds to connect.
Thing to note: It seems as if my signal strength is lessened. Though, this could easily be placebo, weather, etc. It's 1:31AM and I've never paid attention to it before.
Network comes up as 3107 instead of Verizon Wireless.
HTC software updates seem to be broken, it gives a corrupted error. I'm locked/S-OFF, so dunno.
Final deduction: It seems to functional and all, without hiccup most likely. It takes longer to connect than the stock VZW FW does of course, but after the boot it seems fine.
I'm done testing this for now, but if anyone is wondering yeah go for a it. It seems to be fine besides a slower initial connection. Excited for CM to become stable, then I'll play with this some more.
Click to expand...
Click to collapse
I was the guinea pig for this in regards to Sprint, but you've seem to partially answer a question I had.
I know that the Verizon and US Unlocked use the same model ID, but the Sprint and internal do not. Leaves me wondering if I could just run the RUU for my Sprint phone.
Ariac Konrel said:
Changed my CID to SuperCID (22222222).
Got the latest Unlocked U.S. FW from the HTC Dev site (RUU EXE) and flashed it.
Flashed a Verizon radio in fastboot. (The same one used to make the actual U.S. Unlocked variant work on Verizon)
Flashed TWRP in fastboot.
Formatted my data.
It booted without issue.
Followed this guide (though, on initial boot it showed 4GLTE active BUT no bars (line through them).
After following the guide, I rebooted.
Testing functions:
Calls: Functional and no delays.
SMS: Functional and fast.
MMS: Functional and fast.
Data connection: Functional.
Behavior after reboot: Starts again with the bars crossed off, eventually comes up and working though. Works after that, calls too. Takes about 45 seconds to connect.
Thing to note: It seems as if my signal strength is lessened. Though, this could easily be placebo, weather, etc. It's 1:31AM and I've never paid attention to it before.
Network comes up as 3107 instead of Verizon Wireless.
HTC software updates seem to be broken, it gives a corrupted error. I'm locked/S-OFF, so dunno.
Final deduction: It seems to functional and all, without hiccup most likely. It takes longer to connect than the stock VZW FW does of course, but after the boot it seems fine.
I'm done testing this for now, but if anyone is wondering yeah go for a it. It seems to be fine besides a slower initial connection. Excited for CM to become stable, then I'll play with this some more.
Click to expand...
Click to collapse
Does your volte work ? Something you can try is flash Viper10 and select as a verizon model instead of the unlocked version, this will add get you on global mode and I think will fix your signal issues. You list your on Viper10 just dirty flash it again selecting verizon version and give it a try. If it does not help you can always just dirty flash again and go back selecting the unlocked version. Just do a back up before doing this and you will covered if you just want to restore the back up. From my experience this might help just do not try running a custom kernel for the verizon version if you converted to the unlocked as your camera may not work and keep forcing close but you can run a custom kernel for the unlocked if you converted to unlocked. My recommendation would be to run the Elite kernel as I have had really good luck with the Elite kernel on the Htc 10 and I think theirs is what I run well on my Motorola nexus 6 also.
Ariac, regarding OTA software updates on the phone, I think you get that "corrupt" message because you flashed a different radio and twrp. Might be worth flashing the original Unlocked radio/recovery back and see if it at least detects the latest update. If it does, you'll also need to remove superCID to be able to take the update.
I reflashed the RUU yesterday, removed superCID and I was able to take the OTA.
I tried flashing n910vvru2cql1 partial firmware in odin and phone info is still showing cpd1 as my bootloader.
history:
my phone was acting kinda buggy, wouldnt charge, turned off, got really hot about a year ago on a old version of RR and wasnt responding to anything usb so i threw it in a box and used one of my backups, a month ago or so, i moved some firmware files over by sdcard and flashed with twrp and it seems like it cleared up a lot of my issues.
I have been trying to get any rom past 6.0.1 on it and they just dont seem stable enough to run everyday so I found modest rom flashed that and it seemed pretty good except for the random restarts and lagg. i flashed flashpoint v4 kernel to try to clear problems up and it ran better but yet still kinda buggy so said screw it and flashed stock firmware cql1 kernel and over 2 days seems like everything cool except now im trying to get my bootloader up to CQL1 just so everything is unified and Sam Phone Info shows CPD1 for bootloader but CQL1 for pda, csc,baseband-radio
Are there any reason to upgrade bootloader since im already on 6.0.1 unlocked?
I wouldnt think so because my thoughts are its more like an efi bios/grub2/mbr which load the os and the kernel later gets lowerlevel access to the hardware????
Bottomline, I guess i would like to upgrade the bootloader, someone please clarify and help.
Thanks.
brianmilw said:
I tried flashing n910vvru2cql1 partial firmware in odin and phone info is still showing cpd1 as my bootloader.
history:
my phone was acting kinda buggy, wouldnt charge, turned off, got really hot about a year ago on a old version of RR and wasnt responding to anything usb so i threw it in a box and used one of my backups, a month ago or so, i moved some firmware files over by sdcard and flashed with twrp and it seems like it cleared up a lot of my issues.
I have been trying to get any rom past 6.0.1 on it and they just dont seem stable enough to run everyday so I found modest rom flashed that and it seemed pretty good except for the random restarts and lagg. i flashed flashpoint v4 kernel to try to clear problems up and it ran better but yet still kinda buggy so said screw it and flashed stock firmware cql1 kernel and over 2 days seems like everything cool except now im trying to get my bootloader up to CQL1 just so everything is unified and Sam Phone Info shows CPD1 for bootloader but CQL1 for pda, csc,baseband-radio
Are there any reason to upgrade bootloader since im already on 6.0.1 unlocked?
I wouldnt think so because my thoughts are its more like an efi bios/grub2/mbr which load the os and the kernel later gets lowerlevel access to the hardware????
Bottomline, I guess i would like to upgrade the bootloader, someone please clarify and help.
Thanks.
Click to expand...
Click to collapse
Sorry for responding late but in case anyone else is wondering, most partial firmwares that you see posted for our device model (even the ones posted in the international snapdragon rom threads that have Lineage, RR, and ported TW roms) do not contain the aboot.mbn file, aka bootloader. So it will not change our bootloader in anyway.
That's not say a dev or someone like myself who's just a beginner couldn't make a mistake and forget to remove it or maybe they don't know that it's supposed to be removed. So it would be best to stick with the tried and true links that have been posted of you're needing to update your modem. I know for certain the ones that have been posted by ripee, hsbadr, and me are safe, but I've never used not have heard anything negative about the other ones posted.
All that being said, you can update the SM-N910V bootloader if you'd like. Mine is updated to where it ends with CQI2 which is the penultimate update. If there is a difference between CQI2 and CPD1 (initial 6.0.1 bootloader) then it is a slight difference. Sometimes I think I just want to believe that tweaks and changes are working, especially if you put a lot of effort and time into it(which is required when you don't have much knowledge).
This was just posted recently;
VZW_NOTE4_EMMC_15_Chipset_Only_Bootloader_Unlock_U p/Dwngrade_Bootloaders_KK/LL/MM by jkruse
I haven't tried it yet but it looks much easier than the method I used, which is below;
For the folks that just like to tinker and break things....... How else you supposed to learn how to fix it?
How-To Update Your Bootloader from CPD1 to CQI2 by this fool
My P6P (on T-Mobile) was working fine for me on the November release.
I did not sideload the December release.
With the January release, I started to notice significant radio issues.
I am seeing the same issue with the February release and after taking a look, I see that the radio has NOT changed between January and February. (But is a different radio from the November update)
I would definitely like to try flashing the November radio, but my Pixel bootloader is locked and can't be unlocked since it is still carrier locked. (I am working on that.)
In the meantime, is it possible for someone to make a custom OTA sideload package with just the November radio in it for those with locked bootloaders?
The 12L radio is different. I flashed it yesterday (12L factory image) and Signal is back to normal, and switching from Wifi to LTE/5G is much better than it's ever been on my 6 Pro. but its only been 24hours, but worth a try/
Good to know, but if I don't want to go 12L... again, could someone create a custom OTA sideload package with just the radio from 12L?
If this is even possible, which I'm dubious of, you might want to think twice. With a locked bootloader, your recovery options are more limited, so if someone creates such a custom OTA zip (again, if that's even possible to work with an unlocked bootloader), and something goes seriously wrong, it might be either more difficult or impossible to recover.
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
I just wanted to add, I tried flashing a different radio in December after flashing that image before it got pulled, and my phone wouldn't boot (but my bootloader was unlocked so I was able to save it but I wouldn't try it). I suggest you unlock your bootloader and flash 12L on both slots. That's what I did yesterday. Just kind of kill 2 birds with one stone by wiping, reflashing, and using a new build/radio (3 birds I guess?)
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
It depends on how badly things went wrong. I would hope so, too, but would be a bigger gambler than someone who has the bootloader unlocked in the same situation. But of course, if you had an unlocked bootloader, you could flash only the radio.img without any customization needed. But as @TonikJDK indicates, the question is effectively moot, anyway.
TonikJDK said:
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
Click to expand...
Click to collapse
Interesting. I didn't realize that was in place (signing of the various components such as radio+recovery+bootloader+image), and that the checking was disabled as part of the bootloader being unlocked.
chp said:
and that the checking was disabled as part of the bootloader being unlocked.
Click to expand...
Click to collapse
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.
roirraW edor ehT said:
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.
Click to expand...
Click to collapse
Ah yes, you're right. I was overthinking it. The sideload OTA does have a cert, so without the private key, we wouldn't be able to create a new cert to match the custom OTA contents.
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
NippleSauce said:
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
Click to expand...
Click to collapse
Thanks. I've been with Android and Pixel/Nexus for a long time, and other than needing to brush up, I'm still familiar with the ins-and-outs to flashing, etc.
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Since my radio issues started with the January update, I was hoping the February update would fix things. At first it did seem better, but then the poor behavior returned. And when I realized that the radio was unchanged in February from January, that explained things.
chp said:
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Click to expand...
Click to collapse
I feel ya. That's partially why I started buying my phones from the company that makes them (and also because my phone carrier stopped offering any interesting upgrades after being with them for a few years lol). But supposedly, a quick text chat with a T-Mo representative via the T-Mobile app can get your device carrier unlocked via the SIM card if you're polite with the whole thing and ask the right questions. I'm not sure if anything specific needs to be asked or stated, but you could always give that a shot. I just quickly skimmed through a post from someone who did that the other day but I didn't give it too much thought since my device is factory unlocked.
But I wish you the best of luck with your phone service!
Hey all,
I just got my 9 Pro. Unfortunately I had to get it thru T-Mobile. That last couple OnePlus devices I have always converted them to the Global firmware.
This go around I am wondering if it is worth it. Are there any benefits aside from de-bloating?
Looking for some opinions to help me make my decision before I reset and go thru the process of setting up my phone again.
And yes, the SIM is unlocked already, and I have my unlock token to unlock my bootloader.
Fatmonk8 said:
Hey all,
I just got my 9 Pro. Unfortunately I had to get it thru T-Mobile. That last couple OnePlus devices I have always converted them to the Global firmware.
This go around I am wondering if it is worth it. Are there any benefits aside from de-bloating?
Looking for some opinions to help me make my decision before I reset and go thru the process of setting up my phone again.
And yes, the SIM is unlocked already, and I have my unlock token to unlock my bootloader.
Click to expand...
Click to collapse
TMobile 9 Pro user here. Had the 9 as well. Both converted. Quick question without seeming cocky, you mentioned you converted your old OP devices in the past, why did you convert them?
TheKnux said:
TMobile 9 Pro user here. Had the 9 as well. Both converted. Quick question without seeming cocky, you mentioned you converted your old OP devices in the past, why did you convert them?
Click to expand...
Click to collapse
To de-bloat.
But if that's the only positive this go around then it's probably not worth me doing since I have been de-bloating more with ADB lately. But if others have any input on other benefits then I may do it again.
Well my opinion, updates. I'm still on OOS11 but that's by choice. For one,even though I can't change the stock oos bootanimation, it's still better than T-Mobile stock. Second, a lot of support with custom roms, kernels, and mods don't give support to people who are on TMobile firmware for some reason (don't ask, don't know lol).
Third, it's a lot easier to cross-flash firmwares and downgrade, especially with an unlocked bootloader. I was able to go from OOS12 beta to stable, then to custom w/kernel, then to COS 12.1, then back to OOS11 with one single MSM. To me, it just seems all around easier. There's more reasons, I'm just in lunch so I figured give you my two cents.
Right now my setup is OOS 11.2.10.10_DA with latest alpha Magisk using the latest Shamiko with Zygisk with Hide off, fully passing SafetyNet. Arter R12 with latest TWRP.
TheKnux said:
Well my opinion, updates. I'm still on OOS11 but that's by choice. For one,even though I can't change the stock oos bootanimation, it's still better than T-Mobile stock. Second, a lot of support with custom roms, kernels, and mods don't give support to people who are on TMobile firmware for some reason (don't ask, don't know lol).
Third, it's a lot easier to cross-flash firmwares and downgrade, especially with an unlocked bootloader. I was able to go from OOS12 beta to stable, then to custom w/kernel, then to COS 12.1, then back to OOS11 with one single MSM. To me, it just seems all around easier. There's more reasons, I'm just in lunch so I figured give you my two cents.
Right now my setup is OOS 11.2.10.10_DA with latest alpha Magisk using the latest Shamiko with Zygisk with Hide off, fully passing SafetyNet. Arter R12 with latest TWRP.
Click to expand...
Click to collapse
I appreciate you input, and that did help me make a decision.
What was your method to convert your T-Mobile 9 Pro? Because every method I tried ended up bricking my phone. It would always be when I had to flash the modem when it would brick. Followed the guide on here and other sites multiple time and always the same.
Guess it's not like old OnePlus where we can just flash different firmware willy nilly.
Fatmonk8 said:
I appreciate you input, and that did help me make a decision.
What was your method to convert your T-Mobile 9 Pro? Because every method I tried ended up bricking my phone. It would always be when I had to flash the modem when it would brick. Followed the guide on here and other sites multiple time and always the same.
Guess it's not like old OnePlus where we can just flash different firmware willy nilly.
Click to expand...
Click to collapse
So I spent a week figuring this out. I realized a few days ago that I mistakenly flashed the Indian firmware for the OnePlus 9 PRO. I have the regular 9. I tried to flash every other msm I could find and download. Nothing seems to work except the Indian OnePlus 9 PRO msm... Problem is, the camera, flash and fingerprint scanner didn't work. I was able to toggle the unlock oem button by running an adb command line then I did oem unlock in fastboot. After that, I followed the instructions for installing StagOs 12.1, which involves installing lineage recovery then flashed the rom. Everything works flawlessly! Love this rom.
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
SmartMart92 said:
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
Click to expand...
Click to collapse
My TMo OP9P LE2127 had updated to OOS12 before I had a chance to root it. I hadn't read enough about it to worry about trying to block the update. Well, I hated OOS12 and I eventually downgraded back to Stock OOS11 and then converted it EU with the MSM tool. Currently running a rooted OOS11.2.10.10 on both slots.
Not once did I have to touch the modem and my 5G works just fine. Everything worked out of the box (aka conversion MSM). My phone is even still SIM locked. I believe others have experienced the same thing with a LE2127 that updated to the stock TMo OOS12 firmware. The modem seems to stick after that upgrade, even after downgrading it back to OOS11.
I've blocked my phone from manually checking for updates and I'm perfectly happy with my phone for the time being. That said, I have not tried updating my phone to any EU versions of OOS12 (C.48 being the latest, I think?).
So, that's my experience, but your mileage may vary.
SmartMart92 said:
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
Click to expand...
Click to collapse
In order to get the modem working in A12, you have to have root and flash a Magisk module that fixes your build.prop. Unfortunately, your need to be unrooted prevents that from happening.
If you're OK with rooting temporarily, you could modify your build.prop to have "ro.vendor.oplus.radio.multisim.config=ssss" after flashing EU, then unroot afterwards by flashing stock boot.img.
razercortex said:
In order to get the modem working in A12, you have to have root and flash a Magisk module that fixes your build.prop. Unfortunately, your need to be unrooted prevents that from happening.
If you're OK with rooting temporarily, you could modify your build.prop to have "ro.vendor.oplus.radio.multisim.config=ssss" after flashing EU, then unroot afterwards by flashing stock boot.img.
Click to expand...
Click to collapse
Yeah, that could work. Does build.prop need to be updated after each OTA update?
SmartMart92 said:
Yeah, that could work. Does build.prop need to be updated after each OTA update?
Click to expand...
Click to collapse
Shouldn't need to be updated.
Also, you could try unlocking bootloader, rooting, modifying build.prop, unrooting, then relocking bootloader if you're ok with testing. It may/may not work. If it works, then you don't need to modify ever again, at least until a future update touches that file.
If I have no sims detected am I able to flash something to regain sim detection and data?