G3 or GS3? It's perfectly safe for for the S3I trust XDAm but I want to confirm this is safe. Ive rooted several phone but I usually use the adb method. Now I have a G3 on Lollipop that I havent had any luck rooting and Im nervous about using an APK that has so many warnings on my phone.
Thanks
Tom
I believe this method is now obsolete, it doesn't work on latest firmware for the S3. Not being rude but there are plenty of guides to flash twrp and supersuSorry, could you be more specific? I thought following the OP was flashing TWRP. How do I flash those then?
Towelroot. Sorry, my post was unclear
Did you ever open SuperSU and disable Knox from there? Knox may be conflicting with root accessIt's the strangest thing y'all. My root will come and go in seems like an arbitrary manner. The only reason i noticed is because my quickboot reboot widget would make the screen go blank (hang) from which i could hit the 'return' hardware key to go back to homescreen. I would then confirm by opening any root-needed app (triangle/TB, etc) and get the 'root needed for functionality' message.
In any case - to elaborate on the root coming and going phenomenon.
I came from stock T999 (non LTE) and believe i had an OTA or two under my belt but was running 4.0.1 or 4.1.1 latest! I can be lazy about these things and was happy about my original root method (though i can't remember which method that was) but recently tried to see if OTA method worked when i saw that Tmo was on to my root (settings/about/phone/software update produced message. Turns out the flash counter is responcible for that, as confirmed after Triangle usage).
Then i flashed latest NC2 update - found through samfirmware via ODIN, and after i couldn't find a relatively 'safe' method to root (based on online documentation, reading up on KNOX, my own comfort levels, etc), stumbled on the cf-auto-root and flashed that. So far so good for a couple of days.
Then, after a couple of days, the root was gone as described above. Reflashed auto root, integrated SuperSU into system and ran Aroma Installer full de-bloat. I couldn't find the recommended knox system entries to delete via TB, and assumed they were never included in the auto-root image. But i did download KNOX Disabler just in case. Never used it.
Then my root was gone again after a couple of days and thinking i had nothing to lose i tried to run KNOX Disabler. The app didn't seem to work and looked like it was hanging, but after a reboot the root has returned.
So now the situation is that (and this is mostly trial and error), the root will disappear after some time (i'm paranoically checking it twice a day now, and might establish duration or reboot patterns at some point), at which point i'll go through the knox disabler/hang/reboot/root returned loop.
My situation seems unique as far as wide google and xda search results - and it seems manageable (if annoying) for the moment, but it would be great to understand and resolve the bloody strangeness.
Thanks for listening and any contributions on the matter!
It was probably an old post.. I'm sure it will work, but since it is an old cm build you may need to edit the assert lines to match your bootloader.. I wouldn't go back to cm10 though since we have cm11I didn't look much further than this post but it states that for CM you need to start from ICS. Is there another thread I should check out?