Unlocking more bands (specifically band 12) is on the way, please be patient as there are a lot of bugs with having a modified modem firmware.
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE! YOUR WARRANTY IS VOID IF YOU FOLLOW THIS TUTORIAL!
This took like 2 weeks to figure out, I was about to give up, but then it worked. VoLTE on band 4 and 2 for T-Mobile in the USA!!
I have only tested this on my phone, but it should work on others (assuming it is still an A2). I have not verified if this works for phones converted to the 6X so if you want to try please be careful.
Alright, enough with the warnings and stuff.
1. First, enable usb debugging and plug your phone into your computer.
1. Download qpst and install it. You will also need this file . Just save it somewhere, we will use it in a minute.
2. run the following commands (note that you MUST be rooted to enable this. The mod survives returning to stock unrooted, and even survives OTA so you can unroot when finished if you want.):
'''
adb shell
su
setenforce 0
setprop sys.usb.config diag,serial_cdev,rmnet,adb
'''
3. once installed there should be an entry in your start menu. open the folder labelled qpst and select the program "PDC".
4. click the Device dropdown and select the Qualcomm device. (it may not show up first time, make sure you have installed the drivers for your device)
5. once you select your device you should see a lost of items, this can take a minute depending on the speed of your computer.
6. click the load button and select the mcfg_sw.mbn you downloaded earlier.
7. "Commercial-TMO" should now be a listing in the description. Highlight it and right click on it, hover over "SetSelectedConfig" and select "sub0". Let it load for a bit.
8. it should now say pending on the Sub0 column of the Commercial-TMO. Now click activate and let it load.
9. on your phone, you must disable reigon checking. To do so go to your phone app and type in the following: *#*#86583#*#*
10. reboot your phone.
This worked for me, I have not verified that it works for others yet, so if it works for you, please let me know. Also let me know of any bugs.
Shreenshots below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can this phone work on Metro PCS network
I tried and tried, but i cannot get PST to see my phone. I loaded qualcomm drivers and ADB drivers, nothing. Any suggestions?
Daha3ker said:
Unlocking more bands (specifically band 12) is on the way, please be patient as there are a lot of bugs with having a modified modem firmware.
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE! YOUR WARRANTY IS VOID IF YOU FOLLOW THIS TUTORIAL!
This took like 2 weeks to figure out, I was about to give up, but then it worked. VoLTE on band 4 and 2 for T-Mobile in the USA!!
I have only tested this on my phone, but it should work on others (assuming it is still an A2). I have not verified if this works for phones converted to the 6X so if you want to try please be careful.
Alright, enough with the warnings and stuff.
1. First, enable usb debugging and plug your phone into your computer.
1. Download qpst and install it. You will also need this file . Just save it somewhere, we will use it in a minute.
2.once installed there should be an entry in your start menu. open the folder labelled qpst and select the program "PDC".
3. click the Device dropdown and select the Qualcomm device. (it may not show up first time, make sure you have installed the drivers for your device)
4. once you select your device you should see a lost of items, this can take a minute depending on the speed of your computer.
5. click the load button and select the mcfg_sw.mbn you downloaded earlier.
6. "Commercial-TMO" should now be a listing in the description. Highlight it and right click on it, hover over "SetSelectedConfig" and select "sub0". Let it load for a bit.
7. it should now say pending on the Sub0 column of the Commercial-TMO. Now click activate and let it load.
8.on your phone, you must disable reigon checking. To do so go to your phone app and type in the following: *#*#86583#*#*
9. reboot your phone.
This worked for me, I have not verified that it works for others yet, so if it works for you, please let me know. Also let me know of any bugs.
Shreenshots below
Click to expand...
Click to collapse
This sounds scary. I thought volte works on band 12. If the band is missing how would it work. How can you confirm it actually works.
Hi!
I am running into the same issue of two computers (Win 7 and Win 10) that cannot see the phone. Anyone willing to help in getting PDC to see the phone? Thanks!
I have a couple questions for OP
Will this prevent any OTA?
Could you also take a screenshot of 4g while on a call?
What bugs do you experience?
I definitely see that your method unlocks some options in phone info, in the screenshots, but it doesn't necessarily prove anything if you can't see 4g while in a call and see a difference in speed. I notice the difference in speed when trying to do things on a call while on 3g, so if I were to do this I would definitely be able to tell it worked or not.
mymeatb18 said:
I have a couple questions for OP
Will this prevent any OTA?
Could you also take a screenshot of 4g while on a call?
What bugs do you experience?
I definitely see that your method unlocks some options in phone info, in the screenshots, but it doesn't necessarily prove anything if you can't see 4g while in a call and see a difference in speed. I notice the difference in speed when trying to do things on a call while on 3g, so if I were to do this I would definitely be able to tell it worked or not.
Click to expand...
Click to collapse
I would like to know this as well.
Ulver said:
I would like to know this as well.
Click to expand...
Click to collapse
If you want a specific screenshot let me know, I have been using this for a while though with no issues. The Band 12 has a lot of tuning data required and may not be compatible with all a2 devices without buying tuning equipment. (I used a friend's and hoped this was not the case) :/ I will keep working on it though. All is not lost yet.
As for the device not showing in the computer, it does require root as of the pie update because xiaomi disabled diag mode by default... :/
To enable it in the pie update you need to enter the following in adb shell for it to show up in qpst:
su
setprop sys.usb.config diag,adb
Note, do not reboot yet, rebooting resets these values..
Then re- insert the phone into your computer and it should show up.
The nice thing is that this survives ota and root removal once put on so if you want ota you can have it, just unroot once you get the mod working.
Hi Daha3ker,
I tried to enable with the mentioned commands and still PDC cannot see my phone.
Daha3ker said:
If you want a specific screenshot let me know, I have been using this for a while though with no issues. The Band 12 has a lot of tuning data required and may not be compatible with all a2 devices without buying tuning equipment. (I used a friend's and hoped this was not the case) :/ I will keep working on it though. All is not lost yet.
As for the device not showing in the computer, it does require root as of the pie update because xiaomi disabled diag mode by default... :/
To enable it in the pie update you need to enter the following in adb shell for it to show up in qpst:
su
setprop sys.usb.config acm,diag,mtp,adb
setprop persist.sys.usb.config acm,diag,mtp,adb
Note, do not reboot yet, rebooting resets these values..
Then re- insert the phone into your computer and it should show up.
The nice thing is that this survives ota and root removal once put on so if you want ota you can have it, just unroot once you get the mod working.
Click to expand...
Click to collapse
Can't seem to make the phone appear in PDC as well, I've rooted the device with magisk and have tried to input the commands as suggested but it is still not being detected...
This is what I have
Any word on this?
Update, with stock you need to enter the command
setprop sys.usb.config diag,adb
While the phone is plugged in to the computer for it to work. I was using a different set of debug tools.
I had to use the following command to get PDC to work.
su
setenforce 0
setprop sys.usb.config diag,serial_cdev,rmnet,adb
Im running Pixel Experience 20190320 rom with Magisk 18.1.
QPST 2.7.460
I used the QUD.WIN.1.1 Installer-10040.5 drivers on Windows 10 x64.
Could you unroot and relock bootloader and have this continue working and survive OTA updates?
---------- Post added at 11:18 PM ---------- Previous post was at 10:25 PM ----------
Looks like this survives a complete fastboot flash/relock. How would you reverse this and go back to stock?
---------- Post added at 11:30 PM ---------- Previous post was at 11:18 PM ----------
I want to switch back because sometimes when I make calls, it's high pitched and quiet. I can turn off voLTE to go back to the way it was, but would be nice to be stock again.
What bands it's unlocked?
In Brazil is primordial that b28 is unlocked to use Volte (700 MHz)
joaomiguelsm said:
What bands it's unlocked?
In Brazil is primordial that b28 is unlocked to use Volte (700 MHz)
Click to expand...
Click to collapse
Doesn't unlock any bands, just enables voLTE on T-Mobile in the USA. Unfortunately, it's pretty buggy, maybe due to recent updates.
Ulver said:
Doesn't unlock any bands, just enables voLTE on T-Mobile in the USA. Unfortunately, it's pretty buggy, maybe due to recent updates.
Click to expand...
Click to collapse
Oh, sad
This is the worst thin of Xiaomi in Brazil
PDC not recognizing phone
Hi,
I've been trying to get this working off and on for a couple of weeks. I can't get PDC to populate the drop down menu. I am able to get QPST to recognize the phone after doing :
su
setprop sys.usb.config diag,adb in an adb shell. After those commands, the Qualcomm driver loads (according to device manager). QPST configuration finds the phone on COM9. But when I load PDC I get nothing. Any thoughts? The voice calling on 2g in New York is horrible.
Thanks, Mike
mtrohan said:
Hi,
I've been trying to get this working off and on for a couple of weeks. I can't get PDC to populate the drop down menu. I am able to get QPST to recognize the phone after doing :
su
setprop sys.usb.config diag,adb in an adb shell. After those commands, the Qualcomm driver loads (according to device manager). QPST configuration finds the phone on COM9. But when I load PDC I get nothing. Any thoughts? The voice calling on 2g in New York is horrible.
Thanks, Mike
Click to expand...
Click to collapse
im getting same problem... can solve??
pleaaaase... need help.
Related
You do everything here at your own risk. I take no responsibility for any broken devices/sdcards/your house going down on fire and everything else.
PLEASE DO NOT MIRROR THESE FILES!
Requirements:
root
ability to use mouse and keyboard
terminal emulator on your phone
What do you get for doing this?
Propably you'll be able to use a lot more bands than before. Most likely your phone will work on every place in the world now.
Check the third post for a link to OPO guide
C6903
before
{
"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"
}
after
1. Download this zip Google it as it's banned from xda for the ability of imei change
2. Extract it and install QPST from that zip
3. Open the caller app and type in *#*#8778#*#* (it should go off the screen after you type in the last symbol "*"
3.5 Those on custom roms (tested on cyanogen 11 with s4 mini) can use the efs professional toolkit to change the mode to enable the diag port.(Thanks @blackburn !)
4. Connect your phone to your PC
5. Open ADB console
6. Type in these commands:
Code:
adb shell
su
setprop persist.usb.eng 1
7. Turn off USB Debugging, Disconnect your phone from the PC
8. Wait about 10 seconds (don't have to be exact, just let it all disconnect in the PC) and turn USB Debugging back on
10. Connect it back to the PC. It should try to install drivers. Wait until it fails to install all of them.
11. Open device manager - you will see your device model a few times. Go to details tab. Scroll down a single time on that tab. You will see MI_0x there.
12. Go through those devices until you find MI_04 under the second drop down position.
13. Select "update driver" for this device and install the htc driver from the zip.
14. Press start button and navigate to QPST -> QPST Configuration
15. Go back to device manager -> modems -> HTC
16. Find "COM*" in my case it was "COM3". It might be different for you.
17. In QPST Configuration click on "Add new port" and in "Port" type in your "COM*". In my case It's "COM3" in there. In Port label it could be anyting u want. In my case I used a Z1 so I typed IN "Z1".
18. It should look like this now.
19. Navigate to QPST/bin and open RV_NV_Manager.exe
20. press on settings -> Comport and choose your COM port.
21. Press on file -> read from phone
22. Wait patiently until it is finished. Now pay attention!
23. Go to line 1877, click it and copy the decimal number on the right side of a programme. right click - copy
24. Go to the place where you extracted the zip from the first step and start mzTool
25. On the left side you will see "Input radix" - press decimal there.
26. On the right side you will see "RF BC CONFIG" paste your previously copied number from the RV_NV_Manager.exe there.
27. You will see now what bands are you able to use on the bottom of the app in "Bit information"
28. Switch tab to "Band Preference (NV Value)"
29. In there select all GSM bands and WCDMA bands. This place is really a field of testing. In my case (C6903 LTE) I selected all of GSM and WCDMA. I wouldn't suggest you to do anyting else in here unless you know what your'e doing. Let me know if you got something interesting in there.
30. After you're done choosing what bands do you want - copy decimal number from the bottom right
31. Remove all commas from that number ( "," ) so it would be just a bunch of numbers without anything else.
32. Open RV_NV_Manager.exe from the point you left it (step 23) and paste your new number without commas "," there.
33. Press on write NV and then press on file ->write changed NV to the phone.
34. Open up the terminal emulator on your phone and write there this:
Code:
su
setprop persist.usb.eng 0
35. Reboot the device and hope you'll have the reception. If you do, hooray!
36. Type in *#*#SERVICE#*#* (*#*#7378423#*#*) to see your new bands that your phone can use!
If your phone can't boot then flash stock FTF to your device and you should have your reception back!
Enjoy!
I wanted to mention that I'm just the guy that was interested in this and the person that actually made it possible is @BlackSoulxxx all thanks go to him! He's the guy that did it! Please thank him in the second post!
PLEASE DO NOT ASK ME IF IT WORKS ON YOUR DEVICE! I DON'T KNOW. YOU HAVE TO TRY IT YOURSELF.
If you have any problems or issues here's some help from other users http://forum.xda-developers.com/showpost.php?p=55321344&postcount=3
Tested on: ZU, Z1,SP,Xperia TL,Sharp-DOCOMO Aquos Zeta SH-04F
Dangerous stuff to experiment with. Already lost 2 phone (2 expensive paper-weight with OmniBalance design -_- )
But ENJOY!
And remember to check out *#*#4636*#*# to select band (I dont advice to do that, because to revert it you will have to reflash baseband)
And the setting
@olokos
BlackSoulxxx said:
Hey, for everyone with error "execptionthrow" error pls use QXDM and search for nv 1877 and change it
Click to expand...
Click to collapse
Nexus connection
1. Remove all installed drivers.
2. Install LG United Mobile Driver
3. Enable debugging and install adb driver if it's not automatically installed.
4. Using adb issue the following commands on a separate line
Code:
adb shell
su
setprop sys.usb.config diag, adb
5. Your phone should start installing drivers, once installed under Ports in device manager there should be (* indicates a number):
LGE AndroidNet for Diagnostics Port (COM*)
LGE AndroidNet USB Serial Port (COM*)
Thanks for that @CHAMAVELI !
kevin3688 said:
For GSM HTC Phones.
Use "setprop sys.usb.diag.config diagon" instead of "setprop persist.usb.eng 1"
Click to expand...
Click to collapse
One Plus One guide
Moto Droid RAZR Guide
XIAOMI MI2 Guide
LG G3 D852 Guide
Device-specific drivers and Z2 LTE unlock here:
http://forum.xda-developers.com/showthread.php?p=55394190
LTE Unlock guide based on OPO
http://forum.xda-developers.com/showpost.php?p=56577252&postcount=455
olokos said:
Massive stuff. I'm writing it down right now. wait for it.
Click to expand...
Click to collapse
Haha ok, we all waiting ^^
Send from my XZ With My Own Personal Modified MoonWalker SuperB !
What about this thread,I don't understand. You will open a port or an app thread,right?
Mazellat said:
What about this thread,I don't understand. You will open a port or an app thread,right?
Click to expand...
Click to collapse
Much bigger than that. Look at @BlackSoulxxx signature. I'm almost done writing it all down. Hang tight
Finally did it
olokos said:
Much bigger than that. Look at @BlackSoulxxx signature. I'm almost done writing it all down. Hang tight
Click to expand...
Click to collapse
I don't see anything his sign. and waiting for you
Mazellat said:
I don't see anything his sign. and waiting for you
Click to expand...
Click to collapse
Already did it! Try it by yourself!
I forget to tell you that this can works with UB and LB If you want to unlock for non-Xperia device that power by SD PM me....
Is it also supposed to work on the LTE bands, or just GSM and WCDMA? For instance, would it reveal any 'hidden' LTE bands on LT30AT?
ArtDC said:
Is it also supposed to work on the LTE bands, or just GSM and WCDMA? For instance, would it reveal any 'hidden' LTE bands on LT30AT?
Click to expand...
Click to collapse
Yes, works with GSM/WCDMA/LTE, even with CDMA if you phone supporting them. About hidden band, just give it a try
But if your phone is 3G variant, it will unlock wcdma/gsm band only. Using LTE version, result like OP screenshot
Tempted to try this out but what happens if we mess up something? Just do a nandroid and everything is fine?
Ahki767 said:
Tempted to try this out but what happens if we mess up something? Just do a nandroid and everything is fine?
Click to expand...
Click to collapse
Reflash baseband from full ftf
BlackSoulxxx said:
Reflash baseband from full ftf
Click to expand...
Click to collapse
When i disconnect and reconnect, it just worked normally without trying to install drivers
Ahki767 said:
When i disconnect and reconnect, it just worked normally without trying to install drivers
Click to expand...
Click to collapse
Repeat the step
1. Dial *#*#8778#*#*
2. open adb
adb shell
su
setprop persist.usb.eng 1
Click to expand...
Click to collapse
3. turnoff usb debugging and unplug the phone
4. wait 10s, turn on usb debug and connect it again to pc
1. Dial *#*#8778#*#* ---> I try several times and will not turn off
erick_shadow said:
1. Dial *#*#8778#*#* ---> I try several times and will not turn off
Click to expand...
Click to collapse
When you dial it, it will dissappear right? If so, that's ok. Stay on the guide and olokos guide have some place wrong, I have correct it in #2 post
the mark is left on the keyboard and does nothing
How to get into Diag mode:
1) open dialer
2) enter: *#*#717717#*#*
3) you'll see a toast "diag mode enabled"
To disable diag-mode enter the same code again.
How to install drivers in Windows:
1) download and extract xiaomi_mi2_diag_driver.zip
2) after you've connected your phone in diag mode you'll see very much devices
3) choose custom source to search for driver and select the extracted folder.
4) only 3 of the devices will install it doesn't matter we don't need the others.
How to configure QPST:
1) open QPST configuration from start menu
2) on tab "ports" click on "Add new Port"
3) you should see two qualcom ports in the list. choose one and click OK.
4) if displayed phone name is SURF9615, you've selected the correct one. otherwise add the second device, too
But why?
Hello M1cha,
I'm sorry if this is obvious but what exactly can I use this for
Is it changing my IMEI?
And if so, why would I want to change it?
Again, I'm sorry if the answer is obvious and I'm just asking a stupid question.
Unrelated question:
Do you know if Xiaomi.eu will really shut down or not? I can't seem to get straight answers on the Q&A forum
Redme Note LTE TD
Hello
I used your guide and http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
to unlock the WCDMA frequencies on my Redmi NOTE LTE TD ... bought in china .... everything OK ... but the phone works on GPRS ... I have also tried using the menu * # * # 4636 # * # * .. but nothing ..
do you have same idea ??
thank you !
Gobbenobber said:
Hello M1cha,
I'm sorry if this is obvious but what exactly can I use this for
Is it changing my IMEI?
And if so, why would I want to change it?
Again, I'm sorry if the answer is obvious and I'm just asking a stupid question.
Unrelated question:
Do you know if Xiaomi.eu will really shut down or not? I can't seem to get straight answers on the Q&A forum
Click to expand...
Click to collapse
On mi2 u can't change the IMEI because it's locked.
But you can change several settings and unlock bands.
I don't think MA shuts down soon but Marks ups and downs are very annoying.
mzz75 said:
Hello
I used your guide and http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
to unlock the WCDMA frequencies on my Redmi NOTE LTE TD ... bought in china .... everything OK ... but the phone works on GPRS ... I have also tried using the menu * # * # 4636 # * # * .. but nothing ..
do you have same idea ??
thank you !
Click to expand...
Click to collapse
Maybe these bands really aren't supported by hardware?
m11kkaa said:
On mi2 u can't change the IMEI because it's locked.
But you can change several settings and unlock bands.
I don't think MA shuts down soon but Marks ups and downs are very annoying.
Maybe these bands really aren't supported by hardware?
Click to expand...
Click to collapse
but when I enable WCDMA ..i can see the network [0]=CellInfoWcdma ..... but the type of network is still GPRS ... maybe some setting?
I don't think so. That's the normal behavior if a band isn't supported.
You can even enabled LTE but it won't work because the hw doesn't support it.
Modem Dead
I'm sorry to bother you again, but I have a big problem ..... with Qualcomm QPST I have a modified live parameters for the WCDMA network, but now the modem does not work anymore (2g, 3g, lte) and I can not connect the phone with QPST (say NO pHONE) .... I can do something ??
thanks
Well you have to restore the parameters to the original ones. I hope you made a backup.
m11kkaa said:
Well you have to restore the parameters to the original ones. I hope you made a backup.
Click to expand...
Click to collapse
I can not do the restore ... QPST Configurator does not see the phone ... or is there another method ??
Is it possible to enable wcdma band 900 MHz on mi2s?
orlanddon said:
Is it possible to enable wcdma band 900 MHz on mi2s?
Click to expand...
Click to collapse
I'd like to know that, too
i have one of the first batch of mi2 without wcdma 900 and it's very important to my operator so you know if it's hw supported or not? If i mess up with miflash i will restore everything or not? After a wipe i must repeat all the procedure?
Does somebody know which code it is for Redmi2? *#*#717717#*#* doesn't work... I want to try to unlock LTE band 20 (800Mhz), do you think any chance?
Any of you have got unlock 900MHz 3G on MI2 with this ?
Very interested in.
regards
I tried the tips but something's wrong :
QPST is ok i see my phone MI2 : APQ8064
With RF NV manager i got the error when i read from phone :
NvManager::getNvItemsFromPhone( const string comPort ) - QpstServer::sendSyncImpl - Bad response from phone (DM packet commands 19-24)
Again when i tried to make a backup :
"Memory Backup failed"
"Disk Error while writing to file"
Really stange... any advise ?
m11kkaa said:
How to get into Diag mode:
1) open dialer
2) enter: *#*#717717#*#*
3) you'll see a toast "diag mode enabled"
To disable diag-mode enter the same code again.
How to install drivers in Windows:
1) download and extract xiaomi_mi2_diag_driver.zip
2) after you've connected your phone in diag mode you'll see very much devices
3) choose custom source to search for driver and select the extracted folder.
4) only 3 of the devices will install it doesn't matter we don't need the others.
How to configure QPST:
1) open QPST configuration from start menu
2) on tab "ports" click on "Add new Port"
3) you should see two qualcom ports in the list. choose one and click OK.
4) if displayed phone name is SURF9615, you've selected the correct one. otherwise add the second device, too
Click to expand...
Click to collapse
Hi M1cha, I'd like to so a backup, but I can't let it work.
My problems start from the biginning: when I enter the code I got no toast message. I tried to connect anyway the phone (when is on, with and without debug option), but I don't see much devices, only the usual MI2 MTP.
Suggestions? Could be ROM releated?
Fortinho said:
Hi M1cha, I'd like to so a backup, but I can't let it work.
My problems start from the biginning: when I enter the code I got no toast message. I tried to connect anyway the phone (when is on, with and without debug option), but I don't see much devices, only the usual MI2 MTP.
Suggestions? Could be ROM releated?
Click to expand...
Click to collapse
yes, this works in MIUI only
m11kkaa said:
yes, this works in MIUI only
Click to expand...
Click to collapse
Still problems :/
I got this:
{
"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"
}
And If I try to update drivers individually, only one will successfull install. It's normal?
Anyway, after that, I don't know how to open QPST configuration from start menu. What start menu?
Thank you.
Fortinho said:
Still problems :/
I got this:
And If I try to update drivers individually, only one will successfull install. It's normal?
Anyway, after that, I don't know how to open QPST configuration from start menu. What start menu?
Thank you.
Click to expand...
Click to collapse
Up.
Fortinho said:
If I try to update drivers individually, only one will successfull install. It's normal?
Click to expand...
Click to collapse
I don't know but you will see after with qpst if it works.
Fortinho said:
I don't know how to open QPST configuration from start menu. What start menu?
Click to expand...
Click to collapse
What windows do you've got?
With Seven : Start menu is bottom left on your screen
With 8 : go on the mosaic screen (where you have all your program) and type QPST. You will find QPST configuration
Please follow the updated directions provided by Bendrexl below before attempting any other methods.
bendrexl said:
Here's a roundup of essential steps from this thread that worked for me...
:good: HUGE THANKS to: Whoareyou, docna, caspar347, Dishe
Prepare for battle:
Ensure your Verizon Moto E 2015 is configured for USB debugging.
Ensure your Verizon Moto E 2015 has airplane mode enabled.
Ensure your PC/Mac has the Android SDK Platform Tools installed & accessible via your terminal / command line (added to $PATH var).
Download 5.0.2 factory image: http://forum.xda-developers.com/moto-e-2015/general/stocks-firmwares-moto-e-t3113235/page2?nocache=1 (Thanks to caspar347!)
Unzip / expand this .zip archive.
Open a terminal session in the directory you just unzipped (containing NON-HLOS.bin & fsg.mbn)
Execute!
In your terminal with phone plugged in:
$ adb reboot bootloader (your phone should now reboot into bootloader, wait for this)
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot (WAIT for phone to fully boot before continuing)
$ adb shell (your command prompt will change to something like [email protected]_cdma:/ $. If you get kicked out of the session while entering the next commands, just type adb shell again and pick up where you left off)
[email protected]_cdma:/ $ pm clear com.android.providers.telephony
[email protected]_cdma:/ $ settings put global preferred_network_mode 9
[email protected]_cdma:/ $ settings put global preferred_network_mode1 9
[email protected]_cdma:/ $ settings put global preferred_network_mode2 9
[email protected]_cdma:/ $ pm hide com.motorola.setupwizard.phoneservice (optional)
[email protected]_cdma:/ $ exit (or just unplug & reboot phone)
$ adb reboot (or just unplug & reboot phone)
On the phone:
Turn off Airplane mode
Open Settings app > More > Cellular Networks
Ensure Preferred network type selected is "4G (recommended)"
Under Access Point Names, add the appropriate APNs for your specific carrier. (for Fi data, I only needed "h2g2").
Disable all Verizon apps through settings or Titanium Backup. (Optional)
CREDITS: Whoareyou, docna, caspar347, Dishe
Click to expand...
Click to collapse
IF YOUR DEVICE IS RUNNING 5.1, FOLLOW THE GREEN INSTRUCTIONS!
In order to attempt to get Verizon/Motorola to push out a new update with a fix for the removal of the option to switch to GSM, please sign this petition on Change.org and share it to anyone who you know will sign it! https://www.change.org/p/verizon-daniel-s-mead-stop-carrier-locking-motorola-moto-e-lte-xt1528
Background Info: I work at Walmart in the Connection Center, and today I had a customer wanting to switch to Family Mobile from AT&T, so I showed them our Family Mobile devices and T-Mobile Devices, they didnt seem interested in them and said they wanted somthing that had Android 5.0 Lollipop, I thought about it for a minute and remembered that the Moto E (2015) shipped with Lollipop installed, I also knew that Verizon phones come unlocked, so I showed them the device and they decided to go with it, they bought the Family Mobile Micro SIM starter kit, and the Moto E, but once I powered it on, I couldn't get it to connect to Family Mobile, so I tried to access the advanced radio menu (*#*#4636#*#*) to no avail, but I eventually got it working, with full LTE support, heres how:
POSSIBLE SIM SWAP WORKAROUND (Reported by wogeboy):
Disable vzwAPNpermissions.apk and vzwAPNservice.apk using this program: http://bit.ly/1HHyVao
I have not tested this as I dont have a VZW Moto E to test it on.
5.1 Updated Instrcutions:
With the SIM you want to use the the phone :
1. Put the phone into Airplane mode (I'm not sure this is needed, but it doesn't hurt)
2. Go to Settings -> About Phone and tap on "Build Number" until it says you are in Developer Mode (~10 times)
3. Go back one menu, and right above About Phone there should now be an option for Developer Options, go into that.
4. Turn on USB Debugging
5. Connect the phone to your computer and type "adb shell" in your CMD window
6. Run the following commands in adb shell :
pm clear com.android.providers.telephony
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
settings put global preferred_network_mode2 9
7. Turn off Airplane mode
8. Power off and Restart the phone
9. Open up the settings app, go to the mobile networks panel, select "Prefered Network Mode" and change it to "4G"
10. Input the appropriate APNs for your specific carrier
11. (Optional). Disable all Verizon apps through settings or Titanium Backup.
CREDIT: docna
.
5.0.2 Instructions:
1. Power on the device with the GSM SIM card in the SIM card slot
2. Connect to WiFi and complete Google Sign-In
3. Go to the Play Store and search "Network" download the first app (A white circle with a black phone in it) (This will allow us access to the advance radio options)
4. Open the "Network" shortcut
5. Change the radio mode from "CDMA/LTE PRL" to "GSM/LTE Auto"
6. Open up the settings app, go to the mobile networks panel, select "Prefered Network Mode" and change it to "4G"
7. Input the appropriate APNs for your specific carrier
8 (Optional). Disable all Verizon apps through settings or Titanium Backup.
The only thing I couldnt solve was how to remove the "SIM Card is not from Verizon Wireless" error in the status bar permanently, but thats just an annoyance, and causes no usability decrease.
This Works!
Thanks a lot, had been trying to get the GSM working. The "Network" app in the Play Store give access to the hidden radio selection menu. Verizon was able to disable all other way to enter the radio selection menu but this one did it. I think there is a apk file somewhere which disables the annoying "NOT verizon SIM" message. I will post here if I find that works.
That's a lot easier than poking around in NVram! Thanks, OP. And yeah, there's a Setup app or something you need to freeze for then sim error. I'll have to get mine out and find it.
Here are screen snaps. The VZ phone is actually picking up LTE for Ting (T-Mobile).
{
"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"
}
Nice. This is definitely some progress. Still waiting for the sprint version to be unlocked.
Whoareyou said:
Background Info: I work at Walmart in the Connection Center, and today I had a customer wanting to switch to Family Mobile from AT&T, so I showed them our Family Mobile devices and T-Mobile Devices, they didnt seem interested in them and said they wanted somthing that had Android 5.0 Lollipop, I thought about it for a minute and remembered that the Moto E (2015) shipped with Lollipop installed, I also knew that Verizon phones come unlocked, so I showed them the device and they decided to go with it, they bought the Family Mobile Micro SIM starter kit, and the Moto E, but once I powered it on, I couldn't get it to connect to Family Mobile, so I tried to access the advanced radio menu (*#*#4636#*#*) to no avail, but I eventually got it working, with full LTE support, heres how:
1. Power on the device with the GSM SIM card in the SIM card slot
2. Connect to WiFi and complete Google Sign-In
3. Go to the Play Store and search "Network" download the first app (A white circle with a black phone in it) (This will allow us access to the advance radio options)
4. Open the "Network" shortcut
5. Change the radio mode from "CDMA/LTE PRL" to "GSM/LTE Auto"
6. Open up the settings app, go to the mobile networks panel, select "Prefered Network Mode" and change it to "4G"
7. Input the appropriate APNs for your specific carrier
8 (Optional). Disable all Verizon apps through settings or Titanium Backup.
The only thing I couldnt solve was how to remove the "SIM Card is not from Verizon Wireless" error in the status bar permanently, but thats just an annoyance, and causes no usability decrease.
Click to expand...
Click to collapse
Thanks a ton for this! Do you know what the APN setting should be for T-Mobile? That's my current challenge. Every site has a different opinion. Including T-Mobile.
APN: fast.t-mobile.com
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
that should be all you have to set
Method Works on SPRINT AND BOOST too
Thanks
This method works on Boost and Sprint too.
Tested in INDIA working fine with indian GSM carriers.
Whoareyou said:
Background Info: I work at Walmart in the Connection Center, and today I had a customer wanting to switch to Family Mobile from AT&T, so I showed them our Family Mobile devices and T-Mobile Devices, they didnt seem interested in them and said they wanted somthing that had Android 5.0 Lollipop, I thought about it for a minute and remembered that the Moto E (2015) shipped with Lollipop installed, I also knew that Verizon phones come unlocked, so I showed them the device and they decided to go with it, they bought the Family Mobile Micro SIM starter kit, and the Moto E, but once I powered it on, I couldn't get it to connect to Family Mobile, so I tried to access the advanced radio menu (*#*#4636#*#*) to no avail, but I eventually got it working, with full LTE support, heres how:
1. Power on the device with the GSM SIM card in the SIM card slot
2. Connect to WiFi and complete Google Sign-In
3. Go to the Play Store and search "Network" download the first app (A white circle with a black phone in it) (This will allow us access to the advance radio options)
4. Open the "Network" shortcut
5. Change the radio mode from "CDMA/LTE PRL" to "GSM/LTE Auto"
6. Open up the settings app, go to the mobile networks panel, select "Prefered Network Mode" and change it to "4G"
7. Input the appropriate APNs for your specific carrier
8 (Optional). Disable all Verizon apps through settings or Titanium Backup.
The only thing I couldnt solve was how to remove the "SIM Card is not from Verizon Wireless" error in the status bar permanently, but thats just an annoyance, and causes no usability decrease.
Click to expand...
Click to collapse
Hello. It does not work in Ukraine. Tried many operators. Line GSM only emergency calls and all.I choose the network settings and 2G and 3G. Prompt what to do please.
_Z_x_Z_ said:
Hello. It does not work in Ukraine. Tried many operators. Line GSM only emergency calls and all.I choose the network settings and 2G and 3G. Prompt what to do please.
Click to expand...
Click to collapse
The device may not support Ukrainian bands, check with your carrier to see what band they use for HSPA/LTE
I'll have to get mine out and find it.
This only kinda works with T-Mobile. No LTE or 3G, just edge - and that keeps disconnecting and reconnecting about once every minute or so. I'll have to look into the return/exchange policy if I can't get data working.
brotherswing said:
This only kinda works with T-Mobile. No LTE or 3G, just edge - and that keeps disconnecting and reconnecting about once every minute or so. I'll have to look into the return/exchange policy if I can't get data working.
Click to expand...
Click to collapse
You must be in a non-refarmed area, in Shawnee, KS i was able to get Edge/3G/HSPA+/LTE
Whoareyou said:
You must be in a non-refarmed area, in Shawnee, KS i was able to get Edge/3G/HSPA+/LTE
Click to expand...
Click to collapse
Yep. See my snapshot above for Ting GSM (T-Mobile) in Florida. 4G LTE indicated.
I figured it out. With WiFi on my cell signal strength fluctuates wildly, but as soon as I turn off the WiFi the signal settles down, and I get a solid LTE connection averaging about 32Mbps. Strange, but I've seen crazier things.
Side note, the XT1528 is not eligible for the Motorola unlock program, and cannot be rooted by any method currently available. Several "one click root" tools claim to support it, but don't actually work.
Sent from my XT1528 using Tapatalk
Will the boost variant work on net10
Sent from my N800 using XDA Free mobile app
syrkles said:
Will the boost variant work on net10
Sent from my N800 using XDA Free mobile app
Click to expand...
Click to collapse
I personally haven't had any luck with the Sprint variants (Virgin Mobile, Boost) but I also didn't get to try using an activated Sim card, you could try, but I'm not sure
brotherswing said:
I figured it out. With WiFi on my cell signal strength fluctuates wildly, but as soon as I turn off the WiFi the signal settles down, and I get a solid LTE connection averaging about 32Mbps. Strange, but I've seen crazier things.
Side note, the XT1528 is not eligible for the Motorola unlock program, and cannot be rooted by any method currently available. Several "one click root" tools claim to support it, but don't actually work.
Sent from my XT1528 using Tapatalk
Click to expand...
Click to collapse
That root thread won't root the XT1528?
Root must be flashed with a custom recovery, which in turn requires that the boot loader be unlocked. Since the boot loader on the XT1528 can't be unlocked, we can't use that root technique.
brotherswing said:
Root must be flashed with a custom recovery, which in turn requires that the boot loader be unlocked. Since the boot loader on the XT1528 can't be unlocked, we can't use that root technique.
Click to expand...
Click to collapse
Ahh that's for clearing that up for me!
I was planning to get a new phone with a great display, and that was exactly when RP2 went on sale. I'm otherwise satisfied with the phone, but single SIM is definitely a deal breaker in China. Given that I could not find any other phone matching my criteria, I decided to get the RP2 and tried to enable dual SIM on it. Till now I've had some success, and here is what I have done.
If you have strong demand for dual SIM like I do, you may try these steps. This thread, however, is NOT a proper nor complete guide on this topic. It is just a record of my trials - they are highly experimental, risky, and potentially broken. There is absolutely no guarantee on signal quality, stability, power consumption or even the success rate. Your device can be permanently damaged if any detail goes wrong. Make sure you understand all the risks and you are able to justify every command before typing it to your phone!
I do appreciate suggestions for the correct way, though. Comments are greatly welcomed!
My environment
QPST 2.7.477 - only PDC is used here, so any version with standalone PDC tool might do the job. But new versions required if you want to use other tools.
QXDM Professional 3.14.1144 - this one is optional. It's used to tweak some parameters, but dual SIM does work without the tweaks.
Qualcomm USB drivers 2.1.2.0 from 2015/7/8 - older versions might work as well.
Windows 10, 1803
arter97's kernel and Magisk-patched stock kernel images readily at hand. The latter can be obtained by patching a stock kernel image in Magisk Manager with "Keep dm-verity/avb 2.0" UNTICKED. I had the latter installed on the phone.
Make sure root shell can be obtained during boot with ALL kernel images. This is an important recovery approach if the phone bootloops.
Steps
I've gone through a tricky path to confirm that there is indeed a second IMEI in the phone prior to the steps, which supported follow-up researching. This thread will not cover this part as this is merely trial-and-error. I will provide suggestions on diag connection though.
1. make a backup of all partitions on the phone, leaving out system, vendor and userdata partitions of course. There are 88 partitions in my backup.
2. make a QCN backup of modem NV. This step could be optional as modemst1/2 has already been backed-up in previous step - I'm not sure about this, and have completed this step whatsoever.
3. make a backup of /vendor/etc/vintf/manifest.xml, and add slot2 instances to the following HALs:
android.hardware.radio - this one has 2 interfaces, and both of them need the slot2 addition
vendor.qti.hardware.radio.am
vendor.qti.hardware.radio.qtiradio - this one has 2 versions, and both of them need the slot2 addition
4.
Code:
adb shell su -c setprop persist.radio.multisim.config dsds
5. find any USB mode with rmnet in /vendor/etc/init/hw/init.msm.configfs.rc, and switch to it. I used "diag,serial_cdev,rmnet,dpl,adb", and that's
Code:
adb shell su -c setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb
6. Windows shows a lot of new USB devices. Force-install Qualcomm WWAN driver for the RmNet device. I chose "Network Adapters -> Qualcomm -> Qualcomm HS-USB WWAN Adapter 90B8", but anything named after "Qualcomm HS-USB WWAN Adapter" should do.
7. open PDC. There are 3 dual SIM (DSDS) hardware profiles available:
SR_DSDS-LA-7+7_mode-SDM845
SR_DSDS-WD-7+7_mode-SDM845
SR_DSDS-WP8-7+7_mode-SDM845
The one with WP8 in its name can be ignored, and here comes the hard choice.
I tried the WD one in the first place: activated it in the context menu on Sub0 then Sub1, and clicked Activate twice. PDC complained about malformed packet after second click, and the profile was shown as Active on Sub0, and Pending on Sub1. Nothing bad happened after a reboot, regardless of the errors above. Two SIM slots were present in About Phone, and second IMEI is correctly shown there as well. Upon inserting two SIM cards I got dual VoLTE online, and everything behaved like a normal dual SIM SDM845 device. There were some little glitches though: once or twice a day signal bars disappeared and popped up again in a few seconds. Mobile data also stuttered at random times, though not frequent - sometimes mobile data was stable for the whole day. I was satisfied with the results, and made another backup of partitions.
Then I started comparing the WD and LA profiles. I quickly realized that LA marked the phone as DSDS while WD as SS in the device_mode NV entry (I honestly had no idea why dual SIM just worked with WD). There were other differences unknown to me, but LA seemed more "correct" and I decided to switch to this profile. After deactivating WD on both Sub0 and Sub1, I activated LA on Sub0 but not Sub1. The phone could still make use of two SIMs, but without VoLTE on either card. LTE was still available for both cards though. The glitches with WD were mostly gone (data still stuttered but recovered much faster), and the phone SEEMED cooler and battery SEEMED to drain slower.
Finally I could not understand the lack of VoLTE and switched back to WD (still Sub0 only). This time only the first SIM card could register on IMS/VoLTE. The second one registered on LTE but not IMS, regardless of default data card selection. Activating WD on Sub1 did not solve the problem. Manual checks/corrections on the differences between WD and LA made no effect either. I had to flash the backup made after first WD trial, and dual VoLTE worked again.
I came to the following conclusion after this step:
a. hardware profiles may be applied to Sub0 only (can anyone confirm this?)
b. a profile may not be completely reverted after applying. That is to say, same profile status does not mean same baseband behavior.
c. LA profile does not support VoLTE for some reason.
d. if you want dual VoLTE, your best bet would be activating WD on Sub0 and Sub1 right after previous steps, though Sub1 won't accept the setting.
e. mobile data may stutter with dual SIM (this could also be the fault of my service provider however)
Any clarification on this step is appreciated. If you want to enable dual SIM, you have to make your own choice here. Just remember to backup before every change.
8. apply some NV changes from LA on WD base:
ue_usage_setting: from DATA_CENTRIC to VOICE_CENTRIC
device_mode: from SS to DSDS
disable_global_mode: from 1 to 0
I failed to find any difference after these changes. this step could be optional. I myself use the phone as daily driver with these changes though.
That's all. Don't worry, I'm confused as you Everything just works or fails without any valid reason
Other Details
1. RP2 uses the same SIM card slot as Samsung. I filed an card tray from Samsung S7 so that it fits RP2. Its size naturally() fits RP2, just make it as thin as Razer's tray and it will work.
2. if you want to restore a modemst1/2 backup, do that in TWRP. If this needs to be done in Android system, stop vendor.rmt_storage first.
3. if the phone reboots to recovery right after booting to lock screen, this could be SIM count in baseband and system diverging. Run
Code:
adb shell su -c setprop persist.radio.multisim.config ss
during boot to see if this fixes the problem. If it does, restore all backups then start all over.
4. QPST does not recognize the diag port from the phone upon USB connection. Do this so that diag port works:
Code:
# in adb shell, assuming USB mode has already been switched
su
setenforce 0
stop vendor.per_mgr
# wait a few sec until QPST recognizes SDM845 on the diag port
start vendor.per_mgr
# SDM845 disappears and re-appears after a few sec, and QPST is usable
5. arter97's kernel disables diag drivers, and QPST could never recognize the phone. You have to use stock kernel if you intend to use anything other than PDC.
Screenshots and photos:
Screenshot of About Phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot of dual VoLTE:
Photos of the filed card tray inside RP2:
The original Samsung tray:
And after filing:
Reserved for minor fixes
that's interesting
i have tried this, but the second imei doesn't appears what am I doing wrong?
ps: i find second imei in QCN backup
IMG
I finally got it
i updated to rom deodexed and zipalign from Warrior1988
after that I looked at the settings, the second Imei appeared
then I put sim card, android recognizes then it worked
PS: i modded SIM Card with MicroSD, now i have dual SIM with MicroSD :laugh:
IMG
unfortunately, now i see this message on starting, but starts normally (don't shutdown) :victory:
IMG
Update: you can remove this with command
reboot "dm-verity enforcing"
Hey man! What sim card tray did you use and how did you modify it for dual SIM and sdcard?
Using a command to reverify the DM will get rid of the red text and boot
th3cavalry said:
Hey man! What sim card tray did you use and how did you modify it for dual SIM and sdcard?
Using a command to reverify the DM will get rid of the red text and boot
Click to expand...
Click to collapse
I did this method, and used default sim card tray
and thanks for command
So I'm stuck at step 7. I have the both SIM slots showing in the phone but no IMEI for SIM2. When I open PDC it doesn't show anything.
When we add the slot2, do we add slot1,slot2 or do we add a whole nother line in the file for slot2?
Did you have any issues with PDC in the beginning?
updateing said:
I was planning to get a new phone with a great display, and that was exactly when RP2 went on sale. I'm otherwise satisfied with the phone, but single SIM is definitely a deal breaker in China. Given that I could not find any other phone matching my criteria, I decided to get the RP2 and tried to enable dual SIM on it. Till now I've had some success, and here is what I have done.
If you have strong demand for dual SIM like I do, you may try these steps. This thread, however, is NOT a proper nor complete guide on this topic. It is just a record of my trials - they are highly experimental, risky, and potentially broken. There is absolutely no guarantee on signal quality, stability, power consumption or even the success rate. Your device can be permanently damaged if any detail goes wrong. Make sure you understand all the risks and you are able to justify every command before typing it to your phone!
I do appreciate suggestions for the correct way, though. Comments are greatly welcomed!
My environment
QPST 2.7.477 - only PDC is used here, so any version with standalone PDC tool might do the job. But new versions required if you want to use other tools.
QXDM Professional 3.14.1144 - this one is optional. It's used to tweak some parameters, but dual SIM does work without the tweaks.
Qualcomm USB drivers 2.1.2.0 from 2015/7/8 - older versions might work as well.
Windows 10, 1803
arter97's kernel and Magisk-patched stock kernel images readily at hand. The latter can be obtained by patching a stock kernel image in Magisk Manager with "Keep dm-verity/avb 2.0" UNTICKED. I had the latter installed on the phone.
Make sure root shell can be obtained during boot with ALL kernel images. This is an important recovery approach if the phone bootloops.
Steps
I've gone through a tricky path to confirm that there is indeed a second IMEI in the phone prior to the steps, which supported follow-up researching. This thread will not cover this part as this is merely trial-and-error. I will provide suggestions on diag connection though.
1. make a backup of all partitions on the phone, leaving out system, vendor and userdata partitions of course. There are 88 partitions in my backup.
2. make a QCN backup of modem NV. This step could be optional as modemst1/2 has already been backed-up in previous step - I'm not sure about this, and have completed this step whatsoever.
3. make a backup of /vendor/etc/vintf/manifest.xml, and add slot2 instances to the following HALs:
android.hardware.radio - this one has 2 interfaces, and both of them need the slot2 addition
vendor.qti.hardware.radio.am
vendor.qti.hardware.radio.qtiradio - this one has 2 versions, and both of them need the slot2 addition
4.
Code:
adb shell su -c setprop persist.radio.multisim.config dsds
5. find any USB mode with rmnet in /vendor/etc/init/hw/init.msm.configfs.rc, and switch to it. I used "diag,serial_cdev,rmnet,dpl,adb", and that's
Code:
adb shell su -c setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb
6. Windows shows a lot of new USB devices. Force-install Qualcomm WWAN driver for the RmNet device. I chose "Network Adapters -> Qualcomm -> Qualcomm HS-USB WWAN Adapter 90B8", but anything named after "Qualcomm HS-USB WWAN Adapter" should do.
7. open PDC. There are 3 dual SIM (DSDS) hardware profiles available:
SR_DSDS-LA-7+7_mode-SDM845
SR_DSDS-WD-7+7_mode-SDM845
SR_DSDS-WP8-7+7_mode-SDM845
The one with WP8 in its name can be ignored, and here comes the hard choice.
I tried the WD one in the first place: activated it in the context menu on Sub0 then Sub1, and clicked Activate twice. PDC complained about malformed packet after second click, and the profile was shown as Active on Sub0, and Pending on Sub1. Nothing bad happened after a reboot, regardless of the errors above. Two SIM slots were present in About Phone, and second IMEI is correctly shown there as well. Upon inserting two SIM cards I got dual VoLTE online, and everything behaved like a normal dual SIM SDM845 device. There were some little glitches though: once or twice a day signal bars disappeared and popped up again in a few seconds. Mobile data also stuttered at random times, though not frequent - sometimes mobile data was stable for the whole day. I was satisfied with the results, and made another backup of partitions.
Then I started comparing the WD and LA profiles. I quickly realized that LA marked the phone as DSDS while WD as SS in the device_mode NV entry (I honestly had no idea why dual SIM just worked with WD). There were other differences unknown to me, but LA seemed more "correct" and I decided to switch to this profile. After deactivating WD on both Sub0 and Sub1, I activated LA on Sub0 but not Sub1. The phone could still make use of two SIMs, but without VoLTE on either card. LTE was still available for both cards though. The glitches with WD were mostly gone (data still stuttered but recovered much faster), and the phone SEEMED cooler and battery SEEMED to drain slower.
Finally I could not understand the lack of VoLTE and switched back to WD (still Sub0 only). This time only the first SIM card could register on IMS/VoLTE. The second one registered on LTE but not IMS, regardless of default data card selection. Activating WD on Sub1 did not solve the problem. Manual checks/corrections on the differences between WD and LA made no effect either. I had to flash the backup made after first WD trial, and dual VoLTE worked again.
I came to the following conclusion after this step:
a. hardware profiles may be applied to Sub0 only (can anyone confirm this?)
b. a profile may not be completely reverted after applying. That is to say, same profile status does not mean same baseband behavior.
c. LA profile does not support VoLTE for some reason.
d. if you want dual VoLTE, your best bet would be activating WD on Sub0 and Sub1 right after previous steps, though Sub1 won't accept the setting.
e. mobile data may stutter with dual SIM (this could also be the fault of my service provider however)
Any clarification on this step is appreciated. If you want to enable dual SIM, you have to make your own choice here. Just remember to backup before every change.
8. apply some NV changes from LA on WD base:
ue_usage_setting: from DATA_CENTRIC to VOICE_CENTRIC
device_mode: from SS to DSDS
disable_global_mode: from 1 to 0
I failed to find any difference after these changes. this step could be optional. I myself use the phone as daily driver with these changes though.
That's all. Don't worry, I'm confused as you Everything just works or fails without any valid reason
Other Details
1. RP2 uses the same SIM card slot as Samsung. I filed an card tray from Samsung S7 so that it fits RP2. Its size naturally() fits RP2, just make it as thin as Razer's tray and it will work.
2. if you want to restore a modemst1/2 backup, do that in TWRP. If this needs to be done in Android system, stop vendor.rmt_storage first.
3. if the phone reboots to recovery right after booting to lock screen, this could be SIM count in baseband and system diverging. Run
Code:
adb shell su -c setprop persist.radio.multisim.config ss
during boot to see if this fixes the problem. If it does, restore all backups then start all over.
4. QPST does not recognize the diag port from the phone upon USB connection. Do this so that diag port works:
Code:
# in adb shell, assuming USB mode has already been switched
su
setenforce 0
stop vendor.per_mgr
# wait a few sec until QPST recognizes SDM845 on the diag port
start vendor.per_mgr
# SDM845 disappears and re-appears after a few sec, and QPST is usable
5. arter97's kernel disables diag drivers, and QPST could never recognize the phone. You have to use stock kernel if you intend to use anything other than PDC.
Click to expand...
Click to collapse
th3cavalry said:
So I'm stuck at step 7. I have the both SIM slots showing in the phone but no IMEI for SIM2. When I open PDC it doesn't show anything.
When we add the slot2, do we add slot1,slot2 or do we add a whole nother line in the file for slot2?
Click to expand...
Click to collapse
PDC works for me from the beginning. Please check:
1. Did you install the correct driver for the RmNet device?
2. There is a combo box in PDC window with nothing selected by default. Could you choose HS-USB WWAN Adapter in its dropdown list?
th3cavalry said:
So I'm stuck at step 7. I have the both SIM slots showing in the phone but no IMEI for SIM2. When I open PDC it doesn't show anything.
When we add the slot2, do we add slot1,slot2 or do we add a whole nother line in the file for slot2?
Click to expand...
Click to collapse
for me the second IMEI only worked after I installed this https://forum.xda-developers.com/razer-phone-2/development/rom-mr1-stock-deodexed-zipalign-t3916502
and to PDC work i used this driver https://androidfilehost.com/?fid=11410963190603864074
Wait, so... Even though this is a single-SIM phone, it has a second IMEI in it, and the hardware to read a second SIM? All they had to do to make this officially dual-SIM was make a slightly different SIM tray and change the hardware profile?
Gamesoul Master said:
Wait, so... Even though this is a single-SIM phone, it has a second IMEI in it, and the hardware to read a second SIM? All they had to do to make this officially dual-SIM was make a slightly different SIM tray and change the hardware profile?
Click to expand...
Click to collapse
Maybe they need more resources to fine tune dual SIM experiences (if they have not given up the plan for this variant). For example modem could crash when IMS registration states change on both slots simultaneously (this is why my signal bars disappear from time to time), and radio performance could be drastically degraded when two slots are registered on different bands. Making a product market-ready takes much more resources than making in happen in lab, and Razer might not want to invest that much in this area.
updateing said:
Maybe they need more resources to fine tune dual SIM experiences (if they have not given up the plan for this variant). For example modem could crash when IMS registration states change on both slots simultaneously (this is why my signal bars disappear from time to time), and radio performance could be drastically degraded when two slots are registered on different bands. Making a product market-ready takes much more resources than making in happen in lab, and Razer might not want to invest that much in this area.
Click to expand...
Click to collapse
Makes sense. I suppose I shouldn't trivialize the process. It mostly just surprises me that the hardware (and some of the software) is there at all. They must have had plans to do dual-SIM up until almost the last minute, because otherwise I can't imagine why they wouldn't save the money needed to put that extra hardware in there. And I can't imagine they'll release any such thing at this point. They basically shut down their mobile phone division, and haven't even released a software update in months.
hey guys..
enabling diag is workig on android 8.1.? it was using on pie but didnt work on oreo...anyone faced wtih this pb..?
Code:
aura:/ $ su
aura:/ # setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb
aura:/ #
---------- Post added at 02:27 PM ---------- Previous post was at 02:10 PM ----------
t-mobile_mda said:
hey guys..
enabling diag is workig on android 8.1.? it was using on pie but didnt work on oreo...anyone faced wtih this pb..?
Code:
aura:/ $ su
aura:/ # [B]setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb[/B]
aura:/ #
Click to expand...
Click to collapse
i think it is not working on oreo..tried again on pie and worked again...
Code:
C:\Users\X\Desktop\Razer\Phone_2\Root\8.1>adb shell
aura:/ $ su
aura:/ # [B]setprop sys.usb.config diag,serial_cdev,rmnet,dpl,adb[/B]
C:\Users\X\Desktop\Razer\Phone_2\Root\8.1>
hey again guys..
can anyone pls sahre the modemst parts..? single sim or dual it doesnt metter..
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst2 -> /dev/block/sdf3
dd if=/dev/block/sdf2 of=/sdcard/sdf2
dd if=/dev/block/sdf3 of=/sdcard/sdf3
w.b.r.
What are the chances of breaking my phone with these steps?
Just like anything else, trial and error.
So does this kill WiFi calling?
I tried this and I jacked it up a bit. i got it to get both SIMs working (TMOUS and KT). The WiFi calling for TMOUS stopped working and also if I went to "Mobile Data" it reset the radio and never opened the menu. So i tried to revert and it got stuck in a boot loop and when i did get in the cell was completely not working, No sim, no IMEI. Luckily i flashed an older ROM (shipped 8.1MR0) and progressively upgraded through the ROMs from there and have service again. This tells me that the Stock Razer Images from their developer site don't have 'everything' for a full restore.
t-mobile_mda said:
hey again guys..
can anyone pls sahre the modemst parts..? single sim or dual it doesnt metter..
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-03-18 15:27 modemst2 -> /dev/block/sdf3
dd if=/dev/block/sdf2 of=/sdcard/sdf2
dd if=/dev/block/sdf3 of=/sdcard/sdf3
w.b.r.
Click to expand...
Click to collapse
Grab the Stock ROM for your version then extract it: https://developer.razer.com/razer-phone-dev-tools/factory-images/
All of them have "modem.img" used in there flash script in this command:
Code:
%fastboot_cmd% flash modem_a modem.img
%fastboot_cmd% flash modem_b modem.img
I don't think this works on 9MR2
Enable 5G and DSS on OnePlus 8T
As you may or may not know OnePlus didn't add proper changes into EFS configs to allow us use 5G on every network in the world. This guide will help you unlock 5G access and DSS (Dynamic Spectrum Sharing) and doesn't require root access until you don't want to access 5G in SA (standalone) mode.
I'm NOT responsible to any damage you make to your phone. There's barely any chance to damage anything, but you've been warned.
Requirements:
EngineerMode apk installed on your phone.
USB Debugging enabled on your phone.
OnePlus drivers installed on your desktop.
QPST app installed on your desktop.
Qualcomm diagnostic drivers.
Downloads:
EngineerMode apk: ApkMirror
QPST app: Mediafire
Qualcomm drivers & my configs: GDrive
Instruction #1 - enable 5G:
On your phone, dial *#801# > use EngineerMode > enable Engineer Mode Toggle (ON) and connect your device to your Desktop via USB.
On your Desktop, open Device Manager. You should see two new 'other devices'. Update their drivers by: right click > Update Driver > Browse my computer [...] > Let me pick [...] > All devices > then browse for Qualcom diagnostic drivers you've downloaded & use qcmdm.inf > choose something called 'Android Modem 9018'.
Open QPST. You should see devices in Active Phones and Ports list. If not: Add new port > add two devices shown in the list. Then: Start Clients > QPST EFS Explorer and select SDX55 device. This may take a few seconds.
Once you see EFS Explorer go to /policyman, then copy to a separate folder following files as a backup: carrier_policy.xml, carrier_policy.xml_Subscription01.
Delete those 2 files from the EFS Explorer. Find my corresponding configs and copy them over to the /policyman.
On your phone, disable Engineer Mode Toggle, disconnect from your PC and reboot.
Once booted, dial *#*#4636#*#* > Phone Information > Set preferred network type to NR/LTE/TDSCDMA/GSM/WCDMA. Now you should have 5G NSA enabled.
* To enable (force) 5G SA, you have to use Network Signal Guru app to change NR5G Mode from NSA to NSA/SA or SA. But this will require root access.
You can make sure everything is working correctly by using CellMapper app and checking 5G Status. RESTRICTED means your plan doesn't allow you to use 5G, NOT_RESTRICTED means you are too far from the cell, try to move closer, CONNECTED means everything is working perfectly. However, this method isn't ideal - every software update or SIM card change you will loose all modifications.
Instruction #2 - enable DSS:
Dynamic spectrum sharing (DSS) provides a very useful migration path from LTE to NR by allowing LTE and NR to share the same carrier.
Follow 1st and 3rd step from Instruction #1.
Once you see EFS Explorer go to /policyman and copy lte_feature_restrictions.xml file to your computer - we're going to edit it, so make a backup somewhere.
Open the file with a text editor of your choice.
You should see a section like this:
XML:
<plmn_list name="dss_plmns" ns="global">
228-01 505-01 505-11 505-39 505-71 505-72 204-04 262-01 262-06 204-16 204-20 232-03 232-07 204-04 311-480 240-02 238-06 240-01 206-01 204-08 204-12 204-18 204-69 238-01 238-10
</plmn_list>
These are the networks allowed to use DSS. Now you should go to MCC-MNC and find a proper mcc-mnc
codes for your network. Add them to the file as shown above.
Now you should find section looking like this:
XML:
<lte_feature name="NR_DSS">
<all_of>
<boolean_test name="carrier:dss_is_enabled" />
<serving_plmn_in list="dss_plmns" />
</all_of>
</lte_feature>
And change it to this:
XML:
<lte_feature name="NR_DSS">
<any_of>
<boolean_test name="carrier:dss_is_enabled" />
<serving_plmn_in list="dss_plmns" />
</any_of>
</lte_feature>
All you have to do now is to save the file, copy it over to the /policyman in the EFS Explorer and copy step 6. and 7. from Instruction #1. And that's it!
Remember: OP8T from different regions with support of the same 5G bands would sometimes not work in the NSA mode in your carrier network because of different ENDC combos and different LTE anchors. Check if your device would support your carrier network at cacombos.com.
More on how to properly edit carrier plicy files at MT-TECH Blog. Guide tested on KB2003: Play/P4, KB2007: T-Mobile and KB2005: Verizon.
Special thanks to:
Mr. Minh Truong
Mr. Abdullah Alshehri
Evenshop Themobilestore
Can you verify the driver model to install in step 2? The lowest number "MDM Diagnostics" model is 9031.
{
"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"
}
I've found other diagnostic drivers with the "9018" in them, but they don't say MDM.
jefffeely said:
Can you verify the driver model to install in step 2? The lowest number "MDM Diagnostics" model is 9031.
View attachment 5165055
I've found other diagnostic drivers with the "9018" in them, but they don't say MDM.
View attachment 5165057
Click to expand...
Click to collapse
You should use qcmdm.inf and then browse for 'Qualcomm Android Modem 9018' (it should be right on top of the list). I will add this to the main post. Sorry, my bad
bemolx said:
You should use qcmdm.inf and then browse for 'Qualcomm Android Modem 9018' (it should be right on top of the list). I will add this to the main post. Sorry, my bad
Click to expand...
Click to collapse
That fixed it, thanks!
Well I did all these steps and it made no difference for me. I still can't get 5g. I used to get it here and now I don't. I don't know if something changed on my phone or if a tower went down or what. The CellMapper app has zero 5g information in it for me, and I'm not paying $50 for the upgrade for Network Signal Guru to tell me more information. When I forced to 5G, I get absolutely nothing ):
When 5g was working it was only about 10mbps, and LTE is 100mbps, so it makes sense to stick with LTE for now. I was excited to be able to try out DSS though.
If nothing else, thanks for this guide. It was nice to get QPST up and running again. It had been a long time since I used it.
jefffeely said:
Well I did all these steps and it made no difference for me. I still can't get 5g. I used to get it here and now I don't. I don't know if something changed on my phone or if a tower went down or what. The CellMapper app has zero 5g information in it for me, and I'm not paying $50 for the upgrade for Network Signal Guru to tell me more information. When I forced to 5G, I get absolutely nothing ):
When 5g was working it was only about 10mbps, and LTE is 100mbps, so it makes sense to stick with LTE for now. I was excited to be able to try out DSS though.
If nothing else, thanks for this guide. It was nice to get QPST up and running again. It had been a long time since I used it.
Click to expand...
Click to collapse
I saw you have KB2007 so you must be in the different region. If it got worse (no 5G at all) I suggest sticking to the MT-TECH.FI blog and trying to modify carrier policy files the way Mr Minh did.
The first time I was trying to get 5G working I used many guides with many configs but none of them worked. So I followed his instruction.
It seems like every model may have different configs. I'm sorry it didn't work for you
bemolx said:
I saw you have KB2007 so you must be in the different region. If it got worse (no 5G at all) I suggest sticking to the MT-TECH.FI blog and trying to modify carrier policy files the way Mr Minh did.
The first time I was trying to get 5G working I used many guides with many configs but none of them worked. So I followed his instruction.
It seems like every model may have different configs. I'm sorry it didn't work for you
Click to expand...
Click to collapse
Sorry I wasn't clear, your guide didn't make things worse. I stopped receiving 5g at my house a couple weeks ago. I was just hoping your guide would bring it back.
In fact, I drove over to a tower today to test out your configuration. Worked great there!
jefffeely said:
Sorry I wasn't clear, your guide didn't make things worse. I stopped receiving 5g at my house a couple weeks ago. I was just hoping your guide would bring it back.
In fact, I drove over to a tower today to test out your configuration. Worked great there!View attachment 5165877
Click to expand...
Click to collapse
Ah I see. Good to see it's working.
Maybe the carrier operator decided to move the cell away or upgrade it in the near future at you home place if it was such bad at performance. Who knows
bemolx said:
Ah I see. Good to see it's working.
Maybe the carrier operator decided to move the cell away or upgrade it in the near future at you home place if it was such bad at performance. Who knows
Click to expand...
Click to collapse
I just flashed back to T-mobile's 011.0.1.3.KB09CB and 5g is back at my house, just only 5mbps lol. I am now suspecting that they changed the modem for 11.0.4.6 so that it would only switch to 5g if it had a stronger signal.
jefffeely said:
I just flashed back to T-mobile's 011.0.1.3.KB09CB and 5g is back at my house, just only 5mbps lol. I am now suspecting that they changed the modem for 11.0.4.6 so that it would only switch to 5g if it had a stronger signal.
Click to expand...
Click to collapse
Can you extract and post here carrier policy files while you're on 11.0.1.3? I'm curious to see how do they look like.
bemolx said:
Can you extract and post here carrier policy files while you're on 11.0.1.3? I'm curious to see how do they look like.
Click to expand...
Click to collapse
Here's the whole folder. I had already pulled it to compare lol.
I am on tmo using the 8t purchased at a tmo. Do i need this? I am on global rom.
kevkid said:
I am on tmo using the 8t purchased at a tmo. Do i need this? I am on global rom.
Click to expand...
Click to collapse
T-Mobile's configs are different than mine, however my configs also work just like @jefffeely posted here.
If you're lacking 5G connectivity you can try either my or jefffeely's configs. It really depends how the carrier has developed the 5G architecture around you.
Can you explain something for me?
I deleted the whole policyman folder, and there was no difference, the phone functions as if there was no problem at all, so what is going on guys?
even 5G and Volte is working well
Mod edit - translated by https://translate.google.com:
I tried to extract hydrogen files in China based on your method. I hope these XML can help you improve this operation.
The download address is
I tried to extract nitrogen files in China according to your method. Hope these XML can help you improve this operation. The download address is
**************************
我根据你的方法尝试提取了中国地区氢的文件，希望这些XML可以帮助您完善此操作。
下载地址是
我试图根据您的方法在中国提取氮气文件。希望这些XML可以帮助您改进此操作。下载地址是
chinabackup.rar
drive.google.com
Engineering Support said:
Can you explain something for me?
I deleted the whole policyman folder, and there was no difference, the phone functions as if there was no problem at all, so what is going on guys?
even 5G and Volte is working well
Click to expand...
Click to collapse
Interesting. I would like to know that as well. Was it still gone after reboot?
I also want to know what made you decide to delete the whole folder
I can confirm that this guide worked on Verizon in the U.S, at least on the n5 band. However, 5G speeds are still slower for me than 4G. While it may prove more useful in the future, I don't think 5G is mature enough to replace 4G just yet.
Engineering Support said:
Can you explain something for me?
I deleted the whole policyman folder, and there was no difference, the phone functions as if there was no problem at all, so what is going on guys?
even 5G and Volte is working well
Click to expand...
Click to collapse
That's kinda strange. I can't really tell what's going on, I wonder if you've rebooted your phone.
z9999xc said:
我根据你的方法尝试提取了中国地区氢的文件，希望这些XML可以帮助您完善此操作。
下载地址是
我试图根据您的方法在中国提取氮气文件。希望这些XML可以帮助您改进此操作。下载地址是
chinabackup.rar
drive.google.com
Click to expand...
Click to collapse
Thanks for sharing it! I'll review this in the morning.
parker.stephens said:
I can confirm that this guide worked on Verizon in the U.S, at least on the n5 band. However, 5G speeds are still slower for me than 4G. While it may prove more useful in the future, I don't think 5G is mature enough to replace 4G just yet.
Click to expand...
Click to collapse
It really depends how the 5G is developed at your location. I've tested NR NSA in different parts of a single city and sometimes it's worse than 4G too. As you said - not mature enough yet.
bemolx said:
Enable 5G and DSS on OnePlus 8T
As you may or may not know OnePlus didn't add proper changes into EFS configs to allow us use 5G on every network in the world. This guide will help you unlock 5G access and DSS (Dynamic Spectrum Sharing) and doesn't require root access until you don't want to access 5G in SA (standalone) mode.
I'm NOT responsible to any damage you make to your phone. There's barely any chance to damage anything, but you've been warned.
Requirements:
EngineerMode apk installed on your phone.
USB Debugging enabled on your phone.
OnePlus drivers installed on your desktop.
QPST app installed on your desktop.
Qualcomm diagnostic drivers.
Downloads:
EngineerMode apk: ApkMirror
QPST app: Mediafire
Qualcomm drivers & my configs: GDrive
Instruction #1 - enable 5G:
2. On your Desktop, open Device Manager. You should see two new 'other devices'. Update their drivers by: right click > Update Driver > Browse my computer [...] > Let me pick [...] > All devices > then browse for Qualcom diagnostic drivers you've downloaded & use qcmdm.inf > choose something called 'Android Modem 9018'.
Click to expand...
Click to collapse
Hi,
I am stucked in the 2nd step.
I have a KB2003 and I can't update the devices with the driver you provided.
It says that the drivers are not compatible with the device.
I can't go further.
Thanks for your help.
docles
docles said:
Hi,
I am stucked in the 2nd step.
I have a KB2003 and I can't update the devices with the driver you provided.
It says that the drivers are not compatible with the device.
I can't go further.
Thanks for your help.
docles
Click to expand...
Click to collapse
Have you tried disabling signature verification enforcement?
Are you sure you've enabled file transfer via USB?