DO NOT BLAME ME FOR DAMAGE TO YOUR PHONE IF THIS IS NOT HANDLED CAREFULLY, WHILE SHORTING. DO IT AT YOUR OWN RISK WITH CARE AND PATIENCE.
The phone was dead...no fastboot... no recovery...no boot logo...no LED...
Only it was being detected by PC when connected and showing as
Qualcomm HS-USB Diagnostic device or QUSB_Bulk
in device manager
Finally managed to find the EDL test point for Max M2 (X01AD).
Be aware that once you open your back cover screws your warranty becomes void.
Things Required:
1. Usb Cable--GOOD QUALITY ONE.
2. Tweezers with sharp pin edges (preferably to make two contact point shorted).
3. Patience & Concentration.
HOW TO
Install QPST
open QFIL...there is a good guide in help topic...refer that for basics. (Qualcomm Flash Image Loader).
1. Remove battery then Plug the usb to phone charging port.
2. While shorting the points with tweezers, plug in the USB to the system USB port.
3. Wait for 5 to 10 sec...Device manager will show either USBDiagnostics9008 or Qloader9008 points, based on the drivers installed. If system shows earlier one...then
Right click-->update driver-->browse computer-->Let me pick--> un tick compatible driver-->Qualcomm-->and you will see Qualcomm HS-USB QDLoader 9008 driver..select and install it.
If system asks for restart..restart it and repeat the point-2 to get in to EDL mode.
Open QFIL-->flash.
select programmable_.._.._ ddr.mbn && rawprogram_unparse.xml during flash.
IMEI and serial number will be gone. Need to fix.
You need to short circuit the two test point as per attached picture during entire QFIL flash.
ROM link
https://vnrom.net/2018/12/rom-raw-ch...ne-max-pro-m2/
Use WW_ZB632KL or WW_ZB632KL file.
Look for zb632/633 KL and find 15.2016.1902.159
Hope it helps...
<Mod edit: Quoted post deleted>
Congratulations...???
[email protected] said:
DO NOT BLAME ME FOR DAMAGE TO YOUR PHONE IF THIS IS NOT HANDLED CAREFULLY, WHILE SHORTING. DO IT AT YOUR OWN RISK WITH CARE AND PATIENCE.
The phone was dead...no fastboot... no recovery...no boot logo...no LED...
Only it was being detected by PC when connected and showing as
Qualcomm HS-USB Diagnostic device or QUSB_Bulk
in device manager
Finally managed to find the EDL test point for Max M2 (X01AD).
Be aware that once you open your back cover screws your warranty becomes void.
Things Required:
1. Type C Cable--GOOD QUALITY ONE.
2. Tweezers with sharp pin edges (preferably to make two contact point shorted).
3. Patience & Concentration.
HOW TO
Install QPST
open QFIL...there is a good guide in help topic...refer that for basics. (Qualcomm Flash Image Loader).
1. Plug the type C to phone charging port.
2. While shorting the points with tweezers, plug in the USB to the system USB port.
3. Wait for 5 to 10 sec...Device manager will show either USBDiagnostics9008 or Qloader9008 points, based on the drivers installed. If system shows earlier one...then
Right click-->update driver-->browse computer-->Let me pick--> un tick compatible driver-->Qualcomm-->and you will see Qualcomm HS-USB QDLoader 9008 driver..select and install it.
If system asks for restart..restart it and repeat the point-2 to get in to EDL mode.
Open QFIL-->flash.
select validated_.._.._ ddr.mbn && xx_xx_no_fsg.xml during flash.
You need to short circuit the two test point as per attached picture during entire QFIL flash.
ROM link
https://vnrom.net/2018/12/rom-raw-ch...ne-max-pro-m2/
Use WW_ZB632KL or WW_ZB632KL file.
Look for zb632/633 KL and find 15.2016.1902.159
Hope it helps...
Click to expand...
Click to collapse
Why type-C cable ? Our phone has micro usb port
Jay_1212 said:
Why type-C cable ? Our phone has micro usb port
Click to expand...
Click to collapse
U r right.... I meant to normal usb. Rectified.
Test point
Help me I am unable to find the test points on my Asus ZenFone max 2 pro
I am getting this error while flashing above mentioned file with above mentioned steps. Why I am getting this error can anyone help me out about this?
Love you !
All the all the repairer in my city say : your phone is dead and I have already try to buy an other when I say this solution : it hurts the finger but gives a deep satisfaction.
Thanks a lot
clement_mint_android said:
Love you !
All the all the repairer in my city say : your phone is dead and I have already try to buy an other when I say this solution : it hurts the finger but gives a deep satisfaction.
Thanks a lot
Click to expand...
Click to collapse
This method no bad, but if you have firehose fail... what? How to fix?
Did you try with..?
UnBrick (EDL) - ZQL1830_Factory_201812181515_ChangeFlash.zip
Related
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Try mi flash tool
Main problem is that I have tried all 3 miflash I could found 2.11.6 20131108 20140509 and none of them recognizes device and I can't even initiate flashing process ;/
it sounds like a driver issue. just download all the drivers you can find for your phone.
Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Same problem here, waiting for someone give the solution
if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,
ZenR2 said:
if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,
Click to expand...
Click to collapse
r u following correct procedure for using MI flash tool ?
is ur Phone able to boot to FLash mode ( turn phone off > Press volume + Key then Press Power on - it will show flash mode )
Now Open MI Flash tool > Press Refesh > it will show phone now ( a number will b shown instead of name Xiamo Mi3)
Now Extract Fastboot rom to C Drive ( it should look like this C:\ROM (Location should not cointain space)
Now click Browse > advance > select C:\ROM\Folder\ select bat file
Its not drivers issue since its get detected as QUALCOMM HS-USB QDLoader 9008 or QUALCOMM HS-USB Diagnostic 9006 depending of its state.
In QDLoader it is recognized by miflash as COM20 device and I can upload by miflash or qpst boot image, then it switches to diagnostic that is recognized by some sort of string and I can upload/proceed with rest of rom flashing that includes creating partitions and writing data to them.
Main problem is that when its successfully flashed it is still cold dark, while PC can see it and all partitions like 28 of them...
And I think its related to the fact that qpst reports phone as in download mode.
Any idea how to exit that mode, like in Mi2 that was forced to enter "service" by shortening some pins to put it download mode to flash cold dead ones?
agdag said:
magdag from en.miui.com forum seems to be able to hekp ..or try [email protected] , jason provide paid service
Click to expand...
Click to collapse
You were already looking at it
Kinda wasted a lot of Mine and Yours time and some of my money
If You got any other ideas since that time how to resurrect it just let me know.
Any solution?
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?
androidy88 said:
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?
Click to expand...
Click to collapse
You can check the steps I took for recovering from a similar problem here: http://en.miui.com/forum.php?mod=viewthread&tid=22811
If you have any other questions, tag me on your reply and i'll try my best to help.
Hi,
I have a following problem with my Redmi 4X. I tried to flash new rom and reboot my phone on twrp. When the phone shut down nothing happens anymore just black screen. No fastboot or recovery mode. When I contact the phone to Windows pc it shows in device manager: Qualcomm HS-USB Diagnostics 900E (COM20). I have tried to flash new rom with QFIL and Miflash (tried to change the driver to Qualcomm HS-USB QDLoader 9008).
With QFIL the error is: Download Fail: Switch to EDL FailFailed to switch to Emergency Download mode.
With Miflash the error is: Cannot receive hello packet. MiFlash is trying to reset status!
Any suggestions?
https://www.youtube.com/watch?v=uxrhJkSZc6E
Already tried that. Doesn't seem to change a thing.
Shouldn't it turn the driver to "Qualcomm HS-USB QDLoader 9008" after test point method?
This is what shows in command prompt:
C:\Windows\system32>adb reboot edl
error: device '(null)' not found
C:\Windows\system32>adb devices
List of devices attached
C:\Windows\system32>
k4rpp4 said:
Shouldn't it turn the driver to "Qualcomm HS-USB QDLoader 9008" after test point method?
This is what shows in command prompt:
C:\Windows\system32>adb reboot edl
error: device '(null)' not found
C:\Windows\system32>adb devices
List of devices attached
Click to expand...
Click to collapse
After the test point method you will see a new "9008" device in the Device Manager.
Then all of the above commands will be completely irrelevant and useless.
In the 9008 mode use MiFlash, not QFIL/QPST, to reflash your phone.
Cheers!
The test points seems to change nothing. I think that after the " adb devices" command I should see my device listed but that is not the case and therefore impossible to flash rom. Somehow I should be able to change the "900E mode" to "9008 mode" without changing the driver manually and I think the test point method should do just that.
Here is video of what I have tried to do. If someone could point out what to do differently to get the flash work I would be very grateful.
https://drive.google.com/open?id=1aOkb3FCBzanMUW3WSdyuxyQO-33rdsBv
Windows 10 will not accept the 9008 driver because the driversignature ist not signed from Microsoft.
If you will unbrick it with Windows 10 64bit look here: https://www.youtube.com/watch?v=2d8KEruHWPg
and here: https://www.maketecheasier.com/install-unsigned-drivers-windows10/
Had allready done that also. Gave it another try without success
k4rpp4 said:
Had allready done that also. Gave it another try without success
Click to expand...
Click to collapse
Is the Qualcomm 9008 driver now installed?
Did you start the mi-flash tool with administrator privileges?
I installed the Qualcomm drivers but device manager still shows 900E driver unless I manually change it to 9008.
edit:
I finally succeeded with test point method. Now flashing. Im so grateful to you ConradB.
k4rpp4 said:
I installed the Qualcomm drivers but device manager still shows 900E driver unless I manually change it to 9008.
edit:
I finally succeeded with test point method. Now flashing. Im so grateful to you ConradB.
Click to expand...
Click to collapse
Perfect :good:
Bro please help my device in bricked
k23m said:
After the test point method you will see a new "9008" device in the Device Manager.
Then all of the above commands will be completely irrelevant and useless.
In the 9008 mode use MiFlash, not QFIL/QPST, to reflash your phone.
Cheers!
Click to expand...
Click to collapse
Thank you buddy .. Your 4 years old post help me to turn on my hard brick redmi 4x.
I don't know the actual reason of hard brick but The situation was my phone was in condition like
1. Possible to go in fastboot mode
2. When turning on there is only mi logo for fraction of second.
I tried test point method as described . It turned on in one attempt..I just want to add something. I face some issues after test point flashing . So I just flash miui again . Then It's working perfectly fine. After Test point flash check your battery. Maybe fully drained. Just charge it and turn it on..
I am posting this just for Information..
sayan990 said:
Thank you buddy .. Your 4 years old post help me to turn on my hard brick redmi 4x.
I don't know the actual reason of hard brick but The situation was my phone was in condition like
1. Possible to go in fastboot mode
2. When turning on there is only mi logo for fraction of second.
I tried test point method as described . It turned on in one attempt..I just want to add something. I face some issues after test point flashing . So I just flash miui again . Then It's working perfectly fine. After Test point flash check your battery. Maybe fully drained. Just charge it and turn it on..
I am posting this just for Information..
Click to expand...
Click to collapse
I do had same issue with my mobile but even when I tried to flash MIUI I got "ACK count don't match" attached img
DISCLAIMER: IM NOT RESPONSIBLE FOR DAMAGE TO YOUR PHONE IF THIS IS NOT HANDLED CAREFULLY, WHILE SHORTING. ONLY TWEEZERS SHOULD CONTACT THE POINTS NOT ANY THING ON MB, WHICH WOULD RESULT IN SHORT CIRCUIT AND CAUSE PERMANENT MO-BO DAMAGE. DO IT AT YOUR OWN RISK WITH CARE AND PATIENCE.
I finally managed to find the EDL test point for 5Z. Took risk of opening it and randomly testing the points...
Things Required:
1. Type C Cable--GOOD QUALITY ONE.
2. Tweezers with sharp pin edges.
3. Patience & Concentration.
HOW TO ENABLE EDL WITH TEST POINTS:
1. Plug the type C to phone charging port.
2. While shorting the points with tweezers, plug in the USB to the system USB port.
3. Wait for 5 to 10 sec...Device manager will show either USBDiagnostics9008 or Qloader9008 points, based on the drivers installed. If system shows earlier one...then select and udpate driver and you will see Qloader9008 driver..select and install it. If system asks for restart..restart it and repeat the point-2 to get in to EDL mode.
As of now, programming files through QFIL and QMCST are both present in the raw zip file. firehose_ddr.elf is present in the factory image.
Since im testing them, I cannot assertain the success rate, as it depends on nature of brick. Currently im testing QFIL on my bricked phone...
Hope it helps...
Please check the photo
DroneJC said:
DISCLAIMER: IM NOT RESPONSIBLE FOR DAMAGE TO YOUR PHONE IF THIS IS NOT HANDLED CAREFULLY, WHILE SHORTING. ONLY TWEEZERS SHOULD CONTACT THE POINTS NOT ANY THING ON MB, WHICH WOULD RESULT IN SHORT CIRCUIT AND CAUSE PERMANENT MO-BO DAMAGE. DO IT AT YOUR OWN RISK WITH CARE AND PATIENCE.
I finally managed to find the EDL test point for 5Z. Took risk of opening it and randomly testing the points...
Things Required:
1. Type C Cable--GOOD QUALITY ONE.
2. Tweezers with sharp pin edges.
3. Patience & Concentration.
HOW TO ENABLE EDL WITH TEST POINTS:
1. Plug the type C to phone charging port.
2. While shorting the points with tweezers, plug in the USB to the system USB port.
3. Wait for 5 to 10 sec...Device manager will show either USBDiagnostics9008 or Qloader9008 points, based on the drivers installed. If system shows earlier one...then select and udpate driver and you will see Qloader9008 driver..select and install it. If system asks for restart..restart it and repeat the point-2 to get in to EDL mode.
As of now, programming files through QFIL and QMCST are both present in the raw zip file. firehose_ddr.elf is present in the factory image.
Since im testing them, I cannot assertain the success rate, as it depends on nature of brick. Currently im testing QFIL on my bricked phone...
Hope it helps...
Please check the photo
Click to expand...
Click to collapse
After trying this my mobile not detecting in pc and fast charging also not working
Ashwin18d said:
After trying this my mobile not detecting in pc and fast charging also not working
Click to expand...
Click to collapse
me too. not detecting PC
Ashwin18d said:
After trying this my mobile not detecting in pc and fast charging also not working
Click to expand...
Click to collapse
The one you flashed through process is factory firmware to restore the device only...You need to update the same through Fastboot firmware for phone to work as intended.
Download fastboot firmware and flash it.
DroneJC said:
The one you flashed through process is factory firmware to restore the device only...You need to update the same through Fastboot firmware for phone to work as intended.
Download fastboot firmware and flash it.
Click to expand...
Click to collapse
Boot to fastboot but not detect on pc
I try
- change cable
- connect another computer
4rm4uto01 said:
Boot to fastboot but not detect on pc
I try
- change cable
- connect another computer
Click to expand...
Click to collapse
same problem service center guys charge for 25000 bugs .for the changing of mother board
4rm4uto01 said:
me too. not detecting PC
Click to expand...
Click to collapse
Hold the power key with them
Hello,
So I happen to somehow hard brick my huawei p10 via HiSuite while downgrading from EMUI 9.1.0.262 to 9.0.1.180 and to 8.0.0 (dont know which version). After phone finished downgrading to 8.0 its suddenly turned off and it wont turn back again. When I plug it to the charger the phone gets warm, while on computer (connected via usb) its recognized as fastboot device. I tried shorting testpoint but I couldnt get SERAIL recognition.
Please help me, I wanna save this bease I know it still has potential.. Huawei is so damn dumb when it comes to software support and firmware updates via PC unlike Xiaomi, Samsung whom have Odin and MiFlash.
its sad, big minus for huawei
kenzyyy said:
Hello,
So I happen to somehow hard brick my huawei p10 via HiSuite while downgrading from EMUI 9.1.0.262 to 9.0.1.180 and to 8.0.0 (dont know which version). After phone finished downgrading to 8.0 its suddenly turned off and it wont turn back again. When I plug it to the charger the phone gets warm, while on computer (connected via usb) its recognized as fastboot device. I tried shorting testpoint but I couldnt get SERAIL recognition.
Please help me, I wanna save this bease I know it still has potential.. Huawei is so damn dumb when it comes to software support and firmware updates via PC unlike Xiaomi, Samsung whom have Odin and MiFlash.
its sad, big minus for huawei
Click to expand...
Click to collapse
Tip for getting the testpoints to work:
* Disconnect the battery. You'll have to remove the plate over the battery connector.
* Plug in your USB cable to the phone - leave it disconnected from the computer.
* Short the testpoint.
* Plug the cable into the computer while keeping the testpoint shorted.
It should now come up in serial mode. You can, at your own risk, reconnect the battery now - I've never had a problem doing this, but the socket is now live so...
irony_delerium said:
Tip for getting the testpoints to work:
* Disconnect the battery. You'll have to remove the plate over the battery connector.
* Plug in your USB cable to the phone - leave it disconnected from the computer.
* Short the testpoint.
* Plug the cable into the computer while keeping the testpoint shorted.
It should now come up in serial mode. You can, at your own risk, reconnect the battery now - I've never had a problem doing this, but the socket is now live so...
Click to expand...
Click to collapse
Thanks for replying..
I get the testpoint working but after I get it to work PC doesn't recognize testpoint mode. I tried everything the phone is dead, it's stuck in fastboot..
I just want to get it to work it's all I want, I just want to flash any system on it I tried LINUX method but it's the same issue testpoint not recognized by PC other modes are recognized.
kenzyyy said:
Thanks for replying..
I get the testpoint working but after I get it to work PC doesn't recognize testpoint mode. I tried everything the phone is dead, it's stuck in fastboot..
I just want to get it to work it's all I want, I just want to flash any system on it I tried LINUX method but it's the same issue testpoint not recognized by PC other modes are recognized.
Click to expand...
Click to collapse
On Windows, you'll have to dig up some very specific drivers for the port.
On Linux, you need to make sure things like ModemManager aren't installed, as Linux directly recognizes the serial port exposed by the device, and if you have a package installed that tries autodetecting modems, it screws with the serial mode of the device - it's not terribly tolerant of protocol data that it doesn't understand.
irony_delerium said:
On Windows, you'll have to dig up some very specific drivers for the port.
On Linux, you need to make sure things like ModemManager aren't installed, as Linux directly recognizes the serial port exposed by the device, and if you have a package installed that tries autodetecting modems, it screws with the serial mode of the device - it's not terribly tolerant of protocol data that it doesn't understand.
Click to expand...
Click to collapse
Thank you again for replying.
Now I'm getting this in device manager (see picture)
So I've got this how in the heck do I get it working again? Is there any software that allows me to get it running? Plz don't recommend DC phoenix I've paid them and I didn't have so much luck with them..
:good:
kenzyyy said:
:good:
Click to expand...
Click to collapse
From there, you need to load the IDT mode fastboot, and then in theory you can reflash everything else.
Check elsewhere, I've seen a package floating around for restoring from a brick situation here. Otherwise, your choices are pretty much DC Phoenix or to go tracking down internal Huawei tools, as those are the only other pieces of software I know of for flashing the device back from such a brick situation.
irony_delerium said:
From there, you need to load the IDT mode fastboot, and then in theory you can reflash everything else.
Check elsewhere, I've seen a package floating around for restoring from a brick situation here. Otherwise, your choices are pretty much DC Phoenix or to go tracking down internal Huawei tools, as those are the only other pieces of software I know of for flashing the device back from such a brick situation.
Click to expand...
Click to collapse
How can I find it? I have found this thread currently I am downloading all necessary files + it's for Kirin 960 which is good I think. So do you think this will work? Here is the link: https://forum.xda-developers.com/mediapad-m5/how-to/downgrade-unbrick-huawei-device-methods-t3915693
U dont need hikey, just use image download tool 2.0.0.9
kikson112 said:
U dont need hikey, just use image download tool 2.0.0.9
Click to expand...
Click to collapse
So even if my device is recognized in fastboot and serial port (test point) mode it means I can unbrick it with Image Download Tool by flashing stock firmware? Cause my device is super duper dead black screen stuck in fastboot tried every single key combination plus I've let it charge for 2 nights still nothing and PC still recognizes in fastboot only..
EDIT: My bootloader is locked.
Thanks for replying btw! :highfive:
writing by idm is from test point usb com 1.0, i cant promis u that all goes well, probably imei will gone, beckup oem info from fastboot it may be help for future,
and if all goes bad, u cant do anythink more, feel free to contact me
kenzyyy said:
So even if my device is recognized in fastboot and serial port (test point) mode it means I can unbrick it with Image Download Tool by flashing stock firmware? Cause my device is super duper dead black screen stuck in fastboot tried every single key combination plus I've let it charge for 2 nights still nothing and PC still recognizes in fastboot only..
EDIT: My bootloader is locked.
Thanks for replying btw! :highfive:
Click to expand...
Click to collapse
3 Step Game
1st Write Board Firmware By Furious Gold Or DC Phoenix & Free TOOL IDT 2.0.0.9
2nd When Phone Powered On write Oem Info Model: VTR-L29 Vendor: hw , Country: eu
3rd Flash Stock Firmware 9.1 Or 9.0 ( C432 )
Game Over
if you need board firmware or stock firmware let me know
imeicodes said:
3 Step Game
1st Write Board Firmware By Furious Gold Or DC Phoenix & Free TOOL IDT 2.0.0.9
2nd When Phone Powered On write Oem Info Model: VTR-L29 Vendor: hw , Country: eu
3rd Flash Stock Firmware 9.1 Or 9.0 ( C432 )
Game Over
if you need board firmware or stock firmware let me know
Click to expand...
Click to collapse
Could you please post the necessary FW for P10 VTR-L29 9.0.1.185(C432E1R1P9)?
As I understand it would be the firmware with XML so i can use the Image download tool to flash it?
Thank you
Hey everyone,
yesterday my zenfone 8 just shutdown without any sign of a problem before . i thought its nothing but since then it dosnt turn on !!!
my only hope is when i connected it to my pc i got qualcomm 900e , i managed to change it to Qualcomm HS-USB QDLoader 9008 with driver update.
but still no fastboot no nothing.
i understand there is a way with qfil tool but i dont know how to get the files for it. any help please???
i see that qfil can fix it with rawdata and patch0 but i dont have this files. can some one please help???
You can get it on ROMdevelopers
QFIL / UnBrick - QMSCT_ForCSC_DefaultFuseLock_Sake_30.02.46.108_repkg.zip
AzimBahar said:
You can get it on ROMdevelopers
QFIL / UnBrick - QMSCT_ForCSC_DefaultFuseLock_Sake_30.02.46.108_repkg.zip
Click to expand...
Click to collapse
Hey azim , i downloaded the files but it seems it knows that i am on 900e even when i tries to use other drivers to be 9008. can you please assits how to get out of 900e?? btw i managed to get the files out of my device but sahara server failed because of 900e :/
Connect phone to pC using test point and follow guides
Trigger device to 9008 mode-
1. Remove USB cable and battery (Change a new chipset, UFS
should be empty)
2. Connect the battery
3. Device will boot into the emergency download mode
4. Confirm that the device manager has detected “Qualcomm HS-
USB QDLoader 9008 (COM x)”.
& Its may help too
ZS590KS_Keybox_Keymaster_HDCP_Online_Tool_M1220.zip
AzimBahar said:
Trigger device to 9008 mode-
1. Remove USB cable and battery (Change a new chipset, UFS
should be empty)
2. Connect the battery
3. Device will boot into the emergency download mode
4. Confirm that the device manager has detected “Qualcomm HS-
USB QDLoader 9008 (COM x)”.
& Its may help too
ZS590KS_Keybox_Keymaster_HDCP_Online_Tool_M1220.zip
Click to expand...
Click to collapse
I dont understand what i need to do . I even tried with edl cable but still stuck on 900e
Once try to uninstall USB Driver & install ASUS QCOM Driver.
As you said , i managed to change it to Qualcomm HS-USB QDLoader 9008 with driver update
Click to expand...
Click to collapse
After try again !
Note - You May use EDL Cable for EDL mode !
AzimBahar said:
Once try to uninstall USB Driver & install ASUS QCOM Driver.
After try again !
Note - You May use EDL Cable for EDL mode !
Click to expand...
Click to collapse
I tried with edl cable... Only test point left to find
duduhayo said:
I tried with edl cable... Only test point left to find
Click to expand...
Click to collapse
sir i have the same issues, are you know the test point right now?
Kiyori said:
sir i have the same issues, are you know the test point right now?
Click to expand...
Click to collapse
Hey, i wish. No one found it, I am still waiting for the one