Database Users

Full Root for Nook Glowlight

It took some doing, but after following the instructions in this link:
http://forum.xda-developers.com/showthread.php?t=2559915
I was finally able to root my Nook Glowlight. The instructions are kind of sprawled out and extremely unclear so I will sum up.
As always, you will need the ADB. In order to install the ADB, you need the Java Development Kit and the Android Studio (formerly known as the Android SDK)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
http://developer.android.com/sdk/installing/studio.html
How to obtain root via ADB: The ONLY way you can root is using Windows. I was successful on Windows 7 32 bit, but it may be possible on other versions.
step 1) install bootloader driver.
You need to grab the drivers from here (bnusbdrivers.zip):
http://forum.xda-developers.com/showpost.php?p=49665945&postcount=279&nocache=1&z=184593200683593
then, open the Device Manager (on Windows). Be ready to right click on the new device 'omap3660' that shows.
With the nook turned completely off, plug in a USB cable. you will have less than 3 seconds to right click the new omap3660 device that shows up in the system profiler.
If you were successful and you right clicked on it in time, manually install the Barnes & Noble USB driver (there are entries added to the generic Google drivers for both the TI Omap 3660 bootloader and the ADB device after you modify the uRamdisk later on)
***NOTE***
If you WEREN'T successful on your first try (took me THREE times to get to it in time), you aren't going to get another chance to install the drivers. At least not easily anyway, because after Windows tries to automatically install the drivers for the bootloader and fails, it will disregard the device any time it shows up after that. So, you are going to need to delete the registry entries that it created, which in my experience was easier said than done. Even admin access was not sufficient to make the necessary changes to the registry.
You will need to launch regedit.exe using another tool called psexec which is available here:
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
after you download the pstools package, copy those .exe files to C:\Windows\System32\ (in order to add them to $PATH in cmd.exe)
Then, once you've installed the pstools commands to C:\Windows\System32\, run cmd.exe as admin (right click it and select 'run as administrator') and then open regedit.exe with the following command
Code:
psexec -s -i -d regedit.exe
Then, once regedit is open you need to find the keys created by the Nook bootloader and delete them. The Nook bootloader's device ID is 0451:d00e
You are going to be looking in HKEY_LOCAL_MACHINE\Current Control Set\enum\usb\ for the keys with the bootloader's device IDs. There may also be keys generated in control set 001 and 002 as well. Delete all of those keys and then reboot your computer. Then with the nook power off completely, repeat the process from the first step. eventually you will be successful installing the bootloader driver.
Step 2) temporarily boot with uRamdisk-noogie
you need to download omaplink.exe from here:
http://www.temblast.com/android.htm
and you also need to download the four files which allow you to temporarily mount the boot partition; omap3_aboot.bin, u-boot-ng2-exp-v03.bin, uImage-ng2-130-stk and uRamdisk-noogie.
They are available here:
http://forum.xda-developers.com/showpost.php?p=49779966&postcount=285
download usbboot-ng2-images-noogie-v1.zip
The next part is easy.
Extract the .zip file and then fire up cmd.exe. cd into the directory of the newly extracted .zip
in the new working directory, enter the command
Code:
omaplink omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-stk uRamdisk-noogie
Then, with the Nook powered all the way off and omaplink running, plug it in and a few seconds later, after the device boots up all the way, you will be looking at the contents of the boot partition instead of the internal storage like normal.
Step 3) Edit uRamdisk
you will need to download bootutil.exe from here
http://www.temblast.com/android.htm
copy bootutil.exe to C:\Windows\System32
with the boot partition mounted, copy uRamdisk to your computer and extract the files init.rc and default.prop, eg;
Code:
bootutil /x /v uRamdisk init.rc default.prop
then using notepad++ (available here: http://notepad-plus-plus.org/) edit the files as follows
default.prop
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
and
init.rc
comment out lines 375 and 392-399
(do this by adding a # to the beginning of the line)
uncomment line 215
(do this by deleting the # at the beginning of the line)
save both files and then repack them into uRamdisk
Code:
bootutil /r /v uRamdisk init.rc default.prop
copy uRamdisk back onto the Nook, eject the disk and power off the device. Reboot and you should be able to connect to ADB via WiFi
eg;
Code:
adb connect 192.168.0.10
replacing '10' with whatever IP your Nook is grabbing from your router.
Step 4) Full Root
at this point, you have root access via ADB only. You will not have root access in any apps like Root Explorer, Terminal, TiBackup, etc.
In order to finish PROPERLY rooting your Nook, you need to install 'su' to /system/bin/ and install the superuser.apk
Code:
adb connect 192.168.0.10
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
reboot your device one more time and then you will be fully rooted.
*** Note ***
this devices firmware seems to be a strange hybrid between donut and eclair, although it purports itself to be Android 2.1. The Superuser.apk and su binary came from an old Cyanogenmod 4.6 build in case anyone was wondering (Android Donut). The ones from Cyanogenmod 5 (Android Eclair) do not work. you will get the 'install failed older sdk' error.

installing busybox
I tired installing busybox by using the stericson busybox pro.apk. It would always freeze at 6.47%.
I figured out that if I grabbed an older version of the busybox binary and pushed it to /system/xbin manually and then chmodded it to the proper permissions, auto updates and proper symlinking work using the busybox app
Code:
adb shell mount -o remount, rw /system
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
Then reboot, and run the busybox app to update and create symlinks.
enjoy!

installing nano and bash
Code:
adb connect 192.168.0.10
adb shell
mount -o remount, rw /system
adb push nano /system/xbin/
chmod 6755 /system/xbin/nano
adb push bash /system/xbin/
chmod 6755 /system/xbin/bash
bash
mv /system/bin/sh /system/bin/sh.bak
ln -s /system/xbin/bash /system/bin/sh
chmod 6755 /system/bin/sh
adb push profile /system/etc/
adb push terminfo /system/etc/
and then in terminal emulator under 'Preferences' change the initial command to
Code:
export TERMINFO=/system/etc/terminfo;export TERM=linux;export HOME=/sdcard;
and finally
Code:
adb push bashrc /sdcard
adb shell
mv /sdcard/bashrc /sdcard/.bashrc
exit
nano works just fine via ADB, but because of lack of 'ctrl' key (and physical buttons to assign it to) you won't be able to write files (ctrl+o) using the terminal on your nook. But between having full proper root access, busybox, a proper bash terminal emulator and nano for editing config files, this should REALLY extend the usefulness of your Nook Glowlight. It should work just fine on other versions of Nook too.

Hi N00b-un-2,
Many thanks for your summary!
There is one important edit that I think you missed,
in init.rc you also need to:
Line #375, comment out "disabled" with a # at the start of the line.
(see http://forum.xda-developers.com/showthread.php?p=49070213#post49070213)
without this I couldn't get adb to connect.
And since you already made it very noob friendly, might I suggested you clarify:
Line #215 remove # to enable adb over wifi
(rather than search for 5555)
Also, I'm not expert, but I believe the commands to get superuser on the device are (at least it worked for me):
adb connect 192.168.x.x
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
Finally, I'm not sure if this is important, but maybe remount system as read only again:
adb shell mount -o remount, ro /system
Thanks again, nice work!
---------- Post added at 01:48 PM ---------- Previous post was at 01:10 PM ----------
Hi again,
had similar issues with installing busybox, here's what worked for me (note needed to run su to create dir):
adb shell mount -o remount, rw /system
adb shell /system/bin/su
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
cheers.

As far as remounting /system as ro, I would HIGHLY recommend just rebooting at this point, otherwise your nook might be stuck in a weird pseudo-rooted state. Probably won't cause any problems, but why risk it?
Thanks for clarifying the line number. I will make the appropriate edits to my instructions. I was working off the top of my head and couldn't remember what exact line the ADB over TCP config was, as I just used ctrl+w '5555' to find it myself.
There are several pre-edited uRamdisk images floating around the forum with various features enabled which would be easier for noobs than extracting the config files and manually editing and then repacking them. In the future I'll probably throw those on here as well.
darz said:
Hi N00b-un-2,
Many thanks for your summary!
There is one important edit that I think you missed,
in init.rc you also need to:
Line #375, comment out "disabled" with a # at the start of the line.
(see http://forum.xda-developers.com/showthread.php?p=49070213#post49070213)
without this I couldn't get adb to connect.
And since you already made it very noob friendly, might I suggested you clarify:
Line #215 remove # to enable adb over wifi
(rather than search for 5555)
Also, I'm not expert, but I believe the commands to get superuser on the device are (at least it worked for me):
adb connect 192.168.x.x
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
Finally, I'm not sure if this is important, but maybe remount system as read only again:
adb shell mount -o remount, ro /system
Thanks again, nice work!
---------- Post added at 01:48 PM ---------- Previous post was at 01:10 PM ----------
Hi again,
had similar issues with installing busybox, here's what worked for me (note needed to run su to create dir):
adb shell mount -o remount, rw /system
adb shell /system/bin/su
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
cheers.
Click to expand...
Click to collapse

N00b-un-2 said:
There are several pre-edited uRamdisk images floating around the forum with various features enabled which would be easier for noobs than extracting the config files and manually editing and then repacking them. In the future I'll probably throw those on here as well.
Click to expand...
Click to collapse
Would have been good if I could have easily found a pre-edited image, but your instructions were a great alternative, thanks again

darz said:
Would have been good if I could have easily found a pre-edited image, but your instructions were a great alternative, thanks again
Click to expand...
Click to collapse
Sorry for the really noob question, I have rooted, wifi adb running and installed apps as per your instructions, but I can't seem to access any of it on the nook. How can I get access to the launcher I installed?
You mentioned pre-edited images, do any of those come with the apps I need to get access to a custom launcher?
Cheers,
Dariusz
==============
Updated: All sorted
==============
For some reason had some issues with ADW launcher, Launcher pro worked fine.
ps I think I made a mistake with the su step I suggested, if you run a one line shell command I don't think it keeps su privileges, so I believe you need to run commands within the shell as per below:
adb shell
mount -o remount, rw /system
/system/bin/su
mkdir -p /system/xbin
exit
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk

Noob
Hey guys any instructions noob friendly or a video in youtube,i stick up at dab connect 192.168.0.10.I dos't have a Windows PC and using Mac whit Parallels Desktop.Is it possible instructions for Mac?

The above instructions from N00b-un-2 should work fine running a vm with parallels on your Mac.
OB
Sent from my SPH-D710VMUB using Tapatalk 2

valentin1985 said:
Hey guys any instructions noob friendly or a video in youtube,i stick up at dab connect 192.168.0.10.I dos't have a Windows PC and using Mac whit Parallels Desktop.Is it possible instructions for Mac?
Click to expand...
Click to collapse
Before you perform the adb connect step you need to find out what your IP address is:
On your nook, click on the settings icon in the top right corner and then select "Change"
Under Wireless Networks, select the wifi name that you are already connected to (where it says "Connected to the internet")
This will display your connection details, remember that IP address
Now go back to your pc and type:
adb connect [IP address]

darz said:
Before you perform the adb connect step you need to find out what your IP address is:
On your nook, click on the settings icon in the top right corner and then select "Change"
Under Wireless Networks, select the wifi name that you are already connected to (where it says "Connected to the internet")
This will display your connection details, remember that IP address
Now go back to your pc and type:
adb connect [IP address]
Click to expand...
Click to collapse
BIG HINT! If you're using Powershell ISE, you have to type .\adb.exe connect [IP address] or else it won't recognize "adb" as an executable!
Don't ask why, because I don't know. :?

thenookieforlife3 said:
BIG HINT! If you're using Powershell ISE, you have to type .\adb.exe connect [IP address] or else it won't recognize "adb" as an executable!
Don't ask why, because I don't know. :?
Click to expand...
Click to collapse
So far so good,but now what?

valentin1985 said:
So far so good,but now what?
Click to expand...
Click to collapse
I just gave a little tip on Powershell ISE. I do not know much about the Nook GlowLight rooting process, as I have a NSTG, not a NG. Ask someone else.

thenookieforlife3 said:
I just gave a little tip on Powershell ISE. I do not know much about the Nook GlowLight rooting process, as I have a NSTG, not a NG. Ask someone else.
Click to expand...
Click to collapse
Yes,i try whit dis command .\adb.exe connect 192.168.0.9 but result is the same.

valentin1985 said:
Yes,i try whit dis command .\adb.exe connect 192.168.0.9 but result is the same.
Click to expand...
Click to collapse
But that's okay! What I said was, if you are using the command program Powershell ISE, do it that way instead. But you are just using cmd.exe, not Powershell ISE!
In cmd.exe, which is what you are using, it is not neccessary to type .\adb.exe. Just type adb.
From there, ask someone else in this thread.

thenookieforlife3 said:
But that's okay! What I said was, if you are using the command program Powershell ISE, do it that way instead. But you are just using cmd.exe, not Powershell ISE!
In cmd.exe, which is what you are using, it is not neccessary to type .\adb.exe. Just type adb.
From there, ask someone else in this thread.
Click to expand...
Click to collapse
I prefer to use ConEmu or Console2 when I am forced to use Windows. Not a big fan of CMD.EXE or Powershell/PowershellISE. there are plenty of other CLI alternatives out there

N00b-un-2 said:
I prefer to use ConEmu or Console2 when I am forced to use Windows. Not a big fan of CMD.EXE or Powershell/PowershellISE. there are plenty of other CLI alternatives out there
Click to expand...
Click to collapse
Well, as I ONLY use Windows and Powershell ISE has a nice-enough layout for my purposes, I use it. That's why I gave a tip on it.

Actually on a lot of installs just typing adb in the command console won't work either unless it's got the path variable set up correctly, I find it easiest to just right click and choose run as administrator, no need for the path to be setup.
OB
Sent from my SPH-D710VMUB using Tapatalk 2

FW 1.2.1
Hi guys,
thanks for creating this thread. I was wondering if this rooting procedure was tested with the firmware 1.2.1 ?

real-6 said:
Hi guys,
thanks for creating this thread. I was wondering if this rooting procedure was tested with the firmware 1.2.1 ?
Click to expand...
Click to collapse
This rooting procedure is for the new Nook GlowLight with firmware 1.3.1. Your device is a Nook Simple Touch with GlowLight, which can be rooted very easily using the rooting package here.

Install Debian Linux on the FireTV

Hey guys,
I was looking for a way to install some Linux applications on the FireTV. After trying out optware (which installs a package manager to android systems) with little success, I ended up installing a Debian Chroot on the external USB. The following is a list of apps which now run almost natively on the firetv:
- Transmission 2.82/couchpotato/sickbeard
- openssh
- nano
- x11 environment
- vnc server
- ftp server
I hope these instructions will be useful for some people. Your firetv needs to be rooted for this to work. The process is relatively quick and as easy as it can get. The tricky part is to let The Debian environment boot when the FireTV boots. Here we go:
1. First, get DebKit from Google Play
2. Sideload DebKit onto the FireTV and start it up
3. Grant DebKit Root Permissions
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Push the Menu Button on your FireTV remote and go to settings
5. Select the image Location. I created a folder called debian on the external USB device. The USB works natively through the new FireTV firmware.
6. For the image size I decided to make it 2GB. At first I had a 1GB image but I quickly ran out of space installing the x11 environment
7. Under Debian Distribution I would recommend installing Jessie since it gives you the latest Transmission version. With wheezy you get v 2.6 which does not let you choose folders through the web ui.
8. Go back to the main menu and choose "Install". Follow the onscreen instructions.
At this point you should have a working Debian installation on your FireTV.
9. The first thing we want to do is install openssh to create a login into the chroot. To log into your new Debian installation use
"adb connect 192.168.1.x" (firetv ip) and "adb shell"
10. Once you are logged into the firetv shell, execute "debkit mount" , then "debkit chroot".
11. Inside the chroot execute "apt-get update && apt-get install openssh". You will see a few error messages which are caused by the environment variables of the android shell. When using nano for example you'll notice that the enter key doesn't work. On a full size keyboard you can use the other enter key to confirm though.
12. Now try logging in to your debian chroot with ssh [email protected]" (firetv ip)
AUTOSTART
In order to autostart your debian chroot I created the following script.
1. Go to the android shell and remount /system in rw ( mount -o remount,rw /system )
2. Create or edit /system/etc/install-recovery-2.sh which will autostart (vi /system/etc/install-recovery-2.sh, then chmod 755 /system/etc/install-recovery-2.sh)
3. Here is my complete autostart script. I have all my media connected to my router which has a NFS server running:
Code:
#!/system/bin/sh
sleep 20
busybox mount -o remount,rw /
busybox mkdir -p /mnt/nfs.TV
busybox mkdir -p /mnt/nfs.Movies
busybox chmod 777 /mnt/nfs.TV
busybox chmod 777 /mnt/nfs.Movies
busybox remount,ro /
su --mount-master -c "busybox mount -o nolock,hard,intr,rw -t nfs 192.168.10.1:/mnt/TV /mnt/nfs.TV"
su --mount-master -c "busybox mount -o nolock,hard,intr,rw -t nfs 192.168.10.1:/mnt/Movies /mnt/nfs.Movies"
/data/data/com.mizusoft.debkit/files/debkit mount
sleep 5
busybox mount --bind /mnt/nfs.TV /data/data/com.mizusoft.debkit/files/mnt/mnt/TV
busybox mount --bind /mnt/nfs.Movies /data/data/com.mizusoft.debkit/files/mnt/mnt/Movies
busybox mount --bind /mnt/nfs.Movies/Music /sdcard/MPD/music
sleep 5
/data/data/com.mizusoft.debkit/files/bin/chroot /data/data/com.mizusoft.debkit/files/mnt/ /bin/bash -c "/home/ssh.sh"
4. I mount my nfs shares to the FireTV and then bind them inside the chroot.
5. Here are the contents of /home/ssh.sh which is a script to start the chroot ssh
Code:
/usr/sbin/sshd
sleep 10
/usr/bin/ssh [email protected] "/home/startup.sh"
6. and the contents of /home/startup.sh
Code:
/etc/init.d/transmission-daemon start
/etc/init.d/couchpotato start
/etc/init.d/cron start
7. What you end up with is a FireTV which runs Debian on the side. I've had this setup for the last two months and can say that so far the performance of Kodi does not seem to suffer of having the Debian Chroot running at the same time.
I hope this tutorial will be helpful for people who are looking for ways to extend the use of their FireTV.
Cheers,
Chris

mrchrister said:
Hey guys,
I was looking for a way to install some Linux applications on the FireTV. After trying out optware (which installs a package manager to android systems) with little success, I ended up installing a Debian Chroot on the external USB. The following is a list of apps which now run almost natively on the firetv:
- Transmission 2.82/couchpotato/sickbeard
- openssh
- nano
- x11 environment
- vnc server
- ftp server
I hope these instructions will be useful for some people. Your firetv needs to be rooted for this to work. The process is relatively quick and as easy as it can get. The tricky part is to let The Debian environment boot when the FireTV boots. Here we go:
1. First, get DebKit from Google Play
2. Sideload DebKit onto the FireTV and start it up
3. Grant DebKit Root Permissions
4. Push the Menu Button on your FireTV remote and go to settings
5. Select the image Location. I created a folder called debian on the external USB device. The USB works natively through the new FireTV firmware.
6. For the image size I decided to make it 2GB. At first I had a 1GB image but I quickly ran out of space installing the x11 environment
7. Under Debian Distribution I would recommend installing Jessie since it gives you the latest Transmission version. With wheezy you get v 2.6 which does not let you choose folders through the web ui.
8. Go back to the main menu and choose "Install". Follow the onscreen instructions.
At this point you should have a working Debian installation on your FireTV.
9. The first thing we want to do is install openssh to create a login into the chroot. To log into your new Debian installation use
"adb connect 192.168.1.x" (firetv ip) and "adb shell"
10. Once you are logged into the firetv shell, execute "debkit mount" , then "debkit chroot".
11. Inside the chroot execute "apt-get update && apt-get install openssh". You will see a few error messages which are caused by the environment variables of the android shell. When using nano for example you'll notice that the enter key doesn't work. On a full size keyboard you can use the other enter key to confirm though.
12. Now try logging in to your debian chroot with ssh [email protected]" (firetv ip)
AUTOSTART
In order to autostart your debian chroot I created the following script.
1. Go to the android shell and remount /system in rw ( mount -o remount,rw /system )
2. Create or edit /system/etc/install-recovery-2.sh which will autostart (vi /system/etc/install-recovery-2.sh, then chmod 755 /system/etc/install-recovery-2.sh)
3. Here is my complete autostart script. I have all my media connected to my router which has a NFS server running:
Code:
#!/system/bin/sh
sleep 20
busybox mount -o remount,rw /
busybox mkdir -p /mnt/nfs.TV
busybox mkdir -p /mnt/nfs.Movies
busybox chmod 777 /mnt/nfs.TV
busybox chmod 777 /mnt/nfs.Movies
busybox remount,ro /
su --mount-master -c "busybox mount -o nolock,hard,intr,rw -t nfs 192.168.10.1:/mnt/TV /mnt/nfs.TV"
su --mount-master -c "busybox mount -o nolock,hard,intr,rw -t nfs 192.168.10.1:/mnt/Movies /mnt/nfs.Movies"
/data/data/com.mizusoft.debkit/files/debkit mount
sleep 5
busybox mount --bind /mnt/nfs.TV /data/data/com.mizusoft.debkit/files/mnt/mnt/TV
busybox mount --bind /mnt/nfs.Movies /data/data/com.mizusoft.debkit/files/mnt/mnt/Movies
busybox mount --bind /mnt/nfs.Movies/Music /sdcard/MPD/music
sleep 5
/data/data/com.mizusoft.debkit/files/bin/chroot /data/data/com.mizusoft.debkit/files/mnt/ /bin/bash -c "/home/ssh.sh"
4. I mount my nfs shares to the FireTV and then bind them inside the chroot.
5. Here are the contents of /home/ssh.sh which is a script to start the chroot ssh
Code:
/usr/sbin/sshd
sleep 10
/usr/bin/ssh [email protected] "/home/startup.sh"
6. and the contents of /home/startup.sh
Code:
/etc/init.d/transmission-daemon start
/etc/init.d/couchpotato start
/etc/init.d/cron start
7. What you end up with is a FireTV which runs Debian on the side. I've had this setup for the last two months and can say that so far the performance of Kodi does not seem to suffer of having the Debian Chroot running at the same time.
I hope this tutorial will be helpful for people who are looking for ways to extend the use of their FireTV.
Cheers,
Chris
Click to expand...
Click to collapse
Definitely Cool! Are you strictly using it for the apps you've mentioned or have you found other uses? More screenshots would be awesome--video would be the best. But don't want you to go through too much trouble. I'm very curious to see how it runs in real time, but I'm not likely to have a chance to try it in the foreseeable future. Thanks a lot for sharing though!
BTW--whats the boot time like? It'd be nice to run sickbeard on it if I'm able to switch back and forth fire os/ debian.

Hey Klit,
when I have a bit more time on my hands I might add a video tutorial , it's definately a pretty straight forwarded process if you don't fear using the terminal. the debian environment is only accessible through a terminal so you cant switch between fire os and a debian window manager . The boot time is not affected by loading the debian chroot since the debian stuff loads after fire os is loaded. Sickbeard works great btw!

What mode is Debian running in and is it a visual UI desktop?
While I am here,I must ask,can someone attempt to get a full Linux running using Xserver for maximum performance and make some detailed instructions afterward,I couldn't figure it out myself.
I had a version of Linux running with a UI desktop and a few browsers that worked decent.
Though this done with a slower method and made visible using a VNC app.
It's been so long since I ran it,and I forgot how to start it,and haven't used it since.
It would be nice to have a full Linux OS running via Xserver at high performance,enough to run several cool things smoothly without the framedrops and jitters that VNC gets.

This tutorial is based on Debootstrap, so it installs Debian into a "subdirectory" of fire os. In this case it mounts a 2GB image from the external USB to the Firetv. When you ssh into this environment it will feel like a debian server and you can do most things you can do in debian. you can read more about this over here:
https://wiki.debian.org/Debootstrap
I have a vncserver running on the firetv with fluxbox as my window manager. it runs great but this is not a dual boot setup with debian coexisting on the firetv.

Thanks for the detailed instructions, OP! I wonder if this would work as a Terraria server... TShock is simply too much for the Raspberry Pi.

I would like to install Debian and remove fire OS completely. Does any one have instructions or a link? Thank you.

https://github.com/freedreno/freedreno/wiki/FireTV

Fire TV Stick?
Great work! I can't wait to get the time to try it out myself.
It sounds like you did this on the Fire TV installing Debian on an external USB drive. Did I get that correct? Can this be done on a Fire TV Stick which has no external USB option?
Also, it looks like both Debian and Android run simultaneously based on your comments, is that correct? Does anyone know if there is a way to set it so Android launches when HDMI is plugged in and Debian launches when HDMI is not plugged in and not both simultaneously?

Sharp Aquos Crystal 306sh ROOT ?

Hello brothers .
exuse me I have Sharp Aquos Crystal 306sh 4.4.2 version s4081
but how to root ? i try root but not work ....
thanks .

What software version is your sharp
Sent from my SPH-L720 using Tapatalk

i try but not find ........................you know or anyone help me
thanks

Settings about device
Sent from my SPH-L720 using Tapatalk

Thanks...i find it
After ..... .
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
Install instructions
- download latest supersu-install from here https://download.chainfire.eu/696/Su...etrieve_file=1
- download the attached "A3UL_4.4.2-wp_mod.zip"
- reboot to recovery (TWRP)
- Install Supersu-install.zip (a current supersu install is required as one of it's scripts will load the module)
- Install A3UL_4.4.2-wp_mod.zip
- Reboot
To test if the module is loaded you can open Terminal Emulator and type "lsmod" and wp_mod.ko should be in the list of loaded modules.
For a further test you can run the following in Terminal emulator.
su
mount -o remount rw /system
echo "this is a wp_mod test" > /system/wp_mod_test.txt
sync
reboot
Its good thanks for the Mr MiniBlu
The orginal post :::
http://forum.xda-developers.com/desire-610/development/mod-wpmod-disable-write-protection-t3149168
Sent from my 306SH using XDA-Developers mobile app

srmd said:
Thanks...i find it
After ..... .
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
Install instructions
- download latest supersu-install from here https://download.chainfire.eu/696/Su...etrieve_file=1
- download the attached "A3UL_4.4.2-wp_mod.zip"
- reboot to recovery (TWRP)
- Install Supersu-install.zip (a current supersu install is required as one of it's scripts will load the module)
- Install A3UL_4.4.2-wp_mod.zip
- Reboot
To test if the module is loaded you can open Terminal Emulator and type "lsmod" and wp_mod.ko should be in the list of loaded modules.
For a further test you can run the following in Terminal emulator.
su
mount -o remount rw /system
echo "this is a wp_mod test" > /system/wp_mod_test.txt
sync
reboot
Its good thanks for the Mr MiniBlu
The orginal post :::
http://forum.xda-developers.com/desire-610/development/mod-wpmod-disable-write-protection-t3149168
Sent from my 306SH using XDA-Developers mobile app
Click to expand...
Click to collapse
This doesn't work on the latest software (S7232) from what I recall from that thread.

How to root sharp zeta sh-01f? Please help me

How to root sharp 206 sh build 0022

Native OpenSSH and BASH for Android

Hi! In short this is for everybody who need openssh server and bash. Fill free to enjoy this port
How to use:
1. install zip trought recovery
2. boot into android, do remount system partition rw
3. setup password trought terminall emulator using command "passwd"
4. do remount system partition ro
5. generate ssh keys trought terminal emulator using command "ssh-keygen -A"
6. start sshd trought terminal emulator using command "/system/bin/sshd"
Username for things is sshd, password is one which you set.
Forget adb shell and enjoy openssh!

Ticwatch 2 watchfaces for Ticwatch E/S

I've owned a Ticwatch 2 for about a year, and it was a great watch, but I decided to get an Android Wear watch, so I sold the Ticwatch 2 and bought a Ticwatch E Ice. I love the Ticwatch E, and I love Android Wear 2.0, but there are a few things I miss about the Ticwatch 2. I really liked most of the watch faces from Mobvoi that were available for the Ticwatch 2, and I was disappointed to see that only about 3 of those cool watch faces came with the Ticwatch E.
I have collected about 100 of the Ticwatch 2 watch faces and posted them here. You can install the watch faces on your Ticwatch E/S via ADB over wifi with a PC. I believe they would work on just about any Android Wear smartwatch.
Here is the link.
https://drive.google.com/open?id=1ifoZpsLFpCUZl1Vbo67avl4NsMpJzsKk
(I hope this isn't breaking any rules.)
EDIT: See post #9

please allow drive folder access.

Here is the updated link
https://drive.google.com/open?id=1ekIGahdY3hblziaW4y1bgf0ngz_aIgk7
Enjoy these awesome watch faces

ThankYou!!

easily install all these watchfaces
Copy and paste all these lines in a text file, change the name from .txt to .bat and then after connecting the watch with adb launch the file .bat
adb install -r "0dyssey_1.0.apk"
adb install -r "adhd Watch face_1.0.apk"
adb install -r "All-Round Flower_1.0.apk"
adb install -r "App Error_1.0.apk"
adb install -r "Armor_1.0.apk"
adb install -r "Aurora_1.0.apk"
adb install -r "auspiciouscloud_1.0.apk"
adb install -r "Black Eye_1.0.apk"
adb install -r "Black Gent_1.0.apk"
adb install -r "Black Steel_1.0.apk"
adb install -r "Blank_1.0.apk"
adb install -r "Blue Eye_1.0.apk"
adb install -r "Blue Light_1.1.apk"
adb install -r "Bohemia_1.0.apk"
adb install -r "Broken Screen_1.0.apk"
adb install -r "Business Time_1.0.apk"
adb install -r "Campus_1.0.apk"
adb install -r "Champagne Gold_1.0.apk"
adb install -r "ChrisTicmas_1.0.apk"
adb install -r "Classic Machine_1.0.apk"
adb install -r "Classic White_1.0.apk"
adb install -r "Coffee_0.apk"
adb install -r "Colorful Pedometer_1.1.apk"
adb install -r "Colorful_1.0.apk"
adb install -r "Cube_1.0.apk"
adb install -r "Dark Knight_1.0.apk"
adb install -r "Dawn_1.0.apk"
adb install -r "Digital Pro_1.0.apk"
adb install -r "Digital_1.0.apk"
adb install -r "Division_1.0.apk"
adb install -r "electric line_1.0.apk"
adb install -r "Electronic TimeZone_1.0.apk"
adb install -r "ElegantGold_1.0.apk"
adb install -r "Elegant_1.0.apk"
adb install -r "Elegent_1.0.apk"
adb install -r "Equation_1.1.apk"
adb install -r "Fashion_1.1.apk"
adb install -r "Film_1.0.apk"
adb install -r "Fish_1.0.apk"
adb install -r "Fluorescence_1.0.apk"
adb install -r "Flyer_1.1.apk"
adb install -r "Forged Gold Time_1.1.apk"
adb install -r "Forged Steel_1.0.apk"
adb install -r "Gem_1.0.apk"
adb install -r "Halloween Skull_1.0.apk"
adb install -r "Hot_1.0.apk"
adb install -r "Intelligent Drive_1.0.apk"
adb install -r "iron sodier_1.1.apk"
adb install -r "Iron Will_1.0.apk"
adb install -r "kingofglory_1.1.apk"
adb install -r "Leader_1.0.apk"
adb install -r "Legs_1.0.apk"
adb install -r "Light Planet_1.0.apk"
adb install -r "Light Shadow_1.0.apk"
adb install -r "Lion dance_1.0.apk"
adb install -r "Lucky New Year_1.1.apk"
adb install -r "Machinery _ Electronics_1.1.apk"
adb install -r "Magic Shadow_1.0.apk"
adb install -r "ManyChickens_1.2.apk"
adb install -r "Mechanical_1.0.apk"
adb install -r "Meteor_1.0.apk"
adb install -r "Mithril_1.0.apk"
adb install -r "Modern Classics_1.0.apk"
adb install -r "Move Fit_2.2.apk"
adb install -r "Music Band_1.5.apk"
adb install -r "Mutual affinity_1.0.apk"
adb install -r "Naturally_1.0.apk"
adb install -r "Neon dive_1.0.apk"
adb install -r "New Year Calligraphy_1.2.apk"
adb install -r "Nightlight_1.0.apk"
adb install -r "Orange Light_1.3.apk"
adb install -r "Paper Folding_1.0.apk"
adb install -r "Paradox_1.0.apk"
adb install -r "Pearl_1.0.apk"
adb install -r "Playboy_1.0.apk"
adb install -r "primetime_1.0.apk"
adb install -r "Quadrel_1.0.apk"
adb install -r "Rabbit_1.0.apk"
adb install -r "Retro Wave_1.2.apk"
adb install -r "Rome_1.0.apk"
adb install -r "Silent_1.0.apk"
adb install -r "Silver_1.0.apk"
adb install -r "Snowflakes_1.0.apk"
adb install -r "source.properties
adb install -r "Space Man_1.0.apk"
adb install -r "Speed_1.0.apk"
adb install -r "Spring Blessing_1.0.apk"
adb install -r "Starry Sky_1.0.apk"
adb install -r "Starry_1.0.apk"
adb install -r "StarWar_1.5.apk"
adb install -r "Star_1.0.apk"
adb install -r "Steel Moon_1.0.apk"
adb install -r "Style_1.2.apk"
adb install -r "suntooblack_1.0.apk"
adb install -r "Super Mario_1.0.apk"
adb install -r "systrace
adb install -r "Tank Battle_1.0.apk"
adb install -r "The Lantern Festival_1.0.apk"
adb install -r "Time Shuttle_1.1.apk"
adb install -r "Transit_1.0.apk"
adb install -r "Tree Planting_1.0.apk"
adb install -r "Twinkle_1.0.apk"
adb install -r "Walker_1.0.apk"

O **** god, it worked on amazfit pace, only stand by not working but i think its can be ported.

Thanks for the wonderful faces.
Flyer, Bluelight and Mechanical are my favorite as they show most info we need on the face.
There is a ghost rider face that I am looking for...any way to extract that apk?
Also are there any where subeye is customizable

anangphatak said:
Thanks for the wonderful faces.
Flyer, Bluelight and Mechanical are my favorite as they show most info we need on the face.
There is a ghost rider face that I am looking for...any way to extract that apk?
Also are there any where subeye is customizable
Click to expand...
Click to collapse
I don't have my TW2 anymore.

Here is the new new link:
https://drive.google.com/open?id=1RsTJzc0l10QUnP52oCtO0_xQ1XNQL0Wn
I was inspired by fsamoggia's good idea and I included a batch file and a linux script in the folder. Find the file named windows_faces.bat or linux_faces. I am new to writing scripts, but I think they will work. Let me know if they work properly, anyone. I also renamed the apk files to make them easier to deal with.

Thanks a lot @zillo:)
Super easy installation thank you @fsamoggia
Much nicer watch faces than any of the 3rd party apps. Much appreciated!

Help
I'm trying to figure out how to install these watchfaces into my Ticwatch S. Any assistance here would be appreciated.
thanks

The Real KC said:
I'm trying to figure out how to install these watchfaces into my Ticwatch S. Any assistance here would be appreciated.
thanks
Click to expand...
Click to collapse
You have to use ADB. Install ADB on your PC. Open a terminal. Connect your watch to your PC with ADB over wifi. Type the command
Code:
adb connect xxx.xxx.x.xx:5555
. Put your watch's IP instead of the x's. The commands to install the faces are in the script. There is a linux script (linux_faces) and a windows script (windows_faces.bat) in the folder with the faces. Download the faces/script files to your PC. Put them in a folder on your PC. make sure the script file is in the same folder as the faces. In terminal, cd to the folder with the faces. Run the script. If using Linux, make the file executable with the command
Code:
chmod +x /path/to/scriptfile
. Then execute it with the command
Code:
./linux_faces
. If using Windows, just double click on the .bat file, you might have to right click on it and "run as Administrator." Just make sure that in the terminal, you are in the directory with all of the files. There's about 100 faces, so it will take a while to install. I believe it should work. Let me know if it worked for you please.

Thanks
zillo:) said:
You have to use ADB. Install ADB on your PC. Open a terminal. Connect your watch to your PC with ADB over wifi. Type the command
Code:
adb connect xxx.xxx.x.xx:5555
. Put your watch's IP instead of the x's. The commands to install the faces are in the script. There is a linux script (linux_faces) and a windows script (windows_faces.bat) in the folder with the faces. Download the faces/script files to your PC. Put them in a folder on your PC. make sure the script file is in the same folder as the faces. In terminal, cd to the folder with the faces. Run the script. If using Linux, make the file executable with the command
Code:
chmod +x /path/to/scriptfile
. Then execute it with the command
Code:
./linux_faces
. If using Windows, just double click on the .bat file, you might have to right click on it and "run as Administrator." Just make sure that in the terminal, you are in the directory with all of the files. There's about 100 faces, so it will take a while to install. I believe it should work. Let me know if it worked for you please.
Click to expand...
Click to collapse
I appreciate your prompt response!! Unfortunately, that is a much more complex process than I am able to accomplish.

Hi, will these watchfaces work for Ticwatch S2 too? Please advise. Thanks.

I don't see why not. I think it will work on any Wear OS watch.

i try on ticwatch pro.
thx
some works fine
others looks like resolution are not right

Just tried it on my Ticwatch C2. The resolution is off, like it's magnified. Doesn't work.

Do these watch faces require ticsystem enabled? If not, can you recommend any other mods/3rd party apps, etc once I disable ticsystem? Any roms that compete with battery life with or without ticsystem running on them? Apologies if this is a general mobvoi thread and you dont have the watch. Noob here with a stock ticwatch e.
cheers

svntsvn said:
Do these watch faces require ticsystem enabled? If not, can you recommend any other mods/3rd party apps, etc once I disable ticsystem? Any roms that compete with battery life with or without ticsystem running on them? Apologies if this is a general mobvoi thread and you dont have the watch. Noob here with a stock ticwatch e.
cheers
Click to expand...
Click to collapse
I haven't tried disabling Ticsystem on my watch. I'm not sure if it has anything to do with it. The Ticwatch 2 watch faces worked on my Ticwatch E but not on my Ticwatch C2. A user said that it didn't work on the Ticwatch Pro, so it seems that it just won't work on newer Ticwatches. I haven't really tried to find a solution. As for ROMs, I've only used stock ROMs on my watches, so I can't comment on that. Too bad Mobvoi doesn't just make all their nice watch faces available for download on any watch.

I glanced over an article last night about them dropping a bunch a bunch of faces from their stable of watches on the play store. That's probably gone or else I'm sure you would have come across it by now.
Try the disable, I'm just a day in but it's supposed to help a bit. Certainly don't miss mobvoi bloat. Cheers