yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] kornball:
Are you aware of any downside to running the update command fastboot update --skip-reboot --disable-verity --disable-verification image-xxxxxx-xxxxxxxx.zip and then flashing the patched boot.img before booting back into android? I previously disabled both verity and verification in the android version that originally came with the phone.
[Google Pixel 6 Pro] swieder711:
The test version from yesterday did not show the Canary channel as an option for updates.

The new version from today, 23016, has Canary as a channel.

I uninstalled the Magisk APK and installed the new one from GitHub.

"Hide the Magisk App" is also no longer greyed out.
[Google Pixel 6 Pro] V0latyle:
Disabling verity and verification isn't necessary as of Magisk Canary 23016.

Other than that, there's no downside to flashing the patched boot image before booting to Android.

Technically, flashing the patched boot image shouldn't even be necessary. This is how I update my P5:

Update bootloader, radio, then system

Boot the "old" patched boot image

Make sure system boots with root; use Direct Install in Magisk to patch the new boot image.
[Google Pixel 6 Pro] bradhoschar:
Couldn't get root, so figured I'd start all over.

1. Used Android Flash tool to flash SQ1D.211205.016.A1, disabled verity and verification, did not wipe.

2. Installed app-debug.apk (Canary 23016), patched boot img, and flashed boot image.

3. Opened the magisk app, and another root program was granted superuser, but got toast notification saying magisk was denied superuser rights.

4. Settings within Magisk are minimal, but I have root?

Coming from a OnePlus 8 pro, haven't dealt with Pixels in a while, so if someone could dumb it down for me, that'd be great!
[Google Pixel 6 Pro] MArtyChubbs:
Oh no worries at all. I didn't mean it like that I was just trying to be marginally helpful. Sorry brother
[Google Pixel 6 Pro] rester555:
I updated based on these steps. Thanks @V0latyle. It shouldn't be a problem flashing vbmeta after the fact right?
[Google Pixel 6 Pro] V0latyle:
I think you misunderstood me - we don't need to mess with vbmeta at all anymore.

Disabling verity and verification is no longer necessary.

Magisk itself is the root manager, the notification you saw was Magisk denying another app root. Simply launch Magisk, tap the Superuser button at the bottom (shield icon), and you can review root permissions for apps.
[Google Pixel 6 Pro] bradhoschar:
If you look at screenshot, the shield icon is greyed out. And the other app (LiveBoot) was GRANTED superuser rights.
[Google Pixel 6 Pro] V0latyle:
See up at the top where it says "Installed: N/A"?

That means you don't have root.

Reboot to bootloader, then boot your patched boot image. If it works, use Direct Install in Magisk.

If that doesn't work, and if you still have your November patched image, try to boot that. If you have root, then perform Direct Install in Magisk.
[Google Pixel 6 Pro] bradhoschar:
But I do have root....

I don't have November, and the comments are saying not to downgrade.
[Google Pixel 6 Pro] rester555:
@V0latyle Currently vbmeta verity and verification flags are disabled for me... Don't I have to reenable by flashing vbmeta without the disable flags?
[Google Pixel 6 Pro] V0latyle:
No. Just don't worry about it anymore. If you're up and running, don't mess with anything. Next time you update, just update normally without disabling anything.
[Google Pixel 6 Pro] rester555:
Makes sense. thanks.
[Google Pixel 6 Pro] V0latyle:
According to Magisk, you don't - or at least Magisk can't interface with root.

You can try re-patching and reflashing the patched image; make sure you're using the right one.

Failing that, you can try uninstalling and reinstalling Magisk, although this probably won't fix it.

Ultimately, there's no way to recover a Magisk installation without root, except for wiping data and starting over.
[Google Pixel 6 Pro] bradhoschar:
I've tried patching since yesterday. Guess I'll clean flash Nov, then update to Dec and try again.
[Google Pixel 6 Pro] V0latyle:
Why not just clean flash December?
[Google Pixel 6 Pro] bradhoschar:
I guess I can.
[Google Pixel 6 Pro] V0latyle:
I just figure there's no reason to take extra steps if it's not necessary. Time is money.
[Tilt, TyTN II, MDA Vario III General] yokozuna82:
I just traded my moto q global smartphone for a tilt and I love it however there is one thing that I can't get to work properly and that is my blue tooth headset I bought a Jawbone 2 an expensive device but it sounds all muffeled and and the sound breaks up I was wondering dose any one have a tweaks or tricks to make it sound the way its suppose to.
[Google Pixel 6] Morgrain:
There is some talk in the P6 race to brick Telegram group, it seems that the december update is causing root to fail.

