Poor wording.Flashed fine and seems to be a bit of an improvement. Haven't used it long enough to comment on battery life but reception seems better in low signal areas.
What does "sort of works" mean?
Here are the hashes for VRUEMJ9_zif.zip:
MD5: B0AD9E7BB4468139F954F703DC7BBC13
SHA1: 27723CDE1032C8D033C807809D0E0C29F5576BD3
---------- Post added at 10:23 AM ---------- Previous post was at 09:39 AM ----------
-----
bleh the answer to the below question is that it has 44686592 bytes of null padding...
tail -c 44686592 modem.bin | od
0000000 000000 000000 000000 000000 000000 000000 000000 000000
*
252356400
---
I'm trying to figure out why the modem.bin file in your package is twice as large as the modem file provided in this thread by immuts. If i understand correctl your modem.bin came from sv's package. These are fat32 images that can be mounted on any linux system and they contain the exact same content if mounted:
-
modem.bin: x86 boot sector; partition 1: ID=0x6, active, starthead 0, startsector 0, 409600 sectors, code offset 0x3c, OEM-ID "MTOO4013", sectors/cluster 8, root entries 512, sectors/FAT 200, heads 5, sectors 409600 (volumes > 32 MB) , serial number 0x29b2acbf, unlabeled, FAT (16 bit)
-
vruemj9_radio.img: x86 boot sector; partition 1: ID=0x6, active, starthead 0, startsector 0, 409600 sectors, code offset 0x3c, OEM-ID "MTOO4013", sectors/cluster 8, root entries 512, sectors/FAT 200, heads 5, sectors 409600 (volumes > 32 MB) , serial number 0x29b2acbf, unlabeled, FAT (16 bit)
-
Under linux you would mount one of these files with "mount -o loop modem.bin [some directory]
-
Anyway do you know why the files differ in size ?
-
47588096 vruemj9_radio.img
vs
92274688 modem.bin
Poor wording.Flashed fine and seems to be a bit of an improvement. Haven't used it long enough to comment on battery life but reception seems better in low signal areas.