adbLink v5.1

Search This thread

jocala

Senior Member
Jul 4, 2010
3,203
1
2,469
Ocala
adbLink 5.1 is a companion program for Kodi.

It works with Kodi for Windows, Mac,Linux and Android

Global Features

Manage multiple Kodi devices from one PC
Edit XML and other files on your devices
Clone Kodi setups to new devices
Backup/Restore Kodi setups
Custom Cache Support for Kodi
Log file viewer for adbLink/Kodi logs
Hyperlinked HTML Help

Android Features

Install Programs without Android SDK
ADB/Fastboot enabled command-line
Busybox for root and non-root
Built-in WIFI/USB remote
Move Kodi data to external drives
Manage devices via USB or IP address
Root-aware File Manager
Install/Uninstall Apps

adbLink 5.1 is available for Windows, macOS and Linux/ChromeOS

http://www.jocala.com
 
Last edited:

Sc0rp10

Senior Member
Aug 22, 2010
254
59
40
Dubai
Samsung Galaxy S21 Ultra
hey jocala,

I'm on fire tv 1 OS 5.0.5.1 freshly installed. I have an attached hard drive which wont mount either on boot or while manually mounting. I am able to mount it using stick mount manually.

Could it be something to do with busybox? I had a similar problem on OS 3 and it was a busybox issue.
 

Sc0rp10

Senior Member
Aug 22, 2010
254
59
40
Dubai
Samsung Galaxy S21 Ultra
hey jocala,

I'm on fire tv 1 OS 5.0.5.1 freshly installed. I have an attached hard drive which wont mount either on boot or while manually mounting. I am able to mount it using stick mount manually.

Could it be something to do with busybox? I had a similar problem on OS 3 and it was a busybox issue.

so now I'm able to mount drive by running the script and from the adblink app. I am also able to browse the drive in adb shell but the drive1 folder appears empty in kodi and ES file explorer. also the script won't run on boot.
 
Last edited:

jocala

Senior Member
Jul 4, 2010
3,203
1
2,469
Ocala
so now I'm able to mount drive by running the script and from the adblink app. I am also able to browse the drive in adb shell but the drive1 folder appears empty in kodi and ES file explorer. also the script won't run on boot.

Unfortunately, Android sandboxes the drive so only root can see it. With OS5 the install-recovery*.sh scripts are no longer started at boot by the stock kernel, so starting things at boot no longer works.
 
  • Like
Reactions: Sc0rp10

jocala

Senior Member
Jul 4, 2010
3,203
1
2,469
Ocala
When I open adblink it Pops up with the error Can't create logfile.

This error means that adbLink is unable to write to the installation location.

It mostly happens to Mac users when they run adbLink from within the dmg container. You must DRAG the app from the dmg folder to the /Applications folder. It can also happen if you don't have write privileges in the Application folder (your user isn't admin). It that case drag adbLink to your Desktop, or any other location where you have write privileges.
 

googster

Senior Member
Apr 21, 2014
258
53
I was able to install kodi and a few other app a week afoot , I tried today to install a app and now I get device offline error...read the help file tried what it said still won't install.. Device offline.. Any suggestions?

Sent from my SM-G935P using XDA-Developers mobile app
 

jocala

Senior Member
Jul 4, 2010
3,203
1
2,469
Ocala
I was able to install kodi and a few other app a week afoot , I tried today to install a app and now I get device offline error...read the help file tried what it said still won't install.. Device offline.. Any suggestions?

Sent from my SM-G935P using XDA-Developers mobile app

Try pressing "Refresh ADB", sometimes it helps.
Check for other processes that may have adb tied up
Reboot
 
  • Like
Reactions: googster

googster

Senior Member
Apr 21, 2014
258
53
Try pressing "Refresh ADB", sometimes it helps.
Check for other processes that may have adb tied up
Reboot
Thank you for the reply.. When you say other processes do you mean on the firetv or on the computer...?
Where would I find them and how to stop them... Or a thread on it... Or something.. Thanks
 
Last edited:

jocala

Senior Member
Jul 4, 2010
3,203
1
2,469
Ocala
Thank you for the reply.. When you say other processes do you mean on the firetv or on the computer...?
Where would I find them and how to stop them... Or a thread on it... Or something.. Thanks

Think of the "offline" status as a busy signal. It simply means that another instance of adb has snagged a connection to your Fire TV, preventing you from properly connecting. That "other" adb connection could be a phantom adb instance running on your PC, or an adb connection made from another computer/tablet/phone on your network, or something like FireStarter running on the device itself. For a computer, use task manager for windows/ activity monitor for mac. I use ps to look at processes running under the linux kernel (Fire TV, phones,tablets,etc).

Also, try rebooting the Fire TV...
 
  • Like
Reactions: googster

googster

Senior Member
Apr 21, 2014
258
53
Think of the "offline" status as a busy signal. It simply means that another instance of adb has snagged a connection to your Fire TV, preventing you from properly connecting. That "other" adb connection could be a phantom adb instance running on your PC, or an adb connection made from another computer/tablet/phone on your network, or something like FireStarter running on the device itself. For a computer, use task manager for windows/ activity monitor for mac. I use ps to look at processes running under the linux kernel (Fire TV, phones,tablets,etc).

