Reverse Engineered Chromebook SOF Audio support for Google MAX98373 & Nuvoton 88L25

https://github.com/isaiahscape/cros-sofaudio/releases/latest

Thanks to @3kierz for helping me out, specially to @coolstar who made this driver possible.

👨🏻‍💻 @agamtechtricks

https://music.apple.com/us/jfdsalkfavsd

apple knows ball

👨🏻‍💻 @agamtechtricks x @attmemes

👨🏻‍💻 @agamtechtricks x @attmemes

Good morning everynyan, Welcome to the Appl—

Horse horse horse horse horse installing my horse how it feels to cook yummy food la la la la la la la la la la la pi pi pi pi pi pi pi pi pi la la la la la la la la la la la la la la pi pi pi pi pi pi pi pi pi pi pi la la la la la la la more not gacha games review to come

The article "Recovering a Titan" from helluvaOS Red Winter Hunt Unit (TSNII Labs) covers the inner workings, failure states, and low-level rescue protocol for Google's hardware security chip (GSC / Titan M2/M3 / Dauntless / Epic) found on Pixel devices. It introduces Perlica, an in-house Rust CLI designed to parse, plan, and execute firmware recovery.

The Problem (Silent "NOS Production Error")
When a Pixel's GSC Read-Write (RW) firmware becomes corrupted, the device enters a hard-to-diagnose bricked state. The bootloader still responds and displays Secure boot: PRODUCTION, but shows NOS production: error! (Nugget OS failure). Because the GSC serves as the hardware root of trust, the phone cannot boot.

Google's Hidden OEM Rescue Protocol
The chip communicates with the host over SPI using undocumented fastboot OEM commands rather than standard flash commands:

fastboot oem gsc: Pings the security chip (10-second timeout).
fastboot oem gsc version: Queries the logical partition layout and version strings.
fastboot oem "gsc header RO_A" (or RO_B, RW_A, RW_B): Inspects per-partition headers.
fastboot oem gsc rescue & fastboot flash gsc <bin>: Triggers the recovery pipeline and streams firmware.
fastboot oem gsc sjtag-cfg: Checks hardware JTAG status (locked to internal Google debug units).

Partition Structure & Verification

GSC uses an A/B partition scheme with two Read-Only banks (RO_A, RO_B) and two Read-Write banks (RW_A, RW_B).
If RW_A is unselected, missing its status marker, or reports no parsed version, the device enters a degraded state requiring a "pure rescue."
Firmware rescue frames require strict SHA-256 integrity checks; an unacknowledged or mismatched frame stalls the transmission.
Very old RO firmware marked with /spil_ requires intermediate transitional images before accepting current firmware.

Next-Gen Hardware Insights
• The article notes differences in newer payloads (such as Epic / Longjing chips intended for later Pixel hardware):
The manifest is structured as a binary struct at a fixed 64 KB offset (half that of Dauntless).
• Payloads are larger (~344 KB vs. 258 KB on earlier chips) and do not use traditional framed rescue payloads or standard anti-rollback counters.

What Perlica Does
Rather than blindly sending byte streams or relying on Google's proprietary web-based flasher, Perlica provides a deterministic CLI pipeline:
• Inspect: Reads partition tables and slot headers.
• Plan: Evaluates slot status, rollback states, and required intermediate stages.
• Execute: Streams rescue frames with SHA-256 checks.
• Verify: Queries partition receipts post-flash to confirm the chip has cleanly switched to an active, valid RW state.

👨🏻‍💻 @agamtechtricks

What the fuck Instagram?

Last night, I suddenly got the 'verify if you're a human' prompt where I had to take a video selfie, and now my account is disabled.

Is there any way to get it back?

made a new account on a new device, with a new number and new email id

amazing experience