Database Info

[Q] Help Un-bricking Sensation 4G?

So I checked the existing pages about bricked Sensations but I didn't
see any predicaments that were quite this bad let alone a fix. Anyways;
Was updating to newest firmware 3.24 because I was getting ready to flash a
new ICS rom. Updated fine in Hboot, and then I somehow managed to reboot before I could get into clockwork recovery mod. Got caught in a boot-loop so I
pulled the battery to try to get back into fastboot and it wouldn't even turn on.
So I pulled the battery again, held the power button to drain any power and put the battery back in and tried it again. It will not charge, the led will not turn on, and it gets a black screen with the back-light on. Can not get into anything, kinda looking like the internal memory was wiped somehow.
So are there any fixes? Or am I screwed? If so if I call tmobile will they replace it (in the event that everything was wiped)? Any help appreciated!

Wanderer_Zero said:
So I checked the existing pages about bricked Sensations but I didn't
see any predicaments that were quite this bad let alone a fix. Anyways;
Was updating to newest firmware 3.24 because I was getting ready to flash a
new ICS rom. Updated fine in Hboot, and then I somehow managed to reboot before I could get into clockwork recovery mod. Got caught in a boot-loop so I
pulled the battery to try to get back into fastboot and it wouldn't even turn on.
So I pulled the battery again, held the power button to drain any power and put the battery back in and tried it again. It will not charge, the led will not turn on, and it gets a black screen with the back-light on. Can not get into anything, kinda looking like the internal memory was wiped somehow.
So are there any fixes? Or am I screwed? If so if I call tmobile will they replace it (in the event that everything was wiped)? Any help appreciated!
Click to expand...
Click to collapse
Do you have ADB installed? Plug in the phone and power on, then see of your PC can see the phone by going to a command prompt and running
Code:
adb devices

tried it, doesnt show up

Wanderer_Zero said:
tried it, doesnt show up
Click to expand...
Click to collapse
I'm just looking at some stuff about QPST, which might help you - I'll post back once I understand it
Have you tried downloading a stock RUU and running that?

wmoore said:
I'm just looking at some stuff about QPST, which might help you - I'll post back once I understand it
Have you tried downloading a stock RUU and running that?
Click to expand...
Click to collapse
Hi wmoore,
i am currently in a position of figured out the information about this program, see my other post...
I am just trying to find someone who might help me with the project
GreetZ

Have a look at this. Follow steps 3 and 4 and tell me if you can see your device.
---------- Post added at 08:30 PM ---------- Previous post was at 08:29 PM ----------
Da_Loony said:
Hi wmoore,
i am currently in a position of figured out the information about this program, see my other post...
I am just trying to find someone who might help me with the project
GreetZ
Click to expand...
Click to collapse
Not sure how much help I would be I'm just trying to read up on QPST now. I have heard of it but never looked into any detail.

cant do that; when i try to boot my phone, all that happens is the backlight turns on and im stuck with a black screen. cant boot, cant get into fastboot/bootloader/cwm or anything

