Sharp brick c-3000

Sharp brick c-3000

[Pavel Machek]

Hi!

I'm not sure what I did wrong... I can still access "flasher" menu, by
holding down okay after reset, I press 4, 2, Y after that, screen just
goes black, but I do not get "update screen" after that. SD inserted
or not, no change. I'll play a bit more.

								Pavel
-- 
Thanks, Sharp!

Re: Sharp brick c-3000

[Richard Purdie]

Hi,

On Mon, 2005-10-24 at 23:16 +0200, Pavel Machek wrote:
> I'm not sure what I did wrong... I can still access "flasher" menu, by
> holding down okay after reset, I press 4, 2, Y after that, screen just
> goes black, but I do not get "update screen" after that. SD inserted
> or not, no change. I'll play a bit more.

Ah, I can guess :-(. Have a look at this:
http://www.h5.dion.ne.jp/~rimemoon/zaurus/pic/nandmap.jpg (from
http://www.h5.dion.ne.jp/~rimemoon/zaurus/memo_006.htm)

updater.sh writes the kernel into the space marked "2nd Kernel" - 1264kb
long. I'd guess you wrote a kernel larger than this, you overwrite the
initrd.gz which is used to run updater.sh. We really need to add a size
check to the OE copy of updater.sh. Anyhow, the damage has been done and
that update route is now broken. I should have warned about this
although I assumed Sharp might have fixed it on newer devices :-/.

So I said the Zaurus is unbrickable and you appear to have bricked it?
There is another level of system restore thankfully. In the past, to fix
this problem on both a c700 and a c760 I've used the files from here:

http://pocketworkstation.org/files/recover/

(http://pocketworkstation.org/files/recover/README-flash-recover.txt is
the instructions I used.)

You need to find the files for the c3000 and then attempt this
procedure. I don't have the files for the c3000 but you should be able
to get from somewhere. When you find them, let me know as I might also
find them handy ;-).

Your other alternative is to perform a NAND Restore, if you can find a
NAND backup for the C3000. The D+M menu has an option for this and I'm
sure it will also be documented on the web. When in this state I
couldn't get that to work on my c760 though it could have been the image
I was trying to restore it with or my CF card...

Incidentally OE has safeguards that warn you if the kernel is too big...

Richard

Re: Sharp brick c-3000

[Pavel Machek]

Hi!

> > I'm not sure what I did wrong... I can still access "flasher" menu, by
> > holding down okay after reset, I press 4, 2, Y after that, screen just
> > goes black, but I do not get "update screen" after that. SD inserted
> > or not, no change. I'll play a bit more.
> 
> Ah, I can guess :-(. Have a look at this:
> http://www.h5.dion.ne.jp/~rimemoon/zaurus/pic/nandmap.jpg (from
> http://www.h5.dion.ne.jp/~rimemoon/zaurus/memo_006.htm)
> 
> updater.sh writes the kernel into the space marked "2nd Kernel" - 1264kb
> long. I'd guess you wrote a kernel larger than this, you overwrite
> the

Last kernel I flashed was 1285752 bytes big...

> initrd.gz which is used to run updater.sh. We really need to add a size
> check to the OE copy of updater.sh. Anyhow, the damage has been done and
> that update route is now broken. I should have warned about this
> although I assumed Sharp might have fixed it on newer devices :-/.

Heh, apparently they did not :-(. Or I have some other problem.

> Your other alternative is to perform a NAND Restore, if you can find a
> NAND backup for the C3000. The D+M menu has an option for this and I'm
> sure it will also be documented on the web. When in this state I
> couldn't get that to work on my c760 though it could have been the image
> I was trying to restore it with or my CF card...

I can't seem to enter D+M menu. Instructions say "wait for up-to an
hour", so I guess that's what I should do.

> Incidentally OE has safeguards that warn you if the kernel is too big...

I should really learn how to use that framework...
								Pavel

-- 
Thanks, Sharp!

Re: Sharp zaurus c-3000

[Pavel Machek]

Hi!

[cc to the list]

> > > Your other alternative is to perform a NAND Restore, if you can find a
> > > NAND backup for the C3000. The D+M menu has an option for this and I'm
> > > sure it will also be documented on the web. When in this state I
> > > couldn't get that to work on my c760 though it could have been the image
> > > I was trying to restore it with or my CF card...
> > 
> > D+M menu still works for me, so I tried this one -- on SD card (my CF
> > card is only 16MB). Not sure what I'm doing wrong.
> > 
> > pavel@amd:/data/l/zaurus$ md5sum /mnt/systc300.dbk
> > 6a37ce6a4bee0b7a39fd0140c70eda16  /mnt/systc300.dbk
> > -rwxr-xr-x   1 root root 17317904 Jan  1  2003 systc300.dbk*
> > 
> > I only tried "NAND update". Should I do "Erase / NAND update"? Result
> > was
> > 
> > SD update
> > --- Found orders ---
> > Error!!!
> 
> This might mean you've also broken D+M. I couldn't get it to work when I
> had this problem either. Whether that was me or whether it was truly
> broken, I don't know.
> 
> That leaves the low level loader to restore NAND. Were you able to find
> C3000 images anywhere? If not, I can perhaps have a try and extracting
> them from my C3000. You should just need to fix the initrd partition I
> guess...

I managed to recover it. There are actually two "NAND update" options
in D+M menu (at different places). One of them works, second does
not. Oops. Just for the record, usefull files are at
http://www.trisoft.de/download . 
								Pavel
-- 
Thanks, Sharp!