Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,743,029 Members 43,812 Now Online
XDA Developers Android and Mobile Development Forum

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

Tip us?
 
Skeetch79
Old
(Last edited by Skeetch79; 17th July 2014 at 04:54 PM.)
#1  
Skeetch79's Avatar
Senior Member - OP
Thanks Meter 159
Posts: 232
Join Date: Oct 2010
Location: West Milford, NJ
Default [Firmware][Unofficial][ODIN]S4 DevEd[boot/recovery/radio/modem][MDK-MJ7-MK2-NC5]

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!
The Following 10 Users Say Thank You to Skeetch79 For This Useful Post: [ Click to Expand ]
 
Skeetch79
Old
(Last edited by Skeetch79; 6th June 2014 at 03:35 PM.)
#2  
Skeetch79's Avatar
Senior Member - OP
Thanks Meter 159
Posts: 232
Join Date: Oct 2010
Location: West Milford, NJ
Default 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
The Following 3 Users Say Thank You to Skeetch79 For This Useful Post: [ Click to Expand ]
 
Skeetch79
Old
(Last edited by Skeetch79; 17th July 2014 at 04:54 PM.)
#3  
Skeetch79's Avatar
Senior Member - OP
Thanks Meter 159
Posts: 232
Join Date: Oct 2010
Location: West Milford, NJ
Default 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
The Following 3 Users Say Thank You to Skeetch79 For This Useful Post: [ Click to Expand ]
 
markwebb
Old
(Last edited by markwebb; 6th February 2014 at 01:41 AM.)
#4  
Senior Member
Thanks Meter 106
Posts: 464
Join Date: Jun 2010
Location: Windsor Locks
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
OG Droid >>> Droid Bionic >>> Samsung Galaxy S4 Dev Edition/Nexus 5/MOTO X
Samsung Chromebook
Nexus 7 2013
Chromecast
 
Skeetch79
Old
#5  
Skeetch79's Avatar
Senior Member - OP
Thanks Meter 159
Posts: 232
Join Date: Oct 2010
Location: West Milford, NJ
Quote:
Originally Posted by markwebb View Post
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/ow...CH-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.
The Following 5 Users Say Thank You to Skeetch79 For This Useful Post: [ Click to Expand ]
 
jpcalhoun
Old
#6  
Senior Member
Thanks Meter 75
Posts: 257
Join Date: Feb 2012
Quote:
Originally Posted by Skeetch79 View Post
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/ow...CH-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.
Wow, thank you Skeetch79. These could be a life saver no doubt.
 
Skeetch79
Old
#7  
Skeetch79's Avatar
Senior Member - OP
Thanks Meter 159
Posts: 232
Join Date: Oct 2010
Location: West Milford, NJ
Quote:
Originally Posted by jpcalhoun View Post
Wow, thank you Skeetch79. These could be a life saver no doubt.
No problem, happy to help.

Case in point: I have always enjoyed Philz Touch Recovery. I decided to give TWRP a go. An earlier version flashed fine and I didn't have any issues. I flashed a later version and upon booting my phone it would automatically load to download mode. I could not get past it. Fortunately I had the stock boot and recovery files on hand, which I flashed through Odin and was back to stock boot and recovery. I then proceeded to load Philz and all was fine.
 
jpcalhoun
Old
#8  
Senior Member
Thanks Meter 75
Posts: 257
Join Date: Feb 2012
Quote:
Originally Posted by Skeetch79 View Post
No problem, happy to help.

Case in point: I have always enjoyed Philz Touch Recovery. I decided to give TWRP a go. An earlier version flashed fine and I didn't have any issues. I flashed a later version and upon booting my phone it would automatically load to download mode. I could not get past it. Fortunately I had the stock boot and recovery files on hand, which I flashed through Odin and was back to stock boot and recovery. I then proceeded to load Philz and all was fine.
I've seen a couple of post the last few days with other's experiencing the same thing. I've never had an issue with TWRP, but then again I've never flashed anything but 2.5.0.2. I started out on Philz but was trying to flash a ROM (I think it was Vanar) and I could not get the ROM to boot. The ROM developer recommended I try a different recovery, TWRP, I did, and the ROM flashed correctly. I didn't like the ROM so I switched to a TW version of Eclipse, but kept TWRP. What's strange is TWRP has been the "gold standard" of recoveries for a long time...I wonder what has happened in the later versions of TWRP? Again, thanks for these files...great job!!!
 
