yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] p3y0t3:
I have two of these phones. One is soft bricked\stuck on startup animation thanks to kingroot, the other is qdload bricked after flashing a homebrew twrp recovery. The soft bricked one can go into recovery, plus while its attempting to boot it enables a usb interface with the hardware id of USB\VID_1EBF&PID_707D&REV_0310. Urm anyhow, I am 99.9% sure this phone can be debricked using the qualcomm sd card method. Just for kicks I tried booting the qdload phone with a samsung debrick sd card, and it WANTS to work however the locked bootloader prevents it from loading. I have most all of the partitions backed up from the soft bricked phone.. If I could get my hands on a complete system image I could almost assuredly fix the qdload phone. If someone has a complete image, hook a brother up!
[Android Q&A, Help & Troubleshooting] Impr0ve:
Anybody still working on this?

I have my phone in a stuck condition I had the same coolpad catalyst 3622a it's stuck on the metropcs screen when trying to start I had it rooted no problem but tried installing a different SU app and now its stuck please help with this and thanks for all your good work so far :)
[Android Q&A, Help & Troubleshooting] Impr0ve:
This thread need some attention

please say y'all are still pursuing this quest I really would love my phone to work again if anybody still working on it or already has a solution please post a reply sorry for bugging you guys :eek:
[Android Q&A, Help & Troubleshooting] sikkinixx:
Coolpad 3622a

Can you zip your dump file or whatever you used to fix your Coolpad please. And post a link please you would make me and alot of people happy.. thank you.
[Android Q&A, Help & Troubleshooting] Saert:
It would be great indeed, i have one device is stuck on bootscreen after rooting
[Android Q&A, Help & Troubleshooting] brandonabandon:
Did you unlock the BL?
[Android Q&A, Help & Troubleshooting] Saert:
Oh this device needs to open the bootloader didn't knew that.
[Android Q&A, Help & Troubleshooting] RCALL:
You have a Coolpad 3622a complete firmware on Dropbox for everyone to use, yet I can't find the link anywhere, unless I missed it?
[Android Q&A, Help & Troubleshooting] alexxxbaby24:
if you end up creating an update.zip file or custom recovery or even just the image file, email it to me bivensalexia@gmail.com please....very much appreciated.. i have a catalyst that i rooted with kingoroot then accidentally updated the firmware...soft bricking it. i have no idea how to recover it without custom recovery or a stock rom . please help !
[Android Q&A, Help & Troubleshooting] Yinxo16:
hey guys here its a software to unbrick the coolpad 3622a metro pcs, credits to the creator. https://drive.google.com/file/d/0Byi69Jpw2ZDtWEpNVm1UUjI3X2s/view
[Android Q&A, Help & Troubleshooting] p3y0t3:
Ok, so after quite literally months of searching, I believed I had found a working 3622a rom. Twas on a spanish forum, and claimed to be a coolpad catalyst 3622a metro pcs rom. And to be honest, it LOOKS like it would work. Its a marshmallow based rom, definitely for a 8909 based handset... Check it out: h**ps://drive.google.com/file/d/0Byi69Jpw2ZDtWEpNVm1UUjI3X2s/view

dOh didnt see above post
[Android Q&A, Help & Troubleshooting] p3y0t3:
Its looking like the above mentioned rom probably isnt the answer we are seeking. I brought over the above roms' sbl1, aboot, rpm and tz to my unbrick image, and the bootloader pukes on it. Back to the drawing board.
[Android Q&A, Help & Troubleshooting] p3y0t3:
If anyone would like to mess around with emmcdl and a 8909 singleimage file, they are attached to this post. I was able to initialize the emmc with this singleimage... Give her a whirl maybe you'll get lucky. =)
[Android Q&A, Help & Troubleshooting] p3y0t3:
This may or may not be of any assistance to hard bricked catalyst owners... You can get into fastboot on these devices by pulling the battery, holding down volume up, then plugging the device into USB with volume up still held in. It seems as though these phones ship with an overly crippled fastboot however...
[Android Q&A, Help & Troubleshooting] brandonabandon:
I got Xposed working this device. Enough thanks for this post I will write a thread.
[Android Q&A, Help & Troubleshooting] tpacino:
Thanks I've been looking everywhere for this you are a savior
[Android Q&A, Help & Troubleshooting] BookCase:
Have a look at THIS thread. You might find your answers there or be able to assist in finding a solution. I wonder if we can get these 2 threads merged together.
[Android Q&A, Help & Troubleshooting] BookCase:
Please share how you revived your device, I have been at this for days and cannot figure it out. I would be very grateful.

