[Linux/Mac] ADB & Fastboot (Un)Install Script - HTC Wildfire S

I have created a script to be used to install ADB and Fastboot on a Mac or a Linux computer. Simply run the script in Terminal or a like application and it will copy ADB and Fastboot to /bin/ (for Linux it will install the android-rules). Also, in the ZIP is an uninstaller script to remove ADB and Fastboot (and for Linux, the android-rules).
Also, as of Version 3.1 this also installs the JDK for Linux-based systems.
While advanced users probably won't need this, it would be good for noobs who need help using the ADB and Fastboot commands.
You can see the source and files at Google Code: https://code.google.com/p/adb-fastboot-install/.
You can download the file here: from Google Code
If you have any problems or errors, let me know.

Changelog:
Version 3.1
Added JDK Install for Linux
Version 3
Created separate scripts for Linux & Mac
Updated uninstall script
Version 2.1.1
Fixed errors in installer
Version 2.1
More code efficient.
Better comments in script.
Version 2
Combined installer scripts into one Universal
Updated Uninstall.sh to remove udev rules
Version 1.1
Added udev rules for Linux
Version 1
Initial release

kalaker said:
Attached is a file to install ADB and Fastboot. You can run this script from anywhere. This also includes an uninstall to remove ADB and Fastboot from your system.
To view source: http://www.github.com/kalaker
You can run this in Terminal or your equivalent application.
Click to expand...
Click to collapse
Link that works:
http://forum.xda-developers.com/showthread.php?p=25273268

Thank you for posting that! I forgot I also posted this here in WFS!! Thank you! I will update the 1st post here!

Now hosted on Google Code!

Related

[Q] Cyanogenmod 7 and Linux

Hi all,
I have just received my Defy and I'd like to flash Cyanogenmod 7, I've flashed numerous roms to numerous phones in the past but I was always using Windows. I now use Linux (latest ubuntu derivative).
Is there a guide anywhere for flashing from a linux machine? My google-fu is pretty much pulling up a blank on the subject!
Thanks very much
Follow steps from FAQ for CM7, and just use this : http://forum.xda-developers.com/showthread.php?t=1076138 for flashing SBF and rooting,
It's my second post for the same question today
There's just two things to know:
1) You don't use RSD Lite to flash sbf files, you use this instead: http://blog.opticaldelusion.org/2011/02/sbfflash-updates.html
2) To root the phone you don't use SuperOneClick. Instead, get this DefyRoot pack: http://forum.xda-developers.com/showthread.php?t=1076138. Extract the pack, run the script using sudo.
And that's that. With the above differences in mind, you can follow the usual instructions: http://forum.xda-developers.com/showthread.php?t=1065798
Edit: Damn, bikerabhinav was faster
Thank you guys for the quick replies! time to give it a go
Sorry but you don't happen to know the link for installing adb on linux do you? presumably I need it hehe
I got the SDK and extracted to a directory of my choice, how on earth do I use it though, executing android in a terminal does not work, the rest is simple, can't believe I'm stuck on this part lol
I sorted that, I ran android and downloaded the development tools, I now have adb. I need to research more now, ran adb via terminal, then tried to run the rootdefy.sh but it told me adb wasn't started! see this is going to be a learning curve in Linux
You don't need the SDK, the RootDefy pack has everything necessary. I never installed the SDK.
ADB starts automatically if it isn't running yet. Did you run the script as sudo, like I told you? If not, there can be various problems. It's not necessary to run it with sudo if there's an udev rule for the phone. The script attempts to write one, but I'm not sure if it still works with the latest udev versions.
So let's do it manually:
- unplug the phone
- create a /etc/udev/rules.d/51-android.rules file containing this:
Code:
ATTRS{idVendor}=="22b8", MODE="0666"
- now reload udev:
Code:
sudo udevadm control --reload-rules
- just to be sure, kill all previous adb instances:
Code:
sudo pkill adb
- now plug the phone in and run the script again; with or without sudo, it shouldn't make a difference anymore
Thanks very much, all done and dusted now

[TOOLS] [LINUX, MAC, WINDOWS] Knives & Forks

