OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: Capn_Fish on June 14, 2007, 07:47:53 pm
-
Issue: Installing uBoot fails (got flashing lights). Charge light doesn't come on.
Solution: The three Rs: Reformat the card (FAT16, under Linux, mkfs.vfat -F 16 /dev/CARDDEVICE), redownload the uBoot files, and retry the process.
Issue: pdaXrom won't find the install files when trying to install the ROM.
Solution: Boot into the emergency system and check to see that the card is mounted (type 'df' to see. If /dev/hdx1 or /dev/mmcblk0p1 is listed, it's mounted). Then, cd to the directory with the install files, for CF installs:
cd /mnt/cf
For SD:
cd /mnt/card
Then execute this:
sh autoboot.sh ./
The install should run fine.
Issue: My Z won't boot after trying to install pdaXrom. I want to go back to ROM xyz.
Solution: Do a NAND restore. Download the correct file from here (select your Z model on the right):
http://www.trisoft.de/en_downloads.htm (http://www.trisoft.de/en_downloads.htm)
and put the SYSTCXXX.DBK file on an SD/CF card (FAT16 formatted). remove all power from the Z (battery and AC), then hold Fn+D+M and insert the adapter. YOu should get a diagnostics menu. Go to the third page and select NAND restore. Note that you should only have one card (either SD or CF in the Z at this point).
If it doesn't see the file, 1, make sure the name is in all caps, and 2, see below.
You can then install ROM xyz normally.
Issue: After formatting a card, I can't get a NAND restore/other FAT16-sensitive action to work.
Solution: Make sure the system ID is set correctly. fdisk your card:
for SD:
fdisk /dev/SDDEVICE
for CF:
fdisk /dev/CFDEVICE
Then set the partition's ID to 6 by typing 't' for type, then the patition's number (1), then '6' for FAT16. Reformat your card:
mkfs.vfat -F 16 /dev/CARDDEVICE
then put the necessary files on the card and retry the action.
Issue: My card isn't found when trying to do a NAND restore or I get the "SYSxxx.DBK: file not exist" error when I try to restore my Z.
Solution: Make sure you have the DBK file on the root of the card, and that the card is FAT16-formatted and the System ID is set correctly (see above). For SD, make sure there isn't a CF card in the CF slot as well.
I feel like I'm missing other common issues, if so, please post them.
If this thread could be stickied, that would be great.
-
Question :
If it's dead, how do you get it to come back to life. I just tried mine and it's completely dead now.
-
What did you do/try to do?
EDIT: This only covers software "bricking." If it's a hardware issue, these probably won't help .
-
Phew Awesome! it worked, A mod can delete my posts id they would like, to conserve the threads integrity. Thanks allot.
-
If you format the card device instead of the partition device (i.e. /dev/mmcda instead of /dev/mmcda1) you don't have to worry about setting the partition types correctly, since there aren't any. Windows/cameras/etc tend to format removable media like that anyway; so compatibility isn't a problem. Heck, a partitioned card is the unusual case!
The diag menu is quite happy with such a formatted card.
-
Thanks for pointing that out. I was under the impression that having no partitions made it not work, but maybe that's for automounting (with a default fstab).
-
Thank you very much for this thread - I thought I'd bricked my 860 when I installed u-boot and it didn't re-boot.
One thing to report: I couldn't get the emergency system to see anything on my CF card (i.e. the nandlogical commands in the install guide) until I mounted it manually with
mount /dev/hda1 /mnt/cf
It may have been because the card was in when I applied power. Hope that helps someone.
-
I'm confused... I tried to install u-boot... now my Z doesn't have a charge light, i can't get into any of the menu's to try any of these recoveries... what do i do?
k
-
I'm confused... I tried to install u-boot... now my Z doesn't have a charge light, i can't get into any of the menu's to try any of these recoveries... what do i do?
k
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163453\"][{POST_SNAPBACK}][/a][/div]
You can always get into the Fn+D+M menu.
Remove the battery and AC from your Z, hold down Fn, D, and M, then insert the power cable.
-
I'm confused... I tried to install u-boot... now my Z doesn't have a charge light, i can't get into any of the menu's to try any of these recoveries... what do i do?
k
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163453\"][{POST_SNAPBACK}][/a][/div]
You can always get into the Fn+D+M menu.
Remove the battery and AC from your Z, hold down Fn, D, and M, then insert the power cable.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163457\"][{POST_SNAPBACK}][/a][/div]
cool, thx. I thought it was just D+M, not Func+D+M.
k
-
You can always get into the Fn+D+M menu.
Remove the battery and AC from your Z, hold down Fn, D, and M, then insert the power cable.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=163457\"][{POST_SNAPBACK}][/a][/div]
Great! I only found until now D+M but not Fn. I'll try later and hope it works
Thank you for the information!
-
I tried to install U-Boot. It seemed to work- I got to a prompt. I simply left my Z sitting there like that while I downloaded a newer debian tarball. The Z went black. I can get into func D+M ok, but I cant reboot or anything of that kind. Is the only option when U-Boot does this to do a Nand restore, install U-Boot again and....what don't let the Z sit? Install a new OS in less than 5 minutes or else?
Well--off to a nand restore.
-
To boot into the uboot emergency mode, you need to press [OK] when booting starts.
But to install debian, I recommend having the whole rootfs ready before installing uboot and the kernel, because uboot cannot handle ext3 and will freeze when accessing the internal drive or CF.
-
To boot into the uboot emergency mode, you need to press [OK] when booting starts.
But to install debian, I recommend having the whole rootfs ready before installing uboot and the kernel, because uboot cannot handle ext3 and will freeze when accessing the internal drive or CF.
I kinda got the last part-But I had preessed ok--it scrolled a bunch o stff then came to a prompt. isn't that what iti is supposed to do?
Anyway, If i can mke uboot do anything but cause to restore my Nand (3x this morning and counting) I was planning to install the taraball to a 1 G CF, then see about doing someinthing with my internal drive
-
To boot into the uboot emergency mode, you need to press [OK] when booting starts.
But to install debian, I recommend having the whole rootfs ready before installing uboot and the kernel, because uboot cannot handle ext3 and will freeze when accessing the internal drive or CF.
I kinda got the last part-But I had preessed ok--it scrolled a bunch o stff then came to a prompt. isn't that what iti is supposed to do?
Anyway, If i can mke uboot do anything but cause to restore my Nand (3x this morning and counting) I was planning to install the taraball to a 1 G CF, then see about doing someinthing with my internal drive
Am I supposed to include a kernel or something on the card I install Uboot from?
-
To boot into the uboot emergency mode, you need to press [OK] when booting starts.
But to install debian, I recommend having the whole rootfs ready before installing uboot and the kernel, because uboot cannot handle ext3 and will freeze when accessing the internal drive or CF.
I kinda got the last part-But I had preessed ok--it scrolled a bunch o stff then came to a prompt. isn't that what iti is supposed to do?
Anyway, If i can mke uboot do anything but cause to restore my Nand (3x this morning and counting) I was planning to install the taraball to a 1 G CF, then see about doing someinthing with my internal drive
Am I supposed to include a kernel or something on the card I install Uboot from?
Uboot and the kernel are separate and they use two totally different sets of files to install. If the installation of uboot is successful and can boot into the uboot emergency mode, i think it's better to remove all the uboot files from the card (say, a SD) and put only the autoboot.sh and the kernel.img on it and then run /mnt/card/autoboot.sh to flash the kernel. This applies to both pdaXrom and debian eabi (yonggun kernel).
-
This is better place to my ask, so I ask again....
Hello everybody!
I made something wrong with my Zaurus SL-C1000. I tried to install U-boot, but I didn't erase NAND before. After U-boot installation of course everything was wrong. I went to Service menu to NAND restore and I did it using Trisoft NAND Backup for my Z. After reboot everything was wrong. On forum someone told me, that I should to erase Nand before restoring. I tried to do it, but during NAND erase process I have communicate:
erasing...1
Bad Block Num = 128
ERROR! Too many bad.
code=(201)
During restore process I have communicate:
Restore...failed
format error
Now My Zaurus is broken at all. Have you got any idea what to do now? I will be very appreciate for help.
-
Try doing a NAND restore without the NAND erase, if you haven't already. That's what I have done in the past, and it seems to work.