Root [Boost Mobile] KitKat ND8 update

[jdsingle76]

Ok guys, because I love you so much(no homo), and frankly, got tired of sitting on the sidelines watching while guys like @CNexus and @bilgerryan were busting their tails to try and get ND8 figured out, I took the plunge. That

 

[TheBritton]

That's some dedication right there!!
We appreciate you and thanks for keeping us updated!

 

[Shadowsun]

Hey is anyone running the 4.4.2 ota update, a buddy of mine got the update on his sprint sph-L710 samsung galaxy s3 yesterday so i was wondering if boost was going to release it soon.

 

[smith058]

Jdsingle, would it be possible to backtrack out of Knox by doing that method posted by shabby?

How to truly unbrick your SGS3 - Boost SGS3
http://androidforums.com/showthread.php?t=771877


Just a thought and maybe worth a try

 

[jdsingle76]

UPDATE: I was able to get root to stick. This is how I had to do it:
-Flash CWM(I used Philz latest), via Odin, uncheck auto-reboot and F.Reset Time
-When done, pull battery, then boot to recovery
-Wipe cache, dalvik(good habit), then Philz settings/re-root System (SuperSU). It will instruct you to go into playstore and download SuperSU
-Reboot, download SuperSU in playstore. Open SuperSU, it will give you a Knox warning, asking you if you want to disable Knox(I said yes), and profit!

 

[jdsingle76]

Jdsingle, would it be possible to backtrack out of Knox by doing that method posted by shabby?

How to truly unbrick your SGS3 - Boost SGS3
How to truly unbrick your SGS3 - Boost SGS3 - Android Forums


Just a thought and maybe worth a try

Personally, since I've heard of some really bad stuff happening from playing with Knox, I wouldn't even attempt to "backtrack." But it might be worth a try if you have a spare GS3 lying around

 

[wetbiker7]

Thanks JD. You da man!!

 

[HiiiPowers]

UPDATE: I was able to get root to stick. This is how I had to do it:
-Flash CWM(I used Philz latest), via Odin, uncheck auto-reboot and F.Reset Time
-When done, pull battery, then boot to recovery
-Wipe cache, dalvik(good habit), then Philz settings/re-root System (SuperSU). It will instruct you to go into playstore and download SuperSU
-Reboot, download SuperSU in playstore. Open SuperSU, it will give you a Knox warning, asking you if you want to disable Knox(I said yes), and profit!

Your a winner I'll tell you that and brave glad everything went smoothly have you noticed any huge changes between the 4.3 to 4.4 update

 

[munguse]

Yeah my Boost S3 downloaded the update but haven't installed it. Not going to install it because I'm running custom MOAR rom so I either have to revert back to stock and update or just wait for an updated rom from the dev over at XDA. Also don't have time right now while studying for finals.

 

[cwhatever]

Merged the two threads that have the same subject.

 

[jdsingle76]

Yeah my Boost S3 downloaded the update but haven't installed it. Not going to install it because I'm running custom MOAR rom so I either have to revert back to stock and update or just wait for an updated rom from the dev over at XDA. Also don't have time right now while studying for finals.View attachment 70649

I was talking to @TheBritton and this update has only came to Boost/VM users who are on MOAR. Sprint thinks you are on Sprint, and are trying to push your the OTA. Since you are rooted, and have cwm, it will not take. Boost and VM 4.4 has not dropped yet. Two reasons why this is true. First, there's no kernel source code on Samsung's open source website, and two, the updates to Boost and VM always have a different number/letter designator, since they always drop later. And there's been nothing in the news from any sources about it being out yet.

 

[Kreatur3]

I was talking to @TheBritton and this update has only came to Boost/VM users who are on MOAR. Sprint thinks you are on Sprint, and are trying to push your the OTA. Since you are rooted, and have cwm, it will not take. Boost and VM 4.4 has not dropped yet. Two reasons why this is true. First, there's no kernel source code on Samsung's open source website, and two, the updates to Boost and VM always have a different number/letter designator, since they always drop later. And there's been nothing in the news from any sources about it being out yet.

Barebones gets the notification as well but I knew it was because it thinks I'm on sprint. If you Odin the sprint update, I believe you did?, will you still be able to take the Boost version? Not sure why you would or need to but curious.

 

[jdsingle76]

Barebones gets the notification as well but I knew it was because it thinks I'm on sprint. If you Odin the sprint update, I believe you did?, will you still be able to take the Boost version? Not sure why you would or need to but curious.

There is no "Boost version." I did flash the Sprint ND8, yes. As of now, it's the only 4.4.2 OTA out for the s3 that I have seen or know of.

 

[Kreatur3]

There is no "Boost version." I did flash the Sprint ND8, yes. As of now, it's the only 4.4.2 OTA out for the s3 that I have seen or know of.

Sorry for not being clear. I meant when, or if, Boost releases a 4.4.2 update for its variant of the s3.

 

[jdsingle76]

Sorry for not being clear. I meant when, or if, Boost releases a 4.4.2 update for its variant of the s3.

Since I'm rooted and have cwm it wouldn't flash the boost ota, and since I'm on the Sprint version, it may not even offer it. But to answer your question, when it comes out, I will probably flash the tar.

 

[wetbiker7]

Looks like Cnexus and crew have got the Sprint update working properly. After reading the credits, I saw that you are part of that crew. Thanks for your hard work bro.

Will you be updating this thread with a version for Boost or are we gonna need to use the Sprint version?

 

[jdsingle76]

Looks like Cnexus and crew have got the Sprint update working properly. After reading the credits, I saw that you are part of that crew. Thanks for your hard work bro.

Will you be updating this thread with a version for Boost or are we gonna need to use the Sprint version?

Thanks man. It was definitely a collaborative effort. Now that we've "cracked" it, the minute the Boost/VM OTA drops and someone can snag me a tar, I'll build them. I'm running Sprint's right now and it's running smooth. However, the days of updating builds and still hiding from Knox are over I'm afraid.

 

[wetbiker7]

Thanks man. It was definitely a collaborative effort. Now that we've "cracked" it, the minute the Boost/VM OTA drops and someone can snag me a tar, I'll build them. I'm running Sprint's right now and it's running smooth. However, the days of updating builds and still hiding from Knox are over I'm afraid.

Sounds great bro. I know you'll have it ready not long after Boost or VM drops it.

I've been doing some reading and it does seem that Knox is here to stay. Sammy really did a job intertwining it into almost everything. If people are gonna want KitKat then they'll just have to accept that it's part of the package. Kinda sux but it is what it is. After thinking about it for awhile, it doesn't bother me as much. As long as it doesn't affect functionality or performance, I'm cool.

 

[mydian]

No way am I knoxing up my phone just for Kit Kat. I hope someday there is away around it for a kit kat TW rom but for now I'll avoid it and enjoy the freedom of the MG2 boot loader. Thanks for all your hard work though. Looks like this will be my last Samsung phone.

 

[smith058]

Warranty only last for so long after that Knox is meaningless.

It comes down to is will samsung do warranty repairs for hardware issues if the knox is tripped. If they'll still do repairs then who cares.

By the way how long are our phones under warranty?

 

[steelyus1]

Warranty only last for so long after that Knox is meaningless.

It comes down to is will samsung do warranty repairs for hardware issues if the knox is tripped. If they'll still do repairs then who cares.

By the way how long are our phones under warranty?

1 yr warranty

 

[wetbiker7]

Yep. 1 year is it. Even with the bootloader tripped I've still heard of Sammy fixing hardware related issues after Knox has been tripped.

If it was something like CarrierIQ or something like that then I would definitely have a different opinion. Knox is just something that lets Sammy know that the phone has been rooted. Not really a big deal for me. I take full responsibility for my software when I root. If I mess it up, sure I'm going to try and get it fixed but if Sammy doesn't fix it who do I have to blame? Myself. Hardware issues however are a different story and I would fight Sammy over that. If the MB messes up it's not really going to matter because the phone is not going to boot anyways. Kinda hard to tell if Knox has been tripped with a phone that won't boot.

We're very lucky to have an amazing tool with Sammy...... Odin. Thankfully it can fix most software related screw ups. If the software does actually end up getting messed up then there's a very good possibility that the user did not read and follow the correct flashing procedures anyways. That's not Samsung's fault. It's a two way street people. It's not like Sammy has stopped us from rooting or anything. They just want to be able to tell if the phone has been rooted so they know they know that the user has intentionally altered the software.

Just my 2 cents on Knox.

I have an Asus TF300T. Asus requires that you sign up on their website and register before you can download the tool that unlocks your bootloader. It requires the tablet's personal ID # to unlock. After reading up on the tablet weeks beforehand, I still bought it, had the botloader unlocked and was rooted within 30 minutes of being home. So see....... I've already been down this road before in a sense. I still chose to unlock, flash TWRP and root.


EDIT:

I am still going to wait on tripping the flag with TW. I'm already running KitKat with the AOSP ROMs.

 

[wyelkins]

I think I will sit out the Knox Bootloader for a while too. The main downside to me is that it DOES somewhat limit my options in that it prevents flashing an older Bootloader by hard bricking the device. A pretty harsh penalty.

Granted, while I have never really wanted or needed to downgrade my Bootloader in the past, and might not want to in the future, I like having that option. I do lean towards Libertarian values. Lol.

Also, I don't really see any incremental benefit to running a TW Kitkat at the moment. I am happy with the existing MOAR if I want TW and LiquidSmooth (currently) for my Kitkat needs.

If, somehow it turns out that there is some real benefit to ND8, like much better radio support, it might be worth it.

I also agree that my next phone will be a Nexus, but that will happen when my S3 dies or has brickocide committed on it by my stupidity. I hope that is a long time away.

 

[jmatherly411]

Can you flash the ND8 build to a stock, non-rooted MK5 build S3?

 

[mydian]

Warranty only last for so long after that Knox is meaningless.

It comes down to is will samsung do warranty repairs for hardware issues if the knox is tripped. If they'll still do repairs then who cares.

By the way how long are our phones under warranty?

There is a bit more to it than that. I like being able to down grade the firmware and unbrick the phone. I can care less about warranty I have insurance if it came down to it. Samsung is attempting to change the device that I purchased. No thanks I'll pass.