loader firmware request:boost moblie 2023 celero 5g plus (WTCELERO5G)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- embedded-iot
Research direction
The request is for a matching Qualcomm Firehose programmer and partition map files for the 2023 Wingtech Celero 5G Plus (WTCELERO5G, Snapdragon 695). Start by checking the repository’s loader inventory for that device or chipset and compare any candidate against the requested model. Done means locating a matching factory package or confirming that none is available in the repository.
Written by the indexing model from the issue text.
Description
Hello everyone,
I am looking for a clean, factory stock firmware package (Stock ROM) for the original 2023 Celero 5G Plus to recover a soft-bricked device currently sitting in EDL mode. Here are the exact device specifications: * Marketing Name: 2023 Boost Celero 5G" Plus" . just to clarify the regular size Celero 5g (non plus) & both 2024 Celero 3 5g reg & plus size those are mediatek processors and will not work for this phone ) * Manufacturer/OEM: Wingtech * Device Code Name: WTCELERO5G * Chipset: Qualcomm Snapdragon 695 5G (SM6375) * Current State: Device is responsive in Emergency Download Mode (Qualcomm HS-USB QDLoader 9008 on COM1). What I specifically need from the package: * The matching Qualcomm Firehose Programmer (.elf / .mbn file) compatible with this Wingtech build. * The corresponding XML partition maps (rawprogram0.xml and patch0.xml) to use with QFIL/emmcdl. If anyone has a mirror link to this factory archive or a working dump, it would be immensely appreciated. Thank you!
kind regards,
lumber buck
- Dominant language
- Python
- Stars
- 555
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bkerler/Loaders
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ida-arbeitszeit/workers-control#1578 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aws-samples/sample-per-model-bedrock#898 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
intake mcp-intake needs-human-review priority:high
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Ikalus1988/MisakaNet#5041 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100