yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] badabing2003:
I can't possibly comment on all modules, however modules that don't make any system changes (even remount rw can cause issues) should be fine.

I have the following modules and I never disable them and have had no issues updating without disabling them.

Perhaps a safe list can be compiled over time.

Systemless Hosts v1.0

Universal SafteyNet Fix v2.2.1

BuiltIn BusyBox v1.0.3

SQLite for ARM aarch64 devices v1.3

Axet's Call Recorder v1.0.1
[Google Pixel 6] badabing2003:
What's your Mac version?

macOS 11 Big Sur or newer only.
[Google Pixel 6] longbottle:
10.13.6
[Google Pixel 6] badabing2003:
Sorry, you're only option is to build it yourself, you can find the instructions on GitHub, let me know if you have any questions.
[Google Pixel 6] longbottle:
I mean, at this point I've already rooted my device manually. But it just seems kind of silly that the application runs fine otherwise, but just won't verify the validity of the factory firmware file. Oh well.
[Google Pixel 6] badabing2003:
In the support file I don't see any evidence that it was rooted or flashed using PF.

There are library dependencies, Even if some parts seems to be working and others not, I wouldn't perform it with PF if I were you unless you build it for your device, because you never know where it would fail and what would be the implications of it.
[Google Pixel 6] longbottle:
Since it didn't work to even find the boot image in the firmware zip file, I decided to dig it out, modify it manually, and flash it with fastboot, per old ways.

I think the actual issue here might be that the factory firmware for the Pixel 6 still uses boot.img because it shipped with Android 12, and PF is expecting there to be a init_boot.img like there is for the devices that shipped with Android 13.
[Google Pixel 6] badabing2003:
Nope,

PF automatically figures it out from the image, but if it can't look inside the image because the libraries are mismatched, it can't decide.

Like I said, unless you build it on your OS, you shouldn't be using PF, once you do, you'd see that it will figure out what needs to be done.
[Google Pixel 6] longbottle:
Building an application so that I can use the application to root a device is adding extra steps in. Thought the point here was to streamline the process.

I appreciate the replies, thank you for your time.
[Google Pixel 6] badabing2003:
New Release:

Sep 24, 2023 v5.8.0.1 release

Bug fix: #99 Settings not opening on linux/arch based distro
[Google Pixel 6] tom1807:
Just a short feedback. A14 installed, all went smooth, root was preserved.

Cheers

Tom
[Google Pixel 6] kiwigi:
Thanks for the feedback and to @badabing2003 and I hope there are some worthwhile changes in the OS.
[Google Pixel 6] badabing2003:
Time would tell, I know that AFwall+ broke for me, and so did few of my Tasker tasks.

