Develop Bugs

SafetyNet still tripped after RUU

I ran the latest RUU to update my US unlocked HTC 10 to 2.41.617.3. I was hoping that it would fix it so I could pass the SafetyNet but even right after a wipe, data format, clean install and no root, the safetycheck test still comes back with CTS profile match: false. Am I doing something wrong here?

ray985 said:
I ran the latest RUU to update my US unlocked HTC 10 to 2.41.617.3. I was hoping that it would fix it so I could pass the SafetyNet but even right after a wipe, data format, clean install and no root, the safetycheck test still comes back with CTS profile match: false. Am I doing something wrong here?
Click to expand...
Click to collapse
The only other thing I can think of that would trip it is an unlocked bootloader.
Other than that, SN would **** up.
My advice is to just install Magisk and enable Magisk hide to pass SafetyNet.

Ariac Konrel said:
The only other thing I can think of that would trip it is an unlocked bootloader.
Other than that, SN would **** up.
My advice is to just install Magisk and enable Magisk hide to pass SafetyNet.
Click to expand...
Click to collapse
Thanks. I tried using Magisk and Magisk hide but unfortunately they don't work at bypass SafetyNet either for me.

ray985 said:
Thanks. I tried using Magisk and Magisk hide but unfortunately they don't work at bypass SafetyNet either for me.
Click to expand...
Click to collapse
If your bootloader is unlocked, it will fail. Install any of the current custom kernels on the forum, they all have the bootloader fix to allow it to pass safetynet. You may even be able to relock your bootloader via sunshine.

ray985 said:
Thanks. I tried using Magisk and Magisk hide but unfortunately they don't work at bypass SafetyNet either for me.
Click to expand...
Click to collapse
aer0zer0 said:
If your bootloader is unlocked, it will fail. Install any of the current custom kernels on the forum, they all have the bootloader fix to allow it to pass safetynet. You may even be able to relock your bootloader via sunshine.
Click to expand...
Click to collapse
That's what I did on my WWE variant. I bought and ran SunShine to set my device S-OFF/locked. Since then it passes SafetyNet on my end.
As it's behaviour is the same as S-OFF/unlocked it even comes in handy as soon as one's going to sell it. In such case one could easily RUU back to stock an set the secureflag back to S-ON afterwards. Renders the device in a state that's looking like you never touched it at all.
Sent from my htc_pmeuhl using XDA Labs

5m4r7ph0n36uru said:
That's what I did on my WWE variant. I bought and ran SunShine to set my device S-OFF/locked. Since then it passes SafetyNet on my end.
As it's behaviour is the same as S-OFF/unlocked it even comes in handy as soon as one's going to sell it. In such case one could easily RUU back to stock an set the secureflag back to S-ON afterwards. Renders the device in a state that's looking like you never touched it at all.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
i was one of the first to mail in, so mine is set to unlocked on vzw by default. I haven't had any need to change it though.

aer0zer0 said:
If your bootloader is unlocked, it will fail. Install any of the current custom kernels on the forum, they all have the bootloader fix to allow it to pass safetynet. You may even be able to relock your bootloader via sunshine.
Click to expand...
Click to collapse
Thanks, I'll play around with some of the custom kernels and see if that fixes it.

Is there a way to root my Mi 6 without unlocking the bootloader?

Good day guys,
Today I received my Mi 6. Friends told me Xiaomis usually come with an option to enable root, but I can't find it here. Can anyone help me?

I think you need to install the Developers Rom and there you have an option to enable root.

Ammmm no, you can't, at least you discover a zero-day exploit with execution code and bla bla bla.
For Root, you need mod boot/system image in the best case, or flash a tool like supersu to make the changes in fly... so you need a unlocked bootloader or custom recovery and flashing custom recovery need a unlocked bootloader.

Theliels said:
Ammmm no, you can't, at least you discover a zero-day exploit with execution code and bla bla bla.
For Root, you need mod boot/system image in the best case, or flash a tool like supersu to make the changes in fly... so you need a unlocked bootloader or custom recovery and flashing custom recovery need a unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the reply, I guess i'm requesting the bootloader unlock to Xiaomi then.

