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

Root [Boost Mobile] Can I root my S3 if I've already upgraded to 4.3?

JReesh

Lurker
I have a fairly new Boost Mobile Galaxy S3 that has never been rooted. I updated to 4.3 when it became available. I'd like to root it now (I've never rooted before, but I have a friend that can help out). Is is possible to root it with it being updated to 4.3 or are we still waiting? I do not want to brick my phone.
 
Welcome to the forums by the way! Sticky threads are always a good starting point for reading and research by the way. Any clarification needed on anything, just ask! Again, welcome!
 
Just as a side not, 4.3 has knox, so do some research before you root.
In short knox is a safety measure Samsung has taken, and once thr trigger is tripped there is no going back, and it voids your warranty. I
It does not however harm the phone in any way physically, just triggers a value and lets Samsung or repair people know you have rooted the phone.

I'd recommend doing a research Knox and what is knox.....unless you already have and don't care about knox, then your free to do whatever you wish and can root to your satisfactin :).

And welcome to the forums.
 
I have a question about maybe knox and or the moar rom??
I bought a phone and it already has 3.4 on it. It came with no warranty and I have a 3'rd party warranty that doesn't care about rooting. So I rooted and I saw it tripped the knox, oh well. Everything went great. I made a backup of stock, and I can restore that with no problem. I am using Twrp. i then flashed Moar and it loaded fine. I started to do some setting up and made a backup and rebooted fine. I then did a wipe everything and flashed Wicked sensations and played with it a bit and made a backup of that. I then restored a backup of moar and it stayed on the boot screen for over an hour and I finally backed out. I then tried to restore the Wicked and the same thing. I then restored the stock and all went well and worked. I then reflashed the moar rom from the beginning and re setup everything and it all works great. I can power down and repower up fine. I made a backup and haven't tried to restore but I have a feeling it wont again. When I made the backups I did all 5, boot, cache, data, recovery, system on all the backups I made. Now the stock has the stock bootloader and the roms have another. But they load just fine the first time with that but wont restore and just sit at the boot animation forever till I quit it. Just wondering if anyone has an answer. I went on the xda forums and I looked and can't post in the thread because too new. I guess I will switch to Philz later and give that a shot and should I not backup all 5? Otherwise like the phone and having a blast with this thing.Right now it is running flawlessly on the moar rom, just can't switch back and forth.

Thx all for this great info here!!!! :):):)
 
I have a question about maybe knox and or the moar rom??
I bought a phone and it already has 3.4 on it. It came with no warranty and I have a 3'rd party warranty that doesn't care about rooting. So I rooted and I saw it tripped the knox, oh well. Everything went great. I made a backup of stock, and I can restore that with no problem. I am using Twrp. i then flashed Moar and it loaded fine. I started to do some setting up and made a backup and rebooted fine. I then did a wipe everything and flashed Wicked sensations and played with it a bit and made a backup of that. I then restored a backup of moar and it stayed on the boot screen for over an hour and I finally backed out. I then tried to restore the Wicked and the same thing. I then restored the stock and all went well and worked. I then reflashed the moar rom from the beginning and re setup everything and it all works great. I can power down and repower up fine. I made a backup and haven't tried to restore but I have a feeling it wont again. When I made the backups I did all 5, boot, cache, data, recovery, system on all the backups I made. Now the stock has the stock bootloader and the roms have another. But they load just fine the first time with that but wont restore and just sit at the boot animation forever till I quit it. Just wondering if anyone has an answer. I went on the xda forums and I looked and can't post in the thread because too new. I guess I will switch to Philz later and give that a shot and should I not backup all 5? Otherwise like the phone and having a blast with this thing.Right now it is running flawlessly on the moar rom, just can't switch back and forth.

Thx all for this great info here!!!! :):):)

Basically, Philz is going to be the way to go. I know TWRP actually recommends not backing up the recovery partition, so that you don't upgrade further down the line and then accidentally restore an older version of TWRP when restoring certain Nandroids. Plus, with Philz, you can go back and restore TWRP backups in the Custom Restore settings. Additionally, did you use the SuperSU zip to get rooted? It is designed to counteract Knox.
 
Basically, Philz is going to be the way to go. I know TWRP actually recommends not backing up the recovery partition, so that you don't upgrade further down the line and then accidentally restore an older version of TWRP when restoring certain Nandroids. Plus, with Philz, you can go back and restore TWRP backups in the Custom Restore settings. Additionally, did you use the SuperSU zip to get rooted? It is designed to counteract Knox.

I followed this http://androidforums.com/boost-mobi...30-guide-mk5-wip-rooting-mk5-4-3-newbies.html the way it said. I saw that it tripped that second line in the making. I will try Philz this weekend and let you all know. I also have a ? about the mms fix and don't know where to post that. I have the msl and went into the dialer and there was no info there at all so I filled in what he had a screenshot of and I still can't send any pics? There was no proxy #'s there or anything. Thx for the quick reply!!!
 
I followed this http://androidforums.com/boost-mobi...30-guide-mk5-wip-rooting-mk5-4-3-newbies.html the way it said. I saw that it tripped that second line in the making. I will try Philz this weekend and let you all know. I also have a ? about the mms fix and don't know where to post that. I have the msl and went into the dialer and there was no info there at all so I filled in what he had a screenshot of and I still can't send any pics? There was no proxy #'s there or anything. Thx for the quick reply!!!

If you are on a TW ROM like Wicked or MOAR, go into the phone and type ##72786# on the dialler. It will reboot itself, just let it do its thing for a few minutes and when it is done your PRL and profile should be running properly.
 
If you are on a TW ROM like Wicked or MOAR, go into the phone and type ##72786# on the dialler. It will reboot itself, just let it do its thing for a few minutes and when it is done your PRL and profile should be running properly.

Thx!!!!! That did the trick for sure!:D:) Will try Philz this weekend and see on that?
 
Basically, Philz is going to be the way to go. I know TWRP actually recommends not backing up the recovery partition, so that you don't upgrade further down the line and then accidentally restore an older version of TWRP when restoring certain Nandroids. Plus, with Philz, you can go back and restore TWRP backups in the Custom Restore settings. Additionally, did you use the SuperSU zip to get rooted? It is designed to counteract Knox.

As for the SuperSU, I did but you flash the recovery in odin first and when I finished before flashing SU in the recovery that is when I saw the 2'nd line was at 01.
 
Thx!!!!! That did the trick for sure!:D:) Will try Philz this weekend and see on that?

Philz is literally just a flash away, if you don't like it then TWRP is just another flash away! As for SuperSU, did you open the app once you were booted back into system? You will want to do so and then update the binary. It should also ask if you want it to disable Knox. I use the TWRP/CWM option to update the binary, the manual method never seems to work.
 
Philz is literally just a flash away, if you don't like it then TWRP is just another flash away! As for SuperSU, did you open the app once you were booted back into system? You will want to do so and then update the binary. It should also ask if you want it to disable Knox. I use the TWRP/CWM option to update the binary, the manual method never seems to work.

Actually I had not done that yet, will give it a try!:)
 
Back
Top Bottom