2025071900 - Pixel 7 - Corrupt GZIP trailer

GrapheneOS

jsdude It sounds like the device has a faulty CPU cache or memory corrupting data. We've double checked that nothing is wrong with any of the update servers. We have 3 update servers to cover different parts of the world so you're downloading from a specific one based on your location. Does not appear anything is wrong with any of the servers and we have no other reports of issues. In particular, you're getting an error about corrupt data from TLS which indicates that it's being corrupted in memory or cache.

jsdude

I also got the error through the Web Installer and command line after I verified the download. Definitely does not sould like an infrastructure issue.

jsdude

I re-installed factory OS and it definitely has issues. Small downloads worked ok but tried to install anything with a decent size, I can see that the download percentage bouncing around as it tries to download and it eventually fails. Probably retrying chunks as it gets checksum errors when it hits its the bad memory sectors.

de0u

jsdude I re-installed factory OS and it definitely has issues.

That's pretty conclusive, I'm afraid.

andrej567

3 year old hardware malfunctioning.. good to know.. I would assume it should last 5y.. hah.. old i am.

I have 2y, 2m

de0u

andrej567 There isn't a mechanism by which all devices of the same model break after exactly the same amount of time. Some run longer than others, so some run shorter.

And flash storage absolutely wears out faster when more things are written/rewritten. Lots of electronics break sooner if they are run hotter. Batteries fail sooner if they are run to exhaustion more often.

andrej567

de0u sure
I just have to remember this and not be surprised once it happens..
that such failures exist and its not ohhh ehh I installed new OS version and the guys broke the OS again.

de0u

andrej567 I just have to remember this and not be surprised once it happens..
that such failures exist and its not ohhh ehh I installed new OS version and the guys broke the OS again.

🙂🙂🙂🙂🙂

jsdude

This reminds me of debugging an Alpha BlackBerry Storm (yikes!) way back in the day with a memory issue, albeit was a bad microsd, but it still presented itself in very strange ways.

This Pixel issue is the first time I ever experienced an internal memory/cache issue on any device.

Blank

de0u Hello, glad you talked about that. Juste a Quick question. I know the screen allows us to check the signature of GraphenOs through their Website, is that right ? At least I always proceeded so... But does the Yellow screen also confirm that the bootloader has been relocked, as expected ?

de0u

__Blank__ But does the Yellow screen also confirm that the bootloader has been relocked, as expected ?

I don't think so. I believe "fastboot mode" displays that status, and the setup wizard encourages locking the bootloader, but I don't think that status is reported on every boot.

Blank

de0u okay, thanks. Otherwise I think it is possible to check the boatloader status through the auditor App, even though I don't now the display name of that status 😅