Related
Hi all,
I've tried different methods to apply the November OTA to my Pixel 3, but so far none has worked seamlessly. Here's what I've tried so far:
- TWRP install the full OTA from Google (fails with a timestamp error)
- sideloading the full OTA from Google (same timestamp error)
- using topjohnwu's suggestion from his Magisk GitHub, which in short temporarily unroots the phone to allow the regular OTA process to take place, then before rebooting use Magisk Manager to patch the boot image of the spare partition (in this scenario, the phone won't even boot fully, it does boot but eventually restarts before hitting the lockscreen).
Is there any correct way to apply OTAs straight from the phone, without using a computer? If not, what would be the best way to update the Pixel 3?
Why not just flash-all (minus the -w) the system image?
sliding_billy said:
Why not just flash-all (minus the -w) the system image?
Click to expand...
Click to collapse
Because that requires a computer. I'd rather have a solution that would allow me to update on the fly; preferably, flashing an OTA through TWRP, which would then allow me to also reflash TWRP itself and Magisk. But, then again, this would simply be my optimal scenario - if it can't be done, I'll stick to flash-all.
GryphonBR said:
Because that requires a computer. I'd rather have a solution that would allow me to update on the fly; preferably, flashing an OTA through TWRP, which would then allow me to also reflash TWRP itself and Magisk. But, then again, this would simply be my optimal scenario - if it can't be done, I'll stick to flash-all.
Click to expand...
Click to collapse
Understood. I have just got so used to installing with the flash-all that is second nature. OTA through TWRP wasn't even working for a long time on the OG Pixel series, and putting the ~700 MB OTA file on the phone seemed like a waste since I only had a 32GB. Either way, permanent TWRP and Magisk are still installed directly from the phone and the TWRP .img fastboot boot needs a computer anyways so there is really no way to avoid the computer completely from end to end.
sliding_billy said:
Understood. I have just got so used to installing with the flash-all that is second nature. OTA through TWRP wasn't even working for a long time on the OG Pixel series, and putting the ~700 MB OTA file on the phone seemed like a waste since I only had a 32GB. Either way, permanent TWRP and Magisk are still installed directly from the phone and the TWRP .img fastboot boot needs a computer anyways so there is really no way to avoid the computer completely from end to end.
Click to expand...
Click to collapse
Well, if I could apply a full OTA directly from an already installed TWRP, then it'd be as simple as reinstalling TWRP and Magisk after the OTA. I was used to doing this on AOSP-based ROMs like Ressurection Remix or CyanogenMod/LineageOS.
GryphonBR said:
Well, if I could apply a full OTA directly from an already installed TWRP, then it'd be as simple as reinstalling TWRP and Magisk after the OTA. I was used to doing this on AOSP-based ROMs like Ressurection Remix or CyanogenMod/LineageOS.
Click to expand...
Click to collapse
No way to do it on a Pixel device (that I am aware of) since TWRP needs ran from outside of the OS. I seem to remember this coming up a bit when the OG Pixel first launched, and then it was just accepted to use fastboot boot.
sliding_billy said:
No way to do it on a Pixel device (that I am aware of) since TWRP needs ran from outside of the OS. I seem to remember this coming up a bit when the OG Pixel first launched, and then it was just accepted to use fastboot boot.
Click to expand...
Click to collapse
Yeah, there's something funky about how TWRP works with the A/B setup, because of the embedded recovery into boot and such, I assume. In any case, at this point it seems like I actually can get it updated using fastboot, so that'll have to do for the time being.
Thanks for bouncing off ideas with me!
GryphonBR said:
Yeah, there's something funky about how TWRP works with the A/B setup, because of the embedded recovery into boot and such, I assume. In any case, at this point it seems like I actually can get it updated using fastboot, so that'll have to do for the time being.
Thanks for bouncing off ideas with me!
Click to expand...
Click to collapse
Any time. Good luck!
GryphonBR said:
Because that requires a computer. I'd rather have a solution that would allow me to update on the fly; preferably, flashing an OTA through TWRP, which would then allow me to also reflash TWRP itself and Magisk. But, then again, this would simply be my optimal scenario - if it can't be done, I'll stick to flash-all.
Click to expand...
Click to collapse
Last I heard flashing OTA in twrp is broken, but even if it is fixed as soon as you flash the OTA you would lose TWRP. So you still need a computer to boot to TWRP to install it and/or root.
The key point is you have to boot to TWRP before you can flash either it or Magisk.
TonikJDK said:
Last I heard flashing OTA in twrp is broken, but even if it is fixed as soon as you flash the OTA you would lose TWRP. So you still need a computer to boot to TWRP to install it and/or root.
The key point is you have to boot to TWRP before you can flash either it or Magisk.
Click to expand...
Click to collapse
But that's what I was trying to do in the first place: booted from TWRP, apply OTA than flash TWRP and Magisk.
Which doesn't boot up, unfortunately. Not sure why.
GryphonBR said:
But that's what I was trying to do in the first place: booted from TWRP, apply OTA than flash TWRP and Magisk.
Which doesn't boot up, unfortunately. Not sure why.
Click to expand...
Click to collapse
Right, it is broke that way right now. It's hard to do because recovery where TWRP sits and boot are the same partition now. Touch one you touch both. So when you flashed the OTA you wiped TWRP out of recovery.
TonikJDK said:
Right, it is broke that way right now. It's hard to do because recovery where TWRP sits and boot are the same partition now. Touch one you touch both. So when you flashed the OTA you wiped TWRP out of recovery.
Click to expand...
Click to collapse
That's true, but when I'm using TWRP that's the runtime instance, not the installed one. So even if it gets overwritten by the OTA installation, it wouldn't matter since it would still be active at that moment.
I went nuts trying to figure out how to sideload the Nov OTA update through TWRP (was always easy with my OG Pixel) and then figured it doesnt work lol. Just did like was already suggested and took out the -w from the OTA and it went smooth after I updated my platform tools. This is the way I will do it from now on even if TWRP gets fixed which that looks unlikely.
Anyone do it without using TWRP?
Dbzruben said:
Anyone do it without using TWRP?
Click to expand...
Click to collapse
Yes, download the factory image and edit the flash-all batch file to remove the -w. Alternately, you can flash the stock boot image of your current os version and use the stock recovery to sideload the ota. Either way twrp will be replaced with the stock recovery.
Sent from my [device_name] using XDA-Developers Legacy app
Dbzruben said:
Anyone do it without using TWRP?
Click to expand...
Click to collapse
Method that worked for me (Fi Pixel3 (blueline), on Nov update, previously rooted via Magisk 17.3 Patch Boot Image File method) has been posted elsewhere & doesn't require TWRP installation. This assumes your device is already OEM Unlocked, has Developer Options/USB Debugging enabled/setup and you have the latest ADB/Drivers installed on your PC:
Download Dec Factory image (blueline-pq1a.181205.006)
Download TWRP 3.2.3-0 bootable image (twrp-3.2.3-0-blueline.img)
Download Magisk 17.3 zip
Download Magisk Manager 6.0.1 APK
Download Magisk Uninstaller (Canary)
Move TWRP bootable image file to ADB folder on PC (Win7 for me)
Unzip Dec image contents into ADB folder on PC
Find the Dec Boot.img file from extracted Dec image contents and copy it to Device Storage (Download folder)
Move Magisk Manager APK & Magisk Uninstaller zip to Device Storage (Download folder)
Modify the flash-all.bat file from the extracted Dec image contents location in Notepad (remove the -w) and save/overwrite the file back to the same directory & close Notepad
Open up command window from ADB folder on PC
adb reboot bootloader
fastboot boot twrp-3.2.3-0-blueline.img
"Install" the Magisk Uninstaller zip (via TWRP) wait for that to finish then reboot to bootloader.
(Re)Open a command window from your PC's ADB folder if you closed it.
flash-all (with the -w previously removed in Notepad). Wait for it to finish.
fastboot reboot (if it doesn't boot back to System once finished)
(Now in Android after 1st system boot) Check that Dec update has taken (Settings->System->About Phone->Build Number). No root.
To continue rooting Dec Image:
Install Magisk Manager APK (from Settings->Storage->Files->Download folder)
Open MM (ignore/dont install anything via MM if prompted). No root (as of yet).
In MM: Settings->Update Channel-> Change to "Beta"
Swipe down in MM to "Update" MM and "Install" v17.3 (17302.zip hotfix) via Patch Boot Image File method (using Dec Boot.img previously extracted and put into Device Storage (Download folder)).
Output Patched_Boot.img should now be located in Device Storage (Download folder).
Copy Patched_Boot.img file from Device Storage to ADB folder on PC
Open up a command window from ADB folder on PC again:
adb reboot bootloader
fastboot flash boot_a Patched_Boot.img
fastboot flash boot_b Patched_Boot.img
fastboot reboot
(assuming everything took) Open up MM, confirm Magisk 17.3 is installed & you have root
Re-Install all relevant MM modules (i did not have Active Edge module previously installed but heard there were issues with this module & root)
There's way more steps in that than needed and really doesn't address how to apply an ota to a rooted phone.
Line 13 is the only thing that would apply.
Sent from my [device_name] using XDA-Developers Legacy app
I cont root my pixel with Dezember Update. It stock on bootloop after i flashed the patched Magisk images.
Serial Kazama said:
I cont root my pixel with Dezember Update. It stock on bootloop after i flashed the patched Magisk images.
Click to expand...
Click to collapse
Have you tried to root using twrp and the magisk zip?
Sent from my [device_name] using XDA-Developers Legacy app
Find the solution, i forgot to use the Magist Uninstaller Zip before i root the new OTA. My fault. Thx anyway!
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: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ2A.210305.006, Mar 2021"!
Magisk v22.0 Patched Boot Image: https://www.androidfilehost.com/?fid=17248734326145746586
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=17248734326145746583
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=17248734326145746585
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------
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 (RQ1A.210205.004, Feb 2021)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq1a.210205.004-factory-dtbo.img: https://www.androidfilehost.com/?fid=17248734326145727318
coral-rq1a.210205.004-factory-boot.img: https://www.androidfilehost.com/?fid=17248734326145727317
March 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq2a.210305.006-c7e59bf8.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-rq1a.210205.004-factory-boot.img
3. fastboot flash dtbo coral-rq1a.210205.004-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-rq2a.210305.006-c7e59bf8.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-rq2a.210305.006-magisk_patched-22.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.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------
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
Since Magisk v21.x, Core Only mode has been replaced by using Android's built-in Safe Mode. Booting into Safe Mode should essentially boot you back into your system but with all modules disabled (as well as Magisk Hide). Keep in mind that even after you reboot, modules will remain disabled, unless you re-enable them first. Also remember to re-enable Magisk Hide if you had it enabled before.
Please see @Didgeridoohan's guide for more details: https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Core_Only_Mode
It's also worth mentioning, his guide is extremely well-made and contains a lot of useful information that could benefit all Magisk users and modders. I highly recommend looking through it anyway!
I've tried this but it keeps rebooting into fastboot mode with "no valid slot to boot". Also tried other kernels but can only boot to the unpached boot img.
neomasterpt said:
I've tried this but it keeps rebooting into fastboot mode with "no valid slot to boot". Also tried other kernels but can only boot to the unpached boot img.
Click to expand...
Click to collapse
Did you try flashing the patched img to both slots?
Code:
fastboot flash boot magisk_patched.img --slot all
worked like a charm. thanks
The update itself worked with your method. However since then my phone keeps freezing after I try to unlock it. Ergo it boots up normally, I see the start screen but when I try to unlock it by writing down my pin, the phone freezes and instandly restarts. I already tried booting to safemode and disabling all magisk modules, but it seems that this did not work.
This is my method works all the time.
patched boot.img via magisk
fastboot flash bootloader<bootloader.img>
fastboot reboot bootloader
fastboot flash radio<radio.img>
fastboot reboot bootloader
fastboot --skip-reboot update<image.zip>
fastboot reboot bootloader
fastboot flash boot<patchedboot.img>
fastboot reboot
neomasterpt said:
I've tried this but it keeps rebooting into fastboot mode with "no valid slot to boot". Also tried other kernels but can only boot to the unpached boot img.
Click to expand...
Click to collapse
Did you get this sorted out?
Morgrain said:
The update itself worked with your method. However since then my phone keeps freezing after I try to unlock it. Ergo it boots up normally, I see the start screen but when I try to unlock it by writing down my pin, the phone freezes and instandly restarts. I already tried booting to safemode and disabling all magisk modules, but it seems that this did not work.
Click to expand...
Click to collapse
I would try flashing the stock boot image and see if you can get in.
Maybe can also try flashing the full factory image with the -w removed in the script file. Just run stock first (don't replace the boot.img with the Magisk patched boot) to make sure it's not Magisk related.
I hate to bring potential bad news, but I had something similar happen, twice now. Though not exactly as described. Both times I had to full wipe too... First time, I woke up to my phone being completely out of space, and while I could unlock, I would only have a few seconds (seemingly random) to use the phone before it would freeze and reboot. I thought maybe it had to do with the phone running out of space at the time.
When it happened again a few months later, my phone had plenty of space. But like last time, phone would boot up, I would unlock, and then it would run like crap until eventually forced rebooting. Trying all combinations of stock / Magisk / modified boot images, flashing full firmware (with -w removed), rolling back to previous firmware... Nothing worked and eventually it just got stuck at the G logo. Had to full wipe at that point, but luckily I had backups of my important stuff.
First time happened on Android 10, second time happened on Android 11. Weird. There's actually a thread I read a while back with people describing the same issue, and ultimately seems like only a full wipe fixed it.
Oh and one last thing - for me, while I can't prove it, both times it happened shortly after I installed the Storage Isolation / Redirect (Riru) app / module... Didn't occur to me until later that maybe that somehow messed with some permissions related to System UI that even disabling the module later wouldn't fix. I use it on my other devices without issue, but I have since never installed it back on my P4XL and no problems in months. Also both times, Magisk Manager was also acting crazy, and I couldn't flash new modules or anything. It kept saying it didn't have storage permissions, even though it did, and no amount of uninstalling / reinstalling / etc would bring it back to a working state. Again why I somewhat suspect Storage Isolation was causing some weird stuff to happen...
But since it only happened to you after updating, hopefully it's something else, and hopefully going stock can maybe get you back running. Maybe one of the partitions failed to update or something, and flashing the full image can help. Just remember to remove the "-w" flag in the batch / shell file or it'll wipe your data!!!
Edit: oh, this is probably pretty important, were you already running Magisk v22.0? Magisk Manager is completely revamped in 22.0, and I wouldn't be surprised if you would have problems if running older Magisk Manager with Magisk 22.0. If you were still on 21.x and Manager 8.x, I would flash last months firmware (-w removed, blah blah), update to Magisk 22.0, and then run the OTA... Best of luck, I hope it all works out for you!
Booted my old ssd with windows 10 just to update from feb to march.
Everything fine so far using your files no idea whats wrong with my new Windows ssd tho lol
I'm also getting the "no valid slot to boot" both with the self patched boot image and the one posted here.
Tried this command "fastboot flash boot magisk_patched.img --slot all" did not work.
Jesus1988 said:
Did you try flashing the patched img to both slots?
Code:
fastboot flash boot magisk_patched.img --slot all
Click to expand...
Click to collapse
Nope! did not work!
I can boot with Cleanstate kernel also. Just not Magisk. also tried to patch cleanstate but the patched version wont boot.
neomasterpt said:
Nope! did not work!
I can boot with Cleanstate kernel also. Just not Magisk. also tried to patch cleanstate but the patched version wont boot.
Click to expand...
Click to collapse
Were you already on Magisk 22.0 before updating?
Either way, flash this month's factory dtbo and boot images to their respective partitions. See if you can boot. Could be working the way you described because another installation patched your dtbo and it needs to be reverted.
If you were on Magisk 21.x before updating, upgrade Magisk Manager (now just Magisk.apk) to 22.0. Make sure to follow all warnings on Magisk's changelog (if Magisk Manager app package was hidden before, unhide before updating).
Flash the Magisk 22.0 patched boot image. Flash either the one in the OP or patch it yourself using Magisk (Manager) 22.0. Boot the phone. If it works, flash kernel in EX / FR KM.
Also please let me know if you were on Magisk 22.0 or 21.x before updating. I wanna know if this could cause problems as I mentioned previously.
i5lee8bit said:
Were you already on Magisk 22.0 before updating?
Either way, flash this month's factory dtbo and boot images to their respective partitions. See if you can boot. Could be working the way you described because another installation patched your dtbo and it needs to be reverted.
If you were on Magisk 21.x before updating, upgrade Magisk Manager (now just Magisk.apk) to 22.0. Make sure to follow all warnings on Magisk's changelog (if Magisk Manager app package was hidden before, unhide before updating).
Flash the Magisk 22.0 patched boot image. Flash either the one in the OP or patch it yourself using Magisk (Manager) 22.0. Boot the phone. If it works, flash kernel in EX / FR KM.
Also please let me know if you were on Magisk 22.0 or 21.x before updating. I wanna know if this could cause problems as I mentioned previously.
Click to expand...
Click to collapse
Still does not work.
And yes I was on v22.
neomasterpt said:
Still does not work.
And yes I was on v22.
Click to expand...
Click to collapse
But you can boot stock? Did you try booting in safe mode yet?
If you can't even boot to safe mode while Magisk patched boot is installed, as a last resort, and may be overkill because unfortunately I don't physically have access or know your whole setup, download the Feb 2021 full factory image. Flash it with the "-w" flag removed so you don't lose data. Install Magisk 22.0 apk, patch the stock boot file (for Feb 2021) and flash it. Hopefully it boots back to your previous state on Feb 2021 firmware before attempting upgrade.
Now we can try 2 different directions. Overkill version: open Magisk Manager and (complete) uninstall. Now take the OTA as per OP instructions and hopefully it boots now. You should be rooted but now with no modules installed.
Or, try disabling any potential modules that may be causing problems before updating again. Reboot once fully after disabling before doing upgrade. I would recommend disabling anything that targets SystemUI, as well as Ed/LS-posed. Or perhaps it could be an Xposed module itself.
Good luck.
I had to do a full wipe before getting root to work and boot. Probably due to something with Magisk updating to v.22
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images")
Some users have reported that booting (instead of flashing) the patched boot image works and makes root temporarily available but i didn't have any success with that.
The phone booted up but root didn't work.
I won't explain how to unlock the bootloader or set up adb here.
!Warning! This will wipe your phone so take a backup!
Also i do not take any responsibility if you break your device.
And if anything goes wrong just factory reset your device using the Android Flash Tool or by following this tutorial.
Here's what i did to get Magisk v22.0 working on the first developer preview of Android 12:
Install A12 with disabled AVB & dm-verity:
Make sure USB-Debugging is enabled in developer-options and you have authorized the pc you're using on your phone.
Boot your phone into fastboot mode.
You can do this by turning it off and then starting it by holding Power + Volume Down
until fastboot mode appears or just adb reboot bootloader
Go here and click on the link for the Android Flash Tool.
(I didn't copy the link directly so i don't have to update it everytime google releases a new update)
It should ask you to allow the website to access ADB Keys. Click Ok.
If the website somehow doesn't work, try using Google Chrome.
Select your Pixel 5. If it's not showing up click add device.
Click on the edit symbol (pen) in the box where the selected build is shown.
Make sure Wipe Device, Disable Verity and Disable Verification are checked.
Install and boot the phone when it's finished.
Patch & flash boot.img
Download and install the Magisk Canary App from GitHub.
Download the factory image from here and extract boot.img from it.
(Inside the downloaded zip-file is another zip file containing the boot image)
Copy the extracted boot.img to your phone and open the magisk app.
Click on Install -> Select and Patch a File and let it do its magic.
Copy the magisk-patched boot image that should be found in your phones download folder back to your PC.
Reboot into fastboot mode as i explained earlier and flash the patched boot image.
(fastboot flash boot magisk_patched.img)
Then reboot the device.
Now root should be working. If it bootloops and says your phone has to be factory reset, do it.
If for some reason you still get an AVB-Error and end up stuck in fastboot mode just flash the stock image and try to patch it again.
This is my first post on here and i didn't have much time but i'm glad if it helped at least one person.
Thanks for create this post.Works perfect,
Ivixmax said:
Thanks for create this post.Works perfect,
Click to expand...
Click to collapse
Hey, thanks for this. FYI @LazerL0rd (zest kernel) detailed here (click on the spoiler) how to do this with just the command line and factory images and without the need for the AFT.
edit: formatting
I keep on getting the AVB-Error to no end.
new beta magisk not working
morpheus620 said:
new beta magisk not working
Click to expand...
Click to collapse
Make sure to disable verity & verification and use magisk canary, not beta
okay. is working. sorry für the misstake.
morpheus620 said:
okay. is working. sorry für the misstake.
Click to expand...
Click to collapse
Alles gut
Anyone able to get safety net to pass on Android 12?
greenlight63 said:
Anyone able to get safety net to pass on Android 12?
Click to expand...
Click to collapse
Unfortunately no, universal safetynet fix 2.0.0 by kdrag0n makes basicIntegrity pass but since the update to dp3 CTS still fails.
Dirty flashing newer factory images will restore the verity and verification state, so when you patch the kernel with magisk it will fail to boot again.
Installing a verity and verification disabled image without wiping from the web based flasher will also corrupt your data and not let the phone boot, forcing you to wipe.
Wonder what the flags are for flashing factory images with verity and verification state off and giving the ability to continue on without wiping and being able to boot the magisk patched kernel again.
fastboot update --disable-verity --disable-verification image-redfin-spp3210325.010.zip maybe?
Or prepatch the boot.img before flashing it with fastboot, and then flashing it back before rebooting from after flashing the factory image as an update?
tauio111 said:
Dirty flashing newer factory images will restore the verity and verification state, so when you patch the kernel with magisk it will fail to boot again.
Installing a verity and verification disabled image without wiping from the web based flasher will also corrupt your data and not let the phone boot, forcing you to wipe.
Wonder what the flags are for flashing factory images with verity and verification state off and giving the ability to continue on without wiping and being able to boot the magisk patched kernel again.
fastboot update --disable-verity --disable-verification image-redfin-spp3210325.010.zip maybe?
Or prepatch the boot.img before flashing it with fastboot, and then flashing it back before rebooting from after flashing the factory image as an update?
Click to expand...
Click to collapse
Don't know but sounds interesting. I just use
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after every update
Works like a charm Android 12 pixel 4a 5g
I just installed the newest Public Beta via OTA. Can I root? I was rooted on 11 before and just enrolled in the beta program and installed it via OTA. Without factory reset or reflash. Now I tried patching boot.img via Magisk Manager, but it wont boot. I mean it boots, but wont unlock phone to homescreen. I'm locked out of my phone. Reverted back to stock PB1 boot image. Any ideas without factory reset?
THEVAN3D said:
I just installed the newest Public Beta via OTA. Can I root? I was rooted on 11 before and just enrolled in the beta program and installed it via OTA. Without factory reset or reflash. Now I tried patching boot.img via Magisk Manager, but it wont boot. I mean it boots, but wont unlock phone to homescreen. I'm locked out of my phone. Reverted back to stock PB1 boot image. Any ideas without factory reset?
Click to expand...
Click to collapse
I just tried it using the canary build and it won't boot either. It gets stuck at the Bootloader screen and shows "Failed to load/verify boot images". Maybe we need to wait for an update to for Magisk?
QuickInfo said:
I just tried it using the canary build and it won't boot either. It gets stuck at the Bootloader screen and shows "Failed to load/verify boot images". Maybe we need to wait for an update to for Magisk?
Click to expand...
Click to collapse
Did you try it according to the manual from the first post from @myhuky3?
kafisc said:
Did you try it according to the manual from the first post from @myhuky3?
Click to expand...
Click to collapse
Not yet, I'll wait until the end of the beta program before I reset it. I can get temporary root by booting into the patched Magisk boot image
Following the OP it worked great on the public beta been running it since last night its awesome thank you for the guide
delete
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: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ2A.210405.005, Apr 2021"!
Magisk v22.0 Patched Boot Image: https://www.androidfilehost.com/?fid=2188818919693776322
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=2188818919693776321
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=2188818919693776320
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------
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 (RQ2A.210305.006, Mar 2021)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq2a.210305.006-factory-dtbo.img: https://www.androidfilehost.com/?fid=17248734326145746585
coral-rq2a.210305.006-factory-boot.img: https://www.androidfilehost.com/?fid=17248734326145746583
April 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq2a.210405.005-0d148a1d.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-rq2a.210305.006-factory-boot.img
3. fastboot flash dtbo coral-rq2a.210305.006-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-rq2a.210405.005-0d148a1d.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-rq2a.210405.005-magisk_patched-22.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.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------
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
Since Magisk v21.x, Core Only mode has been replaced by using Android's built-in Safe Mode. Booting into Safe Mode should essentially boot you back into your system but with all modules disabled (as well as Magisk Hide). Keep in mind that even after you reboot, modules will remain disabled, unless you re-enable them first. Also remember to re-enable Magisk Hide if you had it enabled before.
Please see @Didgeridoohan's guide for more details: https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Core_Only_Mode
It's also worth mentioning, his guide is extremely well-made and contains a lot of useful information that could benefit all Magisk users and modders. I highly recommend looking through it anyway!
@i5lee8bit - thanks, worked fine on my Pixel 4 XL. However, during the OTA process my console showed me following error message:
Code:
C:\Unified_Android_ToolKit\platform-tools_r30.0.4-windows\platform-tools> adb sideload C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip
serving: 'C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip' (~94%) adb: failed to read command: No error
The device itself showed something across the lines of exit error code 0.
Everything seems to be running ok so far. Do I have to worry about the OTA stopping to transfer at 94%?
niko26 said:
Code:
C:\Unified_Android_ToolKit\platform-tools_r30.0.4-windows\platform-tools> adb sideload C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip
serving: 'C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip' (~94%) adb: failed to read command: No error
The device itself showed something across the lines of exit error code 0.
Everything seems to be running ok so far. Do I have to worry about the OTA stopping to transfer at 94%?
Click to expand...
Click to collapse
Maybe you should update your platform tools to the latest version: it's v31.0.0 as of February 2021. Your log says you're running 30.0.4.
Hi. This first time happens to me when I reboot the phone the Root is gone and have to flash the magisk_patched again!! Please is there any suggestion on how I keep Root after reboot?
DinarQ8 said:
Hi. This first time happens to me when I reboot the phone the Root is gone and have to flash the magisk_patched again!! Please is there any suggestion on how I keep Root after reboot?
Click to expand...
Click to collapse
You'll have to re-root after each update. The method used to keep root when updating via OTA was removed from Magisk b/c it was causing problems on Pixels.
niko26 said:
@i5lee8bit - thanks, worked fine on my Pixel 4 XL. However, during the OTA process my console showed me following error message:
Code:
C:\Unified_Android_ToolKit\platform-tools_r30.0.4-windows\platform-tools> adb sideload C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip
serving: 'C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip' (~94%) adb: failed to read command: No error
The device itself showed something across the lines of exit error code 0.
Everything seems to be running ok so far. Do I have to worry about the OTA stopping to transfer at 94%?
Click to expand...
Click to collapse
Like @Ghisy already said, definitely start with trying newest platform tools. I've had that error come up before but experienced no problems.. weird thing is it happened to my wife's Pixel 4, but not my Pixel 4 XL when I did the updates right after another. So used the same platform tools, PC, etc. Another thing to consider that may help you feel better is that some custom ROMs actually expect that to happen when installing their ROM as a sideload OTA, so could indeed be nothing to worry about.
If it really really worries you, you could always flash the full factory image with "-w" removed from the script file, and either replace the boot.img with the Magisk patched one (rename it first), or flash it separately later. But for now if everything is working normally and it indicates you're on April 2021, I wouldn't worry about it.
DinarQ8 said:
Hi. This first time happens to me when I reboot the phone the Root is gone and have to flash the magisk_patched again!! Please is there any suggestion on how I keep Root after reboot?
Click to expand...
Click to collapse
What @Lughnasadh said is certainly true; is this what you mean? Or the way I read your question, are you losing root between reboot despite flashing the Magisk patched boot image? Are you sure you flashed it? Are you doing fastboot flash boot (file.img) or doing fastboot boot (file.img)? Make sure you're actually flashing it, not just booting to it. If all else fails, try doing a complete uninstall of Magisk and then start over (hopefully won't be necessary). I've never heard of anyone having the problem you're having though, and it sounds more like you're fastboot booting to the Magisk patched image, and not actually fastboot flashing it...
i5lee8bit said:
Like @Ghisy already said, definitely start with trying newest platform tools. I've had that error come up before but experienced no problems.. weird thing is it happened to my wife's Pixel 4, but not my Pixel 4 XL when I did the updates right after another. So used the same platform tools, PC, etc. Another thing to consider that may help you feel better is that some custom ROMs actually expect that to happen when installing their ROM as a sideload OTA, so could indeed be nothing to worry about.
If it really really worries you, you could always flash the full factory image with "-w" removed from the script file, and either replace the boot.img with the Magisk patched one (rename it first), or flash it separately later. But for now if everything is working normally and it indicates you're on April 2021, I wouldn't worry about it.
What @Lughnasadh said is certainly true; is this what you mean? Or the way I read your question, are you losing root between reboot despite flashing the Magisk patched boot image? Are you sure you flashed it? Are you doing fastboot flash boot (file.img) or doing fastboot boot (file.img)? Make sure you're actually flashing it, not just booting to it. If all else fails, try doing a complete uninstall of Magisk and then start over (hopefully won't be necessary). I've never heard of anyone having the problem you're having though, and it sounds more like you're fastboot booting to the Magisk patched image, and not actually fastboot flashing it...
Click to expand...
Click to collapse
Ohhh yes thanks to remember me i forgot to write FLASH i was only boot without flash. Thanks for all
im having an issue with getting root back. i followed the instructions and when its time to reboot to the system, i get the splash screen but it reboots back to the bootloader or itll reboot twice and send me to the OS but without Magisk. ive done the factory image thing and still the same thing. i need help
@i5lee8bit Good stuff as usual, updated fine over here! Thanks!
Does anyone know the update process for Magisk now that everything is unified? I used to update manager then patch the boot image again. Is it still the same process from Magisk 22 to 22.1 (today's update)?
Ghisy said:
@i5lee8bit Good stuff as usual, updated fine over here! Thanks!
Does anyone know the update process for Magisk now that everything is unified? I used to update manager then patch the boot image again. Is it still the same process from Magisk 22 to 22.1 (today's update)?
Click to expand...
Click to collapse
If you are already rooted on Magisk 22.0, you should be able to just update the app to 22.1 and then do the direct install method to update root (I just did this and everything was fine using Beta channel). If you were unrooted and installing root for the first time (rather than updating), patching the boot image would be the way to go.
@Lughnasadh Yeah, I'm already rooted on v22. Just did the app update then direct install and it worked fine! I've been in the rooting game since the HTC Desire but the latest changes with Magisk confused me for a minute there!
Thanks
bluizzo said:
im having an issue with getting root back. i followed the instructions and when its time to reboot to the system, i get the splash screen but it reboots back to the bootloader or itll reboot twice and send me to the OS but without Magisk. ive done the factory image thing and still the same thing. i need help
Click to expand...
Click to collapse
Hey sorry, had a really busy week and haven't been on XDA in a few days. Did you get this resolved yet?
My first thought was you were probably bootlooping due to a Magisk (or Xposed) module that doesn't agree with the new firmware. Because that could cause a bootloop, kicking you back to bootloader and eventually forcing a safe mode boot, disabling all Magisk modules and MagiskHide... only problem with this is that afterwards, you should still have root, though with all modules and MagiskHide disabled (I'm more attuned to believe this was actually your case, not that you were "losing root" per se. When it boots back up, are you able to go into Magisk Manager and toggle your modules? Also, what does it say on the manager's home page under "Magisk" and "App" sections? (the parts titled "Installed"). You'll also want to make sure you're running / have installed Manager v22.0 (if flashing the Magisk patched image I provided in the OP; you can always update Magisk / Magisk Manager to v22.1 afterwards).
Sounds like you already tried flashing the 04-2021 full factory image too? Which would eliminate the possibility you maybe flashed the wrong boot / dtbo / or OTA files. If all else fails:
Re-flash full factory image (remove the -w flag in the script file - it sounds like you already did this so I'm assuming you know why) and it should boot unrooted - but you should be able to use the phone.
Make sure Magisk Manager version is 22.0 (i.e. same version as patched in the OP, though 22.1 would work fine too), and if not, grab it from topjohnwu's github and install it.
Reboot to bootloader and flash the Magisk patched boot image in OP (fastboot flash boot coral-rq2a.210405.005-magisk_patched-22.0.img).
Boot the phone. Hopefully you're done.
But if it bootloops, boot it in safe mode (this will disable all your modules as well as MagiskHide). Reboot again.
Open Magisk Manager and all modules should be disabled... time to test for the culprit!
Remember to re-enable MagiskHide, if you had it enabled before. It does not automatically re-enable like it did back in the pre-Magisk 21.0 days. Wow, this post ended up being a lot longer than I expected, and you might not even need the help anymore, lol (though I hope you did get it resolved sooner than later). But at least I can link to this as reference for future guides. Best of luck to you.
Lughnasadh said:
If you are already rooted on Magisk 22.0, you should be able to just update the app to 22.1 and then do the direct install method to update root (I just did this and everything was fine using Beta channel). If you were unrooted and installing root for the first time (rather than updating), patching the boot image would be the way to go.
Click to expand...
Click to collapse
Exactly as @Lughnasadh said, this is what I do too (except I'm using stable channel). Direct Install used to give me problems, but that was almost a year ago (a bit after I first got the phone last March), but it hasn't given me any problems since. Even in the very unlikely chance it did cause problems, you could always re-flash the patched boot image in the OP and then patch the stock boot image yourself using Magisk Manager and flash it.
i5lee8bit said:
Hey sorry, had a really busy week and haven't been on XDA in a few days. Did you get this resolved yet?
My first thought was you were probably bootlooping due to a Magisk (or Xposed) module that doesn't agree with the new firmware. Because that could cause a bootloop, kicking you back to bootloader and eventually forcing a safe mode boot, disabling all Magisk modules and MagiskHide... only problem with this is that afterwards, you should still have root, though with all modules and MagiskHide disabled (I'm more attuned to believe this was actually your case, not that you were "losing root" per se. When it boots back up, are you able to go into Magisk Manager and toggle your modules? Also, what does it say on the manager's home page under "Magisk" and "App" sections? (the parts titled "Installed"). You'll also want to make sure you're running / have installed Manager v22.0 (if flashing the Magisk patched image I provided in the OP; you can always update Magisk / Magisk Manager to v22.1 afterwards).
Sounds like you already tried flashing the 04-2021 full factory image too? Which would eliminate the possibility you maybe flashed the wrong boot / dtbo / or OTA files. If all else fails:
Re-flash full factory image (remove the -w flag in the script file - it sounds like you already did this so I'm assuming you know why) and it should boot unrooted - but you should be able to use the phone.
Make sure Magisk Manager version is 22.0 (i.e. same version as patched in the OP, though 22.1 would work fine too), and if not, grab it from topjohnwu's github and install it.
Reboot to bootloader and flash the Magisk patched boot image in OP (fastboot flash boot coral-rq2a.210405.005-magisk_patched-22.0.img).
Boot the phone. Hopefully you're done.
But if it bootloops, boot it in safe mode (this will disable all your modules as well as MagiskHide). Reboot again.
Open Magisk Manager and all modules should be disabled... time to test for the culprit!
Remember to re-enable MagiskHide, if you had it enabled before. It does not automatically re-enable like it did back in the pre-Magisk 21.0 days. Wow, this post ended up being a lot longer than I expected, and you might not even need the help anymore, lol (though I hope you did get it resolved sooner than later). But at least I can link to this as reference for future guides. Best of luck to you.
Exactly as @Lughnasadh said, this is what I do too (except I'm using stable channel). Direct Install used to give me problems, but that was almost a year ago (a bit after I first got the phone last March), but it hasn't given me any problems since. Even in the very unlikely chance it did cause problems, you could always re-flash the patched boot image in the OP and then patch the stock boot image yourself using Magisk Manager and flash it.
Click to expand...
Click to collapse
Nah, you're good fam. I ended up accidentally flashing the factory img and I'm back with root. Thank you for your help and the guides
Hello everyone hope you are all keeping well.
Here is a little guide on how to Unlock/Lock the Bootloader and Root/Unroot our Nord2T.
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
Unlock The Bootloader;
If you haven't done it already...beware that this will erase all of your user data. To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(device should now unlock)
Code:
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
Rooting Guide;
Unlocking the Bootloader is necessary before continuing
1 - Download Nord2T stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Spoiler: Global Build boot.img's
Stock boot CPH2399_11_A.07 (did not extract it and can't find the firmware file to be able to download and extract, if someone could please upload a link to it on this thread I would sincerely appreciate it)
Stock Boot CPH2399_11_A.09
Stock Boot CPH2399_11_A.11
Stock Boot CPH2399_11_A.14
Stock Boot CPH2399_11_A.15
Stock Boot CPH2399_11_A.16
Stock Boot CPH2399_11_A.17
Stock Boot CPH2399_11_A.19
Stock Boot CPH2399_11_C.24
Stock Boot CPH2399_11_C.26
Stock Boot CPH2399_11_C.27
Spoiler: IND Build boot.img's
Stock Boot CPH2401_11_A.11
Stock Boot CPH2401_11_A.13
Stock Boot CPH2401_11_A.14
Stock Boot CPH2401_11_A.15
Stock Boot CPH2401_11_A.16
Stock Boot CPH2401_11_A.17
Stock Boot CPH2401_11_A.18
Stock Boot CPH2401_11_A.19 (I didn't capture the download for this, if anyone has it please send me a link to the official OTA)
Stock Boot CPH2401_11_C.23
Stock Boot CPH2401_11_C.24
Stock Boot CPH2401_11_C.26
Stock Boot CPH2401_11_C.27
2 - Download latest Magisk Manager from HERE and install it on your phone
3 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
4 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
5 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
6 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
7 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
System Updates;
For system updates. Just apply the OTA update as normal.
Once updated you will have no root and you must follow steps above again with the new boot.img that corresponds to the firmware version you are on.
Unroot;
To unroot simply flash the stock boot.img.
Relock Bootloader;
If you have TWRP installed flash the stock boot.img (same as your firmware version from earlier in this post)
This is so as you can access fastboot properly.
1 - To relock Bootloader first download Oxygen Updater app from the Playstore.
2 - Download the firmware which corresponds to the firmware which you have currently installed.
3 - Move/copy this firmware.zip to your PC and extract it. (inside you will see a folder and a couple files. The only file we need is payload.bin)
4 - Download/install Fastboot Enhance on your PC
5 - Reboot phone to bootloader mode so it gets detected by Fastboot Enhance, from there boot to fatsbootd.
6 - Flash payload.bin in Fastboot Enhance
7 - Wipe data in fastbootd from your Nord 2T, reboot and finish phone setup.
8 - Enable developer options, enable USB debugging from developer options.
9 - Reboot to bootloader and run the command;
Code:
fastboot flashing lock
The device will be now successfully locked.
Hope this helps out
Thank you so much
Thanks so much. Going to try this weekend with my daughter phone.
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
jolaviska said:
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
Click to expand...
Click to collapse
No I still haven't received the ota. Did you get updated to this version already?
I received the update but refusing to apply it
jolaviska said:
I received the update but refusing to apply it
Click to expand...
Click to collapse
It will show up again.
Don't worry.
Rooted my Nord 2T successfully. Thanks once again
Download Nord2T stock boot.img
Click to expand...
Click to collapse
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
luke! said:
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
Click to expand...
Click to collapse
By using THIS software. I will always update this thread with the latest boot.img files in the future but this is the software I used
Thank you.
And what is the procedure to OTA update, once we have magisk_patched_boot.img installed.
OTA won't install, so need to revert somehow install new update and root again?
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Stock Global boot CPH2399_11_A.11 added to OP. Sorry for the delay, only received the update today
nielsync said:
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Click to expand...
Click to collapse
Ya I didnt do it this way at all because my device updated while i was asleep and i was unrooted, so I had to patch the new boot using the method in the OP.
I would definitely advise restoring the stock boot.img before proceeding with an update, then install the update normally and just patch the new image with magisk and then flash.
For a while the 'install to inactive slot' option only works on certain devices, the Nord 2T obviously is'nt one of those devices.
I'm sure the magisk documentation recommends restoring stock images before an update.
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
cioce said:
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
Click to expand...
Click to collapse
I didn't want to share any of the magisk images because there is a new version of magisk every other week and people may like to be on the beta branch or canary branch of magisk or whatever.
It's very easy to patch the image though. Just download magisk.apk and use it to patch the boot.img's I've provided above. Then move the patched.img to your pc and flash.
But anyways here is the magisk patched.img for CPH2399_11_A.11 using magisk 25.2 stable
Stock Boot for Indian variant CPH2401_11_A.13 added to OP
can u post the latest update boot.img for indian unit CPH2401_11_A.14
Stock boot for Indian CPH2401_11_A.14 added to OP
Stock boot for Global CPH2399_11_A.14 added to OP