[Firmware][Unofficial][ODIN]S4 DevEd[boot/recovery/radio/modem][MDK-MJ7-MK2-NC5]

Search This thread

Skeetch79

Senior Member
Oct 29, 2010
315
203
West Milford, NJ
Google Pixel 5
No problem on the delay, it is the holidays. Thank you very much for the reply and the info. I don't think my device will come back by any other means than JTAG. I can't use ODIN because it won't even boot into download mode. I do believe though, that if I can JTAG the correct files to the tz partition, the chain of trust will be restored and device will boot at least the bootloader. From there I can ODIN usable firmware. I have acquired the tz.mbn file from a consumer device on MDK but if you have it available from the Dev Ed MDK I would feel more confident in the restoration of my device.

Edit: The MDK PIT file could also be beneficial to my quest. Thanks!

Merry Christmas! Hope this helps! https://www.dropbox.com/sh/1430zr036jkhdn8/AAAo9ZuGQ4cuZv695SFdn_yUa?dl=0
 

cawaller

Member
May 17, 2011
44
4
GPS Issue

UI knew at some point I would be back here asking for help. Been playing around with a few of the ROMS that are out there for the S4 Dev. I'm on MDK and so far have been able to flash pretty much all but one of them. I'm not sure if it was one of the ROMS I flashed but last week the GPS quit working in my apps. When I start Strava or Map My Run, the GPS never locks in. I discovered this after running nearly 5 miles one day. The app said it needed more distance to register a run. I've restored back to my base version but still have the issue. I've downloaded GPS Test and it does not lock on any Satellites. It sees 20-23 of them depending on where I am when I test but never locks on. If I open Maps and choose the location button, it takes me to my location, but if I start a navigation it will plot a route but then tell me "gps signal lost. Any ideas on how to get that function back assuming it is not a hardware issue?
I flashed the boot, modem and radio back to base and got my GPS back.
 
Last edited:

klabit87

Senior Member
Jul 11, 2011
3,013
2,281
Is there any way I could get the OC1 files?
Thanks so much for the valuable information and files here.
 

generalnod

Senior Member
Dec 2, 2012
68
7
ant+ support via radio file for l545OYUAMDK?

Does the radio file include the firmware update to provide ant+ support?

