Flashing with the 32-30 kernel worked, but I am unable to retrieve my backup. I tried renaming the original file (called '2004-04-15-20-35' to '2004-04-15-20-35-unknown' but it still can't find the file in the restore application.

For some reason I seem to have a different backup naming convention to the one Maslovsky mentions in his notes, 003-01-01-00-01.backup_SL5500-US-3.

I tried to put a .backup in my name but it won't accept '.' as a character.

There's now 4 of us with this problem so clearly it doesn't work - will have a go with the 32-30 one and let all know the results.

Make that 5.... no joy with the 64-00, but the 32-30 is fine.... 64-00 locks up after the boot image - throws up running the rc.rofilesys script as far as I can tell. I run my own custom filesystem image that works with either sort of kernel and it looks like it blows up when its checking the /proc/cmdline to find out the memsize used....

Tried reflashing together with w initrd.bin from the sharp 3.13 rom (rombursted) and no joy either. Same result when starting. Pinguin logo and the INIT: version 2.7.8 booting and hard lock.

Only diference is that when the flashing process ended the two leds starting flashing together. This stopped as soon as the hard reset button was pressed. Never saw this before and I have tried almost every rom out there....

What can I try next? Does anyone have the 64-0 rom working on their Zs?

Hi maslovsky!
Thank you very much for take the time to answer and the good will to help!!!... The simple suspend and put in the craddle put the ligth in order, now steady and normal!

If this may help some of the other users, as a report of working, my Z5500 now appears to work fine, but I use the 30-32 rom and my Lexar SD card is formatted in VFAT (for easy access under windows and by means a card RW adapter...), and the initrd.bin of the upgrade is ProtoTKC v1.0, and the standar backup file was restored withouth rename it.

Im thinking about made a test with this new Cacko Zimage 64-0+ProtoTKC2.0+HomeOnSD script but Im not clear if there is a trouble with this combination, and I must make an effort to get the time for doing try and error work because my real work is a little charged by this days,so,if someone tried it or know see something that could make that the things dont go fine/work, well, some advice/alert will be appreciated, specially if it could save some waste of time/efforts...

Well, now we know what's wrong!!! It can't be used on the stock sharp rom.

Gotta say though Maslovsky, in your initial instructions it specifically states that the new kernel would work on the sharp 3.13 rom. Guess we are all lucky that we haven't turned our Z's into fancy new paperweights.

I have the 32-30 kernel flashed on my stock sharp 3.13 and it is so far working fine. Any plans to make the 64-0 work on the normal rom?

Well, now we know what's wrong!!! It can't be used on the stock sharp rom.

Gotta say though Maslovsky, in your initial instructions it specifically states that the new kernel would work on the sharp 3.13 rom. Guess we are all lucky that we haven't turned our Z's into fancy new paperweights.

I have the 32-30 kernel flashed on my stock sharp 3.13 and it is so far working fine. Any plans to make the 64-0 work on the normal rom?

Yes, I must have been not clear enough on my instructions, sorry. I've updated them. 64-0 cannot work on normal ROM, since there is no space for /home. You have to flash Cacko/Crow ROMs to use 64-0 config.

Yes, I must have been not clear enough on my instructions, sorry. I've updated them. 64-0 cannot work on normal ROM, since there is no space for /home. You have to flash Cacko/Crow ROMs to use 64-0 config.

I run a Crow like ROM and the 64-0 still doesn't work, maybe I didn't make that clear in my previous reply. No worries as I've gone back to my own kernel, if I can find the details of the patches I might roll them into mine and see what happens.