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
Related
Ok so i followed the instructions to root my D3 twice and i have gotten the proper results, after the second reboot when i adb to my device i am given the root prompt.
That is about it though. I have installed superuser, tried to install jrummy16 busybox installer so i could get titanium working, but neither of the apps can find superuser or get root access.
Any ideas. Sorry for not putting this in the OG Thread but figured that would get real big real quick, thought it might be easier to start a separate thread for issues with the exploit.
need to find and push the su binary to the phone first. Superuser won't work without it.
Alright i got it working.
Anyone know of a good resource for how to kill all of the bloatware?
Is it safe to use titianium to remove the VZ apps, as in uninstall not just freeze
Titanium backup
Sent from my DROID3 using Tapatalk
at this point, i've just been freezing things. I'm waiting till we get a better list of what we can safely remove without breaking things.
Feels good man!
{
"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"
}
lordgodgeneral said:
need to find and push the su binary to the phone first. Superuser won't work without it.
Click to expand...
Click to collapse
Can anyone add this stuff to the guide? I know most of the stuff is logical for some of you, but I've never rooted a device or used android. (edit: and planning on getting a droid 3 soon)
Also how to delete bloatware and install/use ADB
DoubleYouPee said:
Can anyone add this stuff to the guide? I know most of the stuff is logical for some of you, but I've never rooted a device or used android.
Also how to delete stuff and install/use ADB
Click to expand...
Click to collapse
Here's exactly how I did it... all steps stolen from the thread in the developers forum:
1) Make sure you've installed the android-sdk from Google on your computer. (http://developer.android.com/sdk/index.html)
2) Connect phone to computer. In terminal or a dos prompt, navigate to the directory where you installed the sdk and where adb is located.
(example location)
and type the following:
Code:
adb shell
mv /data/local/12m /data/local/12m.bak
ln -s /data /data/local/12m
3) Power off and power back on your Droid 3.
4) Drop back to shell/prompt and back to adb location. Type the following commands:
Code:
adb shell
rm /data/local/12m
mv /data/local/12m.bak /data/local/12m
mv /data/local.prop /data/local.prop.bak
echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
5) Restart the phone again. You now have root.
6) Get a copy of su (http://www.megaupload.com/?d=82FH3AGI) and extract it to the same directory as adb on your computer. Type the following:
Code:
adb remount
adb push su /system/bin
adb shell chmod 6755 /system/bin/su
7) Install superuser from the android market.
Done!
Thanks! And then you delete apps with superuser?
I'm having trouble with:
Code:
adb push su /system/bin
It keeps returning:
Code:
cannot stat 'su' : No such file or directory
I have su (from the above link) in the same directory as adb...
*EDIT*
I have root within adb. So I definitely did everything before this right.
Did you extract su from the zip and put in the same directory as adb?
Yep.
10char
similar problem here. adb shell recognizes me as [email protected]_solana so im assuming its rooted..but when i try "adb remount" and press enter it says adb not found. i extracted the su file to my adb directory. Any ideas?
If you get an error like I did (top of 2nd page), try this:
Code:
C:\AndroidSDK\platform-tools\adb push C:\AndroidSDK\platform-tools\su \system\bin\su
That worked for me.
I hope this is helpful to any one that is having a hard time.
I found a one touch root video like 5 mins ago on youtube.
This is not my viedo all credits go to thedriodpeople the ones that made the video.
http://www.youtube.com/watch?v=RpGcuhoUp0k
k finally got the remount to succeed...now its say "chmod 6755: not found" after i enter "adb shell chmod 6755 /system/bin/su"
nevermind, simply retyped the same command and seemed to work on the third try mysteriously. working now
Hosed up my contacts after root and un-install --Help please--
---Solved---
So, I pulled a noob move and uninstalled a number of apps using titanium backup without understanding the repercussions of each. After uninstalling a few at a time, I would reboot my device and everything seemed fine. Little did I know, after uninstalling most, if not all, of the bloat I am unable to click a contact's picture to bring up the submenu and select call or text or whatever.
I didn't write down a list of items that I uninstalled and I should have frozen the apps prior to uninstall. I'm not a complete idiot and stayed away from obvious apps that shouldn't be uninstalled and what I thought was ALL motroblur stuff.
Long story short, I get a "com.motorola.contacts" stopped unexpectedly error(force close prompt) after trying to view a contact. I can look through all of the dialer menus showing contacts and recent calls and whatnot but I can't view a specific contact in detail. The searching I've done seems like there are a number of apps that use com.motorola.contacts and I believe I still have all of them installed but apparently not since there isn't a ton of detail on the latest motoblur that the D3 runs.
Does anyone have an idea of what apps use this process on the D3?
Thanks.
EDIT Javier78 ended up providing a solution to this issue.
http://forum.xda-developers.com/showpost.php?p=16998796&postcount=5
Quick fix and I was on my way again.
I dont think we know what all uses that process.
Sounds like your are going to have to do a factory restore, give it sometime eventually we will have a list of what is safe to remove and what isnt
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?
The SoupKit
{
"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"
}
What is SoupKit? At it's heart, SoupKit is for those who are tired of messing around with Windows and are ready to do try something that works. It was created to be "sort of" modular in that after the ADB installer has been installed, other Linux scripts can be installed and run from the command line by just typing the name of the script and without worrying about changing directories or dealing with permissions. It's intended to make the transition from Windows to Linux for Android a little bit easier.
How does it work?
The SoupKit ADB Installer --- FOR ALL KINDLE FIRES
This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself, all while taking a fraction of the space needed for the Android SDK. What this means for you is, you will be able open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or certain operators that are confusing to command line newbies ( ./ ). You can enter commands just as you see them in tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android.
What you need:
First, you need Linux. Don't worry, it's not as bad as you may think.
Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot).
Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.
I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).
You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.
If you're using a LiveUSB, there is no root/sudo password, just hit enter.
Do not use a USB 3.0 port
Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.
Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder.
SoupKit has been tested extensively on all the latest versions of Ubuntu and Mint, but it hasn't really been tested on anything outside of that. Try other distros if you will, but be warned.
To install:
Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.
Credits:
Don't worry. I didn't forget about you guys. I'll finish this when I have time. In the meantime, you know who you are, and thank you.
Is that all?
NOPE. What SoupKit would be complete without a little something to go with it? SEE POST #2
Due to recent updates, I've decided to remove the option to install Hashcode's 2nd bootloader. There are too many areas where things can go wrong so I think it would be best to let the user follow the small handful of instructions in the 2nd bootloader thread to get it done. IMO, it is not worth the risk to rely on the user to make sure a downgraded stock bootloader is installed before running the script. Plus I think using a script toinstall the downgraded bootloader gives users a false sense of safety in what is potentially very dangerous to do.
ROOT PLUS for 2nd Generation Kindle Fires
That's right. This works for ALL 2nd generation Kindle Fires.
What does it do?
The screenshot above should answer that question pretty quickly.
What do you need to know?
Since Hashcode's bootloader hack is device specific, you must download the version for your device. Each one has the exact same script but the stack, boot and recovery images are different for each particular device. You must have the SoupKit installed for this to work properly. It installs in the same way as the SoupKit; unzip, double click, run in terminal, blah blah.
Make sure you have ADB enabled under “Security” in the settings.
Anything else?
At any point after installation, if you need to run the utility again, just type "rootplus" in the terminal.
What's next?
I have a few more things in store for you guys and they will all be made for the SoupKit. As packages are installed, just type the name of the package in any terminal to launch them at any point (hence "modular"). Everything will be easy to install, easy to launch, and new user friendly.
Don't be skerrd. Move out of your comfort zone a little and give Linux and SoupKit a try. I'm sure you won't be disappointed.
Credits:
* Bin4ry - of course, for providing the root exploit
* Dees_Troy - for Team Win Recovery
* prokennexusa and his team - for testing this out on all of the second generation devices
* Thepooch - for extensive testing and always being there to lend a hand
Downloads:
SoupKit - http://d-h.st/PbX
RootPlus for all Kindle Fires - http://d-h.st/jOe
Changelog:
04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons. There is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon.
03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error
03-16-2013 - Bugfix: (RootPlus)
* Fixed issue with permissions on the rootplus script
03-10-2013 - Update: (RootPlus)
* Added extra safety measures, including MD5 check on 2nd bootloader install
02-23-2013 - Initial release
I actually wish I needed this because god damn this is a sexy piece of kit.
Thanks soup
Sent from my Amazon Kindle Fire2 using xda app-developers app
Awesome. So glad to see the kf1 devs working for us over here!
I'll probably never need this, but there are MANY who will find this useful.
Thanks soupmagnet!
--
Sent from my Kindle Fire 2, CM 10.1
Wilkinsss said:
this is a sexy piece of kit.
Click to expand...
Click to collapse
Oh, I see what you did there...
soupmagnet said:
Oh, I see what you did there...
Click to expand...
Click to collapse
Well I don't need it I have adb and fastboot running fine on linux already but I still downloaded it anyways, just because I can.
Update 3-10-2013: Added extra safety measures, including MD5 check on 2nd bootloader install
I seem to have installed the soupkit correctly, I followed the instructions. I also installed the root plus in the same manner, but when it installs it just disappears. When I type rootplus in terminal it tells me "permission denied"
It also gives me command not found when I try to open soupkit.sh
thanks
2strokenut said:
I seem to have installed the soupkit correctly, I followed the instructions. I also installed the root plus in the same manner, but when it installs it just disappears. When I type rootplus in terminal it tells me "permission denied"
It also gives me command not found when I try to open soupkit.sh
thanks
Click to expand...
Click to collapse
That sucks...I'll have to fix that. In the meantime you can enter the following in terminal to fix the permissions:
Code:
sudo chmod a+x ~/bin/SoupKit/files/rootplus
Then you should be able to start it by entering "rootplus" in the terminal with no problem.
Sorry for the inconvenience.
[Edit:] There have quite a few downloads since the last update. Has anyone else had this problem?
soupmagnet said:
That sucks...I'll have to fix that. In the meantime you can enter the following in terminal to fix the permissions:
Code:
sudo chmod a+x ~/bin/SoupKit/files/rootplus
Then you should be able to start it by entering "rootplus" in the terminal with no problem.
Sorry for the inconvenience.
[Edit:] There have quite a few downloads since the last update. Has anyone else had this problem?
Click to expand...
Click to collapse
That worked like a charm! Thanks for all you do!
---------- Post added at 02:35 PM ---------- Previous post was at 02:11 PM ----------
I hate to be such a noob, but, I got the thing rooted and now trying to install the bootloader and TWRP, this is as far as I have gotten. Hasn't done anything in about 10 minutes. I've toggled ADB.
Verifying MD5 Checksum...
blaze-stack.img: OK
Checksum matched
Installing stack...
95 KB/s (4096 bytes in 0.041s)
0+1 records in
0+1 records out
4096 bytes transferred in 0.002 secs (2048000 bytes/sec)
Rebooting...
< waiting for device >
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
I exited the terminal and re-ran option 6, this is what it gives me now:
blaze-stack.img: OK
Checksum matched
Installing stack...
93 KB/s (4096 bytes in 0.042s)
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
failed on '/system/etc/install-recovery.sh' - No such file or directory
Rebooting...
< waiting for device >
There may be something off with the timing. In original testing on my KFHD 8.9, that was caused from the script entering the command to reboot too fast. I had the script pause for a second or two before rebooting which seemed to help (or I thought I did). I'll look into it a little further to see if I can make it work better. The error you get on the second time you run the script is because the first time you ran it, that file was renamed so it wouldn't exist the second time around.
[Edit:] Just hold the power button to shut down and then reboot while the script is sitting at "waiting for device"
Hi Soup,
I installed soupkit, I installed rootplus. The terminal just disappears but I assume it installed correctly. What I am trying to figure out is this:
Make sure you have ADB enabled under “Security” in the settings.
I am running Ubuntu Precise. I don't see anything under Settings about Security or about enabling ADB. Can you help me out a bit? Thaks!
[Edit] I had to: sudo chmod a+x ~/bin/SoupKit/files/rootplus too to get a terminal window on rootplus. But it doesn't do anything when I press 1.
[Edit again] Nevermind... was stupid to think that the Security change was in Ubuntu, I found it on the KF.
empoy78th said:
Hi Soup,
I installed soupkit, I installed rootplus. The terminal just disappears but I assume it installed correctly. What I am trying to figure out is this:
Make sure you have ADB enabled under “Security” in the settings.
I am running Ubuntu Precise. I don't see anything under Settings about Security or about enabling ADB. Can you help me out a bit? Thaks!
[Edit] I had to: sudo chmod a+x ~/bin/SoupKit/files/rootplus too to get a terminal window on rootplus. But it doesn't do anything when I press 1.
[Edit again] Nevermind... was stupid to think that the Security change was in Ubuntu, I found it on the KF.
Click to expand...
Click to collapse
Yeah, sorry about that...I'm working to get the permissions fixed now so I can upload a new working version. Barring distractions (yeah right), I should have a new one up within the hour. If nothing else, it will be fixed by the end of the day.
soupmagnet said:
Yeah, sorry about that...I'm working to get the permissions fixed now so I can upload a new working version. Barring distractions (yeah right), I should have a new one up within the hour. If nothing else, it will be fixed by the end of the day.
Click to expand...
Click to collapse
Thanks soup! Just to give you an update (although I think you are working on this already), when I press 1 on root plus, I end up on <waiting for device> although the KF2's finished rebooting. I tried the previous suggestion about holding down the power button and re-launching rootplus, but it didn't resolve it.
I will gladly test your new version. Thanks again!
---------- Post added at 11:39 AM ---------- Previous post was at 11:22 AM ----------
empoy78th said:
Thanks soup! Just to give you an update (although I think you are working on this already), when I press 1 on root plus, I end up on <waiting for device> although the KF2's finished rebooting. I tried the previous suggestion about holding down the power button and re-launching rootplus, but it didn't resolve it.
I will gladly test your new version. Thanks again!
Click to expand...
Click to collapse
Another question if I may:
When you have shell updates, does it use the same folder on the same partition? I am not quite good at Linux yet, so cleaning up previous installations is not my strength at all. Thanks!
empoy78th said:
Another question if I may:
When you have shell updates, does it use the same folder on the same partition? I am not quite good at Linux yet, so cleaning up previous installations is not my strength at all. Thanks!
Click to expand...
Click to collapse
Assuming I understand you correctly,
I write the install script in such a way that updating to a newer version simply replaces what already exists, so there's no need to uninstall anything.
3-16-2013: Fixed issue with permissions on the rootplus script
soupmagnet said:
Assuming I understand you correctly,
I write the install script in such a way that updating to a newer version simply replaces what already exists, so there's no need to uninstall anything.
Click to expand...
Click to collapse
You understood it. Good to know. Thanks!
soupmagnet said:
3-16-2013: Fixed issue with permissions on the rootplus script
Click to expand...
Click to collapse
Do I download both soupkit and rootplus for updates? Sorry for the noob question.
In rootplus, options 1 and 5 worked for me. However, on option 6, I stay at <waiting for device>. Done it twice and also held the power button to no avail.
Like in description
Navibar 3 -5 -7 buttons mod - android 5.0
air3g, air 2
If you have my rom Lolipop ( mirek190 ) just plug USB and choose proper option.
On other rom make sure you have root and USB debugging on.
3 buttons navigation bar
{
"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"
}
5 buttons navigation bar
7 buttons navigation bar
air 3g
https://drive.google.com/open?id=0B8BF9-TGlz-FY2tWZUVZa05FU00
air 2
https://drive.google.com/open?id=0B8BF9-TGlz-FTEhvUTl2clE3Z3M
Ps - NOT RUN IT AS ADMINISTRATOR !
Hi mirek.
Can you add systemui.apk with a clock in its original position with 3 buttons?
Nope - center clock stays in the center like buttons
delete
Great job Mirek!
Hi, can you do this for the Air III? Do you need the stock SystemUI.apk?
EDIT:
I found this post www[dot]tsochen[dot]com/blog/post/15 and nearly the same intructions works for Air III M5C5. But the status_bar_*xml fix as not needed. This is the diff of navigation_bar.xml for 3 buttons
gist[dot]github[dot]com/kazuoteramoto/c0730bb27d0fb8dc6332
The system cannot find the path specified
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Wow, thanks, teramoto--this is fantastic! I just modded the SystemUI.apk on my device based on the tsochen link you provided, and your diff. I didn't want the screenshot and volume +/- buttons, but I did want to keep the menu button. So I just modded as indicated, and left the @id/menu entries untouched. The result is a nicely centered, four button variant.
EDIT: Somebody requested that I post my modded SystemUI.apk for a 4-button nav bar for the Air 3/III 32GB (M5C5). At the link below, I have done this, but also included 3- and 5-button versions, as well as the original 7-button SystemUI.apk version from the M5C5 v1.04 stock rom. The various SystemUI.apk files are obviously named by an explicit filename extension as you'll see when you download the archive. Also, let me reiterate--these are specifically for an Air 3/III 32GB (M5C5) tablet. Make sure that file ownership/permission is set correctly on installation else you will run into errors with the UI, and you will have to go in via adb root for manual fixing. Finally, and most importantly, note that credit for this goes to teramoto and the tsochen blog posting he pointed out above, which I just followed to do this, and also to mirek190 for starting this thread, and for helping out so many X98 Air users. Here's the link:
https://mega.nz/#!Hw0jRKBJ!0omuxVQXFHjzdbMV1bg6yvBhtMT570-gBhnkKxw2A4o
irfaan92 said:
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Click to expand...
Click to collapse
Facing the same problem...
irfaan92 said:
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Click to expand...
Click to collapse
Have you installed drivers ?
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
irfaan92 said:
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
Click to expand...
Click to collapse
I did the same as you for whole day....thanks anyway.
irfaan92 said:
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
Click to expand...
Click to collapse
Thanks for a clue - 1st post updated .
verbage said:
Make sure that file ownership/permission is set correctly on installation else you will run into errors with the UI, and you will have to go in via adb root for manual fixing.
Click to expand...
Click to collapse
Someone asked for some more details about how to "go in via adb root for manual fixing". The question did not provide a lot of details except that the person copied over the file, renamed it, and then the navbar disappeared. So I am assuming that the SystemUI.apk file is correctly named and in the right place on the filesystem, but there is an issue of file ownership/permissions that needs to be fixed manually. If you are in that situation, or the UI is in an endless FC loop because of the same issue, here is what to do.
First, you'll need a working adb (Android Debug Bridge) install. If you don't have one already, the simplest thing to do is to just use the core adb files that mirek190 provides in either one of his ~2MB button mod archives linked at the start of this thread. In particular, I am talking about the "data" directory that has the five exe/dll files. Anyway, extract that, and then open a DOS command window in that directory. To quickly open up a command window, shift-right click on a blank part of the Explorer window, and choose the "Open command window here" option.
Now plug in your tablet, and give the following six commands in the command window you opened:
adb root [this initializes adb in root mode]
adb shell [this spawns an actual adb shell so you'll see the command prompt change]
mount -o rw,remount /system [this makes the /system partition writeable so you can make changes]
cd /system/priv-app/SystemUI [this changes to the right directory to avoid loooonnnngggg command lines]
chown root.root SystemUI.apk && chmod 644 SystemUI.apk [this manually specifies the correct file ownership and permissions]
exit [this gets you back out of the adb shell]
Note again that the above six commands are what is needed if the issue is just one of file ownership and permissions, and the modded SystemUI.apk is already correctly named and in the right spot. It is also the barebones version of a manual fix--before you give any commands, you might want to do some exploration to make sure my assumptions in the previous sentence are correct... For example, if your SystemUI.apk file is incorrectly named, you'll have to fix that first (i.e. "mv INCORRECTLYNAMEDFILE SystemUI.apk"). And before exiting out of the adb shell, you might want to restart the UI on the tablet just to make sure things are working correctly in case you need more triage via adb.
Hope this helps!
verbage said:
Someone asked for some more details about how to "go in via adb root for manual fixing". The question did not provide a lot of details except that the person copied over the file, renamed it, and then the navbar disappeared. So I am assuming that the SystemUI.apk file is correctly named and in the right place on the filesystem, but there is an issue of file ownership/permissions that needs to be fixed manually. If you are in that situation, or the UI is in an endless FC loop because of the same issue, here is what to do.
First, you'll need a working adb (Android Debug Bridge) install. If you don't have one already, the simplest thing to do is to just use the core adb files that mirek190 provides in either one of his ~2MB button mod archives linked at the start of this thread. In particular, I am talking about the "data" directory that has the five exe/dll files. Anyway, extract that, and then open a DOS command window in that directory. To quickly open up a command window, shift-right click on a blank part of the Explorer window, and choose the "Open command window here" option.
Now plug in your tablet, and give the following six commands in the command window you opened:
adb root [this initializes adb in root mode]
adb shell [this spawns an actual adb shell so you'll see the command prompt change]
mount -o rw,remount /system [this makes the /system partition writeable so you can make changes]
cd /system/priv-app/SystemUI [this changes to the right directory to avoid loooonnnngggg command lines]
chown root.root SystemUI.apk && chmod 644 SystemUI.apk [this manually specifies the correct file ownership and permissions]
exit [this gets you back out of the adb shell]
Note again that the above six commands are what is needed if the issue is just one of file ownership and permissions, and the modded SystemUI.apk is already correctly named and in the right spot. It is also the barebones version of a manual fix--before you give any commands, you might want to do some exploration to make sure my assumptions in the previous sentence are correct... For example, if your SystemUI.apk file is incorrectly named, you'll have to fix that first (i.e. "mv INCORRECTLYNAMEDFILE SystemUI.apk"). And before exiting out of the adb shell, you might want to restart the UI on the tablet just to make sure things are working correctly in case you need more triage via adb.
Hope this helps!
Click to expand...
Click to collapse
Hi. first let me thank you for your effort.
I tried your solution but I'm still without the buttons and notification bar.
Code:
D:\@SUPPORT\TECLAST_X98\x98air3g-buttons-mod\data>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
D:\@SUPPORT\TECLAST_X98\x98air3g-buttons-mod\data>adb shell
[email protected]_m5c5:/ # mount -o rw,remount /system
mount -o rw,remount /system
[email protected]_m5c5:/ # cd /system/priv-app/SystemUI
cd /system/priv-app/SystemUI
[email protected]_m5c5:/system/priv-app/SystemUI # ls
ls
SystemUI.apk
x86
[email protected]_m5c5:/system/priv-app/SystemUI # ls -l SystemUI.apk
ls -l SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-13 01:11 SystemUI.apk
[email protected]_m5c5:/system/priv-app/SystemUI # chown root.root SystemUI.apk && chmod 644 SystemUI.apk
chown root.root SystemUI.apk && chmod 644 SystemUI.apk
<
[email protected]_m5c5:/system/priv-app/SystemUI # ls -l SystemUI.apk
ls -l SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-13 01:11 SystemUI.apk
[email protected]_m5c5:/system/priv-app/SystemUI #
Am I doing something wrong? Any other idea? Or can I put the original file back?
Thanks for any help with this
EDIT: I forgot to mention that I'm using now the sikke1's GoogleNow custom rom. That might be the reason?
wepecko said:
I tried your solution but I'm still without the buttons and notification bar...Am I doing something wrong? Any other idea? Or can I put the original file back?...EDIT: I forgot to mention that I'm using now the sikke1's GoogleNow custom rom. That might be the reason?
Click to expand...
Click to collapse
Hmmm, from your ls -l command, it appears that the file ownership and permission were already set correctly, and so there was no need to give the chown/chmod commands again, but doing so didn't hurt, and only confirmed things.
My M5C5 is also on sikke1's rom--I started with mirek190's v6.1 slim version for the Air 2/II even though I have an Air 3/III, and it worked pretty good except for some hiccups. And so that is why I ended up on sikke1's debloated M5C5 rom, too.
Have you rebooted? You may be nervous to do so, understandably, but adb is enabled by default in the sikke1 rom so even if the graphical UI does not pop up, you can still do manual triage via adb.
---------- Post added at 07:19 PM ---------- Previous post was at 06:53 PM ----------
One thought for the future--if you are going to do this manually, you should stage it appropriately to hopefully avoid issues. For example, copy the original to a backup with the -p option to preserve file properties while still leaving the in-use original completely intact (i.e. "cp -p SystemUI.apk SystemUI.apk.ORIGINAL)". Then copy your modded apk file(s) into the same directory, and make sure file ownership/permissions are set as per above. Then do another cp -p to replace the in-use original with the modded apk.
Here's my listing for the directory to show you what I mean. I have the original apk plus the 3-, 4-, and 5-button modded apks all in the same directory with the correct ownership/permissions set. I can quickly change to any config, for example, the 3-button config, with a single cp -p command, i.e. "cp -p SystemUI.apk.MODDED-3-BUTTON SystemUI.apk". And there is no downtime/hiccup because one file is immediately replaced by the other, and the ownership/permissions are already correctly set.
Code:
[email protected]_m5c5:/system/priv-app/SystemUI # ls -la
ls -la
-rw-r--r-- root root 3572761 2015-12-31 00:54 SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-03 16:43 SystemUI.apk.MODDED-3-BUTTON
-rw-r--r-- root root 3572761 2015-12-31 00:54 SystemUI.apk.MODDED-4-BUTTON
-rw-r--r-- root root 3572764 2016-01-03 16:43 SystemUI.apk.MODDED-5-BUTTON
-rw-r--r-- root root 3604448 2015-12-31 00:21 SystemUI.apk.ORIGINAL
drwxr-xr-x root root 2015-08-26 23:06 x86
[email protected]_m5c5:/system/priv-app/SystemUI #
Again, since you have confirmed everything, I would suggest rebooting if you have not done that. As I said, even if the graphical UI does not come up, you can still get into adb for repairs. At the very worst, you might have to reflash the rom.
I'm not sure why you have had hiccups, but these modded apks are directly from the stock SystemUI.apk of a v1.04 M5C5 rom. I have the modded navigation_bar.xml files, and I can send those or just diffs vs. the original so you can see the few lines that I changed. But you'll see they are just like described by teramoto and the tsochen blog he pointed out.
Thanks verbage. I understand your backup procedure and admit it was a mistake to rewrite the file directly.
However im still trying to find solution to this. I did restart ofcourse, several times, but it didnt help at all. It was late yesterday so i didn't have much time to try different scenarios. Anyway tonight im going to try to update the file with 4 and 5 buttons versions and will see if I'll have any luck.
One more idea: would it be possible that the reason of this not working is that it might be in conflict with xposed apk already installed?
Sent from my XT890 using Tapatalk
wepecko said:
Anyway tonight im going to try to update the file with 4 and 5 buttons versions and will see if I'll have any luck... One more idea: would it be possible that the reason of this not working is that it might be in conflict with xposed apk already installed?Sent from my XT890 using Tapatalk
Click to expand...
Click to collapse
Hmmm, sorry to hear you are still having a problem. The 3-, 4-, and 5-button versions all work perfectly on my Air 3/III using sikke1's debloated M5C5 rom, and since you have the same device, any of the versions should also work for you.
Certainly, the 7-button stock original should work, too, and that is also included in the archive I posted.
Whether there may be a conflict with the xposed framework you have installed, I don't know as I do not have xposed installed on my Air 3/III.
Anyway, good luck with fix, and we'll wait to hear more.
I tried again from the start and everything is working perfect now. Tested succesfully all versions of SystemUI file.
I have no explanation on the troubles during the first try though. I did everything the same way as yesterday.
:victory:
wepecko said:
I tried again from the start and everything is working perfect now. Tested succesfully all versions of SystemUI file.
I have no explanation on the troubles during the first try though. I did everything the same way as yesterday.
:victory:
Click to expand...
Click to collapse
Great, glad to hear you have it working!
Please, propose a task which does:
- unfreeze set of apps and
- switch ON location (or other) service.
And also:
- freeze apps,
- switch OFF location etc service.
It's needed for phone power efficiency, Google services switched on only when an app needing it is launched (and vice versa).
HELIUM, LOCKED bootloader, [ROM][UNOFFICIAL][7.1.2][HYDROGEN/HELIUM]LineageOS 14.1 r.06-24-2017 by*nijel8
Wait, how do you have a custom ROM on a device with a locked bootloader?
I use the following to freeze a list of apps:
create a run shell command, with root:
cat "/storage/emulated/0/disable-apps.txt" | while read d; do tmp=$(echo $d | awk {'print $1'}); adb shell "su -c 'pm disable $tmp'"; done
the text file just includes apps in full name, such as net.dinglisch.android.taskern,1 name per line
for location, run this shell command with root:
settings put secure location_providers_allowed +gps,network
@alienyd thanx a lot, it looks like the key engine are Linux shell commands for Android. And how do you know of them, is there any "man" for Android shell commands (like: settings put secure location_providers_allowed +gps,network) to look through oneself?
Vagelis1608 said:
Wait, how do you have a custom ROM on a device with a locked bootloader?
Click to expand...
Click to collapse
Yes, it is possible in this phone model: Xiaomi MiMax (Qualcomm Snapdragon chipset)
HELIUM, LOCKED bootloader, [ROM][UNOFFICIAL][7.1.2][HYDROGEN/HELIUM]LineageOS 14.1 r.06-24-2017 by*nijel8
hmm somehow my reply wasn't posted...
anyways, just search for useful tasker shell commands, I saw some threads in here about that. You can also list out all system variables and their values, which is imo priceless for automating tasks!
Yes, but found many examples from most are just typical Linux system commands, like:
Code:
mount -o remount,rw /system
mount -o remount,ro /system
mv /original/path /new/path
cp /original/path /new/path
etc.
And where are purely Android commands list, like:
Code:
pm disable
settings put secure location_providers_allowed +gps,network
?
And they are Android commands, not Tasker's, right?
HELIUM, LOCKED bootloader, [ROM][UNOFFICIAL][7.1.2][HYDROGEN/HELIUM]LineageOS 14.1 r.07-08-2017 by*nijel8
ioy said:
Yes, but found many examples from most are just typical Linux system commands, like:
etc.
And where are purely Android commands, like:
?
And they are Android commands, not Tasker's, right?
HELIUM, LOCKED bootloader, [ROM][UNOFFICIAL][7.1.2][HYDROGEN/HELIUM]LineageOS 14.1 r.07-08-2017 by*nijel8
Click to expand...
Click to collapse
They are Linux commands, but since android is based on Linux it has them.
Tasker can run them without an issue using the Run Shell action (some commands require you to tick the use root box).
Yes, but these commands could be run also from e.g. terminal emulator or scripts without Tasker installed at all, right? In this meaning questioned: if they are Tasker independent and belong to Android itself?
And please, do you know commands to set particular screen orientation: portrait or landscape?
HELIUM, LOCKED bootloader, [ROM][UNOFFICIAL][7.1.2][HYDROGEN/HELIUM]LineageOS 14.1 r.07-08-2017 by*nijel8
ioy said:
Yes, but these commands could be run also from e.g. terminal emulator or scripts without Tasker installed at all, right? In this meaning questioned: if they are Tasker independent and belong to Android itself?
And please, do you know commands to set particular screen orientation: portrait or landscape?
Click to expand...
Click to collapse
Yes, the "commands" you listed are within the OS of android, not integral to Tasker. The example mount command is basic to any Linux kernel. The settings "commands" are really a list of configuration settings that the OS refers to and are android (and device) specific. The are 3 groups of configuration settings: system, global and secure. You can see what your device has by opening a terminal and entering:
settings list system > /sdcard/system-values.txt
That command will list all of the entries in the system configuration and their current values. The output will be put into a file named system-values.txt on the root of your sdcard.
For example, whether the screen is permitted to rotate when the accelerometer senses device rotation is controlled by the value in:
system settings > value user_rotation
For an overview of these configuration settings, please see Best run shell commands in Tasker
Using the "secure" configuration values is the way to replace the defunct "secure settings" plugin using tasker's built in scripting ability.
As far as commands to set screen orientation, IMHO, it's just easier to use Rotation Locker. It integrates with tasker.
ktmom said:
settings list system > /sdcard/system-values.txt
That command will list all of the entries in the system configuration and their current values.
Click to expand...
Click to collapse
Is it possible controlling the whole phone with just these settings variables, i.e. will just commands
Code:
settings get secure/global/system name_of_the_setting
settings put secure/global/system name_of_the_setting 0 or 1
suffice?
ktmom said:
For an overview of these configuration settings, please see Best run shell commands in Tasker
Click to expand...
Click to collapse
I've already read it but thank you very much! (And there're still several doubts)
ktmom said:
As far as commands to set screen orientation, IMHO, it's just easier to use Rotation Locker. It integrates with tasker.
Click to expand...
Click to collapse
Easier, why? Plain text commands are elegant and minimalistic, if Tasker can fire them it is nice to avoid installation of any further third party application. And the whole my question was about it, for any particular task in Tasker you can always find some application which could perform it (without Tasker). And the rationale is to replace them all with one Tasker, agree?
Please, answer the question: which text console command can switch screen orientation: Portrait or Landscape (can't see relevant variable)
ioy said:
Is it possible controlling the whole phone with just these settings variables, i.e. will just commands
Code:
settings get secure/global/system name_of_the_setting
settings put secure/global/system name_of_the_setting 0 or 1
suffice?
Click to expand...
Click to collapse
No, it's a big part, but, for example, forcing an app that is programmed to not rotate ever, into rotating is more than defining settings.
Easier, why? Plain text commands are elegant and minimalistic, if Tasker can fire them it is nice to avoid installation of any further third party application. And the whole my question was about it, for any particular task in Tasker you can always find some application which could perform it (without Tasker). And the rationale is to replace them all with one Tasker, agree?
Click to expand...
Click to collapse
No, not agreed. The point of tasker is to bring the ability to script custom actions to the programming knowledgeable community. Tasker enables people familiar with the concept of if/then/else or variable arrays, ect to derive results based on triggers WITHOUT having to be experts in the deepest layers of the android system.
Plugins bring to the user access to actions not included in tasker. If every possible combination of options was built into tasker, the app would be enormous. It's also unnecessary for the average user who is looking to pop up a particular keyboard automatically when an specific app is launched. Or to turn gps on/off only when using navigating apps....ect.
Please, answer the question: which text console command can switch screen orientation: Portrait or Landscape (can't see relevant variable)
Click to expand...
Click to collapse
The user rotation variable I used in an example earlier. Which is the same as using tasker's built in Display AutoRotate. Other than "because I can", I can't imagine why using the built in action would not be preferred.
The trick is there more that goes into whether or not an app will be forced to rotate. The individual app's display layer does things like looks at the screen dpi and the app's layout and I don't know what and determines how and when to rotate if the user authorizes the screen to rotate in the first place. This can all be over ridden if you are sufficiently knowledgeable in the programming of android apps. But then, why the heck would anyone introduce the overhead of a framework like tasker.
I encourage you to look for android app development tutorials to enhance your understanding in the depth you are looking for. But also understand that you are pushing the use case of the tasker app.
Automagic offers such an option.
{
"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"
}
It's disappointing Tasker needs some plugin to do this simple thing. If I need plugin then why tasker, there are many other applications controlling screen orientation!
ivy.lally said:
Automagic offers such an option.
It's disappointing Tasker needs some plugin to do this simple thing. If I need plugin then why tasker, there are many other applications controlling screen orientation!
Click to expand...
Click to collapse
If you want to use a different app for everything, be my guest.
Tasker has a built-in action for autorotation.
An this only switches AutoRotation ON/OFF, what is actually needed is screen orientation settings: to switch AutoRotation OFF and then to set fixed screen orientation of choice.
HELIUM, LOCKED bootloader, [ROM][UNOFFICIAL][7.1.2][HYDROGEN/HELIUM]LineageOS 14.1
alienyd said:
I use the following to freeze a list of apps:
create a run shell command, with root:
cat "/storage/emulated/0/disable-apps.txt" | while read d; do tmp=$(echo $d | awk {'print $1'}); adb shell "su -c 'pm disable $tmp'"; done
the text file just includes apps in full name, such as net.dinglisch.android.taskern,1 name per line
for location, run this shell command with root:
settings put secure location_providers_allowed +gps,network
Click to expand...
Click to collapse
Hello!
I know this is a while ago that You posted this, I hope anyway that You answers me!? I want to freeze a App (Sony-Smart-Connect) automatically with Tasker, and in searching for a how to, I have seen Your post here! Can You Please say me, where exactly in the shell command I must put the full App-Name, and where can I find the full App-Package-Name of a installed App!? My Device is rooted, and I have a root-file-explorer with access to all folders! Please Help me!:highfive:
Thanks in advance!
RoseL.
roselanguste said:
Hello!
I know this is a while ago that You posted this, I hope anyway that You answers me!? I want to freeze a App (Sony-Smart-Connect) automatically with Tasker, and in searching for a how to, I have seen Your post here! Can You Please say me, where exactly in the shell command I must put the full App-Name, and where can I find the full App-Package-Name of a installed App!? My Device is rooted, and I have a root-file-explorer with access to all folders! Please Help me!:highfive:
Thanks in advance!
RoseL.
Click to expand...
Click to collapse
I think your app package name is: com.sonyericsson.extras.liveware
I don't use that app but going to apkmirror.com and searching for it gave me the package. Depending on version, settings -> apps and finding the app might have the package name listed. It no longer does on my oreo ROM.
The operative explanation in the post you quoted is:
the text file just includes apps in full name, such as net.dinglisch.android.taskern,1 name per line
Click to expand...
Click to collapse
The text file is what is called in the run shell command:
run shell command, with root:
cat "/storage/emulated/0/disable-apps.txt" | while read d; do tmp=$(echo $d | awk {'print $1'}); adb shell "su -c 'pm disable $tmp'"; done
Click to expand...
Click to collapse
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I think your app package name is: com.sonyericsson.extras.liveware
I don't use that app but going to apkmirror.com and searching for it gave me the package. Depending on version, settings -> apps and finding the app might have the package name listed. It no longer does on my oreo ROM.
The operative explanation in the post you quoted is:
The text file is what is called in the run shell command:
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Thanks! I have found a other way! - I have downloaded the Secure-Settings-Tasker-Plugin, and it has the ability to Freeze, Kill Apps, and it worked in the moment! But I learn a new thing from Your answer!
Thanks!
fyi the core command is
shell su -c pm disable (app-full-name)
You should be able to manually freeze apps with it. My post was meant for batch freezing with a file list. As this is a native shell command, you don't need any extra plugin for the job.
alienyd said:
I use the following to freeze a list of apps:
create a run shell command, with root:
cat "/storage/emulated/0/disable-apps.txt" | while read d; do tmp=$(echo $d | awk {'print $1'}); adb shell "su -c 'pm disable $tmp'"; done
the text file just includes apps in full name, such as net.dinglisch.android.taskern,1 name per line
for location, run this shell command with root:
settings put secure location_providers_allowed +gps,network
Click to expand...
Click to collapse
For some reason this doesn't seem to work for me.
I have pasted the error log below:
15.45.19/E Run Shell: ->
15.45.19/E Run Shell: ->
15.45.19/E Run Shell: ->
15.45.19/Shell runBackground cat "/storage/emulated/0/disable-apps.txt" | while read d; do tmp=$(echo $d | awk {'print $1'}); adb shell "su -c 'pm disable $tmp'"; done root: true timeout: -1
15.45.19/Shell start process-thread ID 803
15.45.19/E add wait type Shell1 time 2147483647
15.45.19/E add wait type Shell1 done
15.45.19/E add wait task
15.45.21/E Error: 1
Edit: I tried the command in Termux and the following error came up:No devices/emulators found.