TuxScreen on SourceForge TuxScreen CVS search the Wiki
Browsing -> Wiki -> Main -> [ReInferno]
Google
Topic:
edit, info, topics, orphans, hubs and nodes, or recent changes in the Wiki create a new user or login

TimRiker records his work in progress:

Do this at your own risk! It may render your TuxScreen unbootable

TimRiker did this once and for some reason the kernel partition was completely blank (0xff) after following this procedure. JTAG was required to recover. It is believed that a bad connection on the sodimm is was at fault. Be sure your sodimm is firmly seated. If you are not sure, you may want to remove it while performing this procedure.

Futher information shows a bug in blob flash code that has now been resolved. Use the 20020709 blob or newer. If you have an older blob, then flash a new blob first, then reboot and then follow these steps.


This procedure will use blob to reinstall Inferno on a phone that is now running Linux. This could render your phone unbootable! Proceed with caution.

Under Linux try:

# cat /proc/mtd 
dev:    size   erasesize  name
mtd0: 00020000 00010000 "BLOB boot loader"
mtd2: 003e0000 00020000 "initrd"

If you get anything different do NOT do follow this procedure!

Start by grabbing an Inferno image from http://www.TuxScreen.net/download/inferno/ or use an image that you backed up before installing linux. The file size should be exactly 4194304 bytes. If it is not abort now! do not go on!

Now we split up the image using dd under linux:

dd if=newinferno.img bs=131072 count=1 of=blob.part
dd if=newinferno.img bs=131072 skip=1 count=31 of=ramdisk.part

Now we use minicom and blob to upload and flash each of these images. It is critical that the blob partition is flashed last so that Inferno will find the others and be bootable. It is assumed that you know the minicom commands to change baud rate back and forth. It is assumed that you are using ttyS0 to connect to the TuxScreen. If not replace it with the correct port below.

blob> xdownload ramdisk

Now send the ramdisk.part over with xmodem

blob> flash ramdisk
Saving ramdisk to flash ... done

Then send the first block over.

blob> xdownload blob

and send blob.part over with xmodem.


If there have been any errors or unexpected behavior up till this point stop here, do not go on you can still get back to Linux. If any of the above has not gone correctly this next step will render you TuxScreen unbootable so be sure.


If you are sure everything is ok, then type:

blob> flash blob
Saving blob to flash . . done

and then:

blob> reboot                 
Rebooting...

You might also read FlashingWithSboot

SourceForge Content of these pages are owned and copyrighted by the poster. SourceForge