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
Related
I was on a stock rom with root and use OTA root keeper and took the jellybean ota update. I'm now on 4.1.1 with root, but can't get the bootloader unlocked. Only reason I say the BL isn't unlocked is because every time I flash a OC kernel, I cant change the cpu or when it does allow me to change the cpu, it just goes right back to 1512.
I can flash roms, but it seems as if the whole rom doesn't flash. I tried ez-recovery with ez-unlock and it just says device status unknown and when I click unlock it says it unlocks it but status still says unknown. Anyone done the ota rootkeeper and got the unlocked bootloader back?
I did the OTA rootkeeper then used EZ Unlocker with no issues.
Sent from my SCH-I535 using xda premium
DarkMenace said:
I did the OTA rootkeeper then used EZ Unlocker with no issues.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Not sure how I screwed it up. I odin'd back to stock (route66). Then did root and installed root keeper and backed it up. Then took all.of the ota's until I got to 4.1.1, then restored root, installed ez-recovery and flashed cwm, then installed ez-unlock. Device status says unknown. Did yours say locked/unlocked on yours?
It did untill I used EZ Unlock. Once I used that the unlock icon vanished.
Sent from my SCH-I535 using xda premium
justdhutch said:
I was on a stock rom with root and use OTA root keeper and took the jellybean ota update. I'm now on 4.1.1 with root, but can't get the bootloader unlocked. Only reason I say the BL isn't unlocked is because every time I flash a OC kernel, I cant change the cpu or when it does allow me to change the cpu, it just goes right back to 1512.
I can flash roms, but it seems as if the whole rom doesn't flash. I tried ez-recovery with ez-unlock and it just says device status unknown and when I click unlock it says it unlocks it but status still says unknown. Anyone done the ota rootkeeper and got the unlocked bootloader back?
Click to expand...
Click to collapse
Download version 1.2 of EZ-Unlock from here. The latest version on the market has a bug that leaves the status always saying "unknown".
It sounds to me like your bootloader is unlocked, and the OC issue is with your kernel. If your bootloader was locked, your phone would not boot with a custom kernel, instead you would be greeted with "Unauthorized software detected, bring your phone into Verizon Wireless".
On my I535 I have this is Odin:
Odin Mode
Product Name: SCH I535
Custom Binary Download: NO
Current Binary: Samsung Official
Qualcom Secureboot: Enable
Warrenty Bit: 1
Bootloader AP SWREV: 1
Baseband Version: i535VRUCML1
Can someone tell me if I have KNOX?
And if someone can tell me if there doing a safestrap for I535?
*I did take the Official 4.3 download.*
*I did use the W0lfDroid root method.*
DJBurner said:
On my I535 I have this is Odin:
Odin Mode
Product Name: SCH I535
Custom Binary Download: NO
Current Binary: Samsung Official
Qualcom Secureboot: Enable
Warrenty Bit: 1
Bootloader AP SWREV: 1
Baseband Version: i535VRUCML1
Can someone tell me if I have KNOX?
And if someone can tell me if there doing a safestrap for I535?
*I did take the Official 4.3 download.*
*I did use the W0lfDroid root method.*
Click to expand...
Click to collapse
I think your knox counter was tripped (yes, you have it) and no, there is no safestrap available for this phone model.
If you're on the ml1 base you're stuck with root only. Any attempt to downgrade or flash a custom recovery will result in a softbrick.
Sent from my SCH-I535 using Tapatalk 2
Thank you
BadUsername said:
I think your knox counter was tripped (yes, you have it) and no, there is no safestrap available for this phone model.
If you're on the ml1 base you're stuck with root only. Any attempt to downgrade or flash a custom recovery will result in a softbrick.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Ohh well Its not like i get this phone Verizon I was the Smart person who still has Unlimited data.
BadUsername said:
I think your knox counter was tripped (yes, you have it) and no, there is no safestrap available for this phone model.
If you're on the ml1 base you're stuck with root only. Any attempt to downgrade or flash a custom recovery will result in a softbrick.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can the warranty bit (at least as it's shown in Odin mode) be set or reset from 1 to 0?
TwistedPoet said:
Can the warranty bit (at least as it's shown in Odin mode) be set or reset from 1 to 0?
Click to expand...
Click to collapse
Nope, not the warranty bit, only the flash count.
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Nope, not the warranty bit, only the flash count.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I was afraid of that. I need to send the device back to Verizon but soon as they see that they'll charge me something outrageous. Well, at least I know not to pay for the warranty coverage anymore. Thanks for you quick reply!!!
It started when I tried to install a CM11 update. I did not see that was only for KK BL, then I tried to revert to stock rom(using RSD lite) and install the old version for the JB BL again, but my wifi still not working(or working only when it wants lol).
Anyone could help me?
I tried to flash a lot of different roms, even reset with RSD, but the issue stills. I don't know what more I can do
Thx for the att and sorry for my horrible english...
Carcass.br said:
It started when I tried to install a CM11 update. I did not see that was only for KK BL, then I tried to revert to stock rom(using RSD lite) and install the old version for the JB BL again, but my wifi still not working(or working only when it wants lol).
Anyone could help me?
I tried to flash a lot of different roms, even reset with RSD, but the issue stills. I don't know what more I can do
Thx for the att and sorry for my horrible english...
Click to expand...
Click to collapse
im having the same issue... my step dad said there was a patch somewhere but i think its a patch from verizon thats going to be an ota so... we will lose root
derpyherp said:
im having the same issue... my step dad said there was a patch somewhere but i think its a patch from verizon thats going to be an ota so... we will lose root
Click to expand...
Click to collapse
lose root? your bootloader is not unlocked?
ncsuwolfs said:
lose root? your bootloader is not unlocked?
Click to expand...
Click to collapse
I thought you loose root when you take ota's??
derpyherp said:
I thought you loose root when you take ota's??
Click to expand...
Click to collapse
If you are rooted, the OTA will fail, so you have to flash back to stock before taking OTAs.
If you are locked and you take an OTA, you will lose access to whatever exploit was patched. In the case of going from JB to KK, the original root (Saferoot I believe) won't work. However, Towelroot will work for those that have locked bootloaders.
However, if you are rooted and on the latest official KK, then you can unlock your bootloader and then, no matter what OTA comes out after that, you will still be able to root your phone without the use of an exploit like Towelroot. Instead, you take .zip image of the SU app you are using and flash it in TWRP or CWM recovery. No exploit needed.
Towelroot is only for those that don't have an unlocked bootloader and it's an exploit (a security issue) within the specific version of the Android OS. OTAs patch these as they are released, which means another exploit has to be discovered in order to achieve root for locked bootloaders.
So, right now, if you are not unlocked, you better unlock on the initial KK release because the latest soak test does patch Towelroot and the bootloader exploit. You've been warned.
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"
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