Quote:
Originally Posted by natemcnutty
Crap, you're right! I renamed the damned file when I was messing around with compiling tinboot and compared it to itself... Just downloaded them directly off the gits and compared with HxD, and I do see the differences from 0x2C to 0x32:
Code:
IMGFS.BIN: 4C 5A 58 00 82 46 02
EMPTYIMG: 58 50 52 00 FE C2 01
Unfortunately, my battery is dead at the moment, and I have to let it fully charge before I can flash these test tinboots. I might get lucky and be able to try this tonight. If not, tomorrow morning when I get in to work, I have a folder with 4 different tinboots to try out in order of least to most brick risk :P |
You "should" be good on not bricking, they are pretty good at handling a bad flash! Once you build them you can try to extract them just as a test... If you can't do that then you shouldn't flash them.
I was trying to do the same thing today, had a couple of bad flashes...
I think I was missing something.
If you want I can test, probably better with a USB cord, send me a PM or stop over at IRC chat...
What did you do to get them made?
Our imgfs.bin is getting inserted during the making process with the ImgfsToNb.exe. The Vogue's emptyimgfs is just getting built right in the kernel, this is why we don't see it on the NBHInfo.exe.
So... We should be able to just add it do the kernel like you have it above and forget about it. We might not even need it however, I read somewhere that it was just there because some flashing utilitly's (older one's like the Vogue) can't handle it.