HI guys, I know there is a EE/3UK thread available but this Dual SIM version related, so don't shoot me, pls In Czech we only can buy Dual SIM version (official distribution - unofficial is available but only at some stores that are not very reliable + if you buy unofficial distribution you won't be able to bring it to Sony repair center but only to a seller). So I bought Dual SIM and I asked my network provider (czech Vodafone) if they are going to provide VoLTE/VoWiFi services for this phone and answer was no, as this is dual SIM and not a single SIM (they don't want you to use second SIM card of their competitor even if you use SD card in that hybrid slot).
So my question is if you think it would be possible to get it working on XZP Dual SIM in the future? Or (this is the worst scenario) will it be possible only when root is available as all modem files are stored in /system/etc/customization/modem (and I guess it's not a good idea to flash single SIM system.sin over DSDS system.sin)? If only rooting will help, how do I find out which other files from 1 SIM version should be necessary (dependencies) to flash (apart of amss_fsg_maple_vodafone_cz_volte_vowifi_tar.mbn)? Maybe build.prop and editing
Code:
# DSDS Modem Bringup
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,0
I know provider has to enable these features but as said they won't do it at this DSDS version but only at single SIM. There is an app from czech Vodafone (only for WiFi calling) but that app doesn't even work on dual SIM version :/ Thank you for any hint
I'm sure you can use VoLTE/VoWiFi if you can find proper settings. In the best case, if VoLTE/VoWiFi is already enabled on your phone, just find any phone that already has this enabled and then copy ims settings from apn menu.
If you never use VoLTE on any other phones before you may need to ask you phone operator to forcefully enable this service for you (for example, XZs is said not to compatible with VoLTE with my current operator, but after I forcefully asked them to enable the service no matter what phone I am using, VoLTE has shown. .
The following is the screenshot from my dual sim XZP with VoLTE icon on the top.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
romeokk said:
I'm sure you can use VoLTE/VoWiFi if you can find proper settings. In the best case, if VoLTE/VoWiFi is already enabled on your phone, just find any phone that already has this enabled and then copy ims settings from apn menu.
If you never use VoLTE on any other phones before you may need to ask you phone operator to forcefully enable this service for you (for example, XZs is said not to compatible with VoLTE with my current operator, but after I forcefully asked them to enable the service no matter what phone I am using, VoLTE has shown. .
The following is the screenshot from my dual sim XZP with VoLTE icon on the top.
Click to expand...
Click to collapse
Thank you for reply. May I ask what provider you have, please? I just got reply from VF: "direct VoLTE/VoWiFi support for dual SIM phones is not possible due to chipsets capabilities". lol
lesmil said:
Thank you for reply. May I ask what provider you have, please? I just got reply from VF: "direct VoLTE/VoWiFi support for dual SIM phones is not possible due to chipsets capabilities". lol
Click to expand...
Click to collapse
I'm using dtac (Telenor Thailand) and AIS.
Here in my country, all flagship phones (except iPhone) are dual sims. I have used XZs dual, Galaxy S7Edge dual, and S8+ dual, all of them shows VoLTE/VoWifi icons and toggle switches.
In Europe, no operator has volte or vowifi for dual sim version.
Your best chance would be to flash single sim firmware to your dual sim device.
Not done that personally, but some people have do it with success.
Ofcourse you will lose 2nd SIM
If anything goes wrong then you can flash back to DS firmware
VeixES said:
In Europe, no operator has volte or vowifi for dual sim version.
Your best chance would be to flash single sim firmware to your dual sim device.
Not done that personally, but some people have do it with success.
Ofcourse you will lose 2nd SIM
If anything goes wrong then you can flash back to DS firmware
Click to expand...
Click to collapse
Thanks mate. I have seen your post earlier that flashing single sim fw over dual sim is experimental and I haven't seen anobydy flashing it so far (maybe I didn't search properly ). I will check Single SIM FWs later to see if there is modem update for cz vodafone tho and might give it a chance to flash (the truth is that Sony hasn't added that support for that carrier - I see german, uk VF but not CZ one). I don't care much about second SIM as I use that slot for SD card anyway.
I will check later on which oem variant you would need, so it correctly loads VF CZ
Where did you find amss_fsg_maple_vodafone_cz_volte_vowifi_tar.mbn ? On XZ, VF CZ firmware loads amss_fsg_kagura_vodafone5_tar.mbn and on XZ Premium there is also amss_fsg_maple_vodafone5_tar.mbn available.
But from VF webpage, i don't even see XZ having volte or vowifi calling support. And XZ Premium does not seem to have VF CZ region firmware. You seem to be on a very experimental track now.
Atleast for T-Mobile CZ i can see proper modem config available amss_fsg_maple_telekom_czech_volte_vowifi_tar.mbn, so when they decide to start selling XZ Premium then you would have VoLTE/VoWiFi for that provider.
With rooted device, you could manually select modem configuration files. But knowing the root situation on XZ Premium and the operator whitelisting devices, then i would not hold my breath for that method also.
Meh, I was thinking faster than typing. Should be "for example, if such a mbn exists". So vodafone5 is for CZ VF? How did you find it out if I may ask, pls? Even this czech telekom is suspicious, as only Slovak Telekom sells XZP (in czech there is no carrier selling it actually). I will check FW regulary with XperiFirm to find out if sony added CZ VF support into CE1 Single SIM and will decide if to flash this version over dual SIM. May I only ask, if I do that, is there any driver that has to be installed? Or is it enough having Xperia Companion installed (and not running while using newflasher)?
1. Download the oem/region fw via Xperifirm
2. Use Unsin.exe https://forum.xda-developers.com/crossdevice-dev/sony/tool-unsin-sin-v3-unpacker-t3128106 to unpack the oem*.sin file
3. Use 7zip or ext2explorer to extract files from oem*.ext4 file
These files are then all the bits and customization for given operator/region. Along the the extracted files there is folder "modem-config" which will contain modem.conf file(can be in different subfolders). THis modem.conf file defines(in shortened name) which conf to load when sim card is inserted. Checking all the modem.con files will tell you which operators get special configuration loaded if their sim inserted. If there is nothing in modem.conf or there is no "modem-config" folder then no special modem configuration will be loaded(no volte, no vowifi etc).
Checked single sim CE1 fw also, no special modem conf loading to any operator. So i would suggest staying on the dual sim CE1 firmware and wait for CZ operators to announce selling XZ Premium.
VeixES said:
1. Download the oem/region fw via Xperifirm
2. Use Unsin.exe https://forum.xda-developers.com/crossdevice-dev/sony/tool-unsin-sin-v3-unpacker-t3128106 to unpack the oem*.sin file
3. Use 7zip or ext2explorer to extract files from oem*.ext4 file
These files are then all the bits and customization for given operator/region. Along the the extracted files there is folder "modem-config" which will contain modem.conf file(can be in different subfolders). THis modem.conf file defines(in shortened name) which conf to load when sim card is inserted. Checking all the modem.con files will tell you which operators get special configuration loaded if their sim inserted. If there is nothing in modem.conf or there is no "modem-config" folder then no special modem configuration will be loaded(no volte, no vowifi etc).
Checked single sim CE1 fw also, no special modem conf loading to any operator. So i would suggest staying on the dual sim CE1 firmware and wait for CZ operators to announce selling XZ Premium.
Click to expand...
Click to collapse
I already have all those files and desined and extracted all possible ext4 . Will check it every time new update is available tho. And I found a posts where single sim fw was flashed over dual sim fw:
https://forum.xda-developers.com/showpost.php?p=73273002&postcount=111
https://forum.xda-developers.com/showpost.php?p=73279355&postcount=113
Thx for your time m8.
Edit: I think that modem-conf is carrier hiccup - when you insert their sim card, vowifi and volte will be working, if you insert another carier sim card it won't work.
lesmil, it seems there is a Vodafone CZ specific firmware for Sony XZ1 https://xpericheck.com/cda/1310-8082
Currently it does not load "vodafone_czech_volte_vowifi" modem config yet, but this might change in the future.
Maybe we can mix and match these modem configs between XZ premium and XZ1, but will have to wait and see.
Hello mate. I do know about Vodafone CZ modem at XZ1 and XZ1 Compact. They will sell these phones (without Vodafone branded ROM, so VoLTE and VoWiFi should work OOB from any czech seller). The thing is that Sony won't add VF CZ modem config into XZP :/ That's how EU carriers define 21th century ^^
Someone try flashing single sim soft on dual sim model?
piotrzet said:
Someone try flashing single sim soft on dual sim model?
Click to expand...
Click to collapse
Already told you I did. If you need 100 confirmations that it is working, maybe you should create thread for it
[ROOT] US T-mobile VoLTE & Wifi calling working on Pie if you flash my .zip via TWRP
Tested on XZP dual on latest 47.2.A.6.30 US firmware
Related
Have you ever lose your phone ‘s signal due to accidentally selecting USA BAND in *#*#4636#*#* menu? If yes, this guide is for you. Thanks to @ian.anindya for guidance and clues on how to restore my phone’s signal back.
Requirement:
1. Rooted HTC One E8 phone
2. Knowledge on how to use ADB command
3. Software Qpst, Qxdm and Mztool
4. A cup of coffee
This is how to do it:
1. Download all necessary software here and extract to separate folder.
2. Install Qpst and Qxdm.
3. Enable USB debugging on your phone and connect it to PC. Verify with command
Code:
adb devices
It must show your device ID and must not be offline.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Input command below to activate diagnostic mode
Code:
adb shell
su
If this is the first time you issue the command, check your phone. There is a prompt asking for root permission, grant it. Continue with below command
Code:
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
5. Your PC will detect new hardware and install necessary drivers. If you do not have the drivers, browse to HTC Diag folder which you download together with qpst and qxdm software. If the drivers installation succeed, check your PC device manager and it will show your HTC Diagnostic Interface (in my case COM5, the value can be different on your PC).
Your phone is now ready for the fun part playing with NV items
6. Open QPST configuration from your windows start menu. Go to Ports tab, and then add your HTC Diag com port.
7. We need to backup current NV items in case something goes wrong. Choose start client, software download. On backup tab, select where to store .qcn file and click start and wait until finished. After finished, close QPST program.
8. Open QXDM professional from your windows start menu. Select NV Browser in the drop down list. Since we do not connect our phone yet, the NV list is not editable.
9. Choose option, communications. Select HTC Diag com port in the target port. If succeed now the NV browser window is editable.
Tick Dual SIM if your phone is dual SIM version. Subscription ID field will be activated.
ID 0 is for SIM 1 and ID 1 is for SIM 2.
For this purpose, we will only need to edit NV item 1877, 441, 946 and 2954.
10. SIM 1
Make sure Dual SIM is ticked and Subscription id is 0.
We use Mztool application to define frequency parameters.
Go to Band Preference (NV Value) tab to configure GSM and WCDMA frequency that we want to put in our phone. Choose the frequency that supported by your phone.
Mine is like this
According to the picture,
Box No.1 refers to NV item 1877. Value is 73925504 (remove commas)
Box No.2 refers to NV item 441. Value is 896
Box No.3 refers to NV item 946. Value is 1128
Box No.4 referes to NV item 2954. Value is 0
All values are in Decimal
Now we need to input these values in NV browser window in Qxdm.
NV Item 1877
On column ID, find item 1877. Click Read to read current value. Take note of it, in case something goes wrong. Write the new value 73925504 under input field and click Write. Click Read again to verify.
NV Item 441
On column ID, find item 441. Click Read to read current value. Take note of it, in case something goes wrong. Write the new value 896 under input field. The value is automatically converted in to Hex.
In my case 896 in decimal is the same as 0x380 in Hex. Click Write. Click Read again to verify.
Do not touch the nam value.
NV Item 946
On column ID, find item 946. Click Read to read current value. Take note of it, in case something goes wrong. Write the new value 1128 under input field. The value is automatically converted in to Hex.
In my case 1128 in decimal is the same as 0x468 in Hex. Click Write. Click Read again to verify.
Do not touch the nam value.
NV Item 2954
On column ID, find item 2954. Click Read to read current value. Take note of it, in case something goes wrong. Write the new value 0 under input field and click Write. Click Read again to verify.
Do not touch the nam value.
Up to here, if you reboot your phone, It should get GSM/WCDMA signal on SIM 1 only. Now we are working for SIM 2.
11. SIM 2
Dual SIM is still ticked but this time choose Subscription ID 1
Remember that SIM 2 supports only GSM (no WCDMA). So in Mztool, choose only GSM signal.
Mine is like this
According to the picture,
NV item 1877 value is 2622336
NV item 441 value is 896
NV item 946 value is 40
NV item 2954 value is 0
All values are in Decimal
Do the same procedures as SIM 1.
12. After finished editing NV items, close Qxdm and then we have to close the diagnostic mode.
Wait around 10 seconds and then input command below to deactivate diagnostic mode
Code:
adb shell
su
echo 0 > /sys/devices/virtual/android_usb/android0/f_diag/on
13. Reboot your phone using ADB command
Code:
adb reboot
After rebooting your phone, wait for 1 or 2 minutes and then hopefully you will get the GSM/WCDMA signal.
Later on, I will continue this guide on how to add LTE Band
===Reserved===
Hello,.
first off all im from Indonesia too, from Surabaya,..
Ane komen pake bahasa inggris aja ya soalnya ini forum internasional
I had that issue too, try to factory reset about several time but still no clue,...
i sent my device to service center, about 1 month and when my device back, its updated from 4.4.2 to 5.0.2, but my sim 1 slot still no signal, its ridiculous how htc tech guy work, they not test my device after update
i wanna follow your guide,. is that work on lolipop?
thanks for advice
Yes, it works on lolypop 5.0.2. Root your device first using latest supersu, flash from twrp recovery.
stuntgp said:
Yes, it works on lolypop 5.0.2. Root your device first using latest supersu, flash from twrp recovery.
Click to expand...
Click to collapse
Yes i'm gonna try to root it first, newbie about it, so many reading about "how to" :laugh:
wish me luck,.. im gonna inform you and maybe need your advice if meet any trouble,.. :laugh:
after reading all night, try and error your guide on second night, yeahhhh finally my sim 1 signal HTC E8 (m8sd - Indonesia) goes ON again, and normal capturing network Indosat, and Simpati (Indonesian Provider) and look working good on HSDPA and 3G ,...
BTW your value on MZtools is different when im genereate, but i am follow your value (because i know we are from same country),..
HTC Service in Indonesia cannot fix this, THEY JUST UPGRADE ROM FROM 4.4.2 TO 5.02 I DONT KNOW WHY THEY ARE NOT TESTING MY SIGNAL FIRST BEFORE SEND BACK MY DEVICE,....
HAHAHAH THX A LOT FOR MADE THIS GUIDE,..... its really reliable guide and easy to follow (i am noob )...
bugs182 said:
after reading all night, try and error your guide on second night, yeahhhh finally my sim 1 signal HTC E8 (m8sd - Indonesia) goes ON again, and normal capturing network Indosat, and Simpati (Indonesian Provider) and look working good on HSDPA and 3G ,...
BTW your value on MZtools is different when im genereate, but i am follow your value (because i know we are from same country),..
HTC Service in Indonesia cannot fix this, THEY JUST UPGRADE ROM FROM 4.4.2 TO 5.02 I DONT KNOW WHY THEY ARE NOT TESTING MY SIGNAL FIRST BEFORE SEND BACK MY DEVICE,....
HAHAHAH THX A LOT FOR MADE THIS GUIDE,..... its really reliable guide and easy to follow (i am noob )...
Click to expand...
Click to collapse
Glad to hear that... Now I am trying to inject LTE band, especially for Band 3 and Band 8 which is supported in Indonesia.
Thanks bro
This thread solved my problem after 1,5 months)
Good job
I'm from indonesia too
Malang exactly
Thanks for @ian.anindya for show me this thread and remoted my pc using team viewer to unbrick my phone
Sorry for bad english
Sent from my HTC One_E8 dual sim using XDA Free mobile app
network Roaming not working after this nv restore
hi there,
thanks a lot for putting up these recovery steps..they were really helpful..but only one thing is that i'm still unable to get a signal while roaming..
do you have any solution for the same..or atleast if i can get a backup of qcn file from stock untouched htc e8 ...that should help..
Jude85 said:
hi there,
thanks a lot for putting up these recovery steps..they were really helpful..but only one thing is that i'm still unable to get a signal while roaming..
do you have any solution for the same..or atleast if i can get a backup of qcn file from stock untouched htc e8 ...that should help..
Click to expand...
Click to collapse
I have not tried roam with other network, but have you checked frequency band of your destination network? and compare with the one in your NV items list?
stuntgp said:
I have not tried roam with other network, but have you checked frequency band of your destination network? and compare with the one in your NV items list?
Click to expand...
Click to collapse
Hi, this is more about a national roaming within india and i dont think the bands will vary in such case...and to be more clear i had searched the bands listed for E8 dual sim on htc site and added them on the mz tool. i believe there is some other nv item that needs an edit to enable the roaming, would be of great help if you could suggest reg it.
Install Superuser "The su binary is out of date."
stuntgp said:
Yes, it works on lolypop 5.0.2. Root your device first using latest supersu, flash from twrp recovery.
Click to expand...
Click to collapse
I am having difficulty in rooting my phone (HTC One E8 Dual Sim) completely, as I get error message "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." Options are --> Cancel/ Recovery Install. When I choose Recovery Install, I get another screen which states "There was an error installing Superuser. Please send a log of the error to the developer."
I used TWRP 2.8.7.0 to flash recovery through ADB and installed superuser.zip obtained from clockworkmod site which I guess is the latest version of SU.
I request for your technical expertise to help m e out as I need to perform lot of troubleshooting steps further to rectify the issue with USA Band.
Thank you.
Jude85 said:
Hi, this is more about a national roaming within india and i dont think the bands will vary in such case...and to be more clear i had searched the bands listed for E8 dual sim on htc site and added them on the mz tool. i believe there is some other nv item that needs an edit to enable the roaming, would be of great help if you could suggest reg it.
Click to expand...
Click to collapse
Hi ,
could you pls post the NV items used ,
I'm from India too , but i couldnt get CDMA signal after chaging NV items .
Now im able to use GSM only in slot 2 .
in Slot 1 couldnt reconize cdma/gsm .
---------- Post added at 05:12 AM ---------- Previous post was at 05:08 AM ----------
stuntgp said:
I have not tried roam with other network, but have you checked frequency band of your destination network? and compare with the one in your NV items list?
Click to expand...
Click to collapse
Hi ,
could you pls post the NV items used ,
I'm from India too , but i couldnt get CDMA signal after chaging NV items .
Now im able to use GSM only in slot 2 .
in Slot 1 couldnt reconize cdma/gsm .
default qcn /original qcn
Even my phone sim slot one doesnt work. it detects sim number but no n/w. I tired changing the NV items as suggested, still no n/w
I have only 2G n/w in sim slot 2
The moment i reached US, slot one stopped working.
Please suggest some way to enable slot one .
Thanks
rahul01libra said:
Hi ,
could you pls post the NV items used ,
I'm from India too , but i couldnt get CDMA signal after chaging NV items .
Now im able to use GSM only in slot 2 .
in Slot 1 couldnt reconize cdma/gsm .
---------- Post added at 05:12 AM ---------- Previous post was at 05:08 AM ----------
Hi ,
could you pls post the NV items used ,
I'm from India too , but i couldnt get CDMA signal after chaging NV items .
Now im able to use GSM only in slot 2 .
in Slot 1 couldnt reconize cdma/gsm .
Click to expand...
Click to collapse
For people under warranty !
Hey Guys ! I had the same problem in my HTC E8. Gave it to the service centre and got the motherboard replaced after ~25 days.
Just got the phone back . Has a different IMEI number now.
Phone now has Wifi signal issues ( Getting very less signal strength in relative comparison to my other phone ) and it takes about ~15minutes for the data to turn ON.
Hence the phone is back to the service centre .
can be refurbished device
icyspikey said:
Hey Guys ! I had the same problem in my HTC E8. Gave it to the service centre and got the motherboard replaced after ~25 days.
Just got the phone back . Has a different IMEI number now.
Phone now has Wifi signal issues ( Getting very less signal strength in relative comparison to my other phone ) and it takes about ~15minutes for the data to turn ON.
Hence the phone is back to the service centre .
Click to expand...
Click to collapse
The warranty replacement can be refurbished ones. This is the only reason I did not send my mobile to HTC US warranty claim centre. The Indian purchased mobile also have global warranty , but the claim device can be refurbished. I purchased mine just 3 month back for full price and dont want to receive refubished unit
So still working on my second sim slot, hopefully if the first sim slot works in India once I reach , I will be very happy . Atleast i dont have to fight with HTC for warranty replacement .
Anyways i will never buy another HTC .
NV Items for Indian bands used in HTC ONE E8
SIM 1
1877 : 82314112
0441 : 896
0946 : 1256
2954 : 0
SIM 2
1877 : 2622336
0441 : 896
0946 : 40
2954 : 0
Atlast my both sim s working gr8 .
Thank you Anindya for such a great post ...............:good::good::good::good::good::good::good::good:
---------- Post added at 12:29 PM ---------- Previous post was at 12:25 PM ----------
VERY big Thank you:good::good::good::good::good::good::good::good::good::good::good::good:
d
can see both band USA and Cellular(800 Mhz)
rahul01libra said:
SIM 1
1877 : 82314112
0441 : 896
0946 : 1256
2954 : 0
SIM 2
1877 : 2622336
0441 : 896
0946 : 40
2954 : 0
Atlast my both sim s working gr8 .
Thank you Anindya for such a great post ...............:good::good::good::good::good::good::good::good:
---------- Post added at 12:29 PM ---------- Previous post was at 12:25 PM ----------
VERY big Thank you:good::good::good::good::good::good::good::good::good::good::good::good:
d
Click to expand...
Click to collapse
Thanks a lot for response, Now with your NV values, i can see both bands USA and Cellular (800 MHz) from *#*#4636#*#*
Atleast it has come back to original setting , even though i still dont have n/w in sim slot 1
With my experiance ..... pls follow the below ,,,,
Put the CDMA in SIM lot 1 and GSM in sim slot 2
1 . Got to *#*#4636#*#* and selct radio bands to Cellular (800 MHz) only ,,,,
2 .. and keep the all type of signalings like WCDMA/GSM/CDMA/EVODO/LTE auto ......
u will get sifnal in both sims.................
keep rocking.......................:good::good::good::good::good:
slot one is tmobile gsm
I am using T-Mobile gsm in slot one . I think wcdma or 3g gsm should work onnslot one . Correct me if I am wrong
Airtel 2g/3g used to work in slot one when I was in India
I will be happy even if 2g works . I have kept the settings as you have mentioned
Warning: This is dangerous! Even if you do everything according to the following description, your phone may end up damaged! There are no warranties!!
You may want to have a look at this thread: [GUIDE] to enable DualSim on SingleSim Moto Z by xequtor.
It also describes a way to enable dual-sim capability for devices that are shipped with just single-sim capability. Based on the research by -=MoRpH=- for another MOTO device, xequtor adapted the hack for the MOTO Z - nice work!
That method requires you to perform modifications on files within the FSG partition and setup a persistent variable. This is considerably safe, since this basically affects pretty generic data. Stick with this, if you want to keep the risks of what you're doing (to your device) rather low!
Note: if you did the changes as descibed in xequtor's guide and you now want to try out this method - you first need to revert those changes, e.g. restore your backup of the original fsg partiton (TWRP)!
There is another way. I initially wanted to post it into xequtor's thread. However, I decided against it in order to avoid confusion that can easily result in irreparable data loss if done wrong! The required modification is considerably simple, even much simpler than the other approach, but it bears a different kind of risk: you're operating on per device individual data. These are usually not part of "nandroid" backups. Device-individual data is stored in the various partitons of the sdc flash drive. The following approach makes a tiny modification to the HW partition. However, we first make backups - and only with those in hand, the potential risks are severely mitigated, almost eleminated!
unlock bootloader
perform dualsim mod patch <-- here we go!
re-lock bootloader
Advantages: persistent: with patch applied, you phone will remain a dual-sim phone, regardless of OTA-/fastboot-updates and restored backups. relock-safe: with a stock rom properly installed, you can relock the bootloader and keep the dual-sim feature. It doesn't vanish after OTA-updates etc. You have to manually revert the mod to get back to single-sim mode.
Issues: IMEI-1: as with all dualsim mods: IMEI-1 will display as 0 (invalid), a carrier possibly may not let you connect. Detectable modification:Though this mod does in no way affect the security of this device, is is detectable. In the unlikely event, that this causes problems, you can still undo the changes and go back to single-sim mode. Unlocked bootloader:If you unlocked your bootloader just for this mod, as we cannot do the mod without, you can lock it again afterwards. However, the warranty-void bit keeps being set.
You need:
USB-Stick (either native or via USB-C-Hub/Adapter) ... or ... microSD card ...or... do it all via fastboot & adb
have fastboot & adb drivers installed.
have the bootloader unlocked
If you have just only unlocked the bootloader and changed nothing else then make a backup of your current recovery image! For this you can boot TWRP from ram:
Code:
fastboot boot twrp-3.1.0-0-griffin.img
Then you have to flash TWRP in order to be able to write the mod to flash - afterwards, you still can restore the original recovery and then relock the bootloader.
Code:
fastboot flash recovery twrp-3.1.0-0-griffin.img
Mod via USB-stick / microSD-card & update_signed.zip: [Note: this is experimental and risky! For now, I recommend the manual option described below]
copy the attached update_signed.zip to your USB stick (or microSD card)
connect USB-Stick/microSD card to your MOTO-Z
boot into TWRP recovery
install --> go to usb/sdcard and select the update_signed.zip
in order to activate the mod, you still need to erase the partitions modemst1, modemst2 and cache: reboot into bootloader...
Code:
fastboot oem hw
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot reboot
Modding details / diy via fastoot & adb:
boot into bootloader mode
Code:
fastboot oem hw
you'll see the dualsim: false entry. That's what we are want to change...
boot recovery from flash (ram boot = no write access)
Code:
adb shell "dd if=/dev/block/sdc3 of=/tmp/sdc3.bin"
adb pull /tmp/sdc3.bin
Look for the dualsim entry via hex editor. There you will find the pattern "dualsim [...] \06 [..] false \00". The update script changes that to "dualsim [...] \06 [..] true \00 \00". It should be \05, but that requires proper checks of the absolute address boundaries - you might need to rearrange all the following tags. A sting with two terminating zeros keeps the structure and has no negative effect. (See hex editor screenshots below).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Afterwards, upload the modified file back to the phone and dd it back into flash:
Code:
adb push sdc3_mod.bin /tmp/sdc3_mod.bin
adb shell "dd if=/tmp/sdc3_mod.bin of=/dev/block/sdc3"
adb reboot bootloader
in bootloader mode you may want to check whether it worked.. & erase modemst1, modemst2 & cache!
Code:
fastboot oem hw
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot reboot
Here are some pictures from my re-locked dualsim-modded stock rom - as you can see, full dualsim support is present. However, no IMEI for the second sim card. At least here in Germany and many other countries that's (currently) not an issue.
I didn't upgrade to the latest nougat version in order to keep my current bootloader version... (I'm running LineageOS anyway..)
Links:
https://dl.twrp.me/griffin/twrp-3.1.0-0-griffin.img.html
reserved
It is blocked on bootloader unlocked message after the installation of the update zip
I have the lastest bootloader
EDIT: I installed Lineage OS and it works but the sim 2 has not network
chucky91 said:
It is blocked on bootloader unlocked message after the installation of the update zip
I have the lastest bootloader
EDIT: I installed Lineage OS and it works but the sim 2 has not network
Click to expand...
Click to collapse
Did you erase modemst1, modemst2 & cache after you applied the mod?
If so, perhaps IMEI=0 actually is an issue for you... (which country, which carrier?)
I erased modemst1, modemst2 & cache after I applied the mod. I saw that it works fine when I choose the sim 1 by default for data but when I choose sim 2, I lose network from sim 2, my carrier are Free and Bouygues (France) in roaming with Rogers and Telus (Canada)
chucky91 said:
I erased modemst1, modemst2 & cache after I applied the mod. I saw that it works fine when I choose the sim 1 by default for data but when I choose sim 2, I lose network from sim 2, my carrier are Free and Bouygues (France) in roaming with Rogers and Telus (Canada)
Click to expand...
Click to collapse
In case you did the dualsim modifications to the fsg partition (deleting/renaming files) as suggested in the other guide, you need to revert them!
Just flash back the original fsg partition (twrp). Then, erase modemst1/2+cache and reboot...
How I restore the original fsg partition?
chucky91 said:
How I restore the original fsg partition?
Click to expand...
Click to collapse
Get the unmodified fsg.mbn from a recent rom update...
Code:
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
But your guide is my fisrt modification on my moto Z, I never modified nothing before. I revert and reflash but same problem.
I have the lastest bootloader updated with Nougat OTA, the problem can be this?
And the data works for you with the sim 2?
chucky91 said:
I have the lastest bootloader updated with Nougat OTA, the problem can be this?
And the data works for you with the sim 2?
Click to expand...
Click to collapse
You are currently roaming in france with your canadian sim cards is that right? I have no idea how IMEI=0 is handled there in general and perhaps for roaming customers in particular.
From what you are describing it sounds like they are kicking you out just because you're trying to connect with IMEI=0...
Are there any other dualsim-modder aliens roaming in france willing to testify?
Lol i'm roaming in Canada with french sim, yes i think that the imei doesn't allow me to have netorwk when I want to use my data from my sim 2
Thanks. Did manual method on reteu device with latest official software ( NPLS25.86.30-8 ). Dual sim options now available. At the moment I have no second nano sim available, but do not expect any problems as I'm also in Germany.
I put a Sim from Telus and the 2nde sim works when I choose it to use data...The issue is probably the roaming.
chucky91 said:
I put a Sim from Telus and the 2nde sim works when I choose it to use data...The issue is probably the roaming.
Click to expand...
Click to collapse
Thanks for the feedback... that makes you an ideal candidate for testing (Not that I currently have anything for you to test, though)
Currently, we are lucky that dualsim works at all! That may easily change with a non-reversible bootloader update that for instance enforces a more restrictive modem firmware.
The problem you're experiencing is likely connected to the 2nd IMEI showing an invalid number ("0"). A properly configured setup has an ID-block for each sim slot. Since our model is shipped with single-sim configuration, the second ID-block is missing. (I say it again: we are lucky that it generally works at all.. !)
Faking the second ID block would be the next step. However, the data is digitally signed and bound to the processor's serial number. Only those ID blocks with a valid signature are accepted.
In "engineering mode" that signature verfication is/can be skipped. While this was said about a different MOTO phone model, I'd expect that it also applies for our MOTO Z.
If this is true, then this means: a) engineering mode is a bootloader thing, b) the bootloader is allowed to install unsigned modem firmware/data.
However: a) the engineering mode fuse is blown during commercial production. There is no way to officially re-enable engineering mode.
Re: b) the bootloader (aboot) code is available for reverse-engineering, which is good. In the past, there have been possibilities (trust zone kernel exploit).. but moto has done some (non-reversible) patching meanwhile.
Can we duplicate the imei from 1st modem to 2nd modem? And for the restrictions, Actually, i'm using the lastest Bootloader and it works fine !
chucky91 said:
Can we duplicate the imei from 1st modem to 2nd modem? And for the restrictions, Actually, i'm using the lastest Bootloader and it works fine !
Click to expand...
Click to collapse
There is a bit (or rather a number) in the signed(!) data block indicating the sim slot... So no, that doesn't work. (Modifying the data would invalidate the signature and thus get the whole block rejected).
Will this work with moto z play? In a permanent way
Sent from my STV100-1 using Tapatalk
So, as I understand, you need an original dual-sim manufactured mobile phone, but there are nobody who have one... or is afraid to share the IMEI to you, isn't it?
Nevertheless, in addition there is a digital signature which is not easy to analyze... or to understand. Therefore I think there is no way to get a second IMEI into the single-SIM mobile phone
---------- Post added at 01:06 PM ---------- Previous post was at 01:05 PM ----------
benzinerwin said:
There is a bit (or rather a number) in the signed(!) data block indicating the sim slot... So no, that doesn't work. (Modifying the data would invalidate the signature and thus get the whole block rejected).
Click to expand...
Click to collapse
So, as I understand, you need an original dual-sim manufactured mobile phone, but there are nobody who have one... or is afraid to share the IMEI to you, isn't it?
Nevertheless, in addition there is a digital signature which is not easy to analyze... or to understand. Therefore I think there is no way to get a second IMEI into the single-SIM mobile phone
b0mmel said:
So, as I understand, you need an original dual-sim manufactured mobile phone, but there are nobody who have one... or is afraid to share the IMEI to you, isn't it?
Nevertheless, in addition there is a digital signature which is not easy to analyze... or to understand. Therefore I think there is no way to get a second IMEI into the single-SIM mobile phone
Click to expand...
Click to collapse
I've obtained and analyzed such an ID-block. It's linked to the phone's serial number. You would have to change it to your serial number, but changing any tiny bit inside the ID block immediately renders the signature invalid. So there's nothing you can do besides looking for a loophole... (I'm not that confident, though. Research in that matter would require a lot of effort - probably too much for something that works (with IMEI=0) well enough for most/many).
I'm in France actually with 2 french sim cards (no roaming) and it works fine. The first 20min, it didn't work, i has to reboot 4-5 times
Here is a rooting method for the Plam Phone either the US variant or the Vodafone variant this has not been tested or confirmed working on any other device. This root method may break in the future because it is using a tool that isn't designed for the public i tried getting the firehose packaged with the tool to work in other edl flashing tools but was not able to get it working. So this is all we have for now. There is minimal risk in doing this it just has a lot of steps and it requires a pc running windows.
Note: This will wipe your device so anything stored on it will be lost please backup anything important like photos/contacts/etc
Download and install Sugar QCT from here (Be sure to install the usb drivers as well)
Included in the zip is the username and password that you will need to use to run the program please do not post it here.
Boot the device into recovery by turning the device off and then holding the power button until it restarts 3-4 times and boots to recovery
Select the option to go into emergency download mode
Now plug the device into your computer and open Sugar QCT
From the list select pepito/PVG100 (US) or pepito_vdf (Vodafone)
Now select Upgrade this will download the palms firmware package and flash it to the device
When it finishes do not close sugar
Unplug your device and hold the power button for a few minutes so it will restart out of EDL mode, use a rubber band or something to apply pressure to it so you don't have to hold it
Go to where Sugar QCT is installed (C:\Program Files (x86)\SUGAR QCT_SP_Gotu2\bin\)
In there you should see a folder called PVG100-xxxx (The x's are your serial number)
Copy that to your desktop or anywhere else that you like
In the folder, there should be some random looking mbn files these are actually the firmware files just names are randomized to make using them harder.
There should be a file called B1AMD0D0CV00.mbn if not look for a file that starts with a B it will be the boot.img
You will need to push that to an android device and patch it with magisk manager.
Once that is done replace the B1AMD0D0CV00.mbn in your copy of the firmware with the patched boot.img
Boot it back into emergency download mode as previously stated
Close and reopen sugar
Copy your firmware copy back into C:\Program Files (x86)\SUGAR QCT_SP_Gotu2\bin\ be sure it is the same folder structure
Now select your model again and then press the upgrade button in sugar this will now flash your modified firmware to the device.
Once it finishes hold the power button for a few minutes so it will restart out of EDL mode, use a rubber band or something to apply pressure to it so you don't have to hold it
When it restarts and powers up then go through setting the phone up and install magisk manager and you're rooted.
Thanks to @StormSeeker1 for telling me about holding the power button for a few minutes to get out of EDL previously you had to let the phone die to get out of it which is a pain.
Interesting, shall do it tomorrow.
Curious, this doesn't use the root exploit discussed in other threads? Where is (7) downloading from?
snoopy20 said:
Interesting, shall do it tomorrow.
Curious, this doesn't use the root exploit discussed in other threads? Where is (7) downloading from?
Click to expand...
Click to collapse
It doesn't use any root exploit, it's downloading the firmware directly from TCL servers, the tool used is designed for service centers.
If they are the same hardware, it should be possible to flash Vodaphone over the top?
snoopy20 said:
If they are the same hardware, it should be possible to flash Vodaphone over the top?
Click to expand...
Click to collapse
They are signed with different keys, so it will probably cause the device to boot loop and or not startup. I would not recommend trying it.
Is it possible to dump the radio files from an network unlocked device, and use these files to unlock Verizon network.
Any other ideas to unlock network?
Current findings:
1. Remove the Verizon sim warning.
Simply edit the /vendor/build.prop and modify line "ro.product.vzw=true" to false. However, it has a side effect, causing the contacts in dailer FC while browsering.
2. Enable diag, serial and QMI
One method is dialing "###2324#", another approach is launching "EngineerMode" through apps like quickshortcutmaker, then navigate to Connectivity - DiagProtector.
3. Boot animation path
/Vendor/JRD_custres/media/
4. Most garbage apps path
/Vendor /priv-app/
Every time I try to replace the MBN files after being patched the utility keeps redownloading the originals. Any advice?
xswxm said:
Is it possible to dump the radio files from an network unlocked device, and use these files to unlock Verizon network.
Any other ideas to unlock network?
Current findings:
1. Remove the Verizon sim warning.
Simply edit the /vendor/build.prop and modify line "ro.product.vzw=true" to false. However, it has a side effect, causing the contacts in dailer FC while browsering.
2. Enable diag, serial and QMI
One method is dialing "###2324#", another approach is launching "EngineerMode" through apps like quickshortcutmaker, then navigate to Connectivity - DiagProtector.
3. Boot animation path
/Vendor/JRD_custres/media/
4. Most garbage apps path
/Vendor /priv-app/
Click to expand...
Click to collapse
I put my t-mobile sim into mine and it worked fine no edits needed and mine is officially locked to verizon.
kotaKat said:
Every time I try to replace the MBN files after being patched the utility keeps redownloading the originals. Any advice?
Click to expand...
Click to collapse
Are you postive that the folder structure is the same?
deadman96385 said:
I put my t-mobile sim into mine and it worked fine no edits needed and mine is officially locked to verizon.
Are you postive that the folder structure is the same?
Click to expand...
Click to collapse
I am using another carrier, not USA ones, and it has problems with 4G network.
it works, thanks
Just began mind. So far it's stuck on 2%.
Regarding flashing Vodaphone over Verizon, if the ROM files are signed with different keys then modifying the boot.img will surely break the signage?
snoopy20 said:
Just began mind. So far it's stuck on 2%.
Regarding flashing Vodaphone over Verizon, if the ROM files are signed with different keys then modifying the boot.img will surely break the signage?
Click to expand...
Click to collapse
Are you still stuck at 2%? Of downloading, or of flashing?
deadman96385 said:
I put my t-mobile sim into mine and it worked fine no edits needed and mine is officially locked to verizon.
Are you postive that the folder structure is the same?
Click to expand...
Click to collapse
tapa_t said:
Are you still stuck at 2%? Of downloading, or of flashing?
Click to expand...
Click to collapse
Tried flash pvg100e over pvg100, it will stuck at the beginning and the program won't flash.
xswxm said:
Tried flash pvg100e over pvg100, it will stuck at the beginning and the program won't flash.
Click to expand...
Click to collapse
Doesn't that empirically prove that different versions have different signatures, or at least ROM's are different enough to prevent switching over? Maybe we are just so lucky that boot.img is not checked as rigorously.
Is pvg100e for Vodafone? Where did you get the ROM if your device is pvg100?
Does it finish flashing if you do pvg100 over pvg100?
tapa_t said:
Doesn't that empirically prove that different versions have different signatures, or at least ROM's are different enough to prevent switching over? Maybe we are just so lucky that boot.img is not checked as rigorously.
Is pvg100e for Vodafone? Where did you get the ROM if your device is pvg100?
Does it finish flashing if you do pvg100 over pvg100?
Click to expand...
Click to collapse
The tool deadman provided definitely works if u follow the instruction and choose the right version.
For the signature issue, maybe u can find the answer in another thread about temporary root.
As to the version problems, pvg100 is for Verizon.
To my knowledge, the pvg100e is for many other vendors, such as Vodafone, and the UK version maybe share the same model name. There is another version pvg100eu, for European. U can find more evidence in the temporary root thread.
So far the following:
Windows 10 64 - goes to 2% then after a few seconds a 5002 error.
Windows 7 64 inside Virtualbox - goes to 2% and then doesn't move.
I've tried the drivers and others on the web although the latest is around 2014/15.
xswxm said:
The tool deadman provided definitely works if u follow the instruction and choose the right version.
For the signature issue, maybe u can find the answer in another thread about temporary root.
As to the version problems, pvg100 is for Verizon.
To my knowledge, the pvg100e is for many other vendors, such as Vodafone, and the UK version maybe share the same model name. There is another version pvg100eu, for European. U can find more evidence in the temporary root thread.
Click to expand...
Click to collapse
Checked last night, mine, pvg100, is snapdragon 430, and the China mainland version is pvg100c with snapdragon 435.
deadman96385 said:
It doesn't use any root exploit, it's downloading the firmware directly from TCL servers, the tool used is designed for service centers.
Click to expand...
Click to collapse
I'm not looking to root right now, but if I'm understanding this correctly this should mean that I can use SugarQCT to pull the latest version (1AMD) firmware for my Palm that doesn't show any OTA's available and is still on the original 1AGL firmware. Is that correct?
Thanks for making this happen, deadman96385!
tapa_t said:
Doesn't that empirically prove that different versions have different signatures, or at least ROM's are different enough to prevent switching over? Maybe we are just so lucky that boot.img is not checked as rigorously.
Click to expand...
Click to collapse
No need for empirical proof, I did the analysis here.
The difference is: the early part of boot is Qualcomm code using Qualcomm security. These are the "pbl", "sbl/edl" and "aboot/fastboot" programs (and also "modem", "tz" and other bits). These were the parts that I was looking at in the link above.
When "aboot" completes, it hands over to the late part of boot, which is Android code using Google security. These are the "boot.img/Linux kernel" programs, "recovery", "system", "vendor", "data", etc. They use a different security model. That's what this root method targets. You are correct when you say "Maybe we are just so lucky that boot.img is not checked as rigorously".
It does imply that you can mix the PVG100 Qualcomm partitions for "early boot" with the PVG100E Android partitions for "late boot" and vice-versa. But someone with motivation needs to test this... (No, you can't unlock cellular bands this way; the "modem" partition is from Qualcomm and must match your hardware.)
A good diagram is below; Source (and explanation): https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-chains.html -- I recommend studying this article.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ssuds said:
I'm not looking to root right now, but if I'm understanding this correctly this should mean that I can use SugarQCT to pull the latest version (1AMD) firmware for my Palm that doesn't show any OTA's available and is still on the original 1AGL firmware. Is that correct?
Click to expand...
Click to collapse
This should work. Keep in mind that whilst 1AMD seems to be fine, future versions may (permanently) close the vulnerabilities that allow you to get root, modify system partitions or use the current version of SugarQCT. I don't think this will happen but we should all keep the possibility in mind.
Which Windows version are people using? I've tried W10 and also W7 through a virtualbox but with the above errors.
To use volte in unreleased countries where Sony has not released the product, unlock and magisk must be used regardless of firmware.
There is no menu to use VOLTE, but you can force it by modifying the build prop. After that, you can open the Qualcomm Diagnostic Port (qpst, EFS Explorer) and replace the EFS file to use VOLTE.
Unlike xperia 1&5, the corresponding adb shell-su (setprop sys.usb.config rndis,eng_mode,adb) does not work on xperia 1 ii. I'm frustrated. Is the build prop USB item wrong? Does anyone know of a command to activate the Qualcomm Diagnostic Port? :crying:
htcmage said:
To use volte in unreleased countries where Sony has not released the product, unlock and magisk must be used regardless of firmware.
There is no menu to use VOLTE, but you can force it by modifying the build prop. After that, you can open the Qualcomm Diagnostic Port (qpst, EFS Explorer) and replace the EFS file to use VOLTE.
Unlike xperia 1&5, the corresponding adb shell-su (setprop sys.usb.config rndis,eng_mode,adb) does not work on xperia 1 ii. I'm frustrated. Is the build prop USB item wrong? Does anyone know of a command to activate the Qualcomm Diagnostic Port? :crying:
Click to expand...
Click to collapse
It's way more easy. Just flash the right Firmware and it will Work on Stock. I had to use the EU one since EU3 didn't gave me VoLTE or WiFi Calling on My Dual SIM UK/German Model. And it isn't working with GSIs btw. Since SONY implented that stuff differently to what i know. Xiaomi and LG Devices got forced by Me with only build.prop Mods.
Only requirement besides the Firmware will be a Carrier that does also Support it. More isn't needed...
This post records how I combine many tutorials online and finally enable VOLTE and VoWifi on my Realme GT Neo 2 while the toggles are not available at the beginning.
TLDR: Most Realme devices support VOLTE and VoWifi, but the toggles may not be available in countries where Realme is not sold officially. However, they could be enabled by editing the build.prop file. Root and Magisk are necessary. Using Magisk, services like Google Pay can still work properly (price is potentially less security).
As we all know, most Realme devices support VOLTE and VoWifi, and usually you can find and activate them easily in Settings->Mobile network->SIM-> SIM info & settings. There are many tutorials on the website. However, in countries where Realme is not sold officially, you may not find these 2 toggles. I'm not sure about the exact reason but some are saying that local operators have strict whitelist policy (like ATT and TMobile), and of course a device sold only overseas won't be on it.
My situationI bought a Chinese version Realme GT Neo 2 and the bands are compatible with Tmobile 4G (link). After getting the phone, I refer to this post to flash the global version firmware. My operator is Mint, a mvno of Tmobile and I cannot find VOLTE or VoWifi toggles. After reading this post and using an app called ForceLTE, I'm able to use 4G data. But whenever I make a phone call, the signal jumps back to 3G and data becomes H+(HSDPA). Recently Mint sent me a message, saying that they are retiring 3G soon and my device is not compatible. After a certain date, my phone will not be able to make/receive phone calls if still relying on 3G.
IMEM check fails on Tmobile, Mint, and ATT websites.
On Xiaomi devices there's a code used to activate VOLTE directly, on Oneplus devices you can use log app, but no similar way can be found for Realme devices.
This method I find could be applied to other Realme devices in other countries when the toggles are not available in SIM info & settings.
DisclaimerPlease try the posts I mentioned first.
This method requires root. Take your own risk for any of your behaviors.
I'm not responsible for any of your losses (including, but not limited to device, finance, data, personal info)
Device infoRealme GT Neo 2 chinese version
Global version firmware (RMX3370_11_C.02) via TWRP
Bootloader locked after flashing the firmware
Steps1. Unlock the bootloader (refer to this post). Attention: unlock will get all data wiped!
2. Install TWRP (refer to this post) and Magisk (refer to this post).
Attention: even after you flash TWRP.img to the recovery partition, if you keep using stock firmware (no matter what region/version), recovery will go back to stock one after the first time you boot to the system. You'll have to install Magisk (or use 3rd party firmware) to keep TWRP
3. Install MagiskHide props config (refer to this post) to allow us to edit the build.prop file. It is in system partition (ext4, read-only), and can no longer be edited directly (even if you try to remount it in TWRP or ZArchiver with -rw).
4. Install a terminal emulator from google playstore. Android is a linux system, imagine this app as a window you can open on your PC with linux to input commands.
5. In the emulator,
5.1 type "su" and enter
5.2 type "props" and enter
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5.3 type "5" and enter (Add/edit custom props)
5.4 type "n" and enter (New custom prop)
5.5 type "persist.dbg.ims_volte_enable" and enter (the prop we want to add)
5.6 type "1" and enter (enter your desired option)
5.7 type "y" and enter (Enter y(es), n(o), e(xit) or an option from above)
5.8 type "n" and enter (do you want to reboot now)
5.9 repeat step 5.3-5.8 for the following props:
persist.dbg.ims_volte_enable, type "1" in step 5.6
persist.dbg.volte_avail_ovr, type "1" in step 5.6
persist.dbg.vt_avail_ovr, type "1" in step 5.6
persist.dbg.wfc_avail_ovr, type "1" in step 5.6
persist.radio.rat_on, type "combine" in step 5.6
persist.radio.data_ltd_sys_ind, type "1" in step 5.6
persist.radio.data_con_rprt, type "1" in step 5.6
persist.radio.calls.on.ims, type "1" in step 5.6
In step 5.8 after you finish entering the last prop, type "y" and enter (reboot now)
6. After reboot, check whether 2 toggles are there in Settings->Mobile network->SIM-> SIM info & settings
7. If you still want to properly use apps like Google Pay after root, refer to this post
Test if VOLTE and 4G network work1. In settings->Notifications & status bar->Status icons, make sure you turn on VoLTE, VoWiFi and Mobile network
2. If you are connected to a wifi and VoWifi works, you should see a small wifi sign above telephone sign in status bar, like this
In addition, for Tmobile, in Settings->Mobile network->SIM1, the Carrier is shown as T-Mobile Wi-Fi Calling (for mvno like mint, don't forget to turn it on on mint website->personal settings first).
3. Disconnect the wifi, you should see "4G" above the network sign, as well as VoLTE sign in the status bar. Turn on data, make a phone call (such as voicemail), minimize the window, check if "4G" sign is still there. Finally, with the call going on, try openning a website like Google. If "4G" sign is there during the whole process, congratulations!
Let me know if this works for you, or if you have any questions/suggestions. Thanks!
Worked for me thanks. Couldn't get volte registered on network. But I now have my toggles.
andrew202 said:
Worked for me thanks. Couldn't get volte registered on network. But I now have my toggles.
Click to expand...
Click to collapse
Hi, thanks for the reply and it's good to hear that. I just updated the steps to check VoWifi and VoLTE, do they work for you? If not, try this post (developer options + ForceLTE) and reboot.
darkhunter9 said:
Hi, thanks for the reply and it's good to hear that. I just updated the steps to check VoWifi and VoLTE, do they work for you? If not, try this post (developer options + ForceLTE) and reboot.
Click to expand...
Click to collapse
No my ims status is not registered. I spoke with my isp telus. Basically device not on list I won't get volte to work. So guessing the only option is some sort of spoofing.
andrew202 said:
No my ims status is not registered. I spoke with my isp telus. Basically device not on list I won't get volte to work. So guessing the only option is some sort of spoofing.
Click to expand...
Click to collapse
Please do not give up hope. Using MagiskHide props you can even change your device name (RMX3370). Probably one plus device would be a good choice to fake.
GOOD JOB! I have a rmx3366, Realme GT Explorer Master Edition with the original chinese version firmware(RMX3366_11_A.16), realme UI v2.0. Do you think I can follow your steps without flashing the global version firmware?
I will be ready to go with Tmobile 2g for voice/text otherwise.
piapiapia said:
GOOD JOB! I have a rmx3366, Realme GT Explorer Master Edition with the original chinese version firmware(RMX3366_11_A.16), realme UI v2.0. Do you think I can follow your steps without flashing the global version firmware?
I will be ready to go with Tmobile 2g for voice/text otherwise.
Click to expand...
Click to collapse
Yes I believe the method should work for most Realme devices, even with UI 2.0.
If you have your bootloader unlocked, feel free to give it a try without flashing global firmware. All properties you set in MagiskHide props config are reversible. Start from step 2.
If your bootloader is still locked, the unlocking process will wipe all data anyway (for personal info security). For a better chance, I suggest to flash the global firmware. I'm not sure whether Chinese version firmware has any restriction (software side) on specific 4G bands used by carrier in US/other countries.
darkhunter9 said:
Yes I believe the method should work for most Realme devices, even with UI 2.0.
If you have your bootloader unlocked, feel free to give it a try without flashing global firmware. All properties you set in MagiskHide props config are reversible. Start from step 2.
If your bootloader is still locked, the unlocking process will wipe all data anyway (for personal info security). For a better chance, I suggest to flash the global firmware. I'm not sure whether Chinese version firmware has any restriction (software side) on specific 4G bands used by carrier in US/other countries.
Click to expand...
Click to collapse
It is helpful! Thank you! My phone does not have a global version, but it works well with Tmobile so far except the volte part. I will try on the Chinese stock firmware.
piapiapia said:
It is helpful! Thank you! My phone does not have a global version, but it works well with Tmobile so far except the volte part. I will try on the Chinese stock firmware.
Click to expand...
Click to collapse
Did a little bit search and it seems what you said is a sad truth. Good luck bro!
help me i have followed you but its not successful
Phan Đức Nam said:
help me i have followed you but its not successful
Click to expand...
Click to collapse
Sorry can you please provide some more info or description?
darkhunter9 said:
Xin lỗi, bạn có thể vui lòng cung cấp thêm một số thông tin hoặc mô tả được không?
Click to expand...
Click to collapse
my neo2 bought in china, i have moved my rom to russia (a.02) and some other versions are not working
Phan Đức Nam said:
my neo2 bought in china, i have moved my rom to russia (a.02) and some other versions are not working
Click to expand...
Click to collapse
Did you do step 5? I didn't see "(active)" behind your "5 - Add/edit custom props". So basically, these props are not added to magisk successfully. In addition, in your screenshot I see 5G signal available. If that's the case there's really no need to worry about 4G VOLTE.
darkhunter9 said:
Did you do step 5? I didn't see "(active)" behind your "5 - Add/edit custom props". So basically, these props are not added to magisk successfully. In addition, in your screenshot I see 5G signal available. If that's the case there's really no need to worry about 4G VOLTE.
Click to expand...
Click to collapse
I did step 5 it didn't work so it failed, my 5G icon is Theme only
Phan Đức Nam said:
I did step 5 it didn't work so it failed, my 5G icon is Theme only
Click to expand...
Click to collapse
Maybe check firmware starting with C and RUI3 then. Sorry I cannot provide a solid solution.
darkhunter9 said:
Maybe check firmware starting with C and RUI3 then. Sorry I cannot provide a solid solution.
Click to expand...
Click to collapse
I am in RUI 3 C.06 RU region but still not working
Phan Đức Nam said:
I am in RUI 3 C.06 RU region but still not working
Click to expand...
Click to collapse
As I said, somehow these custom props are not added to your Magisk successfully, as 5 is not active in your screenshot.
I haven't done any of the steps, but the weird thing is, is VoLTE enabled by default?
I use Google Phone instead of built-in call app, and it shows HD next to the numbers. Does it mean VoLTE is enabled?
My model is RMX3370, Chinese version, running Realme UI 3.0, RMX3370_11_C.08
JohnVo said:
I haven't done any of the steps, but the weird thing is, is VoLTE enabled by default?
I use Google Phone instead of built-in call app, and it shows HD next to the numbers. Does it mean VoLTE is enabled?
My model is RMX3370, Chinese version, running Realme UI 3.0, RMX3370_11_C.08
View attachment 5666647
Click to expand...
Click to collapse
Not necessarily. The best way to check is if you are on a call check if you can still access the internet using mobile data. Without VoLTE, the modem shifts to 3G/2G, and you can't use mobile data simultaneously.
Hey XDA,
I felt obliged to contribute since the following steps worked for me and I got VoLTE and WiFi Calling switches in settings in my Realme GT Neo 2 global version RMX3370 that is on Freedom Mobile in Canada.
All factory, no root required, no bootloader unlock required.
May work on other Realme models.
Source: https://realme-gadgetlife.net/how-to-enable-volte/ (in Japanese, I used Google Translate). I can't remember where I found this link, all credits go to where they are due.
Steps, check pictures in the above link:
1. Enable Developers Options and USB Debugging (search online if needed)
2. Connect your phone to a Windows laptop
3. On the phone choose connection type Transfer files / Android Auto
(first time you will be prompted on your phone if you want to allow USB connection from this PC, choose Yes)
4. On the laptop install platform tools, open a command prompt and change directory to where they are installed
5. Enter command "adb devices"
6. The output should say:
List of devices attached
<your realme serial number> device
7. Enter command: "adb reboot fastboot"
8. The phone will enter the fastboot mode and display language selector. No need to do anything on the phone.
9. Enter command: "fastboot reboot recovery"
10. Nothing changes on the phone, no need to touch it this time either
11. Enter command: "adb devices"
12. The output will be:
List of devices attached
<your realme serial number> recovery
Here I installed realme Software&Driver Update tool from
Software Update - realme (India)
Update the latest software version on your realme phone.
www.realme.com
This may help if you're having issues at this step.
13. Enter the commands listed below ONE BY ONE. For some reason they didn't work when I entered them all together.
adb shell setprop persist.data.iwlan.enable true
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.dbg.wfc_avail_ovr 1
adb shell setprop persist.radio.rat_on combine
adb shell setprop persist.radio.data_ltd_sys_ind 1
adb shell setprop persist.radio.data_con_rprt 1
adb shell setprop persist.radio.calls.on.ims 1
adb shell setprop persist.data.iwlan 1
adb shell setprop persist.data.iwlan.ipsec.ap 1
adb shell setprop persist.radio.volte.dan_support true
adb shell setprop persist.radio.VT_ENABLE 1
adb shell setprop persist.sys.cust.lte_config true
adb shell setprop persist.rcs.supported 1
adb reboot
14. The phone reboots and the VoLTE and WiFi Calling switches are there in Settings - Mobile Networks - <SIM> !
Note that I am not saying that your phone will display VoLTE or VoWiFi in the notification area but at least the switches (options) become available in settings
Thanks to the authors of the page above!