Theliels said:
Ammmm no, you can't, at least you discover a zero-day exploit with execution code and bla bla bla.
For Root, you need mod boot/system image in the best case, or flash a tool like supersu to make the changes in fly... so you need a unlocked bootloader or custom recovery and flashing custom recovery need a unlocked bootloader.
Click to expand...
Click to collapse
what about install TWPR (still locked) then root it? is it possible?

mennas said:
what about install TWPR (still locked) then root it? is it possible?
Click to expand...
Click to collapse
Are you kidding?
No.
When boot loader is locked only code signed by xiaomi will run.
So twrp will just not bootup.
Also fastboot is only enabled on the phone when boot loader is unlocked so you'd have a hell of a time flashing it
And then youd likely softbrick the phone with no recovery to flash a ROM so maybe even hardbricked...
Don't try.
Just unlock.

Dobsgw said:
Are you kidding?
No.
When boot loader is locked only code signed by xiaomi will run.
So twrp will just not bootup.
Also fastboot is only enabled on the phone when boot loader is unlocked so you'd have a hell of a time flashing it
And then youd likely softbrick the phone with no recovery to flash a ROM so maybe even hardbricked...
Don't try.
Just unlock.
Click to expand...
Click to collapse
I don't know if this applies to Xiaomi and if it works on more recent versions of Android but on Xperia Z3, installing TWRP with locked bootloader was actually possible I did it myself, and hundreds of others has done it to (you couldn't change to a non-stock ROM, without unlocking the bootloader of course, but that's a different story)
Obviosly that would need a newer exploit in order to push TWRP.
But of course Google or Xiaomi may had added additional protections to the bootloader since then.
(with this being said, you probably need to be quite experienced to start looking into that kind of stuff)

-Zteam- said:
I don't know if this applies to Xiaomi and if it works on more recent versions of Android but on Xperia Z3, installing TWRP with locked bootloader was actually possible I did it myself, and hundreds of others has done it to (you couldn't change to a non-stock ROM, without unlocking the bootloader of course, but that's a different story)
Obviosly that would need a newer exploit in order to push TWRP.
But of course Google or Xiaomi may had added additional protections to the bootloader since then.
(with this being said, you probably need to be quite experienced to start looking into that kind of stuff)
Click to expand...
Click to collapse
You'll notice on newer xperia phones that's jot possible
You have to unlock.
They wised up and patched the KitKat exploit (although one was found in the 575 kernel)
So yeah potentially it would be possible to find an exploit and modify /system.
But the Z3 (I own one too) required having the mods to be in system if the BL was locked. Wolfbreak obviosuly managed to get twrp installed to system and then used scripts to open it.
But a custom kernel would still brick the phone.
So you were confined to root and recovery and custom ROMs based on stock.
You have to unlock to modify the kernel (which most root now does to avoid safetynet)
So there's not much point in this system level exploit.
Phone wouldn't boot as soon as a non stock or modified kernel was installed (lots of people would try and do this and brick their phones I guarantee)
Much better to just unlock.

Dobsgw said:
You'll notice on newer xperia phones that's jot possible
You have to unlock.
They wised up and patched the KitKat exploit (although one was found in the 575 kernel)
So yeah potentially it would be possible to find an exploit and modify /system.
But the Z3 (I own one too) required having the mods to be in system if the BL was locked. Wolfbreak obviosuly managed to get twrp installed to system and then used scripts to open it.
But a custom kernel would still brick the phone.
So you were confined to root and recovery and custom ROMs based on stock.
You have to unlock to modify the kernel (which most root now does to avoid safetynet)
So there's not much point in this system level exploit.
Phone wouldn't boot as soon as a non stock or modified kernel was installed (lots of people would try and do this and brick their phones I guarantee)
Much better to just unlock.
Click to expand...
Click to collapse
Of course you will be much more limited without unlocked bootloader but on the other hand you don't have to void your warranty, unrooting your phone, without any traces of root is very useful, if you happens to need your warranty.
And you can still use stuff like setcpu, xposed framework, enable EIS and camera api2. just to name a few things.
Safetynet didn't bother me that much.
That's why people are looking for ways to root without unlocking the bootloader.

