Damn!!!!! Guess I'm staying on 26101.
Thanks for the update!!
Damn!!!!! Guess I'm staying on 26101.
Did you read this, it was in the same thread:
I did not, but...... might as well waitDid you read this, it was in the same thread:
[/URL][/URL]
Hi,SDK Platform-tools Update
SDK Platform-tools r. 34.0.3, was released May 22, 2023.
@badabing2003 reported a problem when using it.
https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571575
@Lughnasadh, suggested a fix.
https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571601
@badabing2003, confirmed the suggested fix works.
https://forum.xda-developers.com/t/...7-pro-cheetah-safetynet.4502805/post-88571617
Note: If you use Windows SDK Platform- tools r. 34.0.3. You must set the environment variable.
I think the same is true if you use Linux SDK Platform-tools r. 34.0.3. You must set the enviroment variable.
What error message did you get (screenshot)?Hi,
Did you test any update or rom flashing on Pixel 6 with the rev. 34.0.3 ?
I'm asking because with the rev. 34.0.1, I already had to set ANDROID_PRODUCT_OUT as an environment variable but flashing the rom was still failing.
I don't have any error, my problem was solved using the SDK rev 33 for the May update.What error message did you get (screenshot)?
Which ROM are you trying to flash?
No.I don't have any error, my problem was solved using the SDK rev 33 for the May update.
I just want to know if you have tested the latest SDK platform tools rev 34.0.3 with a Pixel 6 or not.
Nope.I today updated my phone months after I figured out that the OTA update with Magisk doesn't work. Before trying to take the next OTA update and bricking my phone again: Does taking the OTA update with Magisk (assuming to deactivate all modules, uninstalling Magisk and to install magisk into the inactive slot) now work?
https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip - WindowsHi,
Does someone can share SDK Platform-tools 33.0.3 for Linux please?
Thanks.
Beware that if you are on A14B3.1 (maybe other builds as well), you may have trouble patching the boot image with this new Canary release. Couldn't do it on my Pixel 6 Pro. Issue has been opened on Magisk Github.
Looks like there is a Pull Request in progress to fix this issue.Beware that if you are on A14B3.1 (maybe other builds as well), you may have trouble patching the boot image with this new Canary release. Couldn't do it on my Pixel 6 Pro. Issue has been opened on Magisk Github.
Thanks for the update.Looks like there is a Pull Request in progress to fix this issue.
Have no idea. Judging by the PR, I suspect it affects both.Thanks for the update.
Does it only affect Android 14 beta or does it also affect Android 13?
nevermind, it changed "init_boot" to "boot" and it worked. I don't know where I get "init_boot" from.This is the error I get when I try that:
View attachment 5999815
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 flashing unlock
and press enter.fastboot reboot
at the Command Prompt and press enter.fastboot flashing lock
fastboot reboot
fastboot flash init_boot 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.fastboot flash boot boot.img --slot all
adb wait-for-device shell magisk --remove-modules
fastboot Reboot
adb reboot sideload
adb sideload oriole-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 oriole-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
adb sideload oriole-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.Yeah, sometimes flashing an old boot image (it will fail to boot) and then flashing a new boot image works. Sometimes sideloading an OTA works. Sometimes just waiting for the next monthly OTA works. It's a crazy thing with this Pixel 6 series and the changes that have come with it.Thank you both @Lughnasadh and @capntrips!
What's odd is I did reflash my boot image thinking that would fix but it didn't, had to reflash anew from sideload.
Thanks again for the info