So I have been struggling the past few hours trying to get the Systemless root to work. I've followed all of the guides on this and the Magisk forum and yet the SafetyNet fails. Here are the steps I have taken:
Downloaded H830 10i ZIP
Downloaded Magisk v7 ZIP
Downloaded phh superuser magisk r259 ZIP
Boot into TWRP
Format Data
Flash the three ZIP files one at a time in the order mentioned
Flash no-veirfy
Reboot System
Step through setup page
Install Magisk Manager apk
Install phh SuperUser apk
Install SafetyNetHelper
The end result of all of that is a failed SafetyNet. Am I missing something? I would really appreciate any help. Thanks
SafetyNet has been undergoing an impressive number of revisions over the past few weeks. Most recently, this past weekend, it effectively shut out the majority of rooted users. There are reports of it shutting out folks purely for having an unlocked bootloader, particularly with the Nexus 6P.
Specifically for our G5, here's my history:
Magisk v7 and earlier was working well up until a few weeks ago. Safetynet was updated to detect Magisk in general. End of that chapter.
Chainfire and phhusson, the 2 main root leaders in Android, each came up with their own workarounds to evade SafetyNet. Chainfire came up with suhide, to be flashed after his supersu zip, and phhusson released his own version of phh root which also hid root from SafetyNet.
These worked for about a week until SafetyNet adapted. suhide was then updated with a manual script to run which evaded it again for several more days. This was working for me on Sunday morning. And then it didn't anymore. There were many variations people then advertised (using different root switch apps, etc), but none worked for me.
Magisk v8 was just released, which includes a setting to hide Magisk and root from SafetyNet. However, this does not work to fully evade Safetynet, and thus Android Pay won't start. It may be that SafetyNet is now looking at other things, such as unlocked bootloader status, and Magisk's presence is irrelevant.
Specifically, while working with these, I accidentally reset my G5 to near stock conditions (no root, encrypted data partition), except for the TWRP recovery and unlocked bootloader. Safetynet checker apps FAILED on this near pristine stock phone. This is disconcerting.
In short, there's no way I've found to get a SafetyNet pass since this past weekend. You could try returning completely to stock and relocking the bootloader, which will also probably wipe all your data, to test this theory, but not worth it in my book.
seconding what waylo said. i was trying all day to get safetynet to pass but i flashed the stock rom, did a factory reset, and still couldn't get safetynet to pass (all i had was unlocked bootloader + TWRP)
i think we just have to wait until we get a custom kernel with the boot verify checker that safetynet uses patched
Thanks for your help a few months ago. Given the time for Magisk to mature I was wondering if Magisk on the H830 is now possible. From reading throughout this forum, some users have had success but no one has an official guide. I just got a new LG G5 (gps issue) and I finally unlocked the bootloader and installed TWRP following the Noob Friendly Guide. Along the way I had to enter in the following code to keep my device from TWRP boot looping:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Once I got the 20a software version up and running I went ahead and flashed Magisk 12.0, went into the Magisk Manager Settings, turned on Busybox/Magisk Hide/Systemless Host, and performed a SafetyNet Check. The end result is a failed CTS Profile Mismatch. Did I miss something or did Google patch SafetyNet again?
SomeguynamedBentley said:
Thanks for your help a few months ago. Given the time for Magisk to mature I was wondering if Magisk on the H830 is now possible. From reading throughout this forum, some users have had success but no one has an official guide. I just got a new LG G5 (gps issue) and I finally unlocked the bootloader and installed TWRP following the Noob Friendly Guide. Along the way I had to enter in the following code to keep my device from TWRP boot looping:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Once I got the 20a software version up and running I went ahead and flashed Magisk 12.0, went into the Magisk Manager Settings, turned on Busybox/Magisk Hide/Systemless Host, and performed a SafetyNet Check. The end result is a failed CTS Profile Mismatch. Did I miss something or did Google patch SafetyNet again?
Click to expand...
Click to collapse
You need to install the latest v13 beta. It's on the magisk threads. Uninstall v12 with the magisk uninstaller and immediately install v13.
waylo said:
You need to install the latest v13 beta. It's on the magisk threads. Uninstall v12 with the magisk uninstaller and immediately install v13.
Click to expand...
Click to collapse
Awesome! Got it. Hopefully the learning curve from here on out as Google rolls out patches is not as steep so I can keep up!
A word to those reading this thread: you need to reboot after turning on Magisk Hide and Systemless Host in settings (as of 6/19/17).
Related
Most Nexus phones users use magisk in order to be able to have root and xposed and also be able to easily pass safetynet check tests in order to be able to get OTA updates.
Well now magisk 14.4 works on our device and OTA updates should work just fine according to this https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Of course when Android Oreo rom comes out we should wait before applying it just to be sure that magisk and twrp will work on that rom so that we wont be left without root after updating (or brick the device.
I wrote a guide for installing magisk 14.4 on our device having 2nd october OTA installed, i copy it here so that more people can see it.
DISCLAIMER - USE AT YOUR OWN RISK! Bellow steps worked for my device but they might brick yours, you might lose warranty etc.!!!!!!
I am not a developer, I am just a user that wants to have the new phone setup like the older phones in my possession before using it as the main everyday phone.
All below packages are here due to the hard work of the people who made them. If you use them, give them the appropriate credits. This is also the reason that I don't attach any files in this post, I only give links to download the packages on the the forum threads/ sites I also found them.
Here I just show a combination of packages/ programs that worked.
PREREQUISITES:
1) Read the whole guide before starting. Make sure you are familiar with all the terms used and you understand what you are doing in each step.
2) I advise you to firstly download all the needed packages and have them in a folder in your computer and also make a copy of them in your phone and then start with the steps of this guide.
3) In this guide I use a windows pc. Fastboot commands are written in cmd. If you use a pc with another operating system, just make sure you can use adb/ fastboot commands and that you can also use miflash or another tool to flash the rom to your phone.
4) Make sure you have correct adb drivers installed in your pc. For this guide I have used adb-setup-1.4.3.exe from this thread.
So this is the step by step procedure with links:
Flash official rom with miflash
rom image: Here is the latest rom. (tissot_images_7.10.14_20171014.0000.00_7.1_d791bf99f4.tgz is the image I used while writing this guide)
miflash: MiFlash2017-7-20-0.zip
Boot to freshly flashed rom,
Install second october OTA update (75mb),
Do reboot and wait a few minutes until the update is installed.
If you have not done any changes to your device (other root like supersu, old magisk verision etc) you can ignore above step.
From settings-->developer options:
Usb debuging on
OEM unlocking on
Just to be on the safe side for magisk manager app also go to Settings --> Security and enable Unknown sources.
Then shutdown phone, boot phone to fastboot with Vol- & power button,
send the command "fastboot oem unlock" in order to unlock bootloader.
Phone reboots by it self if I remember correctly.
Boot to rom, now being unlocked, and see the splash screen to see if it says "Unlocked" to be sure that it is unlocked.
Then shut down the phone.
Again boot phone to fastboot with Vol- & power button,
boot twrp (just boot, not flash) with command "fastboot boot recovery.img"
recovery-3.1.1-1
From twrp, install Magisk-v14.4-20171103-073038
It installs magisk 14.4 but magisk manager apk version installed with this is 14.0.
So, in order to have magisk 14.4, reboot to rom, uninstall magisk manager and then install Magisk Manager 5.4.0 (as suggested by matcho13579) MagiskManager-v5.0-20170513.apk
The problem now with this version of magisk manager is that it installs modules correctly and they work just fine, but the installed modules are not listed in magisk manager modules page (they work but they cannot be seen). That means that you cannot disable a single module, you have to enable magisk core mode to disable all of them or normal mode to have all modules enabled - I hope this will be fixed in a newer version. Magisk-v14.4-20171103-073038 zip file as I said installs magisk manager 14.0 which also appears to be working, but I did all tests on my device with MagiskManager-v5.0-20170513.apk installed.
Next, inside magisk manager downloads, search and install xposed framework sdk 25 systemless by topjohnwu.
After installation is completed reboot phone (phone boot takes some time at this step).
Then install this Xposed installer apk -material design XposedInstaller_by_dvdandroid_31_10_17.apk.
Now you have October 2nd update rom in your device, magisk 14.4 & xposed framework.
If you select magisk core only mode (which disables magisk modules), have enabled magisk hide and hide it form all apps except the ones you want to have root access, the device passes safetynet and theoretically you can install OTA updates (xposed framework -systemless or not- does not pass safetynet, but being installed systemlessly through magisk, it can be disabled), according to this link
Inside magisk manager you can also install this MiA1Plus_V1.01 module in order to enable camera2api & EIS, to be able to use google camera application.
Finally, i installed gravitybox using gravitybox non-fbe 7.0.4 - 29/10/2017 and it also appears to be working, I have not tested it thoroughly though:
https://forum.xda-developers.com/showpost.php?p=73340439&postcount=2
https://forum.xda-developers.com/attachment.php?attachmentid=4317286&d=1509267532
After installing xposed... Safety net goes fail
Sent from my Mi A1 using Tapatalk
How do I flash stock recovery. I flashed twrp earlier and cannot find stock recovery. There is no recovery.img in the tissot system image.
Aman301582 said:
How do I flash stock recovery. I flashed twrp earlier and cannot find stock recovery. There is no recovery.img in the tissot system image.
Click to expand...
Click to collapse
Recovery is included in boot.img
tidschi said:
Recovery is included in boot.img
Click to expand...
Click to collapse
Which means I'll lose root after flashing ?
Aman301582 said:
Which means I'll lose root after flashing
Click to expand...
Click to collapse
Yes, but it takes 1min to boot to TWRP, flash TWRP and Magisk?
blackyz01 said:
After installing xposed... Safety net goes fail
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
As I have written in the first post "xposed framework -systemless or not- does not pass safetynet, but being installed systemlessly through magisk, it can be disabled"
This means that if you enable magisk core mode which disables all modules or if you disable xposed framework module, it passes safetynet.
tidschi said:
Yes, but it takes 1min to boot to TWRP, flash TWRP and Magisk?
Click to expand...
Click to collapse
Okay, managed to get stock recovery back. But 2nd ota is not installing. Always fails
Why install old Magisk Manager? New one seems like it works, unless I am missing something..
ilpanos said:
Finally, i installed gravitybox using gravitybox non-fbe 7.0.4 - 29/10/2017 and it also appears to be working
Click to expand...
Click to collapse
Only one question about this: why did you choose NON-FBE version instead of the normal one?
Thank you :good::good::good:
this is worked for me
but i have a qu. how we will update next OTA?
matcho13579 said:
Only one question about this: why did you choose NON-FBE version instead of the normal one?
Click to expand...
Click to collapse
Just because unfortunately it seems that FBE is not currently supported on our device and it is using FDE.
Perhaps the normal version also works, but I didn't want to be in a situation where I find out in the future that something doesn't work correctly and I have to uninstall it.
suryaabadsar said:
Thank you :good::good::good:
this is worked for me
but i have a qu. how we will update next OTA?
Click to expand...
Click to collapse
First we have to make sure that magisk works correctly in the new OTA. Then and only then, enable magisk core mode to disable modules and pass safetynet and update according to the instructions in the link I have on the first post.
Will we lose root after an OTA update?
You have to do the procedure as described in the link I have provided in the first post. I am putting it again here:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
ilpanos said:
Just because unfortunately it seems that FBE is not currently supported on our device and it is using FDE.
Perhaps the normal version also works, but I didn't want to be in a situation where I find out in the future that something doesn't work correctly and I have to uninstall it.
Click to expand...
Click to collapse
I'm currently using the normal version and everything is working as intended.
That's why I ask, because it might not work the same way with Magisk (I used CF-Root + SuperSU + standard Xposed method)
ilpanos said:
First we have to make sure that magisk works correctly in the new OTA. Then and only then, enable magisk core mode to disable modules and pass safetynet and update according to the instructions in the link I have on the first post.
Click to expand...
Click to collapse
I HAVE UNROOT PHONE WITH THE SAME METHOD AND RE-LOCK BOOTLOADER WITH FASTBOOT COMMAND fastboot oem lock
NOW OTA WILL WORK PROPERLY ON MY PHONE.?
Thanks for the perfect guide.
One side note: official ROM on the provided link is already version .30, so no need to boot into the ROM and install the updates, the update is already merged in
@ilpanos hello mate! I just ordered my A1 from Trading Shenzhen. I have an clear conception what to do with my A1 when it has arrived. So therefore I am collecting some knowledge about flashing and modding (I am not a beginner, but not familiar with A/B partitions). Your thread is very useful here, many thanks.
I have still one question and maybe you can answer it: i would like to remove the google apps from the system, but I don't know if this works just like usual (to remove it from /system/app or priv-app). The reason is that I am using microG instead gapps.
Or will removing files and folders screw up something?
Thanks in advance!
Cheers!
Well, the thing is that by even mounting system partition as read-write ,and of course doing any change - even adding a line in build.prop - disables the ability to do OTA updates. You will have to reflash the new rom for each update. This is the purpose of this thread, to show that there is a way to mod root etc systemlessly without loosing the ability to update (of course under certain conditions).
For the life of me I cannot root this latest patch. I have tried 6 times either with having the Magisk app repack the boot image or by booting TWRP to install the Magisk zip. Using either method forces my phone into the same state/condition. When the phone reboots, it goes into recovery which says the data on my phone may be corrupt and prompts me to either try again or factory restore (erase data).
i was able to. i booted into twrp, sideloaded the twrp installer, then the magisk zip and sultan kernel and everything is running smoothly for me
Ok, so I was able to recover and root from an answer given in a pixel 3 thread using:
Pixel 3/Pixel 3 XL
- fastboot flash boot --slot all boot.img (from December factory image)
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- magisk-18.0.zip
- reboot system
What happens though is when I use adaway to update the hosts file, it breaks everything and I can't boot into system until I do the above steps again. Strange...
Do you have adaway install by chance?
Hi! I have no problem with last update, magisk nor adaway. I just flashed last update with flash-all.bat script, than fastboot twrp, install magisk ver. 18... and everything is working on 100%.
To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.
Diesel_Jeremiah said:
To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.
Click to expand...
Click to collapse
I'm on the December patch and am rooted with Magisk 17.1.
I actually just noticed the new update and am fixing to update Magisk. But you don't have to use v18. 0 to root December update. I've been on December update since it came out and rooted like always right away and haven't had any bootloops.
I rooted okay today with Magisk 18.0. It sounds like some people have had problems if they did not first uninstall Magisk with the latest uninstaller. That's what I did as a precaution (rather than just restoring the stock boot.img with the Magisk app, before upgrading the factory image).
FilthyFord said:
I'm on the December patch and am rooted with Magisk 17.1.
I actually just noticed the new update and am fixing to update Magisk. But you don't have to use v18. 0 to root December update. I've been on December update since it came out and rooted like always right away and haven't had any bootloops.
Click to expand...
Click to collapse
I had issues on both of my Pixel 2 phones trying to use any Magisk less than v18.0
I also had issues with v18.0 until I used the uninstaller first.
I read that other people were having the same issue.
I guess you got lucky?
Diesel_Jeremiah said:
I had issues on both of my Pixel 2 phones trying to use any Magisk less than v18.0
I also had issues with v18.0 until I used the uninstaller first.
I read that other people were having the same issue.
I guess you got lucky?
Click to expand...
Click to collapse
I guess so. I always open the .bat file and remove the -w so that it don't we my phone tough. Not sure if that makes a difference.
somin.n said:
Hi! I have no problem with last update, magisk nor adaway. I just flashed last update with flash-all.bat script, than fastboot twrp, install magisk ver. 18... and everything is working on 100%.
Click to expand...
Click to collapse
I enabled automatically granted root access and after a few mins after boot it granted access to adaway and after a reboot it seems to have worked again.
https://androidfilehost.com/?w=files&flid=249276&sort_by=date&sort_dir=DESC
I have Android 10 on my OG Pixel. I have secured it with pin and fingerprint. When i booted twrp-3.3.1-0-sailfish.img it sucesfully decrypted data with PIN then i flashed latest available zip which is twrp-pixel-installer-sailfish-3.3.0-0.zip. Rebooted and phone booted normaly. Then i downloaded latest magisk zip and apk. I tried to flash magisk but pin unlock does not work in twrp 3.3.0-0 which i flashed. Then i tried to boot from twrp-3.3.1-0-sailfish.img and this version decrypts data fine. Maybe because it's newer version and there is some fix in there. Can i flash 3.3.1-0 to my device permanently?
Why there is no 3.3.1-0 flashable zip for OG Pixel? https://eu.dl.twrp.me/sailfish/
Pixel XL does have 3.3.1-0 flashable zip too which is dated the same as live boot img 3.3.1-0 image https://eu.dl.twrp.me/marlin/
Can i flash magisk from booted twrp-3.3.1-0-sailfish.img and not with twrp that i flashed? Will it work?
matusala said:
I have Android 10 on my OG Pixel. I have secured it with pin and fingerprint. When i booted twrp-3.3.1-0-sailfish.img it sucesfully decrypted data with PIN then i flashed latest available zip which is twrp-pixel-installer-sailfish-3.3.0-0.zip. Rebooted and phone booted normaly. Then i downloaded latest magisk zip and apk. I tried to flash magisk but pin unlock does not work in twrp 3.3.0-0 which i flashed. Then i tried to boot from twrp-3.3.1-0-sailfish.img and this version decrypts data fine. Maybe because it's newer version and there is some fix in there. Can i flash 3.3.1-0 to my device permanently?
Why there is no 3.3.1-0 flashable zip for OG Pixel? https://eu.dl.twrp.me/sailfish/
Pixel XL does have 3.3.1-0 flashable zip too which is dated the same as live boot img 3.3.1-0 image https://eu.dl.twrp.me/marlin/
Can i flash magisk from booted twrp-3.3.1-0-sailfish.img and not with twrp that i flashed? Will it work?
Click to expand...
Click to collapse
Twrp does not work on 10. You can root fairly easily by clean flashing 10, installing the latest magisk Canary build and then patching the boot.img through magisk. There is currently no working twrp and although you can root you cannot mount your system. We await further magisk updates to fix that.
Go to the main magisk support thread on XDA. It's all there.
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3558
I've done it anyway and all working fine (apart from system mount). Magisk hide works, my adblockr works. It's all good.
Follow this guide for root. It works the same for the original Pixel
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Horgar said:
Twrp does not work on 10. You can root fairly easily by clean flashing 10, installing the latest magisk Canary build and then patching the boot.img through magisk. There is currently no working twrp and although you can root you cannot mount your system. We await further magisk updates to fix that.
Go to the main magisk support thread on XDA. It's all there.
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3558
I've done it anyway and all working fine (apart from system mount). Magisk hide works, my adblockr works. It's all good.
Follow this guide for root. It works the same for the original Pixel
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Click to expand...
Click to collapse
I removed fingerprint and pin code temporarily and flashed magisk.zip and installed magisk apk. All is working great. Then i set up pin and fingerprint and once there was some problem pin did not unlock phone fingerprint did. After reboot it also fixed.
Thing is if i boot 3.3.1-0 with fastboot boot it works, it decrypts data with pin. But 3.3.0-0 says pin wrong. I tried to install twrp-3.3.1-0.img from TWRP 3.3.0-0 with new menu to flash ramdisk but it says something that not enough memory available. How can i flash new 3.3.1-0 TWRP there is no zip. What version of TWRP do you have?
matusala said:
I removed fingerprint and pin code temporarily and flashed magisk.zip and installed magisk apk. All is working great. Then i set up pin and fingerprint and once there was some problem pin did not unlock phone fingerprint did. After reboot it also fixed.
Thing is if i boot 3.3.1-0 with fastboot boot it works, it decrypts data with pin. But 3.3.0-0 says pin wrong. I tried to install twrp-3.3.1-0.img from TWRP 3.3.0-0 with new menu to flash ramdisk but it says something that not enough memory available. How can i flash new 3.3.1-0 TWRP there is no zip. What version of TWRP do you have?
Click to expand...
Click to collapse
The issue you describe is nothing to do with being on Android 10. That issue of decryption with twrp has been around for a while. Just get rid of pin etc, then you will get into twrp. But. Twrp does not work with 10. There is no point attempting to flash twrp for the time being. It does not work.
If you want a working root, you need to do the old way by patching your boot.img. That seems to be the only working root method so far on 10
Horgar said:
The issue you describe is nothing to do with being on Android 10. That issue of decryption with twrp has been around for a while. Just get rid of pin etc, then you will get into twrp. But. Twrp does not work with 10. There is no point attempting to flash twrp for the time being. It does not work.
If you want a working root, you need to do the old way by patching your boot.img. That seems to be the only working root method so far on 10
Click to expand...
Click to collapse
Why do you keep saying it does not work? I just got rid of pin + fingerprint then went into TWRP which i flashed before from live TWRP. Flashed magisk.zip it worked perfectly and then rebooted and installed magisk manager. TWRP works great with 10 if i do not have pin + fingerprint and magisk also works great.
I used twrp to flash Magisk on 10.0. I didn't flash twrp, just booted it. It flashed the normal magisk fine and I have root. What is more strange, my Pixel accepted and installed 10.0 via the OTA. I have never had a rooted phone accept an OTA before.
jackdubl said:
I used twrp to flash Magisk on 10.0. I didn't flash twrp, just booted it. It flashed the normal magisk fine and I have root. What is more strange, my Pixel accepted and installed 10.0 via the OTA. I have never had a rooted phone accept an OTA before.
Click to expand...
Click to collapse
Magisk is systemless root maybe that's why it did that.
matusala said:
Why do you keep saying it does not work? I just got rid of pin + fingerprint then went into TWRP which i flashed before from live TWRP. Flashed magisk.zip it worked perfectly and then rebooted and installed magisk manager. TWRP works great with 10 if i do not have pin + fingerprint and magisk also works great.
Click to expand...
Click to collapse
If Twrp sticks and works on 10 then that's good. But all the reports on XDA are saying Twrp will not stick and/or does not work on 10. You're the only person I've heard that has got a working Twrp on 10
Horgar said:
If Twrp sticks and works on 10 then that's good. But all the reports on XDA are saying Twrp will not stick and/or does not work on 10. You're the only person I've heard that has got a working Twrp on 10
Click to expand...
Click to collapse
Have you tried just booting twrp instead of flashing it?
jackdubl said:
Have you tried just booting twrp instead of flashing it?
Click to expand...
Click to collapse
No. Not tried. But if it worked for you that's good to know. I know for others it didn't work. Patching the boot.img only takes 10 minutes anyway.
Are you able to mount your system with magisk rooted 10?
Horgar said:
No. Not tried. But if it worked for you that's good to know. I know for others it didn't work. Patching the boot.img only takes 10 minutes anyway.
Are you able to mount your system with magisk rooted 10?
Click to expand...
Click to collapse
I seem to remember getting some strange messages while flashing Magisk, like it couldn't mount system or something. It was in red. It seemed bad but it also came after successfully flashing Magisk, so it said. Everything was working fine after I rebooted. All root apps working as normal.
Howdy y'all, this is all something I did recently after resurrecting my Google pixel. I also got Android 10 and twrp working with magisk. All was good until I tried mounting system so I can edit build.prop. I spend a ton of time trying to research why I could not mount system. Came up empty until I found this thread with someone mentioning you cannot mount system. Why is this? Is there no way that I can edit build.prop in this configuration?
jeffritz1 said:
Howdy y'all, this is all something I did recently after resurrecting my Google pixel. I also got Android 10 and twrp working with magisk. All was good until I tried mounting system so I can edit build.prop. I spend a ton of time trying to research why I could not mount system. Came up empty until I found this thread with someone mentioning you cannot mount system. Why is this? Is there no way that I can edit build.prop in this configuration?
Click to expand...
Click to collapse
If your running Magisk you could try the Magiskhide props config module, Its in the downloads section of magisk manager. Should allow you to set custom props, there is a dedicated thread for it so may be worth a look there also.
junglism93 said:
If your running Magisk you could try the Magiskhide props config module, Its in the downloads section of magisk manager. Should allow you to set custom props, there is a dedicated thread for it so may be worth a look there also.
Click to expand...
Click to collapse
Yeah, after trying everything under the sun I started going down this route but as I was going through the Magiskhide props config module menu I see "Edit Magisk Props" and "Edit custom props" but It made me believe that it creates / edits new custom props and could not see a way of editing the build.prop in /system. May need to dig further into it since I never used this module before. Thanks for mentioning the Magiskhide props config module support thread.
is rooted Magisk on Android 10 or 11 with Pixel 1 possible?
jeffritz1 said:
Yeah, after trying everything under the sun I started going down this route but as I was going through the Magiskhide props config module menu I see "Edit Magisk Props" and "Edit custom props" but It made me believe that it creates / edits new custom props and could not see a way of editing the build.prop in /system. May need to dig further into it since I never used this module before. Thanks for mentioning the Magiskhide props config module support thread.
Click to expand...
Click to collapse
Is there a link. I currently have a pixel on 8.1 and I am trying to get a rooted pixel up and running so I can tether. This will be my daily phone. I am looking for the best solution for a safe and robust system that allows tethering. thanks for any leads.
Sam
YogaSlackers said:
Is there a link. I currently have a pixel on 8.1 and I am trying to get a rooted pixel up and running so I can tether. This will be my daily phone. I am looking for the best solution for a safe and robust system that allows tethering. thanks for any leads.
Sam
Click to expand...
Click to collapse
Hey, almost a week late but hope it's still helpful. Yes I recommend the official 10 firmware with Magisk, flashed through a temporary TWRP.
I've been running this setup for months, I can use all my root apps, even Google Pay and Netflix no problem.
I had rooted my Samsung Galaxy Note 8 using TWRP (latest version) and Magisk version 23.0. Everything worked well until 2 days ago when magisk auto updated to version 24.1.
After this, all the options available on 3home page disappeared except option to install magisk 24.1 and magisk app.
I was expecting gydisk OP to be available as seen in various screenshots from internet about magisk 24.1 but unfortunately, didn't see any option to enable it (Screenshot attached).
Thinking the magisk update may gone haywire, reinstalled the stock firmware for my Galaxy Note 8 phone, flashed TWRP, RMM_Bypass_v3_corsicanu.zip, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip, Magisk 24.1, successfully.
However when rebooted into system, the magisk app still showed no option for Gydisk or any other option except previously mentioned above I.e Install magisk or magisk app.
Have checked & found OEM unlocking and USB debugging is still open.
Now I am lost and wondering where could I be going wrong.
Appreciate very much if someone can guide me in right direction in getting Gydisk option si that I can pass the safety check and hide magisk.
Your screenshot shows that Magisk is not installed.
You only installed the app. Try install in the upper right corner and choose for direct install without patching.
Prof_Shekhar said:
I had rooted my Samsung Galaxy Note 8 using TWRP (latest version) and Magisk version 23.0. Everything worked well until 2 days ago when magisk auto updated to version 24.1.
After this, all the options available on 3home page disappeared except option to install magisk 24.1 and magisk app.
I was expecting gydisk OP to be available as seen in various screenshots from internet about magisk 24.1 but unfortunately, didn't see any option to enable it (Screenshot attached).
Thinking the magisk update may gone haywire, reinstalled the stock firmware for my Galaxy Note 8 phone, flashed TWRP, RMM_Bypass_v3_corsicanu.zip, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip, Magisk 24.1, successfully.
However when rebooted into system, the magisk app still showed no option for Gydisk or any other option except previously mentioned above I.e Install magisk or magisk app.
Have checked & found OEM unlocking and USB debugging is still open.
Now I am lost and wondering where could I be going wrong.
Appreciate very much if someone can guide me in right direction in getting Gydisk option si that I can pass the safety check and hide magisk.
Click to expand...
Click to collapse
xabu said:
Your screenshot shows that Magisk is not installed.
You only installed the app. Try install in the upper right corner and choose for direct install without patching.
Click to expand...
Click to collapse
Thank you xabu for your reply.
I had tried to install it numerous times using the direct install method as suggested by you but it gives me a "installation failed" message (Screenshot attached).
Also, presuming that my previously installed magisk v 23.0 may not have been uninstalled during the process of auto update to magisk version 24.1 (only 24.1 app installed but not magisk itself not upgraded due to unknown reasons), I reinstalled the app v 23 and uninstalled magisk completely. Frustrated, I installed the stock firmware again, reinstalled TWRP and flashed magisk 24.1. However, the result appears to be same. No magisk installation.
It appears to me that magisk v 23 is not yet completely uninstalled as if I delete this 24.1 app, reinstall app for 23.1 most of the functionality comes back though not all. I still can't hide magisk but it passes safety check.
Also I have tried to uninstall any previous version of magisk using renamed magisk app as uninstall.zip via TWRP. Also I get following message:
"cannot find vbmeta partition, patch vbmeta in boot image.
Removing magisk files."
Now when I go to Magisk app, I get only option to "select and patch a file."
Appreciate if anyone can suggest me a way forward.
Also, I get the vbmeta partition not found error while trying to install Magisk via TWRP (screenshot attached)
I have selected and installed Magisk patched boot image file using ODIN3. Removed TWRP. Tried to install using Magisk app 24.1 but get installation failed due to unable to check signature (screenshot attached).
Request some guidance.
Start here ....
Magisk - The Age of Zygisk.​Your questions are very interesting but too difficult for me to answer. Magisk 24.1 normally replaces the 23 almost automatically .... By uninstalling the module the situation becomes completely different and you should probably start from scratch. In my link "start here" you'll find the place where real specialists are.
Wishing you all the best !
Appreciate your advice.
However, I have reinstalled the stock firmware 3 times since this morning just as to ensure that I start from a clean slate. Also used Adb commands to uninstall any remanants of the previous Magisk manager if at all left there.
However, still stuck with the puzzling question as to where am I going wrong.
Prof_Shekhar said:
Also I have tried to uninstall any previous version of magisk using renamed magisk app as uninstall.zip via TWRP. Also I get following message:
"cannot find vbmeta partition, patch vbmeta in boot image.
Removing magisk files."
Now when I go to Magisk app, I get only option to "select and patch a file."
Appreciate if anyone can suggest me a way forward.
Click to expand...
Click to collapse
Exact same issue for me!
Also for me....same tests that @Prof_Shekhar have done
Prof_Shekhar said:
I had rooted my Samsung Galaxy Note 8 using TWRP (latest version) and Magisk version 23.0. Everything worked well until 2 days ago when magisk auto updated to version 24.1.
After this, all the options available on 3home page disappeared except option to install magisk 24.1 and magisk app.
I was expecting gydisk OP to be available as seen in various screenshots from internet about magisk 24.1 but unfortunately, didn't see any option to enable it (Screenshot attached).
Thinking the magisk update may gone haywire, reinstalled the stock firmware for my Galaxy Note 8 phone, flashed TWRP, RMM_Bypass_v3_corsicanu.zip, Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip, Magisk 24.1, successfully.
However when rebooted into system, the magisk app still showed no option for Gydisk or any other option except previously mentioned above I.e Install magisk or magisk app.
Have checked & found OEM unlocking and USB debugging is still open.
Now I am lost and wondering where could I be going wrong.
Appreciate very much if someone can guide me in right direction in getting Gydisk option si that I can pass the safety check and hide magisk.
Click to expand...
Click to collapse
The same thing happened to me so i tried and tried and tried for like 4-5 hours after reinstalling multiple times the firmware so i gave up and came to the conclusion that its not supported yet for a few phones like the Note8 (SM-N950F ~ my version of the phone).So the only thing you can do rn is to stick to version 23.0 then go to settings and change the channel to custom channel and paste this link "https://raw.githubusercontent.com/t...304e59f631280cc26ccc6d40a7cf04f7f37/beta.json" in there so the magisk version doesn't update itself or you update it by accident
Beast-chan said:
The same thing happened to me so i tried and tried and tried for like 4-5 hours after reinstalling multiple times the firmware so i gave up and came to the conclusion that its not supported yet for a few phones like the Note8 (SM-N950F ~ my version of the phone).So the only thing you can do rn is to stick to version 23.0 then go to settings and change the channel to custom channel and paste this link "https://raw.githubusercontent.com/t...304e59f631280cc26ccc6d40a7cf04f7f37/beta.json" in there so the magisk version doesn't update itself or you update it by accident
Click to expand...
Click to collapse
@Beast-chan
Hope you were able to install Magisk 24.1 Canary version without any further issues.
Prof_Shekhar said:
@Beast-chan
Hope you were able to install Magisk 24.1 Canary version without any further issues.
Click to expand...
Click to collapse
tbh i didnt try the Canary version...does it work or why do you ask?
Beast-chan said:
tbh i didnt try the Canary version...does it work or why do you ask?
Click to expand...
Click to collapse
@Beast-chan
Definitely. I have installed Magisk 24.1 Canary using patched AP file from stock firmware, and then reinstalled the Magisk 24.1 Canary version. It has been working without any issues since then.
Don't forget to install universal safetyNet Fix.
Let me know if you run into any issues.
Prof_Shekhar said:
@Beast-chan
Definitely. I have installed Magisk 24.1 Canary using patched AP file from stock firmware, and then reinstalled the Magisk 24.1 Canary version. It has been working without any issues since then.
Don't forget to install universal safetyNet Fix.
Let me know if you run into any issues.
Click to expand...
Click to collapse
ok ty i will try it
I rooted my A7160 last year using Magisk only, no TWRP, since I couldn't find TWRP for the Exynos chipset. A couple days ago I dumbly let Magsik update to v22.1, which removed Magisk Hide, an essential for me. I want to downgrade Magisk, but haven't yet found a way to do so without TWRP.
First, does anyone know of a way to downgrade Magisk without TWRP? I've tried restoring my Titanium Backup of Manager, but that prompts me to download and install the full Magisk, which will leave me with the new Magisk. I also tried fresh install of the 7.5.1 Magisk Manager app, which only lets me install 22.1.
Second, is there any work on or anyone willing to work on TWRP or other custom recovery for the Exynos chipset (A7160)?
Third, is there any other way to hide root? A brief search did not yield anything promising yet.
Thanks in advance!
stgibson said:
I rooted my A7160 last year using Magisk only, no TWRP, since I couldn't find TWRP for the Exynos chipset. A couple days ago I dumbly let Magsik update to v22.1, which removed Magisk Hide, an essential for me. I want to downgrade Magisk, but haven't yet found a way to do so without TWRP.
First, does anyone know of a way to downgrade Magisk without TWRP? I've tried restoring my Titanium Backup of Manager, but that prompts me to download and install the full Magisk, which will leave me with the new Magisk. I also tried fresh install of the 7.5.1 Magisk Manager app, which only lets me install 22.1.
Second, is there any work on or anyone willing to work on TWRP or other custom recovery for the Exynos chipset (A7160)?
Third, is there any other way to hide root? A brief search did not yield anything promising yet.
Thanks in advance!
Click to expand...
Click to collapse
FYI Update for others' reference: I got what I needed with Zygisk and DenyList, so should be OK without downgrading. If I need to downgrade, I realized an option that may work: re-flashing the previously-used patched boot.img.