yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8] guniens:
Hi @badabing2003 sorry to bother you but really don't know what else to do or who else to ask.

I've a P8 and have a strange problem, basically when I turn off the phone at night and on in the morning time is 50m/1h behind, all auto sync options enabled and as soon as I connect to internet, either wifi or mobile data, time is synced.

However this doesn't always happen.

AFAIK time sync is done via cellular towers signal (NITZ protocol) and via internet (NTP protocol) afterwards.

I didn't have this problem with a Pixel 6 and I had the exact same setup expect for security patches, the P6 was behind as I sold it before updating.

Another thing is that I always used PF, but with the P6 I was always using the factory image even for OTAs, with the P8, as of now, I've only used OTA images. Could that be the cause?

Does it happened to you or something similar? Can you help me?

Thanks in advance!
[Google Pixel 8] badabing2003:
Try to isolate the problem.

1- see if it is associated to first power on, or sync issues.

Instead of powering off at night, put it in airplane mode, and check in the morning to see if it still behind.

2- if it is, try setting the timezone manually, and then the time, and then turn auto and get out of airplane mode.

OTA vs factory has no bearing on the outcome of this.

1 hr difference could be due to wrong time zone, but 50 minutes does not, and that's really weird.
[Google Pixel 8] guniens:
Hi! First of all thank you

About 1: I put it in airplane mode and also turn off wifi right?

About 2: should I disable auto sync before trying point 1?

I remember seeing an issue in Magisk's GitHub stating a 60s delay at boot, could this be the issue?
[Google Pixel 8] badabing2003:
1- yes

2- shouldn't matter, if it's in airplane mode, auto sync won't work, and to be able to manually set the time with airplane mode, you'd have to turn off the auto-sync anyways.
[Google Pixel 8] guniens:
Got it!

Will try and report back but guess I would need a couple of days of testing to get consistent results.

Can I still flash the March update before doing the tests?
[Google Pixel 8] guniens:
Hi @badabing2003

Did what you said, both steps. Time in the morning was dead right (actually 4/5s behind).
[Google Pixel 8] badabing2003:
Did you turn off airplane mode afterwards (I suppose you would to use your phone)

What happened?

What happens if after that (while it is still in airplane mode) you power off and power it back on?

Turn of auto-sync and test again tomorrow
[Google Pixel 8] guniens:
Will try and report back.

In the meantime I flashed the March update, kept all modules disabled except systemless hosts and play integrity fork and powered off for 4 hours. Time was correct.
[Google Pixel 8] guniens:
Hi again @badabing2003, some updates:

Good Thursday, powered off for 4 hours in the afternoon.

Good Friday, powered off for 8 hours at night (Thursday), was about 30/40s behind, adjusted as soon as I connected to internet.

Good Saturday, powered off for 8 hours at night (Friday), was about 40/60s behind, adjusted as soon as I connected to internet.

Good Saturday, powered off for 4 hours in the afternoon.

Now I've powered it off and put on charge for about 1 hour or so and when powered up was 7 minutes behind.

This is with every auto sync option enabled and all magisk modules disabled.

I was thinking about a software issue or one of the module itself as a culprit, could it be the charger?
[Google Pixel 8] badabing2003:
If all modules are disbaled, they can't be the culprit.

I'm wondering if one of the wifi connection gets established first before the data connection, and the dhcp server provides a time servcer from your router or something else in your household, which is behind.

That is was airplane mode tests are more important.

First both off

and then one or the other (test both scenarios) of data / wifi
[Google Pixel 8] guniens:
Only play integrity fork and systemless hosts.

I actually turn off both wifi and mobile data before powering off.

So should power off in airplane mode for the first test right?

Next test with wifi and next with mobile enabled? With auto sync time will be correct in these tests.
[Google Pixel 8] matthewd020472:
good day all, just saw this pixel flasher and wanted to try it. i am on october firmware and ANY firmware i try to flash it says it shows me this error

Device is now in adb mode.

Updating connected devices ...

Getting package com.topjohnwu.magisk path on the device ...

2024-03-10 03:44:37 ERROR: Could not get package com.topjohnwu.magisk path.

i can not find where to tell pixel flasher where to find magisk. can anyone assist me?
[Google Pixel 8] bdr127:
Click the big "Settings" button in the upper right. "Magisk Package Name" --> enter the package name in the text box.
[Google Pixel 8] matthewd020472:
its there already

