5,594,805 Members 37,053 Now Online
XDA Developers Android and Mobile Development Forum

[GUIDE] Unlock your MK2 Knox Galaxy S4

Tip us?
 
Tsumi
Old
(Last edited by Tsumi; 16th March 2014 at 01:07 PM.)
#1  
Member - OP
Thanks Meter 14
Posts: 67
Join Date: Nov 2010
Thumbs up [GUIDE] Unlock your MK2 Knox Galaxy S4

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 View Post
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
The Following 3 Users Say Thank You to Tsumi For This Useful Post: [ Click to Expand ]
 
ionutul
Old
(Last edited by ionutul; 27th February 2014 at 08:44 AM.)
#2  
Junior Member
Thanks Meter 0
Posts: 13
Join Date: 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:	440
Size:	216.2 KB
ID:	2603295  
 
Tsumi
Old
(Last edited by Tsumi; 2nd March 2014 at 10:52 AM.) Reason: motochopper, not chainfire
#3  
Member - OP
Thanks Meter 14
Posts: 67
Join Date: Nov 2010
Quote:
Originally Posted by ionutul View Post
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.
The Following User Says Thank You to Tsumi For This Useful Post: [ Click to Expand ]
 
masoodskio
Old
#4  
Junior Member
Thanks Meter 0
Posts: 7
Join Date: Dec 2010
Quote:
Originally Posted by ionutul View Post
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 curious, how come you didn't trip the Knox counter?
 
JerkLife
Old
#5  
JerkLife's Avatar
Member
Thanks Meter 8
Posts: 67
Join Date: Feb 2013
Default Help

Hey I Have A Tmobile Galaxy s4 and it says my sim isn't registered on the network i was just wondering if there was anyway to get this running, i tried the above method and it completed but i still can't use a tmobile sim on my phone.
 
Tsumi
Old
#6  
Member - OP
Thanks Meter 14
Posts: 67
Join Date: Nov 2010
Quote:
Originally Posted by JerkLife View Post
Hey I Have A Tmobile Galaxy s4 and it says my sim isn't registered on the network i was just wondering if there was anyway to get this running, i tried the above method and it completed but i still can't use a tmobile sim on my phone.
If you have a T-mobile S4 and a T-mobile sim, and it says sim is not valid, then you need to contact T-mobile about your sim card. Either that, or your phone has a bad IMEI (not sure what error message would pop up if you have a bad IMEI). Either way, it's not an unlocking problem. Either your sim or your phone is invalid on the T-mobile network.
The Following User Says Thank You to Tsumi For This Useful Post: [ Click to Expand ]
 
dyangster
Old
#7  
Junior Member
Thanks Meter 1
Posts: 23
Join Date: Mar 2014
Quote:
Originally Posted by Tsumi View Post
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: [ Click to Expand ]
 
dyangster
Old
#8  
Junior Member
Thanks Meter 1
Posts: 23
Join Date: Mar 2014
Got to only 93% via Kies... two times!
Attached Thumbnails
Click image for larger version

Name:	Fail.jpg
Views:	249
Size:	145.0 KB
ID:	2627860  
 
egren58
Old
#9  
egren58's Avatar
Senior Member
Thanks Meter 194
Posts: 1,550
Join Date: 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
 
dyangster
Old
#10  
Junior Member
Thanks Meter 1
Posts: 23
Join Date: Mar 2014
Quote:
Originally Posted by egren58 View Post
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.!
Tags
knox, mk2, unlock
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes