Then I'm not sure but hopefully you have been able to fix your issue
Then I'm not sure but hopefully you have been able to fix your issue
OP, Part I - INFORMATION, Prerequisites, The latest...OTA...or OTA ImageDoes anyone know the device download directory for OTA updates on the Pixel 5?
I accidentally accepted the A12 update. I was able to pause it, but I'd like to delete it if it downloaded so it doesn't auto-install on a reboot.
Sorry if I wasn't clear. I'm not looking for the OTA to flash it. I'm looking for the device directory it downloads to so I can PREVENT automatic or accidental installation.OP, Part I - INFORMATION, Prerequisites, The latest...OTA...or OTA Image
My mistake, I do not know what directory it downloads to.Sorry if I wasn't clear. I'm not looking for the OTA to flash it. I'm looking for the device directory it downloads to so I can PREVENT automatic or accidental installation.
It started the process and I was able to pause it, but I want to delete whatever it has downloaded. I don't know where to find it on device.
Turn off automatic system updates on Dev settingsSorry if I wasn't clear. I'm not looking for the OTA to flash it. I'm looking for the device directory it downloads to so I can PREVENT automatic or accidental installation.
It started the process and I was able to pause it, but I want to delete whatever it has downloaded. I don't know where to find it on device.
I did that on day one and I assure you from experience with A10/11, it's not enough. I also disabled/froze two known update packages. This is Google's incessant workaround through a Google Play Services notification, which I don't want to turn off as it may hook to other notifications.
I'm assuming you are doing, OP, Part II - Instructions, 3. Take the OTA Update and Maintain Root.So i did. follow the instructions on taking the OTA update, tried it with the new February one.
(Edit: restore images in magisk first…) I did deactivate apply update, hit OTA and waited until it’s done. Prompting to reboot, I got to magisk and hit install (ota stuff…, see image)
It rebooted fine, magisk is installed and I have root, but I’m on January patch and update page in settings prompts me to reboot to apply the February patch… any hints?
Edit2: bootloader says I’m booted in slot b, which magisk said to install the OTA?!
Correct, I pressed this in magisk as I followed exactly every step in the instructions.
This is the link to the Instructions to Install Magisk to Inactive Slot.Correct, I pressed this in magisk as I followed exactly every step in the instructions.
And as stated here (
Post in thread '[Guide] Root Pixel 6 (Android 12) with Magisk'
https://xdaforums.com/t/guide-root-pixel-6-android-12-with-magisk.4388733/post-86366139) this should again work with 24101, what I m using.
Edit2: Same behavior for a pixel 6 user: https://xdaforums.com/t/guide-root-pixel-6-oriole-with-magisk.4356233/post-86389143
Am I totally wrong here or missing something ? Can I hit install to inactive slot and test again? Or should I just flash the update manually?
Yes I know, I followed all instructions there 100%, I did install to inactive slot and did not use direct installThis is the link to the Instructions to Install Magisk to Inactive Slot.
Ok! I have no clue why it is not working.Yes I know, I followed all instructions there 100%, I did install to inactive slot and did not use direct install
Were you on a custom kernel when you started the process?Alright, hopefully he can clarify things here (another user in Pixel 6 thread wrote it worked for him)
@Homeboy76 But just to be sure: manually flashing factory image should get me updated, no matter that OTA already did optimize apps and so on? Or just take the OTA and regain root afterwards?
No custom kernel or smth, Stock A12 january patch
Hmm, not sure. Should have worked. The only thing I can think of is that the February OTA wasn't pushed to your device yet and you installed the January one again. But that really doesn't make sense unless you were not on the January build previously.
KernelSU requires a GKI, which I'm sure your A11 is not.I was going to try KernelSU on my Pixel 5 running A11 a while ago, but I got sidetracked and never got to it. I now want to try either KernelSU or APatch on this device.
Does anyone have any successful experience getting either KernelSU or APatch to work on the Pixel 5 running A11?
I want to stick with A11 if possble, because there's a working TWRP version for the Pixel 5 running that OS version, and I do not want to lose nandroid backup/restore capabilities.
Thank you in advance for any thoughts.
fastboot --version
at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.fastboot flash init_boot init_boot.img --slot all
adb wait-for-device shell magisk --remove-modules
. When it finishes type fastboot Reboot
fastboot flashing unlock
and press enter.fastboot reboot
at the Command Prompt and press enter.fastboot flashing lock
fastboot reboot
fastboot flash init_boot init_boot.img --slot all
adb wait-for-device shell magisk --remove-modules
fastboot Reboot
flash-all
at the Command Prompt and press enter.flash-all
at the Command Prompt and press enter.flash-all
at the Command Prompt and press enter.fastboot flash boot boot.img --slot all
adb wait-for-device shell magisk --remove-modules
fastboot Reboot
adb reboot sideload
adb sideload redfin-ota-aa9a.999999.999-aaaa9999.zip
at the command prompt and press Enter.adb reboot bootloader
at the command prompt and press Enter.fastboot flash boot magisk_patched-99999_aA99a.img
at the command prompt and press Enter.fastboot reboot
at the command prompt and press Enter.adb devices
at the command prompt and press Enter. You should see your device's serial number.adb reboot sideload
at the command prompt and press Enter.adb sideload redfin-ota-aa9a.999999.999-aaaa9999.zip
at the command prompt and press Enter.adb reboot
at the command prompt and press Enter.adb reboot sideload
at the command prompt and press Enteradb sideload redfin-ota-aa9a.999999.999-aaaa9999.zip
at the command prompt and press Enter.adb reboot bootloader
at the command prompt and press Enter.fastboot flash boot magisk_patched-99999_aA99a.img
at the command prompt and press Enter.fastboot reboot
at the command prompt and press Enter.fastboot flash boot boot.img --slot all
adb wait-for-device shell magisk --remove-modules
fastboot flash boot "magisk_patched...img"
(name of patched.img file) without the quote marks at the Prompt and press enter.fastboot reboot
at the Prompt and press enter.fastboot devices
to verify communication with phone. It should return your phone's serial number.You should have your stock image you can push over. I do not think replacing the boot image with another patched image would disable anything. You can also use adb to remove any modules. Regardless heres my patched boot image and the command to remove modules. Power off, connect phone enter this command, hold power button to boot phone.is there a magisk boot img with modules disabled?. i have a boot loop and need a boot img with it disabled.