View attachment 6078264
[Google Pixel 8] bdr127:
Do you have Magisk hidden? Go to the Magisk Manager app on your phone -- click the Settings gear in the upper right, and then look at "Hide the Magisk app."
[Google Pixel 8] matthewd020472:
Not clicked to hide
[Google Pixel 8] badabing2003:
Yep

One more, with the reverse, ie data on first and then wifi on

These are tests rather than a fix, trying to isolate where the problem might be,

@matthewd020472

What is the issue?

Have you read the usage guide and followed the steps?

I will not provide any support without support file.
[Google Pixel 8] matthewd020472:
where can i find the usage guide?
[Google Pixel 8] badabing2003:
Start by reading OP
[Google Pixel 8] matthewd020472:
so OTA are preferred over factory images?
[Google Pixel 8] matthewd020472:
flashing the OTA just updates the phone to the firmware selected, i get that .. maybe i am dumb i dont see where it then roots the phone.

if i choose factory firmware and it processes the file and then produces the init_boot file, i would flash the firmware to update it, then flash the patched file to gain root?
[Google Pixel 8] badabing2003:
Check step #8 again.
[Google Pixel 8] matthewd020472:
OTA file selected, tried patching it and i get the error

2024-03-11 15:22:00 User initiated Magisk Patch boot

==============================================================================

==============================================================================

2024-03-11 15:22:00 PixelFlasher 6.8.2.1 Patching Magisk boot

==============================================================================

Patching on hardware: husky

Deleting /storage/emulated/0/Download/init_boot_a06ee98e.img from the device ...

2024-03-11 15:22:00 ERROR: Could not delete /storage/emulated/0/Download/init_boot_a06ee98e.img

Return Code: 1.

Stdout:

Stderr: adb.exe: device '39191FDJG004QM' not found

Aborting ...
[Google Pixel 8] badabing2003:
Device, is not connected

And please don't ask for help without porviding support file.
[Google Pixel 8] matthewd020472:
appologies
[Google Pixel 8] matthewd020472:
this app is amazing to say the least. alot easier then flashing and patching with adb. i guess it is pretty simple either use the OTA file or the firmware and process the file then patch and flash yes? just want to make sure its that easy to do, i have over 650 GB worth of files, vides and pictures and such. would hate to lose it all.
[Google Pixel 8] badabing2003:
Yes the process is the same or similar wheter you choose OTA or factory,

You process, patch, select patch, flash

I suggest you use OTA and flash twice in a row, this way you'd get both slots bootable.

You're on Aug 2023 release slot A

Selected Device on 2024-03-11 14:15:16:
Device ID: REDACTED
Device Model: husky
Device Active Slot: a
Device Mode: adb
Device: REDACTED 8 Pro
Device First API Level: 34
Device Version End Date: October 2026
Device Secuity Update End Date: October 2030
Has init_boot partition: True
Device Bootloader Version: ripcurrent-14.0-10807316
Device is Rooted: True
Device Build: UD1A.230803.041
Device API Level: 34
Android Version: 14
Android Name: Android 14
Android Codename: Upside Down Cake
Android Release Date: Q3 2023
Android Latest Update: Present
Device Architecture: arm64-v8a
Device Kernel: Linux localhost 5.15.110-android14-11-ga6d7915820a0-ab10726252 #1 SMP PREEMPT Mon Aug 28 18:42:09 UTC 2023 aarch64 Toybox
Device Kernel Version: 5.15
Device KMI: 5.15.110-android14
sys_oem_unlock_allowed: 1
ro.boot.flash.locked: 1
ro.boot.vbmeta.device_state: locked
ro.product.first_api_level: 34
ro.boot.veritymode: enforcing
ro.boot.verifiedbootstate: green
ro.secure: 1
ro.zygote: zygote64
ro.vendor.product.cpu.abilist: arm64-v8a
ro.vendor.product.cpu.abilist32:
vbmeta type: ab
Slot A Verity: Disabled
Slot A Verification: Enabled
Slot B Verity: Enabled
Slot B Verification: Enabled
WARNING! WARNING! WARNING! Slot a verity / verification does not match slot b verity / verification WARNING! WARNING! WARNING! There is a mismatch of currently selected vbmeta verity state and device's verity state
Magisk Manager Version: 27.0:27000
Magisk Path: /data/app/~~xyibvKeVc_Udh9NX8C8t4w==/com.topjohnwu.magisk-yIAitzkoJ3H38L_zTajsog==/base.apk
Checked for Package: com.topjohnwu.magisk
Magisk Version: 27.0:27000
Magisk Config SHA1: 00c253f2099e77e07a6a25bc2cd0125366341b65
Magisk Modules:
ViPER4AndroidFX repackagedhoch77 enabled v2.7.2.1-v77-(864fafa) [Update Available]
Systemless Hosts enabled 1.0
Universal SafetyNet Fix enabled v2.4.0-MOD_2.0
Zygisk - LSPosed enabled v1.9.2 (7024)
Shamiko enabled v0.7.4 (188) [Update Available]