-Zteam- said:
Of course you will be much more limited without unlocked bootloader but on the other hand you don't have to void your warranty, unrooting your phone, without any traces of root is very useful, if you happens to need your warranty.
And you can still use stuff like setcpu, xposed framework, enable EIS and camera api2. just to name a few things.
Safetynet didn't bother me that much.
That's why people are looking for ways to root without unlocking the bootloader.
Click to expand...
Click to collapse
OK well when the exploit is found you'll have it

Dobsgw said:
Are you kidding?
No.
When boot loader is locked only code signed by xiaomi will run.
So twrp will just not bootup.
Also fastboot is only enabled on the phone when boot loader is unlocked so you'd have a hell of a time flashing it
And then youd likely softbrick the phone with no recovery to flash a ROM so maybe even hardbricked...
Don't try.
Just unlock.
Click to expand...
Click to collapse
10 hours left lol. i hope after 10 hours there will be no more additional trouble coming up.
So, my plan after im able to unlock it is to root>install twrp>flash it back to global stabel(my current is global beta).
im still confused about stay with beta or flash it back to stabel. Any sugesstion?

mennas said:
10 hours left lol. i hope after 10 hours there will be no more additional trouble coming up.
So, my plan after im able to unlock it is to root>install twrp>flash it back to global stabel(my current is global beta).
im still confused about stay with beta or flash it back to stabel. Any sugesstion?
Click to expand...
Click to collapse
Stay with beta its usually better.
Or switch to aosp if you don't like MIUI
Stable Oreo should come soon as the Chinese ROM just got Oreo stable

Dobsgw said:
Stay with beta its usually better.
Or switch to aosp if you don't like MIUI
Stable Oreo should come soon as the Chinese ROM just got Oreo stable
Click to expand...
Click to collapse
ok. ill stay with this beta oreo then thanks

Dobsgw said:
Stay with beta its usually better.
Or switch to aosp if you don't like MIUI
Stable Oreo should come soon as the Chinese ROM just got Oreo stable
Click to expand...
Click to collapse
Wait, is Chinese stable on oreo already?

NickTheSickDick said:
Wait, is Chinese stable on oreo already?
Click to expand...
Click to collapse
Yeah.
Also expecting Oreo kernel sources to release soon too

Dobsgw said:
Yeah.
Also expecting Oreo kernel sources to release soon too
Click to expand...
Click to collapse
Damn, that didn't take long. I remember just how buggy it was when oreo first entered alpha.

NickTheSickDick said:
Damn, that didn't take long. I remember just how buggy it was when oreo first entered alpha.
Click to expand...
Click to collapse
They need to be even quicker 8.1 has been out for a fair while as well....
At least it got to Oreo.
I'm sure there will be more updates for the "stable" branch soon.
In my use I found beta to be better

CTS profile match failed

Hi there.
I have an unrooted realme 6 pro. 2 days ago I tried to use Google pay and it did not work. It said that "You can´t pay contactless using this device. It may be rooted or running uncertified software.
I went to google play and I saw that my device is certified. After running some SafetyNet checks it says that CTS profile match failed. evakuation type: BASIC HARDWARE_BACKED. And then after reading some blogs I saw that on Google Play my netflix isn´t supported on my device although I have already installed it.
Any help or advice?
Thanks

Is your bootloader unlocked?
There's only 2 reliable ways to pass SafetyNet including CTS. The first is a completely stock device running pure OEM firmware with a locked bootloader.
The second is with Magisk, using DenyList and 2 modules: Universal SafetyNet Fix and MagiskHide Props Config.
A stock ROM on an unlocked bootloader will fail.
A custom ROM on a locked bootloader will fail.

V0latyle said:
Is your bootloader unlocked?
There's only 2 reliable ways to pass SafetyNet including CTS. The first is a completely stock device running pure OEM firmware with a locked bootloader.
The second is with Magisk, using DenyList and 2 modules: Universal SafetyNet Fix and MagiskHide Props Config.
A stock ROM on an unlocked bootloader will fail.
A custom ROM on a locked bootloader will fail.
Click to expand...
Click to collapse
I have also checked that. It has always been locked. I do not know if the problem is caused due to the new android update since is now running on android 11. Plus I dont want to root my phone

