Honor Scale 2 (LUP-B19 / N001): CAK/C1/C2?

[FaZios]

Honor Scale 2 (LUP-B19 / smart product id N001) — CAK/C1/C2

First, thanks for the Huawei Hagrid WSP work in #1408 — the handler already
recognises my scale: productProfileForMarker maps "N001", "LUP-B19", "LUPIN-B19HN" to HONOR_SCALE_2.

The blocker is the three product secrets. As documented, the driver stays in
probe-only mode without CAK, C1 and C2 (32 hex each), and the code intentionally
contains no Huawei Health key-extraction logic.

I verified my understanding of the derivation against the Scale 3 PoC vector in
HuaweiHagridWspLibTest — deriveHagridRootKey(C1, C2, C3-from-MAC) reproduces
the documented d680f0f3... root key. So the algorithm side is clear; I only
lack the LUP-B19 constants.

Questions:

1. Are the CAK/C1/C2 for the Honor Scale 2 (LUP-B19) already known /
   shareable? They should be per-model constants, identical across units.
2. If not, how did you obtain the Scale 3 values — runtime hook on Huawei
   Health, static extraction, something else? A pointer to the method would let
   me capture the LUP-B19 set myself and contribute it back.

Happy to run captures on my own device and open a follow-up PR with the values

• a PoC vector for the LUP-B19, same shape as the existing Scale 3 test.

[oliexdev]

1. No. openScale holds no CAK/C1/C2 for any model — not for the Scale 2 Pro, Scale 3, Scale 3 Pro or the LUP-B19. Neither Add minimal Huawei Hagrid WSP support #1408 nor Add huawei scale 3 support #1474 shipped values, and the handler and lib are deliberately free of them. The secrets stay user-supplied through the per-driver settings, and I don't intend to change that.

2. I can't point you at a method — the Hagrid work came from contributors and I never handled the extraction side. The extraction path is deliberately not documented anywhere in this project, and I'd like to leave it at that. I'd also rather not have this turn into a how-to thread here. Thanks.