[EVO 4G Android Development] jorge_moran_jams:
I'm having problems... I've been trying to debug and now I think I know what the problem is.

I tried starting debdroid from the apk it seemed to work but it actually didn't so I went on and tried starting it manually from terminal. I realized I had a couple of problems first:

loop: can't open device /dev/block/loop: No such file or directory

I checked with root explorer and there is a folder /dev/block

The next problem is bash. I ran everything I've written here after typing su in terminal, I guess that's pretty much the same as bash. Now I read the debdroid file and it executes bash. I know I don't have bash, but I'm afraid if I install another busybox from the market I'll mess up the one that comes preloaded with the Atrix 4G (which is my phone). I recall this being a problem the first times the Atrix was rooted with Superoneclick which installed a new Busybox

Any ideas?

Thanks a lot

Edit:

I could get bash working without installing completely my busybox I just got bash from here

http://xdaforums.com/showthread.php?t=977051

I'm happy to report that I could get backtrack 5 running, but now I'm having problems with xfce... I'm getting this when I try to startvnc

Here are the two logs, the XFCe log and the vnc log:

root@debdroid:/var/log# more Xorg.0.log

_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed

_XSERVTransMakeAllCOTSServerListeners: server already running

Fatal server error:

Cannot establish any listening sockets - Make sure an X server isn't already run

ning

Please consult the The X.Org Foundation support

at http://wiki.x.org

for help.

Please also check the log file at "/var/log/Xorg.0.log" for additional informati

on.

(WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor

(WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor

(WW) xf86OpenConsole: VT_GETS

ddxSigGiveUp: Closing log

more /root/.vnc/debdroid\:1.log

16/05/11 18:43:50 Xvnc version TightVNC-1.3.9

16/05/11 18:43:50 Copyright (C) 2000-2007 TightVNC Group

16/05/11 18:43:50 Copyright (C) 1999 AT&T Laboratories Cambridge

16/05/11 18:43:50 All Rights Reserved.

16/05/11 18:43:50 See http://www.tightvnc.com/ for information on TightVNC

16/05/11 18:43:50 Desktop name 'X' (debdroid:1)

16/05/11 18:43:50 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t

16/05/11 18:43:50 Listening for VNC connections on TCP port 5901

/root/.vnc/xstartup: line 3: xfce-mcs-manager: command not found

Xlib: extension "RANDR" missing on display ":1.0".

Xlib: extension "RANDR" missing on display ":1.0".

Xlib: extension "RANDR" missing on display ":1.0".

** (xfwm4:593): WARNING **: The display does not support the XRender extension.

** (xfwm4:593): WARNING **: The display does not support the XRandr extension.

** (xfwm4:593): WARNING **: The display does not support the XComposite extensio

n.

** (xfwm4:593): WARNING **: The display does not support the XDamage extension.

** (xfwm4:593): WARNING **: The display does not support the XFixes extension.

** (xfwm4:593): WARNING **: Compositing manager disabled.

** (xfdesktop:594): WARNING **: Failed to connect to socket /var/run/dbus/system

_bus_socket: No such file or directory

xfdesktop[594]: starting up

process 594: D-Bus library appears to be incorrectly set up; failed to read mach

ine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory

See the manual page for dbus-uuidgen to correct this issue.

process 593: D-Bus library appears to be incorrectly

Suggestions?