Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[GUIDE] Unlock your MK2 Knox Galaxy S4

OP Tsumi

19th February 2014, 12:00 PM   |  #1  
OP Member
Thanks Meter: 17
 
72 posts
Join Date:Joined: Nov 2010
After several hours of trial and error, I found a way that worked for me. It will trip the Knox counter though. Also, what worked for me may not work for everyone else. If you brick your device that's not my fault in any way, so good luck

Using this guide, flash back to the stock TAR (not the UVUAMDL TAR). This restores 4.2.2, which allows access to the menu. However, this alone is not enough, as it won't give you access to the perso functions. Attempting to flash the UVUAMDL TAR will result in an error (at least, it did for me).

Second, extract the modem.bin from the UVUAMDL file, and flashed it to the phone using Odin. It's similar to the guide above, but instead of using PDA, you use phone. This gives you access to the perso functions, as it forces the baseband back to UVUAMDL from UVUEMK2. It may be possible to flash the UVUAMDL.tar modem files found in other threads, I haven't tried this out myself though.

Now, at this point you can follow the instructions in this thread, as every option should now be available. If they're not, make sure your Android version is 4.2.2 and that the baseband is UVUAMDL.

If it works at this point, great, go on to the next step (you may have noticed by now that your sound is not working). If not, use RegionLock Away to fully unlock the phone. At this point, your phone should be fully unlocked and you can see it connected to the network. However, dialing/calling lags significantly, and there is no sound.

