yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] Mepsipax:
I just tried this, but it doesn't work either.

So my old phone is running Android 10. (I wrote A11 before because I misremembered so I went and edited that.)

I installed Swift Backup, made a local backup of the app "Slack" just to try it.

Pulled the backup under accounts/<hash>/backups/apps/local to my pc.

On new Phone

Installed Swift Backup.

Pushed the backup onto it from my PC in the same folder.

In Swift Backup, went to Slack app. It shows backup a couple minutes ago, so it recognizes the backup.

Then try to restore app + data. Fails with errror.

I then tried to uninstall slack, install slack again via play store, then only restore data. Still fails with error.

This leads me to believe there's some fundamental data incompatibility between A10 and A13.
[Google Pixel 6] V0latyle:
So the app works as long as you don't restore data?
[Google Pixel 6] Mepsipax:
I don't quite understand this question. Yes, regular app installation via play store work. but I want to restore app settings and app data from my old phone onto my new phone. So when I tried with the tb, all restored apps would crash. When I tried it with swift Backup, the restore process inside swift backup would fail with an error. Something about "corrupt data". Since that data is from a swift backup on my old phone though, would think that data restoration between android versions 10 and 13 simply does not work on any app.
[Google Pixel 6] V0latyle:
My question is whether the app works if you don't restore data for that app via TB or Swift Backup - as in, it works fine with clean data?

Sounds like an incompatibility problem. I don't know enough about what changed from Android 10 to 13 to know why this would be the case.
[Google Pixel 6] Mepsipax:
Yes, that's exactly what happens. I kinda gave up on it now tbh.
[Google Pixel 6] S.N.@.K.3:
So I m also new to Pixel 6 and I dont know how many OTA I have taken including this month , currently I m on tq2a.230505.002 Build , I havent unlocked the bootloader yet, if its useless and I m gonna brick my device so its no use, please help me out too.. What I need to do ?

https://xdaforums.com/t/warning-read-this-before-your-initial-upgrade-to-android-13.4482091/
[Google Pixel 6] Lughnasadh:
Read the OP in this thread.
[Google Pixel 6] V0latyle:
The instructions to unlock your device are in the first post of this thread.

Unlocking the bootloader allows you to flash modified or custom images.

The only thing that could brick your device is flashing a modified or corrupted bootloader, so whenever you're flashing bootloader, make absolutely sure it's the correct image.

If you experience a boot loop, make sure you're using the correct boot image for your device. I recommend Magisk 25.2, not newer.
[Google Pixel 6] S.N.@.K.3:
Thanks for replying here...

So long story short...

I need to unlock the bootloader its obvious... And I need a root...

Are these commands are just enough?

adb reboot bootloader

fastboot flashing unlock

Now I have downloaded ota and also factory image what exactly I have to do after unlocking the bootloader.... Patching by masgisk boot.img from factory zip>update.zip to device and pc and then flash?

Now if yes, then what I have to do? And where and why I use the active slots commands?
[Google Pixel 6] S.N.@.K.3:
Need ur guidance here @V0latyle
[Google Pixel 6] V0latyle:
You don't need to mess with the slots, unless the device is on Android 12, in which case you'll want to flash the new bootloader to both slots.

Again, the instructions on updating and rooting your device are in the first post of this thread. Go back and read it, please. If you have questions about something specific, I'll be happy to help, but I took the time to write an exhaustive guide, and I would appreciate it if you used it instead of asking me to give you answers that are already readily available.
[Google Pixel 6] S.N.@.K.3:
Mate @V0latyle I do understand the precious time of urs and also understand u look around the post of xda community and answers them....

Now I m on A13 already took OTA's, so as u said its for Andriod 12 so tht means I only just go ahead start adb commands on my current os13 and flash without any tension...

Also I have read tht u have recommend users to flash directly and easy from Pixel Flasher thread.... Should I do tht?
[Google Pixel 6] d4guser:
Hi, I am wondering whether it is currently possible to unlock (and subsequently root) a Pixel (6a specifically) without wiping the user data?

I'm even interested if there is potentially a way, for instance, even a way that doesn't always work, so long as it's known to work sometimes. Any info much appreciated.
[Google Pixel 6] simplepinoi177:
Short & direct answer is; no. I'm willing to bet on it, but if anyone knows better, feel free to correct.

