Related
**** The posted systemless kernel is only compatible with SuperSU 2.56!!! ****
*** Starting with SuperSU 2.60+ kernel can now be auto-patched for systemless root. ***
**As of 06 December 2015 flar2 has released ElementalX 6.02 for Sense Marshmallow **
* If you still desire a stock kernel with systemless root but want to use newer SuperSU see below *
Messed around with the boot.img from today's Marshmallow update and have made it compatible with systemless root.
Systemless root in general is experimental and so is the kernel. I've literally just made it and tested it enough to that it boots and apps are able to be granted root access, so flash at your own risk.
Kernel has been running without issue.
Other than systemless root compatibility, this kernel is completely stock and no other modifications made.
Intructions - Systemless:
Download kernel from here.
Download SuperSU 2.56 beta from this post (only one that works with this method of root).
Copy both to phone
Flash the image directly using TWRP (toggle from ZIP to IMG under install)
Immediately flash SuperSU-v2.56-20151030013730.zip afterwards.
Reboot
TWRP will notify of no SU when you reboot, click DO NOT INSTALL as TWRP needs to be updated to detect this root method (it only looks in /system)
Instructions - Traditional:
Download kernel from here.
Download SuperSU 2.52 beta from this thread (it's the M compatible version)
Copy both to phone
Flash the image directly using TWRP (toggle from ZIP to IMG under install)
Immediately flash BETA-SuperSU-v2.52.zip afterwards.
Reboot
Keeping stock kernel with updated SuperSU:
If you prefer running the stock kernel with systemless root and want to stay current on SuperSU versions you need a stock kernel when you update SuperSU. When SuperSU installs it tries to restore a backup it made of your boot.img from the last time SuperSU was installed. Since this was made before auto patching there won't be a backup. Also, in newer versions it detects if your device needs systemless or if it can modify /system. If TWRP hasn't been told to keep system read-only it will likely default to a /system install. So, if you want to keep stock kernel and systemless root there are two things you are going to need:
Stock Kernel: You can actually use the kernel provided for traditional root as a stock kernel for the purpose of these instructions.
Systemless Override: To guarantee that SuperSU gives you the systemless install over /system you need to create a file called ".supersu" with the line "SYSTEMLESS=true" and place it in /data in TWRP before you install (eg. /data/.supersu). Alternatively, you can download this one (extract from the ZIP and place in /data).
When the file is placed in /data flash the boot.img in TWRP and then flash SuperSU. It will make a backup when it installs so don't remove it as it will look for this backup again when you install an updated version.
Note: These are only to tide us over until HTC releases source allowing awesome devs like flar2 to work their kernel magic.
Not checked yet, but is systemless the only way to do it on 6.0 ?
Electronic Punk said:
Not checked yet, but is systemless the only way to do it on 6.0 ?
Click to expand...
Click to collapse
No, you can still do it by modifying /system, but Marshmallow made it so kernels had to be modified as well to allow root. @Chainfire took it a step further, since we already have to modify the boot.img we can modify it a little more and remove the need to alter /system and make it easier to accept OTA updates. The link I put in the OP explains it a little more, but here it is again.
Added root modified kernel for using "traditional" (modifies /system) root to the OP along with link to current Marshmallow compatible SuperSU.
I'm trying to do a systemless root. Just to confirm, I should flash the latest TWRP. Then from there flash the kernel then SuperSU both through TWRP?
mcta said:
I'm trying to do a systemless root. Just to confirm, I should flash the latest TWRP. Then from there flash the kernel then SuperSU both through TWRP?
Click to expand...
Click to collapse
If you still have stock kernel and no root you can just flash the latest SuperSU (v2.65).
If you're systemless already but don't have a backup you need to flash a boot.img that isn't already systemless modified as SuperSU will abort the install.
You can't flash the one in the OP for traditional (modifies /system) root and it will patch that one, but unless your set your /system partition to read-only, it will install using traditional root (this is the case with any unmodified boot.img not just this one because it's modified for traditional root). To make sure SuperSU installs using systemlesss you need to place the mentioned .supersu file in /data/ o make sure system is read-only in twrp. You also want to use latest SuperSU.
Just make sure you don't let TWRP install it's own SuperSU package that it includes. TWRP by default can't detect systemless root installs, so each time you reboot from TWRP it will warn that there is no root access on the device. It is important you make sure to click DO NOT INSTALL.
If you don't want to be bugged with the no root message in TWRP you can download this version which has the incompatible SuperSU package removed disabling the root check.
HAHAHAHAHA!!!!! Silly me...... it was written up there......
mcta said:
I'm trying to do a systemless root. Just to confirm, I should flash the latest TWRP. Then from there flash the kernel then SuperSU both through TWRP?
Click to expand...
Click to collapse
Okay, hopefully this is a stupid question, but I want to be sure before I flash something to boot.
I followed the instructions before the later versions of SuperSU betas came out, so I have the above linked custom boot image, but would like to be able to update to later versions. Can I safely assume that the boot_signed.img file I pulled out of ROM.ZIP in the Developer Edition Marshmallow RUU is the correct "stock" bootloader? Note that I ran the RUU, let it pause on accepting the license, then pulled the ROM.ZIP out of the temp folder to extract the binary.
Hi! Im pretty much new to rooting and I was wondering does the phone have to be S-OFF or S-ON. If it has to be S-OFF, how do you do it?
Thank you for help!
Hello, everyone!
TL;DR: You're about to perform a systemless root installation on your phone so make sure you have uninstalled Xposed Framework, uninstalled root, the device's bootloader is unlocked and your phone's boot image is in its untouched stock state. Then boot into TWRP and install SuperSU-v.279-SR3 or newer.
UPDATE 2017-01-19:
- Provided missing bootloader information regarding root. Thanks, @Charlita for the heads-up!
- Moved TL;DR section to the top.
UPDATE 2017-01-15:
- SuperSU-v.279-SR3 learned how to use systemless mode as default flashing method for Motos. This is great news as the installation process now is just a matter of flashing the SuperSU installer. The segmentation fault had been fixed on SR2 and this version also includes that fix.
- Included a TL;DR section.
UPDATE 2016-12-25:
- SuperSU-v.279-SR1 contains a regression bug regarding the "segmentation fault". Skip this version for now. I've already contacted Chainfire.
- suhide: as the Chainfire himself stated, the tool is a losing game so I'm not putting any further effort here.
UPDATE 2016-11-03:
- As of SuperSU-v2.78-SR3 boot image patching works out-of-the-box. Just install it and you're done!
- TWRP version 3.x works as expected.
- Unfortunately, SafetyNet checking fails as Google constantly updates the server-side code.
- WIP: Check if Chainfire's suhide are able to help here.
UPDATE 2016-08-08:
- Added a backup reminder.
- Added flashable zip systemless_root_enabler_by_glauberlima.zip.
After a few days playing with it, I finally managed to perform a systemless root install for our beloved Moto X 2014
Benefits:
- Install OTA updates when they arrive;
- SafetyNet checking will pass so Android Pay can be used (not available in Brazil yet).
Requirements (links below) :
- Android 6 Marshmallow
- Bootloader must be unlocked otherwise you won't be able to root your phone;
- Boot partition must be in its original untouched stock state otherwise, SuperSU installer won't be able to patch it;
- System partition must be untouched as well but a simple uninstall of applications that have changed it should be enough. This step is not mandatory but if your system partition remains changed SafetyNet checking will fail;
- Your device must be unrooted. SuperSU has the option "Completly remove root". Use it;
- If you have Xposed Framework installed, uninstall it;
- You'll need ADB and Fastboot in order to flash stock boot.img if applicable;
- TWRP. Version 3.0.2-2 works just fine. If you prefer 2x series, I highly recommend version 2.8.7.1;
- SuperSU-v2.79-SR3 zip installer (or a newer version). DO NOT TRY AN OLDER VERSION. WILL NOT WORK;
Install guide:
- Make a Nandroid backup first using TWRP;
- Uninstall Xposed Framework if applicable;
- Uninstall SuperSU;
- Connect your device to your computer via USB;
- Reboot into bootloader:
Code:
adb reboot-bootloader
- Restore stock boot partition (you can skip this step if you already been on stock boot):
Code:
fastboot flash boot xt1097_boot_stock_with_may_2016_update.img
VERY IMPORTANT: The binary file boot xt1097_boot_stock_with_may_2016_update.img is device dependent. I have extracted stock boot.img from victara May 2016 update full ROM package and put it here. If you are trying on the other variants, make sure you will use the right image.
- Reboot into Recovery (TWRP);
- Flash the attached zip file systemless_root_enabler_by_glauberlima.zip. This will set both variables SYSTEMLESS=true and BINDSYSTEMXBIN=false. Without these variables set, SuperSU will fail to systemless root the device. Feel free if you want to manually enter the commands in the Command Prompt:
Code:
adb shell "echo SYSTEMLESS=true>/data/.supersu"
adb shell "echo BINDSYSTEMXBIN=false>>/data/.supersu"
- Install SuperSU and reboot system. If the first boot fails, just wait - the second will work I promise you!
- As soon as Android UI shows up you should be systemless rooted;
- Confirm SuperSU is installed by recognizing the green icon on your app drawer;
- Open up any root app you have. The world-famous Superuser permission request dialog should pop-up;
- Install SafetyNet Helper, in order to attest your Android, is passing Google's SafetyNet checking: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Now you should be good. Congrats!
Go ahead and get some systemless apps:
- Systemless Xposed Framework
- Systemless Adaway
This procedure should work for the other variants too - all you need is the original boot.img
If you need any help feel free to ask.
Attached you can find the screenshots taken from my XT1097 after the procedure
Related links:
SuperSU-v2.79-SR3:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Latest stable SuperSU:
http://download.chainfire.eu/supersu-stable
Systemless Xposed Framework:
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Systemless AdAway:
http://forum.xda-developers.com/showthread.php?t=2190753
Material Design Xposed Installer:
http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Minimal ADB and Fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP for Moto X 2014:
http://forum.xda-developers.com/mot...recovery-twrp-2-8-0-0-touch-recovery-t2911523
Thanks:
@Chainfire
Even if I am on stock I have to flash boot*.img?
Sent from my XT1097 using Tapatalk
rtrotsky said:
Even if I am on stock I have to flash boot*.img?
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
Since your device already has the untouched stock boot you don't need to flash anything.
I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!
I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?
jbaumert said:
I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!
I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?
Click to expand...
Click to collapse
Could you provide your recovery.log from TWRP so we can see the detailed logging information?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip
This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.
glauberlima said:
Could you provide your recovery.log from TWRP?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip[code]
This will copy contents to the clipboard. Paste it in notepad then save and attach here.[/QUOTE]
This is pretty neat. Given what I read as the requirements am I correct this only works with stock ROM? (and test will only pass on stock).
Click to expand...
Click to collapse
vpxf said:
This is pretty neat. Given what I read as the requirements am I correct this only works with stock ROM? (and test will only pass on stock).
Click to expand...
Click to collapse
Hi @vpxf
The unmodified boot.img is a requirement for SuperSU as it tries to patch the boot image on-the-fly during the install process (by the time you flash it using TWRP). If the image is not in its original state, SuperSU will fail to install in systemless mode.
Regarding your question about custom ROMs compatibility I don't know if the SafetyNet checking will pass/fail. That's a good test to perform.
glauberlima said:
Could you provide your recovery.log from TWRP so we can see the detailed logging information?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip
This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.
Click to expand...
Click to collapse
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".
NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.
As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.
bertolehm said:
As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.
Click to expand...
Click to collapse
jbaumert said:
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".
NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.
Click to expand...
Click to collapse
As stated by @bertolehm I've discussed in the other posts the exactly same issue with the zip installer you have reported @jbaumert. Take a look at them:
http://forum.xda-developers.com/showpost.php?p=67792193&postcount=1193
http://forum.xda-developers.com/showpost.php?p=67805517&postcount=1233
Regarding your device being systemless rooted check with SafetyNet Helper Sample app. If everything turns green you are good
** Duplicated **
Thanks for the tutorial.
The first boot fails, ok ; but how long is the second boot ?
I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little
oyoyl said:
Thanks for the tutorial.
The first boot fails, ok ; but how long is the second boot ?
I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little
Click to expand...
Click to collapse
Which variant is your X?
glauberlima said:
Which variant is your X?
Click to expand...
Click to collapse
XT1092
oyoyl said:
XT1092
Click to expand...
Click to collapse
15 minutes... That's definitely too much.
I'm about to update this guide with my new findings so If you don't mind I'd like to suggest you this:
Repeat the steps but this time skip the update to latest version. After the reboot access SuperSU. It should display a message regarding your su needs update. Accept it.
Make sure your nandroid backup is up to date.
Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.
I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...
Thanks
Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss
Hi! Hey, I followed the steps and my MotoX got stuck when rebooting after flashing. I'm trying to enter fastboot with power+Volume down but no luck so far, any idea? I hope you can help me!
oyoyl said:
Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.
I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...
Thanks
Click to expand...
Click to collapse
OK. Just leave a reply by the time you have the result of your test.
guilhermoaraujo said:
Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss
Click to expand...
Click to collapse
One of your installed apps modified system partition. Did you test on a completly stock image?
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.
I did as I usually do I updated my system and then reflashed vbmeta and root but for the latest update it didn't work.
If you're using magisk to root (and twrp), then after flashing the latest version (24.1 right now), boot into you system, open the apps drawer then close it and wait a little while. sometimes it takes a minute to load in that shortcut for installing the magisk app. if you managed to install the app, but you dont have root, open the app and make sure that you have both options on the home page installed (i believe its magisk, and magisk app). You need the top one for root, the bottom one is the one you just installed. Also make sure they are up to date, as sometimes outdated versions dont work. Or maybe the opposite is happening, and the newer version of magisk doesnt work for you, if thats the case then download the version you used before and flash that.
blocky3321 said:
I did as I usually do I updated my system and then reflashed vbmeta and root but for the latest update it didn't work.
Click to expand...
Click to collapse
Because the ota cancel magisk robot. U have to repatch new boot.img and reflash magisk
PhotonIce said:
If you're using magisk to root (and twrp), then after flashing the latest version (24.1 right now), boot into you system, open the apps drawer then close it and wait a little while. sometimes it takes a minute to load in that shortcut for installing the magisk app. if you managed to install the app, but you dont have root, open the app and make sure that you have both options on the home page installed (i believe its magisk, and magisk app). You need the top one for root, the bottom one is the one you just installed. Also make sure they are up to date, as sometimes outdated versions dont work. Or maybe the opposite is happening, and the newer version of magisk doesnt work for you, if thats the case then download the version you used before and flash that.
Click to expand...
Click to collapse
with the older versions i get suck in a boot loop and with the new version there is no root
blocky3321 said:
with the older versions i get suck in a boot loop and with the new version there is no root
Click to expand...
Click to collapse
Look into how to root discussion. I have uploaded boot.img patched from new 12.5.4
Open your eyes
wetito said:
Look into how to root discussion. I have uploaded boot.img patched from new 12.5.4
Open your eyes
Click to expand...
Click to collapse
i tried the boot and vbmeta it didnt work got stuck in a boot loop
It you have 12.5.4 firmware working 100% I have flashed on my device
wetito said:
It you have 12.5.4 firmware working 100% I have flashed on my device
Click to expand...
Click to collapse
tried again and got suck on the miui screen on fastboot reboot
blocky3321 said:
with the older versions i get suck in a boot loop and with the new version there is no root
Click to expand...
Click to collapse
i just tried rooting my phone with magisk 24.2 (latest at the moment). just follow the steps i listed in my first post and you'll have root.
PhotonIce said:
i just tried rooting my phone with magisk 24.2 (latest at the moment). just follow the steps i listed in my first post and you'll have root.
Click to expand...
Click to collapse
use magisk 24.1, because 24.2 it's a beta. it's buggy. my files are patched with 24.1
blocky3321 said:
tried again and got suck on the miui screen on fastboot reboot
Click to expand...
Click to collapse
1. Download the fastboot version of your rom here:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
I prefer 12.5.4 as it's not buggy, laggy as MIUI 13 and it has navigation button shortcuts, a new cool feature. Remind again, you must download Type fastboot, not Type recovery
2. Unzip downloaded rom, look for [rom name] folder -> images -> boot.img file
3. Copy that boot.img to your phone storage, any phone is fine
4. Run Magisk 24.1 on the any phone that got the boot.img file
5. Press Install
6. Choose Select and Patch a file
7. Navigate and choose the copied boot.img
8. You'll get something like this in your phone storage: magisk_patched-24100_VDv7z.img
9. Copy magisk_patched-24100_VDv7z.img to your PC
10. Install ABD 15 seconds installer, if not already done so
11. Get phone to fastboot mode
12. Use this command to enter fastbootd
Code:
fastboot reboot fastboot
13. Flash empty vbmeta.img:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Where is this vbmeta.img from? Check downloaded rom folder, look for [rom name] folder -> images -> vbmeta.img file
14. Use this command to flash your Magisk patched img:
Code:
fastboot flash boot magisk_patched-24100_VDv7z.img
Reminder: Each time Magisk patches an img file, it changes name randomly, so don't blindly input this command, you must change name too: fastboot flash boot [magisk patched boot name].img
15. Reboot to your phone's rom:
Code:
fastboot reboot
After enabling Zygisk, my device (LG V20 with Xposed Framework, AlphaOmega rom, MK2000 kernel, etc.) hangs on the boot animation. Unfortunately, I neglected to turn off encryption after my most recent attempt, so I cannot uninstall Magisk through TWRP like before.
Because the device cannot reach the locker, I also cannot unlock it in order to turn off the pin/encryption. I tried to run "magisk --sqlite 'update settings set value=1 where [key]="zygisk"'" from ADB shell, but was told that "root is required for this operation."
Is there any way to turn off Zygisk (or uninstall Magisk completely) from within ADB, fastboot, or TWRP, or has Magisk completely hosed my device at this point?
Bill720 said:
After enabling Zygisk, my device (LG V20 with Xposed Framework, AlphaOmega rom, MK2000 kernel, etc.) hangs on the boot animation. Unfortunately, I neglected to turn off encryption after my most recent attempt, so I cannot uninstall Magisk through TWRP like before.
Because the device cannot reach the locker, I also cannot unlock it in order to turn off the pin/encryption. I tried to run "magisk --sqlite 'update settings set value=1 where [key]="zygisk"'" from ADB shell, but was told that "root is required for this operation."
Is there any way to turn off Zygisk (or uninstall Magisk completely) from within ADB, fastboot, or TWRP, or has Magisk completely hosed my device at this point?
Click to expand...
Click to collapse
if you can flash the original boot img of your rom in fastboot you'll be able to remove magisk
I made some progress on this.
jons99 said:
if you can flash the original boot img of your rom in fastboot you'll be able to remove magisk
Click to expand...
Click to collapse
boot1.img or boot2.img?
both I guess?
why you have 2 boot imgs?
jons99 said:
both I guess?
why you have 2 boot imgs?
Click to expand...
Click to collapse
No idea. I don't even know if they're valid anymore, since I'm on a custom rom and kernel. It's been years since I've installed this stuff, so I don't remember the specifics.
you know what you can do instead is just fastboot boot into your unrooted boot ing and open the magisk app disable zygisk and reboot this way you'll keep magisk
I made some progress on this. Somehow, the device is now bootable again, but Magisk will now not install from (any version of) the app or from recovery. TWRP still can't run the uninstaller because it thinks that the device is encrypted, even though I did remove the pin code.
Bill720 said:
I made some progress on this. Somehow, the device is now bootable again, but Magisk will now not install from (any version of) the app or from recovery. TWRP still can't run the uninstaller because it thinks that the device is encrypted, even though I did remove the pin code.
Click to expand...
Click to collapse
you don't need to run the uninstaller just change the .apk at the end of the magisk app to .zip and flash it in twrp
jons99 said:
you don't need to run the uninstaller just change the .apk at the end of the magisk app to .zip and flash it in twrp
Click to expand...
Click to collapse
That's what I did to get here. It installs from there, (despite the fact that TWRP asks for a password now) but the Magisk app still doesn't recognize it.
Bill720 said:
That's what I did to get here. It installs from there, (despite the fact that TWRP asks for a password now) but the Magisk app still doesn't recognize it.
Click to expand...
Click to collapse
if you have an old kernel you might need to flash an older version of magisk try v23 maybe
jons99 said:
if you have an old kernel you might need to flash an older version of magisk try v23 maybe
Click to expand...
Click to collapse
These results are with version 23.
ok try to see if you have an old backup of your boot partition that's already patched with magisk and try to restore it (make a backup of your existing boot partition first)
jons99 said:
ok try to see if you have an old backup of your boot partition that's already patched with magisk and try to restore it (make a backup of your existing boot partition first)
Click to expand...
Click to collapse
Not sure that I would've taken one of those.
well you can always patch the boot img with magisk and flash it in fastboot that always works
Bill720 said:
After enabling Zygisk, my device (LG V20 with Xposed Framework, AlphaOmega rom, MK2000 kernel, etc.) hangs on the boot animation. Unfortunately, I neglected to turn off encryption after my most recent attempt, so I cannot uninstall Magisk through TWRP like before.
Because the device cannot reach the locker, I also cannot unlock it in order to turn off the pin/encryption. I tried to run "magisk --sqlite 'update settings set value=1 where [key]="zygisk"'" from ADB shell, but was told that "root is required for this operation."
Is there any way to turn off Zygisk (or uninstall Magisk completely) from within ADB, fastboot, or TWRP, or has Magisk completely hosed my device at this point?
Click to expand...
Click to collapse
Try this:
Turn device off
Open ADB command line
Type adb wait-for-device shell magisk --remove-modules
Connect device to USB cable and boot
This should remove modules allowing a successful boot with root.
Did you post this question on Reddit? I just answered an identical question there yesterday lol
jons99 said:
well you can always patch the boot img with magisk and flash it in fastboot that always works
Click to expand...
Click to collapse
Where could I procure a clean boot.img file? Is that part of the rom, the kernel, or something else?
usually it's inside payload.bin from within the rom zip
jons99 said:
usually it's inside payload.bin from within the rom zip
Click to expand...
Click to collapse
Interesting. I extracted the AlphaOmega Rom .zip, and found no payload.bin, but there is a boot.img file in the "kernel" folder. Should I still use that, even if I don't use the kernel supplied with the rom?
you can always use fastboot boot instead of fastboot flash and just boot to this patched boot img you created and see if it works if not a reboot will remove it
jons99 said:
you can always use fastboot boot instead of fastboot flash and just boot to this patched boot img you created and see if it works if not a reboot will remove it
Click to expand...
Click to collapse
I'll have to try that next. Now, if I could just find a working fastboot driver for this device...