hello
please looking for information
if I make adb oem unlock, and later I change my mind and want locked back to factory state, can I lock it myself? How?
Also if i root with magisk, will knox be tripped? Can I then wipe phone and reinstall stock firmware non-rooted and everything will be fine again?
Just wondering, wanna try custom roms and stuff, but want to be able to get phone to factory working state afer all that.. Looking for informations please
maxis123 said:
hello
please looking for information
if I make adb oem unlock,
Click to expand...
Click to collapse
This isn't a thing. There is an OEM Unlocking toggle in Developer Options that can be enabled; once this is done, the bootloader can be unlocked.
maxis123 said:
and later I change my mind and want locked back to factory state, can I lock it myself? How?
Click to expand...
Click to collapse
Yes, you can relock the bootloader, just make sure you flash back to factory firmware. Locking the bootloader on custom firmware can brick your device.
maxis123 said:
Also if i root with magisk, will knox be tripped?
Click to expand...
Click to collapse
Yes. Any custom or modified firmware image will trip Knox. This includes Magisk patches and TWRP.
maxis123 said:
Can I then wipe phone and reinstall stock firmware non-rooted and everything will be fine again?
Click to expand...
Click to collapse
You can re-lock the bootloader as I described above, but once Knox is tripped, it will be tripped forever and cannot be reset.
maxis123 said:
Just wondering, wanna try custom roms and stuff, but want to be able to get phone to factory working state afer all that.. Looking for informations please
Click to expand...
Click to collapse
It's sorta a one-way trip. Although you can flash back to stock and relock the bootloader, Samsung security features won't work if Knox is tripped. This means you won't be able to use Samsung Pay or other apps that depend on Knox.
if by rooting i wil trip knox and later i cant get phone to factory state with knox not tripped , then im afraid that rooting samsung is a no option for me...thanks for replys
if I unlock BL and root, after that is it possible to get device to factory state aagain? with knox not tripped .
Related
Hello everyone,
after I rooted my phone with the saferoot method, the Knox flag stayed 0 but I have the system status set to 'custom'.
Now I want to return the phone for a warranty case and I want to erase all my data and unroot it. I have read all the posts but I don't get a definitive answer for this. Additionally I have changed my dpi and installed wanam which I used to modify the look. This all means that my system files have been modified, so I can't just do a factory reset.
From what I read, I should remove wanam, busybox, supersu, or use the saferoot unroot script, but as I said, my system files are modified and I dont think this would be enough to set the status to official. I also read that I should use a no-wipe rom, but I cant find the specific rom same as my current firmware, and I'm not sure how I should flash it, from stock recovery or else?
so basically, how do i completely return my phone to stock with status official with currently modified system files?
my current AP is N7100XXUEMK9, CP: N7100XXUEMJ9 and CSC: N7100DBTEMK2, this is all just in case someone needs them. can anyone help me? thanks.
ssterjo said:
Hello everyone,
after I rooted my phone with the saferoot method, the Knox flag stayed 0 but I have the system status set to 'custom'.
Now I want to return the phone for a warranty case and I want to erase all my data and unroot it. I have read all the posts but I don't get a definitive answer for this. Additionally I have changed my dpi and installed wanam which I used to modify the look. This all means that my system files have been modified, so I can't just do a factory reset.
From what I read, I should remove wanam, busybox, supersu, or use the saferoot unroot script, but as I said, my system files are modified and I dont think this would be enough to set the status to official. I also read that I should use a no-wipe rom, but I cant find the specific rom same as my current firmware, and I'm not sure how I should flash it, from stock recovery or else?
so basically, how do i completely return my phone to stock with status official with currently modified system files?
my current AP is N7100XXUEMK9, CP: N7100XXUEMJ9 and CSC: N7100DBTEMK2, this is all just in case someone needs them. can anyone help me? thanks.
Click to expand...
Click to collapse
Flash your official firmware with Mobile Odin pro, with clear data cache options checked.
m.b.jikre said:
Flash your official firmware with Mobile Odin pro, with clear data cache options checked.
Click to expand...
Click to collapse
Thanks for the quick reply. Correct me if I'm wrong but wouldn't mobile odin or even odin from PC trigger knox? I've read in many posts that it would trigger it. Also, the firmware would also flash csc and modem, which would probably again, trigger knox. Am I right or wrong?
ssterjo said:
Thanks for the quick reply. Correct me if I'm wrong but wouldn't mobile odin or even odin from PC trigger knox? I've read in many posts that it would trigger it. Also, the firmware would also flash csc and modem, which would probably again, trigger knox. Am I right or wrong?
Click to expand...
Click to collapse
If you're flashing official rom then Knox would not trigger, so don't worry.
m.b.jikre said:
If you're flashing official rom then Knox would not trigger, so don't worry.
Click to expand...
Click to collapse
are you sure? I don't want to be stubborn, but everywhere I read that if you try to flash anything will trigger knox, and I don't want to void the warranty. so is it really safe?
furthermore, even if I do flash with mobile odin, can I just flash the system partition and not the rest? would this be enough to restore the system status?
ssterjo said:
are you sure? I don't want to be stubborn, but everywhere I read that if you try to flash anything will trigger knox, and I don't want to void the warranty. so is it really safe?
furthermore, even if I do flash with mobile odin, can I just flash the system partition and not the rest? would this be enough to restore the system status?
Click to expand...
Click to collapse
Don't worry, take a look at: http://forum.xda-developers.com/showthread.php?t=1915386
Same to that just flash your official ROM with PC odin or mobile odin, without triggering Knox.
After seeing many people ask questions about Knox on a regular basis about what they can or can't do, I have decided to create this thread that will hopefully make things clear for those searching information about Knox on our devices.
So first things first.
What exactly is Knox?
Information about Knox
Knox allows people to use their device on a secure business (work) network. It allows the data which belongs to the business to be encrypted per DoD standards. Once the Knox/warranty bit is tripped, you can no longer use this service because it proves the device has been tampered with. You can imagine how much simpler it would be to manipulate this service without the restrictions Samsung had to enforce in order to protect sensitive data. This is the main reason I believe the Knox bootloader was added and why root access, once gained, is still limited in some cases. There is also claims that a tripped warranty bit means your warranty will be void, but I have not seen any cases where people have been denied warranty. However it is better to play it safe than sorry if you really do care about warranty.
Wikipedia sums it up pretty nicely.
Knox on Wikipedia
Click to expand...
Click to collapse
F.A.Q
Q. I have Knox firmware on my device, can I still root, flash custom roms, and kernels?
A. Yes, yes you can. Procedure is the same as it has always been. If you have questions search the forum or ask in this thread. Your Knox counter may trip doing any of this so continue to next FAQ for info.
Click to expand...
Click to collapse
Q. What will trip my Knox counter?
Flashing custom recovery or kernels will trip Knox counter, so avoid them at all costs if you want or need to keep that counter at 0x0. Some root methods will also trip this counter, keep reading if you want to avoid this.
Click to expand...
Click to collapse
My Knox counter is tripped, how can I reset it?
Once tripped, the counter CANNOT be reset.
Click to expand...
Click to collapse
Q. How can I root and not trip Knox?
We can currently use the TowelRoot method by geohot for 4.3 and 4.4.2. Follow link below to thread. It does NOT work on 4.4.4
TowelRoot
Click to expand...
Click to collapse
Q. How can I downgrade my firmware?
You cannot and Odin will fail at any attempt to do so. Do not try to bypass this and try to downgrade another way, you run a high risk of bricking you device! This applies to any device that has been officially updated from 4.3 and up from OTA, Odin, or Kies. If you must downgrade for any reason, flash an older rom in custom recovery only. That is the only way to downgrade. Knox Bootloader will not and cannot be removed, so learn how to get along with it.
Click to expand...
Click to collapse
Q. How can I avoid bricking my device? I have seen people say flashing will brick anything with Knox bootloader.
Do not flash firmware for other devices. Do that and you will be okay. On some devices you can flash other firmwares, if you have questions about this you can ask in this thread.
Click to expand...
Click to collapse
Q. Will tripping the Knox counter void my warranty?
As I stated earlier, there have been cases of people successfully filing insurance claims on their devices. However if you really care about warranty, you may want to avoid tripping this counter to be on the safe side.
Click to expand...
Click to collapse
Q. I see an odd message when I start up my device and it says something about SEAndroid kernel not enforcing, what is this and how do I fix it?
It is normal, you either flashed a custom kernel or custom rom with modified kernel. Do not let it bother you but if you flash back the stock unmodified kernel it will disappear. There is also the possibility you performed an unsupported root method and your device is bootlooping, if this is the case, then flash back to stock firmware with Odin to fix and use an updated root method like TowelRoot
Click to expand...
Click to collapse
And if you have any questions feel free to ask
Nice work bro. Should answer a lot of questions for folks.
Haters Made Me Famous
Deviant Team Member
Forgot to reserve, but mine! I'll use this in case Sammy changes something in the next version of android
Never know
And if you have any questions feel free to ask
Click to expand...
Click to collapse
Thanks for this post!
After rooting using TowelRoot, should you install SuperSU or some other su?
Sizzlechest said:
After rooting using TowelRoot, should you install SuperSU or some other su?
Click to expand...
Click to collapse
SuperSu from the Play Store
The Sickness said:
SuperSu from the Play Store
Click to expand...
Click to collapse
Thanks! It won't trip Knox, right?
Sizzlechest said:
Thanks! It won't trip Knox, right?
Click to expand...
Click to collapse
Nope, perfectly safe
Sizzlechest said:
Thanks! It won't trip Knox, right?
Click to expand...
Click to collapse
A custom recovery or kernel trips Knox
Good. It prompts you to disable Knox, so I thought that might trip it.
I need help with update
Sorry people, it has been many years that I have been on here. I just got the s4, rooted using the SU method (not towel) and it shows 0x1 for knox.
When I try to go to my software update it says, your devise had been modied and cannot be updated.
please help
It's having root that is keeping you from updating. Not tripping Knox.
I'd download the latest firmware. From sammobile or shinyside's links. And use Odin to flash.
Anyway to flash or odin a custom os with a stock kernel and recovery without tripping knox? Mabey a modified official tar? Just replace system, etc?
lordodin912 said:
Anyway to flash or odin a custom os with a stock kernel and recovery without tripping knox? Mabey a modified official tar? Just replace system, etc?
Click to expand...
Click to collapse
It might be possible but I don't know the procedure. I imagine it must be very unconventional, otherwise we would see it very often
Thanks, SEAndroid kernel not enforcing worried me.
Hmmmmmm wish I were a bit more fluent in this area.....itd be nice if you could just replace/repackage the tar file....then mabey id get off MDL....just read something about repacking tar files for odin and apparently you cant pull and repackage the system without breaking the signature (of the system) therefore odin wont flash....but imma noob in this area. If anyones got any info, please share
noobieneedshelp said:
Sorry people, it has no been many years that I have been on here. I just got the s4, rooted using the SU method (not towel) and it shows 0x1 for knox.
When I try to go to my software update it says, your devise had been modied and cannot be updated.
please help
Click to expand...
Click to collapse
Use this to go back to stock and fix Knox then root again with towelroot method.
http://forum.xda-developers.com/showthread.php?t=2336392
http://forum.xda-developers.com/galaxy-s4-tmobile/general/root-nb4-knox-0x0-t2802185
Thanks for the info!
Just for clarity: What does having a tripped Knox bit mean? Just that the phone has been tampered with and possibly voiding the warranty?
Legioss199 said:
Thanks for the info!
Just for clarity: What does having a tripped Knox bit mean? Just that the phone has been tampered with and possibly voiding the warranty?
Click to expand...
Click to collapse
Yes, and it also means you can no longer use the Knox service.
Any one knows how to re-lock the bootloader of one plus 3???
And
How to remove that screen on boot up after unlocking one plus three??? :/
If you read the screen properly ull see the instructions on the screen itself do everything the same way you unlock the bootloader just instead of oem bootloader unlock type oem bootloader lock ...but make sure you're on stock rom and recovery
zubinvig said:
If you read the screen properly ull see the instructions on the screen itself do everything the same way you unlock the bootloader just instead of oem bootloader unlock type oem bootloader lock ...but make sure you're on stock rom and recovery
Click to expand...
Click to collapse
But then My root access will be wiped??
I want root access and dont want than annoying screen
two questions different answer but I would bet if there is a way to remove nag screen a google search would find it. Keep searching threads
there is no reason to re-lock bootloader, its still under warranty through Oneplus even with unlocked bootloader. but if u really want to
1. fastboot flash stock recovery (fastboot flash recovery recovery.img) (make sure u download the file, its somewhere here on the forums
2. reboot and then reboot to fastboot (fastboot oem lock) (i have never re locked a bootloader so i am not sure if it will rewipe ur device again like unlocking it does)
3. boot to OS and get developer options again and uncheck OEM Unlock (do this last)
i would not recommend re locking since it wont void warranty and seemed like a lot people screwed up their devices relocking it, but they also unchecked the oem unlock before flashing stock recovery, also i am not sure if step 2 is needed, i would just make sure u flash stock recovery 1st before doing anything
HELP
I try to relock the bootloader but in this momento my oneplus 3 is blocked...I cant update with the stock rom...please some help!!! :crying:
zubinvig said:
If you read the screen properly ull see the instructions on the screen itself do everything the same way you unlock the bootloader just instead of oem bootloader unlock type oem bootloader lock ...but make sure you're on stock rom and recovery
Click to expand...
Click to collapse
What happens if i follow same steps with installed FREEDOM OS on my oneplus 3. You said make sure you are in stock OS.
Once i have unlocked the phn my device doesn't get recognised by the pc when i use command" fastboot devices".. Now, i'm unable to flash twrp, plz solve my issue.!!!
Arun Ammineni said:
What happens if i follow same steps with installed FREEDOM OS on my oneplus 3. You said make sure you are in stock OS.
Click to expand...
Click to collapse
ecarchi said:
I try to relock the bootloader but in this momento my oneplus 3 is blocked...I cant update with the stock rom...please some help!!! :crying:
Click to expand...
Click to collapse
What part of be on stock OS is so hard to understand?
If you're not absolutely stock when relocking, you will brick your device.
Then good luck trying to enable OEM Unlocking when not being able to boot.
As someone who messes with their phone, relocking your bootloader is one of the worst possible things you can do.
If not done correctly, it WILL brick your device.
If you want to go back to stock, then surely do, there is absolutely no need to relock your boot loader unless you're selling your device to someone or if you're looking to pass SafetyNet for Android Pay or something.
Also, you cannot have the cake as well as eat it. You need to have an unlocked boot loader for root, exposed, etc. There is no way around this.
Phones previously had to be reverse engineered and exploited to gain root access, now OEMs freely allow unlocking.
kgs1992 said:
What part of be on stock OS is so hard to understand?
If you're not absolutely stock when relocking, you will brick your device.
Then good luck trying to enable OEM Unlocking when not being able to boot.
As someone who messes with their phone, relocking your bootloader is one of the worst possible things you can do.
If not done correctly, it WILL brick your device.
If you want to go back to stock, then surely do, there is absolutely no need to relock your boot loader unless you're selling your device to someone or if you're looking to pass SafetyNet for Android Pay or something.
Also, you cannot have the cake as well as eat it. You need to have an unlocked boot loader for root, exposed, etc. There is no way around this.
Phones previously had to be reverse engineered and exploited to gain root access, now OEMs freely allow unlocking.
Click to expand...
Click to collapse
I hope you can read this. I'm not a noob and I am looking to relock my bootloader because I am going to sell it. The person wants it fully stock so I need to relock the bootloader in order to regain access to official Ota updates.
I need to be on complete stock (stock recovery and rom) right? Would you please kindly point me to where I need to go to download the stock Rom and recovery. There's some TWRP flashable OTA zips on Oneplus forums that restore stock Rom and recovery but I want to be sure that that is enough and that I don't end up bricking my device for something as stupid as this. Any help would greatly be appreciated!
Arthurvben said:
I hope you can read this. I'm not a noob and I am looking to relock my bootloader because I am going to sell it. The person wants it fully stock so I need to relock the bootloader in order to regain access to official Ota updates.
I need to be on complete stock (stock recovery and rom) right? Would you please kindly point me to where I need to go to download the stock Rom and recovery. There's some TWRP flashable OTA zips on Oneplus forums that restore stock Rom and recovery but I want to be sure that that is enough and that I don't end up bricking my device for something as stupid as this. Any help would greatly be appreciated!
Click to expand...
Click to collapse
Fash 3.2.4 FW from here.
Follow all instructions from here (except I would suggest sideloading the StockROM before relocking).
Arthurvben said:
I hope you can read this. I'm not a noob and I am looking to relock my bootloader because I am going to sell it. The person wants it fully stock so I need to relock the bootloader in order to regain access to official Ota updates.
I need to be on complete stock (stock recovery and rom) right? Would you please kindly point me to where I need to go to download the stock Rom and recovery. There's some TWRP flashable OTA zips on Oneplus forums that restore stock Rom and recovery but I want to be sure that that is enough and that I don't end up bricking my device for something as stupid as this. Any help would greatly be appreciated!
Click to expand...
Click to collapse
I followed the same guide posted on OnePlus Forum to re-lock my bootloader. Just follow them, it works.
Here is that link from OnePlus forum.
1. I restored my stock rom backup from TWRP
2. Flashed Stock recovery
3. fastboot oem lock
4. Sideload stock ROM
Done.
I unlocked because stock ROM I felt was much stabler and hassle free. Have rooted and played with custom ROMs enough in my Nexus 5 days. Just too much stress and can end up with non-working features. Might root again in future if I find something compelling in custom ROM.
batmobile_bang said:
I followed the same guide posted on OnePlus Forum to re-lock my bootloader. Just follow them, it works.
Here is that link from OnePlus forum.
1. I restored my stock rom backup from TWRP
2. Flashed Stock recovery
3. fastboot oem lock
4. Sideload stock ROM
Done.
I unlocked because stock ROM I felt was much stabler and hassle free. Have rooted and played with custom ROMs enough in my Nexus 5 days. Just too much stress and can end up with non-working features. Might root again in future if I find something compelling in custom ROM.
Click to expand...
Click to collapse
If you unlock bootloader and root device. Do you still get OTA updates if you stay on stock ROM?
borijess said:
If you unlock bootloader and root device. Do you still get OTA updates if you stay on stock ROM?
Click to expand...
Click to collapse
If you unlock device, you will still be able to apply OTA. If you rooted by modifying the /system partition, OTA will fail, but if thou rooted using systemless method, you can apply OTA.
Iam on stock OOS 4.0.3 and i was plagued by the same error
--adb sideload the complete rom (with locked bootloader)-- method worked for me.
Previously i had unlocked bootloader and was on freedom OOS 2.3 with TWRP and then i realized that stock updates are better.
So i installed stock recovery and and tried to flash Stock Firmware 4.0.3 through sideload command and it failed.
then i installed TWRP and then installed stock OOS 4.0.3 and it installed fine but with some error.
Then i installed stock recovery
So i rebooted it and after long time it was installed but then i started getting dm_verity error and also i was frustated with unlocked bootloader message.
So i locked my boot loader first from fastboot oem lock and then sideloaded the stock 4.0.3 again and it really worked.
So now i am on stock rom and stock recovery and no more dm_verity error or unlocked bootloader msg to wait for 5 secs...
Now iam really loving my Oneplus 3..
I have a question, if i relock the bootloader (assuming i should flash stock recovery and ROM first), will knox security be back to normal? Or that's it, once unlocked, i'll never be able to lets say use Samsung Pay again?
Pupet_Master said:
I have a question, if i relock the bootloader (assuming i should flash stock recovery and ROM first), will knox security be back to normal? Or that's it, once unlocked, i'll never be able to lets say use Samsung Pay again?
Click to expand...
Click to collapse
Once you trip knox you can't get it back and therefore Samsung won't work ever again.
ShaDisNX255 said:
Once you trip knox you can't get it back and therefore Samsung won't work ever again.
Click to expand...
Click to collapse
Thanks m8.
if i flash custom rom and root ...can i back to official rom and lock bootloader again?
yes, check YouTube for how to do it
however, knox is disabled forever and some apps will not work without an enabled knox
w41ru5 said:
yes, check YouTube for how to do it
however, knox is disabled forever and some apps will not work without an enabled knox
Click to expand...
Click to collapse
It doesn't matter if it's on Secure Folder and Samsung Pay... but can I receive updates if I unroot it?
absentsound said:
It doesn't matter if it's on Secure Folder and Samsung Pay... but can I receive updates if I unroot it?
Click to expand...
Click to collapse
yes, OTA will work
and even if it doesn't, you can always download the fw and flash it with Odin
Secure Folder working on rooted devices with a little tweak
the S. Pay is not working at all w/o knox
w41ru5 said:
yes, OTA will work
and even if it doesn't, you can always download the fw and flash it with Odin
Secure Folder working on rooted devices with a little tweak
the S. Pay is not working at all w/o knox
Click to expand...
Click to collapse
Thank you... you helped me a lot with this information...