Closed SparklingWaterBurns closed 1 year ago
The tool expects adb to be installed through your distros package manager (apt, pacman, dnf, etc). I see you're running Debian through Chrome OS's Linux container, so you would use apt.
sudo apt install adb
It works, but now i get this error instead:
./ui.sh: 32: zenity: not found
what is it trying to find?
Zenity is the GUI tool needed for Fire-Tools, it can be installed using:
sudo apt install zenity
I'll update the setup instructions to include Chrome OS so it's not as confusing.
Got it fixed but it's not recognizing my fire or my phone anymore. USB Debugging is turned on in Developer Settings.
I've had that happen a couple times to fix it, on your Fire Tablet go to Device Options > Developer Options > Default USB Configuration and set it to File Transfer
I tried it and it still won't work. the Fire's cable is good and the Chromebook detects it but adb won't.
I have a USB converter dongle laying around. The USB-C plug fits into my phone only (fire uses a different type.) I can plug my fire's cable into the converter and then plug it into my Chromebook and that's the only way that it detects it besides using the other side of the fire cable.
After a reboot of ChromeOS and clearing USB debugging authorizations, It recognized the device!!
FIre Tools says device is unknown/unsupported??
could enabling/disabling widgets be a feature? just tried it with a command and it worked:
adb shell appwidget grantbind --package com.teslacoilsw.launcher --user 0
I found a bug. Tried to switch the launcher but it tried installing an already installed app.
I'm working on a way to automatically enable widgets for whatever launcher you choose, even .apks.
That error is my bad I forgot to add the Nova and Lawnchair .apks for the latest release but I'll have an updated version by tomorrow.
Apparently debloat worked with one app but Fire OS fixed it and now it stopped... All i'm getting are java.lang.IllegalArgumentExceptions when it tries to run.
Looks like adb is having problems connecting because those packages are present on all fire tablets & the tool will skip to the next package if it can't disable the one that it's working on.
Describe the bug:
I am attempting to make use of an old Fire tablet from 2017, but i simply can't use the program because it thinks ADB isn't installed. (platform-tools folder is in my home folder. Fire-Tools is also in there.)
Developer Mode and USB debugging is turned on on my fire.
Expected behavior:
To be able to use the program and have it detect ADB installed.
Platform:
Device:
Additional context:
ADB works with my fire tablet.