Database Develop

Cannot install Debian on JF 1.5 US? Help?

Hey, Im following
http://www.androidfanatic.com/cms/community-forums.html?func=view&catid=9&id=2248
For how to set debian up. However chmod 4755 * fails for me saying operation not permitted when I am cd /sdcard/debian I read through a couple other posts on google and the site above where it says people can on versions pre 1.5 but once on 1.5 US it breaks the su whitelist some?
Anyways, Anyone have some ideas for me, as the google trail went cold for me as the people who had this issue was already at the end of the threads with no resolve or joy. Thanks. =)

too much in 'yo chmod!

hey i have set up mine. you just gotta forget about the chmod and just skip it and do the rest of the steps then type exit. then once it reboots, just type
su
cd /sdcard/debian
sh bootdeb
then it should be running

Yea I thought so too on the chmod step, so I tried going to the next, the installer.sh and said not allowed or something.

I tried running boot debian and so, and it came up with the load screen, then it had a chmod issue and then the G1 restarted. So what am I missing here? =/

hmm, im not entirely sure. when i installed it i simply
su
cd sdcard/debian
chmod 4755 *
su sh ./installer.sh
exit
su
cd sdcard/debian
sh bootdeb

Well I was reading other posts, Could it be a issue that Im already running apps off the EXT2 part of my SD card? I have the debian files on the FAT32 area. I saw some people saying that might be a cause of the issue?

if your debian dir is on fat32, you need to delete the first line of installer.sh script

Ok did that and the installer.sh ran did alot of not found errors then when I tried to bootdeb it looked like it was trying to load, then it rebooted the G1. =/
Any other ideas? Also if I wanna try to uninstall the work it did, what does it create to delete?

Mysticales said:
Ok did that and the installer.sh ran did alot of not found errors then when I tried to bootdeb it looked like it was trying to load, then it rebooted the G1. =/
Any other ideas? Also if I wanna try to uninstall the work it did, what does it create to delete?
Click to expand...
Click to collapse
Which image are you using? There's one for fat32 and one for ext2. Try this: download fat32 version http://www.androidfanatic.com/cms/unofficial-app-repo.html?func=fileinfo&id=21
you may need to remount when entering the following commands in the terminal
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
place zip file on sdcard. go to terminal and enter:
su
unzip "whatever_your_debian_file_is_named".zip (not sure what its called)
cd "whatever_your_debian_file_is_named"
cp installer.sh /sdcard/gscript
then go to Gscript and load installer.sh, before you save, delete the line that says "./fsrw"
then save this edited script as installer1.sh
go back to terminal
cp /sdcard/gscript/installer1.sh /sdcard/debian
cd /sdcard/debian
su
sh ./installer1.sh
sh ./bootdeb
if that doesnt work out try rebooting and doing these commands
cd /sdcard/debian
sh ./bootdeb

to delete, go to debian directory then
rm -r debian
afaik, all the data from debian is self-contained in debian.img

Ill try that, btw yea I have that file you linked to. But before I do this, the stuff your mentioning, wont affect the fact that I have my apps installed to the SD right? Mounting and unmounting things.

Mysticales said:
Ill try that, btw yea I have that file you linked to. But before I do this, the stuff your mentioning, wont affect the fact that I have my apps installed to the SD right? Mounting and unmounting things.
Click to expand...
Click to collapse
No, your apps should be safe. If you're using the link I posted, you need to put debian on /sdcard which is fat32
you're apps2sd should be mounted at /system/sd and should be unaffected by your debian installation/uninstallation.
I'm not sure if remounting /system is required, but i think it allows you permissions so you can use the utilities in /system/bin. I would remount just to save myself time.
Btw, I could not chmod my debian directory, but debian runs fine for me.

jonnybueno said:
to delete, go to debian directory then
rm -r debian
afaik, all the data from debian is self-contained in debian.img
Click to expand...
Click to collapse
Oops, my bad. Should be:
cd /sdcard or cd /system/sd depending on where you put your debian directory
the you can
rm -r debian