V0latyle said:
Is your bootloader unlocked?
There's only 2 reliable ways to pass SafetyNet including CTS. The first is a completely stock device running pure OEM firmware with a locked bootloader.
The second is with Magisk, using DenyList and 2 modules: Universal SafetyNet Fix and MagiskHide Props Config.
A stock ROM on an unlocked bootloader will fail.
A custom ROM on a locked bootloader will fail.
Click to expand...
Click to collapse
... You cannot have custom rom on unlocked bootloader LOL. Just saying. Unless a device is ancient, back in the days where you could run custom roms without unlocked bootloader.

JhinCuatro said:
... You cannot have custom rom on unlocked bootloader LOL. Just saying. Unless a device is ancient, back in the days where you could run custom roms without unlocked bootloader.
Click to expand...
Click to collapse
But that's the thing. I don't have a custom from. I did not root my phone. The only thing I did is to open the developer options. The bootloader was always locked. That started happening after the update to android 11. I sent my phone to the customer service now but I do not think they will do anything.

JhinCuatro said:
... You cannot have custom rom on unlocked bootloader LOL. Just saying. Unless a device is ancient, back in the days where you could run custom roms without unlocked bootloader.
Click to expand...
Click to collapse
You can, you just have to set a custom root of trust. See Android Boot Flow

V0latyle said:
You can, you just have to set a custom root of trust. See Android Boot Flow
Click to expand...
Click to collapse
Oops I misstated. I meant custom rom on locked bootloader**.

manu3732 said:
But that's the thing. I don't have a custom from. I did not root my phone. The only thing I did is to open the developer options. The bootloader was always locked. That started happening after the update to android 11. I sent my phone to the customer service now but I do not think they will do anything.
Click to expand...
Click to collapse
Same problem with my OnePlus Nord.

oOEDGUYOo said:
Same problem with my OnePlus Nord.
Click to expand...
Click to collapse
Did you find any fix yet... Am having the same issue

happy619 said:
Did you find any fix yet... Am having the same issue
Click to expand...
Click to collapse
I ended up installing the Pixel Experience rom. It was the only way to fix it

oOEDGUYOo said:
I ended up installing the Pixel Experience rom. It was the only way to fix it
Click to expand...
Click to collapse
I have been on custom ROMs for over 6 months on nord ... Some have bad update cycles .. Some are unstable and many more issues although my Device was certified

I have the same problem, bootloader is normally unlocked and I have Universal SafetyNet Fix and MagiskHide Props Config installed, using lineage 18.1 on my redmi 9 pro device

I have flashed both ...( Magisk hide prop conf & universal safety net )
But still "CTS failed, can somebody help me please....

I have this problem too. Any solutions ? I tried magisk with prop conf and safety net-fix and still have cts failed...

Finally success
of course magisk with deny list setup and the rest
1. remove universal safety fix
2. reboot
3. install displax fork mod 3.0 here
4. reboot
5. clear cache from google wallet

The rest ? What you mean ? Cause i have problem with CTS failed and im desperatly looking for solution

Oshvitzon said:
Finally success
of course magisk with deny list setup and the rest
1. remove universal safety fix
2. reboot
3. install displax fork mod 3.0 here
4. reboot
5. clear cache from google wallet
Click to expand...
Click to collapse
The rest ? What you mean ? Cause i have problem with CTS failed and im desperatly looking for solution

Mrlama112 said:
The rest ? What you mean ? Cause i have problem with CTS failed and im desperatly looking for solution
Click to expand...
Click to collapse
The regular instructions:
Magisk with zygisk , hide app , configure deny list and then as i said in the previous post

Oshvitzon said:
Finally success
of course magisk with deny list setup and the rest
1. remove universal safety fix
2. reboot
3. install displax fork mod 3.0 here
4. reboot
5. clear cache from google wallet
Click to expand...
Click to collapse
Thank you! Worked like a charm! IDK why my CTS Profile suddenly started failing, but this seemed to have fixed it.

Oshvitzon said:
Finally success
of course magisk with deny list setup and the rest
1. remove universal safety fix
2. reboot
3. install displax fork mod 3.0 here
4. reboot
5. clear cache from google wallet
Click to expand...
Click to collapse
Thanks so much it worked well. Am I able to update the Google Wallet without it affecting the mod 3.0?

Banking apps and firefox not working properly

