Related
Anyone know if I need to downgrade to MM and re-flash twrp to get Magisk working for systemless root?
I can install SuperSU but Magisk automatically reboots the phone while flashing the Zip file in twrp.
Zekisu said:
Anyone know if I need to downgrade to MM and re-flash twrp to get Magisk working for systemless root?
I can install SuperSU but Magisk automatically reboots the phone while flashing the Zip file in twrp.
Click to expand...
Click to collapse
No Magisk possible on N.
Read up on it here: https://forum.xda-developers.com/honor-8/how-to/info-loop-support-7-0-emui-magisk-t3578091
N01tra said:
No Magisk possible on N.
Read up on it here: https://forum.xda-developers.com/honor-8/how-to/info-loop-support-7-0-emui-magisk-t3578091
Click to expand...
Click to collapse
Cool ty for your reply.
Also all versions after 11.1 break the fingerprint sensor.
Magisk kernel is currently being worked on .ETA 10 days , check the post in the Dev section
+
Does systemless xposed work on nougat? If so, please provide the links.
BELIEVER PK said:
Does systemless xposed work on nougat? If so, please provide the links.
Click to expand...
Click to collapse
Yes,it does,just install magisk and in downloads search for Xposed modul.Then install and reboot your phone.
Thanks bud.
Works flawlessly since V89.0. Available here in OP https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Right now I'm using ELITE ROM V7. 3 and i have rooted supersu but i want to install Magisk for using banking apps n to hide root for some apps. Please guid me step by step to install magisk on elite rom v7. 3
RedSkull23 said:
Works flawlessly since V89.0. Available here in OP https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Click to expand...
Click to collapse
Alright. Do apps like Titanium Backup, gravity box and other xposed modules work, just like they do on supersu?
nagrale.prem said:
Right now I'm using ELITE ROM V7. 3 and i have rooted supersu but i want to install Magisk for using banking apps n to hide root for some apps. Please guid me step by step to install magisk on elite rom v7. 3
Click to expand...
Click to collapse
Completely uninstall SuperSU, flash through TWRP the unsu.zip available here on XDA thanks to osm0sis, and then flash Magisk.
BELIEVER PK said:
Alright. Do apps like Titanium Backup, gravity box and other xposed modules work, just like they do on supersu?
Click to expand...
Click to collapse
Of course they works. Every module works, but not GravityBox. It can't work on an heavy Android modification like EMUI as far as I know, so unless that there's a way to make it work while on SuperSU, it isn't possible to use it on EMUI (as stated in module description on Xposed repo).
Failed while flashing magisk zip.
-Mounting /System, /Vendor, /cache, /data
-Device platform: arm64
-Constructing environment
-/data/magisk.img detected!
-Mounting /data/magisk.img to /magisk
-Found Boot Image: /dev/block/mmclk0p34
-Unpacking boot image
-Checking ramdisk status
! Boot image patched by other programs!
! Please restore stock boot image
Updater process ended with ERROR:1
Error installing zip file '/sdcard/MagiskManager/Magisk-v13.3.zip'
Updating partition details...
...done
Need solutions for above error please...
nagrale.prem said:
! Boot image patched by other programs!
! Please restore stock boot image
Updater process ended with ERROR:1
Click to expand...
Click to collapse
Your boot.img looks already patched by a superuser app... You didn't uninstalled SuperSU in the right way, or you're trying to flash Magisk over SuperSU. As suggested in the log, restore stock boot.img of your firmware before trying to flash Magisk, else it won't work. (Plus, try to flash latest version, V15.3, other than 13)
RedSkull23 said:
Your boot.img looks already patched by a superuser app... You didn't uninstalled SuperSU in the right way, or you're trying to flash Magisk over SuperSU. As suggested in the log, restore stock boot.img of your firmware before trying to flash Magisk, else it won't work. (Plus, try to flash latest version, V15.3, other than 13)
Click to expand...
Click to collapse
Can you please give me link of stock boot.img of honor 6x and give steps to Uninstall supersu
nagrale.prem said:
Can you please give me link of stock boot.img of honor 6x and give steps to Uninstall supersu
Click to expand...
Click to collapse
I've already told you how to remove supersu in the previous page dude, you need to read, not going blind.
The boot.img isn't a common file equal in every firmware, it differs by build number, region, version... begin with writing here your actual build number for extended, and I'll look for the relative boot.img (if it's available here on XDA).
RedSkull23 said:
Your boot.img looks already patched by a superuser app... You didn't uninstalled SuperSU in the right way, or you're trying to flash Magisk over SuperSU. As suggested in the log, restore stock boot.img of your firmware before trying to flash Magisk, else it won't work. (Plus, try to flash latest version, V15.3, other than 13)
Click to expand...
Click to collapse
RedSkull23 said:
I've already told you how to remove supersu in the previous page dude, you need to read, not going blind.
The boot.img isn't a common file equal in every firmware, it differs by build number, region, version... begin with writing here your actual build number for extended, and I'll look for the relative boot.img (if it's available here on XDA).
Click to expand...
Click to collapse
I own honor 6x India version. I understand Uninstal process for supersu. Right now I'm using ELITE ROM V7.3 so i don't know bulid no. N all stuff sorry. I know you will help me
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
quantumcity said:
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
Click to expand...
Click to collapse
I had the same problem I uninstalled Xposed framework rebooted now the the safetynet check is Ok
airdi1 said:
I had the same problem I uninstalled Xposed framework rebooted now the the safetynet check is Ok
Click to expand...
Click to collapse
As I mentioned in the post, I do not have Xposed framework
quantumcity said:
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
Click to expand...
Click to collapse
What version of Magisk did you flash? Flash Magisk 16.4 only. Older versions don't support the OnePlus 6 and flashing newer versions has caused many weird problems. Flash Magisk uninstaller, reboot to TWRP, then flash Magisk 16.4. Once it gets going it will tell you that it can update the Magisk version. Let it update that way. Flashing newer versions causes many weird problems bit letting it update always seems to work.
run the uninstaller magisk .zip then check if safety net passed, might be something unrelated?
im on 5.1.9 with SN passing with TWRP and Magisk
tabletalker7 said:
What version of Magisk did you flash? Flash Magisk 16.4 only. Older versions don't support the OnePlus 6 and flashing newer versions has caused many weird problems. Flash Magisk uninstaller, reboot to TWRP, then flash Magisk 16.4. Once it gets going it will tell you that it can update the Magisk version. Let it update that way. Flashing newer versions causes many weird problems bit letting it update always seems to work.
Click to expand...
Click to collapse
I have magisk 16.7
virtyx said:
run the uninstaller magisk .zip then check if safety net passed, might be something unrelated?
im on 5.1.9 with SN passing with TWRP and Magisk
Click to expand...
Click to collapse
How do I do that? Do you have a link to this zip?
quantumcity said:
I have magisk 16.7
Click to expand...
Click to collapse
Google "Magisk uninstaller". Flash that file in TWRP. Then reboot to recovery. Then flash Magisk 16.4
quantumcity said:
How do I do that? Do you have a link to this zip?
Click to expand...
Click to collapse
its in the magisk official thread.
virtyx said:
its in the magisk official thread.
Click to expand...
Click to collapse
Yes
So for me, the safety net check passes in the Magisk app but I am not able to access Google tez which tells me that my device is rooted or custom ROM has been changed. Using Magisk v 16.0
16.4... notice the 4
Just fyi I'm on 5.19 and using Magisk 16.0 and safety net passes just fine. Use Google pay daily and play store shows certified.
I hide everything Google related in magisk hide just to be sure
Eric214 said:
16.4... notice the 4
Click to expand...
Click to collapse
I know. What I meant is safety net passes everywhere except for Google Tez app. Don't know why!
I have attached the screenshots below. And I understand that I'm using Magisk 16.0
skr975 said:
I know. What I meant is safety net passes everywhere except for Google Tez app. Don't know why!
Click to expand...
Click to collapse
Do you have it hidden in Magisk? Google Pay works here if you hide it.
Okay, so I have uninstalled magisk, don't have root, and I still can't use google pay, install netflix, use my bank's app, etc.
No root, no magisk, no xposed, no custom recovery.
How can I figure out why all these apps won't work?
quantumcity said:
Okay, so I have uninstalled magisk, don't have root, and I still can't use google pay, install netflix, use my bank's app, etc.
No root, no magisk, no xposed, no custom recovery.
How can I figure out why all these apps won't work?
Click to expand...
Click to collapse
In playstore / settings are you uncertified? After unlocking bootloader I was and couldn't use Google pay. I flashed magisk and it was still uncertified so I cleared playstore app data. Now the phone says certified and Google pay works for me.
I suggest you flash 16.4 magisk and clear app data in playstore to see if you can get them working. Also you will need a different app than magisk manager to check safety net ATM as it will come back with "invalid response"
Sent from my OnePlus6 using XDA Labs
Read the full page of OnePlus 9 thread! No firmware and boot files were found
iSkyJIE said:
Read the full page of OnePlus 9 thread! No firmware and boot files were found
Click to expand...
Click to collapse
What're you on about?
TheKnux said:
What're you on about?
Click to expand...
Click to collapse
Did not find the T-Mobile version of OnePlus 9 firmware or boot.img! Need boot files to root this phone！
You pull the boot.img yourself
iSkyJIE said:
Did not find the T-Mobile version of OnePlus 9 firmware or boot.img! Need boot files to root this phone！
Click to expand...
Click to collapse
There's ways to pull the boot.img using adb/fastboot commands once your bootloader is unlocked. Then all you have to do is patch it using Magisk and flash it in fastboot.
TheKnux said:
You pull the boot.img yourself
There's ways to pull the boot.img using adb/fastboot commands once your bootloader is unlocked. Then all you have to do is patch it using Magisk and flash it in fastboot.
Click to expand...
Click to collapse
Thank you for your reply！
My bootloader has been unlocked! But I don't know how to extract it to boot.img
You don't specifically need the T-Mobile boot.img to root your phone. Get the boot.img from this post: https://forum.xda-developers.com/t/root-oneplus-9.4253651/page-4#post-84874313
Install the Magisk App on your phone
Reboot into fastboot
fastboot boot boot11244AAmagisk.img
Once your phone boots, open the Magisk app
Ignore any message about it needing to setup
Install Magisk with a direct install
Reboot and now your phone should be rooted
I've tested this on my one T-Mobile OnePlus 9 and it works perfectly, even passing SafetyNet
Lomeli12 said:
You don't specifically need the T-Mobile boot.img to root your phone. Get the boot.img from this post: https://forum.xda-developers.com/t/root-oneplus-9.4253651/page-4#post-84874313
Install the Magisk App on your phone
Reboot into fastboot
fastboot boot boot11244AAmagisk.img
Once your phone boots, open the Magisk app
Ignore any message about it needing to setup
Install Magisk with a direct install
Reboot and now your phone should be rooted
I've tested this on my one T-Mobile OnePlus 9 and it works perfectly, even passing SafetyNet
Click to expand...
Click to collapse
Thank you,
I'll try extracting the 11.2.2.2AA international version of boot, which I'm currently version 11.2.2.2
If anyone has the stock oneplus9
T-mobile 11.2.2.2 boot.img please kindly share.In haste, trying to root my phone I accidentally flashed a patched 11.2.2.2 boot.img from the eu version. It got root but now I can't pass safety check. I would like to restore stock T-Mobile boot.img
inspron said:
If anyone has the stock oneplus9
T-mobile 11.2.2.2 boot.img please kindly share.In haste, trying to root my phone I accidentally flashed a patched 11.2.2.2 boot.img from the eu version. It got root but now I can't pass safety check. I would like to restore stock T-Mobile boot.img
Click to expand...
Click to collapse
MagiskHide enabled?
TheKnux said:
MagiskHide enabled?
Click to expand...
Click to collapse
Yes.
inspron said:
Yes.
Click to expand...
Click to collapse
Not sure then. I'm at work right now so I'm kinda tied up for helping you out until I get home.
TheKnux said:
Not sure then. I'm at work right now so I'm kinda tied up for helping you out until I get home.
Click to expand...
Click to collapse
Thank you. I am hopping that the problem will be fixed when I have access to a stock boot.img from T-Mobile oneplus9.
Attached is my stock 11.2.2.2 boot.img from T-Mobile oneplus 9 (LE2117).
Hope it helps you out.
boot.img
drive.google.com
inspron said:
If anyone has the stock oneplus9
T-mobile 11.2.2.2 boot.img please kindly share.In haste, trying to root my phone I accidentally flashed a patched 11.2.2.2 boot.img from the eu version. It got root but now I can't pass safety check. I would like to restore stock T-Mobile boot.img
Click to expand...
Click to collapse
Magisk 22.1 stable, has a safety net api error. Not sure if that is your issue. Mine fails in magisk app but passes on safety net test apk.
Jg1234 said:
Magisk 22.1 stable, has a safety net api error. Not sure if that is your issue. Mine fails in magisk app but passes on safety net test apk.
Click to expand...
Click to collapse
Wow! Thank you. Failed Magisk but It does pass this https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest
Jg1234 said:
Attached is my stock 11.2.2.2 boot.img from T-Mobile oneplus 9 (LE2117).
Hope it helps you out.
boot.img
drive.google.com
Click to expand...
Click to collapse
Thank you stranger!!!
Jg1234 said:
Magisk 22.1 stable, has a safety net api error. Not sure if that is your issue. Mine fails in magisk app but passes on safety net test apk.
Click to expand...
Click to collapse
I am curious, when we get an incremental update from T-mobile, we will be able to apply the update if we pass Safety net or it's not related?
inspron said:
I am curious, when we get an incremental update from T-mobile, we will be able to apply the update if we pass Safety net or it's not related?
Click to expand...
Click to collapse
I'm not to sure on that one.. I came from the 6t t-mobile version and it had the local upgrade option.
inspron said:
I am curious, when we get an incremental update from T-mobile, we will be able to apply the update if we pass Safety net or it's not related?
Click to expand...
Click to collapse
No, T-mobile doesn't allow update if bootloader unlocked. has nothing to do with safetynet. If you look in system after unlocking your bootloader and rebooting you will see system update no longer avail.
Jg1234 said:
Attached is my stock 11.2.2.2 boot.img from T-Mobile oneplus 9 (LE2117).
Hope it helps you out.
boot.img
drive.google.com
Click to expand...
Click to collapse
11.2.2.2 AA International’s BOOT is only 96MB, and the T-MOBILE 11.2.2.2 BOOT you provide is 192MB, maybe this is the difference.
Hey guys, haven't been in the root scene for a few years now and I'm thinking about getting back into it.
Is xposed still a thing?
I have updated to android 12.. will I need to revert in order to do any flashing?
Anyone just running stock with root/xposed? Unless I see a compelling ROM I feel like this would be my choice. How do you like it? Does everything work correctly? Is there a way to add small features like 'hold power for flashlight,' stuff like that?
Do you recommend a particular ROM? What is compelling about it over stock?
Thanks!
I used this guide and running stock android 10 with Magisk root:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I am using:
TWRP 3.4.0.0
Magisk 21.4
Magisk Manager 8.0.7
Riru 23.5
Riru - EdXposed 0.5.2.1_4677
EdXposed Manager 4.6.2
All running with No problems!
systemshock869 said:
Hey guys, haven't been in the root scene for a few years now and I'm thinking about getting back into it.
Is xposed still a thing?
Click to expand...
Click to collapse
Well, kind of. It now exists as a Magisk module. You need to install Riru module and LSposed module to get an "Xposed like" feature.
BUT, latest Magisk versions (Beta and Canary who are more compatible with Android 12) now have a new feature called zygisk. That feature is not compatible with Riru and LSposed. So if you're going to LSposed, use latest stable Magisk, which still works.
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
No.
systemshock869 said:
Anyone just running stock with root/xposed? Unless I see a compelling ROM I feel like this would be my choice. How do you like it? Does everything work correctly? Is there a way to add small features like 'hold power for flashlight,' stuff like that?
Click to expand...
Click to collapse
I'm running stock with latest Magisk Canary and besides that, I only use my Addon features module (which adds some cool custom stuff into stock ROM).
systemshock869 said:
Do you recommend a particular ROM? What is compelling about it over stock?
Thanks!
Click to expand...
Click to collapse
The only ROMs I know that exist for Pixel 4a are ABC and Proton AOSP ROMs. But, if I'm not mistaken, there aren't any ones built for Android 12.
Cheers!
Thanks so much! It's always frustrating, as a casual user, to come back to the mod scene and have to try to re-learn the current meta for both android modding and your particular device by wading through scattered forum posts.
Typhus_ said:
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
No.
Click to expand...
Click to collapse
Are there any guides for doing all this in Android 12? Seems like most guides are a bit outdated..
JohnC said:
I used this guide and running stock android 10 with Magisk root:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I am using:
TWRP 3.4.0.0
Magisk 21.4
Magisk Manager 8.0.7
Riru 23.5
Riru - EdXposed 0.5.2.1_4677
EdXposed Manager 4.6.2
All running with No problems!
Click to expand...
Click to collapse
I was hoping to keep Android 12.. That's exactly the type of guide I'm looking for but seems a bit outdated! Any particular reason you've stuck with A10?
systemshock869 said:
Are there any guides for doing all this in Android 12? Seems like most guides are a bit outdated..
I was hoping to keep Android 12.. That's exactly the type of guide I'm looking for but seems a bit outdated! Any particular reason you've stuck with A10?
Click to expand...
Click to collapse
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
systemshock869 said:
Any particular reason you've stuck with A10?
Click to expand...
Click to collapse
Just that some Xposed apps and modules only work with android 10, and I don't see any features of A11 or A12 that I would use.
Typhus_ said:
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
Click to expand...
Click to collapse
Awesome. Thanks! There seem to be some concerns in the Magisk thread about safetynet.. do you have root successfully hidden?
Is TWRP required for installing the addon module zips from your first post?
systemshock869 said:
Awesome. Thanks! There seem to be some concerns in the Magisk thread about safetynet.. do you have root successfully hidden?
Is TWRP required for installing the addon module zips from your first post?
Click to expand...
Click to collapse
SafetyNet will fail as soon as you unlock your bootloader.
There is a Magisk module provided by kdrag0n that fixes that but the free version, for the time being, needs Riru and Lsposed to work properly. That means you need to root your device using stable Magisk 23.0 if youwant to fixe SafetyNet right away.
The magisk patched boot.img version that I've shared on that post I've pointed out to you is Canary Magisk, where Magisk Hide feature no longer exists and it's incompatible with Riru and LSposed, as I've already said.
I'm running my device with SafetyNet failing and I couldn't care less since it's not problematic for my daily usage. Any app I cannot install through playstore can be installed using apkmirror. As for Magisk hide, it doesn't exit anymore but there's a "App deny list" that works as well to "hide" Magisk from banking apps (for instance).
I'm not using TWRP since there's really no need for it on Pixel 4a.
Everything can be done through fastboot and Magisk.
Anyway, if you really want to have SafteyNet passing, you need to manually patch stock boot.img (that you may find as well on that thread I've shared) with latest Magisk stable and flash that version. Afterwards install Riru, LSposed and SaftyNet fix by kdrag0n.
Cheers!
Typhus_ said:
I'm not using TWRP since there's really no need for it on Pixel 4a.
Click to expand...
Click to collapse
I use TWRP to do image Backups/Restores.
JohnC said:
I use TWRP to do image Backups/Restores.
Click to expand...
Click to collapse
I don't need to do that. Everything I have is backed up on my Google account.
Sure, /data and stuff like games or whatever needs to be downloaded again but, it's fine by me.
Furthermore, I don't use custom ROMs any more. Just stock Pixel ROM with my mods installed and I get by just fine, smooth and happy.
Cheers!
systemshock869 said:
I have updated to android 12.. will I need to revert in order to do any flashing?
Click to expand...
Click to collapse
Depends on the ROM. LineageOS staff say to install the latest Android 11 image before flashing a LineageOS 18.1 rom. I'd assume that to be true for any other roms based on LineageOS.
Typhus_ said:
It depends on what you want to do.
If you want to just root your device, you only need to do 2 things:
1 - Unlock your bootloader (see HERE )
2 - Flash Magisk patched boot.img (see HERE )
For custom ROMs and etc, you should just check the ROMs, Kernels, Recoveries, & Other section. I bet there's a lot of info there about that.
Click to expand...
Click to collapse
Do u have to disable OTA updates to keep from a calamity? If so, are manual updates a pain? Can u retain ur data with manual OTAs?
Zaxx32 said:
Do u have to disable OTA updates to keep from a calamity?
Click to expand...
Click to collapse
Yes.
Zaxx32 said:
If so, are manual updates a pain?
Click to expand...
Click to collapse
No.
Zaxx32 said:
Can u retain ur data with manual OTAs?
Click to expand...
Click to collapse
Yes.
Everytime a new build comes up, download the factory image directly from Pixel Official firmware site, extract it, open flash_all.bat, on the update command you see a "-w" flag. Delete the "-w" and save flash_all.bat. Connect device to PC, reboot to fastboot and run edited flash_all.bat.
If you don't delete the -w, you'll lose your data.
Cheers!
Awesome....thanx!