Magisk basic integrity failed after normal flash - Xiaomi Mi Mix 2 Questions & Answers

I'm trying to hide magisk for almost a week but it keeps showing that basic integrity failed and cts profile also failed. I tried it on AICP, OMNI and lineage. What I am doing every time is factory reset, wipe data, clean install of rom, gapps than magisk and always ive got 2 red dots on checking safetynet integrity. Anybody can help?

krzystooof said:
I'm trying to hide magisk for almost a week but it keeps showing that basic integrity failed and cts profile also failed. I tried it on AICP, OMNI and lineage. What I am doing every time is factory reset, wipe data, clean install of rom, gapps than magisk and always ive got 2 red dots on checking safetynet integrity. Anybody can help?
Click to expand...
Click to collapse
I saw some issues with magisk 16.4 also with miui 10

PeppeCNN said:
I saw some issues with magisk 16.4 also with miui 10
Click to expand...
Click to collapse
I tried it on magisk 16.0 16.4 and 14.0. I haven't done it on miui. I tried on AICP Omni and Los. I talked with people that uses it every day with magisk and safety net passed. They have done everything just like me and their software is working

Are you flashing Magisk immediately after you flash Gapps? If so you should try completely booting into the ROM before you flash Magisk.

jhs39 said:
Are you flashing Magisk immediately after you flash Gapps? If so you should try completely booting into the ROM before you flash Magisk.
Click to expand...
Click to collapse
Both. Both not working
Sent from my MI Mix 2 using Tapatalk

If you are running the latest official version of TWRP and not an earlier version or custom version and you are also running the most recent version of Magisk I would format (not just wipe) the phone memory and install again from scratch.

jhs39 said:
If you are running the latest official version of TWRP and not an earlier version or custom version and you are also running the most recent version of Magisk I would format (not just wipe) the phone memory and install again from scratch.
Click to expand...
Click to collapse
Im doing it every time

Do you use Google Apps? And if so, are you certified? (You can find it in the Play Store -> Settings). It sounds like a problem i used to have, but now is gone, but i need more information so verify it.
And What ROM are you using right now?

SanHelios said:
Do you use Google Apps? And if so, are you certified? (You can find it in the Play Store -> Settings). It sounds like a problem i used to have, but now is gone, but i need more information so verify it.
And What ROM are you using right now?
Click to expand...
Click to collapse
Yeah. I use open gapps. Arm64 micro. I can't see this option in play store but after checking safety net status in magisk manager it shows up and I'm not certified
I'm on omni right now but I tried aicp and los also

krzystooof said:
Yeah. I use open gapps. Arm64 micro. I can't see this option in play store but after checking safety net status in magisk manager it shows up and I'm not certified
I'm on omni right now but I tried aicp and los also
Click to expand...
Click to collapse
Okay, here's what i do everytime, AFTER i flashed LOS, OpenGapps and MAGISK from scratch.
1) Download Lineageos-Zip, Magisk-Zip and Apk, (and maybe Custom-Kernel)
2) Boot into recovery-mode
3) Wipe Dalvik and Cache
4) Reboot Recovery
5) Flash Lineageos and after Magisk
6) Boot System
7) Install Magisk-Apk but don't start the app
8) Go into Setting -> Apps & Notifications -> Google Play Store -> Storage -> Clear Cache AND Clear Data
9) Go into Setting -> Apps & Notifications -> Magisk -> Storage -> Clear Cache AND Clear Data
After these procedures, You should start Magisk and the Safetynet-Test, should be green on ctsProfile and basicintegrity.
If you start Google Play-Store, install any app you want. To check, if it worked, go into Settings of Google Play-Store and check at the bottom.
Please give any feedback, if it worked.
---------- Post added at 08:23 PM ---------- Previous post was at 08:21 PM ----------
krzystooof said:
Yeah. I use open gapps. Arm64 micro. I can't see this option in play store but after checking safety net status in magisk manager it shows up and I'm not certified
I'm on omni right now but I tried aicp and los also
Click to expand...
Click to collapse
I tried this procedure with LOS, RR, OMNIROM and ABC-Rom, always worked.

