Database Develop

How to replace launcher.apk in system folder

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

[Solved] The Market issues on JH2

I found a thread over in the I9000 section that may explain our problems with the Market on JH2.
http://forum.xda-developers.com/showthread.php?t=757461
This would seem to suggest that if you are running an unreleased firmware you need to replace the build.prop file from the released version in order to fix the market.
I have not tried this yet, I need to find the build.prop file from the original firmware first.

You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell. If you get an error about unknown user/group, try chown 0.0 instead of root.root.
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Explorer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app (if running).
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.

I found this JF6 build.prop file in the stock system dump here. Let's see how this works:
http://forum.xda-developers.com/showthread.php?t=730226

Uploaded the stock build.prop to /system. It seems to make no difference in terms of availibility of the missing apps (only tried Fandango, but still missing). Grrrrr...need solution.

This did work for me. Thanks for the JF6 build.prop file.
This requires a rooted phone. You can brick your phone messing around with root. Not my fault...
I shut down the Market app, cleared its cache in Settings/Applications/Market (Filter select All Files to show Market app).
I added the JF6 build.prop to /system, replacing the JH2 version. I use root explorer to move the file on and off the SD internal.
Changed the permissions back to rw-r-r, using root explorer permissions. When the file is transferred back to the phone from the SD, the permissions will be rw-rwx-rx. Changed ownership back to root.root on the phone using terminal emulator:
$ su
# chown root.root /system/build.prop
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.

daverup said:
This did work for me. Thanks for the JF6 build.prop file.
I shut down the Market app, cleared its cache in Settings/Applications/Market.
I added the JF6 build.prop to /system, replacing the JH2 version.
Changed the permissions back to rw-r-r, and changed ownership back to root.root
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.
Click to expand...
Click to collapse
Trying to what you posted, but I don't see market listed under Settings/Applications or Settings/Applications/Manage Applications. How do I get to it, to clear cache?

rajendra82 said:
Trying to what you posted, but I don't see market listed under Settings/Applications or Settings/Applications/Manage Applications. How do I get to it, to clear cache?
Click to expand...
Click to collapse
Once you get to manage applications you need to change the filter to show all apps. Press the menu button > filter > all.

dontshakepandas said:
Once you get to manage applications you need to change the filter to show all apps. Press the menu button > filter > all.
Click to expand...
Click to collapse
Working now. This is great. Now with the last issue resloved, I can keep the new firmware around. This needs a sticky, with all these weekly firmware releases from samsung-firmwares showing up.

daverup said:
This did work for me. Thanks for the JF6 build.prop file.
I shut down the Market app, cleared its cache in Settings/Applications/Market.
I added the JF6 build.prop to /system, replacing the JH2 version.
Changed the permissions back to rw-r-r, and changed ownership back to root.root
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.
Click to expand...
Click to collapse
Can you post the commands used to do this for users who aren't as knowledgeable.

yes. walkthrough please?
would love to get this working, I don't want to have to flash back to original.

kyphur said:
Can you post the commands used to do this for users who aren't as knowledgeable.
Click to expand...
Click to collapse
Edited post with details

kyphur said:
Can you post the commands used to do this for users who aren't as knowledgeable.
Click to expand...
Click to collapse
You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell. If you get an error about unknown user/group, try chown 0.0 instead of root.root.
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Exploer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app (if running).
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.

One more thing,
The trick is working to fool the Market into believing that a JH2 phone is actually still on JF6.
This will probably also fool any program designed to upgrade the phone after checking the firmware version.
It would probably be a good idea to reflash via odin back to JF6 before doing any "released' upgrades via OTA or Kies.

daverup said:
One more thing,
The trick is working to fool the Market into believing that a JH2 phone is actually still on JF6.
This will probably also fool any program designed to upgrade the phone after checking the firmware version.
It would probably be a good idea to reflash via odin back to JF6 before doing any "released' upgrades via OTA or Kies.
Click to expand...
Click to collapse
Either that, or get a full flash of the newly released Froyo firmware with GPS Fix in September (hoping and praying), and flash it forward to the new stock version. Of course, not all parts of the system are fooled. Checking Settings -> About Phone, still shows the correct JH2 information.