Wanderer_Zero said:
cant do that; when i try to boot my phone, all that happens is the backlight turns on and im stuck with a black screen. cant boot, cant get into fastboot/bootloader/cwm or anything
Click to expand...
Click to collapse
Well, i am in the same situation with my sensation, it doesn't power on and when connected to the pc it shows up as QHSUSB_DLOAD and the driver was not found auto by windows
i'm going to provide the links to the program and the driver in the thread i started to get the QCN File...
The standard answer provided here in that situation is that your phone is bricked and you need to send it to HTC for warranty reparation...I am going to try to get a DIY method to reflash your phone from scratch (as now it's waiting for a ROM to be download (Qualcomm High Speed USB DownLOAD mode)
---------- Post added at 12:02 PM ---------- Previous post was at 11:42 AM ----------
wmoore said:
Have a look at this. Follow steps 3 and 4 and tell me if you can see your device.
---------- Post added at 08:30 PM ---------- Previous post was at 08:29 PM ----------
Not sure how much help I would be I'm just trying to read up on QPST now. I have heard of it but never looked into any detail.
Click to expand...
Click to collapse
Well...
Everything is explained in http://forum.xda-developers.com/showthread.php?t=1468791
How much help can you be? simple, i need a dump of the rom which runs on your Sensation, but not an .img file, but a .qcn file, QPST provides that feature, but it hardcodes you EMEI and serial into it, therefor i need to get all the info about your phone, all numbers you can provide that are listed on the box in order to get searching for those variables in that file which is dumped...
When found i can change them into my vars, to try and flash the phone back to life... i geuss it'll be a work off about a week to get everything found in a 400MB file or so

Da_Loony said:
Well, i am in the same situation with my sensation, it doesn't power on and when connected to the pc it shows up as QHSUSB_DLOAD and the driver was not found auto by windows
i'm going to provide the links to the program and the driver in the thread i started to get the QCN File...
The standard answer provided here in that situation is that your phone is bricked and you need to send it to HTC for warranty reparation...I am going to try to get a DIY method to reflash your phone from scratch (as now it's waiting for a ROM to be download (Qualcomm High Speed USB DownLOAD mode)
---------- Post added at 12:02 PM ---------- Previous post was at 11:42 AM ----------
Well...
Everything is explained in http://forum.xda-developers.com/showthread.php?t=1468791
How much help can you be? simple, i need a dump of the rom which runs on your Sensation, but not an .img file, but a .qcn file, QPST provides that feature, but it hardcodes you EMEI and serial into it, therefor i need to get all the info about your phone, all numbers you can provide that are listed on the box in order to get searching for those variables in that file which is dumped...
When found i can change them into my vars, to try and flash the phone back to life... i geuss it'll be a work off about a week to get everything found in a 400MB file or so
Click to expand...
Click to collapse
OK well I already have QPST and the QHSUSB drivers downloaded but QPST cannot see my phone. I found something on an LG forum explaining how to get the COM port number from Device Manager but my phone doesn't show up the same way.
Can you tell me how to find my COM port?

wmoore said:
OK well I already have QPST and the QHSUSB drivers downloaded but QPST cannot see my phone. I found something on an LG forum explaining how to get the COM port number from Device Manager but my phone doesn't show up the same way.
Can you tell me how to find my COM port?
Click to expand...
Click to collapse
Yep
Windows 7?
Open your Control Panel from your start menu and put it on classic view, in order to see the device manager link, open this.
There you will see Ports (COM & LPT)
Unfold this and you will see your device there with a (COMx) behind it
in the QPST configurator you will have a tab with the name: Ports
click this
on the right bottom there is a button: Add New Port
click this, a dialog will open where you can see your ports, click the port which is of your phone, if not seen, just type COMx (x being the number stated in the device manager)
And press OK
As from now you will be able to see your phone on the first tab normally seen
now go to the menu "Start Clients"
SOFTWARE DOWNLOAD
If you see that the port is not correct on top, click the Browse next to it in order to choose the correct port, you'll see it will detect your phone then...
Goto the Backup tab and click browse, give the file a place and name, press start...
Then wait i guess, i am not in the possition to know how long it would take...
Now you have the QCN file made as i need in my post
This is a hexadecimal dump of your phone in Quallcomm Bundle Numeric format, with that we can start figuring out, how to get your serial number, emei etc out, to infuse our own to get our phone back up and running by using the restore function of the QPST program
Clear enough? :s
---------- Post added at 12:33 PM ---------- Previous post was at 12:30 PM ----------
It might also be that due to the fact that your phone is actually a still working exemplar that you need to follow the guide here: http://forum.xda-developers.com/showthread.php?t=1180211 in order to get your phone connected in QPST

Da_Loony said:
Yep
Windows 7?
Open your Control Panel from your start menu and put it on classic view, in order to see the device manager link, open this.
There you will see Ports (COM & LPT) <SNIP>
Click to expand...
Click to collapse
This is where I come unstuck. I don't have Ports in my Device Manager. I'm on a laptop that doesn't have serial or parallel ports, so that is probably why.

wmoore said:
This is where I come unstuck. I don't have Ports in my Device Manager. I'm on a laptop that doesn't have serial or parallel ports, so that is probably why.
Click to expand...
Click to collapse
Perhaps they are hidden?
Which windows are you using?

Da_Loony said:
Perhaps they are hidden?
Which windows are you using?
Click to expand...
Click to collapse
Win7 Ultimate x64. I checked hidden devices but they are not there either.

wmoore said:
Win7 Ultimate x64. I checked hidden devices but they are not there either.
Click to expand...
Click to collapse
Try to follow the manual i've placed online in my thread step by step: http://forum.xda-developers.com/showthread.php?t=1468791
guess your phone is not in diagnostics mode and therefor making not the right type of connection via USB

Da_Loony said:
Try to follow the manual i've placed online in my thread step by step: http://forum.xda-developers.com/showthread.php?t=1468791
guess your phone is not in diagnostics mode and therefor making not the right type of connection via USB
Click to expand...
Click to collapse
I've just realised why this isn't working for me. I'm using an AOSP ROM, so no HTC diags

wmoore said:
I've just realised why this isn't working for me. I'm using an AOSP ROM, so no HTC diags
Click to expand...
Click to collapse
No prob it was nice to know you would have helped me out if possible... up to the next one hehe

Da_Loony said:
No prob it was nice to know you would have helped me out if possible... up to the next one hehe
Click to expand...
Click to collapse
I've just taken a backup and am flashing ARHD 6.0.2 (because I had it downloaded already)
Gimme 20 minutes.

wmoore said:
I've just taken a backup and am flashing ARHD 6.0.2 (because I had it downloaded already)
Gimme 20 minutes.
Click to expand...
Click to collapse
Many thanks, i'm gonna PM you with my info (as promissed in my thread)

So I've gone back to ENG HBOOT 1.17 and Telstra stock ROM, Clockwork Recovery 5.0.0.8 and rooted. I have USB debugging on and am in diagnostic mode but I still don't get HTC Diag device or anything like it in Device Manager. I've shown hidden devices in there too.
The only phone related item I have is Portable Device, when expanded it says D:\ (which is my SD card drive in the phone). I tried changing USB mode from charge to disk to sync and every other option but still don't see the device in Device Manager.
Not sure what else I can do here .... Plus it's pretty late and I want to restore my phone before bed. If you can think if anything I've done wrong or anything I can try differently, please let me know and I'll try tomorrow.

No problem man, i know there is a time difference between Belgium and Australia
Have you checked that the phone is in charge mode and not in disk drive mode?
GreetZ
wmoore said:
So I've gone back to ENG HBOOT 1.17 and Telstra stock ROM, Clockwork Recovery 5.0.0.8 and rooted. I have USB debugging on and am in diagnostic mode but I still don't get HTC Diag device or anything like it in Device Manager. I've shown hidden devices in there too.
The only phone related item I have is Portable Device, when expanded it says D:\ (which is my SD card drive in the phone). I tried changing USB mode from charge to disk to sync and every other option but still don't see the device in Device Manager.
Not sure what else I can do here .... Plus it's pretty late and I want to restore my phone before bed. If you can think if anything I've done wrong or anything I can try differently, please let me know and I'll try tomorrow.
Click to expand...
Click to collapse

[Q] restoring bricked oneplus one problem

First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks

gl411 said:
First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks
Click to expand...
Click to collapse
Have you installed the Qualcomm driver?Its very tricky,Windows wont allow to install it easily.

Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?

gl411 said:
Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?
Click to expand...
Click to collapse
It should be the driver problem,no other choice.

maskelisuvari said:
It should be the driver problem,no other choice.
Click to expand...
Click to collapse
The easiest way for unbricking oneplus (yes, I tried it): http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
ColourOS firmware has all needed files for proper flashnig, including right tool for doing that.
Only thing that didnt work on my Win 8.1 x64 was drivers mentioned in post above.
I had to use this QHSUSB_DLOAD drivers from member DallasCZ (that I used for unbricking ZTE v9180). Only with that drivers my Windows recognized bricked phone and Flash tool could find and flash it.
Flash tool in only on chinese, that is a bit problem, but instructions given in post I linked are more/less usefull.
This is a link to DallasCZ shared folder with qhsusb drivers:
https://drive.google.com/folderview...&usp=sharing&tid=0B1T7tp6tJ_3kQkZSWjNsazJZbGc

If you are sure the driver is okay,plug in the usb cable and out and in,until you see the green line on the tool.Also you can follow the guide as in below link:
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
The same thing but this time you can flash CM11s instead of ColorOs.Also there is a video.Pls check it.

Ok so I did the process over and over again, the sixth computer did it right! I was back on ColorOS and now back to CM11S.
This thread can be closed, thanks for the help!

No problem,glad to hear you solved the problem

BRICKED 6045Y -QDLoader 9008 - any sugestion welcome

Hello,
since 5 years i am playing with google android OS and about 15 devices it looks like i have first fully bricked device.
What happened?
I made a custom marsmallow firmware from the update.zip.
The bad thing was (i think) that i deleted the aboot and also sbl1 partition from the update and also the script for flashing recovery. The second bad thing was (maybe) that i included busybox and root to the update.zip right from the begining without testing the firmware without it.
Then i made complete wipe of cache, dalvik cache, data and system (anothe rmistek i think). Flashed the firmware with no problem, no errors. Then i made wipe cache and dalvik cache again (as i used to, when going to higher OS version).
Afte rthat i hit reboot and my device is dead since then.
It cant be powered on normaly, neither recovery, neither bootloader, neither qualcomm loader.
Only thing that happens is when i connect the device to PC, the LED turns on. I have to tweak the ALCATEL USB drivers to be compatible with my WIN10PRO (yes i hate the win 10 because of the drivers,but had no other option than upgrade to win10).
Now i managed to see the device as "Android HS-USB QDLoader 9008 (yes 9008 not 9006 also bad thing).
When i try to connect to the device with panasonic eluga SUGAR_QCT_SP tool or with mobile upgrade Q or with SUGAR_QCT_SP tool i always get error when the tool downloads the MPRG. It cant download it from the device so it gives me error and thats it.
Since I dont have the proper rawprogram0.xml, patch.xml and other mbn files to pus them trough QPST i think i am in the dead end.
So if anybody has any suggestion i wil appreciate it.
If not, i will send it to warranty repair on friday and get finger crossed that they will repair it (while the service in chzech republic who is Alcatel aproved is a bunch of loosers, who do anything to do not have make it as warranty repair).

DallasCZ said:
Hello,
since 5 years i am playing with google android OS and about 15 devices it looks like i have first fully bricked device.
What happened?
I made a custom marsmallow firmware from the update.zip.
The bad thing was (i think) that i deleted the aboot and also sbl1 partition from the update and also the script for flashing recovery. The second bad thing was (maybe) that i included busybox and root to the update.zip right from the begining without testing the firmware without it.
Then i made complete wipe of cache, dalvik cache, data and system (anothe rmistek i think). Flashed the firmware with no problem, no errors. Then i made wipe cache and dalvik cache again (as i used to, when going to higher OS version).
Afte rthat i hit reboot and my device is dead since then.
It cant be powered on normaly, neither recovery, neither bootloader, neither qualcomm loader.
Only thing that happens is when i connect the device to PC, the LED turns on. I have to tweak the ALCATEL USB drivers to be compatible with my WIN10PRO (yes i hate the win 10 because of the drivers,but had no other option than upgrade to win10).
Now i managed to see the device as "Android HS-USB QDLoader 9008 (yes 9008 not 9006 also bad thing).
When i try to connect to the device with panasonic eluga SUGAR_QCT_SP tool or with mobile upgrade Q or with SUGAR_QCT_SP tool i always get error when the tool downloads the MPRG. It cant download it from the device so it gives me error and thats it.
Since I dont have the proper rawprogram0.xml, patch.xml and other mbn files to pus them trough QPST i think i am in the dead end.
So if anybody has any suggestion i wil appreciate it.
If not, i will send it to warranty repair on friday and get finger crossed that they will repair it (while the service in chzech republic who is Alcatel aproved is a bunch of loosers, who do anything to do not have make it as warranty repair).
Click to expand...
Click to collapse
Try with other Pc with WIndows 7 or 10 ..today i get my phone back 3 times with panasonic software and shows me "Android HS-USB QDLoader 9008"..sometimes fails with download mprg but try again ...first press + and - and then connect usb and try with panasonic in my situation power and volume buttons are don't work so i must open the phone

Alek Dev said:
Try with other Pc with WIndows 7 or 10 ..today i get my phone back 3 times with panasonic software and shows me "Android HS-USB QDLoader 9008"..sometimes fails with download mprg but try again ...first press + and - and then connect usb and try with panasonic in my situation power and volume buttons are don't work so i must open the phone
Click to expand...
Click to collapse
have tried with 3 PCs with win7 and with 3 usb cables. Still error when downloading MPRG.
I cannot understand where it went wrong. The aboot and sbl1 parition shouldnt affect the device to boot to recovery or to bootloader, because when the sbl1 chechk for aboot it should be fine whle they are the same version.

DallasCZ said:
have tried with 3 PCs with win7 and with 3 usb cables. Still error when downloading MPRG.
I cannot understand where it went wrong. The aboot and sbl1 parition shouldnt affect the device to boot to recovery or to bootloader, because when the sbl1 chechk for aboot it should be fine whle they are the same version.
Click to expand...
Click to collapse
i hardbricked many times and panasonic helped in every time...one time i made test zip of Miui and i hardbricked only led worked,screen not worked but panasonic helped me........i can't understand what's the problem with downloading MPRG

Alek Dev said:
i hardbricked many times and panasonic helped in every time...one time i made test zip of Miui and i hardbricked only led worked,screen not worked but panasonic helped me........i can't understand what's the problem with downloading MPRG
Click to expand...
Click to collapse
thats the probelm. I also dont know why is there a probelm to download the MPRG to comunicate with the device.
The removable battery was a good thing, because you can power off the device. Now i can just guess if the device is powered off or not when i connect to the PC.
And of course this f**ing windows 10.

maybe when the 6.0.1 will be released i can connect with propper mbn. but i cant wait. I will send it to repair on friday or buy another device (zenfone 3 or moto g4plus).
Now i am still trying to bring it to life.

DallasCZ said:
thats the probelm. I also dont know why is there a probelm to download the MPRG to comunicate with the device.
The removable battery was a good thing, because you can power off the device. Now i can just guess if the device is powered off or not when i connect to the PC.
And of course this f**ing windows 10.
Click to expand...
Click to collapse
Try to disconnect the Battery and reconnect and then try with Pc AND Panasonic

here is the screen.

Alek Dev said:
Try to disconnect the Battery and reconnect and then try with Pc AND Panasonic
Click to expand...
Click to collapse
but it means to open the device, and i am a little bit affraid not to loose the warranty by opening it and reconnect the battery.

DallasCZ said:
but it means to open the device, and i am a little bit affraid not to loose the warranty by opening it and reconnect the battery.
Click to expand...
Click to collapse
Try to go to TAB Infromation and Get information from Device and then press Reboot Device....I think if you dissconect battery and reconnect it will work....also
whether to open or not Тhe service will want money for repair

Alek Dev said:
Try to go to TAB Infromation and Get information from Device and then press Reboot Device....I think if you dissconect battery and reconnect it will work....also
whether to open or not Тhe service will want money for repair
Click to expand...
Click to collapse
if they cant boot the device they will probably replace the mainboard so they will not get known if the device was unlocked or rooted.
If i will open it and replace the battery i will break the stamps on the battery so they will know i was inside the device and they will refuse to make it as warranty repair.
SO if there is no software option i will send it to warranty repair. If they will refuse to repair it as warranty repair. then i will consider to open it and do whatever it takes to get it to life

DallasCZ said:
if they cant boot the device they will probably replace the mainboard so they will not get known if the device was unlocked or rooted.
If i will open it and replace the battery i will break the stamps on the battery so they will know i was inside the device and they will refuse to make it as warranty repair.
SO if there is no software option i will send it to warranty repair. If they will refuse to repair it as warranty repair. then i will consider to open it and do whatever it takes to get it to life
Click to expand...
Click to collapse
Did you have TeamViewer..i think that i can help you to get your device to life ( if you have Teamviewer send me ID AND pass to PM)

@Alek Dev: i congratulate you ! respect .... Sometime, you're like a morpion. But in this case , i salute your dedication
I hope you manage to save DallaCZ :angel:

murigny64 said:
@Alek Dev: i congratulate you ! respect .... Sometime, you're like a morpion. But in this case , i salute your dedication
I hope you manage to save DallaCZ :angel:
Click to expand...
Click to collapse
We are tried but Nothing same error . .i will google it ..)

murigny64 said:
@Alek Dev: i congratulate you ! respect .... Sometime, you're like a morpion. But in this case , i salute your dedication
I hope you manage to save DallaCZ :angel:
Click to expand...
Click to collapse
As i said to him...sometimes he is a pain in the ass, but he meneged to sped his time to try to solve my problem...rispect!

DallasCZ said:
As i said to him...sometimes he is a pain in the ass, but he meneged to sped his time to try to solve my problem...rispect!
Click to expand...
Click to collapse
i think the problem is drivers...because my device in device manager is showed like "Qualcomm HS-USB QDLoader 9008 " yours is showed like "Android HS-USB QDLoader 9008"-i think that you can again try this + and - and connect usb or + and - and pwr button and then usb

DallasCZ said:
As i said to him...sometimes he is a pain in the ass, but he meneged to sped his time to try to solve my problem...rispect!
Click to expand...
Click to collapse
Sent from my SM-N920V using XDA Free mobile app
---------- Post added at 02:30 AM ---------- Previous post was at 02:26 AM ----------
frankie paul said:
Sent from my SM-N920V using XDA Free mobile app
Click to expand...
Click to collapse
Alek Dev said:
i think the problem is drivers...because my device in device manager is showed like "Qualcomm HS-USB QDLoader 9008 " yours is showed like "Android HS-USB QDLoader 9008"-i think that you can again try this + and - and connect usb or + and - and pwr button and then usb
Click to expand...
Click to collapse
Sent from my SM-N920V using XDA Free mobile app
---------- Post added at 02:35 AM ---------- Previous post was at 02:30 AM ----------
DallasCZ said:
if they cant boot the device they will probably replace the mainboard so they will not get known if the device was unlocked or rooted.
If i will open it and replace the battery i will break the stamps on the battery so they will know i was inside the device and they will refuse to make it as warranty repair.
SO if there is no software option i will send it to warranty repair. If they will refuse to repair it as warranty repair. then i will consider to open it and do whatever it takes to get it to life
Click to expand...
Click to collapse
Sent a my SM-N920V using XDA Free mobile app

Alek Dev said:
i think the problem is drivers...because my device in device manager is showed like "Qualcomm HS-USB QDLoader 9008 " yours is showed like "Android HS-USB QDLoader 9008"-i think that you can again try this + and - and connect usb or + and - and pwr button and then usb
Click to expand...
Click to collapse
I tried with "Android HS-USB QDLoader 9008" and also with "Qualcomm HS-USB QDLoader 9008" and even with "Alcatel HS-USB QDLoader 9008" always error when reading MPRG from the device.

http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This should help you I think

yash_rathore25 said:
http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This should help you I think
Click to expand...
Click to collapse
maybe,but you have to rewrite all the .xml files with data for your device, which we dont have.

Revive of DEAD HONOR 9! (HARDBRICK) (NO TURN ON/CONNECT USB) - SOLUTION!!. (PICTURES)

Hello,
I finaly found out a method how to establish USB-Connection with a "dead" honor 9 (wasn't recognized by computer/didn't turn on/just nothing).
WARNING!! YOUR warranty will be lost IF YOU OPEN HONOR 9!, no guarantee you get anything fixed/Maybe you break more!!
So I show you how I did it:
1: Open the Honor 9 Back: Tutorialvideo (not made by me)
https://www.youtube.com/watch?v=SUI5sA99nDw
- I used Hair Dryer + Knife to open the back. But use the tools in this video if you have.
2: - Install right USB-Drivers.: I needet the drivers "ASC-Driver_Handset WinDriver 2.01.00.00.exe" - You can find them in google!
3. - Connect the 2 Test Points like in my images. I used the SIM-Card tool from the phone to do it.
4. - Connect phone via USB - if everything gone right it shows up in the device manager as "HUAWEI USB COM 1.0"
5. - NOW We need an app or method to flash FirmWare in this mode... actually not supported by DC-Phoenix.... If any solution I edit in the thread.
6. UPDATE UPDATE! PHONE GOT REVIVED READ SECOND POST!

UPDATE UPDATE !
- HONOR 9 REVIVED FROM THE DEAD
- Downloaded DC-PHOENIX (dc-unlocker.com) ->Made Account/Charged Credits
- Connect the Phone via Testpoints, than open DC-Phoenix APP
- Flashed ( Stanford-AL10_STFAL00S001028_Board Software_general_Android 7.0_EMUI5.1_05022CLB ) ->You can find it in DC-Phoenix search.
-> Phone got revived. (NO MORE Huaway boot animation - I got strange red and green colors instead)
-> Open H9 in Fastboot mode (Turn phone off than: VOL+Down + USB CABLE PUT IN)
-> OPEN DC-PHOENIX
-> FLASHED "Stanford-L09_C432B130_Firmware_Belgium_Germany_France_Netherlands_Portugal_Switzerland_Spain_Italy_Austria_Poland_Denmark_Finland_Czech_Republic_Hungary.APP" with DC-Phoenix.
[UPDATE 2}
- You have to restore IMEI/SN/CARRIER AND COUNTRY AFTER UPDATING (empty board) with HCU Client - (You can find the software on dc-unlocker.com)
- THAN INSERT SIM CARD TO GET OFFICIAL OTA UPDATES.
-> 100% back to stock with full OTA, everything working, boot animation also back

What could be the reason of those death ? planned obsolescence ? Virus ? just HW problem / quality ? no luck ? ........

sonneper said:
What could be the reason of those death ? planned obsolescence ? Virus ? just HW problem / quality ? no luck ? ........
Click to expand...
Click to collapse
Failure in playing and experimenting with the Software.

ok , nevermind, you manage it ! good play : ) !

