Hi, a little question. If I closed the bootloader and returned to the stock ROM with no root, will I receive OTA updates again? Also another question, I want to modify some files before I flash the rom like I want to remove samsung emoji and put ios emoji in their place, is it possible?
kingozilla said:
Hi, a little question. If I closed the bootloader and returned to the stock ROM with no root, will I receive OTA updates again?
Click to expand...
Click to collapse
I've heard people say that you do get OTA if you flash stock and re-lock your bootloader but never tested it myself.
kingozilla said:
Also another question, I want to modify some files before I flash the rom like I want to remove samsung emoji and put ios emoji in their place, is it possible?
Click to expand...
Click to collapse
No, any modification will be detected as custom and won't be able to be flashed with a locked bootloader.
You can receive OTA and update normally after locked bootloader
ShaDisNX255 said:
I've heard people say that you do get OTA if you flash stock and re-lock your bootloader but never tested it myself.
No, any modification will be detected as custom and won't be able to be flashed with a locked bootloader.
Click to expand...
Click to collapse
Ok thank you, I downloaded the stock rom and wont return to root in near future, because I strongly want the stability over apps - bank apps and phone, and I want encryption, and not anymore have more time for this. But how can I close the bootloader to receive OTA updates? Does installing it just normally through odin close it?
kingozilla said:
Ok thank you, I downloaded the stock rom and wont return to root in near future, because I strongly want the stability over apps - bank apps and phone, and I want encryption, and not anymore have more time for this. But how can I close the bootloader to receive OTA updates? Does installing it just normally through odin close it?
Click to expand...
Click to collapse
Make sure you are at stock. Boot into unlock mode again, do it the same like unlock, it will lock your bootloader. When stock boot up, enable Developer option, turn off allow OEM unlocking, reboot. Now you are able to receive OTA normally.
Related
Hi!
I'm wanting to unlock the bootloader on my new TF700, but I read this in the bootloader unlocker disclaimer:
...can no longer receive ASUS software updates...
Click to expand...
Click to collapse
Does this mean that I can't use ANY official ASUS updates, even if I want to run the update manually? Or does this just refer to OTA updates? I really want to put Jellybean on here when they release it, so I probably won't unlock the bootloader if I can't update to it manually.
Also, does unlocking the bootloader also run a factory reset and wipe the device?
nothsa said:
Hi!
I'm wanting to unlock the bootloader on my new TF700, but I read this in the bootloader unlocker disclaimer:
Does this mean that I can't use ANY official ASUS updates, even if I want to run the update manually? Or does this just refer to OTA updates? I really want to put Jellybean on here when they release it, so I probably won't unlock the bootloader if I can't update to it manually.
Also, does unlocking the bootloader also run a factory reset and wipe the device?
Click to expand...
Click to collapse
You'll be flashing ROMs, not getting ASUS's updates. A rom for the latest firmware usually takes less than a week to get on the dev section of the forum.
nothsa said:
Hi!
I'm wanting to unlock the bootloader on my new TF700, but I read this in the bootloader unlocker disclaimer:
Does this mean that I can't use ANY official ASUS updates, even if I want to run the update manually? Or does this just refer to OTA updates? I really want to put Jellybean on here when they release it, so I probably won't unlock the bootloader if I can't update to it manually.
Click to expand...
Click to collapse
Only refers to OTA, as far as we currently know -- the bootloader unlock hasn't been available long enough to prove otherwise.
Also, does unlocking the bootloader also run a factory reset and wipe the device?
Click to expand...
Click to collapse
Nope, it only reboots. It will leave your user data intact when performed correctly. Obviously, when the crap goes into the ventilator, global nuclear war might ensue or your cat may just die (if you don't have one, you will receive one from a local asylum a few days before, that's enough emotional attachment to make it hurt).
<Oh, sometimes I'm vile. Sorry! >
Hi XDA-Devvers,
In a topic (http://forum.xda-developers.com/showthread.php?t=1510719) I read about the following:
Nonverbose said:
Root won't stop an ota but an unlocked bootloader will. You can check in your boot screen if its still unlocked or if its relocked.
Click to expand...
Click to collapse
Doesn't that mean that we can root our tablet, lock the bootloader again (fastboot oem lock), install Voodoo OTA RootKeeper and once there's an OTA available, just backup the root with the Voodoo app and install it?
How awesome would that be :laugh:
Since I am not a pro in that kind of stuff: Can anyone confirm this theory might actually work for real?
fastboot oem lock is unavailable once you unlocked the bootloader.
Ah bummer. Can we relock the bootloader yet? IF we were able to relock the bootloader, it would work, wouldn't it?
TomONeill said:
Ah bummer. Can we relock the bootloader yet? IF we were able to relock the bootloader, it would work, wouldn't it?
Click to expand...
Click to collapse
No, as many informations -including bootloader version- are sent to check if a new OTA is available
alx5962 said:
No, as many informations -including bootloader version- are sent to check if a new OTA is available
Click to expand...
Click to collapse
Okay, thank you for replying. This makes the decision to root a little harder since I want to keep getting updates and for that you'll need ClockWork (and the people who are pushing the update to XDA)(Clockwork does have the nandroid backup though, which I want to have when rooting), which doesn't run very stable last time I read (I rooted before, but then I sent my tab back (heat problems) and got a new one. I flashed a beta ROM xd).
I thanked your post
Isn't it enough to have the original Kernel and ROM? Do you really need a locked bootloader to get OTA updates?
Has anyone tested the universal root method? See http://forum.xda-developers.com/showthread.php?t=1886460
As this doesn't effect the Kernel, OTA updates might work if rooting works with this method.
I've not tried it. I've read some people are bricking their tablets with the universal, and since the A700 is basically a brick waiting to happen, I think I'll pass on it for a while.
I didn't know that there was a root workaround found for 183.46.10 so I foolishly updated to 183.46.15. I've had this phone since 4.1.2 so will a factory reset take me back to 4.1.2? Otherwise will RSD Lite help me? (I'm really sorry for being so ignorant about these things and asking questions that I'm sure are dumb)
cschuck320 said:
I didn't know that there was a root workaround found for 183.46.10 so I foolishly updated to 183.46.15. I've had this phone since 4.1.2 so will a factory reset take me back to 4.1.2? Otherwise will RSD Lite help me? (I'm really sorry for being so ignorant about these things and asking questions that I'm sure are dumb)
Click to expand...
Click to collapse
Unless you unlocked your bootloader, you have NO way to go back to a previous version nor can you root. There is no way to unlock the bootloader once you've taken to .15 OTA.
Sorry to be the bearer of bad news, but once you took the .15 OTA, you lost all access to root and unlock the bootloader. There is no going back. Your only hope is if someone discovers a new security flaw that can be exploited to gain root access, but since this is a 2-year-old phone, I wouldn't hold my breath.
iBolski said:
Unless you unlocked your bootloader, you have NO way to go back to a previous version nor can you root. There is no way to unlock the bootloader once you've taken to .15 OTA.
Sorry to be the bearer of bad news, but once you took the .15 OTA, you lost all access to root and unlock the bootloader. There is no going back. Your only hope is if someone discovers a new security flaw that can be exploited to gain root access, but since this is a 2-year-old phone, I wouldn't hold my breath.
Click to expand...
Click to collapse
What if I accidentally updated to 183.46.15 but my bootloader is unlocked? I was fully rooted with unlock on the 4.1.2 bootloader, but wanted to update so I could flash the new CM11 builds, but I too foolishly took the .15 OTA after installing .10. I just can't seem to find a way to roll back to .10 or flash a recovery now...
LogDog2012 said:
What if I accidentally updated to 183.46.15 but my bootloader is unlocked? I was fully rooted with unlock on the 4.1.2 bootloader, but wanted to update so I could flash the new CM11 builds, but I too foolishly took the .15 OTA after installing .10. I just can't seem to find a way to roll back to .10 or flash a recovery now...
Click to expand...
Click to collapse
You're fine. Once unlocked, always unlocked. Just flash root and you're good to go.
The unlocking of the bootloader on this phone is a physical change, not a software change. Basically, something called an efuse was blown. Hence just like with the old fashioned fuses from a long time ago in a house far far away, once they blow, you have to physically take them out and replace them with a new one. In the case of the phone, you can't really do that without putting in an entirely new motherboard. Hence, once unlocked, always unlocked. They can't lock it back up since it was a physical change on the phone itself.
iBolski said:
You're fine. Once unlocked, always unlocked. Just flash root and you're good to go.
The unlocking of the bootloader on this phone is a physical change, not a software change. Basically, something called an efuse was blown. Hence just like with the old fashioned fuses from a long time ago in a house far far away, once they blow, you have to physically take them out and replace them with a new one. In the case of the phone, you can't really do that without putting in an entirely new motherboard. Hence, once unlocked, always unlocked. They can't lock it back up since it was a physical change on the phone itself.
Click to expand...
Click to collapse
That's awesome news. So I should be able to flash a new recovery through ADB?
LogDog2012 said:
That's awesome news. So I should be able to flash a new recovery through ADB?
Click to expand...
Click to collapse
As long as your bootloader is unlocked, yes. Then, you can flash root.
You need to use the correct recovery that is based on the KK bootloader.
Most are using TWRP as their custom recovery. You can get it here:
http://forum.xda-developers.com/showpost.php?p=53245455&postcount=1
Flash that and then boot into recovery and flash the latest SuperSU:
http://download.chainfire.eu/supersu
Is there a way to know if I have boot loader unlocked ?
boot into fastboot, read message displayed on your screen
Hi guys,
first of all, thank you all for your amazing work! Its great to have such nice guys working on android.
I saw a thead in the "rom" section but since im new in the forum i cant ask in the thread there :/
Do i need to unlock the bootloader in order to flash twrp for full root?
What about the OTA updates? I guess i cant updates after i unlocked the bootloader?
I read about the funkyhuwei method but it seems to be quite costly. One time or maybe even per month ok but 1 credit for 10$?? Wow..
Thanks guys!
Yes. You need unlock bootloader to do other things like flashing twrp.
And you can receive ota updates.
unlocked bootloader and warning messages
5[Strogino] said:
Yes. You need unlock bootloader to do other things like flashing twrp.
And you can receive ota updates.
Click to expand...
Click to collapse
Hi, I unlocked my bootloader, but every time I boot I see these messages that my phone has been unlocked and can't be trusted. I understand this is normal, but is there any way to NOT see this warning?
Also, does this affect any encryption, AndroidPay, fingerprint phone lock, security setting,.... basically, what does that mean "phone cannot be trusted"?
mat_919 said:
Hi, I unlocked my bootloader, but every time I boot I see these messages that my phone has been unlocked and can't be trusted. I understand this is normal, but is there any way to NOT see this warning?
Also, does this affect any encryption, AndroidPay, fingerprint phone lock, security setting,.... basically, what does that mean "phone cannot be trusted"?
Click to expand...
Click to collapse
It can't be removed without locking bootloader again.
Not until someone figures out how to flash TWRP without unlocking bootloader, OR flash official firmware but keep recovery untouched.
And it doesn't affect them (afaik anyway, it works great with Magisk and I don't think it hides unlocked bootloader).
Hi, i am looking more styles for EdgeLighting. before, we could use EdgeLighting+ but now its not working on android 12.
there is an app called muviz edge that contains excellent styles but app does not work properly. so i am looking for a better app for replacing edgelighting+ with beautiful styles.
can we install S21 or something else edge lighting app on our A51?
do you have any recommended app?
Funny thing is, your phone already has all the edge lighting effects built in, the only problem is that there is a specific file called floating_feature that's missing one text line that would make all those extra edge lighting effects appear
So to answer your question, to get more styles for edge lighting you need to root your phone and edit the following file:
system/etc/floating_feature.xml
And add the following line inside the features:
<SEC_FLOATING_FEATURE_SYSTEMUI_CONFIG_EDGELIGHTING_FRAME_EFFECT>frame_effect</SEC_FLOATING_FEATURE_SYSTEMUI_CONFIG_EDGELIGHTING_FRAME_EFFECT>
Save, reboot and your phone should now have all the effects available that Samsung enables on their flagship phones.
And before you ask, no, there is no way to do this without root.
Tnx, but with root, secure folder will be disabled. and i cant root my phone.
in android 10 We could install edgelighting+ that installs additional styles. (without root).
so Did EdgeLighting+ somehow edit this file?
mahdi72 said:
Tnx, but with root, secure folder will be disabled. and i cant root my phone.
in android 10 We could install edgelighting+ that installs additional styles. (without root).
so Did EdgeLighting+ somehow edit this file?
Click to expand...
Click to collapse
I have no clue. But as you said, edge lighting+ no longer works so on newer Android versions, rooting is your only choice.
ShaDisNX255 said:
I have no clue. But as you said, edge lighting+ no longer works so on newer Android versions, rooting is your only choice.
Click to expand...
Click to collapse
Can i Edit Stock Rom in Linux (add Floating_Feature, remove apps, add new apps) and flash it in my A51 phone?
Do I need root to install this modified rom?
mahdi72 said:
Can i Edit Stock Rom in Linux (add Floating_Feature, remove apps, add new apps) and flash it in my A51 phone?
Do I need root to install this modified rom?
Click to expand...
Click to collapse
You will need to root, yes. Since you will edit it, it will lose Samsung's trusted signature and will therefore count as a custom ROM
ShaDisNX255 said:
You will need to root, yes. Since you will edit it, it will lose Samsung's trusted signature and will therefore count as a custom ROM
Click to expand...
Click to collapse
As far as I have researched, it does not seem to require root, but we have to open the bootloader or OEM Option in Developer Mode.
People are also talking about a tool called Odin Patched, which can bypass some verifications.
Is it possible to flash only the edited CSC file with this tool? Sorry to take up your time
mahdi72 said:
As far as I have researched, it does not seem to require root, but we have to open the bootloader or OEM Option in Developer Mode.
People are also talking about a tool called Odin Patched, which can bypass some verifications.
Is it possible to flash only the edited CSC file with this tool? Sorry to take up your time
Click to expand...
Click to collapse
Hey no worries, XDA is meant for a place to learn and I'm happy to try and help/educate in any way I can.
Opening the bootloader is step 1 in getting root access. You may think that root is the equivalent of installing Magisk and that's what root is but it's a lot more than that. By installing something custom you've in some way obtained root access by editing your stock ROM.
But anyway, going back to your original question/answer, the patched Odin can only bypass some verifications on Odin's side but it can't bypass the verification that the phone does itself. The patched Odin is mainly for installing U firmware on U1 variants and vice-versa, something that you can't do on the original Odin. It can't really bypass checking the validity of Samsung's signature on stock firmware. Even if it could bypass that check, the phone also checks the firmware it's being installed so it will detect it as a custom fw file
So, long story short, if you edit stock FW with any tool it will break Samsung's trusted signature and both phone and Odin will pick it up as a custom firmware (i.e. custom ROM) and you will only be able to install it by unlocking the bootloader. Flashing anything custom will break/trip Knox and it will be broken forever
Let me know if you have any more questions I can help you with.
ShaDisNX255 said:
Hey no worries, XDA is meant for a place to learn and I'm happy to try and help/educate in any way I can.
Opening the bootloader is step 1 in getting root access. You may think that root is the equivalent of installing Magisk and that's what root is but it's a lot more than that. By installing something custom you've in some way obtained root access by editing your stock ROM.
But anyway, going back to your original question/answer, the patched Odin can only bypass some verifications on Odin's side but it can't bypass the verification that the phone does itself. The patched Odin is mainly for installing U firmware on U1 variants and vice-versa, something that you can't do on the original Odin. It can't really bypass checking the validity of Samsung's signature on stock firmware. Even if it could bypass that check, the phone also checks the firmware it's being installed so it will detect it as a custom fw file
So, long story short, if you edit stock FW with any tool it will break Samsung's trusted signature and both phone and Odin will pick it up as a custom firmware (i.e. custom ROM) and you will only be able to install it by unlocking the bootloader. Flashing anything custom will break/trip Knox and it will be broken forever
Let me know if you have any more questions I can help you with.
Click to expand...
Click to collapse
Thank you, now many things are clear.
I want to know if unlocking the bootloader is worth it?
I have no problem with the warranty, I have the phone for more than 2 years and Samsung has no after sales service in our country. But for me, the use of banking app, Secure Folder, Samsung Pass are very important.
Is there a way to make all these apps work without problems by unlocking the bootloader?
Surely the OTA updates will also fail with this work, right?
can i unlock bootloader, flash edited files and relock bootloader?
mahdi72 said:
But for me, the use of banking app, Secure Folder, Samsung Pass are very important.
Click to expand...
Click to collapse
Some banking apps are harder to trick than others. I have no problems hiding root from my banking app but I've seen others struggle to hide from theirs, can't really comment on it. Secure Folder has a fix in Android 12 so it should be able to be fixed. Samsung Pass is something that still has no fix as far as I know so if you decide to root/blow knox fuse, this will never work again even if you lock your bootloader again. I've made my change to Google Pass which works with root so Samsung Pass isn't important to me anymore.
mahdi72 said:
Surely the OTA updates will also fail with this work, right?
Click to expand...
Click to collapse
This is correct, OTA updates stop working when you unlock your bootloader but if you re-lock your bootloader, you may get OTA updates again.
mahdi72 said:
can i unlock bootloader, flash edited files and relock bootloader?
Click to expand...
Click to collapse
No, this will lock your phone. Once you edit anything with root or install a custom fw (rom) then it will always count as custom for the phone. If you lock your bootloader while you have custom fw installed, your phone will be stuck in download mode telling you that your phone has custom fw and will refuse to boot until you flash stock fw.
Thank you very much for your very detailed explanation
So, for this part, I need Magisk, which probably Hide all banking apps in Iran
ShaDisNX255 said:
Some banking apps are harder to trick than others. I have no problems hiding root from my banking app but I've seen others struggle to hide from theirs, can't really comment on it.
Click to expand...
Click to collapse
According to your explanation, This is my decision: I can unlock the bootloader and flash the modified ROM (I can apply the necessary fixes for Secure Folder and other changes to the ROM (Can i?)). The only thing I miss is the Samsung Pass feature, which I can replace with Google Pass, OTA updates can be ignored and do not have much priority for me.
The only important thing is the banking apps.
When the bootloader is unlocked, is the root status rooted or un-rooted? Because I feel that some banking apps only check root access and have nothing to do with bootloader (At least in Iran).
If the root status has not changed after Unlocking the bootloader (I think the root status changes after installing Magisk or SU) I think that I can do the above steps and reach my goal
mahdi72 said:
This is my decision: I can unlock the bootloader and flash the modified ROM (I can apply the necessary fixes for Secure Folder and other changes to the ROM (Can i?))
Click to expand...
Click to collapse
You can, yeah.
mahdi72 said:
When the bootloader is unlocked, is the root status rooted or un-rooted?
Click to expand...
Click to collapse
With unlock bootloader alone it's still un-rooted
mahdi72 said:
When the bootloader is unlocked, is the root status rooted or un-rooted? Because I feel that some banking apps only check root access and have nothing to do with bootloader (At least in Iran).
If the root status has not changed after Unlocking the bootloader (I think the root status changes after installing Magisk or SU) I think that I can do the above steps and reach my goal
Click to expand...
Click to collapse
This is where it can get a little tricky and depends on each app because it's not a standard. If your banking app checks if your bootloader is unlocked then you pretty much need Magisk to hide your bootloader unlocked. Without Magisk, any app will be able to check that you have an unlocked bootloader
If your bank app checks to see if you have Magisk only then you can certainly avoid having to flash Magisk if you're not going to use it anyway
If your bank apps checks safetynet then you will again need to flash Magisk and flash a patch to pass safetynet tests
Again, it's not a standard so it all depends on the bank app in question. You can certainly try to unlock your bootloader and stay in stock and check if your bank apps detects your unlocked bootloader. Just unlocking bootloader shouldn't blow knox yet.
ShaDisNX255 said:
You can, yeah.
With unlock bootloader alone it's still un-rooted
This is where it can get a little tricky and depends on each app because it's not a standard. If your banking app checks if your bootloader is unlocked then you pretty much need Magisk to hide your bootloader unlocked. Without Magisk, any app will be able to check that you have an unlocked bootloader
If your bank app checks to see if you have Magisk only then you can certainly avoid having to flash Magisk if you're not going to use it anyway
If your bank apps checks safetynet then you will again need to flash Magisk and flash a patch to pass safetynet tests
Again, it's not a standard so it all depends on the bank app in question. You can certainly try to unlock your bootloader and stay in stock and check if your bank apps detects your unlocked bootloader. Just unlocking bootloader shouldn't blow knox yet.
Click to expand...
Click to collapse
thank you so much Now everything became clear to me