Nice. Seems to have worked. Funny, it didn't work until after i installed/ uninstalled a couple items.

thanks!
For some reason I can't get any of this to stick. I'll rename the /system/build.prop to build.prop.bak with root explorer, but as soon as I leave the folder and come back to it the rename is undone.
debugging mode is on and root explorer says its mounted as r/w. tried changing permissions to rw-rwx-rx like you stated in your first intructional post, permissions do not change.
using adb shell only gives me the error that build.prop is read only.

staySICK said:
thanks!
For some reason I can't get any of this to stick. I'll rename the /system/build.prop to build.prop.bak with root explorer, but as soon as I leave the folder and come back to it the rename is undone.
debugging mode is on and root explorer says its mounted as r/w. tried changing permissions to rw-rwx-rx like you stated in your first intructional post, permissions do not change.
using adb shell only gives me the error that build.prop is read only.
Click to expand...
Click to collapse
I am guessing that your root privilages are not working. Does you phone give you a popup when you do su in ADB shell. If so, tell the phone to allow su privlages to ADB in that popup. If you do, ADB should not complain. If that doesn't work, you have to redo your rooting procedure, as something might be messed up there.

adb shell su does prompt the superuser request on my phone, which I've acknowledged.
Rooted using SuperRooter by designgears method.
hm... just tried a simple adb shell command (reboot), gave me an error too.
Sounds like a problem with my root access then? maybe I should unroot and switch to the previous version of superuser.

staySICK said:
adb shell su does prompt the superuser request on my phone, which I've acknowledged.
Rooted using SuperRooter by designgears method.
hm... just tried a simple adb shell command (reboot), gave me an error too.
Sounds like a problem with my root access then? maybe I should unroot and switch to the previous version of superuser.
Click to expand...
Click to collapse
Probably best to ask about this issue in that thread, as more knowledgeable folks might know how to overcome this.

rajendra82 said:
You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Exploer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app.
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.
Click to expand...
Click to collapse
This worked for me, one thing to note, when I ran the last command from Root Explorer "# chown root.root /system/build.prop" Root Explorer responded with
chown: unknown user/group root:root
But after restarting and installing/uninstalling a few apps Fandango shows up where it did not before.
Thanks.

[Q] busybox and nandroid issues

I have been experimenting with my new droid/milestone the past couple of days, odd problems which I am past now but still curious about.
Firstly after flashing the 2.1 sbf with rsd it will autoboot and screen slider will be there, then when I reboot, screen slider will be missing. This only happend when I flashed an sbf from the sbf site(2.1 uk version, not service), doing a factory reset didn't have any problem -could reboot as many times and slider would be there.... then suddenly after factory boot it would dissapear after first boot. Anyway solved this problem by installing screen mode widget after first boot after flash, solved problem, but still weird. Fixed this now but still curious about it.
Next, nandroid backup is missing from recovery menu, I have rooted and can execute root commands after typing "su" via Android Terminal emulator, so pretty sure is rooted. So why no nandroid? I thought I could do nandroid backup after rooting.
Next busybox won't install, tried the app, did the "searching system" for over an hour(not exagerrating), eventually gave up and uninstalled.
Trying to do a "manual busybox install" now, using this guide:
Busybox How-to? - Android Forums
Can't execute commands via usb/adb in recovery mode as the other guy suggested so been trying these commands both with terminal emulator on phone, and usb-debugging mode with windows shell. Using these I can go "su" and type "ls" to see files on my droid phone....but when I try to "mount /system" or /sdcard from windows I just get a print about mount options, when I try to "cat /sdcard/busybox > /system/xbin/busybox" I get a "file is read only" error.
I would like advice on how to install busybox, I would like to do it manually(because the app seems to not work for me, remember I waited over an hour while it "searched") and I want to learn to manually do stuff anyway. I tried to chmod /system/xbin too, but that didn't seem to change it from read only.
Also any thoughts on why nandroid backup is missing from my recovery menu even though my droid is rooted. I thought it was meant to appear.
I am still learning and researching, and appreciate any links or tips.