yz8_1337 said:
Do you also think this works with mine which bootloops after downgrading from Oreo to Nougat?
Click to expand...
Click to collapse
This should work with all damaged Smarpthones but I also think there are better and much softer techniques to revive looping or software side errors where the phone still turns on.
Maybe try via fastboot mode? But no OT please there are enough threads for it bro.
Revive via testpoints should always be the last option to revive a phone.

I tried this and doesnt work for me, it doesnt even show up as unknown device in device manager.
does anyone know why or is my phone completely dead?

SusKuN1337 said:
I tried this and doesnt work for me, it doesnt even show up as unknown device in device manager.
does anyone know why or is my phone completely dead?
Click to expand...
Click to collapse
Maybe wrong drivers installed, maybe you didn't connect the testpoints right (I also needet much tries)

4r44444 said:
Maybe wrong drivers installed, maybe you didn't connect the testpoints right (I also needet much tries)
Click to expand...
Click to collapse
i got told yesterday that the motherboard is broken, so, rest in peace honor 9 :<

I updated my phone with HuRUpdater and no my phone won't turn on. I wanted to locate the ASC-Driver_Handset WinDriver 2.01.00.00.exe, but all of the links are false download links. Can someone point me to a valid link for the driver? Thanks!

Rapid81 said:
I updated my phone with HuRUpdater and no my phone won't turn on
Click to expand...
Click to collapse
Did you save your recovery.log in TWRP after you flashed with HuRUpdater ?
Update from Build to which build ?
On which cust region ?
Rapid81 said:
I wanted to locate the ASC-Driver_Handset WinDriver 2.01.00.00.exe, but all of the links are false download links. Can someone point me to a valid link for the driver? Thanks!
Click to expand...
Click to collapse
Here is ASC-Driver_Handset WinDriver 2.01.02.00.exe :
HUAWEI DRIVER HANDSET PRODUCTLINE 2.01.02.00
https://androidhost.ru/6rf
Please tell us back your experience flashing board software.

