Hi Guys
So, as you all know, Quick capture is disabled in devices connected to an Indian network and this had me pissed off for a very long time.
I looked into the Emergency Affordance Service which is responsible for identifying Indian SIMs and found a way to disable it (at least on the 5t).
But a word first.
DISCLAIMER: The Govt of India has stated that it is mandatory for all phone manufacturers to add this functionality for the right reasons. By disabling the feature you will NOT be able to use the triple-press power button for emergency call. I do not take responsibility for any damage caused due to the actions described in this post.
Alright, lets jump into it.
Step 1. Install a terminal emulator app (or connect via adb shell)
Step 2. Enter the following command without quotes:
"settings put global emergency_affordance_needed 0"
(You may use the "settings get global emergency_affordance_needed" command to confirm if it worked.)
Step 3. Check the OnePlus Camera app - the Quick capture option should be there.
Step 4. Profit!?
Notes:
My 5t was rooted with magisk, but I ran the command on a normal ($) prompt so I'm not sure if this requires root or not. Please try it on unrooted devices and let me know so I can update this post accordingly. Also, I haven't checked if it persists after a reboot.
Not working on non rooted device.
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
abhishek0704 said:
Not working on non rooted device.
Click to expand...
Click to collapse
dsjd said:
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
Click to expand...
Click to collapse
Yeah even I saw that it goes back to normal even without a reboot.
The EmergencyAffordanceService periodically scans the MCC of the SIM and sets that value to 1 if the MCC is 404 or 405.
So I tried spoofing the MCC in many different ways, but none of them worked for me.
This section of the config file sets the list of the MCC codes for which EmergencyAffordance is enabled.
Code:
<!-- Do not translate. Mcc codes whose existence trigger the presence of emergency
affordances-->
<integer-array name="config_emergency_mcc_codes" translatable="false">
<item>404</item>
<item>405</item>
</integer-array>
If we can somehow modify this array, I think it should be permanently disabled. But I guess that would require an Xposed module or apk editing (areas I know nothing about)
There are other methods I'm sure, maybe one involving an Xposed module which hooks the method that checks for the MCC codes and makes it return false.
If anyone has any ideas, please do chime in.
any idea how the phone detects that its india? Could we spoof that?
Failure transaction error in OB2 even after su command.
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Failure calling service settings: Failed transaction (2147483646)
zeeshanonlyme said:
Failure transaction error in OB2 even after su command.
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Failure calling service settings: Failed transaction (2147483646)
Click to expand...
Click to collapse
Use ADB shell instead of doing in on your phone
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Edit: Found It
https://www.reddit.com/r/oneplus/comments/6ur1ma/double_tap_power_button_setting/
The devs name is Mishaal Rahman ...Maybe he could help us out.
abhishek0704 said:
Not working on non rooted device.
Click to expand...
Click to collapse
dsjd said:
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
Click to expand...
Click to collapse
dsjd said:
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Click to expand...
Click to collapse
I've (kind of) figured out a few ways to resolve this, but not the implementation part.
This Xposed module should be able to solve the issue by making the method check return false, but I cant seem to get the module working on my device.
Anyone with Xposed, could you see if the module is working for you? It FCs whenever I open it.
dsjd said:
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Click to expand...
Click to collapse
I've (kind of) figured out a few ways to resolve this, but not the implementation part.
This Xposed module should be able to solve the issue by making the method check return false, but I cant seem to get the module working on my device.
Anyone with Xposed, could you see if the module is working for you? It FCs whenever I open it.
Sorry for bumping an old thread but has anybody figured out how do get this working permanently with xposed or magisk ? I bought a OP6 and miss this feature coming from a Nokia 7+
MAGISK Module!
Hi,
Was able to create a magisk module to do this automatically every boot and also got wifi auto turn on to work, check out the thread here.
kashyapha1994 said:
Yeah even I saw that it goes back to normal even without a reboot.
The EmergencyAffordanceService periodically scans the MCC of the SIM and sets that value to 1 if the MCC is 404 or 405.
So I tried spoofing the MCC in many different ways, but none of them worked for me.
This section of the config file sets the list of the MCC codes for which EmergencyAffordance is enabled.
Code:
<!-- Do not translate. Mcc codes whose existence trigger the presence of emergency
affordances-->
<integer-array name="config_emergency_mcc_codes" translatable="false">
<item>404</item>
<item>405</item>
</integer-array>
If we can somehow modify this array, I think it should be permanently disabled. But I guess that would require an Xposed module or apk editing (areas I know nothing about)
There are other methods I'm sure, maybe one involving an Xposed module which hooks the method that checks for the MCC codes and makes it return false.
If anyone has any ideas, please do chime in.
Click to expand...
Click to collapse
Might be possible to override this with an overlay (non-root Substratum.)
Hello, Just a small hack that allows me to use the VoLTE that my provider points out is "only available on handsets purchased directly from them" (SFR in France). This got me thinking ==> If VoLTE works on their handsets and not mine then :
a) The carrier infrastructure supports VoLTE
b) The sim cards must be provisioned correctly
c) The difference would therefore be in the telephone configuration ==> I'm thinking build.prop config in their "special firmware"
So looking through various forums - I came across the following:
https://forums.oneplus.com/threads/root-working-volte-on-stock-oxygen-3-1-0.480128/, https://forum.xda-developers.com/apps/magisk/module-v4-volte-enabler-t3649613 and https://source.android.com/devices/tech/config/carrier (to help understand what IMS is all about)
Here's what I added to the end of my build.prop [you will need root for this]:
Code:
#VoLTE - force the IMS into VoLTE provisioned mode on.
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
If you don't want to do that directly in the build.prop you can do this directly from a debug shell
Code:
adb shell
$ su
# setprop persist.dbg.ims_volte_enable 1
# setprop persist.dbg.volte_avail_ovr 1
# reboot
Please note that this did indeed allow me to make/receive calls and use 4G at the same time.
I also see "HD 4G" logo appear to the left of my signal bars.
When I look at my phone config (dial *#*#4636#*#*) I see VoLTE as provisioned.
I think that these lines force the phone to use VoLTE - the risk is that this might break your 4G - you have been warned. I don't guarantee that this works for you.
Can an administrator place this in the https://forum.xda-developers.com/mi-a2/how-to forum please ?
I made this change with temporary root when i activated api for gcam, put this lines with temporary root and get OTA too
if yuou don't have root you can use *#*#86583#*#* . tested working on sfr too.
Tried that but that didn't work... This root build.prop stuff did... I have also added keys for video calling and VoWiFi but until I see those working I'm not keen to publish...
duxxyuk said:
Tried that but that didn't work... This root build.prop stuff did... I have also added keys for video calling and VoWiFi but until I see those working I'm not keen to publish...
Click to expand...
Click to collapse
VoWifi how? Whats the code?
I've got these lines on the back of my build.prop but it doesn't appear to work for me:
Code:
#WiFi calling
persist.data.iwlan.enable=true
persist.dbg.wfc_avail_ovr=1
rober788 said:
I made this change with temporary root when i activated api for gcam, put this lines with temporary root and get OTA too
Click to expand...
Click to collapse
How does a temporary root work? I can't find anything with Google.
Magisk module VoEnableer maybe the best chois.
Thanks for sharing.. it also works on mi a2 lite
Thanks, It works
Many people have had this question in mind.
Tech is there to use it (source: gsmarena, sc below)
but why im not able to use it?
Has anyone been able to enable it with root access?
Seems to work here. Stock 9.0, only used ADB to enable VoLTE and remove carrier check.
I believe it's more a carrier side to support it.
justanpotato said:
Many people have had this question in mind.
Tech is there to use it (source: gsmarena, sc below)
but why im not able to use it?
Has anyone been able to enable it with root access?
Click to expand...
Click to collapse
RoSk0BoSk0 said:
Seems to work here. Stock 9.0, only used ADB to enable VoLTE and remove carrier check.
I believe it's more a carrier side to support it.
Click to expand...
Click to collapse
Which command did you use to enable VoLTE via ADB?
_mysiak_ said:
Which command did you use to enable VoLTE via ADB?
Click to expand...
Click to collapse
You need temporary root for them, there are many guides for that.
This goes after successful "adb shell"
Code:
$su
#setprop persist.dbg.ims_volte_enable 1
#setprop persist.dbg.volte_avail_ovr 1
#setprop persist.dbg.vt_avail_ovr 1
#setprop persist.dbg.wfc_avail_ovr 1
Other threads suggest these too, but haven't done them. I've had network fluctuations with them, but YMMV.
Code:
#setprop persist.radio.rat_on combine
#setprop persist.radio.data_ltd_sys_ind 1
#setprop persist.radio.data_con_rprt 1
#setprop persist.radio.calls.on.ims 1
Credits to: @ToucanSam [MODULE v17.x] VoLTE & VoWiFi Enabler (2018-09-20)
RoSk0BoSk0 said:
Seems to work here. Stock 9.0, only used ADB to enable VoLTE and remove carrier check.
I believe it's more a carrier side to support it.
Click to expand...
Click to collapse
My carrier supports it. But for some odd reason its not working at all.
My previous phone s6edge+ had no problems with connecting to my carrier LTE-A network.
Any ideas ?
((EDIT))
Its working now
I was planning to get a new phone with a great display, and that was exactly when RP2 went on sale. I'm otherwise satisfied with the phone, but single SIM is definitely a deal breaker in China. Given that I could not find any other phone matching my criteria, I decided to get the RP2 and tried to enable dual SIM on it. Till now I've had some success, and here is what I have done.
If you have strong demand for dual SIM like I do, you may try these steps. This thread, however, is NOT a proper nor complete guide on this topic. It is just a record of my trials - they are highly experimental, risky, and potentially broken. There is absolutely no guarantee on signal quality, stability, power consumption or even the success rate. Your device can be permanently damaged if any detail goes wrong. Make sure you understand all the risks and you are able to justify every command before typing it to your phone!
I do appreciate suggestions for the correct way, though. Comments are greatly welcomed!
My environment
QPST 2.7.477 - only PDC is used here, so any version with standalone PDC tool might do the job. But new versions required if you want to use other tools.
QXDM Professional 3.14.1144 - this one is optional. It's used to tweak some parameters, but dual SIM does work without the tweaks.
Qualcomm USB drivers 2.1.2.0 from 2015/7/8 - older versions might work as well.
Windows 10, 1803
arter97's kernel and Magisk-patched stock kernel images readily at hand. The latter can be obtained by patching a stock kernel image in Magisk Manager with "Keep dm-verity/avb 2.0" UNTICKED. I had the latter installed on the phone.
Make sure root shell can be obtained during boot with ALL kernel images. This is an important recovery approach if the phone bootloops.
Steps
I've gone through a tricky path to confirm that there is indeed a second IMEI in the phone prior to the steps, which supported follow-up researching. This thread will not cover this part as this is merely trial-and-error. I will provide suggestions on diag connection though.
1. make a backup of all partitions on the phone, leaving out system, vendor and userdata partitions of course. There are 88 partitions in my backup.
2. make a QCN backup of modem NV. This step could be optional as modemst1/2 has already been backed-up in previous step - I'm not sure about this, and have completed this step whatsoever.
3. make a backup of /vendor/etc/vintf/manifest.xml, and add slot2 instances to the following HALs:
android.hardware.radio - this one has 2 interfaces, and both of them need the slot2 addition
vendor.qti.hardware.radio.am
vendor.qti.hardware.radio.qtiradio - this one has 2 versions, and both of them need the slot2 addition
4.
Code:
adb shell su -c setprop persist.radio.multisim.config dsds
5. find any USB mode with rmnet in /vendor/etc/init/hw/init.msm.configfs.rc, and switch to it. I used "diag,serial_cdev,rmnet,dpl,adb", and that's
Code:
adb shell su -c setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb
6. Windows shows a lot of new USB devices. Force-install Qualcomm WWAN driver for the RmNet device. I chose "Network Adapters -> Qualcomm -> Qualcomm HS-USB WWAN Adapter 90B8", but anything named after "Qualcomm HS-USB WWAN Adapter" should do.
7. open PDC. There are 3 dual SIM (DSDS) hardware profiles available:
SR_DSDS-LA-7+7_mode-SDM845
SR_DSDS-WD-7+7_mode-SDM845
SR_DSDS-WP8-7+7_mode-SDM845
The one with WP8 in its name can be ignored, and here comes the hard choice.
I tried the WD one in the first place: activated it in the context menu on Sub0 then Sub1, and clicked Activate twice. PDC complained about malformed packet after second click, and the profile was shown as Active on Sub0, and Pending on Sub1. Nothing bad happened after a reboot, regardless of the errors above. Two SIM slots were present in About Phone, and second IMEI is correctly shown there as well. Upon inserting two SIM cards I got dual VoLTE online, and everything behaved like a normal dual SIM SDM845 device. There were some little glitches though: once or twice a day signal bars disappeared and popped up again in a few seconds. Mobile data also stuttered at random times, though not frequent - sometimes mobile data was stable for the whole day. I was satisfied with the results, and made another backup of partitions.
Then I started comparing the WD and LA profiles. I quickly realized that LA marked the phone as DSDS while WD as SS in the device_mode NV entry (I honestly had no idea why dual SIM just worked with WD). There were other differences unknown to me, but LA seemed more "correct" and I decided to switch to this profile. After deactivating WD on both Sub0 and Sub1, I activated LA on Sub0 but not Sub1. The phone could still make use of two SIMs, but without VoLTE on either card. LTE was still available for both cards though. The glitches with WD were mostly gone (data still stuttered but recovered much faster), and the phone SEEMED cooler and battery SEEMED to drain slower.
Finally I could not understand the lack of VoLTE and switched back to WD (still Sub0 only). This time only the first SIM card could register on IMS/VoLTE. The second one registered on LTE but not IMS, regardless of default data card selection. Activating WD on Sub1 did not solve the problem. Manual checks/corrections on the differences between WD and LA made no effect either. I had to flash the backup made after first WD trial, and dual VoLTE worked again.
I came to the following conclusion after this step:
a. hardware profiles may be applied to Sub0 only (can anyone confirm this?)
b. a profile may not be completely reverted after applying. That is to say, same profile status does not mean same baseband behavior.
c. LA profile does not support VoLTE for some reason.
d. if you want dual VoLTE, your best bet would be activating WD on Sub0 and Sub1 right after previous steps, though Sub1 won't accept the setting.
e. mobile data may stutter with dual SIM (this could also be the fault of my service provider however)
Any clarification on this step is appreciated. If you want to enable dual SIM, you have to make your own choice here. Just remember to backup before every change.
8. apply some NV changes from LA on WD base:
ue_usage_setting: from DATA_CENTRIC to VOICE_CENTRIC
device_mode: from SS to DSDS
disable_global_mode: from 1 to 0
I failed to find any difference after these changes. this step could be optional. I myself use the phone as daily driver with these changes though.
That's all. Don't worry, I'm confused as you Everything just works or fails without any valid reason
Other Details
1. RP2 uses the same SIM card slot as Samsung. I filed an card tray from Samsung S7 so that it fits RP2. Its size naturally() fits RP2, just make it as thin as Razer's tray and it will work.
2. if you want to restore a modemst1/2 backup, do that in TWRP. If this needs to be done in Android system, stop vendor.rmt_storage first.
3. if the phone reboots to recovery right after booting to lock screen, this could be SIM count in baseband and system diverging. Run
Code:
adb shell su -c setprop persist.radio.multisim.config ss
during boot to see if this fixes the problem. If it does, restore all backups then start all over.
4. QPST does not recognize the diag port from the phone upon USB connection. Do this so that diag port works:
Code:
# in adb shell, assuming USB mode has already been switched
su
setenforce 0
stop vendor.per_mgr
# wait a few sec until QPST recognizes SDM845 on the diag port
start vendor.per_mgr
# SDM845 disappears and re-appears after a few sec, and QPST is usable
5. arter97's kernel disables diag drivers, and QPST could never recognize the phone. You have to use stock kernel if you intend to use anything other than PDC.
Screenshots and photos:
Screenshot of About Phone:
{
"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"
}
Screenshot of dual VoLTE:
Photos of the filed card tray inside RP2:
The original Samsung tray:
And after filing:
Reserved for minor fixes
that's interesting
i have tried this, but the second imei doesn't appears what am I doing wrong?
ps: i find second imei in QCN backup
IMG
I finally got it
i updated to rom deodexed and zipalign from Warrior1988
after that I looked at the settings, the second Imei appeared
then I put sim card, android recognizes then it worked
PS: i modded SIM Card with MicroSD, now i have dual SIM with MicroSD :laugh:
IMG
unfortunately, now i see this message on starting, but starts normally (don't shutdown) :victory:
IMG
Update: you can remove this with command
reboot "dm-verity enforcing"
Hey man! What sim card tray did you use and how did you modify it for dual SIM and sdcard?
Using a command to reverify the DM will get rid of the red text and boot
th3cavalry said:
Hey man! What sim card tray did you use and how did you modify it for dual SIM and sdcard?
Using a command to reverify the DM will get rid of the red text and boot
Click to expand...
Click to collapse
I did this method, and used default sim card tray
and thanks for command
So I'm stuck at step 7. I have the both SIM slots showing in the phone but no IMEI for SIM2. When I open PDC it doesn't show anything.
When we add the slot2, do we add slot1,slot2 or do we add a whole nother line in the file for slot2?
Did you have any issues with PDC in the beginning?
updateing said:
I was planning to get a new phone with a great display, and that was exactly when RP2 went on sale. I'm otherwise satisfied with the phone, but single SIM is definitely a deal breaker in China. Given that I could not find any other phone matching my criteria, I decided to get the RP2 and tried to enable dual SIM on it. Till now I've had some success, and here is what I have done.
If you have strong demand for dual SIM like I do, you may try these steps. This thread, however, is NOT a proper nor complete guide on this topic. It is just a record of my trials - they are highly experimental, risky, and potentially broken. There is absolutely no guarantee on signal quality, stability, power consumption or even the success rate. Your device can be permanently damaged if any detail goes wrong. Make sure you understand all the risks and you are able to justify every command before typing it to your phone!
I do appreciate suggestions for the correct way, though. Comments are greatly welcomed!
My environment
QPST 2.7.477 - only PDC is used here, so any version with standalone PDC tool might do the job. But new versions required if you want to use other tools.
QXDM Professional 3.14.1144 - this one is optional. It's used to tweak some parameters, but dual SIM does work without the tweaks.
Qualcomm USB drivers 2.1.2.0 from 2015/7/8 - older versions might work as well.
Windows 10, 1803
arter97's kernel and Magisk-patched stock kernel images readily at hand. The latter can be obtained by patching a stock kernel image in Magisk Manager with "Keep dm-verity/avb 2.0" UNTICKED. I had the latter installed on the phone.
Make sure root shell can be obtained during boot with ALL kernel images. This is an important recovery approach if the phone bootloops.
Steps
I've gone through a tricky path to confirm that there is indeed a second IMEI in the phone prior to the steps, which supported follow-up researching. This thread will not cover this part as this is merely trial-and-error. I will provide suggestions on diag connection though.
1. make a backup of all partitions on the phone, leaving out system, vendor and userdata partitions of course. There are 88 partitions in my backup.
2. make a QCN backup of modem NV. This step could be optional as modemst1/2 has already been backed-up in previous step - I'm not sure about this, and have completed this step whatsoever.
3. make a backup of /vendor/etc/vintf/manifest.xml, and add slot2 instances to the following HALs:
android.hardware.radio - this one has 2 interfaces, and both of them need the slot2 addition
vendor.qti.hardware.radio.am
vendor.qti.hardware.radio.qtiradio - this one has 2 versions, and both of them need the slot2 addition
4.
Code:
adb shell su -c setprop persist.radio.multisim.config dsds
5. find any USB mode with rmnet in /vendor/etc/init/hw/init.msm.configfs.rc, and switch to it. I used "diag,serial_cdev,rmnet,dpl,adb", and that's
Code:
adb shell su -c setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb
6. Windows shows a lot of new USB devices. Force-install Qualcomm WWAN driver for the RmNet device. I chose "Network Adapters -> Qualcomm -> Qualcomm HS-USB WWAN Adapter 90B8", but anything named after "Qualcomm HS-USB WWAN Adapter" should do.
7. open PDC. There are 3 dual SIM (DSDS) hardware profiles available:
SR_DSDS-LA-7+7_mode-SDM845
SR_DSDS-WD-7+7_mode-SDM845
SR_DSDS-WP8-7+7_mode-SDM845
The one with WP8 in its name can be ignored, and here comes the hard choice.
I tried the WD one in the first place: activated it in the context menu on Sub0 then Sub1, and clicked Activate twice. PDC complained about malformed packet after second click, and the profile was shown as Active on Sub0, and Pending on Sub1. Nothing bad happened after a reboot, regardless of the errors above. Two SIM slots were present in About Phone, and second IMEI is correctly shown there as well. Upon inserting two SIM cards I got dual VoLTE online, and everything behaved like a normal dual SIM SDM845 device. There were some little glitches though: once or twice a day signal bars disappeared and popped up again in a few seconds. Mobile data also stuttered at random times, though not frequent - sometimes mobile data was stable for the whole day. I was satisfied with the results, and made another backup of partitions.
Then I started comparing the WD and LA profiles. I quickly realized that LA marked the phone as DSDS while WD as SS in the device_mode NV entry (I honestly had no idea why dual SIM just worked with WD). There were other differences unknown to me, but LA seemed more "correct" and I decided to switch to this profile. After deactivating WD on both Sub0 and Sub1, I activated LA on Sub0 but not Sub1. The phone could still make use of two SIMs, but without VoLTE on either card. LTE was still available for both cards though. The glitches with WD were mostly gone (data still stuttered but recovered much faster), and the phone SEEMED cooler and battery SEEMED to drain slower.
Finally I could not understand the lack of VoLTE and switched back to WD (still Sub0 only). This time only the first SIM card could register on IMS/VoLTE. The second one registered on LTE but not IMS, regardless of default data card selection. Activating WD on Sub1 did not solve the problem. Manual checks/corrections on the differences between WD and LA made no effect either. I had to flash the backup made after first WD trial, and dual VoLTE worked again.
I came to the following conclusion after this step:
a. hardware profiles may be applied to Sub0 only (can anyone confirm this?)
b. a profile may not be completely reverted after applying. That is to say, same profile status does not mean same baseband behavior.
c. LA profile does not support VoLTE for some reason.
d. if you want dual VoLTE, your best bet would be activating WD on Sub0 and Sub1 right after previous steps, though Sub1 won't accept the setting.
e. mobile data may stutter with dual SIM (this could also be the fault of my service provider however)
Any clarification on this step is appreciated. If you want to enable dual SIM, you have to make your own choice here. Just remember to backup before every change.
8. apply some NV changes from LA on WD base:
ue_usage_setting: from DATA_CENTRIC to VOICE_CENTRIC
device_mode: from SS to DSDS
disable_global_mode: from 1 to 0
I failed to find any difference after these changes. this step could be optional. I myself use the phone as daily driver with these changes though.
That's all. Don't worry, I'm confused as you Everything just works or fails without any valid reason
Other Details
1. RP2 uses the same SIM card slot as Samsung. I filed an card tray from Samsung S7 so that it fits RP2. Its size naturally() fits RP2, just make it as thin as Razer's tray and it will work.
2. if you want to restore a modemst1/2 backup, do that in TWRP. If this needs to be done in Android system, stop vendor.rmt_storage first.
3. if the phone reboots to recovery right after booting to lock screen, this could be SIM count in baseband and system diverging. Run
Code:
adb shell su -c setprop persist.radio.multisim.config ss
during boot to see if this fixes the problem. If it does, restore all backups then start all over.
4. QPST does not recognize the diag port from the phone upon USB connection. Do this so that diag port works:
Code:
# in adb shell, assuming USB mode has already been switched
su
setenforce 0
stop vendor.per_mgr
# wait a few sec until QPST recognizes SDM845 on the diag port
start vendor.per_mgr
# SDM845 disappears and re-appears after a few sec, and QPST is usable
5. arter97's kernel disables diag drivers, and QPST could never recognize the phone. You have to use stock kernel if you intend to use anything other than PDC.
Click to expand...
Click to collapse
th3cavalry said:
So I'm stuck at step 7. I have the both SIM slots showing in the phone but no IMEI for SIM2. When I open PDC it doesn't show anything.
When we add the slot2, do we add slot1,slot2 or do we add a whole nother line in the file for slot2?
Click to expand...
Click to collapse
PDC works for me from the beginning. Please check:
1. Did you install the correct driver for the RmNet device?
2. There is a combo box in PDC window with nothing selected by default. Could you choose HS-USB WWAN Adapter in its dropdown list?
th3cavalry said:
So I'm stuck at step 7. I have the both SIM slots showing in the phone but no IMEI for SIM2. When I open PDC it doesn't show anything.
When we add the slot2, do we add slot1,slot2 or do we add a whole nother line in the file for slot2?
Click to expand...
Click to collapse
for me the second IMEI only worked after I installed this https://forum.xda-developers.com/razer-phone-2/development/rom-mr1-stock-deodexed-zipalign-t3916502
and to PDC work i used this driver https://androidfilehost.com/?fid=11410963190603864074
Wait, so... Even though this is a single-SIM phone, it has a second IMEI in it, and the hardware to read a second SIM? All they had to do to make this officially dual-SIM was make a slightly different SIM tray and change the hardware profile?
Gamesoul Master said:
Wait, so... Even though this is a single-SIM phone, it has a second IMEI in it, and the hardware to read a second SIM? All they had to do to make this officially dual-SIM was make a slightly different SIM tray and change the hardware profile?
Click to expand...
Click to collapse
Maybe they need more resources to fine tune dual SIM experiences (if they have not given up the plan for this variant). For example modem could crash when IMS registration states change on both slots simultaneously (this is why my signal bars disappear from time to time), and radio performance could be drastically degraded when two slots are registered on different bands. Making a product market-ready takes much more resources than making in happen in lab, and Razer might not want to invest that much in this area.
updateing said:
Maybe they need more resources to fine tune dual SIM experiences (if they have not given up the plan for this variant). For example modem could crash when IMS registration states change on both slots simultaneously (this is why my signal bars disappear from time to time), and radio performance could be drastically degraded when two slots are registered on different bands. Making a product market-ready takes much more resources than making in happen in lab, and Razer might not want to invest that much in this area.
Click to expand...
Click to collapse
Makes sense. I suppose I shouldn't trivialize the process. It mostly just surprises me that the hardware (and some of the software) is there at all. They must have had plans to do dual-SIM up until almost the last minute, because otherwise I can't imagine why they wouldn't save the money needed to put that extra hardware in there. And I can't imagine they'll release any such thing at this point. They basically shut down their mobile phone division, and haven't even released a software update in months.
hey guys..
enabling diag is workig on android 8.1.? it was using on pie but didnt work on oreo...anyone faced wtih this pb..?
Code:
aura:/ $ su
aura:/ # setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb
aura:/ #
---------- Post added at 02:27 PM ---------- Previous post was at 02:10 PM ----------
t-mobile_mda said:
hey guys..
enabling diag is workig on android 8.1.? it was using on pie but didnt work on oreo...anyone faced wtih this pb..?
Code:
aura:/ $ su
aura:/ # [B]setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb[/B]
aura:/ #
Click to expand...
Click to collapse
i think it is not working on oreo..tried again on pie and worked again...
Code:
C:\Users\X\Desktop\Razer\Phone_2\Root\8.1>adb shell
aura:/ $ su
aura:/ # [B]setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb[/B]
C:\Users\X\Desktop\Razer\Phone_2\Root\8.1>
hey again guys..
can anyone pls sahre the modemst parts..? single sim or dual it doesnt metter..
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst2 -> /dev/block/sdf3
dd if=/dev/block/sdf2 of=/sdcard/sdf2
dd if=/dev/block/sdf3 of=/sdcard/sdf3
w.b.r.
What are the chances of breaking my phone with these steps?
Just like anything else, trial and error.
So does this kill WiFi calling?
I tried this and I jacked it up a bit. i got it to get both SIMs working (TMOUS and KT). The WiFi calling for TMOUS stopped working and also if I went to "Mobile Data" it reset the radio and never opened the menu. So i tried to revert and it got stuck in a boot loop and when i did get in the cell was completely not working, No sim, no IMEI. Luckily i flashed an older ROM (shipped 8.1MR0) and progressively upgraded through the ROMs from there and have service again. This tells me that the Stock Razer Images from their developer site don't have 'everything' for a full restore.
t-mobile_mda said:
hey again guys..
can anyone pls sahre the modemst parts..? single sim or dual it doesnt metter..
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst2 -> /dev/block/sdf3
dd if=/dev/block/sdf2 of=/sdcard/sdf2
dd if=/dev/block/sdf3 of=/sdcard/sdf3
w.b.r.
Click to expand...
Click to collapse
Grab the Stock ROM for your version then extract it: https://developer.razer.com/razer-phone-dev-tools/factory-images/
All of them have "modem.img" used in there flash script in this command:
Code:
%fastboot_cmd% flash modem_a modem.img
%fastboot_cmd% flash modem_b modem.img
I don't think this works on 9MR2
Hello everyone!
Finally I've find way to turn on Volte and Wifi calling back on 11.3.4 and 11.4.5!
When i bought the phone on the stock version i had aviability to turn on VoLte and WifiCalling, but after 2 updates - 11.3.4 and 11.4.5, dont why this options gone.
Little guide how to bring back this option on your phone:
1. Use this app "Apk Extractor" to backup your currently Logkit
(https://play.google.com/store/apps/details?id=com.ext.ui&hl=pl&gl=US)
2. Download this version of Logkit: https://drive.google.com/file/d/1bQYKY6tI5O37yXVyXpFYdOHIvMB9iuMt/view
3. Now, open the dialer app and dial *#800# to access the menu.
4. Scroll down and tap the Function switch option and turn on VoLte and WiFi calling.
5. Reboot phone
6. Check Sim & Network option
7. After that reinstal your backup Logkit!
https://imgur.com/a/Yqtn2tt
I do now have the option to turn on wifi calling! However when I toggle it on, it does not stay on. KB05AA on Verizon wireless.
Thanks now I can see mine and it's already on?
Can someone upload the backup of the original apk. I kinda didn't do that. Lol thanks I'm advance. Also mine doesn't stick either. I am on verizon as well.
cameljockey1 said:
Can someone upload the backup of the original apk. I kinda didn't do that. Lol thanks I'm advance. Also mine doesn't stick either. I am on verizon as well.
Click to expand...
Click to collapse
-Michael_ said:
I do now have the option to turn on wifi calling! However when I toggle it on, it does not stay on. KB05AA on Verizon wireless.
Click to expand...
Click to collapse
Sorry guys, but I don't know your operator.
On the stock have you vo and wifi?
Do you have the backed up log kit apk? Can you send it to me please.
Anyone get this working with Verizon?
cameljockey1 said:
Do you have the backed up log kit apk? Can you send it to me please.
Click to expand...
Click to collapse
Here's mine.
cameljockey1 said:
Can someone upload the backup of the original apk. I kinda didn't do that. Lol thanks I'm advance. Also mine doesn't stick either. I am on verizon as well.
Click to expand...
Click to collapse
You can just look for it in the apps, make sure you press "show system app" and after you found the logkit, press "Uninstall updates"
Sent from my unknown using Tapatalk
i already have this option in my mobile v2001, i activated but its not working for some reason, i guess it needs Qualcomm driver update just like op 7..
meshal300 said:
i already have this option in my mobile v2001, i activated but its not working for some reason, i guess it needs Qualcomm driver update just like op 7..
Click to expand...
Click to collapse
You can also activate VoLTE by changing MBN with Qualcomm PDC like OP5/6/7 but you must be rooted now
Follow the guide here
Download archive, read the pdf, it's in french but you have screenshots for explaination, if you have some questions, quote me
It can be usefull just for using software with your parameters / Carrier
hi, i don't find logkit apk in apk extractor. however I displayed the system applications
have an idea why?
i tired to enable volte and vowifi and both are enabled but still no volte or vowifi on my old phone it worked fine same sim in th e8t and its not working any ideas?
Thanks for this. Just tried and I now have the WiFi calling option and it works fine (for Vodafone UK).
Funny thing is even when I reinstall the extracted (backed up) logkit it still doesn't revert to the original one. Uninstalling updates also does revert back but it fine. I can't imagine there's any harm in using the downloaded one.
After upgrading to OOS12 this method is not working any more.. Does anybody have a new solution to get volte vowifi back?
tiuro said:
After upgrading to OOS12 this method is not working any more.. Does anybody have a new solution to get volte vowifi back?
Click to expand...
Click to collapse
In OOS12 and ColorOS12 access to logkit and engineering mode were somewhat hidden by developers.
The easiest way to access toggles is obtained with root access and Magisk.
Just install attached module. Enable VoLTE and VoWiFi toggles.
Thank you! Works flawlessly!
Any help activating VOLTE for un-rooted 8T KB2003 running KB2003_11_c.36 please?
eslonim said:
Any help activating VOLTE for un-rooted 8T KB2003 running KB2003_11_c.36 please?
Click to expand...
Click to collapse
Without root it's quite complicated because on OOS12&13 access to engineering mode via dialer code is disabled.
[GUIDE] Fix/Enable 5G and DSS
Enable 5G and DSS on OnePlus 8T As you may or may not know OnePlus didn't add proper changes into EFS configs to allow us use 5G on every network in the world. This guide will help you unlock 5G access and DSS (Dynamic Spectrum Sharing) and...
forum.xda-developers.com
Secrecy unlock
WARNING - THIS (ORIGINAL) METHOD IS NOT WORKING WARNING - BE CAREFULL REGARDING (your) IMEI SHARING ! You need to enable Developer Options and USB Debugging in the Phone Download the Oppo_Free_Unlock_v1.0.zip Secrecy Auto Unlocker : Open the...
forum.xda-developers.com
Rootk1t said:
Without root it's quite complicated because on OOS12&13 access to engineering mode via dialer code is disabled.
[GUIDE] Fix/Enable 5G and DSS
Enable 5G and DSS on OnePlus 8T As you may or may not know OnePlus didn't add proper changes into EFS configs to allow us use 5G on every network in the world. This guide will help you unlock 5G access and DSS (Dynamic Spectrum Sharing) and...
forum.xda-developers.com
Secrecy unlock
WARNING - THIS (ORIGINAL) METHOD IS NOT WORKING WARNING - BE CAREFULL REGARDING (your) IMEI SHARING ! You need to enable Developer Options and USB Debugging in the Phone Download the Oppo_Free_Unlock_v1.0.zip Secrecy Auto Unlocker : Open the...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks - I will try that. Also I read elsewhere to check with carrier that VOLTE turned on for my account