Related
I'm looking to replace the launcher.apk in the /system/app folder. I know i could just download a replacement launcher from the market and use that but whenever i do that my phone seems to slow down considerably.
So what i'm hoping is that somebody can tell me the adb commands to use to remove the Launcher.apk from the system/app folder and replace it with my choice of launcher? If you know how please reply with the exact commands. Telling me to use adb uninstall will not help seeing as how i've already tried and it didn't work
Please do not tell me to go read adb for dummies or an adb command guide cause i have tried to use these and the commands i type in never work.
Please do not tell me to use the search button as i have and noone seems to have asked this question yet.
If it's not possible just say so.
you may be able to do this through terminal too.
ive not found a tutorial on this specific application but it can be done.
Try this
1. su (allows root permission)
2. mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system (make the system folder writeable)
3. cat /system/app/.apk > /sdcard/launcherbackup.apk (backs up system launcher)
4. cat /sdcard/(launcher name).apk > /system/app/launcher.apk (copies launcher to system)
5. enjoy
**PLEASE NOTE**
I am not responsible for if this fails. i have yet to try it myself as i find no need. the code was taken from another tutorial but so far has yet to fail to work for me on other aspects
**PLEASE NOTE**
Well theres 2 types of home replacements.
1. Who allow themselves to replace stock launcher
2. Who dont allow and have to be used as stand-alone
Regardless ur cleanest method would be :
adb remount
adb shell rm /system/app/Launcher.apk
adb uninstall com.android.launcher
adb shell rm /data/dalvik-cache/*Launcher*
adb shell rm /cache/dalvik-cache/*Launcher*
Now just place ur favorite launcher in ur /system/app folder.
adb remount
adb push <drag apk here> /system/app/
Now just reboot ur phone
traumatism said:
you may be able to do this through terminal too.
ive not found a tutorial on this specific application but it can be done.
Try this
1. su (allows root permission)
2. mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system (make the system folder writeable)
3. cat /system/app/.apk > /sdcard/launcherbackup.apk (backs up system launcher)
4. cat /sdcard/(launcher name).apk > /system/app/launcher.apk (copies launcher to system)
5. enjoy
**PLEASE NOTE**
I am not responsible for if this fails. i have yet to try it myself as i find no need. the code was taken from another tutorial but so far has yet to fail to work for me on other aspects
**PLEASE NOTE**
Click to expand...
Click to collapse
I did this for my hero and it works, thanks man
thanks a lot
traumatism said:
you may be able to do this through terminal too.
ive not found a tutorial on this specific application but it can be done.
Try this
1. su (allows root permission)
2. mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system (make the system folder writeable)
3. cat /system/app/.apk > /sdcard/launcherbackup.apk (backs up system launcher)
4. cat /sdcard/(launcher name).apk > /system/app/launcher.apk (copies launcher to system)
5. enjoy
**PLEASE NOTE**
I am not responsible for if this fails. i have yet to try it myself as i find no need. the code was taken from another tutorial but so far has yet to fail to work for me on other aspects
**PLEASE NOTE**
Click to expand...
Click to collapse
can i replace stock by any other launcher by this method???
You can use Link2sd app to convert an app (launcher from market) to system app, then reboot your device and then disable stock launcher in settings or freeze it with link2sd.
I still find having stock launcher there, in case something is wrong with an update, very useful, so I wouldn't even freeze the stock launcher.
Edit: obviously, root required, but its not like you didn't know that from the beginning.
Sent from my Nexus 7 using xda app-developers app
Daneshm90 said:
Well theres 2 types of home replacements.
1. Who allow themselves to replace stock launcher
2. Who dont allow and have to be used as stand-alone
Regardless ur cleanest method would be :
adb remount
adb shell rm /system/app/Launcher.apk
adb uninstall com.android.launcher
adb shell rm /data/dalvik-cache/*Launcher*
adb shell rm /cache/dalvik-cache/*Launcher*
Now just place ur favorite launcher in ur /system/app folder.
adb remount
adb push <drag apk here> /system/app/
Now just reboot ur phone
Click to expand...
Click to collapse
Wow I replaced my stock by holo launcher!!! Working fine
Thaknk you
bkrill said:
I'm looking to replace the launcher.apk in the /system/app folder. I know i could just download a replacement launcher from the market and use that but whenever i do that my phone seems to slow down considerably.
So what i'm hoping is that somebody can tell me the adb commands to use to remove the Launcher.apk from the system/app folder and replace it with my choice of launcher? If you know how please reply with the exact commands. Telling me to use adb uninstall will not help seeing as how i've already tried and it didn't work
Please do not tell me to go read adb for dummies or an adb command guide cause i have tried to use these and the commands i type in never work.
Please do not tell me to use the search button as i have and noone seems to have asked this question yet.
If it's not possible just say so.
Click to expand...
Click to collapse
The best n easiest way wud b usin a root browser.
Firstly root ur mob n download a file manager that can browse root folder such as root explorer.
Copy the launcher.apk file from ur sd card n paste it to system/app folder aftr activating r/w setting n set permissions to rw-r-r.
N then move the stocklauncher.apk to ur sd card.
For samsung gb mobs stock launcher is touchwiz30launcher.apk
Try to do tings in simple ways.
Sent from my GT-S5302 using xda app-developers app
Whatsapp problems
Hey guys,
The 4.4 KitKat Rom is working just fine. But I ran into some problems with Whatsapp. I successfully validated my phone number and restored my old messages. Now the problem is that Whatsapp won't recognize my contact numbers? When I press on the "New Conversation" button my friendlist should appear but it doesn't. Then I tried refreshing the list by pressing on menu and refresh. Then he tells me "Please try again later".
Has anybody got the same issues? Or any ideas?
Thanks
Ochs said:
Hey guys,
The 4.4 KitKat Rom is working just fine. But I ran into some problems with Whatsapp. I successfully validated my phone number and restored my old messages. Now the problem is that Whatsapp won't recognize my contact numbers? When I press on the "New Conversation" button my friendlist should appear but it doesn't. Then I tried refreshing the list by pressing on menu and refresh. Then he tells me "Please try again later".
Has anybody got the same issues? Or any ideas?
Thanks
Click to expand...
Click to collapse
theres no issue if change stock launcher only i think
bkrill said:
I'm looking to replace the launcher.apk in the /system/app folder. I know i could just download a replacement launcher from the market and use that but whenever i do that my phone seems to slow down considerably.
So what i'm hoping is that somebody can tell me the adb commands to use to remove the Launcher.apk from the system/app folder and replace it with my choice of launcher? If you know how please reply with the exact commands. Telling me to use adb uninstall will not help seeing as how i've already tried and it didn't work
Please do not tell me to go read adb for dummies or an adb command guide cause i have tried to use these and the commands i type in never work.
Please do not tell me to use the search button as i have and noone seems to have asked this question yet.
If it's not possible just say so.
Click to expand...
Click to collapse
Another suggestion guys.......note: dont ever uninstall the previous launcher yet...this result a crash...just do this first...your phone should be rooted try Link2SD app from playstore just scroll down and move app to phone and then the upper right corner you'll see the menu then convert to system app...and upper left corner then reboot....100% is working.....by arowenayih
I looked around the net for a feasable solution but nobody seemed to give me a practical solution. So I decided to experiment and came up with an unbelivable solution that takes literally 20-30 seconds per app and is FULLY automated.
My problem was as follows. I like to install new ROMs by wiping, flashing and reinstalling my apps. The problem with that is when you have 130 apps and Astro file manager seems to install 3-5 then quits back to the packages screen, it becomes extremely friken agrivating and simply hell-as annoying!
So I needed a way to install all my previously backed up apps (which Astro does a BEAUTIFUL job with) from my SD card to my phone all in one go, without prompts and without any input.
To do this its simple, just write your own batch script and run adb install.
You will need:
1. Android SDK (your version, ie. 2.2, 2.1, 1.6 ect.)
Code:
youtube.com/watch?v=A1SOSXwkc_8
2. USB Cable to PC
3. Enable "USB Debugging" on phone
**Prefer doing a fresh install of latest ROM, no third party apps and dont open Android Market if you have Froyo because it will try and download all your previously downloaded apps again. Cool but not cool here.**
Now, I assume you already have the APK bunch on your SD card, like I had.
I use Astro File Manager to backup all my apks to my /sd/backup/apps (which is automatically set).
Once you have all your APKs in one directory, I suggest putting them on you C:\. For example "c:\apps" for ease of scripting.
Step 1.
Open command prompt (CMD) and change directory to your "c:\apps"
Example:
Code:
cd..
cd..
cd apps
Now you should see your path set as "C:\apps" in CMD.
Step 2.
Create directory print.
In CMD "C:\apps" run:
Code:
dir /s /b > print.txt
This will print all directory files and extensions but nothing else, like size and attributes into your "C:\apps" folder. Now you will see a "print.txt" file in your "c:\apps" folder. If you open it, you will see a list of all your APKs.
Step 3.
Assuming you are using Notepad to view your "print.txt" file, press "CTRL+H". This will open the Find and Replace dialog box.
In Find type
Code:
C:\
In replace type
Code:
adb install -r c:\
Hit enter and it will modify all the APKs with the adb install command. Save and close notepad.
Step 4.
Now you need to rename that .txt extension in your "c:\apps\print.txt" to "print.bat". You need to have extension shown in windows. Google that if you dont know how to do that.
Once saved as a .bat file, simply execute and it will run through the sequence to install all your APK files without any prompts on your phone. Voila, and enjoy.
EXAMPLE:"c:\apps\print.bat"
Code:
adb install -r c:\apps\com.twitter.android-1.apk
adb install -r c:\apps\com.ups.mobile.android-2.apk
adb install -r c:\apps\com.vavni.android.battleship-1.apk
adb install -r c:\apps\com.viclabs.myRemote-2.apk
adb install -r c:\apps\com.waterflea.wifiscan-1.apk
adb install -r c:\apps\com.wyse.pocketcloud-1.apk
adb install -r c:\apps\com.xrath.jmsn-2.apk
adb install -r c:\apps\com.xtralogic.android.rdpclient-1.apk
adb install -r c:\apps\com.xtremelabs.android.speedtest-1.apk
adb install -r c:\apps\com.yahoo.mobile.client.android.im-1.apk
adb install -r c:\apps\com.yahoo.mobile.client.android.mail-2.apk
adb install -r c:\apps\com.yahoo.mobile.client.android.search-1.apk
adb install -r c:\apps\hongbo.bluescreen-1.apk
adb install -r c:\apps\info.marlan.sim-1.apk
adb install -r c:\apps\koushikdutta.telnet-1.apk
adb install -r c:\apps\kr.mobilesoft.yxplayer-2.apk
adb install -r c:\apps\net.mafro.android.wakeonlan-1.apk
adb install -r c:\apps\nl.rogro.GScript-1.apk
adb install -r c:\apps\org.ajeje.fakelocation-1.apk
adb install -r c:\apps\org.ale.abtc-1.apk
adb install -r c:\apps\org.android7.aviplayer-1.apk
adb install -r c:\apps\org.connectbot-1.apk
adb install -r c:\apps\org.gmote.client.android-1.apk
adb install -r c:\apps\org.iii.ro.meridian-1.apk
adb install -r c:\apps\org.kman.WifiManager-1.apk
adb install -r c:\apps\org.openobjectives.serverassistant-1.apk
adb install -r c:\apps\org.prowl.networkmapper-1.apk
adb install -r c:\apps\org.transdroid-1.apk
This will go in sequence and show "success" when finished installing. It will then run the next command in sequence until its done.
** I tried to write this thread as a help to those trying to do the same thing I was trying to do. This is in no way meant to validate anything and is meant merely as a resource to anybody. If your going to be an ass, shove it, if you like it, im happy I could help.**
Wow, that certainly is an interesting solution. Personally I just push everything to data/app when in recovery, wipe dalvik-cache, then reboot, always works fine.
An even easier solution:
http://forum.xda-developers.com/showthread.php?t=716806
Thanks man! this helpes me out with multiple installs on the SDK's VM.
hello,
i know i am off topic but i dont find only this thread with the app i am searching.
i search for the "ups mobile" app and the market on my desire (froyo 2.2) found this app not. (Sorry for my english) The app is free, no warez!
Can anyone send my the app or an link with the app ?
many thanks and sorry for off topic.
peter
Check this out...
http://forum.xda-developers.com/showthread.php?t=740545
All the work are already done :0)
Thanks for the advice. However, I have about 50 apks to backup and Astro is unable to backup like 15 of them. IE Crystallight Defense. It just says it's unable to do it and I don't know why. Thanks for any help.
awesome, simple yet effective ... just restored 103 apps
thanks
this is simplest method yet...
copy .apk to any folder in sdcard, mine "marketapp"
then type these following commands below:
=====================================
adb shell
su
cd /sdcard/marketapp
for app in *.apk; do pm install -r $app; done
=====================================
regards,
d4rkcell
Install apk
Hello Fellow Androids!
If this is off topic, please accept my apologies. I am searching through all of XDA for a simple solution to adding apk. Now before you start bashing, please keep in mind that I am well aware of the "search" options + google + XDA etc.
Long story short, I have:
1) Rooted
2) Fashed many Roms (currently on Stock 2.1)
3) Lag Fixxed (see signature)
4) Removed Bloatware
5) I am familiar with ABD and commands
Problem:
All I'm trying to do is install certain "apk"s using ADB. I am well aware of the Program that installs/ pushes apps automatically that are found in G1 + Vibrant + HTC + Droid Forums without having to do any typin......BUT.....I would like to know my way around ABD <----Main reason why i dont want the easy way out.
I have been here:
http://forum.xda-developers.com/showthread.php?t=716806
as well as here:
http://forum.xda-developers.com/showthread.php?t=743457
even been here:
http://forum.xda-developers.com/showthread.php?t=740545
I know what you are thinking, why not use them? As i said before, i would like to be efficient with ADB. So...
I have tried methods found here:
http://forum.xda-developers.com/showthread.php?t=517874
As well as:
http://forum.xda-developers.com/showthread.php?t=532719
The problem I am having is:
Whether i navigate to my folder (desktop with all my apps) and use either
"adb push app /system/sd/app
adb push app-private /system/sd/app-private"
or simply
"adb install <path to file> - Example: adb install c:/apps/apps2sd.apk"
I always get the error: "cant find <whatever apk> to install"
No matter which directory i have it, i get that message.
Note:
1) I have debugging on
2) I mounted sd <----also tried Without mounting
3) I have used the same command when I removed bloatware but i understand Adding apks are slightly different.
4) I have all the drivers installed + Microsoft's .net framework + etc
What am i doing wrong?
All Critics, input, education bashing (just not hating) lol are welcome. Thanks!
dannycurtean said:
**Prefer doing a fresh install of latest ROM, no third party apps and dont open Android Market if you have Froyo because it will try and download all your previously downloaded apps again. Cool but not cool here.**
Click to expand...
Click to collapse
Very nice, thanks.
Is there any way to make installed APKs being seen by Market ?
I mean, is it possible to relink all the batch-installed .apk files as they were installed from Android market ?
If not, this method is fine at first but becomes painful with all the lost market updates
Thanks a lot
darkcell said:
this is simplest method yet...
copy .apk to any folder in sdcard, mine "marketapp"
then type these following commands below:
=====================================
adb shell
su
cd /sdcard/marketapp
for app in *.apk; do pm install -r $app; done
=====================================
regards,
d4rkcell
Click to expand...
Click to collapse
Thanks a lott for this !!!!
having about 260 apps installed it saves me several hours to reinstall after updating to froyo !!
k.mooijman said:
Thanks a lott for this !!!!
having about 260 apps installed it saves me several hours to reinstall after updating to froyo !!
Click to expand...
Click to collapse
Would be them updated from market, afterwards ?
I fear they'll loose the market link, by installing them from local apk files...
Even easier.
Thanks for the great information. I realize you can save yourself a few steps after gathering all the apk's in one location by using this command line (XP or higher):
Step 2. In the Android SDK folder containing adb, type:
Code:
for %f in (c:\apps\*.apk) do @(echo adb install -r %f)
dannycurtean said:
I looked around the net for a feasable solution but nobody seemed to give me a practical solution. So I decided to experiment and came up with an unbelivable solution that takes literally 20-30 seconds per app and is FULLY automated.
My problem was as follows. I like to install new ROMs by wiping, flashing and reinstalling my apps. The problem with that is when you have 130 apps and Astro file manager seems to install 3-5 then quits back to the packages screen, it becomes extremely friken agrivating and simply hell-as annoying!
So I needed a way to install all my previously backed up apps (which Astro does a BEAUTIFUL job with) from my SD card to my phone all in one go, without prompts and without any input.
To do this its simple, just write your own batch script and run adb install.
You will need:
1. Android SDK (your version, ie. 2.2, 2.1, 1.6 ect.)
Code:
youtube.com/watch?v=A1SOSXwkc_8
2. USB Cable to PC
3. Enable "USB Debugging" on phone
**Prefer doing a fresh install of latest ROM, no third party apps and dont open Android Market if you have Froyo because it will try and download all your previously downloaded apps again. Cool but not cool here.**
Now, I assume you already have the APK bunch on your SD card, like I had.
I use Astro File Manager to backup all my apks to my /sd/backup/apps (which is automatically set).
Once you have all your APKs in one directory, I suggest putting them on you C:\. For example "c:\apps" for ease of scripting.
Step 1.
Open command prompt (CMD) and change directory to your "c:\apps"
Click to expand...
Click to collapse
darkcell said:
this is simplest method yet...
copy .apk to any folder in sdcard, mine "marketapp"
then type these following commands below:
=====================================
adb shell
su
cd /sdcard/marketapp
for app in *.apk; do pm install -r $app; done
=====================================
regards,
d4rkcell
Click to expand...
Click to collapse
This looks like a great solution. Is there some way to run this from the phone itself? When I tried using Terminal Emulator in ICS, I get a Segmentation Fault error.
Found this in Google results, was extremely useful for restoring all my Xoom apps from my pre-root times
Hi to spartan062984
Couple of suggestions which I found to work.
Copy adb.exe to \windows\system32.--- this will give you a global adb which works from any directory.
Make a folder 'APK' ( or what you wish ) and put your apk's into it.
In DOS cd to APK and then run your install e.g. adb install xyz.apk \app
Hope it works for you
Keith
dannycurtean said:
I looked around the net for a feasable solution but nobody seemed to give me a practical solution. So I decided to experiment and came up with an unbelivable solution that takes literally 20-30 seconds per app and is FULLY automated.
My problem was as follows. I like to install new ROMs by wiping, flashing and reinstalling my apps. The problem with that is when you have 130 apps and Astro file manager seems to install 3-5 then quits back to the packages screen, it becomes extremely friken agrivating and simply hell-as annoying!
So I needed a way to install all my previously backed up apps (which Astro does a BEAUTIFUL job with) from my SD card to my phone all in one go, without prompts and without any input.
To do this its simple, just write your own batch script and run adb install.
You will need:
1. Android SDK (your version, ie. 2.2, 2.1, 1.6 ect.)
Code:
youtube.com/watch?v=A1SOSXwkc_8
2. USB Cable to PC
3. Enable "USB Debugging" on phone
**Prefer doing a fresh install of latest ROM, no third party apps and dont open Android Market if you have Froyo because it will try and download all your previously downloaded apps again. Cool but not cool here.**
Now, I assume you already have the APK bunch on your SD card, like I had.
I use Astro File Manager to backup all my apks to my /sd/backup/apps (which is automatically set).
Once you have all your APKs in one directory, I suggest putting them on you C:\. For example "c:\apps" for ease of scripting.
Step 1.
Open command prompt (CMD) and change directory to your "c:\apps"
Example:
Code:
cd..
cd..
cd apps
Now you should see your path set as "C:\apps" in CMD.
Step 2.
Create directory print.
In CMD "C:\apps" run:
Code:
dir /s /b > print.txt
This will print all directory files and extensions but nothing else, like size and attributes into your "C:\apps" folder. Now you will see a "print.txt" file in your "c:\apps" folder. If you open it, you will see a list of all your APKs.
Step 3.
Assuming you are using Notepad to view your "print.txt" file, press "CTRL+H". This will open the Find and Replace dialog box.
In Find type
Code:
C:\
In replace type
Code:
adb install -r c:\
Hit enter and it will modify all the APKs with the adb install command. Save and close notepad.
Step 4.
Now you need to rename that .txt extension in your "c:\apps\print.txt" to "print.bat". You need to have extension shown in windows. Google that if you dont know how to do that.
Once saved as a .bat file, simply execute and it will run through the sequence to install all your APK files without any prompts on your phone. Voila, and enjoy.
EXAMPLE:"c:\apps\print.bat"
Code:
adb install -r c:\apps\com.twitter.android-1.apk
adb install -r c:\apps\com.ups.mobile.android-2.apk
adb install -r c:\apps\com.vavni.android.battleship-1.apk
adb install -r c:\apps\com.viclabs.myRemote-2.apk
adb install -r c:\apps\com.waterflea.wifiscan-1.apk
adb install -r c:\apps\com.wyse.pocketcloud-1.apk
adb install -r c:\apps\com.xrath.jmsn-2.apk
adb install -r c:\apps\com.xtralogic.android.rdpclient-1.apk
adb install -r c:\apps\com.xtremelabs.android.speedtest-1.apk
adb install -r c:\apps\com.yahoo.mobile.client.android.im-1.apk
adb install -r c:\apps\com.yahoo.mobile.client.android.mail-2.apk
adb install -r c:\apps\com.yahoo.mobile.client.android.search-1.apk
adb install -r c:\apps\hongbo.bluescreen-1.apk
adb install -r c:\apps\info.marlan.sim-1.apk
adb install -r c:\apps\koushikdutta.telnet-1.apk
adb install -r c:\apps\kr.mobilesoft.yxplayer-2.apk
adb install -r c:\apps\net.mafro.android.wakeonlan-1.apk
adb install -r c:\apps\nl.rogro.GScript-1.apk
adb install -r c:\apps\org.ajeje.fakelocation-1.apk
adb install -r c:\apps\org.ale.abtc-1.apk
adb install -r c:\apps\org.android7.aviplayer-1.apk
adb install -r c:\apps\org.connectbot-1.apk
adb install -r c:\apps\org.gmote.client.android-1.apk
adb install -r c:\apps\org.iii.ro.meridian-1.apk
adb install -r c:\apps\org.kman.WifiManager-1.apk
adb install -r c:\apps\org.openobjectives.serverassistant-1.apk
adb install -r c:\apps\org.prowl.networkmapper-1.apk
adb install -r c:\apps\org.transdroid-1.apk
This will go in sequence and show "success" when finished installing. It will then run the next command in sequence until its done.
** I tried to write this thread as a help to those trying to do the same thing I was trying to do. This is in no way meant to validate anything and is meant merely as a resource to anybody. If your going to be an ass, shove it, if you like it, im happy I could help.**
Click to expand...
Click to collapse
This works good so far.. lets hope that system process likes it.
trying now.
darkcell said:
this is simplest method yet...
copy .apk to any folder in sdcard, mine "marketapp"
then type these following commands below:
=====================================
adb shell
su
cd /sdcard/marketapp
for app in *.apk; do pm install -r $app; done
=====================================
regards,
d4rkcell
Click to expand...
Click to collapse
I love simple solutions in linux
You have killed all 100km long tutorials and apps
Very Good, Thanx
i'm testing
very good method..
good lock..
Could anyone kindly share the adb code to change the permissions of an apk and push it to system/app/ ?
Using adb from a PC.
Please and thanks. :fingers-crossed:
Krsmqn said:
Could anyone kindly share the adb code to change the permissions of an apk and push it to system/app/ ?
Using adb from a PC.
Please and thanks. :fingers-crossed:
Click to expand...
Click to collapse
You know you can set the permissions before you push it to /system/app
Windows right?
http://www.cyberciti.biz/tips/windows-change-access-permissions-from-the-command-line.html
Or after you push it to /system/app
Code:
adb shell chmod <permissions> <filename>
Thank you for the reply.
To push to system/app, do I have the code right?
adb push xxxxxx.apk /system/app/
?
I try that and I get the error "device not found"
adb devices shows my device... wth?
Can anyone help?
How to Push Application to /system/app
Krsmqn said:
Could anyone kindly share the adb code to change the permissions of an apk and push it to system/app/ ?
Using adb from a PC.
Please and thanks. :fingers-crossed:
Click to expand...
Click to collapse
Krsmqn,
The code was missing a little information, I am sorry. First you need to make sure adb is enabled on the Kindle by
pulling down the upper status bar where you see the time. After you pull it down select More+ the go into
Security make sure Enable ADB is turned On. Next click the <- Arrow Back, then choose Device. Make sure
Allow Installation of Applications is turned On. If all this is OK, then let's test ADB. Make sure the Kindle is
plugged into USB, next go into Windows Device Manager by Right Hand Mouse Click on "Computer", select
"Properties", next select "Device Manager". Do you see Android Composite ADB Interface under Kindle Fire?
If no, go back to our tutorial and reinstall the ADB Driver as outlined in this tutorial:
http://forum.xda-developers.com/showthread.php?t=2069117
Once ADB is functioning properly, then let's PUSH files!
First let's make sure adb is running and make sure adb see's the Kindle. Please run these commands:
Code:
adb kill-server
adb start-server
adb devices
The output after devices will be a serial number, if this looks good, move on. First you need to make
sure the apk you want to push is in the same directory as adb.exe - if you have moved the apk to
the adb.exe directory, then run the following:
Code:
[FONT=Verdana]adb remount
adb push file_name_comes.apk_here /system/app/
adb shell chmod 644 /system/app/file_name_comes_here.apk
adb reboot[/FONT]
Does this help?
prokennexusa said:
Krsmqn,
The code was missing a little information, I am sorry. First you need to make sure adb is enabled on the Kindle by
pulling down the upper status bar where you see the time. After you pull it down select More+ the go into
Security make sure Enable ADB is turned On. Next click the <- Arrow Back, then choose Device. Make sure
Allow Installation of Applications is turned On. If all this is OK, then let's test ADB. Make sure the Kindle is
plugged into USB, next go into Windows Device Manager by Right Hand Mouse Click on "Computer", select
"Properties", next select "Device Manager". Do you see Android Composite ADB Interface under Kindle Fire?
If no, go back to our tutorial and reinstall the ADB Driver as outlined in this tutorial:
http://forum.xda-developers.com/showthread.php?t=2069117
Once ADB is functioning properly, then let's PUSH files!
First let's make sure adb is running and make sure adb see's the Kindle. Please run these commands:
Code:
adb kill-server
adb start-server
adb devices
The output after devices will be a serial number, if this looks good, move on. First you need to make
sure the apk you want to push is in the same directory as adb.exe - if you have moved the apk to
the adb.exe directory, then run the following:
Code:
[FONT=Verdana]adb remount
adb push file_name_comes.apk_here /system/app/
adb shell chmod 644 /system/app/file_name_comes_here.apk
adb reboot[/FONT]
Does this help?
Click to expand...
Click to collapse
Thank you for the help. I am thoroughly confused. This is going to be as detailed as I can make it.
Ok.... here's what happens:
The device shows up on my computer in device manager as "kindle fire > android adb interface" ... good right? But when plugged in, the usual "usb connected interface with the turn on usb storage button" doesn't show up on my kindle. The notification drop down only says "connected to a low power charger" .. blah blah. I will get to the CMD stuff in a sec.
On the kindle:
Besides the above mentioned stuff, when I press More :
Settings > My Account> the menu closes. The entire menu, so now I am looking at my home screen.
Settings> Applications>Notification settings> results in going back to the "more" or settings menu.
Settings>Applications>Installed Applications> seems to work . Shows both lists. All & Running.
Settings>Applications>Sync Amazon Content> results in nothing. Below that, Amazon App list is empty.So... figures.
Settings>Parental Controls are grayed out.
Settings>Sounds&Display> Everything here works except for >Notification Sounds> Back to Settings.
Settings>Wireless>Connects fine (didn't try bluetooth)
Settings>Device>About>All info is there (update kindle is grayed out)
Settings>Device>Storage>Back to Settings
Settings>Device>Date&Time> Time grayed out. Date grayed out. Select time zone works. Use 24h works.
Settings>Device>Allow Install of Apps> Works (is turned on)
Settings>Device>Reset to Factory Defaults> Menu pops up (are you sure blah blah) but I already did that and it's why I have these problems.
Settings>Location-based Services> Enable location works..
Settings>Language&Keyboard>Device language works.
Settings>Language&Keyboard>Keyboards>Default is Japanese? Keyboard Settings>All options work. But Japanese is the only language option.
Settings>Security>Everything here works, adb is on. No device admins.
Settings>Legal & Compliance>Notices>Everything here is fine.
Settings>Legal & Compliance>Terms of use> Back to Settings menu
Settings>Legal & Compliance>Safety stuff> Works
Settings>Legal & Compliance>Privacy>Opens Chrome (see chrome problems)
So that's what's up with the settings.
App issues:
Chrome> "Critical functionality required to run chrome is missing; either your chrome installation is incompatible, or not compatible with this version" Click ok and chrome closes. Chrome is the only browser installed that I can see.
Terminal Emulator> "Terminal Emulator has stopped" error msg.
Google search works untill it opens chrome.
Navigation> won't load (hangs at waiting for location with location on and wifi connected)
Maps> works including search. and wiki until you try to open chrome.
Latitude> works except when chrome in involved.
Google Drive> "Google Drive has stopped"
Youtube> Works fine until chrome is opened.
Camera/Video player/Music player/Gallery> Work
94/7fm (Streaming music app)> works except chrome is opened
Calendar> Won't open, asks you to register> registration attempt just closes without action.
Gmail>works untill chrome is opened.
Kindle Docs> Opens but is empty>cloud service fails at sign in.
News&weather> works until chrome is opened.
Amazon Video> closes instantly.
A few "go launcher apps (appcenter, gamezone, themes ,etc...) open but try to open chrome and fail.
That's about it for apps.
ADB:
adb devices: shows device
Try to push es file explorer renamed to ES.apk, located with adb.exe:
Code:
[FONT=Verdana]
c:\SDK\platform-tools>adb remount
remount failed: Operation not permited
c:\SDK\platform-tools>adb push ES.apk /system/app/
failed to copy 'ES.apk' to ' /system/app/ /ES.apk' : Read-only file system
c:\SDK\platform-tools>adb shell chmod 644 /system/app/ES.apk
Unable to chmod /system/app/ES.apk; No such file or directory
c:\SDK\platform-tools>adb reboot
[/FONT]
Rebooted to no avail. Am I still rooted? Do I need to change the permissions before I move it?
I hope I gave enough info. I'll be checking back frequently, as I really want to get this fixed.
*Edit*
On my other thread (usb not working) You're info helped me to install es file explorer. Thank you! I will try to figure it out and keep you posted.
No sound - biggest issue
Ok, I figured that until I can get all this google stuff worked out, I'd just side load apks. No problem. Installed Dolphin Browser HD and some other apps. After downloading winamp and putting a bunch of music on my device, I realized that there's no sound from the external speakers. Headphones work fine. Any ideas?
EDIT* sound all the sudden started working.. weird.
Kindle Fire HD - Odd Issues
Krsmqn said:
Ok, I figured that until I can get all this google stuff worked out, I'd just side load apks. No problem. Installed Dolphin Browser HD and some other apps. After downloading winamp and putting a bunch of music on my device, I realized that there's no sound from the external speakers. Headphones work fine. Any ideas?
EDIT* sound all the sudden started working.. weird.
Click to expand...
Click to collapse
Krsmqn,
If you continue to have these oddities, I would recommend you to order a USB Factory Cable so you
can flash a fresh copy of the software back to your Kindle. We do sell the Factory USB Cables for $15
shipped. Just PM us if you would like to order one. The Factory USB Cable allows the Kindle to be
booted in Fastboot mode.
app can not run when push /system/app
Hi all,
When i push app in /system/app when reboot and click on icon app but app hang and not run.Please help me ? I install my app on sd card run very well
So I picked up a ADT-1 due to having Ethernet and more HD space on it. FOund out only certain apps can "cast" to it due to it being a dev device has there been anyone that figured out what needs to get it to have full casting features?
https://developer.android.com/tv/adt-1/index.html
Try changing ro.build.type to eng in build.prop, that should open up all apps.
/sub
let us know if this works
Confirmed this works!
HomerSp = worth his weight in gold.
Sorry
HomerSp said:
Try changing ro.build.type to eng in build.prop, that should open up all apps.
Click to expand...
Click to collapse
Sorry to sound like a newbie, however can someone teach me how to do this? I was trying to look it up on xda but had no luck finding anything. If anyone point me in the right direction, I would be very happy. Thank you again
Bboy_LeoGun said:
Sorry to sound like a newbie, however can someone teach me how to do this? I was trying to look it up on xda but had no luck finding anything. If anyone point me in the right direction, I would be very happy. Thank you again
Click to expand...
Click to collapse
1. Root
2. Open /system/build.prop
3. Change the line
4. Reboot
5. Enjoy.
I'm trying to do this but I'm being very unlucky. Not sure what's going wrong and any light on the matter will be greatly appreciated.
I changed the ro.build.type from `user` to `eng` and my device (on LPX13D) stops booting completely. All I see is the android logo and then blank screen. I already tried two times. The process I did is (from sudo on my Ubuntu 14 machine)
- adb pull /system/build.prop
- edit build.prop on `nano` on Ubuntu (change only that line)
- adb push build.prop /sdcard/
- adb shell
- su
- mount -o remount,rw /system
- mv /sdcard/build.prop /system/
the second time I adb pull /system/build.prop again just to check that the only thing changed was that, and it was fine.
The only thing I've been able to do to recover the system is to:
- install CWM from here https://forum.gtvhacker.com/adt-f52/topic1629.html (fastboot flash recovery <filename>)
- flash the image from here http://forum.xda-developers.com/har...t/adt1-stock-molly-images-unbricking-t2927888
- and then using the root from this post: https://plus.google.com/+Chainfire/posts/a5YshULM8hf to be able to "adb shell su"
any help? Maybe some bizarre permission on my ubuntu machine because I'm on "sudo shell" ?
Budius said:
I'm trying to do this but I'm being very unlucky. Not sure what's going wrong and any light on the matter will be greatly appreciated.
I changed the ro.build.type from `user` to `eng` and my device (on LPX13D) stops booting completely. All I see is the android logo and then blank screen. I already tried two times. The process I did is (from sudo on my Ubuntu 14 machine)
- adb pull /system/build.prop
- edit build.prop on `nano` on Ubuntu (change only that line)
- adb push build.prop /sdcard/
- adb shell
- su
- mount -o remount,rw /system
- mv /sdcard/build.prop /system/
the second time I adb pull /system/build.prop again just to check that the only thing changed was that, and it was fine.
The only thing I've been able to do to recover the system is to:
- install CWM from here https://forum.gtvhacker.com/adt-f52/topic1629.html (fastboot flash recovery <filename>)
- flash the image from here http://forum.xda-developers.com/har...t/adt1-stock-molly-images-unbricking-t2927888
- and then using the root from this post: https://plus.google.com/+Chainfire/posts/a5YshULM8hf to be able to "adb shell su"
any help? Maybe some bizarre permission on my ubuntu machine because I'm on "sudo shell" ?
Click to expand...
Click to collapse
build.prop has to be chmodded to 0644, or the device will not boot.
HomeSp I can't thank you enough!
That was exactly the issue. Third time is a charm.
So at the end of the procedure I:
- cd /system/
- mv build.prop build.prop.bak (just for the the sake of it)
- mv /sdcard/build.prop /system/
- chmod 0644 build.prop
- chown :root build.prop (prolly not needed but what-a-heck, why not)
- ls -l (and checked that both build.prop and build.prop.bak are exactly the same permission, owner and group)
- exit, exit adb reboot and all works great"
Thanks again!!!
Budius said:
- and then using the root from this post: https://plus.google.com/+Chainfire/posts/a5YshULM8hf to be able to "adb shell su"
Click to expand...
Click to collapse
For the purposes of modifying build.prop using "adb shell su", do you only have to flash the bootloader image from the linked post? I'd like to make the bare minimum changes so that future OTA's will install after restoring the original build.prop and flashing the stock bootloader.
jm9843 said:
For the purposes of modifying build.prop using "adb shell su", do you only have to flash the bootloader image from the linked post? I'd like to make the bare minimum changes so that future OTA's will install after restoring the original build.prop and flashing the stock bootloader.
Click to expand...
Click to collapse
my idea was a bare-minimum changes too. I just ended up ****ing up stuff and had to re-built a couple of times until I made it right.
but yeah, if you're comfortable with terminal commands and do the proper `chmod` (which I originally didn't), you can get everything done with "adb shell su" following like this:
- from PC: adb shell pull file to your PC
- from PC: edit file
- from PC: adb shell push file to /sdcard/
- from PC: adb shell
- from device shell: su
- from device shell/su: make /system/ writable, chmod file, rename "old" build.prop, copy new one over, double check chmod before rebooting.
ps.: the root from that post does install SuperUser.apk on the device, it's there on the UI, but after you do those changes there's some options in the .apk to remove root and uninstall it (if you want to)
I just thought that I'd directly use some build prop editor apk and do it easily but now my device is bricked :v
Stock ROM on download.
I'm just getting a black screen and bootloader.
So, the build.prop edit detailed in this thread works fine to make the ADT-1 a cast target for all Google Cast enabled apps. The problem is that it's hardly worth doing right now since Google Cast support on Android TV seems to be a work in progress. There's a support article that details third-party apps that are not supported - https://support.google.com/androidtv/answer/6123347
In addition to the apps listed there, I found that Watch ESPN isn't working on ADT-1 either. It's selectable in the app, but the video playback will not start. Here's to hoping that Google brings the Google Cast Receiver app for Android TV up to snuff soon - https://play.google.com/store/apps/details?id=com.google.android.apps.mediashell
jm9843 said:
So, the build.prop edit detailed in this thread works fine to make the ADT-1 a cast target for all Google Cast enabled apps. The problem is that it's hardly worth doing right now since Google Cast support on Android TV seems to be a work in progress. There's a support article that details third-party apps that are not supported - https://support.google.com/androidtv/answer/6123347
In addition to the apps listed there, I found that Watch ESPN isn't working on ADT-1 either. It's selectable in the app, but the video playback will not start. Here's to hoping that Google brings the Google Cast Receiver app for Android TV up to snuff soon - https://play.google.com/store/apps/details?id=com.google.android.apps.mediashell
Click to expand...
Click to collapse
Have any of you tried Slingplayer casting after changing build.prop?
Apple TV just died recently, it was the most reliable thing for Airplaying Slingplayer. Chromecast slingplayer kind of is ****ty at times.
Followed Budius' instructions and it worked perfectly.
adb pull /system/build.prop
----(edit build.prop on Notepad++ and changed ro.build.type=user to ro.build.type=eng)
adb push build.prop /sdcard/
adb shell
su
mount -o remount,rw /system
cd /system/
mv build.prop build.prop.bak
mv /sdcard/build.prop /system/
chmod 0644 build.prop
chown :root build.prop
ls -l
---(checked that both build.prop and build.prop.bak are exactly the same permission, owner, and group)
mount -o remount,ro /system
exit
exit
adb reboot
during the update from 5.0 -> 5.0.2 my ADT-1 stopped working again
It showed the little droid with the belly open and an error message
so that means here I went again to restore it, and this time I manage to streamline a bit the process, so let's share with you guys. Remember, my idea with this process is to have STOCK, but with Cast working from any app. I have no intention to root, or flash custom this or that. I want something that I can cast without issues and hopefully it will update the next update without problems.
first of all, the CWM link I posted before is giving malware warnings on Chrome so I found an alternative, and of course XDA is the source (see downloads).
so to factory restore ADT-1 to good working condition, was the same I said before:
- install CWM:
Code:
fastboot flash recovery cwm_molly_recovery_lpx13d.img
- install stock image. CWM->install zip-> from ADB:
Code:
adb sideload update-molly-Stock-LPV79-1.zip
- reboot and let auto-update run until the end.
now to enable cast to all apps with absolutely minimal modifications to the system (hopefully enabling future updates to run without issues)
- reboot ADT-1, holding the button, enter fastboot mode
- reboot to the CWM, but without installing it:
Code:
fastboot boot cwm_molly_recovery_lpx13d.img
- in CWM go to `mount n storage` -> mount /system
and carry on to do the build.prop modification from there, the trick is that I did not have to install a custom recovery and did not have to install super user. I made the modification directly via a RAM-only CWM and that's it. So below is just a copy of my previous post
Code:
> adb pull /system/build.prop /home/budius/build.prop
then change the build.prop on my computer and rename to new_build.prop.
And back to terminal
Code:
> adb push /home/budius/new_build.prop /system/new_build.prop
> adb shell
# cd system
# mv build.prop build.prop.bak
# mv new_build.prop build.prop
# chmod 0644 build.prop
And that's all! Full cast enabled to ADT-1 with the most absolutely minimal system changes I could come up with :victory: :highfive:
Downloads:
- here you'll find a very nice workin CWM.
- good working stock Android TV image for ADT-1
bonus:
while searching stuff I found this: https://plus.google.com/+AdamLawrence/posts/5Yr5vG7QJUq
I didn't try it but it seems useful, so the link is there.
I have installed Google Now launcher on the 5..1.1 firmware, I have root access as well and have pm hid and removed (just rm'ing the process folders from /system/priv-app) most of the bloatware. Whenever I try to hit the "home" button it just brings up a message saying " The requested action is not permitted. Check Parental Controls settings and retry". I also pm hid and attempted to remove com.amazon.parentalcontrols and it hasn't had any effect either.
If I reboot the device it does bring up the Now launcher, but as soon as I go to another application view and try to go "back" or use the home button I get the parental controls message.
KennBr said:
I have installed Google Now launcher on the 5..1.1 firmware, I have root access as well and have pm hid and removed (just rm'ing the process folders from /system/priv-app) most of the bloatware. Whenever I try to hit the "home" button it just brings up a message saying " The requested action is not permitted. Check Parental Controls settings and retry". I also pm hid and attempted to remove com.amazon.parentalcontrols and it hasn't had any effect either.
If I reboot the device it does bring up the Now launcher, but as soon as I go to another application view and try to go "back" or use the home button I get the parental controls message.
Click to expand...
Click to collapse
Well that's a new one, though have seen people say that now launcher is finicky and to have another launched installed as well.
I to have ota 5.1.1 with root and have tried to block the stock lauuncher got the same error i tried with 2 diff launchers, i havent tried to install both then disable the stock maybe it will trigger something to do with the default settings. in one of the settings menus for one of the launchers it says something about "set default launcher" and when i select it to set it to new launcher it just opens the stock one. does anyone know if there is a way to change what launcher the home button defaults to, either through adb shell or fastboot someway.
Have you tried su pm hide com.amazon.parentalcontrols
from a adb shell
jdeandeck said:
I to have ota 5.1.1 with root and have tried to block the stock lauuncher got the same error i tried with 2 diff launchers, i havent tried to install both then disable the stock maybe it will trigger something to do with the default settings. in one of the settings menus for one of the launchers it says something about "set default launcher" and when i select it to set it to new launcher it just opens the stock one. does anyone know if there is a way to change what launcher the home button defaults to, either through adb shell or fastboot someway.
Have you tried su pm hide com.amazon.parentalcontrols
from a adb shell
Click to expand...
Click to collapse
How did you try to block it?
Whilst the stock launcher is on and is a system app the Fire OS won't let any other launcher steal default.
Pond-life said:
How did you try to block it?
Whilst the stock launcher is on and is a system app the Fire OS won't let any other launcher steal default.
Click to expand...
Click to collapse
I used adb shell pm hide com.amazon.firelauncher -- adb reboot-- reboots to apex launcher but when i push home i get the error, do i need to actually uninstall it or can i install a rom management app and remove it from system app list and freeze it im trying not to do any of this stuff without confirmation on it working, my wife is worried ill ruin her fire. Do you know how hard is it to flash back to stock firmware from a bricked Fire?
i have flashed devices before roms and recovery so im not a noob but i would just hate to be wrong and try something and not be able to fix it.
jdeandeck said:
I used adb shell pm hide com.amazon.firelauncher -- adb reboot-- reboots to apex launcher but when i push home i get the error, do i need to actually uninstall it or can i install a rom management app and remove it from system app list and freeze it im trying not to do any of this stuff without confirmation on it working, my wife is worried ill ruin her fire. Do you know how hard is it to flash back to stock firmware from a bricked Fire?
i have flashed devices before roms and recovery so im not a noob but i would just hate to be wrong and try something and not be able to fix it.
Click to expand...
Click to collapse
Hmm I'm sure that hiding it has worked for others, maybe not on 5.1.1 though, I froze it in titanium backup. Widgets didn't work in Apex until I pushed it to system but it did work as main launcher. As did trebuchet and Nova.
If it's opening when you've hidden it then suggests that it's not hidden maybe needs root shell to do it on 5.1.1 as with hiding the ads and ota
Pond-life said:
Hmm I'm sure that hiding it has worked for others, maybe not on 5.1.1 though, I froze it in titanium backup. Widgets didn't work in Apex until I pushed it to system but it did work as main launcher. As did trebuchet and Nova.
If it's opening when you've hidden it then suggests that it's not hidden maybe needs root shell to do it on 5.1.1 as with hiding the ads and ota
Click to expand...
Click to collapse
it doesnt open but it gives me the parental control error, is it possible to rename the apex application maybe to com.amazon.firelauncher.apk and overwrite the current one, after backing up the original of course, to get rid of the parental error?
jdeandeck said:
it doesnt open but it gives me the parental control error, is it possible to rename the apex application maybe to com.amazon.firelauncher.apk and overwrite the current one, after backing up the original of course, to get rid of the parental error?
Click to expand...
Click to collapse
Pretty sure that wouldn't work. It'll likely expect Apex to be able to work in ways amazon launcher can but it can't.
If you've got a back up of the original you could try renaming it or just deleting it on the tablet, I don't think hide is working as it should.
Could try the supertool to switch the launcher to nova and then change launcher to Apex after. The tool does delete the amazon launcher, so backed up original handy.
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
Using pm hide com. amazon. firelauncher worked fine for me to disable the Fire launcher but I had to reboot before Google Now tried to launch. Which it did, but then trying to use the home or back buttons brings on the message.
Another weird thing, all the bloat thst I hid the same way deems to have come back overnight somehow. I did disable Ota updates so not sure how that is.
KennBr said:
Using pm hide com. amazon. firelauncher worked fine for me to disable the Fire launcher but I had to reboot before Google Now tried to launch. Which it did, but then trying to use the home or back buttons brings on the message.
Another weird thing, all the bloat thst I hid the same way deems to have come back overnight somehow. I did disable Ota updates so not sure how that is.
Click to expand...
Click to collapse
so if you have perm root than first download and install
HTML:
http://www.apkdrawer.com/rom-toolbox-pro-apk/
then install the google now launcher and run it and everything get it running then reboot
next through the Rom Toolbox make the Google Now a system app
then "adb shell pm hide com.amazon.launcher" then "adb reboot"
Just incase this factors in i used the script from the super tool, since i run linux and cant run the bat file, as a guide i was trying to get my laucher "adb push Apex-Launcher.apk" & "adb shell "cp /data/local/tmp/--Apex-Launcher.apk--(my preferred laucher) /system/apps/Apex-Launcher.apk" but it would not let me mount file system as RW, so before i tried the above solution, which worked for me, i ran (adb reboot-bootloader) and (fastboot oem append-cmdline "androidboot.unlocked_kernel=true") so you may or may not have to do this before you try to hide the launcher but after you install Rom Toolbox
KennBr said:
Using pm hide com. amazon. firelauncher worked fine for me to disable the Fire launcher but I had to reboot before Google Now tried to launch. Which it did, but then trying to use the home or back buttons brings on the message.
Another weird thing, all the bloat thst I hid the same way deems to have come back overnight somehow. I did disable Ota updates so not sure how that is.
Click to expand...
Click to collapse
Those are both symptoms of the hide command not working fine. It needs to be done in root as jdeandeck did.
If you disable the ota with a hide command too I'd rename the ota files or do that again in root.
jdeandeck said:
so if you have perm root than first download and install
HTML:
http://www.apkdrawer.com/rom-toolbox-pro-apk/
then install the google now launcher and run it and everything get it running then reboot
next through the Rom Toolbox make the Google Now a system app
then "adb shell pm hide com.amazon.launcher" then "adb reboot"
Just incase this factors in i used the script from the super tool, since i run linux and cant run the bat file, as a guide i was trying to get my laucher "adb push Apex-Launcher.apk" & "adb shell "cp /data/local/tmp/--Apex-Launcher.apk--(my preferred laucher) /system/apps/Apex-Launcher.apk" but it would not let me mount file system as RW, so before i tried the above solution, which worked for me, i ran (adb reboot-bootloader) and (fastboot oem append-cmdline "androidboot.unlocked_kernel=true") so you may or may not have to do this before you try to hide the launcher but after you install Rom Toolbox
Click to expand...
Click to collapse
I am using Linux as well, I got the persistent root going, Super SU installed as described in this thread: http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362/post64347634#post64347634 I tried intsalling the Now launcher just via the Play Store app. However, when I tried to remove the bloat from the /system/priv-apps/ directory I also noticed the filesystem was read-only so I remounted it like so (I am totally unsure if this is proper)
Code:
adb shell
su
mount -o rw,remount /system
That seemed to give me sufficiant read-write access with a root terminal.
Pond-life said:
Those are both symptoms of the hide command not working fine. It needs to be done in root as jdeandeck did.
If you disable the ota with a hide command too I'd rename the ota files or do that again in root.
Click to expand...
Click to collapse
As in a root terminal? I launched an adb shell and used su and mount as described above to get read-write access and a root terminal, then did...
Code:
cat /data/local/tmp/bloat_list | while read process ; do pm hide $process ; done
and
Code:
cat /data/local/tmp/bloat_list | while read process ; do rm -R $process ; done
It seemed to remove the directories associated with the given item on the "bloat_list" file which I compiled from the "safe to remove bloatware" threads and pushed to the /data/local/tmp directory using adb. I did this prior on 5.0.1 without breaking too much... Aside from not being able to open my account settings any longer.
Contents of my "bloat_list"
Code:
com.amazon.ags.app
com.audible.application.store
com.amazon.camera
com.amazon.client.metrics
com.android.contacts
com.amazon.csapp
com.amazon.device.backup
com.amazon.h2settingsfortablet
com.amazon.kindle
com.amazon.kindle.kso
com.amazon.kindle.otter
com.amazon.mp3
com.amazon.kindle.otter.oobe
com.amazon.kindle.otter.settings
com.amazon.kindle.personal_video
com.amazon.legalsettings
com.amazon.photos.importer
com.amazon.photos
com.amazon.platform
com.amazon.tahoe
com.amazon.venezia
com.amazon.whisperlink.core.android
com.amazon.windowshop
com.amazon.zico
com.andoid.contacts
com.android.calendar
com.android.email
com.audible.application.kindle
com.goodreads.kindle
com.nuance.edr.androidservice.service
com.amazon.webapp
amazon.jackson-19.apk
com.kingsoft.office.amz
com.amazon.kor.demo
com.amazon.ods.kindleconnect
com.amazon.accessorynotifier
com.amazon.cloud9
com.amazon.weather
com.amazon.calculator
So every item in that list would have been acted on with both pm hide and rm -R (just clarifying)
Yet somehow a good amount of the items on that list came back over night. I'm not really sure my method for removing the files really had the effect that I think it did, because everything still seemed to work as if I hadn't deleted it... Well except for the "My Account" section of the "Settings", so I don't think I should have done the "rm -R" part to delete the files because it seems to have had some kind of effect.
As for the launcher situation, I backed up the firelauncher first before trying to remove and hide it and that did seem to work, but given the parental controls message I had to restore the launcher to maintain functionality. I don't think that trying to delete the items on the bloat_list first might have "broken" something and caused the message though because I tried to change the launcher BEFORE the items on the bloat_list.
I tried installing the Apex Launcher and for whatever reason it's working even without hiding or deleting Firelauncher... Though I haven't rebooted yet so I'm doubting that will remain the case.
As for the Rom Toolbox app, what exactly does it do? Reboots the device into some kind of custom recovery where I can alter settings? I've never heard of it before.
KennBr said:
I am using Linux as well, I got the persistent root going, Super SU installed as described in this thread: http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362/post64347634#post64347634 I tried intsalling the Now launcher just via the Play Store app. However, when I tried to remove the bloat from the /system/priv-apps/ directory I also noticed the filesystem was read-only so I remounted it like so (I am totally unsure if this is proper)
Code:
adb shell
su
mount -o rw,remount /system
That seemed to give me sufficiant read-write access with a root terminal.
As in a root terminal? I launched an adb shell and used su and mount as described above to get read-write access and a root terminal, then did...
Code:
cat /data/local/tmp/bloat_list | while read process ; do pm hide $process ; done
and
Code:
cat /data/local/tmp/bloat_list | while read process ; do rm -R $process ; done
It seemed to remove the directories associated with the given item on the "bloat_list" file which I compiled from the "safe to remove bloatware" threads and pushed to the /data/local/tmp directory using adb. I did this prior on 5.0.1 without breaking too much... Aside from not being able to open my account settings any longer.
Contents of my "bloat_list"
Code:
com.amazon.ags.app
com.audible.application.store
com.amazon.camera
com.amazon.client.metrics
com.android.contacts
com.amazon.csapp
com.amazon.device.backup
com.amazon.h2settingsfortablet
com.amazon.kindle
com.amazon.kindle.kso
com.amazon.kindle.otter
com.amazon.mp3
com.amazon.kindle.otter.oobe
com.amazon.kindle.otter.settings
com.amazon.kindle.personal_video
com.amazon.legalsettings
com.amazon.photos.importer
com.amazon.photos
com.amazon.platform
com.amazon.tahoe
com.amazon.venezia
com.amazon.whisperlink.core.android
com.amazon.windowshop
com.amazon.zico
com.andoid.contacts
com.android.calendar
com.android.email
com.audible.application.kindle
com.goodreads.kindle
com.nuance.edr.androidservice.service
com.amazon.webapp
amazon.jackson-19.apk
com.kingsoft.office.amz
com.amazon.kor.demo
com.amazon.ods.kindleconnect
com.amazon.accessorynotifier
com.amazon.cloud9
com.amazon.weather
com.amazon.calculator
So every item in that list would have been acted on with both pm hide and rm -R (just clarifying)
Yet somehow a good amount of the items on that list came back over night. I'm not really sure my method for removing the files really had the effect that I think it did, because everything still seemed to work as if I hadn't deleted it... Well except for the "My Account" section of the "Settings", so I don't think I should have done the "rm -R" part to delete the files because it seems to have had some kind of effect.
As for the launcher situation, I backed up the firelauncher first before trying to remove and hide it and that did seem to work, but given the parental controls message I had to restore the launcher to maintain functionality. I don't think that trying to delete the items on the bloat_list first might have "broken" something and caused the message though because I tried to change the launcher BEFORE the items on the bloat_list.
I tried installing the Apex Launcher and for whatever reason it's working even without hiding or deleting Firelauncher... Though I haven't rebooted yet so I'm doubting that will remain the case.
As for the Rom Toolbox app, what exactly does it do? Reboots the device into some kind of custom recovery where I can alter settings? I've never heard of it before.
Click to expand...
Click to collapse
Once in terminal the commands are the same from whatever computer you are using aren't they? Doesn't rm need the full directory address as it's not through pm?
The rom toolbox I think he just used to make the Now launcher a system app, so not something you can't do in adb.
Rom Toolbox is my favorite app for everything. Here is a list of some of the features you will find:
ROM Management
Install ROM’s & themes from a growing list of ROM’s. KAPOK, Cyanogen Mod and other popular ROM’s included in ROM Toolbox Pro apk.
Create, manage & restore nandroid backups
Wipe data, cache, dalvik-cache, battery stats
Install multiple ROMs & ZIPs from your SD card
App Manager
Batch backup & restore apps and their data
Schedule backups to run at a certain time
Restore apps from nandroid backups
Backup/Restore text messages, bookmarks, accounts, etc.
Backup your apps to dropbox
Freeze/Defrost system & user apps
Backup/restore Android Market link
Task manager
Automated batch uninstaller
E-mail your apps to friends
Move any user app to the SD card
Clean up dalvik-cache
Zip align, fix permissions, wipe data & cache, force close any app
Root Explorer
Access the whole of android’s file system (including the elusive data folder!).
Batch copy/paste, zip, tar, delete, move any file or folder
Change file permissions and ownership
View, edit & share files with ROM Toolbox Pro apk
File manager with two panels for easier management
Script-er & Terminal Emulator
Create and run scripts as root
Set your scripts to run at-boot
Auto Start Manager
Enable/disable apps that run on start-up
Enable/disable any broadcast receiver, activity or service
Reboot er
Reboot recovery, powerdown, bootloader, restart status bar, etc.
Font Installer
Install custom fonts from a huge list or from your sdcard
Set fonts as favorites & send them to friends
Boot Animation Installer
Install custom boot animations from a huge collection or from your sdcard
Preview boot animations
Create a boot animation from a GIF file
Have a new random boot animation each time you boot-up!
Theme Manager & Status bar Icon Changer
Create and install full themes (Meta Morph compatible)
Customize your status bar by installing custom icons for wifi, signal, gps, etc.
Change your battery icons in the status bar to a custom one from a list of 200+
Boot Logo Changer
Change your boot logo for supported phones
Theme Chooser Themes
View a list of themes for the T Mobile Theme Chooser
Set CPU
Set CPU & scaling governor
CPU Profiles
Kernel tweaks to speed up performance
Build.prop Editor
Easily edit your build.prop
Change LCD density, improve battery life, increase performance
Auto Memory Manager
Set min free values & select from presets. Apply values at boot
SD Booster
Increase the speed of your SD card
Permissions
Contacts – Backup call log and sms
SMS – Backup call log and sms
Accounts – Backup and restore from Google Drive
As for the bloat problem the:
Code:
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
Seems to be imoportant for my Special Offer "screensaver" hiding a.k.a. com.amazon.kso
but idk if this works i guess i could try myself but Rom Toolboxes App Manager feature, that is only available in the pro, can "freeze" the com.amazon.firelauncher....
ok the above seems to worked maybe having the app installed when i did it did something in the settings or i froze the launcher and just dont remember it, but when i froze the firelauncher and pushed the home button, without the apexlauncher installed, nothing happened, not even the parental control message. then i reinstalled the apex launcher, hint get the pro from the site i mentioned before, and adb reboot, it worked.
next i might try to freeze some bloatware and see what i can get rid of but still save amazon app store stuff like books, audio books+store, videos, Game circle-thats for me, music player, shop amazon, which as i type i realize i can do from the Rom Toolbox with root, i swear im not selling anything
Pond-life said:
Once in terminal the commands are the same from whatever computer you are using aren't they?
The rom toolbox I think he just used to make the Now launcher a system app, so not something you can't do in adb.
Click to expand...
Click to collapse
Yeah they are the same since it's basically a *nix shell, was just showing how I did it. I'm not sure if there's some nuance I'm not aware of thst would make it not work... It seemed like I had all the permissions I needed, and I have root set up persistently as described in the thread I linked to.
The rom toolbox app, how does it boot recoveries if fastboot can't? Sorry I'm so used to desktops, fiddling with Androids goes above my head.
And the commands are the same but the \ in windows commands are / in linux like android so scripts meant for windows wont work on linux, or that i have found and i cant get .bin to run but never tried to change to .sh and run as shell script but thats for another forum
jdeandeck said:
Rom Toolbox is my favorite app for everything.
As for the bloat problem the:
Code:
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
Seems to be important for my Special Offer "screensaver" hiding a.k.a. com.amazon.kso
but idk if this works i guess i could try myself but Rom Toolboxes App Manager feature, that is only available in the pro, can "freeze" the com.amazon.firelauncher....
ok the above seems to worked maybe having the app installed when i did it did something in the settings or i froze the launcher and just dont remember it, but when i froze the firelauncher and pushed the home button, without the apexlauncher installed, nothing happened, not even the parental control message. then i reinstalled the apex launcher, hint get the pro from the site i mentioned before, and adb reboot, it worked.
next i might try to freeze some bloatware and see what i can get rid of but still save amazon app store stuff like books, audio books+store, videos, Game circle-thats for me, music player, shop amazon, which as i type i realize i can do from the Rom Toolbox with root, i swear im not selling anything
Click to expand...
Click to collapse
It does seem rather a flexible toolkit.
Once you've got permanent root the fastboot bit shouldn't be needed I don't think. Hmmm.
I did clear much of the apps out, though did put Shop Amazon back on as I think something I wanted to use wouldn't work. I can't recall what though.
KennBr said:
Yeah they are the same since it's basically a *nix shell, was just showing how I did it. I'm not sure if there's some nuance I'm not aware of thst would make it not work... It seemed like I had all the permissions I needed, and I have root set up persistently as described in the thread I linked to.
The rom toolbox app, how does it boot recoveries if fastboot can't? Sorry I'm so used to desktops, fiddling with Androids goes above my head.
Click to expand...
Click to collapse
I use it to mostly change build.prop and backup apks and terminal emulator other things that i feel comfortable doing nothing like flashing or whatever i only flash from terminal on my linux pc or there is a app for flashing lg phones nothing easier than that.
KennBr said:
Yeah they are the same since it's basically a *nix shell, was just showing how I did it. I'm not sure if there's some nuance I'm not aware of thst would make it not work... It seemed like I had all the permissions I needed, and I have root set up persistently as described in the thread I linked to.
The rom toolbox app, how does it boot recoveries if fastboot can't? Sorry I'm so used to desktops, fiddling with Androids goes above my head.
Click to expand...
Click to collapse
Ooops I edited that one while you were replying.
Unlike pm doesn't rm need to know where the file or directory is like in this from the supertool?
adb shell "rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk"
so it'd need to know that those directories were in priv-app in system?
And it seems to make a different part writeable than you did, at least I think that's what the chmod does and uses disable rather than hide oh and the " " everywhere.
adb shell su -c "chmod 777 /cache"
adb shell su -c "pm disable com.amazon.otaverifier"
adb shell su -c "pm disable com.amazon.device.software.ota"
adb shell su -c "pm disable com.amazon.settings.systemupdates"
And the fastboot oem command followed by fastboot reboot, not fastboot continue, lets me adb remount fine then when im done doing whatever i use adb reboot then it will reboot and reconfigure apps and settings or something and works good.
---------- Post added at 02:36 AM ---------- Previous post was at 02:30 AM ----------
Pond-life said:
Ooops I edited that one while you were replying.
Unlike pm doesn't rm need to know where the file or directory is like in this from the supertool?
adb shell "rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk"
so it'd need to know that those directories were in priv-app in system?
And it seems to make a different part writeable than you did, at least I think that's what the chmod does and uses disable rather than hide oh and the " " everywhere.
adb shell su -c "chmod 777 /cache"
adb shell su -c "pm disable com.amazon.otaverifier"
adb shell su -c "pm disable com.amazon.device.software.ota"
adb shell su -c "pm disable com.amazon.settings.systemupdates"
Click to expand...
Click to collapse
i edited what i read to what i needed and if it said adb shell i ran everything from the adb shell fro terminal instead of saying adb shell su every time i said adb shell then su then pm ...