This is what I had to do to fix the Unknown caller ID issue with 4G Calling enabled in the respective SIM settings:
Installed QPST Tool on my computer.
With USB debugging enabled in Developer Settings and Magisk for root access, enabled DIAG mode using adb:
Code:
$ adb shell
surya:/ $ su
surya:/ # setprop sys.usb.config diag,serial_cdev,rmnet,adb
In QPST >> PDC activated the respective profile for Sub0 and Sub1 and removed the originally automatically chosen profile (otherwise it kept reversing the desired setting on reboot).
Checked status with *#*#INFO#*#*.
Can this be done without root, I'm having the same issue on a Meizu device without root access & don't have a option to disable VoLTE
TheInfiniteAndroid said:
Can this be done without root, I'm having the same issue on a Meizu device without root access & don't have a option to disable VoLTE
Click to expand...
Click to collapse
If on an original ROM, there should be a way to access a service menu where you can switch on the diag mode that's necessary to be able to use PDC by using the phone dialer.
You may want to search for how to enable diag mode for your device (on my previous OnePlus with OxygenOS firmware it was somthing like *#*#801#*#* or *#*#808#*#*).
Master One said:
If on an original ROM, there should be a way to access a service menu where you can switch on the diag mode that's necessary to be able to use PDC by using the phone dialer.
You may want to search for how to enable diag mode for your device (on my previous OnePlus with OxygenOS firmware it was somthing like *#*#801#*#* or *#*#808#*#*).
Click to expand...
Click to collapse
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
TheInfiniteAndroid said:
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
Click to expand...
Click to collapse
Do you happen to know if there's a way to find it through Activity Manager, finding it hard to navigate
@TheInfiniteAndroid, sorry, can't help with this, don't know Activity Manager.
Hi, I have switched my profiles on my Mi 8 to DT_Greece to activate VoWiFi and deleted the original ROW_Commercial profile.
Whenever a call is getting through VoWiFi or VoLTE i still get unknown caller ID.
Do you perhaps have any other idea to fix that?
razenxd said:
Hi, I have switched my profiles on my Mi 8 to DT_Greece to activate VoWiFi and deleted the original ROW_Commercial profile.
Whenever a call is getting through VoWiFi or VoLTE i still get unknown caller ID.
Do you perhaps have any other idea to fix that?
Click to expand...
Click to collapse
You may want to try another profile in that case, as there is no other way to solve this.
Master One said:
You may want to try another profile in that case, as there is no other way to solve this.
Click to expand...
Click to collapse
Aah really? That sux
Ι've tried more than the half configs listed and only DT_greece seems to enabling VoWiFi for Vodafone Greece carrier
razenxd said:
Aah really? That sux Ι've tried more than the half configs listed and only DT_greece seems to enabling VoWiFi for Vodafone Greece carrier
Click to expand...
Click to collapse
Indeed, sucks if not working, but I have no other idea. Try the second half of configs as well, maybe there is one that just works with your carrier.
Master One said:
Indeed, sucks if not working, but I have no other idea. Try the second half of configs as well, maybe there is one that just works with your carrier.
Click to expand...
Click to collapse
That's what i'm doing at the moment.
No luck so far
On RN10 Pro my carrier works just fine, I already have extracted the .mbns from RN10 Pro's firmware but now i need to find which one is actually is using and a way to insert it to my device!
Master One said:
This is what I had to do to fix the Unknown caller ID issue with 4G Calling enabled in the respective SIM settings:
Installed QPST Tool on my computer.
With USB debugging enabled in Developer Settings and Magisk for root access, enabled DIAG mode using adb:
Code:
$ adb shell
surya:/ $ su
surya:/ # setprop sys.usb.config diag,serial_cdev,rmnet,adb
In QPST >> PDC activated the respective profile for Sub0 and Sub1 and removed the originally automatically chosen profile (otherwise it kept reversing the desired setting on reboot).
Checked status with *#*#INFO#*#*.
Click to expand...
Click to collapse
Thanks for posting on this, but what do you mean by qpst>>pdc? When I run qpst I see no active devices, pdc doesn't either. So no clue how to proceed.
treebaard said:
Thanks for posting on this, but what do you mean by qpst>>pdc? When I run qpst I see no active devices, pdc doesn't either. So no clue how to proceed.
Click to expand...
Click to collapse
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after connecting?
Master One said:
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after
Master One said:
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after connecting?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yes, up to the step of my phone being recognized, as it isn't automatically recognized at all by qpst config. And since there is no faq of any kind on what to do if the phone isn't recognized by QPST, I'm stuck.
I presume the issue is that I don't see any ports listed in the ports view. But I installed the Qualcomm usb driver already, so not sure how to fix that
per https://forum.xda-developers.com/t/rom-11-lineageos-official-surya-karna.4202533/post-85746887 , did you fix this in LOS 17.1, or 18?
treebaard said:
per https://forum.xda-developers.com/t/rom-11-lineageos-official-surya-karna.4202533/post-85746887 , did you fix this in LOS 17.1, or 18?
Click to expand...
Click to collapse
I'm not a developer and I can't really help as I'm not currently using LOS. You may want to find out if DIAG mode is supported and working in LOS.
TheInfiniteAndroid said:
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
Click to expand...
Click to collapse
PDC you will find it in the folder with the installed program QPST.
I did it. Sorry for my English.
Master One said:
I'm not a developer and I can't really help as I'm not currently using LOS. You may want to find out if DIAG mode is supported and working in LOS.
Click to expand...
Click to collapse
Another user said this procedure worked with LOS 17.1, but not 18.1 which we now run. I don't see a new device added in windows task manager, so I guess something's changed, and the QPST folks need to look into it.
treebaard said:
Another user said this procedure worked with LOS 17.1, but not 18.1 which we now run. I don't see a new device added in windows task manager, so I guess something's changed, and the QPST folks need to look into it.
Click to expand...
Click to collapse
The QPST folks have nothing to do with this, maybe (I mean hopefully) @gardiol can comment on DIAG mode support in the current version of LOS.
Can this have anything to do with the MUIU vs. OSS vendor?
I'm still running an older version of ArrowOS with the MIUI vendor, but possibly the DIAG mode problem came up with the move to OSS vendor?
Related
After I seen two threads regarding QPST/CDMA Workshop, I decided to give it a try too.
However, I had the problem with drivers, which I luckily solved.
Drivers source: http://catalog.update.microsoft.com...updateid=14df499c-c71f-4152-a63b-1c1e40cfc14c
So, here's the solution for everyone:
1. Unzip the attached archive.
2. adb shell, su, echo 1 > /sys/devices/virtual/usb_composite/modem/enable
3. Open Device Manager. Under unknown devices you'll find two "SEMC HSUSB" devices.
4. For both, install drivers from the folder.
You'll get unsigned driver warning, ignore and continue with installation.
5. Reboot phone.
6. adb shell, su, echo 1 > /sys/devices/virtual/usb_composite/diag/enable
7. QPST/CDMA workshop should detect the phone now.
I won't link QPST (I don't know if there are any copyright barriers), but you can find it extremely easy on Google. You want QPST 2.7 build 355.
If you're asked for SPC code, it's default 000000.
Now, I need testers: anyone with locked bootloader, or bootloader unlocked with Omnius/SEtool, please open EFS Explorer and tell me if there's anything inside cert, client-cert and client-key folders. Alternatively, try to find any SE/SEMC certificates in EFS.
Best regards
64 bit vista won't let me install. any chances you can make this.
trent6gol said:
64 bit vista won't let me install. any chances you can make this.
Click to expand...
Click to collapse
Strange. What error are you getting?
Thanks no error messages at all!
Good. Is your bootloader locked?
No new hardware are detected, even with modem enable set to 1
Im in Xperia arc unlocked by setool
Alejandrissimo said:
No new hardware are detected, even with modem enable set to 1
Im in Xperia arc unlocked by setool
Click to expand...
Click to collapse
Just turn on modem mode and install provided drivers for both HSUSB devices in Device Manager.
Blagus said:
Just turn on modem mode and install provided drivers for both HSUSB devices in Device Manager.
Click to expand...
Click to collapse
When I set the modem to 1 the adb stop working and the sa102 dissapear from the device manager but there is now new hardware detected.
Yes, that's what should happen - you should have two or three HSUSB devices under unknown ones. Install drivers for them.
Blagus said:
Yes, that's what should happen - you should have two or three HSUSB devices under unknown ones. Install drivers for them.
Click to expand...
Click to collapse
Nop. There is no unknown devices at all :S
Im runing a custom kernel, maybe need to run stock?
link up my video also and claim its yours atleast give credit
also guys if your on stock rom verizon to enter DIAG mode you enter ##3424
edokassiah said:
link up my video also and claim its yours atleast give credit
also guys if your on stock rom verizon to enter DIAG mode you enter ##3424
Click to expand...
Click to collapse
Which video?
Fyi for those using cdma workshop, You dont need to do the adb commands, phone wont "read" the info for general stuff, just goto security, send the spc code, it will unlock, then continue to upload your PRL stuff and change nam settings. Worked fine. =)
what is this exactly? and what is DIAG/QPST/CDMA workshop?
For cdma phones to change out which carrier its on, you need diag mode (which is the programming mode thats seperate from rom flashing as it tells the phone which tower to connect to) qpst and cdma workshop, are tools we use to program this stuff easier. Cdma workshop costs 100$ for a license tho.
x64 Drivers that WORK!!!!!!!!!!!
i dunno if this even matters anymore but i just made these x64 drivers and they have been tested and work just fine htey are not signed but they will install on win 7 x64
Will this driver let us who use custom rom to using DIAG mode?
since most of custom ROM kill the DIAG ability, so nothing will happen when u press #3424
no they wont unforutnatly
I have rooted my device and also gave root access to shortcut master and phone info app but still it doesn't launch the menu and gives some error. Any solution?
I have the same problem, you can achieve band locking through shortcut master under app explorer, check out hidden network settings. Interestingly it has a reference for standalone 5G!
Might need to flash with a combination file to achieve full service mode. I have an S8+ running with an engineering Rom and it has 2 system apps which can achieve full service mode, the apps are called Samsung keystring and iot hidden menu. With samsung Keystring you can enter any secret code. And with iot hidden menu you just select debug menu. Was messing around with lucky patches seeing if I could modify them to work on the S9+ but no luck yet.
Hopefully someone will find a way soon. I had the same problem on another S8+ after it upgraded to Oreo, so I think it's linked to that, but don't think there is an option to have android 7 for the S9!
This looks like it's worth a try.
https://forum.xda-developers.com/note-4-sprint/general/how-to-access-hidden-menu-adb-rooted-t3403289
Aidoooo said:
I have the same problem, you can achieve band locking through shortcut master under app explorer, check out hidden network settings. Interestingly it has a reference for standalone 5G!
Might need to flash with a combination file to achieve full service mode. I have an S8+ running with an engineering Rom and it has 2 system apps which can achieve full service mode, the apps are called Samsung keystring and iot hidden menu. With samsung Keystring you can enter any secret code. And with iot hidden menu you just select debug menu. Was messing around with lucky patches seeing if I could modify them to work on the S9+ but no luck yet.
Hopefully someone will find a way soon. I had the same problem on another S8+ after it upgraded to Oreo, so I think it's linked to that, but don't think there is an option to have android 7 for the S9!
This looks like it's worth a try.
https://forum.xda-developers.com/note-4-sprint/general/how-to-access-hidden-menu-adb-rooted-t3403289
Click to expand...
Click to collapse
But bro you can change so many settings in full service mode like selecting CA combination,activating 4x4 mimo,256 qam etc. I know about hidden service menu but for me it doesn't properly lock bands for some reason so i rooted just for accessing full service mode but i get this error. That telephony command doesn't open the menu but still the broadcast value i get is 0. I want the menu so bad because i only use 4g and i can improve speeds by changing some settings but **** samsung has locked us out. Maybe if ur phone is rooted and you have that 2 apps u mentioned try placing that apps in sys/priv-app folder and try opening it or may be find another way.
I will give that a try, i want to get the full service mode working also for sure, I am hoping for an option of setting the LTE category higher 16 or 20. I was reading it could also be due to the version of supersu used as the same thing happens with the phone info app. And those app developers don't think it's there app.
Aidoooo said:
I will give that a try, i want to get the full service mode working also for sure, I am hoping for an option of setting the LTE category higher 16 or 20. I was reading it could also be due to the version of supersu used as the same thing happens with the phone info app. And those app developers don't think it's there app.
Click to expand...
Click to collapse
But i am using magisk and also tried it with latest supersu but it didn't work. Like is there anyone who can solve this problem
Aidoooo said:
I will give that a try, i want to get the full service mode working also for sure, I am hoping for an option of setting the LTE category higher 16 or 20. I was reading it could also be due to the version of supersu used as the same thing happens with the phone info app. And those app developers don't think it's there app.
Click to expand...
Click to collapse
Did u find any way?
Hi all,
I'm having exactly this problem now. My purpose is to use the advanced service mode to lock LTE bands and to activate the 256 QAM and MIMO 4x4 functions. I have my G965F rooted and I'm having the same problems described before executing "Phone info" and dialing directly the "2683662" code. I updated the firmware to "G965FXXS2BRI1" with the same result.
I was wondering if flashing COMBINATION ROM could help... but I'm a newbie with this things...
does anyone have any idea about how to solve it, please? At leaste, any idea to use the band lock functions?
Thank you!
Hey, did anyone find a solution for this?
Interceptor777 said:
Hey, did anyone find a solution for this?
Click to expand...
Click to collapse
Seems most of here who wants to achieve the SERVICEMODE are on all OREO FW....No problem getting it to work on Nougat/MM..But after OREO came out, now **** comes on Servicemode...
Finally got it working !!!! damn Sammy disabled the SM on Oreo FWs.
castrojeremy11 said:
Finally got it working !!!! damn Sammy disabled the SM on Oreo FWs.
Click to expand...
Click to collapse
How'd you get it working?
Sleepsy said:
How'd you get it working?
Click to expand...
Click to collapse
Just Downgrade to Nougat - the only option
Downgrade then root it then as use Shortcut app..
Nougat?
castrojeremy11 said:
Just Downgrade to Nougat - the only option
Downgrade then root it then as use Shortcut app..
Click to expand...
Click to collapse
Hi mate, I can't find nougat firmwares for S9/S9+, all I can find are oreo and above, where did you find it?
castrojeremy11 said:
Just Downgrade to Nougat - the only option
Downgrade then root it then as use Shortcut app..
Click to expand...
Click to collapse
I don't know if this will help, as I have an S8. It works on Pie, and I think I may have used it while on Oreo.
I was able to able to get Safestrap (via EDL exploit: Thanks jrkruse!), and edit efs/carrier/hiddenmenu (from NO to YES)
In the dialer, the only code that ended up working for me (after much searching), was *#27663368378#
All the shorter codes failed. But, type it enough, and you'll memorize it like I did.
Alternatively (to memorizing), just for kicks I just converted it to words. An applicable one is "as-modem-test"
224 More acronyms: https://phonespell.org/combo.cgi?n=27663368378
Included link, since we're exposed to tons of these codes.
hello
It's strange that the advanced Menu Mode is disabled ... How the samsung staff will do to repair or test phones ?
Sleepsy said:
I don't know if this will help, as I have an S8. It works on Pie, and I think I may have used it while on Oreo.
I was able to able to get Safestrap (via EDL exploit: Thanks jrkruse!), and edit efs/carrier/hiddenmenu (from NO to YES)
In the dialer, the only code that ended up working for me (after much searching), was *#27663368378#
All the shorter codes failed. But, type it enough, and you'll memorize it like I did.
Alternatively (to memorizing), just for kicks I just converted it to words. An applicable one is "as-modem-test"
224 More acronyms: https://phonespell.org/combo.cgi?n=27663368378
Included link, since we're exposed to tons of these codes.
Click to expand...
Click to collapse
the as-modem-test thing is clever. mnemonics can and do frequently prove themselves to be handy!
If you are rooted then use "Network signal guru" it can lock band and also might help you.... As i had used to force lte band 03 as my phone takes band 40 which has low speed.
Sleepsy said:
I don't know if this will help, as I have an S8. It works on Pie, and I think I may have used it while on Oreo.
I was able to able to get Safestrap (via EDL exploit: Thanks jrkruse!), and edit efs/carrier/hiddenmenu (from NO to YES)
In the dialer, the only code that ended up working for me (after much searching), was *#27663368378#
All the shorter codes failed. But, type it enough, and you'll memorize it like I did.
Alternatively (to memorizing), just for kicks I just converted it to words. An applicable one is "as-modem-test"
224 More acronyms: https://phonespell.org/combo.cgi?n=27663368378
Included link, since we're exposed to tons of these codes.
Click to expand...
Click to collapse
you should also make sure keystrings r enabled by changing /efs/FactoryApp/keystr from no to yes
also keep in mind keystrings r also carrier dependent.. some have kore than others and some have different ones.. its based on csc.. if u look through them u will find each carrier has a keystrings.dat file
Hi,
i've a rooted pixel 3, is there a way to enable diag port? Thanks
Yeah but manipulations are impossible. Like, if you're looking to use pdc tool to flash mbn files , just quit now.
Xdevillived666 said:
Yeah but manipulations are impossible. Like, if you're looking to use pdc tool to flash mbn files , just quit now.
Click to expand...
Click to collapse
Is it possibile to do things like enable volte? Thanks
tekno281 said:
Is it possibile to do things like enable volte, change imei or meid? Thanks
Click to expand...
Click to collapse
Volte has to be allowed by your carrier first. I had a first gen pixel and my carrier didn't support it for vllte. Contacted them and they pushed he settings from their end. I had to do some manipulation to trigger the proper mbn file and it ended up working.
However that was when debugging aosp vendor image from Google allowed diag mode . They don't now.
So short answer is no for enabling volte. In regards to the other stuff, I wanna say no as ell.
Imei spoofing might be an option
Meid, no idea
You can do the mods via magisk, but VoLTE must first be allowed by your carrier.
help
imei spoofing possible with that? because i'm in a country where the phone gets blocked by the imei, and i want to rewrite one. Yes it isn't legal but no other option instead of wasting my phone.
Xdevillived666 said:
Volte has to be allowed by your carrier first. I had a first gen pixel and my carrier didn't support it for vllte. Contacted them and they pushed he settings from their end. I had to do some manipulation to trigger the proper mbn file and it ended up working.
However that was when debugging aosp vendor image from Google allowed diag mode . They don't now.
So short answer is no for enabling volte. In regards to the other stuff, I wanna say no as ell.
Imei spoofing might be an option
Meid, no idea
Click to expand...
Click to collapse
imei spoofing possible with that?
luqman.mirza said:
imei spoofing possible with that?
Click to expand...
Click to collapse
Not that I'm aware of
Xdevillived666 said:
Not that I'm aware of
Click to expand...
Click to collapse
But you said you were able to connect with the qpst. so did it get detected properly or not? because i want to make some changes in qcn under qpst. and can you please confirm the steps exactly you followed to enable diag port.
luqman.mirza said:
But you said you were able to connect with the qpst. so did it get detected properly or not? because i want to make some changes in qcn under qpst. and can you please confirm the steps exactly you followed to enable diag port.
Click to expand...
Click to collapse
Phone and ports are recognised ,yeah but it doesn't open in qpst .like I can't modify anything. Only ever tried on pie . Haven't touched it on q. I followed pixel 2 qxdm thread where they have custom built magisk and module for it.
luqman.mirza said:
But you said you were able to connect with the qpst. so did it get detected properly or not? because i want to make some changes in qcn under qpst. and can you please confirm the steps exactly you followed to enable diag port.
Click to expand...
Click to collapse
lol...
just bcuz someone can connect in qpst doesnt mean theres not other security features in place that could prevent you from messing with qcn or imei.. functions are probably limited/restricted
luqman.mirza said:
imei spoofing possible with that?
Click to expand...
Click to collapse
imei spoofing is also illegal in many countries.. you tryna spy on someone or get free service lol
elliwigy said:
imei spoofing is also illegal in many countries.. you tryna spy on someone or get free service lol
Click to expand...
Click to collapse
for your information pal, i want to fix my imei which is showing something 0044 instead of my original one and there is no carrier detection as well. LOL
Also, i'm able to get detected in qpst via modem port and made a backup of qcn file and even to restore it as well but it says read-only memory and no changes were made. LOL
pixel 3 diag port enable is ok but when u re lock bootloader or factory reset every change made on qcn or qxdm will revert
luqman.mirza said:
help
imei spoofing possible with that? because i'm in a country where the phone gets blocked by the imei, and i want to rewrite one. Yes it isn't legal but no other option instead of wasting my phone.
Click to expand...
Click to collapse
hi luqman did u successfully spoofed imei on pixel 3 .i made it but after a factory reser it resets to some 00204000......numbers
BADAMI said:
hi luqman did u successfully spoofed imei on pixel 3 .i made it but after a factory reser it resets to some 00204000......numbers
Click to expand...
Click to collapse
I have the same problem the factory reset then those numbers but to fix it it’s just 20 seconds.
only problem is, when I flash CalyxOS on it, I can’t enter Diag mode.
do you know any way around it?
cant seem to root calyx, I just need to enter Diag mode in caly, or is there a way I can root caly?
Hello everyone...
i'm facing issue while enabling diag port on Pixel 4 xl.
when i write adb shell then ok... after that i write "su" it says permission denied...
Nouman0114 said:
Hello everyone...
i'm facing issue while enabling diag port on Pixel 4 xl.
when i write adb shell then ok... after that i write "su" it says permission denied...
Click to expand...
Click to collapse
When you execute "su", you should receive a popup on the phone where you have to grant superuser permissions. You have only a few seconds to reply by default. Check Magisk, Settings, Superuser, for these 3 options:
Automatic Response
Request Timeout
Superuser Notification
Make sure none of them are set to Deny or None.
dcarvil said:
When you execute "su", you should receive a popup on the phone where you have to grant superuser permissions. You have only a few seconds to reply by default. Check Magisk, Settings, Superuser, for these 3 options:
Automatic Response
Request Timeout
Superuser Notification
Make sure none of them are set to Deny or None.
Click to expand...
Click to collapse
dcarvil said:
When you execute "su", you should receive a popup on the phone where you have to grant superuser permissions. You have only a few seconds to reply by default. Check Magisk, Settings, Superuser, for these 3 options:
Automatic Response
Request Timeout
Superuser Notification
Make sure none of them are set to Deny or None.
Click to expand...
Click to collapse
Hi, all. Please help me with some issues. Have Sonim XP5s dualsim gsm phone ATT locked.
1 Bootloader. Trying to unlock it.
*#*#2387#*#* activated USB debug. Set OEM unlock, but bootloader locked. fastboot unlock, fastboot oem unlock, fastboot flashing unlock do nothing. How i can unlock it?
2 Firmware. Does anyone have image to flash with QFIL? I try to flash empty one but QFIL say timeout and take no action. EDL started but ignore all requests. Bootloader issue?
3 SIM2 activation. Phone disable second SIM at all. Need correct firmware?
4 ATT unlock. How i can do it, with correct firmware installed?
5 Root. Kingroot, kingoroot no success. Custom recovery not found. Flashing\booting custom recovery is locked.
Thanks.
bumpity-bump
I have the same phone that I just bought and (sheepishly) just found out has wi-fi calling disabled by AT&T. That was a main reason for getting it, but unfortunately I went by the Sonim website's info and not AT&T's regarding that feature. Verizon's version has it enabled, but it's also much scarcer on the secondary market. The XP5800 doesn't seem to be a popular phone for tinkering judging by the lack of info on doing so.
Does anyone know if wi-fi calling could hypothetically be activated by rooting and then toggling some values, or is it more likely that the involved code was omitted entirely? I saw something to the former about tethering.
Bit_Basher said:
be activated by rooting and then
Click to expand...
Click to collapse
Still have found no rooting way. Bootloader locked, so no custom recovery can be used. Very unpopular phone, as you see, thread dead.
SpectralUA said:
Still have found no rooting way. Bootloader locked, so no custom recovery can be used. Very unpopular phone, as you see, thread dead.
Click to expand...
Click to collapse
Each Android can get rooted by means of SuperSU ZIP. Only requirement is to have successfully USB debugging option enabled in Android->Settings->Developer options. You install this ZIP via phone's stock recovery.
To access developer mode, google "developer mode sonim xp5s". Open article: kb.eschat.com "Open Developer Options Tab on Sonim XP5, XP5s or XP3...". The device will then open the Developer Options tab. Ensure the take bug report option is enabled, and that USB debugging is also enabled. You may also add a menu button to the Power tab for future access to this feature.
Be sure you use a clean SuperSU ZIP to avoid malware. Suggest getting one from the xda forum.
Hi. Is there any success with rooting or enabling second sim to working 2 sims together?
jwoegerbauer said:
Each Android can get rooted by means of SuperSU ZIP. Only requirement is to have successfully USB debugging option enabled in Android->Settings->Developer options. You install this ZIP via phone's stock recovery.
Click to expand...
Click to collapse
How i can do it? Stock recovery have no menu. /cache access denided from user. Putting update.zip do nothing without /cache/recovery/command. Did you know some trick to proceed install? ADB debugging enable, but no root rights there.
haikkk said:
Hi. Is there any success with rooting or enabling second sim to working 2 sims together?
Click to expand...
Click to collapse
Nothing.
Here are the firmware images for the Sprint XP5s
5SA.0.4-05-8.1.0-29.33.00_USER_PST.zip
Root has been achieved with Magisk!
ytagger said:
Root has been achieved with Magisk!
Click to expand...
Click to collapse
Is there any way to get Android Auto to work on the XP5s?
Hello All.
sorry for off topic, but can’t find anywhere.
does anybody know how to remove PIN on Sonim XP5s? Can’t access phone without entering PIN.
I would really appreciate for any help.
Thank you.
bkarshibaev said:
how to remove PIN on Sonim XP5s?
Click to expand...
Click to collapse
Recovery mode. Power + volUp long to show menu. Factory reset.
SpectralUA said:
Recovery mode. Power + volUp long to show menu. Factory reset.
Click to expand...
Click to collapse
Hello SpectralUA,
Does it really remove PIN?
I’m planning on buying Sonim XP5s and send it overseas. I just want to be 100% sure that Recovery mode will remove PIN.
Thank you.
bkarshibaev said:
Hello SpectralUA,
Does it really remove PIN?
I’m planning on buying Sonim XP5s and send it overseas. I just want to be 100% sure that Recovery mode will remove PIN.
Thank you.
Click to expand...
Click to collapse
Yes, it does, except if Factory Reset is blocked by Scout
ytagger said:
Yes, it does, except if Factory Reset is blocked by Scout
Click to expand...
Click to collapse
Is there way to check if Scout has restriction?
also, do you know which XP5s (AT&T, SouthernLinc, Sprint or Verizon) has wifi calling enabled and 2nd sim card slot is unlocked? I mean unlocked version of those 3 carriers.
Thank you.
bkarshibaev said:
Is there way to check if Scout has restriction?
Click to expand...
Click to collapse
Not if the device is PIN locked and you don't know it, obviously .
If it's open, just try to reset the phone from the regular menu and you'll see if it's restricted
bkarshibaev said:
2nd sim card slot is unlocked?
Click to expand...
Click to collapse
2nd sim usable without 1st. Found no way to enable both at same time.
Maybe anyone know how to dualsim (standby mode, etc) this unit?
ytagger said:
Here are the firmware images for the Sprint XP5s
5SA.0.4-05-8.1.0-29.33.00_USER_PST.zip
Click to expand...
Click to collapse
The link is not working. Do you have a different one?
So first you have to root. I used twrp and magisk. There are guides on how to do that you can find by searching around.
Then once you do that, follow these directions,
What I did was manually entered all of these setprop commands below, on the terminal emulator app that I downloaded from the play store. First I typed in su in the app and pressed enter. Don't know if that matters but it said it granted superuser rights to the terminal emulator app, which I suppose could be important. I'm rooted with magisk and twrp don't know if that matters either.
setprop persist.vendor.dbg.ims_volte_enable 1
setprop persist.vendor.dbg.volte_avail_ovr 1
setprop persist.vendor.dbg.vt_avail_ovr 1
setprop persist.vendor.dbg.wfc_avail_ovr 1
Then I guess I reset the phone a couple times maybe turned the data on and off and then today it was all working and said volte at the top of the phone. Also vowifi is an option you can turn on as well in network settings. Now in the network settings you can also turn volte ("4G calling") on and off now.
Been testing it on calls and it works perfectly. No more dropped calls from 3G or H+ only call service.
dial *#*#4636#*#* in the phone dialer and click phone information to be taken to secret phone information settings and if it shows LTE under Both data network type and VOICE NETWORK TYPE, then that's another indicator that I got volte working.
You can also type getprop in the terminal emulator and if it says 1 on all the volte and vowifi options that means you enabled these network features as well
This is the easiest method I've found so let me know if it works for you. Now the zenfone 7 works in the USA! At least for tmobile I'd be interested for someone with ATT to try out the method and report back if it works or other people with other phone services.
Shout out to @Seosam and the other guys who actually know what they are doing who helped me figure out this simple method!
The pictures attached show that volte is enabled on my device and what yours should look like at least on tmobile for this phone.
juanappleseed said:
So first you have to root. I used twrp and magisk. There are guides on how to do that you can find by searching around.
Then once you do that, follow these directions,
What I did was manually entered all of these setprop commands below, on the terminal emulator app that I downloaded from the play store. First I typed in su in the app and pressed enter. Don't know if that matters but it said it granted superuser rights to the terminal emulator app, which I suppose could be important. I'm rooted with magisk and twrp don't know if that matters either.
setprop persist.vendor.dbg.ims_volte_enable 1
setprop persist.vendor.dbg.volte_avail_ovr 1
setprop persist.vendor.dbg.vt_avail_ovr 1
setprop persist.vendor.dbg.wfc_avail_ovr 1
Then I guess I reset the phone a couple times maybe turned the data on and off and then today it was all working and said volte at the top of the phone. Also vowifi is an option you can turn on as well in network settings. Now in the network settings you can also turn volte ("4G calling") on and off now.
Been testing it on calls and it works perfectly. No more dropped calls from 3G or H+ only call service.
dial *#*#4636#*#* in the phone dialer and click phone information to be taken to secret phone information settings and if it shows LTE under Both data network type and VOICE NETWORK TYPE, then that's another indicator that I got volte working.
You can also type getprop in the terminal emulator and if it says 1 on all the volte and vowifi options that means you enabled these network features as well
This is the easiest method I've found so let me know if it works for you. Now the zenfone 7 works in the USA! At least for tmobile I'd be interested for someone with ATT to try out the method and report back if it works or other people with other phone services.
Shout out to @Seosam and the other guys who actually know what they are doing who helped me figure out this simple method!
The pictures attached show that volte is enabled on my device and what yours should look like at least on tmobile for this phone.
Click to expand...
Click to collapse
In my mind these setprops are usable without root!
You only need debug mode and can use ist with adb shell
Seosam said:
In my mind these setprops are usable without root!
You only need debug mode and can use ist with adb shell
Click to expand...
Click to collapse
Hmm I might try since I'm not rooted then!
Seosam said:
In my mind these setprops are usable without root!
You only need debug mode and can use ist with adb shell
Click to expand...
Click to collapse
What is ist? And can you access idb shell without a computer? Like only on the phone itself?
CVonV said:
Hmm I might try since I'm not rooted then!
Click to expand...
Click to collapse
Please try! I have a non tech savvy friend who wants this phone and if there is a non root easy way to enter these set prop commands without getting rid of OTA updates then I'd definitely like to know!
Seosam said:
In my mind these setprops are usable without root!
You only need debug mode and can use ist with adb shell
Click to expand...
Click to collapse
it is not possible
It is true. not possible ...
Seosam said:
In my mind these setprops are usable without root!
You only need debug mode and can use ist with adb shell
Click to expand...
Click to collapse
Ok now that you've confirmed unable to do these commands without root can you confirm if after activating VoLTE can we unroot and unlock bootloader? The reason I ask is because I heard unlocked bootloader removes widevine l1. Thanks for any advice.
maxsterling said:
Ok now that you've confirmed unable to do these commands without root can you confirm if after activating VoLTE can we unroot and unlock bootloader? The reason I ask is because I heard unlocked bootloader removes widevine l1. Thanks for any advice.
Click to expand...
Click to collapse
Yes, you can unroot. But to lock bootloader again, you need to reset your phone.
So, unroot yes, lock bootloader no.
Seosam said:
Yes, you can unroot. But to lock bootloader again, you need to reset your phone.
So, unroot yes, lock bootloader no.
Click to expand...
Click to collapse
But if we are willing to reset phone to lock bootloader then this is ok too? When we lock bootloader will the VoLTE changes made remain? Thanks again. Cheers
maxsterling said:
But if we are willing to reset phone to lock bootloader then this is ok too? When we lock bootloader will the VoLTE changes made remain? Thanks again. Cheers
Click to expand...
Click to collapse
I'm not sure. But I think it will reset the modem too. So you will lost Volte.