Just wondering if anyone has extracted a radio img from a sbf?
I'm trying to get all the radios i can find and make CWM installers for them. so far i can only get them from OTA updates. Is this the only way?
Ive tried moto-depacker but cannot figure out how to combine the mbn headers into an image....
I would like to get away from using the computer for flashing anything
Search for a thread called "fruit cakes" in android development. It has flashable CWM files for radios.
Sent from my MB860 using XDA App
If you are in linux you need to get sbf_flash from mdm, than get the sbf files you want to extract the radios from and do "sbf_flash -x yourfile.sbf" all the images will be extracted as *. img than just get the img number where radio is stored and thats it. Taking them from fruitcakes as already suggested would be quicker though.
neer2005 said:
Search for a thread called "fruit cakes" in android development. It has flashable CWM files for radios.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Sigh..... So where is the 1.97R fruitcake??? I only see 2 radios in that thread.
I want to extract all radios I can find and make CWM installers so I can test out different radios in different areas without having to use a computer to flash.
Sent from my MB860 using XDA Premium App
SolidHelix said:
Just wondering if anyone has extracted a radio img from a sbf?
[...]
I would like to get away from using the computer for flashing anything
Click to expand...
Click to collapse
Ditto on dumping the PC... though you will need to use this on a PC to extract the radio.img files:
http://www.e2mod.com/content/view/93/27/
http://www.motorolafans.com/forums/e6-firmware/22882-how-to-create-your-own-monsterpack.html
Props to NFHimself for mentioning this method in his Telstra radio thread here (post #4):
http://forum.xda-developers.com/showthread.php?t=1049434
There are a few posts here of .zip format radio images... not sure if they include only CG5 or also RDL1 and RDL3. Don't know how inspect a radio.img to determine this. Any ideas?
More info here on CG5, RDL1 and RDL3:
http://forum.xda-developers.com/showthread.php?t=1059643
http://forum.xda-developers.com/showthread.php?t=1059643
NFHimself said:
Single Binary Format
[...]
Desbf, I don't know the history behind this or what it has been used for in the past, it was on a list of google hits for the obscure motorola sbf format. You run it, select a sbf file, and it automatically creates a folder with all the files contained in the sbf extracted. You can delete files and then save an sbf that can be flashed. It has a parse CG button, don't know what it's for. It has been used to flash the Telstra radio onto Att and Bell. I have yet to use it to flash something using RDL3, just the radio using RDL1.
[...]
Speaking of files, here is what I understand about them:
The utilities spit out SMG files, it's a motorola format, not sure of the acronym.
RDL1:
RDL3:
Ram downloader 1 is used for the radio, it is flashed after everything else, changing mode to do so, everything else is flashed using Ram downloader 3. I don't know what happened to RDL2.
[...]
CG5 is the radio, plus other things apparently. In [De]Packer it's a virtual collection of mbn files, partition.mbn, amas_sec.mbn (the radio), osb1_sec.mbn, cefs.mbn, db1_sec.mbn. I have no idea what they are about. I know they are from CG5 because an sbf with just RDL1, RDL3, and CG5 spits out RDL1, RDL3, and the above without a CG5.
Click to expand...
Click to collapse
Well now I feel stupid...
Upon much closer inspection it seems that desbf.exe can't actually be used to create .img files. It appears that I mis-read NFHimself's thread...
I too have banged my head against this for a couple of nights and come to the same conclusion. The few radio.img/bp.img files out there apparently came from either AT&T or Orange FR OTA updates.
So we know Motorola knows how to do this... but HOW???
http://forum.xda-developers.com/showthread.php?t=1049434&page=14
acer73 said:
it's possible to have a CW file of this radio?
Click to expand...
Click to collapse
NFHimself said:
Only if it is available as an OTA file, the sbf radio format contents would have to be translated into a different format for a CWM zip.
Cheers!
Click to expand...
Click to collapse
Another possible line of attack:
http://and-developers.com/partitions:cdt
Extracting partitions
Method, which use right ecc correction
You need kernel module and mtd-utils. Here you can download precompiled mtd-utils and kernel module, with sources. mtd-utils.tar.bz2
Code:
insmod mtd_dumpall.ko
echo "0 64" > /proc/mtd_dumpall
cat /proc/mtd_dumpall > /tmp/mtd0.bin
The result is in ASCII format where ^d[^:]+ denotes data lines and ^o[^:]+ denotes OOB data. Each data line have 0x20 ASCII hex.
To transform them to binary:
Code:
grep ^d | xxd -r -c 0x20 > out.bin
or just try use nanddump directly
janneg_'s kernel module
After booting into Linux, some of these partitions are available through MTD devices (/dev/mtd*). But other partitions are not available because the Linux kernel provided by Motorola does not map them into MTD devices. janneg_ has created a kernel module that maps them all, thus enabling us to extract anything from the Milestone's Flash. You can try a precompiled binary here if you don't want to compile it yourself.
Click to expand...
Click to collapse
Some of the download links on this page are stale, notably the precompiled binary for janneg_'s kernel module...
NFHimself provides a partial Code Group to partition name map here:
http://forum.xda-developers.com/showpost.php?p=13386993&postcount=1
zambezy does the same here:
http://forum.xda-developers.com/showpost.php?p=12687720&postcount=502
But what is the partition name for CG5?
*bump*..anyone still working on creating the CWM zip for 1.97 radio? If someone can tell the process I am willing to create it.
Any Update on that? I would like to get the baseband from the German 2.3.4 sbf.
Related
I have searched for but found nothing for our leaked bretheren (me included) that would allow us to downgrade. Would the downgrade method of days gone by be applicable as well? If so can someone provide details please?
I am specifically looking to do so that I may have a non leak phone.
Namaste and Thanks!
PS- go see Scott Pilgrim, IT RUCKIN FAWKS XD
Sent from my FroyoEris using XDA App
nomorefear said:
I have searched for but found nothing for our leaked bretheren (me included) that would allow us to downgrade. Would the downgrade method of days gone by be applicable as well? If so can someone provide details please?
I am specifically looking to do so that I may have a non leak phone.
Namaste and Thanks!
PS- go see Scott Pilgrim, IT RUCKIN FAWKS XD
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Install the Leak-V3 PB00IMG.ZIP rom via HBOOT, or run the "Official" 2.1 RUU utility. They produce an essentially identical result.
The July 17 OTA will pop up sometime after the first boot when you do the above - possibly before you have even finished reconfiguring the phone.
bftb0
I don't want hboot 1.49 however.
nomorefear said:
I don't want hboot 1.49 however.
Click to expand...
Click to collapse
Fine. Then just unzip the Leak-V3 PB00IMG.ZIP file to a folder on your SD card and manually install each of the images contained therein using Amon_RA and the (adb shell) command line.
Just be aware that
1) "recovery.img" and "boot.img" are bootable Android images, so they are installed into their respective partitions (with the Amon_RA recovery booted) using the "flash_image" program.
2) "system.img" and "userdata.img" are yaffs2 (filesystem images); these are installed into the partitions /system and /data (respectively) in a four-step process:
- mount the partition
- do a (dangerous) rm -rf * command INSIDE THAT MOUNTED PARTITION to delete all the files
- perform an unyaffs command within that mount point using the respective image file
- unmount the partition.
Note that the the steps that I have just described are EXACTLY the same thing that a Nand Restore does. You could either read the shell script nandroid-mobile.sh (do an "adb pull /sbin/nandroid-mobile.sh nandroid-mobile.sh") to see the exact set of commands that are used...
OR, if you want, you could hand-create a fake Nandroid backup set from the
boot.img
system.img
userdata.img (renamed to data.img)
files, and do a Nandroid restore of them. Then, as a final step (still inside Amon_RA) do a
# flash_image recovery /sdcard/the-pb00img-that-i-unpacked/recovery.img
Note that my instructions are a little bit vague; that was done on purpose, because you need to understand what you are doing before you attempt it. If you do enough research to decipher and completely understand the jibberish above, it will be safe to perform.
bftb0
nomorefear said:
I don't want hboot 1.49 however.
Click to expand...
Click to collapse
Actually, I just re-read your first post that intimates that you were a leaker.
That means that you must have had the 1.49.0000 S-ON bootloader on your phone already - the same one that is in the PB00IMG.ZIP file of the Leak-V3.
Did you replace it somehow after you rooted? If not, the objection is removed.
bftb0
Before I finally rooted, I used the verizon ota RUU I think. Then I rooted. My understanding is my firmware is a bit shoddy due to being a leaker, even with the RUU.... Maybe I'm being a noob about it. I do understand the instructions and I'm very much capable of most things explained in this forum. Thanks again b
Sent from my FroyoEris using XDA App
The only thing I think might work is the jcase flash any ruu/ota/hboot thingy I found earlier today. Does it?
Sent from my FroyoEris using XDA App
So far I have tested redbend_ua for backup purposes, and got the bml7 and bml8 partitions backed up, and tested just restoring the bml8 partition with the clockwork recovery that is being tested on the epic. The utility did write the image / partition correctly (afaik) and rebooted the phone upon completion. The phone booted correctly to android, but then upon another reboot to test recovery, it just boot loops, even a normal boot and trying to get to the downloader mode.
This utility seems to work and do what it was meant to, but i would not use this tool without knowledge of what you are doing. On that note, i will not post a link to the tool, just as a safeguard, for now at least.
it is known to work on bml7 (the kernel partition).
for the last few fays ive been trying to gather information regarding flashing an entire rom (all the partitions resides in an odin update file) using redbend_ua only, but i couldn't get a clear understanding of what todo with the two cache.rfs & dbdata.rfs files (each located on both the PDA and the CSC files). also, repartitioning the disk is also needed when flashing a new rom, so i need to recognize the new partition table layout (which i assume resides in the .pit file).
as for now, its only a lot of assumptions for me. they only confirmation i could get was from here: hxxp://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S
z4ziggy said:
it is known to work on bml7 (the kernel partition).
for the last few fays ive been trying to gather information regarding flashing an entire rom (all the partitions resides in an odin update file) using redbend_ua only, but i couldn't get a clear understanding of what todo with the two cache.rfs & dbdata.rfs files (each located on both the PDA and the CSC files). also, repartitioning the disk is also needed when flashing a new rom, so i need to recognize the new partition table layout (which i assume resides in the .pit file).
as for now, its only a lot of assumptions for me. they only confirmation i could get was from here: hxxp://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S
Click to expand...
Click to collapse
Both cache and dbdata can largely be ignored; I actually had to nuke my /dbdata partition earlier due to something I did. It gets rebuilt on boot, it's just a SQLite store for the applications and on most Android phones resides within /data. No idea why Samsung felt it necessary to separate this partition.
if this is so, and both cache.rfs & dbdata.rfs can be ignored, then updating an entire rom using redbend_ua from within update.zip is possible (right now the project-voodoo is using the redbend_ua method to flash kernel only from within update.zip file, but the idea is the same).
i think we need to get some more confirmation before actually testing this because failure on flashing the rom will break the phone... and no one wants to have that
z4ziggy said:
if this is so, and both cache.rfs & dbdata.rfs can be ignored, then updating an entire rom using redbend_ua from within update.zip is possible (right now the project-voodoo is using the redbend_ua method to flash kernel only from within update.zip file, but the idea is the same).
i think we need to get some more confirmation before actually testing this because failure on flashing the rom will break the phone... and no one wants to have that
Click to expand...
Click to collapse
I did some more testing and can confirm that cache and dbdata can both be empty on boot.
this is excellent news!
i will work later today on a template for update.zip using redbend_ua and post here for reference.
also, a thought came to mind - what is the difference between redbend_ua and dd? if all redbend_ua does is dumping data from/to a partition, then it is simply a dd replacement. isn't it?
z4ziggy said:
this is excellent news!
i will work later today on a template for update.zip using redbend_ua and post here for reference.
also, a thought came to mind - what is the difference between redbend_ua and dd? if all redbend_ua does is dumping data from/to a partition, then it is simply a dd replacement. isn't it?
Click to expand...
Click to collapse
If you currently have redbend_ua on your device, could i get you to dump /dev/block/BML7 to /sdcard/recovery.bin and upload it / link it? i need it
fallingup said:
If you currently have redbend_ua on your device, could i get you to dump /dev/block/BML7 to /sdcard/recovery.bin and upload it / link it? i need it
Click to expand...
Click to collapse
Yeah.. I could've used that yesterday too.. I ended up swapping out my device this morning.
Sounds like some progress is being made. Very good to hear confirmation on cache and dbdata
i actually got it working now, after my brick anyways. Now i need to find the verizon dump not a USC dump
fallingup said:
i actually got it working now, after my brick anyways. Now i need to find the verizon dump not a USC dump
Click to expand...
Click to collapse
Glad to hear it.. I was getting seg-faults trying to mount /system .
Someone who has done the whole DI01 update, please dump their system for me, or just the framework folder, apparently the one given to me had the stock android lockscreen patch applied to it lol.
Aside from that, the DI01 deodex works perfect, I opt_png'ed and zip_align'ed all the apk's, as well as the framework-res and twframework-res.
I will also need someone who knows how to sign updater-scripts to open the one attached, and just save it again properly and upload it for me. I am trying to get a flashable CW zip but the darn thing always gives me a status 6 error, which means the CW cannot read the updater script.
Sorry for the n00b question, but what benifit does deodexing provide? Also if there is another software update will I have to readd any .apk's to my /system folder?
Why not just flash your own system back to stock, then run the update, then dump /system? If you'd like an update script that doesn't update modem.bin, I already have one.
Assuming you're updating via CWM, why are you signing the zip? You don't need any signature, just zip the file up.
Is there anything involved in a dump besides just copying the files in /system?
namebrandon said:
Why not just flash your own system back to stock, then run the update, then dump /system? If you'd like an update script that doesn't update modem.bin, I already have one.
Assuming you're updating via CWM, why are you signing the zip? You don't need any signature, just zip the file up.
Click to expand...
Click to collapse
Because I am too lazy to go through all that.
I don't need it signed per say. More like opened, edited, and saved properly. It is said it is best to edit the update script in s Linux based environment which I don't have, but that notepad should suffice, yet when I save it with my notepad, I get the error of cw not being able to read it properly.
I have a fresh phone that just got the D101 update. Just need directions on what if anything is involved beyond just getting the /system directory via adb.
s44 said:
I have a fresh phone that just got the D101 update. Just need directions on what if anything is involved beyond just getting the /system directory via adb.
Click to expand...
Click to collapse
That is all I need. The only things I deodex are the contents of system/app and system/framework.
frostman89 said:
I don't need it signed per say. More like opened, edited, and saved properly. It is said it is best to edit the update script in s Linux based environment which I don't have, but that notepad should suffice, yet when I save it with my notepad, I get the error of cw not being able to read it properly.
Click to expand...
Click to collapse
Try a real editor, like bluefish or something.. Those scripts look like sh#! in notepad.
If no one has done it by tonight, just grab me on IRC and I'll do it under Linux for you.
Make sure you've got the file/directory structure right too.. You can't just throw a script in a zip file, but I'm sure you knew that. Myself and and a few others had the wrong directory structure at first, don't remember what error number that gave us though.. I think it just froze.
OK, how can I get it to you? I can't post links or (I think) files yet.
s44 said:
OK, how can I get it to you? I can't post links or (I think) files yet.
Click to expand...
Click to collapse
You can just zip it up and upload it to mediafire.com
Just splice up the link like WWW. Website. Com and I will just delete the spaces.
Mediafire upload just not working for some reason. Hm.
s44 said:
Mediafire upload just not working for some reason. Hm.
Click to expand...
Click to collapse
http://multiupload.com/
J1HDKEGYAR at multiupload
Hey guys.. Odin3 version3 and higher has gz support. I've been working with this for a bit and tonight I found that Odin will accept tar.md5.gz files. This is important for GNote2 users as the stock ROM is 1.2Gigs! You can get an extra 10-40% compression and 100% gaurantee that the files arrive to your users computer in the condition that you packaged them using this method. I have not found a guide on using the gz format so I thought I would write one up.
You will need:
A Linux computer
Your rom (we will call it MyROM)
How to package for Odin on Windows
I will cover packing into a single file, adding an MD5, and compressing the file down. For the purposes of this, we are working with "MyROM". You will want to call your ROM whatever you like. Just make sure to add version information to the file name so users don't get confused. Also note, the name MUST be consistent throughout the process. If you change the name, Odin can fail.
Another good tip is to put a model number in the name so there is no confusion as to what device your Odin package goes to. Several users, myself included, have 20+ Odin packages on their computer.
So first you want to turn the ROM into a single tar file and then make sure changes are written to the disk.
Code:
tar -H ustar -c boot.img hidden.img modem.bin param.bin recovery.img system.img tz.img sboot.bin>./MyROM.tar;sync;
Next we want to add an MD5 to the file so Odin can check its consistancy.
Code:
md5sum MyROM.tar >> MyROM.tar;
Now we will change it into a tar.md5 file so Odin knows it has an MD5 attached to it.
Code:
mv MyROM.tar MyROM.tar.md5; sync;
Finally we will compress it with GZip. GZip is the only compression method supported by Odin.
Code:
gzip MyROM.tar.md5 -c -v > MyROM.tar.md5.gz;
You will now have a file called MyROM.tar.md5.gz.
Conclusion
The first time the file is flashed, Odin will uncompress it into MyROM.tar.md5, then check its consistancy, then flash the file. Using this method you will be transferring the smallest file possible and adding integrity checks.
notes
Note to Verizon GNote2 users: Stay away from using Odin after IROM unlock as flashing a package intended for another device will perma-lock your device into another carrier's bootloaders. Especially stay away from GS3 as the displays are not compatible.
good ****! this is def useful
Awesome news! Any test results with the older versions? If not one click solutions may not benefit.. but servers and users will by cutting the downloads even more!
Sent from my SPH-L900 using Tapatalk 2
Windows OS
How can I do it on a Windows computer?
MAQ7 said:
How can I do it on a Windows computer?
Click to expand...
Click to collapse
Install Virtual Box and a Linux distribution. I haven't seen any tools for Windows that work properly to make tar archives that work with Odin.
cygwin.
Mine all work
imnuts said:
Install Virtual Box and a Linux distribution. I haven't seen any tools for Windows that work properly to make tar archives that work with Odin.
Click to expand...
Click to collapse
adrynalyne said:
cygwin.
Mine all work
Click to expand...
Click to collapse
I managed to make tar on Windows using cygwin :good:.
Thank you
Interesting adam, I always compressed the whole odin package into a rar file (same effect but one step extra). Also I made an article about odin a while ago:
http://broodplank.net/?p=496
Btw, did you know that you can put cwm backups (ext4.tar) inside an odin package? It's the first odin image I ever saw, filled with a CWM backup, and yes it works XD
But it's not an 1:1 copy of course, Also I wonder how nandroid backups actually store their permissions, I mean dd is a 1:1 dump, which is logical, cwm has the updater-script. but the nandroid backups which are actually just tar files packed with the contents, how do they store it?
Last thing, Odin packages can be a last resort fix, believe me, many users reported that flashing my rom broodROM_RC5.tar.md5 (which contains about 13 files, you can imagine how many partitions it includes) fixed their phone when nothing else worked.
So thank you Samsung for leaking your tool, A world with Samsung Kies only would be a very sad "softbricky" world
broodplank1337 said:
But it's not an 1:1 copy of course, Also I wonder how nandroid backups actually store their permissions, I mean dd is a 1:1 dump, which is logical, cwm has the updater-script. but the nandroid backups which are actually just tar files packed with the contents, how do they store it?
Click to expand...
Click to collapse
TAR files preserve file permissions.
I still like making a 7z out of the final .tar.md5 file.
The info in OP is great to know as it does save a step for the end user but I'd rather them take a couple steps to vet out the incompetent ones. Could prevent a brick
mrRobinson said:
I still like making a 7z out of the final .tar.md5 file.
The info in OP is great to know as it does save a step for the end user but I'd rather them take a couple steps to vet out the incompetent ones. Could prevent a brick
Click to expand...
Click to collapse
Only on the Verizon Galaxy Note. All others are IROM locked. The IROM lock prevents flashing of an improper SBOOT. An unlocked VZWGNote 2 can flash any SBOOT.
Other than this specific case, adding third party tools other than ZIP compression means your user must download special tools.
Extra files?
If I were to pack an extra README.txt file into the tar before prepping it for Odin, would Odin then ignore it during the flash? Obviously there's no entry for what to do with an extraneous text file in the pit, so hopefully Odin would just disregard it.
I happened to find out today that heimdall has support for "Heimdall Firmware Packages." You can read and write them from the heimdall frontend (the 1.3 FE binary is forward compatible with my source built 1.4 heimdall). What's interesting, is that the format is almost identical to odin's format. It is still packaged in a tar file, and it contains the same system.img, boot.bin, recovery.bin etc. files you'd find in the Odin tar. By default it's format is Package.tar.gz. The only significant difference is the addition of a firmware.xml file that identifies the proper partition for each image file, as well as the target platform, the author, and other details like that.
So I got curious. I took a Package.tar.gz file generated by heimdall, and repackaged it as a Package.tar.MD5.gz file. Heimdall has no problem reading this! So the upshot is, Odin now handles the .gz, so as long as Odin isn't bothered by an extra firmware.xml file inside the tar, the same format would be compatible with either tool.
PS> Don't flame me about flash counters or bricked phones. I do understand that Odin/Heimdall are only particularly relevant for returning a phone to stock, but that's still a very important functionality and it would be great to have a unified format.
goo.im/devs/h0tw1r3/GT-N7005/GT-N7005-IMM76D-DXLJ2-Baseband
This is probably the closest I've found, but as far as I know, flashable modem zipz are supposed to have 2 more files, mainly:
1. META-INF/com/google/android/update-binary
2. META-INF/com/google/android/update-script
I know next to nothing about these files and their uses. I've also taken a look at the update-script file, my guess is that it's whatever's shown in recovery display when you flash it.
Where can I find a flashable DXLJ2 modem for the Note N7005/SGH-i717?
I've tried other modems such as UCMD3, UCLF6, etc., they drop connections often in where I live, the only one which worked out okay for me was DXLJ1, so I decided to try and get the DXLJ2 modem to test it out, but can't find it.
I'm planning on using this in the Padawan JB rom as the default modem that came with that custom ROM did not work for me.
I've also noticed that there are some ROMs which make use of the DXLJ2 modem, but I know nothing about development or how modems are incorporated into ROMs.
tl;dr - I'd like a flashable DXLJ2 modem zip if possible, thanks!
Did you try Google? Probably not because I found a few links to other sites in seconds.
440bro said:
Did you try Google? Probably not because I found a few links to other sites in seconds.
Click to expand...
Click to collapse
I have, I'm guessing I must be using wrong keywords since I tried "DXLJ2 Modem Baseband download xda android" numerous times on Google and have only managed to find ROMs which use that baseband, but not as a flashable ZIP by itself.
I always Google before asking questions, and only ask when I have trouble finding something.
Probably seems dumb since some people can find it easier than me, but like I said, I've tried and failed, which is why I'm asking here.
why not just download the stock n7005 .tar and extract the modem.bin and flash with odin. sometimes less is more(keywords). n7005 dxlj2 and extract modem.bin. you will find what you need on first page of each of these searches.
s89281b said:
why not just download the stock n7005 .tar and extract the modem.bin and flash with odin. sometimes less is more(keywords). n7005 dxlj2 and extract modem.bin. you will find what you need on first page of each of these searches.
Click to expand...
Click to collapse
Hey thanks for the reply, much appreciated!
Just to confirm though, is modem.bin supposed to be in the root directory of the tar? I don't see such a file, only:
-amss.bin
-mdm.bin
(These 2 files also appeared in the link in the first post.)
along with the boot image (boot.img), recovery image (recovery.img) and 2 EXT4 filesystem partitions/files (cache.img.ext4 & system.img.ext4)
here is link to a flashable zip of ucmd3 modem. http://storagecow.eu/index.php?dir=Xda/AT&T+Note+1/Stock+Jelly+Bean/ replace the files in tmp folder with both files you got from tar and you should have a recovery flashable dxlj2 zip.
s89281b said:
here is link to a flashable zip of ucmd3 modem. storagecow.eu/index.php?dir=Xda%2FAT%26T+Note+1%2FStock+Jelly+Bean%2F replace the files in tmp folder with both files you got from tar and you should have a recovery flashable dxlj2 zip.
Click to expand...
Click to collapse
Thanks, I'll do that when I can! (My phone isn't with me right now)
I'd just like to know if the same META-INF folder can be used for other other modems as well, for the same device (N7005/I717) and for totally different devices as well (N7000, GS3, etc.)
What does the update-binary (in META-INF) actually do?
Also why is there no modem.bin, just mdm.bin?
I apologise for the questions, I'd just like to learn more if possible. I can probably get it to work already but I'd like to know a bit more and save myself some trouble in the future.