Related
For those who use any official MIUI release (be it Global or Chinese, Stable or Dev):
Download your GSI of preference from Treble-compatible Devices Development section of XDA to your PC. Make sure you download an ARM64 A-only version.
In TWRP on your phone, hit Wipe and then Format Data and confirm it with typing „yes”
Connect your phone in fastboot mode to your PC
Open the command prompt in the folder where your fastboot.exe is located
Type: fastboot flash system path_to_your_GSI.img (Tip: you can also type fastboot flash system and drag and drop it on the command prompt window)
Type: fastboot reboot
The device should reboot to your freshly installed GSI.
For those who use xiaomi.eu ROM: (YMMV, it worked for me so I put it here, see below if it doesn't work for you)
Download your GSI of preference from Treble-compatible Devices Development section of XDA to your PC. Make sure you download an ARM64 A-only version.
Download vendor.img from here to your PC. You can also use any official vendor.img provided in official Xiaomi fastboot firmware packages if you know what you’re doing.
In TWRP on your phone, hit Wipe and then Format Data and confirm it with typing „yes”
Connect your phone in fastboot mode to your PC
Open the command prompt in the folder where your fastboot.exe is located
Type: fastboot flash system path_to_your_GSI.img (Tip: you can also type fastboot flash system and drag and drop it on the command prompt window)
Type: fastboot flash vendor path_to_your_vendor.img (you can drag and drop as well)
Type: fastboot reboot
Alternate, easier (and preferred) way:
Download and flash any official MIUI release like this one here
Follow instructions for official MIUI releases above
The device should reboot to your freshly installed GSI.
How to pass SafetyNet on GSI:
Download the latest Magisk 16.6 and flash it through TWRP
Reboot
In Magisk Manager app, open the side menu and tap Download
Download MagiskHide Props Config, install it and reboot
After reboot, go to Setting and Developer Options and enable Terminal app, right under ADB debugging option
A Terminal app should appear in your apps list. If not, you can also use any terminal emulator app from Play Store
Type „su”, hit enter and grant root permissions
Type „props” and hit enter
Type „1”, hit enter
Type „f”, hit enter
Type „11”, hit enter
Type „7”, hit enter
Type „y”, hit enter
Type „y”, hit enter and your device will reboot
If you care about auto-brightness (which i bet you do), you can also set the module manually to Mi MIX 2S fingerprint:
Follow steps 1-9 from above
Type:
Code:
Xiaomi/polaris/polaris:8.0.0/OPR1.170623.032/V9.5.19.0.ODGMIFA:user/release-keys
and hit enter (thanks @cnrd for the tip!)
Type "y", hit enter
Type "y", hit enter and your device will reboot
After booting successfully, your device will pass SafetyNet, you can check it in Magisk Manager. Tested on my Chinese (XE model) device with the latest Resurrection Remix official GSI, Google Pay is working fine.
Using the Mi 6 ctsProfile kills the background light (at least on phh-treble), use the Mi Mix 2S profile instead:
Code:
Xiaomi/polaris/polaris:8.0.0/OPR1.170623.032/V9.5.19.0.ODGMIFA:user/release-keys
cnrd said:
Using the Mi 6 ctsProfile kills the background light (at least on phh-treble), use the Mi Mix 2S profile instead:
Code:
Xiaomi/polaris/polaris:8.0.0/OPR1.170623.032/V9.5.19.0.ODGMIFA:user/release-keys
Click to expand...
Click to collapse
Added, thanks!
Great tutorial, thank you very much!
Has anyone tried this with the latest pixel experience gsi? Resurrection Remix is running fine but pixel experience always reboots to the fastboot screen.
I used the instructions from the pixel experience thread, but without success. I read the whole thread again and again and did it step by step as mentioned to be sure not to miss any important steps. Not luck.
Can you try it with the Mix2S and confirm that it works and how you it?
Don't want to capture this thread. I'm just desperately trying to get this done to boot.
Best regards
Kleinholzinferno
Thanks for the explain.
Is the OP using this method on a different device? I don't recall seeing any ROMs for the Mix 2S.
napes22 said:
Thanks for the explain.
Is the OP using this method on a different device? I don't recall seeing any ROMs for the Mix 2S.
Click to expand...
Click to collapse
OP is using a Treble ROM. If you go to the Treble section of XDA, there's a bunch of ROMs that will work for the 2s. Instead of flashing a device specific zip file you can flash a generic image file that will work on any phone that supports treble, like the Mi Mix 2s.
This guide walks you through flashing those images, and getting Magisk to work on the 2s.
russphil said:
OP is using a Treble ROM. If you go to the Treble section of XDA, there's a bunch of ROMs that will work for the 2s. Instead of flashing a device specific zip file you can flash a generic image file that will work on any phone that supports treble, like the Mi Mix 2s.
This guide walks you through flashing those images, and getting Magisk to work on the 2s.
Click to expand...
Click to collapse
Thanks, although I had upgraded the Beta to 8.7.10, so probably won't be flashing anything until a workaround comes along. I'm waiting for someone to confirm if it's only for Redmi Note 5.
Thank you for the tutorial, maybe you could add the fact that you have to use the fastboot.exe from miflash.
I´ve used the Minimal ADB and Fastboot Files but they make write Errors and the Rom won´t boot.
Hope I could try this method on my Mi 6X, will report back once I can unlock my Bootloader.
marcii-ec said:
Thank you for the tutorial, maybe you could add the fact that you have to use the fastboot.exe from miflash.
I´ve used the Minimal ADB and Fastboot Files but they make write Errors and the Rom won´t boot.
Click to expand...
Click to collapse
I've done it through Minimal ADB and Fastboot on Windows and through Fastboot on macOS and both work fine.
napes22 said:
Thanks, although I had upgraded the Beta to 8.7.10, so probably won't be flashing anything until a workaround comes along. I'm waiting for someone to confirm if it's only for Redmi Note 5.
Click to expand...
Click to collapse
You can check it if you reboot to Fastboot and see if "fastboot getvar anti" returns anything. If it does, your device has anti-rollback protection enabled.
As far as I know, anti-rollback is enabled on MIX 2S from 8.7.16 onwards, so you should be safe.
woofwoof75 said:
Hope I could try this method on my Mi 6X, will report back once I can unlock my Bootloader.
Click to expand...
Click to collapse
If your device is Treble-compatible, it should work with no problems, however keep in mind that should you run into any issues when using the provided fingerprint, you have to look up some from a stable MIUI for your device.
teddy74eva said:
You can check it if you reboot to Fastboot and see if "fastboot getvar anti" returns anything. If it does, your device has anti-rollback protection enabled.
As far as I know, anti-rollback is enabled on MIX 2S from 8.7.16 onwards, so you should be safe.
Click to expand...
Click to collapse
Yeah, when I run "fastboot getvar anti" I get invalid variable. Which leads me to believe that I don't have any issues at the moment. I won't upgrade from 12, but I'd like to move to Treble at some point.
EDIT: Just checked the "flash_all.bat" file within the 8.7.12 file and saw the following
::set CURRENT_ANTI_VER=1
::for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i)
::if [%version%] EQU [] set version=0
::if %version% GTR %CURRENT_ANTI_VER% (
Click to expand...
Click to collapse
Looks like 8.7.12 for Mi Mix 2S is not screwed.
Hello fellow gsi users. I'm new to this props editing thing and wanted to ask two questions for noobs.
If I follow the terminal commands in the OP the device fingerprint shows Xiaomi Mi 6 8.0.0 right? Is this right to use for the MiMix2S? I think so otherwise it wouldn't be mentioned to use.
And i don't understand the command for the auto brightness. What exactly does this do? Enable the automatic brightness settings from the original rom?
Need advice please. Maybe there's a thread that I haven't found yet that explains this topic. I'm eager to get more information but all I found was too general and not the answers I was looking for.
kleinholzinferno said:
Hello fellow gsi users. I'm new to this props editing thing and wanted to ask two questions for noobs.
If I follow the terminal commands in the OP the device fingerprint shows Xiaomi Mi 6 8.0.0 right? Is this right to use for the MiMix2S? I think so otherwise it wouldn't be mentioned to use.
And i don't understand the command for the auto brightness. What exactly does this do? Enable the automatic brightness settings from the original rom?
Need advice please. Maybe there's a thread that I haven't found yet that explains this topic. I'm eager to get more information but all I found was too general and not the answers I was looking for.
Click to expand...
Click to collapse
Basically, setting your fingerprint to Mi6 8.0 fools Google's checks of your installed system's certification, telling them that you are currently running a certified and tested Mi6 firmware. Every firmware has to follow Google's standards and rules for it to be able to fully use Google Services.
Now, I've included Mi6 fingerprint in my guide because it's readily available in MagiskHide Props, thus making it easier to set everything up to a workable state. However, as one user mentioned, if you use Mi6 fingerprint on MIX 2S, it breaks autobrightness. So, in order to be fully certified and keep autobrightness working, you can manually enter a fingerprint provided in the first post, which comes from MIX 2S 8.0 firmware. The only downside is that you have to be careful not to make any mistake when typing, so it's a little bit harder.
If you can live without autobrightness (since, as of now, it's terribly slow), feel free to use the Mi6 preset fingerprint. If you care or if you want to do things as they should be done, go for the manual route. Both of them will make your device Google certified and both of them will allow you to pass SafetyNet checks.
I may generalized some things or not mention them due to my lack of knowledge. If anybody would like to correct something, please do so
P.S. I may completely delete the preset fingerprint guide, as I don't think it's that hard to enter the proper fingerprint manually and it would definitely make things clearer.
Thank you very much for this information, makes everything much clearer for me.
Regarding auto brightness: I don't mind if it works for now, I can live with the manual settings. Better than a laggy auto settings thingy that doesn't worm properly.
The only thing that bothers me is that the screen is much too bright at night (or with night light activated) even in the lowest setting. Is there any possibility to change the minimum value?
Could you explain how to enter the proper fingerprint manually?
Best regards
Edit: nevermind the last question, I found it. In the newer version there's an entry for the mi mix 2s. Xiaomi devices are now listed under number 12, not 11 and the mi mix 2s is listed as own device. Works perfectly fine! Safety net passed, all green now!
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 is a temporary solution to a pending pull request. This thread will be deprecated if or when the official release is updated.
I don't have the original signing key, but there is really no reason to attempt reverse engineering an app that's open source. Instead, it is signed with one of my own "Google Play certified" keys. Changes are below for anyone that would rather build and sign the application locally.
The caveat to using a different key is that the unofficial version cannot be installed directly over the official and vice versa.
Pull Request
Do not hardcode su binary path by AbandonedCart · Pull Request #3 · HomerSp/AsusVoLTE
This fixes an issue where rooted devices are not recognized (#2)
github.com
Original Source
GitHub - HomerSp/AsusVoLTE: Enable VoLTE/VoWiFi on the ROG Phone 2
Enable VoLTE/VoWiFi on the ROG Phone 2. Contribute to HomerSp/AsusVoLTE development by creating an account on GitHub.
github.com
Thanks a lot for your update.
I made some progress.
App is working perfectly, triggered the USB PDC mode as well. (Which I couldn't do earlier).
The older versions we used were not detecting the device.
Got the new QPST from here
The latest driver I could find was from here
Still stuck at exactly here;
{
"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"
}
The guide I follow is the one which worked for me on the ROGII - Which is here. Didnt require any MBN flashing, as I have a global device and just needed to use the existing VoWiFI Profile.
Any ideas on how to resolve the connection issue?
Maybe there are newer drivers?
EDIT:
Some information here shows PDC doesnt work anymore.
Thread
JazonX said:
EDIT:
Some information here shows PDC doesnt work anymore.
Thread
Click to expand...
Click to collapse
PDC has been replaced with EfsTool, according to that (and other) threads.
[Guide]Activate VoLTE/VoWiFi OOS 11(OB1&OB2)
Hi everyone. /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following * these directions. YOU are...
forum.xda-developers.com
The thread I referenced in the Australia version of the VoLTE threads covers setup a little better for the specific use. Downloads are available in both.
[Guide] Enabling VoLTE/VoWiFi v2
Preface With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier...
forum.xda-developers.com
twistedumbrella said:
PDC has been replaced with EfsTool, according to that (and other) threads.
[Guide]Activate VoLTE/VoWiFi OOS 11(OB1&OB2)
Hi everyone. /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following * these directions. YOU are...
forum.xda-developers.com
The thread I referenced in the Australia version of the VoLTE threads covers setup a little better for the specific use. Downloads are available in both.
[Guide] Enabling VoLTE/VoWiFi v2
Preface With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks a lot, Made it through to the EFS Tools guide.
Did the mod to the EFSToolsdllconfig, Matched Ports.
Currently stuck here, Will keep you updated of the progress.
EDIT:
Tested with my ROG II and the command is working, So it's unable to read the ROG 5 for some mysterious reason.
I would test, but VoLTE works out of the box for Tencent / T-Mobile. No use trying to break it, especially if it's meant to survive updates / firmware.
At the point of giving up.
Stuck here;
and also I noticed that the Driver detection page keeps refreshing.
So I assume that neither of the tools we use are compatible with the ROG 5 yet, as they all link and work properly with my ROG II.
[Guide] activate Volte on Android 11 (root)
Finally I got it working on ww_30.40.30.96 on German carrier O2. I used most of the Guide from @HomerSp : https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/ requirements: adb for PC QPST latest EFS Tools from JohnBel...
forum.xda-developers.com
GitHub - JohnBel/EfsTools: Command line tools for Qualcomm EFS file system
Command line tools for Qualcomm EFS file system. Contribute to JohnBel/EfsTools development by creating an account on GitHub.
github.com
Not sure if any of that is a solution, but it seems to be the next suggestions
twistedumbrella said:
[Guide] activate Volte on Android 11 (root)
Finally I got it working on ww_30.40.30.96 on German carrier O2. I used most of the Guide from @HomerSp : https://forum.xda-developers.com/t/guide-enabling-volte-vowifi-v2.4028073/ requirements: adb for PC QPST latest EFS Tools from JohnBel...
forum.xda-developers.com
GitHub - JohnBel/EfsTools: Command line tools for Qualcomm EFS file system
Command line tools for Qualcomm EFS file system. Contribute to JohnBel/EfsTools development by creating an account on GitHub.
github.com
Not sure if any of that is a solution, but it seems to be the next suggestions
Click to expand...
Click to collapse
Thanks a lot for the responses;
(And thank you for your patience)
Here are my findings;
* The new EfsTools app is sorta broken, because it doesnt SIM Slot #2 Changes - Someone already reported it.
* Android 11 seems to block the PDC function, hence no ADB command can trigger it. However somehow your version of the AsusVoLTE app on first post here forcefully enters the Phone to PDC mode. This is a win, however the Device Manager keeps refreshing every second - so no connection can be made. I'm using Qualcomm Driver 1.0061 which seems to be the latest. I have used older .37 / .40 drivers as well, nothing changes the "frequent refresh" behavior.
* Not sure how this guy managed to get the ADB command to work on Android 11 in Zenfone, I tested it with both USB ports, multiple cables.. Nothing seems to trigger anything.
The code he suggested is
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
* OnePlus folks have the same issue and they have managed to enable PDC support by taking the phone to Field Test Mode via "ADB reboot FTM" command. This doesnt work for asus. OnePlus Method.
* I tried putting the phone in EDL mode, however this doesn't enable any Diag or PDC port, it seems its only for flashing. So far I have no clue whether any engineering or FTM mode exists on Asus.
* Many forums have *#*# codes - I think I have tried all of them, none of them seems to make any new option appear in sim menus.
So .. still. No VoLTE, and therefore no 5G either.
If you have any ideas / guides I can try .. Much appreciated!
Enabling Diagnostic Mode
I wanna enable the diagnostic mode and try to see if i can add more LTE bands through QPST. I tried the generic command through adb shell and its not working:( Any suggestions are welcome.
forum.xda-developers.com
Looks like it might be repeat information, though.
twistedumbrella said:
Enabling Diagnostic Mode
I wanna enable the diagnostic mode and try to see if i can add more LTE bands through QPST. I tried the generic command through adb shell and its not working:( Any suggestions are welcome.
forum.xda-developers.com
Looks like it might be repeat information, though.
Click to expand...
Click to collapse
Thanks a lot once again,
Both the suggested codes have no effect. Tried with SU, without SU, without spaces..
Nothing triggers any any new drive installation.
So far, Only your App's (Fixed Asus VoLTE) Enable PDC function can enable this Port. However it doesn't stick, as it keeps refreshing every 2 seconds (probably causing efs tools not to detect the port). QPST can see the port, but doesnt identify what device it is.
I tried a module which allows SeLinux to go permissive, thinking that might help. Almost hard bricked as this has no TWRP. Luckily the combination of Magisk removal code, stock boot image, and safe mode helped me out.
Damn, never thought I'd struggle this much to get 5G working.
Anyone come up with anything recent that works? Struggling with Rog 5 to enter Diag mode and so forth.
Vojtek12 said:
Anyone come up with anything recent that works? Struggling with Rog 5 to enter Diag mode and so forth.
Click to expand...
Click to collapse
You can enter diag mode using this commands
Inline links are only good when they save space for a reference that most readers may not be interested in reading
jbm76 said:
Install these usb drivers - https://gsmusbdriver.com/category/xiaomi/page/3
These are the commands -
Both of these work.
adb shelll,
su
setprop sys.usb.config diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
Either setprop command will work.
setprop sys.usb.config rndis,diag,diag_mdm,diag_mdm2,qdss,qdss_mdm,serial_cdev,dpl
In regards to the VOLTE issue still no go on A11 - I have been able to access the EFS partition but the ims_user_agent won't stick even if I write to it with in EFS explorer of EFs tools, it doesn't survive a reboot.
Click to expand...
Click to collapse
JazonX said:
Thanks a lot once again,
Both the suggested codes have no effect. Tried with SU, without SU, without spaces..
Nothing triggers any any new drive installation.
View attachment 5393765
So far, Only your App's (Fixed Asus VoLTE) Enable PDC function can enable this Port. However it doesn't stick, as it keeps refreshing every 2 seconds (probably causing efs tools not to detect the port). QPST can see the port, but doesnt identify what device it is.
I tried a module which allows SeLinux to go permissive, thinking that might help. Almost hard bricked as this has no TWRP. Luckily the combination of Magisk removal code, stock boot image, and safe mode helped me out.
Damn, never thought I'd struggle this much to get 5G working.
Click to expand...
Click to collapse
I'm facing same issue as u now, the driver page keep refreshing every 2 seconds. Can u tell ur solutions pls. Tks mate!
LinhBT said:
I'm facing same issue as u now, the driver page keep refreshing every 2 seconds. Can u tell ur solutions pls. Tks mate!
Click to expand...
Click to collapse
Never found a solution. Tried a lot and asked a lot around here and eventually got rid of the phone.
JazonX said:
Never found a solution. Tried a lot and asked a lot around here and eventually got rid of the phone.
Click to expand...
Click to collapse
My ROG 5S is now in a very weird situation while both SIM is working, baseband is there, but no IMEI ( but still can make and receive phone call, sms....etc ). Also, can't unlock bootloader since it has no IMEI
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!
Can someone please make a custom rom for oppo a5s i'm begging
i tried like 10 gsi roms and none of them worked properly
Because GSI ROMs require Android supports Project Treble, have you checked phone supports Project Treble?
Using ADB simply type the following command:
Code:
adb shell "getprop ro.treble.enabled"
It will return a boolean value, true if your device supports Treble and false if it doesn't.
jwoegerbauer said:
Because GSI ROMs require Android supports Project Treble, have you checked phone supports Project Treble?
Using ADB simply type the following command:
Code:
adb shell "getprop ro.treble.enabled"
It will return a boolean value, true if your device supports Treble and false if it doesn't.
Click to expand...
Click to collapse
when i said worked properly i meant being stable because i know my phone is treble supported a only system and i tried many os like arrowos, havocos, phh aosp (10-9-8.1) but they all crash a lot and a lot of hardware does not work like fingerprint and face unlock and the brightness is at max 50%
If you flash a GSI ROM all OEM / vendor specific files ( the drivers ) are missing by default, hence you must not be surprised that a lot of hardware isn't working as expected.
jwoegerbauer said:
If you flash a GSI ROM all OEM / vendor specific files ( the drivers ) are missing by default, hence you must not be surprised that a lot of hardware isn't working as expected.
Click to expand...
Click to collapse
yea that's why it kinda disappointing
i was trying to make the gsi rom recognize the hardware but i couldn't find a solution