OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> How To Restore A Seriously Bricked Z, Panic, then solution
DrWowe
post Dec 29 2005, 03:20 PM
Post #1





Group: Members
Posts: 696
Joined: 17-January 04
Member No.: 1,468



I was screwing around with the flash memory, and bricked my Z so hard that it wouldn't do anything except flash the mail and power LEDs. None of the special boot sequences I know worked and I couldn't get to the NAND restore, or any other restore procedures I knew of.

I looked around for solutions in vain, and I was getting to box it up and start the long round-trip to Japan, when a lucky set of Google search terms came up with an idea. I tried it, and it worked.

Since the page I found is only in Google's cache of the dead externe.net forums, I'm going to copy it here for posterity.

http://72.14.203.104/search?q=cache:X30-yH...fdaf8e5488c9172

QUOTE
bastichelaar

Posted: Thu Jun 03, 2004 6:17 pm
YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES

I have the solution!!! I am so happy now!!! I was surfing for hours and hours, and playing with binary files and dd...

But I found a website that has the solution for my device: http://www.piro.hopto.org/~piro/pukiwiki/p...B%5BP2ROM%5D%5D

I pushed FN+D+M while connecting the AC power, and suddenly I did have a Service Menu!

Now I'm trying to restore a c860 NAND from www.trisoft.de.

Everybody thanks!


I'm also going to copy a translation of the Japanese WiKi page. smile.gif It seems to have a very complete description of special ways of booting.

QUOTE
Because it was possible to revive with NAND RESTORE here when FLASH in zaurus has been crushed before, let's write the thing that it did around here or the doubt and.

It is a thing of the reference as for the page above. Moreover, I will read the page of 59414D41 Mr. to whom the page was written.
It is considerably important and comprehensible.

By the way, the thing done after it determines it of act of danger considerably. The responsibility cannot be taken no matter what it happens.
It had already been destroyed, and this act was able to be eased for me.
By the way, only SL-C700 is confirmed.

How for start-up of debugging menu.

Basically, it stands up by turning on the lock switch of the battery lid while pushing some keys.
Moreover, it is acceptable even if it pushes at the restart. The battery is removed, and it is OK to do the adaptor in while pushing the key.

From Zaurus forum
key combination  boot option number  action  Operation by my Zaurus
none  0  normal boot  Usual boot
?  1  BOOT REMOTE DIAG  ?
DP  2  Normal diag  Refer to the page of 59414D41 Mr..
DM  3  Service diag  Refer to the page of 59414D41 Mr..
DC  4  Update NAND from NOR  There is no CF update screen.
QT  4  Update NAND from NOR  There is no CF update screen.
DL  5  Boot CMDLINE is changed and it boots it.  Usual boot
DZ  6  Update NOR from NOR  For Flash combustion of Bets without NOR update screen(Maybe,)
DK  7  Update NAND from NAND  There is no CF update screen.
DB  8  BOOT: Maintain kernel  Guy of boot 0x220000 of kernel for maintenance
AB  9  Backup  backup ?
DV  9  Backup  backup ?
DA  ?  Angel Debug Monitor  Angel Debug Monitor version 0.42
DR  ?  REMOTE CHECK  It is output with REMOTE CHECK 2400bps. The command of two characters can be sent. Is it considerably danger or .. Bootflag can have changed.
LX  ?  It is the same as option number 0.  ?
Fn+P+D  ?  Normal diag  Diag is booted without NAND LOADER's passing. (In the cereal output,)
Fn+D+M  ?  Service diag  Diag is booted without NAND LOADER's passing. (In the cereal output,)

Oh dear the around here person ..NAND FLASH BACKUP.. thinks with diag menu.

C750 ..kernel.. is seen and doubtful reset_key_combination ..corgi_logkey.c.. is discovered.
Fn+Home, Fn+P+D, and Fn+M+D are recorded anything doesn't happen though it tentatively confirmed not recording up.
Can only SL-C750/760 be done because it is not in the kernel of SL-C700?

Destruction and restoration of NAND device

/(mtdblock2) was not able to be read for a moment suddenly ..the former kernel and...
Oh dear, it is generated the error while writing it when thinking the furnace as soon as reconciling when initrd.bin is rewritten.
At this point, the debugging menu ..information.. worries .... considerably. Including thing sent to repair

And the net are variously examined and the cod and the debugging menu are discovered to be. (..piling up.. did not only read ..ー.. neatly. )
When it boots with DB by the kernel for debugging, and mtd2 was done in the mount, writing is improper though it is possible to read somewhat for the time being.

NAND is backed up with diag menu though it is first of all broken in the said thing. Can it become calm a little because it considerably drives it at time the other day?
Error generation in restore though it manages to obtain SYST700.DBK, and restore is done. At this point, it considerably becomes blue.
The thing that restore can be done confirms the backup goods of NAND of broken, and NAND FLASH(FULL) is executed for the time being. The resignation mode around here considerably.
Restore can have been done by doing SYST700.DBK ..obtaining.. in restore. It is a considerable state of the excitement here.
It was possible to finally revive.
Thank you for information about 59414D41 Mr..

Choi at about half a day at this period.

However, restoration was very because my system had been completely customized.
When a considerably steady system can be done, one degree NAND FLASH BACKUP.
However, it is ..painful.. to take time to back up. For about one hour(With SD. )

