SuperSU said knox disabled?? - Verizon Samsung Galaxy S III

Okay so my phone is running android 4.4.2 stock and i rooted using towel root and then i ran supersu and it said would you like to disable knox i said yes it said knox is now disabled does this mean i can unlock the bootloader or no???

Knox and the bootloader are completely seperate. Once your on 4.4.2 NE1 there is no unlocking the bootloader. Your stuck with it
From my CM11 S3

Related

[Q] Really Weird GS3 thing (No Knox on 4.3)

So I just got a refurb'd gs3 and I checked the apps and it doesn't appear to have Knox, but it's on 4.3? It says it's on build JSS15J.I535VRUCML1 and that the baseband is ML1, but there doesn't appear to be knox on it. Also, when I boot to recovery or whatever, it says Bootloader SWREV: 1 or something like that. Is it safe to assume that it was previously unlocked and I can install a custom rom or something? I was gonna try the standard saferoot at first.
Swagulous said:
So I just got a refurb'd gs3 and I checked the apps and it doesn't appear to have Knox, but it's on 4.3? It says it's on build JSS15J.I535VRUCML1 and that the baseband is ML1, but there doesn't appear to be knox on it. Also, when I boot to recovery or whatever, it says Bootloader SWREV: 1 or something like that. Is it safe to assume that it was previously unlocked and I can install a custom rom or something? I was gonna try the standard saferoot at first.
Click to expand...
Click to collapse
Knox is there and your bootloader is still locked. You have to root with saferoot. Everything you need is here:
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2

Locking bootloader after lollipop factory image install.

I'm running stock 4.4.4 android on my nexus 5 and I want to unlock the bootloader to flash the 5.0 factory image without rooting or anything. Can I lock my bootloader and reset tamper flag after that and keep my warrenty?
Even with an unlocked bootloader you keep warranty....
#stayparanoid
Actually I don't, I checked with my carrier.
You'd need root to do this. If it were KitKat, I could tell you the steps but L is different as you need a permissive kernel to have root so once that is replaced I am unsure if we can unroot using SuperSU
I'd recommend in your case, wait for the OTA
I'm sad I have to wait more.. I was hoping I can install the update and then just lock bootloader Getting the OTA update will probably take forever.

[Q] If I update a rooted device OTA, will I have to run OEM unlock to root again

Hi,
I have an LG Nexus 5 (KTU84P, or "hammerhead") running Android KitKat 4.4.4. It is rooted using Chainfire's AutoRoot for the Nexus 5 for Android 4.4.4, and I have no custom ROM, simply Vanilla Android but with SuperSU. I am looking to update to Android L, version 5, and I have received a notification for the OTA update.
I understand that with OTA updates, your data will not be wiped, but you will lose root access. I have researched ways to keep the root, but they only appear to be for older versions of Android. I understand that I will lose root.
My question is, will I have to run the "oem unlock" (which I understand is the part of the whole rooting process which actually wipes your device), or will I just have to load Chainfire's AutoRoot? If I go through with it, I will use his AutoRoot for hammerhead for Android L, but basically my end goal is to root and update and not lose any data.
Thanks, if you need more info, let me know?
Autoroot will not wipe your data if your bootloader is already unlocked. Only if your bootloader was locked to begin with.
Nope. Once unlocked it stays unlocked unless you lock it yourself
frenziedfemale said:
Autoroot will not wipe your data if your bootloader is already unlocked. Only if your bootloader was locked to begin with.
Click to expand...
Click to collapse
musclehead84 said:
Nope. Once unlocked it stays unlocked unless you lock it yourself
Click to expand...
Click to collapse
Thank you both very much!
Of course with L you can no longer get the OTA if you have custom recovery. Just incase you weren't aware
rootSU said:
Of course with L you can no longer get the OTA if you have custom recovery. Just incase you weren't aware
Click to expand...
Click to collapse
I have updated OTA, and I kept EVERYTHING, even my root apps, but when I open up SuperSU I get a notification explaining that the Su binary is not installed, which is obviously removed when updating. Now, I'm just backing up my data. Another thing I would like to confirm is, if I use Chainfire's Auto Root for the Nexus 5 running Android 5.0, will it run OEM unlock again, and if it does, will I be affected considering my bootloader is already unlocked?
AudaxNovus said:
I have updated OTA, and I kept EVERYTHING, even my root apps, but when I open up SuperSU I get a notification explaining that the Su binary is not installed, which is obviously removed when updating. Now, I'm just backing up my data. Another thing I would like to confirm is, if I use Chainfire's Auto Root for the Nexus 5 running Android 5.0, will it run OEM unlock again, and if it does, will I be affected considering my bootloader is already unlocked?
Click to expand...
Click to collapse
If its unlocked, it can't be unlocked again.
Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.
D3abL3 said:
Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.
Click to expand...
Click to collapse
Odd. Hasn't locked for anyone else afaik
D3abL3 said:
Just a little info, afaik, if you update from KK to L and had an unlocked bootloader ('oem unlock'), like I did, your bootloader will get locked again after update, as it did with me.
So that "if it was unlocked it'll stay unlocked" is not correct.
Click to expand...
Click to collapse
There's a REALLY easy way to test that theory.
Open the factory image archives and check the script. Unless it runs 'fastboot oem lock' it isn't relocking it.
#stayparanoid
Don't you think this makes the trick?
"fastboot flash bootloader bootloader-hammerhead-hhz12d.img"

