Changing CSC to Verizon doesn't provide you all features? Do you really need to flash firmware? Just curious. What additional features does one get by flashing firmware that you wouldn't get by changing CSC?Weird. Never seen that screen before. Idk but I flashed Verizon firmware on my xaa to try and get certain features, also flashed back to unlocked firmware with no problem. I'm also not rooted tho, so idk.
RCS does not work in samsung messages on unlocked Verizon no matter what you do. I had also followed another thread to get RCS working but it turns out it's a Verizon thing that is blocked on unlocked USA phones. Flashing Verizon firmware gave me that feature, but I eventually went back to XAA because I just use Google messages now.Changing CSC to Verizon doesn't provide you all features? Do you really need to flash firmware? Just curious. What additional features does one get by flashing firmware that you wouldn't get by changing CSC?
Or Is it because u had XAA firmware?
FYI i have unlocked Tmobile branded Note20U and then when i moved to ATT, i changed CSC to ATT and get all features, no need to flash ATT firmware unless im missing features im not aware of.
I can attest to that , briked mine 5 timesAfter unsuccessfully trying to root latest DUB5 firmware form T-mobile with Magisk - found a solution:
T-Mobile apperently locks vbmeta to official state only in latest firmwares.
1. Patch original T-mobile AP with Magisk.
2. Replace BL_N986USQU1DUB5_CL20936746_QB38027387_REV00_user_low_ship_MULTI_CERT.tar.md5 with other BL image from Android 11 (Latest XAA will work).
3. If you do not repalce BL file, you will get an error "vbmeta_fail" and your phone will get locked.
The t mobile euicc is looking for 30.0.6 version before it will install and run correctly.
I can't mount it as editable to look for just 30,
Any ideas, unpack on my laptop and edit that way...
If I put it to look for 29 and up it should work. I got it to back door install but it's,not writing profile cause version it's looking for ain't there yet
looking into the tmb euicc file i got from you, you know how thye look for version of android to run and install on, this one is looking for 30.0.6 to install on, open up the installer package and in the android manifest, in complie version sdk it says 30.0.6 for version name r.0x1 android:versionName "30.0.6" like its looking for highr version than is installed as om sdk 30What exactly are you trying to mount? What is 30.0.6? Verison of euiccservice?
looking into the tmb euicc file i got from you, you know how thye look for version of android to run and install on, this one is looking for 30.0.6 to install on, open up the installer package and in the android manifest, in complie version sdk it says 30.0.6 for version name r.0x1 android:versionName "30.0.6" like its looking for highr version than is installed as om sdk 30
i found a retorfit installer inside the package that writes the kotlin to metadada but looking at install log it freezes after it sees im only on sdk 30...was thinkingif i could modify the version it was looking for to 29 and up that it might install correctly maybe 30 and up because file system is way different, i cant edit the file though , im going to try to open on my laptop and see if i can modify...but thats project for tommorow...theyre laying foundation to enable but this should have been back in 10 like they promised, i got it halfway working and it found and added my plan but wont make or recive callss as it cant fine imei for esim ......
Ok ive seen a lot about the esim but what about the dual sim option? or does the snapdragon model not have the slot for that? I know it doesnt com with the dual sim tray and its obviously not as easy to just get a new tray and pop your sims in. But is it a software or hardware issue for it?
A dual SIM tray will fit, however there are no SIM contacts for the second slot. Only contacts for an SD Card.I flashed AP from 9860 into 986U1 and it does appear with 2 physical IMEI numbers. BUT the SIM is not recognized in secondary slot (I bought a tray with DUAL-SIM from Exynos verision) so no LUCK.
What carrier/ country are you in. I can get you CA up to 3dl and carrier features by modification of the sx55 fusion modem file.
This is my map carrier list, bri chc and tgy only have 4 options by default. All the same. But I can add NA SA and some euro carriers with simple copy and paste inside mdm files.
Pretty sure it's for google fiSo, I've read in several places the US N20U has eSIM. I see the eSIM control app is in stalled. But that's all I see of it. Even an article here on XDA says all N20Us have eSIM except Japan, Korea and China. Can anyone confirm? And if so, how? (I've never used eSIM)
Making changes to cscfeatures alone wont enable eSIM. You need working euiccservice working propertly in priv app, which still wont install properly. You need to enable Sim card manager in build.prop and most important thing - EID would still show none in status of the phone. You need a working EID in order to get eSIM to work.Hey folks,
I've decoded the cscfeatures*.xml files and added the necessary change there *and* have also created a quick magisk module to splice in the EuiccService.apk file to /system/priv-app (will upload shortly, it's on another device) but here's my (likely rather simple to solve) question:
How can I force eSIM options to appear in the Settings app to actually make use of this mod? I have both an exynos N20 Ultra and a Snapdragon N20 Ultra (SM-N9860) - this is the last piece of the puzzle preventing me from migrating to the Snapdragon phone entirely so would love to solve it. Some report success with the US variant but wondering if anyone has got this working with the HK variant (N9860)?
I'd greatly appreciate any help!