Rockbox Development > New Ports
Sandisk Sansa View
crackmonkey421:
Thanks zivan. I tried your modified firmware and it didn't work. I got this on my screen:
Invalid image
Object loading failed while booting
Please connect USB cable
I connected the USB cable and put the original firmware.mi4 back on and all is back to normal. My easy success recovering makes me want to keep trying though.
Other question: What windows compiler do you use for mi4code.c? I tried Dev C++; didn't work. I have linux installed, but I'd rather use windows.
On another note, to get into recovery mode you have to completely shut down the sansa view first. To do this just hold the power button for longer than usual. I was very confused for a few minutes.
zivan56:
Cygwin should do it (with proper development packages and libgcrypt). Just follow the steps on the wiki for setting up a build environment (you don't have to follow the part where you run setup.exe again). Then just run the run given on the mi4code page to compile it.
I didn't have a running Linux install, so I used the old Windows binary provided. This might have been the reason (I didn't change the size of the binary, just letters in strings).
removed (modified string, but with latest mi4code)
removed (not modified, but decrypted and re-encrypted)
Bagder:
Zivan's second (unaltered) image would be very interesting just to see if our "dummy-sign" approach works on the View or not.
crackmonkey421:
Well I think this is great news: that second unaltered image works fine. I'll be using my View at work all day today with that firmware, but I'm sure there will be no problems.
Bad news: the modified image still doesn't work. Same error as before.
So I guess the old signing approach still works but we got some strings modified that it doesn't like in Zivan's modified firmware.
I'm not giving up... just getting started. I'll be making small changes and flashing. If anyone has any other firmwares to try or a View to flash, I'd love the help.
If I have enough free time I'd also like to research the original Sansa e200 project for more ideas.
zivan56:
I guess it may be a checksum issue? When I did a strait decrypt/re-encrypt, it didn't change the checksum. However, when modifying a single character it changed (for obvious reasons). Another possibility is that is may use a second checksum somewhere else in the firmware which has not yet been discovered.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version