Issues with serial connection (bricked)

[cause]

have a bricked V2 and I am following the postings here:
http://www.pogoplugged.com/forum/thread ... al+console

I have a cable connected and I was able to start a terminal (I have used putty and linux terminal "screen /dev/ttyUSB0 115200 8N1") and watch it boot (which kicks out a lot of errors) but I am unable to interupt the boot. I can see the "press any button to disable autboot" but no matter what I press it still autoboots—and I dont see the prompt at the end.

when using screen I can't copy the whole session to post here, but here are the last lines:

init started: BusyBox v1.7.0 (2008-02-26 19:25:17 IST)starting pid 267, tty '': '/etc/init.d/rcS'mkdir: cannot create directory '/tmp/mnt_opt': Read-only file systemumount: cannot umount /tmp/mnt_opt: No such file or directorymount: mounting /dev/sda1 on /tmp/mnt_opt failed: No such file or directoryumount: cannot umount /tmp/mnt_opt: No such file or directorymount: mounting /dev/sdb1 on /tmp/mnt_opt failed: No such file or directoryumount: cannot umount /tmp/mnt_opt: No such file or directorymount: mounting /dev/sdc1 on /tmp/mnt_opt failed: No such file or directoryumount: cannot umount /tmp/mnt_opt: No such file or directorymount: mounting /dev/sdd1 on /tmp/mnt_opt failed: No such file or directoryumount: cannot umount /tmp/mnt_opt: No such file or directory/etc/init.d/rcS: line 2: /opt/etc/init: No such file or directorystarting pid 280, tty '': '/bin/sh'-sh: export: `‘': not a valid identifier’h:w$

Is there anything I am doing wrong?

[WarheadsSE]

I swear I've seen this before.

I swear I've answered this before.

[cause]

haha, you have answered this before—but the problem persists. I decided to cast a larger net with figuring this out. I still don't understand how I can witness the whole boot but not interrupt it. I have tried OSX vs Win vs Linux, laptop vs desktop, terminal vs putty. Still fruitless. I have checked my rx/tx like you suggested—with any other combination of the two does not output the boot process.

[WarheadsSE]

Have you tried crossing the pins? Aka, connect Tx to Rx on the serial adapter itself, and verifying that a key press results in a matching character on the screen?

[cause]

okay, I shorted the RX and TX and opened "screen /dev/ttyUSB0 115200 8N1" in a linux terminal—it stayed open so that indicated a connection but I was unable to type in it.

[WarheadsSE]

That seems to be your problem then

[cause]

so it is the cable then?

[WarheadsSE]

Try it from another computer, if it still happens, then yes, it's the cable.