Related
[UPDATE/KEEP ROOT GUIDE] AUG 2020 (QQ3A.200805.001) "FLAME" Magisk/Stock Boot Images
Sorry I'm a little late this month. Didn't have time to update my wife's phone for a few days. I know the P4 forums aren't as "alive" as the P4XL forums, but I still wanted to continue sharing since I'm doing the work anyway. Hope you guys are still finding these guides and files useful.
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 "FLAME" ONLY, NOT PIXEL 4-XL "CORAL"!!
Here are the factory and Magisk Patched (v.24 is still the latest as of typing this) boot images for the August 2020 (QQ3A.200805.001) update.
**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 AUGUST 2020 QQ3A.200805.001!
Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=8889791610682911607
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=8889791610682911606
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=8889791610682911608
THESE FILES ARE FOR "10.0.0 (QQ3A.200805.001, Aug 2020)" ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!
Also, as most of us know by now, it looks like Google flipped HW attestation back on, and so SafetyNet will now fail (not just on August, but even previous builds). basicIntegrity test passes, but ctsProfile fails (due to hardware attestation method Google flipped back on), regardless of EdXposed / Magisk Hide status. Until people way smarter than us figure it out, if ever, I can't tell you how to fix it other than reverting back to full stock and locked bootloader. Oh well, carry on. Root is still more important to me anyway - for me the pros still far outweigh the cons.
[SAFETYNET UPDATE!!]: Another temporary SafetyNet fix available, thanks to @Displax. Just note some users have mentioned it could have some unforeseen side effects, as it changes your build prop's entry for your device model name to an unknown in order to force BASIC hardware attestation. Use at your own risk. Big thanks to Displax! Face unlock now working again on my TD Bank and Citi mobile apps. Also worked on my wife's P4 "flame". =)
Just flash Displax's zip file in Magisk Manager: https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40656
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 "10.0.0 (QQ3A.200705.002, Jul 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
flame-qq3a.200705.002-factory-dtbo.img: https://www.androidfilehost.com/?fid=8889791610682886735
flame-qq3a.200705.002-factory-boot.img: https://www.androidfilehost.com/?fid=8889791610682886734
August 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-qq3a.200805.001-dc4e0a1b.zip
I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT 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 flame-qq3a.200705.002-factory-boot.img
3. fastboot flash dtbo flame-qq3a.200705.002-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 flame-ota-qq3a.200805.001-dc4e0a1b.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 flame-qq3a.200805.001-magisk_patched-20.4.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it. I've only personally tested with Kirisakura though.)
*Kirisakura 5.2.2 works beautifully.
This was a 100% seamless update that required 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.
SafetyNet not passing? READ OP AGAIN.
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/how-to/magisk-modules-disabler-booting-magisk-t3991739
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
Coming from an earlier build than July 2020?
Download the July 2020 Full Factory Image .zip file and extract it. BEFORE RUNNING THE FLASH-ALL BATCH / SHELL FILE, EDIT THE FILE AND REMOVE THE "-w" FLAG FROM THE LAST FASTBOOT LINE. If you fail to remove -w, your phone will be wiped when it reaches this step. After flashing the full factory image, your phone will automatically reboot into O/S. From here, reboot back into bootloader, and flash the new Magisk patched boot image.
SafetyNet not passing? READ OP AGAIN.
thank you for the thread!
OP has been updated with yet another SafetyNet workaround fix. I'm about 1.5 months late, so my bad!
Boss, are you doing one thread for Pixel 4 September too?
ahalol said:
Boss, are you doing one thread for Pixel 4 September too?
Click to expand...
Click to collapse
I did it the same way.
The only difference is that you have to patch your boot.img with Magisk Canary Build.
Is it possible to get canary the build with the custom URL option? I remember at some point was possible, however all my searches have come up empty. Or is it best to install the canary apk? Thanks in advance.
gmmurphy said:
Is it possible to get canary the build with the custom URL option? I remember at some point was possible, however all my searches have come up empty. Or is it best to install the canary apk? Thanks in advance.
Click to expand...
Click to collapse
I uninstalled the stable build and installed the Canary apk.
I rebooted my phone due to 0 signal and now it's just stuck on 'phone is starting' for hours. QQ. I think it was due to Magisk.
I dirty flashed September Unicorn ROM but still no luck. Ahh don't know what to do.
Sorry for going off the grid for a while everyone. I've been busy with life stuff, baby stuff, family travels, etc.
Also want to note that I don't actually officially own a Pixel 4, but rather is my wife's phone. And I've held off on updating our phones to Android 11 until GravityBox is updated for Android 11. But I did create a guide for my phone (Pixel 4 XL) for September, and now October. I still plan on continuing to make these guides for the P4, but even for the P4XL I had to be careful and have someone test last month since I wasn't updating myself. There are a few additional warnings in terms of making sure any modules are updated before upgrading or much higher risk of bootloop than previous updates.
When I get some time, hopefully sometime this weekend, I'll publish the guides for both months with the proper files for Pixel 4 (flame). Sorry for the wait, stay tuned...
I hope this is the right place to ask, pardon me if not:
Issue: After upgrading to Android 11, the patched boot image causes bootloop, when patched using Magisk Canary
Phone/setup: Pixel 4 XL, updated today to Android 11 using OTA, which strangely enough worked just fine. Previously used the usual Magisk build, but grabbed Canary for this stuff. I'm flashing using latest ADB tools via download straight from Google + using original Pixel cable which so far has worked great with fastboot. Fastboot devices -l reports the phone.
Approach:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Download latest Canary build straight from github front page, moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.
Approach two:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot_a modified-image, fastboot flash boot_b modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.
Any idea what I'm doing wrong?
EDIT: Solution here! https://forum.xda-developers.com/showpost.php?p=83499831&postcount=23
delanvital said:
I hope this is the right place to ask, pardon me if not:
Issue: After upgrading to Android 11, the patched boot image causes bootloop, when patched using Magisk Canary
Phone/setup: Pixel 4 XL, updated today to Android 11 using OTA, which strangely enough worked just fine. Previously used the usual Magisk build, but grabbed Canary for this stuff. I'm flashing using latest ADB tools via download straight from Google + using original Pixel cable which so far has worked great with fastboot. Fastboot devices -l reports the phone.
Approach:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Download latest Canary build straight from github front page, moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.
Approach two:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot_a modified-image, fastboot flash boot_b modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.
Any idea what I'm doing wrong?
Click to expand...
Click to collapse
Pixel 4a here, just tried to follow OTA instructions and ended up bootlooped until I paused it. After resuming it rebooted but the update didn't take and magisk was uninstalled. I did have the safetynet fingerprint module installed so probably this caused an issue? Not sure it relates exactly to your problem but thought I'd chime in with a similar problem and model.
EDIT:
After this reboot where I lost magisk I retried the OTA and it succeeded. I then tried to flash the patched boot.img in fastboot but it failed now I'm endlessly bootlooping.
EDIT 2:
tried a couple things but couldn't get 11 to boot so I flashed back to 10 but wiped my userdata so I'm done messing around for awhile I think 11 just is a no go for now.
ReservedName said:
Pixel 4a here, just tried to follow OTA instructions and ended up bootlooped until I paused it. After resuming it rebooted but the update didn't take and magisk was uninstalled. I did have the safetynet fingerprint module installed so probably this caused an issue? Not sure it relates exactly to your problem but thought I'd chime in with a similar problem and model.
Click to expand...
Click to collapse
On Android 10, when booting Magisk in the core only mode, I would still fail the ctsProfile. I would never complete safetynet 100%. I am not sure what should be possible, but it seems some ppl can make it pass safetynet on Android 10 by running Magisk in core only mode. When upgrading to Android 11, and before flashing any boot.img, but after installing Canary build, I would still fail the ctsProfile part of the satefy net. I wonder if that somehow impacts.
If wonder if the issue is linked to the fingerprint. I also have the fingerprint module (where it allows apps to believe it's using a fingerprint, but in fact it's my face). I will try and remove all the modules, then uninstall Magisk, then reinstall Canary build. Cheers mate.
delanvital said:
I hope this is the right place to ask, pardon me if not:
Issue: After upgrading to Android 11, the patched boot image causes bootloop, when patched using Magisk Canary
Phone/setup: Pixel 4 XL, updated today to Android 11 using OTA, which strangely enough worked just fine. Previously used the usual Magisk build, but grabbed Canary for this stuff. I'm flashing using latest ADB tools via download straight from Google + using original Pixel cable which so far has worked great with fastboot. Fastboot devices -l reports the phone.
Approach:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Download latest Canary build straight from github front page, moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.
Approach two:
Flash-all.bat without -w, boots fine, all in order = boots fine, all in order
Extract boot.img, move to phone
Moditfy boot.img, transfer image to pc
ADB reboot bootloader, fastboot flash boot_a modified-image, fastboot flash boot_b modified-image
Outcome: Stuck in boot - makes it to the "G" logo with the spinning line below. Left like that for 20 minutes, no change.
Any idea what I'm doing wrong?
Click to expand...
Click to collapse
Same here, and after the Glogo, if I restart I get ""no valid slot to boot". Flashing unpatched boot.img gets me back in, but there doesn't seem to be a way to root 11 release build?
Works fine on my Pixel 4 xl. I'm using a patched boot img. Make sure you use the correct boot img
cgo72123 said:
...if I restart I get ""no valid slot to boot". Flashing unpatched boot.img gets me back in...
Click to expand...
Click to collapse
Google Store Pixel 4a here. I have the exact same experience. Tried:
2. Uninstall Magisk -> Install OTA -> Install Inactive Slot -> bootloops 3 times and settles on previous boot slot, Android 10, no Magisk
3. Patch Boot.img -> flash-all.bat -> fastboot flash boot magisk_patched.img -> fastboot bootloop with the message "no valid slot to boot"
Can confirm re-flashing stock boot.img or running the full update script successfully boots Android 11, no root of course
Pixel 4 XL user here. I updated to Android 11 last night. Same thing happened to me. Waiting for an update to Magisk for Android 11
ChocoboX said:
Pixel 4 XL user here. I updated to Android 11 last night. Same thing happened to me. Waiting for an update to Magisk for Android 11
Click to expand...
Click to collapse
I noticed a new buildof Magisk available in the manager. New modified boot image has a slightly different filesize. Tried fastboot boot magisk_patched.img but still stuck on G and the moving line below. I wonder what is different compared to the 4xl users who has no problems...
Just want to point out that a common cause for issues when updating from one Android version to another is incompatible mods.
Make sure that no Magisk modules are installed that could be causing issues. Uninstalling the modules before updating, uninstalling Magisk, manually deleting the module directories in /data/adb/modules (or the whole modules directory) or wiping /data would all be ways of accomplishing this...
This might not be true for everyone, but it's quite likely.
Edit: Oh yeah... And don't install TWRP. Only booting it seems to be fine though.
I got it to work !!! Pixel 4 XL user. Might work on other Pixel phones / non-Pixel phones as well.
You need to download Magisk Canary apk first.
Try this post https://www.xda-developers.com/latest-magisk-canary-release-adds-support-for-android-11/
Here is the trick, you need to set the update channel in the settings to Canary Debug. Just Canary won't work and won't show any updates!
Then you will see immediately that a new version is available for manager and Magisk. Update the manager first. Then install Magisk to boot.img. Flash and there you go. I even got modules working and GPay works and even the CTS profile works! previously that failed on me (despite trying the settings recommended and Terminus commands with Busybox)
does not work
ChocoboX said:
I got it to work !!! Pixel 4 XL user. Might work on other Pixel phones / non-Pixel phones as well.
You need to download Magisk Canary apk first.
Try this post https://www.xda-developers.com/latest-magisk-canary-release-adds-support-for-android-11/
Here is the trick, you need to set the update channel in the settings to Canary Debug. Just Canary won't work and won't show any updates!
Then you will see immediately that a new version is available for manager and Magisk. Update the manager first. Then install Magisk to boot.img. Flash and there you go. I even got modules working and GPay works and even the CTS profile works! previously that failed on me (despite trying the settings recommended and Terminus commands with Busybox)
Click to expand...
Click to collapse
i have the same versions but do not see the Canary Debug.
currently it is not working
There's only been one Canary channel for some time (and it's the debug release, even though it doesn't say so in the Manager). If anyone is using a Manager that has both a "Canary" and a "Canary Debug" channel they're using an old build of the Manager. And on such a build, the regular "Canary" channel won't work since it no longer exists.
chaim said:
i have the same versions but do not see the Canary Debug.
currently it is not working
Click to expand...
Click to collapse
Ok, I found the correct link to download Magisk Canary apk
https://forum.xda-developers.com/pixel-4-xl/how-to/android-11-beta-1-jun-2020-t4113249
It's an older version but once you switch to Canary Debug it should show correct updates. For there things worked for me.
Also, I'm attaching a link to download the Magisk boot image for Android 11 directly, in case you want to skip this whole process. Just flash it with Fast Boot
https://1drv.ms/u/s!Ark6wHh1kVRCg9NyWPCCeqtpfT4XUA?e=oRse0J
Does Soli work or do you need to download that module too?
rester555 said:
Does Soli work or do you need to download that module too?
Click to expand...
Click to collapse
What is Soli? Sorry for the dumb question. I can try and see.
It's the RF based motion sensor in the front of the phone that turns on active display and swipes in front of the display to control the phone.
rester555 said:
It's the RF based motion sensor in the front of the phone that turns on active display and swipes in front of the display to control the phone.
Click to expand...
Click to collapse
I'm in the US already so it works without a problem for me. I also tried to install Enable Soli from GitHub and it installed and phone booted. Not sure how to test it further for you.
Just so that there's no confusion...
The correct (and only) place to get the Magisk installation zips and Manager apks is always going to be on John's GitHub.
Here's the (current) link to the up-to-date Canary Manager:
https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
But, if in doubt, always go to the above linked GitHub to get the latest downloads.
Downloading from anywhere else might mean that you are installing an altered (possibly maliciously) root Manager. Don't take the risk...
magisk_patched.img
what command do you use to flash it
i use:
./fastboot flash boot magisk_patched.img
and i gets stuck in bootloop
chaim said:
can anyone upload the magisk_patched.img for pixel 4xl
Click to expand...
Click to collapse
While I don't mind sharing my patched.img, just remember that TJW always recommends that users should patch their own boot.img so as to avoid any potential problems. Having said that, here you go :good:
https://drive.google.com/file/d/15fWU492AQ3eBJCgMGWe2wgc5J2b4MSPu/view?usp=drivesdk
Hi all,
TLDR QUESTION: do I have to "fastboot flash boot magisk_patched_boot.img" every time after "adb sideload ota_file.zip" ?
-------------------------------------------------------------------------------------------------------------------------------------------------
I'm coming over from only using samsung galaxy series to Pixel 5.
I've always used custom roms with root and whenever there was an update available, the usual process was:
1. Flash updated rom.zip
2. Flash magisk.zip
Done.
I assume it's a similar process for pixel phones and I intend to stay on stock rom with root.
I need to pass safetynet for google pay so I have to change the device fingerprint to Pixel 3a to bypass hardware attestation (as written on this forum guides).
1. Does changing the fingerprint to 3a break the on-device OTA updates?
2. Does changing the fingerprint to 3a break updates for Pixel 5 apps?
3. After an OTA update, (either by on-device or sideload), do I have to re-flash the magisk patched boot.img to retain root?
4. Also, if I decide to un-root, does bootloader re-locking also require a device wipe?
Thank you.
swangjang said:
Hi all,
TLDR QUESTION: do I have to "fastboot flash boot magisk_patched_boot.img" every time after "adb sideload ota_file.zip" ?
-------------------------------------------------------------------------------------------------------------------------------------------------
I'm coming over from only using samsung galaxy series to Pixel 5.
I've always used custom roms with root and whenever there was an update available, the usual process was:
1. Flash updated rom.zip
2. Flash magisk.zip
Done.
I assume it's a similar process for pixel phones and I intend to stay on stock rom with root.
I need to pass safetynet for google pay so I have to change the device fingerprint to Pixel 3a to bypass hardware attestation (as written on this forum guides).
1. Does changing the fingerprint to 3a break the on-device OTA updates?
2. Does changing the fingerprint to 3a break updates for Pixel 5 apps?
3. After an OTA update, (either by on-device or sideload), do I have to re-flash the magisk patched boot.img to retain root?
4. Also, if I decide to un-root, does bootloader re-locking also require a device wipe?
Thank you.
Click to expand...
Click to collapse
This may help. https://forum.xda-developers.com/pixel-5/how-to/tutorial-unlock-bootloader-root-valid-t4178673/page1
For bootloader, I'm pretty sure that relocking would wipe the device. I think unlocking it wipes the device.
Though, it's not entirely necessary, I think, to relock the bootloader after unrooting. I think, for preference of complete security over device. I believe it disallows device modification.
dirtyreturn said:
This may help. https://forum.xda-developers.com/pixel-5/how-to/tutorial-unlock-bootloader-root-valid-t4178673/page1
For bootloader, I'm pretty sure that relocking would wipe the device. I think unlocking it wipes the device.
Though, it's not entirely necessary, I think, to relock the bootloader after unrooting. I think, for preference of complete security over device. I believe it disallows device modification.
Click to expand...
Click to collapse
Hi, thanks for your response however I have already read that guide but it does not answer any of my questions.
swangjang said:
Hi, thanks for your response however I have already read that guide but it does not answer any of my questions.
Click to expand...
Click to collapse
Oh, sorry.
1) I think it changes a build.prop entry for device manufacturer or model.
2) Pixel 5 apps? Do you mean specifically designed for this device? I have a 3xl also, and I think and it seems, that stock apps are the same. Ah, for example, the Google stock camera app - I am not sure if a Pixel 5 specific feature would disappear or not work or something.
3) I THINK you will need to. Like, at least with elementalx and kirisakura kernel the (?)script(?) looks to see if Magisk is installed and retains it. I am assuming the Google stock kernel does not .
4) unlocking the bootloader wipes the device, I believe. I would assume relocking the bootloader would. Personally, I've never relocked the bootloader on any device after unrooting . If you do relock, back up your internal storage as an incase , failsafe, or general rule or something.
Hopefully, there will be someone to chime in in case I am wrong.
Hi, i don't use OTA but full image for update but no, it don't break change props on pixel 5 but yes you need to flash magisk again.
Good update. No issues for november update
As the december system/security update is coming, may I confirm the correct way to update:
1. disable all magisk modules, unhide magisk manager
2. Flash newest factory image, or flash OTA zip
3. reboot, and you get an updated but unrooted device
4. root the device as usual with magisk
5. Reapply all the magisk modules you use
cescman said:
As the december system/security update is coming, may I confirm the correct way to update:
1. disable all magisk modules, unhide magisk manager
2. Flash newest factory image, or flash OTA zip
3. reboot, and you get an updated but unrooted device
4. root the device as usual with magisk
5. Reapply all the magisk modules you use
Click to expand...
Click to collapse
That's typically the way I've always do it except you do not unhide MM. I also modify the batch file named ‘flash-all.bat’ and remove the ‘-w' so it doesn't wipe my device.
cescman said:
As the december system/security update is coming, may I confirm the correct way to update:
1. disable all magisk modules, unhide magisk manager
2. Flash newest factory image, or flash OTA zip
3. reboot, and you get an updated but unrooted device
4. root the device as usual with magisk
5. Reapply all the magisk modules you use
Click to expand...
Click to collapse
With the Pixel 2 my process was
1. fastboot flash stock boot and dtbo images for your current build version. (Not sure if dtbo is really needed)
2. Apply OTA via ADB
3. Allow phone to boot and finish update
4. Use magisk to patch the boot image from the new build version
5. fastboot flash patched boot image.
I have used this method for three years with the Pixel 2 and only had one issue. I used smalipatcher to make mock GPS look like real GPS and apparently the magisk module needs to be re-created for each build.
j0nnyd said:
That's typically the way I've always do it except you do not unhide MM. I also modify the batch file named ‘flash-all.bat’ and remove the ‘-w' so it doesn't wipe my device.
Click to expand...
Click to collapse
I do this as well, but couldn't get the boot image patched through magisk for some reason. Anyone have a patched boot image they can share?
I hope to get a more streamlined solution eventually, but this is what I did to upgrade my Unlocked Pixel 5:
Download factory image
Unzip
Edit "flash-all.bat" to remove the "-w", save as "flash-nowipe.bat"
plug in phone and enable debugging
adb reboot bootloader
flash-nowipe.bat
unzip "image-redfin*" into a temp folder
cd into the temp folder
adb push boot.img /sdcard/Download/boot.img
on phone run Magisk Manager and patch /sdcard/Download/boot.img
adb pull /sdcard/Download/magisk_patched.img
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
I didn't need to uninstall / reinstall any modules, they were all there after the final reboot. I did have to uninstall / reinstall vanced using vanced manager to get it working.
Next time I will try patching the boot image and repacking so I need fewer reboots.
*deleted*
TonyApuzzo said:
I hope to get a more streamlined solution eventually, but this is what I did to upgrade my Unlocked Pixel 5:
Download factory image
Unzip
Edit "flash-all.bat" to remove the "-w", save as "flash-nowipe.bat"
plug in phone and enable debugging
adb reboot bootloader
flash-nowipe.bat
unzip "image-redfin*" into a temp folder
cd into the temp folder
adb push boot.img /sdcard/Download/boot.img
on phone run Magisk Manager and patch /sdcard/Download/boot.img
adb pull /sdcard/Download/magisk_patched.img
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
I didn't need to uninstall / reinstall any modules, they were all there after the final reboot. I did have to uninstall / reinstall vanced using vanced manager to get it working.
Next time I will try patching the boot image and repacking so I need fewer reboots.
Click to expand...
Click to collapse
1. What's your build.prop before upgrade?
2. Did you uninstall Magisk (restore/complete) before upgrade?
3. If #2 is 'NO', did your 'Restore Magisk Manager' and disable 'MagiskHide' before upgrade?
Thank you very much!
Hopefully someone can help me out here:
I'm on Mi 9T (davinici) with xiaomi.eu-cROM 12.1.2 (Stable) and OrangeFox Beta R11.0 Recovery. Bootloader is obviously unlocked.
I followed the guide for Magisk v22.0 and installed the apk first, opened it and it says
"Ramdisk No"
Alright, so I have to patch the recovery.img.
In Orangefox Recovery I open the Terminal and extract recovery.img with
Code:
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery.img
Reboot to system and I chose "Install" in Magisk, "Recovery Mode" is already selected, click "Next" and I select the newly created file "recovery.img". Magisk does it's thing and I have "magisk_patched_cOdEy.img" in my Download folder which I pull with adb.
I reboot to fastboot mode and
Code:
fastboot flash recovery magisk_patched_cOdEy.img
which works w/o problems and reboot again.
But when I open Magisk it still says it's not installed.
So, I check the guide under Magisk in Recovery, where it gets really confusing, but from what I got is that I need to start the phone with recovery button combo (Power+VolUp for Mi 9T) pushed and release at splash screen so Magisk is activated. I try this multiple times since it's really hard with the timing (milliseconds too long it kicks me into fastboot mode. idk why).
Can someone figure out what went wrong/what I did wrong? Never had problems with earlier Magisk versions.
Follow up question: There's some warning about going back to stock recovery will brick your phone in installation. Does that include installing OrangeFox again? I'm 95% sure it doesn't, but would be nice to know before I do it.
Some Xiaomi devices have their bootloaders set up so that it will accept an initramfs that was manually added to the boot image. Therefore, on these devices you'll need to patch the boot image even though there's no ramdisk. Try that.
Didgeridoohan said:
Some Xiaomi devices have their bootloaders set up so that it will accept an initramfs that was manually added to the boot image. Therefore, on these devices you'll need to patch the boot image even though there's no ramdisk. Try that.
Click to expand...
Click to collapse
Can I reinstall OrangeFox or TWRP recovery then?
I'll report back, when I tried it.
edit: So this actually works and I was able to enter TWRP recovery again after flashing.
edit 2: Now WiFi is not working anymore. fml.
edit 3: For anyone stumbling over this thread. Nothing worked, I had to do a compelte wipe and then flash Magisk "the old way", by renaming the .apk into a .zip and flashing it in recovery. That did the trick without any probems and I'm rooted now after quite a hassle.
yeah, I stumbled upon it. And I'm having the same/a very similar issue. I was very happy with Magisk up to v22 when the problems began.
I'm still at DerpFest based on Android 9.0 (from 2019 ) and TWRP-3.4.0.0.I had Magisk running since it was 19.4, upgraded it multiple times already. So didn't think much about updating to 22. Then, it said the same: no ramdisk. Pitty. OK, so I went ahead and let Magisk patch the TWRP.img I still got on my phone and flashed the patched TWRP onto recovery. Upon booting, Magisk is there, but no wifi, no sound, no light sensor, ... LTE works, though .
Anyways, I just want to get my old setup back, so I thought, I just flash the original TWRP again. According to the Magisk documentation, if I don't press any button, it should boot to Android without Magisk. Well, it always boots into Android+Magisk disregarding that. If I flash the original TWRP.img back, I always end up in TWRP. So, the order is: boot.img -> magisk-modified-recovery.img -> (boot.img?) -> system. How can I get the behaviour Magisk advertises?
And yes, I tried uninstalling Magisk (via uninstall.zip meythod), which said it would uninstall, but actually didn't. I also flashed different boot images (a backup I had in TWRP, the original boot.img I've found in the DerpFest zip...) to no avail.
So, Immortal68, which of the many wipes one can do did result in the old behaviour? And: now that you have Magisk22, does it say "Ramdisk: yes" again?
1> The Shamshung recent firmware upgrade CWD1 might have some patches that makes rooting problemtic. I flashed TukiROM1.2 with Magisk 26.1 (boot.img patch method) the first time and it worked but as soon as I connected to wifi somehow it upgraded to Magisk Delta (thats how I came to know about the existence of Magisk Delta). Both Magisk 24.3 & 26.1 are not surviving reboots even after flashing (Magisk.OTA.persistence-v1.zip). So staying rooted on a stock factory rom is still an issue. I will try TukiRom1.3 though I request OP to compress the ROM file from 2.7GB to lesser if possible.
2> GSI RAW image files don't go past the bootlogo screen. I tried system image files Elixir, LPOS, Crdroid, EvolutionX, Derpfest etc., none of them booted no matter what dmverity or multidisaabler etc. I flashed before or after. The same raw images used to boot on the same device when it was Andoid 11 but now on Andoid 13 Stock Factory ROM CWD1 GSI images dont boot.
3> Since Magisk is either bootlooping the device after reboot/ After flashing Magisk/or Magisk patched images not surviving reboots, so when I flash the Stock boot image it goes straight to download mode with Vbmeta signed using public key etc errors, or if I flash Magisk patched boot image from TWRP it stuck on Shamshung logo.
4> I have tried some of Dev Roynas ROMs [https://sourceforge.net/projects/a51-builds-by-royna/files/] but they all end up with [TWRP error : 1 Assert failed : update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")] also same error through Sideload.
5> I tried (systemrw_1.32_flashable) by Dev Lebigmac but since the altercation between XDA & Lebigmac on March 2023 he got banned from XDA, I cant get hold of (systemrw_1.4_flashable) to try to check if CWD1 Update is RO-Rom and anything other than 1UI5.1 based wont flash etc.
If anyone has any solutions for CWD1 Factory Stock Rom pls assist. TIA