I have put together a package from files others have shared in different threads, as well as this thread and other places on the internet. In it is the drivers needed to connect our device to Windows computers, as well as the latest YGDP tool to flash firmware to our phone, a .CPB firmware image file that was shared on another thread HERE, the dump files of that .CPB image and the dump files from "Wiko_FREDDY_V8_Marshmallow" which was shared HERE.

That package can be found HERE.

I have compressed the file with WinRar which is required to decompress it and can be obtained HERE.

I have tried flashing the .CPB image alone and have tried replacing the dump files from the .CPB image with ones from "Wiko_FREDDY_V8_Marshmallow", to no avail.

Perhaps someone here can give this a shot with what I have attained so far or try other methods and share your findings.
[Android Q&A, Help & Troubleshooting] ewokmojo:
How did you install xposed? What version? Did you use FlashFire? What settings dud you use? I rooted the phone with Kingroot- though BookCase, who linked your post, told me I needed to root with Kingo root. We will see if this was a problem or not... Thank you.
[Android Q&A, Help & Troubleshooting] brandonabandon:
To thank a post, we click the thumbs up icon. No matter, I see there is a demand for development here this device. Sry. I don't mean to hijack this thred, I believe our intentions are similar. Anyhow, I'm not writing a new thread for Xposed installation. 776422 threads exist and it took 5 mins of googling and 10-15 mins of actual "labor" to accomplish installation. Yes, you must use flashfire. But before you can use the app you need chainfires SuperSU as the flashfire app is picky. https://missingtricks.net/replace-kingroot-kinguser-with-supersu-superuser-android-guide/ following this guide you will complete the task. I will up the zip I used also. FYI the remove kingoroot APP does not work it just flakes/hangs. You must install terminal app and follow the directions. I have the current v87 framework installed and have no issue with any module. I HIGHLY recommend installing amplify module. You will see a major difference in battery life especially this device. Gl.
[Android Q&A, Help & Troubleshooting] p3y0t3:
Well many thanx out to BookCase for posting the link that contained the 3622a CPB file. Worked like a charm. However, the included version of the yulong downloader didnt work for me; I already had the v5 of it, which doesnt require a pw and worked as advertised. Many thanks again!
[Android Q&A, Help & Troubleshooting] p3y0t3:
So Ive got to spend some quality time with my catalyst over the last 24hrs, and am well on my way to having a working twrp on it. I dont know how common of knowledge this is, but to unlock the bootloader on this phone, do this:

1) Enable developer options from within android. If you dont already know how to do this go no further!

2) In developer options, enable OEM Unlockin

3) Restart the phone in bootloader mode. IE: either issue a adb reboot-bootloader command or boot into recovery and choose to reboot to bootloader from there.

4) Once in bootloader\fastboot mode, issue the command: fastboot -i 0x1ebf oem unlock-go

THIS WILL WIPE YOUR DEVICE!
[Android Q&A, Help & Troubleshooting] p3y0t3:
Ive taken the above linked CPB file, extracted it and went through the motions with emmcdl. Ive done this procedure no less than 10 times in 24hours, so I know it *works*. Anyhow, Ive archived it and put it up on drive if anyone wants to give it a whirl. Basic instructions are given when you run the rar SFX. This is totally meant to be done in EDL\9008 mode.. You WILL LOSE EVERYTHING!

https://drive.google.com/drive/folders/0B-QlOqkZBs8GWWxMWDk0UVdIY1E?usp=sharing
[Android Q&A, Help & Troubleshooting] Alixbot:
Hey everyone. Here's a package I put together to change Kingroot to SuperSu in a couple easy steps.

SuCat.zip

Also I have extracted the rooted system.img file. If anyone knows how I can flash it to the phone that's gonna help me out a lot since I was really tired one night and accidentally deleted a lot of system files in one of my catalysts instead of replacing the one file I needed to and I bricked my phone. You can find that image file here.

Fastboot won't connect for me yet and adb gives me permission errors. I could really use some help here.
[Android Q&A, Help & Troubleshooting] Alixbot:
I'm having issues even doing that. Adb works and fastboot is completely hopeless. My computer doesn't even see it in Linux.

If anyone can help me figure out how to fix fast boot with this phone I have made a TWRP for this device I could test once I can fast boot flash.

---------- Post added at 01:34 AM ---------- Previous post was at 01:24 AM ----------