oslo83 said:
Did you save your recovery.log in TWRP after you flashed with HuRUpdater ?
Update from Build to which build ?
On which cust region ?
Here is ASC-Driver_Handset WinDriver 2.01.02.00.exe :
HUAWEI DRIVER HANDSET PRODUCTLINE 2.01.02.00
https://androidhost.ru/6rf
Please tell us back your experience flashing board software.
Click to expand...
Click to collapse
No, I did not saved the log. The update went well, no error or any difference. I updated my phone with HuRUpdater several times without problem.
I updated to STF-L09C432B376, but I had problems with that firmware and I went back to B371, as I did before, when I had issues with B374 as well.
Everything went well, and after B371, I installed Magisk v17, like always, pressed the reboot button and since that, the phone won't turn on.
Thanks for the link!

@Rapid81
As you're stating that after installing the driver, the WIndows sees the phone as "HUAWEI USB COM 1.0" :
So you're good to go, then no need for you to open up your device loonking for test points
---------- Post added at 16:28 ---------- Previous post was at 16:19 ----------
Let's chat via PM as I think I have some tools to replace DC-Phoenix tools which is a license-only. I'd like you to test.
I also liled to know how you managed to get COM1 without openphone and connecting testpoints...

oslo83 said:
@Rapid81
As you're stating that after installing the driver, the WIndows sees the phone as "HUAWEI USB COM 1.0" :
So you're good to go, then no need for you to open up your device loonking for test points
---------- Post added at 16:28 ---------- Previous post was at 16:19 ----------
Let's chat via PM as I think I have some tools to replace DC-Phoenix tools which is a license-only. I'd like you to test.
I also liled to know how you managed to get COM1 without openphone and connecting testpoints...
Click to expand...
Click to collapse
I just installed the mentioned driver, connected the phone and the "HUAWEI USB COM 1.0" showed up.
I wrote back to you.