Make sure the device is connected, scan / select device, it show as above.

Download the latest OTA

Process

Patch

Flash Pixel Phone

Wait for it to boot to system, it should be on slot B

Scan / select, and just hit the Flash Pixel Phone again.
[Google Pixel 8] matthewd020472:
much appreciated sir thank you very much.
[Google Pixel 8] badabing2003:
Update Release:

Mar 11, 2024 v6.8.3.0 change log:

Fix MacOS builds, we're finally back to buiding with MacOS 11 (fingers cross it lasts).

If internet is not available, do not try to build a menu with Google Devices.
[Google Pixel 8] TOSHIYUKI AOKI:
HI!

Please tell me.

I have the Japanese version of Pixel 8 (GZPF0).

Is it possible to install a global Pixel 8 ROM using this tool?

If I install the global version of Pixel 8 (GPJ41), will the WiFi standard become WiFi 7?

thank you.
[Google Pixel 8] badabing2003:
I don't know.
[Google Pixel 8] guniens:
Hi again @badabing2003

I found the root cause of the problem: charging while powered off.

Time was always correct when powering off at night and on in the morning while NOT in charge during the night.

Time is wrong when I put in on charge powered off and power on in the morning.

I was using a Samsung 25w PD past charger that I was previously using with my Pixel 6 and also bought the official Google 30w charger.

One thing to note: I powered off the phone and put in charge for 1h30min on Friday while at work, using the Google charger, TIME WAS CORRECT when I powered it on.

I powered off the phone and put in charge all night tonight (well maybe was more like 4/5 hours of sleep lol), using the Google charger, TIME WAS WRONG when I powered it on. This time was wrong by 40min behind.

Is it reasonable to fully bring back to stock and lock bootloader and do a couple more tests and then send it for RMA or there's something else to try?

Thanks in advance!
[Google Pixel 8] badabing2003:
Nice puzzle.

Do the power off , put on charger overnight, but before you power it up, connect it to your PC and run this command

adb wait-for-device shell "su -c 'dmesg -T'"

Check the timestamps and see if there is a jump backwards or something abnormal.

But yeah if your device is under warranty, make it Google's problem, not yours.
[Google Pixel 8] guniens:
Thanks will try the command and keep you updated.

I would like to be extra sure before sending for RMA because is a pain in the ass lol.

Could be that boot and init_boot are different/patched differently and this causes my problem? As when I put on charge I get the unlocked bootloader warning.

That's the other difference with my previous P6.
[Google Pixel 8] badabing2003:
With P6 you patch boot, there is no init_boot

With P8, u have both, and you only patch init_boot, you don't patch boot (i hope you're not doing that)

When you have an unlocked bootloader, you get that message, no matter P6 or P8
[Google Pixel 8] guniens:
Yes, did everything in PF so everything right!

I was thinking about differences between boot and init_boot btw if any at all.
[Google Pixel 8] guniens:
Hi @badabing2003 here's the output command, hope I've got everything it's like 7k lines.

Don't really know what to look for.
[Google Pixel 8] badabing2003:
It shows that when you powered on, the time was

Mon Mar 18 07:40:37 2024

What was the actual time?
[Google Pixel 8] guniens:
No, it was 08:50 something

Btw I would like to fully format my phone but keep root, can I use the latest factory image, process and patch the boot image and flash to both slots erasing data too?
[Google Pixel 8] badabing2003:
Yes, after reboot, you need to install Magisk application it would say that it needs to complete setup, say there and you'd be rooted.

The difference appears to be 1 hr, sounds like timezone issue or dst issue.

Try this.

Keep auto sync off, manually set everything correctly and leave it at that.

See if it still falls behind.
[Google Pixel 8] guniens:
Yes, this time was 1h or so (maybe a little more) behind but last time I had the issue after power off-charge-power on I was maybe 30min behind.
[Google Pixel 8] badabing2003:
please submit support file, this is not enough for me to understand properly.
[Google Pixel 8] AggresiveSoldier:
Think should be it, on a diff note, i copied the .img file from downloads to my local system.

