It's a tough thing to search for. Google thinks I'm looking to root or unlock my phone.
I've followed the steps in a video thread entitled "[HOW TO] Unbrick, Unroot, Relock Verizon Galaxy S4" successfully. However the padlock icon is unlocked when the device boots up.
Can Odin or similar tool re-lock the bootloader of an ME7 Galaxy S4?
Do I need to PDA back to MDK?
Not concerned with losing files. Just need to return the device to factory stock.
Well first of all you might be a little confused here... the ME7 firmware currently has no way to unlock the bootloader yet so if you somehow found a way please share with us and collect your money
Anyway, you can get back to stock using this guide: http://forum.xda-developers.com/showthread.php?t=2301259
I have a locked brand new s4 if you wanna trade lol
Sent from my SCH-I535 using Tapatalk
b237696 said:
It's a tough thing to search for. Google thinks I'm looking to root or unlock my phone.
I've followed the steps in a video thread entitled "[HOW TO] Unbrick, Unroot, Relock Verizon Galaxy S4" successfully. However the padlock icon is unlocked when the device boots up.
Can Odin or similar tool re-lock the bootloader of an ME7 Galaxy S4?
Do I need to PDA back to MDK?
Not concerned with losing files. Just need to return the device to factory stock.
Click to expand...
Click to collapse
Boot into recovery and clear the cache.
My phone is rooted with xposed framework with Wanam Xposed and I don't have the screen that indicates "custom" and my device shows up as official in the about screen.
I also have taken the recent OTA.
That worked, Craw.
Thank you & goodnight.
I'm looking to update my mom's phone, I honestly don't remember what I did to it in the past. As far as I can tell it's rooted on NC5, with a lock boot loader (I assume although when booting up I see an unlocked lock with the words "custom" underneath it) and knox is 0x0. Does that mean my bootloader is actually unlocked? and am I following this guide (http://forum.xda-developers.com/gal...-to-root-i545vrufnk1-4-4-2-12-1-2014-t2959613) to update to the latest version?
Thanks
You are most likely rooted but for sure your bootloader is still locked. As far as updating, if you don't want to keep root or anything then just odin back to stock and accept an OTA. If you want root then there are other ways to update posted in this forum.
Is there any way to relock the bootloader on exynos s9+? Ive tried reflashing stock via Odin but the bootloader is still unlocked and not allowing me to use android pay etc.
I know knox will be tripped but there's no reason that I can't use android pay with a non rooted phone surely? I've tried the root checker app as well and that shows that I do not have root.
When I check in developer options it says the bootloader is already unlocked and the slider is to the left for the oem unlock option. I have tried to slide it to the right which factory resets the device but then on going into developer options again it still shows as the same status (bootloader already unlocked with oem unlock slider to the left)
What can I do to get my phone properly back to stock?
Thanks
hookguy said:
Is there any way to relock the bootloader on exynos s9+? Ive tried reflashing stock via Odin but the bootloader is still unlocked and not allowing me to use android pay etc.
I know knox will be tripped but there's no reason that I can't use android pay with a non rooted phone surely? I've tried the root checker app as well and that shows that I do not have root.
When I check in developer options it says the bootloader is already unlocked and the slider is to the left for the oem unlock option. I have tried to slide it to the right which factory resets the device but then on going into developer options again it still shows as the same status (bootloader already unlocked with oem unlock slider to the left)
What can I do to get my phone properly back to stock?
Thanks
Click to expand...
Click to collapse
Actually there is a good reason why google pay wouldn't work even if the device isn't rooted. There are Payment/banking (and other apps I am sure) require that the device be secure. With the bootloader unlocked the security on your device is severely weakened.
Did you root the phone at all, flash anything to the phone or do anything to modify it at all (something like this as an example). If there was nothing at all done to the phone other then toggling the oem unlock, then it sounds like flashing the proper firmware to the phone, unticking the oem unlock option and factory resetting the phone should work.
If knox is tripped then there is no reversing that. Google searching also shows this would be a likely cause as to why you can not relock the bootloader.. Once knox is tripped it is irreversible (this is because it is an E-fuse), not even flashing stock will not make it go away.
I think your best bet at this point might actually be to have root and then use Magisk to hide root from the apps you want to use. I'm not sure which apps this will work for but it's probably worth looking into since there may be no going back with your bootloader
Thank you for the help guys. I did suspect that may be the case and I wouldnt be able to relock but it seemed some people were able to.
Will just root with magisk and use magisk hide to make it work. Thanks!
Having searched high and low without finding an answer, I have done a factory reset (uninstalled Magisk root, I did not install TWRP so I did not trip Knox, Odined factory image back to device) which was easy enough, but I cannot find out how to RELOCK the bootloader to original lock so the tablet is pristine. The bootloader is still unlocked after the factory reset and I need to relock it.
So... Any help out there on how does one relock the bootloader on a Tab S6?
Thanks.
Did you try this?
https://www.the***********.com/relock-samsung-galaxy-s10-bootloader-guide/
For the S10, but the principle should be the same - Probably worth a try.
Hi all,
I've recently had KnoxGuard finally removed by Samsung. I had used Secure Folder just before I received the email and the PIN worked absolutely fine without any issues. However, I subsequently received the email and restarted my phone and I could see the "OEM unlocking" option but now Secure Folder won't recognise my PIN.
Is this a freakish coincidence or is the removal of KnoxGuard the cause?
I'm running the latest April patch and I do not see the option "Forgot PIN". Any chance of recovering my Secure Folder area? I've tried the PIN so many times that it took 8 hours to give me the option to try again.
Unlocking the bootloader aka OEM Unlock, will brick Knox chip permanently and apps like samsung pass, samsung wallet, Secure folder will become disabled or wont work anymore.
Jake.S said:
Unlocking the bootloader aka OEM Unlock, will brick Knox chip permanently and apps like samsung pass, samsung wallet, Secure folder will become disabled or wont work anymore.
Click to expand...
Click to collapse
Unlocking the bootloader DOES NOT trip the KNOX at all.
Flashing CUSTOM binaries trips KNOX.
JohnTheFarm3r said:
Unlocking the bootloader DOES NOT trip the KNOX at all.
Flashing CUSTOM binaries trips KNOX.
Click to expand...
Click to collapse
Right.
JohnTheFarm3r said:
Unlocking the bootloader DOES NOT trip the KNOX at all.
Flashing CUSTOM binaries trips KNOX.
Click to expand...
Click to collapse
Wrong it does brick the knox chip, it has even been proven and so does it state clearly by samsung. Since even warranty becomes voided once bootloader aka OEM Unlock is made. If it does not brick knox then explain why knox does not work for thecrater after he did OEM unlock and if he now did it?
But it has happened that when you do bootloader / OEM Unlock then knox chip hasn't reacted to it so status remains 0 instead of going 1. So that is just lucky chance. But by default I have seen pics of people doing this unlock and status has changed to 1 after doing the unlock which means KNOX is bricked/tripped.
So my Knox status is 0x0 with OEM Unlock.
Jake.S said:
Wrong it does brick the knox chip, it has even been proven and so does it state clearly by samsung. Since even warranty becomes voided once bootloader aka OEM Unlock is made. If it does not brick knox then explain why knox does not work for thecrater after he did OEM unlock and if he now did it?
But it has happened that when you do bootloader / OEM Unlock then knox chip hasn't reacted to it so status remains 0 instead of going 1. So that is just lucky chance. But by default I have seen pics of people doing this unlock and status has changed to 1 after doing the unlock which means KNOX is bricked/tripped.
Click to expand...
Click to collapse
C9H13N said:
So my Knox status is 0x0 with OEM Unlock.
Click to expand...
Click to collapse
Like I said it happens by lucky chance that it stays 0x0 but most of times it would go 0x1.
I remembered years ago on Sony Xperia z or something where it would do same bug. When you unlock bootloader it would change status from 0 to 1 stating bootloader has been changed. But when I did it then it showed 0 still so when I re-locked bootloader and sent it on warranty repair they wouldn't see that bootloader has been touched. Since status for it showed 0 when it should show 1.
Jake.S said:
Like I said it happens by lucky chance that it stays 0x0 but most of times it would go 0x1.
I remembered years ago on Sony Xperia z or something where it would do same bug. When you unlock bootloader it would change status from 0 to 1 stating bootloader has been changed. But when I did it then it showed 0 still so when I re-locked bootloader and sent it on warranty repair they wouldn't see that bootloader has been touched. Since status for it showed 0 when it should show 1.
Click to expand...
Click to collapse
I just checked my Note 10+, which is also equipped with Dr's Rom: There, too, the Knox status would be 0x0 - although the entire ROM was flashed, as was the modem etc.
It should be clear to everyone that the guarantee claim is lost with a root anyway. However, if the status shows 0x0 and Samsung refuses to repair the device under warranty (as an example) even though the counter shows no intervention, I would personally protest against it...
Still, I don't think it's a coincidence that both of my cell phones, which are OEM Unlock, are so lucky that they both display 0x0...?!
C9H13N said:
I just checked my Note 10+, which is also equipped with Dr's Rom: There, too, the Knox status would be 0x0 - although the entire ROM was flashed, as was the modem etc.
Still, I don't think it's a coincidence that both of my cell phones, which are OEM Unlock, are so lucky that they both display 0x0...?!
Click to expand...
Click to collapse
May be you are checking with app like Phone Info or similar which showing spoofed status
On download mode you can see correct status.
dr.ketan said:
May be you are checking with app like Phone Info or similar which showing spoofed status
On download mode you can see correct status.
Click to expand...
Click to collapse
I'll check this via Download-Mode.
dr.ketan said:
May be you are checking with app like Phone Info or similar which showing spoofed status
On download mode you can see correct status.
Click to expand...
Click to collapse
You are right.
On the S23U, Warranty Void is 0x1 and on the Note10+ it's only 1.
Jake.S said:
Wrong it does brick the knox chip, it has even been proven and so does it state clearly by samsung. Since even warranty becomes voided once bootloader aka OEM Unlock is made. If it does not brick knox then explain why knox does not work for thecrater after he did OEM unlock and if he now did it?
But it has happened that when you do bootloader / OEM Unlock then knox chip hasn't reacted to it so status remains 0 instead of going 1. So that is just lucky chance. But by default I have seen pics of people doing this unlock and status has changed to 1 after doing the unlock which means KNOX is bricked/tripped.
Click to expand...
Click to collapse
It's NOT WRONG. It's literally how IT IS.
The unlocked bootloader doesn't do ANYTHING to KNOX. Flashing ROMS or ROOTING or flashing any CUSTOM partitions trips Knox.
Sorry to break it to you, but you're not well-informed. Even Samsung states it contrary to your claims.
And that can be even seen in the bootloader menu.
Do your research before posting false information.
JohnTheFarm3r said:
It's NOT WRONG. It's literally how IT IS.
The unlocked bootloader doesn't do ANYTHING to KNOX. Flashing ROMS or ROOTING or flashing any CUSTOM partitions trips Knox.
Sorry to break it to you, but you're not well-informed. Even Samsung states it contrary to your claims.
And that can be even seen in the bootloader menu.
Do your research before posting false information.
Click to expand...
Click to collapse
Yes, as far as you don't flash custom binary, knox won't trip.
dr.ketan said:
Yes, as far as you don't flash custom binary, knox won't trip.
Click to expand...
Click to collapse
Exactly my point. Jake.S seems to be stating otherwise and telling that even just by unlocking the bootloader you trip the KNOX which is completely false, even according to Samsung.
JohnTheFarm3r said:
It's NOT WRONG. It's literally how IT IS.
The unlocked bootloader doesn't do ANYTHING to KNOX. Flashing ROMS or ROOTING or flashing any CUSTOM partitions trips Knox.
Sorry to break it to you, but you're not well-informed. Even Samsung states it contrary to your claims.
And that can be even seen in the bootloader menu.
Do your research before posting false information.
Click to expand...
Click to collapse
I was surprised when he said that the OEM unlock was enough to alert Knox...
Always rooted after an OEM unlock, so I never checked if the Knox status changed before I rooted and enabled OEM...
Thanks for the clarification and input! ( :
As far as I know, OEM unlock by itself will not trip Knox, however, flashing a custom ROM definitely will. It's the whole point of the fuse in the CPU.
Anyway, with regards to Secure Folder, I had to delete and recreate the Secure Folder environment because it was getting ridiculous with a message to wait 24 hours.