Resetting arcNumber from an operational Arch kernel
If you can boot into Arch off your USB device and have a working fw_printenv/setenv, you can just issue the following command as root:
$this->bbcode_second_pass_code('', 'fw_setenv arcNumber 1682')
You'll be able to run the Iomega stock kernel upon reboot.
Recovering arcNumber on a bricked iConnect
I built an image that makes use of iConnect's "emergency boot" mode so follow this section if you got your iConnect to the point where it can neither boot off your USB device nor boot the stock kernel. Following the procedure below will reset your arcNumber to the stock value of 1682 and will also update your boot sequence in case it got screwed up somehow.
$this->bbcode_list('1')
If everything works correctly, the power LED will turn solid blue and all other LEDs will be turned off in a few seconds.
If you're left with any blinking LEDs, something went wrong:
- blue power LED is blinking: USB filesystem could not be mounted;
- otb LED is blinking: the included runme.sh script could not be executed or returned an error;
- usb1 LED is blinking: fw_setenv is not operational;
- usb2 LED is blinking: arcNumber could not be changed.
If your iConnect is sufficiently screwed up that you still cannot run the stock kernel after this, try running Iomega's official recovery imager; this will reflash the iConnect to the factory state. Note that you won't be able to run that until the arcNumber is set to 1682.
Recovering with JTAG
If you managed to overwrite your entire uboot partition and can't even get the uboot prompt over serial, you can try JTAG recovery.