DC-Phoenix give me an error when writing bootloader. I have a brick now.

Rapid81 said:
DC-Phoenix give me an error when writing bootloader. I have a brick now.
Click to expand...
Click to collapse
Have you tried to physically connect test point?
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
4r44444 said:
Maybe wrong drivers installed, maybe you didn't connect the testpoints right (I also needet much tries)
Click to expand...
Click to collapse
Flashed ( Stanford-AL10_STFAL00S001028_Board Software_general_Android 7.0_EMUI5.1_05022CLB ) ->You can find it in DC-Phoenix search.
What's it mean? Use what to Flash?

Ccboxes said:
Have you tried to physically connect test point?
Click to expand...
Click to collapse
Yes, several times, with method was 100% worked. The main board died.

Rapid81 is getting its bricked STF honor9 seen as COM3 by windows.
He said he changed it in windows settings to COM1.
But both times it didn't worked with DC-Phoenix or IDT...
Maybe he did not managed something...

oslo83 said:
Rapid81 is getting its bricked STF honor9 seen as COM3 by windows.
He said he changed it in windows settings to COM1.
But both times it didn't worked with DC-Phoenix or IDT...
Maybe he did not managed something...
Click to expand...
Click to collapse
Could you give the IDT and frimware to me？I want to try before DC.