Hello guys and girls. I'm gonna describe a little tool called Knives & forks and why it's so awesome. It's made by a user called DieHappy, so all credit to him! Source post: http://forums.acsyndicate.net/showthread.php?5008
Need I say once more that this isn't my work?
Before we start, I'd like to say I take no responsibility if something bad happens!
What is this, you say?
It is a set of tools for everyone, all operating systems and devices. It is a toolkit written in Python to work for Linux, Mac OS X and Windows.
Well, what does it actually do?!
Easy there. DieHappy started working on this not so long ago, so the features are limited. Right now, he focuses on making sure this program offers a stable base for all known android devices. It sets up correct ADB and Fastboot drivers and also makes the need of an android sdk useless if you only use the drivers. No need to set up an environmental path to the sdk or to navigate to a folder to use ADB, you can use ADB from ANYWHERE! Just open up cmd/a terminal and type adb and bam, it works.
How to support this project?
I don't really offer assistance to this as my knowledge is limited, but I can probably give you answers to most questions. Check out the original thread here for more help.
How to reply to this thread?
Ask anything, or write anything about this program here. Do not clutter the original thread over at ascyndicate forums.
Ok, how do I go about installing this?
First off, make sure you know how to decompress archives (namely zip or rar archives). Try 7-zip. Also, make sure you know the process of creating and renaming folders.
Download current version: 12.02.04
Mac OS X
This was tested on Mac OS X 10.7.2. Please report your success or any errors you have running this on other versions, but report them on the source thread, no use in reporting this here.
Unzip to "/Users/INSERT-YOUR-USERNAME-HERE/knives-and-forks/"
NOTE: REPLACE "INSERT-YOUR-USERNAME-HERE" WITH YOUR COMPUTER USERNAME.
FOR EXAMPLE, I WOULD UNZIP THE FILE TO: "/Users/DieHappy/knives-and-forks/"
NOTE: MAKE SURE THE DIRECTORY NAME IS SIMPLY "knives-and-forks".
DO NOT INCLUDE THE VERSION NUMBER IN THE FILE NAME FOR THE .ZIP FILE YOU DOWNLOADED.
Open Finder to "/Users/INSERT-YOUR-USERNAME-HERE/knives-and-forks/"
Double-Click "/Users/INSERT-YOUR-USERNAME-HERE/knives-and-forks/Knives-and-Forks-Mac.app"
You should see the Knives and Forks Main Menu in the Terminal window.
Linux
This was tested on Ubuntu 11.10 and Xubuntu 11.10. Please report your success or any errors you have running this on other versions or Linux distros.
Unzip to "/home/INSERT-YOUR-USERNAME-HERE/knives-and-forks/"
NOTE: REPLACE "INSERT-YOUR-USERNAME-HERE" WITH YOUR COMPUTER USERNAME.
FOR EXAMPLE, I WOULD UNZIP THE FILE TO: "/home/DieHappy/knives-and-forks/"
NOTE: MAKE SURE THE DIRECTORY NAME IS SIMPLY "knives-and-forks".
DO NOT INCLUDE THE VERSION NUMBER IN THE FILE NAME FOR THE .ZIP FILE YOU DOWNLOADED.
Open Terminal
Change the permissions to executable for "Knives-and-Forks-Linux.sh" by typing this into the Terminal window, then pressing [ENTER]:
Code:
chmod +x ~/knives-and-forks/Knives-and-Forks-Linux.sh
NOTE: "~" is a shortcut so you don't have to type "/home/INSERT-YOUR-USERNAME-HERE/"
Change to the "knives-and-forks" dir by typing the following in the Terminal window, then pressing [ENTER]:
Code:
cd ~/knives-and-forks
Run "Knives-and-Forks.sh" by typing the following in the Terminal window, then pressing [ENTER]:
Code:
[B]./[/B]Knives-and-Forks-Linux.sh
NOTE: DON'T FORGET TO TYPE "./" BEFORE THE FILE NAME.
THIS TELLS LINUX TO RUN THE SCRIPT IN THE CURRENT DIRECTORY.
TYPING JUST THE FOLLOWING WOULD RESULT IN AN ERROR:
Code:
Knives-and-Forks-Linux.sh
You should see the Knives and Forks Main Menu in a new Terminal window.
Windows
This was tested on Winows 7 Pro x64. Please report your success or any errors you have running this on other versions.
Unzip to your user profile directory
-- Vista, 7, Server 2008, Server 2008 R2: "c:\Users\INSERT-YOUR-USERNAME-HERE\knives-and-forks\"
-- 2000, XP, Server 2003: "c:\Documents & Settings\INSERT-YOUR-USERNAME-HERE\knives-and-forks\"
NOTE: REPLACE "INSERT-YOUR-USERNAME-HERE" WITH YOUR COMPUTER USERNAME.
FOR EXAMPLE, IN WINDOWS 7 I WOULD UNZIP THE FILE TO: "c:\Users\DieHappy\knives-and-forks\"
NOTE: MAKE SURE THE DIRECTORY NAME IS SIMPLY "knives-and-forks".
DO NOT INCLUDE THE VERSION NUMBER IN THE FILE NAME FOR THE .ZIP FILE YOU DOWNLOADED.
Run "c:\Users\INSERT-YOUR-USERNAME-HERE\knives-and-forks\Knives-and-Forks-Windows.cmd"
Python will automatically be downloaded and installed for you.
Once python is installed, you should see the Knives and Forks Main Menu in the command prompt window.
Ok, installed it, now what?
You should be able to open up your terminal application (or command prompt) and run some adb commands. In the future we will be automating adb commands for you, but for now you can try rebooting your device via adb by opening up a terminal (or command prompt) window, then typing the following, then pressing [ENTER]:
Code:
adb reboot
NOTE: AT THIS STAGE, YOU SHOULD ONLY NEED TO RUN THE KNIVES & FORKS SCRIPT ONCE TO INSTALL DRIVERS AND GET ADB WORKING. ONCE SETUP IS COMPLETE, YOU CAN RUN ADB COMMANDS AS SOON AS YOU OPEN UP YOUR TERMINAL/COMMAND PROMPT WINDOW.
If everything worked, your Android device should reboot. For further reading on what you can do with adb you can read THIS PAGE.
Code:
[B]**** 12.02.04 ****[/B]
- LINUX CHANGES:
-- "python2" is now called by "Knives-and-Forks-Linux.sh" instead of "python" on Arch.
- This prevents starting the script with Python 3, which results in errors.
-- Changes to "scripts/linux/install-adb-linux.sh":
- "su" will be used if "sudo" is not installed, or user doesn't have permissions to use it.
- Added 32-bit libs for more 64-bit distros:
- Arch (new in this release)
- CentOS (new in this release)
- Debian
- Fedora (new in this release)
- Ubuntu, Kubuntu, Xubuntu
- Added Debian version of '/etc/udev/rules.d/99-android.rules'
- Added '/lib/udev/rules.d/92-permissions.rules' for Debian.
This should fix permissions, allowing adb to run without sudo or su.
- WINDOWS CHANGES:
-- Fixed a couple of missing quotes which were breaking things under Windows XP
- "%userprofile%" was coming back as "c:\documents" instead of
"c:\documents and settings\username" in a couple of places
-- "c:\python27" is now the only directory where we look for python.exe
- It is faster to download and install Python to "c:\Python27" than it is to search for it
elsewhere.
- This will also prevent issues where Python 3 was installed instead of Python 2, since the
script currently gives errors under Python 3.
-- Updated amd64 and x86 versions of setx.exe for updating system PATH on XP/VISTA/7
-- PATH is updated with adb.exe location after Python is installed.
-- The computer will now reboot after updating the PATH, to make sure it will be updated before
running the main program.
[B]
**** 12.01.27 ****[/B]
- GENERAL CHANGES:
-- After adb is installed, adb will reset the android device by running "adb reboot" instead of
displaying a list of attached devices with "adb devices".
adb was occasionally reporting no devices were attached, when they infact were. When this happened
"adb reboot" still worked, so it is a better test to see if adb is setup properly.
-- Friendlier messages during adb install and testing
-- Added a startup check to make sure the script is running from the correct directory
-- Removed empty Project directory, as it is not being used yet.
- LINUX CHANGES:
-- Added support for "lxterminal" and "urxvt" in "Knifes-and-Forks-Linux.sh"
-- Changed idVendors for Linux udev rules to lowercase instead of uppercase.
- WINDOWS CHANGES:
-- Startup script searches for python in "C:\Program Files (x86)" then "C:\Program Files" and
"c:\" last.
-- Drivers should now install even if the language is not English
-- Added drivers for Casio C771 G'zOne Commando
-- Added LG drivers
-- Replaced setx.exe
[B]**** 12.01.25 ****[/B]
- Replaced "Knives-and-Forks-Mac.sh" with "Knives-and-Forks-Mac.app".
Starting the script on a Mac should now be as simple as double-clicking the new .app file.
[B]**** 12.01.24 ****[/B]
- Fixed a typo which caused the script to crash when viewing the credits screen.
- Smarter python fix for Windows users.
-- "C:\" and all sub-directories are searched for python.exe.
-- If python is not not found, it will be downloaded from python.org and installed to c:\python27.
-- If python is found (in "C:\python27", "c:\python", "c:\xyz123", "c:\program files\python27" or
in any directory with any name anywhere on drive c:) the main menu script will launch.
- Added changelog.txt to the release .zip file.
[B]
**** 12.01.23 ****[/B]
- Minor update to fix Python installation for Windows users, which was causing the script not to launch.
[B]
**** 12.01.22 ****[/B]
(FIRST PUBLIC RELEASE)
- Added option to install adb & fastboot for Linux, Windows, Mac
- Added Linux drivers for:
-- ACER
-- ASUS
-- DELL
-- FOXCONN
-- GARMIN-ASUS
-- Google
-- Hisense
-- HTC
-- HUAWEI
-- K-TOUCH
-- KT Tech
-- KYOCERA
-- LENEVO
-- LG
-- MOTOROLA
-- NEC
-- NOOK
-- NVIDIA
-- OTGV
-- PANTECH
-- PEGATRON
-- PHILIPS
-- PMC-SIERRA
-- QUALCOMM
-- SK TELESYS
-- SAMSUNG
-- SHARP
-- SONY ERICSSON
-- TOSHIBA
-- ZTE
- Added Mac drivers for:
-- Nothing. According to Google, "It just works." Let me know if they are right.
- Added a custom Windows installer with drivers for:
-- GOOGLE
-- HTC
-- HUAWEI
-- SAMSUNG
is it useful to you guys? I mean, you don't ever have to hassle with having bad drivers as these always work. And you never need to hassle with ADB and/or fastboot commands as this sets up environmental values and other stuff so you can access the adb and fastboot commands from wherever you are, i.e. no need to navigate to a certain folder.
*bump*
Thanks man. Did some googling just now and found tools for my linux mint debian edition. Any new on this tools mate?Perhaps new features for next release.
Mac OSX 10.6.8, nothing happens on double click on .app file
Can You Mirror?
Theshawty said:
*bump*
Click to expand...
Click to collapse
I have tried 4 a wk. It seems the site is down. Could you please attach the latest version here or mirror it mega? I would greatly appreciate it. I just wanted to try this out and "round out" my toolkits. Thank you for your time and help.