Jonny your great. =) The remounting thing worked! Then ran the installer, got alot of not found, but after that all, I booted into Debian, and did the onetime.sh to set the unix pw.
(Which for the record to anyone in the future doing a search on this once your in debian, do cd scripts and enter that folder and type sh onetime.sh )
Now onto the next step and adding a GUI Which gonna attempt that all now.
Edit: And Grr... not gonna try to do the rest of the repos on EDGE connection.. Gotta wait till I get home. =( (Wifi rules for linux starts lol)

I think the image we installed is only 750MB so from what I've read, it is advisable to resize your debian img. Thats another world of brain hurt for me... but there is this guy with this thread who is offering to upload his custom image.
http://forum.xda-developers.com/showthread.php?t=528262
5 more votes by the end of the day and maybe he'll upload it.

Well... I already did the resize heh. Got a 2.3GB image on right now, which fits on my 4GB, since I have a 1GB EXT2 Partition and rest is fat32.
I used ubuntu to make a image and mount both images and copied the data from one into the other, then did the tasks after I booted debian again to get everything smooth again. =) But I wont stop him from uploading his image if it has a GUI already installed, which is what im after atm. =)

Update, So far having a lil issue getting the desktop to show up on VNC, however I did get other tasks done and stable running. Also came across this post which is vital as the default install seems to want to give you a repo that 404s too much so before you start your tasks, after you install debian and get into it, do this stuff.
ZilverZurfarn said:
For those (like me) who get errors when apt-get'ing thightvncserver and/or lxde:
(from the thread at androidfanatic.com)
instructions
cd /etc/apt
nano sources.list
now add
deb http://ftp.debian.org/debian lenny main contrib non-free
deb-src http://ftp.debian.org/debian lenny main contrib non-free
after the first one
then hold down the trackball and hit o
then hit return (to save the new sources.list)
then hold the trackball and hit x (to exit nano)
then type
apt-get update
apt-get install tightvncserver
apt-get install lxde
That did the trick for me at least.
/Mats
Click to expand...
Click to collapse

yeahhh
now my problem is that debian is restarted all time
error
chroot: can't change root directory to /data/local/mnt: No such file or director
y

Well While mine worked, sorta, I just went with the 1 click debian install thread, made life a lil easier. Heh.

How do you install new HTC_IME?

Hi I was trying to install the new HTC_IME on my phone right now I am currently using 2.0 and I tried to install with appsinstaller and it didn't work. So is there a way to do it threw terminal emulator, or threw recovery?
I don't use adb cause I tried setting it up and it didn't work.
So somebody please give me a good reply! Thanks!

try with astro

if astro doesn't work try this.
you must have adb working. adb does wonders. works every time. top cmds is for adb and bttm is terminal on phone.
Adb remount
Adb push HTC_IME.apk system/app
Adb shell rm system/sd/app/HTC_IME.apk
Adb shell rm data/app/HTC_IME.apk
Adb shell reboot
Or from terminal
Mount -o rw,remount -t yaffs2 dev/block/mtdblock3 /system
Cp *yourdir*/HTC_IME.apk system/app
rm data/app/HTC_IME.apk
rm system/app/HTC_IME.apk
reboot
PHP:
since you dont use adb, if your using any kind of windows let me know and i can personally walk you thru an adb setup. i have encountered the worst of worst mess ups. durrr lol... fosho . . . . .