I'm fairly certain Google makes it that way -- much like Samsung makes their devices to "trip"(there's some debate whether it's a physical "tripping" mechanism or on a system level) when KNOX is tripped....
[Google Pixel 6] d4guser:
Ok, thanks for the quick reply!
[Google Pixel 6] V0latyle:
You should do whatever you are comfortable with.

It is not possible to unlock the bootloader without wiping data. It has nothing to do with Google or Samsung or anyone else; it is Android functioning as intended. The idea here is that a locked bootloader helps make a device "secure", but when the bootloader is unlocked, the device can be compromised, such as root, which would allow access to all user data. So, when you unlock the bootloader, data is wiped as a protective measure. This means that someone can't steal your phone and unlock your bootloader then access your sensitive information.

As for what triggers it, that is built into the bootloader - when the user confirms that they want to unlock the bootloader, it then erases and reformats /data.
[Google Pixel 6] d4guser:
Thank you for the additional details :)
[Google Pixel 6] pa.pn2:
Did anyone already rooted June build with latest magisk Canary?
[Google Pixel 6] deusfaux:
just did, seems fine so far
[Google Pixel 6] Nightf0x_007:
normally updating from may to june like every month via pixelflasher with adb 33.0.3 and keeping data and disabled verity and verification, device wont boot and shows corrupted data message after it finished updating

reflashed may firmware also same message

help please any ideas how can i boot the device ? i dont want to lose my data asi dont have a backup

incase this might be of any help at all i didnt flash both slots + i have a magisk patched boot image of june update on my pc also im using magisk alpha (the patched boot image is by magisk alpha)
[Google Pixel 6] Lughnasadh:
Go over to the Pixel Flasher thread and submit a support zip to @badabing2003 . If it's the red eio corruption message you should still be able to boot by pressing the power button when you get that message.
[Google Pixel 6] Nightf0x_007:
1st option reboot 2nd option reset device data, i reboot it reboots again to this screen
[Google Pixel 6] Lughnasadh:
If you rooted while updating, try flashing the stock boot image.
[Google Pixel 6] Nightf0x_007:
not i didnt root while updating but my device was rooted, i followed the same procedure i follow every monith while updating, i flash firmware without root then i fastboot boot to the patched image then i install magisk from the app
[Google Pixel 6] Lughnasadh:
Having a hard time following exactly what you did. You say you didn't root while updating but then go on to say that you followed the same procedure you use, which includes rooting. Are you currently rooted or not? If so, try flashing the stock boot image.
[Google Pixel 6] Nightf0x_007:
my guide is flashing the update, no it doesnt include root, after i boot the device after updating i fastboot boot to a magisk patched boot image i created before flashing the update (i extract it from the update zip and keep it), then from magisk i install magisk again now root is permament thats what i do every month

can you magisk patch and upload for me the may firmware boot image (if you can, TIA)? here is the stock may image
[Google Pixel 6] Lughnasadh:
But I'm asking if you are currently rooted or were you not able to get that far?
[Google Pixel 6] Nightf0x_007:
here my steps

downlaod the update full image firmware

extract the boot image and patch it via magisk and keep it

update via pxielflasher keeing data and disabling verity and verification

now device updated without root

i fastboot boot to the magisk patchec image created earlier

now device is udpated and with temp root , i reinstall magisk from inside the magisk app

done

(i know its a long prcoedure but thats what im doing for along time now and it works)
[Google Pixel 6] Nightf0x_007:
currently my device when booted it boot to the android recovery page, when try again rebooting it gets back to this page, i fastbooted boot to the may stock image it gets back to this page also so i need a may boot image magisk patched to try to boot up, unfortuanetly i deleted the may patched image i have
[Google Pixel 6] V0latyle:
Why are you disabling DM-verity and vbmeta verification? You aren't using a custom kernel, there's no reason to do so.

If the unpatched boot image won't boot either, your problem is not with the boot image.
[Google Pixel 6] Nightf0x_007:
No im using kirisekura kernel
[Google Pixel 6] Nightf0x_007:
Idk will give it a try
[Google Pixel 6] V0latyle:
Sorry, your posts weren't that clear.