SanHelios said:
Okay, here's what i do everytime, AFTER i flashed LOS, OpenGapps and MAGISK from scratch.
1) Download Lineageos-Zip, Magisk-Zip and Apk, (and maybe Custom-Kernel)
2) Boot into recovery-mode
3) Wipe Dalvik and Cache
4) Reboot Recovery
5) Flash Lineageos and after Magisk
6) Boot System
7) Install Magisk-Apk but don't start the app
8) Go into Setting -> Apps & Notifications -> Google Play Store -> Storage -> Clear Cache AND Clear Data
9) Go into Setting -> Apps & Notifications -> Magisk -> Storage -> Clear Cache AND Clear Data
After these procedures, You should start Magisk and the Safetynet-Test, should be green on ctsProfile and basicintegrity.
If you start Google Play-Store, install any app you want. To check, if it worked, go into Settings of Google Play-Store and check at the bottom.
Please give any feedback, if it worked.
---------- Post added at 08:23 PM ---------- Previous post was at 08:21 PM ----------
I tried this procedure with LOS, RR, OMNIROM and ABC-Rom, always worked.
Click to expand...
Click to collapse
It's not working for me. I also formatted data, becouse omni wouldnt start
UPDATE
I flashed magisk once again and cleared caches and data. Than everything was working

Related

[Q] Google account disappeared after updating CyanogenMod