that doesnt make any sense, why are you removing HTC_IME right after you're done pushing it?
You need three files for HTC IME to work, HTC_IME.apk, Clicker.apk (both of those in /system/app or /data/app) and libt9.so (in /system/lib)
Assuming you place all three in C:\
Code:
adb remount
adb push C:\libt9.so /system/lib
adb push C:\Clicker.apk /system/app (or /data/app if you don't have space)
adb push C:\HTC_IME.apk /system/app (or /data/app if you don't have space)
no need to reboot, just give it time to finish dexopting (about a minute) then go to Settings>Locale & Text and enable (checkmark) Touch Input, disable Android Keyboard if you wish.
About where to get the files? search, but it's easier if you search inside Cyanogen's (version 4.0.4 and below) roms and pull them from those.

rockin_mod said:
if astro doesn't work try this.
you must have adb working. adb does wonders. works every time. top cmds is for adb and bttm is terminal on phone.
Adb remount
Adb push HTC_IME.apk system/app
Adb shell rm system/sd/app/HTC_IME.apk
Adb shell rm data/app/HTC_IME.apk
Adb shell reboot
Or from terminal
Mount -o rw,remount -t yaffs2 dev/block/mtdblock3 /system
Cp *yourdir*/HTC_IME.apk system/app
rm data/app/HTC_IME.apk
rm system/app/HTC_IME.apk
reboot
PHP:
since you dont use adb, if your using any kind of windows let me know and i can personally walk you thru an adb setup. i have encountered the worst of worst mess ups. durrr lol... fosho . . . . .
Click to expand...
Click to collapse
What do you mean by *yourdir*? Lol sorry kinda of a noob to this

Brandice128 said:
What do you mean by *yourdir*? Lol sorry kinda of a noob to this
Click to expand...
Click to collapse
First of all thank you for taking my advice , the Q & A section is the best place for all your questions about android . Seeing that your new here it would be wise that you do some research on the following
ADB
zip7
rar
cyanogen's 1.4 recovery
terminal commands
and so on . There's a lot but as you search you will find them ...
NOW the yourdir question ,it's on your SDcard where you downloaded your htc_ime.apk , if it's on the root of the sdcard (not in any folders) then just use cp sdcard/HTC_IME.apk or if you downloaded it then it's in your download folder then you do cp sdcard/download/HTC_IME.apk

adb remount
adb install directoryofyourfile\HTC_IME.apk
Click to expand...
Click to collapse
worked for me

How to remove (live)wallpaper

I can't find a thread for this, but how would I delete stock wallpapers or stock live wallpapers. I prefer to pick and choose which ones to remove to try and save a little space.
I have a rooted N1 with Cyan's mod. I'm comfortable using ADB, just don't know the proper commands, locations of wallpapers or names of specific files.

Me too. want to know where the files are located.

Me three. I've searched around in nearly every directory and cannot find them. I would like to remove the stock htc wallpapers to save space.

adb shell rm /system/app/LiveWallpapers.apk
adb shell rm -r /data/data/com.android.wallpaper
adb uninstall com.android.wallpaper
adb shell rm /system/app/MagicSmokeWallpapers.apk
adb shell rm -r /data/data/com.android.magicsmoke
adb shell rm /system/app/VisualizationWallpapers.apk
adb shell rm -r /data/data/com.android.VisualizationWallpaper
adb uninstall com.android.VisualizationWallpaper
adb shell rm /system/app/Mode10Wallpapers.apk
LiveWallpapers.apk = contains nexus and water live wallpaper and some other i cant remember
wallpapers are located inside of /system/framework/framework-res.apk and does require slight knowledge of how to edit framework files

hey i follow the first adb then i got this (?) then no go???what i need to do after (?)

vinny.1967 said:
hey i follow the first adb then i got this (?) then no go???what i need to do after (?)
Click to expand...
Click to collapse
Check if ur phone is detected by adb (adb devices). Then do an adb remount and the run the above adb commands

My device is detected but i try to put in the above commands I it says that its a read-only file system.

Static wallpapers (except the single default wallpaper) are stored in your launcher or in CM6 or Kang-o-rama a special wallpapers app.
It's much easier to download ES File Explorer, turn on root functions, mount system as read/write (same menu) and selectively delete the files you want from /system/app/ and /data/data/ as above.
But really, you're not going to save any user space as all because, for the most part, you're deleting stuff from /system which you don't otherwise need space on.

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.