yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] Homeboy76:
Update to OP

New

Android 13 Beta QPR1 Program for the Google Pixels 4a5(G)/5/5a/6/6Pro/6a
[Google Pixel 6] iifuzz:
I am on the "Lock Bootloader" step and I am getting an error that says

"

C:\platform-tools>fastboot flashing lock

FAILED (remote: 'invalid android images, skip locking')

fastboot: error: Command failed

"

Any suggestions?
[Google Pixel 6] Homeboy76:
<Edit> What @capntrips wrote in Post # 347. :)
[Google Pixel 6] capntrips:
Invalid images means you've still got some modded partitions that must be restored to stock before you can lock the bootloader.

The return to stock section is missing the part where you flash the stock firmware. Simply factory resetting the device will not restore the factory images to the various partitions.

The simplest method would be to use the flash tool and check the box for locking the bootloader.
[Google Pixel 6] tom1807:
Did you update to Android 13? Do you have on both slots the Android 13 bootloader?

I guess, you still have the Android 12 bootloader on one slot which prevents to lock the bootloader.

Cheers
[Google Pixel 6] iifuzz:
I just followed the directions starting off with Android 13. I don't know anything about slots. I just reverted back using the android flasher website and gave up. I miss the old one button utilities back in the day.
[Google Pixel 6] m_pastuszek:
I can't patch boot after update to T1B1. Did someone make it?

It's writting boot correctly, but nothing happens. I've tried Canary, but still the same.
[Google Pixel 6] Homeboy76:
When you write

"but nothing happens"

.

What do you mean? The fastboot command, fastboot flash boot magisk_patched...img is not working or something else?

Maybe the boot.img you extracted from the Factory Image (

oriole-t1b1.220819.006-factory-25b9512e.zip

) was corrupt. I don't Know.

Try

- Re-download the factory image

- Check the SHA256 for the factory image:

25b9512e5acb521126f874179fdef55e1f880a333ca0d57ab9e7658b154defe8

- Extract the boot.img and patch it with Magisk Canary 25203 again

Goodluck!

:)
[Google Pixel 6] tom1807:
Check this warning please posted for A13 by Google

Cheers
[Google Pixel 6] Homeboy76:
That

warning

is in the OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~, 2. Install/Update Factory Image keep data, wipe data..., •

Important Note(s):

, 1. "Updating Pixel 6, Pixel 6 Pro, and Pixel 6a devices to Android 13 for the first time
[Google Pixel 6] tom1807:
You are right, could have done that also, but he wrote

Seems not so much.

Cheers

Tom
[Google Pixel 6] m_pastuszek:
The issue was that fastboot flash boot magisk_patched...img was flashing correctly, but Magisk still didn't detect root. I don't know why, but when I woke up in the morning and checked, root was detectable and Magisk also was working correctly 😉
[Google Pixel 6] Quoddity:
Is there a list of pixel models which can have their bootloaders unlocked?

I live in Canada and I want to make sure whatever phone I purchase next can have a custom ROM installed on it.
[Google Pixel 6] Homeboy76:
@Quoddity,

Google Pixel 6 Models:. The international model should have an

unlockable bootloader

.

If you purchase your Google Pixel phone from the

Google Store

or

Google Fi

. You can order the Google pixel with an

unlockable bootloader

. Google pixel phones purchased from, most, U.S. carriers have

locked bootloaders

, and are

carrier locked

.
[Google Pixel 6] rossbeck:
Has anyone been able to apply the September OTA update and re-gain root? I uninstalled Magisk and restored images, but the OTA update fails. "Couldn't update - installation problem". Update size on my 6 is 28.05MB.

Should I download the 2GB OTA and sideload that instead?
[Google Pixel 6] badabing2003:
My not flash factory image with -w removed, just like the guide in OP suggests?

OTA should work, but if you had issues with OTA (what exact issues did you encounter?) factory image should work.

