• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile] [GUIDE][MK5][WIP]Rooting MK5 4.3 for Newbies!

Status
Not open for further replies.

TheBritton

Resident Galaxy Cat
Oct 9, 2011
2,257
1,225
Amarillo, TX
thebritton.tumblr.com
ROOTING MK5 FOR NEWBIES
THIS IS FOR USA DEVICES ONLY!!
This Guide is designed for complete newcomers including those who have acquired new devices shipped with MK5. This Guide may seem reiterative to those familiar with the rooting world ;)

WARNING: ROOTING MK5 WITH KNOX WILL TRIP THE KNOX FLAG!

Information about Knox:
[Q&A][i9505] Knox Q&A / Discussion Thread - ask questions here! - xda-developers
[FAQ] KNOX and you - xda-developers
https://www.samsungknox.com/en/overview/technical-details


Known Facts About KNOX:

  • Upgrading to newer Samsung firmware MK5 will upgrade the bootloader to KNOX bootloader. this will give an additional 2 lines in download mode about KNOX status.
  • Not possible to downgrade to KNOX-disabled firmwares/bootloaders without tripping the KNOX flag (An attempt sets 0x1) (even though some people state, downgrade is possible when omitting the bootloader file in a firmware package: see http://forum.xda-developers.com/show....php?t=2444671, not confirmed)
  • Even if you flash a KNOX-enabled firmware via Odin (e.g. the latest fw) Knox will be set to 0x1
  • Flashing unsigned or modified images via Odin will set KNOX to 0x1
  • Once the KNOX flag gets set to 0x1 there is no way to set it back (that anyone has found yet anyway!) Samsung stated, resetting the flag is impossible
  • KNOX is mandatory and can not be completely removed
  • Warranty Void is no counter, it is a flag (0,1) it was never seen 0x2 or so
  • Mirroring all partitions from a clean 0x0-Device to a 0x1-Device via JTAG produces an unfunctional device (reversible by restoring the 0x1 partitions on the phone)
  • KNOX bootloader verifies signatures of kernels and recoveries. No custom ones possible without voiding the KNOX warranty
  • If the KNOX warranty void line says 0x1 then you cannot use KNOX software as your device has been flagged as insecure. By this I mean that if your workplace / company supports bring your own device to work for corporate emails etc and they use KNOX to keep security your device will not allow this. You are still able to use future Samsung firmware releases with the KNOX flag 0x1.
  • with the new KNOX bootloader root will work, however rooting will trip the KNOX flag

ROOTING MK5 4.3:
Make sure you have the Samsung USB drivers installed on your computer.
You may find those here: Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe

First thing you'll need to root this phone is a custom recovery. We will be using Philz Touch Recovery. It performs beautifully on this device and is packed with features. You will need to download to your computer the latest tar here: http://androidforums.com/virgin-mob...cial-philz-touch-recovery-6-0-11-24-13-a.html

If you don't have Odin installed on your computer, do that now. You can find Odin here: [ tool ] Odin 3.04 - xda-developers

Now you're going to want to download this file to your SD Card:
SuperSU (CWM installable zip) found here: [2014.02.06] SuperSU v1.93 - xda-developers

You have downloaded and installed Odin and Samsung USB drivers listed above? You've downloaded the Philz Recovery .tar file to your computer and you've place the SuperSU file on your SD card? Okay, great!

Now, let's flash the custom recovery, which will be Philz Recovery, on your device! And let's root this thing!

  1. Turn off your VM Samsung Galaxy S3
  2. On your PC, launch the ODIN.exe file you unzipped from the prerequisites.
  3. On ODIN, click the PDA section and select the Philz Recovery .tar you downloaded from the link above. Uncheck Auto Reboot! Make sure NO partition options are checked!
  4. Place phone in download mode by holding Volume Down + Home while powering up. Hold until confirmation screen appears. Confirm by pressing Volume +.
  5. Connect your phone to the PC via USB cable
  6. Check ODIN. A small box on the upper left should turn blue and the dialog box must display "Added!!"
  7. Select "Start" and wait for it to finish. After it is complete, Odin will say PASS! After you see this, disconnect the USB cable from your phone and pull your battery out of your phone.
  8. Place the battery back in. While holding the VOLUME UP + Home button, while powering up and hold it until you see the blue text that says "Booting into recovery". As soon as you see this blue text let go of all the buttons!
  9. We will now install SuperSU with the custom recovery. Click on Install in your custom recovery (Philz) and navigate to where you placed the file listed earlier which will be the SuperSU zip. Assuming the installation is successful, you will then want to select Reboot System from your Philz Recovery menu.
  10. You should now be rooted! I assume you are familiar with what rooting does so there is no need to explain how SuperSU works. ENJOY YOUR ROOTED PHONE!

PLEASE NOTE: If you haven't updated to MK5 4.3 yet, you can do so by flashing jdsingle's Knox-Free MK5 ROM which does NOT contain Knox bootloader or apps found here: http://androidforums.com/virgin-mob...exed-deodexed-virgin-mobile-boost-mobile.html
 
I recall you having written in another thread that rooting trips the KNOX marker in the bootloader, but that one should still be able to receive and install Samsung official OTA updates regardless. Correct?

From my understand, yes. You will be able to install future updates. You just will not be able to downgrade to a non-Knox bootloader
Tripping the Knox flag disables Knox security and if you were a government agent or corporate exec that uses it, your protected info is not accessible anymore ;)

