I've found something intereseting [Only registered and activated users can see links. ].
brf6350.bin is very similar to those ~11kbytes being sent to bluetooth module by fw_all.bin.
And it's called a bluetooth firmware there. So I guess Giomen is right.
The strange thing is that brf6350.bin is not a monolithic peace of code, it's a sequence of packets delimited with 0x01 byte. So the data is formatted in the following way:
0x01 <2 bytes for message code> <1 byte for message data length> <message data> 0x01 ... repeat until end of file.
The same thing is valid for data inside fw_all.bin, it is treated as a sequence of packets by fw_all.bin
There are also never bluetooth firmware versions [Only registered and activated users can see links. ], but it's also said that each firmware requires it's own intialization script. So, I guess, it's not easy to replace bluetooth firmware inside fw_all.bin.
lolypop000
006-D1283-01.bin doesn't look like an encrypted file, because there are some non-random byte sequences like E1 E0 E3 E2 E5 E4 E7 E6 F9 F8 FB FA.
And, assuming it's not encrypred, it's not a firmware. Can you check if it's created by fw_all.bin? Maybe it's some kind of a diagnostic log.



Likes: 


Reply With Quote
Bookmarks