If that does not work (typically no reason it shouldn't) then there is also Android Flash tool.

Short answer to the root question is: Yes we are able to regain root.
[Google Pixel 6] badabing2003:
I suspect that you are still on A12?, if you are on A13, then whatever you do, do not attempt your 3rd option, ie reflash A12, you could end up bricking your device.

The reason it wouldn't update is because it felt that it was tempered with or not what it was expecting.

The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.

At this point I think the best option is to flash_all.bat factory image, with -w removed (see OP).

if you are on A13, or upgrade to A13, make absolutely certain that you flash the bootloader (not the same as boot.img) to both slots, see this thread.

Feel free to ask specific questions or anything that is not clear.
[Google Pixel 6] Homeboy76:
At the point you are at now, following @badabing2003 advice (Post 361) is the best thing you can do:

OP, ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~..., 2. Install/Update Factory Image

keep data

,

wipe data

... Then you should read all of the

Important Note(s):

, before proceeding to •

Flash Factory Image Keep Data

.
[Google Pixel 6] HypromanGT:
Yes, I am still on A12, specifically SQ3A.220705.003.A3.

OK, I'll give that a shot, thank you.

One question, though: I'm assuming I should be flashing the latest (A13, September) factory image, and not (re-)flashing the one I am currently on? (Probably a dumb question, but I've lost a fair amount of confidence at this point)

Noted!

FWIW, I was following your post #319 regarding

Steps For Installing the OTA Update

which is what I was looking to do.

Thank you both for your help!
[Google Pixel 6] badabing2003:
Yes you can use the latest A13, unless for whatever reasons you don't want that.

Keep in mind that once you go to A13, you can't go back to A12 (at least not without issues)

I'm personally on A13 and am happy with it.

I personally never go the OTA route, I find factory image path more reliable and honestly faster too.
[Google Pixel 6] HypromanGT:
Flashing latest A13 factory images (no wipe) to both slots worked. Thank you so much!! 🙇‍♂️

One small note/correction: The instructions call for adding "-- skip-reboot" to the first image flash command in flash-all.bat. It looks like the space in between the double-dash and "skip" is unintentional.

This was my first time trying to let the OS perform the OTA, actually. I had no issues manually sideloading them to the Pixel 2 XL in the past, but I'll definitely be using the factory images going forward 🙃
[Google Pixel 6] badabing2003:
Yeah, that sounds like a typo, there should not be any space.
[Google Pixel 6] Homeboy76:
Fixed
[Google Pixel 6] ypnos42:
Thank you for a great and comprehensive guide.

I don't understand why the guide makes you install both:

Universal SafetyNet Fix · v2.1.3 (Riru) v2.3.1 (Zygisk)

Displax | Release v2.3.1-MOD · Displax/safetynet-fix

In fact, the mod by Displax is a fork of the other repository, and includes the full functionality. It works on its own. I also tested it with a Pixel 6a.
[Google Pixel 6] Homeboy76:
Please check the

edited

instruction in the OP:

~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...

5. Root/Reroot with Magisk and Pass SafetyNet

•

Pass Safety Net with SafetyNet Fix
[Google Pixel 6] Aerosilver:
Sorry for cuestion, what are the steps to update A13 stable to A13 beta and keep root?
[Google Pixel 6] Homeboy76:
I don't know what the steps are to update A13 stable to A13 beta and keep root.

The recommended way to flash Android 13 QPR1 Beta to a Pixel device is to use Android Flash Tool.

I'm guessing going from Android 13 to Android 13 QPR1 Beta

will require wiping your phone

.

My suggestion is to follow the

linked

installation instructions in the OP:

~ ~ ~ Part I - INFORMATION ~ ~ ~

4.

NEW

•

Android 13 Beta QPR1 Program for the Google Pixels 4a5(G)/5/5a/6/6Pro/6a

1. Factory Images

• Link

2. OTA Images

• Link
[Google Pixel 6] Tone Capone:
Hoping someone can help. Just bought a used Google 6. It had 13 installed. After booting into it a couple of times, I checked the current slot and it was 'a'. Using fastboot, I flashed the 13 bootloader to slot 'b'. Then I used the edited flash-all.bat file as suggested in the OP. It gave me something about a 'sparse' error at the end. I cannot boot to system. The Google logo comes up but after about 10 seconds goes back to Bootloader. I have tried changing slots and booting to system, but same result.

I checked and rechecked the hash and it matches what is on the Google Factory Images for the Pixel 6.

Please help!
[Google Pixel 6] Homeboy76:
When you go to settings => About phone what is the Build number on your phone?

I'm assuming three things:

You have the latest version of

SDK Platform-tools

installed on your computer.

You downloaded the latest, applicsble, factory image and extracted it:

13.0.0 (TP1A.220905.004, Sep 2022) b7d576f50b9e27b753c18a9ed70669d9cbd212bb01db121de959d48cfe448e67

or

