I had Stock Android 9 with Magisk before without TWRP, but somehow it automatically downloaded the OTA and it started asking to restart my device to update the Android version. I tried to uninstall Magisk through the manager but I messed up since it forced restarted the device. It bootlooped afterwards. I tried to install stock firmware for 9, then 10, both didn't work. Other threads say that I should change the active partition, it worked but now the Manager says the ctsProfile is false. I tried to hide the Magisk through its settings but it didn't work. I also tried to reflash with stock firmware but it didn't work as well. I don't know what to do next. Any advice for what I should do?
The only guaranteed way how to pass the SafetyNet test is to have 100% stock phone (stock ROM and locked bootloader).
Unguaranteed way (possible until Google deploys HW verification which can't be spoofed) is to root phone with Magisk and enable Magisk hide and reboot the phone (default options should be enough). Some modules will automatically break Safetynet (e.g. Xposed).
Edit: I am failing CTS profile test too, so I'd say that Google started with improved SafetyNet deployment again and we're out of luck. You can search main Magisk support thread for further info (e.g. https://forum.xda-developers.com/showpost.php?p=82935207&postcount=40370)
Thank you so much! It seems that the only way for me to pass Safetynet is to relock the bootloader, and I'm worried that it will fail since it is a risky move. Glad that it worked and it prompted me to factory reset, and now updated again to A10 . Guess I will stay in stock for now.
Its very easy! Just have to flash some zip
Sami Devo said:
Its very easy! Just have to flash some zip
Click to expand...
Click to collapse
Congrats, you just earned yourself a bounty for breaking the TEE (about $100.000). You just need to provide this "some zip" and demonstrate the mechanism.
_mysiak_ said:
Congrats, you just earned yourself a bounty for breaking the TEE (about $100.000). You just need to provide this "some zip" and demonstrate the mechanism.
Click to expand...
Click to collapse
???
---------- Post added at 09:41 PM ---------- Previous post was at 09:34 PM ----------
Just use magisk flash modules
https://drive.google.com/folderview?id=1-D9RKn9bWYQLbm3ODX_xZ_0Xe9mJmROi
And in magisk. Use system hide . Etc
Once its okk pass all cts okk.. u will find Netflix in play store ??
Sami Devo said:
[emoji1787][emoji1787][emoji1787]
---------- Post added at 09:41 PM ---------- Previous post was at 09:34 PM ----------
Just use magisk flash modules
https://drive.google.com/folderview?id=1-D9RKn9bWYQLbm3ODX_xZ_0Xe9mJmROi
And in magisk. Use system hide . Etc
Once its okk pass all cts okk.. u will find Netflix in play store [emoji1787][emoji1787]
Click to expand...
Click to collapse
Yeah, sure.. Just read a bit about HW Safetynet test, you can't spoof it.
i'm planning to unlock the bootloader and flash a custom rom leaving the bootloader unlock. mi qnoob question is:
having the bootloader unlock, does it fail the safetynet pass?
thanks in advance for your comments.
d_g_m_2000 said:
i'm planning to unlock the bootloader and flash a custom rom leaving the bootloader unlock. mi qnoob question is:
having the bootloader unlock, does it fail the safetynet pass?
thanks in advance for your comments.
Click to expand...
Click to collapse
Currently it does not (well on some of the custom ROMs I tried, do t know about stock) but Google are implementing hardware attestation which was mentioned in the comment above which will allow safety net to see an unlocked bootloader status and automatically fail safety net.
It's completely ridiculous but it's happening now. I dont know what this means for custom ROMs but for rooting it's a disaster
d_g_m_2000 said:
i'm planning to unlock the bootloader and flash a custom rom leaving the bootloader unlock. mi qnoob question is:
having the bootloader unlock, does it fail the safetynet pass?
thanks in advance for your comments.
Click to expand...
Click to collapse
As far as I know, Google is staging the rollout of HW Safetynet test to random people, but it will most probably reach all phones eventually. I am already on "BASIC,HARDWARE_BACKED" type. It should not matter if you have stock or custom ROM, you will fail the CTS test right away with unlocked bootloader as soon as you are migrated to HW test.
garylawwd said:
Currently it does not (well on some of the custom ROMs I tried, do t know about stock) but Google are implementing hardware attestation which was mentioned in the comment above which will allow safety net to see an unlocked bootloader status and automatically fail safety net.
It's completely ridiculous but it's happening now. I dont know what this means for custom ROMs but for rooting it's a disaster
Click to expand...
Click to collapse
_mysiak_ said:
As far as I know, Google is staging the rollout of HW Safetynet test to random people, but it will most probably reach all phones eventually. I am already on "BASIC,HARDWARE_BACKED" type. It should not matter if you have stock or custom ROM, you will fail the CTS test right away with unlocked bootloader as soon as you are migrated to HW test.
Click to expand...
Click to collapse
I thought it only break magisk hide but i see now that it does hurt a lot more. thank you guys for your replies.
d_g_m_2000 said:
I thought it only break magisk hide but i see now that it does hurt a lot more. thank you guys for your replies.
Click to expand...
Click to collapse
Magisk hide actually still works fine, Safetynet is independent from it. My banking app doesn't use Safetynet (yet) and Magisk hides root successfully, so I can use it freely..
_mysiak_ said:
Magisk hide actually still works fine, Safetynet is independent from it. My banking app doesn't use Safetynet (yet) and Magisk hides root successfully, so I can use it freely..
Click to expand...
Click to collapse
My banking app is outrageous. It recognises root, gives me a warning and I'm allowed to proceed with my login as normal. Sorry for ot
garylawwd said:
My banking app is outrageous. It recognises root, gives me a warning and I'm allowed to proceed with my login as normal. Sorry for ot
Click to expand...
Click to collapse
That's exactly how I imagine an ideal banking app. Give a warning or two, maybe request some extra acknowledgement that you are aware of risks and let you use the app in an unrestricted mode. I can't fathom why some apps are so "afraid" of root (especially those which don't work with sensitive personal data or money). But well, eventually I'll have to carry two phones (rooted + stock) or stop using such apps.. [emoji846]
Related
So I think most of you already know about Google's strict update to their SafetyNet API, which is used by Android Pay, and Pokemon Go among other apps.
If you don't, SafetyNet is a protocol used by Google Play Services that returns whether your device has been "tampered with". Having Root Access, Xposed installed, or a custom ROM or Kernel, have been known to trip this check, which will prevent the apps that utilize SafetyNet's functionality from running on the device.
Several developers on XDA and in the rooting community have been working overtime in an attempt to find a loophole in SafetyNet's code - enter the likes of Magisk and SuHide, each of which no longer work to hide root from SafetyNet as of the date of this writing.
Now, my personal belief is that after a person has purchased an Android device (and in effect that copy of the device's software) they should be free to make any and all modifications they choose to it - at the risk of their own security of course. Additionally, with apps like Pokemon Go, which offer in-game purchases and then change user agreements through app updates which block potential users after they may have made these same in-game purchases, the argument could be made that the SafetyNet API is even promoting fraud.
It isn't my intention to convince anyone of my position, only understand it. At this time, I am trying to gain a better understanding of exactly what elements found on a device prompt SafetyNet to return that a device has been tampered with. I was once rooted, with Xposed installed, but have since uninstalled both, and even re-flashed stock firmware. Even still, the SafetyNet Helper App I have been using for research always returns a failure. For posterity, I am also unable to log into Pokemon Go on stock firmware with no root or Xposed.
If root access is enabled, I have found that the SafetyNet check itself (step 1) will fail and the app will present a red screen, whereas if root access is not installed, the SafetyNet check will pass, but the Device Signature Verification with Google (step 2) will fail, which results in an overall failure where apps like Android Pay and Pokemon Go are concerned. The most modern counter I have found to hide root from SafetyNet is found here but even it states that the device must be able to pass the SafetyNet check on its own before this modifies SuperUser can be installed, so I feel a bit stuck.
I haven't seen anyone address SafetyNet and the Xperia Z5 Compact in the same sentence, and so my question is, can the Z5C pass SafetyNet at all since its most recent update? Please, download the SafetyNet Helper App from the Play Store and run it on your Z5C. Let me know if you get a red screen (failure at first step) a blue screen (failure at second step) or a green screen (passing). Also tell me about your device, and any modifications you have made to it. Seeing as how I can no longer pass the SafetyNet check at all on newly flashed stock firmware, I worry that the Xperia Z5C may not have been given Google's "Device Signiture Verification" - like many other international Android devices.
And if anyone else can shed some light on this situation, I would be most grateful.
Blue screen error.
Krypton custom rom based on .253 with zach's kernel. xposed installed
Sent from my iPad using Tapatalk
What about downgrading Google Play Services? as far as i remember the Safetynet APi is included in this package. Don't know if it is server based or written inside the package, though.
Has anyone found a way to bypass SafetyNet for Nougat?
grayleshy said:
Has anyone found a way to bypass SafetyNet for Nougat?
Click to expand...
Click to collapse
I also want to know this, when running safetynet test it shows me a red screen, even though I already removed root and flashed stock firmware.
rolo143 said:
I also want to know this, when running safetynet test it shows me a red screen, even though I already removed root and flashed stock firmware.
Click to expand...
Click to collapse
because of unlocked bootloader
im using magisksu + magiskhide and its bypassing the safetynet
meistr91 said:
because of unlocked bootloader
Click to expand...
Click to collapse
There is a workaround?
meistr91 said:
because of unlocked bootloader
Click to expand...
Click to collapse
Can I relock it again?
https://forum.xda-developers.com/z5-compact/general/recovery-nougat-7-0-android-bootable-t3609358
rolo143 said:
Can I relock it again?
Click to expand...
Click to collapse
Magisk changes the properties and "relocks" it for you during the start up procedures.
--- previous post
NeoBeum said:
https://forum.xda-developers.com/z5-compact/general/recovery-nougat-7-0-android-bootable-t3609358
Magisk changes the properties and "relocks" it for you during the start up procedures.
Click to expand...
Click to collapse
But magisk requires root. I remove root because there are some games and apps that detect it. So I wanted to pass SafetyNet but still can't.
I have Magisk working, I'm just rebuilding the recovery project and fixing some stuff
Has one been able to patch libandroid to make suhide work on Nougat with security patches after October 2016?
I have CarbonROM 5.1 Moo installed on my Zperia Z5 compact. This along with Magisk 14.3. (And... yeah... As it seems, the Magisk module "Universal SafetyNet Fix" is also required in my case. )
With this, it all works fine. SafetyNet checks out as valid/okay. No problems.
Will it work?
PuffDaddy_d said:
Will it work?
Click to expand...
Click to collapse
Most probably. The dev has one on order.
May not on day one, but I'd expect it very soon.
The question is how long will Magisk continue to work. According to an XDA:
Full documentation on the Titan Security Module is not yet available, but a few Google engineers have posted Tweets that give us some information. First, in response to a tweet by Dees_Troy, lead developer of TWRP, Google’s tech lead for Android hardware-backed security subsystems, Shawn Willden, states that the new security module will not be used for runtime system analysis. This is important for Magisk users because hardware-backed runtime system analysis would make systemless-root much more difficult. However, Google already opened up an API for the Trusted Execution Environment (TEE), so runtime system analysis could still happen in the future (in other words, there could still be bad news for Magisk.)
Click to expand...
Click to collapse
mycall0 said:
The question is how long will Magisk continue to work. According to an XDA:
Click to expand...
Click to collapse
I wouldn't expect Google to purposely use it to kill Magisk... however I would expect them to make it difficult to be rooted and still pass the SafetyNet check.
I'm just surprised that nobody has confirmed that Magisk works on the P3 yet.
I mean, my phone was delivered this morning, so I assumed that tons of people all over the country were eagerly unlocking bootloaders and flashing away.
But still all quiet here on this thread?
From what I understand, that's because the factory image is only out since a few hours...
Someone on the Xl forum tried and the phone didnt boot so he had to factory flash the image. So looks like its the waiting game for root.
TopJohnWu will have his pixel Friday. He is excited about it, I bet we have root by Monday.
I tried to patch the boot.img through the magisk app and then flash that through fastboot. Flashed successfully but would not boot.
I have noticed that as soon as I unlocked the bootloader I fail safety net. Has that always been the case even without any system modifications?
jsauder2 said:
I tried to patch the boot.img through the magisk app and then flash that through fastboot. Flashed successfully but would not boot.
I have noticed that as soon as I unlocked the bootloader I fail safety net. Has that always been the case even without any system modifications?
Click to expand...
Click to collapse
From what I understand that is the case, unless you use Magisk to "cloak" and "fool" the apps into thinking it isn't.
Eudeferrer said:
From what I understand that is the case, unless you use Magisk to "cloak" and "fool" the apps into thinking it isn't.
Click to expand...
Click to collapse
Guess I've not tried using my phone unlocked without magisk in awhile...
jsauder2 said:
I have noticed that as soon as I unlocked the bootloader I fail safety net. Has that always been the case even without any system modifications?
Click to expand...
Click to collapse
No, my Nexus 5 running LineageOS has always passed with Magisk and unlocked bootloader (and Pay, etc. works).
CSX321 said:
No, my Nexus 5 running LineageOS has always passed with Magisk and unlocked bootloader (and Pay, etc. works).
Click to expand...
Click to collapse
Does it pass when it's unlocked but doesn't have magisk though? That's what I was wondering. This is really the first time I've had a phone unlocked without root (since it doesn't work yet), so I've never actually thought about that until now.
jsauder2 said:
Does it pass when it's unlocked but doesn't have magisk though? That's what I was wondering. This is really the first time I've had a phone unlocked without root (since it doesn't work yet), so I've never actually thought about that until now.
Click to expand...
Click to collapse
Ah, good question. I don't know. I've always had my phone unlocked and rooted.
jsauder2 said:
Does it pass when it's unlocked but doesn't have magisk though? That's what I was wondering. This is really the first time I've had a phone unlocked without root (since it doesn't work yet), so I've never actually thought about that until now.
Click to expand...
Click to collapse
I want to say that it was relatively recently (maybe in the last 2-2.5 years) where if you only unlocked the bootloader, it would fail SafetyNet. For a while, you had to flash a kernel on top of unlocking the bootloader to pass SafetyNet.
tysj said:
I want to say that it was relatively recently (maybe in the last 2-2.5 years) where if you only unlocked the bootloader, it would fail SafetyNet. For a while, you had to flash a kernel on top of unlocking the bootloader to pass SafetyNet.
Click to expand...
Click to collapse
My experience is if I unlock bootloader, I fail SafetyNet unless Magisk is installed. Sometimes after a reboot, I still fail until I load the Magisk app and have it check once. Then the phone is fine again.
As to the original question: I installed the newest beta of Magisk on my Pixel 3 XL, downloaded the factory boot.img from Google and patched it using the app. Flashing to my active boot slot caused fastboot to complain about no valid boot images. Flashing the original boot.img allowed the phone to start normally again.
imsaguy said:
My experience is if I unlock bootloader, I fail SafetyNet unless Magisk is installed. Sometimes after a reboot, I still fail until I load the Magisk app and have it check once. Then the phone is fine again.
As to the original question: I installed the newest beta of Magisk on my Pixel 3 XL, downloaded the factory boot.img from Google and patched it using the app. Flashing to my active boot slot caused fastboot to complain about no valid boot images. Flashing the original boot.img allowed the phone to start normally again.
Click to expand...
Click to collapse
confirmed same results on Pixel 3 (non XL)
jsauder2 said:
I tried to patch the boot.img through the magisk app and then flash that through fastboot. Flashed successfully but would not boot.
I have noticed that as soon as I unlocked the bootloader I fail safety net. Has that always been the case even without any system modifications?
Click to expand...
Click to collapse
Yeah that's always been the case with unlocked bootloader
He just rooted the 3XL according to his Twitter. Release this weekend maybe?... Dude wasted no time, absolute machine.
Flashed the MIUI EU 11.0.6 and cts profile is false but basic integrity shows true. Also, play store shows "device not certified"
I've already used Magisk hide for Google Play services. Tried to re-flash magisk but still the same.
ROM: MIUI 11.0.6 EU Q
Kernel: Sesh 5.1 71Hz
Recovery: Official TWRP recovery
Magisk 20.3
Solution:
https://forum.xda-developers.com/poco-f1/themes/guide-edxposed-miui-11-0-4-android-q-t4050773/page3
MasterFURQAN said:
Flashed the MIUI EU 11.0.6 and cts profile is false but basic integrity shows true. Also, play store shows "device not certified"
I've already used Magisk hide for Google Play services. Tried to re-flash magisk but still the same.
ROM: MIUI 11.0.6 EU Q
Kernel: Sesh 5.1 71Hz
Recovery: Official TWRP recovery
Magisk 20.3
Click to expand...
Click to collapse
Google changed cts from their end. No matter what rom you flash on any phone you use, it'll fail CTS now. Wait for magisk to be updated.
Daruwalla said:
Google changed cts from their end. No matter what rom you flash on any phone you use, it'll fail CTS now. Wait for magisk to be updated.
Click to expand...
Click to collapse
Just read the article. Thanks anyways.
Xposed installed? If yes you should try this module for pass the safetynet
https://forum.xda-developers.com/showpost.php?p=81982121&postcount=80
Works for me
vjbenn said:
Xposed installed? If yes you should try this module for pass the safetynet
https://forum.xda-developers.com/showpost.php?p=81982121&postcount=80
Works for me
Click to expand...
Click to collapse
I found that out some days ago. I forgot to edit the OP.
FYI this module only fakes the status of the CTS profile. You can check your "true" status by using an app called safety net checker from play store.
Tried every one of the exposed module and all fail so that is no good for me...... anything else that will work..... even stock ROMs with unlocked bootloader with out root come up as device uncertified have a realme 5 with locked bootloader and it is fine have LG v20 it's fine and a Asus Zenfone 3 ultra locked no issues have pocof1 unlocked bootloader and it fails...........
It appears it is bootloader unlocked is what the issues is......the problem is you can't lock bootloader if you want custom recovery the problem is if you have a locked bootloader and you get jacked by someone you can't recover your device.......
Or maybe that's what Google wants to happen......
stinka318 said:
Tried every one of the exposed module and all fail so that is no good for me...... anything else that will work..... even stock ROMs with unlocked bootloader with out root come up as device uncertified have a realme 5 with locked bootloader and it is fine have LG v20 it's fine and a Asus Zenfone 3 ultra locked no issues have pocof1 unlocked bootloader and it fails...........
Click to expand...
Click to collapse
Mine passes the CTS check now even without the edXposed module.
stinka318 said:
It appears it is bootloader unlocked is what the issues is......the problem is you can't lock bootloader if you want custom recovery the problem is if you have a locked bootloader and you get jacked by someone you can't recover your device.......
Or maybe that's what Google wants to happen......
Click to expand...
Click to collapse
MasterFURQAN said:
Mine passes the CTS check now even without the edXposed module.
Click to expand...
Click to collapse
Flashed no gravity kernel and my problem went away as well I believe it has something to do with how Google receives information about the bootloader in the kernel.......
It was working ok for me till today. I had the problem with cts profile : false, then it clears from itself (google change something or revert the changes) , but now I checked randomly in magisk manager and this time I got both cts profile false and basic integrity false , so think google change the things again and even more restrictive than previous time , anyone else can confirm ?
Just download the app and sign up for an account on your Shield! No credit card or anything required.
on unlocked bl fully stock it doesnt work.. it says my device is not secure lol
elliwigy said:
on unlocked bl fully stock it doesnt work.. it says my device is not secure lol
Click to expand...
Click to collapse
Dunno what to tell ya. Works perfectly on mine, and a few friends have done it as well.
elliwigy said:
on unlocked bl fully stock it doesnt work.. it says my device is not secure lol
Click to expand...
Click to collapse
Peakcock app will only work on fully certified Google builds
If your device doesn't pass Google safetynet the app will not work
This also includes people who use the hotfix builds as they are not Google certified
If your device is rooted by magisk and it passes safetynet you can try hiding the app with magisk hide & making sure magisk manager is installed with a random package name from its settings menu
TheFixItMan said:
Peakcock app will only work on fully certified Google builds
If your device doesn't pass Google safetynet the app will not work
This also includes people who use the hotfix builds as they are not Google certified
If your device is rooted by magisk and it passes safetynet you can try hiding the app with magisk hide & making sure magisk manager is installed with a random package name from its settings menu
Click to expand...
Click to collapse
i know lol.. just thought it was funny. however it will be very difficult to make safetynet pass moving forward if its checking hardware.. lots devices are failing safetynet currently even with all of those measures being taken..
was also saying that even without root and simply having bl unlocked it will not work
Hello very friendly helping people!
Im a 10 year iPhone user, but over time i came to hate all the restrictions and so i got myself a K30 Ultra and later today it should finally arrive!
Unfortunately i found out that it doesnt check the Google SafetyNet thingy and i can't use Google Pay with it. That kinda sucks, I never thought about stuff like this on iOS, but I'm confident there is a solution for it.
I found out about rooting my device, but it somehow isn't possible because of the Mediatek chip. But then I also found out that apperenty there IS a way to use the program/thingy that makes the phone pass SafetyNet (Magisk) without the need of a custom ROM.
I'm sorry if im confusing words like rooting im very noobish about all this.
So here are my questions in short form:
1. Can I make Google Pay Work in any way on my Redmi K30 Ultra?
2. Does this also affect my banking apps (I'm using DKB and Kontist) and can this be solved, too?
3. Could you link me some guides how to do it?
4. Is there any danger doing it (like deleting my phone if it doesnt work) and is there a possibility to safe my device on the PC or something like this to be safe?
5. Are their any safety concerns doing "it" (not sure what the solution will be) and should I install an anti virus program on the device? I just read about the cerberus trojan and its kinda scary. I think iOS systems were always pretty safe against those.
6. Anything else i need to know?
Thank you so much! I appreciate it a lot that there is a place where i can go to get help on those things! <3
Google Pay and any other banking apps refuse to work when a rooted Android gets detected by them. BTW: SafetyNet API doesn't purely check whether the device's Android is rooted, as the API is designed to check the overall integrity of device's Android.
jwoegerbauer said:
Google Pay and any other banking apps refuse to work when a rooted Android gets detected by them. BTW: SafetyNet API doesn't purely check whether the device's Android is rooted, as the API is designed to check the overall integrity of device's Android.
Click to expand...
Click to collapse
Hey, thanks for your post!
Are you implying that there is no way around that and its doomed to forever not work on my device?
To clarify things: SafetyNet is run by an app that has implemented this API, it's not run by Android OS itself. Yes, Magisk allows you to lever out this test by manipulating device's fingerprint so you will possibly be able to use Google Pay etc.pp
FYI: Any app not having SafetyNet API implemented easily can check whether Android got rooted / tampered or not. The app simply runs functions like
Code:
isRootNative
isDetectedDevKeys
isDetectedTestKeys
isFoundBusyboxBinary
isFoundDangerousProps
isFoundHooks
isFoundResetprop
isFoundSuBinary
isFoundWrongPathPermission
isFoundXposed
isNotFoundReleaseKeys
isPermissiveSelinux
isSuExists
isMagiskSUExists
isFoundMagisk
isFoundRootCloakingApps
what can't get prevented by Magisk.
jwoegerbauer said:
Yes, Magisk allows you to lever out this test by manipulating device's fingerprint so you will possibly be able to use Google Pay etc.pp
Click to expand...
Click to collapse
Ok, perfect. Would you be able to link me to a guide that shows me how to install Magisk on my device? It has a Mediatek chip so a custom ROM isn't possible (as far as I understand).
Mirardt said:
Ok, perfect. Would you be able to link me to a guide that shows me how to install Magisk on my device? It has a Mediatek chip so a custom ROM isn't possible (as far as I understand).
Click to expand...
Click to collapse
How to install Magisk without a Custom ROM is explained here.
If a Custom ROM like TWRP isn't officially made public for your device then you have to compile TWRP at your own.
This is TWRP and Magisk for the latest firmware on the K30 Ultra. https://mifirm.net/downloadtwrp/166
---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------
Google Pay on a rooted device with Magisk installed /is/ possible, my Galaxy Note 9 with Dr. Ketan's ROM works with Google Pay and I believe it's due to the CTS Profile fix which is available in its ROM Tool app. So there's going to be some way to make it work with the K30 Ultra.
JaboJG said:
This is TWRP and Magisk for the latest firmware on the K30 Ultra. https://mifirm.net/downloadtwrp/166
Click to expand...
Click to collapse
Oh wow how cool is that, that is custom for the K30 ultra
And do I install that with the guide linked above or do I need some certain skill and experience to do that. It says it isn't tested yet. If I do a mirror of my phone before nothing really bad can happen right?
Google Pay on a rooted device with Magisk installed /is/ possible, my Galaxy Note 9 with Dr. Ketan's ROM works with Google Pay and I believe it's due to the CTS Profile fix which is available in its ROM Tool app. So there's going to be some way to make it work with the K30 Ultra.
Click to expand...
Click to collapse
Nice!!!
Yeah the only think that failed SafetyNet Test is the "CTS profile match". But I can't use those roms for my K30 ultra, right, so I just do it with Magisk?
Thanks so much!!
You need to unlock your bootloader with the Mi Unlock tool then flash TWRP over fastboot, and in TWRP make the appropriate backups and flash Magisk. There's many guides and it's relatively straight forward.
K30 Ultra is basically a brand new phone, it's like a month old. It'll be a while but keep an eye on XDA Forums, on the internet, and on YouTube. Somebody will eventually describe or figure out how to fix the CTS Profile.
I think I'm not gonna modify mine and I'll just wear my Apple Watch to use it for contactless payments.
JaboJG said:
You need to unlock your bootloader with the Mi Unlock tool then flash TWRP over fastboot, and in TWRP make the appropriate backups and flash Magisk. There's many guides and it's relatively straight forward.
K30 Ultra is basically a brand new phone, it's like a month old. It'll be a while but keep an eye on XDA Forums, on the internet, and on YouTube. Somebody will eventually describe or figure out how to fix the CTS Profile.
I think I'm not gonna modify mine and I'll just wear my Apple Watch to use it for contactless payments.
Click to expand...
Click to collapse
Alright, so I read 12384 guides and had a very tiny sense of it. The Mi Unlock tool stopped me, though, and now I'll have to wait another 6 days.
As I understood it, my data will be erased, but can be just be restored by MIUI if backed up before. I'm gonna let you know how it worked after I'll do it in about a week.
Probably I won't have to patience to wait. Google Pay is a really nice to have, but neither voLTE, nor voWifi works on my device, so I for sure have do hack that some weird way, because i have no mobile network at all at home and absolutely need voWifi.
Thank you very much for your kind help! <3
No problem at all.
I'm not sure if Wifi-Calling (voWifi) works with my carrier as I've turned it on with the carrier and in the phone, and it doesn't seem to be making calls over wifi. Not a big deal for me though as I've got Unlimited calls with my carrier.
Please let us know if and when you do flash the TWRP as I'd like feedback before flashing it myself.
Do your banking apps refuse to work or is it only google pay that fails due to the safetynet fail?
JaboJG said:
No problem at all.
I'm not sure if Wifi-Calling (voWifi) works with my carrier as I've turned it on with the carrier and in the phone, and it doesn't seem to be making calls over wifi. Not a big deal for me though as I've got Unlimited calls with my carrier.
Please let us know if and when you do flash the TWRP as I'd like feedback before flashing it myself.
Click to expand...
Click to collapse
Yeah, me too, but I have a very bad connection in my flat so I do need voWifi anyway. I will let you know and hope I won't brick my device. But as I understand it, bricking the device just by flashing twrp is very unlikely, right?
MerlijnD said:
Do your banking apps refuse to work or is it only google pay that fails due to the safetynet fail?
Click to expand...
Click to collapse
Only Google Pay, both of my banking apps work perfectly. I couldnt scan the security bar code though, some internal google app wouldn't allow it. So i had to put in both the (very long) idendification and security numbers in manually.
Alright thanks. Another thing im interested in is if Snapchat works when safetynet fails. Did you do any tests regarding that?
MerlijnD said:
Alright thanks. Another thing im interested in is if Snapchat works when safetynet fails. Did you do any tests regarding that?
Click to expand...
Click to collapse
Not using Snapchat, but I just installed it and it starts without problems. Didn't made an account though.
So I'm gonna be able to flash twrp and Magisk in exactly 14 hours and have some questions i would really appreciate an answer to <3
Using this: https://mifirm.net/downloadtwrp/166
1. The thing i want to flash first is twrp and it is the file called "recovery.img" in the downloaded folder, is that correct?
2. Just flashing twrp is "relatively" safe and if I do a backup and the device bricks by installing Magsik after, i can recover it through twrp, correct?
3. Should I not install todays new security update to MIUI or does that not matter at all?
edit: 4. Do I need/want to have "USB debugging", "Install via USB" and "USBebugging (Security Settings)" enabled or just "OEM unlocking"?
Thank you so much! I'm very nervous since i didn't read any experiences of rooting the K30 Ultra before and I'm scared of killing it.
Hey Mirardt, good luck. Let us know how you get on!
1. Yeah, you'll use fastboot to flash the recovery.img for TWRP.
2. Do a full backup with TWRP and you should be safe.
3. Doesn't matter, it's just the September Android security update.
4. Yeah turn on USB Debugging and connect your phone to your computer - it will ask you if you want to allow this computer to debug your phone, choose accept and always (or something similar to those words.) Do this before flashing TWRP.
Mirardt said:
So I'm gonna be able to flash twrp and Magisk in exactly 14 hours and have some questions i would really appreciate an answer to <3
Using this: https://mifirm.net/downloadtwrp/166
1. The thing i want to flash first is twrp and it is the file called "recovery.img" in the downloaded folder, is that correct?
2. Just flashing twrp is "relatively" safe and if I do a backup and the device bricks by installing Magsik after, i can recover it through twrp, correct?
3. Should I not install todays new security update to MIUI or does that not matter at all?
edit: 4. Do I need/want to have "USB debugging", "Install via USB" and "USBebugging (Security Settings)" enabled or just "OEM unlocking"?
Thank you so much! I'm very nervous since i didn't read any experiences of rooting the K30 Ultra before and I'm scared of killing it.
Click to expand...
Click to collapse
JaboJG said:
Hey Mirardt, good luck. Let us know how you get on!
1. Yeah, you'll use fastboot to flash the recovery.img for TWRP.
2. Do a full backup with TWRP and you should be safe.
3. Doesn't matter, it's just the September Android security update.
4. Yeah turn on USB Debugging and connect your phone to your computer - it will ask you if you want to allow this computer to debug your phone, choose accept and always (or something similar to those words.) Do this before flashing TWRP.
Click to expand...
Click to collapse
Hey Jabo, nice, I'm gonna do just that! Just for clarification, I use Mi Unlock Tool first, THEN twrp, then backup, then magisk?
I'll let you know and thanks for the good luck!
edit: so the command would be "fastboot flash recovery recovery.img", right?
I'm VERY sorry for the noobish questions.
I'm going to quickly use this thread to ask how to actually unlock the K30 Ultra Bootloader. I did everything the guides said, but Mi Unlock still doesn't recognize the phone when it's plugged in. Any Advice?
Hey guys (especially JaboJG). quick update: Flashing twrp and Magsik both just worked perfectly. no brick. Thanks for your help!!
The only issue is that it didnt help in passing Google Safety Check. I tried almost everything there is and will post my logs of MagiskHide Props in their thread soon.
Also, now some apps don't work anymore because they detect the root. I hope we will find a fix.
macrett said:
I'm going to quickly use this thread to ask how to actually unlock the K30 Ultra Bootloader. I did everything the guides said, but Mi Unlock still doesn't recognize the phone when it's plugged in. Any Advice?
Click to expand...
Click to collapse
No idea, sorry. It just worked for me.