Hey man. Any idea how I can get fast boot to work? I got a twrp made. Fast boot no see my phone though and I figured you know what you're doing so any help? I even tried the USB fastboot method and windows not seeing it.
[Android Q&A, Help & Troubleshooting] p3y0t3:
Ok, so you've tried the trick with pulling the battery out, LEAVING the battery out, holding down the volume up button then with button held down plugging in the usb cable? Understand also that this phones fastboot is neutered until you OEM unlock it. If you cant get into the device settings to toggle the OEM unlock option, fastboot will do you no good.

1) Enable developer options from within android. If you dont already know how to do this go no further!

2) In developer options, enable OEM Unlockin

3) Restart the phone in bootloader mode. IE: either issue a adb reboot-bootloader command or boot into recovery and choose to reboot to bootloader from there.

4) Once in bootloader\fastboot mode, issue the command: fastboot -i 0x1ebf oem unlock-go
[Android Q&A, Help & Troubleshooting] BookCase:
I can't boot into the OS whatsoever. Is there no other way?
[Android Q&A, Help & Troubleshooting] p3y0t3:
Well yes, you could make a quick and dirty qdload cable out of a spare micro usb cable, force the phone into 9008 mode, download the coolpad catalyst rom and flash it. https://drive.google.com/open?id=0B-QlOqkZBs8GWWxMWDk0UVdIY1E has the rom archived with basic instructions on making the cable when the winrar self extracting rar is ran. After flash, go in and enable bootloader unlocking, unlock it, go to town.
[Android Q&A, Help & Troubleshooting] Seeking info:
Need help with flashing tool

I have stock Rom, but windows 10 doesn't recognize it when using ygpd flashing tool. Any help is

Email: monsterdrink82@gmail.com
[Android Q&A, Help & Troubleshooting] lehmancurtis:
I'm also having issues with the 9008 device state. I'm able to change states through the use of Qualcomm's QPST program. However, much of the program is above my pay-grade. Trying to combo QPST with YGDP manually, and it seem even more futile than the attempt to cut corners that landed me in this state in the first place.
[Android Q&A, Help & Troubleshooting] j.scig980:
command prompt help

im trying to unbrick my catalyst. ive downloaded all the firmware files from the google drive link. i made the cable. my pc shows the QDloader in device manager but i dont know what to do next. i read the instructions that showed up when i extracted the .rar files but i need someone to walk me thru all the command prompt stuff. proper syntax and all that jazz. id really appreciate it. the suspense of being on the brink of finally accomplishing this is killing me and its quite frustrating all that now stands in my way is my own lack of knowledge regarding what i assume are pretty basic and elementary commands. please help. also if some good Samaritan is willing to just text me that way im notified immediately and its at the convenience of the outstanding helpful individual who (hopefully) comes to my aide. 8019414227 anytime ill drop whatever i may be doing. btw i know my way around a computer a little better than the standard "i-only-use-my-computer-for-youtube-facebook) user so it should be slightly easier and faster than teaching algebra to a toddler.
[Android Q&A, Help & Troubleshooting] Falc0net:
It works fine!! Thanks

Just use YGDP tool and password is 9527, then turn off the phone and hold volume + then again hit volume up and start flashing on YGDP.

Works perfect for the T-mobile version.
[Android Q&A, Help & Troubleshooting] lehmancurtis:
Does anyone have an eMMC backup of this device?
[Android Q&A, Help & Troubleshooting] lehmancurtis:
FINALLY!!! I recovered from Qdloader_9008, bricked with black screen and no sign of life. The key for me was the file UserConfig.xml. I also stumbled upon a QFIL firmware. Added the previously mentioned XML, ran one command (with the "chop-shop" qdloader cable I learned about from this amazing forum), and did some basic debugging. I left the connections shorted during the flash with the battery removed. More to follow with links and credit to the source. Thanks to everyone for the knowledge shared and for the questions that generated them.
[Android Q&A, Help & Troubleshooting] lehmancurtis:
Just in case it hasn't been mentioned, adb and fastboot are basically useless when the device can't boot into any version of the OS. On this device (and all the MSM8909 SoC's I've encountered) use Qualcomm's edl (emergency download mode) this state. If you use emmcdl.exe to flash rawprogram0.xml you will regain adb, fastboot, And most functionality. It's buggy at that point though.
[Android Q&A, Help & Troubleshooting] Impr0ve:
can anybody help me unbrick my phone please I'm having a hard time understanding how to do this thank you
[Android Q&A, Help & Troubleshooting] Impr0ve:
I Downloaded all that stuff and I can't get QFIL to recognize my device and I installed the Qualcomm drivers as well but when I look in the device manager I see in the list Android under other devices tab with ? and caution sybol
[Android Q&A, Help & Troubleshooting] lehmancurtis:
I've put together a twrp recovery for this phone. It flashes and boots fine, but I can't get touch working. Any advice?
[Android Q&A, Help & Troubleshooting] EnderDev:
Coolpad 3622a