EDIT: and thanks! I guess it would be good to add warning that rooting trips the KNOX bootloader (doing so now) LOL :D
 
  • Like
Reactions: peter counias
Upvote 0
Dumb out-of-left-field question... I'm on CM10.2 Nightly, MD7 modem, CWM Touch 6.0.4.3 right now. if I was to put the stock recovery back, and flash the MK5 update, would I lose CM10.2, like would it flash stock back on? If so, would I be able to put CWM back on through odin and flash CM10.2 back?
 
Upvote 0
I have flashed knox remover script right after flashing supersu update and there were no problems with supersu working at the first boot after rooting.
[CWM][SCRIPT][4.2.2/4.3] DE-SAMSUNGNIZER Script V4.1 - Clean all unneded Samsung Crap - xda-developers

I think this is much simpler.

I have also used the latest CWMT (6.0.4.3) for d2spr from the clockworkmod website. Since it is an image, I have just put it in a tar file to use with Odin
http://www.clockworkmod.com/rommanager

The tar file is also here
CWMT-6.0.4.3-d2spr
 
  • Like
Reactions: TheBritton
Upvote 0
I have flashed knox remover script right after flashing supersu update and there were no problems with supersu working at the first boot after rooting.
[CWM][SCRIPT][4.2.2/4.3] DE-SAMSUNGNIZER Script V4.1 - Clean all unneded Samsung Crap - xda-developers

I think this is much simpler.

I have also used the latest CWMT (6.0.4.3) for d2spr from the clockworkmod website. Since it is an image, I have just put it in a tar file to use with Odin
ClockworkMod ROM Manager - Recoveries

The tar file is also here
CWMT-6.0.4.3-d2spr

So if we flash the stock rooted MK5 update plus the knox removal script we will be completely knox free without any complications?
 
Upvote 0
So if we flash the stock rooted MK5 update plus the knox removal script we will be completely knox free without any complications?

You need to root first to be able to use a custom recovery that can flash KNOX removal script. The bootloader indicates that warranty is invalid in red now. I don't see any complications other than a permanently broken warranty after removing KNOX. I don't know what was that piece-of-garbage doing, there isn't anything missing without it.
 
Upvote 0
You need to root first to be able to use a custom recovery that can flash KNOX removal script. The bootloader indicates that warranty is invalid in red now. I don't see any complications other than a permanently broken warranty after removing KNOX. I don't know what was that piece-of-garbage doing, there isn't anything missing without it.

I'm already rooted. I never flashed the update.
 
Upvote 0

