Related
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:
Trying to root my sprint galaxy s3.
As a new user I am blocked from properly posting the link for the instructions I'm following, so you'll have to copy/paste. They are here:
galaxys3root.com/galaxy-s3-root/how-to-root-u-s-canadian-dual-core-galaxy-s3-on-mac-osx/
(I'm using linux not mac, but anyway)
When I plug in the phone, I can see in linux dmesg that it is connected. (I did enable USB debugging in the developer options)
However when I run adb-linux, it does not detect the device
# ./adb-linux wait-for-device
* daemon not running. starting it now *
* daemon started successfully *
(hangs forever)
# ./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
#
So adb-linux is not detecting the phone-- the list of devices is empty
I'm using debian with linux kernel 3.2.0 (I also tried with kernels 2.6.38 and 2.6.32, same result. I'm running as root, note the # prompt)
Someone posted about a similar problem, and a helpful person recommended "Did you try the kext fix?" - but I have not been able to figure out what the kext fix is and if it is applicable-- the only place I found it mentioned was in relation to Odin.
http://m.youtube.com/#/watch?v=7Soapch0c5U&desktop_uri=/watch?v=7Soapch0c5U
Riding the Uni on the GSIII
jwitt418 said:
youtube.com/#/watch?v=7Soapch0c5U&desktop_uri=%2Fwatch%3Fv%3D7Soapch0c5U
Riding the Uni on the GSIII
Click to expand...
Click to collapse
thanks, but not helpful since it's a windows-only solution.
However I found a newer version of ADB (stands for Android Debug Bridge) and it is seeing my device! So I'll post back with an update as to how the root goes.
btw - running e.g. ./adb-linux version will show the version. 1.0.25 failed, and 1.0.29 seems to be working
success! Rooted my phone. upgrading from adb 1.0.25 to adb 1.0.29 made the difference.
Hi,
I updates my galaxy watch by changing CSC but now it is impossible to connect anymore in OneUI!
Wifi connection only is ok
IP Fix ok
Bluetooth Off
On sdb always failed or device offline...
It was ok in the prevoious os version!!!
Maybe someone can help me?
Thank you for help
it takes a while try changing the port to 26099 or 26101 it took me like 2 hours on my first try
I also had problems resetting CSC back to UK after temporarily changing it to get my Galaxy Watch 46mm to get the new Tizen upgrade. Make sure that the watch is still set to debug mode and developer mode is activated after the CSC change and the watch has reformatted itself.
In my case, I could not reconnect to the watch with sdb until I had manually deleted the sdb key & pub files on my laptop, to force the watch to ask me to re-accept the RSA key and let my laptop connect to it again. The files to be deleted are sdbkey and sdbkey.pub under C:\users\username\.tizen (make sure you can see hidden files in Windows Explorer).
Good luck.
AJP
Ok thanks for help but not working!
-> Activate Developpement mode + Debug USB ok
-> Erasing tizen files in my pc
but don't work very strange!It says always 'target is offline'..
studywes said:
Ok thanks for help but not working!
-> Activate Developpement mode + Debug USB ok
-> Erasing tizen files in my pc
but don't work very strange!It says always 'target is offline'..
Click to expand...
Click to collapse
Try using updated sdb version and use phone as Hotspot for both devices.
You can find most up to date version in c/tizenstudio after installing it
Sent from my Samsung SM-G973F using XDA Labs
One step often omitted for getting "sdb connect" to work is after turning on debug, off bluetooth, on wifi, and making wifi connection.... THEN REBOOT the watch.
Thank you for help!!All is ok after a simple reboot!!!!!!!!
Thanks Gruuvin
I can not run SDB on my Win 10 64bit.
Downloaded SDBstarterKidv1 unziped sdb_2.2.60_windows-64 and navigated cmd to C:\Users\Petr\Desktop\SDBstarterKidv1\sdb_2.2.60_windows-64\data\tools
sbd shell does not work.
C:\Users\Petr\Desktop\SDBstarterKidv1\sdb_2.2.60_windows-64\data\tools>sdb shell error: target not found failed environment shell, so it will retry shell command. error: target not found C:\Users\Petr\Desktop\SDBstarterKidv1\sdb_2.2.60_windows-64\data\tools>
Can you guys help me?
run with admin rights or make path var. on PC it's really sensitive about what and where stuff is installed
can't connect
petrmelis said:
I can not run SDB on my Win 10 64bit.
Downloaded SDBstarterKidv1 unziped sdb_2.2.60_windows-64 and navigated cmd to C:\Users\Petr\Desktop\SDBstarterKidv1\sdb_2.2.60_windows-64\data\tools
sbd shell does not work.
C:\Users\Petr\Desktop\SDBstarterKidv1\sdb_2.2.60_windows-64\data\tools>sdb shell error: target not found failed environment shell, so it will retry shell command. error: target not found C:\Users\Petr\Desktop\SDBstarterKidv1\sdb_2.2.60_windows-64\data\tools>
Can you guys help me?
Click to expand...
Click to collapse
I have the same problem, did you solve it somehow? or what solution.
also can't connect from windows 64.
Most old methods of changing the region on the samsung watches don't work anymore. Given their return policy I thought I bought expensive junk.
*#272*719434266344#
Click to expand...
Click to collapse
starts the csc selection but doesn't actually change the region.
TL;DR you need to install the combination firmware and edit two files
INFO: Netodin works fine in linux as well with wine since it works over the wifi
1. Start NetOdin3 click options and disable auto reboot
2. Click AP and select the combination firmware
3. Hold reboot button on the Samsung watch, when the reboot screen shows up press home multiple times to get into the boot menu
4. Jump to the Download (Wireless) and hold the boot button again to get into the Firmware download menu
5. Press the same button to more times to switch the watch to AP mode
6. Connect your wifi to the watch SM-R830-someid
7. In NetOdin3 press Start to flash the combination firmware
8. Click reset and now press CSC button
9. Select the CSC md5 and press start
10. When you reboot the device hold the boot button again until you enter the boot menu again
11. Select recovery and let the device restart
12. Enter settings -> About watch -> Software -> Tap software version until debug mode starts (you may need to restart your watch)
13. Connect watch to wifi
14. sdb connect <watchip>
15. sdb root on
16. sdb shell
17. backup active-customer.info: sdb pull /csa/csc/csc-active-customer.inf
18. backup prodcode.dat: sdb pull /csa/imei/prodcode.dat
19. edit /csa/csc/csc-active-customer.inf and replace csc code (I used vim and the XAR for the US version, https://www.geeksforgeeks.org/vi-editor-unix/ )
20. edit /csa/imei/prodcode.dat and replace last three characters to csc code you want (don't enter the csc selection after this it will reset it to the factory region)
21. reboot the device into recovery (i used /usr/bin/csc-util --reboot customer_change but i'm not sure it's necessary)
22. run netodin again and select AP, BL and CSC to flash stock
23. enjoy samsung pay if you have a US credit card (seems like you no longer need to install samsung pay apks on non samsung phone it's part of the wearables app)
R830 combination firmware
https://www.file-upload.net/download-13751174/combination-R830XXU1ASI2.7z.html
R830 3 file firmware
https://www.file-upload.net/download-13751206/multi-3file-R830XXU1BSI9.7z.html
sha256 checksums:
e719a024540706c07ae956c2a737b43dcaefa2b3335b1118121b6ca8168089ab AP_R830XXU1BSI9_usr.tar.md5
d0be4fdd7f5abaa6a4520f487b85dec14f94dd9d14a239fde69f5281817f7d99 BL_R830XXU1BSI9_usr.tar.md5
8f28bee9aa56b5c8d2fb8fa7bf16ab5cf0c3bff5fc547e2ada18a90c161f61e5 COMBINATION-FT40_R830XXU1ASI2.tar.md5
efe5e799c95c70aa1de8cced5a544bc471b2b74f61a3babffa72a7e295804225 CSC_OXA_R830OXA1BSI9_usr.tar.md5
Click to expand...
Click to collapse
Thanks to @adfree for the links and purcival for the order of how to flash the combination firmware and stock after
[0] Netodin
[1] how to change region on samsung gear s3
[2] combination firmware for sm-r820 by @adfree
[3] sdb in tizen studio CLI tools section
Hi,
Can l use this method just for updating the firmware of my watch?l'm still on R830XXU1ASHF.. if yes should l follow all these steps??
Thanks
What csc your watch?
tb_ said:
What csc your watch?
Click to expand...
Click to collapse
Thank you for your reply,l bought my watch in UK.
According to the list the csc is BTU-UNITED KINGDOM.
A Beginner
Hi,
First of all I want to thank you guys for the grat work.
I want to say that I am actually a beginner or amature when it comes to what you are doing
The instructions are very clea. But I would really appreciate it if anybody describes what to do with more details, especially the codes of sdb. Just some more details
It would be great if you can upload a video "If possible"
1. What is the worst thing that might happen if I do something wrong? Can the watch be ruind? Can I fix it if it happens?
2. Where can I find the csc of my country "Sweden" I googled it and found like 5 or 6 different csc !! Is there any trusted source?
3. Is it appliable to R820??? the 44mm model? or do I need to do something different in my case??
Thanks in advance
Coming from the other thread to confirm this worked for me, thanks a ton! Didn't think it would be that simple with just editing two text files.. lol
For those who missed it(I did), some steps are missing where one has to repeatedly connect back to AP every time something has to be done in NetOdin.
Also if anyone is confused about the steps, it's pretty much the same process for all samsung watches so just search for it on youtube, it's there.
Out of curiosity, where did you get the firmware from?? @tb_
2avrmillion said:
Coming from the other thread to confirm this worked for me, thanks a ton! Didn't think it would be that simple with just editing two text files.. lol
For those who missed it(I did), some steps are missing where one has to repeatedly connect back to AP every time something has to be done in NetOdin.
Also if anyone is confused about the steps, it's pretty much the same process for all samsung watches so just search for it on youtube, it's there.
Out of curiosity, where did you get the firmware from?? @tb_
Click to expand...
Click to collapse
Hi ,
Thanks for your feedback,are the sdb thing code mandatory?on youtube they only add the 3 or 4 files on odin and just flash it...
Hey guys, firstly thankyou! This worked perfectly and now I'm able to use Samsung pay down in Australia! Only thing that I would add from the perspective of being a complete beginner to Odin, is how to save the files when you edit the CSC (press escape then type ":wq") it took me an extra 20 minutes to figure it out and I thought someone might find it useful
2avrmillion said:
Out of curiosity, where did you get the firmware from?? @tb_
Click to expand...
Click to collapse
Got it from a third party. I was worried that it was counterfeit so before installing it I went through the system files to see if it's really the right model. But I can of course not guarantee that it wasn't modified by a third party. But I kinda assume that samsung won't boot from any random image given that you can't downgrade Samsung and even their tizen to any version you want apparently.
dodo1515 said:
Thank you for your reply,l bought my watch in UK.
According to the list the csc is BTU-UNITED KINGDOM.
Click to expand...
Click to collapse
{tizen} % cat preconfig/BTU/preset/csc-preset.ini
[default]
keyboard_lang="en_GB"
keyboard_preinstalled_lang="1^en_GB#en_US#de_DE#fr_FR#it_IT#pl_PL^en_GB
Click to expand...
Click to collapse
The csc.img has BTU inside. But I can't guarantee you anything when I ran this with my zone set to XTC it was booting fine but I couldn't get my phone to connect / initialize the watch after the factory reset. But not sure if it was the app or because i didn't properly reset or if I maybe shouldn't have reset.
So I can tell you that it will boot without issues but whether it works no idea. Maybe someone else can comment on that.
Highpryority said:
Hey guys, firstly thankyou! This worked perfectly and now I'm able to use Samsung pay down in Australia! Only thing that I would add from the perspective of being a complete beginner to Odin, is how to save the files when you edit the CSC (press escape then type ":wq") it took me an extra 20 minutes to figure it out and I thought someone might find it useful
Click to expand...
Click to collapse
I think you are talking about steps 17 and 18. If so can you please till me a bit more detailed how to do these steps ! I mean Do we edit manually in the sdb?? or how are we editing? Why do we need to save the files after editing? there is nothing about saving files in the steps above!
Sorry if my questions are silly but I am a real beginner here!
tareqsy91 said:
1. What is the worst thing that might happen if I do something wrong? Can the watch be ruind? Can I fix it if it happens?
Click to expand...
Click to collapse
No one will give you guarantees on this because no one wants to blame if something goes wrong. But if you try absolutely under no circumstances interrupt the flashing process and absolutely don't use the wrong model ROM. Also to be safe don't try to flash a firmware that has a lower version than your current one.
tareqsy91 said:
2. Where can I find the csc of my country "Sweden" I googled it and found like 5 or 6 different csc !! Is there any trusted source?
Click to expand...
Click to collapse
csc usually depends on the vendor. So there are a bunch of sweden csc's . But you should be able to find your current csc in /cas/imei/prodcode.dat
a list is on droid views
tareqsy91 said:
3. Is it appliable to R820??? the 44mm model? or do I need to do something different in my case??
Click to expand...
Click to collapse
r820 is the 44mm bluetooth model.
825 and 835 are lte with one version being US and the other being global I believe.
tb_ said:
No one will give you guarantees on this because no one wants to blame if something goes wrong. But if you try absolutely under no circumstances interrupt the flashing process and absolutely don't use the wrong model ROM. Also to be safe don't try to flash a firmware that has a lower version than your current one.
r820 is the 44mm bluetooth model.
825 and 835 are lte with one version being US and the other being global I believe.
Click to expand...
Click to collapse
Lower frimware? I have Tizen version 4.0.0.7
1. Do you know if the availabe combination frimware for R820 is of a lower frimware??
2. Yes My R820 is the 44mm bluetooth. thats correct. I guess I should use R820 which you linked in your original post!
3. Can you please describe more about steps 17-18 I didn't really understand how to edit! It's my first time using this sdb thing
Thanks for your patience everybody answering or even reading my questions
I think I am the most commenting member on this topic.
I have read a lot and almost all the details in each shared link in this thread.
I am trying hard I swear. Lately after downloading the shared files in the links in the original post. I can't start the file "web-cli_Tizen_Studio_3.3_windows-64"
It is just flashing a cmd window and nothing happens after that!
What should I do in this case??
The other file in the link "web-ide_Tizen_Studio_3.3_windows-64" is telling I should have JDK software which I installed but It didn't help anyway!
tareqsy91 said:
I think I am the most commenting member on this topic.
I have read a lot and almost all the details in each shared link in this thread.
I am trying hard I swear. Lately after downloading the shared files in the links in the original post. I can't start the file "web-cli_Tizen_Studio_3.3_windows-64"
It is just flashing a cmd window and nothing happens after that!
What should I do in this case??
The other file in the link "web-ide_Tizen_Studio_3.3_windows-64" is telling I should have JDK software which I installed but It didn't help anyway!
Click to expand...
Click to collapse
Don't use that because I had the same issue in Windows 10. Go to https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330 and download SDBstarterKidv1.zip. Extract it and run ansicon.exe under data/tools folder. It will open a command prompt.
shinzomask said:
Don't use that because I had the same issue in Windows 10. Go to https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330 and download SDBstarterKidv1.zip. Extract it and run ansicon.exe under data/tools folder. It will open a command prompt.
Click to expand...
Click to collapse
Thanks for the advice
I haven't done Netodin steps yet.
I am trying now to just connect the watch to the computer through the wifi network.
I have debugging mode on in the watch but I still can not connect to the watch
It keeps telling me failed to connect
connecting to 192.168.0.16:26101 ...
failed to connect to 192.168.0.16:26101
Is it normal I can't connect before doing the netodin steps??
tareqsy91 said:
Thanks for the advice
I haven't done Netodin steps yet.
I am trying now to just connect the watch to the computer through the wifi network.
I have debugging mode on in the watch but I still can not connect to the watch
It keeps telling me failed to connect
connecting to 192.168.0.16:26101 ...
failed to connect to 192.168.0.16:26101
Is it normal I can't connect before doing the netodin steps??
Click to expand...
Click to collapse
Normally the watch comes up with a prompt to allow your pc to connect to your watch. Maybe you might have to restart your watch. I would try the netodin step first because it might be more straightforward to connect the combination firmware to the computer because I didn't get any prompt on that.
Also maybe check that your virus scanner/firewall isn't blocking access.
shinzomask said:
Normally the watch comes up with a prompt to allow your pc to connect to your watch. Maybe you might have to restart your watch. I would try the netodin step first because it might be more straightforward to connect the combination firmware to the computer because I didn't get any prompt on that.
Also maybe check that your virus scanner/firewall isn't blocking access.
Click to expand...
Click to collapse
I've tried to turn off my antivirus and firewall but still no connection.
The newer versions of sdb 4.1.8 is showing the following:
The version of SDB client (4.1.8) and server (2.2.60) are different.
This may cause version compatibility problems.
It is recommended to use SDB server 4.1.8. *
I've tried to turn off my antivirus and firewall but still no connection.
The newer versions of sdb 4.1.8 is showing the following:
The version of SDB client (4.1.8) and server (2.2.60) are different.
This may cause version compatibility problems.
It is recommended to use SDB server 4.1.8. *
Click to expand...
Click to collapse
1.
sdb.exe once started is Background process...
To close active sdb you can do this:
Code:
sdb kill-server
2.
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
Look into this old post...
Try to read:
Code:
Guidelines_on_Connecting_GearS2_device_using_WiFi.pdf
Guidelines_on_Connecting_GearS2_device_using_WiFi_151222.pdf
Ignore Gear S2 text... because this is same shhh... since years...
Mandatory is to find your correct IP.
Hint...
Maybe it helps to try different PCs or Notebooks... sometimes more luck on other device... but only with correct IP in Command...
connecting to 192.168.0.16:26101 ...
failed to connect to 192.168.0.16:26101
Click to expand...
Click to collapse
If these digits are correct...
Command Line looks like this:
Code:
sdb connect 192.168.0.16
Not more not less... NO need to add something behind...
Best Regards
This is driving me crazy guys
Still cannot connect to the watch through wifi yet
I am getting this answer now
* server not running. starting it now on port 26099 *
* server started successfully *
connecting to 192.168.0.16:26101 ...
failed to connect to 192.168.0.16:26101
I am trying on both the older and the newer versions of sdb
Debugging mode is on in my watch
When writing same command again "sdb connect 192.168.0.16" I get weird figures or "error: target offline" in the newest version of sdb
I have even tried to create a private wifi from the computer I use and connect the watch to the same network but it didn't help either.
I am still only trying to connect the watch to the computer through sdb. I haven't done the odin steps yet. I am afraid doing odin steps and not being able to complete the sdb connecty steps !!
I have another question:
Where I live in Sweden. Samsung didn't release a bluetooth version at all. That's why I bought mine from Germany.
If I change my csc to Sweden. Will it work as there is actually no swedish bluetooth SM-R820 !! I mean that mine watch will be probably the only bluetooth r820 with swedish csc !!!! will I get updates as usual? will the watch even work?
@tareqsy91
1.
You have nobody who can help you?
No family... no friends nor neighbar with second/other PC... Notebook?
I am using different PCs with:
Win XP
Win 7
Win 8
Win 8.1
Never tried with sh .tty Win 10...
1.1
Maybe give infos what you use... Windows Version AND 32 bit or 64 bit
2.
Sweden or Germany...
No matter...
F. device work with byteexact Values... Sales Code aka CSC...
2.
Their are few other methods to READ EXACT infos from device... instead talking about blabla Sweden or Germany...
Look at this post... with screenshots...
App which can read these 2 files from Watch:
https://forum.xda-developers.com/showpost.php?p=80072694&postcount=786
Code:
com.somyac.gear.transfer.lite
Best Regards
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!