Have you tried ditching touch functionality all together? Personally I wouldnt care wether or not twrp had touch Id just care about if you can use the volume buttons to navigate :D
[Android Q&A, Help & Troubleshooting] lehmancurtis:
Volume buttons are not functioning properly either. Command line works great. I just used it and the normal boot ui to install SuperSU. Flashes and wipes fine. I would love to have a more user friendly experience though lol.
[Android Q&A, Help & Troubleshooting] EnderDev:
Coolpad 3622a

Didnt know those were borked also. :D

Im in the middle of somehow using QFIL(or something like it) and automating it to reinstall the rom and use a pre-rooted system image.

Will post status later.
[Android Q&A, Help & Troubleshooting] lehmancurtis:
Use Qpst first so you don't have as many issues with Sha (it's sha1).

Edl bypasses the avb check on these but still seems to backfire later.
[Android Q&A, Help & Troubleshooting] EnderDev:
Coolpad 3622a

Thanks ill do that!

Also does anyone know how to make it showup in the comports list?

Ive installed drivers for the phone and qualcomm drivers but alas I cannot find it.

Thanks for your help.
[Android Q&A, Help & Troubleshooting] lehmancurtis:
Method A)

Remove the battery, press and hold vol+&pwr, plug the device into the computer, countinue holding vol+&pwr for about 30 seconds (or until your comport shows up), once you establish connection, replace your battery (that's the tricky part due to the construction of the battery cover/needed buttons).

Method B)

Depending on the state of functioning your device is in, some times you can wait until last to plug the device into the computer and press and hold vol+& pwr until the edl rests (about 30 seconds) and the COM port will be visible in at least the device manager. Then you can get the number from properties and plug it into qfil.

