yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Guides, News, & Discussion] AquilaDroid:
Yes, I've been on 23016 throughout all this.

Went directly from Android 11 (updated Oct) and didn't wipe data. I did this: fastboot update "C:\Platform Tools January\image-redfin-sq1a.220105.002.zip"

instead of flash-all.bat (with -w removed). Would it be worth a try the flash-all.bat route? It has updated to A12, just can't get Magisk installed

In the previous attempt:

C:\Platform Tools January>fastboot boot "C:\Platform Tools January\magisk_patched-23016_wnekP.img"

Sending 'boot.img' (98304 KB) OKAY [ 2.261s]

Booting (bootloader) boot.img missing cmdline or OS version

OKAY [ 1.529s]

Finished. Total time: 3.931s

what is the message "boot.img missing cmdline or OS version"?

Am I correct that "fastboot boot" is a "one time thing" (that after a reboot it will revert back to the previous state? (So I ultimately need to "fastboot FLASH boot..."?)

No TWRP involved (wish it was available?).

As Pogo used to say: "The older I get the confused(er) I get"...

Thanks for being here to all of you!
[Google Pixel 5 Guides, News, & Discussion] elong7681:
That is correct if you reboot you will lose root but you should boot it first and then direct install it through the Magisk app.
[Google Pixel 5 Guides, News, & Discussion] AquilaDroid:
Thanks, @elong7681

I just tried:

fastboot boot "C:\Platform Tools January\magisk_patched-23016_r8SwK.img"

Sending 'boot.img' (98304 KB) OKAY [ 2.268s]

Booting (bootloader) boot.img missing cmdline or OS version"

again, it failed, restarted and reboots into Android Recovery with "Cannot load Android System" with two options - try again and Factory Data Reset

When I select "try again" it boots back to Android 12 without Magisk. I assume that if it was able to boot into the patched image I'd see the option to uninstall Magisk? I've never seen an option to install through the app. The only option when clicking on install for Magisk (not the "App") is "Select and Patch a file (which I've done several times!). As I've said before, it shows "Installed N/A, Sygisk No, Ramdisk Yes.

Edit: (And thanks @V0latyle, I missed your post when the thread went to this page!)
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
TBH I'm scratching my head here, I have no idea what's causing the problem for you.

I think you need to just start over with the factory image. Don't wipe, it shouldn't be necessary. Dirty flash the factory image, then make sure it boots. Once it does, reboot to bootloader and attempt to boot the patched image. Use the latest update.

If it still doesn't work, manually reflash vbmeta to both slots.

If THAT doesn't work, it's probably time to wipe data...but for a truly fresh start, I recommend using the Android Flash Tool and checking the Force Flash All Partitions box.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
When you force flash all partitions does that fully change everything back to its original state?
[Google Pixel 5 Guides, News, & Discussion] Morgrain:
The Android Flash Tool has several options to untick. Do I also need to untick "Force Flash all Partitions"? It says "as well as force a wipe", so - since I want to update my rooted phone without having a wipe - I guess I also have to untick that?

View attachment 5509003
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yes

The only box that should be ticked is Skip Reboot.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
Has anyone tried to see if the Android Flash Tool could disable verity without a data wipe?
[Google Pixel 5 Guides, News, & Discussion] contaoxxx:
Hi

I have two questions because I am a little scared:

1)

Which way do you prefer (Update Android 11 to 12)?

automatic OTA update>after done, root with Canary 23016 or flash factory image

I don't wont to wipe my phone.

2)

I have always updated and rooted as follows:

flash.bat (-w flag remove)

adb reboot bootloader

double click flash.bat

boot.img patch with Magisk

adb reboot bootloader

fastboot flash boot magisk_patched.img

fastboot reboot

But now there is only a flash_all.bat

Do I also have to remove -w flag at:

fastboot -w update image-redfin-sq1a.220105.002.zip

Is this the correct way to go?