Time to chase for solutions :(
[Google Pixel 6] nummer:
i was able to easily upgrade to android 14 as well, everything preserved. lsposed and aosp mods were a couple things that i were worried about, but they are both working just fine.
[Google Pixel 6] tom1807:
So forum moved, so my previous post was vanished, so post again:

I have (several) weird problem, everything was fine after last night flashing to A14 including root.

Today I played a little with the mobile, then suddenly error messages about apps keep crashing.

The next weird thing was, that previous app icons were gone and I had to go through one-by-one in the PlayStore under Installed(!) and check each app and had to install again.

Interesting part, all apps I had to reinstall, could access all the data previously saved on the mobile.

Enpass, my astronomy programs, some side-loaded apps, OneDrive; all tis worked right after installing them again, no registration or login required.

Then the GooglePlaySystem Update is now back to July 1, 2023, any update to a newer version fails.

But now the worst part.

I don't have root anymore.

Tried with the Pixelflasher, after reboot no root.

Tried manually to patch the boot.img, which is successful in Magisk, boot to fastboot, use the command "fastboot flash boot magisk_patched.img" but after reboot Magisk still shows N/A under Magisk.

ADB is v34.0.4-10411341.

I recall that previously had to patch the Pixel 7 boot image and I am not sure whether the current ADB version doesn't make problems (again).

Anyone an idea?

Attached the log files of PF:

PixelFlasher_2023-10-05_02h03m19s.log: Shows the successful flash from last night

PixelFlasher_2023-10-05_10h19m46s.log and PixelFlasher_2023-10-05_11h19m47s.log show the unsuccessful attempts to flash and root again with PF.

Cheers

Tom
[Google Pixel 6] badabing2003:
yes flashing slot a in PixelFlasher_2023-10-05_02h03m19s.log completed without errors, which was completed at

2023-10-05 02:10:30 Done!

Next thing we have logs are at:

2023-10-05 10:19:57

And you don't have root, and more importantly, Magisk is not found.

Where is Magisk, where did it go? what happened to it?

Do you recall what you did outside of PF that would have brought it to this state?

Then you tried to flash again.

2023-10-05 10:26:52 Done!

Still no root

You tried it few more times

Always no root.

I would change two things.

1- use Platform Tools 33.0.3, avoid using 34.x

2- There could be a Magisk somewhere getting in the way.

Get this app from play store.

Run the checks, specially "Xposed Check" (even if you don't have Xposed)

see if it find Magisk in the list and fails.

If it does, it tells you the package name.

Go and uninstall that package (you can do it with PF's Package Manger to search for it)

Reboot

Repeat

Untill no more Magisks are found.

Then install Magisk
[Google Pixel 6] Jaitsu:
Dropping in to report another successful A14 flash, no issues. Magisk is playing nice with all the same setup as I used under A13.
[Google Pixel 6] tom1807:
Thanks a lot for looking into that, though I am sure that PF is not to blame, but I really appreciate your suggestions and trying to help.

2am in the morning, flashed A14 without problems, went to bed and didn't touch the mobile anymore.

Before flashing, I restored Magisk from the "Hide"-state, after successful flash, I hide Magisk again.

Next morning, played with A14, changed from 3-button navigation to Gesture Navigation, changed the App Grid from 5x5 to 4x4, and from this moment, my home screen lost all desktop icons (like Pixel Launcher crashed or deleted all data) and then I got error messages of different applications crashing.

Checked then the app drawer, and the majority of apps were gone.

This is were I noticed that Magisk was also not showing up in the app drawer, in addition to the other apps.

Like I said before, I had to reinstall them, even PlayStore listed them under "Installed".

And then I started to use PF again to install A14 again, as you noticed, the attempts were unsuccessful.

Yeah, still have a backup of v33.0.3.

Will try to flash with this version again.

You are maybe into something.

Like I wrote before, when reinstalling the "lost" apps, they opened like they were never uninstalled and opened at once using the still available data.

I noticed, that the new attempts contain several lines starting with "inflating" which didn't show up in the first flash. But I am mot sure whether this is anything of importance.

Oh, this looks concerning.

Play Integrity Check:

Fail: Device Integrity, Strong Integrity, Virtual Integrity (no surprise here)

Root Check:

Fail: Root Management Apps

Xposed Check:

PM Command:

Fail: com.topjohnwu.magisk

PM Conventional APIs:

Fail: com.topjohnwu.magisk

PM Sundry APIs:

Fail: com.topjohnwu.magisk

PM Intent Queries:

Fail: com.topjohnwu.magisk

All other entries show "Pass"

Will follow up but this time with ADB v33.0.3 to eliminate a potential issue and get back to you.

Edit: Wow, the Package manager lists all previous installed apps which are now not installed. That's amazing.

Cheers

Tom
[Google Pixel 6] badabing2003:
Not really,

When you use rooted Magisk, ie the resources from /data/adb/Magisk (you need root for that)

There is nothing to unpack, inflate.

When you use the Magisk manager app, pf first find the path to Magisk APK, unpacks it into a temporary directory and uses that to create a patch, that is why you are inflating.
[Google Pixel 6] tom1807:
Yeah, I figured this when I tried a new flash with ADB v33.0.3 and tried to install new.

Anyway, no luck after cleaning up Magisk with PF.

TB Checker also didn't find any traces.

However, I saw a reference to a package name "q.xzhkrtj" which I am almost sure that this is the hidden Magisk app from the previous successful flash. But, I can't delete or remove it.

When I boot to recovery and try to mount the system, I get error messages.

At this stage, I think I should do a clean flash.

Attached the last logfile, making sure no Magisk installed.

Cheers

Tom
[Google Pixel 6] kiwigi:
Have you done it in the same way as monthly updates with factory images?
[Google Pixel 6] badabing2003:
Yes, nothing changes.
[Google Pixel 6] badabing2003:
Something is off on your phone.

I don't like this message.

2023-10-06 12:29:31 ERROR: Could not get package list.
global flags not at the start of the expression at position 13

I just pushed an update that include refined debug messages to understand what is going on.

Just use PF 5.8.0.3

Go to Package Manager

Find the q.xzhkrtj

take a screenshot

then select it and right click and choose uninstall.

Generate support file.
[Google Pixel 6] badabing2003:
Update Release:

Oct 06, 2023 v5.8.0.3 release

Improved debug messages for troubleshooting.
[Google Pixel 6] Galaxea:
I did the update to A14 through the phone update, and then tried to patch the boot.img with Magisk to get root back but it never worked.

I then use PF to patch and install and everything is working fine. Great tool. Thanks.
[Google Pixel 6] kiwigi:
Thanks heaps @badabing2003, it worked perfectly!
[Google Pixel 6] tom1807:
Thanks for replying and being so invested in that.

Below the screenshot:

View attachment 6018165

and attached the support file.

Edit: Wasn't there before an option for verbose?

Maybe I am blind but couldn't find it.

Edit-2: Ok, so when starting PF with Advanced Options enabled, Verbose doesn't show up, Disable Advanced Options and Verbose shows up, Enable Advanced Options again, and Verbose stays visible.

Cheers

Tom
[Google Pixel 6] coendeurloo:
My post got deleted during the move so here it is again:

I'm currently on A14 beta (U1B2.230922.006)

Should I update to A14 with the full OTA... or the Factory image using Pixel Flasher? I tried to flash the full OTA earlier, and it didn't work for some reason...
[Google Pixel 6] badabing2003:
Would you happen to have a phone with multi-user? or with intune?

That screenshot does not look right

:) I bet you don't see Clear Console button either?

When you enable Advanced options, there's more stuff that shows on the screen, which take a bit more real estate.

Normally PF resizes the window to adjust, but if your monitor resolution is low, you might miss some parts.

Full OTA should be find.

What exactly did not work?

Support file would help me troubleshoot.
[Google Pixel 6] coendeurloo:
Something about switching slots it seems?

==============================================================================
2023-10-07 15:09:36 PixelFlasher 5.8.0.3 Flashing Phone
==============================================================================
Android Platform Tools Version: 33.0.3-8952118
Rebooting device 21041FDF6006UQ for sideload ...
Waiting 20 seconds ...
2023-10-07 15:10:03 Flashing device 21041FDF6006UQ ...
Active code page: 850
Current Active Slot is: [a]
serving: 'C:\Users\deurl\Downloads\oriole-ota-up1a.231005.007-b69a2c1b.zip' (~0%)
serving: 'C:\Users\deurl\Downloads\oriole-ota-up1a.231005.007-b69a2c1b.zip' (~1%)
serving: 'C:\Users\deurl\Downloads\oriole-ota-up1a.231005.007-b69a2c1b.zip' (~2%)
...
serving: 'C:\Users\deurl\Downloads\oriole-ota-up1a.231005.007-b69a2c1b.zip' (~45%)
serving: 'C:\Users\deurl\Downloads\oriole-ota-up1a.231005.007-b69a2c1b.zip' (~46%)
serving: 'C:\Users\deurl\Downloads\oriole-ota-up1a.231005.007-b69a2c1b.zip' (~47%)
Total xfer: 1.00x
rebooting to bootloader ...
Sleeping 5-10 seconds ...
Reading current slot value ...
Current slot: [a]
Comparing the current slot with the previous active slot ...
"Current slot is the same as the previous slot."
"It appears that OTA flashing did not properly switch slots."
"Aborting ..."
rebooting to system ...
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
2023-10-07 15:12:00 Done!
Flashing elapsed time: 144 seconds
------------------------------------------------------------------------------
[Google Pixel 6] tom1807:
No, nothing like that. The greyed out programs refer to programs which are still available on my mobile, buu the program icons are missing. So, if I download these from PlayStore again, they are showing as installed.

There is a Clear Console? :p

Yeah, I work mainly on the notebook but it's 1920x1080.

Cheers

Tom
[Google Pixel 6] badabing2003:
No,

Notice how it stopped at 47%

The message about switching slot is PF double checking to make sure that OTA properly installed and switched slots before flashing the patch, because if it proceeded then your main slot would have been flashed and you would have bootlooped.

Try sideloading again and it most likely would work, I have see this happen rarely, it's the Updater (Google's) itself not completing the job for whatever reasons.

I'm concerned your data partition is messed up.

I'll try to dig some more into your logs, but everything is pointing to that.

yeah, maximize the window, it should fit into 1920, 1080 well enough.
[Google Pixel 6] tom1807:
Do you think a Verbose log would give more information?

I am afraid you are right.

I noticed the following lines from the original "good" flash and in the later follow-up flashing

[liblp] Partition product_a will resize from 0 bytes to 2929668096 bytes
[liblp] Partition system_a will resize from 0 bytes to 962285568 bytes
[liblp] Partition system_ext_a will resize from 0 bytes to 270757888 bytes
[liblp] Partition system_b will resize from 0 bytes to 20312064 bytes
[liblp] Partition vendor_a will resize from 0 bytes to 605216768 bytes
[liblp] Partition vendor_dlkm_a will resize from 0 bytes to 43245568 bytes

I cannot recall seeing this with the ADB v33.0.3 when flashing the September update.

The October Flash was done with ADB v34.0.4

Cheers

Tom
[Google Pixel 6] coendeurloo:
I tried doing it two times again, but unfortunately it's the same story:

==============================================================================
2023-10-07 21:13:26 PixelFlasher 5.8.0.3 Flashing Phone
==============================================================================
Android Platform Tools Version: 33.0.3-8952118
Rebooting device 21041FDF6006UQ for sideload ...
Waiting 20 seconds ...
2023-10-07 21:13:53 Flashing device 21041FDF6006UQ ...
Active code page: 850
Current Active Slot is: [a]
serving: 'C:\Users\deurl\Downloads\oriole-ota-up1a.231005.007-b69a2c1b.zip' (~0%)
serving: 'C:\Users\deurl\Downloads\oriole-ota-up1a.231005.007-b69a2c1b.zip' (~1%)
serving: 'C:\Users\deurl\Downloads\oriole-ota-up1a.231005.007-b69a2c1b.zip' (~2%)
...
serving: 'C:\Users\deurl\Downloads\oriole-ota-up1a.231005.007-b69a2c1b.zip' (~44%)
serving: 'C:\Users\deurl\Downloads\oriole-ota-up1a.231005.007-b69a2c1b.zip' (~45%)
serving: 'C:\Users\deurl\Downloads\oriole-ota-up1a.231005.007-b69a2c1b.zip' (~46%)
serving: 'C:\Users\deurl\Downloads\oriole-ota-up1a.231005.007-b69a2c1b.zip' (~47%)
Total xfer: 1.00x
rebooting to bootloader ...
Sleeping 5-10 seconds ...
Reading current slot value ...
Current slot: [a]
Comparing the current slot with the previous active slot ...
"Current slot is the same as the previous slot."
"It appears that OTA flashing did not properly switch slots."
"Aborting ..."
rebooting to system ...
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.001s
2023-10-07 21:15:52 Done!
Flashing elapsed time: 147 seconds
------------------------------------------------------------------------------
[Google Pixel 6] badabing2003:
That part is telling us the previous state of the partitions were all 0 bytes, possibly a botched flashing, and this time it resized to whatever the image needed.

By any chance, did you see any update notification on your phone?

You could try the factory image approach.
[Google Pixel 6] tom1807:
Kinda strange, the last flash I did was the September update with the factory image, unfortunately I don't have this log anymore so I can't check this.

So a clean installation is in order.

Cannot even mount the system from recovery, throws an error message.

Cheers

Tom
[Google Pixel 6] badabing2003:
You had custom rom / recovery?

I think it is best.
[Google Pixel 6] tom1807:
No, that's the strange part, I used PF to boot to recovery on Slot A and it showed me a recovery, but when switching to Slot B and boot to recovery I was greeted with the "No Command" sentence.

Yeah, I am wondering now how long I carry already this misconfiguration.

I bought the Pixel 6 used and later confirmed it was only 1 month old when I bought it. But it was not unlocked at that time.

However, I am still convinced that the root of the problems is ADB v34.0.4.

Cheers

Tom
[Google Pixel 6] badabing2003:
It's possible, but hard to tell, a factory flash (not ota) with wipe, force and flash both slots (while choosing stock boot) will restore it to brand new state, then install Magisk, create a patch and just Flash Boot (not Flash Pixel Phone)
[Google Pixel 6] tom1807:
Yeah, I am in the process of backing up my apps and data and will do that.

I only usef actory images to flash the Pixel since you published PixelFlasher.

In the beginning I used OTA and had to wait long time for "Optimizing the device".

I am more concerned now where the recovery came from , AFAIK, Pixel devices (and maybe also in generic A/B devices) have no recovery anymore. The image also doesn't contain one.

I suspect now, that the previous owner tried that to root, didn't work, locked the bootloader again and sold it.

Because I had to unlock the bootloader before the first installation.

Thanks a lot for investing your time for that.

Edit: By flashing the images to the Inactive slots (A and B) one after the other, I got rid of the recovery.

Cheers

Tom
[Google Pixel 6] coendeurloo:
Yeah I think I did see something like that in the meantime! Not sure to what it upgraded though, definitely still on beta.

So a factory image with the standard settings and keep data might work here?
[Google Pixel 6] badabing2003:
it should.
[Google Pixel 6] badabing2003:
Update Release:

Oct 11, 2023 v5.8.1.0 release

Added data for Pixel 8, Pixel 8 Pro

Build workflow update, sha256 checksums are now published along the binaries.
[Google Pixel 6] tom1807:
So, to bring this to an end, following outcome.

I did as you suggested with Wipe, Force and Flash both slots with stock boot.

Everything was clean.

What didn't work to use the Flash Boot only to gain root.

No matter what I tried, active slot, inactive slot and only the selected patched boot image, I couldn't obtain root.

There is a high chance that I did something wrong by making a wrong selection.

So, after that, I just patched the image and flashed the mobile again to the active slot and Root was available again.

Thanks again for your time and for helping in this situation.

Cheers

Tom
[Google Pixel 6] badabing2003:
I can think of one of the two possibilities.

- After wipe, Magisk manager is gone, even if you flash boot the patch, it requires Magisk Manager, which you would need to install, and preferably the matched version (but not necessarily)

- The patch you were flash booting was created with an older Magisk, which is not compatible with A14.

Your last step

If you recreated a patch, that would have guaranteed that Magisk was installed, and if this patch worked, it means that had you Flashed Boot this patch, it would have worked as well without the need to do a full flash.

In any case I'm happy that you got it working.
[Google Pixel 6] bgumble:
Unfortunately there is no factory image for the pixel 6, until now.
[Google Pixel 6] badabing2003:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

View attachment 6021659
[Google Pixel 6] bgumble:
Unfortunately there is only full OTA (without keeping data)
[Google Pixel 6] tom1807:
The above link by badabing2003 leads to the full factory images.

Don't mix up the filename "UP1A". That's referring to "Upside Down Cake" as codename, not Update. ;)