Then did a fastboot flash boot file.img and now my system is stuck in Fastboot mode.

Time to try and recover it;')

Edit: Factory image flashed to both slots and its booting again.

Still getting the same error about the kernel patching.
[Google Pixel 8] badabing2003:
Ok I see the issue.

Unlike Magisk, KernelSU always patches boot.img, and doesn't patch init_boot.img

I'll have to update PF to handle that.
[Google Pixel 8] AggresiveSoldier:
Awesome you seen what happens.

I'll wait for the PF update and will try again when done.
[Google Pixel 8] badabing2003:
New Release:

Mar 19, 2024 v6.8.4.0 change log:

When patching with KernelSu on devices that have init_boot partition, patch boot partition, not init_boot.

Added Dev Tools | keybox.xml validity checker (credit to @hldr4)

Extra Img Extraction setting now additionally extracts dtbo, vendor_boot, vendor_kernel_boot, super_empty (useful for some ROMs).

When custom patching, Paste button will automatically paste the path to the (extra) image type selected.

Improved logging.
[Google Pixel 8] AggresiveSoldier:
Thank you verry much, KernelSU shows as installed now in my device after redoing it with latest OTA file.

One little thing though, at the end it stated that its looking for Magisk APK package name, it obviously cant find that installed on the device.

The KernelSU program wasnt installed automaticly, i found the APK in the downloads folder though so its on the device, just not installed.

Manually installing ofcourse isnt a big problem.

Added new support file so you can have a look at what happened.
[Google Pixel 8] badabing2003:
Everything is looking good in termns of creating the patch and flashing, but PF doesn't see your device as rooted, probably because you have not granted su permissions to shell.

Which brings me to the next point.

I don't use KernelSu because my test devices don't support it, hence I don't know how one is supposed to manage the su permissions?

Are you still supposed to use Magisk Manager?

If so, just install it.

PF always checks to see if Magisk is installed, if it doesn't it just warns, you can ignore that message if you don't need Magisk, but if you do install it (you can do so from within PF as well)

When patching with Magisk, and Magisk is not found, PF installs it, but when patching with KernelSu, PF doesn't automatically install it, because as I said, I don't even know if it is required.

Although PF does download the latest Magisk to your PC to extract a component of it (magiskboot) to unpack / repack the boot.img with the KernelSu Image replacing the kernel within.
[Google Pixel 8] AggresiveSoldier:
That could be cause KSU works the other way around compared to Magisk.

Where with Magisk everything has root and you need to deny apps from root, with KSU nothing has root unless you grant root from the KSU manager.

So KSU doesnt use Magisk but has its own KSU Manager.

The KSU Manager APK file was in the downloads folder of the phone after flashing, so i could easy install the APK from there or just download it from the github.

The KSU manager APK file is in every release and is called in the following manner KernelSU_V0.x.x-xx-RandomNumbers-release.apk
[Google Pixel 8] badabing2003:
Ok thanks

I added an option to install the latest KernelSU manager from within PF.

It should be part of the next release.
[Google Pixel 8] badabing2003:
New Release:

Mar 26, 2024 v6.9.0.0 change log:

Add support for patching KernelSU LKM (Kernel modules, GKI only). This is in addition to the classic KernelSU support.

Add support for patching with APatch

Rename Install Magisk to Install Root App as it now supports directly installing KernelSU and Apatch through PixelFlasher.

Add Install ZygiskNext module option in Magisk tool options.

Use UTF-8 encoding for the logifile instead of ISO-8859-1

Miscellaneous minor improvements.
[Google Pixel 8] guniens:
Hi @badabing2003

I still didn't solve my problem, even flashed the stock boot image e locked the bootloader (now fully stock).

I've submitted a repair request and have a question, I've choosen connectivity problems and software problems as these were the best fitting problems to my situation, how do I explain the problem in detail?

Do I have to put a description in the RMA package?

Thanks in advance!
[Google Pixel 8] badabing2003:
Sorry I wouldn't know, I haven't done an RMA with Google since Nexus 6P days, and I don't recall that far back what I had to fill in.
[Google Pixel 8] guniens:
No prob! Thanks again for your help!
[Google Pixel 8] badabing2003:
New Release:

Apr 05, 2024 v6.9.1.0 change log:

