nothing for android 13 system update here in the uk yet? im on vodafone. I know I can do sideload, but dont want to be left in a half baked situation resulting in me having to reflash everything and start from scratch
Does the hub have its own power supply?Success, by way of a counterintuitive path.
Using the same laptop and Google USB cable (A to C), but plugging the cable into a USB C to A hub connected to a USB C port on the laptop, the ADB sideload worked perfectly. One would think that a direct connection from the laptop to the phone would be the path to follow, but I had no success with directly connecting to either a USB A or USB C port on the laptop, adding the hub made all the difference.
In my case, everytime I try to update through magisk, I end up with rebooting into splash screen. I always need to flash boot.img through Linux PC/Laptop
But that means twice as many writes to the firmware memory cells!
Also a fan of this method. But I couldn't successfully repack the image zip (it says fail to extract my patched boot.img), so I had to flash patched boot separately. BTW I forgot to add --skip-reboot but as a remedy I immediately held volume down button when I saw the command prompt showed the flash finished XDJust in case this helps answer anyone's questions, here was my experience updating my Pixel 6.
I was running the Android 12 July 2022 security patch, rooted with Magisk 25201, app hidden, Zygisk enabled, and DenyList enforced. Modules in use are Systemless Hosts, USNF-Mod 2.3.1, and one called "OnePlus Oxygen OS 11 - Two-Button Navigation (Standard Height)" that, of course, restores two-button navigation. Everything was working fine, device certified, tap-to-pay working, etc. I didn't restore the app or disable any modules before updating.
I followed the same update process I always use. I downloaded the full factory image and extracted boot.img from image-oriole-___.zip, transferred it to my phone, and patched it with Magisk. Then I transferred the patched file back to my computer, renamed it to boot.img, and put it back into image-oriole-___.zip. I removed -w from the flash-all.bat file, rebooted the phone to bootloader, and ran the batch file. Android 13 was installed, and the phone rebooted.
From what I had read, I was expecting it to take a couple of hours or more optimizing apps. But I was pleasantly surprised when it simply booted up normally after about 30 seconds. Everything looks perfect, Android 13 is installed, Magisk still functioning as expected, and I almost can't believe how smoothly it went.
The only weird thing I encountered at all was that during the flashing process there was a new message I hadn't seen before: "invalid sparse file format at header magic". I didn't find much online about what that means, but it doesn't seem to have done any harm. The flashing still completed successfully and everything seems normal. I'm using the latest platform tools (33.0.2), so it shouldn't be that.