13.0.0 (TP1A.220905.004.A1, Sep 2022, Verizon, Verizon MVNOs) 8b8585b24193e41f7f1480cef89311a912a751d4e60b6cac97264fe8fd6dcc4b

You can boot the bootloader .

If my assumptions are correct try this:

Boot the bootloader

Open a Command Prompt at the command prompt type: adb wait-for-device shell magisk --remove-modules

Then type: fastboot Reboot

Go to the OP and do ~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~...,2. Install/Update Factory Image

keep data,

,

wipe data

..., •

Flash Factory Image Keep Data

Note: Don't forget to read the •

Important Notes
[Google Pixel 6] Tone Capone:
When I first got the phone yesterday, I checked the build and it was the 13.0.0 TP1A.220905.004

1. Latest version of SDK tools installed

2. The non-verizon image was downloaded (verified checksum)

3. The only thing I can do is boot the bootloader currently

Previously, I had booted into the OS about 4 times without issue. I wanted to make sure both slots had the new boot loader.

The phone was not rooted and had a locked bootloader. I unlocked the boot loader and proceeded to try and flash the other slot (b) with the boot loader. Once that was done and verified, I proceeded with the Edited Flash-All as mentioned in the OP.

ADB does not currently list any devices. But fastboot commands work. ADB debugging was checked off when I started.

It will not boot into the OS...says something about the device being corrupted and may not work properly. Then it just goes back to bootloader. That's where I am stuck.

I have no idea how to fix it.
[Google Pixel 6] Lughnasadh:
Try using Android Flash Tool since fastboot commands work.

Also, make sure you have the latest drivers installed (assuming you are using Windows) and use an A to C cable with a USB 2.0 port.
[Google Pixel 6] Homeboy76:
Took the words right outa my mouth.:ROFLMAO::ROFLMAO::ROFLMAO:
[Google Pixel 6] Tone Capone:
Strangely enough, it worked. I can't say I understand what could have been different other than it did not use my downloaded image (with a verified hash).

Thanks soooooo much for the suggestion to use the flash tool...I had never used it!
[Google Pixel 6] Homeboy76:
:oops: Are you asking a question?
[Google Pixel 6] Lughnasadh:
That person seems to be posting similar posts in a bunch of different threads, Thinking maybe they're trying to get their post count up to 10 🙄

@AarohiAngel , please don't spam threads like this.
[Google Pixel 6] Hiwa@:
Hi Guys

this method can help Boot Failure as below picture, after reboot will back always to fastboot
[Google Pixel 6] Homeboy76:
Good looking out!

:rolleyes: Oops! Cut 'N' Paste without review. :mad:
[Google Pixel 6] baldybill:
If we root the Pixel 6, will it retain pixel-only features like call screening and such?
[Google Pixel 6] badabing2003:
Yes
[Google Pixel 6] bobbarker2:
I am having the same problem where I get the device is corrupted message on boot, but I'm rooted, pass safetynet and everything works perfectly fine.

I updated using flash-all without data wipe. I've repeated steps to the letter from OP to try and fix the issue, whatever it may be, but no luck.
[Google Pixel 6] Homeboy76:
Are you using Magisk Canary 23017?

Is your SDK Platforms-tools r31.0.3?
[Google Pixel 6] bobbarker2:
Yes. Like I said I followed instructions exactly.
[Google Pixel 6] Homeboy76:
Ok.

Maybe this is the solution: https://quoramarketing.com/pixel-6-...ption-suggests-factory-reset-solution-inside/
[Google Pixel 6] bobbarker2:
I'm not crashing. As I said, the phone boots fine, its rooted with Magisk 23017 and passes safetynet. When I reboot my phone, I get the "device corrupt" message and press power to continue and it boots right up.

I've tried doing another flash-all several times and on both slots. Still get the silly "device corrupt" message even though its working perfectly fine.
[Google Pixel 6] Lughnasadh:
You'll likely have to wipe data to get rid of that, either via factory reset or flash-all with the -w intact.
[Google Pixel 6] Homeboy76:
Ok. I hope the next monthly update fixes it. If not I would back up everything and wipe your phone (flash-all with -w) to, hopefully, fix it.
[Google Pixel 6] bobbarker2:
Yep that's the conclusion I've came to, I just don't want to admit defeat yet... I've tried every trick suggested or I've found. This phone is so strange how people can carry out the same operations and end-up with different results.
[Google Pixel 6] Lughnasadh:
Of course, if everything is working fine...... 🤷‍♂️