I have rooted phone with miui global 12.0.5 with twrp recovery and magisk 24.3. This summer I started experiencing problems with some banking apps and google pay/wallet detecting root and firefox not working properly (firefox does not open or opens only in background).
Also I can't update or use Tier scooter app because play store says it's no longer compatible with my device...
Can all this be fixed with flashing stock rom and unrooting phone? What should I do?

Roro666 said:
I have rooted phone with miui global 12.0.5 with twrp recovery and magisk 24.3. This summer I started experiencing problems with some banking apps and google pay/wallet detecting root and firefox not working properly (firefox does not open or opens only in background).
Also I can't update or use Tier scooter app because play store says it's no longer compatible with my device...
Can all this be fixed with flashing stock rom and unrooting phone? What should I do?
Click to expand...
Click to collapse
Did you use magisk hide?
Have you a Begonia or Begoniain?
Latest Stock rom are 2022 A11
normally it should work but you have to lock the bootloader.
Unroot before use Miflash and reboot.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

NOSS8 said:
Did you use magisk hide?
Have you a Begonia or Begoniain?
Latest Stock rom are 2022 A11
normally it should work but you have to lock the bootloader.
Unroot before use Miflash and reboot.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
I used magisk hide and I also have both universal safetynet fix and zygisk. And I have begonia.
If I remember correctly some apps can detect unlocked bootloader nowadays so locking the bootloader might be the only way to fix things

Roro666 said:
I used magisk hide and I also have both universal safetynet fix and zygisk. And I have begonia.
If I remember correctly some apps can detect unlocked bootloader nowadays so locking the bootloader might be the only way to fix things
Click to expand...
Click to collapse
Maybe try a newer or older version of Magisk.

NOSS8 said:
Maybe try a newer or older version of Magisk.
Click to expand...
Click to collapse
Updated magisk but it only fixed the tier app... What are the worst downsides of unrooting? I've found non-root ad blocker and I'm using YouTube Vanced so ads shouldn't be a problem but I might get all the removed xiaomi bloatware back?

Roro666 said:
Updated magisk but it only fixed the tier app... What are the worst downsides of unrooting? I've found non-root ad blocker and I'm using YouTube Vanced so ads shouldn't be a problem but I might get all the removed xiaomi bloatware back?
Click to expand...
Click to collapse
the disadvantage you know, to add the risks brick.
some apps can be disabled.
Try this tool (no longer updated but works great)
https://szaki.github.io/XiaomiADBFastbootTools/

Question OnePlus 9 Pro TMO converted to Global.

Hey I'm on F.18 and cannot adjust screen color anyone else having this issue ?

Bulauski2005 said:
Hey I'm on F.18 and cannot adjust screen color anyone else having this issue ?
Click to expand...
Click to collapse
Works for me. F.18 TMO Converted as well. Unlocked, rooted. The whole 9 yards
Do a factory reset or use twrp to dirty flash F.18

With root access on F.18 do you have the unlocked bootloader warning screen ? Also can you run Substratum theme engine modules with Magisk ?

SaintZ93 said:
Works for me. F.18 TMO Converted as well. Unlocked, rooted. The whole 9 yards
Do a factory reset or use twrp to dirty flash F.18
Click to expand...
Click to collapse
With root access on F.18 do you have the unlocked bootloader warning screen ? Also can you run Substratum theme engine modules with Magisk ?

Bulauski2005 said:
With root access on F.18 do you have the unlocked bootloader warning screen ? Also can you run Substratum theme engine modules with Magisk ?
Click to expand...
Click to collapse
Yes, I have root access and bootloader unlocked warning. That is due to OnePlus keeping the Qualcomm code for it in. Has no affected on day to day use. As for Substratum, I don't use it. I also don't see it working well on OOS13 tbh since Android 13/OnePlus modifications to theming is completely differently coded than previous Android versions.

SaintZ93 said:
Yes, I have root access and bootloader unlocked warning. That is due to OnePlus keeping the Qualcomm code for it in. Has no affected on day to day use. As for Substratum, I don't use it. I also don't see it working well on OOS13 tbh since Android 13/OnePlus modifications to theming is completely differently coded than previous Android versions.
Click to expand...
Click to collapse
What are some cool things I can do with F.18 rooted ?