Cheers

Tom
[Google Pixel 6] badabing2003:
Sorry but I have no idea what you're talking about.
[Google Pixel 6] V0latyle:
Yeah, me neither. The OTA does not wipe data. The factory image is not the OTA. There are two ways to update; OTA (either automatic via system, or sideload via recovery) or factory image via fastboot with or without a data wipe.
[Google Pixel 6] bgumble:
Sorry for being confused and thx for your help.

If I select a factory image I can choose between Keep Data and WIPE data,

but if I select an OTA image there isn't such an option, thow I thought flashing wipes all the data.
[Google Pixel 6] badabing2003:
Because OTA never wipes.

From the main thread.

View attachment 6022078
[Google Pixel 6] bgumble:
thx for your quick answer, so I'll flash my pixel 6 1st time with full OTA Android 14 and that will keep all my data. Perfect. Thank you for your help and this great tool!
[Google Pixel 6] badabing2003:
New Release:

Oct 18, 2023 v5.8.2.0 release

Added `Wipe` option (only available in custom flashing), this will wipe userdata after flashing, required for first time vbmeta verification disabling.

Added validation checks to make sure A and B slot vbmeta verity / verification states match.

Added a warning when toggling `Disable Verification` to inform about the the potential wipe implications.

Display both slots verity / verification states when displaying device details.

