Note to Mac owners working with the shell scripts included in the factory image - flash-all.sh will NOT execute fully on an M1 MacBook Pro with Apple silicon. Midway through the fastboot update command, the phone will reboot into fastbootd and halt. Apparently this is an issue with USB-C to -C connections on the new MacBooks. I pulled my previous Intel MacBook off the shelf, connected my P6P with a USB-A to -C cable, the fastboot update command executed fully, and my phone is happily running the Jan firmware.
Uninstalling magisk isn't needed but I would recommend to deactivate the modules because you could run into bootloops.
Thanks for the tips.The line with the update is missing (fastboot --skip-reboot update image-raven-sq1d.220105.007.zip):
PATH=%PATH%;"%SYSTEMROOT%\System32" fastboot flash bootloader bootloader-raven-slider-1.0-8013568.img fastboot reboot-bootloader ping -n 5 127.0.0.1 >nul fastboot flash radio radio-raven-g5123b-93368-211225-b-8029609.img fastboot reboot-bootloader ping -n 5 127.0.0.1 >nul fastboot --skip-reboot update image-raven-sq1d.220105.007.zip fastboot reboot-bootloader ping -n 5 127.0.0.1 >nul fastboot flash boot magisk_patched.img fastboot reboot
The patched boot was renamed just like it shows in the flash-all?
Yes, I did it strictly according that tips. cmd windows also show that the patched boot img was flashed but it failed boot into systme just got a bootloop when powered by android appeared.
Same here. How do we fix this?Oh damn, this worked for me in Dec, but the Jan version horked itself. It looks like it didn't observe the --skip-reboot and tried to reboot after the update, but before flashing the patched image. Now I get a corrupted message.
edit- or maybe I should not have disabled-verity. I can't remember if it did in Dec or not.
Is it possible to get adb working again without wiping? I can't seem to get it connect now.
Unplug your phone.
Thanks. Unfortunately I can't get into the phone. It just goes straight to recovery.
Same here. How do we fix this?
EDIT: Fixed it by sideloading OTA - no data wipe!
ETA: YAY, I'M BACK UP AND RUNNING AFTER USING STOCK RECOVERY TO SIDELOAD THE FULL OTA. THANKS EVERYONE, YOU'VE MADE MY DAY!!! Hello all, I'm hoping someone has some advice: I downloaded the 1/2020 factory image, removed the -w from the .bat...forum.xda-developers.com
Yes it worked. I tried the flash-all.bat and it failed again as before, so I sideloaded again (lost root) and then just booted the rooted image and rerooted.
ExcellentJust used the method in the OP to update. All good! Checked version, root retained, SafetyNet Passes, Gpay launches, Duo Mobile passes all checks. No issues.
This method has been the fastest most consistent way for me to update since day 1 of the P6P. In total it takes about 10 minutes. Five minutes to extract the boot.img, copy it to the phone, patch, copy patched image back, and modify the flash-all.bat. Then slightly under 5 minutes to reboot into the bootloader and run the .bat file. Which basically consists of watching the screen for errors. Much easier for me than all the convoluted steps in some of the procedures previously described. It has been 100% successful every time.
Best of luck to everyone!
fastboot --skip-reboot update [****image_name****] fastboot reboot-bootloader ping -n 5 127.0.0.1 >nul fastboot flash boot magisk_patched.img fastboot reboot echo Press any key to exit...
adb reboot sideload
adb sideload "insert OTA file name here.zip"
adb reboot bootloader
fastboot flash boot "patched_boot.img"
holy poop that worked!! i was scared to try it myself but since i have a backup phone with all my data on it, it wouldnt be so bad to wipe the pixel if i messed it up doing it this way! But hey, it actually worked!!