Database Info

Relocking bootloader

So I want to root my phone only so I can use it with my daydream vr viewer. In order to do that I have to edit the build.prop and I think also some xml file.
My issue is that by unlocking the bootloader you lose widevine l1 so no more netflix HD.
So my question is: Can I unlock, root, edit the files, unroot, relock the bootloader and if I do, will my build.prop remain the same one or is it overwritten when relocking the bootloader? Also does the widevine l1 status come back after relocking?
Thank you in advance

Relocking the bootloader with mods such as root and/or custom recovery TWRP will typically lead to no boot. My understanding, is that the phone needs to be fully stock when locking the bootloader (for the reason stated). Not sure what the result will be from changing build.prop, then removing all other mods (root, custom recovery) and relocking the bootloader. But I'd say it is risky. May lead to no boot, and possibly even resorting to the unbrick tool to get it going again.
Another thing to be aware, is that modifying build.prop may have some undesired side effects. Better to use one of the Magisk modules to get Daydream running, which you can then turn the Magisk module off when not needed (not using Daydream). On my OnePlus 3T, the modified build.prop for some reason caused glitches with the stock camera app (would not take any video) for some reason. I've only played around a little bit with Daydream (and corresponding Daydream enabler Magisk module). I haven't noted any side effect (like I did with the 3T and the camera app). But it's something to at least be aware of.
https://forum.xda-developers.com/mo...agisk-daydream-cardboard-enabler-nfc-t3917601

Correct me if I am wrong, but to use magisk wouldn't I need to be rooted? so again I would not have netflix HD.

You're better off flashing a completely unmodified version of OOS then follow these instructions

poulidis said:
Correct me if I am wrong, but to use magisk wouldn't I need to be rooted? so again I would not have netflix HD.
Click to expand...
Click to collapse
Once you unlock the bootloader, Widevine gets lost permanently. No going back even if you relock. Also Magisk is your root access.

Zocker1304 said:
Once you unlock the boot loader, Widevine gets lost permanently. No going back even if you re lock. Also Magisk is your root access.
Click to expand...
Click to collapse
Please stop spreading lies. Once you unlock boot loader yes you do lose widevine (drops down to l3 so 480p playback) you definitely can get it back by simply flashing another stock zip from oneplus and rebooting and relocking the bootloader. Once done it will restore your widevine. Please do research before you attempt to state something that isn't fact. Also doing the msm download tool will always relock your bootloader and restore widevine back to its original state.

poulidis said:
Correct me if I am wrong, but to use magisk wouldn't I need to be rooted? so again I would not have netflix HD.
Click to expand...
Click to collapse
Magisk is the root method. So, yes, you would need to be rooted (and bootloader unlocked) to use the module. I'm suggesting the module as an alternative to "manually" changing build.prop, not as an alternative to rooting.

To add from my post above here is proof. Before this I was on Omni bootloader unlocked. I noticed TMobile dropped 9.5.9 and I wanted to test it. So I used the msm tool to go back to TMobile and took the ota updates to 9.5.9 now here I am with l1 access and full hd Netflix.

blackknightavalon said:
You're better off flashing a completely unmodified version of OOS then follow these instructions
Click to expand...
Click to collapse
I don't think you are properly understanding what the top poster is trying to do (or asking). He wants to keep(restore) Widevine L1 status (by relocking the bootloader) while still having a modified build.prop (so Daydream VR will work, which it will not on a fully stock 7 Pro).

redpoint73 said:
I don't think you are properly understanding what the top poster is trying to do (or asking). He wants to keep(restore) Widevine L1 status (by relocking the bootloader) while still having a modified build.prop (so Daydream VR will work, which it will not on a fully stock 7 Pro).
Click to expand...
Click to collapse
It won't work as dm verity will kick in and not allow the phone to boot. It checks if anything has been modified and if it has it will flag the phone and make it unbootable

