• 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.
Just FYI, that info about the MD4 firmware is way out of date and actually potentially dangerous now that Knox is in play for some users; the failure was due to not modifying the asserts properly to reflect your actual bootloader. Britton, we definitely need to get some of these stickies cleaned up or updated, can you contact the mods. I am worried about the new crop of users who got a good deal for Black Friday/Cyber Monday and are promptly ruining their devices, or at least encountering complicated problems. Maybe a warning in the title about "outdated information" for those stickies not being maintained by the authors, I don't know, or remove them altogether and transfer the relevant, more current posts from within those threads to new threads.

The previous post is a little ironic to me because I just finished posting a thread on XDA designed to clear up a lot of the confusion involving bootloaders, modems, assert lines, and how Knox can come into play. A lot of their users are actually a step behind the VM/Boost users on this forum because we have been dealing with assert lines and bootloaders for a while, and the Sprint users, with their new MK3 bootloader, don't know what to do when they get an "assert failed" message due to the bootloader check.
 
I took the liberty of editing the guide to say MD4 MG2 but I'll see about having the guide itself updated or at least a disclaimer at the top. I've attempted to contact Austrie but I haven't been able to..
 
TheBritton said:
Maybe we can un-sticky it or something as well... I'll get on that today!
Click to expand...

Thanks buddy! I just suspect some of the users who are new to this phone, even if they are experienced with Android in general, will be unintentionally misled since there have been great strides made since June/July when some of the tutorials and guides first came out. It may be blind luck that they stumble onto either a current sticky or an outdated one, as the MG2, MD4, MD7 nomenclature will probably mean nothing to them.
 
What do you guys think of editing this thread to serve as a Guide ONLY for MK5?

http://androidforums.com/virgin-mob...-guide-return-vm-galaxy-s3-stock-md7-mg2.html

I am the OP of this thread and I think since most people do not have MG2 and especially MD7 anymore, we can just remove the information on that altogether to avoid bricks? I'm not really sure if once you root your device and trip the Knox bootloader if you can actually reflash the mK5 firmware to get back to stock?? I assume so?

Also, looking at Austrie's root guide I don't see anything that will potentially brick a device as there is no Odin firmware linked there. So I don't think it needs to be removed maybe just "un-sticked"? I could be wrong though..
 
TheBritton said:
What do you guys think of editing this thread to serve as a Guide ONLY for MK5?

http://androidforums.com/virgin-mob...-guide-return-vm-galaxy-s3-stock-md7-mg2.html

I am the OP of this thread and I think since most people do not have MG2 and especially MD7 anymore, we can just remove the information on that altogether to avoid bricks? I'm not really sure if once you root your device and trip the Knox bootloader if you can actually reflash the mK5 firmware to get back to stock?? I assume so?

Also, looking at Austrie's root guide I don't see anything that will potentially brick a device as there is no Odin firmware linked there. So I don't think it needs to be removed maybe just "un-sticked"? I could be wrong though..
Click to expand...

I just mainly think we need to do everything we can to at least steer people in the right direction, and the stickies are where everyone looks first, for good reason. As far as rooting, your guide should be fine for anyone, MK5 or otherwise, since root is, at its most basic, just a matter of installing custom recovery via Odin and then flashing SuperSU from the new recovery. If a new user comes across the outdated info first, who knows where their subsequent search for more info will lead them. You wouldn't believe some of the stuff I am seeing posted on XDA recently regarding these types of issues. I think part of their problem over there as well is the "elite" or snobby attitude of not wanting to provide help the way it is provided over here, but I think it is having a financial impact on their users because expensive phones are getting bricked because noobs or rookies are being expected to find their own way. I definitely don't want that happening over here.
 
Back to JeebusJones and his problem, I would suggest starting literally from scratch with a fresh install of Philz Touch via Odin and then a flash of SuperSU v. 1.80, and then proceeding to try to install a new ROM. Don't even bother with your backups right now.

P.S. The original post by JeebusJones is exactly what we need to see, don't apologize for the "wall of text." It is frustrating when someone posts or starts a thread with "Help me, but I'm not going to give you any pertinent info, you have to play 20 questions with me and it will be like pulling teeth." None of us will ever refuse to help unless you are downright rude, but we can brainstorm sooner rather than later if we don't have to waste a day or two and a bunch of replies to get to the heart of the problem. Also, thanks JeebusJones for spurring on the housecleaning that Britton just took care of, this forum has been such a huge help to me and I want it to continue to help the new crop of users I am seeing who are getting involved.
 
