Rockbox Development > New Ports

Toshiba Gigabeat S30

<< < (6/14) > >>

saratoga:
You mean they don't sign the bootloader too?

ptw419:
I can confirm what Zunepet is stating is true. I have managed to get the Gigabeat V30 updater to work w/ my S30 by simply going through the updater w/ a hex editor and replacing every unicode reference w/ a "gigabeat V30" to "gigabeat S30". The udpater flashed my S30 and replaced my current firmware. The bad thing is my S30 is dead for now :\ . Great job Zunepet, and many thanks for what you have accomplished!!  

edit:I've actually managed to restore my s30  firmware w/ this method.

ZunePet:
> You mean they don't sign the bootloader too?
It is digitally signed and checked before it is used. That is a very good thing (otherwise my GigaBeat and ptw419's would be permanent bricks now).

During the update process it will try to reflash the ROM with the updated EBoot.bin/pmcboot_secure.bin and Recovery.bin. It will attempt a reflash only if the digital signatures are valid (that's a good thing)
Those two files you upload must be the GigaBeatS ones, unaltered -- otherwise it will wedge (temporarily, until you reformat the drive).

The NK.bin is the one we want to play with, and ideally only once. After that, new later stage bootloaders / "firmware" (eg: .rockbox\rockbox.gigabeat) should be loaded from the 2nd disk partition (the one we have semi-direct access to; what you see as "Storage" in Windows Explorer)

AnthraxPants:
Thanks for the link toffe  :)
Plenty of info provided,  thank you to anyone who has helped.

Toshiba has dropped prices on S30 here in Australia.  Now available for around AU$60 less in price, roughly AU$320 or US$250.  

I'm still flat out working but should have a break late next week and be able to finally look at purchasing another S30 soon.  I will try to make time to jump on IRC next week.

Kramdra:
>The GigaBeatS uses digitally signed firmware. If you change almost any byte in >the NK.BIN the SHA-1 hash changes, it fails the signature test, and the image >will not be run.
>Fortunately the boot loader is not very secure. With a trivial mod to the >NK.BIN file, you can disable the check (BTW: 16 bytes)

How do you get round the check, would it just be a case of for every bit changed, we need to change another bit in the opposite way, in a similar place of the code? I read this can be done on the zune/something else...

would there be any other issues to prevent code from running?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version