droidtech1 said:
Next, nandroid backup is missing from recovery menu, I have rooted and can execute root commands after typing "su" via Android Terminal emulator, so pretty sure is rooted. So why no nandroid? I thought I could do nandroid backup after rooting.
Click to expand...
Click to collapse
This is odd. Which OpenRecovery did you install? Androidiani? GOT? Or the "original" OpenRecovery? Are you aware, that you come into OpenRecovery by starting Recovery Mode and apply update.zip?
droidtech1 said:
Next busybox won't install, tried the app, did the "searching system" for over an hour(not exagerrating), eventually gave up and uninstalled.
Trying to do a "manual busybox install" now, using this guide:
Busybox How-to? - Android Forums
Click to expand...
Click to collapse
Using the app from the market worked like a charm for me. No idea, what might have gone wrong for you...
droidtech1 said:
Can't execute commands via usb/adb in recovery mode as the other guy suggested so been trying these commands both with terminal emulator on phone, and usb-debugging mode with windows shell. Using these I can go "su" and type "ls" to see files on my droid phone....but when I try to "mount /system" or /sdcard from windows I just get a print about mount options, when I try to "cat /sdcard/busybox > /system/xbin/busybox" I get a "file is read only" error.
Click to expand...
Click to collapse
For remounting, try "mount -o rw,remount /dev/block/mtdblock6 /system" and for undoing this, use "ro" instead of "rw".
droidtech1 said:
I would like advice on how to install busybox, I would like to do it manually(because the app seems to not work for me, remember I waited over an hour while it "searched") and I want to learn to manually do stuff anyway. I tried to chmod /system/xbin too, but that didn't seem to change it from read only.
Click to expand...
Click to collapse
You should download busybox and put the "busybox"-file in the directory /sdcard. After that do:
Code:
# su
# mount -o rw,remount /dev/block/mtdblock6 /system
# cp /sdcard/busybox /system/xbin
# cd /system/xbin
# chmod 755 busybox
# ./busybox --install
# mount -o ro,remount /dev/block/mtdblock6 /system
One thought at the end: How did you root?

I rooted by flashing "vunerable recovery" using RSD lite, copied milestone-root.zip to sd card, renamed it update.zip, rebooted into recovery mode, flashed update.zip from there.
I didn't realise I had to install something like open recovery, think because I remember not having to do that on my pulse? Anyway will try and install one of those now.
Thanks those commands at the end helped, actually managed to copy busybox to /system/xbin, however the 2nd last one "./busybox --install" gave me a load of errors -all being no such file or directory, for example "/usr/bin/wc: no such file"
about 30 of those path errors. Maybe the command path "./busybox" needs to be something else?

