yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] jjkwasnik:
@digitalirony

Sorry, have been busy at work and didn't notice your reply about getting fastboot working.

Yes my phone is in fastboot mode with the usb cable plugged in. I was actually running ubuntu 9.1 in VMware on my winxp machine. I have a ubuntu station but any usb device that requires power freaks the machine out. and my laptop is from work, so i dont really want to partition it and all that fun stuff. so installing vmware was easy and suitable, bec i can put it on a usb hard drive and run it from there without any issues.

but to get to the point, on xp i run fastoot devices and it shows the device, while on ubuntu i run fastboot devices and it just comes up blank. I was having issues getting adb devices to work and then i edited the rules.d files and then restarted udev and it appeared to work fine.

Not sure if anyone else has any idea's about how to get fastboot running in ubuntu.
[Nexus One Android Development] jjkwasnik:
the only other thought i had, is that maybe i could try using fastboot on winxp, i tried it quickly, but i didn't have enough time to look at the syntax sunday night. im not an expert with fastboot either, only have used it a few times to update the radio image.
[Nexus One Android Development] rheza02:
how about people only want to run the startxcfe ?, do you have solution for that ?

thanks
[Nexus One Android Development] sycohnda209x:
Great work

Is it possible to download flash 10.1 linux version that is out and use it on the phone for full flash?:D
[Nexus One Android Development] rheza02:
i'm not sure now, i never can boot to debian.adb didn't detech any devices.

this will be great if we know another way to boot without fastboot and adb.
[Nexus One Android Development] olearyp:
Hulu Desktop would be slick...OTOH, this.
[Nexus One Android Development] rheza02:
my dmesg

http://pastebin.com/f2c7590cc

my messages

http://pastebin.com/f7546bad

i can't boot to debian now, its look like my pc didn't reconize any adb devices.
[Nexus One Android Development] drTestPilot:
Do I understand it correctly? So there is a Firefox and Flash for Linux. And this hack could boot Debian. Plus it supports WiFi. So as long there is WiFi near you it is possible to browse Flash sites?

But is it not possible to boot into Debian just from your SD card so far?
[Nexus One Android Development] liam.lah:
jairuncaloth, Why are you using Iceweasel? did firefox have to be modified to work on the phone?
[Nexus One Android Development] rheza02:
any progress guys ?
[Nexus One Android Development] tordne:
that's my goal too, I forgot to include the mounts of /proc /devpts /sysfs in the file.

When you've done that you can easely install xcfe4 in connectbot.

Unfortunately you can't start the X11 in connectbot.

because my adb still doesn't work(after 4 days), I've tried the files 50-andr*les, 51-and*es, 52-an*s and even the 70-persi*net.rules

with all the different SYSFS{idVendor}=="0bb4" or ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="4e12"

but I got a question too???

When I'm in Debian in connectbot I can ssh into my phone, I tried to make IPtable rules to allow me to connect via ssh in the beginning since this rediculous adb doesn't work.

So when i do the fastboot -c "root=/dev/mmcblk0p2 rw rootfs=ext3 init=/sbin/init rootwait noinitrd" boot zImage

I see a new ip address with nmap, but on port 22 it keeps saying conn refused.

And my screen of the phone is still hanging on the nexus startup screen.

Can somebody explain me, after the initial install and reboot and before their install of xcfe what do they see?

The same screen as me and it keeps hanging there??

Is the phone actually allready in Debian??? So why would you people want to use adb instead of ssh???

