Related
Hey..After getting my esn added I can't seem to get the apn settings to stick.I do have talk & text but no internet whatsoever.I would really appreciate some help if somebody is willing to lend a helping hand..Thanks
Seems like there's no one with a photon on metro
I am also on Metro with text,talk,3G. But no MMS yet (I don't use it as much anyway).
Follow this link see if you can get your 3G to work.
http://forum.xda-developers.com/showthread.php?p=8395950#post8395950
There are differences in getting Photon to work with 3G. So some of the steps indicated in the above link are different. And I assume that you know how to get your MSL number. Here are the differences:
1. You don't need HTC diag drivers. This should be Motorola driver.
2. In order to get to diag mode. You need to boot into boot loader and choose BP tools
3. You will need to get QPST_2.7_366
4. Once you got everything:
follow step 9 - 28. However at step 22, instead of choosing "Simple IP", you want to choose "MOB+Simple IP". Otherwise 3G will not work.
Once done you should have 3G. However there is an annoying error Mobile IP Registration will be in your notification (ignore this, it does not matter).
Finally!!! I got it to work.I wasn't changing the spc code that's why it was giving me a problem.Thanks man & as soon as I figure out this mms thing imma let u know
Have you been able to get mms? if so, will you explaing how? thanks...
eltano07 said:
Have you been able to get mms? if so, will you explaing how? thanks...
Click to expand...
Click to collapse
Are you on a custom rom?
I have mms working fine sending and receiving on AOKPCB
GhostxLawliet said:
Are you on a custom rom?
I have mms working fine sending and receiving on AOKPCB
Click to expand...
Click to collapse
Can you please help me a little more about that...how to get the custom rom you mentioned for example, also how to install it would me helpfull...will I loose all my info when doing it? THANKS IN ADVANCE...
eltano07 said:
Can you please help me a little more about that...how to get the custom rom you mentioned for example, also how to install it would me helpfull...will I loose all my info when doing it? THANKS IN ADVANCE...
Click to expand...
Click to collapse
I pm'd you
I'm having trouble programming the phone.I started up my phone in bp tools but my phone doesnt seem to show up.
Is there certain drivers im suppose to install? i used the drivers from the main site because i couldn't find any other place to dl the drivers.
Are you on a gingerbread ROM ? If not then you should be.Double check your drivers & see if the phone pops up under ports in device manager.Once it shows up & gives you a port number then its a go.QPST & CDMA workshop is all you need
Im currently running cm7 and its on 2.3.7
In ports i see motorola QC Diag Port (COM8)
When i connect to COM8 with cdma workshop it becomes unresponsive (crash?)
connecting through qpst i see COM8 also but it reads as no phone.
Also thank you for your help so far!
U need to be on a blur ROM or else CDMA WS is gonna be unresponsive.Use rocko rom or any blur rom then retry
My mopho doesnt seem to pick up on metropcs i did the above and had my esn added to metro
not sure what went wrong.
EDIT: i got my internet working through dfs using the provision settings up top but my phone calls and text aren't sending/recieving
any luck with mms with aokp 4.0?
After reading through the OPO thread and someone confirming they saw bands unlocked for their OP2, but could not test if they are working as well as reading through the OP3 and similar threads with our processor I finally delved into trying this. Here is the quick guide of how to do it. Sorry if there is any confusion I will try my best to make it concise as possible. This is my first time writing a guide up for XDA.
I have not been able to test each band to confirm it's working, but it is showing up in Network Guru. I am on AT&T so I only unlocked AT&T bands (bc that's all I care about currently and it makes it easier for me to test)
I WILL NOT BE HELD RESPONSIBLE IF SOMETHING WRONG HAPPENS TO YOUR DEVICE BY FOLLOWING THIS GUIDE!
Credit: All my fellow XDA'rs who have been diligently testing, experimenting, bricking/unbricking, creating ROMs, FLASH, Root ability, and Bootloader unlocking. You are the heart and soul of XDA!
[URL="https://forum.xda-developers.com/member.php?u=4066277" @otonieru[/URL] for the concise guide
[URL="https://forum.xda-developers.com/member.php?u=7846474" @baskaflyfer[/URL] Rmt Storage Patch Zip
Here is the OP3 thread I based this guide off of and credit to all those mentioned in there as getting this far would have been impossible without them: https://forum.xda-developers.com/oneplus-3/how-to/guide-unlock-additional-lte-bands-t3519563
OKAY:
PreReq's:
1. Rooted
2. TWRP or like
3. RMT Storage patch from OP3 forums: SEE POST BELOW!
4. DFS Explorer - Find via searching XDA, again checking OP3 thread or OPO
5. ADB installed (whether that be minimal ADB or like from other toolboxes out there)
6. QPST - Check forums for download
Guide:
1. Put phone in MTP mode if not default (Some default to charge mode) Just go to status bar and press the charging mode to change to file transfer
2. Place file from PRE-REQ #3 in a folder you'll remember
3. Reboot phone (or shut down) and when coming on hold Vol Down+Power for a few seconds and let go
4. Boot into TWRP
5. Backup (If you don't have a backup of EVERYTHING at this point, probably a good idea to do so)
---If you do take only EFS
And install file from #3
6. Restart into System
7. Open up your CMD and run this ADB command :
adb devices
adb shell
su (you will get pop up on your phone to give root authorization for ADB, authorize it)
setprop sys.usb.config diag,adb (this will open your OP3 diagnostic port)
Click to expand...
Click to collapse
This forces it into DIAG mode, check your Device Manager to see if you see a port connection displaying a COM PORT.. IF NOT, you need to install drivers--Search thread for drivers, likely will be find in original OPO or OP3 thread.
***********THIS SECTION IS PURELY PRECAUTIONARY*********************** SKIP TO 11 IF YOU WANT
Purely precautionary we did not have to restore any QCN as they do in OP3 due to encryption:
8. Install QPST, open QPST
Now fire up QPST and go to "Port" tab, and choose "Add New Port" ,
9. On "Serial/USB Port" tab, unchecked the option of "Show Serial & USB...bl bla bla" option, you will see your phone listed there as a "COM#" (# is a number depending on your PC) choose it, and click "OK"
10. Now choose "Start Clients" from the Menu tab above, and choose "Software Download"
**********************************************************************************
11. CLOSE QPST. Open up DFS Explorer, when the signup option comes up it is up to you whether or not you want to register for an account (Good to support them since it's a good application) If not, press the X and the app will be there
12. You should see your PORT listed as you did on QPST. Double click on it (If you can't; confirm QPST is closed otherwise you won't be able to connect to the port) You should see it turn green and highlighted ONLINE if you successfully connected
13. Go to the "Band" option then click on "LTE"
14. Press READ; Give it a second and you should see all currently enabled bands listed; If you want to compare you can go to "Network Guru" and press the 3 dots on the top right and press Band Locking and then press LTE.. Should list the same ones
15. Check the additional bands (Just because it says it's enabled, doesn't mean hardware wise it will work due to chipset hardware limitations; This is why as you all do this if you can confirm which bands for you connected and/or didn't connect we can keep a running list.)
16. Press "Write"
17. Since we're in Demo mode it will count down and then in the LOG box you'll see operation successful
18. Restart the phone at this point and disconnect the cable
19. Wait until it boots up again and go to "Network Guru" press the 3 dots again and go to Band Locking and you should see the new bands listed
*If you don't press the 3 dots and press Clear forcings and it'll prompt that a power cycle may occur; That's okay, let it, mine did, wait until the phone comes back up and repeat 19 and the new bands should be listed.
20. LET US KNOW ON THIS THREAD what bands are working, what aren't. It will allow us to further play with the device to discover if there's limitations or if further editing is required like in the OP3.
*Please press THANK YOU if this guide was helpful.
**Sorry for the missing of some info in the guide! Seems when I added the HYPERLINK it removed most of the other text before it so it started at #4 instead of the remainder of #1-3
Direct link to RMT STORAGE PATCH:
Rmt Storage Patch Zip
usb debugging should be enabled i think, you didn't mentioned that. " (this will open your OP3 diagnostic port)" and here should be op2 i think. thanks for thread, i have a2005 and want to unlock 20 band(800mhz), will try asap, now i have exams running out of time. btw, so the risk of breaking phone is low right, this steps only modify EFS partition only? so hybrid recovery and flashfire can backup/restore if enything goes wrong
What is the benefit from this? Better reception?
Sent from my ONE A2005 using Tapatalk
So... Are your at&t bands working now? Which bands specifically?
我從使用 Tapatalk 的 Nexus 9 發送
Still something is missing
Hi, I think something is missing. Let me describe what I have done on a A2005:
1- I downloaded the rmt_storage from the link provided on Pre-reqs #3.
2- I backed up EFS, installed the patched rmt_storage, reboot into system.
3- I installed the modified HTC modem driver as unsigned driver, did the adb diag port commands, and the phone is recognized by DFS.
4- On DFS, I must click on SPC 000000 since the log shows errors. I'm not sure if a specific SPC value is required ***
5- When I click on Read, it captures the values, I wanted to add Band 3 (1800) so I checked it and then clicked on write. The logs showed that the write was successful.
6- I restart the phone, connect it and load adb diag port commands again, load DFS, click on read and the values stay
7- When I open Network Guru on locked LTE bands, the list shows me the previous one, as if nothing has been written. I restarted the phone already several times, still no LTE on Band 3.
Besides the SPC code, I might think that:
- The rmt_storage somehow it's not working
- DFS keeps the values but they are not reflected into Network Guru or phone. I already set 4G/3G/2G enabled on the connectivity options. No changes
- Maybe there is another value that needs to be changed with another tool such as QXDM
Any help would be very appreciated!!!
haroldgv said:
Hi, I think something is missing. Let me describe what I have done on a A2005:
1- I downloaded the rmt_storage from the link provided on Pre-reqs #3.
2- I backed up EFS, installed the patched rmt_storage, reboot into system.
3- I installed the modified HTC modem driver as unsigned driver, did the adb diag port commands, and the phone is recognized by DFS.
4- On DFS, I must click on SPC 000000 since the log shows errors. I'm not sure if a specific SPC value is required ***
5- When I click on Read, it captures the values, I wanted to add Band 3 (1800) so I checked it and then clicked on write. The logs showed that the write was successful.
6- I restart the phone, connect it and load adb diag port commands again, load DFS, click on read and the values stay
7- When I open Network Guru on locked LTE bands, the list shows me the previous one, as if nothing has been written. I restarted the phone already several times, still no LTE on Band 3.
Besides the SPC code, I might think that:
- The rmt_storage somehow it's not working
- DFS keeps the values but they are not reflected into Network Guru or phone. I already set 4G/3G/2G enabled on the connectivity options. No changes
- Maybe there is another value that needs to be changed with another tool such as QXDM
Any help would be very appreciated!!!
Click to expand...
Click to collapse
what and where is PRE-REQ #3?
haroldgv said:
Hi, I think something is missing. Let me describe what I have done on a A2005:
1- I downloaded the rmt_storage from the link provided on Pre-reqs #3.
2- I backed up EFS, installed the patched rmt_storage, reboot into system.
3- I installed the modified HTC modem driver as unsigned driver, did the adb diag port commands, and the phone is recognized by DFS.
4- On DFS, I must click on SPC 000000 since the log shows errors. I'm not sure if a specific SPC value is required ***
5- When I click on Read, it captures the values, I wanted to add Band 3 (1800) so I checked it and then clicked on write. The logs showed that the write was successful.
6- I restart the phone, connect it and load adb diag port commands again, load DFS, click on read and the values stay
7- When I open Network Guru on locked LTE bands, the list shows me the previous one, as if nothing has been written. I restarted the phone already several times, still no LTE on Band 3.
Besides the SPC code, I might think that:
- The rmt_storage somehow it's not working
- DFS keeps the values but they are not reflected into Network Guru or phone. I already set 4G/3G/2G enabled on the connectivity options. No changes
- Maybe there is another value that needs to be changed with another tool such as QXDM
Any help would be very appreciated!!!
Click to expand...
Click to collapse
In Network Signal Guru, choose clear forcing. And check the LTE bands again,
or, install Network Signal Guru after you done unlocking, else it will show what it remember on previous set up
---------- Post added at 01:44 PM ---------- Previous post was at 01:43 PM ----------
chxei said:
what and where is PRE-REQ #3?
Click to expand...
Click to collapse
the guide forget to mention that u need to flash rmt storage patch before do any modification,
else no mod will be saved (will revert upon boot)
the patch is in my OP3 thread
Thanks! So today's update:
1- I connected the phone again, ran adb commands, reviewed the bands again on DFS tool and settings stayed. I'm pursuing to enable Band 3
2- I uninstalled Network Signal Guru
3- On Recovery, flashed again the patched rmt_storage, boot the phone, wrote the values again on DFS tool. Reboot phone
4- I installed Network Signal Guru and now it's showing up on the bands lists. I unchecked the bands default on A2005 and used the ones from Eruper/Asia Model as FDD-LTE: Bands 1/3/5/7/8/20 and TDD-LTE: Bands 38/40/41. My provider in Costa Rica (Movistar) uses Band 3 (1800) for their LTE. I clicked on Band locking, clicked on GSM and WDCMA and removed all checks. Then clicked on LTE and left all LTE bands in hopes that it will connect to that frequency. The list shows:
B1: 2100
B3: 1800+
B5: 850
B7: 2600
B8: 900 GSM
B20: 800 DD
B38: TDD2600
B40: TDD 2300
B41: TDD 2500
When I only picked LTE bands as checked, it never resovled to get connected to any cell base.
5- I dialed *#*#4636#*#* to access the information about the phone and monitored the signal setting it up to "LTE Only". No signal on that either
Top of my head, I will restore the qcn backup I made and restore the backup I made for EFS and start again. Now it's saving values after reboot, which is great, but not identifying anything.
Is there any log worth posting here? I read on the OP3 guide that they were restoring a qcn file with bands enabled. Is it worth trying the same?
Anyone that has LTE band 3 enabled would be very appreciated if they post their qcn backup
t99220475 said:
So... Are your at&t bands working now? Which bands specifically?
我從使用 Tapatalk 的 Nexus 9 發送
Click to expand...
Click to collapse
I have not been able to further test as all the phones I compare to that are also AT&T ie: AT&T S6 are connected to the same Bands as me so cannot test til I get to an area where other bands are available currently. Will report back as I can test, but was hoping others can test in the mean time as well.
haroldgv said:
Thanks! So today's update:
Click to expand...
Click to collapse
You shouldn't need to restore any QCN or EFS, just re-check the bands you unchecked and it should pickup all the bands again. Also, confirm your APN is correct to be used with LTE?
Did you get ANY LTE Bands before this mod? Or you only have LTE on Band3?
You can use RAT locking to enable LTE Only rather than unchecking all the WCDMA and GSM bands. that way it'll force LTE, if it doesn't go to the Cellular Network tab and press the Preferred NETWORK to go to LTE ONLY.
sadly for me nothing happened, i have a2005 and want to add band 3 and band 20, did everything 2-3 times whats in a guide, everything went well, write process was comlete but bands didn't added
When you say didn't add, you don't see them in network guru or you see then, but unable to catch signal on them?
aurfawce said:
When you say didn't add, you don't see them in network guru or you see then, but unable to catch signal on them?
Click to expand...
Click to collapse
both, not shown in neywork guru, nor lte signal
chxei said:
both, not shown in neywork guru, nor lte signal
Click to expand...
Click to collapse
You tried to force clear in network guru? If so, when you reconnect and enter diag mode and go to DFS, press bands and LTE, press read, did the changes you made stick?
Just so ppl around here know... there is old forum about band OPT band unlocking with various trials of changing bands, which failed, due to missing RMT patch OR BUT it got MANY juicy info !!!
in the past other users sent me qcn/qcnx files of the EU and CN models ( credit: whoever sent me these files from the old thread ) - I hope this help you out.
keep up the good work ! :good:
gps3dx said:
Just so ppl around here know... there is old forum about band OPT band unlocking.
( un-successful of course due to missing RMT patch OR modem ( on A2005=US) ) with juicy info.
in the past other users sent me qcn/qcnx files of the EU and CN models ( credit: whoever sent me these files from the old thread ) - I hope this help you out.
keep up the good work ! :good:
Click to expand...
Click to collapse
Have you tried what we said here? And tried to see if you can band lock on 3?
I'm going to see the qcn based off of the op3 guide as well as they had to do qcn restoring.
aurfawce said:
Have you tried what we said here? And tried to see if you can band lock on 3?
I'm going to see the qcn based off of the op3 guide as well as they had to do qcn restoring.
Click to expand...
Click to collapse
not yet...it will take me some time, i'm a master's student in exam period.
nontheless, as you can see from the old forum, i'm really interested in opening LTE band 3 on my A2005.
Thanks guys! I live in Venezuela and we use band 3 for LTE and I have the EU version. I'll try this guide today
EDIT: I tried without success, I did all the process but i do not have LTE signal on Band 3. On Network Guru, Band 3 appears as supported. I tried RAT locking but It keeps without signal.
gps3dx said:
Just so ppl around here know... there is old forum about band OPT band unlocking with various trials of changing bands, which failed, due to missing RMT patch OR BUT it got MANY juicy info !!!
in the past other users sent me qcn/qcnx files of the EU and CN models ( credit: whoever sent me these files from the old thread ) - I hope this help you out.
keep up the good work ! :good:
Click to expand...
Click to collapse
Thank you for the qcn files. I've tried it, and it overwrites my imei, which is expected. Then I tried to replace the imei with mine by hex editor, but flashing the modified qcn still overwrites my imei. We may get into the same trouble with op3, which is the imei encryption.
I started searching for a solution to enable VoLTE for OnePlus 2 since the device was not supported by my carrier and stumbled on this thread by dagoban.
Credits goes to dagoban and jamal2367 (his thread in German is here)
Warning:
a. You can break your phone, so make sure you know what you are doing.
b. I've tested this method with quite a number of PIE custom roms, it doesn't work.
Requirements:
a. OxygenOS 3.6.1 - here
b. Root with Magisk 17.3 and add Module VoEnabler 1.4 by Toucan
c. TWRP Recovery version 3.2.1-0
d. Root Explorer
e. Download QPST 2.7.460 from here
f. Download QUD Windows installer QUD.WIN.1.1 Installer-10037.3 Setup.zip from here
g. Put your SIM in slot 1
Steps:
1. Flash OxygenOS 3.6.1
2. Flash TWRP Recovery 3.2.1-0
3. Flash Magisk 17.3 (had issue with later versions, so do not update when prompted)
4. Install QPST 2.7.460 on your Windows PC or Laptop
5. Install QUD on your Windows PC or Laptop
6. Reboot your your Windows PC or Laptop
7. In Magisk 17.3, add VoEnabler-v1.4 module
8. For good measure, reboot OPT
9. Add APN for your SIM if required by carrier
10. In some cases, you might need to call your carrier to make sure that VoLTE is activated for your SIM card
11. In Settings, SIM & Network, Enable VoLTE
12. With Phone (dialer), key in *#801#
13. Set Serial and Full-port switch to ON
14. With Phone (dialer), key in *#*#4636#*#* and check that VoLTE is enabled (show as TURN OFF VOLTE PROVISIONED FLAG)
15. Run PDC app in Administrator Mode (use "Type here to search" to key in PDC, right click on PDC and click on Run as administrator)
16. If QDI comms errors occurs, try other USB ports and reinstall the two software, reboot and try again.
17. In PDC, select your device, click on OEM_Overseas, deactivate Sub0
18. Click on OpenMkt-Commercial-CU, deactivate Sub1
19. Click on Remove button and close PDC
20. Run Root Explorer, navigate to /system/etc/firmware/mbn_ota
21. Delete mcfg_sw_OEM_Overseas-Commercial.mbn
22. Delete mcfg_sw_CMCC_CSFB_DSDS_Comercial_Volte.mbn
[Before Deletion]
[After Deletion]
23. Run PDC app in Administrator Mode again
24. Click on Oversea-Commercial_DS again and click on remove
25. Close and run PDC again
26. Set Volte_OpenMkt-Commercial-CMCC, active Sub0 and Sub1
27. Click on Activate button
28. Close PDC
29. If successful, you should be able to see VoLTE Logo on the right hand side of the status bar
30. If you don't see it, try rebooting your OPT
31. Enjoy
XDA:DevDB Information
[Guide] VoLTE + VoWiFi on OPT 3.6.1 OOS, Tool/Utility for the OnePlus 2
Contributors
zard
Version Information
Status: Testing
Stable Release Date: 2019-03-17
Created 2019-03-17
Last Updated 2019-03-17
Reserved #1
Reserved #2
If it doesn't work on pie then its useless cause all custom roms before pie has volte
Sent from my ONE A2003 using XDA Labs
Vishal Gharat1 said:
If it doesn't work on pie then its useless cause all custom roms before pie has volte
Sent from my ONE A2003 using XDA Labs
Click to expand...
Click to collapse
You're right but my purpose of sharing is because there are users who's carrier has not provided support to OnePlus 2 based on Oxygen OS 3.6.1.
Sent from my Pixel 3 XL using Tapatalk
Here's another method by Airpil, my post at his thread is here https://forum.xda-developers.com/showthread.php?p=79325534.
Using this method, I had successfully gotten VoLTE working on Pixel 2 XL (no VoLTE icon on status bar though) Pie with April patch.
This same method with Magisk 18.2 modded to get diagnostic port also works on Android Q beta 1.
Android Q beta 2 doesn't work, possibly because it needs the latest Magisk Canary build 19003 or 19004 to be modded. There's information on OP of that thread but I don't understand how to do it. If anyone understands how to do it, please reply here or PM me.
Sent from my Pixel 3 XL using Tapatalk
I have two OnePlus phones. One with OnePlus 2 Oxygen 3.6.1. I have made the changes described here and I have VoLTE (but no VOWIFI) on the DIGI.HU mobile network. Hurray!
The Other is OnePlus 3 Oxygen 9.0.3. I also tried and managed VoLTE service on DIGI.HU network.
However, restarting OnePlus 3, the service disappeared and QPST (PDC) never wants to connect to OnePlus 3 again.
Oneplus 2 can still connect to the same laptop on QPST. I tried to install the drivers on another machine ls the program but did not help, no connection.
Can somebody help me?
well thanks....!
it worked on my one plus 3t A3010 model.but after factory reset again the volte disappeared will u give a solution for that....
deepudrone 905 said:
well thanks....!
it worked on my one plus 3t A3010 model.but after factory reset again the volte disappeared will u give a solution for that....
Click to expand...
Click to collapse
It works on VoLTE with airtel sim
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: https://github.com/JohnBel/EfsTools/releases/tag/v.0.14
Qualcomm-Driver
mbn file for your carrier- I used Google Pixel 4a from @swangjang : https://github.com/swangjang/Pixel-...pss/readonly/vendor/mbn/mcfg_sw/generic/Pixel
1. settings props:adb shellsusetprop persist.vendor.dbg.ims_volte_enable 1setprop persist.vendor.dbg.volte_avail_ovr 1setprop persist.vendor.dbg.vt_avail_ovr 1setprop persist.vendor.dbg.wfc_avail_ovr 1
2. go into diag mode for X55 modem:adb shellsusetprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adbMake sure to install the drivers for it manually, especially the Diag Drivers.
3. find the correct com portgo to QPST configuration and find the X55 Modem com port in active phones. After it stop the QPST server.
4. EfsToolsGo to the EFSTools folder and find the EfsTools.dll config file. Open and change from autoport:
efstool port="yourcomport" (e.g. efstool port="com8")
5. Flash the mbn fileNow its' the same procedure like in the guide from Homersp. So I copy it from there:
You can test the connection by running this in the cmd window:
Code:
EfsTools.exe efsInfo
This should report back some info if everything is working. If not, try rebooting the device and redo the bits from the DIAG guide.
Step 3 - disabling mcfg
Extract efs.zip from above to the same directory as EfsTools.exe, and make sure the mcfg_autoselect_by_uim file is there. Now simply run this in the cmd window, one line at a time:
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
If everything worked you should see no error messages.
Step 4 - writing mbn
If you are using the Xiaomi Mi 9T mbns zip from above, move it to the EfsTools directory and extract it. Now we simply need to find the mbn for your carrier.
The mbn directory structure is generally laid out like this: <region>/<carrier>/commerci/<country>/mcfg_sw.mbn. For example, the one for my carrier is eu/h3g/commerci/se/mcfg_sw.mbn. Copy the mcfg_sw.mbn file to the same directory as the EfsTools.exe, then go to the cmd window you opened and type this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
To get it working on the second SIM slot you will also have to run this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
If it has worked you should see a bunch of output, but no errors. Try rebooting now, and hopefully after it has booted you will have fully functional VoLTE and VoWiFi.
Thank you! Going to try this for T-Mobile.
Trying this but I can never get my wife's phone to show up in QPST and notice connecting her phone vs my G8 behaves differently in Device Manager. My G8 I'm able to see my Com Port number via Device Manager. The Zenfore only shows up as ASUS Android Composite ADB Interface and under Portable Devices. Weird.
wud_e said:
Trying this but I can never get my wife's phone to show up in QPST and notice connecting her phone vs my G8 behaves differently in Device Manager. My G8 I'm able to see my Com Port number via Device Manager. The Zenfore only shows up as ASUS Android Composite ADB Interface and under Portable Devices. Weird.
Click to expand...
Click to collapse
That's strange. What happens in the "normal" diag mode: setprop sys.usb.config rndis,diag,adb ?
Which firmware your wife's has?
Seosam said:
That's strange. What happens in the "normal" diag mode: setprop sys.usb.config rndis,diag,adb ?
Which firmware your wife's has?
Click to expand...
Click to collapse
Sorry long day at work. It's WW_30.40.30.93.
Doing adb shell, su then setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
It doesn't error or report anything.
Seosam said:
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: https://github.com/JohnBel/EfsTools/releases/tag/v.0.14
Qualcomm-Driver
mbn file for your carrier- I used Google Pixel 4a from @swangjang : https://github.com/swangjang/Pixel-...pss/readonly/vendor/mbn/mcfg_sw/generic/Pixel
1. settings props (I don`t know if we need this):adb shellsetprop persist.vendor.dbg.ims_volte_enable 1setprop persist.vendor.dbg.volte_avail_ovr 1setprop persist.vendor.dbg.vt_avail_ovr 1setprop persist.vendor.dbg.wfc_avail_ovr 1
2. go into diag mode for X55 modem:adb shellsusetprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adbMake sure to install the drivers for it manually, especially the Diag Drivers.
3. find the correct com portgo to QPST configuration and find the X55 Modem com port in active phones. After it stop the QPST server.
4. EfsToolsGo to the EFSTools folder and find the EfsTools.dll config file. Open and change from autoport:
efstool port="yourcomport" (e.g. efstool port="com8")
5. Flash the mbn fileNow its' the same procedure like in the guide from Homersp. So I copy it from there:
You can test the connection by running this in the cmd window:
Code:
EfsTools.exe efsInfo
This should report back some info if everything is working. If not, try rebooting the device and redo the bits from the DIAG guide.
Step 3 - disabling mcfg
Extract efs.zip from above to the same directory as EfsTools.exe, and make sure the mcfg_autoselect_by_uim file is there. Now simply run this in the cmd window, one line at a time:
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
If everything worked you should see no error messages.
Step 4 - writing mbn
If you are using the Xiaomi Mi 9T mbns zip from above, move it to the EfsTools directory and extract it. Now we simply need to find the mbn for your carrier.
The mbn directory structure is generally laid out like this: <region>/<carrier>/commerci/<country>/mcfg_sw.mbn. For example, the one for my carrier is eu/h3g/commerci/se/mcfg_sw.mbn. Copy the mcfg_sw.mbn file to the same directory as the EfsTools.exe, then go to the cmd window you opened and type this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
To get it working on the second SIM slot you will also have to run this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
If it has worked you should see a bunch of output, but no errors. Try rebooting now, and hopefully after it has booted you will have fully functional VoLTE and VoWiFi.
Click to expand...
Click to collapse
Do you have a link for the qualcomm drivers to download? I'm trying to get this to work on T-mobile in the U.S.
juanappleseed said:
Do you have a link for the qualcomm drivers to download? I'm trying to get this to work on T-mobile in the U.S.
Click to expand...
Click to collapse
I'm not sure, too long ago. But I believe I used the driver of https://qpsttool.com/qpst-tool-v2-7-496 .
The is an extra folder for driver install.
wud_e said:
Sorry long day at work. It's WW_30.40.30.93.
Doing adb shell, su then setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
It doesn't error or report anything.
Click to expand...
Click to collapse
It should work :/
What happens when you use the setprop sys.usb.config rndis,diag,adb ?
Do you got a question from magsik first time after adb shell -> SU?
edit: Tipp: update to 30.40.30.96- it's the official ww Update, the 30.40.30.93 was just test for a few phones
My wife is far too busy and has no time for my nerdy ways! Even though she is gonna miss it (shoot I am too) she is gonna return the phone. She gets way too many business calls and it keeps dropping service sporadically due to being on T-Mobile. Thank you and I hope your tutorial is helpful to others!
I Got Volte VoWifi working on Tmobile in the US for the zenfone 7 pro! Read on below for easy instructions that worked for me.
Ok guys I was obsessing over all this, (as someone who doesn't program at all), how to get volte working on tmobile for the zenfone 7 pro on android 11, version (30.40.30.96), that I have in the U.S. And I ended up giving up on it late last night accepting I don't know what I'm doing in my life in general lol. Then randomly, I restarted my phone today for an unrelated reason and then I saw the volte letters at the top of my phone! I was like WTF!
So I THINK it's fully working now. Though I'm open to someone here helping me verify if I'm truly right or wrong about that. In fact I welcome it because I did it kind of on accident in an easier way than this guide or other guides have taught how to do it.
For more potential proof that I fully got it working:
The settings to enable volte, ("4G calling" as it's called in the menu) off and on are now present in the 'Settings>Network & Internet>Mobile Network' page, which seemingly indicates volte as an option to turn on and off has been enabled on the phone. Also Wifi Voice Calling as an option to enable is also there as well if you click the "Advanced" Menu Option on that same page under 4G calling and 5G Network Options.
BUT, when I check Settings>System>About Phone>Status>Sim Status it still doesn't say Volte or LTE under data or voice, it still says 4G which one might think would be an indicator against volte being truly enabled. Though I think it just means that officially my carrier tmobile doesn't have it activated on my sim even though it is activated on my phone? Could someone correct me on if I have this right?
BUT if i dial *#*#4636#*#* in the phone dialer and click phone information to be taken to secret phone information settings it shows LTE under Both data network type and VOICE NETWORK TYPE, which IS an indicator that I got volte working.
I also downloaded two volte status checker apps from the play store and they both said it is connected so I suppose at this point I am sold unless someone here tells me how wrong I am.
Also when I called my voicemail, aka placed a phone call, it said "HD voice" on my phone and it kept 4G data enabled instead of downshifting to 3G or H+ which is another strong indicator I got it working.
Ok So here's how I think I got it working easily for those who may get it to work doing the same method that's the easiest way I have found.
So I wasn't able to do any of the complicated stuff, (to me it's complicated), in any of the guides above because I just couldn't get my phone to connect right with qspt or anything else for whatever reason. Nor could I get a shell on my computer to even recognize the setprop commands. I didn't even get to the later steps because I couldn't complete the first ones.
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!
It seems like instead of having to use qspt and all that other stuff to enter the commands through a computer that then connect to a phone I just entered them on the phone itself through the terminal emulator app and it worked?
Other than that I'm not sure how else I got it working because when I tried to enter those setprop commands from my computer to the phone I couldn't even get it to work and the computer kept telling me setprop wasn't a recognized command, whereas when I entered those commands into the terminal emulator app on the phone itself, it DID recognize setprop as a valid command, even though when I entered the block of setprop commands through manual typing it didn't say anything once I entered them to verify that they did anything.
But I think the results say that they in fact DID do something.
I know my explanation is long but it seems I got it working a lot simpler than anyone else has just using the terminal emulator app on the phone itself after having it rooted on android 11 so wanted to share in case someone else can get it to work this way as well because man was it a pain in my ass to figure it out lol.
And please if someone is more knowledgeable let me know if I got it wrong or if there was something else I did to make it work that I'm not aware of at the moment or if I haven't FULLY got it enabled or it's only saying I did or something. But there seems to be a lot more evidence it is working that evidence that it isn't. Called my mom and she said my voice was clearer and richer as well so I think I got it.
I'm looking forward to using this phone in the U.S. and seeing if this radically improves my call quality and connection dependability! Cuz this phone's hardware is awesome it's just the software that is whack and incomplete because Asus cheaped out on the licensing this time. They did it for the bluetooth audio quality also. But Viper for android has solved that as well.
juanappleseed said:
Ok guys I was obsessing over all this, (as someone who doesn't program at all), how to get volte working on tmobile for the zenfone 7 pro on android 11, version (30.40.30.96), that I have in the U.S. And I ended up giving up on it late last night accepting I don't know what I'm doing in my life in general lol. Then randomly, I restarted my phone today for an unrelated reason and then I saw the volte letters at the top of my phone! I was like WTF!
So I THINK it's fully working now. Though I'm open to someone here helping me verify if I'm truly right or wrong about that. In fact I welcome it because I did it kind of on accident in an easier way than this guide or other guides have taught how to do it.
For more potential proof that I fully got it working:
The settings to enable volte, ("4G calling" as it's called in the menu) off and on are now present in the 'Settings>Network & Internet>Mobile Network' page, which seemingly indicates volte as an option to turn on and off has been enabled on the phone. Also Wifi Voice Calling as an option to enable is also there as well if you click the "Advanced" Menu Option on that same page under 4G calling and 5G Network Options.
BUT, when I check Settings>System>About Phone>Status>Sim Status it still doesn't say Volte or LTE under data or voice, it still says 4G which one might think would be an indicator against volte being truly enabled. Though I think it just means that officially my carrier tmobile doesn't have it activated on my sim even though it is activated on my phone? Could someone correct me on if I have this right?
BUT if i dial *#*#4636#*#* in the phone dialer and click phone information to be taken to secret phone information settings it shows LTE under Both data network type and VOICE NETWORK TYPE, which IS an indicator that I got volte working.
I also downloaded two volte status checker apps from the play store and they both said it is connected so I suppose at this point I am sold unless someone here tells me how wrong I am.
Also when I called my voicemail, aka placed a phone call, it said "HD voice" on my phone and it kept 4G data enabled instead of downshifting to 3G or H+ which is another strong indicator I got it working.
Ok So here's how I think I got it working easily for those who may get it to work doing the same method that's the easiest way I have found.
So I wasn't able to do any of the complicated stuff, (to me it's complicated), in any of the guides above because I just couldn't get my phone to connect right with qspt or anything else for whatever reason. Nor could I get a shell on my computer to even recognize the setprop commands. I didn't even get to the later steps because I couldn't complete the first ones.
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!
It seems like instead of having to use qspt and all that other stuff to enter the commands through a computer that then connect to a phone I just entered them on the phone itself through the terminal emulator app and it worked?
Other than that I'm not sure how else I got it working because when I tried to enter those setprop commands from my computer to the phone I couldn't even get it to work and the computer kept telling me setprop wasn't a recognized command, whereas when I entered those commands into the terminal emulator app on the phone itself, it DID recognize setprop as a valid command, even though when I entered the block of setprop commands through manual typing it didn't say anything once I entered them to verify that they did anything.
But I think the results say that they in fact DID do something.
I know my explanation is long but it seems I got it working a lot simpler than anyone else has just using the terminal emulator app on the phone itself after having it rooted on android 11 so wanted to share in case someone else can get it to work this way as well because man was it a pain in my ass to figure it out lol.
And please if someone is more knowledgeable let me know if I got it wrong or if there was something else I did to make it work that I'm not aware of at the moment or if I haven't FULLY got it enabled or it's only saying I did or something. But there seems to be a lot more evidence it is working that evidence that it isn't. Called my mom and she said my voice was clearer and richer as well so I think I got it.
I'm looking forward to using this phone in the U.S. and seeing if this radically improves my call quality and connection dependability! Cuz this phone's hardware is awesome it's just the software that is whack and incomplete because Asus cheaped out on the licensing this time. They did it for the bluetooth audio quality also. But Viper for android has solved that as well.
Click to expand...
Click to collapse
For some U.S. carriers may it work so. I have read in ROG 2 or 3 forum about it. Maybe because Asus has build in these carriers but not activated. For other you need whole procedure....
Tip: you can check your setptop status with getprop e.g. getprop persist.vendor.dbg.ims.volte If you get a "1" back it's activatetd.
Seosam said:
For some U.S. carriers may it work so. I have read in ROG 2 or 3 forum about it. Maybe because Asus has build in these carriers but not activated. For other you need whole procedure....
Tip: you can check your setptop status with getprop e.g. getprop persist.vendor.dbg.ims.volte If you get a "1" back it's activatetd.
Click to expand...
Click to collapse
Hey there, thank you for the response. I'm glad I didn't have to do anything else because I'm woefully underskilled at understanding the rest of the procedures though with enough time could have figured it out of course.
My image attached below shows what I got when I wrote in getprop to the terminal emulator.
When I wrote the command you gave me specifically it didn't return anything, though there are 1s returning for all the other setprop commands previously entered which is the same thing yes?
wud_e said:
My wife is far too busy and has no time for my nerdy ways! Even though she is gonna miss it (shoot I am too) she is gonna return the phone. She gets way too many business calls and it keeps dropping service sporadically due to being on T-Mobile. Thank you and I hope your tutorial is helpful to others!
Click to expand...
Click to collapse
I figured out how to enable volte on tmobile pretty easily if you still have the phone to try it out on! My guide on how to do it is posted in this thread.
juanappleseed said:
I figured out how to enable volte on tmobile pretty easily if you still have the phone to try it out on! My guide on how to do it is posted in this thread.
Click to expand...
Click to collapse
Hey, awesome to see. She got a new Samsung phone and took her number back to Cricket. Howerver, I haven't had a chance to unroot and relock the bootloader so I could verify this for you on the phone. At least see if the settings stick using an on phone terminal like you did.
Also I do have a Mint Sim I'm test driving for a Mi 10 Ultra. I'll see what happens adding that Sim in since it is T-Mobile after all.
----------
Unrelated sort of. Something happened last night that I didn't think was needed and made me question if any of this is needed at all when trying to get these phones to work on Cricket. So the Samsung my wife bought is the S20 Ultra which is 5G, AT&T variant. I was doing a speed test with my Mi10 and then randomly asked my wife to do it on the S20. Her speed never got over 4G speeds. I mentioned that and she said Cricket charges extra for 5G. Interesting! So I wonder if popping your SIM in a 5G phone no matter what triggers their alarm system and they shut it down because they want the "cost" of 5G. I'm going to take my Mi 10 ultra to the Cricket store and since Amazon has like a 30 day window of needing merchandise back after making a return claim I'll take the Zenfone 7 also. Maybe in store asking to upgrade to 5G nets a different result than popping in the SIM which they recommend anyway, but it shouldn't be this hard.
wud_e said:
Hey, awesome to see. She got a new Samsung phone and took her number back to Cricket. Howerver, I haven't had a chance to unroot and relock the bootloader so I could verify this for you on the phone. At least see if the settings stick using an on phone terminal like you did.
Also I do have a Mint Sim I'm test driving for a Mi 10 Ultra. I'll see what happens adding that Sim in since it is T-Mobile after all.
----------
Unrelated sort of. Something happened last night that I didn't think was needed and made me question if any of this is needed at all when trying to get these phones to work on Cricket. So the Samsung my wife bought is the S20 Ultra which is 5G, AT&T variant. I was doing a speed test with my Mi10 and then randomly asked my wife to do it on the S20. Her speed never got over 4G speeds. I mentioned that and she said Cricket charges extra for 5G. Interesting! So I wonder if popping your SIM in a 5G phone no matter what triggers their alarm system and they shut it down because they want the "cost" of 5G. I'm going to take my Mi 10 ultra to the Cricket store and since Amazon has like a 30 day window of needing merchandise back after making a return claim I'll take the Zenfone 7 also. Maybe in store asking to upgrade to 5G nets a different result than popping in the SIM which they recommend anyway, but it shouldn't be this hard.
Click to expand...
Click to collapse
Update!!! It works and it makes me sad that it worked this easily! Only because we are returning it. Before using Termux as su and entering the commands, my Mint Sim did not show Volte and VoWifi was not an option. Changing the settings Volte shows up in the top of the screen next to the connection icons and going into the Sim options you are able to flip VoWifi on and then that worked as well. Also verified in *#*#4636#*#* Great work both of yall!!! This is a legit option. Will verify taking my MI 10 to Cricket in case that helps further.
wud_e said:
Update!!! It works and it makes me sad that it worked this easily! Only because we are returning it. Before using Termux as su and entering the commands, my Mint Sim did not show Volte and VoWifi was not an option. Changing the settings Volte shows up in the top of the screen next to the connection icons and going into the Sim options you are able to flip VoWifi on and then that worked as well. Also verified in *#*#4636#*#* Great work both of yall!!! This is a legit option. Will verify taking my MI 10 to Cricket in case that helps further.
Click to expand...
Click to collapse
I'd be interested for sure and glad you verified a super easy solution that at least works for us tmobile users in the USA. As for 5G on zenfone 7 from what I understand it doesn't have the bands to work on tmobile. I believe ATT has one 5G band available.
Yeah Cricket wouldn't touch either phone. So I'm going to switch to Mint for MI 10.
Můj operátor nemá v seznamu podporovaných telefonů telefon 4a. Nevíte, kde najít MBN pro:
My carrier does not have phone 4a in the list of supported phones. Don't know where to find mbn for:
My operator is 02 telefonica CZ
{
"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"
}
----------[Test Platform]----------
[ Device ]
----| Motorola Moto Edge + XT2061-3 (Global)
[ Carrier ]
----| Verizon Wireless USA
[ Stock Firmware ]
----| BURTON_RETAIL_11_RPBS31.Q1-19-19-14-11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
[ GSI Firmware ]
----| LineageOS 18.X (Android 11)
----------[Features]----------
*** This only pertains to the test platform used, no other GSI was tested
[ Working ]
----| LTE Data
----| CDMA Voice
----| Text
----| WiFi
----| Bluetooth
----| Camera
[ Not Working ]
----| Display over USB-C *** This may not be present in any custom rom for any phone, cannot verify
----| VoLTE
[ Not Tested ]
----| Fingerprint Sensor
----| VoWiFi
----| Tethering
----------[Important Information]----------
Android 11 on this device uses a dynamic partition for various partitions called super. The only way to access system is through fastbootd
VZW (Verizon Wireless) stock firmware version confirmed working on XT2061-3, albeit without mmWave 5G (due to [this]). Using this stock was not tested with GSI, but will more than likely work.
----------[Sources of Information]----------
[How to flash GSIs on devices with dynamic super partition]
[[Tutorial] Magisk on GSI on devices with dynamic partition]
----------[Prerequisites]----------
Moto Edge + XT2061-3 *** Verizon's XT2061-1 will NOT work
Unlocked Bootloader [found here]
Stock Android 11 Firmware [found here] *** If unsure which version, use same as test platform.
Latest platform-tools [found here]
TWRP [found here] or [mirror here] *** mirror uses 7zip archive dropping size to 21.1MB from 49.2MB
GSI AB arm64 Android 11 image [found here]
----------[Guide]----------
[ Flash Stock Firmware ]
1---| Boot device into the bootloader (Volume & Power)
2---| Connect to PC
3---| Extract firmware package
4---| open flashfile.xml
5---| Execute the commands as listed in flashfile.xml by using one of the orders below
5a-------| fastboot operation var (ie fastboot getvar max-sparse-size)
5b-------| fastboot operation partition filename (ie fastboot flash partition gpt.bin)
6---| When flashing vbmeta, use this command
7--------| fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8---| Reboot to bootloader from bootloader menu
[ Prepare Data ]
1---| Boot into TWRP, do not flash
1a-------| fastboot boot twrp-3.4.0-0-burton-beta1.img
2---| If menu comes up about enter password, just hit cancel
3---| Click Wipe, Format Data, yes
4---| Click Wipe, slide to factory reset
[ Boot into fastbootd ]
1---| Boot device into bootloader (Volume Down & Power) or select reboot into bootloader from TWRP
2---| Use fastboot to boot into fastbootd
2a-------| fastboot reboot fastboot
[ Flash GSI Image ]
1---| With fastbootd we can flash directly the system partition
1a-------| fastboot flash system gsi.img
2---| Reboot and your device should be booting the GSI
[ Installing Magisk ]
1---| Extract boot.img from stock firmware archive
2---| Copy boot.img to phone
3---| Install magisk.apk from github
4---| Open Magisk, click Install, select from file, choose boot.img
5---| Copy patched magiskboot.img from Downloads to your pc
6---| Reboot into bootloader
7---| Flash magiskboot.img
7a-------| fastboot flash boot magiskboot.img
----------[Notes]----------
If you have any problems, please refer to the links posted in [Sources of Information]. Those are the guides I used. Although they include some steps omitted in this guide, they may be relevant for you.
----------[Thanks]----------
Thanks to [kusti420] for providing information about the super partition and how to flash GSIs.
----------[Feedback]----------
I have provided this guide to get feedback about which GSIs work and what features in those GSIs work. If you follow this guide, please report back what was working and any steps different from this guide that you had to take. Thanks!
i ran into trouble with this. the firmware you have and lineage your using is now outdated but i tried with both your version and the updated ones and 18.x version of lineage does seem to detect my sim card and the new one lineage 19 detects it but i get the error from verizon that my phone cant be authenticated for calls but everything else works. i notice when im running updated stock, the sim card reads fine and service works normally but before when i had it running older stock firmware (android 10) i got the same thing. everything would work but calls. then when i updated the stock firmware, everything worked. so im not sure what im missing here when trying to follow your direction for getting this installed but maybe you know whats going on since your a verizon user using the global variant. please write me back when you get this. thanks a bunch
bjf189 said:
i ran into trouble with this. the firmware you have and lineage your using is now outdated but i tried with both your version and the updated ones and 18.x version of lineage does seem to detect my sim card and the new one lineage 19 detects it but i get the error from verizon that my phone cant be authenticated for calls but everything else works. i notice when im running updated stock, the sim card reads fine and service works normally but before when i had it running older stock firmware (android 10) i got the same thing. everything would work but calls. then when i updated the stock firmware, everything worked. so im not sure what im missing here when trying to follow your direction for getting this installed but maybe you know whats going on since your a verizon user using the global variant. please write me back when you get this. thanks a bunch
Click to expand...
Click to collapse
Well I only had the phone as a test for getting mmWave 5G on the global variant, which isn't possible due to a proprietary solder pattern on the board, but I no longer use this phone.
What I would recommend for you is to flash the NON-HLOS.bin from the stock firmware that worked for you without a problem. It's the modem firmware and it could cause problems like that. I didn't have any issue with my sim card, calls worked fine over CDMA and I could get text messages and LTE data worked.
I have never even seen the error that says the phone can't be authenticated for calls. Is it coming from a verizon app or is it an android error? I would also suggest to make sure the correct APN is being used, should be VZWINTERNET. I had an issue with an older motorola where it would for some reason randomly switch to some other VZW APN that was wrong.
I didn't do thorough testing of this, I just wanted to get the baseline for getting custom roms running, but I didn't encounter anything like what you're going through. Considering you had this problem on a certain stock firmware version, my best guess is the modem firmware. I did flash the VZW firmware on the phone and that worked as well, maybe you should try flashing that modem firmware? I didn't have issues, but I can't 100% recommend it because VZW expects the QTM 5G modules to be present, which it isn't. I don't know if this could cause hardware issues. Other than that, the phones are 100% identical.
Sorry I didn't get back to you sooner, XDA's "stay logged in" checkbox does not seem to work correctly and this website is a hassle to navigate.
Knuxyl said:
Well I only had the phone as a test for getting mmWave 5G on the global variant, which isn't possible due to a proprietary solder pattern on the board, but I no longer use this phone.
What I would recommend for you is to flash the NON-HLOS.bin from the stock firmware that worked for you without a problem. It's the modem firmware and it could cause problems like that. I didn't have any issue with my sim card, calls worked fine over CDMA and I could get text messages and LTE data worked.
I have never even seen the error that says the phone can't be authenticated for calls. Is it coming from a verizon app or is it an android error? I would also suggest to make sure the correct APN is being used, should be VZWINTERNET. I had an issue with an older motorola where it would for some reason randomly switch to some other VZW APN that was wrong.
I didn't do thorough testing of this, I just wanted to get the baseline for getting custom roms running, but I didn't encounter anything like what you're going through. Considering you had this problem on a certain stock firmware version, my best guess is the modem firmware. I did flash the VZW firmware on the phone and that worked as well, maybe you should try flashing that modem firmware? I didn't have issues, but I can't 100% recommend it because VZW expects the QTM 5G modules to be present, which it isn't. I don't know if this could cause hardware issues. Other than that, the phones are 100% identical.
Sorry I didn't get back to you sooner, XDA's "stay logged in" checkbox does not seem to work correctly and this website is a hassle to navigate.
Click to expand...
Click to collapse
I'll try flashing the Verizon modem when I can. Recently, my service randomly died and I turned on airplane mode to restore service but the unable to authenticate for calls happened again when it worked fine before. I had to restart the phone to get calls working again. No idea what it was about. As for the apn, I was going to transfer the apn over from my s21 plus but it seems the verizon sim already sets the apn automatically to where it's not able to be changed. It's all greyed out. I noticed that I also got the unable to authenticate for calls before I updated the firmware. I bought the phone used and it was behind in updates. When I updated to the second most recent update, I noticed calls started to work. I haven't updated to latest since installing magisk with root broke the Ota update. I could update with a pc easy but I haven't since the things listed here are now out of date so trying to stay with the firmwares listed here. Lastly for 5G, i checked the bands the phone supports before buying it and I believe it matched one or two bands with 5G and I do get 5G in few areas. It also supports most LTE bands that Verizon gives. I didn't see any cdma support, only GSM but from my understanding GSM and CDMA is an older thing when it came to 2g or 3g. What I've gathered is if voice can be done through LTE then calls would work. So just a tip on the testing and things I've come across so far
I just noticed in the thread that voice over LTE doesnt work. I wonder if that's my issue? However I see CDMA voice is working so says the thread here. It's confusing at this point
bjf189 said:
I just noticed in the thread that voice over LTE doesnt work. I wonder if that's my issue? However I see CDMA voice is working so says the thread here. It's confusing at this point
Click to expand...
Click to collapse
Ok I remember now when I was trying to enable VoLTE the calls just wouldn't work. I didn't get an error though. You have to turn off VoLTE for it to work again. This is in Settings/Network & Internet/Mobile Network/Advanced Calling.
The developer of the lineageos gsi was aware of this issue and tried to fix it but I guess it only applies to whatever phone he was testing with.
As long as the APN says VZWINTERNET you should be fine. Trying to flash over another APN isn't worth the effort and can cause more problems than it could fix, the values are correct as long as the right APN is being selected.
CDMA is Verizons standard calling radio technology, was also used by Sprint. CDMA is being phased out though to be replaced by LTE entirely. I don't know when this will happen. If you check the GSMArena link in the first post you will see all the bands listed on this phone, and it does support CDMA, which is why calling works without VoLTE.
Considering you were having problems on the stock firmware, it seems like your issue is more than just VoLTE not working, because what you explained is not a typical issue, and no matter what stock firmware you were on, VoLTE and CDMA calling both should've worked out of the box. I would test to make sure your Verizon account even has VoLTE support first because that seems to be the only reason for error messages popping up like you had. Although this doesn't really matter though because this method does not support VoLTE from what I tested.
Knuxyl said:
Ok I remember now when I was trying to enable VoLTE the calls just wouldn't work. I didn't get an error though. You have to turn off VoLTE for it to work again. This is in Settings/Network & Internet/Mobile Network/Advanced Calling.
The developer of the lineageos gsi was aware of this issue and tried to fix it but I guess it only applies to whatever phone he was testing with.
As long as the APN says VZWINTERNET you should be fine. Trying to flash over another APN isn't worth the effort and can cause more problems than it could fix, the values are correct as long as the right APN is being selected.
CDMA is Verizons standard calling radio technology, was also used by Sprint. CDMA is being phased out though to be replaced by LTE entirely. I don't know when this will happen. If you check the GSMArena link in the first post you will see all the bands listed on this phone, and it does support CDMA, which is why calling works without VoLTE.
Considering you were having problems on the stock firmware, it seems like your issue is more than just VoLTE not working, because what you explained is not a typical issue, and no matter what stock firmware you were on, VoLTE and CDMA calling both should've worked out of the box. I would test to make sure your Verizon account even has VoLTE support first because that seems to be the only reason for error messages popping up like you had. Although this doesn't really matter though because this method does not support VoLTE from what I tested.
Click to expand...
Click to collapse
Well I will do more testing here shortly. I noticed that on lineage 18.x (Android 11) I get a missing Sim card error when a Sim card is present. Then with latest lineage 19, I get no sim error except the calling authentication error. I have Verizon firmware with the modem now so I'll try testing lineage again with the Verizon modem to see how it plays out.
UPDATE: i tried both lineage 18.x and 19 that have android 11 and 12 in them. still have the same result of phone not able to be authenticated even after flashing verizon modem. ive even tried other gsi roms and ether ended in a bootloop or an error saying petition was too small. it seems that the apn for verizon becomes greyed out and changes the apn settings itself from the sim card. ive even tried using the latest stock update with the gsi and same results. (had to pay a site for the firmware since the newest update is exclusive?) at this point, ive decided using a gsi on this phone with verizon service a bust. so ive decided to stick with stock with root and magisk.
on a side note, i noticed the newer updates have provisioning apps installed on the stock firmware for carriers. not sure if that makes much of a difference but im done messing with it.
First of all thanks Knuxyl for your guide, it helped me to install a GSI ROM n my Edge+, I found really good images but in the end all the images I tried had the same issue... "bluetooth devices connects but transfer no audio", I dont think this is a ROM issue, because I tested 6 android 10 custom ROMS and 3 android 11 with the same result, so I wonder if you dont have this same issue or you manage to solve it.
Im using crdroid v313+211013 and BT wont connect to anything unless I disable A2DP hardware offload inside developer options, with this option enable, the phone pairs with devices but transfer no sound also most of audio codecs are not selctable, they are disabled (grau color), if I enable gabeldorsche stack, the phone is unable to pair with devices. Please if anyone have this issue or suggestion let me know. Have a great day.
@Knuxyl - Thanks for putting this guide together.
@ifritknight - Indeed, I also couldn't get bluetooth to work. I got bootloop with Havoc and LOS 19. LOS 18 worked well.
hi , thank you , there are upgrade?
Well this platform isn't widely supported. I wrote the guide just to get us a foot in the door. The problems with VoLTE, sim, and Bluetooth are more than likely an improper implementation of the new oem partition stuff Google started enforcing, which started with Project Treble.
I did request the source for the kernel for global retail and verizon variants like a year ago. They finally released them within the past month on their github, so maybe a lineage developer could take a peek and possibly officially support this phone. This phone is too good to not support, but the display over usb c would take some effort.
Here are the links
Verizon
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-RPBS31.Q1-19-58-26-2
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-RPBS31.Q1-19-58-26-2
github.com
Retail
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-RPBS31.Q1-19-19-14-11
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-RPBS31.Q1-19-19-14-11
github.com