I just updated from CM9.0 to 9.1. The step I've taken is install zip, clear cache and thats all.
Now after reboot, it's like I haven't install GAPPS. I installed it when I first install 9.0 but now after flashing 9.1 (without full wipe cause it's only 9.0 to 9.1) Play Store crashes, Gmail too, no add Google account option in settings. Except for that everything is okay.
I read through posts saying installing GAPPS helps but I was wondering why, when I installed it on 9.0.
On CM9/9.1 GAPPS are wiped by installing an update of CM, flash GAPPS again.
The update removes earlier version of CyanogenMod completely in order to avoid issues.
Just reinstall GAPPS.

Updating ROM with Latest Nightly Lineage or Other ROM & TWRP Backup/Restore

Hi guys,
How do I properly update Lineage OS nightly updates or any other ROM for that matter. The update through the "About Phone" doesn't seem to work. It gets to about 70% then tells me the download failed. I tried many times. I did some research around the forums and everyone seems to say do it manually by downloading the ROM and flashing it via TWRP overtop. So I did that but when it rebooted it lost all my user and app data and I had to reapply all my settings manually.
I also did a twrp backup before I did the previous install. I tried to do a restore and same thing. It seemed to have lost all my app data and user data. Had to redo everything manually so instead i just installed the latest nightly and redid everything manually. Did I misunderstand how to update the ROM?
Thanks!
tranh2 said:
Hi guys,
How do I properly update Lineage OS nightly updates or any other ROM for that matter. The update through the "About Phone" doesn't seem to work. It gets to about 70% then tells me the download failed. I tried many times. I did some research around the forums and everyone seems to say do it manually by downloading the ROM and flashing it via TWRP overtop. So I did that but when it rebooted it lost all my user and app data and I had to reapply all my settings manually.
I also did a twrp backup before I did the previous install. I tried to do a restore and same thing. It seemed to have lost all my app data and user data. Had to redo everything manually so instead i just installed the latest nightly and redid everything manually. Did I misunderstand how to update the ROM?
Thanks!
Click to expand...
Click to collapse
Just download the full rom and follow the procedure.
1. Take a backup of System, Data and Boot.
2. Wipe System
3. Flash in this order: ROM > Gapps (Yes you do need to do this)> Custom kernel (optional) > SuperSU/Magisk (optional) > any other mods.
4. Now wipe Cache and Dalvik and reboot!
5. First boot might take a while. If it loops just try it again or restore the backup and create a new topic!
Ah thank you! I was selecting the wrong options. This worked

Which [Android 8] daily driver to move to from FreedomOS 2.10.4 [7.1.1] ?

Back after a long time.
My OP3
- Freedom OS 2.10.4 [Android 7.1.1]
- BluSpark Recovery v40
On my OP3 I've always been on Freedom OS . Mostly due to
- Being close to stock,
- Debloated
- rooted for ad blocker, cerberus and titanium
However off the late facing lot of issue with network. Frequent drops on VoLTE and 4G networks on both sims. VoLTE sim will often disconnect and I will end with "Dial-> Immediate Call Ended" issue.
=> What would you recommend to use as daily driver ?
Would appreciate if you should add links. Any additional info regarding prerequisites (recovery, firmware etc) will be helpful.
You can try:
1-OxygenOS 5.0.3 with RenderZenith or Derp kernel.(Do not go for open beta OxygenOS builds, they are abandoned.)
2-Paranoid Android 7.3.1(Nougat but it won't upset you)
3-If camera, VoWiFi and OTA updates are not important, OmniDragon.
Everyone's expectations are different. These are just mine experiences.
You should update your TWRP before flashing, i guess it is outdated; PA and OxygenOS contains their own firmware but for OmniDragon you can use Open Beta 39/OxygenOS 5.0.3 firmwares.
qhsusb_bulk said:
You can try:
1-OxygenOS 5.0.3 with RenderZenith or Derp kernel.(Do not go for open beta OxygenOS builds, they are abandoned.)
2-Paranoid Android 7.3.1(Nougat but it won't upset you)
3-If camera, VoWiFi and OTA updates are not important, OmniDragon.
Everyone's expectations are different. These are just mine experiences.
You should update your TWRP before flashing, i guess it is outdated; PA and OxygenOS contains their own firmware but for OmniDragon you can use Open Beta 39/OxygenOS 5.0.3 firmwares.
Click to expand...
Click to collapse
Thanks. Will check OxygenOS 5.0.3
Any reason why you did not suggest LineageOS?
Also will I be able to keep custom recovery and root with OxygenOS 5.0.3
hyperorb said:
Thanks. Will check OxygenOS 5.0.3
Any reason why you did not suggest LineageOS?
Also will I be able to keep custom recovery and root with OxygenOS 5.0.3
Click to expand...
Click to collapse
According to my experiences, unfortunately LineageOS 15.1 is not a daily driver on SD820 phones. Used it on Mi5 and OP3, both of them suffered with lag, overheating, shuttering, deep sleep not working sometimes (lost apx.%30 battery per night), bad camera quality. It is good rom, but this issues must be solved.
You can keep root and TWRP on OOS. Process:
1-Flash TWRP and boot it.
2-Make the wipes(dalvik/data/cache/system are must, if you want full wipe of userdata you can select internal storage too.
3-Install OxygenOS zip, custom kernel zip(optional) and latest Magisk beta zip(16.7 today).
Reboot and profit.
qhsusb_bulk said:
According to my experiences, unfortunately LineageOS 15.1 is not a daily driver on SD820 phones. Used it on Mi5 and OP3, both of them suffered with lag, overheating, shuttering, deep sleep not working sometimes (lost apx.%30 battery per night), bad camera quality. It is good rom, but this issues must be solved.
You can keep root and TWRP on OOS. Process:
1-Flash TWRP and boot it.
2-Make the wipes(dalvik/data/cache/system are must, if you want full wipe of userdata you can select internal storage too.
3-Install OxygenOS zip, custom kernel zip(optional) and latest Magisk beta zip(16.7 today).
Reboot and profit.
Click to expand...
Click to collapse
Thank you for helping with my queries.
So it's just like flashing a custom rom. Also If I wipe internal storage then the ROM zip file will also get wiped. Wonder how do I copy it then?
Last set of queries before I flash this coming weekend
- Whch TWRP ? Latest blu_spark should do ? (I remember blu_spark had specific TWRP for OP3_OP3T
- I remember reading about recovery getting overwritten when flashing OxygenOS.. Will it happen with full rom zip
- Any precautions you would like to suggest ?
hyperorb said:
Thank you for helping with my queries.
So it's just like flashing a custom rom. Also If I wipe internal storage then the ROM zip file will also get wiped. Wonder how do I copy it then?
Last set of queries before I flash this coming weekend
- Whch TWRP ? Latest blu_spark should do ? (I remember blu_spark had specific TWRP for OP3_OP3T
- I remember reading about recovery getting overwritten when flashing OxygenOS.. Will it happen with full rom zip
- Any precautions you would like to suggest ?
Click to expand...
Click to collapse
Yes, if you wipe internal storage, the rom will be wiped. But you can just copy it from your pc while you are in twrp.
Latest Blu_spark twrp works fine for me. Will work for you too.
If recovery is overwritten, you can just flash twrp again via fastboot. It won't be overwritten then.
I think there was a way that after you can avoid having to fastboot by just installing twrp again right after you have flashed oos rom and then reboot. But I am not quite sure if it works. Maybe someone else with experience can elaborate. Anyways, the fastboot method will definitely work.
@hyperorb , If you flash Magisk right after OOS, your recovery won't be replaced by Oxygen one.
For recovery, you can use Official TWRP or OmniDragon TWRP.
many thanks @qhsusb_bulk @Harsh862
will try wit latest blu_spark first but will also keep others handy. Will not refresh internal storage for now. Maybe once I get a bit comfortable with this part. Will revert once I update.
OP3 OOS 5.0.3
Attaching link in case someone else need
Easy breezy.
Thanks to @qhsusb_bulk @Harsh862 Upgraded to OOS 5.0.3
1) Backups ( whatsapp, titanium, nandroid)
2) Remove all security - pin , fingerprint
3) Reboot to recovery
4) Upgrade TWRP to 8.6.1 blu_stark
5) Reboot to recovery
6) Full wipe except internal storage
7) Flash OOS
8) Wipe dalvik / cache
-------
9) Flash Magisk 16 (1600). I'm not sure what happened but it froze at a point with some message about /Vendor . Screen went black which white LED on.
10) Waited for 30 sec
11) Manual reboot to recovery
12) Wipe dalvik / cache
13) Flash Magisk 15.6.3
14) Wipe dalvik / cache
15) Reboot to recovery
------
16) All Ok
17) Reboot to System
I've been on nitrogenos for half a year. Maybe your could give a try
hyperorb said:
Easy breezy.
Thanks to @[email protected] Upgraded to OOS 5.0.3
1) Backups ( whatsapp, titanium, nandroid)
2) Remove all security - pin , fingerprint
3) Reboot to recovery
4) Upgrade TWRP to 8.6.1 blu_stark
5) Reboot to recovery
6) Full wipe except internal storage
7) Flash OOS
8) Wipe dalvik / cache
-------
9) Flash Magisk 16 (1600). I'm not sure what happened but it froze at a point with some message about /Vendor . Screen went black which white LED on.
10) Waited for 30 sec
11) Manual reboot to recovery
12) Wipe dalvik / cache
13) Flash Magisk 15.6.3
14) Wipe dalvik / cache
15) Reboot to recovery
------
16) All Ok
17) Reboot to System
Click to expand...
Click to collapse
Is this offical Rom?
Yes. I downloaded from OnePlus forums
hyperorb said:
Easy breezy.
Thanks to @qhsusb_bulk @Harsh862 Upgraded to OOS 5.0.3
1) Backups ( whatsapp, titanium, nandroid)
2) Remove all security - pin , fingerprint
3) Reboot to recovery
4) Upgrade TWRP to 8.6.1 blu_stark
5) Reboot to recovery
6) Full wipe except internal storage
7) Flash OOS
8) Wipe dalvik / cache
-------
9) Flash Magisk 16 (1600). I'm not sure what happened but it froze at a point with some message about /Vendor . Screen went black which white LED on.
10) Waited for 30 sec
11) Manual reboot to recovery
12) Wipe dalvik / cache
13) Flash Magisk 15.6.3
14) Wipe dalvik / cache
15) Reboot to recovery
------
16) All Ok
17) Reboot to System
Click to expand...
Click to collapse
Step 9 happens to me everytime I flash OOS/OB. I simply wait for the white led to come on, press the Power button for 8+ seconds and phone switches off. Restart in recovery mode and flash Magisk. This time it will install.