Ccboxes said:
Could you give the IDT and frimware to me？I want to try before DC.
Click to expand...
Click to collapse
IDT 2.0.0.9
https://bi-t.xyz/ozS5cy2kTm
---------- Post added at 06:40 ---------- Previous post was at 06:34 ----------
IDT shoud work with with original BoardSoftware not repacked like DC-unlocker's .dgtks .

OP 7 Pro QUALCOMM CrashDump mode

Hi guys, today I was playing Teamfight Tactics on my OnePlus 7 Pro. Suddenly, the game froze and I couldn't do anything. Couldn't exit the app, couldn't turn off the screen. After a couple minutes, the display goes dark and then I see the following message on my screen:
QUALCOMM CrashDump Mode
I tried every buttons combinations that I could, for longer than 5 seconds each, and one of them (I think the power + volume up) it looked like it restarted the phone. I saw the OP logo but the image was shattered. Then, the same crash dump message appear.
I connected the phone to the charger and left it for a couple of hours.
Now the screen is all black and no button combination works.
The OS version was 10.0.4.GM21BA.
Is there something I can do to fix it at home?
I tried searching for a solution first but I'm not that familiar with fastboot, MSM, TWRP and other terms that I encountered and have no idea of.
Any help would be appreciated! Thank you.

Were you using any modifications? like magisk or custom rom.
It usually appears when some file has been corrupted and the best way usually is through msm tool