#As a side note, I had greater success with emmcdl.exe.
[Android Q&A, Help & Troubleshooting] lehmancurtis:
Anyone else have the dual SIM option on this phone? Check out the upper right corner of my screenshot.
[Android Q&A, Help & Troubleshooting] lehmancurtis:
Now I have these options in settings. (I don't know if this is usful or just strange)

**I discovered the dual SIM bug was because of improper build.prop setting
[Android Q&A, Help & Troubleshooting] EnderDev:
Coolpad 3622a

Thanks, will attempt but the plastic spacers on my volume buttons wound up breaking off so I have to use something else:silly:

---------- Post added at 09:00 PM ---------- Previous post was at 08:53 PM ----------

May be that most chinese manufacturers make a single rom for a specific processor.

So that might just be a bug because the rom has built in dual sim functionality and somehow it thinks that your phone has two sims.

---------- Post added at 09:25 PM ---------- Previous post was at 09:00 PM ----------

d'Oh:p

I had a coolpad development driver installed that took over the qualcomm ports data.

Driver is Qualcomm Diagnostics Interface 3197.
[Android Q&A, Help & Troubleshooting] lehmancurtis:
Here is a link to what I have so far (NOT COMPLETELY FUNCTIONAL YET). This twrp recovery.img will boot and load without crashing and allows twrp flashing via adb shell and functions found in the twres/ folder. Hopefully someone can help me by adding the touchscreen functionality.

https://drive.google.com/file/d/1soQ4jrIwlQDYF5ITJmtbhdEBUz_rrd6I/view?usp=drivesdk
[Android Q&A, Help & Troubleshooting] EnderDev:
Coolpad 3622a

Awesome! Unfortunately though the usb jack broke off, a replacement is expected in the mail.

Also, im not rom wizard but is there perhaps a way to reverse engineer the stock rom(system.img I think) and find how it handles volume buttons and touchscreen?
[Android Q&A, Help & Troubleshooting] lehmancurtis:
I that info but haven't been able to manipulate the recovery partition in such a way that the permissions are passed to it in the form of recovery_as_boot. Boot is dev/block/by-number/mmsblk0p24 and recovery is allocated the same exact partition size and is located at mmsblk0p29, I believe system is mmsblk0p26. The permission files are in either /d or /data . Drivers and other hardware specific firmware lives in the /sys folder rather than /system. I think the issue is in sys/class/input/input ( 0-9). There are around 8 numbered input folders. One contains a name something like Ftxblahts not sure what is actually in place of the blah but one of it's parameters is set to 1,0 I believe replacing the 0 with a 1 will fix everything . I just haven't been able to successfully gain enough permission to write to the file.
[Android Q&A, Help & Troubleshooting] Josephdbrewer25:
Can someone help? I have seemed to have got my Coolpad stuck. Goes straight to download and install. Won't boot. The only way my PC sees it is after I press the vol up button but it's then shows up as unknown device..I'm so confused.

Here's my email Josephdbrewer25@gmail.com
[Android Q&A, Help & Troubleshooting] lehmancurtis:
You need fastboot _(minimal adb and fastboot will be fine). You also need to download and install the Qualcomm bootloader drivers. (Restart your machine after installing the drivers). If you have access to fastboot it makes things easier. Search the xda forums for the stock ROM (easy to find and download).

Unzip the stock ROM file. Find the folder containing fastboot.exe, and copy these files from the ROM to your fastboot folder: system.img, recovery.img, and boot.img

* Many time reflashing just the system.img will do, but not always.

From your fastboot folder press shift+right-click and select option to launch command prompt.

First unlock your bootloader

fastboot oem unlock-go --wipe

reboot

fastboot reboot

*Press and hold the volume + button while reboot to re-enter fastboot.

If you want to remove frp protect (optional).

fastboot erase config

Flash system partition

fastboot -w flash system ./system.img

after completion, reboot again.

Flash boot partition

fastboot flash boot ./boot.img

reboot

Flash recovery partition

fastboot flash recovery ./recovery.img

Hope this helps.
[Android Q&A, Help & Troubleshooting] Josephdbrewer25:
Thanks for your reply, I couldn't get fastboot to find the phone so I eventually got it into emergency download mode. But it fails at flashing
[Android Q&A, Help & Troubleshooting] lehmancurtis:
*AS A PRECAUTION REMOVE ANY REMOVABLE CARDS.

Search for emmcdl.exe with search plus. You still have to use qcom drivers. You will need to put the program in your rom folder. Open cmd in your ROM folder. I shared the command used to flash rawprogram0.xml. I haven't used it in a while but it's something like ...

emmcdl.exe -p (name of your COM port eg COM3) -f {name-of-firehose-program) -x rawprogram0.xml

*Replace (name-of-firehose-program) with the name of the one in your ROM folder. Be sure to leave off the ().

*You may loose you imei number, but will regain function of device. (I'm trying to figure out how to restore the imei and will update when a solution is found and tested).
[Android Q&A, Help & Troubleshooting] Josephdbrewer25:
Just one issue. Says image load failed with status:0

Warning: Flash programmer failed to load trying to continue

Then it's got some weird looking symbol and it hangs for awhile then says failed, device not ready
[Android Q&A, Help & Troubleshooting] lehmancurtis:
I forgot one detail. Type in your code but before you press enter you need to prepare the device. You have two options: one remove the battery for 5-10 seconds, replace the battery without pressing anything, plug the device into your computer (you have roughly 5-10 seconds from here to next step), and finally enter the code to flash. Two with device connected , press and hold volume+ & power for about 30 seconds (until edl resets) then enter cmd.

*The error ending with trying to continue is normal. After that's displayed, it should run a great deal of code on it's own and device should self boot.
[Android Q&A, Help & Troubleshooting] Josephdbrewer25:
Alright. I did see it do some weird stuff. Something about sparse image. I'm noob when it comes to the Coolpad. I mainly deal with Moto/Lenovo devices

Quick question, how long does it take? I ask because it just stops and hangs there. Like I said before, something about the sparse image.

Also the phone is stuck in edl. I'm trying what you said now. I'm assuming it's loading but idk. It's stuck.
[Android Q&A, Help & Troubleshooting] lehmancurtis:
If it hangs it should do so very long.
[Android Q&A, Help & Troubleshooting] lehmancurtis:
Run emmcdl.exe --help

You may find it helpful.
[Android Q&A, Help & Troubleshooting] lehmancurtis:
https://xdaforums.com/android/help/coolpad-catalyst-model-3622a-metropcs-t3452899

Check the link above for other info.
[Android Q&A, Help & Troubleshooting] Josephdbrewer25:
How long?
[Android Q&A, Help & Troubleshooting] lehmancurtis:
Try adding ur partition xml file to the command.

emmcdl.exe -p (COM ) -f prog_emmc_firehose_ddr.mbn -x .\"rawprogram0.xml,partition0.xml" SetActivePartition=1

More info can be found here http://nainglinnaung91.blogspot.com/2017/03/how-to-work-emmcdlexe.html?m=1 .

Reflash your bootloader first. Something like...

emmcdl.exe -p (COM) -f prog_emmc_firehose_ddr.mbn -b .\sbl1.mbn

#Replace (COM) with COM followed by you device port number.

What caused brick?