Thx
[Google Pixel 5 Guides, News, & Discussion] AquilaDroid:
I think you have the right method, replace the flash.bat with flash-all.bat with the -w flag removed. One of the experts may have other suggestions though.
[Google Pixel 5 Guides, News, & Discussion] contaoxxx:
Would you prefer to update over flashing factory image or installing OTA update?

Edit:

Do I have to uninstall any Magisk modules like Systemless Hosts, MagiskHide Probs Config and Universal SafetyNet Fix?
[Google Pixel 5 Guides, News, & Discussion] elong7681:
Universal SafetyNet Fix needs to be installed
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
My friend, you've been asking this question a lot...

The reason a data wipe is required when verity is disabled after having been enabled is related to the device bootloader. There is absolutely no way around it. It doesn't matter what update method you use or what tricks you try, you will always get Rescue Party after disabling verity with populated /data.

You can disable verity/verification with the Android Flash Tool when flashing an update. It's exactly the same as disabling verity/verification when manually flashing the factory image via ADB.

I know you want a better answer, but there simply isn't one.

Shouldn't matter. I personally prefer flashing the factory image. Data wipe is not required.

Yes.

No.
[Google Pixel 5 Guides, News, & Discussion] AquilaDroid:
OK, one more day of failure. I tried starting all over and flashed the flash_all.bat (-w removed) and rebooted. Then went back and flashed the patched boot.img to both slots, and it went through the reboot a couple times and back to fastboot where I reflashed the stock boot.img and all was well but no Magisk. I uninstalled the Magisk program, rebooted and tried everything again with the same result. I boot.img missing cmdline or OS version:

C:\Platform Tools January>fastboot boot "C:\Platform Tools \magisk_patched-23016_pL71W.img"

Sending 'boot.img' (98304 KB) OKAY [ 2.284s]

Booting (bootloader) boot.img missing cmdline or OS version

OKAY [ 1.538s]