I'm on l545OYUAMDK running Cyanogenmod 12 and I'd like to get the ant+ firmware update included with MJ7 (I don't like using an adapter).

My impression is fully updating to MJ7 is going to cause issues using customs roms...so I've avoided it.

thanks in advance for any help as well as for posting these and keeping them online!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    For Samsung Galaxy S4 Developer Edition Devices Only!

    I have extracted the Boot.img, Recovery.img, NON-HLOS.bin (Radio) and Modem.bin files from the Samsung Galaxy S4 Developer Edition on builds I545OYUAMDK (original Factory Firmware), I545OYUEMJ7 and I545OYUEMK2. With those files, I have created various tar.md5 restore files which include the Boot, Recovery, Radio and Modem partitions. The tar.md5 files were created using 64-bit Cygwin in Windows 8 by running the following commands (for example):

    filename=I545OYUAMDK
    tar -H ustar -c boot.img recovery.img > $filename.tar
    md5sum -t $filename.tar >> $filename.tar
    mv $filename.tar $filename.tar.md5


    I have also extracted the MD5 sums and SHA-1 values from each tar.md5 file below and have posted them for reference. Please use at your own risk. I am not responsible for damaged devices.

    Again, for S4 Developer Edition Devices Only!!!

    Odin 3.07 - Odin 3.07
    Odin 3.09 - Odin 3.09

    I545OYUAMDK
    Boot and Recovery: I545OYUAMDK_Boot_Recovery_Restore.tar.md5
    MD5 sum: 6b41bc15f669ef1c962626c011735790
    SHA-1: 1cc5d06781ecb6fa4dea28b107cad8b6237902ce

    Modem and Radio: I545OYUAMDK_Modem_Radio_Restore.tar.md5
    MD5: b063d6a1496cf2076199782542ec9f08
    SHA-1: b67a531b252d94a01b559b260a744d81610d9792

    Modem: I545OYUAMDK_Modem_Restore.tar.md5
    MD5: ee08455730004f0c4321bf98ca2a26d8
    SHA-1: bce6dda7f5b6aab3abd965f734e4b772ec8a035e

    Radio: I545OYUAMDK_Radio_Restore.tar.md5
    MD5: 487aab147698d96eb254336e4192fc1e
    SHA-1: 25273c28a5ea411cfdc113e8fceb30c5a7ff9097

    I545OYUEMJ7
    Boot and Recovery: I545OYUEMJ7_Boot_Recovery_Restore.tar.md5
    MD5 sum: a8c2954756ef9b82102d4c9cc999f810
    SHA-1: f9fc296bff37682718b07a1de47f8250b1aaf52d

    Modem and Radio: I545OYUEMJ7_Modem_Radio_Restore.tar.md5
    MD5: acf4d72e743469932a2aa9f54f4cafeb
    SHA-1: 69271c6e610835dbfd320e4bafb5a759814e7e74

    Modem: I545OYUEMJ7_Modem_Restore.tar.md5
    MD5: 9396924db03efd8fb1856813cf2419b6
    SHA-1: f5210eee25281b68fb450893c02357e7a26d10ed

    Radio: I545OYUEMJ7_Radio_Restore.tar.md5
    MD5: 3989422900fb177d4d36efa35e1869ae
    SHA-1: 519111d252122776a6d2a7f33c888544da2f5a36

    I545OYUEMK2
    Boot and Recovery: I545OYUEMK2_Boot_Recovery_Restore.tar.md5
    MD5 sum: b5017c04df3b73a363e012feef73c343
    SHA-1: 13372816d6e774d84272f53b5285ed6a62c30a97

    Modem and Radio: I545OYUEMK2_Modem_Radio_Restore.tar.md5
    MD5: 63eec954e5d4290b8d7dfb96fcdae580
    SHA-1: 2f3b4f6587ca3e233e0091db5742c9171053ca40

    Modem: I545OYUEMK2_Modem_Restore.tar.md5
    MD5: 7791393740b06a304b015ee1f28a0fa8
    SHA-1: 9d5eb0b7f90ae8d4ee04486533eac30a30dbd279

    Radio: I545OYUEMK2_Radio_Restore.tar.md5
    MD5: 9252cbac68d52a62a8811e7cd4542940
    SHA-1: cb20f968c0e1fff74d68613c56230da1b127cdef

    I have flashed these files using Odin 3.07 and Odin 3.09. Load tar.md5's into "PDA" slot in Odin 3.07 or "AP" slot in Odin 3.09. For both Odin 3.07 and Odin 3.09, "F. Reset Time" and "Auto-Reboot" options are ok to be checked, but make sure "Re-partition" is NOT CHECKED.

    If you have any questions or any requests for other partitions please do not hesitate to ask. This is the first thread I have ever created, please go easy on me! :)
    5
    Holy moly. This is wonderful news! Am on vacation and will try when I get home next week. Thank you so much.
    If you can flesh out each step more clearly it is most appreciated. Do we keep 2 versions of Odin opened at same time or do one at a time?

    Sent from my SCH-I545 using xda app-developers app

    I would be glad to help out as best I can.

    You only need one version of Odin installed and running at a time, I know there are two versions available, which is the reason I linked to both. User's choice. Surge or Bait-Fish may have more insight whether one is better than the other. Personally, I have always used 3.07.

    1. Download and install USB drivers for phone from Samsung's Website (http://www.samsung.com/us/support/owners/product/SCH-I545ZKDVZW? - scroll down for "downloads" option)

    2. Download the desired tar.md5 file as linked above. Check the md5 or SHA-1. (I have stumbled across an interesting program that integrates in to Windows and gives the option of md5, SHA-1, etc checking - HashCheck Shell Extension - http://code.kliu.org/hashcheck/ - right click the tar.md5 file and choose properties. You will see the option for Checksums)

    3. Put phone in download mode. (Power off phone. Hold Volume down and Power button. Press Volume up at the warning screen.)

    4. Connect to Computer via USB. Let windows install necessary drivers.

    5. Load Odin.

    6. Odin should list the phone on a ID:COM port (upper left of the program - i.e. ID:COM 6)

    7. Load tar.md5 file into Odin - 3.07 use PDA button. 3.09 use AP button.

    8. Make sure only Auto-reboot and F. Reset Time are checked. Re-Partition should not be checked, if it is, UN-CHECK it!

    9. As long as tar.md5 is loaded properly, the phone is in download mode, Odin sees the phone on a COM port and only F. Reset Time and Auto-Reboot are checked, press the "start" button.

    10. The phone should reboot and eventually you will see a green "PASS!" above the COM port area.

    11. You should be now good to go.

    12. Reboot to recovery or check baseband to ensure things worked.

    I have hosted these files also as a way to get out of binds (i.e. you flash an inappropriate Philz Touch recovery or TWRP recovery, you can revert to stock recovery and boot or you wish to change or revert basebands). You can obviously also use these files at your own leisure to change basebands, recoveries or boots.

    Hope this helps. Enjoy the rest of vacation.

    As I said, I have other partitions available if need be.
    3
    Individual Boot and Recovery images

    Individual Boot and Recovery Odin tar.md5's

    I545OYUAMDK
    Boot: I545OYUAMDK_Boot_Restore.tar.md5
    MD5 sum: afba73816e13008afecf2499b3a5c3a3
    SHA-1: a2ba6c75436b022fa40061aecea9716a795d527d

    Recovery: I545OYUAMDK_Recovery_Restore.tar.md5
    MD5 sum: 87ea570503f3114f45b89dc9991e0e2d
    SHA-1: eb7f3a50bf7af6935eacd6e29a791d9d1e4e359e

    I545OYUEMJ7
    Boot: I545OYUEMJ7_Boot_Restore.tar.md5
    MD5 sum: cb183c42be45915f7ebb26a9342d72a8
    SHA-1: f537fa025a7f139c2538629cb8cb90334a7205f4

    Recovery: I545OYUEMJ7_Recovery_Restore.tar.md5
    MD5 sum: 2c3c1fdb9b4ca20f9985c20cd77faf54
    SHA-1: 108f6e5b169bef047c9f2ce8551f91a1265c3236

    I545OYUEMK2
    Boot: I545OYUEMK2_Boot_Restore.tar.md5
    MD5 sum: beea9797febf1471ae75240a67379d3a
    SHA-1: d40ca498559c38adec9a135fa81728ffcf1c7ea3

    Recovery: I545OYUEMK2_Recovery_Restore.tar.md5
    MD5 sum: 9faa83bed96ea652584bc56c54bd986b
    SHA-1: 4b573f989b6b1b7a4fcfe96608f091ca47deeb1e
    3
    I545OYUFNC5 Boot, Recovery, Radio and Modem images [UPDATED: 7/15/2014]

    Below you will find the Modem, Radio and and Boot images from the recent Verizon 4.4.2 I545OYUFNC5 KitKat build (Developer Device version) and Recovery image from the recent Verizon 4.4.2 I545VRUFNC5 build (Retail version). Since there isn't a root method yet for Verizon 4.4.2 KitKat on the Galaxy S4, in order to achieve root, the stock recovery partition had to be overwritten with Philz Touch Recovery and Chainfire's SuperSu was then flashed. Because of this there isn't a back up of the 4.4.2 Developer Recovery image. The Recovery Image that is included is the stock recovery from the Retail Galaxy S4 on 4.4.2 KitKat, this functions perfectly fine on the Developer Device.

    The Build for the Galaxy S4 Developer Edition device on 4.4.2 KitKat is KOT49H.I545OYUFNC5 and the Baseband is I545OYUFNC5. If you decide to flash the stock Recovery, it will say I545VRUFNC5 in the upper corner of the recovery screen. If you want a custom recovery, however, you can flash the latest Philz Touch Recovery for jflte devices (found here). At the time of this write-up 6.50.6 is the latest version.

    I have not tested any of these files on the Developer S4 running builds earlier than 4.4.2 KitKat - i.e. I545OYUAMDK (4.2.2), I545OYUEMJ7 (4.3) and I545OYUEMK2 (4.3). I do not think the Radio and Modem would have any issue on a non-KitKat build, but I would recommend holding off on the Boot file unless you have a 4.4.2 KitKat build on your device. Both Modem (modem.bin) and Radio (NON-HLOS.bin) were edited to remove the padded zero's at the end of the file which allows ODIN flashing (allows the pass on the signature test)(thanks @Surge1223 for your HexEdit guide). If you have any issues with the Modem and Radio, you can always flash back to a version which is stable for your device using the above posted files.

    Below you will find the Boot, Recovery, Modem and Radio images as individual tar.md5's and also bundled as Modem/Radio, Boot/Recovery and Boot/Recovery/Modem/Radio.


    I545OYUFNC5

    Boot (OYU): I545OYUFNC5_Boot_Restore.tar.md5
    MD5: 4653908b820535c4a953432a46558378
    SHA-1: 6f67c3ad8e2ec38b3189b300e478d5e912055445

    Recovery (VRU): I545OYUFNC5_Recovery_Restore.tar.md5
    MD5: 7fb655f8b05b0e72edb5258705de992a
    SHA-1: d07f72bd8f8279c5dff23c02589f76308a5b8ee5

    Modem (OYU): I545OYUFNC5_Modem_Restore.tar.md5
    MD5: bc61795e901c424f4735d63b88571c4c
    SHA-1: 8e53ec92b82a64868a28dffbe7513fa662d45c48

    Radio (OYU): I545OYUFNC5_Radio_Restore.tar.md5
    MD5: b6dbfa97425ac88c710cb05743a99932
    SHA-1: 733118569ec934d87b9e22fe903d17d3ea427601

    Boot (OYU) and Recovery (VRU): I545OYUFNC5_Boot_Recovery_Restore.tar.md5
    MD5: 3066f7578bf7d5a1aa982a8ab5b1bcf8
    SHA-1: 606b3252ee826dc87577ed4397c24db34845ffca

    Modem (OYU) and Radio (OYU): I545OYUFNC5_Modem_Radio_Restore.tar.md5
    MD5: 3ae8fc408c542d4d99f0b2cf199e0776
    SHA-1: e3dfb6634a802d19dcfe92abeaa028788a28ac8e

    Boot (OYU), Recovery (VRU), Modem (OYU) and Radio (OYU): I545OYUFNC5_Boot_Recovery_Modem_Radio_Restore.tar.md5
    MD5: 7c55aae7fdf93a6cacb076eaece03b77
    SHA-1: 9960f092ee7fcd0321d99929f309b87caee8b7a6
    2
    So, if I have a Developer Edition and wanted to backup my aboot partition, would I do that with a terminal command like this?
    Code:
    busybox dd if=/dev/block/mmcblk0p6 of=$/storage/sdcard0/backup/aboot.mbn
    (taking that code from http://xdaforums.com/showthread.php?t=2417603 )
    You know, just in case...

    From a pc with your phone connected, adb set up and root permissions already granted you can run: adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/extSdCard/aboot.mbn'"



    Sent from my SCH-I545 using Tapatalk