OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Sharp ROMs => Topic started by: havoc on February 08, 2004, 10:09:21 am
-
I attempted to flash my 5600 with the OpenZaurus ROM, following the OpenZaurus instructions of holding down the C and D keys while resetting. I got flashing LEDs, but the flash never completed (after waiting 30 min+), now I have no Zaurus. I have attempted flashing back to the Sharp provided 5600 ROM.
If I\'d dug a little deeper, I\'d have found that the update for the 5600 goes through the menu, and not the C+D+reset method.
Am I pretty much screwed here, or is there a way for me to get my Zaurus back up?
havoc
-
First,
bring up the maintenance menu and select format, this should work
if not, remove the battery for about 2 hrs and try again with the Sharp files to flash back
Greg
-
There\'s no menu to choose from. No boot, \"no nothin\'.\"
The batteries out. I\'ll see what happens when I get back from Church.
Thanks for the tip!
-
There was a thread on the dev/net about this problem but for some reason I can\'t search more then 30 days back without being redirected to Sharp. I will check this later.
This may help some:
http://www.zaurususergroup.com/index.php?n...ht=bricked+5600 (https://www.oesf.org/forums/index.php?showtopic=1457&highlight=bricked+5600)
Greg
-
Thanks, that helped. I can get to the Reset+D+M and Reset+D+P menues. I have performed, successfully, a NAND Flash (Full), but that doesn\'t seem to solve my problems.
How do I \"un-brick\" this thing? All I want to do is a ROM, any ROM loaded back into this thing and have it run.
-
Referencing this thread:
http://www.zaurususergroup.com/index.php?n...iewtopic&t=1152 (https://www.oesf.org/forums/index.php?showtopic=1152)
Can anyone send me a full NAND Flash Backup for an SL-5600? This might get me up and running again.
havoc@harrisdev.com
-
what is nand?
cant you just use load the files update.sh, zImage.bin from current sharp rom to it?
-
Havoc, do you know how you get to the Maintenance menu? It\'s in all the 5600 ROM upgrade instructions.
Look at the Linux user instructions here:
http://www.myzaurus.com/ROMupdate6.asp (http://www.myzaurus.com/ROMupdate6.asp)
-
That\'s great, IF you haven\'t already bricked your 5600 by using the upgrade instructions for OZ! I DON\'T HAVE A MAINTENANCE MENU BECAUSE I HOSED THE WHOLE THING.
THERE IS NO WAY TO GET TO THE MAINTENANCE MENU ON MY 5600. What I need is a workaround to get the Maintenance Menu BACK.
In Case anyone missed this one critical point, There is no Maintenance Menu on my 5600 because I blew it away when I tried to update the ROM using the D+C+Reset instructions found on the OZ page.
Now, is there any way I can replace the NAND on my mahcine, or is there any other way I can get this thing back to the point where I DO have a Maintenance Menu?
-
That\'s great, IF you haven\'t already bricked your 5600 by using the upgrade instructions for OZ! I DON\'T HAVE A MAINTENANCE MENU BECAUSE I HOSED THE WHOLE THING.
THERE IS NO WAY TO GET TO THE MAINTENANCE MENU ON MY 5600. What I need is a workaround to get the Maintenance Menu BACK.
I know your upset, but that won\'t help you here. This is a tricky area to repair.
Here\'s a link to read:
http://externe.net/zaurus/forum/viewtopic....&highlight=nand (http://externe.net/zaurus/forum/viewtopic.php?t=96&highlight=nand)
Here\'s Klaus Weidner\'s link, he has had some luck with this ? go to his sight and email him:
http://pocketworkstation.org/ (http://pocketworkstation.org/)
Good luck
Greg
-
yyyyyyyyyyyyeah, that made it worse.
I renamed the SYSTC700.DBK to SYST5600.DBK, and did a NAND Restore. That was BAD.
Now, my other menus are gone. The best I can get is flashing Mail and Battery LEDs on a D+C+Reset (Full Reset).
The Z is on it\'s way to Romeoville, IL, to be serviced. I\'ll ship it out this afternoon.
At least I can say that I\'m impressed with Sharps phone support in the US! Got an answer AND a knowledgeable technician on the first call.
I bet I\'m a little gun shy about OpenZaurus ROMs after this.... maybe I can pick up a used 5500 to test ROMs with in the future....
-
I know this is a little bit after the horse has bolted, but for the benifit of anyone reading this in the future with a similar problem.
Try to get a nand image from someone with the same model zaurus as yours.
NEVER try and flash a different models nand backup file to your machine.
The only exception to this ( at the time of writing ) are the c760 and c860, which are hardware identical to each other, even then you are still taking a risk. I would advise you to locate a nand image from a machine with the same model number.
havoc, I know this doesn\'t help much now, but had you waited for a nand backup from another sl5600 you would have almost certainly cured your problem.
The trouble with nand backup files is that it contains everything on your machine including all your pim data, passwords, any comercial apps you may have bought etc. So people would be daft to post one from their machine.
Given time, somebody who had recently re-flashed could have posted a \"clean\" image for you to apply to your machine.
Conics hold \"clean\" images from the clamshell series, maybe some kind sould coul still upload a \"clean\" sl5600 rom for future folks to use in cases like this.
The other moral of this story is to always take a nand backup of your machine before trying a new rom, or anything that has a risk associated with it.
I take a nand backup of my machine before I install any software that I haven\'t previously tried as it is the easiest/quickest way of recovering your machine fully in case things go wrong.
So far I have only done two nand restores, and both worked perfectly.
Peter.
-
yeah, Peter, I\'m right there... just got there a whole lot later than you did.
I waited for 12 hours. I got 0 indication of an SL-5600 NAND backup coming this year, so I jumped. No biggie.
Can you guess what the first thing I\'m going to do when it comes back is? You bet! There will be a copy of SYST5600.DBK available at http://www.galacticslacker.com/ (http://www.galacticslacker.com/) within the hour of my opening the box.
While it\'s still fresh, and no personal data. That\'ll be a nice touch.
Too bad that no one is aware of the value of such a backup BEFORE they start messing with their unit.
Oh, well. I\'m glad I can be of service to future generations of Zaurus users.
-
I have 2 5600\'s, and one is a fresh barely touched sitting next to me. If someone could point me in the right direction to a good tutorial on how to make a NAND Backup I could make one out of the fresh 5600. It\'s also one with the PXA255 processor, so maybe someone with the PXA250 processor could get one also?
havoc: which kind do you have coming in?
-
It\'s a 5600, and I just sent it to the Sharp Service Center this morning. I had no idea they had already changed the CPUs in the 5600 until just now.
Based on my most recent experience, I\'ll let someone else tell you how to get to the Maintenance Menu, but if you want to send me a NAND Backup, I\'ll be happy to post it with any helpful info.
Shoot me a note at havoc@harrisdev.com, and we\'ll iron out the details of getting me the file.
-
I don\'t know why all this NAND backup and flashing is necessary and it\'s just asking for trouble. AFAIK, NAND flashing flashes absolutely everything, including the bootloader, which is a Bad Idea IMHO.
I would only recommend flashing using the updater.sh, zImage.bin and initrd.bin files with the OK+Cancel Maintenance Menu. This is practically fool proof and doesn\'t overwrite anything that could turn your precious into an expensive paperweight.
If you want to make sure you can get back to your previous setup, you only need to make a tar of /home and ensure you\'ve got the zImage.bin and initrd.bin files for your current ROM, which is what Sharp supplies the 5600 ROMs as.
-
Hi,
So if you flash the sl-5600 using this, lets say to put a different rom , OZ , zynergy, and the flash failed for some reason, by having these files, you should easily be able to reflash to standard rom?
Thanks
-
I don\'t know why all this NAND backup and flashing is necessary and it\'s just asking for trouble. AFAIK, NAND flashing flashes absolutely everything, including the bootloader, which is a Bad Idea IMHO.
I have to agree with this 99.9%
@ havoc, I\'m sorry this happened
@ Guest, Normally you can return to Sharp rom with Maint. Menu.
That being said, after what has happened here (because of a little impatience) I have made my personal nand backup file. I had never been in the service menus before this because this procedure is not clearly documented yet. This nand file is 66.1mb and the normal backup file is 27.5 mb. With these 2 files I can now restore everything including the bootloader to it\'s present state.
Now as zbones has posted I could not possibly give this file out, but the next time I have a clean flash I will make one that I can.
The other problem here is the fact we now have two SL-5600 Nand files, two different cpus IMO would make for two different Nand Files?
My problem is I use a 56k dailup, and for me to upload a 66 meg file with photos showing the menus with a very clear set of instructions would take a very long time.
Now to sum this all up, if someone has a high speed connection, a 5600, and is willing to do this I think this would be a great idea.
My two cents
Greg
-
I don\'t know why all this NAND backup and flashing is necessary and it\'s just asking for trouble. AFAIK, NAND flashing flashes absolutely everything, including the bootloader, which is a Bad Idea IMHO.
I would only recommend flashing using the updater.sh, zImage.bin and initrd.bin files with the OK+Cancel Maintenance Menu. This is practically fool proof and doesn\'t overwrite anything that could turn your precious into an expensive paperweight.
If you want to make sure you can get back to your previous setup, you only need to make a tar of /home and ensure you\'ve got the zImage.bin and initrd.bin files for your current ROM, which is what Sharp supplies the 5600 ROMs as.
As has already been pointed out, \"that horse done left the barn!\"
More and more, I\'m getting the impression that there may be an underlying hardware issue with my 5600. The initial C+D+Reset flash attempt I made should have correctly flashed the ROM even though that is not the \"correct\" procedure for the 5600, it still should have worked. When it failed to flash the ROM correctly, it should have failed to a safe state, and I should have been left wondering why the ROM had not been replaced with OZ.
The NAND restore was a last-ditch effort to recover the unit. Being that no SL-5600 SYST5600.DBK was available on the net (according to the Gospel of Google), I used the C700 NAND backup out of desperation. I think it was already too late at that point, so it was going to have to make it\'s pilgrimage to Romeoville, IL, either way.
None the less, future Seekers of the Zaurus will have a clean NAND backup in case they find themselves as desperate as I was at that moment. I\'ll leave as much machine specific info with the file as possible, and all due warnings.
-
I decided to share my 5600 NAND backup file with the community. It is 250 CPU, basic the Kompany ROM with no additional software. The size of the file is 67Mb. I have just made it and have not tried restoring from it. I could not upload it to the Download section here (maybe there is size limitation). Please post here if you have web space on http or ftp server to post this file. I do not want to disclose my email to everybody in the world.
-
kurochka
I would suggest sending a pm to offroadgeek for instructions.
Thanks
Greg
-
I\'ve sent the file (NAND 5600/250 backup) to havoc. He promised to put it on his own site.
-
Okay, kurochka, you can find the link to the NAND image here:
http://www.galacticslacker.com/perl-bin/re...e?folder=Zaurus (http://www.galacticslacker.com/perl-bin/re?folder=Zaurus)
Please review the wording and let me know of typos, misspellings, errors or any additions or modifications.
I wonder if anyone will be brave enough to try it after reading our disclaimer?
-
Yahoo! My Z SL-5600 will be back tomorrow after it\'s quick pilgrimage to Romeoville, IL!
I only had the silly thing for a few days before I bricked it and had to send it back, but I\'m SO looking forward to getting it back.
-
I did the same thing with my c860... Is there a rescue procedure or something? Or do I have to attach it to a serial cable to read the output?
-
Since I\'m fooling around with creating a custom ROM, I will post a NAND image of the default ROM (1.32) setup in it\'s default settings before doing a thing with it (before even resetting it), and will post it in a few days (possibly tonight depending on how much time I have). Then once that\'s done I\'ll go grab the default ROM\'s root and go wild with making a new ROM...
But the NAND backup should be coming sometime soon. I\'ll post link when I have it, since it can\'t hurt to have more than one NAND backup.