and why can't I ssh into the debian if the ports were open in connectbot?
[Nexus One Android Development] rheza02:
Thanks god, not only me have this problem. :(
[Nexus One Android Development] tordne:
my dmesg are the same except for the sd-card and filesystem I got 3 partitions and i use ext3...

But anyway here is the difference at the end

[ 10.947540] usb: portchange USB_SPEED_HIGH
[ 11.087432] diag_configure() 1
[ 11.087585] ### notify_usb_connected(1) ###
[ 11.087921] usb_mass_storage usb_mass_storage: config #1
[ 19.971710] EXT3 FS on mmcblk0p2, internal journal

so this is after 19 secs, but I always kept my phone on for about 4 to 8 mins.

when i look at /var/log/messages it is mostly the same as yours, most important things that he says at the end is...

-> he mounts my Debian to my root /

-> he enables the adb function

-> for the rest he charges and keeps on enabling and disabling the usb

I know how to read these logs, but I can't do much with it...
[Nexus One Android Development] rheza02:
fyi, i just format my debian partition and leave it. :(

i will install again this weekend.
[Nexus One Android Development] jairuncaloth:
Can you guys see the phone with adb normally (in android)?

If so, sounds like adbd isn't running in debian.
[Nexus One Android Development] rheza02:
its normal in android.

------------------

what is the progress now ?,

can you make a call from debian ?, when the image will be ready ?

thanks
[Nexus One Android Development] tordne:
no I've never seen my phone with adb, only with fastboot.

even when i say in connectbot adbd it says "cannot bind tcp:5037"

Might be a ridiculous question... can i have something to do with my firewall?

It's quite secure... with fwsnort...

only my OUTPUT is on ACCEPT, and if i connect from my laptop it means that i established the connection... so normally seen it has nothing to do with it (still it stays in my thoughts after I tried everything..)
[Nexus One Android Development] jairuncaloth:
Sorry guys, busy weekend.

Iceweasel is firefox. Just unbranded since the firefox logo doesn't meet debian's licensing requirements.

If you're running amon_ra's recovery, it includes parted. If you have linux on your desktop you could use something like gparted. Windows I dunoo...

I have run into this as well but I've been having trouble with my router dropping wireless connections lately so I can't say if we have the same problem.

I looked in the repo. No flash 10. I guess arm isn't a supported arch for flash. I haven't dug much deeper then that though.

adb is more reliable. If you screw up your network config you won't be able to get into debian on the first boot. To make adb start, you just need to copy over a binary and add a single line to /etc/rc.local

Did you tell sshd to start on boot in debian?

While chrooted into debian partition run this.

# update-rc.d ssh defaults

For those with trouble with adb. Did you add '/sbin/adbd &' to /etc/rc.local before the 'Exit 0' line? Also, don't forget to copy over the binary to /sbin/adbd
[Nexus One Android Development] jjkwasnik:
tonight im going to have some more free time, and im goign to try to get fastboot to recognize my device..... it will recognize it on windows xp on the same pc, but will not recognize it on ubuntu 9.1.

to the people that have been having issues with adb recognizing your device, i did have some issues with this as well. it was very random though, i will have to remove the files from rules.d and restart udev, and possibly restart the OS. and when it comes back up i will re-add the files to rules.d and then restart udev, and then run adb start-server and this was helping the device to be recognized.

not sure why nexus has such a hard time being recognized by adb or fastboot.

i may try to to use my win xp image to use fastboot tonight, to see if i can at least get the kernel booted if i cant get ubuntu to recognize it again.
[Nexus One Android Development] rheza02:
can you make a image of your debian partition ?, its difficult to starting install it again :(.
[Nexus One Android Development] tordne:
I've done all these steps... even when i'm in nexus and i type in adbd he tells me cannot connect to port:5037

when i do

$$>> netstat -a p tcp -n | grep 5037

I see adbd is already running

I even killed it, but it just came back with an other pid

- now something else cause i installed xfce4 with debian in connectbot, he had some problems with my locales.

- i changed the default runlevel from 2 to 5 (trying to keep the standards high)

- but when i look in my rc5.d there is nothing mentioned of x11-common.

and it has only this mentioned ( S01bootlogs S01rsyslog S02aumix S02cron S02dbus S02ssh S03hal S04rc.local S04rmnologin S04stop-bootlogd)

- as you see my ssh was already there, but i think this need some more adapting before i can start X
[Nexus One Android Development] jjkwasnik:
@ rheza02

I could make an image when i get home where my sd card is with debian on it, im not 100% that my debian install is perfect or working because i cant use fastboot yet to boot the kernel.

I did have a few issues when i started the first time but i didn't mount the correct partition in the begining. And i was trying to use gparted to partition the sdcard, but there was some things that the phone wasn't liking, so i partitioned it via recovery mode.

this is what i did to fix......

i had put a 2nd 4gb sd card in my phone, i booted into recovery and went into partition sd card. Im sure you could do this with your current SD card but make sure you back up everything before you over write the partitions.

-2.2 gb partition for ext2

-750 mb partition for /swap

-leftover for fat32

i booted my phone up, and plugged in the usb cable, i went to the phone and turned file sharing on so my pc would see the sd card. i installed gparted on ubuntu so i could see what the mount point for the hard drive was called. (the first time i did this my sd card was /dev/sdc2) not /dev/sde2

i set up the mount points... mount /dev/sdc2 /mnt/android

you may just be trying to mount a point to /mnt/android that is not actually on your sd card.... thats where i went wrong the very first time. after you get that mount point set up corectly and run (debootstrap --arch armel --foreign squeeze /mnt/android http://ftp.us.debian.org/debian)

when the files get installed they appear to be going to /mnt/android on your ubuntu machine but you have a mount point set up as (/dev/sdc2 or /dev/sde2 what ever drive letter your sd card is) which is where the files are actually getting installed.

see if that helps
[Nexus One Android Development] tordne:
@jairuncaloth or anybody that had a working adb and could install debian and xfce4 perfectly... and who can get it running with the fastboot command.

can this person execute the following commands and connect it to a post at least we'll know which scripts he runs at startup...

it is better to execute this as normal user

ls -l /etc/rc?.d >> /home/$USER/rc-list.txt
ls -l /etc/init.d >> /home/$USER/rc-list.txt

I know that debian starts up, i see it in the logfiles, but it's just that he doesn't startup the necessary scripts.

thanks for helping me out.
[Nexus One Android Development] jairuncaloth:
Xfce isn't configured to start on boot. I usually just start it form the terminal. If you want X to start by default, you might want to get something like GDM or XDM installed.
[Nexus One Android Development] tordne:
hahaha.....

jairuncaloth you are beautiful and smart.... (I don't know about the first one but the second for certain, hehehe)

So when I was still in android I ssh in from my laptop and uninstalled xfce4, then installed gdm and restarted....)

ANDROID stick your ADB where sunlight doesn't shine... SSH rules (and fastboot)

it took me a few days and a few nights that my woman nags around my ears "what are you doing, come to bed..." HAHAHA....)

Debian here i come...............
[Nexus One Android Development] hobomeat:
I'm following the OP, and have run into a problem fairly early on.

When I enter the chroot line in the adb shell, I get this:

# chroot /data/local/mnt/ /debootstrap/debootstrap --second-stage
chroot /data/local/mnt/ /debootstrap/debootstrap --second-stage
[B]/debootstrap/debootstrap: 332: cat: not found[/B]

!!

The phone is rooted, has busybox, and I can run cat just fine on a phone terminal emulator or on the adb shell, so I don't know what the problem is...?

I've checked line 332 of the debootstrap script, and it doesn't have cat on it, which just makes me more confused...

EDIT:

I suppose it's actually referring to the "cat"s on lines 297, 298 and/or 300? Can I edit those lines to fix it?

EDIT2:

Ok, I replaced the cat stuff on lines 297 and 298 with "armel" and "squeeze", and that removed the error for line 332, but now I have "not found" errors for

376: grep

386: mkdir

and I don't know what to repair these lines with......

Plus, of course, I have no idea why these problems are coming up in the first place!
[Nexus One Android Development] rheza02:
@jjkwasnik

thanks man, thats problem i got when i'm reinstalling again :(.

i'll be waiting your image. :D
[Nexus One Android Development] jjkwasnik:
@rheza02

I actually forgot my usb cable at work last night, so i couldn't compile that for you, but i got to work, and mounted the drive and burned it to an .iso file for you, not 100% it captured every file...... just don't know where to host it for you. i could set up an ftp server on my ubuntu machine at home, but i cant access that right now. and have some stuff to do after work today.
[Nexus One Android Development] rheza02:
just sent pm to you, just upload it there man. thanks
[Nexus One Android Development] jjkwasnik:
@ jairuncaloth

so i ended up getting fastboot to recognize my device..... these needed to be in the 51-android.rules config file

SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"

SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"

**18d1 - is for adb

**0bb4 - is for fastboot

while your usb device is connected and run lsusb from terminal it will show you your usb device.

next i ran sudo chmod a+rx /etc/udev/rules.d/51-android.rules

sudo /etc/init.d/udev restart or sudo service udev restart

then unpluged usb cable and pluged it back in with debugging mode turned on, ran adb devices and it recognized device. if device is not recognized you may need to unplug cable and retry

once in bootloader mode, i had to unplug the usb cable and plug it back in, and fastboot devices recognized it.

once i ran fastboot to load the kernel i had to put the directory where the kernel was located before zImage and that worked fine.

i unplugged my device and plugged it back in, adb devices recognized my device. and was able to log into the debian OS

** now only issue is that i run ifconfig, and eth0 is not coming up, i set up the the wifi accesspoint for my work, and tried it again......... maybe i didn't load the wifi drivers correctly in the kernel is my next guess.

i will retry that part when i get some time tonight/tomorrow i spent a few hours at work today messing around with fastboot. need to actually do some work now.

any ideas on wifi to help point me in the right direction??? Thanks!!!
[Nexus One Android Development] rheza02:
Finally, i can boot to debian, after reinstalling it again. play on it around 15 minutes, after that unpluging the usb, and stop on there, i can't boot to debian anymore. but nvm, i'm already documented the Nexus One With DEBIAN OS!! :D

Will Upload to youtube in an hour.:D
[Nexus One Android Development] jjkwasnik:
@rheza02

did you use the iso file i uploaded for you, or did you start the install from the beginging?
[Nexus One Android Development] rheza02:
install it from beginning man.

btw, thanks.

------------------------------------------------------

i'm just check the file, its only have size 230mb, is it correct ?, i thought it was bigger than that.
[Nexus One Android Development] _unknown:
hobomeat: I've just come across the same problem as you describe. I assume you are executing the following command:

chroot /data/local/mnt/ /debootstrap/debootstrap --second-stage

This does not set up the proper environment, so you can solve it with the following steps:

This allows the script to execute properly, without modifications. Good luck with the rest of the setup, I'm currently waiting on the above command to finish myself ;-)
[Nexus One Android Development] hobomeat:
Thanks unknown, that did the trick ;)

Ah, I can finally use my Ubuntu box to do this, instead of a windows one...
[Nexus One Android Development] rheza02:
guys, if you wanna see how its work.

just see this youtube video

http://www.youtube.com/watch?v=SQ939llCqVc

:D
[Nexus One Android Development] m00moo:
Video dont work buddy

EDIT: hmm dont seem to work on N1 itself for me. PC is fine
[Nexus One Android Development] hobomeat:
Could someone tell me where to get the bcm4329.ko file needed in the OP guide? (I don't have it on my system, like the OP seemed to.)

For the 2.6.29 kernel, if that makes a difference (I'm just using the kernel built by and linked to from the OP.)
[Nexus One Android Development] tordne:
I must say that my wireless in debian doesn't work yet.

now my question.

I installed lxde and wicd.

I can see eth0 this is my wired connection through usb.

when i say connect he wants to search for an ip address.

on my phone i changed /etc/wicd/wired-settings.conf to give it a fixed ip address. but it doesn't seem to work.

Does anyone have any ideas on this one...

also i wanted to install zhone, I filled up my sources.list but it doesn't seem to find zhone.

For the moment I use matchbox-keyboard... it looks fine to me for the moment.

at least now i can use the terminal in debian.

But for me now is the most important thing to get my ssh and wired connection working.

I can install things in debian, but everytime I have to restart in android and use connectbot
[Nexus One Android Development] tordne:
now i tried this bcm4329.ko that was posted on page 7.

when i'm still in connectbot and i do

$$>> depmod -a

everything is fine

but when i try it when i started up debian it says can't read module .../bcm4329.ko: Exec format error

Any idea's???
[Nexus One Android Development] jairuncaloth:
Sounds like the bcm4329.ko you have doesn't work with your kernel.

Try this one

http://irregular-expression.com/tmp/bcm4329.ko
[Nexus One Android Development] bobtentpeg:
Goddamn, I can not get this to work properly and its starting to piss me off
[Nexus One Android Development] jairuncaloth:
Some specifics would help us figure out what's going on...
[Nexus One Android Development] bobtentpeg:
Its not booting all the way. Might be an issue with my card though, it was funky on my G1 too
[Nexus One Android Development] hobomeat:
Sounds like the problem I am having now. (I don't have cyanogenmod though. I am using the superboot rom from modaco though...)

I'm pretty much all the way through, but this:

fastboot-linux -c 'root=/dev/mmcblk0p2 rw rootfs=ext2 init=/sbin/init rootwait noinitrd' boot zImage

causes a reboot, then another reboot, and Android comes up as usual.

My fstab is:

/dev/mmcblk0p2 / ext2 defaults 1 1
proc /proc proc defaults 0 0
/dev/mmcblk0p1 /media/sdcard vfat defaults 0 0

Have I done something wrong?

EDIT: my phone has the bootloader unlocked, and is rooted.
[Nexus One Android Development] tordne:
tried it several times, I also tried the bcm4329.ko from android, but he nevers recognizes it...

also a few questions... if I look in my log files i see he only uses 219Mb RAM.

Feb 21 04:17:47 Antirrhinum kernel: [ 0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes)
Feb 21 04:17:47 Antirrhinum kernel: [ 0.000000] Console: colour dummy device 80x30
Feb 21 04:17:47 Antirrhinum kernel: [ 0.000000] console [tty0] enabled
Feb 21 04:17:47 Antirrhinum kernel: [ 0.000610] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Feb 21 04:17:47 Antirrhinum kernel: [ 0.000946] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[B][COLOR="Red"]Feb 21 04:17:47 Antirrhinum kernel: [ 0.012512] Memory: 219MB = 219MB total
Feb 21 04:17:47 Antirrhinum kernel: [ 0.012573] Memory: 216832KB available (4144K code, 884K data, 108K init)[/COLOR][/B]
Feb 21 04:17:47 Antirrhinum kernel: [ 0.013153] Calibrating delay loop... 509.54 BogoMIPS (lpj=2547712)
Feb 21 04:17:47 Antirrhinum kernel: [ 0.239929] Mount-cache hash table entries: 512

I'm gonna read some more about making a new zImage, cause in this one I also got errors like

Feb 21 04:17:47 Antirrhinum kernel: [ 0.000000] Kernel command line: board_mahimahi.disable_uart3=0 board_mahimahi.usb_h2w_sw=0 board_mahimahi.disable_sdcard=0 diag.enabled=0 board_mahimahi.debug_uart=0 smisize=0 androidboot.baseband=4.04.00.03_2 androidboot.cid=GOOGL001 androidboot.carrier=GOOGLE androidboot.mid=PB9910000 androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT9CSP818969 androidboot.bootloader=0.33.0012 root=/dev/mmcblk0p2 rw rootfs=ext3 init=/sbin/init rootwait noinitrd
Feb 21 04:17:47 Antirrhinum kernel: [ 0.000000] Unknown boot option `board_mahimahi.disable_uart3=0': ignoring
Feb 21 04:17:47 Antirrhinum kernel: [ 0.000000] Unknown boot option `board_mahimahi.usb_h2w_sw=0': ignoring
Feb 21 04:17:47 Antirrhinum kernel: [ 0.000000] Unknown boot option `androidboot.baseband=4.04.00.03_2': ignoring
Feb 21 04:17:47 Antirrhinum kernel: [ 0.000000] Unknown boot option `androidboot.cid=GOOGL001': ignoring
Feb 21 04:17:47 Antirrhinum kernel: [ 0.000000] Unknown boot option `androidboot.carrier=GOOGLE': ignoring
Feb 21 04:17:47 Antirrhinum kernel: [ 0.000000] Unknown boot option `androidboot.mid=PB9910000': ignoring
Feb 21 04:17:47 Antirrhinum kernel: [ 0.000000] Unknown boot option `androidboot.keycaps=qwerty': ignoring
Feb 21 04:17:47 Antirrhinum kernel: [ 0.000000] Unknown boot option `androidboot.mode=normal': ignoring
Feb 21 04:17:47 Antirrhinum kernel: [ 0.000000] Unknown boot option `androidboot.bootloader=0.33.0012': ignoring

Making boot-images is new to me, but i can understand that you took the android boot kernel to start debian.

I also have the problem that when i start debian sometimes it just blocks and doesn't respond anymore.

I just wanted to start programming some c apss for my phone, but this is already one week just to root and etc... and trying to get debian running on this phone.
[Nexus One Android Development] jairuncaloth:
Are you using apps2sd? If so double check what partition debian is on and adjust your fstab and fastboot command appropriately.

tordne: Those errors are pretty normal. I see them when I boot android normally as well. As far as memory goes, I'm using the stock 2.6.29 kernel. I'll be upgrading to the high-mem kernel soon.
[Nexus One Android Development] tordne:
I thought from the beginning that this fstab was very small... so ... I've been reading and reading and reading and ..... reading... :-)

here is the fstab of my phone now

# /etc/fstab static filesystem information
#
# file system	mount point	type	options	dump	fsck
#	order

/dev/mmcblk0p2	/	ext3	defaults	1	1
/dev/mmcblk0p1	/media/sdcard	vfat	defaults	0	0
/dev/mmcblk0p3	swap	swap	pri=1	0	0
proc	/proc	proc	defaults	0	0
sysfs	/sys	sysfs	defaults	0	0
devpts	/dev/pts	devpts	gid=4,mode=620	0	0
tmpfs	/dev/shm	tmpfs	defaults	0	0

this got the basic stuff in it.

@ jairuncaloth: can you point me in a direction or some books on how you made that zImage? I started to read LFS, and i'm searching for a decent arm kernel?
[Nexus One Android Development] _unknown:
For those of you who want to see debian boot in all it's glory, as well as aid with debugging the boot process, you need the following kernel parameters:

CONFIG_NO_USER_SPACE_SCREEN_ACCESS_CONTROL=y
# CONFIG_FB_EARLYSUSPEND is not set
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FB_MSM_LOGO is not set

I'm not completely sure you need all of them, but that's the combination that did the trick for me. However, I'm on a 32A Magic, and sadly I'm still not able to get X11 working, nor wifi (we need different drivers than the nexus).
[Nexus One Android Development] jairuncaloth:
@ _unknown

Unfortunately FB console doesn't work on the N1 in my experience. If you don't have a serial cable. You can't see what's happening during boot.