Related
Hello everyone ... Yesterday i tried to take screensot with DDMS.bat like usually... But after launch ddms.bat and plug DHD into PC ERRORs appears.
First is adb.exe stopped working http://screenshooter.net/2759574/gjoqvjp
Second: Microsoft Visual C++ Runtime Error http://screenshooter.net/2759574/sqhiuql
third: TODO: <File description> .... http://screenshooter.net/2759574/pxrrsbs
if i connect DHD without run ddms my adb.exe is working fine i think (adb devices recognize SN of my device) but afterrun ddms adb is crashing and other errors appear :/
Log in cmd window looks like:
12:39:39 E/adb:
12:39:39 E/adb: This application has requested the Runtime to terminate it in an unusual way.
12:39:39 E/adb: Please contact the application's support team for more information.
12:39:44 W/DeviceMonitor: Failed to connect to client '4505': timeout
12:39:47 E/DeviceMonitor: Adb connection Error:
12:39:47 W/DeviceMonitor: Failed to connect to client '4795':
12:39:48 W/DeviceMonitor: Failed to connect to client '4808': Connection refused: connect
12:39:48 E/DeviceMonitor: Connection attempts: 1
12:39:48 E/DDMS: Connection refused: connect
java.net.ConnectException: Connection refused: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannel Impl.java:507)
at java.nio.channels.SocketChannel.open(SocketChannel .java:146)
at com.android.ddmlib.AdbHelper.executeRemoteCommand( AdbHelper.java:367)
at com.android.ddmlib.Device.executeShellCommand(Devi ce.java:276)
at com.android.ddmuilib.SysinfoPanel.loadFromDevice(S ysinfoPanel.java:159)
at com.android.ddmuilib.SysinfoPanel.deviceSelected(S ysinfoPanel.java:126)
at com.android.ddmuilib.SelectionDependentPanel.devic eSelected(SelectionDependentPanel.java:52)
at com.android.ddms.UIThread.selectionChanged(UIThrea d.java:1666)
at com.android.ddmuilib.DevicePanel.notifyListeners(D evicePanel.java:752)
at com.android.ddmuilib.DevicePanel.notifyListeners(D evicePanel.java:740)
at com.android.ddmuilib.DevicePanel.access$1100(Devic ePanel.java:56)
at com.android.ddmuilib.DevicePanel$1.widgetSelected( DevicePanel.java:357)
at org.eclipse.swt.widgets.TypedListener.handleEvent( Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(Unkno wn Source)
at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Display.runDeferredEvents( Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Un known Source)
at com.android.ddms.UIThread.runUI(UIThread.java:492)
at com.android.ddms.Main.main(Main.java:98)
12:39:49 W/DeviceMonitor: Failed to connect to client '4818': Connection refused: connect
12:39:49 E/Logcat: Connection refused: connect
java.net.ConnectException: Connection refused: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannel Impl.java:507)
at java.nio.channels.SocketChannel.open(SocketChannel .java:146)
at com.android.ddmlib.AdbHelper.executeRemoteCommand( AdbHelper.java:367)
at com.android.ddmlib.Device.executeShellCommand(Devi ce.java:284)
at com.android.ddmuilib.logcat.LogPanel$3.run(LogPane l.java:527)
12:39:50 E/DeviceMonitor: Connection attempts: 2
12:39:50 E/EventLog: Connection refused: connect
java.net.ConnectException: Connection refused: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannel Impl.java:507)
at java.nio.channels.SocketChannel.open(SocketChannel .java:146)
Click to expand...
Click to collapse
I was looking for solution everywhere ... Reinstalled JDK (Java), SDK (revision 9), .NET Framework 4, Microsoft Visual 2010 ... What else can i do?
I`m using Windows 7 Ultimate x64, and on DHD ROM: Android Revolution 2.0.9 (but it is not ROM related... i flashed stock 1.32 and the same) However ... few weeks ago ddms was working fine without any errors :/
PLEASE for ANY help.
MOD:
Sorry if in wrong seciotn but didn`t know where can i ask for it.
The new SDK has a different path to adb.exe and its DLL files, so you might want to include:
c:\android-sdk-windows\platform-tools\
to your global PATH variable.
jkoljo said:
The new SDK has a different path to adb.exe and its DLL files, so you might want to include:
c:\android-sdk-windows\platform-tools\
to your global PATH variable.
Click to expand...
Click to collapse
Thanks for reply But i`ve already added this to PATH ... Forgot to write about it.
I wrote above ADB separately works fine ... but via ddms, adb is crashing.
Try to install new HTC Sync and copy files from platform-tools to tools.. After that & adding platform-tools to PATH my DDMS started working, and still works fine. I updated my SDK to the newest version.
Normally the path to adb in PATH is c:\android-sdk-windows\tools, as you may know, so I just added platform-tools path after it.
What do you mean when U say new HTC sync? I got sync for desire HD from SD.
Sent from my Desire HD using Tapatalk
Ok found newer version of HTC Sync ... installed it ... added again PATH/ copied files from platform-tools to tools ... but still the same :/ Anybody? Any ideas? It drives me crazy :/ Wrrrrr Now i`m not sure if any operation with adb, fastboot are safe for me For example radio flashing... With errors like this i`m afraid of bricking my device during radio flash...
New HTC Sync from HTC website. And you do not need a working SDK to flash a radio, just get the radio flash package from flashing guide.
You could try to remove the whole SDK and install SDK starter package from Android website.
I'm a developer experiencing the same issue, Htc Desire HD and adb work properly outside eclipse, but with eclipse it crashes. I have too Win7 64 bit and the newest version of SDK. I think something went wrong in the last update. I'm going to install latest skd in a XP to check what happens, before trying to reinstall eclipse and the SDK on my win7 machine.
Did you add C:\android-sdk-windows\platform-tools to your global PATH variable as suggested earlier in this thread? It fixed adb for me, and I use eclipse, too.
jkoljo said:
Did you add C:\android-sdk-windows\platform-tools to your global PATH variable as suggested earlier in this thread? It fixed adb for me, and I use eclipse, too.
Click to expand...
Click to collapse
As Jkoljo has said it has fixed my problem when new SDK was released.
Putting the path to the platform-tools and ddms worked after that.
Or try: cd "C: \ your SDK directory \ tools \ ddms.bat
If ddms is in platform-tools then: cd "C: \ your SDK directory \ platform-tools \ ddms.bat
I have the same problem. My ADB and HTC sync just works fine but when I run DDMS to capture a screenshot adb always crashes. I added both directories to the path variable. My system is XP 32bit.
With the old version of the sdk I didn't had any problems at all.
Any suggestions?
Mav3ric144 said:
I have the same problem. My ADB and HTC sync just works fine but when I run DDMS to capture a screenshot adb always crashes. I added both directories to the path variable. My system is XP 32bit.
With the old version of the sdk I didn't had any problems at all.
Any suggestions?
Click to expand...
Click to collapse
I gave up Didn`t solve it It still drives me crazy :/:/ The strangest thing is that ddms was working fine few (3) weeks ago. Suddently i connected to capture a screen and? buuuu :/ didn`t work -> adb.exe error :/
I DO NOT TALK HERE ABOUT NOT WORKING ADB
My ADB is working fine until i run ddms.bat. After that adb error appears :/
Hi again,
(Yes I have added the PATH variable)
I have been working in different machines to check if it was a room (AR HD 2.0.9), system or HDH itself problem.
I installed for the first time eclipse+SDK+ADT on a XP 32 bit and I got the same problem I have in my W7 64 bit. Impossible to connect.
Then I installed eclipse+SDK+ADT on a ubuntu 10.10 32 bit and all worked fine after I realised that once I started eclipse I had to open the console with root user, kill adb server and restart the adb server again. After that I had no problem debuggin my applications on the HDH with eclipse and ddms.
So I came back to my Win 7 64 bit and I did the same procedure. Now ddms seems to connect properly with the HDHD but when I try to debug anything I got a new error:
Failed to install myapp.apk on device 'HT0BHRX00568': Unable to open sync connection!
[2011-02-08 00:15:09 - xxx] java.io.IOException: Unable to open sync connection!
[2011-02-08 00:15:09 - xxx] Launch canceled!
I think there has to be something related with the windows installation and the sdk recently update.
Anyone has any new clues??
Thanks
Same here. It's driving me crazy. The funny thing is that it does work intermittently and then just stops again. Rebooting the PC and/or the phone doesn't fix it.
Please post if you find the issue.
I gave up Didn`t found any solution for this WRRRRRR thats the worst :/ There must be a way to fix it !
I'm still trying to solve it. As a temporary solution (I hope!) I'm developing using Eclipse on Ubuntu 10.10
I'm using Windows and not going to change my OS just for ddms ... Arrrrggg it was working on windows and must work again ;(
Tapnąłem z HTC Desire HD.
DDMS error
This seems to be related to and update (either Java, Android SDK or both)
The Java library is not handling IPv6 sockets.
In Linux, sudo "echo -n 0 > /proc/sys/net/ipv6/bindv6only" will turn off the IPv6 binding.
I am not sure what the equivalent method in Windows is.
for reference: http://stackoverflow.com/questions/...ent-ddms-from-command-line-not-seeing-devices
I think Java ... Cuase i didn`t update SDK until this error occured :/
Maybe Windows or Java updater did the update and voila ...ddms suddently stopped working. Maybe someone will find solution for Win users ...
Hi, I have disabled ipv6 on win7 as you suggested and nothing changed. Maybe in August was, but right now, I don't think It's ipv6 related because Eclipse works properly on a Ubuntu 10.10 fully updated with ipv6 running.
Thanks any way
Probably not breaking any ground here (since in hindsight it was blatantly obvious), but I thought I would share anyways...
I own several Android devices, and I'm always playing. well, tonight I was tweaking a few things over adb and got to wondering if I could use adb to connect from one Android device to another. Well, turns out it's pretty easy, if you're rooted...
Both devices need to be connected to the same wireless network.
Install adbWireless from the Playground (sorry, Play Store): https://play.google.com/store/apps/...251bGwsMSwyLDEsInNpaXIuZXMuYWRiV2lyZWxlc3MiXQ..
You only really need it on the receiving device, but I have it on everything anyway.
Copy the Linux adb binary into /system/xbin/ and set the permissions to 755 (rwxr_xr_x), and reboot.
You only really need to do this on the controlling device, but may as well do it on all.
Fire up adbWireless on the receiving device, grant root privileges, and note the IP address
Fire up a Terminal Emulator on the other device, and enter: adb connect <IP address from other device> (you typically don't need to add the :5555 on the end.
Job done! Pretty handy when working from a slate!
I also run dd-wrt firmware on my router, which let's me assign static IPs by MAC address, so the IP for the devices are always the same.
Regards - dr
adb binary is already built in, /system/bin/adb.
besides that, all that's left is get adbd running, and that can be achieved either by an app (like you suggest) or edit init.rc to have adbd as one shot service to allow manual start (doesn't boot with the system). cyanogenmod also has adbd over wireless done like this.
also, one could use an OTG cable to connect devices directly, while i agree adb over wireless is good, adb over ssh would be best.
Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...
danger-rat said:
Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...
Click to expand...
Click to collapse
Agreed.
Sent from my i9250
edit: checkout this commit @aosp-master: https://android-review.googlesource.com/#/c/41846/
i'll be cherry-picking this one today
danger-rat said:
Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...
Click to expand...
Click to collapse
Hi - Where can I get this more functional binary that's half the size of a standard linux binary? I've tried two, they are both around 330Kb, and they fail to run with error "non executable: magic 7F45" because they were not compiled for my ARMV71 processor. I ran chmod 755 on it and when I check the permissions it is executable (-rwxr-xr-x). Can you post a link to the one that's 156kb - I can't find it.
elfaure said:
Hi - Where can I get this more functional binary that's half the size of a standard linux binary? I've tried two, they are both around 330Kb, and they fail to run with error "non executable: magic 7F45" because they were not compiled for my ARMV71 processor. I ran chmod 755 on it and when I check the permissions it is executable (-rwxr-xr-x). Can you post a link to the one that's 156kb - I can't find it.
Click to expand...
Click to collapse
Bumb. Anyone home? Shoot me a link please.
Hey guys,
Now, I have a tablet (running android) and is rooted already (so, I'm ready to get any needed binary on my device). It supports OTG. When I plug in my phone (rooted) using OTG to my tablet, my phone says 'Android debugging enabled' in notifications, is also charging. When I go to TE (Terminal Emulator) of my tab and type: 'adb devices', it displays no device in the list of attached devices (obvious).
And yes, my tab has got OTG host modules in kernel because when I turn on USB mass storage on (in my phone), my tab detects it and I can use it.
Now, my question:
Can I actually do this? i.e., using adb in my tablet (for my phone) via OTG?
Can we run adb from the device to detect itself?
I'm sure you can see why this would be amazing and powerful.. possibly giving root to apps on non-rooted devices with adb's run-as com.package.apk and such?
Is this possible? To have adb run on the Android device and connect to itself? If it is, can you guide me to where to learn it?
Dave :cyclops:
Hello to all,
I've opened this thread because the solution to my problem was in the Experia Z3 sub forum and tied with Lolipop version
Well, i run CM 13 version (Android Marshmallow 6.01) and i went to a problem with tethering :
The access point was set OK, but no network (internet) access for the 'slave' connected device ! It was acting like a device without network...
Of course, my Wileyfox Swift was accessing fine the Net (even while tethering...)
My carrier is (France) FREE Mobile (but not FREE of charge ) and with the same SIM and an old ICS device, it was running fine... So the device is the culprit ! (and maybe the carrier, but the phone was bought without them... so i had to help myself ! )
So i've performed a search onto this entire forum, and found the solution :
I've put as links to keep the original thread, but it works with Wileyfox Swift CM 13 Android Marshmallow
Here we go :
Install 15 seconds ADB tools : http://forum.xda-developers.com/showthread.php?t=2588979
Came back to 80's with terminal console
http://forum.xda-developers.com/z3/general/lollipop-tethering-t3058923
In fact, you 'just' have to open a Powershell or CMD windows, then invoke :
ADB devices (to make your device recognized, once 15seconds installer is fine)
Then
ABD shell (wait for a few seconds to have the prompt with your device name)
Then copy the command like onto the thread
settings put global tether_dun_required 0
Each Linux command is colored in red
TIP : In shells, paste command is right click of the mouse
Thanks to all contributor, i can now use my device as an access point (i'm just pasting thread urls...)
Hi. I mistakenly spilled a glass of water over my MacBook and it is now destroyed (No Aple Care). While I am saving up for a new machine I am using Ubuntu 16.04 on a QNAP 453 Pro.
Everything work fine but i cant get it to recognise my phone in Terminal. When I connect the phone it shows the phone icon but i cant connect. It hasnt asked for authorisation on the phone to use the QNAP so
I can understand why its not showing up when i go into terminal and its not showing up as an attached device.
I tried this -
[email protected]_1604:~/Downloads/platform-tools$ sudo jmtpfs /home/admin/media/myphone
Device 0 (VID=18d1 and PID=4ee2) is a Google Inc (for LG Electronics/Samsung) Nexus 4/5/7/10 (MTP+ADB).
libusb_open() failed!: No such file or directory
LIBMTP PANIC: Unable to initialize device
terminate called after throwing an instance of 'MtpErrorCantOpenDevice'
what(): Can't open device
Aborted
As the title says I dont know much about Ubuntu. Any help would be most appreciated. Thanks.
edit - I am running Stock 7.1.2 beta with an unlocked bootloader.
Do you have debugging enabled in Developer Options on the Pixel?
CZ Eddie said:
Do you have debugging enabled in Developer Options on the Pixel?
Click to expand...
Click to collapse
Yeah and when connected its set to transfer files.
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!