Guess I'll stop trying to avoid wiping, put the -w back in the flash_all.bat and do it that way. Any tips on backing everything up? I'm planning on using Swift backup again but see that it needs root to backup data. It's not been a very rewarding exercise, and a big thanks to all who gave me ideas. I'm still convinced it might be one or more of the Magisk modules I had installed (and didn't uninstall prior to this) since I've seen that Systemless hosts and a couple others may be culprits.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
Yes, I have been asking that question a lot my apologies and yes I was hoping for a better answer but I should have known there wasn't one because you and several other people in this community including myself have tried many different ways to get around factory resetting our phone in order to flash a modified boot image. I appreciate your response and everything you've done to help the community keep doing what you're doing and thank you.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yeah, you seem to be having a pretty unique issue.

Ignore the cmdline/OS version message, it's irrelevant.

It's possible but unlikely that a Magisk module is causing issues.

Are you able to boot the patched image while the stock boot image is flashed?
[Google Pixel 5 Guides, News, & Discussion] AquilaDroid:
This is what I did as a last try: booted patched image, it boot looped with the G logo, then automatically rebooted back to stock boot.img

C:\Platform Tools January>adb reboot bootloader

adb server version (39) doesn't match this client (41); killing...

* daemon started successfully

C:\Platform Tools January>fastboot boot "C:\Platform Tools January\magisk_patched-23016_pL71W.img"

Sending 'boot.img' (98304 KB) OKAY [ 2.284s]

Booting (bootloader) boot.img missing cmdline or OS version

OKAY [ 1.538s]

Thanks again @V0latyle, I'll be pursuing the backup options tomorrow...
[Google Pixel 5 Guides, News, & Discussion] userwaldo:
The link is to the wrong version of the Universal SafteyNet, it points to v2.1.1 instead of v2.2.1.

Here is the correct link:

- https://github.com/kdrag0n/safetynet-fix/releases/download/v2.2.1/safetynet-fix-v2.2.1.zip
[Google Pixel 5 Guides, News, & Discussion] li0rli0r:
Hello, i have a small issue and if anyone knows how to fix it

I rooted my phone, but when I go to security I saw that google play security is on the October patch, i click on him to update it to December, all done right and the phone is restarted, when the phone up again, he up for a few second with security from December, and then the phone automatic rebooting and up again with October update (Google play security)

i tried clean cash from google play, and update again but still it all the time back to October

Does anyone know how to fix it?

thanks
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Thanks for the feedback, link changed to USNF page
[Google Pixel 5 Guides, News, & Discussion] puterboy:
So just confirming that you only need to patch the boot image ONCE per Android version and that you can 'fastboot boot' the same patched version after each subsequent update of the same Android version.

Thanks!
[Google Pixel 5 Guides, News, & Discussion] puterboy:
I updated by Pixel 5a manually to rooted Android 12 and now have Magisk 23016 working.

I tried to take an OTA update for the January update but it fails -- presumably reflecting your "just no very reliably" statement.

Do you have any sense of when/why OTA works and when it fails?

Is there anything I can do on my device to make OTA more likely to work?

If OTA won't work, what is the recommended next best (and least hassle) approach from the options you mention at the top of the thread?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
That's the idea, yes.

1. No.

2. Return to complete stock and don't root?

3. Dirty flash the factory image.
[Google Pixel 5 Guides, News, & Discussion] puterboy:
Naive question perhaps, but is "Dirty flash the factory image" the same as the method listed as "Update and Root Factory Image" on the initial thread post?

Mosti importantly, thanks for the help and all you do for the community.
[Google Pixel 5 Guides, News, & Discussion] puterboy:
Any reason not to use the "Update and Root using the Android Flash Tool" method if using an official Google build?

It seems super easy and there is not need to download anything since the update can be done directly from the browser plus it seems to be super easy to select from multiple (official) builds.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
Dirty flash means removing the -w from the flash-all.bat script which in turn will allow you to keep your data so no factory reset
[Google Pixel 5 Guides, News, & Discussion] elong7681:
no reason at all not to use it just don't check the box for the factory reset option
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
"Dirty flash" means flashing the factory image without wiping data. You can flash the factory image 3 ways:

Manually via ADB

Script/batch file via ADB

Android Flash Tool

Since I choose to manually patch the new boot image every month, I manually flash via ADB. But, if you're live booting the master image after update, it doesn't matter. The Android Flash Tool can be somewhat dummy proof since you don't have to understand how ADB works or how to use the commands; it's as simple as selecting the build and checking the boxes for the options you want.

Also, instead of posting multiple questions, please try to keep your comments to one post. XDA Forum Rules point 5.

It has nothing to do with the script, but yes - flashing the new factory image on top of existing system without wiping data.

Same as above, try to keep your comments to one post.

Hint: You can use the Quote button to select posts you want to quote, or you can click Reply on each one to insert the quote where your cursor is.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

I've got a big problem. I installed the update by Android Flash Tool. Everything went well, I think.

Subsequently I installed Magisk Canary to flash the boot.img to master root.img.

I flashed master root.img, but he stayed on bootloader and reboot on it.

I wanted to move the boot.img original and there I'm on an image "No command"

how I do now ?

EDIT: This is correct ?

View attachment 5511477
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yes, that command would temporarily boot the master root image.

I specifically outlined in the instructions do not flash the master root image.

If you have questions about the instructions, please ask.
[Google Pixel 5 Guides, News, & Discussion] Regys:
So I do not know how, but my phone to restart. I am well with the last update, no rooted

I think I have followed the instructions. I do not understand, what is the use of Master Root if we do not have to flash ?

So what do I do now to root it?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Temporarily boot it:

fastboot boot <master root image>

When phone boots, open Magisk

Tap Install > Direct Install

Reboot device
[Google Pixel 5 Guides, News, & Discussion] Regys:
So I do the same manipulation ?

I reboot bootlaoder > open cmd in platform-tools > and past:

fastboot boot master root.img

Ok ?
[Google Pixel 5 Guides, News, & Discussion] Regys:
Well it works.

I understand, I did the same thing just now.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Okay. So once you've booted the patched image, go into Magisk, tap Install, then tap Direct Install. Once done, reboot your phone.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

Yes, I did it, everything is ok.

Just in SafetyNet, "Response signature validation" failed, but I feel that it's not important ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I am passing Safetynet with the Universal SafetyNet Fix 2.2.1 and MagiskHide Props Config 6.1.2 modules. See the Pass SafetyNet section in the OP.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
Are you having to change your device signature with MagiskHide?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
No
[Google Pixel 5 Guides, News, & Discussion] elong7681:
Ok but you are using MagiskHide Props Config to pass Safetynet?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yes.

This is all I did:

Installed USNF (originally 2.1.1, now 2.2.1)

Enabled Zygisk

Enabled Enforce DenyList

Denied all components of these apps (ignore Facebook and Honeywell Home)

View attachment 5512409

I believe MHPC automatically installs when you enable DenyList.

I have not configured anything else. TBH I don't even know how to use the advanced options in MHPC or USNF.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
I haven't used MHPC in a long time and I also am not familiar with using the advanced features of MHPC but I did not know that USNF had advanced features. Is there a guide on GitHub or some other site for using the advanced features of USNF?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
USNF doesn't have additional instructions on its page beyond installing MHPC to spoof CTS. MHPC on the other hand has a lot of information.

Again, I didn't configure either module - just installed USNF, which I believe also installed MHPC, and blocked the apps in the screenshot. YASNAC reports SafetyNet Pass.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
Has anyone else gone without an automatic update as long as I have? My last update was November... With the new method for root via magisk, I want to simply wait for OTA update to happen, but I check prolly once a week with no results.

Spoiler content hidden.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Please resize your photos or use a spoiler.

I haven't always had the update notification, but I monitor for new releases anyway.

If you're concerned, you can sideload the OTA or dirty flash the factory image. Instructions to do so are in the OP.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
No problem. And thanks!
[Google Pixel 5 Guides, News, & Discussion] AquilaDroid:
OK, over the last few days ago I tried several things to update without wiping my device. I fnally used the Android Flash Tool and flashed the V2 Beta 2 file (w/o wipe). It flashed fine, but then I discovered that I still can't flash the Magisk patched.img successfully. I then went back and bit the bullet to wipe, thinking I'd be safe since I backed everything up to Google 1/ Google Drive. After the flash tool I discovered that I'm not able to restore my data from Google 1 although it looks like it is there. I tried to install Magisk with the direct install option but it went into recovery mode so I'm still without data and Magisk.

I just downloaded the V2 Beta 2 system image (redfin-s2b2.211203.006-factory-588d1292.zip) and am debating whether to flash it or patch the boot.img with Magisk and try that again. (I have been using "fastboot boot" magisk patched image instead of flashing it.)

Also, what is "Syncios" that seems to be constantly trying to install several times on the phone? Is that the missing link between the Android Flash tool and Google 1/drive? When I search for it most of the results are their website.

Sorry to be a pain, but I'm now down to a barely usable phone and struggling more than ever! Thanks for all the help.
[Google Pixel 5 Guides, News, & Discussion] andybones:
Google search shows what "syncios" is.

"All-in-one mobile manager helps you backup, transfer and manage iOS & Android phone data, sync files from computer to phone. Fully support Android 11 & iOS 15 device."

You can try it free or buy for $34.95.

Personally, I suggest Swift backup or AppDash for backing up application data.

And SMS Backup & Restore for text messages.

I also suggest making a backup of your Internal storage at least once a month to a PC.

I have lost too much from getting stuck in a bootloop and forced to factory reset, thus I'm a bit more anal about this and try to get a fresh backup at least once/twice a week.
[Google Pixel 5 Guides, News, & Discussion] AquilaDroid:
Thanks for your reply, @andybones. Yes, I did several backups in the lead up to this, including using Swift Backup, which I can't use now since I can't get root. Still don't know why I'm not able to get to the Google backups to restore everything.

I wish I hadn't been so suspicious of Syncios when it magically appeared on the phone and computer... More attempts tomorrow when my mind is (hopefully) clearer.
[Google Pixel 5 Guides, News, & Discussion] andybones:
Very welcome. And sorry, totally forgot you need root for Swift. I believe AppDash can backup most data w/o root, but I can't say for certain.

Have you ever downlaoded Syncios before? Maybe it's re-downloading from a previous backup or something?

I feel like it is more geared towards iOS, being called Syncios, and everything makes me believe it is, but ofc does support A11+ as their site says.

I do wish I could be of some help. Best of luck my friend.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Ok, Is it important to tick banking applications?

Thanks again for the help !
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yes.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Magisk Canary has been updated to 23017. Installing to inactive slot now supported.

Download it here or update through the Magisk app.

Note: If you have the Magisk app hidden, MAKE SURE you only update through the app! Multiple instances of Magisk will break root.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
View attachment 5513647I hope I did this right, but looks like after clearing storage in Google Play Services, the checking, it worked. Now, do I use the OTA update option now in Magisk?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yep, you spoiler'd properly, thank you.

So when the update prompts you to restart, before you reboot, open Magisk, tap Install, then "Install to inactive slot". THEN reboot. You should boot into the update with root.

If losing root is not acceptable, I'd recommend you wait until you're near a computer just in case something goes wrong.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
Strange. OTA downloaded and installed, after which I installed Magisk via OTA option, as discussed. But for some reason the update failed ...
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Another user suggested restoring the boot image prior to the OTA:

Open Magisk, tap Uninstall, tap Restore Images DO NOT REBOOT

Manually start OTA update: Settings > System > System Update

Allow OTA to download and install; DO NOT REBOOT

When OTA update prompts to restart, open Magisk, tap Install, then tap Install to Inactive Slot

Reboot device

More information here
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
Thank you. I will give it a try when I get back to wifi.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
Nope. Now I've lost root.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Huh. Download factory image, manually patch boot image and flash.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

I have an important issue on the security of an application.

In Magisk it is possible to make an application invisible to hide it from root.

But does Magisk make him only invisible or then he unooys the application ?

In other words, is the application secured ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I am not sure what you are asking.

I don't provide support for Magisk. Magisk specific questions should be posted in this thread.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Ok, I'm going to post there.
[Google Pixel 5 Guides, News, & Discussion] Zanzibar:
My Pixel 5 is rooted, and still on Android 11. I haven't updated yet, because I didn't want to use disable-verity and disable-verification and be forced to wipe data.

With the new Canary version of Magisk (23017), should I be able to finally update to Android 12 without wiping data, and still maintain (or re-patch boot.img) root?

My thought process is this. Either sideload the OTA or flash factory image removing "-w" from the update line. Install Magisk, patch the boot.img file, then fastboot flash boot boot.img.

Does that sound like it would work, and let me keep my data?

Am I missing any steps?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yes, you're missing the most critical step: Always read the OP. Your questions have already been answered and the necessary information provided.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Magisk Canary 23018 is out.

Changes:

[Zygisk] Show warning in app UI to indicate incompatible Zygisk modules

[App] Allow modules to specify an update URL for in-app update + install

Update from within Magisk to prevent problems like breaking root.

If you do not already have Magisk installed, Download it here
[Google Pixel 5 Guides, News, & Discussion] TKruzze:
To state it more clearly, since this seems to be a huge problem...

If you have previously hidden the Magisk app, make certain you PERFORM ALL UPDATES FROM WITHIN THE MAGISK APP. If you don't do it this way, you'll end up with with multiple installs of the app, which will break root.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Updating from within the app is the preferred method. I'll update my posts.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Magisk Canary updated to 23019

Changes:

- [Zygisk] Skip loading modules into the Magisk app to prevent conflicts

- [MagiskBoot] Change `zopfli` to a more reasonable config so it doesn't take forever

- [General] Several `BusyBox` changes

Preferred method of update is from within Magisk app.

If installing for the first time, here is the APK Download
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
@topjohnwu has been busy. He doesn't get nearly enough appreciation for all his hard work.

Magisk Stable is still 23.0.

Magisk Beta is now 24.0

Canary is now 24001

Magisk 24.0 discussion thread