Do I need to Wipe Data ? - Magisk

I have a Google Edition Pixel XL running LineageOS 17.
I miss having root with came with LineageOS 16.
I know almost nothing about Magisk.
Will I need to wipe Data before installing Magisk?

No, wiping data not needed for rooting with Magisk.

Will I need to re-sideload Magisk after each LineageOS weekly update?

HowardZ said:
Will I need to re-sideload Magisk after each LineageOS weekly update?
Click to expand...
Click to collapse
read this discussion i love shrimp also weekly update? that too much work only update OS if it would benefit you somehow

I did the weekly LineageOS 17 update (via phone's settings), clicked to reboot, and Magisk is still there and working.
Titanium Backup and other rooted apps still have root.
Am happy with Magisk

I have one app, HEALOW (a medical app), which refuses to run - says my system is modified.
Magisk's safetynet bypass must not be good enough at this time.
But, it is only one app.

Related

[ROM] Mokee MK81.0 Z2 Pro OFFICIAL NIGHTLY Release

https://download.mokeedev.com/?device=z2pro
bug-reports
https://bbs.mokeedev.com/c/bug-reports
I strongly suggest install "PieBridge" to saving battery.
settings crash at select sim
https://streamable.com/3c5xf
Everything works good . When I was on 3.5.300 there was not LTE . With fw 3.5.259 all seems to be good . As far I feel good with this rom
I strongly suggest install "PieBridge" to saving battery.
There is problem with ctsprofile . I was managed to remove inbuilt root access but it was not helped to get safetynet .
downloading now ir now and mk 71 work on z2pro very smoothly and evwrything work well, just see how is mk 81, i love mk's kernal
mvp3 said:
I strongly suggest install "PieBridge" to saving battery.
Click to expand...
Click to collapse
What exactly is piebridge?
devilred666 said:
What exactly is piebridge?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=me.piebridge.brevent
mar.ur said:
There is problem with ctsprofile . I was managed to remove inbuilt root access but it was not helped to get safetynet .
Click to expand...
Click to collapse
This rom have Xposed integrated. So you never pass safetynet with this system
jhobc said:
This rom have Xposed integrated. So you never pass safetynet with this system
Click to expand...
Click to collapse
No , this rom has no xposed
mar.ur said:
No , this rom has no xposed
Click to expand...
Click to collapse
So download this Magisk module and see if it will fix the Safetynet
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
jhobc said:
So download this Magisk module and see if it will fix the Safetynet
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Click to expand...
Click to collapse
Yes , I was thinking about it . I uninstalled Magisk 16 and then installed Magisk 14 and safetynet fix V2 . It works . Later I will update to Magisk 16 and check if it works .
edit
Magisk 16 gets cts failed . If you want to pass seftynet on Mokee you should use Magisk 14
Could anyone who uses this rom tell me if there is option to set different ringtones for both cards? I mean native option in settings, not using some app.
I remember having it in RR 5.7.4 on my Moto X Play. However it's missing in AEX 4.6 (not only on ZUK).
And how about Slim Recents? KK Mokee had Slim Recents, but I've never used LP+ Mokee on any of my devices.
(deleted)
bug-reports
https://bbs.mokeedev.com/c/bug-reports
Gents,
Anyone tested this Mokee 8.1 (updating 11/03) and saw if Magisk 16 is operational concerning SafetyNet?
I ask it because on Mokee 8.1 (date 09/03) just works SafetyNet on Magisk 14 and with Universal SafetyNet Fix. For any superior Magisk version does not work the SafetyNet.
UPDATING: Magisk 16 still not working about SAFETYNET (ctsprofile) on Mokee 8.1.0 (date 12/03). I'm backing to Magisk 14.
Prefer Aegis to Brevent by Piebridge
mvp3 said:
https://play.google.com/store/apps/details?id=me.piebridge.brevent
Click to expand...
Click to collapse
Would very much like to see Aegis in 8 and not use Brevent Piebridge.
John
Folks, started getting "vendor image mismatch" after recent Nightly. Phone, Lawnchair, and some other apps keep stopping. Tried going back a few versions, no joy. Clear Dalvik, cache, data, and still no good.
Not clear if and how I should install a new vendor image. Many posts out there refer to installing a new one,where to get it, but say to install in the Vendor partition. But I can't find a vendor partition. Advice? (Help!)
John
JBoy53 said:
Folks, started getting "vendor image mismatch" after recent Nightly. Phone, Lawnchair, and some other apps keep stopping. Tried going back a few versions, no joy. Clear Dalvik, cache, data, and still no good.
Not clear if and how I should install a new vendor image. Many posts out there refer to installing a new one,where to get it, but say to install in the Vendor partition. But I can't find a vendor partition. Advice? (Help!)
John
Click to expand...
Click to collapse
Update: Wiped caches, data, system. Reinstalled latest Mokee 8.1 nightly and latest Gapps. All is working. But still getting the vendor image mismatch. Updated TWRP from 3.2.1-0 to 3.2.1-1 and now have capability to flash to vendor partition. But don't know what vendor.img to flash. Any suggestions?
John
JBoy53 said:
Update: Wiped caches, data, system. Reinstalled latest Mokee 8.1 nightly and latest Gapps. All is working. But still getting the vendor image mismatch. Updated TWRP from 3.2.1-0 to 3.2.1-1 and now have capability to flash to vendor partition. But don't know what vendor.img to flash. Any suggestions?
John
Click to expand...
Click to collapse
I've installed last night version , gapps and magisk 16 via 3.2.1-1 twrp . After that factory reset . All is ok .

Apps refuse to start because phone being rooted but it isn't!

At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.
Use Magisk I guess? Use it to hide root from that app.
Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.
ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs
Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?
I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).
ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...
Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid
Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?
After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...
probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.
Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.

Magisk Hide can't wok on latesd CIB mobile bank app

Hi!
The latest CIB mobile bank app (updated at: 2019-09-21) detect phone as rooted.
I tried with Magisk 19.3 and 19.4 beta too.
System is Android v7.1.2 and LineageOS 14.1-20171021-UNOFICIAL-KonstaKANG-Y560.
I've reinstalled the bank app (with reboot system), but nothing changed.
I've tried this steps too, it's brake Magisk installation. After that I must reinstall Magisk.
Please repair/update this on next version!
ANOka said:
Hi!
The latest CIB mobile bank app (updated at: 2019-09-21) detect phone as rooted.
I tried with Magisk 19.3 and 19.4 beta too.
System is Android v7.1.2 and LineageOS 14.1-20171021-UNOFICIAL-KonstaKANG-Y560.
I've reinstalled the bank app (with reboot system), but nothing changed.
I've tried this steps too, it's brake Magisk installation. After that I must reinstall Magisk.
Please repair/update this on next version!
Click to expand...
Click to collapse
Sadly the most safe way to use banking apps is on a stock device without root
([emoji3590]09-09-18[emoji3590])
Works fine on latest Canary after hiding Magisk Manager (settings -> Hide Magisk Manager).
Like above, I tested the app and it doesn't detect root on my device (OP3T, custom Pie ROM, Magisk Canary build 19402 with hidden Manager 237). Magisk can hide from the app, so something about your setup is the issue.
Didgeridoohan said:
...Magisk Canary build 19402 with hidden Manager 237...
Click to expand...
Click to collapse
Where can I download?
ANOka said:
Where can I download?
Click to expand...
Click to collapse
If you've already tried v19.4 beta, there's practically no difference (especially regarding MagiskHide).
Didgeridoohan said:
If you've already tried v19.4 beta, there's practically no difference (especially regarding MagiskHide).
Click to expand...
Click to collapse
I've tried, not working. (See the first open post!)
ANOka said:
I've tried, not working. (See the first open post!)
Click to expand...
Click to collapse
I know, so my statement was made to let you know that you might not need the Canary build at this very moment (since there's currently practically no difference between the builds).
Anyway, take a look here for help on getting the app running:
https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

The right A12 ROMs rooting procedure

After searching the forum thoroughly, trying multiple found solutions and trying to find the answer on my own I decided to ask here. What is the right procedure to clean flash A12 AOSP-based roms and getting root?
Some time ago, after updating to A11 rom, I noticed I can't use Magisk the way I used to to root my device - 'no ramdisk' status made me forget about rooting for a while. Now I want it back at any cost. This is why I want you to answer some of my questions, including the one above:
1. Is 'ramdisk: no' status caused by A11 and above versions?
2. Is there a way to have ramdisk status 'yes' on A12 ROM to root the device without having to patch boot.img?
3. Magisk installation doc has totally different way of rooting in my situation. According to it, for ramdisk status 'no' the only solution is 'Magisk in Recovery'. However, every time I saw someone talk about no ramdisk magisk patching, they were patching the boot image - it works fine and is even suggested by Magisk app. Who is wrong here and which solution is the right one?
4. Is there a way to get SafetyNet to pass on patched boot.img? Is there a way to get it to pass on a rooted A12 rom?
5. Some time ago, I have accidentally flashed european vendor instead of chinese one (I own chinese K20 Pro). I had no problems with it so I ran it for a few months and then flashed it back to chinese. Might this be the source of ramdisk issue?
Big thank you to anyone who replies. I have no important data on my device so there is no need for a data-safe solution. I feel like existing flashing/rooting guides seem outdated as they mention A10 at best. After more than 2 years of owning this device I still love it and am not going to replace it anytime soon and I hope there are still people like me! Cheers!
deadw0lf said:
After searching the forum thoroughly, trying multiple found solutions and trying to find the answer on my own I decided to ask here. What is the right procedure to clean flash A12 AOSP-based roms and getting root?
Some time ago, after updating to A11 rom, I noticed I can't use Magisk the way I used to to root my device - 'no ramdisk' status made me forget about rooting for a while. Now I want it back at any cost. This is why I want you to answer some of my questions, including the one above:
1. Is 'ramdisk: no' status caused by A11 and above versions?
2. Is there a way to have ramdisk status 'yes' on A12 ROM to root the device without having to patch boot.img?
3. Magisk installation doc has totally different way of rooting in my situation. According to it, for ramdisk status 'no' the only solution is 'Magisk in Recovery'. However, every time I saw someone talk about no ramdisk magisk patching, they were patching the boot image - it works fine and is even suggested by Magisk app. Who is wrong here and which solution is the right one?
4. Is there a way to get SafetyNet to pass on patched boot.img? Is there a way to get it to pass on a rooted A12 rom?
5. Some time ago, I have accidentally flashed european vendor instead of chinese one (I own chinese K20 Pro). I had no problems with it so I ran it for a few months and then flashed it back to chinese. Might this be the source of ramdisk issue?
Big thank you to anyone who replies. I have no important data on my device so there is no need for a data-safe solution. I feel like existing flashing/rooting guides seem outdated as they mention A10 at best. After more than 2 years of owning this device I still love it and am not going to replace it anytime soon and I hope there are still people like me! Cheers!
Click to expand...
Click to collapse
Although Magisk official guide on Github is not clear about, for MIUI you should patch boot.img, not recovery, and do not pay attention to Ramdisk no.
However, when patching boot.img, watch to the log window and you will see it reports there that it found Ramdisk
And that procedure works fine on A11 as well - I have it (MIUI 12.5.2 on my side)
I suppose you have the official A11 and you installed over custom A12 ROM).
Old Magisk v23 was released before A12, hence you should IMO go for the new Canary or Alpha 23016
Btw, you will be IMO better askung in the Magisk General XDA thread
zgfg said:
Although Magisk official guide on Github is not clear about, for MIUI you should patch boot.img, not recovery, and do not pay attention to Ramdisk no (when patching boot.img, watch to the log window and you will see it reports that it found Ramdisk)
And that procedure works fine on A11 as well - I have it (I suppose you have the official A11 and you installed over custom A12 ROM)
However, old Magisk v23 was released before A12, hence you should IMO go for the new Canary or Alpha 23016
Btw, you will be IMO better askung in the Magisk General XDA thread
Click to expand...
Click to collapse
Thank you for replying.
I am aware of Magisk Canary, I used it to root my current A12 rom. Yes, I flashed it over the latest chinese MIUI firmware. Is there any way to pass SafetyNet with it though?
deadw0lf said:
Thank you for replying.
I am aware of Magisk Canary, I used it to root my current A12 rom. Yes, I flashed it over the latest chinese MIUI firmware. Is there any way to pass SafetyNet with it though?
Click to expand...
Click to collapse
If you are on Canary 23016 (latest), you must enable Zygisk, and reboot
Then enable Enforce DenyList and go to Configure DenyList, enable Show System and OS apps, find Google Play Services and checkmark com.google.android.gms and
com.google.android.gms.unstable, and reboot again
If you were on the official, certified ROM, that would be enough to pass SafetyNet (since new Magisk app has no more the built-in SN checker, use one from PlayStore like YASNAC)
With your custom ROM you would probably need Universal Safety Net Fix= USNF 2.2.1 (latest).
Maybe even Magisk Hide Props Config (if USNF not enough) to spoof your unofficial/not Google certified ROM fingerprints - you will need to figure out (pain in the ass with custom ROMs)
zgfg said:
If you are on Canary 23016 (latest), you must enable Zygisk, and reboot
Then enable Enforce DenyList and go to Configure DenyList, enable Show System and OS apps, find Google Play Services and checkmark com.google.android.gms and
com.google.android.gms.unstable, and reboot again
If you were on the official, certified ROM, that would be enough to pass SafetyNet (since new Magisk app has no more the built-in SN checker, use one from PlayStore like YASNAC)
With your custom ROM you would probably need Universal Safety Net Fix= USNF 2.2.1 (latest).
Maybe even Magisk Hide Props Config (if USNF not enough) to spoof your unofficial/not Google certified ROM fingerprints - you will need to figure out (pain in the ass with custom ROMs)
Click to expand...
Click to collapse
This is exactly what I needed, thank you!
I dont have this model phone but i faced the same problem, i just flashed ArrowOS S along with magisk but i didnt realised it has now ramdisk no, before i was using AICP and it has ramdisk yes, so i installed latest version of magisk and the system updated but i dont have root anymore, what can i do?
I use OrangeBox for flashing
Edit: also it does replace the custom recovery?

How to root OSS and still pass safetynet checks (2022)

So I just bought a OnePlus 7T Pro McClaren Edition and its great
But I would really like to have it rooted.
I currently finally have stock rom installed again (after many frustrating hours) and am now passing the safetynet check.
I can:
1. Install Magisk (as an apk),
2. Patch boot.img
3. Unlock oem
4. Flash the patched img file
This works and I can have root access.
So far, unless I flash the original boot.img and wipe data again, I cannot lock OEM again (without seeing the corrupted data message).
Also, without locking oem, I'd keep getting the boot warning about bootloader being unlocked (which I guess is not so bad).
Seems like unless I have stock rom flashed, the safetynet check CTS test fails.
Anyways, I'm trying to find a way to root OOS and still pass the safetynet checks.
Thanks.
You need to enable Zygisk in Magisk, configure DenyList (walletfcrel, walletnfrćrelrimes_lifeboat and gapps and gservices), clear all data from Play Store, Play Services and GPay and reboot
Hi, Gpay updated to Google Wallet this method no longer works.
slapman said:
Hi, Gpay updated to Google Wallet this method no longer works.
Click to expand...
Click to collapse
Hi, yes, it does, i can confirm on both Oneplus 7 and Oneplus 7t Pro. You need to install universalsafetynetfix magisk module additionally and don't forget to wipe the data of gpay, google play and play services
DartGerion said:
Hi, yes, it does, i can confirm on both Oneplus 7 and Oneplus 7t Pro. You need to install universalsafetynetfix magisk module additionally and don't forget to wipe the data of gpay, google play and play services
Click to expand...
Click to collapse
At the time it didn't, and I had to find the the updated safetnet fix especially after updating to Android 12 and I custom ROM crDroid 13.
What Android version /oos version are you using ?

Categories

Resources