Restore disable_configstore, EuiccDisabler and thermal CDEV guards, branding and rebuild/sync helpers; document device roles, laptop migration, and Gitea. Co-authored-by: Cursor <cursoragent@cursor.com>
2.7 KiB
Status: parallel KernelSU / SusFS track (kept). Bridge to current Magisk ROM:
007-parallel-on-009.md. Magisk ship resume:009-handoff-20261008.md.
Debug boot — freeze on panic (photo / dump)
Normal sunfish kernel: CONFIG_PANIC_TIMEOUT=5 + often
CONFIG_QCOM_FORCE_WDOG_BITE_ON_PANIC → reboot in seconds. Console is
UART only (console=ttyMSM0); # CONFIG_VT is not set → no Oops text
on the phone display (you only see the Google logo loop).
What a “debug boot” must include (owner)
For a useful photo, both are required — freeze alone is not enough:
- Freeze:
CONFIG_PANIC_TIMEOUT=0+ cmdlinepanic=0; disableCONFIG_QCOM_FORCE_WDOG_BITE_ON_PANICso it does not reboot in 5s. - On-screen console:
CONFIG_VT+CONFIG_FRAMEBUFFER_CONSOLE(+console=tty0in cmdline). Without this, you only see the Google logo.
| Goal | Mechanism | Photo-able? |
|---|---|---|
| Stop reboot loop | panic=0 / PANIC_TIMEOUT=0, no wdog-bite-on-panic |
Logo freezes only |
| Oops on screen | VT + FRAMEBUFFER_CONSOLE + console=tty0 |
Yes if panic after FB; early may still be logo |
| Dump after hang | Freeze + penúltimo + immediate klog/logfs dd |
Not a photo |
Use only on LAB, SusFS/debug trials. Never ship as daily boot. Next SusFS debug build after the sigfix trial must enable both.
Host recipe (LAB SusFS debug boot)
- Defconfig fragment (or temporary edits) on
rom-dev01:
CONFIG_PANIC_TIMEOUT=0
# CONFIG_QCOM_FORCE_WDOG_BITE_ON_PANIC is not set
# optional on-screen console (experimental on Pixel 4.14):
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
-
Cmdline (device tree or unpack/repack boot): add
panic=0and optionallyconsole=tty0. Prefer a vendor_sunfish / BoardConfig override gated by a make var (e.g.SUNFISH_KERNEL_PANIC_DEBUG=1) so normal bacon stays clean. -
Build
bootimage, name artifactboot-resukisu-susfs-DEBUG-YYYYMMDDTHHMMSSZ.img. -
Flash only to
boot_b; keep penúltimo onboot_a. On hang: photo if text appears; Vol−+Power →--set-active=a.
Capture order (always)
- Panic / hang on SusFS (debug) slot
- Fastboot before Android success on good slot
- Then penúltimo + immediate
ddofklog/logfs(4a has nofastboot fetch)
Status
Documented 2026-09-16 after SusFS early kernel_panic with empty Oops in klog.
Sigfix rebuild may already address root cause; keep this recipe for the next
opaque bootloop.