Related
Hello everyone.
I need your help.
My Device: LG G3 D855 32GB
The device does not turn on, the only thing that appears is because when I connect the device to a PC, I see a driver installed:
RELINK HS-USB QDLoader 9008
I read guides on site here, and I'm trying to order
I downloaded the software BoardDiag 2.9
I downloaded the files to the appropriate TOT
I extracted the files by instructors on site.
I opened the program and I followed the guide and it seems to me an error
Download mode is enabled Mode,
I quickly disconnects from the computer and reconnect the computer and then the moment I am unable to do a test and the results are:
AP CHECK START = PASS
EMMC TEST START
FAILED TO OPEN PARTITION FROM EMMC
TEST ABORTED !!
I tried a lot of tutorials but I can not, it always seems the device is in Download Mode
What can I do more?
Please your help,
Eliran
If you go that way, you will need bunch of other stuff. Here is the link
http://open-freax.fr/guide-unbrick-your-lg-g3/
It is a good thing that your PC recognises phone like that.
But first be sure that You can not enter download mode or recovery or even fastboot.
And please say what did you do to make it like that? Wrong flash?
If you CAN enter download mode than you can flash kdz or tot files from there. Easiest way is to use LGUP but you must be careful if you want to try.
The phone fell
Navuhodonosor said:
If you go that way, you will need bunch of other stuff. Here is the link
It is a good thing that your PC recognises phone like that.
But first be sure that You can not enter download mode or recovery or even fastboot.
And please say what did you do to make it like that? Wrong flash?
If you CAN enter download mode than you can flash kdz or tot files from there. Easiest way is to use LGUP but you must be careful if you want to try.
Click to expand...
Click to collapse
Thanks for the comment
The phone fell into the vehicle.
I know the phone is always in Download Mode
The software does not let me do anything and making phone download mode
I did not try to install KDZ.
And I can not open a setup KDZ because the device does not rise and there is no open port.
I only have the port I did above.
Thanks for the help, I worked in the guide and I could not ...
Navuhodonosor said:
If you go that way, you will need bunch of other stuff. Here is the link
It is a good thing that your PC recognises phone like that.
But first be sure that You can not enter download mode or recovery or even fastboot.
And please say what did you do to make it like that? Wrong flash?
If you CAN enter download mode than you can flash kdz or tot files from there. Easiest way is to use LGUP but you must be careful if you want to try.
Click to expand...
Click to collapse
Thanks for the help, I worked in the guide and I could not ...
I went through all the steps I found at:
Now, let’s get the party started
I set up the software the guide and I got an error:
FAIL on the EMMC test
I changed the parameter Read / Write »to« Erase
And again I got the error:
FAIL on the EMMC test
Then I try again, click Start, open a window and write in English and Chinese
Device DLOAD mode
device was not found in dload trying flash peogrammer
I click OK, the window closes and then when I press Start again, the window reappears.
Only when I disconnect the USB cable from the computer and the author briefly again then I’m able to do the test, but he failed.
FAIL on the EMMC test
The device always is in Download Mode and appears port:
RELINK HS-USB QDLoader 9008
My component can not be right at all and it always is in Download Mode?
I did not do short the guide, because the computer also detected me.
It has always seemed stuck in a download mode.
There is another option? Short elsewhere as will enable progress?
Thank you very much for your help,
Eliran
I need help please. What can i do
zarfati66 said:
Thanks for the help, I worked in the guide and I could not ...
I went through all the steps I found at:
Now, let’s get the party started
I set up the software the guide and I got an error:
FAIL on the EMMC test
I changed the parameter Read / Write »to« Erase
And again I got the error:
FAIL on the EMMC test
Then I try again, click Start, open a window and write in English and Chinese
Device DLOAD mode
device was not found in dload trying flash peogrammer
I click OK, the window closes and then when I press Start again, the window reappears.
Only when I disconnect the USB cable from the computer and the author briefly again then I’m able to do the test, but he failed.
FAIL on the EMMC test
The device always is in Download Mode and appears port:
RELINK HS-USB QDLoader 9008
My component can not be right at all and it always is in Download Mode?
I did not do short the guide, because the computer also detected me.
It has always seemed stuck in a download mode.
There is another option? Short elsewhere as will enable progress?
Thank you very much for your help,
Eliran
Click to expand...
Click to collapse
I need help please. What can i do
The phone woke for a moment ...
zarfati66 said:
I need help please. What can i do
Click to expand...
Click to collapse
Hello everyone
Today I tried again to connect the device to your computer, the screen comes on suddenly.
And see the state of battery with a question mark inside a yellow triangle.
I did not realize also saw installed driver
LGE AndroidNet USB Serial Port
I tried to re-install.
Now again became a black screen and the next thing happens:
When the device without a battery connected to a computer costing me
RELINK HS-USB QDLoader 9008
When I'm with a battery, it registers an unknown device.
When the device without a battery test again tried to do this EMMC component fails.
help please
Eliran
relink hs-USB Qdloader 9008
ZARFATI6 said:
Hello everyone
Today I tried again to connect the device to your computer, the screen comes on suddenly.
And see the state of battery with a question mark inside a yellow triangle.
I did not realize also saw installed driver
LGE AndroidNet USB Serial Port
I tried to re-install.
Now again became a black screen and the next thing happens:
When the device without a battery connected to a computer costing me
RELINK HS-USB QDLoader 9008
When I'm with a battery, it registers an unknown device.
When the device without a battery test again tried to do this EMMC component fails.
help please
Eliran
Click to expand...
Click to collapse
I am exactly in the same situation. Have you found any solution so far???? My phone suddenly stopped working and didn't boot up at all first and then I used the LG Flashtool to install original TOT file and all went well. I forgot to close LG Flashtool and it started flashing again. LG Flash tool restarts the phone at about 80% and then it failed at that point and since then I am having this issue.................
Any solution???????
apur32 said:
I am exactly in the same situation. Have you found any solution so far???? My phone suddenly stopped working and didn't boot up at all first and then I used the LG Flashtool to install original TOT file and all went well. I forgot to close LG Flashtool and it started flashing again. LG Flash tool restarts the phone at about 80% and then it failed at that point and since then I am having this issue.................
Any solution???????
Click to expand...
Click to collapse
Same situation too, solutions yet?
Hey I have the same problem .
If any of you found the solution please post it here or pm me, I am stuck
I have an Xperia Play that I got off eBay (I know, I know, personal project - I do have another working one). Reported issue was that it wouldn't boot, but after messing with it, I found that it would 1/10 times if I pull the battery for a few seconds before trying. I was even able to flash a stock firmware again. However, the majority of the time, it won't boot into OS, fastboot, OR flash mode.
Here's why: QHSUSB_DLOAD
From my research, this basically means the bootloader is corrupt or somehow otherwise malfunctioning. When connected to a computer, it resolves to "Qualcomm HS-USB QDLoader 9008 (COM3)" or whatever COM port it lands on, and it does this in fastboot and flash mode. Except for those rare instances where it acts like a normal phone.
I've spent most of the past couple of days digging around in forums, Google, and the Wayback Machine, trying to find a solution. Unfortunately, beyond trying a different computer and reinstalling drivers (both of which I have), the only solutions given are to use Omnius or s1tool/s2tool. They both seem to require payment for unlocking phones, which I don't need, but as far as I can tell should work fine for repairing the s1 boot, which I think is what I need to do. I've been following different guides that all say to remove the battery, connect the test points, and plug in the USB, but I can't get Omnius or the s-tools to work.
Is there any hope for this device? Can anyone who has gone through this before offer some suggestions? Alternatively, is there maybe a way I can just deal with the problem while still being able to use the phone without needing to pull the battery a bunch of times? The Xperia Play is still a great portable gaming system, so I'm hoping we'll be able to figure something out, as I know many other people are starting to acquire these from eBay and try to get them working, and may also run into this issue.
#metoo
I'm also having the same issue.
found this thread [Q] [Hardbricked]Xperia Play lifeless
CamillaHinchcliffe said:
Here's my problem, I wanted to flash a new ROM into my R800a but when I plugged it into my computer it detected the phone as a device called "Qualcomm HS-USB QDloader 9008" and now it does not turn on anymore .
Searching around Google I found that it doesn't turn on because the "SEMCboot" or "Trim Area" is damaged, but I've no idea how to fix that on my own.
Click to expand...
Click to collapse
And this one [How-to] Repair Damaged Bootloader + Trim Area [Red Led][Unknown Device]
Alejandrissimo said:
Sometimes we can brick our devices by a bad unlock, flashing process, or simply bad luck.
The phone doesn't turn on and there is a Red Led Of Death when pressing power button. Even with a GREEN led when we plug the phone with back key pressed the computer detect the phone as "unknown device" so there is no chance to get fixed by Flashtool or SEUS/PC Companion.
Well this problem normally means that the bootloader is broken or damaged. So, in order to fix it we need to write a new SEMCboot and after this we were able to flash a full and fresh firmware with flashtool and unbrick our Xperia.
This process like unlocking process requires SETool dongle/box and a paperclip to make a testpoint to put the phone in flash mode and be able to write the SEMCBoot.
I can help to anyone with a bricked Xperia Arc/Play/Neo/Pro just make send me a PM.
Like unlocking process you will need this 3 programs:
SETool software for unlocking
USB Over network client for remote dongle
Teamviewer client for remote support and guide
THIS PROCESS IS FREE
anyway if you want me to buy a Dr. Peper just
Click to expand...
Click to collapse
And finally, I found this thread in the Xperia SP forum [Guide]Zeus Flash Or qhsusb_dload Solved!!!!!
Almas008 said:
Thanks to mr @the_laser!!!!
Now those who have their phones in qhsusb or zeus flash device can revive their xperia sp to life back....!!!!!
Download attachement and run s1tool and click flash...
select attached sin file set and folow instructions....
Click to expand...
Click to collapse
And also this thread S1 boot download driver.
Some of these fixes and threads are old/outdated, so I dont know what will work Ive already started to use some of the tips last night. I have found out that my phone does get detected as "Qualcomm HS-USB QDloader 9008" but that's as far as Ive gotten. Please read the threads and tell me what you find out, or try that works
I've already been through those threads, and several more like them. The immediate answer is to contact Alejandrissimo, but they've been MIA for years now. I shot them an email the other day, but I don't expect to hear back.
Things I've tried:
Xperia Companion (PC Companion) - doesn't recognize device
SEUS (Sony Ericsson Updater Service) - discontinued, can't connect to servers
S1tool testpoint method - doesn't recognize that a device is connected
Omnius - doesn't recognize that a device is connected
Flashing stock the one time I could get it to boot into flashmode
It looks like this method stands a good chance of working, but it requires an "APPSW .sin_file_set" file, which I haven't been able to acquire for the Xperia Play. From Googling around, it seems that's the blob file that gets downloaded when you get an OTA update or when using XperiFirm (which no longer gives Xperia Play as an option), but all I can find are recompiled *.ftf files. Those files do contain a bunch of *.sin files, but comparing the contents to what you find in a *.sin_file_set file, is too different; the latter has a different folder structure and a bunch of XML files that provide information to the phone. I'm not sure exactly just how necessary that structure is and I couldn't find a guide on recreating a *.sin_file_set file, just how to decrypt one to convert to FTF.
If you click that link to the tutorial for that process, you can download a *.sin_file_set for a different model of phone to see what it should look like.
Of course now I just stumbled on a guide to convert FTF back... I will have to try that.
EDIT: Okay, I grabbed the s1tool from that link and disabled my antivirus before using it. Did the testpoint procedure as described, and got this error:
llbug: [] open error: "The system cannot find the path specified"
Click to expand...
Click to collapse
That might be because the bootloader is still locked. If I can get it to let me into fastboot, I may be able to change that.
EDIT 2: Got it into fastboot, verified the bootloader is locked. Ran the unlock command, but it failed. Tried doing it through s1boot and got the same error as before. Guessing there isn't anything else I can do at this point.
EDIT 3: Forgot to mention the process I tried before was with an FTF, since I discovered S1tool will use those after all (I used the version from that website I linked to). I still need to recompile a sin_file_set version and try that. In the meantime, I did actually receive a response back from Alejandrissimo, so we'll see where that goes and I'll report back.
I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Solved: Use the first blank flash from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175
mookiexl said:
I attempted to flash Dirty Unicorn from they're site, which appeared to go well, then I proceeded to flash the TWRPinstaller.zip that was suggested from the maintainer for our device. when I tried to reboot from recovery I got a no OS message. I ignored the message and attempted to reboot. Now the phone doesn't normally power on or off(which may change once the battery dies), no boot animation, no recovery, no fastboot recognition. The computer recognizes the phone as Qualcomm HS-USB QDLoader 9008. I googled for hours last night trying to fix to no avail. Has any of our great devs found a way to atleast recover the bootloader screen. I think I can handle it myself from there with adb.
Click to expand...
Click to collapse
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
mookiexl said:
Solved: Use the first blank flash to from the link to get back to bootloader screenhttps://firmware.center/firmware/Motorola/Moto%20Z2%20Force/Blankflash/
From bootloaderscreen put your ADB skills to work. I'm not too good with guides but this just saved me $175
Click to expand...
Click to collapse
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?
Technical said:
I did the same, got the same. Can't confirm the Qualcomm HS-USB QDLoader 9008 device will be there.
No charge, no screen, does not turn on/off, no vibration. Worst: no bootloader... Again, could be different if the battery dies.
Three questions:
1. File there is NDX26.183-15_17. Is it the same for OPXS27.109-34-10 on which I'm now? I suppose I need to use the "Oreo" version (2nd file in the list).
2. Which tool/software did you use to flash it? Is there a step by step tutorial?
3. You say "from bootloader screen". What about if we do not have a bootloader screen but a black brick in our hands?
Click to expand...
Click to collapse
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
Before connecting the phone, start the blankflash program. Maybe you have to repeat it a couple of times. Also try different cables, ports and computers.
Dany XP said:
Can somebody help me? I am in the same situation.
T-Mobile, unlock bootloader, hard bricked (already recognized Qualcomm QDLoader 9008 in device manager at least...)
I tried to use the blankflash but...see attachment
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
mookiexl said:
Answers
1.NDX26.183-15_17 (All it does is get your boatloader screen back
2. If you go to the device menu on your computer and your phone reads as Qualcomm HS-USB QDLoader 9008, all you have to do is click on the Blank flash all file and from the extracted folder and command prompt will do the rest. If the device is not recognized QDLoader 9008 then you will need to download qualcomm drivers to your computer
3.That is exactly what the file is for. Getting your black brick to at least the bootloader screen. From there you can adb recovery or stock rom.
What I ended up doing was adb push the bootable TWRP from the this thread https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932.
Flash the TWRP the official for our device from they're site(the bootable TWRP will give you access to extsd and thats where I had the official TWRP )
Rebooted back to bootloader and adb the firmware files for my device from the AOISP thread and rebooted my phone and I was booting DU.
Click to expand...
Click to collapse
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?
LØNEWØLF said:
Can somebody please help me, my laptop isn't even detecting my device as QDLoader 9008, can you please tell me which windows os version did you use, also did you use the usb cable came in the box and did you use usb 2.0 port or 3.0?
Click to expand...
Click to collapse
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go: https://www.androidbrick.com/download/latest-2017-qualcomm-diag-qd-loader-windows-10-drivers-signed/
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0! ???
Dany XP said:
Well, you need of course, Qualcomm loader driver, to at least having your device recognized as 9008. There u go:
After that, go ahead with blankall and stuff...
P.s. and yes ..stay away from USB 3.0!
Click to expand...
Click to collapse
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens
LØNEWØLF said:
Thanks for the reply bro....but I have that driver installed...I installed before connecting it....still not detecting... I'm gonna try this once more in my friend's pc... let's see what happens
Click to expand...
Click to collapse
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?
Dany XP said:
I know it's a long shot but...do u have any other Qualcomm device to try?
U can enter EDL mode with adb command "adb reboot edl". Yes, it's that simple. ?
Click to expand...
Click to collapse
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?
LØNEWØLF said:
OK I'll try...but how would I get back from edl to Normal without doing anything in the edl?
Click to expand...
Click to collapse
Uh...good question
Last time i flashed ThE stock ROM via mi flash tool i lost energy on my pc so prosess ended un error. My phone was in fastboot but i rebooted and never turns on again. I cant get fastboot mide anymore. Adb not recognice it but i can see it on PC in device mánager as "gualcomm HS-USB diagnostics 900E (COM3)
Any help?
MaxxTwo said:
Last time i flashed ThE stock ROM via mi flash tool i lost energy on my pc so prosess ended un error. My phone was in fastboot but i rebooted and never turns on again. I cant get fastboot mide anymore. Adb not recognice it but i can see it on PC in device mánager as "gualcomm HS-USB diagnostics 900E (COM3)
Any help?[/QUOTE
Just go to fastboot mode and type: "fastboot oem edl"
If you can´t enter fastboot, you have to open your phone and connect both testpoints
it's all on xda questions and anwsers mi A2 lite
Click to expand...
Click to collapse
Nxkealen said:
MaxxTwo said:
Last time i flashed ThE stock ROM via mi flash tool i lost energy on my pc so prosess ended un error. My phone was in fastboot but i rebooted and never turns on again. I cant get fastboot mide anymore. Adb not recognice it but i can see it on PC in device mánager as "gualcomm HS-USB diagnostics 900E (COM3)
Any help?[/QUOTE
Just go to fastboot mode and type: "fastboot oem edl"
If you can´t enter fastboot, you have to open your phone and connect both testpoints
it's all on xda questions and anwsers mi A2 lite
Click to expand...
Click to collapse
Thanks! But its in indi, can not undetstand nothing XD
Click to expand...
Click to collapse
https://redirect.viglink.com/?key=e...ter-t3862648/amp/&ref=https://www.google.com/
1- install mi flash tool and Qualcomm driver on your Pc
2- open the phone (just remove the battery connector )
3-plug a USB cable in the device
4- short the jtag pins(you can find their location in this page www mobilerdx com/2018/09/xiaomi-redmi-6-pro-test-point-boot-into-edl-9008-mode.html
7-plug the USB cable in the Pc while shortening the pins
If you do these steps mi flash tool should reconize your device and you will be able to flash it
Thanks man! My phone is working properly again. Let me tell my story in this.
Never opened a device before this. So I decided to take it to the official service. Unfortunately they told me that the mother board was damaged and the cost to REPLACE it is the same as buy a new phone!
So I been forced to try fix it by my self.
A couple of latex gloves XD and don't ask how I did to short the points but it works...
Now I'm using my Daisy again and waiting for official Android Q !!!
Sorry for a new thread. My device went into brick state . Cannot even use power and volume button. Followed almost majority of youtube and xda. The process of Ant flash or flash was not working older versions also. It gets stuck with authorisation as I am using EDL mode . Is there a way to skip Auth. Kindly help.
No you can't skip auth, you have to get it on your Xiaomi account which will take 30-60 days or in some cases more. Or they can just ignore/deny it.
You can use test-point method, but do it on your own risk. If you mess something in your motherboard then you can kiss your phone goodbye.
Alternatively you can just send your device to a service center and they will fix it for you.
However if your phone is detected in fastboot mode. Then you can fix it yourself.
Try downloading this driver then check if your device is detected in fastboot.
XDHx86 said:
No you can't skip auth, you have to get it on your Xiaomi account which will take 30-60 days or in some cases more. Or they can just ignore/deny it.
You can use test-point method, but do it on your own risk. If you mess something in your motherboard then you can kiss your phone goodbye.
Alternatively you can just send your device to a service center and they will fix it for you.
However if your phone is detected in fastboot mode. Then you can fix it yourself.
Try downloading this driver then check if your device is detected in fastboot.
Click to expand...
Click to collapse
Thank you . ADB ( have a warning kind of symbol) when I connect phone I get a refresh kind of stuff happening in Device manager but ADB continue to have that code (10)). How to resolve this or if this normal then I am unable to access the phone .
Secondly Test-Point Method (I am yet to get to it) is this EDL mode then I did try couple of time as there are many threads but I think everyone showed Video but continued to state no Auth is required so I tried more times now but no luck .. I will google more on Test Point method if that is different. Appreciate your answer
Who should we approach to get an Authorization (Will give a try ) as service center states mother board replacement. All threads related this were in 2018.. Just saw one thread but that was kind of not leading to closure .
Teddy126 said:
Thank you . ADB ( have a warning kind of symbol) when I connect phone I get a refresh kind of stuff happening in Device manager but ADB continue to have that code (10)). How to resolve this or if this normal then I am unable to access the phone .
Secondly Test-Point Method (I am yet to get to it) is this EDL mode then I did try couple of time as there are many threads but I think everyone showed Video but continued to state no Auth is required so I tried more times now but no luck .. I will google more on Test Point method if that is different. Appreciate your answer
Who should we approach to get an Authorization (Will give a try ) as service center states mother board replacement. All threads related this were in 2018.. Just saw one thread but that was kind of not leading to closure .
Click to expand...
Click to collapse
Your reply is all over the place, I didn't get a single thing of what you said.
Just boot your device to fastboot then type in cmd fastboot devices if you get a response with your device id then your device is detected in fastboot.
Test-point is exactly EDL mode just that you access it directly from the chipset instead of the normal way so it skips auth.
You have to connect two points in the motherboard with your usb then connect it to the PC with the correct driver (Qualcomm 9008)
If you don't know what you're doing then get it to a professional or some friend of yours, don't break it more.
XDHx86 said:
Your reply is all over the place, I didn't get a single thing of what you said.
Just boot your device to fastboot then type in cmd fastboot devices if you get a response with your device id then your device is detected in fastboot.
Test-point is exactly EDL mode just that you access it directly from the chipset instead of the normal way so it skips auth.
You have to connect two points in the motherboard with your usb then connect it to the PC with the correct driver (Qualcomm 9008)
If you don't know what you're doing then get it to a professional or some friend of yours, don't break it more.
Click to expand...
Click to collapse
Thank and sorry for the confusion.
Please note cannot get to Fastboot mode as power+Vol Down does not respond. What i tried to explain is when I installed ADB drives I get a warning symbol in device management
Tried EDL mode with tweezers by simultaneous connecting so that I try flashing. There were some video's. But I could not flash as it was asking Auth.
Teddy126 said:
Thank and sorry for the confusion.
Please note cannot get to Fastboot mode as power+Vol Down does not respond. What i tried to explain is when I installed ADB drives I get a warning symbol in device management
Tried EDL mode with tweezers by simultaneous connecting so that I try flashing. There were some video's. But I could not flash as it was asking Auth.
Click to expand...
Click to collapse
Well then you have no options but to it give to a professional since you can't do a test-point boot.
XDHx86 said:
Well then you have no options but to it give to a professional since you can't do a test-point boot.
Click to expand...
Click to collapse
Thank you will follow this advise. Just tried by seeing EDL videos which I realize is not true and everyone might have had auth code. Thank you for resp[onding