Database Develop

Help using Terminal

I'm currently using Dwangs donut ROM.
For some strange reason my Terminal Emulator is "missing".
There is no icon for it in my app tray.
Market shows it as installed, but cannot open it nor uninstall it.
I have now installed Better Terminal Emulator Magic. What commands do I need to enter to completely remove Terminal Emulator from my system, so that I can try reinstalling it from the Market?
I hope I've made myself clear - if not please feel free to ask for clarification!

Look in the Development Tools or Spare Parts. I've seen a couple builds where it ends up in there.

qwerty3656 said:
Look in the Development Tools or Spare Parts. I've seen a couple builds where it ends up in there.
Click to expand...
Click to collapse
Just looked in Spare Parts - not there. Can't find Development Tools on my phone.

To remove it do this in the recovery console
mount system
rm /system/app/Term.apk (i think that is the name for it)
reboot

david1171 said:
To remove it do this in the recovery console
mount system
rm /system/app/Term.apk (i think that is the name for it)
reboot
Click to expand...
Click to collapse
Ah, now we're getting somewhere (sort of!)
I've done that, but get the response:
rm: cannot remove ' /system/app/Term.apk' : No such file or directory

that means its not there or its spelled wrong..
try using /system/sd instead of system
also, maybe clearing the market cache would work

B-man007 said:
that means its not there or its spelled wrong..
try using /system/sd instead of system
also, maybe clearing the market cache would work
Click to expand...
Click to collapse
Tried both of these - no joy :-(
1. Same response as before
2. Terminal Emulator still showing as installed (but Open & Uninstall buttons greyed out), even after clearing Market cache.

well if you dl one of cyanogens roms, you can pull the apk from there and push it to system

Yea or adb install -r

if it is not in /system/app then you can drop it in there with these commands, make sure that the .apk is in the root of your sdcard
Code:
mount sdcard
mount system
cp /sdcard/Term.apk /system/app/
reboot

Google Maps with Nav: For NoObs! For Cyanogen ROM's (works!)

First thank you Followinginsanity for breaking the code!
Credit for this break down goes to Paul22000 for his write up. I just added all the links and my input which worked on 5 of my buddy's phones.
Please let me know if I am stepping on anyone's toes and I will remove this.
go to this page ( http://forum.xda-developers.com/showthread.php?t=582656&page=8 ) and download build.props.zip then open and place on the root of the sdcard.
then go to: http://forum.xda-developers.com/showthread.php?t=583627 and download the link on the first page. open it and go to the apps folder in the zip and copy the Maps.apk and place on the root of the sdcard.
- Make sure before you start to make a nandroid backup.
A) Place 3 files on sdcard (build.prop, build.trout.prop, Maps.apk)
B) Terminal (on phone):
su
ash
mount -o remount,rw /system
cp /system/build.prop /sdcard/build.prop.backup
cp /system/build.trout.prop /sdcard/build.trout.prop.backup
cp /sdcard/build.prop /system
cp /sdcard/build.trout.prop /system
cd /system/app
rm *Maps*
rm *maps* ( an error is ok go on, just need to make sure all are deleted. So both Maps and maps done.)
cd /system/sd/app
rm *maps*
rm *Maps* ( an error is ok go on, just need to make sure all are deleted. So both Maps and maps done.)
cd /system/sd/dalvik-cache
rm *maps*
rm *Maps* ( an error is ok go on, just need to make sure all are deleted. So both Maps and maps done.)
reboot
C) Terminal:
su
mount -o remount,rw /system
install /sdcard/Maps.apk /system/app/
D) Open "Maps" on your phone
Directions -> Put end point -> Go -> "Navigate" under "Show on Map" -> Install voice etc
(Must have GPS on and data connection active)
- Not there? Go to the market and download Google Voice. install... open and then exit. go back to Maps and try - Directions -> Put end point -> Go -> "Navigate" under "Show on Map" Agian.
(If "Navigate" doesn't show up, something went wrong.)
E) To get other apps back to normal (if stuff broke):
su
ash
mount -o remount,rw /system
cp /sdcard/build.prop.backup /system/build.prop
cp /sdcard/build.trout.prop.backup /system/build.trout.prop
reboot

this is much faster.. its a update.zip and it supports the builds so facebook and handcent work just fine..
http://forum.xda-developers.com/showthread.php?t=583684