[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]

[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]
ADB & FASTBOOT FOR OS X​
There has been some confusion since I discuss using Fastboot in this post, but the zip only contained ADB. This is completely my fault and I apologize. Either way I've updated the .zip to include ADB & Fastboot.​UPDATED: 08/17/2013 - Added Fastboot to adb-1.0.31-mac.zip​
I've seen several people having issues on OS X trying to use ADB since the release of Android 4.3. In my case ADB recognized my device, but each time I ran adb devices my device would be reported as offline. I downloaded the SDK from Google several times and always ended up with ADB v1.0.29 (4.2.2).
This will should solve your OS X & ADB issues if you're running Android 4.3. This ONLY includes the ADB & Fastboot executable files and is for Mac OS X ONLY. I, like many others, do not need the full SDK. If you're not an app developer, like myself, this is all you need to have ADB working on your machine.
For any new OS X users I'll add a how to just so you don't have to go search for it else where:
How to setup ADB + Fastboot on OS X
Note: This is for not for developers. This only includes ADB & Fastboot and is not the full Android SDK
Step 1: Download the ZIP containing ADB & Fastboot
Step 2: Extract the ZIP to the directory of your choice
Step 3: Optional Create an environment variable
1. Open Terminal
2. Type cd to take you to your home directory.
Code:
cd
3. Type touch .profile to create a hidden file in your home directory named .profile
Code:
touch .profile
4. Type open -e .profile to open the file you just created in TextEdit
Code:
open -e .profile
5. In the file, add the following:
Code:
export PATH=${PATH}:/PathToDirectoryWhereYouExtractedTheZIP
6. Save the file and close TextEdit, quit Terminal, and relaunch the Terminal
Step 4: In Terminal type adb devices, you should see your phone's corresponding serial number Ex: HXM1005HNF012345 device
Code:
adb devices
Note: If you choose not to create an environment variable from Step 3 it effects two things:
1. You will need to cd to the directory containing ADB each time you want to run ADB.
2. When executing ADB commands you will need to add ./ in front of ADB. Ex: ./adb devices
Dropbox Download
Alternate Download
still getting v1.029
wad3g said:
There has been some confusion since I discuss using Fastboot in this post, but the zip only contained ADB. This is completely my fault and I apologize. Either way I've updated the .zip to include ADB & Fastboot.
UPDATED: 08/17/2013 - Added Fastboot to adb-1.0.31-mac.zip​
I've seen several people having issues on OS X trying to use ADB since the release of Android 4.3. In my case ADB recognized my device, but each time I ran adb devices my device would be reported as offline. I downloaded the SDK from Google several times and always ended up with ADB v1.0.29 (4.2.2).
This will should solve your OS X & ADB issues if you're running Android 4.3. This ONLY includes the ADB & Fastboot executable files and is for Mac OS X ONLY. I, like many others, do not need the full SDK. If you're not an app developer, like myself, this is all you need to have ADB working on your machine.
Click to expand...
Click to collapse
would you please assist?

