Related
EDIT:
My mod is not needed anymore!
Everything is fine now, the TWRP guys made the decryption in their latest version (3.2.1 at the time of this post) possible, even with android 8.1.
Go ahead and download it from twrp.me. and don't forget to thank them, because it was a LOT of hard work! Google made big changes under the hood, and it took a lot of patience and endurance to adapt.
Big up to @Dees_Troy and the rest of the team!
Hey People! It seems, that after weeks of trying, hundreds of reboots, countless tests, I can present you a working version of TWRP 3.1. for the Pixel with Android O Developer Preview 4.
Edit: and it also works on the final Android O.
But let's not rush into things.. First of all a DISCLAIMER:
This is a TEST release, you are using it at your own risk. If your phone gets damaged in any way, nobody else but you can be held responsible. If you do not agree, stop reading and don't use this mod!
I would like to give credits to the people who helped me, and made all this possible:
First of all, @Chainfire, who did more then you would think Among other things, he was the one who showed me how to use tune2fs and reset quotas on /data, which makes it possible to mount it. Without this , I couldn't even start. So thank you very much!
Of course where would we be without @Dees_Troy and the other TWRP guys (i.e.: CaptainThrowback, nkk71, steadfasterX, _that...), who created and maintain TWRP, and demonstrated some serious patience on IRC , where I was asking them for help. For days. For weeks Thank you guys! You helped a lot!
What is this "mod"?
This is stock, normal TWRP 3.1 compiled from source, for the Google Pixel (sailfish) with some small tweaks to make it possible to mount /data, and decrypt it.
Can you use it on the Pixel XL (marlin)?
I don't know... I don't have a Pixel XL to test. If you want, you can buy me one and I'll be glad to compile, prepare, and test it for you.
EDIT: Chainfire "tested a few zip installs" and those were working for him on the Pixel XL, so maybe it is worth a try guys! - thanks for this CF! -
What happens behind the curtains?
I made some modifications to a script that prepared stuff to make the decryption of /data possible. Now it does a bit more... It copies libraries and binaries from /system and /vendor partitions to /system and /vendor folders, so they can be un-mounted (needed for backup). Basically, the recovery uses the real files/commands of the currently installed android os to prepare and mount /data partition (to make it ready for decrypting).
I updated the fstab file, so TWRP knows what to mount where.
I also changed a few things in the order how services are started during TWRP boot.
This is mostly everything. I was only changing external parts/files/tools of TWRP. The original code, the core is left intact.
How well was it tested?
I have only 1 phone, the pixel. I have only tested on this one phone, and it works for me. Of course I can't be certain it will for you, but you will see if you try it
I tested decrypting of /data, flashing a zip file, making a backup. Didn't dare to test restore yet
How can you try it?
This is not a flashable zip, this is a bootable image. So to use it, you have to put the phone into fastboot mode, and fastboot boot the image.
1. reboot the phone into fastboot mode
- if you have adb: adb reboot bootloader
- if you don't, then turn off the phone and press volume down while turning it on
2. open a terminal and issue the following command:
Code:
fastboot boot <path to your twrp image here>
(for example: fastboot boot /home/you/twrp-3-1-pixel-bootable-mod.img)
What about a flashable zip?
I had some quick test runs only for now, and it was working for me (flashing the zip, rebooting to recovery) until I flashed supersu, or rebooted the phone to android. I will need some more time to work on this, and see what is going wrong. So please be patient, I will try to do something, but can't guarantee it will work. Soon. Anytime.
Enough of the talk, you can download the image file from here:
https://www.androidfilehost.com/?fid=745425885120753892
Good luck and don't forget to report back!
I will try to do my best to help you, but I have a family and I inted to spend most of my time with them. Please be patient!
If you like my work, you can buy me a beer, it is damn hot here right now, and I would love to drink one
Edit: Because I'm a noob and couldn't push my changes to the gerrits, I created a diff file with all my changes.
If you are checking it, please take into account, that I was in a hurry, and there was a point where I said "F*** it!" and I copied ALL the libs and bins from /system and /vendor
Anyway, here it is : https://www.androidfilehost.com/?fid=817550096634795329
reserved...
I've only tested installing a few ZIPs but that seems to work fine (on Pixel XL).
I've looked at your modified script and I see the tune2fs commands and copying /system and /vendor files, but I don't see where you actually mount/decrypt /data. Or is this still handled by the TWRP binary?
Chainfire said:
I've only tested installing a few ZIPs but that seems to work fine (on Pixel XL).
I've looked at your modified script and I see the tune2fs commands and copying /system and /vendor files, but I don't see where you actually mount/decrypt /data. Or is this still handled by the TWRP binary?
Click to expand...
Click to collapse
Hi Chainfire!
I'm happy to hear, that it works on the Pixel XL
Thanks for the confirmation!
Yes, decrypting the data partition is still being handled by TWRP. I added some debug lines to the C code, you can see it in /tmp/recovery.log.
The main issue was mounting /data first, and I had to enable file based encryption instead of vold...
Thanks, I'll have to make time in the very near future to prep my phone for a fresh install.
I haven't had a need to host Android files since I moved on from LG devices before my HTC 10 and Pixel, but I highly recommend Android File Host with optional FTP access on request.
If you prefer a regular cloud service, I recommend Mega. They give 50GB for free and they have an Android app as well as Windows. Possibly others (Mac?), not sure.
My God this is amazing. Thank you so so much.
bbender716 said:
My God this is amazing. Thank you so so much.
Click to expand...
Click to collapse
You are welcome! Try to imagine how happy I was when I first succeeded At that time I had to issue 5 commands after boot, and restart it twice to make it work
But I was already able to flash ARISE sound mod and I almost cried of joy
roirraW "edor" ehT said:
Thanks, I'll have to make time in the very near future to prep my phone for a fresh install.
I haven't had a need to host Android files since I moved on from LG devices before my HTC 10 and Pixel, but I highly recommend Android File Host with optional FTP access on request.
If you prefer a regular cloud service, I recommend Mega. They give 50GB for free and they have an Android app as well as Windows. Possibly others (Mac?), not sure.
Click to expand...
Click to collapse
Ahh I haven't thought of Android File Host! Although I downloaded gigbytes of roms, and mods from there already
Thanks for the tip!
is my path is cd/adb what command i write before twrp.img
gubacsek said:
Hey People! It seems, that after weeks of trying, hundreds of reboots, countless tests, I can present you a working version of TWRP 3.1. for the Pixel with Android O Developer Preview 4.
But let's not rush into things.. First of all a DISCLAIMER:
This is a TEST release, you are using it at your own risk. If your phone gets damaged in any way, nobody else but you can be held responsible. If you do not agree, stop reading and don't use this mod!
I would like to give credits to the people who helped me, and made all this possible:
First of all, @Chainfire, who did more then you would think Among other things, he was the one who showed me how to use tune2fs and reset quotas on /data, which makes it possible to mount it. Without this , I couldn't even start. So thank you very much!
Of course where would we be without @Dees_Troy and the other TWRP guys (i.e.: CaptainThrowback, nkk71, steadfasterX...), who created and maintain TWRP, and demonstrated some serious patience on IRC , where I was asking them for help. For days. For weeks Thank you guys! You helped a lot!
What is this "mod"?
This is stock, normal TWRP 3.1 compiled from source, for the Google Pixel (sailfish) with some small tweaks to make it possible to mount /data, and decrypt it.
Can you use it on the Pixel XL (marlin)?
I don't know... I don't have a Pixel XL to test. If you want, you can buy me one and I'll be glad to compile, prepare, and test it for you.
EDIT: Chainfire "tested a few zip installs" and those were working for him on the Pixel XL, so maybe it is worth a try guys! - thanks for this CF! -
What happens behind the curtains?
I made some modifications to a script that prepared stuff to make the decryption of /data possible. Now it does a bit more... It copies libraries and binaries from /system and /vendor partitions to /system and /vendor folders, so they can be un-mounted (needed for backup). Basically, the recovery uses the real files/commands of the currently installed android os to prepare and mount /data partition (to make it ready for decrypting).
I updated the fstab file, so TWRP knows what to mount where.
I also changed a few things in the order how services are started during TWRP boot.
This is mostly everything. I was only changing external parts/files/tools of TWRP. The original code, the core is left intact.
How well was it tested?
I have only 1 phone, the pixel. I have only tested on this one phone, and it works for me. Of course I can't be certain it will for you, but you will see if you try it
I tested decrypting of /data, flashing a zip file, making a backup. Didn't dare to test restore yet
How can you try it?
This is not a flashable zip, this is a bootable image. So to use it, you have to put the phone into fastboot mode, and fastboot boot the image.
1. reboot the phone into fastboot mode
- if you have adb: adb reboot bootloader
- if you don't, then turn off the phone and press volume down while turning it on
2. open a terminal and issue the following command:
Code:
fastboot boot <path to your twrp image here>
(for example: fastboot boot /home/you/twrp-3-1-pixel-bootable-mod.img)
What about a flashable zip?
I had some quick test runs only for now, and it was working for me (flashing the zip, rebooting to recovery) until I flashed supersu, or rebooted the phone to android. I will need some more time to work on this, and see what is going wrong. So please be patient, I will try to do something, but can't guarantee it will work. Soon. Anytime.
Enough of the talk, you can download the image file from here:
(If you know a good file hosting service, please let me know):
https://drive.google.com/open?id=0BycCshQzwZmBaUtialo5Y01Dc3c
Good luck and don't forget to report back!
I will try to do my best to help you, but I have a family and I inted to spend most of my time with them. Please be patient!
If you like my work, you can buy me a beer, it is damn hot here right now, and I would love to drink one
Click to expand...
Click to collapse
Any help don't want reistall all again!!!!
is my twro .img is on cd/adb what command i write to flash this beauty?
Well, I was able to boot to TWRP, and successfully flashed WETA audio mod. However, upon rebooting, the V4A app wasn't there.
gubacsek said:
You are welcome! Try to imagine how happy I was when I first succeeded At that time I had to issue 5 commands after boot, and restart it twice to make it work
But I was already able to flash ARISE sound mod and I almost cried of joy
Click to expand...
Click to collapse
Hilariously, the ARISE sound mod is exactly why I had flashed back from DP4. I'm close with those guys and they know their stuff for sure.
mngdew said:
Well, I was able to boot to TWRP, and successfully flashed WETA audio mod. However, upon rebooting, the V4A app wasn't there.
Click to expand...
Click to collapse
Same here
I just tried ARISE. This one installs, but failed to update the driver.
mngdew said:
I just tried ARISE. This one installs, but failed to update the driver.
Click to expand...
Click to collapse
Interesting. I also tried side loading the v4a apk packaged in WETA, granted root permissions and it attempted to install drivers but failed.
mngdew said:
Well, I was able to boot to TWRP, and successfully flashed WETA audio mod. However, upon rebooting, the V4A app wasn't there.
Click to expand...
Click to collapse
maflin18 said:
Same here
Click to expand...
Click to collapse
mngdew said:
I just tried ARISE. This one installs, but failed to update the driver.
Click to expand...
Click to collapse
maflin18 said:
Interesting. I also tried side loading the v4a apk packaged in WETA, granted root permissions and it attempted to install drivers but failed.
Click to expand...
Click to collapse
Guys! Check the free space on /system! On Android O DP4 I had about 100MB free space, and I had to remove some **** before flashing anything. Try /system/app and Pinyin input, Chinese input apks....
The recovery is fine...
What? I don't know what I did differently this time, but the the app keeps asking to install the driver again and again everytime I open the app even though there was a successful driver installation notification.
gubacsek said:
You are welcome! Try to imagine how happy I was when I first succeeded At that time I had to issue 5 commands after boot, and restart it twice to make it work
But I was already able to flash ARISE sound mod and I almost cried of joy
Click to expand...
Click to collapse
Can u pls send link for arise which u have flash...
kiran8631 said:
Can u pls send link for arise which u have flash...
Click to expand...
Click to collapse
It was this one:
https://drive.google.com/file/d/0BycCshQzwZmBRFRJSXAwTDhHcm8/view?usp=drivesdk
At last! I got it working.
gubacsek said:
It was this one:
https://drive.google.com/file/d/0BycCshQzwZmBRFRJSXAwTDhHcm8/view?usp=drivesdk
Click to expand...
Click to collapse
Facing this issue...
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
zdimension said:
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
Click to expand...
Click to collapse
Use mount-magisk.zip found in collection of modules thread and delete the folder via twrp in /magisk
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
zdimension said:
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
Click to expand...
Click to collapse
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
gonsa said:
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
Click to expand...
Click to collapse
Start reading the thread from the beginning and you'll find it.
gonsa said:
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
Click to expand...
Click to collapse
Install "Uninstaller Mod Magisk" from TWRP. Then go in the TWRP terminal and type uninmod_magisk and follow the instructions.
please post the link to thread unistaller magisk module, to other users follow the solution!
edit:
there is https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
nodio said:
please post the link to thread unistaller magisk module, to other users follow the solution!
edit:
there is https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
Click to expand...
Click to collapse
Not working for me!
I will uninstall "Audio Compatibility Patch" V1.0 from zackptg5 & ahrion
In Magisk Manger Status is always " Module will be updated at the next start"
If i use the "TWRP-Uninstaller" the Modul is not in List!
dewois said:
Not working for me!
I will uninstall "Audio Compatibility Pach" V1.0 from zackptg5 & ahrion
In Magisk Manger Status is always " Module will be updated at the next start"
If i use the "TWRP-Uninstaller" the Modul is not in List!
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Click to expand...
Click to collapse
".... Go the module folder under /sbin/.core/img ..."
I dont have this folder in /sbin!
tobi14 said:
".... Go the module folder under /sbin/.core/img ..."
I dont have this folder in /sbin!
Click to expand...
Click to collapse
If you have a current version of Magisk installed, yes you do. Enable viewing hidden files and folders in your file explorer. The dot at the beginning of the folder name means it's hidden...
zdimension said:
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
Click to expand...
Click to collapse
If you can launch TWRP then :
Check magisk.img exist
1. Go to "advanced" and then click on "File Explorer".
2. Check there is "magisk.img" file under "/data"
Backup magisk.img
1. Go to "advanced" and then click on "terminal command".
2. type following command
Code:
cp /data/magisk.img /data/magisk.img.bk
Mount magisk.img
1. Make a temp folder
Code:
mkdir /mktmp
2. Mount magisk.img to /mktmp
Code:
mount -o loop /data/magisk.img /mktmp
3. Navigate to mktmp and remove your module
Code:
cd /mktmp
rm -rf /mktmp/xxxx
Unmount magisk.img and reboot to check if it's work
1. Unmount magisk.img
Code:
umont /mktmp
2. Leave terminal and reboot the phone
3. Enjoy!
mklee11224 said:
If you can launch TWRP then :
Check magisk.img exist
1. Go to "advanced" and then click on "File Explorer".
2. Check there is "magisk.img" file under "/data"
Backup magisk.img
1. Go to "advanced" and then click on "terminal command".
2. type following command
Code:
cp /data/magisk.img /data/magisk.img.bk
Mount magisk.img
1. Make a temp folder
Code:
mkdir /mktmp
2. Mount magisk.img to /mktmp
Code:
mount -o loop /data/magisk.img /mktmp
3. Navigate to mktmp and remove your module
Code:
cd /mktmp
rm -rf /mktmp/xxxx
Unmount magisk.img and reboot to check if it's work
1. Unmount magisk.img
Code:
umont /mktmp
2. Leave terminal and reboot the phone
3. Enjoy!
Click to expand...
Click to collapse
Thanks mate ! it worked like a charm !
just use "ls" command on step 3 after changing directory to mktmp , to show installed modules.:silly:
My Phone Specification : Moto X Play ------ 7.1.1 Stock Firmware -------- Squid kernel --------- rooted using Magisk ------ systemless xposed module "xposed_25" installed using magisk module(Uninstalled by this method !) .:victory:
Tanks a lot!
Crossbreeder lite made my phone unusable. Working fine again!
magisk.img not found in /data
This works like charm, if you can't find the magisk.img in `/data` check `/data/adb` ... I hope this work .
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Click to expand...
Click to collapse
Own domain huh? Business growing? Hehehe I only came for the uninstall zip, hey quick question, I'm on a micro sd-less phone (big news), still a flashaholic, kinda, but my phone so happens to require a data format every time for gsi's, where would you recommend keeping the "things to keep on your device" (Magisk related) so i don't have to carry an otg and drive everywhere i go? Thank you sir, you almost get more thanks than posts! Talk about reputation!
culiacanazo said:
Own domain huh?
Click to expand...
Click to collapse
I keep a few of them around. It was nice to finally find a good use for that one...
but my phone so happens to require a data format every time for gsi's, where would you recommend keeping the "things to keep on your device" (Magisk related) so i don't have to carry an otg and drive everywhere i go?
Click to expand...
Click to collapse
Do you have to completely wipe the device? Or can you keep internal storage intact? If not, it sounds like you're out of luck.
Nice thread hijack, by the way... :laugh:
Didgeridoohan said:
Do you have to completely wipe the device?
Click to expand...
Click to collapse
Well i do a factory reset, flash system img and reboot, let it loop because it will, and then do a data format before it will boot, so system, caches, and data go... (Huawei, see)
Didgeridoohan said:
Nice thread hijack, by the way... :laugh:
Click to expand...
Click to collapse
I kinda stayed on topic didn't i? :crying:
You linked to your help guide which i read the beginning of that by the way has nothing to do with the help you offered to the op and reminded me of my struggles with a totally different device and problem!!
It's like how I'm related to my grandma's cousin's wife's sister's doctor's neighbor's son's friend, ain't it?
Sent from my Huawei Mate 10 Pro using XDA Labs
Would be cool if someone could share the adb solution. In the FAQ is just written "email me for this" wtf?!? It is ****ing anoying to reflash the whole system everytime a module isnt working (yeah thats what you need to do if your device doesnt have twrp, and a lot of a/b devices dont have twrp). Also you need to delete all user datas because you flashed the system new and the new system doesnt know the encryption key for the user datas. There need to be a better solution than using twrp or email the dev for adb solution.
The easiest way would be to make it possible that magisk manager can manage (remove/deactivate) the modules while there is no patched boot.img installed. This would solve all problems related to a/b devices without twrp and magisk modules (not booting or anything else) just flash stock boot.img remove the problematic module flash patched boot.img and done. This is not possible because the module section in magisk manager is hidden when there is no patched boot.img installed.
Second thing i noticed, magisk manager doesnt reset the active modules when you wipe the app data. This should be a MUST. Would also solve the problem of not booting modules without wiping the whole system on a/b devices without twrp.
Apply .disable_magisk
saturday_night said:
Would be cool if someone could share the adb solution. In the FAQ is just written "email me for this" wtf?!? It is ****ing anoying to reflash the whole system everytime a module isnt working (yeah thats what you need to do if your device doesnt have twrp, and a lot of a/b devices dont have twrp). Also you need to delete all user datas because you flashed the system new and the new system doesnt know the encryption key for the user datas. There need to be a better solution than using twrp or email the dev for adb solution.
The easiest way would be to make it possible that magisk manager can manage (remove/deactivate) the modules while there is no patched boot.img installed. This would solve all problems related to a/b devices without twrp and magisk modules (not booting or anything else) just flash stock boot.img remove the problematic module flash patched boot.img and done. This is not possible because the module section in magisk manager is hidden when there is no patched boot.img installed.
Second thing i noticed, magisk manager doesnt reset the active modules when you wipe the app data. This should be a MUST. Would also solve the problem of not booting modules without wiping the whole system on a/b devices without twrp.
Click to expand...
Click to collapse
Hi!. I have this user of XDA Dev. hanging out for a time... well the fact is I'm new. My problem (not the only one) maybe merge a kind of solution to this. And this could be putting the ".disable_magisk" blank file inside the cache partition as an ADB Sideload update.
Next to this. I've found that to do that it's not as simply as it seems to be cause I'm on a Samsung Galaxy S7 Nougat 7.0 Version. And all the examples with update-binary file I have, are from downgrade versions...
I'm stuck in a bootloop due to the Magisk Xposed SDK 24 module. I think this module & encription is not good (as I've read on the Xpose module thread).
So, here I'm asking how to make an script to run directly on the Stock recovery using ADB Sideload, which will put the blank ".disable_magisk" file inside the /cache partition. I need just this, and I think this could help some people who are stuck on this issue.
Now, I have this Thread. But really I need the advice of an expert telling me what to do in order to achieve this. As I think this is an easy labor, but you have to know how to do it... If someone is able to clarify please, I will appreciate so much.
Thanks!
---------- Post added at 05:51 PM ---------- Previous post was at 05:41 PM ----------
neromanello said:
Hi!. I have this user of XDA Dev. hanging out for a time... well the fact is I'm new. My problem (not the only one) maybe merge a kind of solution to this. And this could be putting the ".disable_magisk" blank file inside the cache partition as an ADB Sideload update.
Next to this. I've found that to do that it's not as simply as it seems to be cause I'm on a Samsung Galaxy S7 Nougat 7.0 Version. And all the examples with update-binary file I have, are from downgrade versions...
I'm stuck in a bootloop due to the Magisk Xposed SDK 24 module. I think this module & encription is not good (as I've read on the Xpose module thread).
So, here I'm asking how to make an script to run directly on the Stock recovery using ADB Sideload, which will put the blank ".disable_magisk" file inside the /cache partition. I need just this, and I think this could help some people who are stuck on this issue.
Now, I have this Thread. But really I need the advice of an expert telling me what to do in order to achieve this. As I think this is an easy labor, but you have to know how to do it... If someone is able to clarify please, I will appreciate so much.
Thanks!
Click to expand...
Click to collapse
I need to know how to locate the mount point of my /cache partition at the stock recovery ADB Sideload. Then, to mount it, transfer the blank file to it, and then unmount /cache. I think it's an easy labor. So here my incomplete updater-script:
ui_print("Trying to make an script with ADB Sideload..."); CRLF
ui_print("Creating file to disable Magisk Modules..."); CRLF
I NEED THE MOUNT POINT HERE CRLF
ifelse package_extract_file(".disable_magisk", "/cache/.disable_magisk") == "t", ui_print("OK!"), ui_print("Failed!"); CRLF
UNMOUNT COMMAND HERE. CRLF
--last blank line--
So, I need to complete that, BUT things gets difficult when I need the update-binary for my Nougat 7.0 version, and to sign the whole .zip file in order my stock recovery recognizes it. I think this last thing could be made by this Thread. But really I don't know. Please help.
Thanks!.
Hi,
I own a Pixel XL 128GB, running 8.0.0 October FW. I have installed Magisk 14.3 beta 1437. Almost everything works, except for:
1. When installing Magisk using Magisk's internal installer it always downloads MAgisk 14.0 and tries to install this old, outdated version. Is this a bug?
2. I can't install OTAs, tried following john's installing instructions...
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
My steps were:
* Install stock boot loader - Magisk almost immediately confirms that it has installed the stock boot image. That's a bit surprising, I don't see any flashing dialog like when installing Magisk. Bug?
* trying to update using the internal OTA fails. It takes very long and suddenly stops.
Any idea what went wrong?
niko26 said:
Hi,
I own a Pixel XL 128GB, running 8.0.0 October FW. I have installed Magisk 14.3 beta 1437. Almost everything works, except for:
1. When installing Magisk using Magisk's internal installer it always downloads MAgisk 14.0 and tries to install this old, outdated version. Is this a bug?
2. I can't install OTAs, tried following john's installing instructions...
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
My steps were:
* Install stock boot loader - Magisk almost immediately confirms that it has installed the stock boot image. That's a bit surprising, I don't see any flashing dialog like when installing Magisk. Bug?
* trying to update using the internal OTA fails. It takes very long and suddenly stops.
Any idea what went wrong?
Click to expand...
Click to collapse
1. If you wan't the current beta to install, you need to change to the beta update channel in the Manager settings.
2. You've probably done something that messes with important partitions (/system, /vendor, etc). It's enough to just mount the partition rw to destroy the ability to update through OTA.
Restoring the stock boot image through the Manager is instantaneous...
Hi @Didgeridoohan,
thank you very much for the quick answers!
Didgeridoohan said:
1. If you wan't the current beta to install, you need to change to the beta update channel in the Manager settings.
Click to expand...
Click to collapse
Thanks - I didn't know that.
2. You've probably done something that messes with important partitions (/system, /vendor, etc). It's enough to just mount the partition rw to destroy the ability to update through OTA.
Click to expand...
Click to collapse
Hm, how do I find out what has been messed on /system, and/or /vendor?
Does installing and using AdAway tamper with /system or /vendor?
So reflashing the stock boot image is not sufficent, correct?
And most important.. how do I fix this?
niko26 said:
Hi @Didgeridoohan,
thank you very much for the quick answers!
Thanks - I didn't know that.
Hm, how do I find out what has been messed on /system, and/or /vendor?
Does installing and using AdAway tamper with /system or /vendor?
So reflashing the stock boot image is not sufficent, correct?
And most important.. how do I fix this?
Click to expand...
Click to collapse
If you let AdAway directly write to /system/etc/hosts, then yes, you have a compromised system partition. If you're using Magisk Systemless Hosts you should be fine though. Do you have TWRP installed? That'd be an issue as well...
If you want to make sure that you can update through OTA in the future, clean flash a factory image (you can leave data intact) and then make sure not to touch /system or /vendor at all.
* DELETED *
Didgeridoohan said:
If you let AdAway directly write to /system/etc/hosts, then yes, you have a compromised system partition. If you're using Magisk Systemless Hosts you should be fine though.
Click to expand...
Click to collapse
Yeah, I've been using Magisk's systemless hosts-file.
. Do you have TWRP installed? That'd be an issue as well...
Click to expand...
Click to collapse
TWRP has not been installed permanently.
If you want to make sure that you can update through OTA in the future, clean flash a factory image (you can leave data intact) and then make sure not to touch /system or /vendor at all.
Click to expand...
Click to collapse
There aren't a lot of apps I am granting root. One of them is Titanium Backup. It may have tampered the fs.
Is there any kind of diff against the original folders which I can run to find out what has been tampered to possibly identify which app is causing the issues?
One of the main reasons for installing Magisk was because I was tired of flashing the entire system when updates have been released.
I never couldn't get Flashfire working properly when it comes to install updates / OTAs.
niko26 said:
Yeah, I've been using Magisk's systemless hosts-file.
TWRP has not been installed permanently.
There aren't a lot of apps I am granting root. One of them is Titanium Backup. It may have tampered the fs.
Is there any kind of diff against the original folders which I can run to find out what has been tampered to possibly identify which app is causing the issues?
One of the main reasons for installing Magisk was because I was tired of flashing the entire system when updates have been released.
I never couldn't get Flashfire working properly when it comes to install updates / OTAs.
Click to expand...
Click to collapse
Since the OTA can check for a tampered system, I'm sure there's a way to check. Question is if it's worth the effort.
Any app that has root access can be the culprit... Could also be that you let TWRP mount system rw or something similar. Really hard to say...
Didgeridoohan said:
Since the OTA can check for a tampered system, I'm sure there's a way to check. Question is if it's worth the effort.
Any app that has root access can be the culprit... Could also be that you let TWRP mount system rw or something similar. Really hard to say...
Click to expand...
Click to collapse
Does TWRP mount system as rw by default? Because all I really do is.. boot to TWRP, flash the Magisk's zip. That's it. Nothing else.
Is there any other way I can install OTAs without using a computer with USB (and keeping root of course )?
As said... I never could FlashFire to work correctly. The documentation leaves a lot of questions open - BTW.. props to the Magisk's docs - much better.
niko26 said:
Does TWRP mount system as rw by default? Because all I really do is.. boot to TWRP, flash the Magisk's zip. That's it. Nothing else.
Is there any other way I can install OTAs without using a computer with USB (and keeping root of course )?
As said... I never could FlashFire to work correctly. The documentation leaves a lot of questions open - BTW.. props to the Magisk's docs - much better.
Click to expand...
Click to collapse
TWRP doesn't mount system as rw unless you let it.
I've never used Flashfire and haven't updated through OTA since, 2014-ish. :laugh: I'm mainly going on theoretical knowledge here... On my Nexus I used fastboot to flash the factory image (until I switched to ROM flashing in TWRP) and now I just flash the full update package that OnePlus provides in TWRP.
For a while there I also flashed the system.img and boot.img files in TWRP. If that months security update only had anything to do with those files it was just a matter of downloading the factory image and unpack those two files and flash them directly in TWRP. No computer needed (unless there was an update to the bootloader and/or radio). No idea if this is viable on a Pixel...
My main use for Magisk is that all my system modifications are still there after I update my phone. Drastically cuts down on the time it takes to set my phone up after an update.
Didgeridoohan said:
I've never used Flashfire and haven't updated through OTA since, 2014-ish. :laugh: I'm mainly going on theoretical knowledge here... On my Nexus I used fastboot to flash the factory image (until I switched to ROM flashing in TWRP) and now I just flash the full update package that OnePlus provides in TWRP.
Click to expand...
Click to collapse
I've tried installing TWRP permanently, but the moment I have installed an official patch, it got wiped - and I haven't found any docs how to prevent that.
My main use for Magisk is that all my system modifications are still there after I update my phone. Drastically cuts down on the time it takes to set my phone up after an update.
Click to expand...
Click to collapse
What settings are you referring to?
niko26 said:
I've tried installing TWRP permanently, but the moment I have installed an official patch, it got wiped - and I haven't found any docs how to prevent that.
Click to expand...
Click to collapse
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
What settings are you referring to?
Click to expand...
Click to collapse
I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.
Didgeridoohan said:
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
Click to expand...
Click to collapse
Well, TWRP is gone after an update - I can't boot into it.
[/quote]I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.[/QUOTE]
Hm, I am not sure if I get you right. If it is about apps, I use Titanium Backup to recover my old apps+settings.
system files
Most of the setting you mentioned are messing with the system files. "debloating" or removing and system applications with titanium backup will fail a system check with OTA update. You can freeze the apps i believe.
I changing the screen density and boot scripts. These are all system files locations.
I have had an ota work be re-installing the system apps from titanium backup and reverting all the other changes when it was failing before. Think this was back on android 6.0 though.
Didgeridoohan said:
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.
Click to expand...
Click to collapse
automattic said:
Most of the setting you mentioned are messing with the system files. "debloating" or removing and system applications with titanium backup will fail a system check with OTA update. You can freeze the apps i believe.
I changing the screen density and boot scripts. These are all system files locations.
I have had an ota work be re-installing the system apps from titanium backup and reverting all the other changes when it was failing before. Think this was back on android 6.0 though.
Click to expand...
Click to collapse
Since all of the things I mentioned are done with Magisk, none of them will cause an OTA to fail...
Reinstalling system apps will not work, since nowadays an OTA will fail just by mounting /system as rw.
Hi guys, trying to install latest OTA patch for Pixel 2. I am assuming process would be the same. I tried to follow the guide but hit the bump immediately. I can't see "Restore Stock Boot" when pressing uninstall. But there is restore images option. Hitting it does nothing, I receive the message that there are no backups. Where does the backup go so I can put the original file for it to be reinstalled?
Disclaimer: Your warranty will be void, use at your own risk. YOU are choosing to make these modifications and I am not responsible for any damages these changes might do to your device or sanity.
Hi.
Based on the feedback from this thread, the following steps can be used to aquire root on the SM-T590. The process is quite similar to rooting other devices by using Magisk. It might also work on other versions of the SM-T59x family, which can be OEM unlocked (sorry Verizon users).
Obtain the boot image
Get the firmware that matches the version installed on your device. This is important, otherwise you can easily end up in a bootloop.
Extract the AP tar.md5 file, e.g. "AP_T590XXU2ARJ1_CL14463952_QB20043720_REV00_user_low_ship_MULTI_CERT_meta.tar.md5".
Upon the extracted files, there is a file called boot.img.lz4. Extract it. Important: Most standard compression tools, e.g. 7-zip, are unable to extract lz4 compression ccorrectly. Use the offical lz4 binary from your Linux distribution or get the Windows version here. Once extracted, you should have a file called boot.img.
Patch the boot image
Copy the boot.img file to your device.
Download and install the Magisk Manager apk from the offical Magisk Thread.
In Magisk Manager settings, set the image format to "img.tar".
Enable the "Keep AVB2.0/dm-verity" in the Magisk main screen.
Hit "Install" and select "Patch boot image".
Select the boot image copied previously to your device.
Once finished, the patched image will be located in the Download directory on the internal storage.
Copy the patched image back to your PC.
Unlock and flash
Go into settings and enable developer settings.
In the developer settings, select OEM unlock, read the help text and enable the unlock, if you consent.
Once the device is factory reset and rebooted, turn the device off.
Boot the tablet into download mode.
Flash the patched boot image with Odin in the AP-slot
Reboot, Install Magisk Manager apk again and check if root is available.
Have fun.
Thanks to @gscollier, @airmaxx23 and @EinsamerSpieler for testing.
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology
J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
did you find a solution?
stupid question
I know this is a dumb question but where do you get the firmware....
Also was wondering if that reboot thing is still an issue.
I'll still root, I would like to try the LineageOS, eventually... how well does this work with Android apps/F-droid?
Update: still looking for confirmation on which boot image to use... guess you can't do a backup before flashing like you used to be able to do.
I installed heimdall and adb both seem to work
heimdall instructions
User848 said:
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology
Click to expand...
Click to collapse
the same happens to me.
I also tried removing some microsoft apps with Titanium, but after removing the excel, it goes to a kernel panic...
And then there's the "Security notice" from "SecurityLogAgent" notifications (unauthorised actions have been detected, unauthorised access to a secured area)
any solutions, followed steps but no root
I have the same problem Root is present but once i try to rename a file in /system/app, the device reboots.
Using SM-T590 with canadian image:T590XXU2ASC1
Using Magisk version V7.1.2(208) - V19.1 (19100)
I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.
Quick help please, I have the patched boot image on my pc but when I click the AP slot on odin it doesnt detect it only finds tar, md5 files etc. in the settings i cant change the format to .tar there is no option.
IET_DEMO said:
I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.
Click to expand...
Click to collapse
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time
mingkee said:
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time
Click to expand...
Click to collapse
Well I did it on android 8.1.0, seems like it work on Oreo too
IET_DEMO said:
Well I did it on android 8.1.0, seems like it work on Oreo too
Click to expand...
Click to collapse
How about Titanium Backup?
It works on rooted T510
mingkee said:
How about Titanium Backup?
It works on rooted T510
Click to expand...
Click to collapse
I dont have or use Titanium Backup, I usually clone my devices with twrp backup
There needs to be a better option that works without the current issues when rooting. You either end up with reboots or can not log in to Samsung account at all
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Would it work on 595? Bootloaders should be the same without boot loop?
vq8acsxht said:
Would it work on 595? Bootloaders should be the same without boot loop?
Click to expand...
Click to collapse
I honestly don't know as I don't have a 595. I took a chance on mine and it worked
kidkrooks said:
I honestly don't know as I don't have a 595. I took a chance on mine and it worked
Click to expand...
Click to collapse
Mine is on it's way. I will try it when I get it. I think bootloaders should be same in in both 590/595.
kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Does this still have "Modifying system files leads to reboot" issue or it's solved ?
Fairly newbie user here. I'm looking for a guide that lists how to upgrade the P5 to a new firmware and keep Magisk and all of that. I've looked at the thread below and it is good for getting started up in the beginning, but I'm not following how it works for a new firmware.
[Tutorial] Unlock Bootloader, get root and valid Safetynet
04/09/21 v2 Just install this Module via magisk manager: https://forum.xda-developers.com/attachments/hardwareoff_1-1-zip.5058405/ which is mentioned by this thread...
forum.xda-developers.com
Like how do I flash the new February firmware onto my phone?
Do I then copy the boot.img to the P5 and patch it with Magisk?
Then do I copy the patched boot.img back to my PC and flash it back onto the P5?
Are there are new step or process for unlocking SafetyNet?
I'm just very confused and would appreciate something simple and basic to follow, please.
Thanks!
1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot
UPDATING Pixel 5 Factory Image & Re-Rooting
Why This Thread? I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for...
forum.xda-developers.com
You can bypass safetynet perfectly with hiddencore module for xposed.
HiddenCore Module | Xposed Module Repository
repo.xposed.info
Xposed is dead since Android 10 and higher, so forget about the post of VD171. Sorry if I#m wrong with that, but never heard of working xposed on Pixels (with newest firmware).
cescman said:
1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot
Click to expand...
Click to collapse
This will work definitely fine. Don't mess with uninstalling Magisk as whole application, just disable the modules. Otherwise it will cause bootloops.
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.
hanni2301 said:
Xposed is dead since Android 10 and higher, so forget about the post of VD171. Sorry if I#m wrong with that, but never heard of working xposed on Pixels (with newest firmware).
This will work definitely fine. Don't mess with uninstalling Magisk as whole application, just disable the modules. Otherwise it will cause bootloops.
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.
Click to expand...
Click to collapse
Xposed and Xposed modules are working perfectly on ANDROID 10.
So forget about post of hanni2301, lol
hanni2301 said:
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.
Click to expand...
Click to collapse
I have tried few years ago, in some previous version of android, instead of running flash-all.bat, I flash each image individually, (fastboot flash bootloader..., fastboot flash boot..., fastboot flash recovery.... etc. ). If I took the shortcut of not flashing the original boot image first and then the patched one, but flash the patched boot directly, then the phone run into a bootloop.
cescman said:
1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot
Click to expand...
Click to collapse
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.
Ewto16 said:
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.
Click to expand...
Click to collapse
My friend, you can find a huge a mount of videos about it in youtube.
Adb is NOT for flashing.
Taken care or you can damage your device.
You need to READ and learn first, before to try anything.
If you try to search it, certainly you will find it.
VD171 said:
My friend, you can find a huge a mount of videos about it in youtube.
Adb is NOT for flashing.
Taken care or you can damage your device.
You need to READ and learn first, before to try anything.
If you try to search it, certainly you will find it.
Click to expand...
Click to collapse
Thanks, I appreciate the advice. I was able to follow the initial tutorial on how to setup my phone the first time, but it is well written out step by step. The other guides I've seen for upgrading just sort of breeze through the steps, assuming you know what you are doing.
My phone actually updated to the February release today, which broke my Magisk and lost me my Props configurations. I just want to get those things back.
Ewto16 said:
Thanks, I appreciate the advice. I was able to follow the initial tutorial on how to setup my phone the first time, but it is well written out step by step. The other guides I've seen for upgrading just sort of breeze through the steps, assuming you know what you are doing.
My phone actually updated to the February release today, which broke my Magisk and lost me my Props configurations. I just want to get those things back.
Click to expand...
Click to collapse
Next time, don't flash the factory image. Sideload the OTA.zip instead. That way you won't lose any of that.
Sideload the OTA, flash the patched boot.img (the boot.img you need to get from the factory image though), and you won't lose Magisk, your modules, or your root settings.
I used to do the same. Edit out the -w flag from the flash-all and re- setup my phone. Sideloading the OTA is easier and quicker in the end.
Ewto16 said:
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.
Click to expand...
Click to collapse
1. Yes
3. Edit the flash-all.bat file with any editor, e.g. notepad in windows, you will see -w near the end of the file, remove it, then save and run the file. You must make sure the -w is removed, otherwise all the data will be wiped
4. To boot into bootloader: adb reboot bootloader
To flash the patched boot image: fastboot flash boot magisk_ patched.img (the file name changes every time, just use the one you have when you patch the boot image)
It's easier to replace the "-w" with "--skip-reboot" (first one is double dashes). The phone won't reboot when the image flashing is complete so you can immediately re-flash the patched boot img.
This youtube video is great to follow and has clear step by step guide.
Thanks for the help and tips everyone. I really appreciate it! I was able to get my phone updated and re-rooted.
The only issue I'm having now is that I can't use GPay for contactless payments. When I go to try and use GPay, i get a slashed out line through the contactless payment symbol. It doesn't let me do anything with it from there.
I am on the Feb update, with Magisk installed, and the Universal SafetyNet Fix 2.0.0 module installed. I also have the MagiskHide Props Config module loaded. I pass the SafetyNet Check, but I can't do contactless payments.
I have Magisk hidden from GPay as well.
Any thoughts?
Ewto16 said:
Thanks for the help and tips everyone. I really appreciate it! I was able to get my phone updated and re-rooted.
The only issue I'm having now is that I can't use GPay for contactless payments. When I go to try and use GPay, i get a slashed out line through the contactless payment symbol. It doesn't let me do anything with it from there.
I am on the Feb update, with Magisk installed, and the Universal SafetyNet Fix 2.0.0 module installed. I also have the MagiskHide Props Config module loaded. I pass the SafetyNet Check, but I can't do contactless payments.
I have Magisk hidden from GPay as well.
Any thoughts?
Click to expand...
Click to collapse
Have you actually tried to use your phone at a pay terminal?
My device also passes safetynet but has contactless crossed out. However, it still works at payment terminals.
swangjang said:
Have you actually tried to use your phone at a pay terminal?
My device also passes safetynet but has contactless crossed out. However, it still works at payment terminals.
Click to expand...
Click to collapse
I have not attempted to use it yet. I just assumed that it wouldn't work since it was crossed out. I will have to give it a try.
Ewto16 said:
I have not attempted to use it yet. I just assumed that it wouldn't work since it was crossed out. I will have to give it a try.
Click to expand...
Click to collapse
On my device, I uninstalled the Google pay app and used the built-in "cards and passes" that shows up when you long press the power button.
swangjang said:
On my device, I uninstalled the Google pay app and used the built-in "cards and passes" that shows up when you long press the power button.
Click to expand...
Click to collapse
Interesting....I thought those were one and the same. Thanks for the tip. I'll give that a try.
I'd still like to get GPay working again though.
VD171 said:
Xposed and Xposed modules are working perfectly on ANDROID 10.
So forget about post of hanni2301, lol
Click to expand...
Click to collapse
And the Pixel 5 is on ANDROID 11.
So forget about post of VD171, lol^2
hanni2301 said:
And the Pixel 5 is on ANDROID 11.
So forget about post of VD171, lol^2
Click to expand...
Click to collapse
Grow up, my friend.
Anything can changes from device to device.