Rock on. Just wanted to put something up for all the new people who tried all the other's and couldn't get them to work.

Jamison904 said:
Rock on. Just wanted to put something up for all the new people who tried all the other's and couldn't get them to work.
Click to expand...
Click to collapse
lol yuh iw as there and damn i was there wit so many issues lol..but im glad people are gettin helped and thank you as well for takin ya time out to write all that **** lol.. i woulda just been like egh fucc it to lazy lol..thanks

navigate dissappeared after upgrading to cyan 4.2.5

You could either try reinstalling it or some say you can uninstall Google Voice and reinstall it.
I upgraded from 4.2.4 to 4.2.5 just fine and kept it, but I'd give it a reinstall. Couldn't hurt or try the google voice trick.

nice! good to go after first install, no problems yet!

Works so nice. You devs are geniuses. Love it. Thx so much.

no prob yet but on my phone it says my firmware version is 2.0 and my mod version is cyanogenmod 4.2.3.1 build number esd20, is this right? prior to this i was 1.6 running cyanogenmod 4.2.5
edit**
just did this and it changed everything back to normal
E) To get other apps back to normal (if stuff broke):
su
ash
mount -o remount,rw /system
cp /sdcard/build.prop.backup /system/build.prop
cp /sdcard/build.trout.prop.backup /system/build.trout.prop
reboot

my phone says 1.6 and cyan 4.2.4 but i have all the features of 4.2.5 and yes i have google voice installed

jonnunez said:
no prob yet but on my phone it says my firmware version is 2.0 and my mod version is cyanogenmod 4.2.3.1 build number esd20, is this right? prior to this i was 1.6 running cyanogenmod 4.2.5
edit**
just did this and it changed everything back to normal
E) To get other apps back to normal (if stuff broke):
su
ash
mount -o remount,rw /system
cp /sdcard/build.prop.backup /system/build.prop
cp /sdcard/build.trout.prop.backup /system/build.trout.prop
reboot
Click to expand...
Click to collapse
the problem with this is when you reinstall the backup's you will lose Google Nav. But your old apps work fine again. There is something in the build.prop and build.trout.prop that Google Nav looks for. Once you replace the new ones with your backup's, your back to square one. Might not do it right away but after a few minutes Nav is gone.

jj71787 said:
navigate dissappeared after upgrading to cyan 4.2.5
Click to expand...
Click to collapse
I have to redo this everytime I upgrade. It messes with the build.prop as I mentioned above. Until Cayogen puts out 2.0, we will have to keep messing with Nav to keep it when updating.

L
Jamison904 said:
the problem with this is when you reinstall the backup's you will lose Google Nav. But your old apps work fine again. There is something in the build.prop and build.trout.prop that Google Nav looks for. Once you replace the new ones with your backup's, your back to square one. Might not do it right away but after a few minutes Nav is gone.
Click to expand...
Click to collapse
Ahh your 100% right, woke up this morning and navigate was gone!

jonnunez said:
L
Ahh your 100% right, woke up this morning and navigate was gone!
Click to expand...
Click to collapse
oooooooooh..dude... i just follow you did the part E...

I get file exist at these two steps
cp /sdcard/build.prop /sytem
cp /sdcard/build.trout.prop /system
And I get cannot delete read-only at
rm *Maps*
What am I missing?

jonnunez said:
L
Ahh your 100% right, woke up this morning and navigate was gone!
Click to expand...
Click to collapse
hey man . i find a way to fix our mistake..
you can simply edit one line in your build.trout.prop file found in the system directory on your G1.
The edit is simply changing the ro.build.fingerprint line to:
ro.build.fingerprint=verizon/voles/sholes/sholes:2.0/ESD20/17572:user/ota-rel-keys,release-keys
then it works good..facebook works .. handcent works .. and look into about phone..back to the normal..1.6 tmo G1 drc83

I ended up finding this blog. I did the manual install and then installed Google Voice and everything is working perfectly for me.

FireBrush said:
I get file exist at these two steps
cp /sdcard/build.prop /sytem
cp /sdcard/build.trout.prop /system
And I get cannot delete read-only at
rm *Maps*
What am I missing?
Click to expand...
Click to collapse
You must of forgot to type "su" then press enter when you first started the script.

