Is there any new instruction how to force VoLTE and VoWifi to work on PIXEL3?
Features works great on S9, SIM card is provisioned. The IMS options are blacked out on PIXEL.
Does any Custom ROM forces the feature to work even if carrier says that they don't officialy support it?
If it is just that your provider does not allow this service on Pixel you could try MagiskHide Props Config module to change device fingerprint to match a phone that is supported by your carrier. Not sure if it will word, but worth a shot.
wangdaning said:
If it is just that your provider does not allow this service on Pixel you could try MagiskHide Props Config module to change device fingerprint to match a phone that is supported by your carrier. Not sure if it will word, but worth a shot.
Click to expand...
Click to collapse
Carrier says that the issue is not on their side, they claim that they have enabled services. I checked on S10 with the same SIM card, both VoLTE and VoWifi works without issues.
The other thing is that I don't want to dive deep into changing factory images to force the features. I would need to unlock bootloader and root phone.
Until now Google does everything just to avoid questions and providing support for modem issues for other carriers than US.
mxtuu222 said:
Carrier says that the issue is not on their side, they claim that they have enabled services. I checked on S10 with the same SIM card, both VoLTE and VoWifi works without issues.
The other thing is that I don't want to dive deep into changing factory images to force the features. I would need to unlock bootloader and root phone.
Until now Google does everything just to avoid questions and providing support for modem issues for other carriers than US.
Click to expand...
Click to collapse
It might have something to do with the modem files in the vendor partition, we have that issue here in China. Only way to fix that is to be rooted and systemlessly make the phone read the files correctly. Custom roms cannot change the vendor.img.
wangdaning said:
It might have something to do with the modem files in the vendor partition, we have that issue here in China. Only way to fix that is to be rooted and systemlessly make the phone read the files correctly. Custom roms cannot change the vendor.img.
Click to expand...
Click to collapse
;/ so probably there is no easy workaround. Rooting and modem modification makes it too complex. Especially that on Android Q there is a problem with USB debugging mode for Qualcomm in fastboot
PIXEL2: [GUIDE]Enable VoLTE for unsupported carriers
mxtuu222 said:
;/ so probably there is no easy workaround. Rooting and modem modification makes it too complex. Especially that on Android Q there is a problem with USB debugging mode for Qualcomm in fastboot
PIXEL2: [GUIDE]Enable VoLTE for unsupported carriers
Click to expand...
Click to collapse
Rooting is not really dangerous, and the modem modification makes no real changes. It is systemless changes, which means no files are actually modified. What carrier do you use, odd that a US carrier would not be supported natively by google.
wangdaning said:
Rooting is not really dangerous, and the modem modification makes no real changes. It is systemless changes, which means no files are actually modified. What carrier do you use, odd that a US carrier would not be supported natively by google.
Click to expand...
Click to collapse
I need to have an option for carrier PLAY in POLAND.
I'm curious if just a root and enabling VoEnabler packet from MAGISK will be enough.
Some of the guys from PIXEL 2 were suggesting to use modem configs with VoLTE, VoWifi from the same chipsets Qualcomm 845 and putting it to PIXEL 3.
mxtuu222 said:
I need to have an option for carrier PLAY in POLAND.
I'm curious if just a root and enabling VoEnabler packet from MAGISK will be enough.
Some of the guys from PIXEL 2 were suggesting to use modem configs with VoLTE, VoWifi from the same chipsets Qualcomm 845 and putting it to PIXEL 3.
Click to expand...
Click to collapse
That is problematic, as looking at the modem files (on my device), their is nothing under the folders for PLAY network. That would mean you could get the modem file from another similar device that has it, but the magisk setup would need to change two files instead of one. You would have to mock load a mbn file for your provider. You would need to change /mcfg_sw/generic/"modem file you want to try" and /mcfg_sw/mbn_sw.txt to include the directory of the file you want to include.
In reality, those mbn files you get might never work. This is google borking their work. For us in China, the modem files are their, they just refuse to reference them. For you the files are not even there it seems.
Try this. You will need magisk root to do it. You will also need to edit the zip file with the mbn file you can get a hold of. It will go in this file "For Help Pixel 3 LTE-VoLTE Enabler.zip\system\vendor\rfs\msm\mpss\readonly\vendor\mbn\mcfg_sw\generic\EU\Play" directory. It will simlpy load the modem file you need/want/got from a similar device at boot(just name it mcfg_sw.mbn and put it in there replacing the "put mcfg_sw.mbn here.txt"). You also need to delete the files in the description of the module (these are auto generated files) before this will take place. Good luck.
If you are doubtful, have a good look at what I am asking it to do.
wangdaning said:
Try this. You will need magisk root to do it. You will also need to edit the zip file with the mbn file you can get a hold of. It will go in this file "For Help Pixel 3 LTE-VoLTE Enabler.zip\system\vendor\rfs\msm\mpss\readonly\vendor\mbn\mcfg_sw\generic\EU\Play" directory. It will simlpy load the modem file you need/want/got from a similar device at boot(just name it mcfg_sw.mbn and put it in there replacing the "put mcfg_sw.mbn here.txt"). You also need to delete the files in the description of the module (these are auto generated files) before this will take place. Good luck.
If you are doubtful, have a good look at what I am asking it to do.
Click to expand...
Click to collapse
Great, thank you for all the tips. I will try to find some mbn files from NOKIA modems.
Do you know if it's possible to unlock the bootloader, root, make possible changes, unroot, lock bootloader?
Is the modem file will be permanently on vendor partition even if I install newest OTA?
mxtuu222 said:
Great, thank you for all the tips. I will try to find some mbn files from NOKIA modems.
Do you know if it's possible to unlock the bootloader, root, make possible changes, unroot, lock bootloader?
Is the modem file will be permanently on vendor partition even if I install newest OTA?
Click to expand...
Click to collapse
I am pretty sure you will need to keep root, as magisk is mocking the modem file you need. It somehow could cause the phone to connect and after the phone stays connected, but I do not see how that could work.
Related
Being a huge fan of the Pixel series and living in China is not easy. Just upgraded my XL to 3 XL and naturally I had to enable the LTE to work in China. Regardless what you may see on the Chinese forums (gfan), all the files you need are already present on the phone.
Files you need:
1) The ADB bridge for Windows
2) The most recent factory image
3) Magisk Manager
4) Chinese-Carrier-Pixel-3-xl-LTE-VoLTE-Enabler (Magisk Manager module) - Github direct: https://github.com/wangdaning/Chinese-Carrier-Pixel-3-xl-LTE-VoLTE-Enabler (big thank you to wangdaning for allowing me to publish it.) Also attached as a zip file to this post.
If you don't understand what these files are for or where to find them, perhaps you should ask a friend to help you. Flashing anything wrong could result in an expensive brick. Always backup your data, never blindly trust a post, and do your research. This post is in good faith and I am not liable for your actions.
Now, I don't have any of the variants of 3 (Pixel 3, 3a, 3a XL) but I would assume it would work in a similar fashion; however, see above and do your research. Check file structures, read some posts, backup data, etc. If someone does try it, please report both success and failure to build the knowledge.
1) We need to ensure our phone has an unlocked bootloader. If your bootloader is locked, you WILL lose all your data. Ensure you backup everything you want to keep. There is no getting around this step. We need to be a developer first. Go to Setting->About Phone->Build number (tap it until it says you are a developer). Then go to System-> Developer options -> OEM unlocking: turn it on. Next we need to reboot to the bootloader by resetting the phone and hold the down volume key as it reboots. In the bootloader, first use the volume keys to find and select the unlock the bootloader command with the power key. Then, we need to send the following command:
Code:
fastboot flashing unlock
You will receive a wipe and security warning. Accept and reboot the phone. It will wipe and reset your phone to factory.
2) I started from a stock image (May update; QQ2A.200501.001.B2). I suggest you start from there.
3) While we have the May update in front of us, we need to extract the boot.img so it can be patched to root the phone. TWRP doesn't support us at the time of writing on Android 10. (Hope that new baby is healthy!) The boot image can be found in the zip image-crosshatch-*release code*.zip/boot.img. Transfer this boot.img to the phone to be modded to enable root.
4) Next the phone needs to be rooted. You need to download the most recent version of Magisk Manager. Once installed, open up Magisk Manager. It will report no Magisk and that's ok, we are installing it now.
5) Tap install on Magisk and it will ask if you want to install, so install. Then you need to select the method. We will choose "Select and patch a file." Tell it where you saved your boot.img and it will patch it to allow us to root the phone. The output file we need is called magisk_patched.img is on the phone. Move it back to your directory with your ADB bridge.
6) Next we need to flash this patched boot file to our phone to complete the rooting process. Reboot to the bootloader and send the two commands:
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Reboot the phone and congrats, you are rooted with an unlocked bootloader.
7) To prepare for the install of the mock files that will point to the files on the phone, we need to delete a few checking files. Using your file explorer of choice that can gain root access delete the following:
/data/vendor/modem_fdr/fdr_check
everything in /data/vendor/radio/ (make the target folder empty)
8) Download the LTE_enabler from Github or the zip file here. Open Magisk Manager and open the menu -> Modules -> "Yellow Plus" to add. Point it to the zip file.
9) Reboot and enjoy using your phone as intended.
I tried to be as detailed as I could but not be over verbose either. If any step is unclear, there are more detailed guides on this forum concerning bootloader unlocking and Magisk rooting on Android 10. As a bonus tip, does the "x" showing no data bother you and stop some services from working? If so, this can be fixed by re-pointing your captive portal to something inside the firewall. This can be accomplished with one line of code:
Code:
adb shell "settings put global captive_portal_https_url https://developers.google.cn/generate_204"
Enjoy and if you have questions about Pixel and China, feel free to post them. Support right to repair!
I downloaded the zip file but it tells me it's not a module.
jifengSherry said:
I downloaded the zip file but it tells me it's not a module.
Click to expand...
Click to collapse
Could use more details, otherwise it is hard to help. It definitely is a module and installs fine. Something else is going on.
is this for china only? I have a Canadian 3 XL and moved to Bucharest, need to enable VOLTE on Orange Romania. I'm also on Android 11
It should work, but you would have to slightly modify the files. Instead of pointing to the Chinese carrier modem file you would want to point to the orange Romania file. I looked and there is an mbn file for orange Romania, it is just not included in the mbn_sw.txt. Then again, have you made sure Orange has activated VOLTE for your device?
wangdaning said:
It should work, but you would have to slightly modify the files. Instead of pointing to the Chinese carrier modem file you would want to point to the orange Romania file. I looked and there is an mbn file for orange Romania, it is just not included in the mbn_sw.txt. Then again, have you made sure Orange has activated VOLTE for your device?
Click to expand...
Click to collapse
I contacted Orange and they say VOLTE should be working, that the issue is my device not being compatible with their network. I also bought a Samsung watch 3 with LTE and can't activate LTE through my phone, i assume it's due to the same issue.
I'll follow your guide and report back.
Should be no issue if i am using Android 11 instead of 10 right?
Should be fine, you just need to make sure that you modify the mbn_sw.txt file to include the location of the Orange Romania mbn file. You might just try this first:
7) To prepare for the install of the mock files that will point to the files on the phone, we need to delete a few checking files. Using your file explorer of choice that can gain root access delete the following:
/data/vendor/modem_fdr/fdr_check
everything in /data/vendor/radio/ (make the target folder empty)
Click to expand...
Click to collapse
If that does not work then you need to modify the module to include the romania mbn.
wangdaning said:
Should be fine, you just need to make sure that you modify the mbn_sw.txt file to include the location of the Orange Romania mbn file. You might just try this first:
If that does not work then you need to modify the module to include the romania mbn.
Click to expand...
Click to collapse
Dude i love you! worked perfectly. I followed the guide to root Pixel 3 on Android 11 and then your steps, didn't modify anything and now i have VOLTE enabled!
thank you so much!
angeluszero said:
Dude i love you! worked perfectly. I followed the guide to root Pixel 3 on Android 11 and then your steps, didn't modify anything and now i have VOLTE enabled!
thank you so much!
Click to expand...
Click to collapse
ok i spoke too fast, while VOLTE is enabled now in the settings, when i make a call, it switches to H+ which means its not using VOLTE. any idea? I modified the .txt file to include the location of the romania .mbn file, i modified the file directly on the phone though, after installing the module with magisk manager
Not sure, to many variables at play. I mean it could be that orange Romania only has VoLTE in certain areas/cases. Try using *#*#4636#*#* and phone information, see what it says.
wangdaning said:
Not sure, to many variables at play. I mean it could be that orange Romania only has VoLTE in certain areas/cases. Try using *#*#4636#*#* and phone information, see what it says.
Click to expand...
Click to collapse
I did that, both VOLTE and Wifi calling say provisioned. I guess it might be something on Orange's end.
I saw a reddit post for a Pixel 3 having the same issue and the carrier ended up doing something on their side.
Confirmed working on Pixel 3 w/ Android 11!
Can this patch work on Pixel 4 as well? Thank you
duffercn said:
Can this patch work on Pixel 4 as well? Thank you
Click to expand...
Click to collapse
You would have to find the location of the files on the Pixel 4 as I am not sure where they are. Then modify the module to point to the correct location.
I made a video explaining how google blocks 5G in the software by default for unlisted countries.
I also tried posting this on reddit at r/googlepixel but mods deleted it.
I think this information should be spread to the wider general public because it affects just about every one of us here, having to root our phones to enable 5G, when this should just be enabled out of the box with absolutely no tinkering required.
If a phone is advertised as "5G ready", we should expect to be able to connect to our carrier's 5G network out of the box, regardless of being in a "supported country" or not.
This video shows that carrier-google certification is not necessary to connect to your carrier's 5G network.
I wonder if it's possible to file a class action lawsuit because blocking 5G in the software clearly has to be some sort of "misleading" or "false advertising" in terms of the phone being "5G" ready.
@elong7681
In reply to your other question. (proton rom thread may not be the best thread to discuss this)
carrier_policy.xml file is located inside the carrier mbn file.
To extract the mbn file, you need:
Efs Tools https://github.com/JohnBel/EfsTools/releases
dotnet-core https://dotnet.microsoft.com/download/dotnet-core/3.1
dotnet https://dotnet.microsoft.com/download/dotnet/5.0
1. Install dotnet-core and dotnet
2. Copy mbn file into the efstools folder
3. Run in command prompt: EfsTools.exe extractMbn -i mcfg_sw.mbn -p mcfg
4. New folder (mcfg) will be created and mbn file will be extracted inside.
Carrier_policy.xml is inside the "policyman" folder.
This video will also explain how the mbn files are used to enable or disable 5G.
swangjang said:
@elong7681
In reply to your other question. (proton rom thread may not be the best thread to discuss this)
carrier_policy.xml file is located inside the carrier mbn file.
To extract the mbn file, you need:
Efs Tools https://github.com/JohnBel/EfsTools/releases/tag/0.13
dotnet-core https://dotnet.microsoft.com/download/dotnet-core/3.1
dotnet https://dotnet.microsoft.com/download/dotnet/5.0
1. Install dotnet-core and dotnet
2. Copy mbn file into the efstools folder
3. Run in command prompt: EfsTools.exe extractMbn -i mcfg_sw.mbn -p mcfg
4. New folder (mcfg) will be created and mbn file will be extracted inside.
Carrier_policy.xml is inside the "policyman" folder.
This video will also explain how the mbn files are used to enable or disable 5G.
Click to expand...
Click to collapse
Thanks, I agree making this thread was a good idea.
I managed to pull the modem.img from the device.
To find which partition has what installed:
su
ls -la /dev/block/bootdevice/by-name
To pull the modem partition:
su
dd if=dev/block/sda12 of=/sdcard/modem_a.img
dd if=dev/block/sda13 of=/sdcard/modem_b.img
Unfortunately, it's not organised in folders to something like mcfg_sw/generic/*
but instead, it's all labeled in numbers.
They also can't be extracted using the method in post #2.
5G now working on my P5 with Free Mobile in France. Thanks for this post
swangjang said:
I managed to pull the modem.img from the device.
To find which partition has what installed:
su
ls -la /dev/block/bootdevice/by-name
To pull the modem partition:
su
dd if=dev/block/sda12 of=/sdcard/modem_a.img
dd if=dev/block/sda13 of=/sdcard/modem_b.img
Unfortunately, it's not organised in folders to something like mcfg_sw/generic/*
but instead, it's all labeled in numbers.
They also can't be extracted using the method in post #2.
Click to expand...
Click to collapse
@swangjang I have a quick question for you, before I rooted and started flashing roms and kernels but after I unlocked my bootloader I had the ability to record phones calls through the Google phone app but I only used it once so I stopped paying attention to the phone app while I was using it but I just recently noticed that I can no longer record phone calls, the record button is no longer present when I'm using the phone. I live in the US and that option is available for us but I no longer have the option, is there any chance you could help me get that option back ?
elong7681 said:
@swangjang I have a quick question for you, before I rooted and started flashing roms and kernels but after I unlocked my bootloader I had the ability to record phones calls through the Google phone app but I only used it once so I stopped paying attention to the phone app while I was using it but I just recently noticed that I can no longer record phone calls, the record button is no longer present when I'm using the phone. I live in the US and that option is available for us but I no longer have the option, is there any chance you could help me get that option back ?
Click to expand...
Click to collapse
I don't know much about it either lol. As far as I know, phone call recording was supposed to be removed from Google Phone app due to recording laws. Maybe you somehow had the beta version of the app and it got updated?
I use skvalex's recording app. You have to pay for premium after a free trial and it's quite costly for an app but I don't regret paying for it. It records both sides internally so bluetooth calls are also recorded both sides.
Something that might be worth considering if you can't find a way to get it back.
swangjang said:
I don't know much about it either lol. As far as I know, phone call recording was supposed to be removed from Google Phone app due to recording laws. Maybe you somehow had the beta version of the app and it got updated?
I use skvalex's recording app. You have to pay for premium after a free trial and it's quite costly for an app but I don't regret paying for it. It records both sides internally so bluetooth calls are also recorded both sides.
Something that might be worth considering if you can't find a way to get it back.
Click to expand...
Click to collapse
Thanks for your quick reply and the app reference
swangjang said:
@elong7681
In reply to your other question. (proton rom thread may not be the best thread to discuss this)
carrier_policy.xml file is located inside the carrier mbn file.
To extract the mbn file, you need:
Efs Tools https://github.com/JohnBel/EfsTools/releases/tag/0.13
dotnet-core https://dotnet.microsoft.com/download/dotnet-core/3.1
dotnet https://dotnet.microsoft.com/download/dotnet/5.0
1. Install dotnet-core and dotnet
2. Copy mbn file into the efstools folder
3. Run in command prompt: EfsTools.exe extractMbn -i mcfg_sw.mbn -p mcfg
4. New folder (mcfg) will be created and mbn file will be extracted inside.
Carrier_policy.xml is inside the "policyman" folder.
This video will also explain how the mbn files are used to enable or disable 5G.
Click to expand...
Click to collapse
Hi, this is helpful, but it would be great if you could give further detailed instructions as to how to enable 5G for unsupported carriers. In other words, what needs to be done after step #4 above (editing and copying of files)?
Also, would this process work is a dual sim configuration?
Thanks for your expose!
nsiti said:
Hi, this is helpful, but it would be great if you could give further detailed instructions as to how to enable 5G for unsupported carriers. In other words, what needs to be done after step #4 above (editing and copying of files)?
Also, would this process work is a dual sim configuration?
Thanks for your expose!
Click to expand...
Click to collapse
There are tutorials in other threads in this forum on how to do that. But if written guides are difficult to follow (not judging, the guides assume you have some PC knowledge and it took me a while to understand them too), I can make a video showing step by step process this weekend.
I'm not sure about dual sim 5G. 5G DSDS (Dual Sim Dual Standby) was only just implemented in March update and I don't have a 5G esim to test it.
swangjang said:
There are tutorials in other threads in this forum on how to do that. But if written guides are difficult to follow (not judging, the guides assume you have some PC knowledge and it took me a while to understand them too), I can make a video showing step by step process this weekend.
I'm not sure about dual sim 5G. 5G DSDS (Dual Sim Dual Standby) was only just implemented in March update and I don't have a 5G esim to test it.
Click to expand...
Click to collapse
@swangjang that would be awesome
elong7681 said:
@swangjang that would be awesome
Click to expand...
Click to collapse
Seems it's not necessary any more.
Finally , One Module-unlock 5G-Volte-VoWIFI
Hello,, After a long term of tries and workarounds. Finally found some module by ender-zhao :love::love::love::love::love::love: Thanks for him so much. Simply one module to enable 5G and Volte ,vowifi... install it from magisk , restart and...
forum.xda-developers.com
I haven't tried it yet but it seems promising.
swangjang said:
Seems it's not necessary any more.
Finally , One Module-unlock 5G-Volte-VoWIFI
Hello,, After a long term of tries and workarounds. Finally found some module by ender-zhao :love::love::love::love::love::love: Thanks for him so much. Simply one module to enable 5G and Volte ,vowifi... install it from magisk , restart and...
forum.xda-developers.com
I haven't tried it yet but it seems promising.
Click to expand...
Click to collapse
@swangjang if it isn't too much trouble and you have the time I personally think it would still benefit the community if you did that video tutorial because being able to do it manually would teach people how to do it versus using a simple magisk module either way thank you for your help and work thus far.
@swangjang is it possible to flash the Google and Qualcomm binaries and if so can you point me in the right direction?
elong7681 said:
@swangjang is it possible to flash the Google and Qualcomm binaries and if so can you point me in the right direction?
Click to expand...
Click to collapse
Sorry, I'm not sure what you mean by that...
swangjang said:
Sorry, I'm not sure what you mean by that...
Click to expand...
Click to collapse
They are located here https://developers.google.com/android/drivers Maybe this will help explain my question
elong7681 said:
They are located here https://developers.google.com/android/drivers Maybe this will help explain my question
Click to expand...
Click to collapse
Oh. I have no idea lol.
swangjang said:
Oh. I have no idea lol.
Click to expand...
Click to collapse
Ok I appreciate your response, besides the XDA Developers website is there any other websites like this one that you can recommend ?
elong7681 said:
Ok I appreciate your response, besides the XDA Developers website is there any other websites like this one that you can recommend ?
Click to expand...
Click to collapse
To my knowledge, I don't there are any other alternatives that's English based.
I still dont understand, do I need to root my device to do this?
EDIT: I have moved on to the Pixel 7 and don't have the energy to push into this any more. If this doesn't work for you for any reason, I don't know how to help you, sorry.
--------------------------------------------------------------
This is a step by step video tutorial for those who find written guides difficult to follow.
Download links and CMD commands:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
QPST Tool v2.7.496 - QPST Tool
Download the official QPST Tool v2.7.496 which allows you to flash the stock firmware on your Qualcomm Smartphone and Tablets.
qpsttool.com
Downloads | Notepad++
notepad-plus-plus.org
adb shell
su
resetprop ro.bootmode usbradio
resetprop ro.build.type userdebug
setprop sys.usb.config diag,diag_mdm,adb
diag_mdlog
@nsiti @elong7681
swangjang said:
@nsiti @elong7681
Click to expand...
Click to collapse
@swangjang you've done it once again! Lol thank you!
Thank you! Finally get to enjoy the full capabilities of my phone!
Thanks swanjang, very straightforward
I assume the phone does not have to be rooted for this?
Can similar approach be used to enable VoLTE & VoWIFI for un-supported carriers?
damkov said:
Thanks swanjang, very straightforward
I assume the phone does not have to be rooted for this?
Can similar approach be used to enable VoLTE & VoWIFI for un-supported carriers?
Click to expand...
Click to collapse
Your device must be rooted because abd shell calls for su (superuser).
swangjang said:
Your device must be rooted because abd shell calls for su (superuser).
Click to expand...
Click to collapse
thanks @swangjang for the youtube video, but is there anyway to do the same but without root?
xh4ni said:
thanks @swangjang for the youtube video, but is there anyway to do the same but without root?
Click to expand...
Click to collapse
It's not possible to do this without root. You need root to change some device settings to open a Diag Port, which is the bridge to the EFS Partition. This can only be done if you have root.
@swangjang I will attach all files from the policyman folder that I have from the March update, it includes carrierpolicy.xml
elong7681 said:
@swangjang I will attach all files from the policyman folder that I have from the March update, it includes carrierpolicy.xml
Click to expand...
Click to collapse
I think the March update changed how 'unlisted countries' sim cards load mbn. Your carrier is Verizon, right? therefore it will load the Verizon specific mbn which is why you have the carrier policy xml. But my carrier is not 'officially supported' therefore from March update, it loads the mbn without a carrier policy file maybe. Not too sure.
swangjang said:
I think the March update changed how 'unlisted countries' sim cards load mbn. Your carrier is Verizon, right? therefore it will load the Verizon specific mbn which is why you have the carrier policy xml. But my carrier is not 'officially supported' therefore from March update, it loads the mbn without a carrier policy file maybe. Not too sure.
Click to expand...
Click to collapse
Yes it is Verizon. That's bull**** if Google changed this so that people can't use their phones to it's fullest capabilities.
elong7681 said:
Yes it is Verizon. That's bull**** if Google changed this so that people can't use their phones to it's fullest capabilities.
Click to expand...
Click to collapse
Google is already limiting phone capabilities to US only. E.g "Call screening" and "Hold for me" is also US only feature. I can spoof my location with Market Unlocker to force enable it but this makes my phone think I have a Verizon sim card inserted which occasionally causes me to lose data connection (easy fix is to just make a phone call and hang up). Also, the March feature drop "Smart Compose" is also US only and I have no ****ing idea why. I understand it being English only and that's totally fair but limiting that to just the US is total bull****.
I was a long time samsung fan and switched over to Pixel 5 after hearing about all these advertised features, only to realise after I got it that these features are US only. Pixel 5 may be my first and last google phone, depending on how Google comes around and stop with all their bullshits.
Hi,
What are the commands to turn off diag mode off? or does this automatically disable when removing the USB, thank you.
rasseru16 said:
Hi,
What are the commands to turn off diag mode off? or does this automatically disable when removing the USB, thank you.
Click to expand...
Click to collapse
If I'm not mistaken it reverts back after a reboot and the phone is no longer recognized by QPST
elong7681 said:
If I'm not mistaken it reverts back after a reboot and the phone is no longer recognized by QPST
Click to expand...
Click to collapse
Ok thank you.
Thanks a lot for the video and instructions, however, I tried your method for CMHK (China Mobile Hong Kong) and it doesn't work.
galenfung said:
Thanks a lot for the video and instructions, however, I tried your method for CMHK (China Mobile Hong Kong) and it doesn't work.
Click to expand...
Click to collapse
China uses a different type of network technology than the global standard. This may be why it doesn't work for China.
Thank you so much , that was great & i have a pixel 5 with a 5G work because if this great thread
Hi, is the method works also to rooted CalyxOS or any other custom ROM? I'm thinking to move to CalyxOS, but want to keep VoLTE & VoWifi unlocked capablities and Gcam.
mxtuu222 said:
Hi, is the method works also to rooted CalyxOS or any other custom ROM? I'm thinking to move to CalyxOS, but want to keep VoLTE & VoWifi unlocked capablities and Gcam.
Click to expand...
Click to collapse
Hi, unfortunately I'm not sure if it will work on custom roms.
I just bought a Xperia XZ2 H8276 since the sim pins finally broke in my Xperia X Performance after about 4 year, word of advice don't make a sim work. Was not finding a Xperia XZ2 compact under $200 and the newer 5's are expensive, so that was the choice I made. It did not dawn on me that the move to volte only would make it hard to get newer unlocked phones on a nework. In trun looking into options pertaining to volte, switching to verizon was the only one that seemed to have a viable path. Talked with at&t where I found them unwilling to add my imei and don"t see a mdn that is clear cut for them, do see a mdn for tmobile but no service by my house. Verizon dose have dmd and they got the XZ2 compact, so there was light at the end of the tunel. So got the cheapest volte phone that I could find to activate a sim on, a moto e5 play is what I found. Will get to aguing with them now to add my imei since it work, unsure how that is going to go.
To get statrted a activated sim is needed and was done using the moto e5. After activation, need to talk with someone and have them check that sim the sim is CDMA-less with HD voice only. Best place I found to do that is start a chat with someone on this page, click chat in bottom right.
Verizon HD voice
For how I got the XZ2 to work on verizon gose like this based on many failed attempts. What I ended up doing is flashing H8216 Vodafone_Global_52.1.A.3.49-R9C firmware with H8314 Customized US_52.1.A.3.137-R7C oem sin files with newflasher, you can get these these off xperiafirm.
NewFlasher
XperiaFirm
Now with that in order, the verizon mbn needs added but need root to do so. If you dont have twrp that need installed and be sure to sideload magisk at the same time, other wise you will have boot loop to deal with.
TWRP
Magisk
After the phone has booted into the os, you need to now install the magisk app. Run this from whre you downloaded the application to your pc or install from the browser on the phone, need to cd to the place of download first if using terminal.
adb install Magisk-v23.0.apk
Magisk app
Here is the verizon mbn I pulled from the XZ2c modem sin.
Verizon mbn
That needs copyed to the phone SD card and use Root explorer to copy the mbn where it gose. I tryed PDC but could not get the drivers to work.
Root Explorer
You can you use this to install it if debug is on or down from the phone browser, cd to where you downloaded the file then...
adb install RootExplorer.apk
Now in root explorer, this is the destination to go and can only go there if root has been granted. If you dont get the promt to grant root go into magisk, click the shield at boot then the slider by the app. To copy the generic folder here from the sd card, click and hold it till hilighted where you can click the two papers stacked at the top. There will now be a clip board icon in the bottom right, do to the destination and click it.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw
The internal and external sd card will be one these two locations, ether use "adb push" or mtp to the put the directory on the sd card.
/storage/*-* *=a string of letters and numbers
/storage/emulated/0
/storage/self/primary
Now restart and dial this.
*#*#7378423#*#*
In service menu - service info - software info you should see this under current modem config
row/verizon/vl/us
Now dial this.
*#*#4636#*#*
Under phone information set network type to lte only and should see voice type lte. If all went well, you should now be able to make phone calls.
I would like to move on to installing lineage-os but volte was not working there. I need to use this phone for work, so am not going to get into debuging that. Be my guess to try but Im not sure what brakes installing that.
I got some help from junkie2100 and give thanks to those that have posted info/software that lead me this far in gettting volte working. Here are some the clues that aided in the journey.
clues
clues
clues
As for tmobile, you might be able to replicate this but intead use oem sin's from the xz3 H8416 US along with pulling its mdn out its modem sin. Not sure what is special in the oem sin that pertains to setting up the given carrier, so unsure what is needed to get at&t to work but you free to experiament if you choise just I will not be much help.
Thanks for taking the time to put this together, the information on getting VoLTE working in the US on the XZ2 seems to be pretty scattered across various threads over the last several years, so I appreciate you placing this here.
I am not on Verizon, but I have been trying to figure out how to get this working on T-Mobile. I have followed some other threads that point to downloading the XZ3 OEM sin files as part of its Customized US Firmware like you mentioned, replacing those in the stack for the XZ2 firmware of a matching/similar version, and flashing to my device. I noticed after doing that VoLTE is provisioned (greyed out but turned "on"), but the modem config when checking my settings is still "Unknown." In addition to that, setting the device to "LTE Only" causes calls to not be placed, and "LTE Preferred" leads to calls dropping down to 3G like they originally were before trying to flash anything.
I could maybe use a little help in understanding what you mean be "pulling the mdn out of the modem sin." Is this an additional step to just flashing the two OEM files mentioned above and if so, where would I find it and go about setting it up?
Appreciate it.
The mbn file you need is in the modem sin from the xz3 firmware and this is the binary you need to extract it, put both the unsin binary and modem_X-FLASH-ALL-B6B5.sin in the same folder. This is the config file used by the oem sin to setup the volte.
unsin binary
Now cd to the folder that has both those and run these commands.
./unsin ./modem_X-FLASH-ALL-B6B5.sin
mkdir ./modem
sudo mount -t vfat -o loop modem_X-FLASH-ALL-B6B5.img modem/
You now have the modem sin extracted and the image mounted in folder modem. From there you need a copy of this tmobile folder and move it to the sd card on the phone.
/image/modem_pr/mcfg/configs/mcfg_sw/generic/row/tmobile
Now you can umount the modem image.
sudo umount -t vfat modem_X-FLASH-ALL-B6B5.img modem/
Now on the phone in root explorer that tmobile folder gets copyed to here.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic/row
In this file you will also need to add these two lines so the mbn can be found.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw//mbn_sw.txt
mcfg_sw/generic/row/tmobile/vl/us/mcfg_sw.mbn
mcfg_sw/generic/row/tmobile/vlvw/us/mcfg_sw.mbn
Now restart and dial this.
*#*#7378423#*#*
In service menu - service info - software info you should see one these under current modem config
row/tmobie/vl/us
row/tmobile/vlvw/us
Would anyone care to guess if a rooted/ rom'ed 8216 model of the XZ2 will work on T-mobile now that they have declared many older phone models incompatible (perhaps related to VoLTE capability)? 1mouse3 does your phone still work on T-Mobile? Thanks!
how do i get the samsung screen recorder and secure folder on my a226b and or any other samsung ad i dont have them for some reason and i would like to know if theres any universal twrp or odin thing to flash that would gove them back or maybe secret setting to enable or apk to install
Win_7 said:
how do i get the samsung screen recorder and secure folder on my a226b and or any other samsung ad i dont have them for some reason and i would like to know if theres any universal twrp or odin thing to flash that would gove them back or maybe secret setting to enable or apk to install
Click to expand...
Click to collapse
There Isn't a screen recorder or secure folder on the SM-A226B you can use calculator+ and flash a android 13 GSI to use the screen recorder.
You can enable screenrecorder by modifiying some lines in /system/etc/floating_feature.xml
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
<SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>-pip</SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>
Without spaces. If there is already the value simply change to this. I'm working on a way to enable secure folder in my free time. First tests were successful however there are still some problems. I'm extracting files from A13 5G (SM-A136B) because it has the same chipset as A22 5G and has secure folder
fede2782 said:
You can enable screenrecorder by modifiying some lines in /system/etc/floating_feature.xml
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
<SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>-pip</SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>
Without spaces. If there is already the value simply change to this. I'm working on a way to enable secure folder in my free time. First tests were successful however there are still some problems. I'm extracting files from A13 5G (SM-A136B) because it has the same chipset as A22 5G and has secure folder
Click to expand...
Click to collapse
thanks!!!! will this work on any other phone other than a226b?
and do you know of any file manager app that can actually edit system files (i have a good one called filemanager+ but it can only read even if i do mount -o remount,rw /
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (https://www.apkmirror.com/apk/samsu.../samsung-capture-5-4-22-android-apk-download/) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
fede2782 said:
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (Here's where you can download latest apk) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
Click to expand...
Click to collapse
eh thats ok i used adb and accepted root on device
my phone didnt have the file is that ok if i just create it?
also you made a mistake on the url can you send a working one?
fede2782 said:
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (Here's where you can download latest apk) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
Click to expand...
Click to collapse
um how can i fix "system partition doesnt have enough free space" when trying to convert newer samsung capture to system app
You don't need to convert. Just update with apk when phone on. Like every app. I made a mistake in the link. I fixed it. The file should exist on every Samsung one ui device.
fede2782 said:
You don't need to convert. Just update with apk when phone on. Like every app. I made a mistake in the link. I fixed it. The file should exist on every Samsung one ui device.
Click to expand...
Click to collapse
oh bruh i deleted system app and reinstalled
An apk of Samsung capture must remain in the /system partition in order to get priv-app permissions
I recommend you to reinstall original firmware (One UI 5.1 if it is available in your region) then modify floating_feature.xml.
This file is placed in every samsung device in /system/etc/floating_feature.xml
You do not have to create nothing. Just modify it add that lines. In my firmware (official one UI 5.1) the second line is already placed in the file. So I simply added:
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
in the middle of the file
fede2782 said:
An apk of Samsung capture must remain in the /system partition in order to get priv-app permissions
I recommend you to reinstall original firmware (One UI 5.1 if it is available in your region) then modify floating_feature.xml.
This file is placed in every samsung device in /system/etc/floating_feature.xml
You do not have to create nothing. Just modify it add that lines. In my firmware (official one UI 5.1) the second line is already placed in the file. So I simply added:
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
in the middle of the file
Click to expand...
Click to collapse
i still didnt have the file i made it and updated capture but didnt get screen recorder even after reboot :/ am on android 11 and im not updating especially as theres bootloader update
For me it is working. The file floating_feature.xml needs to exist. if it doesn't exist this means your firmware version is old and it doesn't have modern one UI. I don't know how I can help you more
fede2782 said:
For me it is working. The file floating_feature.xml needs to exist. if it doesn't exist this means your firmware version is old and it doesn't have modern one UI. I don't know how I can help you more
Click to expand...
Click to collapse
i have a70 with screenrecorder its on android 10
my a22 is on oneui 3.1
I don't know.
fede2782 said:
I don't know.
Click to expand...
Click to collapse
alright then sorry for bothgering you
Win_7 said:
alright then sorry for bothgering you
Click to expand...
Click to collapse
Don't worry
Image clipper wip being prepared! Object Eraser! deCorizer - Add missing One UI features to A22 5G
You can flash this Magisk module AT YOUR OWN RISK. I AM NOT RESPONSIBLE for lost warranty, bootloops, lost data or any other damage to your device. THE SOFTWARE IS PROVIDED “AS IS” This module tries to add as many One UI features as possible to...
forum.xda-developers.com
fede2782 said:
Image clipper wip being prepared! Object Eraser! deCorizer - Add missing One UI features to A22 5G
You can flash this Magisk module AT YOUR OWN RISK. I AM NOT RESPONSIBLE for lost warranty, bootloops, lost data or any other damage to your device. THE SOFTWARE IS PROVIDED “AS IS” This module tries to add as many One UI features as possible to...
forum.xda-developers.com
Click to expand...
Click to collapse
it didnt work
it just said system is root and a couple other things then i rebooted nthing
Win_7 said:
it didnt work
it just said system is root and a couple other things then i rebooted nthing
Click to expand...
Click to collapse
At the moment is only for DWC1 OXM
I'll try to download your file from AVA1 as soon as I can and I'll patch it
fede2782 said:
At the moment is only for DWC1 OXM
I'll try to download your file from AVA1 as soon as I can and I'll patch it
Click to expand...
Click to collapse
i have AVA6 not 1