Known Facts About KNOX:

  • Upgrading to newer Samsung firmware MK5 will upgrade the bootloader to KNOX bootloader. this will give an additional 2 lines in download mode about KNOX status.
  • Not possible to downgrade to KNOX-disabled firmwares/bootloaders without tripping the KNOX flag (An attempt sets 0x1) (even though some people state, downgrade is possible when omitting the bootloader file in a firmware package: see http://forum.xda-developers.com/show....php?t=2444671, not confirmed)
  • Even if you flash a KNOX-enabled firmware via Odin (e.g. the latest fw) Knox will be set to 0x1
  • Flashing unsigned or modified images via Odin will set KNOX to 0x1
  • Once the KNOX flag gets set to 0x1 there is no way to set it back (that anyone has found yet anyway!) Samsung stated, resetting the flag is impossible
  • KNOX is mandatory and can not be completely removed
  • Warranty Void is no counter, it is a flag (0,1) it was never seen 0x2 or so
  • Mirroring all partitions from a clean 0x0-Device to a 0x1-Device via JTAG produces an unfunctional device (reversible by restoring the 0x1 partitions on the phone)
  • KNOX bootloader verifies signatures of kernels and recoveries. No custom ones possible without voiding the KNOX warranty
  • If the KNOX warranty void line says 0x1 then you cannot use KNOX software as your device has been flagged as insecure. By this I mean that if your workplace / company supports bring your own device to work for corporate emails etc and they use KNOX to keep security your device will not allow this. You are still able to use future Samsung firmware releases with the KNOX flag 0x1.
  • with the new KNOX bootloader root will work, however rooting will trip the KNOX flag

ROOTING MK5 4.3:
This is not an "official" guide on rooting the Virgin Mobile update to MK5 (Android 4.3)


This is a WIP Guide and will be further improved by discussion within this thread. Group participation is key


I am simply sharing my experience in successfully rooting stock MK5. It is not guaranteed to work for you.

These steps are a result of "dumb luck" and there certainly may be easier and more efficient methods. As of this time there is no flashable pre-rooted versions of MK5 but that doesn't mean that by the time you read this there won't be. So check out that option first and see if it is available since you may find it easier.


Note that prior to these steps, I was running ROOTED MG2

These steps assume that you have successfully update to MK5; if not, there is a separate thread for doing so.


1. Download SuperSU and place on your SD card.

2. Download CWM Recovery and flash with Odin.

3. Boot into recovery and install SuperSU. This puts superuser.apk in the system/app folder.

4. Once you boot up the first time and you try to open a root only app you will get the security alert saying SuperSU has been blocked. Open Application Manager and Force Stop all security software (the one I remember blocking had a key as an icon; can't remember the name).

5. You will also notice that SuperSU is missing from the app drawer. Navigate to system/app with Root Explorer and click on superuser.apk and install it.

6. You will now see SuperSU in the app drawer and you can open it up. Once in SuperSU click on settings and select "Reinstall: Cleanup for reinstallation from Google Play" and once that completes (it should reboot)

7. Upon rebooting, reinstall SuperSU from Google Play.

8. Open SuperSU and it will prompt you to install the binaries. Select the method that doesn't use custom recovery (this may not be necessary but is what I did)

9. Open Titanium Backup (if installed) and see if it achieves root access. If it does, freeze the following apps before rebooting to get rid of the Knox security software:
ContainerAgent.apk
KLMSAgent.apk
KnoxAttestationAgent.apk
KNOXStub.apk

Those are the steps that I took and it worked for me. Good luck!

Well I tried this but it says binaries "There is no SU binary installed, and SuperSU cannot install it." and that I says that I need to manually root it. :/ no go for me. can anyone help me with this?
 
Upvote 0
Well I tried this but it says binaries "There is no SU binary installed, and SuperSU cannot install it." and that I says that I need to manually root it. :/ no go for me. can anyone help me with this?

Try flashing SuperSu 1.8.0 update using philz recovery instead of cwm. That seems to work for those who can't get it to stick with cwm. Like me :)
 
Upvote 0
I have flashed knox remover script right after flashing supersu update and there were no problems with supersu working at the first boot after rooting.
[CWM][SCRIPT][4.2.2/4.3] DE-SAMSUNGNIZER Script V4.1 - Clean all unneded Samsung Crap - xda-developers

I think this is much simpler.

I have also used the latest CWMT (6.0.4.3) for d2spr from the clockworkmod website. Since it is an image, I have just put it in a tar file to use with Odin
ClockworkMod ROM Manager - Recoveries

The tar file is also here
CWMT-6.0.4.3-d2spr

Will this work on phones that upgraded through regular mean like kies or system update on stock rom?
 
Upvote 0
Whenever I try to flash any of the Philz Touch Recovery versions for d2spr in regular CWM it says assert failed: getprop("ro.product.device") == "d2spr" || getprop("ro.build.device") == "d2spr" ||...and repeats that several times then says E: Error in /external_sd/philz_touch_6.0.0.0-d2spr.zip (status 7 ) instalation aborted. Ive tried putting on internal sd external sd tried different versions with same thing every time. Should I flash via Odin instead?
 
Upvote 0
I for got to mention I flashed the mk5 4.3 stock deodexed Rom but still have not achieved root via CWM thats why im trying this method.

Update: Ok guys sorry for any wasted time reading this post. Just got it to flash through Odin. We are successfully rooted on stock mk5 4.3. Thank you guys for all the hard work. TheBritton has helped me tremendously through this process and just wanna give him a big shout out and thank you. The fun now begins.
 
  • Like
Reactions: shamdamdoobily
Upvote 0
I got this awesome phone 3 days ago and well satisfied so far but i want to root wich doesnt seem that hard and well i havent really been on this galaxy s3 all thing root forum and well they made have asked this question before but today i decided to root it ,postive to do it but i wake up an android update to 4.3 and well i did it but my question is this root method posted in this forum safe with this version of android ? Also i pretty much want a stock rom so any problems with the 3g 4g or wifi or messaging or any precautions i should take in mind before i root if possible ?
 
Upvote 0
Status
Not open for further replies.

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones