Related
Hello everybody !
Ok, I am use to not ask any help, and to find out by myself. But I have to admit I don't have any idea remaining to solve this problem.
Let me explain you the situation :
I explain everything with details to not waste your time when you will help me !
When I first bought my Zenfone, everything worked properly. Then, I decided to flash a Custom ROM (to remove the bloatware, and to get the others optimizations). So what I did :
- I unlocked the bootloader,
- I flashed TWRP,
- I installed my custom ROM (SuperZen R15, super clean install) => at this moment, everything is working perfectly,
- I installed a custom Kernel (ProjectT, v56) by fastboot => here we are, the problem just appeared.
At this moment, the WiFi issues appear. When I boot the phone, I can turn on the WiFi (in most cases), then, WiFi just turn off. It is impossible to activate it again. In the best case, I can switch on/off the WiFi, but as soon as I download something, the WiFi just turn off immediately. Often, I just don't detect any network. In the worse case, it is impossible to activate again the WiFi, the ON/OFF button is grey.
So here is what I tried to get it back :
1) put the standard kernel with my TWRP backup => no success
2) flash another ROM (CM12, Paranoid Android, Barebone,...etc) => no success
3) flash my whole TWRP backup (system + kernel) => no success
4) flash the official Asus ROM (recovery.img, system.img, boot.img, droidboot.img) => no success
At the moment, I started thinking that maybe the WiFi just "forgot" my WPA key. So I modified the build.prop :
5) modification of the build.prop by adding the line ro.securestorage.support=false (instead of "true") => no success
6) flash the last Asus update 2.20.40... => no success.
...
I haven't any idea remaining !So I need your help ! This problem seems very standard, but I just couldn't find any solution yet !
P.S : I almost forgot. I talked about the wiFi signal, but it is exactly the same for the bluetooth signal : working on first boot, then when I use it, it just stop working and disconnect itself, and then, impossible to activate it again (grey button)
=> My last idea was to flash the radio directly by TWRP, but I didn't find any radio files for the zenfone 2...
Many thanks for your help, and thank you for reading everything !!
Max
Up !
BackDraft647 said:
Up !
Click to expand...
Click to collapse
Try setting your phone as a wifi hotspot. If other devices are able to detect your device, it is a software issue. Or else, you might have to book an appointment with the Asus service center
[email protected] said:
Try setting your phone as a wifi hotspot. If other devices are able to detect your device, it is a software issue. Or else, you might have to book an appointment with the Asus service center
Click to expand...
Click to collapse
You're such a genius ! I will try this evening ! Thanks a lot !
Didn't do anything. It's not working. I was thinking my wifi was just broken, but something creepy happened this morning. The Wi-Fi worked again (I downloaded one thing to be sure !) and then... My phone froze, and reboot... Is the devil inside my phone ??
SOLVED ! If someone has the same problem, just flash the stock ROM via ADB Sideload !
Step by step :
1) You go here, and download your version of the stock ROM : http://www.asus.com/fr/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
2) (If fastboot/adb drivers are installed) Go into your recovery (Advanced in TWRP)
3) Connect the phone to the PC, type WINDOWS + R , enter 'cmd'
4) Go into your firmware directory you just downloaded, and type : adb sideload 'thenameofthefirmwarefile'.zip
5) Wait (a loooong time), and here we go, reboot, and your phone work again.
BackDraft647 said:
SOLVED ! If someone has the same problem, just flash the stock ROM via ADB Sideload !
Step by step :
1) You go here, and download your version of the stock ROM :
2) (If fastboot/adb drivers are installed) Go into your recovery (Advanced in TWRP)
3) Connect the phone to the PC, type WINDOWS + R , enter 'cmd'
4) Go into your firmware directory you just downloaded, and type : adb sideload 'thenameofthefirmwarefile'.zip
5) Wait (a loooong time), and here we go, reboot, and your phone work again.
Click to expand...
Click to collapse
can you tell me what firmware you used exactly? because i tried to flash the first one, from the asus page.
But it says that i have a newest build and it doesn`t lets me past trough the installing part.
I am also having troubles with my wifi and i would like to fix it
Hello ! I don't remember exactly, I went on a website and selected the right version for my country ! But my problem wasn't solve at all actually... I brought my phone to the store, and they told me my motherboard was just burnt. They changed everything, and now it works like a charm ! Be careful with the custom kernel, I'm pretty sure that's how my phone broke (I'm very careful with batteries,...etc)
Well thanks anyway. I will try to take the phone to te oficial ASUS services from my country but i don´t think they give a new one. I live in Uruguay and this cellphone is not at sale over here
Does sideloading the firmware wipe your apps? Or is every thing still there when its done?
Sent from my ASUS_Z00AD using Tapatalk
Has anyone already found out how to access or enable the USB diag mode for connecting to QXDM?
Thanks!
just curious, for what reason?
noidea24 said:
just curious, for what reason?
Click to expand...
Click to collapse
Well, I work as an engineer in the IMS core environment
noidea24 said:
just curious, for what reason?
Click to expand...
Click to collapse
I would like diag mode to use the DFS Tool to enable/disable LTE bands.
hate to bump an old thread, but did anyone ever figure this out?
Madscotsman said:
hate to bump an old thread, but did anyone ever figure this out?
Click to expand...
Click to collapse
I think maybe google disabled this,I also want this
For Generic HTC devices,such command with root shell may could open the DIAG PORYT
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/func_en
But Google AOSP HTC devices....................
Someone has already solved this Problem but due to the negative attitude of the USERs of PIXEL,so.....................
Looking for the answer to this as well. It's needed for DFS and QPST (QXDM).
Every phone has some particular way to do this and so far I haven't found it on this phone. The Nexus 6 was super easy and I was hoping this one would be too. (On the Nexus 6 all you had to do was select BP Tools from the boot menu. Then it booted like normal but with the diag port enabled. Other phones you have to write to or create a particular file, or there's a dialer code but the usual tricks aren't working here.)
KlokWerk said:
Looking for the answer to this as well. It's needed for DFS and QPST (QXDM).
Every phone has some particular way to do this and so far I haven't found it on this phone. The Nexus 6 was super easy and I was hoping this one would be too. (On the Nexus 6 all you had to do was select BP Tools from the boot menu. Then it booted like normal but with the diag port enabled. Other phones you have to write to or create a particular file, or there's a dialer code but the usual tricks aren't working here.)
Click to expand...
Click to collapse
Have you tried using these commands with terminal emulator?
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
xdadevnube said:
Have you tried using these commands with terminal emulator?
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
Click to expand...
Click to collapse
Oh crud, I just noticed I was replying to a Pixel XL thread rather than a Pixel thread. You'd think they'd be similar.... does your method work on the Pixel XL, though? If you've tried that and say it works I may actually switch, if I can't figure out how to connect this Pixel.
When I try this on the Pixel (sku G2PW4100 running 7.1.1) I just get "Permission denied", even as superuser, even after changing the f_diag folder permissions to allow writes.
You're getting it to work on the G2PW2100, I guess? 7.1.1?
KlokWerk said:
Oh crud, I just noticed I was replying to a Pixel XL thread rather than a Pixel thread. You'd think they'd be similar.... does your method work on the Pixel XL, though? If you've tried that and say it works I may actually switch, if I can't figure out how to connect this Pixel.
When I try this on the Pixel (sku G2PW4100 running 7.1.1) I just get "Permission denied", even as superuser, even after changing the f_diag folder permissions to allow writes.
You're getting it to work on the G2PW2100, I guess? 7.1.1?
Click to expand...
Click to collapse
I apologize for not specifying that I don't have a Pixel or Pixel XL yet.
I know the command I posted above works on the HTC m8. I had almost given up on diag mode on that device until I tried that command.
It sounds like you're on the right track, but unfortunately my understanding is fairly limited. Hopefully somebody with more knowledge can chime in.
I've never messed with this, but I'm looking through the history here to see if there's a clue.
https://github.com/CallMeAldy/devic...f587b26156180b3/init.common.diag.rc.userdebug
...
PaulPizz said:
I believe I have found a way to enter DM Mode on the Pixel XL..
==Instructions==
- Makes sure you are rooted. <-- *If you are not and do not know how, Please do your research*
- Download and install the GalaxyTools3.1.2 app
- Tap the GalaxyTools3.1.2 App, grant it Super User permissions
- Once you are in the GalaxyTools3.1.2 app scroll down and tap "GTUSBItil" Button
- This will open up the "UART" Menu which you should be able to use to select DM+Modem+ADB
==Downloads==
- GalaxyTools3.1.2
** I have not figured out how to get the device to work with DFS.. If anyone figures it out please report back. Id like to know..**
Click to expand...
Click to collapse
Have you tried the "hacked" HTC Modem driver? If you get a list of Unknown devices in Windows Device Manager, you may be able to get install the modem driver and get QXDM or DFS working.
Let me know if you need any of those files.
xdadevnube said:
Have you tried the "hacked" HTC Modem driver? If you get a list of Unknown devices in Windows Device Manager, you may be able to get install the modem driver and get QXDM or DFS working.
Let me know if you need any of those files.
Click to expand...
Click to collapse
I think it just shows up as adb. Im not in front of my computer right now. But send it. I'll check it out. Thanks
Sent from my Pixel XL using Tapatalk
PaulPizz said:
I think it just shows up as adb. Im not in front of my computer right now. But send it. I'll check it out. Thanks
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Awesome! I'll send it when I get to a computer tonight.
I don't have a Pixel yet, so I'm not able to try it myself.
EDIT: Here is the modem driver.
View attachment 4081431
The recommended solution does not work, no com port is added in the device manager.
Hi,
I am desperately looking for the solution for enabling diag mode of Pixel XL phones. Any update regarding this would be very helpful.
Thanks.
I tried to build a userdebug build from AOSP but I didn't get very far (first attempt at it, and it kept failing after 1-3 hours).
So cancelled that endeavor and installed the latest Lineage from InvisibleK which was built as userdebug.
>adb shell
>su
>setprop sys.usb.config diag,adb
PC tried to install new drivers (as expected since it has a different vendor/product id). Qualcomm HS-USB Diagnostics 903D (COM14) showed up under Ports. Unknown ADB Interface couldn't install drivers, though. All the tools seem to be working fine.
I have to quit for now, but hopefully that's a start for you.
I wanted to build the stock build as userdebug because that's how you get the diag USB modes enabled. They were stripped from the -user builds.
Edit 1: Phone shows up in QPST now.
Edit 2: Phone shows up in QXDM after setting Target port in Communication setting.
Edit 3: I am not sure if I had installed the drivers linked in this thread, already. The driver version I have is 2.1.04
If someone can install a non-T-Mobile SIM and let me know what their NV 65538 is, I'd appreciate it.
Edit: This value did not change with a Cricket Sim in versus a T-Mobile SIM.
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!
Is there any possibility to change imei on Redmi Note 8 Pro. I already've rooted and twrp'd it.
Surely there's a way, but should you actually do it? Of course not.
Why not? There are good reasons to do it!
zardoz77 said:
Is there any possibility to change imei on Redmi Note 8 Pro. I already've rooted and twrp'd it.
Click to expand...
Click to collapse
Yes, you can and it's very easy.
This tutorial shows how to change the IMEI with and without root: naijaknowhow.net/how-to-change-imei-of-all-mtk-android-devices/
Since it's MTK sure there is a lot of ways to do it but are you sure?
Changing IMEI is illegal in most countries / will break your ability to call, sending / receiving SMSs.
Except if yours was null/invalid (multiple zeros) and you want to change it back.
@saurik
Doesn't work, very old tools, not that easy like you guys write.
zardoz77 said:
@saurik
Doesn't work, very old tools, not that easy like you guys write.
Click to expand...
Click to collapse
Have you tried maui meta?
Version 10.1816.0.1 just says boot, phone turned off, nothing happens anymore. I boot manually nothing happens in the tool
1920 the same and I got connection with the Redmi via W10, I can for example upload files onto Redmi
This is the right tool. I just rewrote my IMEIs with it. Make sure you have device drivers installed or it will fail to connect.
Palcorix said:
Have you tried maui meta?
Click to expand...
Click to collapse
zardoz77 said:
Version 10.1816.0.1 just says boot, phone turned off, nothing happens anymore. I boot manually nothing happens in the tool
1920 the same and I got connection with the Redmi via W10, I can for example upload files onto Redmi
Click to expand...
Click to collapse
Did it boot to meta mode?
Have you followed instructions? It is nearly the same in every video for IMEI changing.
On the Redmi Note 8 Pro, If you ever lose your IMEI and have a full TWRP backup, restore the following partitions:
- nvcfg
- nvdata
- nvram
- persist
- protect_f
- protect_s
Most notable protect_f and protect_s. This apparently contains modem files. Restoring the others fixed an issue where it didn't ask for MIUI account login after factory reset.
m1906g7g this is my device, maybe I need other drivers? I tried so many. For example "mt67xx USB Vcom" and others.
Doesnt work, of course with Win10 I had to disable "check driver signature". I disabled, that is ok now, but still, which drivers do I need? I use Modem Meta 1920 and it always stands on "Boot..."
CANNOT FIND THE PRELOADER/BROM COM PORT to boot ...pls check USB Driver Version...
When I put preloader USB Driver in Device-Manager, then it says error 10
zardoz77 said:
m1906g7g this is my device, maybe I need other drivers? I tried so many. For example "mt67xx USB Vcom" and others.
Doesnt work, of course with Win10 I had to disable "check driver signature". I disabled, that is ok now, but still, which drivers do I need? I use Modem Meta 1920 and it always stands on "Boot..."
CANNOT FIND THE PRELOADER/BROM COM PORT to boot ...pls check USB Driver Version...
When I put preloader USB Driver in Device-Manager, then it says error 10
Click to expand...
Click to collapse
VCOM MTK drivers i believe
Edit: this one https://androidmtk.com/download-mtk-usb-all-drivers
DUT IN META MODE! it goes to 19% at least....
XTM_Miracle Thunder 2.82, did something "done" but nothing happened, same IMEI
Just curious? What would be the benefit if any to changing your IMEI?
Not seeing a point to it. I had an old Lenovo K3 note an from time to time my IMEI would dissapear an I had a devil of a time getting SMS or calling to work when it did.
Luckily some kid on YouTube invented a software that replaced the default IMEI. An only then the cell worked.
So if removing it causes that many issues then why change it?
hello
yes there is a way.
first of all you have box like UMT Pro.
then you can. its complicated but you can
and you have to flash ENG firameware.
zardoz77 said:
Is there any possibility to change imei on Redmi Note 8 Pro. I already've rooted and twrp'd it.
Click to expand...
Click to collapse
Did you mess up the imei files or is it a blocked (reported stolen) phone? Discussing imei changing is not appreciated and most times even not allowed to discuss on XDA.
gee2012 said:
Did you mess up the imei files or is it a blocked (reported stolen) phone? Discussing imei changing is not appreciated and most times even not allowed to discuss on XDA.
Click to expand...
Click to collapse
in Türkiye goverment doesn't allow phones that brought from abroad. you have to pay lots of taxes. almost as much as phone price. thats why people trying to change imei.
I have Xiaomi Redmi Note 8 PRO GLOBAL bootloader unlocked, TWRP installed, Android 9 , MIUI 11, ADB and Fastboot see the phone and allow access, I need change IMEI, Modem META 10.1952 see the phone VCOM allow access to phone, IMEI data read from phone and Update parameter tool allow data read from phone and store. But when I have changed data serial and imei and write to phone back Modem META indicate upload compleate OK. But after reboot in phone when I turn it ON stay the original parameter phone not changed parameter.
what do you thinking about whay to change IMEI and Serial
I have a redmi note 8 pro, hacking * # * # 4636 # * # * for reasons it does not support the vodafone italia "volte". i disabled dsds now i no longer have access to sim 2 or imei of sim 2 has also disappeared and there is no way to restore it in the menu. can you help me? i have imei 2 written in the package. Thank you PS miui 12.04.0 eeu no root!
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.