Bootloop on every Magisk installation

Hi everyone,
I recently made a fresh install of the latest OOS ROM on my Onplus 5T (OOS 9.0.8). After reinstalling all the apps and data I tried to root the phone. My bootloader was already unlocked, so I just went on to flash TWRP (first tried the official TWRP 3.3.1 dumpling, and then the 3.3.1 blu_spark version). Then I tried to flash Magisk via TWRP (tried versions 19.2, 19.3, 19.4), and every time I try to reboot I get stuck on a black screen with the cyan led on, and I have to uninstall Magisk in order to reboot on the phone. Also the phone is encrypted, and I have a the Microsoft Intune Portal app installed to use some work apps, but I don't know if that can be the source of the problem.
If you have any idea on how to successfully flash Magisk, that would be amazing.
Thanks in advance :good:
I use the same version of ROM and magisk I use is canary build . Working fine. (even its not canary build I also can boot successfully)
you might need to check if some apps you install might cause this.
my recommendation is clear /data and starts fresh then root it before installing any apps. to see if it working fine or not.
also after you flash magisk do you try to wipe cache, dalvik-cache?
and how long are you waiting for its to boot? normally it would take more time than normal boot (without magisk)
Just connect to to ADB and delete vendor.. recovery.. rom.. radio.. antennaa.. ect everything. Get yourself a stock full rom and flash that through ADB. Then flash custom recovery, custom rom, gapps, custom kernel, magisk. thats it. find stock rom on manufacturers data server. I did this to a different phone I had but this is the way to 100% fix everything... by purging the phone to nothing. You can however do a twrp backup before doing so.
Thanks for the input, I will try first to reflash the ROM and root before installing any apps, and see if it works in order to avoid the long process of restoring all my data. I do wipe cache/dalvik cache before and after every flash. If that doesn't work I will try another time a clean flash and tell you if it worked.
I just reflashed the ROM and right after I flashed Magisk 19.3, then rebooted and it worked. Not sure what the issue was but the problem is now resolved. Thanks guys for the advice.