[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]

[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]
ADB & FASTBOOT FOR OS X​
There has been some confusion since I discuss using Fastboot in this post, but the zip only contained ADB. This is completely my fault and I apologize. Either way I've updated the .zip to include ADB & Fastboot.​UPDATED: 08/17/2013 - Added Fastboot to adb-1.0.31-mac.zip​
I've seen several people having issues on OS X trying to use ADB since the release of Android 4.3. In my case ADB recognized my device, but each time I ran adb devices my device would be reported as offline. I downloaded the SDK from Google several times and always ended up with ADB v1.0.29 (4.2.2).
This will should solve your OS X & ADB issues if you're running Android 4.3. This ONLY includes the ADB & Fastboot executable files and is for Mac OS X ONLY. I, like many others, do not need the full SDK. If you're not an app developer, like myself, this is all you need to have ADB working on your machine.
For any new OS X users I'll add a how to just so you don't have to go search for it else where:
How to setup ADB + Fastboot on OS X
Note: This is for not for developers. This only includes ADB & Fastboot and is not the full Android SDK
Step 1: Download the ZIP containing ADB & Fastboot
Step 2: Extract the ZIP to the directory of your choice
Step 3: Optional Create an environment variable
1. Open Terminal
2. Type cd to take you to your home directory.
Code:
cd
3. Type touch .profile to create a hidden file in your home directory named .profile
Code:
touch .profile
4. Type open -e .profile to open the file you just created in TextEdit
Code:
open -e .profile
5. In the file, add the following:
Code:
export PATH=${PATH}:/PathToDirectoryWhereYouExtractedTheZIP
6. Save the file and close TextEdit, quit Terminal, and relaunch the Terminal
Step 4: In Terminal type adb devices, you should see your phone's corresponding serial number Ex: HXM1005HNF012345 device
Code:
adb devices
Note: If you choose not to create an environment variable from Step 3 it effects two things:
1. You will need to cd to the directory containing ADB each time you want to run ADB.
2. When executing ADB commands you will need to add ./ in front of ADB. Ex: ./adb devices
Dropbox Download
Alternate Download
I've used a mac with with all three of me nexus devices so ime pretty familiar but..is anyone else having probs with fastboot trying to flash a system.img ...I kept getting a error everytime. Boot.img would go through but not system img...? Any help would be great. If not no worries...adb seems to work fine if u need to push something ... But this is the first device I couldn't use fastboot flash system with...??
Candy Painted
matthew0776 said:
I've used a mac with with all three of me nexus devices so ime pretty familiar but..is anyone else having probs with fastboot trying to flash a system.img ...I kept getting a error everytime. Boot.img would go through but not system img...? Any help would be great. If not no worries...adb seems to work fine if u need to push something ... But this is the first device I couldn't use fastboot flash system with...??
Candy Painted
Click to expand...
Click to collapse
Did you have ADB previously installed before download this .zip? This is not the full Android SDK, but the updated version of ADB and doesn't include fastboot.
wad3g said:
...and doesn't include fastboot.
Click to expand...
Click to collapse
Perhaps all references to fastboot should be deleted, right now this thread still says "adb + fastboot...". Thanks for providing it all the same. Save me the 400mb download
Chatperdu said:
Perhaps all references to fastboot should be deleted, right now this thread still says "adb + fastboot...". Thanks for providing it all the same. Save me the 400mb download
Click to expand...
Click to collapse
You're right. I can't believe that never crossed my mind, I guess I was assuming everyone previously had ADB on their machine.
Anyway, I've updated the download links and attachments so now everything includes ADB & Fastboot files. Hopefully this will clear up any confusing in the future and I apologize to all of you who had issues due to this.
wad3g said:
You're right. I can't believe that never crossed my mind, I guess I was assuming everyone previously had ADB on their machine.
Click to expand...
Click to collapse
I have a previous installation. I am assuming fastboot doesn't have to match the adb version. Will try it out soon. My previous solution is to boot into bootloader, than adb will find the device, an inefficient work around.
Chatperdu said:
I have a previous installation. I am assuming fastboot doesn't have to match the adb version. Will try it out soon. My previous solution is to boot into bootloader, than adb will find the device, an inefficient work around.
Click to expand...
Click to collapse
Yes a previous version of fastboot should work fine. I don't believe fastboot was updated. I still use the the fastboot version that came with 1.0.29.
i followed these instructions, including creating .profile, but still neither my nexus 4 or new nexus 7 running 4.3 are recognized. Nothing is listed when I do adb devices, just an emtpy list

