Hi,
Is FTV2 able to run node.js app?
thx
Yeah if you sideload termux to it, then you should be able to install node.js in termux.
Note I haven't tested this, I don't really need termux on any of my fire sticks.
Related
Maybe you've heard of this app? https://market.android.com/details?id=com.galoula.LinuxInstall
Note: You need to be rooted for this to work.
I've just installed and run it on my a500 (After a full backup through CWM of course). In settings, I set it to install Ubuntu Maverick Meerkat. It installed fine, although you have to go through some trial and error with the settings panel:
Loop file must be "/data/local/tmp/Linux.loop"
"Bind Android" must be enabled
"Allow write on /system" must be enabled!
Linux is activated through a terminal by typing "linuxchroot". Here is an extract from the terminal. (I'll upload screenshots when I find a working program.)
Code:
#linuxchroot
I: Mounting device for ubuntu maverick...
I: Entering chroot...
I: Executing /etc/init.android/rc_enter.sh
/etc/init.android/rc_enter.sh: 2: /etc/init.d/hostname.sh: not found
[email protected]:/# cat /etc/issue
Ubuntu 10.10 \n \l
[email protected]:/# apt-get install python
Reading package lists... Done
Building dependency tree... Done
python is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[email protected]:/# python
Python 2.6.6 (r266:84292, Sep 16 2010, 14:12:30)
[GCC 4.4.5] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> 3+7
10
>>> exit()
[email protected]:/#
I'm running a stock 4.010.13_COM_GEN2 rom.
I'm working my way around the console now. As you can see, apt-get and python work. I just need to figure out how (if it's possible) to install gnome onto this installation.
Update:
So it turns out "add-apt-repository" isn't installed by default in the usual place. Or the shortcut doesn't work. Either way, I found that the /usr/bin directory contains all the required files. Since this linux seems to log you in directly into root, which might not have well-made shortcuts, you cannot access the applications normally. I cd'd inbto /usr/bin and add-apt-repository works. Now to see if usr can be the default login.
Alright. Forget about trying to get a GUI working on this type of linux. Nvidia's Tegra drivers for Xorg are MIA.
Getting the following:
/system/xbin/linuxchroot.sh: UID: readonly variable
Any thoughts?
Sent from my MB860 using xda premium
just_mike said:
Getting the following:
/system/xbin/linuxchroot.sh: UID: readonly variable
Any thoughts?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
When do you get the message? Right after you type "linuxchroot"? If so, try typing su then hitting enter; and then typing "linuxchroot"
Same thing happens, will post over in the main thread? Thanks
Sent from my MB860 using xda premium
If you want a working guide with all the necessary files there is an app in the market.
For Ubuntu:
https://market.android.com/details?id=com.appbuilder.u14410p30729
Or for backtrack:
https://market.android.com/details?id=com.appbuilder.u14410p30729
Both work on the iconia. The only fiddling I had to do was change a CD command from the guides suggested command to CD /mnt/external_sdcard. I am able to boot both from my iconia .
profclean2000 said:
If you want a working guide with all the necessary files there is an app in the market.
For Ubuntu:
https://market.android.com/details?id=com.appbuilder.u14410p30729
Or for backtrack:
https://market.android.com/details?id=com.appbuilder.u14410p30729
Both work on the iconia. The only fiddling I had to do was change a CD command from the guides suggested command to CD /mnt/external_sdcard. I am able to boot both from my iconia .
Click to expand...
Click to collapse
I cant load it in the iconia
FearL0rd said:
I cant load it in the iconia
Click to expand...
Click to collapse
Where are you stuck? Maybe I can help.
GNOME
Zen_Jackal said:
I just need to figure out how (if it's possible) to install gnome onto this installation.
Click to expand...
Click to collapse
Idea: Install GNOME and then a VNC client and connect.
I'll try it later. Will post my conclusions/steps taken/results here.
-Cameron
Zen_Jackal said:
Alright. Forget about trying to get a GUI working on this type of linux. Nvidia's Tegra drivers for Xorg are MIA.
Click to expand...
Click to collapse
http://developer.nvidia.com/linux-tegra
Possibly this could help??
You cannot run Xorg with Tegra 2 drivers when your GPU is already in use by Android. Either you have to run some sort of a virtual Xorg driver and use VNC to connect to the Linux, or you have to use native Linux and scrap Android.
Connecting via VNC works just fine, I'm doing it all the time... Just don't try running a heavyweight like GNOME or KDE, use something like LXDE (looks ok, but it's a lot faster!). There are plenty of tutorials on how to set this up on the internet.
So this is something a lot of people forget. There are developer's out there who use macs. Maybe they bought an old one for really cheap, maybe they have a hackintosh (a way better alternative), maybe they just like apple (crazy people ). Anyway here is a guid on how to install android NDK and SDK on mac using HomeBrew.
1) Install Homebrew
So what is Homebrew ?
Homebrew is a package manager like apt (so basically it "installs the stuff you need that Apple didn’t"). it's really useful when it comes to installing command line utilities on mac since all you need to type is brew install <insert name here>. To install homebrew open up terminal by going into Finder>Applications>Utilities>Terminal (you should know this by now) and trying in
Code:
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
wait for it to complete. It might ask to install OS X command line tools if you are running 10.9 or later it should download and install them for you. if you are not, download Xcode from the app store and open it. It should install everything you need.
So after the installation is done type
Code:
brew doctor
to make sure you've installed homebrew correctly. (If you get an error brew not found try restarting your terminal)
2) installing NDK and SDK
Now that you have brew install just open up terminal and type
Code:
brew install android-ndk
brew install android
and done
if you ever need to find the location where you installed NDK and SDK at
Code:
/usr/local/Cellar/
Requirements:
TWRP recovery or equivalent
Root access
Android Debug Bridge (adb)
Know how to connect to device through adb (USB, network)
Ability to extract tar, lz and zip archives (7-Zip, Lzip)
Allowed apps from unknown sources through Fire OS
Ability to launch system apps (ES File Explorer, FireStarter)
USB or bluetooth mouse helps but is not required
Installation:
Install Xposed and the HDXPosed module
Download and install Open GApps ARM64, 5.1, pico using TWRP recovery
Download Google Play Store (Android TV) and rename APK to Phonesky.apk
Create a temporary folder on your Fire TV:
Code:
adb shell mkdir -p /sdcard/gtmp/lib/
Push Phonesky.apk to your Fire TV:
Code:
adb push Phonesky.apk /sdcard/gtmp/
Extract Core/gmscore-arm64.tar.lz and Core/gsflogin-all.tar.lz from the Open GApps archive obtained during step #2
Extract the contents of gmscore-arm64.tar.lz and gsflogin-all.tar.lz
Push these newly extracted files to your Fire TV:
Code:
adb push gsflogin-all/nodpi/priv-app/GoogleLoginService/GoogleLoginService.apk /sdcard/gtmp/
adb push gmscore-arm64/nodpi/priv-app/PrebuiltGmsCore/PrebuiltGmsCore.apk /sdcard/gtmp/
adb push gmscore-arm64/common/priv-app/PrebuiltGmsCore/lib/arm64/* /sdcard/gtmp/lib/
Enter adb shell and run su for root
Mount the /system partition with rw access
Code:
mount -o remount,rw /system
Create missing directories that Open GApps failed to create:
Code:
mkdir /system/priv-app/Phonesky
mkdir /system/priv-app/GoogleLoginService
mkdir -p /system/priv-app/PrebuiltGmsCore/lib/arm64
Copy the missing APKs and libraries to their proper locations:
Code:
cp /sdcard/gtmp/Phonesky.apk /system/priv-app/Phonesky/
cp /sdcard/gtmp/GoogleLoginService.apk /system/priv-app/GoogleLoginService/
cp /sdcard/gtmp/PrebuiltGmsCore.apk /system/priv-app/PrebuiltGmsCore/
cp /sdcard/gtmp/lib/* /system/priv-app/PrebuiltGmsCore/lib/arm64/
Change the permissions for the newly created files and directories:
Code:
chmod 755 /system/priv-app/{GoogleLoginService/,Phonesky/,PrebuiltGmsCore/,PrebuiltGmsCore/lib/,PrebuiltGmsCore/lib/arm64/}
chmod 644 /system/priv-app/Phonesky/Phonesky.apk
chmod 644 /system/priv-app/GoogleLoginService/GoogleLoginService.apk
chmod 644 /system/priv-app/PrebuiltGmsCore/PrebuiltGmsCore.apk
chmod 644 /system/priv-app/PrebuiltGmsCore/lib/arm64/*
Remove the temporary folder:
Code:
rm -r /sdcard/gtmp/
Exit adb shell
Download Google Play services (Android TV), variant 846 (8 for Android TV, 4 for arm64-v8a, 6 for 320 dpi) and rename APK to com.google.android.gms.apk
Download Google Account Manager 4.4.4 and rename APK to com.google.android.gsf.login_4.4.4.apk
Install Google Play services (Android TV) and Google Account Manager 4.4.4 using adb:
Code:
adb install 'com.google.android.gms.apk'
adb install -r -d 'com.google.android.gsf.login_4.4.4.apk'
Disconnect adb and reboot Fire TV
Connect to adb, enter adb shell and run su
Mount the /system partition as ro
Code:
mount -o remount,ro /system
Exit adb shell and disconnect adb
Play Store Setup:
Launch Google Play Store. Play Store is a system app and requires a program such as ES File Explorer or FireStarter to launch.
Login to your Google account. You should be able to fully navigate this version of Google Account Manager with the Fire remote, but a mouse can be helpful.
Play Store should have launched and you can now install Android TV apps and use apps that require Play Store or Google accounts.
Credits:
AFTVnews for their Play Store guide
guyHalestorm for his updated AFTVnews Play Store guide
I created this because guyHalestorm's guide was getting pretty outdated and wanted a better guide for the next time I have to install Play Store instead of referencing multiple guides, comments and updating commands.
Notes:
I omitted some very, very basic things from the guide such as how to use adb, extract archives, and launch system apps from specific apps due to the guide already being very long and most XDA users should be familiar with these or can be easily learned from Google.
Windows users may have to replace forward slashes (/) with back slashes (\) in paths depending on their shell.
I only tested this on my Fire TV 2 but I don't see why this wouldn't work on other Fire TV devices with root. I didn't personally test this 1:1 since I already installed Play Store, so let me know there's problems.
Oh wow, thanks for this. I will try this out when I get home tonight.
Proved on Fire OS [5.2.6.2_r1] and it's working fine.
Made a couple changes to the guide which are hopefully the last:
Fixed minor typos
Fixed Phonesky.apk source directory path in cp command (command would have failed)
Greatly simplified push and copy commands which should also improve future Open GApps compatibility
Corrected directory and file permissions (chmod) which may have worked before but were incorrect and possibly insecure. If you've followed the guide before, do step 9 & 10, 13 and then 21 & 22
ok solved done
Anyone tested this on Fire TV 3?
StDevious said:
Anyone tested this on Fire TV 3?
Click to expand...
Click to collapse
Doesn't work on Fire TV 3 bro. There's no root for us v3 users. :'(
First of all thank you @Bracket- for the guide :good:
I have done Everything exactly like the guide
but i can't open the playstore.
When i open it, it loads for few seconds and then it close.
Do you have or anybody else here have an idea why this happens?
My system: Fire TV 2, 5.2.6.2 rooted, xposed and hdxposed installed
chris-89 said:
First of all thank you @Bracket- for the guide :good:
I have done Everything exactly like the guide
but i can't open the playstore.
When i open it, it loads for few seconds and then it close.
Do you have or anybody else here have an idea why this happens?
My system: Fire TV 2, 5.2.6.2 rooted, xposed and hdxposed installed
Click to expand...
Click to collapse
If you already have root, this guide is much too complicated
Simply modify build.prop and then install the appropriate GApps and you have the complete Play Store & Services available.
Take a look around: here
You only need these steps:
2. Customize build.prop
4. Install Open Google apps for Android TV (the newest version works fine)
5. Allow Google registration (NoTouchAuthDelegate)
Prerequisites:
XposedInstaller-3.1.5.apk (install Xposed v89+)
HDXPosed-1.3.apk
BusyBox
rainman74 said:
If you already have root, this guide is much too complicated
Simply modify build.prop and then install the appropriate GApps and you have the complete Play Store & Services available.
Take a look around: here
You only need these steps:
2. Customize build.prop
4. Install Open Google apps for Android TV (the newest version works fine)
5. Allow Google registration (NoTouchAuthDelegate)
Prerequisites:
XposedInstaller-3.1.5.apk (install Xposed v89+)
HDXPosed-1.3.apk
BusyBox
Click to expand...
Click to collapse
Thanks for you help :good:
I will do this tomorrow.
Short question: do i need also the gapps-config.txt or not?
And when i need it, what did i need for using only the playstore and services?
chris-89 said:
Thanks for you help :good:
I will do this tomorrow.
Short question: do i need also the gapps-config.txt or not?
And when i need it, what did i need for using only the playstore and services?
Click to expand...
Click to collapse
yes, you need gapps-config.txt
Code:
forceclean
skipswypelibs
skipvendorlibs
GoogleAssistant
+extsharedstock
+keyboardstock
+provision
+packageinstallerstock
+webviewstock
+notouchauthdelegate
Include
gappspico
rainman74 said:
yes, you need gapps-config.txt
Click to expand...
Click to collapse
Thanks, playstore works now :victory:
Btw whats the different between the notouchauthdelegate.apk from the gapps package and your tv-notouchgsf.apk? and why we need yours and not the one from the package? I ask just for my understanding
chris-89 said:
Thanks, playstore works now :victory:
Btw whats the different between the notouchauthdelegate.apk from the gapps package and your tv-notouchgsf.apk? and why we need yours and not the one from the package? I ask just for my understanding
Click to expand...
Click to collapse
The package com.google.android.gsf.notouch of Open GApps (TV-Stock version) does not work on Fire TV so that the AndroidManifest.xml had to be modified.
I followed the guide as exactly as I could:
I did not install Xposed and the HDXPosed module, because it is nowhere stated what it is for.
Open Gapps arm64 releases of 5 September 2018 are the last containing Core/gsflogin-all.tar.lz. So I used:
open_gapps-arm64-5.1-pico-20180905.zip.
my /system ran out of memory, so I had to create a symlink:
Code:
ln -s /data/priv-app/PrebuiltGmsCore /system/priv-app/PrebuiltGmsCore
and continued without any error from there.
But when I run Google Play Store app and try to login, I get Error [RH-01].
Before I get started, let me say that I love Magisk. It's a great app and works beautifully . . . about 99 44/100% of the time.
I also love Link2SD Pro. It's my go-to app not just for linking apps to my SD card, but for freezing and unfreezing apps, moving things in and out of /system, and just generally cleaning and debloating my tablet.
Unfortunately, the two don't work and play nicely on my Fire HD 10 (2017 edition running Fire OS 5.6.4.0 from March 2019). Link2SD relies on having an 'su' program available to do its magic and launches 'su' behind the scenes when it starts up. I verified this in two ways:
1. If I do 'ps' while Link2SD is running it shows that it opens a 'su' session, which in turn spawns a '/system/bin/sh' session owned by root.
2. If I hide Link2SD in Magisk Manager, it tells me it can't get root access.
Why is this important? Because whenever I try to get Link2SD to do anything that requires root access, it throws an error message that says 'CANNOT LINk EXECUTABLE DEPENDENCIES: "libandroid_runtime.so" is 64-bit instead of 32-bit.' This doesn't happen on my Fire HD 8s running 6.3.0.1.
I tried copying mtk-su, which gives me root access if I run it directly, into /system/xbin and creating a symbolic link to it with 'ln -s mtk-su su'. I was able to get a root prompt in the Fire OS shell by executing /system/xbin/su, but when I tried hiding Link2SD in Magisk Manager so it would (hopefully) open su from /system/xbin, which is at the end of my $PATH . . . nothing. I got the Spinning Wheel Of Death and Link2SD never launched. Apparently it was trying to launch mtk-su (as just 'su') behind the scenes and wasn't able to do so, or was waiting for something else to give it permission, or . . . well who knows.
So here I am. I think if I had an su binary that wasn't just a symlink to 'magisk', and that used the libraries in /system/lib, I could drop it into /system/xbin and Link2SD would fire it up if I hid Magisk from it. Any suggestions?
Thanks in advance.
NerdFire said:
Before I get started, let me say that I love Magisk. It's a great app and works beautifully . . . about 99 44/100% of the time.
I also love Link2SD Pro. It's my go-to app not just for linking apps to my SD card, but for freezing and unfreezing apps, moving things in and out of /system, and just generally cleaning and debloating my tablet.
Unfortunately, the two don't work and play nicely on my Fire HD 10 (2017 edition running Fire OS 5.6.4.0 from March 2019). Link2SD relies on having an 'su' program available to do its magic and launches 'su' behind the scenes when it starts up. I verified this in two ways:
1. If I do 'ps' while Link2SD is running it shows that it opens a 'su' session, which in turn spawns a '/system/bin/sh' session owned by root.
2. If I hide Link2SD in Magisk Manager, it tells me it can't get root access.
Why is this important? Because whenever I try to get Link2SD to do anything that requires root access, it throws an error message that says 'CANNOT LINk EXECUTABLE DEPENDENCIES: "libandroid_runtime.so" is 64-bit instead of 32-bit.' This doesn't happen on my Fire HD 8s running 6.3.0.1.
I tried copying mtk-su, which gives me root access if I run it directly, into /system/xbin and creating a symbolic link to it with 'ln -s mtk-su su'. I was able to get a root prompt in the Fire OS shell by executing /system/xbin/su, but when I tried hiding Link2SD in Magisk Manager so it would (hopefully) open su from /system/xbin, which is at the end of my $PATH . . . nothing. I got the Spinning Wheel Of Death and Link2SD never launched. Apparently it was trying to launch mtk-su (as just 'su') behind the scenes and wasn't able to do so, or was waiting for something else to give it permission, or . . . well who knows.
So here I am. I think if I had an su binary that wasn't just a symlink to 'magisk', and that used the libraries in /system/lib, I could drop it into /system/xbin and Link2SD would fire it up if I hid Magisk from it. Any suggestions?
Thanks in advance.
Click to expand...
Click to collapse
Link2SD doesn't uses the Magisk SU. It's only using SuperSU.
AmznUser444 Dev said:
Link2SD doesn't uses the Magisk SU. It's only using SuperSU.
Click to expand...
Click to collapse
As far as I know I don't have SuperSU installed. I searched through all of the directories in my $PATH and the only 'su' I found was the link I posted in the OP.
NerdFire said:
As far as I know I don't have SuperSU installed. I searched through all of the directories in my $PATH and the only 'su' I found was the link I posted in the OP.
Click to expand...
Click to collapse
No sweat. You can easily flash SuperSu SR5 2.82 from Twrp, and don't do Magisk. The only issue is that you have to enable 'allow root by default' in supersu since it does not work if the apps have to ask.
If the stock SR5 does not work, try the slightly modded version from here: https://forum.xda-developers.com/showpost.php?p=74987123&postcount=2
Pre-unlock SuperSu was the only way to go, and it still works fine, but root access control is nonfunctional.
Post back what worked for you!
bibikalka said:
No sweat. You can easily flash SuperSu SR5 2.82 from Twrp, and don't do Magisk.
Click to expand...
Click to collapse
Huh. For some reason I thought SuperSu had gone the way of high-button shoes and daytime baseball. I'll have to go check it out. Thanks!
Hi there,
I'm using a Nvidia Shield TV Pro - unrooted due to the DRM stuff like Dolby Vision.
Now I want to reconfigure Kodi from Scratch. In my current installation there are a lot packages which aren't updatable anymore.
For that reason I was using Termux to copy the Kodi userdata. That worked until one year ago. With some updates of Android this isn't possible anymore. That's very sad, because Termux is fully configured with every tool I need.
Fortunately I can access /sdcard/Android/data/com.xbmc.kodi using adb. The disadvantage: adb shell doesn't even provide VI or any other simple editor. The proposed solution to install busybox fails in need of root permission. And just to copy the busybox binary to an accessable folder didn't work too. Android gives the binary 660 permissions (no execute).
My solution for editing some configuration files in Kodi now is:
adb shell: access /sdcard/Android/data/com.xorg.kodi/files/.kodi
adb shell: cp configfile to /sdcard
Termux: Edit configfile
adb shell: cp /sdcard/configfile back to com.xorg.kodi
That's not a very comfortable solution. Is there better way modify config files of installed applications?