struckn said:
Back to JeebusJones and his problem, I would suggest starting literally from scratch with a fresh install of Philz Touch via Odin and then a flash of SuperSU v. 1.80, and then proceeding to try to install a new ROM. Don't even bother with your backups right now.
Click to expand...

Sounds good -- I'll give that a try. I ended up doing the entire process again after I posted, so I've got a working phone now, but I haven't restarted it yet to see if it hangs -- and I probably won't until Sunday, just so I have a working phone for the weekend.

Thanks for the suggestion! Though out of curiosity, why is Philz Touch preferred to TWRP?

struckn said:
P.S. The original post by JeebusJones is exactly what we need to see, don't apologize for the "wall of text." It is frustrating when someone posts or starts a thread with "Help me, but I'm not going to give you any pertinent info, you have to play 20 questions with me and it will be like pulling teeth." None of us will ever refuse to help unless you are downright rude, but we can brainstorm sooner rather than later if we don't have to waste a day or two and a bunch of replies to get to the heart of the problem. Also, thanks JeebusJones for spurring on the housecleaning that Britton just took care of, this forum has been such a huge help to me and I want it to continue to help the new crop of users I am seeing who are getting involved.
Click to expand...

Haha, I'm glad my general cluelessness could make a contribution! I'm still mostly a newbie (if that wasn't already abundantly clear), so I feel a bit like a toddler playing with a switchblade when it comes to this stuff. I'll keep the thread updated on my progress as it comes. Thanks again!
 
I was a long time TWRP user until finding Philz Touch, it is just very user friendly, highly customizable, and above all else extremely reliable. Works across all Android builds and also doesn't have issues with TouchWiz or AOSP. Seems like the other recoveries bork something that Philz handles with ease. Keep playing with those switchblades my friend, we will try to make the blade dull as long as you ask in advance and read read read! Good luck.
 
Update: It worked! I flashed Philz through Odin and then flashed the ROM, SuperSU, modem, and wifi with Philz, and I can now reboot without a problem. Thanks for your help! Guess I'm a Philz man now. One weird thing -- after I did the internal storage format, the phone rebooted on its own, so I had to boot into recovery again. And then after flashing the modem, the phone again rebooted on its own. This happened twice, so I don't think it was a matter of me accidentally pressing anything. This did not occur after flashing the other zips, so it's a bit puzzling. It still worked, though, so no harm done.

If I might ask one more question, is there a good, up-to-date guide on how to get CM 10.2 working on a VM GS3? Google gives me a bunch of different threads in various states of out-of-dateness, from what I can tell (my confusion about about the MD4 firmware was a result of reading old threads, for example).

Thanks again!
 
JeebusJones said:
Update: It worked! I flashed Philz through Odin and then flashed the ROM, SuperSU, modem, and wifi with Philz, and I can now reboot without a problem. Thanks for your help! Guess I'm a Philz man now. One weird thing -- after I did the internal storage format, the phone rebooted on its own, so I had to boot into recovery again. And then after flashing the modem, the phone again rebooted on its own. This happened twice, so I don't think it was a matter of me accidentally pressing anything. This did not occur after flashing the other zips, so it's a bit puzzling. It still worked, though, so no harm done.

If I might ask one more question, is there a good, up-to-date guide on how to get CM 10.2 working on a VM GS3? Google gives me a bunch of different threads in various states of out-of-dateness, from what I can tell (my confusion about about the MD4 firmware was a result of reading old threads, for example).

Thanks again!
Click to expand...

Read my sticky tutorial on modifying Sprint ROM's. I actually need to update some things but it is still current enough for your needs. Britton cleaned up the sticky area as well, so all those threads are relevant for one set of needs or another. Glad you're up and running!
 
Great news that this Knox thing can be removed. I just have a few questions;

My phones model number is SGH-I747M, will these instructions work for it?

Is it possible to do this without an SD card? i.e. using the phones internal memory
 
Tabarnak said:
Great news that this Knox thing can be removed. I just have a few questions;

My phones model number is SGH-I747M, will these instructions work for it?

Is it possible to do this without an SD card? i.e. using the phones internal memory
Click to expand...

Knox is actually two parts: the bootloader and the associated apps. The apps can be removed, but once you have been Knoxed up, the bootloader can never, never, never, never, never, never be removed. Not a misconception that you would want to have bite you in the butt later on down the road! As far as phone model, VM/Boost/Sprint are all SPH-L710; for any other designation, our info might be helpful to steer someone in the right direction, but that is about where it ends. What is your carrier that you have that particular designation? There is a subforum for virtually every variant, and there are definitely some things that are not interchangeable, even though the broad designation of SGS3 covers all of us.
 
Tabarnak said:
I'm with Virgin Mobile (Canada)
Click to expand...

Cool, then I *think* our info is going to be pertinent, but truly don't know if anything we can use/flash on VM USA is going to be compatible, even one partition being slightly different can have serious repercussions. I will look into this further, see what I can find. My gut feeling is that you probably don't want to flash anything until there is a solid yes or no answer available (anybody who knows please chime in, I am just making an educated guess here), since I am assuming that phone designation means something the way being on different carriers would mean something.
 
OK, according to the CyanogenMod Wiki page, you are on Bell (I know you said VM Canada, but what I mean is the "linked" carrier, or "umbrella" you fall under), is that correct? Looks like you are associated with d2att, which is AT&T, similar to how we piggyback off of d2spr which is Sprint.

Link here: SGS3FAQ - CyanogenMod

Good new is, Philz Touch is available for d2att!
 
I've also found this blog detailing how to root it to update to 4.3 (which I am on BTW). I tried the automatic CyanogenMod installer and it said my device isn't compatible. That number... d2att, what is it called? Isn't there some app to check it? I remember a similar number when rooting my old nexus.
 
Tabarnak said:
I've also found this blog detailing how to root it to update to 4.3 (which I am on BTW). I tried the automatic CyanogenMod installer and it said my device isn't compatible. That number... d2att, what is it called? Isn't there some app to check it? I remember a similar number when rooting my old nexus.
Click to expand...

For starters, my two cents about one-click or auto methods of doing things. I strongly discourage the use of such things, I think users need to actually "get their hands dirty" when doing important things like rooting their phones, you truly need to know what you just did so that you can work through problems both forwards and backwards. I think the CM Installer is a huge disservice on the part of the Cyanogen team, and I am glad it was pulled from the Play Store. You are really just asking for trouble with things like that. That being said, all I can find for the AT&T version of things is a recommendation to use the CF Auto Root method. Don't get me wrong, ChainFire is an absolute genius, we all rely on his SuperSU zip to accomplish rooting our version, but that is in conjunction with installing a custom recovery (Philz for the win!) first. Unfortunately, the AT&T versions are suffering from a complete lack of current info as far as my searching can find.

For reference:

d2spr = Sprint, which by default applies to VM and Boost in the USA; we all use the designation SPH-L710 (designation is just as important to know as carrier)

d2tmo = T Mobile

d2vzw = Verizon

d2att = AT&T

For a Sprint/VM/Boost user, flashing anything meant for the other versions (let alone the international variants) is going to be poison, they are not compatible, period. Ditto for anyone on the other carriers trying to use files intended for Sprint.
 
Tabarnak said:
So what you're basically saying is I can't do shit.
Click to expand...

Kind of in a nutshell! If you are really brave and want to use the Philz for d2att and then flash SuperSU to see what happens, that is up to you, I am not endorsing or saying it will work, I only know what works for the SPH-L710.
 
As not to beat a dead horse.... Please be patient with me.

My current situation:

I picked up a new VM Samsung Galaxy SIII from BestBuy on 12/19/2013 which only had 4.1 on it. I sadly allowed it to do all firmware/OTA upgrades available before reading all the information on this forum. Thus I have the Knox Bootloader and the Knox filled Stock 4.3 ROM.

My questions:

1. I have read the complete two pages here twice and some other threads regarding the ROM listed in the First Post. I have the Knox Bootloader which isn't removable, it is just a matter of fact. Is this Correct?

2. It is said not to ODIN any ROMs as those will have bootloaders which will Brick the phone. However, in the current first post, there is a step to ODIN the linked Recovery. This use of ODIN for this step is okay as Recoveries do not contain bootloaders? I had a previous Motorola Triumph which had Clockworkorange and i was using a ICS ROM so I am familiar with Recoveries, I just always thought they were a custom bootloader which allowed the flashing of modified ROMS. (kinda like adding the option to boot from CD to install an modified OS)

3. Once the Recovery is installed, referenced in my question number 2, it is possible to flash the Un-Knoxed ROM and become Rooted?

4. Flashing the Un-Knoxed ROM doesn't remove KNOX, it just ignores that part of the KNOX Bootloader. Is this statement correct? (I say that because from what I gather KNOX is a two part system: Bootloader and Supported KNOX Enabled ROM. Pretty much like the SecureBOOT EFI and Windows 8.) Rooting at this point doesn't flip the KNOX flag due to the ROM not having the ability to talk to the KNOX Bootloader.

Thank you to anyone who responds to my questions. (Yes I did read the FAQ on KNOX: http://androidforums.com/virgin-mob...t/807185-guide-q-myths-truths-about-knox.html )
 
vsanch24 said:
As not to beat a dead horse.... Please be patient with me.

My current situation:

I picked up a new VM Samsung Galaxy SIII from BestBuy on 12/19/2013 which only had 4.1 on it. I sadly allowed it to do all firmware/OTA upgrades available before reading all the information on this forum. Thus I have the Knox Bootloader and the Knox filled Stock 4.3 ROM.

My questions:

1. I have read the complete two pages here twice and some other threads regarding the ROM listed in the First Post. I have the Knox Bootloader which isn't removable, it is just a matter of fact. Is this Correct?

2. It is said not to ODIN any ROMs as those will have bootloaders which will Brick the phone. However, in the current first post, there is a step to ODIN the linked Recovery. This use of ODIN for this step is okay as Recoveries do not contain bootloaders? I had a previous Motorola Triumph which had Clockworkorange and i was using a ICS ROM so I am familiar with Recoveries, I just always thought they were a custom bootloader which allowed the flashing of modified ROMS. (kinda like adding the option to boot from CD to install an modified OS)

3. Once the Recovery is installed, referenced in my question number 2, it is possible to flash the Un-Knoxed ROM and become Rooted?

4. Flashing the Un-Knoxed ROM doesn't remove KNOX, it just ignores that part of the KNOX Bootloader. Is this statement correct? (I say that because from what I gather KNOX is a two part system: Bootloader and Supported KNOX Enabled ROM. Pretty much like the SecureBOOT EFI and Windows 8.) Rooting at this point doesn't flip the KNOX flag due to the ROM not having the ability to talk to the KNOX Bootloader.

Thank you to anyone who responds to my questions. (Yes I did read the FAQ on KNOX: http://androidforums.com/virgin-mob...t/807185-guide-q-myths-truths-about-knox.html )
Click to expand...

Answers :)

1. One does not simply remove the Knox Bootloader.

2. A custom recovery only contains a "recovery.img" which is why its OK to use Odin to get a recovery on the phone. Do not use Odin for anything else though as there is a chance you can brick the phone. You can flash any custom ROM over the custom recovery as long as it doesn't have a custom bootloader most don't so don't worry about it. I suggest *Philz Recovery BTW ;). USE ODIN FOR RECOVERY AND RECOVERY ONLY.

3. Yes! I unfortunately I took the OTA as well and was able to root and I'm currently running **CM11! Like I said in #1 though you will still have the Knox Bootloader.

4. When you flash the unknoxed version (I suggest deodexed if your into customizing the ***stock ROM a lot) you WILL trip the Knox Bootloader not to fret though because you will have already tripped it by using Odin to get your custom recovery at this point and you will still have the Knox Bootloader. The ROM will not have the Knox apps installed.

Hope this helps! I updated via OTA as well so if you have any questions I can help you along the way seeing that we both GOT KNOXED UP!

* Link to Philz Recovery Thread by jdsingle76
** Link to CM11 Thread by struckn
*** Link to Stock 4.3 w/out Knox which also has the MK5 modem and WiFi fix by jdsingle76 and
TheBritton
 
Status
Not open for further replies.
Back
Top Bottom