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.
Related
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?
I know how to root with magisk and enable camera2api module. (by flashing patched_boot.img) but then , phone wont update, it shows up error. Is there a way to have google camera working and OTA enabled? many thanks
djavo22 said:
I know how to root with magisk and enable camera2api module. (by flashing patched_boot.img) but then , phone wont update, it shows up error. Is there a way to have google camera working and OTA enabled? many thanks
Click to expand...
Click to collapse
No you temporarily have to flash stock boot, do the update, flash patched boot image and enable camera2api again
If you wish to install root just to enable camera2 api, do it via adb shell.
Then uninstall magisk, flash stock boot on partition a, check the camera2 api is it still enabled, it should be.
Do not change any other setting to the system or system files, just enable camera2 api via adb shell, and after root is gone, when you uninstall it, the OTA will work.
Mine is working, I updated last OTA with no problems, so I'm talking in first hand here.
O yeah, and mine camera2 api stayed enabled after OTA update.
minnuss said:
If you wish to install root just to enable camera2 api, do it via adb shell.
Then uninstall magisk, flash stock boot on partition a, check the camera2 api is it still enabled, it should be.
Do not change any other setting to the system or system files, just enable camera2 api via adb shell, and after root is gone, when you uninstall it, the OTA will work.
Mine is working, I updated last OTA with no problems, so I'm talking in first hand here.
O yeah, and mine camera2 api stayed enabled after OTA update.
Click to expand...
Click to collapse
Did you relock bootloder or get the ota with unlock bootloader?
minnuss said:
If you wish to install root just to enable camera2 api, do it via adb shell.
Then uninstall magisk, flash stock boot on partition a, check the camera2 api is it still enabled, it should be.
Do not change any other setting to the system or system files, just enable camera2 api via adb shell, and after root is gone, when you uninstall it, the OTA will work.
Mine is working, I updated last OTA with no problems, so I'm talking in first hand here.
O yeah, and mine camera2 api stayed enabled after OTA update.
Click to expand...
Click to collapse
can you please post further instructions step by step?
ki69 said:
Did you relock bootloder or get the ota with unlock bootloader?
Click to expand...
Click to collapse
Not needed.
minnuss said:
If you wish to install root just to enable camera2 api, do it via adb shell.
Then uninstall magisk, flash stock boot on partition a, check the camera2 api is it still enabled, it should be.
Do not change any other setting to the system or system files, just enable camera2 api via adb shell, and after root is gone, when you uninstall it, the OTA will work.
Mine is working, I updated last OTA with no problems, so I'm talking in first hand here.
O yeah, and mine camera2 api stayed enabled after OTA update.
Click to expand...
Click to collapse
Bro can u shw us step by step process !!
Sid.Boi said:
Bro can u shw us step by step process !!
Click to expand...
Click to collapse
X2
Sid.Boi said:
Bro can u shw us step by step process !!
Click to expand...
Click to collapse
Follow what he said, it's not hard and all the information can be found easily.
Can any of you that have enabled Cam2API tell us, does it make a difference in the OEM Cam app? I know it allows a GCam port to work, which is awesome, but any difference in OEM app?
thnx
You can all do it if you are still in software version 9.6.10.0 (Android One August update), or if you knew how to root your phone on the version that you have right now.
Go to this tool, https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
Then follow this steps.
https://forum.xda-developers.com/showpost.php?p=77611720&postcount=51
I edited this quote for all of you for better understanding.
"Then I tried to use number 7. enable camera2 api, and the problem is that it did not install root correctly, when phone reboots, the user must download full magisk, then the proper root will function.
After enabling camera2 api, which i did manually with adb shell, it will pop up on screen to allow access with root privileges.
adb shell
su
When you enter su, it will pop up on phone screen to allow access with root privileges, allow it for one time, if it is not pop upping on the phone for root, then the root on the phone is not properly installed.
And then type
setprop persist.camera.HAL3.enabled 1
After that, complete uninstall of magisk from option within magisk itself, and when magisk reboot the phone in the process of uninstalling, quickly hold power and down volume button, go to fastboot and flash on both partitions stock boot.img.
Put the stock boot.img of the version of the phone you currently have to adb folder.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Check is the camera2 api enabled after the restart.
That was the correct steps for me."
For me I used MagiskHide props config module to enable camera2
you don't need to fully uninstall magisk to receive otas, just restore images from magisk, receive the update and then install magisk to the inactive slot and use the reboot option in magisk (don't reboot normally)
Does anybody know if the Video is also improved when using Gcam apk?
I can't find any online samples.
Nebrassy said:
For me I used MagiskHide props config module to enable camera2
you don't need to fully uninstall magisk to receive otas, just restore images from magisk, receive the update and then install magisk to the inactive slot and use the reboot option in magisk (don't reboot normally)
Click to expand...
Click to collapse
Can You Please Tell Me The Proper Proceedure. .
I Don't want my phone bricked.
I'm in august patch and having magisk installed with some system changes.
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
Nebrassy said:
For me I used MagiskHide props config module to enable camera2
you don't need to fully uninstall magisk to receive otas, just restore images from magisk, receive the update and then install magisk to the inactive slot and use the reboot option in magisk (don't reboot normally)
Click to expand...
Click to collapse
Can U Please Tell The Steps Broadly?
rafihasan710 said:
Can You Please Tell Me The Proper Proceedure. .
I Don't want my phone bricked.
I'm in august patch and having magisk installed with some system changes.
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
Can U Please Tell The Steps Broadly?
Click to expand...
Click to collapse
If you only used magisk modules and didn't touch /system, just follow the instructions here
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you made any modifications to /system or just mounted it writable, you need to re flash the system image
Get the august fastboot image, unpack and flash system.img to your current slot, then follow the guide i linked
And don't worry you won't brick it, the update will just fail if you did anything wrong
Nebrassy said:
If you only used magisk modules and didn't touch /system, just follow the instructions here
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you made any modifications to /system or just mounted it writable, you need to re flash the system image
Get the august fastboot image, unpack and flash system.img to your current slot, then follow the guide i linked
And don't worry you won't brick it, the update will just fail if you did anything wrong
Click to expand...
Click to collapse
Thank You For The Instruction..
I've modified the system like camera2api and some magisk module....
If i flash the system.img what will change?
And how to do that?
How to flash system.img in current slot?
rafihasan710 said:
Thank You For The Instruction..
I've modified the system like camera2api and some magisk module....
If i flash the system.img what will change?
And how to do that?
How to flash system.img in current slot?
Click to expand...
Click to collapse
That restores the system to stock without modifications
Alternatively, you can just download the latest fastboot image and just flash the whole thing so you won't need to update after that
If you want to just flash system.img and then let your phone update, download the image I linked, extract it, open the images folder, it has system.img
open cmd/terminal, type fastboot getvar current-slot
if the current slot is a, then fastboot flash system_a <path to system.img>
like fastboot flash system_a D:\images\system.img
if the slot is b then use system_b
If you decide to just download the latest image instead, use miflash, instructions are on miui website, just be careful not to wipe data or lock the bootloader (it does that by default)
Nebrassy said:
That restores the system to stock without modifications
Alternatively, you can just download the latest fastboot image and just flash the whole thing so you won't need to update after that
If you want to just flash system.img and then let your phone update, download the image I linked, extract it, open the images folder, it has system.img
open cmd/terminal, type fastboot getvar current-slot
if the current slot is a, then fastboot flash system_a <path to system.img>
like fastboot flash system_a D:\images\system.img
if the slot is b then use system_b
If you decide to just download the latest image instead, use miflash, instructions are on miui website, just be careful not to wipe data or lock the bootloader (it does that by default)
Click to expand...
Click to collapse
Thanks.....
Can You Give The Download Link Of August System.img file.
Jeez what a nightmare... I'm not able to flash the system image at all, fastboot keeps giving random errors on both linux and windows.
rafihasan710 said:
Thanks.....
Can You Give The Download Link Of August System.img file.
Click to expand...
Click to collapse
extract from this
http://bigota.d.miui.com/V9.6.10.0....0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz
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 ?
EDIT: This is not for the TWRP version. I will update this thread soon!
Hello!
Since I saw a lot of people asking, I decided to post how to root a Mi 11 (as of 2021-02-11).
Install the Xiaomi.eu ROM. You can find more details in this post. Keep the ROM's files, you will need some of them!
Connect your phone to the PC and put it into file transfer mode.
Download Magisk Manager from the official GitHub repository and install the APK. DO NOT DOWNLOAD MAGISK MANAGER FROM ANYWHERE ELSE. THIS GITHUB REPOSITORY IS THE ONLY OFFICIAL, TRUSTED SOURCE.
In the directory you extracted the ROM zip file to, there's a directory called images. This directory contains a file called boot.img. Copy the boot.img to your phone's Download folder.
Open the Settings app, go to My Device, then tap MIUI Version until it says You are now a developer.
Go back to your Settings app and use the search bar to search for USB Debugging and enable it. Click on Yes when it asks whether you want to trust this computer.
Once the file is completely copied, open Magisk Manager on your phone. There will be 2 categories: Magisk and Manager. On the Magisk category, click on Install and choose Select and Patch a File. Navigate to your downloads and select boot.img. Click on Let's go.
When Magisk has finished patching your boot.img file, it will say Output file written to /storage/emulated/0/Download/magisk_patched_XXXXX.img, where XXXXX is 5 random letters/digits.
Open a command prompt on your computer and run adb pull /sdcard/Download/magisk_patched_XXXXX.img , replacing XXXXX with the random characters Magisk showed you earlier. This will copy the file to the directory you are currently in; on Windows, if you are using cmd, this will be C:\Users\[your username].
Reboot your phone into fastboot mode by turning it off, then holding the power and volume-down buttons until it vibrates.
Run the commands fastboot flash boot_a magisk_patched_XXXXX.img and fastboot flash boot_b magisk_patched_XXXXX.img (notice the difference: boot_a and boot_b). Don't forget to replace XXXXX with the random characters Magisk Manager generated. Run the command fastboot reboot and open the Magisk Manager app when your phone has finished rebooting. The app should say that it needs to install some other components; click yes and let it do its thing. It will reboot the phone, and after that, Magisk and therefore the root should be working!
When I first did this, my SafetyNet check failed. I fixed this by repeating all the steps, except that I updated the ROM instead of reinstalling it. You can update it even if it's the same version; it will just flash everything again. You may need to clear the cache of Google Play and reinstall Google Pay if the SafetyNet check initially failed.
Hi, I tryed fastboot oem unlock after alow it in developer settings but it says token verification failed.
It is my first Xiaomi, afert came from a OnePlus 5.
How can I manage to flash the boot image?
PandaKiller said:
Hi, I tryed fastboot oem unlock after alow it in developer settings but it says token verification failed.
It is my first Xiaomi, afert came from a OnePlus 5.
How can I manage to flash the boot image?
Click to expand...
Click to collapse
You do not need to use the OEM Unlock option in the developer options. Mine is still off even after I unlocked my bootloader. You need to use the Xiaomi Unlock Tool found at https://en.miui.com/unlock/ .
Before using this tool, you need to log in to you Mi account on your phone. Then, reboot the phone into fastboot mode, connect it to your PC, and use the unlock tool. It will tell you to wait 168 hours (1 week) before trying again. DO NOT RETRY BEFORE THE 168 HOURS ARE OVER OR THE TIMER RESETS! Even if you are a single minute early, it will reset the timer.
Once the week has passed, do this again and your phone will be unlocked. Warning: This will erase your data.
You should prepare the boot image BEFORE unlocking, because otherwise you will have to go through the phone's setup, install Magisk, patch the image, and wipe the phone again.
Another warning: Do not re-lock your bootloader. If the bootloader is re-locked with any ROM other than the one the phone shipped with installed, the phone gets bricked.
Thank you for the explanation.
I did everything as you said, now just need to wait for the painfully 168 hours...
Is there already a .zip to flash in order to disable encryption? Just to not risk losing my data in future updates.
PandaKiller said:
Thank you for the explanation.
I did everything as you said, now just need to wait for the painfully 168 hours...
Is there already a .zip to flash in order to disable encryption? Just to not risk losing my data in future updates.
Click to expand...
Click to collapse
If you use the Xiaomi.EU ROM, you can update without wiping your data. They give you 2 scripts - 1 for installing and 1 for updating.
Thanks for the write-up. Worked like a charm (Y)
Hi Lucavon,
Thx for the guide. I did it twice and after reboot and launch Magisk Manager I got no message asking that other components need to be installed. Did I miss something?
Giova19 said:
Hi Lucavon,
Thx for the guide. I did it twice and after reboot and launch Magisk Manager I got no message asking that other components need to be installed. Did I miss something?
Click to expand...
Click to collapse
Magisk manager has changed a bit in version 22. It may no longer require this extra step. If everything works as expected, it should be fine.
Lucavon said:
Magisk manager has changed a bit in version 22. It may no longer require this extra step. If everything works as expected, it should be fine.
Click to expand...
Click to collapse
Ok noted. I rooted following the full process 3 times and cannot get the safenet.
If i pdate the eurom how i root again? i must the process again? Sry for my Bad English!
Giova19 said:
Ok noted. I rooted following the full process 3 times and cannot get the safenet.
Click to expand...
Click to collapse
That's weird, it works perfectly fine for me. Maybe you need to re-download your Xiaomi.eu ROM.
xXSkylinexX said:
If i pdate the eurom how i root again? i must the process again? Sry for my Bad English!
Click to expand...
Click to collapse
Yes, you need to repeat it. After updating, copy the boot image, patch it again, etc, like in this post.
Hi.
I follow step by step with stable 12.5. (clean install)
Safetynet failed (cts profile failed)
I try safetynet fix 1.1.1 or 2.0.0 and nothing work.
Any solution ?
Plathoon said:
Hi.
I follow step by step with stable 12.5. (clean install)
Safetynet failed (cts profile failed)
I try safetynet fix 1.1.1 or 2.0.0 and nothing work.
Any solution ?
Click to expand...
Click to collapse
Do you have magisk hide enabled?
If you do and you're checking safetynet status with a different app than magisk manager, you need to add it to hide.
Magisk hide is enabled too
SOLVED
- enable magiskhide
- download "magiskhide props config"
- use app like termux and follow steps :
* "su"
* "props"
* "1" (edit device fingerprint)
* "f" (pick a certified fingerprint)
* select your phone
* accept and reboot.
and now it work.
Hello,
I followed all the steps in the root guide. I also have root access. However, I do not have write access to the root directory. What I have done wrong? I have no more idea what it could be. Can someone help me?
Note: I installed the Rom Version xiaomi.eu_multi_MI11_21.3.31_v12-11-fastboot
After installing the Rom, the following error message appeared at the end.
fastboot: error: Cannot generate image for userdata
Can it have anything to do with it?
Lucavon said:
Run the commands fastboot flash boot_a magisk_patched_XXXXX.img and fastboot flash boot_b magisk_patched_XXXXX.img (notice the difference: boot_a and boot_b).
Click to expand...
Click to collapse
Why don't write directly fastboot flash boot_ab magisk_patched_XXXXX.img ? Is that intended ?
bert4711 said:
I followed all the steps in the root guide. I also have root access. However, I do not have write access to the root directory. What I have done wrong? I have no more idea what it could be. Can someone help me?
Click to expand...
Click to collapse
Idk if I was having and same issues, but for me on 3.31 xiaomi.eu I was having issues with the superuser prompt not appearing. I found it happened only when the magisk app was repackaged. Approving prompts while it was unhidden then hiding magisk worked great.
Edited
I use the root explorer, the root query also appears with Magisk. But I still don't get write access to the root directory. I originally had the Global Rom V12.0.4.0.RKBMIXM on it. After the bootloader was open, I flashed the Rom Version xiaomi.eu_multi_MI11_21.3.31_v12-11-fastboot. The following error message occurred at the end of the flash process. fastboot: error: Cannot generate image for userdata I am currently assuming that the problem with root has something to do with it. I have already tried the Version xiaomi.eu_multi_MI11_V12.5.1.0.RKBCNXM_v12-11-fastboot. The result is the same... fastboot: error: Cannot generate image for userdata and no write permissions in the root directory ...
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...