I agree with that last statement. It's really bizarre.
[Google Pixel 6] Homeboy76:
You're faster than a speeding bullet. Do you have a red S on your chest? :ROFLMAO:
[Google Pixel 6] vandyman:
Just to be a little more clear.

Are you talking about the boot up screen with the orange triangle? If so, that is normal for an unlocked bootloader.

Or when does this messege appear in the boot process?
[Google Pixel 6] Homeboy76:
I completely forgot about that screen even though I wrote about it in the OP:

Nope! No corrupt message
[Google Pixel 6] Lughnasadh:
That screen doesn't have a "device corrupt" message on it though, so I assumed he wasn't talking about that.
[Google Pixel 6] Homeboy76:
Twice in one day, you're gooooood! :)
[Google Pixel 6] vandyman:
Yeah, I just wanted to ask to make sure.

Maybe the person was talking about the corruption after the boot up to the home screen.

Confused.... 🙃
[Google Pixel 6] TNSMANI:
MOD ACTION:

Some thread cleaning done. Guys, please stay on topic and avoid posting unconnected issues/messages.

Thank you.
[Google Pixel 6] vandyman:
It looks like I may have solved the bobbarker2 mystery.

After doing some reading in the Pixel threads I noticed the same questions were asked in the Blu Sparks kernel thread.

Diry flashing back and forth with kernel builds and factory images is the cause of the corrupt system.

Factory wipe is the only way I know to fix that issue.

As a side note : the only kernel that I trusted was EX kernel by Flar2. But he has not built it for the Pixel 6 because of issues.
[Google Pixel 6] Homeboy76:
Pixel 6 won't boot in any mode
[Google Pixel 6] Hiwa@:
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
[Google Pixel 6] Homeboy76:
¯\_( ͡❛ ͜ʖ ͡❛)_/¯
[Google Pixel 6] Lughnasadh:
Have you tried Android Flash Tool? Select "Force flash partitions", but doing so will wipe your phone.
[Google Pixel 6] gustden:
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.
[Google Pixel 6] Lughnasadh:
No it's not.
[Google Pixel 6] Homeboy76:
Magisk Canary.Update

app-release_c3b4678f-25204.apk 11Oct
[Google Pixel 6] Homeboy76:
Magisk Canary.Update

app-release_a468fd94-25205.apk 11Oct
[Google Pixel 6] Tokic:
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?
[Google Pixel 6] Homeboy76:
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
[Google Pixel 6] Tokic:
What do you mean by "Do Not enable everything"?
[Google Pixel 6] Homeboy76:
Checking all the boxes in the

DenyList

.

The DenyList has every app you have on your phone in it and System apps (If you want to see the System Apps. Open the DenyList, tap the 3 dot menu, tap Show

system apps

Check the System, App box).
[Google Pixel 6] takeshishen:
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.
[Google Pixel 6] ne0ns4l4m4nder:
Are you using the latest platform tools?
[Google Pixel 6] V0latyle:
33.0.3 is the latest.

@takeshishen the device must be in bootloader mode, please run fastboot devices and paste the output here
[Google Pixel 6] Lughnasadh:
Try 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?

Also, it seems people have better luck when using an A to C cable with USB 2.0 port.
[Google Pixel 6] V0latyle:
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.
[Google Pixel 6] Lughnasadh:
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.
[Google Pixel 6] takeshishen:
I used this method, but it still doesn't work, I used the c to c interface, the original data cable
[Google Pixel 6] takeshishen:
Here is my step by step method, I'm not sure where is the problem.
[Google Pixel 6] V0latyle:
Strange. Did you have a custom ROM installed before?
[Google Pixel 6] Lughnasadh:
Looks like you are still using PowerShell instead of command prompt. And as suggested, try an A to C cable using USB 2.0 port.
[Google Pixel 6] takeshishen:
这是第一次安装和试用root。之前没有什么很成功。

Haven't installed it before, this is my first time trying with this phone. Unfortunately, the last step didn't go well.
[Google Pixel 6] takeshishen:
I'll try a different cable like that.
[Google Pixel 6] badabing2003:
The system boots normally without root?

While in adb mode,

What do you get when you issue these commands

adb shell ls -la /dev/block/bootdevice/by-name/

