Using the Speaker Button/Volume Down trick, I logged in via telnet to the device and did some looking around. It looks like the only way to save anything is by using the /sbin/nvram to write to nvram. The command option -a lists all the nvram settings of which some interesting values are boot.stage, boot.att and more. boot.stage seems to control the boot mode set in /etc/init.d/boot.d/S11boot.monitor startup script.
Now, to do anything useful, you will need to mount /dev/mtdblock1 ( mount -o rw -t yaffs2 /dev/mtdblock1 /boot) which does save data across reboots and take a look at the files there.
I've only spent a few minutes looking into this thing, so yeah, it's hackable, but requires some experience with unix and there's no easy script for this one (yet). I'm sure there is a nvram setting (probably with boot.stage) that can be written so the hub always boots into failsafe mode instead of normal operation. But really, this things is mostly a piece of junk, always was a piece of junk and a ripoff.
Was this reply helpful? (0) (0)