Keys request for XT2513-1 Kansas TMO Android 16

[paulfostersou-lgtm]

Dvice info:

• Model: XT2513-1 (Kansas)
• Carrier: TMO
• Chip: MT6835
• FRP state: protected (255)
• securestate: oem_locked
• serialno: ZT4222ZD26
• uid: 49288D3628436550000000000000
• chipid[0]: 06D6E22C316AC3DD562F96319E44B02720DF7176FF7E3EF8
• chipid[1]: 490F7875E1087FCF

Official unlock data:
3A25578300186178#5A54343232325A
443236006D6F746F2067200000#5229
1D2C46A3AAAD170332B8AAC50EB6A11
832001C47E053EC377868B11CEA4B#4
9288D36284365500000000000000000

Version question:
I used the one-line installer and got v2.0.0. The repo front page / README advertises v3.0.0 (with new Motorola/Kansas support). Why is v2.0 still what installs when v3.0 is shown as current?

Please provide the correct keys (for v2.0.0 or v3.0.0) so I can run the tool on this device.
Happy to send any extra fastboot output if needed.

Thanks!
@anonantics

[github-actions]

💡 Feature Request Received

Thanks @paulfostersou-lgtm for the suggestion!

📝 To help evaluate this, please add:

• Use case: Why do you need this?
• Examples: How would it work?
• Benefits: How does it improve the project?

---

🤖 NullSec Auto-Fix Bot

[github-actions]

👋 Thanks for the suggestion, @paulfostersou-lgtm!

I love hearing ideas from users! ✨

📋 To Help Evaluate:

1. Use Case: What problem does this solve?
2. Current Workaround: How do you handle this now?
3. Priority: Is this blocking your workflow?

Thanks for helping improve NullSec! 💪

---

🤖 NullSec Bot

[github-actions]

👋 Hey @paulfostersou-lgtm! Thanks for the feature suggestion!

I appreciate you taking the time to share your ideas. To help evaluate this:

• Use case: How would this feature help you?
• Priority: Is this blocking your workflow?
• Alternatives: Have you tried any workarounds?

I'll review this and let you know my thoughts! ✨

---

🤖 NullSec Bot