Thank You for your continued support and contributions!
hey by the way i wonder how close the fuse is with the view?
if the devs have a boot loader out yet for the fuse that is.edit**never mind they dont lol it was a thought though
mv firmware.mi4 firmware.orig.mi4./mi4code decrypt -s firmware.orig.mi4 plain.bin./mi4code build plain.bin plain.mi4./mi4code encrypt plain.mi4 plain.enc.mi4 view./mi4code sign plain.enc.mi4 firmware.mi4
./mi4code build bootloader.bin bootloader.plain.mi4./mi4code encrypt bootloader.plain.mi4 bootloader.enc.mi4 view./mi4code sign bootloader.enc.mi4 firmware.mi4
You may need to sign before you encrypt instead of after; that's what I do, but it may work your way too. Maybe the "offs_id" needs set when you build. The firmware.mi4 for v1e200 rockbox gets accepted, so it must be similar to what you would do on an v1e200 to build an mi4 from a bin. I'll try some things when I get home.Edit:When you modified the original firmware.mi4, did you change the file size? Just wondering. I looked into it a little more and the commands look correct from what I've read. I'll try it to write and compile some custom code from scratch and build it in the same way.
was the new checksum calculated correctly and inserted into the file?
The modified bootloader I used fails to write anything, so I guess the SD interface is different or at another location.
Quote from: obo on March 20, 2009, 10:25:42 AMThe modified bootloader I used fails to write anything, so I guess the SD interface is different or at another location.So we need to find the location of the SD interface? Which would be a good place to look; the bootloader.rom or the firmware.mi4?
Page created in 0.082 seconds with 22 queries.