Author Topic: My SL5000D after flash ROM,can help? (Read 6888 times)

jasandpal · « **on:** May 11, 2004, 09:41:08 am »

After I download ROM2.12,then I flash my SL5000D. then crash, the PDAscreen show this http://page.auctions.shopping.yahoo.com/sg...12?aucview=0x30 , I want to flash back to original ROM,but the mail and battery light on for whole day and no turn off. I can not flash back to my old originak ROM,anyone got idea?thanks

nilch · « **Reply #1 on:** May 11, 2004, 10:35:20 am »

Switch the unit off, and take out the battery cover and take out the battery. That should switch it off totally.
After that, power on - make sure you have the zaurus on the power cable and then reflash again - the Ctrl+C+D key sequence.

Are you sure you have the right ROM version for the 5000D and not for the 5500 ?

jasandpal · « **Reply #2 on:** May 13, 2004, 03:18:55 am »

I think the ROM2.12 is for SL5500,after I flash this ROMimage then got probllem. I take out the battery and put back ,then I flash the original ROM 1.39 for SL5000D,but the light goes on,and never turn off. can not flash.

zbones · « **Reply #3 on:** May 13, 2004, 04:29:00 am »

I seem to remember somebody else flashing a 5500 rom onto a 5000 a few months ago, I don\'t recall if he got it working again or not.

Try searching this forum

Peter
*EDIT*, I found it for you :-
http://www.zaurususergroup.com/index.php?n...=867&highlight=

He got different errors than you on the screen.

Can you verify if it was a 5500 rom?

Joshp · « **Reply #4 on:** May 13, 2004, 09:05:09 am »

I have had this problume on my 5500, whan I removed the sharp qtopa and drop in 1.6 version. Bascly what it is /usr/sharp/etc/launch.conf is symlink /home/sharp/etc/launch.conf I think what happend on my was /home was not untared before I started looking for launch.conf.

JP

jasandpal · « **Reply #5 on:** May 13, 2004, 12:36:14 pm »

I think 2.12 is for 5500. I send back to Singapore service centre but they dont know how to fix it cause Sl5000 not sell in Singapore.

jasandpal · « **Reply #6 on:** May 13, 2004, 12:37:26 pm »

How to remove qtopa?
Thanks JP

Joshp · « **Reply #7 on:** May 13, 2004, 01:09:07 pm »

I mounted the initrd.bin file and rmoved /usr/QtPalmtop and /usr/QtPalmtop.rom. I than untared the /root/.home_default.tar and removed /home/QtPalmtop. and Than installed the version of Qtopia. retard the home dir and replaced /root/.home_default.tar with the one I created. I symlinked every thing to /home/QtPalmtop. eg /usr/QtPalmtop.bin ] /home/QtPalmtop. Whan I booted it up I got the same message you getting now. I took a look at the ospack for 2.12 rom and it looks like if you mount it and remove /usr/sharp and than cp -a /home/sharp /usr/ you might be able to fix you problume.

JP

jasandpal · « **Reply #8 on:** May 14, 2004, 10:24:49 am »

cant fix,I think will upgrade to other PDA.thanks everyone

carpy · « **Reply #9 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>

Ram · « **Reply #10 on:** May 14, 2004, 03:16:33 pm »

Jasandpal & Carpy

First, Jasandpal got your PM but am afraid I have not got it fixed - bought another Z 5500 instead, may send the Z5000 back to Sharp to fix if I can afford it.

Second, There is a Diagnostic page you could try that will test writting to ROM if that passes the test you maybe able to fix your Zs but mine fails the write test, I taking that the failed flash inavertantly write protected the ram chip. The Diagnostic page can be found using C + P, on the first page bottom right tap version and it will list what you have flashed yours too.

Third, Carpy that bumph above is exactly what mine displays

Best of luck , if you find a cheap resolution drop me a line.

Ram.

Joshp · « **Reply #11 on:** May 14, 2004, 06:00:16 pm »

Quote

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>

It looks like /dev/mtdblock1 was not formated to be ext2. Try booting up to the Repiers Fs prompt and running mke2fs /dev/mtdblock1, after that try mounting it somewhere. Hope this helps.

JP

jasandpal · « **Reply #12 on:** May 14, 2004, 09:34:20 pm »

Hi ROm
Thanks for reply,I using D+P go to Diagnostic page, but no use, deccided to sell my 5000 as a spare part .

nequiem · « **Reply #13 on:** January 30, 2005, 02:51:29 am »

I ran into this same situation attempting to upgrade my 5500 to 3.13. I flashed it but got the "bad superblock" error. That gave me a tingly, gut wrenching feeling of terror much like the time when I applied a MS patch on the server at work which corrupted the registry hive. I thought I had charcoal briquetted my friend, Mr. Z.

Tried hard reset and no luck. Did mke2fs as JP wrote, got the repeating launch.conf error, but hard reset and presto! It worked.

Thanks JP! You da man! What's the deal with 3.13? I'm afraid to flash anything again after that nasty experience...

Quote

It looks like /dev/mtdblock1 was not formated to be ext2. Try booting up to the Repiers Fs prompt and running mke2fs /dev/mtdblock1, after that try mounting it somewhere. Hope this helps.

JP

jogloran · « **Reply #14 on:** January 30, 2005, 05:36:14 am »

Quote

It looks like /dev/mtdblock1 was not formated to be ext2. Try booting up to the Repiers Fs prompt and running mke2fs /dev/mtdblock1, after that try mounting it somewhere. Hope this helps.

JP

How do you get to this prompt? I don't know about Repiers, but do you mean ReiserFS? I have a C750 now, but I'd like to give reviving the old 5500 a try.

News:

Author Topic: My SL5000D after flash ROM,can help? (Read 6888 times)