This may seem like a weird question, but is there is way to convert back to the T-Mobile firmware? Mostly I would like to avoid having to install the modem manually with every update. If this is no longer the case and there is a permanent modem solution then that's all I would need. I found a lemonade tar.gz for the T-Mobile firmware supposedly, however, I don't know how to make that a installable ROM. The link is a github link here, OnePlus 9 Pro Firmware. I've never swapped off of the carrier firmware and had to manually reinstall the modem with every update before. The most annoying part of that for me would be keeping the bootloader unlocked. That's only a minor issue for me as I play Pokemon Go and unlocked bootloader/root can cause issues with that. I don't generally tweak my phones much anymore. I prefer the non carrier ROM to have more current updates. To recap, is it possible to either go back to T-Mobile ROM or is a permanent modem fix for the conversion?
MSM is the easiest way. Just use the MSM tool for LE2127 and you'll be on your way.
I have a flash-all script that you put in a fastboot flashable stock rom zip, and it'll make it so the radio (modem) persists through OTA's. Just gotta dig around for it and see what I did with it.
Thank you both. If I could get back to T-Mobile firmware then swap back to global again that would be great. I think I may be up the proverbial creek though. In my search I came across what seems like an older thread first and I used the India MSM to flip to global. This unfortunately means the T-Mobile MSM is unable to flash to my phone as it sees it as an India phone. I found the other global MSM, and I am able to see the Target directory and choose O2, however, the MSM fails to download. Param Preload error, device not match image.
I've made peace with not being able to get back to T-Mobile firmware, I may have to research the persistent modem more for a fix that will work with India. Is there a modem install for OOS12 that doesn't brick the phone? I use the ones I have from the T-Mobile files, and they work fine for OOS11, but they immediately brick 12 after install.
Bumping this post to ask again about the modem for Android 12. Also, my Bluetooth audio cuts in and out, it's very crackly. This only started after jumping from the T-Mobile ROM.
Edit: Also the voicemail doesn't show in the Phone app. Voicemail service is listed as "Your Carrier" and I can't do anything with it. There are no options that I can toggle at all.
I was looking at the repo of builds for the 9 Pro. I see there is an Android S for all regions in there. Could that possibly change the region of the firmware to, more or less, not associated anywhere and allow a restore to the T-Mobile firmware?
I'm not entirely sure how, but I did manage to get off of the India firmware and onto the EU firmware. At least from there I should be able to get the persistent modem. Working on that process now.
All right, everything has been running fine on the EU firmware, the only thing I'm still having an issue with is Bluetooth. Not connectivity at all, just on phone calls and in one vehicle for audio. It's incredibly choppy. It didn't used to be an issue, it only started after I left the T-Mobile firmware. Is there something I need to flash for the Bluetooth or a setting I'm missing?
Related
Hello,
After some troubles I've converted my S-OFF x.xx.410.xx phone to a dev edition 2 weeks ago by reading a lot on this forum. I believe I did the following:
- flash 0PJAIMG nougat.zip from bootloader mode / SD
- run 4.14.617.6 RUU after flash
This worked for perfectly for a time.
On 1-1-2017 I got the 4.19.617.1 OTA notification which I accepted as I did not modify the system in any way. OTA completed succesfully however after OTA the phone lost mobile reception. In Android IMEI was not visible. In fastboot I saw IMEI with "fastboot getvar all".
Re-flashing RUU 4.14.617.6 worked to regain mobile reception however OTA nofication would of course still appear. Today I retried but with the same results -- no mobile reception after OTA.
To confirm with the new RUU available I ran the 4.19.617.1 RUU to re-flash phone and indeed no signal at all.
Then I ran the 4.14.617.6 RUU and signal again.
I read this in the FAQ:
"Q1: Everytime I flash a custom rom I lose my IMEI, my mobile reception and my phone stops recognizing my sim card. What's the reason for this?
A: You probably flashed a custom rom that is based on firmware 3.35.x although the firmware of your phone is 3.y (with y being any other number than 35). The boot image of 3.35.x based roms is not compatible with your firmware version. The solution of the problem depends on the question whether you are trying to install a Sense-based rom (like ICE or ViperOneM9) or a non-Sense-based rom (like CM): For Sense-based roms you just need to re-flash the stock boot image of your current firmware version."
This seems like my problem except I run RUU directly from HTC. Any idea on what I can do to accept OTA / reflash phone with 4.19.617.1 RUU ?
Thank you!
Was the phone rooted at the time of accepting the ota?.
There is a thread somewhere that explains how to fix the no signal issue on nougat dev edition.
I don't see the point in risking a brick for a beta firmware (dev edition is the beta to carrier versions) which is not necessarily a better firmware.
Also, make sure the rom and firmware you flash IS GSM and NOT CDMA.
Beamed in by telepathy.
@Fritti: The error that is described in the FAQ only appears if you flash a custom rom while using an incompatible firmware. You've used a RUU and are using the stock rom that got flashed by the RUU. That means firmware and rom are matching. Unfortunately, that means that I have no clue why you're facing this issue. There's no reason why you should lose your reception since all GSM versions are more or less the same if you compare their hardware. As far as I know only the LTE bands of the GSM versions differ.
shivadow said:
Was the phone rooted at the time of accepting the ota?.
There is a thread somewhere that explains how to fix the no signal issue on nougat dev edition.
I don't see the point in risking a brick for a beta firmware (dev edition is the beta to carrier versions) which is not necessarily a better firmware.
Also, make sure the rom and firmware you flash IS GSM and NOT CDMA.
Beamed in by telepathy.
Click to expand...
Click to collapse
If the phone was rooted the OTA wouldn't have been installable.
And please stop posting things that aren't true. The dev firmware is not a beta version. It's the US equivalent of the European 401 firmware or the Asian 708, 709 or 710 firmware. Beta firmwares look like this one: 2.10.401.180. They have three numbers behind the last dot. If you compare the 3.x firmware of SKU 401 and 617 you'll notice that 3.35.401.12 and 3.35.617.12 are almost exactly the same except for some contintent-specific tweaks.
It is true that the dev edition is not necessarily better than the 401 one. However, it's up to every single user to choose whether he or she wants to wait until the latest update gets released for his/her SKU or whether they want to convert to the dev edition which receives all updates first (in case of the M9).
Flippy498 said:
@Fritti: The error that is described in the FAQ only appears if you flash a custom rom while using an incompatible firmware. You're used a RUU and are using the stock rom that got flashed by the RUU. That means firmware and rom are matching.
Click to expand...
Click to collapse
Yes, that's what I thought.
Unfortunately, that means that I have no clue why you're facing this issue. There's no reason why you should lose your reception since all GSM versions are more or less the same if you compare their hardware. As far as I know only the LTE bands of the GSM versions differ.
Click to expand...
Click to collapse
Exactly. I don't understand either. Something get's flashed by the 4.19 RUU that messes up the IMEI detection? Is it possible to extract system.img from 4.19 RUU and just flash that to check whether that works?
If the phone was rooted the OTA wouldn't have been installable.
Click to expand...
Click to collapse
Indeed, phone was not rooted. I used 4.14 RUU and then no other flashes/mods.
And to be clear, for now it seems that I can repeat this -- run 4.19 RUU and no signal, run 4.14 RUU and signal again. If there is some radio partition and/or radio data partition that I can dump to check hex diffs I could try.
Fritti said:
Yes, that's what I thought.
Exactly. I don't understand either. Something get's flashed by the 4.19 RUU that messes up the IMEI detection? Is it possible to extract system.img from 4.19 RUU and just flash that to check whether that works?
Indeed, phone was not rooted. I used 4.14 RUU and then no other flashes/mods.
And to be clear, for now it seems that I can repeat this -- run 4.19 RUU and no signal, run 4.14 RUU and signal again. If there is some radio partition and/or radio data partition that I can dump to check hex diffs I could try.
Click to expand...
Click to collapse
You could use the decryption tool that is linked in the readme thread for extracting the system image and the firmware files.
Hi,
I'm facing the same issue - I think. I'm currently using a 4.14 original RUU ROM from HTC without modification.
When I accept the 4.19 OTA I lose connectivity in a most peculiar way: there are still signal bars and the phone confirms a LTE connection.
But there are no more APN options and no data. Also when I place a call the phone claims I'm out of service area.
One other thing I noticed is that the dialer shows a different number format when entering a phone number. With 4.14 I have the normal DUtch standard for dashes and area codes. With 4.19 I have a US standard. Could it be that the phone thinks I'm in the US and would a edit to the build.prop help?
I hope someone has some advice.
Gawain1986 said:
Hi,
I'm facing the same issue - I think. I'm currently using a 4.14 original RUU ROM from HTC without modification.
When I accept the 4.19 OTA I lose connectivity in a most peculiar way: there are still signal bars and the phone confirms a LTE connection.
But there are no more APN options and no data. Also when I place a call the phone claims I'm out of service area.
One other thing I noticed is that the dialer shows a different number format when entering a phone number. With 4.14 I have the normal DUtch standard for dashes and area codes. With 4.19 I have a US standard. Could it be that the phone thinks I'm in the US and would a edit to the build.prop help?
I hope someone has some advice.
Click to expand...
Click to collapse
Yes, that sounds like the same issue. You can actually edit the settings in the phone to disable the US international prefix. However it does not help for the out of service issue.
I have not yet had the time to try and flash only the firmware / recovery / system from 4.19, I will report back once I have tried.
Fritti said:
Yes, that sounds like the same issue. You can actually edit the settings in the phone to disable the US international prefix. However it does not help for the out of service issue.
I have not yet had the time to try and flash only the firmware / recovery / system from 4.19, I will report back once I have tried.
Click to expand...
Click to collapse
I have some news. I took the 4.19 No-Wipe firmware and flashed it by putting it on my SD card as 0PJAIMG.zip. It flashed and now I'm working on the 4.14 ROM with 4.19 firmware. All is working wel, most notibly making calls and using data.
This leads me to believe there is something in the Kernel/ROM of 4.19 that breaks our calling and data.
Does anybody have any other ideas to make 4.19 work?
The plot thickens .
I installed ICE ROM 4.19 after flashing firmware 4.19 and I had the same problem back, out of service area.
So I started comparing the build.prop files in the 4.14 ROM from HTC and the 4.19 ICE ROM. Then I changes a few lines to these values and I was able to call:
ro.ril.hsxpa=4
ro.ril.hsdpa.category=14
ro.ril.hsupa.category=6
ro.aa.rid=115
To get data (and be able to log in to a google account) I did another thing. I used the dialer to call *#*#4636#*#* and set the phone to WCDMA preferred and I had data.
The only thing left is to be able to use LTE/4G but that's for another time, I can finally use my phone on this firmware!
Gawain1986 said:
The plot thickens .
I used the dialer to call *#*#4636#*#* and set the phone to WCDMA preferred and I had data.
The only thing left is to be able to use LTE/4G but that's for another time, I can finally use my phone on this firmware!
Click to expand...
Click to collapse
Now try switching it back to LTE/WCDMA/GSM.
I had the same with S.Rom and after getting it to connect the way you did, switching back to auto gave me 4G again
bonesy said:
Now try switching it back to LTE/WCDMA/GSM.
I had the same with S.Rom and after getting it to connect the way you did, switching back to auto gave me 4G again
Click to expand...
Click to collapse
No such luck for me... As soon as my phone sees LTE, the phone force closes and aftter I have no Data and I'm out of service area again.
So I know this is nearly a necro but I wanted to give an update that I cannot try this anymore -- shortly after the failures started my phone got stuck in a bootloop. This had to be hardware error as it simply started one morning while I did not change anything. The Vodafone shop I brought it to agreed and send my unit in for (warranty!) repairs. I've since got it back with Android 7.0 on version 4.28.401.3, so there is no need for me to switch to dev edition now. I cannot say whether the signal issues were a symptom or a cause for my unit to fail.
Hoping that Gawain1986 has fixed his issues as well!
Context: I have a Verizon branded Note 10+, trying to use a Mint mobile connection. Wi-fi calling doesn't work, connection speed is atrocious, but everything works swimmingly out of the box when I put the same SIM in my unlocked Pixel. I am quite sure my Note 10+ is unlocked because it is fully paid off and well past the 60 day period, and more importantly because the Mint SIM DOES work in it, just very poorly.
So it's quite evident that I have to flash TMB firmware to get a serviceable reception.
Trying to follow the steps outlined here - https://forum.xda-developers.com/galaxy-note-10+/how-to/n975u-n975u1-firmware-links-t3957648
Based on what I understand I have to flash unbranded firmware first and then my desired carrier firmware which is T-Mobile. Can someone please help me understand what firmware I should be looking for?
My current baseband version N975USQU3CTE7.
My question is when downloading through Frija, should I be looking for SM-N975U1 (VZW) firmware or SM-N975U1 (XAA) firmware for the first step? Or can I use either?
I have moved a Note 10+ from it's original T-Mobile firmware to Verizon and then back, so hopefully, I can explain this process easier then that original bloody guide (which I pulled my own hair out over). To perform the operation ONE WAY, you must have an activated SIM card on the target carrier.
First thing you want to do is perform a full backup for all of your files, as they may get wiped during this process (and more than likely will). I used Samsung's backup to an SDCard I inserted into mine. Remove the SIM Card from the phone before starting this process. You may also wish to remove your Samsung account and any security codes/methods you have when flashing. That might be too much, but I always do it just encase things go wrong for some reason.
Obtain the newest firmwares using SamFirm (currently 0.5.0). If you cannot find a Region in the drop-down listing, just type the three letter code manually into the region box to search for it (this is how I obtained the USC firmware for the SM-N975U1). You want the universal SM-N975U1 Firmware (USC), and the target SM-N975U T-Mobile firmware or whatever other carrier you want to target(yes, U only).
At the time of me typing this, the SM-N975U1 USC firmware is N975U1UES4CTF2 dated 07/06/2020, and the SM-N975U TMB firmware is newer, being N975USQS4CTF3 07/27/2020. It is fine that the TMobile firmware is newer, just realize that flashing FORWARD to newer firmware works, but flashing firmware BACKWARDS is impossible. sammobile[DOT]com has a list of firmwares with PDA and CSC, so you can confirm there what firmware codes are newer then others. (I don't recommend downloading roms from them, unless you feel like shelling out money! I did have to use this site to get the non-U VZW firmware) This, in particular, makes it a pain to flash TO Verizon, as their firmware is typically a month behind everyone else. Ideally, you want the baseband versions of all of the ROM's to match perfectly, but this can be difficult to do as they are always changing.
The last time I performed this, which was only a few months ago before selling one of my Note 10 Plus's, I used Odin3.13.3 3B PatcheD.
Use Oden to flash the U1 USC firmware. Start the phone up with airplane mode off and no sim card. Insert the SimCard and you should see a popup that says "reboot to apply new carrier settings." Reboot the phone and ensure that things are working okay at that point. If you did not see this message, shut down the phone with no sim card and attempt again until you see the message. If you do not see this message, the carrier settings will not apply and you will not be able to flash the target SM-N975U firmware. You can verify this worked correctly by navigating to Settings=>Software Information=>Service provider SW ver. You should see something like "VZW/VZW/TMB" in your particular case. The first two will always be the original hardware's carrier, and the last one should be your target carrier to proceed.
After ensuring you have the correct carrier settings, flash the target firmware of your choice. Using Odin. It is normally important to flash the HOME CSC to get all of the carrier specific stuff, this may include wifi calling settings and software, but I am unsure (this is the main reason you backup the phone). This is the step that will clean wipe your phone in my experience.
To anyone later reading this, from the research I did when I first did this months ago... note that switching the carrier firmware may not make all of that carriers features work. I remember reading that people still could not get AT&T Wifi calling to work, even after contacting AT&T and getting the phone put on the wifi calling whitelist. I don't think Verizon and T-Mobile have those particular issues.
If you ever want to flash the phone back to it's original firmware for any reason, you MUST obtain a SIMCard from that carrier, otherwise you will be stuck!
TheXev said:
I have moved a Note 10+ from it's original T-Mobile firmware to Verizon and then back, so hopefully, I can explain this process easier then that original bloody guide (which I pulled my own hair out over). To perform the operation ONE WAY, you must have an activated SIM card on the target carrier.
First thing you want to do is perform a full backup for all of your files, as they may get wiped during this process (and more than likely will). I used Samsung's backup to an SDCard I inserted into mine. Remove the SIM Card from the phone before starting this process. You may also wish to remove your Samsung account and any security codes/methods you have when flashing. That might be too much, but I always do it just encase things go wrong for some reason.
Obtain the newest firmwares using SamFirm (currently 0.5.0). If you cannot find a Region in the drop-down listing, just type the three letter code manually into the region box to search for it (this is how I obtained the USC firmware for the SM-N975U1). You want the universal SM-N975U1 Firmware (USC), and the target SM-N975U T-Mobile firmware or whatever other carrier you want to target(yes, U only).
At the time of me typing this, the SM-N975U1 USC firmware is N975U1UES4CTF2 dated 07/06/2020, and the SM-N975U TMB firmware is newer, being N975USQS4CTF3 07/27/2020. It is fine that the TMobile firmware is newer, just realize that flashing FORWARD to newer firmware works, but flashing firmware BACKWARDS is impossible. sammobile[DOT]com has a list of firmwares with PDA and CSC, so you can confirm there what firmware codes are newer then others. (I don't recommend downloading roms from them, unless you feel like shelling out money! I did have to use this site to get the non-U VZW firmware) This, in particular, makes it a pain to flash TO Verizon, as their firmware is typically a month behind everyone else. Ideally, you want the baseband versions of all of the ROM's to match perfectly, but this can be difficult to do as they are always changing.
The last time I performed this, which was only a few months ago before selling one of my Note 10 Plus's, I used Odin3.13.3 3B PatcheD.
Use Oden to flash the U1 USC firmware. Start the phone up with airplane mode off and no sim card. Insert the SimCard and you should see a popup that says "reboot to apply new carrier settings." Reboot the phone and ensure that things are working okay at that point. If you did not see this message, shut down the phone with no sim card and attempt again until you see the message. If you do not see this message, the carrier settings will not apply and you will not be able to flash the target SM-N975U firmware. You can verify this worked correctly by navigating to Settings=>Software Information=>Service provider SW ver. You should see something like "VZW/VZW/TMB" in your particular case. The first two will always be the original hardware's carrier, and the last one should be your target carrier to proceed.
After ensuring you have the correct carrier settings, flash the target firmware of your choice. Using Odin. It is normally important to flash the HOME CSC to get all of the carrier specific stuff, this may include wifi calling settings and software, but I am unsure (this is the main reason you backup the phone). This is the step that will clean wipe your phone in my experience.
To anyone later reading this, from the research I did when I first did this months ago... note that switching the carrier firmware may not make all of that carriers features work. I remember reading that people still could not get AT&T Wifi calling to work, even after contacting AT&T and getting the phone put on the wifi calling whitelist. I don't think Verizon and T-Mobile have those particular issues.
If you ever want to flash the phone back to it's original firmware for any reason, you MUST obtain a SIMCard from that carrier, otherwise you will be stuck!
Click to expand...
Click to collapse
To anyone reading this in future, I followed this guide to the letter and worked flawlessly for me..every feature that I wanted now works without any additional configuration..signal quality has improved drastically..
Thanks for taking the time to write this..took me a couple of days to set everything up and prepare..I am glad I didn't rush it
Hello, I have a T-Mobile HD1907. I unlocked the bootloader and used the pixel experience ROM. I had issues with the microphone not working over calls so I used MSM tool to put it back to its original locked state. It worked well and the phone is back to stock. Unfortunately the phone will not OTA update to android 11. Specifically the update 11.0.1.5.HD63CB. The update will start downloading for about 1 sec and then instantly pause. am having the same issue as described here https://forums.oneplus.com/threads/oneplus-7t-fails-on-system-update.1162696/ however I am not eligible for a phone replacement.
If anyone can help me manually update the phone (perhaps using fastbootd to manually flash it?) it'd be greatly appreciated.
EDIT: have also used oxygen updater app, it doesn't work as I have the t-mobile variant
EDIT2: also when I use the newer MSM tool (for android 11 tmobile) I get "param preload" and "No valid trg ID"
Fixed this by flashing
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/T-Mobile_HD63CB/Q/OnePlus_7T_T-Mobile_OxygenOS_10.0.3.zip
then
https://onepluscommunityserver.com/...CB/Q/OnePlus_7T_T-Mobile_OxygenOS_10.0.13.zip
and then finally
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/T-Mobile_HD63CB/R/OnePlus_7T_T-Mobile_OxygenOS_11.0.1.5.zip
I guess u cant skip versions. sorry for making a thread. hopefully this helps someone else
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?
I always flash global image instead of Verizon due to bloat ware and stuff.. I did have a question would it be worth grabbing the Verizon radio images and flashing them as I'm on the Verizon network? Also do you flash them with adb or is there another method? So used to having TWRP.. Much appreciated.
I never flash the VZW image......but you can certainly try the radio as you suggest. Normally, I never see any difference, but curious if others see some....the radio is different in the current VZW image.
You would do "fastboot flash radio radio_imagefile_here"
stalls said:
I always flash global image instead of Verizon due to bloat ware and stuff.. I did have a question would it be worth grabbing the Verizon radio images and flashing them as I'm on the Verizon network? Also do you flash them with adb or is there another method? So used to having TWRP.. Much appreciated.
Click to expand...
Click to collapse
What bloatware (and stuff) are you referring to regarding the VZW image?
stalls said:
I always flash global image instead of Verizon due to bloat ware and stuff.. I did have a question would it be worth grabbing the Verizon radio images and flashing them as I'm on the Verizon network? Also do you flash them with adb or is there another method? So used to having TWRP.. Much appreciated.
Click to expand...
Click to collapse
The Verizon firmware isn't a "Verizon owned" firmware, it's just a variant that Google has released because when Google sent out the "global" firmware for testing Verizon reported issues with it, and it was too late to incorporate the fixes and send out another firmware to all carriers for testing.
The variants in firmwares have nothing changed in them other than the radio/modem/network files and maybe app versions if the variant had to be built at a later date and picked up a new app version in the build process. The firmwares are exactly the same. They don't come with any additional bloatware, because Verizon's networking specific apps are actually already included in the base firmware and are enabled/disabled on the presence of a Verizon SIM. The bloatware you are delivered is when setting up the phone and the setup wizard will offer the carrier bloatware to be installed depending on the carrier of the SIM.
Run the firmware designated for your carrier. You might have service issues if you don't, but it will run almost the same.
I ran the Verizon variant on my phone with T-Mobile and I got service just fine, however it appears that Verizon wanted the scaling for network strength to be changed because it reported 0 bars even though I had service. It also wanted to try really hard to latch onto mmWave, so it appears that Verizon wanted that and potentially more changed.
Just run the online flash tool from Google to get updated, or follow the tutorial threads in the help section.
cmh714 said:
I never flash the VZW image......but you can certainly try the radio as you suggest. Normally, I never see any difference, but curious if others see some....the radio is different in the current VZW image.
You would do "fastboot flash radio radio_imagefile_here"
Click to expand...
Click to collapse
You'll have to flash more. There's also the modem inside the image and there are also APNs and other files for networks on the system image or vendor image too, so it's really just best to take the whole firmware.
Ok so I should just flash over the global and so as usual then right?
stalls said:
Ok so I should just flash over the global and so as usual then right?
Click to expand...
Click to collapse
You mean flash the Verizon firmware over the global firmware you already have on your phone? Yes, it will be fine. You don't need to wipe the phone.