Related
i've searched and searched so if i missed it please point me in the right direction. i would love it if you did.
it seems t-mobile has removed the ability to tether via bluetooth which is really the only tethering i need.
from what i can see using the images below, they use their own software to take things over.
if at all possible any of the following should work in theory:
kill their app
enable something somewhere
install another workaround app (least favorite option)
i would like to avoid going to an aftermarket rom if at all possible since this is really my only issue and i'm so over tinkering (no offense).
Attached shows t-mobiles tether options and the rest of the worlds tether options.
THANK YOU FOR ANY HELP!!!
so in regards to number 3 "install another workaround app (least favorite option)", it seems that FoxFi and CobaltBlue3 work for windows and other devices. I was not able to get it to work on Linux Mint or inside a the car.
i really hate t-mobile right now for doing this. why are they attacking me personally like this?
we need option 1 or 2. 3 sucks.
figured out option number 1 and it was terrible for someone that is tired of tinkering. is there a good way to do this without these steps? if not we need to make one.
the following steps were taken:
root and cwm
cwm backup
remove system/app/TetheringProvision.apk
copy res-framewrok.apk to ext_sdcard
decompile using apk-manager
*edit xml (http://forum.xda-developers.com/showthread.php?t=2057344)
compile
create framework-install.zip (http://forum.xda-developers.com/showthread.php?t=1840098)
install with cwm
reboot
*only sections: How to Enable Native Tethering steps 1 and 2 and How to Enable Bluetooth Tethering step 1
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Aronmorg said:
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Click to expand...
Click to collapse
load up connectbot and ssh to your localhost.
$ su -
permit root access through whatever app you use
# cd /data/data/com.googlecode.android.wifi.tether/var
# chmod 766 tether.log
That is as far as I have gotten. That lets you view the errors in the app (which are many).
Loading WiFi driver (cmd) - failed
Stopping AP - failed
Stopping WiFi interface - failed
Reloading firmware - failed
Starting AP interface - failed
Configuring AP - failed
Starting AP - failed
Configuring Ip-address - failed
Enabling Routing Fix - failed
Enabling NAT rules - failed
Enabling MSS clamping - failed
Enabling IP forwarding - done
Tethering now running - done
I will play more with it tomorrow to try to figure out why things are failing. I am leaning toward permissions issues as it seems that permissions were at the center of the log problem.
Aronmorg said:
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Click to expand...
Click to collapse
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
atombombzero said:
load up connectbot and ssh to your localhost.
$ su -
permit root access through whatever app you use
# cd /data/data/com.googlecode.android.wifi.tether/var
# chmod 766 tether.log
That is as far as I have gotten. That lets you view the errors in the app (which are many).
Loading WiFi driver (cmd) - failed
Stopping AP - failed
Stopping WiFi interface - failed
Reloading firmware - failed
Starting AP interface - failed
Configuring AP - failed
Starting AP - failed
Configuring Ip-address - failed
Enabling Routing Fix - failed
Enabling NAT rules - failed
Enabling MSS clamping - failed
Enabling IP forwarding - done
Tethering now running - done
I will play more with it tomorrow to try to figure out why things are failing. I am leaning toward permissions issues as it seems that permissions were at the center of the log problem.
Click to expand...
Click to collapse
Thanks for the response, truthfully I've never done connectbot and ssh. But it'd be fun to learn, I'll try to learn over the holidays, but I wouldn't understand what's wrong with the app. I'm not a developer. Is there a webinar that explains the basics of understanding apps so that I could learn?
I'm wondering if the developer knows of these issues.
bhint15 said:
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
Click to expand...
Click to collapse
I am running a rooted stock with a stock recovery. In installing the hotspot hack zip, does this require TWRP or CWM recovery??
Aronmorg said:
Thanks for the response, truthfully I've never done connectbot and ssh. But it'd be fun to learn, I'll try to learn over the holidays, but I wouldn't understand what's wrong with the app. I'm not a developer. Is there a webinar that explains the basics of understanding apps so that I could learn?
I'm wondering if the developer knows of these issues.
Click to expand...
Click to collapse
I am just a UNIX admin so I know enough to be dangerous. I am no dev.
bhint15 said:
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
Click to expand...
Click to collapse
Also, I can't find the hack of which you speak. I scoured the forums today and found nothing.
I'm running synergy 4.3 rom and native hotspot works no problem. .
I just got my wife's s4 to use the native hotspot by downloading the service.odex and .jar with stock rom. I don't know if something like that is available with the note 2. I see that someone using the synergy 4.3 rom got native hotspot to work, but is that possible with stock rom.
Hi.
I'm looking for ways to reverse tethering with P6 non rooted. I found the link below, but I'm having difficulty in running the program. Can anyone help me, what should I put in the settings of the program? I'm also running AdBlock Plus for Android, whihc calls for local proxy 'localhost' and port 2020.
http://www.goandroid.co.in/how-to-reverse-tethering/29720/
zemega said:
Hi.
I'm looking for ways to reverse tethering with P6 non rooted. I found the link below, but I'm having difficulty in running the program. Can anyone help me, what should I put in the settings of the program? I'm also running AdBlock Plus for Android, whihc calls for local proxy 'localhost' and port 2020.
http://www.goandroid.co.in/how-to-reverse-tethering/29720/
Click to expand...
Click to collapse
Connectify works well for me over wi-fi, as I understand, you are trying to reverse-tether over usb? port 2020 is not a problem since you will be using 8090 and 8080. You need to have an active and working adb (enable adb on your device and connect it to the pc, open cmd and run [adb devices], see if it turns up or not. If it does then it should not be a problem getting this to work according to the guide.
I have successfully rooted my xl with Magisk, and unlocked the wifi tether however, The connection seems to be somewhat superficial as the connected device doesn't have any INTERNET connection. I have tried connecting both a laptop and another phone to no avail.
I have tried 2 different methods of unlocking the tether:
Adding "net.tethering.noprovisioning=true" to the prop build
Installing Magisk tether mod
Both methods worked equally as half-assed.
Foxfi and all those apps don't work, I have to activate the handset hotspot in order for them to work, but even then it only broadcasts the built-in ssid.
I have scoured the Internet for some clues, but I cannot find anything that relates to my issue recently or my phone specifically. Any help would be greatly appreciated as i have a Joying stereo that is nearly useless without wifi and i dont want to have to return my phone and go back to my m9.
Pixel 2XL
Rooted
buildPD1.170816.025
I have a strange issue after i rooted my xl 2. I could no longer tether to my Nexus 7 2013 but other devices were fine. Don't recall it happening while on 8.1 DP1 or 8.0 prior to Nov update. So i'm back to stock for now and will reroot for this month's update to see if there's any change.
filthysanches said:
I have successfully rooted my xl with Magisk, and unlocked the wifi tether however, The connection seems to be somewhat superficial as the connected device doesn't have any INTERNET connection. I have tried connecting both a laptop and another phone to no avail.
I have tried 2 different methods of unlocking the tether:
Adding "net.tethering.noprovisioning=true" to the prop build
Installing Magisk tether mod
Both methods worked equally as half-assed.
Foxfi and all those apps don't work, I have to activate the handset hotspot in order for them to work, but even then it only broadcasts the built-in ssid.
I have scoured the Internet for some clues, but I cannot find anything that relates to my issue recently or my phone specifically. Any help would be greatly appreciated as i have a Joying stereo that is nearly useless without wifi and i dont want to have to return my phone and go back to my m9.
Pixel 2XL
Rooted
buildPD1.170816.025
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74728795&postcount=12
joeyddr said:
https://forum.xda-developers.com/showpost.php?p=74728795&postcount=12
Click to expand...
Click to collapse
I tried this method but it didn't work on 025, Nov sec, rooted with Magisk and on MetroPCS.
joeyddr said:
https://forum.xda-developers.com/showpost.php?p=74728795&postcount=12
Click to expand...
Click to collapse
is there anyway to do this via terminal emulator or solid explorer ( i have root), just dont have a usb cable with me.
phyl0x said:
is there anyway to do this via terminal emulator or solid explorer ( i have root), just dont have a usb cable with me.
Click to expand...
Click to collapse
yes.
Open teminal and type su (accept root prompt)
then type the step 4 and 5 commands
adeelmysore said:
yes.
Open teminal and type su (accept root prompt)
then type the step 4 and 5 commands
Click to expand...
Click to collapse
i tried that, but got "cmd: Failure calling service settings: Failed transaction (2147483646)"
https://imgur.com/a/Fd8D2
phyl0x said:
i tried that, but got "cmd: Failure calling service settings: Failed transaction (2147483646)"
https://imgur.com/a/Fd8D2
Click to expand...
Click to collapse
try with adb prob will get the same error.
adeelmysore said:
try with adb prob will get the same error.
Click to expand...
Click to collapse
ADB is the only way it works.
JagXK8 said:
I have a strange issue after i rooted my xl 2. I could no longer tether to my Nexus 7 2013 but other devices were fine. Don't recall it happening while on 8.1 DP1 or 8.0 prior to Nov update. So i'm back to stock for now and will reroot for this month's update to see if there's any change.
Click to expand...
Click to collapse
I just did this same thing to the "T." It works.
Download the magisk module through magisk downloads tab and then hook up your phone. Launch a power shell or cmd window from your ADB and fastboot folder.
Type "adb shell"
Hit "enter"
Type "settings put global tether_dun_required 0"
type "reboot"
Hit "enter"
Should it be letting me share wifi connection too though? It lets me share a functioning data connection, but when I hook my pixel up to wifi, turn on the hot spot, connect a device to the pixels hotspot connection, and try getting on the the internet with the second device I don't have internet on it. The second device will show a wifi connection in the status bar. I'm not really worried about it because I think any time I use hotspot it's with a data connection, but I thought I should be able to share a wifi connection too.
joeyddr said:
ADB is the only way it works.
Click to expand...
Click to collapse
ADB worked for me, tether is finally working! yay!
Schroeder09 said:
I just did this same thing to the "T." It works.
Download the magisk module through magisk downloads tab and then hook up your phone. Launch a power shell or cmd window from your ADB and fastboot folder.
Type "adb shell"
Hit "enter"
Type "settings put global tether_dun_required 0"
type "reboot"
Hit "enter"
Should it be letting me share wifi connection too though? It lets me share a functioning data connection, but when I hook my pixel up to wifi, turn on the hot spot, connect a device to the pixels hotspot connection, and try getting on the the internet with the second device I don't have internet on it. The second device will show a wifi connection in the status bar. I'm not really worried about it because I think any time I use hotspot it's with a data connection, but I thought I should be able to share a wifi connection too.
Click to expand...
Click to collapse
Have you been able to do this before? Every device I've ever had will turn off my WiFi as soon as I turn on hotspot. I haven't used it on the pixel 2 yet, but I'm looking a mod that will work on TMobile
rockingondrums said:
Have you been able to do this before? Every device I've ever had will turn off my WiFi as soon as I turn on hotspot. I haven't used it on the pixel 2 yet, but I'm looking a mod that will work on TMobile
Click to expand...
Click to collapse
It does turn off wifi. From my understanding it IS like that on every device that makes a hot spot. They only want you sharing a data connection. You can share wifi. Say you worked at a place that didn't want anything on their wifi except company devices. If you could share a wifi connection this would allow potentially malicious devices onto the network. That's why I think you can only share data. I think this is standard. If I'm wrong or if there is a work around to be able to share wifi hopefully someone will chime in and correct me.
Hi,
I recently bought a new Fire TV 4K that came with Version 6.2.8.1 out of the Box. It also has a Serial Number containing VM in it. According to some posts here this means, that it has some efuses blown and the USB Download Mode disabled in its bootrom, which makes it impossible right now to root or downgrade it.
The reason I need to downgrade is that I need to automate some tasks on the Fire TV for example with tasker. For exmaple I need the Fire TV to switch the Input at Boot automatically. It does this only when I press the home button. Automating this with tasker however requires the Accessibility Service, which Amazon has removed in current Versions of the Firmware. So the only solution is to root it or go back to older Firmwares, and both ways seem to have been blocked by AMazon right now.
Is this the latest information or are there solutions for this device to still root it?
And are there alternative ways to automate for example Home button press without root and Acessibility Service?
And which Fire Tv Stick can still be rooted right now even with the latest Firmware installed?
Any help would be appreciated.
According to this post, only versions with "VM190 or higher" have the fuse blown.
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)
NOTE: There have been multiple reports of devices with serial numbers containing VM190 or higher being shipped with DL-Mode disabled in BROM. These devices cannot be unlocked using kamakiri. These devices do not show up at all on USB when...
forum.xda-developers.com
So maybe your unit has a s/n lower then VM190.
Yeah my Serial contains *VM081* but I bought it far later than the post you mentioned. Also that post was made before Version 6.2.8.1 was released and efuses burned, which apparently does not allow downgrading anymore. And the guy who found the exploit has not posted anymore since 2019.
My understanding is that the USB Download mode being disabled and the efuses blown are two different things.
I have not yet read any comment on wether you can root a fresh out of the box device that has Version 6.2.8.1 on it.
And additionally newer devices seem to have no USB Download mode.
Is there a way to check whether my devices efuses are blown or not? And whether my device has USB Download mode before I open and short the device. RIght now I can still send back the device, but not once I have opened it. I don't wanna find out after opening the device that I can not root it.
So before I open the Fire TV, I wanna know whether it is rootable or not. Otherwise I will send it back. I wanna know wether the rooting method does also work once the device has been updated to 6.2.8.1.
ALso it would help to know wether the efuses burning only is limted to the 4K model. In that case I could get a Lite or Version 2 of the Fire TV. Unfortunately I have not found any FAQ regarding such questions.
Spamm00r said:
My understanding is that the USB Download mode being disabled and the efuses blown are two different things.
Click to expand...
Click to collapse
No, it's most likely the same thing...
Spamm00r said:
Is there a way to check whether my devices efuses are blown or not?
Click to expand...
Click to collapse
Yes, you can short the stick, connect usb and watch in lsusb. It will show no sign of the stick if the efuse is gone.
You can also connect an USB TTL UART Adapter, while doing the shorting. Then the log shows you that the boot-process goes to halt.
Spamm00r said:
So before I open the Fire TV, I wanna know whether it is rootable or not. Otherwise I will send it back. I wanna know wether the rooting method does also work once the device has been updated to 6.2.8.1.
Click to expand...
Click to collapse
The root/unlock method based on BR DL-Mode (via shorting), will not work on any 4k stick running 6.2.8.0 or later, regardless of the serial number.
The new Lite Stick, the new fTV Stick and the newest fTV 4K-Max Stick are also BR DL-Mode disabled.
So its game over for the current Fire TV Stick Models in regards to rooting right?!
This wouldn't be such a big issue if Amazon hadn't removed accessibility services, which dramatically reduces the use of a Fire Tv Stick.
I guess we will have to search for alternative routes. WHile it is probably still possible to root the device via eMMC hardware method, this is way too complex for me.
I have already a few ideas.
My plan now is to use a raspberry pi in conjunction with the Fire TV and issue the automation commands via adb from the raspberry pi.
All I need is issue the Home key at certain points. Everything else Tasker can already do without root and accessibility services.
Also Tasker contains ADB over WIFI Plugin, and only needs a one time issue of the adb tcp command after every boot. After taht you have a adb client running on the fire tv itself to do the rest for automation.
My plan is to let the raspberry issue this adb command at every boot of the fire tv and after that Tasker will be able to do the rest via adb WIFI.
I hope that works out.
For further reference and anyone else stumbling over these issues. Before buying a Fire TV, I wasn't aware of these issues, that for example Accessibility services have been removed and Rooting is impossible right now. So Right now I think the better option is to avoid any Fire TV and buy a Raspberry 4 and run Android TV on it. That way you already have root access and can do anything you want on it.
Spamm00r said:
So its game over for the current Fire TV Stick Models in regards to rooting right?!
Click to expand...
Click to collapse
That is valid for the current methods. There is still further development, but development needs time...
So it's best if you take a look into the xda forums from time to time
Spamm00r said:
So its game over for the current Fire TV Stick Models in regards to rooting right?!
This wouldn't be such a big issue if Amazon hadn't removed accessibility services, which dramatically reduces the use of a Fire Tv Stick.
I guess we will have to search for alternative routes. WHile it is probably still possible to root the device via eMMC hardware method, this is way too complex for me.
I have already a few ideas.
My plan now is to use a raspberry pi in conjunction with the Fire TV and issue the automation commands via adb from the raspberry pi.
All I need is issue the Home key at certain points. Everything else Tasker can already do without root and accessibility services.
Also Tasker contains ADB over WIFI Plugin, and only needs a one time issue of the adb tcp command after every boot. After taht you have a adb client running on the fire tv itself to do the rest for automation.
My plan is to let the raspberry issue this adb command at every boot of the fire tv and after that Tasker will be able to do the rest via adb WIFI.
I hope that works out.
For further reference and anyone else stumbling over these issues. Before buying a Fire TV, I wasn't aware of these issues, that for example Accessibility services have been removed and Rooting is impossible right now. So Right now I think the better option is to avoid any Fire TV and buy a Raspberry 4 and run Android TV on it. That way you already have root access and can do anything you want on it.
Click to expand...
Click to collapse
You don't need to issue TCP command. By default, wireless adb debugging is turned on in Fire TV stick.
Shaikh Amaan FM said:
You don't need to issue TCP command. By default, wireless adb debugging is turned on in Fire TV stick.
Click to expand...
Click to collapse
But the Tasker adb function needs it or how else can I make that Tasker function work?
Spamm00r said:
But the Tasker adb function needs it or how else can I make that Tasker function work?
Click to expand...
Click to collapse
You might already knew this that in normal Android mobile phones, with "adb tcpip 5555" command in PC, you start the wireless adb on port 5555 in phone. But when you enable ADB Debugging in Fire TV from it's settings, the wireless ADB Debugging is by default started, so you don't need to run that TCP command as the wireless debugging is already on and then Tasker will use it to get it's work done.
Shaikh Amaan FM said:
You might already knew this that in normal Android mobile phones, with "adb tcpip 5555" command in PC, you start the wireless adb on port 5555 in phone. But when you enable ADB Debugging in Fire TV from it's settings, the wireless ADB Debugging is by default started, so you don't need to run that TCP command as the wireless debugging is already on and then Tasker will use it to get it's work done.
Click to expand...
Click to collapse
Yes I agree the adb is active one the Fire Tv Stick and you can connect to it via wifi on port 5555.
But tasker still does not work with the adb function.
How did you make it work?
According to this:
https://tasker.joaoapps.com/userguide/en/help/ah_adb_wifi.html
You need to run this comamnd everytime you reboot.
Spamm00r said:
Yes I agree the adb is active one the Fire Tv Stick and you can connect to it via wifi on port 5555.
But tasker still does not work with the adb function.
How did you make it work?
According to this:
https://tasker.joaoapps.com/userguide/en/help/ah_adb_wifi.html
You need to run this comamnd everytime you reboot.
Click to expand...
Click to collapse
I am not using Tasker. But as you said above that you'll use raspberry to issue adb tcip command to the stick to turn on wireless debugging, that's not needed.
As far as I think, you'll have a profile of device boot event in Tasker and in it you'll have a ADB Wifi action which will have the button press command.
If that's the case then it should work without any issue.
In ADB WiFi action, set host to 127.0.0.1 ( Just saw that this is optional as well )
If it doesn't works let me know, I'll try installing tasker in my stick and test adb wifi in it.
How do you change volume in your volume change app without root?
Maybe I can issue the command for changing hdmi input the same way.
Shaikh Amaan FM said:
I am not using Tasker. But as you said above that you'll use raspberry to issue adb tcip command to the stick to turn on wireless debugging, that's not needed.
As far as I think, you'll have a profile of device boot event in Tasker and in it you'll have a ADB Wifi action which will have the button press command.
If that's the case then it should work without any issue.
In ADB WiFi action, set host to 127.0.0.1 ( Just saw that this is optional as well )
If it doesn't works let me know, I'll try installing tasker in my stick and test adb wifi in it.
Click to expand...
Click to collapse
Spamm00r said:
How do you change volume in your volume change app without root?
Maybe I can issue the command for changing hdmi input the same way.
Click to expand...
Click to collapse
What's the adb command to change hdmi input?
Shaikh Amaan FM said:
What's the adb command to change hdmi input?
Click to expand...
Click to collapse
There is no adb command to do that diretcly, but the Fire TV switches to HDMI source, if you press home button. SO I wanna issue Home key input via adb to make it switch the HDMI source to the Fire TV Stick.
"key_home": "adb shell input keyevent 3",
As far as I know you need to have root to issue CEC COmmands diretcly. Otherwiese you ahve to make a system method do that for you.
You probably bought one with a serial number of
G4N0VM081..... which is the new blown fuse version. You need to scour ebay for serial number
G070VM190..... or lower, then follow the current rooting guide. Make sure it's BRAND NEW and never been opened or else you're SOL since used sticks have probably been updated. New rootable sticks exists. I found half dozen on ebay a few months ago.
Spamm00r said:
There is no adb command to do that diretcly, but the Fire TV switches to HDMI source, if you press home button. SO I wanna issue Home key input via adb to make it switch the HDMI source to the Fire TV Stick.
"key_home": "adb shell input keyevent 3",
As far as I know you need to have root to issue CEC COmmands diretcly. Otherwiese you ahve to make a system method do that for you.
Click to expand...
Click to collapse
Ok so I just installed Tasker in my stick, tested adb wifi in it, it didn't worked. But I can develop an app which can execute provided adb command on every boot. It's night in my timezone, I'll develop that app tomorrow inshaallah.
That would be awesome.
Please keep the command to execute generic, as it may be useful to also execute other commands at boot. Let the user decide what command to execute.
Shaikh Amaan FM said:
Ok so I just installed Tasker in my stick, tested adb wifi in it, it didn't worked. But I can develop an app which can execute provided adb command on every boot. It's night in my timezone, I'll develop that app tomorrow inshaallah.
Click to expand...
Click to collapse
Spamm00r said:
That would be awesome.
Please keep the command to execute generic, as it may be useful to also execute other commands at boot. Let the user decide what command to execute.
Click to expand...
Click to collapse
[APP][NO ROOT] ADB on Boot | Run adb commands at boot automatically
How to use? 1. Enable ADB Debugging from Fire TV settings 2. In this app, add the adb commands that you want to execute on every boot 3. Set whether you want to display a Toast message on completion of command execution 4. Test the script if...
forum.xda-developers.com
I have to correct myself about adb wifi out of tasker not working.
ADB Wifi does work depending on the app that you are using. Local ADB shell does not work, while Remote ADB Wifi app does work.
The adb plugin for tasker does not work, but the adb wifi action from Tasker itself does work right away. In my earlier tests, other apps were just blocking adb wifi and I was confused and thought tasker's adb wifi is not working. But you have to properly close the abd wifi session with a "exit" command. Also the windows adb tool freezes and has to be killed in taskmanager. That is a source of error for testing adb on fire TV.
Also the adb wifi of tasker will not accept semicolon seperated commands. Shaikh Amaan FM's tool however does. In tasker You will have to create new task for every command and only issue one command. I don't know why, but thats the result of my troubleshooting.
Also you have to make sure that Tasker is properly bought, a trial version or a not genuine version won't work, as Tasker has signature checks implemented which silently brakes plugins without any obvious error messages.
Plugins however also do not work in Macrodroid.
So best thing is to use Remote ADB Shell app or Tasker's built in adb wifi task. Thatway you can mostly work around the fact that Fire TV is locked down, has no root and has accessibility services disabled.
So this is the solution to:
Solution for no Root and no Accessibility Service on Fire TV 4K Mantis on Version 6.2.8.1
Thatway I'm able to make Fire TV switch input via tasker by issuing a home button press via adb.
That's the best thing you can do under these conditions that you can't have root on Fire TV right now.