Related
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
Hello everyone,
So I will get the Mi A2 lite on Tuesday 64GB/4GB RAM version.
I was wondering if the bootloader will stay unlocked after OTA update.
Also I read on reddit that the latest OTA (January) can possibly brick the device
https://www.reddit.com/r/Xiaomi/comments/ajoh56/psaupdate_bug_do_not_update_to_latest_january
Thanks in advance.
The bootloader only relocks if you wish to do that on your own by either fastboot command or MiFlash with relock selected.
I updated my mi a2 lite while bootloader is unlocked and nothing happened
thorin0815 said:
The bootloader only relocks if you wish to do that on your own by either fastboot command or MiFlash with relock selected.
Click to expand...
Click to collapse
So if the first thing I do is unlock the bootloader I'm pretty much safe...
grish said:
So if the first thing I do is unlock the bootloader I'm pretty much safe...
Click to expand...
Click to collapse
Unlocking/locking is pretty easy on this device, but beware that when you unlock/lock your bootloader phone will erase all data on board. There is a way to bypass that erase too though. So you can do pretty much everything with no serious consequences.
marstonpear said:
Unlocking/locking is pretty easy on this device, but beware that when you unlock/lock your bootloader phone will erase all data on board. There is a way to bypass that erase too though. So you can do pretty much everything with no serious consequences.
Click to expand...
Click to collapse
So there's basically nothing that can go wrong when I unlock the bootloader via fastboot/adb after first boot?
Nope, but your device will be classified as uncertified device inside Playstore, which could be a problem with apps like Netflix or banking stuff.
After the unlocking you could root your device with Magisk to pass Safety.Net, but this could be problematic with OTA's again.
thorin0815 said:
Nope, but your device will be classified as uncertified device inside Playstore, which could be a problem with apps like Netflix or banking stuff.
After the unlocking you could root your device with Magisk to pass Safety.Net, but this could be problematic with OTA's again.
Click to expand...
Click to collapse
Thought that only happens when you use a different system image or modify the partitions. Guess I'll wait a bit then.
grish said:
Thought that only happens when you use a different system image or modify the partitions. Guess I'll wait a bit then.
Click to expand...
Click to collapse
I used Magisk and only Magisk systemless modules, but after I updated from 10.0.2.0 to 10.0.3.0 via OTA my device started to bootloop. Even though I did uninstall Magisk and reinstall after the OTA the right way like I did all the times before.
For the moment I just stay with an unlocked bootloader but without root. I miss Viper4Android, but it's not worth the hassle. I'm using my older Moto G4 as my Spotify player now.
Edit: I just remembered that it happened at the update from Oreo to Pie aswell.
thorin0815 said:
I used Magisk and only Magisk systemless modules, but after I updated from 10.0.2.0 to 10.0.3.0 via OTA my device started to bootloop. Even though I did uninstall Magisk and reinstall after the OTA the right way like I did all the times before.
For the moment I just stay with an unlocked bootloader but without root. I miss Viper4Android, but it's not worth the hassle. I'm using my older Moto G4 as my Spotify player now.
Edit: I just remembered that it happened at the update from Oreo to Pie aswell.
Click to expand...
Click to collapse
The loop, you mean?
Can you use netflix with unlocked bl?
grish said:
The loop, you mean?
Click to expand...
Click to collapse
Yup!
Can you use netflix with unlocked bl?
Click to expand...
Click to collapse
You won't find the Netflix app inside the Play Store when your bootloader is unlocked (Safety.Net fails), but you can download it for example from APKMirror.
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=netflix
Edit: Just tested it with the latest beta version and it worked without problems.
thorin0815 said:
Yup!
You won't find the Netflix app inside the Play Store when your bootloader is unlocked (Safety.Net fails), but you can download it for example from APKMirror.
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=netflix
Edit: Just tested it with the latest beta version and it worked without problems.
Click to expand...
Click to collapse
Thanks a lot.
Do you think the bootloop was because of magisk when going from oreo to pie?
grish said:
Thanks a lot.
Do you think the bootloop was because of magisk when going from oreo to pie?
Click to expand...
Click to collapse
Well, I don't know any other reason, because I haven't touched the system partitions at all.
thorin0815 said:
Well, I don't know any other reason, because I haven't touched the system partitions at all.
Click to expand...
Click to collapse
Unlocking the bootloader on oreo can't be the issue?
grish said:
Unlocking the bootloader on oreo can't be the issue?
Click to expand...
Click to collapse
I don't think the unlocked bootloader was the reason. Never experienced problems with OTA's on all my devices just because of an unlocked bootloader.
With Magisk 17.3 I could install OTAs without a problem, but since Magisk has been updated to 18.0, OTAs don't work anymore. I have to unroot, flash stock, update then recover all the data then root again. It's a pain in the a** to do that everytime so I'm sticking with stock and locked bootloader for now. Also bootloop issues were reported on Mi A2 devices, not Lite AFAIK.
For me problems started with Pie, with Oreo I never faced problems with Magisk and OTA updates. Magisk 18.0 worked just fine for me with Oreo.
Hi I've never wanted to root or custom ROM. I read the instructions and they are pages deep and the issues that come up and are discussed in threads have such confusing back and forth discussions using lingo and abbreviations that make my head spin.
However... Oneplus did their last update on my 5t my fourth oneplus phone... With an already old security update.
Is the only way to not throw away a perfectly working, phone with good Ram and a fairly new battery I paid to have installed just months ago?
If I'm wanting to hold on another year or 2 use the only option custom ROMs that contain security updates?
Is there a way to add security updates without a ROM? Or maybe at least just learn to root and then add just updates or is it only in ROMs?
I could probably happily use my phone as is but worried what effect no security updates really is to my use.
I really tried videos on doing so this myself I'm not comfortable if problems happen. Not very techy.
Any help appreciated
Unfortunately you can no longer get security updates once your device is deemed as old.
Your options will be to get an antivirus app on your phone, install a custom ROM (like LOS or pixel exp), or you can get a new phone.
Since you're new to this stuff I highly recommend you just get a new phone or simply install an antivirus.
Not sure which anti virus is better than which. But I'm confident in Avira, McAfee, and Norton. You may want to purchase their plan though.
Hope I helped.
Thanks alot for the reply. I'll start with an antivirus.
Hello,
I have similar issue, since I would need security patch update to keep running company mails and apps.
I have 2 doubts:
- if I root and install Android 11 custom ROM, security patches will be updated too?
- after this, would I be able to unroot and install company mail apps ( if rooted they will not work) ?
Thanks
Personally I think that your company has put an unfair burden on you to run company mail and apps on your personal phone while expecting you to have an updated phone at the same time. An updated phone should have been "given" to you.
That being said, you can actually flash and run a custom rom without root. Root is optional.
Process is as follows: (you'll need a PC for this)
1. Backup ALL your data
2. Unlock the bootloader
3. Install custom recovery and reboot to recovery
4. Wipe cache & system and format internal memory
5. Copy custom rom & gapps to internal memory
6. Flash custom rom & gapps and reboot system
miloinodense said:
Hello,
I have similar issue, since I would need security patch update to keep running company mails and apps.
I have 2 doubts:
- if I root and install Android 11 custom ROM, security patches will be updated too?
- after this, would I be able to unroot and install company mail apps ( if rooted they will not work) ?
Thanks
Click to expand...
Click to collapse
Yes if you install custom ROM you'll have security updates. It doesn't have to be Android 11 and you don't need root to install a custom ROM.
Also make sure to follow a precise guide about it so you don't encounter any issues. Always make a backup even if you're 100% sure you won't need it.
As far as I know mail apps don't check the integrity or do a SafetyNet check, so even if you root or don't it will work fine.
If you mean banking apps then you can install some modules to bypass the check or just completely remove root. Assuming that you rooted the device.
It shows my lack of knowledge never ever did I think you could Flash a ROM without being rooted.
Thanks
I successfully installed custom ROM w/o root.
But regarding company mail apps, I would need to hide bootloader unlocked status.
maybe it's impossible, if someone has a good idea...
miloinodense said:
I successfully installed custom ROM w/o root.
But regarding company mail apps, I would need to hide bootloader unlocked status.
maybe it's impossible, if someone has a good idea...
Click to expand...
Click to collapse
My banking apps working fine without root with crdroid 7.3 and flamegapps. Might work for your company mail app too.
Some roms readily hide bootloader status
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
miloinodense said:
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
Click to expand...
Click to collapse
Hence that's why the burden should be on the company to provide the "up to date" phone
miloinodense said:
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
Click to expand...
Click to collapse
And that's why the burden should be on the company to provide the "up to date" phone
miloinodense said:
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
Click to expand...
Click to collapse
I think if you change build.prop to some other phone with recent security patches you can bypass this.
XDHx86 said:
I think if you change build.prop to some other phone with recent security patches you can bypass this.
Click to expand...
Click to collapse
Today, I was thinking that this could be good way.
Root, change build.prop, and then unroot.
If you have a link for a good tutorial on change bulid.prop would be nice, thanks.
miloinodense said:
Today, I was thinking that this could be good way.
Root, change build.prop, and then unroot.
If you have a link for a good tutorial on change bulid.prop would be nice, thanks.
Click to expand...
Click to collapse
Just for update:
I tried to Root a stock ROM, edit build.prop (security patch date), unroot, and then lock bootloader.
But even if it was a stock ROM, OP5T was not booting.
Booloader was stopping boot since it was detecting a non-stock ROM.
Indeed, I had to unbrick OP5T since I was not possible to unlock bootloader.
So, still not solved
miloinodense said:
Just for update:
I tried to Root a stock ROM, edit build.prop (security patch date), unroot, and then lock bootloader.
But even if it was a stock ROM, OP5T was not booting.
Booloader was stopping boot since it was detecting a non-stock ROM.
Indeed, I had to unbrick OP5T since I was not possible to unlock bootloader.
So, still not solved
Click to expand...
Click to collapse
Just edit build.prop and use magisk hide module from magisk manager.
XDHx86 said:
Just edit build.prop and use magisk hide module from magisk manager.
Click to expand...
Click to collapse
Edit build.prop w/o root and unlock bootloader is not possible...
Moreover, hiding root will not work with more recent android updates and for sure it will not hide unlock bootloader.
miloinodense said:
Edit build.prop w/o root and unlock bootloader is not possible...
Moreover, hiding root will not work with more recent android updates and for sure it will not hide unlock bootloader.
Click to expand...
Click to collapse
Yeah I assumed you would know that you should root first. But seeing you even attempted to lock bootloader after modifying the device, seems I assumed wrong.
Magisk hide is working fine on later android versions like 8+. And for the bootloader it only trips CTS if your bootloader is using hardware backed key - Which is the case with OP5 - as CTS check also has hardware attestation. But it is possible to bypass said check by using SafetyNet Fix module, of course you will also install that from magisk manager.
I have the HD1900 OnePlus 7T
Unlocked bootloader and Magisk
So i have Netflix installed. I go to magisk hide list and Netflix is not in the list of apps to hide!!!
Just wondering why I can't see the Netflix app in magisk hide??????
Thanks
wugga3 said:
I have the HD1900 OnePlus 7T
Unlocked bootloader and Magisk
So i have Netflix installed. I go to magisk hide list and Netflix is not in the list of apps to hide!!!
Just wondering why I can't see the Netflix app in magisk hide??????
Thanks
Click to expand...
Click to collapse
Shows up here just fine.
nagi_007pk said:
Shows up here just fine.
Click to expand...
Click to collapse
It don't show up in my Magisk Hide list no matter how many times I disable/enable or delete/clear cashe...
Press the magnifying glass in the botton right corner
and make sure show system apps in enabled as well as os apps. Maybe Netflix is installed as a system app on your phone.
nagi_007pk said:
Press the magnifying glass in the botton right cornerView attachment 5331917 and make sure show system apps in enabled as well as os apps. Maybe Netflix is installed as a system app on your phone.
Click to expand...
Click to collapse
Yes you are correct!!!!!! How awesome is that!!! I finally learned something today yay!!! It's their just like you said just like magic. Still not used to this device coming from many prior Samsung devices using Magisk. Your the best Thanks.
Thanks so very much for your help... I feel like an idiot after using Magisk For years and years on this device and many other Samsung devices without issue... On the other hand... I've never encountered this specific issue as everything's always functioned... Thanks for the education is appreciated greatly. I'm intrigued what else I can utilize our accomplish with this information. You're the best.
Don't know why I didn't know that by now lol...
Thanks for teaching me something new today. I'm greatful for you assistance. Cheers
Oh well was hoping hiding Netflix would may be fix my Widevine L3 and restore it back to L1. But, knew it wouldn't and it didn't but at least I now know and at least was able to finally figure out how to try. Thanks again
What oxygen os version are you running if I may ask? If you upgrade to Stock OOS11 you can get widevine L1 with unlocked bootloader and magisk installed. It also works with Amazon video and other encrypted video playback apps very nicely!
nagi_007pk said:
What oxygen os version are you running if I may ask? If you upgrade to Stock OOS11 you can get widevine L1 with unlocked bootloader and magisk installed. It also works with Amazon video and other encrypted video playback apps very nicely!
Click to expand...
Click to collapse
Thanks for letting me know cause I can't find a solid answer to my Widevine issue . Any trick to accomplishing widevine L1? Cause if their is any specific method to L1 then I haven't figured it out.... Thanks
wugga3 said:
Thanks for letting me know cause I can't find a solid answer to my Widevine issue . Any trick to accomplishing widevine L1? Cause if their is any specific method to L1 then I haven't figured it out.... Thanks
Click to expand...
Click to collapse
Upgrade to OOS 11. L1 will be completely fixed even with an unlocked bootloadee
Great to know thanks... But how does OOS11 performance? I'm hearing all kinds of problems...(?) that I'd rather not have since widevine is the only real problem (since I've had this device at it's release).
I've tried almost everything to fix this L3 issue and failed.... Plus, I'm stubborn so failure ain't an option even if failure is the ultimate solution LOL!
The biggest concern is the lack of a working TWRP for the 7T. My Samsung with TWRP was so fun to play with (back up, play with... break... restore... Breath again all good).
Thanks for the information cause it's finally nice to have a reliable source on the matter.
nagi_007pk said:
What oxygen os version are you running if I may ask? If you upgrade to Stock OOS11 you can get widevine L1 with unlocked bootloader and magisk installed. It also works with Amazon video and other encrypted video playback apps very nicely!
Click to expand...
Click to collapse
Well I uninstalled Netflix and did OOS 11.01.1 update...
Still Play Store device certified and Safetynet passed in Magisk Manager
Still L3 and no L1 so I don't know now...
So I can't yet figure this out...
Not sure if you can help get this back to L1 cause I'm don't know what else I'm missing unless it's hide the Magisk app (while Magisk hide is enabled) and/or hiding Netflix (now that I know how to)
No issue here though. Running the global 7T update with OOS 11.0.1.1. I have proper L1 support with an unlocked bootloader and Magisk. You could factory reset your phone and check that way. I did restore my phone completely after updating to Android 11
nagi_007pk said:
No issue here though. Running the global 7T update with OOS 11.0.1.1. I have proper L1 support with an unlocked bootloader and Magisk. You could factory reset your phone and check that way. I did restore my phone completely after updating to Android 11
Click to expand...
Click to collapse
Yikes
The reset is yes my complete last resort.
Cause, the OnePlus back up/restore will make a successful back up - but, when I try to transfer it to my computer it causes an error and quits. So the back file sizes are significantly different between the phone and the computer. Having said that, I believe I was successful to transfer the back up data to a USB storage. So, I'm hoping that I can restore from that after device reset.... Thanks
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?