So until this is fixed/solved, DO NOT UPDATE IF YOU WANT TO RETAIN ROOT.

View attachment 5481629

View attachment 5481631
[Google Pixel 6] ne0ns4l4m4nder:
Oh no topjohnwu you didnt
[Google Pixel 6] Morgrain:
He is working for the enemy now, was only a matter of time for problems to arise since he already stopped supporting MagiskHide at the behest of Google^^

Maybe Magisk just needs an update, maybe we have a bigger problem, we'll see
[Google Pixel 6] MArtyChubbs:
Nah, he'll find root or another Magisk developer will.
[Google Pixel 6] pa.pn2:
Cant we flash a patched stock boot image after the problem is solved?
[Google Pixel 6] bb709394:
As OP stated, do not update to December if you want to keep root. I did before I checked forums and lost root. Rolling back to November to hopefully regain access to root. :cry:
[Google Pixel 6] pa.pn2:
Please report back if its possible to roll back
[Google Pixel 6] sada23:
I don't see any update when I check for update on my Pixel 6.

Do I need to something to get the update? I ma not rooted and hence do not worry about rooting.
[Google Pixel 6] cd993:
Tread carefully, someone tried dirty flashing which then required a clean flash.
[Google Pixel 6] bb709394:
Yup, dirty flashed failed and requiring a clean flash. Good learning experience and lesson for me, don't jump the gun with the newest updates.

Assumptions made when I flashed December update on 4A 5G without any problems... c'est la vie.
[Google Pixel 6] cd993:
Yeah I would have held off rooting, as whilst sideloading the OTA I read that root wasn't working... oh well, a fix will come soon I'm sure
[Google Pixel 6] Lainey52900:
i didnt read this forum before flashing, now im stuck on a screen with the google logo and a loading bar. is my phone ****ed?
[Google Pixel 6] Vio281:
does anyone get corrupted data and stuck on google logo? any help?
[Google Pixel 6] XNine:
You'll likely have to use the Google reset to factory process to ever use the phone again. I haven't rooted my Pixel 6 yet, though, so I can't confirm. But that's how I fixed a bad Pixel 5 update.
[Google Pixel 6] Vio281:
what google reset?
[Google Pixel 6] XNine:
Google Pixel - Update and Software Repair

Need a USB cable and Chrome (I think, never used a different browser for it).

Again, I can't confirm this works but it's just an educated guess
[Google Pixel 6] Vio281:
just try it, only work up to google 5
[Google Pixel 6] Lainey52900:
Okay, so for anyone else here who tries to root using the December patch and gets stuck on the Google logo screen, here are the steps I took to fix it:

1. Hold down the power button until the phone turns off

2. Enter fastboot via holding down the power button and volume down

3. Attach a usb cable to a computer, download the factory image zip, then extract it

4. Once extracted, double click on "flash-all.bat," this will reflash every single component of the image to your phone and once it's done, will reboot and should boot as if nothing ever happened.
[Google Pixel 6] Vio281:
i got a corrupted image and still stuck on google logo.
[Google Pixel 6] Vio281:
for anyone running into the same situation i did, I have to use the flash option on the google firmware page to get my phone working again, Thank god...
[Google Pixel 6] wardii360:
So is the issue rooting the December update, or flashing the update while rooted?
[Google Pixel 6] dilruk:
Were you able to retain root and all the data?
[Google Pixel 6] Rumsfield:
I dirty flashed today and was already rooted. All that happened was I am on the current firmware now and Magisk always shows not installed. Flashing the magisk_patched.img seems like its working as normal but once you finish and fastboot reboot, the phone boots up with Magisk saying its not installed. Some people are getting boot loops or soft bricking and whatnot, but for me everything looks normal its just Magisk doesn't work. (no loops or errors).
[Google Pixel 6] Rumsfield:
Lainey mentioned flash-all.bat, that will wipe the phone clean AFIAK.
[Google Pixel 6] capntrips:
looks like a fix may have already been found
[Google Pixel 6] dilruk:
Wow. is there a updated magisk app?
[Google Pixel 6] Rumsfield:
A request was pulled on the github page with a possible solution, that just means the dev *may* take a look and put out a new update if he has the time.
[Google Pixel 6] dilruk:
Ya, got it. I guess I got too excited
[Google Pixel 6] paratox:
Load fstab from system/etc · topjohnwu/Magisk@ecea07b

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

