Related
Hello..
when i switch phone mode to dm mode using ##3424#..
windows ask me driver called generic serial..i can't find it in windwos\system32\drivers..
so plz anyone can help me ..i need to switch phone to this mode so i can connect it with cdma workshop to Reset SPC code to 6 Zero's..
any reply..!!!
Dear Please Use USB Modem Driver (USBModemxp)
Please don't bring back threads that are almost 2 years old! Thanks.
will some of use still use that phone and still need to know how thank you
I in fact was looking for that answer today, so thx
I tried to ask about this in another thread but I'm going to try to be more clear on this one. I loaded my OG drivers in and put the phone in Debugging Mode and in Diag. Mode. Device manager detects 2 ports, one is for diagnostics. I then run QPST and it detects the connection but with a "?" in front of the phone description then when I open tab for connected phones its empty. I still try to open EFS and its a blank. Are there separate Diagnostics Drivers for this phone like HTC's and other phones or is the software blocking it from being read?
Here
Lokifish Marz said:
Here
Click to expand...
Click to collapse
Crap, my bad. I only posted one here because I had a similar one in Q&A but no response so I figured that "developers" would have the tech savvy to solve my issue better. I tried to edit the title on my other thread but couldn't figure out how. Please remove this thread then and tell me how to change the title of my other one.
Or, someone please PM me with a solution.....Thanks :]
Unlock efs directories/files
Ok, I installed the latest version of QPST and now I am in the EFS of my LG OG but I can't seem to be able to figure out how to unlock the directories/files in order to edit them ( similar to using the "open sesame door" method on an HTC ). Any help would be greatly appreciated. Again, feel free to PM me or Email me at "[email protected]". Thanks.
Preface
With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier - doesn't matter from which device. This has been reported to work on TMO in the US, which did not work with my other method.
Prerequsities
* You must have working DIAG mode. See my other thread for more information on how to set that up.
Downloads
* AsusVoLTE v1.0.1
* EfsTools 0.10 modded 1.2
* EFS items
* Xiaomi Mi 9T MBNs (optional)
Step 1 - setting props
Install the AsusVoLTE app from above, make sure to upgrade if you already have it installed. Run the app and press the Enable VoLTE button; this should set some properties on the device to force-enable VoLTE after we have also done the other steps below. If you already enable VoLTE using my old method you can safely skip this step.
If you prefer to not use the app, simply run this in an adb shell:
Code:
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
If you are unable to set those properties for whatever reason, like if you have returned to stock after flashing the mbn and no longer have root, there is another possibility to force VoLTE/VoWiFi; There's a secret code you can use to force-enable it, but unfortunately it does not survive a reboot (not sure why ASUS didn't make it persistent).
Enter this in the dialler:
Code:
*#*#3642623344#*#*
The number will clear itself, and you shouldn't see any output if it succeeded.
When you have done this, go to (System) Settings -> Mobile network and toggle Mobile data off then on again. You should hopefully see the VoWiFi or VoLTE icon in the status bar now, but like I said above you will have to redo this if you reboot the phone - so if you can, please use the properties method instead.
Step 2 - making sure it works
Before we begin, make sure you close down QPST, otherwise EfsTools will error out because there can not be two clients connected at once.
Unzip EfsTools from above, open up a cmd window and cd to the directory where you extracted it. Depending on how you connect to diag you will need to modify EfsTools.exe.config - if you're connecting via USB you most likely won't have to do anything as it will find the port automatically, unless you have more than one port, in which case you can simply change port from Auto to the COM port of the phone (for example COM13).
If you are connected via wifi you will need to change port to 2500 (or whatever port you used in the AsusVoLTE app) and remote to true. So the efstool line should look something like this:
Code:
<efstool port="2500" remote="true" baudrate="38400" password="FFFFFFFFFFFFFFFF" spc="000000"/>
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.
Source code:
AsusVoLTE - Github
EfsTools - Github
Let me know if this works for you, or if you have any questions.
Regards
I cannot for the life of me get either method to work. Connected via USB. DIAG mode driver is loaded on COM1, even changed Baud rate on the COM port in device manager to 38400. USB method gives me "Critical Error: Bad Command" Remote method does not send any information but indefinitely runs. I'm really not sure what else to try. Im on the latest WW Firmware with Magisk root. Is there anything else I can check? Are you on the 8 GB Tencent version?
xbamaris1` said:
I cannot for the life of me get either method to work. Connected via USB. DIAG mode driver is loaded on COM1, even changed Baud rate on the COM port in device manager to 38400. USB method gives me "Critical Error: Bad Command" Remote method does not send any information but indefinitely runs. I'm really not sure what else to try. Im on the latest WW Firmware with Magisk root. Is there anything else I can check? Are you on the 8 GB Tencent version?
Click to expand...
Click to collapse
Is COM1 the only port available? What does it identify itself as in Device Manager? It should be a Qualcomm ... 902d device.
I'm on the tencent version, yeah, so it should be working for you as well.
HomerSp said:
Is COM1 the only port available? What does it identify itself as in Device Manager? It should be a Qualcomm ... 902d device.
I'm on the tencent version, yeah, so it should be working for you as well.
Click to expand...
Click to collapse
I changed it to that, I'm even trying this on a completely different computer to see. Now its on COM3 on the different system with that driver. I even recently did a full WW firmware flash and factory reset as well. So its pretty much completely stock other than Root and the Apps you made / modified.
Still, Critical error. Bad Command when running efsTools efsInfo
What version of the driver does it say for you?
Edit: When you're able to access efs, What does your sys.usb.state say? I have rndis,adb shown but sys.usb.config is set for rndis,diag,adb. Does your sys.usb.state have diag included?
Use serial port 'COM13'
Critical error. The requested resource is in use.
Use serial port 'COM13'
Critical error. The requested resource is in use.
Use serial port 'COM13'
Critical error. The requested resource is in use.
I keep getting the following error and I'm not sure what the cause may be. Is it possible that a video tutorial could be made to help out in beginning as I'm not sure what I'm doing wrong on my end.
Thank you so much for your work on this though! It is nothing short of amazing.
Does it matter which USB port we use on the device? I've tested both the bottom and the side and neither are working.
Cammarratta said:
Use serial port 'COM13'
Critical error. The requested resource is in use.
Use serial port 'COM13'
Critical error. The requested resource is in use.
Use serial port 'COM13'
Critical error. The requested resource is in use.
I keep getting the following error and I'm not sure what the cause may be. Is it possible that a video tutorial could be made to help out in beginning as I'm not sure what I'm doing wrong on my end.
Thank you so much for your work on this though! It is nothing short of amazing.
Does it matter which USB port we use on the device? I've tested both the bottom and the side and neither are working.
Click to expand...
Click to collapse
Make sure you dont have QPST server running. Its not required if using the tools. I ran into this issue and realized thats what it was that was using it.
How do I make sure the server is not running? I've rebooted and checked but I'm not seeing anything/indication of it doing so. Thank you in advance!
Cammarratta said:
How do I make sure the server is not running? I've rebooted and checked but I'm not seeing anything/indication of it doing so. Thank you in advance!
Click to expand...
Click to collapse
Open up QPST Configuration > at the top click Server > then Stop QPST Server. After that, see if efsTools give you anything. (efsTools efsInfo)
Hrmmm still not working on my end. Not sure what I'm doing wrong but I'll give it a rest for the time being.
My qserver keeps saying that it cannot find my USB or phone either. So I might be missing something. I'll Uninstall and try again though
Cammarratta said:
Hrmmm still not working on my end. Not sure what I'm doing wrong but I'll give it a rest for the time being.
My qserver keeps saying that it cannot find my USB or phone either. So I might be missing something. I'll Uninstall and try again though
Click to expand...
Click to collapse
What does it say for you? It won't find it if you turn it off. What is the COM port / driver that shows up in Device Manager
xbamaris1` said:
I changed it to that, I'm even trying this on a completely different computer to see. Now its on COM3 on the different system with that driver. I even recently did a full WW firmware flash and factory reset as well. So its pretty much completely stock other than Root and the Apps you made / modified.
Still, Critical error. Bad Command when running efsTools efsInfo
What version of the driver does it say for you?
Edit: When you're able to access efs, What does your sys.usb.state say? I have rndis,adb shown but sys.usb.config is set for rndis,diag,adb. Does your sys.usb.state have diag included?
Click to expand...
Click to collapse
Could you try this updated EfsTools: https://github.com/HomerSp/EfsTools...modded-1.1/EfsTools-0.10-modded-1.1-win32.zip Hopefully it should work for you.
sys.usb.state is supposed to say just rndis,adb - diag will only be listed in sys.usb.config.
HomerSp said:
Preface
With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier - doesn't matter from which device. This has been reported to work on TMO in the US, which did not work with my other method.
Prerequsities
* You must have working DIAG mode. See my other thread for more information on how to set that up.
Downloads
* AsusVoLTE v1.0.1
* EfsTools 0.10 modded 1.1
* EFS items
* Xiaomi Mi 9T MBNs (optional)
Step 1 - setting props
Install the AsusVoLTE app from above, make sure to upgrade if you already have it installed. Run the app and press the Enable VoLTE button; this should set some properties on the device to force-enable VoLTE after we have also done the other steps below. If you already enable VoLTE using my old method you can safely skip this step.
Step 2 - making sure it works
Before we begin, make sure you close down QPST, otherwise EfsTools will error out because there can not be two clients connected at once.
Unzip EfsTools from above, open up a cmd window and cd to the directory where you extracted it. Depending on how you connect to diag you will need to modify EfsTools.exe.config - if you're connecting via USB you most likely won't have to do anything as it will find the port automatically, unless you have more than one port, in which case you can simply change port from Auto to the COM port of the phone (for example COM13).
If you are connected via wifi you will need to change port to 2500 (or whatever port you used in the AsusVoLTE app) and remote to true. So the efstool line should look something like this:
You can test the connection by running this in the cmd window:
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:
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:
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.
Source code:
AsusVoLTE - Github
EfsTools - Github
Let me know if this works for you, or if you have any questions.
Regards
Click to expand...
Click to collapse
Absolutely genius, your work here is greatly appreciated everything is working perfectly VoLTE and VoWiFi with caller display
I used the EE mbn included in the Xiaomi Mi 9T MBNs provided , So for anyone on EE i can say it works without a problem.
Thank you :good:HomerSp
in device manager it shows up as
Qualcomm HS-USB Android DIAG 902D (COM13)
EDIT: It started working oddly enough. Which mi9 file would I flash for tmobile USA to test?
Thank you in advance for this!
Edit 2: got it working! Had to Uninstall, reinstall qpst, open up app and click enable DIAG, then stop the server in qstp and input the commands and it worked!
HomerSp said:
Could you try this updated EfsTools: https://github.com/HomerSp/EfsTools...modded-1.1/EfsTools-0.10-modded-1.1-win32.zip Hopefully it should work for you.
sys.usb.state is supposed to say just rndis,adb - diag will only be listed in sys.usb.config.
Click to expand...
Click to collapse
Thought so, just wanted to make sure.
https://imgur.com/a/WZvKteM is what I get. Is it possible to go back to an earlier RAW rom? I want to see if theres something in earlier ROMS that will make it work. I'm just at a loss. I'm not sure what I'm missing for this to work.
@HomerSp, thanks so much for all your efforts and skills - works a charm on ee UK using Mi9T MBN's
xbamaris1` said:
I cannot for the life of me get either method to work. Connected via USB. DIAG mode driver is loaded on COM1, even changed Baud rate on the COM port in device manager to 38400. USB method gives me "Critical Error: Bad Command" Remote method does not send any information but indefinitely runs. I'm really not sure what else to try. Im on the latest WW Firmware with Magisk root. Is there anything else I can check? Are you on the 8 GB Tencent version?
Click to expand...
Click to collapse
Same issue as you, i had it working at the start then it just stopped altogether. Hoping a next asus update could reset whatever i did to it and retry it again
Mine is getting stuck on "Use serial port 'COM5'" and nothing happens after that. Any recommendations how to make it work?
killerdvd said:
Mine is getting stuck on "Use serial port 'COM5'" and nothing happens after that. Any recommendations how to make it work?
Click to expand...
Click to collapse
I had to Uninstall qpst entirely, reinstall it. Then plug my phone in, open up the Asus volteapp and hit enable DIAG, my device then showed up in device manager, then I stopped the qpst server and it worked for me just fine. Using windows 10 with latest update.
Cammarratta said:
I had to Uninstall qpst entirely, reinstall it. Then plug my phone in, open up the Asus volteapp and hit enable DIAG, my device then showed up in device manager, then I stopped the qpst server and it worked for me just fine. Using windows 10 with latest update.
Click to expand...
Click to collapse
Thanks for the quick response. My device is already showing in device manager with COM 6. I never installed QPST since is not needed for USB connection. QPST is not even mention on OP.
I want to say the first part says that you need to have DIAG enabled.
Prerequsities
* You must have working DIAG mode. See my other thread for more information on how to set that up.
Click to expand...
Click to collapse
Which I think needed QPST installed. Unless I'm sadly mistaken, then please disregard!
OOPS!
You were following guides on XDA, and throwing random commands in ADB from the posts under the guides (DON'T DO THIS!) and now your slick new ROG phone 2 doesn't have mobile data, calls, wifi, or bluetooth. You quickly find out that flashing the phone with any firmware old or new, doesn't help you, as this issue is directly linked to your chip in your phone.
I quickly found that I needed a QCN file from someone with a rog 2 phone, however I could not get any help here on XDA except from the user Greatuser123, who did not want to give out his QCN file (understandably), but did send me some notes to try and help with other tools.
With nothing working, and no QCN file, I ordered another ROG 2 and waited for it in the mail. After it got here, I quickly extracted the QCN file, replaced the IMEI's in it, and used QPST to restore my phone.
I am simply writing this guide with the generic QCN file with my info masked out of it, so no one has to go through what I went through.
Common issue
This most commonly happens with ROG 2 Phones from the commands:
DO NOT RUN THESE COMMANDS UNLESS YOU KNOW WHAT YOU ARE DOING!
(spaced command to ensure no one runs this!)
fastboot erase modem st 1
fastboot erase modem st 2
Click to expand...
Click to collapse
On most phones, on a reboot, these partitions would be restored on reboot, but not on most ROG's.
Prerequisites
Rooted Phone
QPST
Qualcomm USB drivers
IMEI Converter
Platform Tools
The Fix
Follow the above root linked video, or find the root thread for your phone here on XDA, and root your phone. This will not work unless you are rooted, although I do not know how you would get into this mess without having your phone rooted already.
Install QPST tools
Install Qualcomm USB drivers
Download the attached zip "good_qcn.zip" and extract the .QCN file anywhere on your machine
Open the .QCN file with any Hex Editor (I used HxD) and search for the Hex-Values: 08 3A 85 99 99 99 99 99 99
NOTE: There will be TWO locations with this value. This is where your IMEI_1 and IMEI_2 will go. Your IMEI_2 goes into the FIRST occurrence, while your IMEI_1 goes in the second.
Download the IMEI Converter app and type in your IMEI_1 and click "Convert", place the converted hex output into a notepad or similar
Do the same for your IMEI_2 and place it in the same location
Now that you have the HEX version of both your IMEI's, paste your IMEI_2 in the FIRST occurrence of the fake IMEI in the QCN file
Paste your IMEI_1 in the last occurrence of the fake IMEI and now save your new .QCN file.
Ensure your device is in USB Debugging Mode.
Download and extract the Platform Tools if you do not have them already.
Plug your phone into your computer using either port
Navigate to your extracted Platform Tools and in a Command Line type "adb devices" to ensure your device is visible.
Run a shell with "adb shell" and elevate your permission with "su"
Now it is time to enable Diag mode by running "setprop sys.usb.config rndis,diag,adb"
At this time, if you installed the Qualcomm Drivers, your device manager should have a port similar to "Qualcomm HS-USB Diag". If not keeping trying to re-enter diag mode and ensure the drivers are correct.
Open up "QPST Configuration" which was installed earlier. You should see your phone listed under "Active Phones". Click "Start Clients" -> "Software Download"
The Port field of the QPST Software Download should list your phone, if not something is wrong.
Click "Restore", and in the xQCN field, click "Browse", change the file type from XQCN to QCN, and select your newly made QCN file
Click "Start", and once the process is done, restart your phone
Conclusion
If all went well, your phone should now have all its bells and whistles again. Sometimes it may require a Factory Reset, and this should always be the practice anyways. If you have mobile data, but only H+ or EDGE, dial *#*#4636#*#* on your phone and ensure LTE is provisioned.
Good luck guys!
Special thanks to: Greatuser123 for helping when no one else would, and HomerSp for his many useful guides that some tools and knowledge was borrowed from.
Hi bro, Nice to meet you and I did my best to help you out, as I spent some stress on this when I was one of the first people that suffered with this issue. And gladly you solved it, bro you misunderstood badly about I did not want to give you the qcn, I was going to give you my qcn file but first I was asking to you for some proof , photo of same phone as me and the package to know that you are not going to change or edit badly ( doing mischievousness) as you never sent the proof I did not send the qcn file.. you can re check again your messages. Bro
Thank you very much for this, life saver.
My wifi and bluetooth works fine but I cannot get my mobile to power back on. When I go into the menu mobile power is just not there :/
Do you have the global or the cn version?
BlazingBullets said:
Thank you very much for this, life saver.
My wifi and bluetooth works fine but I cannot get my mobile to power back on. When I go into the menu mobile power is just not there :/
Do you have the global or the cn version?
Click to expand...
Click to collapse
This QCN came from a global device, but I imagine this could be used to recover the mobile at least temporary to fully fix the device, no matter the origins.
Sorry for the delay.
Greatuser123 said:
Hi bro, Nice to meet you and I did my best to help you out, as I spent some stress on this when I was one of the first people that suffered with this issue. And gladly you solved it, bro you misunderstood badly about I did not want to give you the qcn, I was going to give you my qcn file but first I was asking to you for some proof , photo of same phone as me and the package to know that you are not going to change or edit badly ( doing mischievousness) as you never sent the proof I did not send the qcn file.. you can re check again your messages. Bro
Click to expand...
Click to collapse
No no, please do not think I meant you by that. It was other users (understandably) that questioned my motives before you. I absolutely would have taken you up on your offer if I did not already have the phone on the way Either way, I really appreciate your help during this, and I hope you continue to help other users the same way you did for me.
decrypterfixer said:
This QCN came from a global device, but I imagine this could be used to recover the mobile at least temporary to fully fix the device, no matter the origins.
Sorry for the delay.
Click to expand...
Click to collapse
After a lot of heart ache and even making an EDL cable I could not get cell network back. I"ve sent it into ASUS to get fixed. I have made a few backups and will diff them when I get my device back so hopefully I can see what they have fixed so others don't have to experience this.
BlazingBullets said:
After a lot of heart ache and even making an EDL cable I could not get cell network back. I"ve sent it into ASUS to get fixed. I have made a few backups and will diff them when I get my device back so hopefully I can see what they have fixed so others don't have to experience this.
Click to expand...
Click to collapse
I can help u
Well done mate you will be a hero someday haha good job ?
Leevii2208 said:
I can help u
Click to expand...
Click to collapse
Please provide your support ouvertly here and not via social media!
I've edited your post; please refer to https://forum.xda-developers.com/oneplus-5t/how-to/telegram-chat-channels-forward-t3765018
not work
ty but not working or i did wrong. i wrote (change my imei, two way u and other program) and post new "good.qcn" (i see finished in QPST Software). i restart phone but nothing change. i think phone in document just "read-only".
I want redmagic 3 qcn file
good job bro
Is it works for rog phone 3?
I can't find that hex
hello friends 08 3A 85 99 99 99 99 99 99 no found please help me
Hi, perfect post friend. Im try backup qcn to my Rog Phone 3, but when try said Satuts: Memory Backup Failer and Errors: Disr Error while write to file, any solution to this? I appreciate your help.
decrypterfixer said:
OOPS!
You were following guides on XDA, and throwing random commands in ADB from the posts under the guides (DON'T DO THIS!) and now your slick new ROG phone 2 doesn't have mobile data, calls, wifi, or bluetooth. You quickly find out that flashing the phone with any firmware old or new, doesn't help you, as this issue is directly linked to your chip in your phone.
I quickly found that I needed a QCN file from someone with a rog 2 phone, however I could not get any help here on XDA except from the user Greatuser123, who did not want to give out his QCN file (understandably), but did send me some notes to try and help with other tools.
With nothing working, and no QCN file, I ordered another ROG 2 and waited for it in the mail. After it got here, I quickly extracted the QCN file, replaced the IMEI's in it, and used QPST to restore my phone.
I am simply writing this guide with the generic QCN file with my info masked out of it, so no one has to go through what I went through.
Common issue
This most commonly happens with ROG 2 Phones from the commands:
DO NOT RUN THESE COMMANDS UNLESS YOU KNOW WHAT YOU ARE DOING!
(spaced command to ensure no one runs this!)
On most phones, on a reboot, these partitions would be restored on reboot, but not on most ROG's.
Prerequisites
Rooted Phone
QPST
Qualcomm USB drivers
IMEI Converter
Platform Tools
The Fix
Follow the above root linked video, or find the root thread for your phone here on XDA, and root your phone. This will not work unless you are rooted, although I do not know how you would get into this mess without having your phone rooted already.
Install QPST tools
Install Qualcomm USB drivers
Download the attached zip "good_qcn.zip" and extract the .QCN file anywhere on your machine
Open the .QCN file with any Hex Editor (I used HxD) and search for the Hex-Values: 08 3A 85 99 99 99 99 99 99
NOTE: There will be TWO locations with this value. This is where your IMEI_1 and IMEI_2 will go. Your IMEI_2 goes into the FIRST occurrence, while your IMEI_1 goes in the second.
Download the IMEI Converter app and type in your IMEI_1 and click "Convert", place the converted hex output into a notepad or similar
Do the same for your IMEI_2 and place it in the same location
Now that you have the HEX version of both your IMEI's, paste your IMEI_2 in the FIRST occurrence of the fake IMEI in the QCN file
Paste your IMEI_1 in the last occurrence of the fake IMEI and now save your new .QCN file.
Ensure your device is in USB Debugging Mode.
Download and extract the Platform Tools if you do not have them already.
Plug your phone into your computer using either port
Navigate to your extracted Platform Tools and in a Command Line type "adb devices" to ensure your device is visible.
Run a shell with "adb shell" and elevate your permission with "su"
Now it is time to enable Diag mode by running "setprop sys.usb.config rndis,diag,adb"
At this time, if you installed the Qualcomm Drivers, your device manager should have a port similar to "Qualcomm HS-USB Diag". If not keeping trying to re-enter diag mode and ensure the drivers are correct.
Open up "QPST Configuration" which was installed earlier. You should see your phone listed under "Active Phones". Click "Start Clients" -> "Software Download"
The Port field of the QPST Software Download should list your phone, if not something is wrong.
Click "Restore", and in the xQCN field, click "Browse", change the file type from XQCN to QCN, and select your newly made QCN file
Click "Start", and once the process is done, restart your phone
Conclusion
If all went well, your phone should now have all its bells and whistles again. Sometimes it may require a Factory Reset, and this should always be the practice anyways. If you have mobile data, but only H+ or EDGE, dial *#*#4636#*#* on your phone and ensure LTE is provisioned.
Good luck guys!
Special thanks to: Greatuser123 for helping when no one else would, and HomerSp for his many useful guides that some tools and knowledge was borrowed from.
Click to expand...
Click to collapse
I tried it till finish, but when I check, I lost my wifi mac address (status unavailable) and my imei still unknown. And now I wanna retry, I stuck at QPST Configuration application at step 17, it sometimes detected the phone, sometimes don't, it make me can't continue to click "star clients", (check in device manager, nothing wrong). can you help me?
sure which device rog 2 or 3?
gjkhan said:
sure which device rog 2 or 3?
Click to expand...
Click to collapse
uhhg that's a issue just download visual c++ redistributable 2010 sp1 x86 and it should be fine
gjkhan said:
sure which device rog 2 or 3?
Click to expand...
Click to collapse
Rog2. The port keep blinking when in QPST Tools, sometimes it detected, sometimes don't, so I can't copy the qcn to the phone. And also I don't know what's wrong with the qcn, I had follow the instruction, but it not works
hmmm use another pc or cable.
gjkhan said:
hmmm use another pc or cable.
Click to expand...
Click to collapse
Try itt but problem still persist
Hello Xperia users! In the meantime, I finally solved the VOLTE problem! I approached Qualcomm's diagnostic port-active-efsExplorer and solved the problem by inserting a VOLTE profile from my carrier
Sorry, this is Korea and I am Korean.
However, I will write down the method in English.
Unlike previous 1&5, Qualcomm's diagnostic port cannot be opened.
opening command
I don't even know. I don't think so.
So it's a little different from before.
I tried to force it open.
debugging connection
Open the Command Proposal window.
adb shell input
su input
Do you want to allow shell on your phone?
prompt acceptance of permission
Then the $ shape changes to #.
Now
setprop persist.usb.eng 1
Copy paste entry. Please enter
And you're gonna be out there during tethering.
In My Computer Item
View Device Manager.
Please turn debugging back on.
Of course, no access.
If you turn on debugging again,
I've already set it up, so it looks like that.
Among them, there is a product model named XQ-AT52.
There are four yellow exclamation points in total.
Manually update driver Press [port] to list the manufacturers
It's called Qualcomm hs-usb-diagh and 9091. with this
I need a manual update. gogo
Now run the EFS Express.
Press 0 on the ROW and OK.
(ROW or SF_Default)
Oh, it takes a long time. I thought it stopped.
It opens if you stay still. LOL
It's open. How nice to see you here!
I am the Korean telecommunication company EFS file extracted from xperia1.
I used it. If you need VOLTE,
XPERIA1 (Modem).Extract from SIN file
I will use the Korean communication file.
Just drag it and put it in a folder.
v check and Yes
There'll be folders that don't exist while you're pulling them in.
Then make it and put the file in.
In the folder where you can view this red file,
Drag and drop the file twice.
The reason is that once you do it, you just go in.
The red file is not updated.
That's how the numbers at the back change when you renew.
So make sure to put it in twice.
Files beginning with NV do not have folders.
Put it on top.
It's over now!
Volte Success ^0^ About IMS
VOLTE OK
Confirm Video Calls
It was such a hard time for me!
I was sad because I couldn't get help.
With 5G mobile phones in 2020,
It was terrible to be on the 3G phone.
If there's someone like me,
This information will help you a lot.
Finally, Marktu
Buy! Buy two! I love it.
This is great! How do we find VoLTE profile for our carriers?
mehdi_s82 said:
This is great! How do we find VoLTE profile for our carriers?
Click to expand...
Click to collapse
It's hidden in XPERIA1 firmware.
After downloading the firmware via Xperia Pim, change the extension to Modem.img in the Modem.sin file and extract it to the compression program (7z) to view the folder! Surprisingly, the world's telecommunications company VOLTE EFS file is hidden. +_+ Take advantage of it! You can open the VOLTE menu through the magazine module.
Hi, why don't you show by video or pictures. The windowns language is English. ???
Attach the necessary software.
Thanks
I estimate, its only possible by unlocking/rooting the phone?
how to
Even with the great contributors' information, I think there are a few areas where I struggle.
For additional information, I will post my success stories.
I'm posting them in machine translation. Please forgive me if it's hard to read.
STEP 1: Implement the Tools You Need
Please install the following tools.
QPST(QPST_2.7.460)
Qualcomm-hs-usb-diagnostics-9091-952454(DIAG driver)
Flashtool (and XperiaFirm)
newflasher(INSTALL is unnecessary, but please get it.)
*All of the above were available on the internet as of 8/15.
STEP2: Get a "modem" that supports VoLTE.
As a prerequisite (regardless of the DualSim/SinglSim model)
For countries that want to use VoLTE, SONY is offering
Official firmware is required.
In my example.
Purchased model: XQ-AT52 (for Hong Kong)
The country where you want to use it: Japan -> SO-51A is available.
(The difference in the number of slots in the SIM doesn't affect it. )
This is the case.
If the firmware to run VoLTE does not exist in the country where you want to use it
This method does not work.
The annotations are long, but here are the steps.
Use XperiFirm, provided by SONY in the country where you want to use VoLTE.
Download the firmware.
STEP3: Use the newflasher to write the firmware from STEP2 to your Xperia 1 ii.
In this case, if you want to burn into a model with a different number of SIM slots
Example: Writing SO-51A firmware to XQ-AT52
→The SIM will not be recognized, but it is temporary.
STEP4: Use EFS Explorer to get the necessary files.
Follow the steps of the great htcmage and have your Xperia 1 ii recognized by EFS Explorer.
4-1: Install the QPST.
4-2:Install Magisk on your Xperia 1 ii.
Therefore, it is mandatory to unlock the bootloader.
4-3:Execute the commands at the command prompt as follows.
adb shell
su
setprop persist.usb.eng 1
Magisk's permission is now required to get SuperUser privileges in su.
Note: From the Magisk menu, go to "# SuperUser" and click on
You can allow.
4-4: The debug mode is disconnected, so you need to re-enable it.
4-5: If you have installed the qualcomm-hs-usb-diagnostics-9091-952454 (DIAG driver), you can use
It is recognized by EFS Explorer.
4-6: On the Phone Selectio screen, Banner selects the ROW port.
STEP 5: Back up the files required for VoLTE activation.
Before following the steps below, you must have the SIM of the line/carrier you want to enable VoLTE on.
Please plug in.
I have backed up the following folders.
There may be some things you don't need, but at least it works.
Data_Profiles
efsprofiles
Ims.
nv/item_files/datamodem
nv/item_files/ims
nv/item_files/mcfg
nv/item_files/modem
STEP6: Write the firmware you want to use, and copy the file from STEP5 to
Override.
Follow steps 3 to 4 of STEP 3 to 4 to get the firmware you want to use.
Write & make EFS Explorer recognize it. (Don't remove the SIM.)
Then, overwrite it with the files backed up in STEP 5.
You should probably now have VoLTE available.
Thanks to the person who walked me through the Magisk installation process, and to the great htcmage.
Also, I pray that others wandering in the same sea of information will be saved.
:good:
sura_tth said:
Even with the great contributors' information, I think there are a few areas where I struggle.
For additional information, I will post my success stories.
I'm posting them in machine translation. Please forgive me if it's hard to read.
STEP 1: Implement the Tools You Need
Please install the following tools.
QPST(QPST_2.7.460)
Qualcomm-hs-usb-diagnostics-9091-952454(DIAG driver)
Flashtool (and XperiaFirm)
newflasher(INSTALL is unnecessary, but please get it.)
*All of the above were available on the internet as of 8/15.
STEP2: Get a "modem" that supports VoLTE.
As a prerequisite (regardless of the DualSim/SinglSim model)
For countries that want to use VoLTE, SONY is offering
Official firmware is required.
In my example.
Purchased model: XQ-AT52 (for Hong Kong)
The country where you want to use it: Japan -> SO-51A is available.
(The difference in the number of slots in the SIM doesn't affect it. )
This is the case.
If the firmware to run VoLTE does not exist in the country where you want to use it
This method does not work.
The annotations are long, but here are the steps.
Use XperiFirm, provided by SONY in the country where you want to use VoLTE.
Download the firmware.
STEP3: Use the newflasher to write the firmware from STEP2 to your Xperia 1 ii.
In this case, if you want to burn into a model with a different number of SIM slots
Example: Writing SO-51A firmware to XQ-AT52
→The SIM will not be recognized, but it is temporary.
STEP4: Use EFS Explorer to get the necessary files.
Follow the steps of the great htcmage and have your Xperia 1 ii recognized by EFS Explorer.
4-1: Install the QPST.
4-2:Install Magisk on your Xperia 1 ii.
Therefore, it is mandatory to unlock the bootloader.
4-3:Execute the commands at the command prompt as follows.
adb shell
su
setprop persist.usb.eng 1
Magisk's permission is now required to get SuperUser privileges in su.
Note: From the Magisk menu, go to "# SuperUser" and click on
You can allow.
4-4: The debug mode is disconnected, so you need to re-enable it.
4-5: If you have installed the qualcomm-hs-usb-diagnostics-9091-952454 (DIAG driver), you can use
It is recognized by EFS Explorer.
4-6: On the Phone Selectio screen, Banner selects the ROW port.
STEP 5: Back up the files required for VoLTE activation.
Before following the steps below, you must have the SIM of the line/carrier you want to enable VoLTE on.
Please plug in.
I have backed up the following folders.
There may be some things you don't need, but at least it works.
Data_Profiles
efsprofiles
Ims.
nv/item_files/datamodem
nv/item_files/ims
nv/item_files/mcfg
nv/item_files/modem
STEP6: Write the firmware you want to use, and copy the file from STEP5 to
Override.
Follow steps 3 to 4 of STEP 3 to 4 to get the firmware you want to use.
Write & make EFS Explorer recognize it. (Don't remove the SIM.)
Then, overwrite it with the files backed up in STEP 5.
You should probably now have VoLTE available.
Thanks to the person who walked me through the Magisk installation process, and to the great htcmage.
Also, I pray that others wandering in the same sea of information will be saved.
Click to expand...
Click to collapse
Hello, you are so cool Thank you so much for organizing the guide. I hope it helps many xperia 1 II users ah! I opened the volte-related menu without changing the firmware using the magical module. The reason is that the buildprop cannot be modified for this xperia1 II
pa// Attached file for used module
Has anyone had success doing this on the Xperia 5 ii ?
htcmage said:
Hello Xperia users! In the meantime, I finally solved the VOLTE problem! I approached Qualcomm's diagnostic port-active-efsExplorer and solved the problem by inserting a VOLTE profile from my carrier
Sorry, this is Korea and I am Korean.
However, I will write down the method in English.
Unlike previous 1&5, Qualcomm's diagnostic port cannot be opened.
opening command
I don't even know. I don't think so.
So it's a little different from before.
I tried to force it open.
debugging connection
Open the Command Proposal window.
adb shell input
su input
Do you want to allow shell on your phone?
prompt acceptance of permission
Then the $ shape changes to #.
Now
setprop persist.usb.eng 1
Copy paste entry. Please enter
And you're gonna be out there during tethering.
In My Computer Item
View Device Manager.
Please turn debugging back on.
Of course, no access.
If you turn on debugging again,
I've already set it up, so it looks like that.
Among them, there is a product model named XQ-AT52.
There are four yellow exclamation points in total.
Manually update driver Press [port] to list the manufacturers
It's called Qualcomm hs-usb-diagh and 9091. with this
I need a manual update. gogo
Now run the EFS Express.
Press 0 on the ROW and OK.
(ROW or SF_Default)
Oh, it takes a long time. I thought it stopped.
It opens if you stay still. LOL
It's open. How nice to see you here!
I am the Korean telecommunication company EFS file extracted from xperia1.
I used it. If you need VOLTE,
XPERIA1 (Modem).Extract from SIN file
I will use the Korean communication file.
Just drag it and put it in a folder.
v check and Yes
There'll be folders that don't exist while you're pulling them in.
Then make it and put the file in.
In the folder where you can view this red file,
Drag and drop the file twice.
The reason is that once you do it, you just go in.
The red file is not updated.
That's how the numbers at the back change when you renew.
So make sure to put it in twice.
Files beginning with NV do not have folders.
Put it on top.
It's over now!
Volte Success ^0^ About IMS
VOLTE OK
Confirm Video Calls
It was such a hard time for me!
I was sad because I couldn't get help.
With 5G mobile phones in 2020,
It was terrible to be on the 3G phone.
If there's someone like me,
This information will help you a lot.
Finally, Marktu
Buy! Buy two! I love it.
Click to expand...
Click to collapse
Do you loose 5g support after this method?
Does your mobile restart after changing the data carrier from Sim1 to Sim2?
R
htcmage said:
Hello, you are so cool Thank you so much for organizing the guide. I hope it helps many xperia 1 II users ah! I opened the volte-related menu without changing the firmware using the magical module. The reason is that the buildprop cannot be modified for this xperia1 II
pa// Attached file for used module
Click to expand...
Click to collapse
I reflash XQ AT 52 or AT 51 to XQ AT 72 (China) it resconized Simcard but no signal. This menthod will work in my case??? Thank you
FantasticBeast007 said:
Do you loose 5g support after this method?
Does your mobile restart after changing the data carrier from Sim1 to Sim2?
Click to expand...
Click to collapse
I have a xperia 1 mobile in India but my mobile not support volte please help me
dangh5 said:
I reflash XQ AT 52 or AT 51 to XQ AT 72 (China) it resconized Simcard but no signal. This menthod will work in my case??? Thank you
Click to expand...
Click to collapse
I have a xperia 1 in India but my mobile not support volte please help me
Xperia_xz3 said:
I have a xperia 1 in India but my mobile not support volte please help me
Click to expand...
Click to collapse
Same problem with me.
Mine is the Xperia 1 III.
Will this work with the 1 III Also?
Xperia_xz3 said:
I have a xperia 1 in India but my mobile not support volte please help me
Click to expand...
Click to collapse
Yes you can use volte jio in india.
Telegram - @lazypanda010
I have the Sony Xperia 1 II AU SOG01 Japanese model. I sim unlocked it, I put in my sim card, I use AT&T in the United States. But I can't make phone calls because the VoLTE toggle doesn't appear in settings. I can use data though. I don't understand this guide, can anyone here help me? Does anyone have experiece with this model?
Jmez6314 said:
I have the Sony Xperia 1 II AU SOG01 Japanese model. I sim unlocked it, I put in my sim card, I use AT&T in the United States. But I can't make phone calls because the VoLTE toggle doesn't appear in settings. I can use data though. I don't understand this guide, can anyone here help me? Does anyone have experiece with this model?
Click to expand...
Click to collapse
Hi! We have the same model, where did you sim unlocked your device?
sura_tth said:
how to
Even with the great contributors' information, I think there are a few areas where I struggle.
For additional information, I will post my success stories.
I'm posting them in machine translation. Please forgive me if it's hard to read.
STEP 1: Implement the Tools You Need
Please install the following tools.
QPST(QPST_2.7.460)
Qualcomm-hs-usb-diagnostics-9091-952454(DIAG driver)
Flashtool (and XperiaFirm)
newflasher(INSTALL is unnecessary, but please get it.)
*All of the above were available on the internet as of 8/15.
STEP2: Get a "modem" that supports VoLTE.
As a prerequisite (regardless of the DualSim/SinglSim model)
For countries that want to use VoLTE, SONY is offering
Official firmware is required.
In my example.
Purchased model: XQ-AT52 (for Hong Kong)
The country where you want to use it: Japan -> SO-51A is available.
(The difference in the number of slots in the SIM doesn't affect it. )
This is the case.
If the firmware to run VoLTE does not exist in the country where you want to use it
This method does not work.
The annotations are long, but here are the steps.
Use XperiFirm, provided by SONY in the country where you want to use VoLTE.
Download the firmware.
STEP3: Use the newflasher to write the firmware from STEP2 to your Xperia 1 ii.
In this case, if you want to burn into a model with a different number of SIM slots
Example: Writing SO-51A firmware to XQ-AT52
→The SIM will not be recognized, but it is temporary.
STEP4: Use EFS Explorer to get the necessary files.
Follow the steps of the great htcmage and have your Xperia 1 ii recognized by EFS Explorer.
4-1: Install the QPST.
4-2:Install Magisk on your Xperia 1 ii.
Therefore, it is mandatory to unlock the bootloader.
4-3:Execute the commands at the command prompt as follows.
adb shell
su
setprop persist.usb.eng 1
Magisk's permission is now required to get SuperUser privileges in su.
Note: From the Magisk menu, go to "# SuperUser" and click on
You can allow.
4-4: The debug mode is disconnected, so you need to re-enable it.
4-5: If you have installed the qualcomm-hs-usb-diagnostics-9091-952454 (DIAG driver), you can use
It is recognized by EFS Explorer.
4-6: On the Phone Selectio screen, Banner selects the ROW port.
STEP 5: Back up the files required for VoLTE activation.
Before following the steps below, you must have the SIM of the line/carrier you want to enable VoLTE on.
Please plug in.
I have backed up the following folders.
There may be some things you don't need, but at least it works.
Data_Profiles
efsprofiles
Ims.
nv/item_files/datamodem
nv/item_files/ims
nv/item_files/mcfg
nv/item_files/modem
STEP6: Write the firmware you want to use, and copy the file from STEP5 to
Override.
Follow steps 3 to 4 of STEP 3 to 4 to get the firmware you want to use.
Write & make EFS Explorer recognize it. (Don't remove the SIM.)
Then, overwrite it with the files backed up in STEP 5.
You should probably now have VoLTE available.
Thanks to the person who walked me through the Magisk installation process, and to the great htcmage.
Also, I pray that others wandering in the same sea of information will be saved.
Click to expand...
Click to collapse
Hi!
I think i missed something during yoyr great guide . My case is that I'm in Israel, where Sony doesn't provide original firmware, and I use Xperia 5 iii (XQ-BQ52 from UK), So will this guide work?
Thank you
ruchan said:
Hi! We have the same model, where did you sim unlocked your device?
Click to expand...
Click to collapse
I used a software called S1 Unlock Tool. You need to buy a credit from this website: https://networkunlocking.com/shop/sony-xperia-cable-unlock-0-counter-supported/. There is also a link to download the software. Along with unlocking your phone it will also grant you access to unlock your bootloader if you wish to do so. I did this and tried to root my phone but I wasn't successful, it just soft bricked my phone and was stuck in a boot loop. I had to use Xperia Companion to restore my phone. Maybe you can't root the Japanese variants, I'm not sure. I saw on here on another forum that you can root the Xperia 1 II.