Extract vbmeta.img if found to easily select it for patching.

Improved paste button which now dynamically selects what to paste based on the custom flash option selection.
[Google Pixel 6] guniens:
Hi everyone!

I'm on a Pixel 6 with A13 and rooted, I've been always updating with Pixel Flasher.

I would like to install A14, I've both factory and ota images and I would like to completly erase my Pixel 6 during update, then root again and then installing everything back (just my preference of clean start from a major OS version to another).

What's the right process to do in Pixel Flasher?

Thanks in advance!
[Google Pixel 6] badabing2003:
This is how I would do it.

- Turn on advanced settings in PF

- Use the Factory image first, Process it and select the boot file.

- Make the following choices and hit Flash Pixel Phone button

View attachment 6023014

- You will have stock A14 ready for first setup, set it up, enable developer options, USB debugging ... all the usual stuff

- Install Magisk through PF by clicking on Install Magisk button and selecting the variant,

- Select the boot file in the processed list and hit the patch button to create a patched boot file.

- Clear the Flash to both slots and Force Flash Options.

- Select the patched boot, and hit the Flash Boot button (not the Flash Pixel Phone button)

At this point you have a rooted A14.

If you want to have both slots bootable continue with the following steps, otherwise you're done

Download full OTA, and process it.

Depending on if you want the other slot to be rooted or not, select the appropriate boot (stock or patched)

Hit the Flash Pixel Phone button and you're done.
[Google Pixel 6] guniens:
Should I hit the Flash Boot button or Flash Pixel Phone button?

OEM unlock isn't necessary as it's altready OEM unlocked and stays like that right?

Sorry can you explain a bit more about this?
[Google Pixel 6] badabing2003:
Made it clearer , it's Flash Boot button.

I suggest you read the OP in the main thread to be familiar with PF usage and what each button does.

I never said anything about OEM unlock

I updated my post again, however all of that is in the main thread's OP.
[Google Pixel 6] guniens:
Thanks a lot for you help!