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!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/