Add verified Sharp AQUOS R8 SH-R80 5.15.178 profile

[stupidgiraffe]

Target

Sharp AQUOS R8 SH-R80 (FaYuiry), build SC525 / 04.00.00.

Kernel:
5.15.178-android13-8-00025-g7feb0b0b7cd8-ab14134651

Google GKI provenance:

• Android common commit 7feb0b0b7cd82204ae4d1515e8a3cc3fc9f03529
• Android CI build 14134651
• kernel_aarch64

Physical-device validation

The profile has completed two successful direct/base-mode exploit runs on the physical SH-R80 using fixed CPU pair 3,4.

Observed successful stages included:

• W2 credential escalation to UID 0
• W3 seccomp bypass
• clean multicast route completion
• official KernelSU Android13-5.15 late-load handoff on the later run

recommend_shizuku = 0 because direct mode was the successful/reliable path on this target. An earlier Shizuku/UserService run disconnected after W1.

Extraction note

The extractor's embedded-symbol recovery initially mapped remove_waiter incorrectly and produced a false fixed-kernel result. Supplying the matching Google CI System.map resolved remove_waiter at 0x176d6e0 relative to _text; the extractor then reported the CVE-2026-43499 primitive present and selected multicast_waiter.

This PR only adds the verified profile + index entry; it intentionally does not guess at an extractor fix.

Device-specific notes and reproducibility guard live at: https://github.com/stupidgiraffe/aquos-r8-ghostlock