#181 Handle KernelSU new output filename format.

#187 register exit menu id for MacOS to OS's "Exit" menu.

KernelSU bug fix and improvements.

Improved logging to further easy troubleshooting.

Update banned kernels list.

Update and re-add Magisk zygote64_32 canary with a forked URL.

Minor typo corrections and other improvements.
[Google Pixel 8] AggresiveSoldier:
Just tried to update my phone to the April update.

Downloaded the OTA from Google website, patched with KSU in PF and started update.

All flashing seemed fine but when it should have booted it couldnt, shortly saw a Google logo.

Then it rebooted again a couple of times to eventually state a screen the device cant boot and its possibly corrupted.

Device was running March version with KSU active before i started this.
[Google Pixel 8] Koeties:
I always download the OTA image via PixelFlasher itself (from the Device menu). Do everything from PF and you won't corrupt your phone.
[Google Pixel 8] badabing2003:
KSU might have been active, but you hadn't granted su rights to shell process.

Selected Device on 2024-04-09 08:44:06:
Device ID: REDACTED
Device Model: shiba
Device Active Slot: a
Device Mode: adb
Device Name: Pixel 8
Device First API Level: 34
Device Version End Date: October 2026
Device Secuity Update End Date: October 2027
Has init_boot partition: True
Device Bootloader Version: ripcurrent-14.4-11322024
Device is Rooted: False
Device Build: AP1A.240305.019.A1
Device API Level: 34
Android Version: 14
Android Name: Android 14
Android Codename: Upside Down Cake
Android Release Date: Q3 2023
Android Latest Update: Present
Device Architecture: arm64-v8a
Device Kernel: Linux localhost 5.15.131-android14-11-gdc5052c90a9a #1 SMP PREEMPT Thu Mar 21 08:31:58 UTC 2024 aarch64 Toybox
Device Kernel Version: 5.15
Device KMI: 5.15.131-android14
sys_oem_unlock_allowed: 1
ro.boot.flash.locked: 1
ro.boot.vbmeta.device_state: locked
ro.product.first_api_level: 34
ro.boot.veritymode: enforcing
ro.boot.verifiedbootstate: green
ro.secure: 1
ro.zygote: zygote64
ro.vendor.product.cpu.abilist: arm64-v8a
ro.vendor.product.cpu.abilist32:

Not that should cause any of what you experienced.

However without root, I can't tell what modules you might have had active, which could definitely cause a bootloop.

Looking at the logs, I don't see anything that went bad, so in terms for extraction, creating a patch and flashing, everything was smooth,

See, even the slot got switched from a to b which is a sign that ota flashing was all good.

Selected Device on 2024-04-09 08:54:45:
Device ID: REDACTED
Device Model: shiba
Device Active Slot: b
Device Mode: f.b
Device Name: Pixel 8
Device First API Level: 34
Device Version End Date: October 2026
Device Secuity Update End Date: October 2027
Has init_boot partition: True
Device Bootloader Version: ripcurrent-14.4-11403750
Device Unlocked: True
slot-retry-count:a:
slot-unbootable:a:
slot-successful:a:
slot-retry-count:b:
slot-unbootable:b:
slot-successful:b:

Getting current slot for device: REDACTED ...
Current slot: [b]
Comparing the current slot with the previous active slot ...
Current slot has changed, this is good.
Checking if the bootloader is unlocked ...
Bootloader is unlocked, continuing ...
Flashing patched boot ...

So we'd have to look at other factors.

First things first, let's try to isolate.

Are you still bootlooping? (ignore the corrupt message, that's harmless)

If not, what slot are you on?

Do you have root?

If yes, grant su permissions to PF, scan again

If you are still bootlooping, try to reboot to safe mode (key combo) and see if the system loads, if it does, it's a module issue, if it still doesn't, then try flashing stock boot into active slot.

If it does boot to system, it has to do with the patch.

Based on what you report back, we'll take next actions.

When you do all that, please create another support file, and while you're at it, enable the debug logging.
[Google Pixel 8] badabing2003:
Unrelated to the issue,

You can get corruption for various reasons.

Although it is convenient to download from within PF, it's not a necessity, what you have to pay attention to is the checksum (which could be a mismatch no matter how you download, in which case you have to download again)

In this case it was all good.

Firmware SHA-256: a6dc4599cb4242088d7c77348540107804788e7a9144b50845b753dd006ee065
Expected to match a6dc4599 in the firmware filename and did. This is good!