ah, okay. sorry, I thought you already installed an openrecovery. for many cool features you will need it (e.g. nandroid, for overclocking it's not a must but a nice-to-have). please don't use GOT, it's rather old already. androidiani is okay, I think.
I think your previous attempts to install busybox via the app etc. mixed up some internal links in the device. please reboot and try again (the above steps except the "cp ..."). seems like the app tried to install busybox to /usr/bin but failed... I hope this failed attempt will be fixed by a simple reboot. otherwise it would be great to have the output of:
Code:
# su
# ls /usr/bin

No I re-flashed my main sbf and also did a factory reset to do a clean start, only thing since that full wipe I have done is rooting in the method I described, installed the screenmode widget, textedit, and android terminal emulator.
I have no such file /usr, are you sure I should have this in droid/milestone?
Here is my full output of my root system using ls:
tmp
pds
cdrom
sqlite_stmt_journals
config
cache
sdcard
d
etc
system
sys
sbin
proc
init_prep_keypad.sh
init.rc
init.mapphone_umts.rc
init.mapphone_cdma.rc
init.goldfish.rc
init
default.prop
data
root
dev
perhaps "/usr" is a sub inside one of the above folders? I tried using "find" to find it but that command dosn't seem to work since it won't even find the ones I can see with ls

I found it, /usr is inside /system... so if busybox was moved to /system/xbin, I'm guessing the ./ means install it to the parent directory which was /system which /usr is also in.
The errors I got said no such file "/usr" so It seems like it is trying to install to the wrong directory.... perhaps the command should be "busybox --install" or "/busybox --install" I don't want to experiment and mess things up before your opinion on this.
*edit almost forgot, output of /system/usr is
keychars
bin
srec
keylayout
share
output of /system/usr/bin is
panic_daemon
gki_pd_notifier
nvm_daemon
clean_dex.sh
brcm_guci_drv
bplogd_daemon

This is really strange. Maybe your busybox-file is corrupt.
Where did you download the busybox-file?
Which sbf did you flash?
So for explanation-purposes: When you put an executable or script file in any directory, you can execute it by first making it executable ("chmod 755 /system/xbin/busybox"), changing to that directory ("cd /system/xbin") and then executing it by adding "./" in front of it. The dot slash always stands for the _current_ directory. The _parent_directory has two dots "../".
If you want, you may try:
# /system/xbin/busybox --install
instead of
# ./busybox --install
Or maybe try this one:
# /system/xbin/busybox --install -s /system/xbin
Last time, I installed busybox into the directory /data/busybox, which worked brilliantly, but this path turned out to be unpractical. So I wanted to reinstall it in a different directory. I removed everything from /data/busybox including the directory itself and tried to start the whole procedure with /system/xbin. But that time it protested, that there were no files in "/data/busybox/...". Conclusion: The last busybox-install affected the second one. When I remember correctly I rebooted after that and used the app from the market *g*

My main sbf I flashed was android 2.1(uk version).
I downloaded busybox 1.17.2(won't let me post url here), was from droidforums dot net.
I don't remember if I tried all of his commands, but the last one on that forum seems to have worked.. I think......... it was:
"busybox --install /system/xbin/"
After remounting with your commands and typing the above command, I didn't get any errors, I synced and rebooted and now when I "ls /system/xbin" it shows a bunch of files/names which look like busybox commands. When I type "busybox" it outputs a bunch of commands too... so I am guessing this means it has succesfully installed? I can't say I tried these before attempting install so I have no comparison but I assume I would have a different output if busybox wasn't installed.
So assuming it worked, why would
"busybox --install /system/xbin/" work, and
"/system/xbin/busybox --install" not?
I also managed to install open recovery and do a nandroid backup succesfully
I have another short question, not specific to android but happens in all terminals I use, windows and linux alike. Sometimes I cannot execute commands anymore and it just becomes text in the terminal(just re-echo'ing my text output, without executing any functions)... can't remember specifically when it happened on my windows or linux pc shells, but on my android it happens whenever I have to give "SU" permission to the terminal, I have to quickly close the terminal and reload it again to get su access. I'm sure there is a name for this "state" where you are locked out of using commands in the shell and just typing text but I can't find a way to get out of it(without closing and re-opening terminal), there must be some key combination to be able to execute commands again in the current terminal session. If you have any idea what I am talking about?
Thanks for all your help so far.

droidtech1 said:
My main sbf I flashed was android 2.1(uk version).
Click to expand...
Click to collapse
Don't want to try one of the 2.2?
droidtech1 said:
I downloaded busybox 1.17.2(won't let me post url here), was from droidforums dot net.
I don't remember if I tried all of his commands, but the last one on that forum seems to have worked.. I think......... it was:
"busybox --install /system/xbin/"
After remounting with your commands and typing the above command, I didn't get any errors, I synced and rebooted and now when I "ls /system/xbin" it shows a bunch of files/names which look like busybox commands. When I type "busybox" it outputs a bunch of commands too... so I am guessing this means it has succesfully installed? I can't say I tried these before attempting install so I have no comparison but I assume I would have a different output if busybox wasn't installed.
Click to expand...
Click to collapse
Yes, this sounds very much like installation was successful.
droidtech1 said:
So assuming it worked, why would
"busybox --install /system/xbin/" work, and
"/system/xbin/busybox --install" not?
Click to expand...
Click to collapse
typing "busybox" without the path in front of it worked, because busybox is in the directory /system/xbin, which is already in your $PATH-variable (try "echo $PATH"). So the command interpreter (shell) will automatically look up "busybox" in /system/xbin.
I had a look at the busybox syntax and it's actually
Code:
busybox --install [-s] [INSTALLDIR]
So you have to put the directory you want to install in at the end. That's what your last command makes use of
droidtech1 said:
I have another short question, not specific to android but happens in all terminals I use, windows and linux alike. Sometimes I cannot execute commands anymore and it just becomes text in the terminal(just re-echo'ing my text output, without executing any functions)... can't remember specifically when it happened on my windows or linux pc shells, but on my android it happens whenever I have to give "SU" permission to the terminal, I have to quickly close the terminal and reload it again to get su access. I'm sure there is a name for this "state" where you are locked out of using commands in the shell and just typing text but I can't find a way to get out of it(without closing and re-opening terminal), there must be some key combination to be able to execute commands again in the current terminal session. If you have any idea what I am talking about?
Click to expand...
Click to collapse
Sounds like this is just the state, when shell is busy, i.e. when the last process you started is still running and no prompt ($ or #) is displayed. You may kill the last process in linux using CTRL+C, which will hopefully bring back the shell prompt. No idea which shortcut replaces this on the milestone/droid. I never use any android terminals, but only the ADB-Shell: http://developer.android.com/guide/developing/tools/adb.html

I'm learning to build apps for android so I thought having 2.1 on my droid would be better for testing (instead of 2.2). I also have a Nexus-S with 2.3 and a tmobile-pulse with 1.5. So I want to keep the most native version on each phone since most consumers won't install custom roms, although some will get updates anyway.
I use my droid a lot when I am out and use the terminal a lot so having busybox too has given me more to play around with. I actually find my droid much better working on than the nexus s, love the keyboard and dpad.

[Q] Help with multiple KF2 Root/Unremoveable Programs

I don't know what I've done to my KF2. I have successfully rooted the device, and have even been in fastboot for something I tried (can't remember what, just that I was trying to properly root my device). But I have about 14 programs that won't remove off my device (they only show "Add to Favorites" on my device instead of the additional option to remove from device)? I cannot get into ES File Manager and delete them. The .apk's for these files are located in the system folder, and even when I mount root in ES File Manager, I can't delete any of the files in the folder.
I also have a lot of problems with my toolbars randomly flickering on and off. But nothing I've read and tried, except for restoring the device and rerooting it again fixes this problem. I've also looked at a lot of posts that tell me to do a command with the /data/local.prop file. But I don't have this file on my kindle. I've searched for it everywhere using ES File Manager. I do have a /data/default.prop file, however. But I can't use ADB commands on that file either.
So I was advised to get a factory cable so that I can boot into fastboot. But I can use KFFIRSTAIDE to get into that successfully. Can anyone tell me what I've done to my kindle, what programs, and what commands I need in order to fix this problem? I'm not an idiot; I successfully rooted 3 KF2's and a KFHD successfully before this monster of a device came along!

herrenfam said:
I don't know what I've done to my KF2. I have successfully rooted the device, and have even been in fastboot for something I tried (can't remember what, just that I was trying to properly root my device). But I have about 14 programs that won't remove off my device (they only show "Add to Favorites" on my device instead of the additional option to remove from device)? I cannot get into ES File Manager and delete them. The .apk's for these files are located in the system folder, and even when I mount root in ES File Manager, I can't delete any of the files in the folder.
I also have a lot of problems with my toolbars randomly flickering on and off. But nothing I've read and tried, except for restoring the device and rerooting it again fixes this problem. I've also looked at a lot of posts that tell me to do a command with the /data/local.prop file. But I don't have this file on my kindle. I've searched for it everywhere using ES File Manager. I do have a /data/default.prop file, however. But I can't use ADB commands on that file either.
So I was advised to get a factory cable so that I can boot into fastboot. But I can use KFFIRSTAIDE to get into that successfully. Can anyone tell me what I've done to my kindle, what programs, and what commands I need in order to fix this problem? I'm not an idiot; I successfully rooted 3 KF2's and a KFHD successfully before this monster of a device came along!
Click to expand...
Click to collapse
Well, if you can reboot into fastboot via KFFA, than no, you don't necessarily need a fastboot cable. Have you tried removing these programs via ADB? If you ADB shell into the device, does the command "su" work? System apps can't be uninstalled the normal way, you have to manually delete them from "/system/app/" yourself. But that's weird that you can't get ES to work. Which version of ES file explorer are you using? I know the new version requires you to not only turn root explorer on, but you have to tap two radial dials to switch it from "/system" from RO (read only) to RW (read writable).
Hope this helped

Ph0enix_216 said:
Well, if you can reboot into fastboot via KFFA, than no, you don't necessarily need a fastboot cable. Have you tried removing these programs via ADB? If you ADB shell into the device, does the command "su" work? System apps can't be uninstalled the normal way, you have to manually delete them from "/system/app/" yourself. But that's weird that you can't get ES to work. Which version of ES file explorer are you using? I know the new version requires you to not only turn root explorer on, but you have to tap two radial dials to switch it from "/system" from RO (read only) to RW (read writable).
Hope this helped
Click to expand...
Click to collapse
What command(s) would I use to remove these programs? The only command I know is "ADB SHELL su". I am not an idiot at computer software, but I was absent on the day they handed out the intelligence on DOS commands.
And how would I get rid of the associated program files? Or do I just leave them on the drive?
What I would really like to do is unroot the device (which seemed to screw it up last time I tried it), restore to factory defaults as to erase all this gibberish, and restart from fresh, with a clean slate and then a clean root. Can that be done? How would I accomplish that? Like I said, it seemed that I the problems with the programs not uninstalling started with the restoring of the device, be it by unrooting it or by restoring the device to factory defaults on the kindle.
PS: yes, I can get into SU on ADB on my computer. I just don't know where to go from there. And my ES File Explorer is V. 3.0.9.0. I looked in the settings and could not find a option to change file to RW.

herrenfam said:
What command(s) would I use to remove these programs? The only command I know is "ADB SHELL su". I am not an idiot at computer software, but I was absent on the day they handed out the intelligence on DOS commands.
And how would I get rid of the associated program files? Or do I just leave them on the drive?
What I would really like to do is unroot the device (which seemed to screw it up last time I tried it), restore to factory defaults as to erase all this gibberish, and restart from fresh, with a clean slate and then a clean root. Can that be done? How would I accomplish that? Like I said, it seemed that I the problems with the programs not uninstalling started with the restoring of the device, be it by unrooting it or by restoring the device to factory defaults on the kindle.
PS: yes, I can get into SU on ADB on my computer. I just don't know where to go from there. And my ES File Explorer is V. 3.0.9.0. I looked in the settings and could not find a option to change file to RW.
Click to expand...
Click to collapse
The commands to remove bloatware and stuff (in this case, apps) would be:
Code:
adb shell
su
mount /system
rm /system/app/nameofapp1.apk
rm /system/app/nameofapp2.apk
rm /system/app/nameofapp3.apk
reboot
If a clean slate is what you want, then you can use this tool here to flash three stock Kindle partition images (boot.img, recovery.img, and system.img) to your Kindle via fastboot. The images aren't of the latest firmware, but I don't think OTA updates are disabled, so you can just let your Kindle auto update over wi-fi.
If "su" works in the ADB shell, then I guess you are rooted. I don't know what to say from there, except to backup whatever data you can and start fresh.

Ph0enix_216 said:
The commands to remove bloatware and stuff (in this case, apps) would be:
Code:
adb shell
su
mount /system
rm /system/app/nameofapp1.apk
rm /system/app/nameofapp2.apk
rm /system/app/nameofapp3.apk
reboot
If a clean slate is what you want, then you can use this tool here to flash three stock Kindle partition images (boot.img, recovery.img, and system.img) to your Kindle via fastboot. The images aren't of the latest firmware, but I don't think OTA updates are disabled, so you can just let your Kindle auto update over wi-fi.
If "su" works in the ADB shell, then I guess you are rooted. I don't know what to say from there, except to backup whatever data you can and start fresh.
Click to expand...
Click to collapse
Thanks a great deal. Where is the program to flash the three stock .img files so I can have a from-the-beginning kindle? I've already got the only thing I need from the device - a list of the third-party apps and where I downloaded them from.

herrenfam said:
Thanks a great deal. Where is the program to flash the three stock .img files so I can have a from-the-beginning kindle? I've already got the only thing I need from the device - a list of the third-party apps and where I downloaded them from.
Click to expand...
Click to collapse
...I forgot to post the link, didn't I?
Here it is: http://forum.xda-developers.com/showthread.php?t=2096888
>>>Sent from my homebuilt TARDIS running Android 4.0.3... or maybe it's a rooted Kindle Fire HD<<<

Now What?

Now that we have root, what things are we going to be focusing on next? Probably Safestrap and ROMs. What cool things have you guys found with root?

Vlasp said:
Now that we have root, what things are we going to be focusing on next? Probably Safestrap and ROMs. What cool things have you guys found with root?
Click to expand...
Click to collapse
Well for one thing if you disabled/uninstall Unified Search, it allows google search to work correctly in the launcher, also without root you can replace the amazon keyboard with the google keyboard and get voice search.
Edit: We need to probably install Google play services properly to get Google Play Games to work correctly but I am not sure.

The ability to install apps depending on root is awesome.
If you are asking for wishes, then I wish I could use CyanogenMod on this device.

I have de-amazonified my tablet a bit. Cant wait to get a custom rom installed on it though.

we need a safe list with what apps can we delete... i did the same but i don't know for sure what to delete and what to keep... i mention that i don't use amazon apps nor i logged in..
Sent from my KFFOWI using XDA Forums

balanigga said:
we need a safe list with what apps can we delete... i did the same but i don't know for sure what to delete and what to keep... i mention that i don't use amazon apps nor i logged in..
Sent from my KFFOWI using XDA Forums
Click to expand...
Click to collapse
For the moment......
http://forum.xda-developers.com/showpost.php?p=63605889&postcount=77
If wants to remove more can give chmod 000 to apk & reboot before delete

What about reassigning the home button to a different launcher?

xT29c said:
What about reassigning the home button to a different launcher?
Click to expand...
Click to collapse
Just install another launcher and remove FireLauncher from system.

csolanol said:
Just install another launcher and remove FireLauncher from system.
Click to expand...
Click to collapse
Oh, nice. Okay, thanks!

csolanol said:
Just install another launcher and remove FireLauncher from system.
Click to expand...
Click to collapse
how can i do this? thanks in advance
Edit: nevermind I found it, thanks anyway

joelwylde said:
how can i do this? thanks in advance
Click to expand...
Click to collapse
You can use titanium backup, and remove it like that. I would make a backup firs though just in-case.
Also, I need help trying to unhide the firelauncher process. I have the command here "adb shell pm unhide [package:com.amazon.firelauncher]"
But I need the other command first so ADB can talk to my tablet. Because I ran the command, and it just says "true" when it should say "false".

joelwylde said:
how can i do this? thanks in advance
Click to expand...
Click to collapse
Working Launcher replacement thanks to @diegocr and @Awesomeslayerg ! Here's the steps:
1. See @diegocr post at http://forum.xda-developers.com/showpost.php?p=63599598&postcount=23 and download "boot-firelauncher.img"
2. Enable USB debugging
3. Install your launcher of choice!
4. On your computer, run
adb reboot bootloader
Click to expand...
Click to collapse
5. Once your tablet reboots in to fastboot, run on your computer (if you are not in the same directory as boot-firelauncher.img, put the full path):
fastboot boot boot-firelauncher.img
Click to expand...
Click to collapse
6. Tablet will reboot
7. Once booted open an adb shell:
adb shell
Click to expand...
Click to collapse
8. To back up the existing app, run:
cp /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk /sdcard/Download/com.amazon.firelauncher.apk
Click to expand...
Click to collapse
9. Then nuke it!
rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk
Click to expand...
Click to collapse
10. Now, run to restart your device:
reboot
Click to expand...
Click to collapse
Confirmed working on my tablet with FireOS 5.0.1.
Enjoy!
Forget all the formatting problems
Sent from my KFFOWI using Tapatalk

If you are already rooted you don't need to do all that stuff.
Just adb shell
su
mount -o remount,rw /system
rm -r /system/priv-app/com.amazon.firelauncher or whatever the package is called.
Reboot and it's done.
Remember to install a launcher before this.

csolanol said:
If you are already rooted you don't need to do all that stuff.
Just adb shell
su
mount -o remount,rw /system
rm -r /system/priv-app/com.amazon.firelauncher or whatever the package is called.
Reboot and it's done.
Remember to install a launcher before this.
Click to expand...
Click to collapse
Will this work if I hid the process with ADB before hand? If not, how do I unhide it? What command would I use before "adb shell pm unhide [package:com.amazon.firelauncher]"

Don't know, try if it works hiding, but I doubt it.

I want to replace the hosts file with the one of my Lenovo S660 (China phone). The S660 hosts file is about a mile long and has entries like "0.0.0.0 bad.ad.server" - a very basic but effective way to avoid a lot ads, even at apps. I have not yet took a closer look but I think I would create a mix of both files for the fire.
So, what are the steps?
I have done similar things to my rooted Sony Experia Tipo concerning modifying files at /system, which is mounted RO as default. So I remounted it RW with ES-Explorer, modified what I had to and mounted RO with ES-Explorer again.
I wonder, if this is ok, because of the security means the fire/android has.

I took a chance and I was successfull.
I attached the unchanged hosts file from my Lenovo S660 /system/etc/ as hosts.lenovo.zip file. The fire hosts has just 1 line: 127.0.0.1 localhost. The lenovo's hosts has 25858 lines.
Code:
- unzip hosts.lenovo.zip -> you get host.lenovo
- rename hosts.lenovo to hosts
- connect fire
- adb push hosts /data
- adb shell
- $ su -
- # cd /data
- # chmod 644 hosts
- # exit
- $ exit
- ES Explorer
- Enable root explorer
- remount /system rw
- go to /data
- mark hosts
- cut hosts (to memory)
- go to /system/etc
- mark hosts
- rename hosts to hosts.old
- insert hosts from memory
- remount /system ro
- exit ES Explorer
done.
should work, use at own risk.
Note: You cannot chmod 644 at /mnt/sdcard1 because it is vfat there, that's why you use /data.
Note: You cannot write to /system/etc while at adb shell, even if it is mounted RW, that's why you have to use ES Explorer which will ask you to choose the path with android overlay window - which makes it work (at least my experience).
If you have apps which showed ads before, then you might keep on seeing the very last forever. Or a broken link sign. Or even a popop with broken link sign. Or your ads hosts is missing at the lenovo hosts file and you keep on seeing ads. There even my be websites you cannot visit anymore - which I have not yet experienced, but the risk exists, or will come.
If interested, take a look at http://winhelp2002.mvps.org/hosts.htm for more information and use for your windows or linux pc.
If you don't like it you can go back, you have a copy of your old hosts file.

I want to replace the hosts file with the one of my Lenovo S660 (China phone). The S660 hosts file is about a mile long and has entries like "0.0.0.0 bad.ad.server" - a very basic but effective way to avoid a lot ads, even at apps.
Click to expand...
Click to collapse
Check out the adaway app (open source). It blocks ads through the host file just like you're doing except it puts the host file in place for you, combines host files from a couple different sources (running de-duplication on them) & auto updates your host file as new ad severs are added or removed. Absolutely beats rolling your own host file manually.

That is new information to me, thanks.