If you are looking for my guide on a different Pixel, find it here:
Pixel 3
Pixel 3XL
Pixel 3a
Pixel 4
Pixel 4XL
Pixel 4a
Pixel 4a (5G)
Pixel 5
Pixel 5a
Pixel 6
Pixel 6 Pro
For best results, use the latest stable Magisk release.
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Prerequisites:
Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
USB Debugging enabled
Google USB Driver installed
I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub
Spoiler: Unlock Bootloader
Follow these instructions to enable Developer Options and USB Debugging.
Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
Connect your device to your PC, and open a command window in your Platform Tools folder.
Ensure ADB sees your device:
Code:
adb devices
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
If you see "unauthorized", you need to authorize the connection on your device.
If you see the device without "unauthorized", you're good to go.
Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Code:
fastboot flashing unlock
Select Continue on the device screen.
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA:
Code:
adb reboot sideload
Once in recovery:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:
Code:
fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot <image-device-buildnumber.zip>
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.
Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>
PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.
For instructions, downloads, and support, please refer to the PixelFlasher thread.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet/Play Integrity
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.
Mod available here. Do not use MagiskHide Props Config with this mod.
This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check SafetyNet status:
YASNAC - GitHub
To check Play Integrity status:
Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.
I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.
Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
Hi, thank you for the guide. I am very new here and I have some questions that I hope you can answer before I proceed.
First of all, I assume I should back up my device on an external medium if I screw the pooch. With that in mind, do you have any suggestions/ links on guides that can help me with that? If not, I'm sure I can do some good digging to find something suitable.
Second, I'm not exactly sure what "Bonito" is and from what I have seen from googling, it seems to be connected to the LineageOS operating system. Is this different from the current, factory OS that my phone is running? Is there a way to root my device without changing the factory OS if that's the case? If not, that's okay, I don't mind switching to an open-source OS that seems to have a good reputation.
Third, is the guide supposed to be followed sequentially with the first step being, "Spoiler: Downloads" and the last step being, "Spoiler: Pass SafetyNet?" Or are the first 3 steps, "Spoiler: Downloads", "Spoiler: Unlock Bootloader" and, "Spoiler: Initial Root / Create Master Root Image" are essential steps and the subsequent steps afterwards are based on personal needs? Ideally, using Android Flash Tool seems painless and foolproof which is perfect for me. Afterwards, I will attempt to copy the Spoiler: Pass SafetyNet" step.
Fourth, what is your take on using Android Flash Tool vs TOOL ALL IN ONE for flashing? TOOL ALL IN ONE seems even more painless and fool-proof and apart from backing up, seems easier. But I would love your take on this?
Feel free to answer any or none of these questions. I know it's a lot but id rather ask questions to a staff member before proceeding?
Thanks again for the guide!
Cheetah_Bear said:
Hi, thank you for the guide. I am very new here and I have some questions that I hope you can answer before I proceed.
First of all, I assume I should back up my device on an external medium if I screw the pooch. With that in mind, do you have any suggestions/ links on guides that can help me with that? If not, I'm sure I can do some good digging to find something suitable.
Click to expand...
Click to collapse
Without root, there is no way to do a full backup including app data. The best you can do is sync your Pixel with your Google account.
Cheetah_Bear said:
Second, I'm not exactly sure what "Bonito" is and from what I have seen from googling, it seems to be connected to the LineageOS operating system. Is this different from the current, factory OS that my phone is running? Is there a way to root my device without changing the factory OS if that's the case? If not, that's okay, I don't mind switching to an open-source OS that seems to have a good reputation.
Click to expand...
Click to collapse
"Bonito" is Google's internal name for the device and has little to do with the software. The Pixel 5 is "redfin", the 5a is "bramble", the Pixel 2 was "walleye".
As far as rooting your device, yes - if you follow this guide, you will gain root on the stock OS. I am currently using my Pixel 5 with the OEM firmware, patched with Magisk.
Cheetah_Bear said:
Third, is the guide supposed to be followed sequentially with the first step being, "Spoiler: Downloads" and the last step being, "Spoiler: Pass SafetyNet?" Or are the first 3 steps, "Spoiler: Downloads", "Spoiler: Unlock Bootloader" and, "Spoiler: Initial Root / Create Master Root Image" are essential steps and the subsequent steps afterwards are based on personal needs? Ideally, using Android Flash Tool seems painless and foolproof which is perfect for me. Afterwards, I will attempt to copy the Spoiler: Pass SafetyNet" step.
Click to expand...
Click to collapse
This guide is not sequential; I provided different instructions for different scenarios. The downloads are simply the resources you will need. To attain root, simply follow the instructions under "Initial Root". When the June update is released, you can update using your method of choice, and follow the relevant instructions to regain root.
Cheetah_Bear said:
Fourth, what is your take on using Android Flash Tool vs TOOL ALL IN ONE for flashing? TOOL ALL IN ONE seems even more painless and fool-proof and apart from backing up, seems easier. But I would love your take on this?
Click to expand...
Click to collapse
I personally do not like using third party tools, and I simply use adb/fastboot. The Android Flash Tool is simply for flashing factory firmware and cannot flash custom images.
Cheetah_Bear said:
Feel free to answer any or none of these questions. I know it's a lot but id rather ask questions to a staff member before proceeding?
Click to expand...
Click to collapse
No worries. It sounds like you have a lot to learn but you're at the right place; XDA is full of knowledgeable people who can help you out.
Cheetah_Bear said:
Thanks again for the guide!
Click to expand...
Click to collapse
Thank you for your appreciation.
Well, with a bit of hard work and head-bashing into my desk, my phone is fully rooted and backed up. I want to extend my thanks again for this guide. I'll be sure to return when the next updates roles around.
I am still trying to play around with Safety Net and my financial app. YASNAC says my Saftey Net passes, but my finance app won't open because it's still, somehow, detecting root, even after being placed under the Deny List.
Regardless, that is a problem for another day. Today is a day of celebration because my phone is rooted and rocking.
Thank you again.
Cheetah_Bear said:
Well, with a bit of hard work and head-bashing into my desk, my phone is fully rooted and backed up. I want to extend my thanks again for this guide. I'll be sure to return when the next updates roles around.
I am still trying to play around with Safety Net and my financial app. YASNAC says my Saftey Net passes, but my finance app won't open because it's still, somehow, detecting root, even after being placed under the Deny List.
Regardless, that is a problem for another day. Today is a day of celebration because my phone is rooted and rocking.
Thank you again.
Click to expand...
Click to collapse
Make sure you're using USNF and MHPC; DenyList alone won't do it.
You may also have to block the Play Store due to Play Protect.
Can I do anything with my 3a XL if the OEM debugging is greyed out? Honestly, is it really moddless?
BadRx said:
Can I do anything with my 3a XL if the OEM debugging is greyed out? Honestly, is it really moddless?
Click to expand...
Click to collapse
Most likely not. There is no way to force unlock. If you bought a branded variant like Verizon, unlocking the bootloader is not possible.
V0latyle said:
Most likely not. There is no way to force unlock. If you bought a branded variant like Verizon, unlocking the bootloader is not possible.
Click to expand...
Click to collapse
Why is that? I find that sooo... disturbing. From a hobbyist point of view this is just so unacceptable. You mean to tell me that I can't flash the chips somehow on this phone? Now there was a way carrier lock... you mean to tell me there is no way to carrier unlock? Not even the carrier? That's... just hard to believe.
BadRx said:
Why is that? I find that sooo... disturbing. From a hobbyist point of view this is just so unacceptable. You mean to tell me that I can't flash the chips somehow on this phone? Now there was a way carrier lock... you mean to tell me there is no way to carrier unlock? Not even the carrier? That's... just hard to believe.
Click to expand...
Click to collapse
I'm talking about bootloader unlock. It is a well known fact, having been established since the original Pixel (if not the Nexus series) that Google devices sold through carriers such as Verizon are not bootloader unlockable. This is why if you want a completely unlocked device, you must buy directly from Google.
As far as carrier unlock...that depends on the carrier. If you bought your device from Google, it's already carrier unlocked. But if you bought it through a carrier, they may or may not unlock it depending on their own policies. I don't know what Verizon's is, but most US carriers will allow carrier unlock as long as 1) there is no lien on the device (it's paid off) and 2) your account is not under contractual obligations.
It may seem weird to you, but they're protecting their investments. You can't reasonably expect a carrier to provide you a device at a discount with no restrictions. Either buy used from Swappa, or new full price from Google, and use the carrier only as a carrier. If you buy a phone through them, don't expect the same freedom.
Hi, before spamming all my stuff here, is this the right place to ask for help in the process of rooting (installing magisk and patching the boot.img) my pixel 3a XL?
thank you
Alex
4L3xN3t said:
Hi, before spamming all my stuff here, is this the right place to ask for help in the process of rooting (installing magisk and patching the boot.img) my pixel 3a XL?
thank you
Alex
Click to expand...
Click to collapse
Did you read the OP?
V0latyle said:
Did you read the OP?
Click to expand...
Click to collapse
yes, I spent much more time on reading it and preparing the needed stuff than doing the process
if you're referring to the warning, yes, I'm quite familiar with ADB, Magisk, Android and Root, but not 100%. I've played with some devices in the past, but the last before the 3aXL was a Nexus6 and a lot of thing changed in the root process and I'm a bit confused.
anyway, if it's ok, I would try to explain what's appening, I got a bootloop at the last step of rooting
Alex
4L3xN3t said:
yes, I spent much more time on reading it and preparing the needed stuff than doing the process
if you're referring to the warning, yes, I'm quite familiar with ADB, Magisk, Android and Root, but not 100%. I've played with some devices in the past, but the last before the 3aXL was a Nexus6 and a lot of thing changed in the root process and I'm a bit confused.
anyway, if it's ok, I would try to explain what's appening, I got a bootloop at the last step of rooting
Alex
Click to expand...
Click to collapse
What Android build are you on? Did you update?
What version of Magisk are you using?
What process did you use to root?
V0latyle said:
What Android build are you on? Did you update?
What version of Magisk are you using?
What process did you use to root?
Click to expand...
Click to collapse
ok, well, so, as I said I've an unlocked Pixel 3aXL with a stock ROM (bonito-sp2a.220505.006).
I'm on a fresh configured PC and just downloaded the latest platform-tools, USB driver, factory image, Magisk 25.2 canary.
Followed the guide in this page for the initial root, so I installed magisk, took the boot.img from the factory image, copied into the phone and patched via Magisk app. copied the patched boot.img into my platform-tools folder and flashed on the phone from the recovery via fastboot.
Now, after rebooting, the bootloop came. I just fix it flashing back the factory image, but of corse i'm still not rooted.
Maybe something related to the two boot_a and boot_b slots?
reading the boot.img flashing log it said it was flashed on boot_a (unfortunately i didn't check the actual slot before, I suppose was still boot_a) but then when i flashed the factory image to get rid of the bootloop it went on boot_b.
So I suspect I could have a misalignment beetween the two slot, but I'm not sure at all and anyway don't know exactly how to align them.
thank you
4L3xN3t said:
ok, well, so, as I said I've an unlocked Pixel 3aXL with a stock ROM (bonito-sp2a.220505.006).
I'm on a fresh configured PC and just downloaded the latest platform-tools, USB driver, factory image, Magisk 25.2 canary.
Followed the guide in this page for the initial root, so I installed magisk, took the boot.img from the factory image, copied into the phone and patched via Magisk app. copied the patched boot.img into my platform-tools folder and flashed on the phone from the recovery via fastboot.
Now, after rebooting, the bootloop came. I just fix it flashing back the factory image, but of corse i'm still not rooted.
Maybe something related to the two boot_a and boot_b slots?
reading the boot.img flashing log it said it was flashed on boot_a (unfortunately i didn't check the actual slot before, I suppose was still boot_a) but then when i flashed the factory image to get rid of the bootloop it went on boot_b.
So I suspect I could have a misalignment beetween the two slot, but I'm not sure at all and anyway don't know exactly how to align them.
thank you
Click to expand...
Click to collapse
No, there's no "misalignment" between slots. Each slot has its own partitions, and the system will boot from whatever slot is active. So, since you're on Slot A, the system will load the boot image from /boot_a, and run the system from /system_a. It doesn't cross over.
When I asked "what build" are you running, I meant which Android release, not your phone type. I also asked how you updated - factory image or OTA?
Where did you download Magisk from? There is no "25.2 canary". The current Canary is 25203, but Stable should work just fine.
I suspect you may be doing something wrong, hence the bootloop. Rule of thumb: When you encounter a problem. ALWAYS make sure you're doing everything right, and don't assume there's something wrong with the system until you have gone back through the instructions and made sure you're doing everything correctly.
Word of advice: When someone asks you specific questions, make sure you answer all of them with as much detail as possible. The more information we have, the better we are able to help you.
V0latyle said:
No, there's no "misalignment" between slots. Each slot has its own partitions, and the system will boot from whatever slot is active. So, since you're on Slot A, the system will load the boot image from /boot_a, and run the system from /system_a. It doesn't cross over.
When I asked "what build" are you running, I meant which Android release, not your phone type. I also asked how you updated - factory image or OTA?
Where did you download Magisk from? There is no "25.2 canary". The current Canary is 25203, but Stable should work just fine.
I suspect you may be doing something wrong, hence the bootloop. Rule of thumb: When you encounter a problem. ALWAYS make sure you're doing everything right, and don't assume there's something wrong with the system until you have gone back through the instructions and made sure you're doing everything correctly.
Word of advice: When someone asks you specific questions, make sure you answer all of them with as much detail as possible. The more information we have, the better we are able to help you.
Click to expand...
Click to collapse
ok, sorry, you're right, I lost something.
I wrote "bonito-sp2a.220505.006" because it thought it gives the information that I'm on the last available update for this phone of android 12.1. I always updated via OTA (I think it could be also interesting to know that I hadn't Magisk installed or any other modification at the time of the last update).
about Magisk I assumed that "25203" means "a release (the third?) of the 25.2", my fault...but anyway yes, I have the canary 25203, used it instead of the stable because sometimes in the past with other phones using it was the solution to some installation issues but I think this is not the problem.
I repeated the process (only the 9 steps of the "Spoiler: Initial Root / Create Master Root Image" guide) more than once, so I'm trying to understand if there might be something else wrong or corrupted.
partially unrelated question about the slots: if I force to boot from the slot A I'm supposed to go back to the bootloop, right?
Did you have anything in mind about this?
thank you
4L3xN3t said:
ok, sorry, you're right, I lost something.
I wrote "bonito-sp2a.220505.006" because it thought it gives the information that I'm on the last available update for this phone of android 12.1. I always updated via OTA (I think it could be also interesting to know that I hadn't Magisk installed or any other modification at the time of the last update).
about Magisk I assumed that "25203" means "a release (the third?) of the 25.2", my fault...but anyway yes, I have the canary 25203, used it instead of the stable because sometimes in the past with other phones using it was the solution to some installation issues but I think this is not the problem.
I repeated the process (only the 9 steps of the "Spoiler: Initial Root / Create Master Root Image" guide) more than once, so I'm trying to understand if there might be something else wrong or corrupted.
partially unrelated question about the slots: if I force to boot from the slot A I'm supposed to go back to the bootloop, right?
Did you have anything in mind about this?
thank you
Click to expand...
Click to collapse
I generally recommend against switching slots unless absolutely necessary, and especially not if you update via OTA. The reason for this is if you force the device to boot from the "old" slot, Anti-Rollback Protection will kick in and cause a boot loop.
Since you're able to boot with the unpatched image, just flash that for the time being. Your device has to finish up the update after booting, and the rooted image can sometimes cause a problem with this. Once the device has been running for a bit, say 10 minutes or so, you should be able to safety flash the patched image.
Were you rooted before?
V0latyle said:
I generally recommend against switching slots unless absolutely necessary, and especially not if you update via OTA. The reason for this is if you force the device to boot from the "old" slot, Anti-Rollback Protection will kick in and cause a boot loop.
Since you're able to boot with the unpatched image, just flash that for the time being. Your device has to finish up the update after booting, and the rooted image can sometimes cause a problem with this. Once the device has been running for a bit, say 10 minutes or so, you should be able to safety flash the patched image.
Were you rooted before?
Click to expand...
Click to collapse
The last update was done in May, so I think I waited way more than 10minutes
I really can't remember if I rooted when I bought it, with android 10, but if so (with magisk anyway), after the upgrade to 11 I didn't root again for sure.
4L3xN3t said:
The last update was done in May, so I think I waited way more than 10minutes
I really can't remember if I rooted when I bought it, with android 10, but if so (with magisk anyway), after the upgrade to 11 I didn't root again for sure.
Click to expand...
Click to collapse
Hmm. I am not sure why you are having problems now. The only thing I can suggest is flash the factory image using the instructions in the OP; you can also use the Android Flash Tool. You shouldn't need to wipe your device. Double and triple check to make sure you're patching the correct boot image, maybe post some screenshots or something (use spoilers) to show what you're doing. 99% of the time, if you are using the correct software, the problem is likely Magisk modules or incorrect patching.
V0latyle said:
Hmm. I am not sure why you are having problems now. The only thing I can suggest is flash the factory image using the instructions in the OP; you can also use the Android Flash Tool. You shouldn't need to wipe your device. Double and triple check to make sure you're patching the correct boot image, maybe post some screenshots or something (use spoilers) to show what you're doing. 99% of the time, if you are using the correct software, the problem is likely Magisk modules or incorrect patching.
Click to expand...
Click to collapse
when I flash the factory image (as I did l 2days ago), I use the "flash-all.bat" included in the original zip after I delete the "-w" from "fastboot -w update imagexyz.zip" and this way it doesn't wipe the phone.
I'll try again in the nex days (hope to have time in the weekend) doing some screenshot
stay tuned.
thank you
Related
I've been using an E6653 for the last few months with the Customized UK firmware (32.2.A.0.253). I was initially using it unmodified with Android Pay, then about a month ago Magisk was developed that allowed you to use root and Xposed and still pass SafetyNet checks so I could still use Android Pay. Due to the cat and mouse game with Google, I didn't think having root/Xposed was worth it any more so I decided to flash the stock ROM again which should have wiped everything. I've reflashed the firmware 3 times, but I can't seem to pass SafetyNet checks anymore.
In addition to flashing the stock firmware with Flashtool, is there something else I should be doing? Any help would be appreciated.
Devo7v said:
I've been using an E6653 for the last few months with the Customized UK firmware (32.2.A.0.253). I was initially using it unmodified with Android Pay, then about a month ago Magisk was developed that allowed you to use root and Xposed and still pass SafetyNet checks so I could still use Android Pay. Due to the cat and mouse game with Google, I didn't think having root/Xposed was worth it any more so I decided to flash the stock ROM again which should have wiped everything. I've reflashed the firmware 3 times, but I can't seem to pass SafetyNet checks anymore.
In addition to flashing the stock firmware with Flashtool, is there something else I should be doing? Any help would be appreciated.
Click to expand...
Click to collapse
I found the answer to my own question. Apparently Google updated SafetyNet yesterday to detect an unlocked bootloader. If you have an unlocked bootloader then your device fails SafetyNet checks. I guess I'm never going to be able to use AndroidPay.
https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/
Hi,
Noobish question but do you mind telling me how you got magisk installed?
I'm rooted, unlocked bootloader and restored DRM keys bu honestly, that was hectic.
Should I simply flash the lastest FTF from flash tools and then install TWRP then flash Magisk, OR do I have to go into much more steps such as create boot img etc. Also, will I lose my DRM keys? how would I replace them? If u don't mind, just give me bullets of the step, I think i can manage to find the files.
I'm really looking for clarity and assurance. As clear as the forums are, or supposed to be, I find it noisy and sometimes it's hard to filter through all the dialogues.
Devo7v said:
I found the answer to my own question. Apparently Google updated SafetyNet yesterday to detect an unlocked bootloader. If you have an unlocked bootloader then your device fails SafetyNet checks. I guess I'm never going to be able to use AndroidPay.
https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/
Click to expand...
Click to collapse
inteltecra1700 said:
Hi,
Noobish question but do you mind telling me how you got magisk installed?
I'm rooted, unlocked bootloader and restored DRM keys bu honestly, that was hectic.
Should I simply flash the lastest FTF from flash tools and then install TWRP then flash Magisk, OR do I have to go into much more steps such as create boot img etc. Also, will I lose my DRM keys? how would I replace them? If u don't mind, just give me bullets of the step, I think i can manage to find the files.
I'm really looking for clarity and assurance. As clear as the forums are, or supposed to be, I find it noisy and sometimes it's hard to filter through all the dialogues.
Click to expand...
Click to collapse
It sounds like you're on a fully functioning stock ROM with an unlocked bootloader. If that is the case, then it's pretty easy to get Magisk up and running. The first thing you need to do is get TWRP on your phone, to do that you need to flash a kernel that supports entering TWRP recovery from boot. There are a few kernels that allow you to do that, I am using AndroPlus v38. There is a newer version of AndroPlus, but there have been mixed reports of being able to enter TWRP.
To Flash a new Kernel and TWRP:
Download the latest kernel from https://kernel.andro.plus/ and place the <boot.img> within the zip file in the same folder with the fastboot.exe
Download the version of TWRP from https://dl.myself5.de/ and place the <recovery.img> in the same folder with the fastboot.exe
In the the folder with fastboot.exe, shift+right click and run cmd as admin
Reboot phone in to fastboot mode (hold down the volume up while plugging in usb)
Once the phone is detected type 'Fastboot devices' to make sure you device is detected.
If it's detected flash the kernel by typing the following command 'Fastboot flash boot <boot.img>' (without <>)
Then type 'Fastboot flash recovery <recovery.img>' (without <>)
Once done flashing type 'Fastboot reboot', and make sure you press volume up when the yellow led is showing
Once you've made sure that you can enter TWRP, things will be much easier from here on out. To get Magisk up and running:
Head over to the official Magisk thread and download both the Magisk Manager v2.1 apk and the Magisk v8 zip file to your phone (http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Reboot your phone and enter TWRP by pressing the volume up key when the yellow led is showing
Flash the Magisk v8 zip file. This will patch Magisk into your kernel (boot.img), so if you ever want to get rid of Magisk and it's mods, just reflash your kernel either by using Fastboot or by flashing the kernel zip file through TWRP.
Once Magisk has been successfully flashed, reboot your phone
When you phone has booted up install the Magisk Manager v2.1 apk that you downloaded earlier. If everything went right, the Magisk Manager should show that everything is installed and up to date.
I hope that helps, let me know if you have any other questions.
When I used to above procedure I get an error 'Response payload validation failed'. I have searched a lot in the internet and have seen a lot of people with the same bug. But I couldn't find a solution to this problem. Any ideas?
piet3r said:
When I used to above procedure I get an error 'Response payload validation failed'. I have searched a lot in the internet and have seen a lot of people with the same bug. But I couldn't find a solution to this problem. Any ideas?
Click to expand...
Click to collapse
Google has added more checks to SafetyNet and the procedure above no longer works. The issue is the AndroPlus kernel does not pass SafetyNet so anything you do after that will pass either. Maybe @AndroPlus will get some time to look into it and add some fixes. In the meantime I need to find another kernel that will pass SafetyNet, but I haven't had time to try.
Maybe you could try some other kernels and let us know if you find anything that works.
[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8
Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!
Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:
Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol
Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse
I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing
Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?
Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot
itenos said:
Hi Guys, I've been an active user of XDA in the past but didn't have time to follow in the last couple of years so my memory about flashing and tinkering is quite blank.
Here is my situation:
Mate 9 MHA-L29C636B158 (very old ROM)
Bootloader unlocked with paid code from dc-unlocker
Rooted with PHH's Superuser (the only root that was available for our device back in March 2017)
EMUI 5.0 and Android 7.0 (that was obvious from my Build number but I just wanted to state it again)
TWRP 3.0.2-2 is installed with system kept read-only. Internal SD seems to be encrypted
I never took any OTAs as I was afraid that they would break something
In the last month's many of my banking or financial apps have stopped working because I'm rooted so I read that Magisk would be able to circumvent this safetynet thing and would allow me to continue using these apps. Google Pay would be a nice addition also.
At this point I would like to upgrade my firmware and get rid of PHH's Superuser switching to Magisk instead
Could someone please write a detailed guide how to do that? It might be interesting for other users also that are in my same situation. I'm willing to donate a few bucks for a complete and foolproof guide.
Thanks a lot
Click to expand...
Click to collapse
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
With that said:
If you want to keep your data, make a backup using Hisuite.
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.
Just stumbled over your reply, didn't get an email notification from XDA. Thank you so much. Let's see if I can follow your instructions.
irony_delerium said:
Do you still have the unlock code? You'll want it, as the update from EMUI 5 to EMUI 8, on every device I've got, has relocked the bootloader.
Click to expand...
Click to collapse
Yes, I still have the code
irony_delerium said:
With that said:
If you want to keep your data, make a backup using Hisuite.
Click to expand...
Click to collapse
Done
irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Click to expand...
Click to collapse
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
irony_delerium said:
If you modified other partitions on the device using TWRP or su in general, it wouldn't be a bad idea to use a nocheck recovery or HuRupdater to flash the entire system, to leave everything in a pristine state, since there are partitions you can't flash with fastboot, even with an unlocked bootloader. The instructions for HuR can be found elsewhere on XDA, as can details about nocheck recoveries, though the latter I'd be careful with - using HWOTA7 on Oreo, for example, WILL cause a brick. You've been warned.
Click to expand...
Click to collapse
I don't think that I modified any other partitions, at least not willingly. I even left the system in read-only state. Don't know if phh.su did something by itself?
irony_delerium said:
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically. When Oreo is installed, it'll automatically relock your bootloader; you can continue updating here, though if you've got a particular target you want to go to, you might want to unlock and use HuR again to flash that specific one now that you're on Oreo. (The latest firmwares can't be rolled back to Nougat.) If you have no intention of going back to Nougat, you have your unlock code, and you aren't planning to do any other modifications like rebranding, then update away, though you may want to hold off of the Pie update if offered. (Shouldn't be, yet, but it could have been approved for your device already; it changes the boot partitions yet again.)
Now that you're on Oreo and presumably unlocked again, make sure you've got the FullOTA image downloaded for that firmware to your PC. (Always a good idea, anyway.)
Magisk can be installed by:
1) Flashing TWRP with fastboot, then flashing a suitable Magisk zip
2) Using Magisk Manager to patch a boot image and flashing that.
For TWRP:
Get a copy of TWRP from the forum here. When I use one, it's the 3.2.1-0 from @Pretoriano80, you'll find it in the development section. Any 3.2.x for Oreo should work though - a Nougat TWRP will not work.
Flash TWRP to recovery_ramdisk in fastboot. Boot to TWRP, flash Magisk.
For Magisk Manager:
Extract "ramdisk" from your FullOTA firmware. Place it in internal storage on your device. Use Magisk Manager to patch the image (install / patch boot image). Transfer the patched_boot.img created by Magisk back to your PC and flash that to the "ramdisk" partition in fastboot.
Click to expand...
Click to collapse
Will continue to do the above after your kind confirmation of my last questions. Thanks again
itenos said:
I downloaded the FullOTA with the FirmwareFinder app on my phone and transferred it to my laptop. Extracted the update.app with WinRAR and extracted system, boot, recovery and recovery2 using the Huawei Update Extractor 0.9.9.3.
Just to make no mistake, could you please confirm the order of flashing these 4 files? And maybe the correct command to use in fastboot?
Click to expand...
Click to collapse
The order shouldn't be particularly relevant, just that it's safest to reflash all of them:
- boot because phhsu may have modified the boot image to add su to it
- recovery and recovery2 because you loaded TWRP. recovery2 is specified because it's used to be recommended to flash to erecovery as well as normal recovery.
- system because I'm pretty sure that's the biggest thing modified Hy phhsu, and any other system changes you may have made.
Theoretically, other modified partitions won't matter since the upgrade to 8.0 replaces most (all, I think) of them anyway, but if you have to go through update steps through EMUI 5 first before it'll give you 8, then it's safest that they aren't modified. I mentioned other partitions because, with root & TWRP, you technically could have modified any and all of them.
irony_delerium said:
Download the FullOTA firmware for your current version. Extract system, boot, recovery, recovery2 (as you're on EMUI 5) and flash them either in TWRP or fastboot; that should eliminate PHH SU and TWRP, and ultimately leave the system in a clean state.
Start the update process - you've already been approved for OTAs and they've been offered, so they should happen automatically.
Click to expand...
Click to collapse
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip
itenos said:
Flashing of 158 (original ROM version) went fine. Phone rebooted and titanium reported no root access, so it looks good.
After that I started the OTA update to 172 that waited already long time in my settings and it downloaded it. After downloading it gave me an error during the validation process of the file and asked to download it again.
Unfortunately now both the phone updater and the HiSuite app on my laptop say that 158 is the latest available firmware and no update is available.
I guess that I can download directly the newer firmware but I'm not exactly sure how to flash the whole package and what I should do with the other 2 files that come with it besides the update.zip
Click to expand...
Click to collapse
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.
irony_delerium said:
It might be tweaking out about the fact that you'd previously modified system.
I'd grab the last Nougat release (looks like 191; there are 2 of them, be sure it's not the rollback one you grab) and use hurupdater in TWRP to install it, then let the system try running OTA again.
Click to expand...
Click to collapse
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.
itenos said:
I had to insert the SIM card of the country I bought my phone in to get the OTAs coming. Luckily I still had it with a few $ credit on it. It used just a few cents in data roaming for finding the new firmware, then I downloaded through wifi.
After 4 updates now I'm on 378 and no sign of Pie yet so this afternoon if I find some time I'll continue with rooting.
Click to expand...
Click to collapse
Easy way:
Unlock phone, if you haven't yet again.
Download and flash TWRP from here: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353 (has decryption support) (flash to recovery_ramdisk as Huawei decided to split recovery partition into different parts)
Boot to TWRP, input pin (if you set a pin, else it will decrypt automatically)
Download Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Transfer Magisk to phone.
Flash Magisk zip in TWRP.
Reboot and you're done.
You might have to tinker around with Magisk Hide and hide apps if your banking apps still detect root.
As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all
itenos said:
As the Huawei Backup took over 4 hours to finish and i can't use Titanium, which is much faster, because I'm not rooted at the moment, I thought it's a good idea to first upgrade to Pie before unlocking my bootloader and losing all data. If I need to stay a few days without root it's ok.
Is there any way to get to Pie without being rooted? I tried the erecovery method on firmware finder. It says that my IMEI is now registered to download the update but when I enter erecovery it starts downloading the 378 oreo package.
I would like to avoid backing up and restoring twice this lengthy process, probably 16 hours all in all
Click to expand...
Click to collapse
The erecovery method won't work unless you can change the DNS settings on the network being used - it hijacks some of the requests to Huawei's servers to force the update. (And even then it's a bit finicky; I have yet to successfully use it, all things considered.)
Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.
itenos said:
Yesterday I finally received 9.0.1.159 with EMUI 9.0.1 by OTA. It installed fine and it's amazing how fast my phone became and how much screen on time I have now with my 2 year old device (8 full hours!). Good job Google and Huawei.
Being on Pie now I suppose that the instructions to root from you and ante0 are not valid anymore as they were meant for Oreo.
Could you please modify the instructions for Pie? And further, as I see that since yesterday in FirmwareFinder a new Pie update 9.0.1.178 popped up, could you please also add instructions how to take this OTA being rooted with Magisk once it arrives?
I've read a bit in the Magisk thread but I did not really understand the part of having to boot to recovery everytime I switch on the phone. Further they are talking there about EMUI 9 but I have already 9.0.1, is there maybe a difference I have to take care about?
Last but not least, I didn't forget my initial promise to donate a few bucks for the detailed instructions so please drop me your email in PM and I'll sent you a few through PayPal or in alternative, if you have some paid apps on the Playstore I could buy them so they might get more visibility.
Click to expand...
Click to collapse
The reason recovery boot is needed for Pie is because Huawei removed the ramdisk - in Pie, it's system as root with no way of forcing a ramdisk except by a recovery boot. So as a workaround, Magisk takes over recovery.
The installation instructions for it on Pie are pretty much the same as Oreo, except:
* Patch recovery_ramdisk, not ramdisk. Latest stable Magisk should work (18.1, iirc, has the patches to support recovery boot.)
* When booting, go to recovery. Magisk will start from there and take over the startup process.
irony_delerium said:
The installation instructions for it on Pie are pretty much the same as Oreo, except:
Click to expand...
Click to collapse
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?
itenos said:
Hmm, where do I find the TWRP for Pie in order to flash?
And most importantly how do I have to behave in case of new OTAs coming?
Click to expand...
Click to collapse
TWRP on this case, don't bother.
Extract your stock recovery from your firmware's update.app file, patch with Magisk Manager, and flash the patched image. When you want to flash an ota, put the stock recovery back.
[UPDATE/KEEP ROOT GUIDE] OCT 2020 (RP1A.201005.004) "CORAL" Magisk/Stock Boot Images
PLEASE NOTE: I STILL HAVE NOT UPDATED TO ANDROID 11 YET, SO PLEASE FLASH AT YOUR OWN RISK AS ASSISTANCE FROM ME WILL BE VERY LIMITED. PLEASE BE KIND TO ONE ANOTHER AND HELP EACH OTHER OUT! AND SORRY FOR THE LATE POST. JUST GOT BACK FROM A LONG WEDDING WEEKEND, AND THE 8-HOUR DRIVE (EACH WAY) WITH A 9 MONTH OLD BABY WAS... QUITE AN ADVENTURE.
PLEASE DROP A THANKS IF YOU STILL FIND THESE GUIDES HELPFUL! :good:
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR "RP1A.201005.004, Oct 2020"!
Magisk Canary v21.0 Patched Boot Image: https://www.androidfilehost.com/?fid=10763459528675557936
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=10763459528675557937
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=10763459528675557938
[SAFETYNET INFO]: Again, I'm not updating myself yet, so I'm not sure about this. I will update this info as others report back. On Android 10, using the MagiskHide Props Config module (or an alternate module created by Displax, though I prefer Didgeridoohan's module) and choosing option 2 - Force BASIC key attestation would force BASIC HW attestation and allow SafetyNet to pass again. This works perfectly for me, and I even run additional mods including EdXposed. I'm not sure if this works on Android 11, and I won't be able to confirm myself for a while. If anybody tries it, please let me know and I'll update this section. The module and info on using it can be found here: https://forum.xda-developers.com/ap...just search for it in the Magisk Manager app.
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RP1A.200720.009, Sep 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rp1a.200720.009-factory-dtbo.img: https://www.androidfilehost.com/?fid=8889791610682933260
coral-rp1a.200720.009-factory-boot.img: https://www.androidfilehost.com/?fid=8889791610682933258
October 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rp1a.201005.004-5e85d0f7.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rp1a.200720.009-factory-boot.img
3. fastboot flash dtbo coral-rp1a.200720.009-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rp1a.201005.004-5e85d0f7.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rp1a.201005.004-magisk_patched-21.0.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
I just want to reemphasize once again - I have not yet updated to Android 11, so I haven't been able to personally test any of these newer builds. Any feedback would be appreciated. And of course, be kind to one another and help each other out if you have any issues!
Finally, I need to mention again that the Magisk v21.0 boot image I created for the Oct. 2020 build came out to 64mb (and not the usual 30~something mb), which makes me feel a little wary. I would really appreciate feedback if my pre-patched boot image works. (edit: I just tested with patching my current Aug. 2020 boot image with Magisk v21.0 and it also came out to 64mb and successfully flashed perfectly fine, so hopefully my pre-patched Oct. 2020 image should also be fine.)
Thanks!
i5lee8bit said:
I just want to reemphasize once again - I have not yet updated to Android 11, so I haven't been able to personally test any of these newer builds. Any feedback would be appreciated. And of course, be kind to one another and help each other out if you have any issues!
Finally, I need to mention again that the Magisk v21.0 boot image I created for the Oct. 2020 build came out to 64mb (and not the usual 30~something mb), which makes me feel a little wary. I would really appreciate feedback if my pre-patched boot image works. (edit: I just tested with patching my current Aug. 2020 boot image with Magisk v21.0 and it also came out to 64mb and successfully flashed perfectly fine, so hopefully my pre-patched Oct. 2020 image should also be fine.)
Thanks!
Click to expand...
Click to collapse
It is safe to update to Android 11 and do a clean install by wiping data (so keep the "-w" in the flash-all.bat file), let the phone reboot into Android 11, setup phone and let it install your previous apps, etc.
Afterwards, install MM 8.01, change settings to beta build, patch boot image AND REBOOT THE PHONE. After rebooting, copy the magisk_patched image file to your adb (it should be 64 MB in size) folder. Proceed with using flashing the patched boot image.
I just updated to October's factory image a few minutes ago and success.
bb709394 said:
It is safe to update to Android 11 and do a clean install by wiping data (so keep the "-w" in the flash-all.bat file), let the phone reboot into Android 11, setup phone and let it install your previous apps, etc.
Afterwards, install MM 8.01, change settings to beta build, patch boot image AND REBOOT THE PHONE. After rebooting, copy the magisk_patched image file to your adb (it should be 64 MB in size) folder. Proceed with using flashing the patched boot image.
I just updated to October's factory image a few minutes ago and success.
Click to expand...
Click to collapse
I'm actually holding off because I'm waiting for a few mods to be compatible with 11, particularly GravityBox. Also, the purpose of my guides are to update without the need to wipe data / flash full clean factory image / seamlessly update with absolutely no additional setup. I know people say it's not so bad these days to set up from scratch, but for me it's still definitely a "ain't nobody got time fo dat" situation. =)
Thanks anyway though.
i5lee8bit said:
I just want to reemphasize once again - I have not yet updated to Android 11, so I haven't been able to personally test any of these newer builds. Any feedback would be appreciated. And of course, be kind to one another and help each other out if you have any issues!
Finally, I need to mention again that the Magisk v21.0 boot image I created for the Oct. 2020 build came out to 64mb (and not the usual 30~something mb), which makes me feel a little wary. I would really appreciate feedback if my pre-patched boot image works. (edit: I just tested with patching my current Aug. 2020 boot image with Magisk v21.0 and it also came out to 64mb and successfully flashed perfectly fine, so hopefully my pre-patched Oct. 2020 image should also be fine.)
Thanks!
Click to expand...
Click to collapse
I didn't use your file. What I do is download the full firmware, remove -w and flash, then boot into TWRP and flash the Magisk zip. For some reason this October Update, it wouldn't decrypt my data when booting into TWRP so I patched the boot.img myself. I wanted to let you know that mine also came out to 64mb and after I flashed it to the boot partition, it worked perfectly. So I can "sorta" confirm that it should work.
i5lee8bit said:
I'm actually holding off because I'm waiting for a few mods to be compatible with 11, particularly GravityBox. Also, the purpose of my guides are to update without the need to wipe data / flash full clean factory image / seamlessly update with absolutely no additional setup. I know people say it's not so bad these days to set up from scratch, but for me it's still definitely a "ain't nobody got time fo dat" situation. =)
Thanks anyway though.
Click to expand...
Click to collapse
Seamless update is worth so much. Setting up a phone when its your daily driver is just so much work. No banking pin app will work, you have to set up messangers again, alot of apps will barely work (even with backup services like swift backup or titan) and some apps can't even be backuped at all and will create errors when loading backups.
@i5lee8bit, I just followed your tutorial to successfully upgrade the October patch with the files you provided. Everything is okay. Thanks a lot for your enthusiastic sharing.
WorldOfJohnboy said:
I didn't use your file. What I do is download the full firmware, remove -w and flash, then boot into TWRP and flash the Magisk zip. For some reason this October Update, it wouldn't decrypt my data when booting into TWRP so I patched the boot.img myself. I wanted to let you know that mine also came out to 64mb and after I flashed it to the boot partition, it worked perfectly. So I can "sorta" confirm that it should work.
Click to expand...
Click to collapse
I still haven't bothered with TWRP since the HTC U12+ days, and I actually found that I prefer it that way. Pretty sure TWRP needs to be updated for each (or at least most) monthly update btw. But thanks for the info, looks like 64mb is now the normal way Magisk outputs the patched boot image.
Morgrain said:
Seamless update is worth so much. Setting up a phone when its your daily driver is just so much work. No banking pin app will work, you have to set up messangers again, alot of apps will barely work (even with backup services like swift backup or titan) and some apps can't even be backuped at all and will create errors when loading backups.
Click to expand...
Click to collapse
Yeah, I only backup/restore certain apps (data or apps not on app store) when switching phones because there are always those little glitchy problems and what not if relying on TiBu / Swift too much. I'll use the built in backup/restore for certain apps (like Nova), but other than that when doing a clean install, while Android has better built in features to make it easier to migrate compared to a few years ago, it is still a major PITA.
blue2018 said:
@i5lee8bit, I just followed your tutorial to successfully upgrade the October patch with the files you provided. Everything is okay. Thanks a lot for your enthusiastic sharing.
Click to expand...
Click to collapse
Thanks for the info! Just updated the OP so there isn't a huge scary caution, lol. I figured it would be fine when I tested with August patched with v21.0 and still came out to 64mb, but thanks for the confirmation.
Silly Question Maybe
guys its been a while so pls have patience with my ignorance. I have Xfinity Pixel 4xl and need to use it on T-mobile. Under Developer options,. OEM Unlocking is greyed out and it does not allow me to modify. Am i screwed ?
I tried updating and I can't figure out why it is not working...
Upon boot, I am still on Sept patch with root.
Then eventually it tells me that an update is available to be installed and to reboot to finish.
When I reboot, it says that there was an error.
Magisk no longer has "install after OTA" option. Anyone have any ideas?
xclaim494 said:
guys its been a while so pls have patience with my ignorance. I have Xfinity Pixel 4xl and need to use it on T-mobile. Under Developer options,. OEM Unlocking is greyed out and it does not allow me to modify. Am i screwed ?
Click to expand...
Click to collapse
Sorry about the late response, but maybe this info might help (it's a post I made on slickdeals.net regarding b/l unlocking the P4 series): https://slickdeals.net/f/14385296-x...e-399-free-shipping?p=140865899#post140865899
Also important to note, there is a difference between SIM unlocking (so you can use with T-Mobile) and oem/BL unlocking (so you can modify / root the phone).
tl;dr on my slickdeals post: SIM unlock status controls the oem (bootloader) unlock toggle status. Verizon is known to be the only variant where they fully prevent BL unlocking. XMo is an MVNO off of Verizon. Nobody has reported yet whether it can be done on XMo variants even after SIM unlocking. So you might be screwed.
smithilberry said:
I tried updating and I can't figure out why it is not working...
Upon boot, I am still on Sept patch with root.
Then eventually it tells me that an update is available to be installed and to reboot to finish.
When I reboot, it says that there was an error.
Magisk no longer has "install after OTA" option. Anyone have any ideas?
Click to expand...
Click to collapse
Did you follow the OP / 2nd post exactly? And made sure you're sideloading the correct, Oct 2020 ota zip? Should work fine with the given instructions and links. Make sure you downloaded (or just redownload) all the correct files.
Tbh it sounds like you're just reinstalling the Sept update and boot files.
The November update is out. Anyone here already got the new files?
Morgrain said:
The November update is out. Anyone here already got the new files?
Click to expand...
Click to collapse
I do... not sure if there's a separate thread as this is for the October update.
Side note, I apparently can no longer BOOT to TWRP to flash the Magisk Zip as even the TWRP Coral Beta doesn't decrypt Android 11. So, looks like I'm stuck manually patching the Boot and flashing via bootloader.
Hello All. I'm really struggling with this phone. Note: I don't have a PC so I had to use my roommates computer to unlock this and get it to the point it is now. It took me DAYS to do so.
I've been rooting androids since the G1, so I'm not a novice at this. This process has so far been the most complicated I've encountered and the most risky since I ended up bricking an LG V20.
This is an excellent value phone, but dagnabbit if it isn't a clufusterfoozle to get rooted and modded.
Anyway here is where I'm at:
1. Phone is unlocked via MIUI Unlock.
2. Phone has custom MIUI EU mod. Don't know the exact name of it.
Those are what I believe has been taken care of for sure.
Here are my issues:
1. Phone is unrooted: I've tried to root with magisk countless times. The Magisk Manager gives me a weird screen that it doesn't show on other phones. My magisk manager always shows me this:
New item by Troy Fergus
photos.app.goo.gl
2. Root checks fail every time. To add insult to injury safety check consistently fails as well: https://photos.app.goo.gl/6k5mMBysYB2LECoq9
Because of the above issues, I can't install Root necessary apps such as TItanium backup. This dramatically lessens the value of the phone to me.
4. Decryption fails as well. THis
SELECT THE boot.img from zip file of the rom and patch it using magisk application then flash boot.img patched one into the rom using fastboot by this command
fastboot flash boot boot.img( or whatever the name of boot.img is)
bilalrajput said:
SELECT THE boot.img from zip file of the rom and patch it using magisk application then flash boot.img patched one into the rom using fastboot by this command
fastboot flash boot boot.img( or whatever the name of boot.img is)
Click to expand...
Click to collapse
I'm not sure what that means exactly, but I will try out the advice, thank you!!