Also, try rebooting the Fire TV...
Thank you.. Ok.. I get it.. I used my computer to load a couple of app then used "Apps2fire' on my phone..At the same time.. They both worked. For about 20 minutes.. I factory reset my Firetv and it connected, then used my phone it connected, then shortly after, computer says offline, and phone will not connect..
May have to factory reset my Firetv again and just stick to computer ?.. Thanks again @jocala

Sent from my SM-G935P using XDA-Developers mobile app

---------- Post added at 04:28 PM ---------- Previous post was at 03:58 PM ----------

Thank you.. Ok.. I get it.. I used my computer to load a couple of app then used "Apps2fire' on my phone..At the same time.. They both worked. For about 20 minutes.. I factory reset my Firetv and it connected, then used my phone it connected, then shortly after, computer says offline, and phone will not connect..
May have to factory reset my Firetv again and just stick to computer ?.. Thanks again @jocala

Sent from my SM-G935P using XDA-Developers mobile app
@jocala Im pretty sure it was "Mouse Toggle" I installed.. Its was still trying to start even after I restarted my Firetv.. I uninstalled it now I'm getting a (device instead of offline) under status for adblink thanks again for your help

Sent from my SM-G935P using XDA-Developers mobile app
 

jocala

Senior Member
Jul 4, 2010
3,203
1
2,469
Ocala
Thank you.. Ok.. I get it.. I used my computer to load a couple of app then used "Apps2fire' on my phone..At the same time.. They both worked. For about 20 minutes.. I factory reset my Firetv and it connected, then used my phone it connected, then shortly after, computer says offline, and phone will not connect..
May have to factory reset my Firetv again and just stick to computer ?.. Thanks again @jocala

Sent from my SM-G935P using XDA-Developers mobile app

---------- Post added at 04:28 PM ---------- Previous post was at 03:58 PM ----------

@jocala Im pretty sure it was "Mouse Toggle" I installed.. Its was still trying to start even after I restarted my Firetv.. I uninstalled it now I'm getting a (device instead of offline) under status for adblink thanks again for your help

Sent from my SM-G935P using XDA-Developers mobile app

Good to know. Thanks for the report.
 
  • Like
Reactions: googster

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    adbLink 5.1 is a companion program for Kodi.

    It works with Kodi for Windows, Mac,Linux and Android

    Global Features

    Manage multiple Kodi devices from one PC
    Edit XML and other files on your devices
    Clone Kodi setups to new devices
    Backup/Restore Kodi setups
    Custom Cache Support for Kodi
    Log file viewer for adbLink/Kodi logs
    Hyperlinked HTML Help

    Android Features

    Install Programs without Android SDK
    ADB/Fastboot enabled command-line
    Busybox for root and non-root
    Built-in WIFI/USB remote
    Move Kodi data to external drives
    Manage devices via USB or IP address
    Root-aware File Manager
    Install/Uninstall Apps

    adbLink 5.1 is available for Windows, macOS and Linux/ChromeOS

    http://www.jocala.com
    7
    adbLink 3.6 released

    adbLink v 3.6 released

    /sdcard, /data/local/tmp, & /storage
    added to presets for file manager

    Activity indicator for local restores
    now properly resets when job is done.

    File manager checks that preset
    or ad hoc path exists prior to
    directory change via go button.

    Android Debug Bridge updated
    Version 1.0.39 - 0.0.1-4500957

    File manager updated to work with
    adb v1.0.39

    Fastboot updated
    Version 0.0.1-4500957

    http://www.jocala.com
    6
    08/08/22

    adbLink 5.1 release

    Internal script directory made
    uniform for all architectures.

    Terminal selection expanded.
    Preferences now allows you to
    choose Windows Terminal or
    Command Prompt for Windows,
    Terminal or iTerm for macOS,
    and Gnome Terminal, KDE Console
    or XFCE4 Terminal for Linux.

    Initial support for Intel ChromeOS.
    Tested with ChromeOS Flex.

    5
    adbLink 3.1 released

    adbLink 3.1 changelog 05/01/17

    The file manager is now root-aware. Perform common file management
    functions (copy,move,rename,mkdir,etc) on the /system and /data
    partitions if your device is rooted.

    When upgrading adbLink versions, data is preserved. Tested
    with adbLink 2.04 and up.

    The database and log files are now stored in a standard
    directory located in the user's $HOME. Mac users can
    now run adbLink without admin privileges.

    The progress bar activity indicator is back.

    Devices can be accessed on an ad hoc basis: double-clicking
    a USB serial number or entering an IP address on-the-fly
    allows interaction with the device w/o first creating
    a device record. In this case, Kodi defaults are assumed.

    Notification messages: toast-style messages or normal style is
    now a preference, with normal set as default.

    A global folder location for files copied from your device
    is set to your system $HOME. Changed to a global location of your
    preference, or overridden by a per-device preference in a
    device record.

    Keypad now uses device address as dialog title

    Log filename defaults to kodi.log or spmc.log depending on
    configuration

    System help updated

    http://www.jocala.com

    New video for adbLink v3.1 will be available later this week.