You already tried booting with the stock boot image?
[Google Pixel 6] Nightf0x_007:
Yes, it goes to android recovery page cant load android system ..., Idk what to do actually i just want to boot the phone and backup some of my data then i have no problem in resetting the device
[Google Pixel 6] V0latyle:
Ah, it's going into Rescue Party. Sounds like there might be some vbmeta/verity corruption to me. We had this issue when Android 12 first came out; before Magisk was fixed, it did not properly handle the boot image header.

What version of Magisk are you using?
[Google Pixel 6] Nightf0x_007:
Magisk alpha, i was updating from may to june, yes i remember this issues from before, i have no problem in screwing things up just to boot to system then backup somethings then resetting phone from scratch
[Google Pixel 6] V0latyle:
Still, because none of the boot images are working, I think we are dealing with another issue here. I hate to say it but you may have to wipe data.

When we had to manually disable dm-verity and vbmeta verification for previous versions of Magisk to work, we discovered that if we flashed /boot withou those flags at any point, we would get the same screen, and the only way to get past it was a data wipe.

Unfortunately since TWRP is not available for this device, your data may be toast.

There's one last hail mary you can try: Are you able to boot into recovery? If so, sideload the latest OTA.
[Google Pixel 6] badabing2003:
I checked the logs, even OTA did not work (but verity / verification was still being disabled)

Two last suggestions before the wipe route was provided here.

Hope not disabling verity / verification would work and he can backup the data.
[Google Pixel 6] pa.pn2:
I'm still on April's build rooted, shall we better wait before updating to June build?

The member up in the post had problems while updating
[Google Pixel 6] V0latyle:
If you're on the stock ROM with the stock kernel, you should be fine. I'm not completely sure where he went wrong but if you follow the same update process you have been using you shouldn't have any problems.
[Google Pixel 6] pa.pn2:
I successfully updated to June build without any hassle
[Google Pixel 6] S.N.@.K.3:
@V0latyle help needed, currently I m on Android 13 with unlocked bootloader and rooted, I have opt-in for Android beta, I have now A14 update, so the question is should I uninstall all module from magisk and then uninstall magisk and then install update ota and then reinstall magiska and reboot? or should I start from the beginning like flashing via adb and then root?
[Google Pixel 6] V0latyle:
You'll want to treat this like a OTA update with root, the only exception being that you'll want to update to Magisk 26.1 for Android 14, and although you don't need to uninstall the modules, it may be a good idea to disable them temporarily if you're using any customizations. I am only using the Systemless Hosts module and the USNF MOD 1.2, and I didn't have any trouble updating to the 14 beta.

If you're getting the notification to update to the beta, just follow the Update and Root Automatic OTA section with the caveats I listed above.
[Google Pixel 6] S.N.@.K.3:
@V0latyle thanks I have updated and installed magisk but didn't open the app .. When phone restarted and open the magisk app it asking me to patch the file 🥴 ..
[Google Pixel 6] V0latyle:
Yep, you gotta update Magisk Core too
[Google Pixel 6] S.N.@.K.3:
@V0latyle sorry for asking if it's noob, should download the factory or ota.zip and then extract A14 boot .img ? And then apply for patch?
[Google Pixel 6] V0latyle:
Either way works, if you use Pixel Flasher it will extract the boot image from either, and it can automatically patch the boot image for root.
[Google Pixel 6] pa.pn2:
Did someone patch June build with latest magisk Canary 26.103?
[Google Pixel 6] V0latyle:
Might be better to ask that question in the Pixel Flasher thread
[Google Pixel 6] badabing2003:
I did it on Pixel 5 to test and it worked,

But I have read reports of issues with 26103
[Google Pixel 6] Mahoro.san:
I screwed up the OTA update where now I have updated the OTA but the Magisk Root is missing.

I have tried to reload the root by flashing the patched boot.img in the fastboot.

However the phone is not recognized in the fastboot; there's no device showing while I type Fastboot Devices when it is in the fastboot mode.

I have tried updating the driver when the phone is on and in normal mode.

