hello
i have rooted my note 10+ and flashed dr.ketan rom
and there is an app still detecting the root after using magisk hide and i think it checks if the bootloader is unlocked
and i was wondering is it safe if i relock the bootloader
edit:my banking app does work with magisk hide and the SafetyNet check is successful
Re-locking a bootloader will ensure that the device will only boot to OEM signed and provided Android Images.
FYI: For a custom ROM to be used ( with a few exceptions ), the bootloader must remained unlocked.
For the majority of phones if you try and re-lock the bootloader with LinageOS installed you will end up bricking your phone ( might be soft or hard brick depending on the device ).
TxXDRAGONXxT said:
hello
i have rooted my note 10+ and flashed dr.ketan rom
and there is an app still detecting the root after using magisk hide and i think it checks if the bootloader is unlocked
and i was wondering is it safe if i relock the bootloader
edit:my banking app does work with magisk hide and the SafetyNet check is successful
Click to expand...
Click to collapse
Once u unlock bootloader never relock it many people have reported that their devices got permanently damaged after relocking bootloader
I see but is there a way to spoof it for other apps when it tries to read if the oem is unlocked or not
This is the app i am trying to hide the root from
Tawakkalna (Covid-19 KSA) - Apps on Google Play
Saudi official app to request curfew passes and other COVID-19 related services
play.google.com
For any app ( as this is also true for every service center ) it's an ease to detect whether phone's Android got tampered ( even rooted ). No reliable methods exist to bypass such a query, IMO.
Related
I have been root and flash kernel my pixel 3 before, but I want use google pay, so I flash factory img to my pixel 3.
But i use google pay it is still doesn't working. Is cause i root before?
Have you re-locked the bootloader? An unlocked bootloader will cause Google Pay to not work on stock firmware.
JujuYuki said:
Have you re-locked the bootloader? An unlocked bootloader will cause Google Pay to not work on stock firmware.
Click to expand...
Click to collapse
Is it a good practice to relock the bootloader after root? I though it will reenable signature checks and brick the phone?
Pakabidu said:
Is it a good practice to relock the bootloader after root? I though it will reenable signature checks and brick the phone?
Click to expand...
Click to collapse
If you flashed the factory image you're stock and not rooted, right? But yes you shouldn't lock the bootloader again after modifications. You can relock it after flashing factory image from google though if you fon't flash anything else and don't modify it. That's also the only way to get google pay to work without root and Magisk hide.
Also, as long as you don't untick "enable oem unlocking" in developper settings, you can still unlock if it bricks, as long as you have fastboot access. So if you happened to brick by relocking, just unlocking again (and flashing if needed) would solve it anyway.
JujuYuki said:
If you flashed the factory image you're stock and not rooted, right? But yes you shouldn't lock the bootloader again after modifications. You can relock it after flashing factory image from google though if you fon't flash anything else and don't modify it. That's also the only way to get google pay to work without root and Magisk hide.
Also, as long as you don't untick "enable oem unlocking" in developper settings, you can still unlock if it bricks, as long as you have fastboot access. So if you happened to brick by relocking, just unlocking again (and flashing if needed) would solve it anyway.
Click to expand...
Click to collapse
Thanks man, I'm thinking i have to re lock my phone now, or just wait new magisk can hide google pay.
Awesome how google sells a phone that is unlockable and easily rootable, but then blocks a service to the device. Luckily, where I am google pay is not an option, but I sympathize with you all.
Edemilorhea said:
I have been root and flash kernel my pixel 3 before, but I want use google pay, so I flash factory img to my pixel 3.
But i use google pay it is still doesn't working. Is cause i root before?
Click to expand...
Click to collapse
There is a ton of information on the Magisk page about running Google Pay on an unlocked/rooted device. I use it on both a Pixel 3 and Pixel 3 XL. Locking your bootloader is not necessary right now.
https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
this works.
Followed instructions and edited db and rebooted. Works great in Android 10 on Pixel 3. Thanks for this. I was wondering why wouldn't work on my new phone. So dumb to lock this down.
Question in the subject,
It appears the trend is towards not unlocking bootloaders anymore or offering to do it. Aka much more difficult time to root.
On that topic it seems even with magisk some bank apps know a phone has been unlocked
What are your views... will the custom scene just die off due to that trend?
No....HemeBrow not Die[emoji16]!!! Full backup ROM(App/DataApp and other).App Bank you use in PC/Laptop(Mayby Magist 20???)in smartfon...
Wysłane z mojego Y8 przy użyciu Tapatalka
Airbag888 said:
Question in the subject,
It appears the trend is towards not unlocking bootloaders anymore or offering to do it. Aka much more difficult time to root.
On that topic it seems even with magisk some bank apps know a phone has been unlocked
What are your views... will the custom scene just die off due to that trend?
Click to expand...
Click to collapse
Well, buy an international version of a phone from now on if you desire root and live in the US etc. Secondly if you use magisk hide and rename the magisk app in the manager settings banking apps are all fine, also you cannot have anything named magisk in your files example if you rename a file mag instead of magisk it work be found by those apps
toolhas4degrees said:
Well, buy an international version of a phone from now on if you desire root and live in the US etc. Secondly if you use magisk hide and rename the magisk app in the manager settings banking apps are all fine, also you cannot have anything named magisk in your files example if you rename a file mag instead of magisk it work be found by those apps
Click to expand...
Click to collapse
Well I'm not in the US. My current phone (S7E) had an unlockable BL. But it blew the knox switch which could be used by banking apps to figure things out.
I AM using magisk. I tried on a fresh install with magisk hidden from banking apps and the name of magisk itself changed. I also used the core version, no go - 2 banking apps still figured I was rooted.
In fact even with magisk not installed they complained. A 3rd banking app worked though but I need one of the other 2 badly =\
I was looking to upgrade to the Huawei P30 pro.. no way to unlock BL anymore
That's why I'm saying is this dying off??
toolhas4degrees said:
Well, buy an international version of a phone from now on if you desire root and live in the US etc. Secondly if you use magisk hide and rename the magisk app in the manager settings banking apps are all fine, also you cannot have anything named magisk in your files example if you rename a file mag instead of magisk it work be found by those apps
Click to expand...
Click to collapse
seriously, Is that the method they used for detecting root:laugh::laugh:. It seems so primitive.
samsung can oem unlock without needing PC just goto developer options and enable oem unlocking
ineedroot69 said:
samsung can oem unlock without needing PC just goto developer options and enable oem unlocking
Click to expand...
Click to collapse
That is to just enable unlocking not unlock bootloader. My s7edge had that but could not unlock bootloader on us varients
toolhas4degrees said:
That is to just enable unlocking not unlock bootloader. My s7edge had that but could not unlock bootloader on us varients
Click to expand...
Click to collapse
what? that's not the same on my blu phone oem unlock and unlocking bootloader are the same thing ...
ineedroot69 said:
what? that's not the same on my blu phone oem unlock and unlocking bootloader are the same thing ...
Click to expand...
Click to collapse
Really? The OEM unlock switch is to allow to be unlocked via fastboot
Command. OEM unlock, if the bootloader is locked on us varients ex Samsung locks us bootloader the fastboot command will come back in an error
Also I don't believe Blu ships with locked bootloader's since they are less expensive phones and not a big corporation if that is the case.
Every phone I ever owned had to have the bootloader unlocked via fastboot
toolhas4degrees said:
Really? The OEM unlock switch is to allow to be unlocked via fastboot
Command. OEM unlock, if the bootloader is locked on us varients ex Samsung locks us bootloader the fastboot command will come back in an error
Also I don't believe Blu ships with locked bootloader's since they are less expensive phones and not a big corporation if that is the case.
Every phone I ever owned had to have the bootloader unlocked via fastboot
Click to expand...
Click to collapse
On different phones the OEM Unlock switch does different things
Hello,
i have to root my S8 pro now because the whole internal memory is nearly used by apps and system.
Is there a opportunity to root my device without unlocking bootloader?
I found magisk to modify the boot-partition and for example getting root on the device.
But you have to unlock the bootloader to flash the new boot-partition. I also read that unlocking bootloader always means that the whole device is resetted to factory-defaults which means losing all installed apps.
I have about 50 !! banking apps for generating TANs. For these apps, it's not enough to reinstall the app. You also need to reconnect the app (especially the device) to the banking account.
I think the only way to backup the the configured and connected app is to have root on the device, right?
My plan was to root the device without unlocking bootloader, then make a full-backup, unlock bootloader which resetting the deivce, and restore the full-backup.
After this, I un-root my device because the banking-apps check if a device is rooted. My plan is t re-roote the device using magisk only when needed and when no banking app is used, and then un-root it again.
Any idea how to solve my problem?
Regards
UP
Root requires unlocked bootloader.Nice plan but it won't work.
aBetterAndroid. said:
Root requires unlocked bootloader.Nice plan but it won't work.
Click to expand...
Click to collapse
Really?
unlocked bootloader ist neccessary all the time while device is rooted, not only when flashing?
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
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