The next step is to use Odin to fully restore UVUEMK2, which would restore full functionality. You can download the file from here, and flash using the same steps above. This will restore full sound and phone functionality, while your device remains unlocked. If it gets stuck during the boot animation, you simply need to do a factory wipe from recovery (not sure if this works, haven't tested it myself), or just install your recovery of choice from Odin and install whatever ROM you want to use (what I did, which still required a full factory reset from recovery). Skipping restoring UVUEMK2 and installing your ROM of choice does not work, however. You will still have no sound and the phone function will lag considerably.

If everything goes well, you should have a fully unlocked T-mobile Galaxy S4.

Better guide by kali323:

Quote:
Originally Posted by kali323

1. Download MDB Tar. Extract from 7zip file and then rename the file (remove the .md5) so the filename should be "SGH-M919-UVUAMDB-k0nane.tar"

http://www.hunterspad.com/Domains/St...rn+To+stock%2F

2. Odin the MDB Tar in the PDA slot and once it finish go to recovery and factory reset.

3. It will take forever to reboot and it will be stuck at the boot up screen for awhile with this error "Kernel is not seandroid enforcing set warranty bit: Kernel". In about to 5-10 mins it will boot up.

4. Now youre in MDB 4.2.2 with MK2 modem.


5. Odin the .bin file below. Use the PHONE slot in odin and not PDA. Again it will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"

https://mega.co.nz/#!S9AjUAYA!GOOIp2...JiOypoAjkuAwtc

6. Now you have MDB Rom with MDL modem

7.Odin CF AutoRoot with the link below in the PDA Slot. It will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"

http://download.chainfire.eu/328/CF-...mo-sghm919.zip

8.Download RegionLock Away 1.3 App either in the thread below or buy it at the google play store to support the developer

http://forum.xda-developers.com/show....php?t=2470551

9. Run RegionLock Away and click reboot now. It will take another 5-10 mins to boot up and if you dont ask you for an unlock code with a non tmobile or non tmobile mnvo sim then youre are unlocked.

10. Odin 4.3 or 4.4 and youre done

Some additional info:

Quote:
Originally Posted by blu422

This method works the only problem I encountered is while flashing the modem i couldn't make it flash, i would flash it but then in settings my baseband would stay mk2 so the way to fix this is to flash in odin with auto reboot off. then when its done flashing unplug the phone then pull the battery and boot straight into download mode and flash the modem.bin once again same drill, auto reboot off then pull the battery then reboot and it should work.

edit: just kidding this method did not work for me, the unlock prompt no longer shows up, but an at&t sim card still will not work, although it does tell me i have five voicemails that i cannot listen to. no texts no calls no data, where it should say at&t in the notification panel it says no service... :/ any ideas? I havent yet updated back to 4.3/4.4 yet could that be the problem?

when I try to call it just says "not registered on network"


turns out that it is just because i havent updated back yet, not even a t-mobile sim works. turns out I have a blacklisted imei! but i think I am unlocked hopefully this (at least the first part) answers a few questions aroused during this process, may be the op could get updated with a couple key peices in this post. also huge kudos for this!

Last edited by Tsumi; 2nd May 2014 at 05:25 PM.
The Following 5 Users Say Thank You to Tsumi For This Useful Post: [ View ]
27th February 2014, 09:27 AM   |  #2  
Junior Member
Thanks Meter: 0
 
13 posts
Join Date:Joined: Dec 2012
hello,
i tried to flash the stock tar as you said, but i get an error.
it says:
write protection: enable
secure magiccode check fail : boot
what can i do in this case?
thank you!
Attached Thumbnails
Click image for larger version

Name:	siv.jpg
Views:	946
Size:	216.2 KB
ID:	2603295  
Last edited by ionutul; 27th February 2014 at 09:44 AM.
2nd March 2014, 01:29 AM   |  #3  
OP Member
Thanks Meter: 17
 
72 posts
Join Date:Joined: Nov 2010
Quote:
Originally Posted by ionutul

hello,
i tried to flash the stock tar as you said, but i get an error.
it says:
write protection: enable
secure magiccode check fail : boot
what can i do in this case?
thank you!

I'm not too sure actually, I didn't run into that error, and I don't have other S4s I can try it out on.

There were several things I did do before trying to flash back though, that may have had an effect. The first is rooting through motochopper's method. The second was installing and running regionlock away. Try rooting first and then flashing. Otherwise, I might have to chalk it up as something unique with my phone I'm not aware of.
Last edited by Tsumi; 2nd March 2014 at 11:52 AM. Reason: motochopper, not chainfire
The Following User Says Thank You to Tsumi For This Useful Post: [ View ]
13th March 2014, 05:38 AM   |  #4  
Junior Member
Thanks Meter: 1
 
23 posts
Join Date:Joined: Mar 2014
Quote:
Originally Posted by Tsumi

After several hours of trial and error, I found a way that worked for me. It will trip the Knox counter though. Also, what worked for me may not work for everyone else. If you brick your device that's not my fault in any way, so good luck

Using this guide, flash back to the stock TAR (not the UVUAMDL TAR). This restores 4.2.2, which allows access to the menu. However, this alone is not enough, as it won't give you access to the perso functions. Attempting to flash the UVUAMDL TAR will result in an error (at least, it did for me).

Second, extract the modem.bin from the UVUAMDL file, and flashed it to the phone using Odin. It's similar to the guide above, but instead of using PDA, you use phone. This gives you access to the perso functions, as it forces the baseband back to UVUAMDL from UVUEMK2. It may be possible to flash the UVUAMDL.tar modem files found in other threads, I haven't tried this out myself though.

Now, at this point you can follow the instructions in this thread, as every option should now be available. If they're not, make sure your Android version is 4.2.2 and that the baseband is UVUAMDL.

If it works at this point, great, go on to the next step (you may have noticed by now that your sound is not working). If not, use RegionLock Away to fully unlock the phone. At this point, your phone should be fully unlocked and you can see it connected to the network. However, dialing/calling lags significantly, and there is no sound.

The next step is to use Odin to fully restore UVUEMK2, which would restore full functionality. You can download the file from here, and flash using the same steps above. This will restore full sound and phone functionality, while your device remains unlocked. If it gets stuck during the boot animation, you simply need to do a factory wipe from recovery (not sure if this works, haven't tested it myself), or just install your recovery of choice from Odin and install whatever ROM you want to use (what I did, which still required a full factory reset from recovery). Skipping restoring UVUEMK2 and installing your ROM of choice does not work, however. You will still have no sound and the phone function will lag considerably.

If everything goes well, you should have a fully unlocked T-mobile Galaxy S4.


HELP...!

Ok, I've been reading many many articles for the past few days and finally have mustered enough energy to attempt the unlock my T-Mobile SGH-M919 running MK2 firmware. Since I was unable to get into the service menu and input keys using the many directions on this site.... I attempt to flash to old older firmware, following this guide.

I followed each direction 1 step at and time and followed it to the "T". Anyway, long story short... I tried and it soft bricked my phone. I get the warning screen that the firmware was unsuccessful and that I need to run recovery using Samsung Kies. I download the software and attempt recovery. It got to roughly 90% and then it failed too. I reverted back to Odin and reflash using MK2. It too got to about 90% and fails. What is going on?

Any more tips to get this thing working again?? Help.
The Following User Says Thank You to dyangster For This Useful Post: [ View ]
13th March 2014, 06:03 AM   |  #5  
Junior Member
Thanks Meter: 1
 
23 posts
Join Date:Joined: Mar 2014
Got to only 93% via Kies... two times!
Attached Thumbnails
Click image for larger version

Name:	Fail.jpg
Views:	599
Size:	145.0 KB
ID:	2627860  
13th March 2014, 06:52 AM   |  #6  
egren58's Avatar
Senior Member
Thanks Meter: 291
 
1,970 posts
Join Date:Joined: Jul 2011
Um I'm almost sure once you are on mk2 your not able to go back to mdl. Do to the boot loader...

Sent from my SGH-M919 using xda app-developers app

---------- Post added at 08:52 PM ---------- Previous post was at 08:51 PM ----------

If your rooted you can try region Loa away by chain fire see if it works.

Sent from my SGH-M919 using xda app-developers app
13th March 2014, 07:01 AM   |  #7  
Junior Member
Thanks Meter: 1
 
23 posts
Join Date:Joined: Mar 2014
Quote:
Originally Posted by egren58

Um I'm almost sure once you are on mk2 your not able to go back to mdl. Do to the boot loader...

Sent from my SGH-M919 using xda app-developers app

---------- Post added at 08:52 PM ---------- Previous post was at 08:51 PM ----------

If your rooted you can try region Loa away by chain fire see if it works.

Sent from my SGH-M919 using xda app-developers app



wwwhheeew.... finally got it to unbrick. Took 4 hours to get this thing operational again. I thought the guide specifically says it can downgrade from MK2 to MDL? I already ran the Regionlock app and it appears to be done right, but it's still not sim unlocked.!
15th March 2014, 01:10 AM   |  #8  
dragonhart6505's Avatar
Senior Member
Flag Reading, PA
Thanks Meter: 131
 
485 posts
Join Date:Joined: Jun 2010
Donate to Me
More
Quote:
Originally Posted by dyangster

wwwhheeew.... finally got it to unbrick. Took 4 hours to get this thing operational again. I thought the guide specifically says it can downgrade from MK2 to MDL? I already ran the Regionlock app and it appears to be done right, but it's still not sim unlocked.!

same problem, RLA does not work on MK2, flashing MDL modem and going through the motions also does NOT sim unlock...cant seem to get this thing working.

funny thing is it wont even register on the network with a GoSmart sim, GoSmart being a TMO MVNO.

i hate sammy...
16th March 2014, 01:59 AM   |  #9  
OP Member
Thanks Meter: 17
 
72 posts
Join Date:Joined: Nov 2010
I flashed to the stock firmware first, which I believe is the MDB firmware. It doesn't work attempting to go to MDL. Going to MDB gets you 4.2.2, but you would still be locked because it keeps the MK2 modem.

The second step was to extract the MDL modem.bin from the TAR, and then flash that on Odin via the phone method. That was how I was able to downgrade the modem from MK2 to MDL, but that screws up sound, but allows you access to the unlock functions.
The Following User Says Thank You to Tsumi For This Useful Post: [ View ]
16th March 2014, 07:58 AM   |  #10  
Senior Member
Flag Kali
Thanks Meter: 85
 
270 posts
Join Date:Joined: Jun 2011
More
Odin MDB and factrory reset in recovery. I was stuck at "Kernel is not seandroid enforcing set warranty bit: Kernel" at the boot up screen. I thought it didnt work and wasnt going to boot up and was looking MK2 tar and then out of nowhere after 5 mins I hear the tmobile boot up sound and this **** actually boot it. Im in MDB 4.2.2 with mk2 baseband. Just need to downgrade baseband and Ill let you know if it works guys. Ill post all files as well that I use

---------- Post added at 10:34 PM ---------- Previous post was at 10:07 PM ----------

I have successfully unlocked and I was at 4.3. Huge props to Tsumi. Ill post an updated guide of Tsumi unlocked method of all the files I used

---------- Post added at 10:58 PM ---------- Previous post was at 10:34 PM ----------

How to Unlocked M919 on MK2 4.3. This method has no been tested on the new MB4 4.4.2 update

Huge Props to Tsumi. Is his method and thank/donate to him. i use his guide but it wasnt clear enough so I went searching to internet for links for all the correct files.

Im not responsible for any bricks but if you follow carefully then you shouldn't

This method will trip KNOX

1. Download MDB Tar. Extract from 7zip file and then rename the file (remove the .md5) so the filename should be "SGH-M919-UVUAMDB-k0nane.tar"

http://www.hunterspad.com/Domains/St...rn+To+stock%2F

2. Odin the MDB Tar in the PDA slot and once it finish go to recovery and factory reset.

3. It will take forever to reboot and it will be stuck at the boot up screen for awhile with this error "Kernel is not seandroid enforcing set warranty bit: Kernel". In about to 5-10 mins it will boot up.

4. Now youre in MDB 4.2.2 with MK2 modem.


5. Odin the .bin file below. Use the PHONE slot in odin and not PDA. Again it will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"

https://mega.co.nz/#!S9AjUAYA!GOOIp2...JiOypoAjkuAwtc

6. Now you have MDB Rom with MDL modem

7.Odin CF AutoRoot with the link below in the PDA Slot. It will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"

http://download.chainfire.eu/328/CF-...mo-sghm919.zip

8.Download RegionLock Away 1.3 App either in the thread below or buy it at the google play store to support the developer

http://forum.xda-developers.com/show....php?t=2470551

9. Run RegionLock Away and click reboot now. It will take another 5-10 mins to boot up and if you dont ask you for an unlock code with a non tmobile or non tmobile mnvo sim then youre are unlocked.

10. Odin 4.3 or 4.4 and youre done
Last edited by kali323; 16th March 2014 at 08:20 AM.

The Following User Says Thank You to kali323 For This Useful Post: [ View ]
Post Reply Subscribe to Thread

Tags
knox, mk2, unlock
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes