Hi,
I'm using Havoc OS on my redmi note 3 which is on Android 11. I'm also using the latest Magisk. Currently, I need to use Google health connect, which req my phone to be encrypted. So can I go to settings and encrypt my phone? Or must I uninstall Magisk, encrypt, and then reinstall backMagisk?
I have been searching for this info but most of them are old posts and each mtd is different.
Hope someone can give an updated solution.
Thanks.
Related
Hi, All!
Are there any custom ROMs that have Android Pay working? I don't necessarily need root access; however, wouldn't mind having it with ability to turn it off.
Thanks!
PashaF said:
Hi, All!
Are there any custom ROMs that have Android Pay working? I don't necessarily need root access; however, wouldn't mind having it with ability to turn it off.
Thanks!
Click to expand...
Click to collapse
Lineage OS works fine. Rooted with magisk so I pass safetynet.
I was flashing the official Lineage OS with Magisk v11.1 . i was install the MagiskManager and the phh superuser also. However if i check my device status on MagiskManager the SafetyNet does not pass. It just looping and looping... Iam having MultiROM and my Internal ROM is OOS4.0.2 and Magisk works well, it giving SafetyNet pass.
So why does not work with official LineageOS??
Also was trying different LOS ROMs not just the official but none of them working.
Maybe you need to remove the unlocked bootloader notification before the phone boots.
Someone i read a post and this solved his prob.
Maybe try that. The process to do that in guides section
Navi44 said:
Maybe you need to remove the unlocked bootloader notification before the phone boots.
Someone i read a post and this solved his prob.
Maybe try that. The process to do that in guides section
Click to expand...
Click to collapse
Thanks.
However i was checking the guide section but have not find the tutorial about removing the unlocked bootloader notification. Only the dm-verity notification removal i have found what i have got already.
A link would be appreciated :good::victory:
Hi guys how I pass the safetynet?
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
tyler19820201 said:
Thanks.
However i was checking the guide section but have not find the tutorial about removing the unlocked bootloader notification. Only the dm-verity notification removal i have found what i have got already.
A link would be appreciated :good::victory:
Click to expand...
Click to collapse
UPDATE
I have solved the issue. I am using multiROM and have realized ONLY the Internal ROM getting the safetynet pass!! So i was swap my internal OOS4.0.2 ROM with the Lineage OS. And now the Lineage is the internalROM and the oxygen is the secondary. The Lineage getting safetynet pass but the oxygen does not. Before swapping Oxygen having pass but Lineage does not...
Hope will help this who want to set it up in the future.
Hi,
Recently I installed lineageos android 10 on Samsung Galaxy S3 Neo Duos
Then tried to use magisk to gain root privileges but simply can't do that
SafetyNet Check: All False
Installation Failed: UnSupported / UnKnown Image Format
I search about this problem and found the next link
LineageOS is dropping its own superuser implementation, making Magisk the de facto solution
I read it but can not figure why lineageos team drop superuser, but this is not my problem
I just need to know I there any way to root my device Even if without magisk
Or I Will need to downgrade to android 9
Also if the answer is I must downgrade to android 9
Does this mean any new rom start from android 10 + will not have any way to gain root privileges ???
Thanks.
---------------------------------------------------------
To 73sydney
First: Thank You
I take the next steps
Download lineage From Here
Install TWRP latest version TWRP-3.3.1-1-s3ve3g.img.tar With Odin3_v3.14.1
Use TWRP to install lineage_s3ve3gds: and everything worked correctly
Download Magisk-v20.3.zip
Copy it to my sd card
Open Device In Recovery mode and then use TWRP to install magisk
and it does not show any error messages
Install magisk.apk
Open magisk app
Show me: Magisk is not installed
Press Checking SafetyNet Status
Show CtsProfile: false, basicIntegrity: false
This is how I install android 10 and Magisk
Nothing to do with Android 10 as we just got LineageOS 17 on my Note 4, and i have Magisk running fine, only needed to fix CTS issue with MagiskHide Props Config as per following video
https://youtu.be/wKYC0r-m0Mo
It could be the way youre flashing magisk, or the way the ROM is built, because im just guessing because the Note 4 is unofficial LineageOS, the S3 build would be too. Frankly im surprised anyone would bother with the S3..
To get to the main issue though, lets get the basics... just how are you trying to install Magisk?
Just found your devices forum, theres like 3 threads/guys spraying LineagesOS builds into it. Perhaps tell them to work together for starters....
And really ideally they'd test for the possibility of rooting and root solutions before releasing because gets what question number 1 is going to be, how do i root this? Again, perhaps get them to work on it together
LineagesOS dropped their SU simply because its outdated, doesnt do what Magisk can do (modular addons to customise) and prolly mostly, its not used by anyone
I edit my post to explains all steps i take to install lineageos & magisk
Thank you for your reply
First I Edit my post to all steps you asked
Second: I am not an android professional
I tried to figure out what you means but can not.
I just want to know steps to gain root access
Please Notice: OEM option does not appear in developer options
So please if you can give me a link/resources to know how to root my device [Samsung Galaxy S3 Neo Duos With lineageOs 17.1] this will be very helpful
Thanks.
It's perfectly possible that it isn't possible to root your ROM with Magisk. It depends on how it's created... If it's using fake dts Magisk won't work. References:
https://twitter.com/topjohnwu/status/1226644269261213696?s=20
It was the same case for LineageOS 17.1 on the Nexus 4, but that was fixed. See the ROM thread for more details:
https://forum.xda-developers.com/nexus-4/development/rom-lineageos-15-1-t3758779
None of this is something that you as the user can do anything about. It has to be fixed by the developer, so let them know (if it is a case of the ROM using a fake dts).
Magisk 20.4 with the 7.5.1 manager is working perfectly in a Nexus 5 with LineageOS 17.1.
Hi everyone! I have a little problem. I installed magisk cause I needed root to activate my volte, and then uninstalled magisk manager and flashed twrp again, however, my banking app still say I am rooted. Tryed to use magisk hide but my bank app still see it.
Are there some more files I have to delete to make my banking app work again? Why it still see root if uninstalled magisk?
Same problem here, my rom is:
[ROM][7.0][TW][Exynos][Stable]Refined Nougat N7FE Port 6.0
Welcome to the Galaxy note 4 Nougat project ONLY FOR Galaxy note 4 Exynos WARNING : PLEASE DO NOT PROCEED TO DOWNLOAD UNTIL YOU HAVE READ THE ENTIRE POST ! Some information you should know.. This is a full Note 7FE firmware port...
forum.xda-developers.com
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?
Hi guys, coming from a OnePlus 5t, got my m11u and finally waited the 168hrs! Following the instructions on the first post and finally got the bootloader unlocked, I found that was the hardest part, as I had to figure out on my own how to set up adb and the unlock tool etc. But thanks to YouTube I got through and now on EU 13.0.9.0 stable.
During the first week waiting for the unlock, I was hopeful of seeing if I can just enjoy the CN MIUI 13 ROM...deleted as many CN apps, installed Google Play etc and it seemed to be going well....until I noticed the huge problem w getting call and msg notifications. That was already a dealbreaker and seems like no real solution but to continue with a new ROM.
Now using the EU 13.0.9, everything seems great and working well. Except, I am trying to install Vanced youtube but cannot! On the CN ROM it was simply to turn off MIUI optimization in dev options, but xiaomi.eu has removed that option (cannot get the toggle even by pressing reset multiple times). What are my options at this point? Am I left with only option to root the device?
if so, I will try to learn to do it, but I'm hoping someone can point me towards the correct path. There is a how to thread here but it seems outdated as it refers to MIUI 12 and not 13(a12). So far from what I understand:
- a12 root is done with latest magisk v24+
- however v24 no longer use hide magisk and need to use zygisk and a deny list
- bear in mind I don't understand what the above means yet
- from my current status (newly installed EU ROM), what steps do I take?
- download magisk manager APK and install on phone
- make a patched boot.img - DO I USE THE BOOT.IMG FROM THE EXACT EU ROM I FLASHED?
- use fastboot to boot the patched boot.img?
- after this most tutorials tell me to download hide magisk and such, but v24 will be different
- where to go from here to install Vanced root version, and am I missing any steps? After root, will it affect my banking etc?
any help appreciated! Cheers
VinillaIce82 said:
Hi guys, coming from a OnePlus 5t, got my m11u and finally waited the 168hrs! Following the instructions on the first post and finally got the bootloader unlocked, I found that was the hardest part, as I had to figure out on my own how to set up adb and the unlock tool etc. But thanks to YouTube I got through and now on EU 13.0.9.0 stable.
During the first week waiting for the unlock, I was hopeful of seeing if I can just enjoy the CN MIUI 13 ROM...deleted as many CN apps, installed Google Play etc and it seemed to be going well....until I noticed the huge problem w getting call and msg notifications. That was already a dealbreaker and seems like no real solution but to continue with a new ROM.
Now using the EU 13.0.9, everything seems great and working well. Except, I am trying to install Vanced youtube but cannot! On the CN ROM it was simply to turn off MIUI optimization in dev options, but xiaomi.eu has removed that option (cannot get the toggle even by pressing reset multiple times). What are my options at this point? Am I left with only option to root the device?
if so, I will try to learn to do it, but I'm hoping someone can point me towards the correct path. There is a how to thread here but it seems outdated as it refers to MIUI 12 and not 13(a12). So far from what I understand:
- a12 root is done with latest magisk v24+
- however v24 no longer use hide magisk and need to use zygisk and a deny list
- bear in mind I don't understand what the above means yet
- from my current status (newly installed EU ROM), what steps do I take?
- download magisk manager APK and install on phone
- make a patched boot.img - DO I USE THE BOOT.IMG FROM THE EXACT EU ROM I FLASHED?
- use fastboot to boot the patched boot.img?
- after this most tutorials tell me to download hide magisk and such, but v24 will be different
- where to go from here to install Vanced root version, and am I missing any steps? After root, will it affect my banking etc?
any help appreciated! Cheers
Click to expand...
Click to collapse
- In xiaomi.eu rom, u didnt need to turn off miui opti, they already tweak the rom, so u can install vanced normally (no-root version)
how to root
Installation
The Magic Mask for Android
topjohnwu.github.io
how to hide root : 2:52
- if any app detect root, u can add it in deny list
hungragezone said:
- In xiaomi.eu rom, u didnt need to turn off miui opti, they already tweak the rom, so u can install vanced normally (no-root version)
how to root
Installation
The Magic Mask for Android
topjohnwu.github.io
how to hide root : 2:52
- if any app detect root, u can add it in deny list
Click to expand...
Click to collapse
now that you mentioned it, i went and tried to install it again. I played with some permission settings and now it does work! thank goodness now i don't have to deal with rooting.
thanks!