Pixel 6 won't boot in any modeHi Guys
this method can help Boot Failure as below picture, after reboot will back always to fastboot
View attachment 5722089
Pixel 6 won't boot in any modeHi Guys
this method can help Boot Failure as below picture, after reboot will back always to fastboot
View attachment 5722089
thanks but that doesn't help, i need to know if I can fix it not google replacing the phone, phone is not here otherwise i could try it mysef. just need to know if Magisk or any other Sotfware option exists or hardware replacement is the only way
¯\_( ͡❛ ͜ʖ ͡❛)_/¯thanks but that doesn't help, i need to know if I can fix it not google replacing the phone, phone is not here otherwise i could try it mysef. just need to know if Magisk or any other Sotfware option exists or hardware replacement is the only way
Have you tried Android Flash Tool? Select "Force flash partitions", but doing so will wipe your phone.thanks but that doesn't help, i need to know if I can fix it not google replacing the phone, phone is not here otherwise i could try it mysef. just need to know if Magisk or any other Sotfware option exists or hardware replacement is the only way
No it's not.Just wondering if TWRP is available yet for Pixel 6 / A13? I seen an article on how to install TWRP on the pixel 6, but no mention of android version. I though I would ask here, as I won't trust any other source other than xda.
First Do Not enable everything.In reference to Part II - Instructions, Part 5 Root/Reroot with Magisk and Pass SafetyNet, step Pass Safety Net with SafetyNet Fix, parts 4 and 5:
Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, Google Wallet etc.
and
Get Device Certified Clear Google Play Store, Google Play Services, Google Pay, Google Wallet, etc. data
What exact applications do I need to configure in DenyList and in which apps do I need to Clear storage?
What do you mean by "Do Not enable everything"?First Do Not enable everything.
(I know that is why you are asking. This is for others the may read this post.)
Second, start with these:
- Google Play Service
- Google Play Store
- Google Pay
Checking all the boxes in the DenyList.
33.0.3 is the latest.
fastboot devices
and paste the output hereTry using command prompt instead of PowerShell. Also, it's hard to tell from your screenshot, but is there a space between the period and the i in the root.img entrance?Excuse me, I have successfully unlocked. Magisk is installed and boot.img is extracted. It has also been patched. Why doesn't this step work.
View attachment 5738885View attachment 5738887
I don't know if this works for PowerShell, but I personally find it easier to just drag and drop the file I want to flash into the window, that way I don't have to worry about filenames or paths.Try using command line instead of PowerShell. Also, it's hard to tell from your screenshot, but is there a space between the period and the i in the root.img entrance?
Also, it seems people have better luck when using an A to C cable with USB 2.0 port.
Yeah, I know some prefer it that way. I always use command prompt so not sure how that works with PowerShell, although I would think it would be the same.I don't know if this works for PowerShell, but I personally find it easier to just drag and drop the file I want to flash into the window, that way I don't have to worry about filenames or paths.
I used this method, but it still doesn't work, I used the c to c interface, the original data cableYeah, I know some prefer it that way. I always use command prompt so not sure how that works with PowerShell, although I would think it would be the same.
Here is my step by step method, I'm not sure where is the problem.I don't know if this works for PowerShell, but I personally find it easier to just drag and drop the file I want to flash into the window, that way I don't have to worry about filenames or paths.
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 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
at the command prompt and press Enteradb 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