everyone listen up!
follow the instruction..finally you got map2.0,but look into your setting-about phone..it shows 2.0 not 1.6 tmo g1..i think thats why we cant use facebook and handcent..
just put these 2 build.trout.prop and build.prop in your phone system instead
it shoud works ..everything back normal..and nav works just fine

Can anyone comment if this works in the UK - I have tried a number of ways and none seem to work,
I am using Cyanogens latest Rom and followed the instructions to the letter...
Just get the show on Map options nothing more, nothing less

Issue with market and apps

Hey guys...
I bought a new mini-SD card for my rooted G1. I have the latest CM on it. So now i decided to install my nandroid-backup.. but now i have a problem with downloading all of my old apps from android market. In the market it says that all of my apps are installed, though they aren't. In the app-list of my phone my old apps are still shown and when i click on them it says: This App is not installed on your phone (sorry i'm using a german g1, so i have to translate the messages). So as you can see, my problem is that I can't download any of my old apps from market and i can't delete those entries or like the "rest of the app thats still on my phone". Any ideas ? I don't want to factory reset my phone... cause i love the way it is now (except this issue haha)

Try this. There is a similar issue there the apps don't exist but the Market DB still does, which gives you the problem of not being able to install but cannot uninstall it, because it doesn't exist. Below should help you out.
Code:
Type - mount -o remount,rw /dev/block/mtdblock3 /system (enter)
Type - rm /data/data/com.android.vending/databases/* (enter)
Type - reboot (enter)
Words in bracket are instructions and not to be typed.

BusyBoX

I have busybox 1.6 on my captivate i see on www.busybox.net 1.17.3 is out. I have downloaded it from the site and its a tar file with a folder with a whole bunch of folders and files. How do you install this?

Are you familiar with the phrase, "if it isn't broken, don't fix it?"
I advise you to heed its warning.
But if you must proceed, a quick google search for "how to install busybox manually" brings up this very good result: http://www.droidforums.net/forum/droid-2-hacks/82573-busybox-manual-install-how-guide.html
Edit: By the way, love the avatar. Great album.

Yes i understand if its not broke don't try to fix it but i'm a OCD updater! Would there be any advantages of updating it? P.S. I saw Megadeth and Slayer a month ago they rocked!

Only advantages I can see are having a couple more bug fixes and maybe 4-5 new commands built in.

Download Busybox-1.17.2 HERE
Extract busybox to your SD Card
Make sure you are in PC Mode and Debugging is enabled in Applications options
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/busybox /system/xbin/
cd system/xbin
busybox --install /system/xbin/
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
sync
reboot
You can also use Root Explorer or whatever file browser you may use to copy busybox to your system/xbin folder. Some people use system/bin but I prefer xbin...just a habbit.
Click to expand...
Click to collapse
Ya, I read that and got really scared.
What is PC mode and where do you type these commands? (Vista user)

Ok, figured out how to type in the commands and stuff, but I get stuck on the "cp /sdcard/busybox /system/xbin/" part, I get "cp: not found" I tried lookin up other methods and I keep getting stuck at the same part - trying to move the folder to the xbin folder. adb push gives me the same error - adb: not found.
any help would be appreciated.

Cruton502 said:
Ok, figured out how to type in the commands and stuff, but I get stuck on the "cp /sdcard/busybox /system/xbin/" part, I get "cp: not found" I tried lookin up other methods and I keep getting stuck at the same part - trying to move the folder to the xbin folder. adb push gives me the same error - adb: not found.
any help would be appreciated.
Click to expand...
Click to collapse
Are you rooted? If your answer is yes, just download Busybox from the market and let the app do the installing for you.

miztaken1312 said:
Are you rooted? If your answer is yes, just download Busybox from the market and let the app do the installing for you.
Click to expand...
Click to collapse
Brilliant! Sooo much easier, but I'm not NAND unlocked, I'm z4rooted so it wouldn't install. Tomorrow I'll see if I can root through NAND.
I'll break you yet AT&T!

Cruton502 said:
Brilliant! Sooo much easier, but I'm not NAND unlocked, I'm z4rooted so it wouldn't install. Tomorrow I'll see if I can root through NAND.
I'll break you yet AT&T!
Click to expand...
Click to collapse
I think you're seriously confused. The Captivate isn't a NAND locked phone. Generally when you root, busybox is installed. (I think. At least it always was for me.) You could also try installing Titanium Backup and have that install busybox for you.

[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.