[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3

I have been using Minimal ADB and Fastboot with no issue.

but when the Phone is in fastboot mode, I can't find the device in the Device Manager; it is however recognize in the ADB mode whether it is in operation mode or recovery mode.

I have also tried Driver Signature Enforcement under Startup (7 of Startup menu), that doesn't bring up the devices in the fastboot mode either.

anyone has any idea what to do next
[Google Pixel 6] Lughnasadh:
I would suggest using Platform Tools 33.0.3 (don't use 34+) instead of Minimal ADB (link is for the Windows version).

Would also make sure your USB drivers are up-to-date.

If still not working, try different cables and ports. An A to C cable using USB 2.0 port seems to work well for most.
[Google Pixel 6] Mahoro.san:
Yes I have followed above two steps, using latest driver plus the platform tool to no avail

I have updated the driver when the phone is in recovery mode and bring this back to fastboot mode via "adb boot bootloader" which will bring the phone to fastboot mode.

With the same setup, when I typed "fastboot devices" it showed nothing.....

Thank you for the suggestion however.

I think I will do a factory reset and see if that helps.....

Or is there anyway to root without using fastboot such as adb/recovery mode?
[Google Pixel 6] V0latyle:
The device uses the a generic ADB driver while in system and recovery. When it's in bootloader mode, it uses a device specific fastboot driver. These two are distinctly different.

Factory reset won't help you. You don't have the correct driver installed. There is no way to root via ADB, you need to be able to either flash custom images or live boot them, which can only be done via bootloader.
[Google Pixel 6] badabing2003:
Not detecting as an unknown device in Device Manager is a concern, which would make it unlikely that it is a driver issue.

If it were a driver issue, the system should be able to detect that a device was connected, but not be able to properly communicate with it (It should show up in Device Manager)

Make sure that you select Show Hidden Devices in Device Manager to be certain that the device is not hidden.

I'd flash (sideload) full OTA to assure that the bootloader is in good state , then make sure you remove from system path any traces of any Platform Tools.

Then only use 33.0.3
[Google Pixel 6] V0latyle:
The device must be in bootloader mode. If it's in system or recovery, it'll show up as an ADB device. I think he is either confused or not following instructions and doesn't have the Pixel USB driver installed (necessary for bootloader interface)
[Google Pixel 6] badabing2003:
Absolutely right, I'm just going with what he said, where he indicated that the device is not listed in Device Manager when it is in bootloader mode, which it should no matter what even with no drivers or bad drivers, of course with no drivers or bad drivers fastboot devices will not show anything, but the phone should show up in device manager with some warning symbol or seen as unknown device no?
[Google Pixel 6] Mahoro.san:
You guys are right, I have pulled out my old p

Laptop and give it a go, it recognize the phone in fastboot the first try.

Thanks guys for the help
[Google Pixel 6] V0latyle:
It should, yes. My initial impression was that he was trying it in system or recovery, not bootloader.
[Google Pixel 6] lackalil:
Quick questions: I'm still on the March update and was waiting for the final update on A13. I've been out of the loop with Android news lately because I'm happy with what I'm running now. Usually only update a couple of times a year and tend to stay on the final version for a good while. Sick of playing the cat-and-mouse game with SafetyNet/whatever the new API is. BUT, I just got a notification that the latest update is ready to install and I just need to restart. Automatic updates is off under developer options and I've never seen that message before.

Will it update if I restart using the power menu or dead battery (as opposed to the "restart now" in system updates)?

If so, is there any way to stop that? I was under the impression that OTAs wouldn't work once rooted with Magisk anyway but you never know.

I'll read through the last couple of months of this thread when i get a chance, but is there anything I can do in advance to help get me rooted and up and running if I do get an update forced? My standard process would be to get latest ADB drivers, Magisk and SafetyNet fix but I feel like there's always some new garbage that needs to be worked around to get GPay and Hide/DenyList working.
[Google Pixel 6] V0latyle:
I don't think anyone's really found a definite solution to this. It seems that once you're so far out of date, it'll update you anyway, although I'm not sure whether it's a full update or just something related to Play Services or security. Post your current build number, restart, and see if it changes. If you update you'll still be able to root so there's no issue there.
[Google Pixel 6] lackalil:
Thanks. Restarted and nothing happened...but it did it reboot quicker than usual. Still on TQ2A.230305.008.E1. I remember accidentally clicking "update now" on a Pixel a long time ago (not sure if it was this P6 or a P3a) and it did the same thing. Super quick restart and no changes.

The update notifications have been blocked since day one but I still sometimes get them. This was probably something screwy to do with that.
[Google Pixel 6] V0latyle:
So it didn't really update and you still have root?
[Google Pixel 6] lackalil:
Yep, as far as I can tell it did nothing when I used the power menu. Build number is the same. Root and SafteyNet are still working. It may have done something with Play Services like you suggested but I doubt it because it booted so quickly. Not sure what would happen if I hit the restart button on the system update tab. I seem to recall that it used to have a "download update" button but it only shows "restart now." That would suggest it was downloaded in the background.
[Google Pixel 6] V0latyle:
Correct. So, what you would do now is go to Magisk > Install > Install to inactive slot, and let it reboot.
[Google Pixel 6] Mepsipax:
Hey guys, quick question regarding this:

So apparently, I had automatic updates enabled which led to my phone downloading the OTA without asking.

So the problem is now that I have step 2 before having done step 1. Is it still going to work to just do step 1 now and then 3 and 4 after that or am I boned?
[Google Pixel 6] badabing2003:
If you haven't rebooted yet, just do Steps 3 and 4

Typically without step 1, Google does allow the installation of the update, that is why step 1 is needed, but in your case if it managed to download and install it, and is telling to reboot to apply, then you're past that stage.

It's been reported that Google can push an update regardless of your settings and mods if it wants to.

Typically it doesn't.
[Google Pixel 6] Mepsipax:
Alright people forget about all that. Apparently Google decides when phones do their updates, so mine just rebooted and updated itself because I think a dialog appeared randomly that I accidentally accepted without even being able to read it because I was using my phone and making touch inputs.

Thanks Google!

I lost root now. What's my best approach to get it back?
[Google Pixel 6] V0latyle:
Patch and flash the boot image

Pixel Flasher makes this a helluva lot easier
[Google Pixel 6] Mepsipax:
I still have the master root.img from my initial root. Can I reuse that or is it outdated now?

If I understand correctly I can just reuse that i.e. fastboot flash it and I'm done?
[Google Pixel 6] V0latyle:
No. You can live boot it for temp root so you can use Magisk to install root, but do not flash an older boot image on a newer system
[Google Pixel 6] Mepsipax:
ugh dammit. Guess I'll try PixelFlasher. Thanks!
[Google Pixel 6] V0latyle:
Do you not know how to live boot?

When you use fastboot flash boot boot.img you're telling fastboot to flash the boot partition with boot.img.

But you can tell the device to load the image into memory and execute it without flashing it, which is useful for temporary root or testing:

fastboot boot boot.img

This is the syntax:

fastboot is the application you are using for the command

flash or boot (or others) is the instruction you are giving the above application

Everything after is the additional instructions and criteria for the command. If you just type fastboot it will tell you what commands and switches are available.

For example, fastboot flash boot boot.img --slot=all --disable-verity --disable-verification works like this:

You're telling fastboot that you want to flash the /boot partition with the image named "boot.img", and you want it to flash all available slots for that partition - in our case, /boot_a and /boot_b. You're also telling it that you want to disable dm-verity so it won't check the hash of the image while booting, and you're also telling it to disable vbmeta verification.

Does that make sense?

I'm probably going to remove the instruction for maintaining the "master boot image" because of the potential problems. The idea here is that older boot images will typically boot just fine on updated system, so you're telling the phone to load the old boot image into memory instead of the new one that's been flashed to /boot with the update. You could then use Direct Install in Magisk to patch the images in /boot.

It only works on a temporary basis, so the next time the phone reboots it's going to default to normal operation and attempt to load whatever is in the /boot partition.
[Google Pixel 6] Mepsipax:
Okay, i may have misunderstood. Are you saying I can just

1. Live boot into my old master root.img

2. Open magisk.

3. "Install"

4. Reboot regularly

And I should be back to my permanent root?

I was under the impression, I have to create root img from scratch and all that.