Hey guys, i'm wondering if it's possible to edit the build.prop so I can enable tethering without root. I don't want to lose Android Pay and i'm trying to keep my phone stock for the time being but I would like to be able to use tethering once in a while. Also, I haven't unlocked the bootloader and am using stock recovery and the phone was bought direct from Google.
Thanks everybody!
Same here. Would love to have unlocked hotspot/tether without root
I don't think there is a way to make the necessary edits to the files that need them without root access.
edgemaster191 said:
Hey guys, i'm wondering if it's possible to edit the build.prop so I can enable tethering without root. I don't want to lose Android Pay and i'm trying to keep my phone stock for the time being but I would like to be able to use tethering once in a while. Also, I haven't unlocked the bootloader and am using stock recovery and the phone was bought direct from Google.
Thanks everybody!
Click to expand...
Click to collapse
Unfortunately, there is no way to edit the build.prop without root access. I
Root. Modify. Unroot. Keep bootloader unlocked and install custom kernel to have access to Android Pay if you need it.
Sent from my Pixel using Tapatalk
According to sd_shadow, modifying build.prop can be done with TWRP and PC (without root).
Referring to this post by sd_shadow here: https://forum.xda-developers.com/showpost.php?p=70490702&postcount=118
Any ideas how?
I'm on 7.1.1, bootloder unlocked, Verizon Pixel. Would like to avoid root if possible. That's the main reason I got this phone, I got tired of the rooting-related BS.
indyzzzz said:
According to sd_shadow, modifying build.prop can be done with TWRP and PC (without root).
Referring to this post by sd_shadow here: https://forum.xda-developers.com/showpost.php?p=70490702&postcount=118
Any ideas how?
I'm on 7.1.1, bootloder unlocked, Verizon Pixel. Would like to avoid root if possible. That's the main reason I got this phone, I got tired of the rooting-related BS.
Click to expand...
Click to collapse
I could be wrong, but I think once you modify that file - root or not - you may run into some of that BS anyway (failed OTA's, etc) since the system will have been modified from stock.
chili81 said:
I could be wrong, but I think once you modify that file - root or not - you may run into some of that BS anyway (failed OTA's, etc) since the system will have been modified from stock.
Click to expand...
Click to collapse
So I guess sd_shadow was referring to root-modify-build-prop-unroot procedure. No way to avoid root.....
Subject is self-explanatory. I have a Pixel and I'm 100% stock because I have apps that check for unlocked bootloader and for root and disable themselves if found (I'm not only talking about Android Pay or Pokémon Go, but also Good Mobile [recently renamed BlackBerry Work], which I use for work) and I remember the suhide method didn't work on our phones last time I checked. Could this work?
You need an unlocked bootloader to flash a new kernel so if the apps you want to use check the bootloader, you're SOL.
I stopped rooting my phones for some time. So I'm not really sure on how things work now. I'll be receiving my 8T(KB2001) tomorrow. I just want to unlock the bootloader before setting up the device so that I can just flash the official twrp(when it comes) without clearing data. I just want to know if the device passes safetynet till I flash twrp and magisk? I use Google pay and other bank apps regularly so it's important for me. Also, generally how long does it take for an unofficial/official stable twrp to be available?
Tl;dr - Can I use Google pay with unlocked bootloader without magisk?
Doubtful
KrishTej said:
I stopped rooting my phones for some time. So I'm not really sure on how things work now. I'll be receiving my 8T(KB2001) tomorrow. I just want to unlock the bootloader before setting up the device so that I can just flash the official twrp(when it comes) without clearing data. I just want to know if the device passes safetynet till I flash twrp and magisk? I use Google pay and other bank apps regularly so it's important for me. Also, generally how long does it take for an unofficial/official stable twrp to be available?
Tl;dr - Can I use Google pay with unlocked bootloader without magisk?
Click to expand...
Click to collapse
About Google Pay, I think you can use Google pay on unlocked bootloader without Magisk, But with Magisk installed and MagiskHide enabled you can definitely use Google Pay without any problem. I have used Google Pay with magisk. And Once i forgot to add Google Pay into magiskhide list but able to use without any problem. So dont worry about GPay.
But there is big catch for other banking apps, they will detect unlocked bootloader and refuse to run which can be bypass 100% using MagiskHide. Been using phonepe, paytm , and other official banking apps ( upi too ) without any problem. ( AFAIK had trouble with Sbi pay only) All others are working fine.
Device will pass safetynet once you enable MagiskHide after installing Magsik Canary. ( by default its off , you need to turn on manually after first run) And new magisk supports with Different App name so apps can not detect Magisk as app.
But biggest disadvantage of unlocking bootloader on Oneplus device is you will lose widevine level 1, it will set to L3 instead of L1 if you unlock bootloader, So basically you will lose HD in netflix,prime and other streaming apps which uses widevine. ( No effect on local hd playing using file,or youtube)
Best luck
It will not pass safety net. I checked that just now before enabling magisk hide and renaming the app. Google Pay will not work with the unlocked bootloader, even without having the magisk manager app installed. Samsung Pay worked fine on my watch with only the bootloader unlocked.
I can also confirm this. I had unlocked the bootloader the day I got my 8T and was surprised to see Google Pay not working. It started working fine after I rooted and hide it in Magisk.
rohanhole said:
About Google Pay, I think you can use Google pay on unlocked bootloader without Magisk, But with Magisk installed and MagiskHide enabled you can definitely use Google Pay without any problem. I have used Google Pay with magisk. And Once i forgot to add Google Pay into magiskhide list but able to use without any problem. So dont worry about GPay.
But there is big catch for other banking apps, they will detect unlocked bootloader and refuse to run which can be bypass 100% using MagiskHide. Been using phonepe, paytm , and other official banking apps ( upi too ) without any problem. ( AFAIK had trouble with Sbi pay only) All others are working fine.
Device will pass safetynet once you enable MagiskHide after installing Magsik Canary. ( by default its off , you need to turn on manually after first run) And new magisk supports with Different App name so apps can not detect Magisk as app.
But biggest disadvantage of unlocking bootloader on Oneplus device is you will lose widevine level 1, it will set to L3 instead of L1 if you unlock bootloader, So basically you will lose HD in netflix,prime and other streaming apps which uses widevine. ( No effect on local hd playing using file,or youtube)
Best luck
Click to expand...
Click to collapse
I know I'll lose widevine L1 but I really don't care about that. I also know that I can use Magiskhide to keep them working but I just wanted to wait till the twrp is available. I was just wondering if I can manage without Magiskhide for some time. But looks like I have root now for them. Thanks for the reply :good:
RLD831 said:
It will not pass safety net. I checked that just now before enabling magisk hide and renaming the app. Google Pay will not work with the unlocked bootloader, even without having the magisk manager app installed. Samsung Pay worked fine on my watch with only the bootloader unlocked.
Click to expand...
Click to collapse
deepuvijay said:
I can also confirm this. I had unlocked the bootloader the day I got my 8T and was surprised to see Google Pay not working. It started working fine after I rooted and hide it in Magisk.
Click to expand...
Click to collapse
Ahh that sucks! Thanks for confirming btw.
I am passing safetynet with magisk root on US KB2005 11.0.1.2KB05AA. I can open Pay without any issues but have not fully set it up yet. If I recall on my last HTC with Root it threw an error immediately when opening. I will give it a shot later today.
MNoisy said:
I am passing safetynet with magisk root on US KB2005 11.0.1.2KB05AA. I can open Pay without any issues but have not fully set it up yet. If I recall on my last HTC with Root it threw an error immediately when opening. I will give it a shot later today.
Click to expand...
Click to collapse
Same, except I have fully set up Google Pay with my accounts and the app opens up and everything seems to be okay. I have not actually attempted to pay using it yet however.
Screenshots for more info.
Sent from my OnePlus8T using XDA Labs
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