livinxtreme2114
Old
#9  
livinxtreme2114's Avatar
Junior Member
Thanks Meter 0
Posts: 5
Join Date: Oct 2007
Location: The Coast
Awesome job, bro. The Dev Edition community has really needed something like this for quite a while now. Its nice to now finally have the option to restore back to stock in the event we just so happen to choose to actually take advantage of the very thing our "Developer Edition" devices were specifically marketed for, and for which we paid full retail price to obtain. It baffles me to think that any company would offer any device and market it under the "Developer Edition" label yet refuse to offer any means of support as a base to restore the device back to stock in the likely event, as is often the case in a development scenario, where things go wrong. But that is another story, I just wanted to give you props.

I have a concern though. From what I have gathered browsing through various threads, others with the more recent MJ7 Dev Edition are having trouble flashing custom AOSP roms with the newer bootloader and can not downgrade to MDK. I have the MDK Dev Edition and although I've been able to update my modem in the past to MJ7 by flashing strictly the modem files provided on other threads, I was curious about upgrading my current MDK radio to the more recent MJ7 version as well. But from what I've gathered, I would need to first update my current MDK bootloader version as well to MJ7 in order for the newer MJ7 radio to successfully update. I fear this would leave me with the same problem not being able to flash AOSP roms due to the newer bootloader and unable to downgrade back to MDK.

I guess my question is: Is this correct? And is there really a difference between the NON-HLOS.bin (Radio) and Modem?
If I've helped you in any way, Please remember to hit the Thanks button.
 
Skeetch79
Old
#10  
Skeetch79's Avatar
Senior Member - OP
Thanks Meter 159
Posts: 232
Join Date: Oct 2010
Location: West Milford, NJ
Quote:
Originally Posted by livinxtreme2114 View Post
Awesome job, bro. The Dev Edition community has really needed something like this for quite a while now. Its nice to now finally have the option to restore back to stock in the event we just so happen to choose to actually take advantage of the very thing our "Developer Edition" devices were specifically marketed for, and for which we paid full retail price to obtain. It baffles me to think that any company would offer any device and market it under the "Developer Edition" label yet refuse to offer any means of support as a base to restore the device back to stock in the likely event, as is often the case in a development scenario, where things go wrong. But that is another story, I just wanted to give you props.

I have a concern though. From what I have gathered browsing through various threads, others with the more recent MJ7 Dev Edition are having trouble flashing custom AOSP roms with the newer bootloader and can not downgrade to MDK. I have the MDK Dev Edition and although I've been able to update my modem in the past to MJ7 by flashing strictly the modem files provided on other threads, I was curious about upgrading my current MDK radio to the more recent MJ7 version as well. But from what I've gathered, I would need to first update my current MDK bootloader version as well to MJ7 in order for the newer MJ7 radio to successfully update. I fear this would leave me with the same problem not being able to flash AOSP roms due to the newer bootloader and unable to downgrade back to MDK.

I guess my question is: Is this correct? And is there really a difference between the NON-HLOS.bin (Radio) and Modem?
Thank you for the props. I have to agree that there has been a minimal amount of support for this phone from the community, though some devs are really taking charge and leading the way. Sadly, there has been virtually no support from Samsung.

I do recall, however, when I was on full MDK O/S for my DevS4, I was able to successfully flash the MJ7 radio without issue. I kept the MDK bootloader while enjoying the MJ7 baseband. If you wish, I can always post the tar.md5's of just the radio (minus the modem). When I have the chance, I can always look into it.

I can't really answer your last question confidently. I am relatively new to this whole scene and have learned as I have gone along. Hope I was able to help, just even a little bit.

Tags
developer, edition, i545oyuamdk, i545oyuemj7, i545oyuemk2
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes