[ODIN][Radio] I545VRUAME7

Search This thread

arcanexvi

Senior Member
Aug 22, 2010
1,435
464
Hoffman Estates, IL
Usual warnings: I'm not responsible for what you do to your phone blah blah blah

I yanked the radio out and flashed it via ODIN from the update that's been floating around for those that want to play with it. Flashed it on mine and doesn't seem to have caused any issues (at least on CM). After a day's worth of testing I am noticing that I do get better reception in areas that are trouble areas for me normally.

Note: CM didn't like the new DSP in the NON-HLOS.bin and gave me no audio. I reverted back to just using the new modem.bin file for now and the revert file here can be used if needed. This will restore you to the old HLOS and modem. Just flash the modem.bin below by itself without the HLOS file if you just want the radio updates.I have removed the HLOS file and instructions for the time being until developers update ROMs to be compatible. Using the updated modem is fine by itself.

- Download File

- Flash modem.bin in ODIN under PHONE and wait for PASS! (ODIN did seem to hang for a moment while the phone processed. Don't panic)

- Reboot (if you didn't have it set to do so in ODIN)

- Profit?

Post your results/findings to help other users :)

Note: If your phone has rebooted and hasn't cleared "reset" into "pass" in ODIN it's not the end of the world. As long as it was successful flashing (lower left corner of ODIN) and is currently booted into android after reboot, you're fine.

Updated Radio: http://www.mediafire.com/?jm2d34gb88jx32m
Revert File: http://www.mediafire.com/?242ruwpbqtcssd0

MD5 of updated Radio: 168FB171A19362678B73409C90F0DD61
MD5 of Revert package: 7232DCCB4C00A940B24B8FB1163D7FF0
 
Last edited:

Tada10

Senior Member
Feb 19, 2013
486
182
Can you try the apps2sd or hdr video? :)

Sent from my Samsung Galaxy S4
 

arcanexvi

Senior Member
Aug 22, 2010
1,435
464
Hoffman Estates, IL
That would require coding rather than just pulling files. As I haven't coded since the Thunderbolt era... I'll leave that to the guys that know what they're doing. Cameras in particular are always a pain in the ass.
 

scottusa2008

Senior Member
Nov 30, 2008
550
168
I am willing to give this a shot since you mentioned it helped with your signal in your apt. In my case my location is kinda problematic because of how close it is to Verizon's home network, but I am physically located within the extended network. So in my apartment my signal fluctuates quite a bit, and more so depending on which room I am in (my living room must be close enough to get the home network, but my bedroom is just outside of it's reach).


**Just got done and here's the results - I was able to flash the modem.bin you posted on my stock rooted phone and right off the bat things seem to be better signal wise. After rebooting the phone there were no issues that I can see or find, everything seems to be functioning correctly. Phone calls seem to sound a little better (I have no idea if it's a fluke because of the hour or the new radio), and data hasn't been impacted at all.

I also noticed a small improvement in the signal strength readings, but I will keep monitoring it to make sure it's not a random fluke.
 
Last edited:

vacaloca

Senior Member
Jun 11, 2010
263
115
According to this thread over on the GSM side, one should be able to flash NON-HLOS.bin the same way:
http://xdaforums.com/showthread.php?t=2192025

As I understand, this is also a modem file -- the counterpart to modem.bin, but I am unclear as exactly what functionality is embedded in this image.

Edit 1: Looking at the text strings in the NON-NLOS.bin file, there are a lot of references to voice filters, gain, pitch, speech, agc, etc, and even "European digital cellular telecommunications system 4750 ... 12200 bits/s speech codec for Adaptive Multi-Rate speech traffic channels". Seems like this file is mostly vocoder-related stuff.

Edit 2: Google led to this: http://www.anyclub.org/2012/06/acdb-audio-calibration-database-images.html
It mentions that if "If any of MPSS, DSPS, WCNSS, or LPASS is recompiled" NON-HLOS.bin should be "updated". DSP - digital signal processor, WCNSS = "Wireless ConNectivity SubSystem (WCNSS) driver. The WCNSS is a new Hardware integrating WLAN, BT and FM technologies that is built into new MSM chip." I can't definitions for MPSS and LPASS, but MPSS is mentioned in some Qualcomm job listings relating to Modem Test Technicians/Engineers, so it seems logical that these two files should go together, but given some have had hard bricks when flashing other parts of the firmware, I'd be cautious.
 