install app-release.apk from this zip and patch and flash again. it is working.
[Google Pixel 6] Project_WHaT:
In the System update page of the settings, my phone says 'Installation paused' and that it will 'continue when the device isn't being used'. I was about to go to bed, but I'm now worried that it'll update while I sleep and therefore lose all my data. Is it going to update and restart by itself or do I not need to worry?
[Google Pixel 6] matze19999:
This worked, thank you!
[Google Pixel 6] dilruk:
Can't find a zip :rolleyes:

EDIT: Figured I need to be logged in to GitHub to get the link
[Google Pixel 6] dilruk:
Hope you retained root and all data as mentioned in OP?
[Google Pixel 6] paratox:
if you did the update like in the past with "fastboot update --disable-verity --disable-verification image ..." data wipe should not be a problem. if you never did --disable-verity --disable-verification before your data will be lost.
[Google Pixel 6] dilruk:
Thanks I have already disabled those. Will try and confirm
[Google Pixel 6] Niñdo_:
I am getting stuck in a bootloop after flashing the new patched boot.img. Should I flash stock boot and try again?
[Google Pixel 6] wardii360:
Can you please explain how to obtain the apk? I've grabbed the zip
[Google Pixel 6] mermozito:
hello

my pixel is rooted, with disable verity and verification options, on the november update (.037 version). What shoul i do to have the december update, rooted and without losing my data, please ? i ve downloaded the app-release.apk, but i can't install it, because magisk 23015 is allready installed.Should i uninstall magisk and install this app-release.apk to patch the boot.img ? and after...?...
[Google Pixel 6] sean222:
Thanks! Rooted again :)
[Google Pixel 6] Homeboy76:
Workaround, see @Nezorflame post #43
[Google Pixel 6] Nezorflame:
The actual fix is already merged in Magisk repo (as mentioned in this post): https://github.com/topjohnwu/Magisk/pull/5059