adb shell getprop ro.boot.slot_suffix
[Google Pixel 6] V0latyle:
I'm not sure what the problem might be then. From my end it looks like you're doing everything right. The only thing I can think of is make sure you're using the right files and a known good cable, but your root.img size is the same as the boot.img in the factory package so that should be OK. Sorry you're having trouble, hope we are able to help you figure it out.
[Google Pixel 6] takeshishen:
That's it, I took a screenshot.
[Google Pixel 6] takeshishen:
This cable has dealt with other phones before, I don't think it should be the problem, at least I did the previous steps successfully. Where can I download the boot.img file that has been repaired. Maybe I can try it, all I can think of is the problem in this link. Thanks a lot for your answer.
[Google Pixel 6] takeshishen:
This also doesn't work, I can only try to change the A to C cable tomorrow.Thank you very much.
[Google Pixel 6] V0latyle:
The only thing I can say is when you start having trouble, double and triple check everything. Make sure you're using the right tools, the right files, the right process, etc. I can't specifically say what causes that error but I have seen it happen with outdated ADB tools as well as bad/uncooperative USB cables. The response from the target doesn't always make perfect sense given what the problem might be.

I would say go back through the guides and make sure you're doing everything by the letter.
[Google Pixel 6] badabing2003:
This is weird,

The partition is there.

There only thing i would suggest is to move your files to c:\pixel

And try it from there, i don't think it would make a difference, but it is worth a try just in case the path is causing a problem.
[Google Pixel 6] takeshishen:
I used the webpage provided by Google to flash Android 13 several times, and both partitions should be the same. I tried putting the folder under c:\ and the result is still the same.

The only thing I can think of, is it a bug in my boot.img patch, I can't find where I can download it right now.
[Google Pixel 6] badabing2003:
The error is about boot partition not being found, not root.img being bad.

If you wanted you can give PixelFlasher a try, it would eliminate any typo you might have introduced.
[Google Pixel 6] takeshishen:
Forgive my ignorance, I downloaded this. But don't know how to improve this partition problem.
[Google Pixel 6] tom1807:
Sorry, that I jump in,, but first I suggest that you are not using a remote drive like OneDrive.

Second, keep the path short, in theory it all should work in Windows or DOS, but I witnessed too much strange behavior with long filepaths.

My suggestion, create a folder on your C:\ Drive, call it ADB or something else and get all files to there.

Cheers

Tom
[Google Pixel 6] takeshishen:
Thanks for the suggestion, I have put all the files in C:\. But still not working. I think it should be the problem of the phone partition, but I don't know how to solve it.
[Google Pixel 6] tom1807:
Simple question, drivers are installed?

This means when you are in fastboot mode, is the driver for fastboot in your device manager?

Cheers

Tom
[Google Pixel 6] badabing2003:
I posted my answer here to keep this thread clutter free.
[Google Pixel 6] V0latyle:
@tom1807 suggested the same thing. I don't think it's a path thing.

Also, he does have the correct drivers installed, he's able to interface with the device via both ADB and bootloader

@takeshishen what version of Magisk are you using and where did you download it from?
[Google Pixel 6] takeshishen:
25.2 This version I use
[Google Pixel 6] badabing2003:
Process of elimination.

We can try few things.

1- Live boot to the patched image, let's see if that works see the guides in OP, basically you remove the word flash from your command.

This will tell us if your root.img is good or not.

2- Switch slots and try on the inactive slot, but first factory flash that slot like you did this one and then try to flash the boot.img

If that works, then something about the boot partition on the current slot could be the issue.
[Google Pixel 6] V0latyle:
That's good, there shouldn't be a problem with that version, as long as you did download it from the link you gave.

I might have missed it, did he already try flashing the stock boot image? Maybe one of our gurus @pndwal or @ipdev might have some input.
[Google Pixel 6] manjaroid:
I've been wondering about the path too and keep coming back to OneDrive. @takeshishen - Since c:\something made no difference maybe try logging in as a different user with a local account... just to eliminate OneDrive as a possibility once and for all.
[Google Pixel 6] badabing2003:
I'm not sure at this point what is done.
[Google Pixel 6] V0latyle:
OneDrive by default only covers user files - %USER%/Documents, /Pictures, /Videos. To include anything else it must be specially configured, and it cannot AFAIK back up the root of an OS drive.
[Google Pixel 6] takeshishen:
@V0latyle,@badabing2003 Thank you for your help. I just had time to try again. The same path, and cable. Using PixelFlasher is a success.