Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - carpy

Pages: [1]
1
Sharp ROMs / My SL5000D after flash ROM,can help?
« on: May 14, 2004, 01:49:14 pm »
I still feel stupid, but at least I\'m in good company.  Problem: I don\'t have the $$$ to upgrade.  I just finally got this one!

I have a SL5000 which I admit to have been rather stupid with.
I have been frustrated with Sharp for not putting up their Dev site
where I can get updates for the 5000.
In my frustration I have renamed \"ospack\" to \"romimage\" and flashed the
unit using the 5500\'s train of flash.
It flashed correctly, and upon boot I get the Sharp screen and init 2.78
message then nothing.  Switching the Battery Mode switch back and forth
once I then boot into the same message as shown(below).
Hard reset sends it back to the original Sharp/Init screen.
Now, however I seem to be unable to flash the device, getting the Green
light stays on as long as I let it.  This happens when attempting to
flash OZ3.2 or the Sharp 5500
One of the FAQ\'s I was reading says that means the FLASH device is not
useable (although I\'ve used it before??).
Could this mean that the flash corrupted the bootloader such that it
doesn\'t understand the CF card any more?  I\'m lost.  Would you have any ideas?
------
From: Chris Larson <kergoth@ha...>
~  Re: OZ3 flashes fine, Sharp ROM fails to reflash, bootloader?
2002-12-29 15:04

This problem has nothing to do with the bootloader, and if you
~ _intentionally_ overwrite it, you _will_ brick your zaurus.

<snip>
~ >
~ >
~ > ERROR:
~ > ... Error message on flashed Sharp ROM boot:
~ > INIT: version 2.78 booting
~ > e2fsck 1.19, 13-Jul-2000 for EXT2_FS 0.5b, 95/08/09
~ > ext2fs_check_if_mount: No such file or directory while determining
~ > whether /dev/mtdblock1 is mounted.
~ > Couldn\"t find ext2 superblock, trying backup blocks...
~ > Could this be a zero-length partition?
~ > e2fsck: Attempt to read block from filesystem resulted in short read
~ > while trying to open /dev/mtdblock1
~ >
~ > *** An error occurred during
~ > *** the file system check.
~ > *** Dropping you to a shell;
~ > *** the system will reboot
~ > *** when you leave the shell.
~ > /etc/passwd: root passwd garbled
~ > Give root password for maintenance
~ > (or type Control-D for normal startup):

~ >
~ > ...
~ > (Repair FS) # #
~ > ...
~ >
~ > At this point I\"m logged in ... I couldn\"t find an \"fdisk\" program but
~ > I did get the following list of mounted filesystems from `mount`:
~ >
~ > ...
~ > /dev/mtdblock0 on / type cramfs (ro)
~ > /proc on /proc type proc (rw)
~ > /dev/ram1 on /dev/ type minix (rw)
~ > ...
~ >
~ > I\"m assuming mtdblock1 would also be type \"cramfs\" like mtdblock0 ...
~ > if so, I don\"t know how to fsck a cramfs as there is not an fsck.cramfs
~ > in /sbin (normal fsck.* types are in /sbin as expected).
~ >
~ > When I type \"exit\" and the system reboots it says
~ >
~ > ...
~ > Cannot read /etc/fstab: no such file or directory
~ > Automatic reboot in progress.
~ > ...
~ >
~ > Then it shows the Sharp logo screen and about 3 seconds later the scene
~ > from above repeats.
~ >
~ > /Geoff
~ >
<snip>

Pages: [1]