9/15 postscripts

It has understood well and a postscript is added when fiddling with this while ..the.. output.. seeing making the cereal cable somehow. The cereal cable was connected directly troublesomely though had when seriously making it by using MAX3222 first.

The thing that tentatively entered boot and the maintenance mode can have been done though MAINTE and DIAG of C750 were incidentally put in C700. However, it seems writing in P2ROM and a furnace around here with SL-C700 on the screen of the maintenance mode because it goes out.
Even if reset hanging when the battery lock locks also replaces MAINTE, it is put on P2ROM, and it is hardware or might be either. a kooky bowl Because the advantage doesn't exist maybe even if MAINTE of C750 is put, either it is not worth putting it.
Go to the top of the page
 
+Quote Post
stbrock
post Jan 2 2006, 01:53 PM
Post #2





Group: Members
Posts: 149
Joined: 17-April 04
Member No.: 2,879



This page helped me revived my bricked C860, so 1000 thanks to DrWowe. It took more, too, so perhaps my experience will help someone else. First lesson -- don't knock your Zaurus onto the floor accidently while flashing. I'd flashed the C860 dozens of times before, but a significant knock during flashing finished it, even though the power cable didn't come out. None of the regular flashing or service menu commands worked anymore, but the led's still flashed sometimes. Fn+D+M got me the service menu again. The translated information page seems to indicate that this key sequence bypasses the NAND loader, so I assume that was scrambled.

Once I got a service menu, I thought the rest would be easy. I put the TriSoft NAND image on a CF card and tried a NAND restore, but the Z couldn't read either of the CF cards I tried, both of which worked fine in a Windows card reader. CF diagnostics reported lots of errors and concluded that the CF card was "NG" -- "Not Good" apparently. That sounded like the end of the line, but having little to loose, I played around with the diagnostic menus. The "extra menu" leads to a new page, and the "Zaurus" option on that page led to four more pages of menus, some overlapping the initial three page set, some new. I tried the option to erase NAND flash memory, which seemed to work, and got rid of some of the error messages I had been seeing, but still left my CF card unreadable. I then copied my NAND image onto still another CF card -- a Sandisk card, which people have sometimes found a problem on the Z. For some reason, the Z could read that card, so the flash worked. But the Z still wouldn't reboot from the restored image, only from the reboot option on one of the diagnostic menus. Finally, I flashed the recent pdaXrom beta and that seemed to remove the last remnants of the damage, and all seems back to normal.

As to why the Sandisk card worked, I'm not sure but have a vague recollection that at one point I formated it to ext2, then reformatted it to FAT on the Z. The other cards were likely either formatted at the manufacturer or by Windows. So the second lesson is to keep trying different CF cards formatted differently if the NAND restore program can't read your image. Maybe a card formatted on the Z works better than others in some circumstances. Hope this is useful to someone.
Go to the top of the page
 
+Quote Post
loc4me
post Jan 2 2006, 09:04 PM
Post #3





Group: Members
Posts: 141
Joined: 5-July 05
From: Tucson, AZ
Member No.: 7,538



I am interested in knowing the specail boot sequences. The only ones i know of are:
C+D+reset for flashing 5500
D+M for service menu on the 6000

I dont know any for the C3000. Could someone list all the known boot sequences please? Thankyou.
Go to the top of the page
 
+Quote Post
stbrock
post Jan 3 2006, 07:15 AM
Post #4





Group: Members
Posts: 149
Joined: 17-April 04
Member No.: 2,879



The translated message on boot sequences provided by DrWowe is difficult to interpret, at least for someone with little knowledge of the Z's hardware. I found several of the suggested sequences (QT, DL, LX, Fn-Home, perhaps others) seemed not to be recognized or to do nothing, but of course I was playing with a seriously scrambled Z. I wouldn't have tried things suggested in a document that refers to the Z's "cereal output" if I had much to loose.
Go to the top of the page
 
+Quote Post
DrWowe
post Jan 3 2006, 08:17 AM
Post #5





Group: Members
Posts: 696
Joined: 17-January 04
Member No.: 1,468



QUOTE(stbrock @ Jan 3 2006, 09:15 AM)
The translated message on boot sequences provided by DrWowe is difficult to interpret, at least for someone with little knowledge of the Z's hardware. I found several of the suggested sequences (QT, DL, LX, Fn-Home, perhaps others) seemed not to be recognized or to do nothing, but of course I was playing with a seriously scrambled Z. I wouldn't have tried things suggested in a document that refers to the Z's "cereal output" if I had much to loose.
*


I can shed light on a few of them. Unfortunately, I don't read Japanese either. :-(

D-L boots normally, except that you get an extra command passed to the kernel. What (if anything) is done with this information is up the ROM and the boot scripts. You can see it if you "cat /proc/cmdline". I think the Sharp ROM ignores it.

D-B boots directly into the rescue partition and gives you a command prompt. I've found this one to be very useful.

Q-T I haven't tried myself, but it's supposedly an alternate way of flashing with no service menus or dialogs. It doesn't use a regular NAND image, instead you need it broken up into multiple parts like this: http://www.externe.net/zaurus/flash/nand/parts/6000L/

Some of the others I tried I didn't notice anything at all, at least on my 6000. I think you might need a "cereal cable" to do anything with them. dry.gif
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 25th December 2014 - 04:13 AM