ROM Cooking! A Pain In The Ass!! Lets Put Are Heads Together

[austinsnyc]

well I got BuildOS to work up to the point of building the Defualt.hv and boot.hv and then it crashes. I got the Imgfs tools all the way up to the point of rebuilding the Nb and then I get "MSFLSH50" error so I feel like I'm banging my head back and forth for nothing. I know we dont need to remove bytes like we did with the Hermes but I need some help here!! Pof, Oli, Taz Someone help!!

[pof]

Using the ImgFsTools should be exactly the same as Hermes, except that in hermes the NAND block count was 0x200 and in kaiser is 0x800.

[austinsnyc]

OK so after thinking about this for a second we need to change the code to to dump and build at that block count correct? thats something i dont know how to do myself

[austinsnyc]

Anyone have any other thoughts on this?

[donsaxena]

dude that perceptive pixel thing is amazing. you developed that?

[duttythroy]

I'm pulling out my head here as well friend so near but yet to wait:rolleyes:

[austinsnyc]

dude that perceptive pixel thing is amazing. you developed that?

I build them yes we have a whole team of software and optics eng... people that work with us. I am the one that builds the units, Lead production manager yes thank you it is the only true Multi-touch system on the Market today :)

[tadzio]

Using the ImgFsTools should be exactly the same as Hermes, except that in hermes the NAND block count was 0x200 and in kaiser is 0x800.

There's another difference: the MSFLSH50 header is at position 0x800 rather than 0x200. That's why ImgFsToNb fails currently.

A new, Kaiser-compatible version will be available shortly.

Cheers
tadzio

[duttythroy]

There's another difference: the MSFLSH50 header is at position 0x800 rather than 0x200. That's why ImgFsToNb fails currently.

A new, Kaiser-compatible version will be available shortly.

Cheers
tadzio

Great job ,thanks again:D

[pof]

There's another difference: the MSFLSH50 header is at position 0x800 rather than 0x200. That's why ImgFsToNb fails currently.

A new, Kaiser-compatible version will be available shortly.

Thank you tadzio :D

[jcespi2005]

There's another difference: the MSFLSH50 header is at position 0x800 rather than 0x200. That's why ImgFsToNb fails currently.

A new, Kaiser-compatible version will be available shortly.

Cheers
tadzio

Great news :) thanks for helping here...

[Whiterat]

Hey guys,

Im not really into coding things (generally not great at it) but I do enjoy reverse engineering :)

I have patched:
nbsplit.exe
nbmerge.exe
imgfstonb.exe

They should in theory work now for the kaiser, They dump fine and seem to recreate fine too (although I have no kaiser to test on).

I take no responsability for any damage done,blah blah, this is just a pure test and I take NO credit for the work.

Great respect to tadzio and I am in no-way trying to steal his thunder.

Usage:
nbdump.bat OS.nb

[austinsnyc]

...........................

[tadzio]

DO NOT USE ImgFsToNB FOR THE KAISER YET!

I am currently re-working these tools, and I just discovered that I made an assumption in the ImgFsToNB (and other) tools that is simply incorrect for the Kaiser.

As a result, the generated .nb looks good at first glance (and even can be dumped again), but when flashed, your Kaiser will not boot!

Give me a few more days, and I'll release a new version that will handle the Kaiser ROMs properly (unless there are more surprises like this in my code...)

Cheers
tadzio



Hey guys,

Im not really into coding things (generally not great at it) but I do enjoy reverse engineering :)

I have patched:
nbsplit.exe
nbmerge.exe
imgfstonb.exe

They should in theory work now for the kaiser, They dump fine and seem to recreate fine too (although I have no kaiser to test on).

I take no responsability for any damage done,blah blah, this is just a pure test and I take NO credit for the work.

Great respect to tadzio and I am in no-way trying to steal his thunder.

Usage:
nbdump.bat OS.nb

[le_cactus]

well I got BuildOS to work up to the point of building the Defualt.hv and boot.hv and then it crashes. I got the Imgfs tools all the way up to the point of rebuilding the Nb and then I get "MSFLSH50" error so I feel like I'm banging my head back and forth for nothing. I know we dont need to remove bytes like we did with the Hermes but I need some help here!! Pof, Oli, Taz Someone help!!

Hi austinsnyc,

Congratulations on your first ROM! No let's put our heads together en share some knowledge :D

TIA,

Cheers,
Cacti

[tadzio]

Hi austinsnyc,

Congratulations on your first ROM! No let's put our heads together en share some knowledge :D

TIA,

Cheers,
Cacti

austinsync uses a private build of my ImgfsTools. I added a way to disable the bigstorage feature, and the tools now work in that mode for the Kaiser. Of course, I want the bigstorage back, so I'll try to find out over the weekend what goes wrong there. As soon as I know, I'll release the tools. :-)

Cheers
tadzio

[jcespi2005]

Thanks for this, waiting your public release to start modifying my spanish ROM...

austinsync uses a private build of my ImgfsTools. I added a way to disable the bigstorage feature, and the tools now work in that mode for the Kaiser. Of course, I want the bigstorage back, so I'll try to find out over the weekend what goes wrong there. As soon as I know, I'll release the tools. :-)

Cheers
tadzio

[duttythroy]

austinsync uses a private build of my ImgfsTools. I added a way to disable the bigstorage feature, and the tools now work in that mode for the Kaiser. Of course, I want the bigstorage back, so I'll try to find out over the weekend what goes wrong there. As soon as I know, I'll release the tools. :-)

Cheers
tadzio

cheers mate

[le_cactus]

austinsync uses a private build of my ImgfsTools. I added a way to disable the bigstorage feature, and the tools now work in that mode for the Kaiser. Of course, I want the bigstorage back, so I'll try to find out over the weekend what goes wrong there. As soon as I know, I'll release the tools. :-)

Cheers
tadzio

That is great news. Hope you'll be able to release it soon then.

Danke!

Cheers,
Cacti

[tadzio]

That is great news. Hope you'll be able to release it soon then.

Danke!

Cheers,
Cacti


I would need one or two testers now - someone with a Kaiser who has some experience with flashing ROMs already, who is willing and set up to flash a ROM, and who can recover from a non-booting ROM easily. ImgfsToNb can now operate in several modes, and I need to know which work and which don't.

Note: I do know that at least one mode (the one gives the most free storage) does not work yet, so if you are willing to beta-test, you will very likely flash a non-booting ROM. This can, of course, be rectified by flashing a known-good ROM. Only apply if this is okay for you!

If you want to help me, send me a PM with an email address or an ICQ number, so that I can contact you. austinsync already helped me a lot here (many thanks!), but he's in a timezone where people still sleep right now. :-)

Cheers
tadzio