Stuck on spinning wheel after flashing Lineage and gapps

Hello,
I would like to install Lineage on my OnePlus5T, as the OxygenOS system does not seem to have an option for the Albanian language. Lineage does.
However, since Wednesday July 28, I have been trying and failing. Here are the steps:
1. Unlock bootloader (worked perfectly.)
2. Flash TWRP (No issue there either.)
3. Wipe Data, System, Dalvik, Cache (All okay so far...)
4. Flash Lineage and Gapps (both worked fine). I'm flashing lineage 18, with the pico gapps package for android 11.
5. Wipe dalvik and cache again, then reboot. But I got stuck on the spinning wheel. I had backed up all the data with TWRP, but apparently restoring it won't put me backk on OxygenOS. The backup must've been corrupted when copying to a computer.
I also erased system and vendor with fastboot, which wiped all else from the phone and then I tried again, still no luck.
I have tried flashing OxygenOS again, and that now gives me "zip trebble compatibility error, invalid zip file format".
But all partitions were empty, before flashing the system. What have I done wrong? Or what should/can I try to get the system installed?
Many thanks for any help... Sorry for the long message.
Hmm. Did you try without flashing GAPPS? How would your phone behave with system being flashed only?
dedq said:
Hmm. Did you try without flashing GAPPS? How would your phone behave with system being flashed only?
Click to expand...
Click to collapse
I feel that could work. However, just before I do, I should ask, does Lineage have the core google apps already installed? Google play, etc? If so, I'll give that a try at my earliest convenience.
Many thanks for the help.
Lineage doesn't have anything related to Google. It's totally debloated.
Give flashing without GAPPS a try and you will be able to identify the problem.
dedq said:
Lineage doesn't have anything related to Google. It's totally debloated.
Give flashing without GAPPS a try and you will be able to identify the problem.
Click to expand...
Click to collapse
If this works, how would I be able to get the google apps installed? Would I need to try a different gapps package, maybe?
Many thanks again, and sorry for all the questions.
First see if it works at all after flashing system and we will see after it.
Tobias101 said:
If this works, how would I be able to get the google apps installed? Would I need to try a different gapps package, maybe?
Many thanks again, and sorry for all the questions.
Click to expand...
Click to collapse
It's always worth an attempt to boot after flashing system only. If your phone boots you should reboot to recovery and flash your Gapps. Hopefully your phone wool boot again then.
KeinePanik said:
It's always worth an attempt to boot after flashing system only. If your phone boots you should reboot to recovery and flash your Gapps. Hopefully your phone wool boot again then.
Click to expand...
Click to collapse
Thank you so much, I'm going to give that a try when I can.
Hello,
The system booted without gapps, but didn't boot with it. So I downloaded the nano package, which was the only other available one for android 11, and it now works flawlessly.
Many thanks for all the help!

Categories

Resources