How to install Gapps on Fire TV Stick 2 (tank) with Lineage OS already Installed

First things first, I'd like to give a shoutout to diegocr for making the test version of Lineage OS on tank devices! Before following this tutorial, your Fire TV Stick 2 needs to be unlocked and rooted before installing these mods.
{REQUIREMENTS}: A computer that has adb connections and/or an android phone with Termux commands to run adb, can be found here (simply copy and paste while following the tutorial): https://github.com/MasterDevX/Termux-ADB, you need to be connected to the same internet in order for the connecting to work properly, an already rooted tank that's unlocked, a Google Account Manager which needs to be installed for those who have issues signing into the Google Play Store along with a command you need to run to allow it to work, and a file which contains a PlayFire folder which you'll need to move on the root of the /0/sdcard directory.
Step 1: Download this version of Gapps its tvstock and the system partition has plenty of space available. Link: https://opengapps.org/
The platform needs to be arm, android version is 5.1, and the variant is tvstock.
Step 2: Now that you have Gapps downloaded, download this PlayFire folder along with Google Account Manager before even installing Gapps within TWRP (on the Fire TV Stick). Google Account Manager (Don't download the latest version or else you will get a parse error message due to incompatibility): https://www.apkmirror.com/apk/googl...unt-manager-5-1-1743759-android-apk-download/, PlayFire file w Folder (extract the file and put the PlayFire on the /sdcard directory): https://forum.xda-developers.com/attachment.php?attachmentid=4205571&d=1499532978
Step 3: After downloading and putting the PlayFire folder on the root of your sdcard, reboot into TWRP and flash the Gapps zip file with tv stock and wait until its finished then reboot your Fire TV Stick 2. You'll notice that its going to optimize from 0 to 108, its completely normal since its implementing these system apps into your android system. Upon boot and everything, be sure to connect to the internet due to Lineage OS shutting off the wifi, then run these commands for the Google Play Store to work within terminal as root. What I mean by that is you need to connect to terminal as (adb connect 192.168.x.x), then add (adb shell, su), and finally copy and paste this given command and you're all set: sh /sdcard/PlayFire/LazyNoTouch.sh
Step 4: Everything should work beyond this point. If you're having difficulty with this guide, private message me and I'll send my TWRP backup for those who have no clue what to do.
So I haven't ever really looked into putting custom roms on my fire stick before so I had to look up what PlayFire was. I haven't had time to mod mine yet but I'm a little confused as to why PlayFire (not upgraded since 2017) would be needed if the LeanBack launcher is already on the rom, Is it just reinstalling it with all the xposed and HDXposed stuff it comes with?
Could you please post or message me your twrp backup I have tried everything and can not get it working tried many times. When I run the script nothing happens still can't use Google play or login to it. Followed the steps to the tee.
Worked without any issues! thanks!
Thank you very much @theflashfromthecw it work great, but do you have a patch for working mic search ?
---------- Post added at 05:04 PM ---------- Previous post was at 04:43 PM ----------
The device is freezig after 3 minutes with the newest gapps and the linkes Google ACC manager. Any solutions ?
Try to install xposed-v87-sdk22-arm.zip with Xinstall and Downgrade option enabled before or adb install -d com.google.android.gsf.login_5.1-1743759-22_minAPI21(nodpi)_apkmirror.com.apk to downgrade if PlayStore update it afterward.
Is this still working? I have tried to get this working on FTV Tank running Lineage, but no luck with sign in..
Thanks!
update: I was able to get it working, I needed to enable developer options, and then root access because the script was not completing (needed for making changes to /system).
Thanks again for putting this together!
theflashfromthecw said:
First things first, I'd like to give a shoutout to diegocr for making the test version of Lineage OS on tank devices! Before following this tutorial, your Fire TV Stick 2 needs to be unlocked and rooted before installing these mods.
{REQUIREMENTS}: A computer that has adb connections and/or an android phone with Termux commands to run adb, can be found here (simply copy and paste while following the tutorial): https://github.com/MasterDevX/Termux-ADB, you need to be connected to the same internet in order for the connecting to work properly, an already rooted tank that's unlocked, a Google Account Manager which needs to be installed for those who have issues signing into the Google Play Store along with a command you need to run to allow it to work, and a file which contains a PlayFire folder which you'll need to move on the root of the /0/sdcard directory.
Step 1: Download this version of Gapps its tvstock and the system partition has plenty of space available. Link: https://opengapps.org/
The platform needs to be arm, android version is 5.1, and the variant is tvstock.
Step 2: Now that you have Gapps downloaded, download this PlayFire folder along with Google Account Manager before even installing Gapps within TWRP (on the Fire TV Stick). Google Account Manager (Don't download the latest version or else you will get a parse error message due to incompatibility): https://www.apkmirror.com/apk/googl...nt-manager-5-1-1743759-android-apk-download/, PlayFire file w Folder (extract the file and put the PlayFire on the /sdcard directory): https://forum.xda-developers.com/attachment.php?attachmentid=4205571&d=1499532978
Step 3: After downloading and putting the PlayFire folder on the root of your sdcard, reboot into TWRP and flash the Gapps zip file with tv stock and wait until its finished then reboot your Fire TV Stick 2. You'll notice that its going to optimize from 0 to 108, its completely normal since its implementing these system apps into your android system. Upon boot and everything, be sure to connect to the internet due to Lineage OS shutting off the wifi, then run these commands for the Google Play Store to work within terminal as root. What I mean by that is you need to connect to terminal as (adb connect 192.168.x.x), then add (adb shell, su), and finally copy and paste this given command and you're all set: sh /sdcard/PlayFire/LazyNoTouch.sh
Step 4: Everything should work beyond this point. If you're having difficulty with this guide, private message me and I'll send my TWRP backup for those who have no clue what to do.
Click to expand...
Click to collapse
Hi.... Will this method work on pre-rooted stock image ROM?
Unable to sign-in
Hi. Thanks for this guide. I have completed as you have asked. The GAPPs is installed but I am unable to sign-in to the accounts. Please advice how to fix this.
Hi guys, nice work! Will it work on a 1st generation FireTV (box, not stick)?
NihaalMoosa said:
Hi. Thanks for this guide. I have completed as you have asked. The GAPPs is installed but I am unable to sign-in to the accounts. Please advice how to fix this.
Click to expand...
Click to collapse
You must run
sh /sdcard/PlayFire/LazyNoTouch.sh
no luck
Hi
I am not able to run the script, as I have created a folder called "sdcard" on the root of the internal storage and placed the PlayFire folder there. Furthermore, I used the "sh /sdcard/PlayFire/LazyNoTouch.sh" in ADB Shell, but no luck. Do we need to root Lineage OS before we use the script? If it is, can someone kindly show me a guide, how to root, as I have never done it before.
Flash supersu
https://redirect.viglink.com/?key=e...2-1-t4016981/amp/&ref=https://www.google.com/
In twrp
---------- Post added at 07:08 PM ---------- Previous post was at 07:03 PM ----------
Or im twrp without root.
adb push TV-NoTouchGsf.apk /sdcard/TV-NoTouchGsf.apk
adb shell mount -o rw /system
adb shell "mkdir /system/app/NoTouchAuthDelegate/"
adb shell "chmod 0775 /system/app/NoTouchAuthDelegate/"
adb shell "rm /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "cp /sdcard/TV-NoTouchGsf.apk /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chmod 0644 /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chown root:root /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
0815hoffi said:
Or im twrp without root.
adb push TV-NoTouchGsf.apk /sdcard/TV-NoTouchGsf.apk
adb shell mount -o rw /system
adb shell "mkdir /system/app/NoTouchAuthDelegate/"
adb shell "chmod 0775 /system/app/NoTouchAuthDelegate/"
adb shell "rm /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "cp /sdcard/TV-NoTouchGsf.apk /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chmod 0644 /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chown root:root /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
Click to expand...
Click to collapse
I used your suggested method without the root. It worked
If someone else wants to try this method. I did the following steps:
1. Flashed Gapps.
2. Downloaded the PlayFire (mentioned on the first page of the thread)
3. Did the unzip process and from the sub-folder (where different files exist) ran the terminal and the commands that @0815hoffi mentioned.
4. Did reboot system and when Lineage OS loaded, I manually ran the Google Account Manager (mentioned on the first page of the thread).
any advice on how to properly activate recommendations on leanback
everything else works
lars1384 said:
I used your suggested method without the root. It worked
If someone else wants to try this method. I did the following steps:
1. Flashed Gapps.
2. Downloaded the PlayFire (mentioned on the first page of the thread)
3. Did the unzip process and from the sub-folder (where different files exist) ran the terminal and the commands that @0815hoffi mentioned.
4. Did reboot system and when Lineage OS loaded, I manually ran the Google Account Manager (mentioned on the first page of the thread).
Click to expand...
Click to collapse
would this work with the latest lineage os..?
For me it has not works with the latest.
With
lineage-12.1-20200221-UNOFFICIAL-tank.zip
It has worked.
I Think MicroG support in latest is the Problem maybe.
Cant seem to download tvstock version for the gapps you mentioned. As soon as I select platform and android version.. the tvstock button gets disabled
seems like tvstock is available from android 6.0 onwards for arm platform.
Please help or point me to a compatible gapps zip
Cant find gapps for arm processor, Android 5.1 with tvstock variant. Any help would greatly be appreciated
Mhtkmr25 said:
Cant find gapps for arm processor, Android 5.1 with tvstock variant. Any help would greatly be appreciated
Click to expand...
Click to collapse
Me too. Seems like opengapps doesn't have a mirror for that one anymore. I tried everything I could think of to search for it too, I even tried to build it from source and failed. But I kept reading every post I could and the best I could come up was finding this link:
https://www.androidfilehost.com/?fid=8889791610682906163
from this post from @diegocr, who is the OP of this build of LOS 12.1 for tank:
https://forum.xda-developers.com/t/rom-unlocked-tank-lineageos-12-1.3961110/post-83220635
It works! Didn't have to mess with any scripts because I couldn't actually find the gapps .zip I needed for those anyway. It's already modified. I just had to reboot into TWRP and flash it.
I'm not sure what the actual tvstock would have had that this doesn't. It does seem stripped down, but that was what I was hoping for when I opened up the thing to short out CLK.

Categories

Resources