Last edited:

theresin

Senior Member
Dec 8, 2012
279
159
Tempe, Arizona
Usual warnings: I'm not responsible for what you do to your phone blah blah blah

I yanked the radio out and flashed it via ODIN from the update that's been floating around for those that want to play with it. Flashed it on mine and doesn't seem to have caused any issues (at least on CM). Don't ask if it's better or not. I literally just tested to see if it would work and not brick and that's the extent of what I've done so far other than sending a text and making a phone call to make sure everything's good.

Download File
Flash modem.bin in in ODIN under PHONE and wait for PASS! (ODIN did seem to hang for a moment while the phone processed. Don't panic)
Reboot (if you didn't have it set to do so in ODIN)
Profit?

My mega account is free so I'm not sure how much bandwidth they'll give me but here you go til it blows up :p

Post your results/findings to help other users :)

https://mega.co.nz/#!ikAlTJDI!A6sRNRLh0cXBnpIsc8ra9konK4pMxcZcgWITJw5lQIU


Just flashed it, will give results in the morning (or afternoon, depending on where you're at).


You weren't kidding about Odin pausing up for a bit .. the phone had reset and was already running for about a minute before Odin changed to "PASS" ... so hopefully everyone is patient!
 

chewwy420

Senior Member
Nov 28, 2007
132
27
With the Amish
According to this thread over on the GSM side, one should be able to flash NON-HLOS.bin the same way:
http://xdaforums.com/showthread.php?t=2192025

As I understand, this is also a modem file -- the counterpart to modem.bin, but I am unclear as exactly what functionality is embedded in this image.

Edit 1: Looking at the text strings in the NON-NLOS.bin file, there are a lot of references to voice filters, gain, pitch, speech, agc, etc, and even "European digital cellular telecommunications system 4750 ... 12200 bits/s speech codec for Adaptive Multi-Rate speech traffic channels". Seems like this file is mostly vocoder-related stuff.

Edit 2: Google led to this: http://www.anyclub.org/2012/06/acdb-audio-calibration-database-images.html
It mentions that if "If any of MPSS, DSPS, WCNSS, or LPASS is recompiled" NON-HLOS.bin should be "updated". DSP - digital signal processor, WCNSS = "Wireless ConNectivity SubSystem (WCNSS) driver. The WCNSS is a new Hardware integrating WLAN, BT and FM technologies that is built into new MSM chip." I can't definitions for MPSS and LPASS, but MPSS is mentioned in some Qualcomm job listings relating to Modem Test Technicians/Engineers, so it seems logical that these two files should go together, but given some have had hard bricks when flashing other parts of the firmware, I'd be cautious.

I flashed the Modem.bin and NON-HLOS.bin and all seems to be good so far...
 
  • Like
Reactions: vacaloca

vacaloca

Senior Member
Jun 11, 2010
263
115
OP (or someone else) should create/upload an Odin flashable .tar.md5 of both modem.bin and non-HLOS.bin (after testing). Here is info/instructions:
http://www.sxtpdevelopers.com/showthread.php?t=155

I'm not sure which file should go first in the .tar.md5 file, as order apparently matters.
http://xdaforums.com/showthread.php?t=2278152 seems to imply NON-HLOS.bin should go first.

Edit 1: Yes, non-HLOS.bin goes first. See PIT directly from my SCH-I545 while still on MDK captured by Heimdall:
Code:
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
      Manufacturer: "Sasmsung"
           Product: "MSM8960"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 0100
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 82
           max packet size: 0010
          polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 01
           max packet size: 0200
          polling interval: 00
Claiming interface...
Setting up interface...

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Entry Count: 33
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21325
Unknown 4: 14413
Unknown 5: 13881
Unknown 6: 48
Unknown 7: 0
Unknown 8: 0


--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 25544
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: APNHLOS
Flash Filename: NON-HLOS.bin
FOTA Filename: 


--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 33736
Partition Block Count: 105528
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MDM
Flash Filename: modem.bin
FOTA Filename: 


--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 139264
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL1
Flash Filename: sbl1.mbn
FOTA Filename: 


--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 139520
Partition Block Count: 512
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename: sbl2.mbn
FOTA Filename: 


--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 140032
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL3
Flash Filename: sbl3.mbn
FOTA Filename: 


--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 141056
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ABOOT
Flash Filename: aboot.mbn
FOTA Filename: 


--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 145152
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RPM
Flash Filename: rpm.mbn
FOTA Filename: 


--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 146176
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZ
Flash Filename: tz.mbn
FOTA Filename: 


--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 147200
Partition Block Count: 33792
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PAD
Flash Filename: 
FOTA Filename: 


--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 180992
Partition Block Count: 27904
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img.ext4
FOTA Filename: 


--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 208896
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST1
Flash Filename: nvrebuild1.bin
FOTA Filename: 


--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 215040
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST2
Flash Filename: nvrebuild2.bin
FOTA Filename: 


--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 221184
Partition Block Count: 1560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: M9KEFS1
Flash Filename: m9kefs1.bin
FOTA Filename: 


--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 222744
Partition Block Count: 1560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: M9KEFS2
Flash Filename: m9kefs2.bin
FOTA Filename: 


--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 224304
Partition Block Count: 1560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: M9KEFS3
Flash Filename: m9kefs3.bin
FOTA Filename: 


--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 225864
Partition Block Count: 5652480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img.ext4
FOTA Filename: 


--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5878344
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSIST
Flash Filename: 
FOTA Filename: 


--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5894728
Partition Block Count: 4239360
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img.ext4
FOTA Filename: 


--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10134088
Partition Block Count: 12288
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename: 


--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10146376
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename: 


--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10166856
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename: 


--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 22
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10187336
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FOTA
Flash Filename: 
FOTA Filename: 


--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 23
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10207816
Partition Block Count: 12288
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BACKUP
Flash Filename: 
FOTA Filename: 


--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 24
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10220104
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FSG
Flash Filename: 
FOTA Filename: 


--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 25
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10226248
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SSD
Flash Filename: 
FOTA Filename: 


--- Entry #25 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 26
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 10226264
Partition Block Count: 18432
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSDATA
Flash Filename: persdata.img.ext4
FOTA Filename: 


--- Entry #26 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 27
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 10244696
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img.ext4
FOTA Filename: 


--- Entry #27 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 28
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 10285656
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CARRIER
Flash Filename: carrier.img.ext4
FOTA Filename: 


--- Entry #28 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 29
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 10326616
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img.ext4
FOTA Filename: remained


--- Entry #29 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 34
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PGPT
Flash Filename: pgpt.img
FOTA Filename: 


--- Entry #30 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: MSM8960.pit
FOTA Filename: 


--- Entry #31 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 72
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5
Flash Filename: md5.img
FOTA Filename: 


--- Entry #32 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 73
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 30777311
Partition Block Count: 33
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SGPT
Flash Filename: sgpt.img
FOTA Filename: 

Ending session...
Releasing device interface...
 
Last edited:
  • Like
Reactions: BShadynew

arcanexvi

Senior Member
Aug 22, 2010
1,435
464
Hoffman Estates, IL
OP (or someone else) should create/upload an Odin flashable .tar.md5 of both modem.bin and non-HLOS.bin (after testing). Here is info/instructions:
http://www.sxtpdevelopers.com/showthread.php?t=155

I'm not sure which file should go first in the .tar.md5 file, as order apparently matters.
http://xdaforums.com/showthread.php?t=2278152 seems to imply NON-HLOS.bin should go first.

I don't have a linux box and wiped recently so i don't have a linux box set up to create a single file to flash. If someone wants to do it and beats me to it I'll gladly link it in the op. Until then i've re-uploaded elsewhere for bandwidth.

OP Updated.
 
Last edited:

paulg1981

Senior Member
Jan 16, 2006
788
282
Fort Worth
Can someone link the files to revert back to MDK modem and hlos, just in case?

EDIT: Found it

http://www.rwilco12.com/Files/Devic.../Modems/TAR/SCH-I545_MDK_562219_Modem.tar.md5

---------- Post added at 10:55 AM ---------- Previous post was at 10:38 AM ----------

Just a heads up for everyone, after I flashed the updated modem/non-hlos files my back speaker and wifi wouldn't work. I flashed back to the mdk versions of those files and everything working like a charm again...
 
Last edited:
  • Like
Reactions: mutelight

arcanexvi

Senior Member
Aug 22, 2010
1,435
464
Hoffman Estates, IL
CM didn't like the new DSP in the NON-HLOS.bin and gave me no audio. I reverted back to just using the modem.bin file for now but I'm leaving the instructions as they are because I haven't seen anyone else post the issue. I put this note in the OP as well.
 
  • Like
Reactions: vacaloca

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    Usual warnings: I'm not responsible for what you do to your phone blah blah blah

    I yanked the radio out and flashed it via ODIN from the update that's been floating around for those that want to play with it. Flashed it on mine and doesn't seem to have caused any issues (at least on CM). After a day's worth of testing I am noticing that I do get better reception in areas that are trouble areas for me normally.

    Note: CM didn't like the new DSP in the NON-HLOS.bin and gave me no audio. I reverted back to just using the new modem.bin file for now and the revert file here can be used if needed. This will restore you to the old HLOS and modem. Just flash the modem.bin below by itself without the HLOS file if you just want the radio updates.I have removed the HLOS file and instructions for the time being until developers update ROMs to be compatible. Using the updated modem is fine by itself.

    - Download File

    - Flash modem.bin in ODIN under PHONE and wait for PASS! (ODIN did seem to hang for a moment while the phone processed. Don't panic)

    - Reboot (if you didn't have it set to do so in ODIN)

    - Profit?

    Post your results/findings to help other users :)

    Note: If your phone has rebooted and hasn't cleared "reset" into "pass" in ODIN it's not the end of the world. As long as it was successful flashing (lower left corner of ODIN) and is currently booted into android after reboot, you're fine.

    Updated Radio: http://www.mediafire.com/?jm2d34gb88jx32m
    Revert File: http://www.mediafire.com/?242ruwpbqtcssd0

    MD5 of updated Radio: 168FB171A19362678B73409C90F0DD61
    MD5 of Revert package: 7232DCCB4C00A940B24B8FB1163D7FF0
    9
    So I am on MDK still...is it a bad idea to try this radio out if I am not on ME7? I am on Hyperdrive

    No, you can try out the two and decide which one is better
    here are flashable.zip files you can flash in recovery, much easier IMO


    MDK

    ME7

    (modem = radio)


    credit to hlxanthus for the files.
    6
    Can someone do Flashable zip with radio,I want try to flaf it on sprints4, via odin it chek cheksums.

    These are in order of release. The second of course is the version of the modem from the OP. For people who don't like the new radio, just flash the MDK version. This is ONLY the modem.bin for each. I have tested both as working.

    These are loaded through Goo.IM so if you download them directly to your phone and the GooManager app it verifies MD5 automatically. Either download within GooManager and my name, or from the below links and choose GooManager as the download option when prompted.

    Download - modem_FLASHABLE_MDK.zip [MD5=167fcdd5bd57e4dc78946a63c8c69d46]

    Download - modem_FLASHABLE_ME7.zip [MD5=02147307d65ea815fa9ba8d800d7aac9 ]
    4
    I am willing to give this a shot since you mentioned it helped with your signal in your apt. In my case my location is kinda problematic because of how close it is to Verizon's home network, but I am physically located within the extended network. So in my apartment my signal fluctuates quite a bit, and more so depending on which room I am in (my living room must be close enough to get the home network, but my bedroom is just outside of it's reach).


    **Just got done and here's the results - I was able to flash the modem.bin you posted on my stock rooted phone and right off the bat things seem to be better signal wise. After rebooting the phone there were no issues that I can see or find, everything seems to be functioning correctly. Phone calls seem to sound a little better (I have no idea if it's a fluke because of the hour or the new radio), and data hasn't been impacted at all.

    I also noticed a small improvement in the signal strength readings, but I will keep monitoring it to make sure it's not a random fluke.
    3
    No, you can try out the two and decide which one is better
    here are flashable.zip files you can flash in recovery, much easier IMO


    MDK

    ME7

    (modem = radio)


    credit to hlxanthus for the files.
    Worked great! Flashed ME 7 radio last night without Odin!

    You should add this option to the OP! :thumbup:


    Sent from my SCH-I545 using Tapatalk 2