[Nexus One Android Development] gazzaaa87:
Afternoon all,

Firstly, kudos to @jairuncaloth, this work is fantastic.

I followed this process on the original blog and then discovered this thread. I have have read every post and updated my config accordingly but for some reason I still have a problem - the fastboot command succeeds but then the phone hangs and I am unable to detect/communicate with the device using adb. I therefore cannot install X. I also don't have a serial cable so as the author puts it "I am flying blind".

I have collected together a mixture of feedback/problems/solutions as I have been reading through - the following are unlikely to be in any sort of order so apologies for that. I hope that my comments both help others to complete the process and with a bit of luck someone will be able to help solve my own issues. Here goes:

- small bug in the original post: no '/' at the end of:

$ adb push <kernelroot>/drivers/net/wireless/bcm4329/bcm4329.ko /data/local/mnt/lib/modules/2.6.29-droid-debian/kernel/drivers/bcm4329/

- when I executed the command

apt-get install vi

the installer was unable to find 'vi' (fairly sure this wouldn't make a difference as to whether Debian boots or not but was weird since I was able to install everything else).

- @digitalirony said:

I followed this and when I executed 'depmod -a' again I got the following error, which others in this thread didn't seem to get:

WARNING: Couldn't open directory /lib/modules/2.6.29-01117-g4bc62c2: No such file or directory
FATAL: Could not open /lib/modules/2.6.29-01117-g4bc62c2/modules.dep.temp for writing: No such file or directory

I mkdir'd and then it ran without issue but I wasn't convinced that the module was updated correctly. Does anyone know why this would happen?

- when I executed:

update-rc.d ssh defaults

I got the following output - I was unsure whether it had succeeded or not:

update-rc.d: using dependency based boot sequencing
update-rc.d: warning: ssh stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (none)

- the author said:

I double checked I had done this and still I am unable to connect after booting into Debian. On this point and out of interest: where is the root folder /sbin on the phone? I have been using the DDMS plugin in Eclipse to help visualise the file structure and it doesn't appear to be there. The 'cp' line executes fine btw, this is purely out of curiosity.

- @jjkwasnik said:

I have exactly the same setup - don't know if that makes a difference.

- @tordne said:

Yes, me!

Mine is also the same except with the following lines at the end:

[ 11.035522] usb: portchange USB_SPEED_HIGH
[ 11.274902] diag_configure() 1
[ 11.275085] ### notify_usb_connected(1) ###
[ 11.275421] usb_mass_storage usb_mass_storage: config #1
[ 16.411346] usb: suspend
[ 17.926055] cable_status_update: status=0
[ 17.926300] hsusb: ONLINE -> OFFLINE
[ 17.926452] ### notify_usb_connected(0) ###
[ 17.926788] usb_ept_queue_xfer() tried to queue request while offline
[ 17.926971] diag_configure() 0
[ 17.927124] msm_hsusb: disable pullup
[ 17.966857] msm_hsusb_phy_reset: success
[ 17.968261] batt: charging OFF

On the other hand, I do not have a messages file.

- @jjkwasnik said:

I was getting '???????????? no permissions' when I executed 'adb devices'. This is fixed by running the following:

su
cd <android-sdk-base>/tools
./adb kill-server
./adb start-server
./adb devices
exit

- @jjkwasnik said:

I think it's actually the other way around. In any case, following your steps didn't fix my issue.

- @jjkwasnik said:

Is swap required for this to succeed?

- @_unknown said:

I've tried this, no luck.

I've put down as much info as I can but let me know if there's anything else I can provide to help diagnose the problem. My last option will be to start over but I'd rather not.

Thank in advance for any help you can give me..

-Dan