Weird Build Number not matching for root

I have got a Galaxy S6 device which has got 5.1.1 Lollipop and the build number is COGA (see the attachment screenshot for the full details). But unfortunately, I can't find that build number in PingPong Root. Besides the number seems pretty weird because it's far more different than all the numbers listed there. Now I have 3 questions:
1. Does S6 contain any locked bootloader that I need to unlock in order to root/flash custom rom? How to know if my bootloader is locked or unlocked?
2. How can I root my phone without tripping KNOX counter (PingPong root doesn't support my build number)
3. If there is no way of rooting without tampering the KNOX counter, then tell me which root tutorial should I follow (may be I am ready to trip KNOX)? I am confused about CF Auto Root because one of my friends failed with that and tripped his KNOX counter.
For 5.1.1 there is no rooting without tripping knox at this time.
I've done it the common way: Flashing twrp, flashing a custom kernel (because the Stock kenel will boot loop) and flash SuperSu.

Engineering Bootloader - Fingerprint scanner

I have a quick question regarding rooting my G920F with the engineering bootloader. I am currently on Android 5.1.1 stock unrooted.
I understand the bootloader is 5.0.2 and that the fingerprint scanner won't work because I am on 5.1.1 and the bootloader is 5.0.2.
If after rooting I install a 5.0.2 samsung based rom will the fingerprint scanner come back to life as the bootloader will be 5.0.2 as well as the rom.
Yes with a 5.0.2 Rom the fingerprint will work again.
But keep in mind...wrong thread for asking this question!
So the finger print scanner will come back if i install any 5.0.2 samsung based rom using TWRP
While we're at it - if I install 5.1.1 ROM stock rooted on that 5.0.2 engineering loader, then flash stock bootloader/recovery/kernel, could I, in theory, regain access to the fingerprint scanner while retaining root? I figure I can hide root from Samsung Pay, get V4A and Xposed and be happy lol.
psych0r3bel said:
While we're at it - if I install 5.1.1 ROM stock rooted on that 5.0.2 engineering loader, then flash stock bootloader/recovery/kernel, could I, in theory, regain access to the fingerprint scanner while retaining root? I figure I can hide root from Samsung Pay, get V4A and Xposed and be happy lol.
Click to expand...
Click to collapse
Samsung Pay and Google's version of it are different. Google's version requires no root, Samsung's version requires you to have KNOX 0x0, which you cannot change after you have rooted.
Rekan_ said:
Samsung Pay and Google's version of it are different. Google's version requires no root, Samsung's version requires you to have KNOX 0x0, which you cannot change after you have rooted.
Click to expand...
Click to collapse
I am running 5.1.1 stock (no root). Is it definately correct that if I install the Engineering bootloader and UniKernel then flash a 5.0.2 rom then the fingerprint scanner will come back?
DJGREEN1980 said:
I am running 5.1.1 stock (no root). Is it definately correct that if I install the Engineering bootloader and UniKernel then flash a 5.0.2 rom then the fingerprint scanner will come back?
Click to expand...
Click to collapse
If you are not on the Engineering bootloader now, you cannot downgrade to that bootloader.
Rekan_ said:
If you are not on the Engineering bootloader now, you cannot downgrade to that bootloader.
Click to expand...
Click to collapse
Thanks. So are you saying the method of flashing the engineering bootloader for anyone that has OTA upgraded their S6 to 5.1.1 is no longer working now?
DJGREEN1980 said:
Thanks. So are you saying the method of flashing the engineering bootloader for anyone that has OTA upgraded their S6 to 5.1.1 is no longer working now?
Click to expand...
Click to collapse
Yup, unlucky. :/

Categories

Resources