joemossjr said:
It won't work as dm verity will kick in and not allow the phone to boot. It checks if anything has been modified and if it has it will flag the phone and make it unbootable
Click to expand...
Click to collapse
That was basically what I suspected (see Reply #2 above) but thanks for confirming/explaining it.
My reply that you quoted was in response to Reply #5 above, where the person seemed to misunderstand the original question, to be "how do you relock the bootloader" which isn't what was being asked (I was simply explaining the original question).

poulidis said:
So I want to root my phone only so I can use it with my daydream vr viewer. In order to do that I have to edit the build.prop and I think also some xml file.
My issue is that by unlocking the bootloader you lose widevine l1 so no more netflix HD.
So my question is: Can I unlock, root, edit the files, unroot, relock the bootloader and if I do, will my build.prop remain the same one or is it overwritten when relocking the bootloader? Also does the widevine l1 status come back after relocking?
Thank you in advance
Click to expand...
Click to collapse
You should better just flash Magisk through your TWRP and in Magisk Manager "hide" your root access in "Magisk Hide" menu. After that, you need to download and install "MagiskHide Props Config" module in the "Downloads" section and reboot your device.
I don't have Google Services to confirm it, but you can give it a try.

redpoint73 said:
That was basically what I suspected (see Reply #2 above) but thanks for confirming/explaining it.
My reply that you quoted was in response to Reply #5 above, where the person seemed to misunderstand the original question, to be "how do you relock the bootloader" which isn't what was being asked (I was simply explaining the original question).
Click to expand...
Click to collapse
Your fine I didn't mean to quote you lol

Oneplus 7 pro stock root

Hey everyone !
I'm looking for rooting my OP7 pro with Magisk but I know it will go from widevine L1 to L3 (not a big deal for Netflix but banking and password storing apps can be a problem).
So I've got 3 questions, we don't need to wipe the data before or after rooting the device ?
Do you have some problems with apps like keepass, banking (pay with your phone) or others ?
And last, is it possible to install OTAs after rooting the device without any problem (brick, bootloop or wiping all data) ?
I've already found some answers but I wanted to know more to decide if I'll root it, and which way I'll do it.
Thank you !

I've not rooted but from what I've learnt oem unlock will wipe your phone before root. Banking apps can be fooled with magisk modules. It's tricky to flash new updates & some of them results in bootloop.

thraes said:
So I've got 3 questions, we don't need to wipe the data before or after rooting the device ?
Do you have some problems with apps like keepass, banking (pay with your phone) or others ?
And last, is it possible to install OTAs after rooting the device without any problem (brick, bootloop or wiping all data) ?
Click to expand...
Click to collapse
You need to unlock the bootloader in order to root. And the bootloader unlock process will wipe user data, by definition.
Banking apps will vary in what they look for (root, unlocked bootloader, etc.). Many will work as long as you use the Magisk Hide feature to hide root, as the previous reply mentioned. I've seen post regarding a few bank apps, which seem to be able to detect the bootloader is unlocked. So really no way around this (that particular bank app won't work) if you want to stay rooted. You should NOT lock the bootloader on a rooted device (phone will not boot afterwards). Having an unlocked bootloader and root go hand in hand.
I've updated by OTA several times while rooted, and no issues, and data retained. Some folks have had trouble, probably due to the Slot A/B partitioning on the phone. It does make updating with root a bit trickier (as previous response stated), as you need to install TWRP and Magisk root to the slots in a particular way. There is a guide how to do it, which I've followed and it's worked every time.
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
That being said, I always backup any important data to my computer (or other off-phone means, such as cloud) before doing an update. Just in case something does go wrong.

Question Device is not certified

The boot-loader is unlocked on my ROG 5. I had it rooted with magisk till very recently, however, I gave up root during last firmware update. Perhaps it wasn't a good idea! Since then, Google Play has been saying "Device is not certified". (Obviously, I need a certified device for GPay.)
Is it a must to have root & magisk when boot-loader is unlocked to overcome this problem? Thanks.
(I'm worried about re-locking the boot-loader because of potentially losing the ability to unlock it in the future again. So my preference is to leave it unlocked.)

nexusnerdgeek said:
The boot-loader is unlocked on my ROG 5. I had it rooted with magisk till very recently, however, I gave up root during last firmware update. Perhaps it wasn't a good idea! Since then, Google Play has been saying "Device is not certified". (Obviously, I need a certified device for GPay.)
Is it a must to have root & magisk when boot-loader is unlocked to overcome this problem? Thanks.
(I'm worried about re-locking the boot-loader because of potentially losing the ability to unlock it in the future again. So my preference is to leave it unlocked.)
Click to expand...
Click to collapse
Unlocked Bootloaders will always fail SafetyNet.
Magisk, Kdragon module is the only resort here.
Locking Bootloader is also a solution, but a big no - if you plan to root it later.

Thanks JazonX, I've once again gone through the painful process of activating it all. Long story short, things are working again . I've learnt my lesson (to retain root over a firmware update).

I had before unlocked bootloader after i did recovery and locked it , i got certified google play , as i read you have numerous times to unlock the bootloader

More styles for EdgeLighting

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

Question Re-lock bootloader after root?

Hi folks,
I've managed to stumble my way through using pixel flasher to update my P7Pro to the latest fw with root. Only need root so I can record calls, should I lock the bootloader now I'm done?
Also how do I update in future please without having to wipe, use pixel flasher and patch as I've just done?
I like to think I'm quite tech savvy but the guides for the P7Pro have gone over my head :/

Connorsdad said:
Hi folks,
I've managed to stumble my way through using pixel flasher to update my P7Pro to the latest fw with root. Only need root so I can record calls, should I lock the bootloader now I'm done?
Click to expand...
Click to collapse
Not unless you want to brick your device. You need to be completely stock before relocking your bootloader (unless using avbroot, but you should have a deep understanding about how it works beforehand).
Connorsdad said:
Also how do I update in future please without having to wipe, use pixel flasher and patch as I've just done?
Click to expand...
Click to collapse
Pixel Flasher will work fine for updating.

Lughnasadh said:
Not unless you want to brick your device.
Click to expand...
Click to collapse
Huh, learn something new every day I guess...

Lughnasadh said:
Not unless you want to brick your device. You need to be completely stock before relocking your bootloader (unless using avbroot, but you should have a deep understanding about how it works beforehand).
Pixel Flasher will work fine for updating.
Click to expand...
Click to collapse
Awesome, thanks a lot for your reply, much appreciated.

never ever* lock bootloader on google devices. fastboot only works on unlocked bootloader and there is no alternative to fastboot.
* exception

alecxs said:
never ever lock bootloader on google devices. fastboot only works on unlocked bootloader and there is no alternative to fastboot.
Click to expand...
Click to collapse
And you can't flash a factory image to fix a phone on your own when it's soft bricked. It might have to go to a shop for repairs.

Connorsdad said:
Hi folks,
I've managed to stumble my way through using pixel flasher to update my P7Pro to the latest fw with root. Only need root so I can record calls, should I lock the bootloader now I'm done?
Also how do I update in future please without having to wipe, use pixel flasher and patch as I've just done?
I like to think I'm quite tech savvy but the guides for the P7Pro have gone over my head :/
Click to expand...
Click to collapse
AFAIK, relocking the bootloader requires wiping the device -- much like unlocking does -- and if you're unwilling to set everything (including anything on your /sdcard internal storage, not to mention all apps and their settings & system settings) back up from scratch (as any good complete backups require root access), this might not be what you wish to do.
And, if you had managed to successfully relock the bootloader, you could simply run the in-system update (OTA) that would update without wiping -- or even manually applying OTA from the recovery.
But there are hardly any benefits in re-locking the bootloader (after unlocking it) -- even if one was to a paranoid degree of security; which is the only major reason to (I can point you to the discussions that had taken place on it here, if you wish). If you don't want to run into any issues, you could simply run the stock ROM without root and be hardly impacted by it; with the added benefit of having the option to advanced recovery options and/or rooting options open to you in the future if need be...
alecxs said:
never ever lock bootloader on google devices. fastboot only works on unlocked bootloader and there is no alternative to fastboot.
Click to expand...
Click to collapse
*it just occurs to me you meant to never lock bootloader because it limits options; not the risk of hard-bricking the device -- in which I wrote the following with that assumption. I'll leave the following comment as it is still sound advice, but I apologize in advanced that it doesn't quite relate to what you meant...
I mean, I feel doing Google's official Android Flash Tool is a safe enough method; it wouldn't do well if Google's own tool bricked their devices using their tool...at the very least the tool ensures that the stock factory firmware flashed matches the bootloader version and automates the fastboot commands so when re-locking the bootloader, it has the least potential to brick the device...

Exactly. there is no official flash tool from google, that's why I personally won't recommend to keep bootloader locked. If it's bricked with no working recovery mode, not even repair shop can fix it. all you can do is RMA to google get new device. no edl mode or anything else will help, fastboot is the official flashing method.
If you're referring to the "Android Flash Tool" that's no flash tool at all. I haven't tested it, but to me it looks like a WebUSB browser plugin. Reading the requirements it works with adb commands, usb-debugging and fully booted android is required. Therefore cannot unbrick devices.

Doesn't unlocking the bootloader break saftynet so then you have to root to use gpay?

iRhyiku said:
Doesn't unlocking the bootloader break saftynet so then you have to root to use gpay?
Click to expand...
Click to collapse
I'll just chime in here because I have recently unlocked my bootloader but I haven't been able to root it yet and I haven't had any issues with safety net.

Trippyy Doee said:
I'll just chime in here because I have recently unlocked my bootloader but I haven't been able to root it yet and I haven't had any issues with safety net.
Click to expand...
Click to collapse
Interesting, I thought unlocking would break it. I'll have to unlock then for the extra safty!

iRhyiku said:
Interesting, I thought unlocking would break it. I'll have to unlock then for the extra safty!
Click to expand...
Click to collapse
That's of course another aspect. Good point. If you rely on SafetyNet or it's successor Play integrity, do not unlock bootloader. AFAIR the latter one can't be cheated.

simplepinoi177 said:
But there are hardly any benefits in re-locking the bootloader (after unlocking it)
Click to expand...
Click to collapse
There are some benefits like some banking apps, streaming apps and games beginning to work. So it really depends on what is important for the user. I don't like flashing random mods to make apps work on rooted/ bootloader unlocked devices, primarily banking apps.