I did not use any modifications. The phone had the OS it came with.. This happened suddenly and I have no explanation for it.
I tried using MSM Download Tool but no luck.
If I commect my phone to my Windows 10 PC and keep holding all 3 buttons on the phone, then the phone appears in the Device Manager as:
Qualcomm HS-USB QDLoader 9008
So, I ran the MSM tool which detected my phone, waited for it to complete but nothing happened. The phone is still dead...
I tried both international and european versions of MSM.

I have the same a few month ago. Randomly have qualcomm crush dump. Op support give me advice to flash rom.
I flash rom with msm tools and problem never come back.
---------- Post added at 12:23 PM ---------- Previous post was at 12:20 PM ----------
Stunt3r said:
I did not use any modifications. The phone had the OS it came with.. This happened suddenly and I have no explanation for it.
I tried using MSM Download Tool but no luck.
If I commect my phone to my Windows 10 PC and keep holding all 3 buttons on the phone, then the phone appears in the Device Manager as:
Qualcomm HS-USB QDLoader 9008
So, I ran the MSM tool which detected my phone, waited for it to complete but nothing happened. The phone is still dead...
I tried both international and european versions of MSM.
Click to expand...
Click to collapse
You must hold only volume up and down and then conect USB cable to pc.
---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Read This.

If flashing with MSM doesn't work, youre phone is bricked. Send it back to OnePlus

I have same issue with my OnePlus 7 pro, I tried msm tool to flash, after successfully flash my mobile reboot and again same Qualcomm crash dump error showing.