All we need to do now is wait for the new Canary release, or install the debug version as mentioned a few posts earlier (although I'd wait for the release).
[Google Pixel 6] Nezorflame:
That's just a pull request with the fix in the Magisk's Github repo.

This is not really an "alpha" per se - Magisk repo has automatic build scripts which run new builds on every commit.

So you can go to Magisk's Github actions page yourself, find an action compiled against

master branch (e.g. this one), and download the file in the Artifacts section.

It's going to be a ZIP archive which contains app-debug, app-release and stub APKs - use the debug one and install it, then patch the boot image as usual.

This will help you to get rooted right now. After that you might need to reflash USNF module to get SafetyNet working again (at least I had to, wasn't able to pass SafetyNet before that).

Still, this is a temporary solution since it's not tested yet, so waiting for a new Canary might be a safer bet.
[Google Pixel 6] nummer:
Load fstab from system/etc · topjohnwu/Magisk@ecea07b

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

i downloded this build and now root is working just fine :p
[Google Pixel 6] badabing2003:
Sorry for the ignorant question, what is USNF module?
[Google Pixel 6] nummer:
the universal safetynet fix

GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com
[Google Pixel 6] Chezbel:
In case someone didn't already see this there is now a Magisk canary fix. The build number is 23016. It solved the problem for me. After installing that new version of Magisk, I repatched the Dec boot.img and flashed the magisk_patched-23016_xxx.img and I had root again.
[Google Pixel 6] ibrahim52:
That's true. What I did is clear data and cache for magisks before uninstalling then installing the latest canary version which is usually apk-debug.apk.

GitHub - topjohnwu/Magisk at 0c1f68816e9eb02fe35e4c36221c77d4d87ab33e

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Google Pixel 6] naed3r:
An update was just released I believe (at least for me) I'm going to check when I get home from work in ab an hour to see if it fixes it.
[Google Pixel 6] naed3r:
Load fstab from system/etc by yujincheng08 · Pull Request #5059 · topjohnwu/Magisk

Caused by this commit: https://cs.android.com/android/_/android/platform/system/core/+/e98afa2687eb56184dad8569b929eba04fb93068 Fix #5057, Fix #5058

github.com

seems this PR fixed it. Hoping for the best (when I get home)
[Google Pixel 6] rwilco12:
I did it with the update earlier this morning and root is working great!
[Google Pixel 6] V0latyle:
Magisk Canary 23016 incorporates the Pixel 6 / Pro December fix, as well as the AVB header fix. Disabling verity/verification is no longer required and makes no difference now.

For those of you using the alpha developed specifically for P6: you will need to uninstall Magisk before installing 23016.

Everyone else, just update from within the app.
[Google Pixel 6] jd1639:
Next time edit the flash-all.bat to remove the -w and it won’t erase your entire device.
[OnePlus Nord CE 5G] sam_htc_touch:
Hi,

Sequence of steps:

1. Extracted the boot.img from payload.bin and flashed it to the phone. At this point I was able to get into Fastboot

2. While in Fastboot I went into advanced and wiped the "System Settings", and that's when the trouble started - now the phone is stuck into a boot loop forever, I do however get the options to "Power Off" and "Restart"

3. But none of the options above in Step 2 is able to bring me back to Fastboot (and hence into fastbootd either)

Question: How can I get the phone into Fastboot Mode - have tried MSM Tool v4 as well, but that doesn't even recognize the phone
[OnePlus Nord CE 5G] sam_htc_touch:
Edit - This seems to have been resolved now, think I had to press Vol Down + Power instead of Vol Up + Power

Was able to enter into Fastbootd as well, will try to proceed with unbricking the phone with a fresh mind tomorrow
[OnePlus Nord CE 5G] VoltaGe86:
FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.

I assume running this command the phone doesn't actually flash the boot image but could be wrong
[OnePlus Nord CE 5G] Sony make.believe:
Thats right, "fastboot boot <file_name>" loads temporarily your custom recovery of choice. After rebooting your phone, the custome recovery is gone.

Otherwise, the command "fastboot flash <file_name> recovery" flashs permamently your custom recovery of choice to your device.
[OnePlus Nord CE 5G] Zekedw:
Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice
[OnePlus Nord CE 5G] extranoob:
I have exactly the same issue, on a nord 2
[OnePlus Nord CE 5G] !PdK:
How about vol+/vol-&power all together? When stuck that gives me some screen that allows start, recovery (the one where you can enter advanced settings I expect from your description) and bootloader booting.
[General Questions and Answers] xAxB:
Is there anyway, -not- to have my contact list pull from my Google account the second I add a Google account into my phone?

I have disabled automatically sync data, yet Google still deem it necessary to push my contact from their servers into my second phone where I do -not- want any entire contact.

I remember that on my Galaxy S7, I ended up getting around the issue by simply deleting the contacts I did not want on my phone (probably by disabling sync first).

But on my Pixel, which replaces the S7, I am getting a warning that doing so will remove the contacts on all my other devices despite the fact that I have also disabled auto-sync.

Worse come to worse, I suppose that I could just use a different account on my second phone and avoid adding the account on my primary phone, but I would prefer not to that if only because I would like to be able to access my paid apps (yes, I could also login and out of my primary account as necessary, but I'd prefer a set and forget solution if there is one).

Thanks.
[General Questions and Answers] blackhawk:
I just make backup copies, then import the latest one.
[General Questions and Answers] nazhai:
Hi, you can also use android contacts manager tool to help you make backup of contacts on your android phone to the computer, and you can also manage (edit, delete, etc) them before you take backup. The tool my suggest is Coolmuster Android Assistant. With its help, contacts manager is really easy.
[General Questions and Answers] blackhawk:
With Samsung phones there is already a robust contact manager, no Gookill needed.

Contacts app>manage contacts

View attachment 5482697
[General Questions and Answers] Aserar:
I'm giving away my old tablet that has custom rom and TWRP recovery and I was wondering if there's a possibility of restoring my files after performing format date? And if format date also remove my device account and password?

Thanks in advance
[General Questions and Answers] DragonPitbull:
After formating data has a little probability to rescue files. You can wipe to factory reset also if have doubts. Start tablet and not settings. The "new" user is save with not password.

Look in the internal storage if have any file.

For more confirmation you can make same process about Wipes again to repass new data files to old. It's overlap the informations into files for u not have any doubt.

Good luck
[Android Head-Units] snowmaus:
Dear sirs,

I have recently bought an Allwinner cp600p Carplay Ai Box, horrible! too much lagg while playing youtube videos or mirroring from android phone.

I have tried EVERY setting possible (spend HOURS and HOURS and H O U R E S searching the web and my phone), installed a dozen of mirror apps etc etc.. but the video/mirroring still keeps a little stutter/lag.

The allwinner box is on its way back to China.

Now the question, is there a Carplay Ai box that has NO lag casting/mirroring/playing youtube videos ?

My setup

- Mercedes E class 2020

- Samsung Android phone, i tried 2.4ghz and 5 ghz

- Car has both android auto and Carplay installed form stock

Is there a box that use a WIRED usb connection to the phone (i think this will reduce the lag) ?

Or is there a Carplay Ai Box that has NO lag ?

Kindest regards!

Snowmaus
[Android Head-Units] marchnz:
They are all junk
[Android Head-Units] teddyddet:
We have a product, AI box with Qualcomm Snapdragon SDM450 4GB + 64 GB

Do you wanna give it a try?
[Android Head-Units] snowmaus:
If you dont mind sending me one, for testing, ofcourse i would try :)

Is there another way to mirror/watch youtube thats better?
[Touch Pro, Fuze General] hvwtp:
Whenever I disconnect my HTC from the pc TT7 starts. This happens only in disk drive mode and not in activesync mode. Does anybody know how to prevent this?
[Touch Pro, Fuze General] le_cactus:
Rename (or (re-) move) the 2577 folder from the root of your storage card.

Cheers,

Cacti
[Touch Pro, Fuze General] hvwtp:
Yep! That's it. Thnx! :)
[Google Pixel 6 Pro] Morgrain:
There is some talk in the P6 race to brick Telegram group, it seems that the december update is causing root to fail.

So until this is fixed/solved, DO NOT UPDATE IF YOU WANT TO RETAIN ROOT.
[Google Pixel 6 Pro] Dave Lister:
Has anyone been able to revert to the November update and get root back?
[Google Pixel 6 Pro] Niñdo_:
Wish I saw this 12 minutes earlier xD
[Google Pixel 6 Pro] Nekromantik:
maybe magisk needs to update
[Google Pixel 6 Pro] Dataman100:
Don't try to install the Nov image. Someone in another thread tried and ended up having to Factory Reset their phone. I guess us "pioneers" will have to wait until they fix Magisk. Lol!
[Google Pixel 6 Pro] Nekromantik:
those who lost root did you have latest magisk canary? one made for Android 12L?
[Google Pixel 6 Pro] Quinny899:
Yes.
[Google Pixel 6 Pro] MrSteelX:
Did you all remember to flash vbmeta with the disabled command before booting after installing update
[Google Pixel 6 Pro] cd993:
Yup
[Google Pixel 6 Pro] eg1122:
same experience here, got my mod ready too but no way to test it...just going to have to wait
[Google Pixel 6 Pro] Dave Lister:
Luckily I checked here before updating. Figured it wouldn't hurt to ask it anyone tried.
[Google Pixel 6 Pro] DanielF50:
I had the same stupid idea & got stuck in a bootloop.

I was able to resolve this without having to do a factory reset though... downloaded & flashed November build again with the usual flags in "flash-all.bat" (fastboot --disable-verity --disable-verification update image-raven-sd1a.210817.037.zip), attempted a reboot but same issue, so flashed the December build over the top (with fastboot --disable-verity --disable-verification update image-raven-sq1d.211205.016.a4.zip --skip-reboot), then flashed the magisk boot image (unsure if this helped) & rebooted to a working device with all my data still intact.

May have been a dumb move, but at least I didn't have to factory reset 😂
[Google Pixel 6 Pro] neejay01:
Thanks for the heads-up.
[Google Pixel 6 Pro] LLStarks:
Gotta always be ready to wipe userdata. Use Google backups and first-boot cloud restores for everything.
[Xiaomi Mi 11 Ultra] hassanaliyeh:
Hi Everyone,

Just the heads up, RKAMIXM 12.5.8 is available now. Woke up 2 hours ago with an available update by OTA.

Photos attached.
[Xiaomi Mi 11 Ultra] munky-head:
I wonder, will this version auto-upgrade to MIUI13 later this month?

Also - I assume it's storage-problems-free, like the ones plaguing the Android12 releases?

I'm honestly grinding my teeth over the A12 issues and finding workarounds, and I'll revert in a hearbeat if I knew that I won't have to start from scratch in a couple of weeks from now.
[Xiaomi Mi 11 Ultra] hassanaliyeh:
This one is stable global version, I don't think we will have A12 on global before Feb or march
[Xiaomi Mi 11 Ultra] munky-head:
If I'm not mistaken, a December 28th release date was confirmed already, for the Global MIUI13 A12-based ROM.
[Xiaomi Mi 11 Ultra] hassanaliyeh:
I haven't seen that anywhere, and I doubt it. Doesn't mean I would LOVE THIS to be true 😅