DELETE THIS THREAD PLEASE, PROB is SOLVED
I tried to install lineage os via twrp and i think my tablet its now hardbricked....It go on a blackscreen after the google startup logo and i can'T access bootloader even if it's unlocked, the menu of recovery, bootloader etc don'T pop up when i try button power and vol down....Is there any way to fix that?
myusernameisalreadytaken said:
I tried to install lineage os via twrp and i think my tablet its now hardbricked....It go on a blackscreen after the google startup logo and i can'T access bootloader even if it's unlocked, the menu of recovery, bootloader etc don'T pop up when i try button power and vol down....Is there any way to fix that?
Click to expand...
Click to collapse
Are you sure that in any statup mode you only see the Google logo and then the unit turns off?
Do the following test:
- charge your N7'13 for several hours
- connect it to a PC, and while still connected...
- boot in fastboot mode, "With the device powered off, hold Volume Down + Power until the bootloader appears, then release the buttons."
- observe your PC for new USB device indication (in Device Manager)
What's the new device ID number (if any)?
e.g.
USB\VID_18D1&PID_4EE0
USB\VID_05C6&PID_9008
LOS 15.1 (flex11 build) doesnt have a bootanimaltion. So after rebooting to system You should see a Google logo, then a black screen until setup wizard shows up
Sent from my whyred using XDA Labs
k23m said:
Are you sure that in any statup mode you only see the Google logo and then the unit turns off?
Do the following test:
- charge your N7'13 for several hours
- connect it to a PC, and while still connected...
- boot in fastboot mode, "With the device powered off, hold Volume Down + Power until the bootloader appears, then release the buttons."
- observe your PC for new USB device indication (in Device Manager)
What's the new device ID number (if any)?
e.g.
USB\VID_18D1&PID_4EE0
USB\VID_05C6&PID_9008
Click to expand...
Click to collapse
When i plug it i see LeMobile Android device android composite ADB Interface and when i click on it i see the device id
USB\VID_18D1&PID_4EE7
I can't boot in fastboot mode the screen come black with a backlight after the google logo and nothing happen...
When i flashed the rom i've see the android app update and nothing after
myusernameisalreadytaken said:
When i plug it i see LeMobile Android device android composite ADB Interface and when i click on it i see the device id
USB\VID_18D1&PID_4EE7
I can't boot in fastboot mode the screen come black with a backlight after the google logo and nothing happen...
When i flashed the rom i've see the android app update and nothing after
Click to expand...
Click to collapse
USB\VID_18D1&PID_4EE7 - wow I haven't seen this one before.
Please clarify and/or confirm:
- is it actually Nexus 7 2013 2nd gen?
- what exactly lineage os version/link did you flash?
- "With the device powered off, hold Volume Down + Power until the bootloader appears..." you get blank screen with backlight and USB\VID_18D1&PID_4EE7 on your PC
- "With the device powered off, hold Volume Down + Power..." does it respond OK to "fastboot devices" command on your PC?
NOTE - "With the device powered off, hold Volume Up + Power" gets you into recovery with ADB ID similar to USB\VID_18D1&PID_4EE7 - Have you mixed up " Volume Up" and " Volume Down"?
This case is perplexing and that's why I'm repeating and confirming everything. If it is indeed N7'13 AND there is no hardware issue AND you can't get into fastboot, then proceed to the unbricking guide - https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
To enter 9008 mode...
- turn it off and disconnect USB
- press both vol buttons and...
- plug in to a PC
k23m said:
USB\VID_18D1&PID_4EE7 - wow I haven't seen this one before.
Please clarify and/or confirm:
- is it actually Nexus 7 2013 2nd gen?
- what exactly lineage os version/link did you flash?
- "With the device powered off, hold Volume Down + Power until the bootloader appears..." you get blank screen with backlight and USB\VID_18D1&PID_4EE7 on your PC
- "With the device powered off, hold Volume Down + Power..." does it respond OK to "fastboot devices" command on your PC?
NOTE - "With the device powered off, hold Volume Up + Power" gets you into recovery with ADB ID similar to USB\VID_18D1&PID_4EE7 - Have you mixed up " Volume Up" and " Volume Down"?
This case is perplexing and that's why I'm repeating and confirming everything. If it is indeed N7'13 AND there is no hardware issue AND you can't get into fastboot, then proceed to the unbricking guide - https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
To enter 9008 mode...
- turn it off and disconnect USB
- press both vol buttons and...
- plug in to a PC
Click to expand...
Click to collapse
I dindt know for power+vol up.....with that i've fixed my problem! i'Ve reinstalled lineage 14.1 and it work.... The only issus it's i dind't see the normal fastboot or bootlarder menu with vol down...
Related
I was provided this device to try and help resolve the issue. I am not sure how it got to this point. I believe that it was rooted with a custom ROM, then the individual tried to install a stock ROM (method unknown).
The current situation is:
Galaxy Tab S 10.5 SM-T800 stuck in a bootloop with the TWRP logo on the screen. I can not get the tablet to go into download mode. I have tried all of the different methods to enter download mode, i.e. Power & Vol - & Home, Drain the battery > Plug into PC while holding Vol - & Home, Power & Vol + & Vol -. None of these combinations do anything. The only thing I can do to get a response is to press Power & Vol +, which reboots the device right back into the TWRP loop after the Samsung Logo. Power button alone does nothing.
The device is seen by Windows with the Samsung Drivers but is not mounted to a drive letter, and I can not mount it.
ADB , fastboot and Odin do not see the device.
I would like to flash a new rom either custom or stock, but I need to be able to get the device into download mode so it can be seen by odin.
Any help would be great.
Mike
Probably just timing and pilot error this one. I've never known of any Samsung device boot but be incapable of booting to download mode as download mode is bootloader related.
No working bootloader means dead device.
No matter what state the device is in at the moment with the usb cable removed, hold POWER + VOL DOWN (not up) + HOME until the Samsung boot logo comes up, hold for another couple of seconds then release. Download mode should appear.
I know it should be easy....
I know it should work but it is not, I will make a vid of the process and post. I can not make heads or tails.
Mike
ashyx said:
Probably just timing and pilot error this one. I've never known of any Samsung device boot but be incapable of booting to download mode as download mode is bootloader related.
No working bootloader means dead device.
No matter what state the device is in at the moment with the usb cable removed, hold POWER + VOL DOWN (not up) + HOME until the Samsung boot logo comes up, hold for another couple of seconds then release. Download mode should appear.
Click to expand...
Click to collapse
Is the home button actually working, are you pressing it firm enough?
If the home button doesn't register then the tablet will simply reboot.
Its a bit odd why twrp doesn't fully boot though unless it's the wrong one.
Does it hang at the twrp logo or continually reboot?
I'm not very familiar with phone terms but the situation is like this:-
- suspected like bricked
- connect USB to computer and press Volume Up + Power = USB Logo with white load bar
- disconnect USB and turn on = Repeatedly show Asus logo
- disconnect and press Volume Up + Power = USB Logo with red bar with a splash off Asus logo and turn off (a blink an eye)
- real problem is unable to enter droidboot/fastboot
I have tried to search for the thread to solve this problem but not successful yet. Method that I have tried so far:-
- installing iSocUSB
- installing Intel driver
- installing xfstk (FW+OS failed)
- installing MFT (not know which file that be used as zip/xml)
- run adb tools command (error: device not found)
- Intel SOC appear on device manager and when connect the phone to USB, it will appear CloverView too.
- installing asus pc link
- installing PDANet
I have seen most thread and discussion mention a phrase like "press volume up + power and you will enter fastboot/droidboot" but how about IF I can't enter fastboot/droidboot; they not mention the step. What should I do to enter it? I also search for key "Z00D(ZE500CL) unable to enter droidboot/fastboot" but result from google shows as what I mention before; the phrase "press volume up + power and you will enter fastboot/droidboot" which not working on me.
can anyone help to solve this problem?
please read detail... power button + volume up not working
no solution here?
bakzlags said:
I'm not very familiar with phone terms but the situation is like this:-
- suspected like bricked
- connect USB to computer and press Volume Up + Power = USB Logo with white load bar
- disconnect USB and turn on = Repeatedly show Asus logo
- disconnect and press Volume Up + Power = USB Logo with red bar with a splash off Asus logo and turn off (a blink an eye)
- real problem is unable to enter droidboot/fastboot
I have tried to search for the thread to solve this problem but not successful yet. Method that I have tried so far:-
- installing iSocUSB
- installing Intel driver
- installing xfstk (FW+OS failed)
- installing MFT (not know which file that be used as zip/xml)
- run adb tools command (error: device not found)
- Intel SOC appear on device manager and when connect the phone to USB, it will appear CloverView too.
- installing asus pc link
- installing PDANet
I have seen most thread and discussion mention a phrase like "press volume up + power and you will enter fastboot/droidboot" but how about IF I can't enter fastboot/droidboot; they not mention the step. What should I do to enter it? I also search for key "Z00D(ZE500CL) unable to enter droidboot/fastboot" but result from google shows as what I mention before; the phrase "press volume up + power and you will enter fastboot/droidboot" which not working on me.
can anyone help to solve this problem?
please read detail... power button + volume up not working
Click to expand...
Click to collapse
you have to make xFSTK recognize the device properly.. install intel android usb driver as well along with intel soc. only way to enter fastboot is to install it temporary with xFSTK
sukhwant717 said:
you have to make xFSTK recognize the device properly.. install intel android usb driver as well along with intel soc. only way to enter fastboot is to install it temporary with xFSTK
Click to expand...
Click to collapse
how to make xFSTK recognize my device when bootloop or charging?
Did you found a solution? Same problem
waltermaffy said:
Did you found a solution? Same problem
Click to expand...
Click to collapse
first turn off your hone by holding power button more than 10 second. run xfstk, change timeout to 500 second in option. now load file and click begin download. now connect your phone to pc and. turn the phone on while pressing and holding volume down button
sukhwant717 said:
first turn off your hone by holding power button more than 10 second. run xfstk, change timeout to 500 second in option. now load file and click begin download. now connect your phone to pc and. turn the phone on while pressing and holding volume down button
Click to expand...
Click to collapse
Ok, I'll try very soon. Thank for reply.
What files did you used? there are a lot around and I'm not sure if mines could work
waltermaffy said:
Ok, I'll try very soon. Thank for reply.
What files did you used? there are a lot around and I'm not sure if mines could work
Click to expand...
Click to collapse
use what ever you have. just try again and again. you can get files from my thread. and tips too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
use what ever you have. just try again and again. you can get files from my thread. and tips too.
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
I can't solve my problem I've tried any possible files. I made a right installation of the drivers disabling signature using win10. When I turn on my phone appears "Intel inside" and I need to shut down the phone, pressing and holding power button + vol up in order to make appear usb logo that stay there for just 1 sec and then it shutdown again. Connecting my phone to the pc in that second I can make detected it and the usb logo on the phone is still there. Pressing "Begin Download" the download start but it stops after the 5%, the bar under the usb logo on the phone became red, and the log tells me "Windriver Error: 0x20000015, timeout expired" after xfstk tried to send OSIP.
I don't know if the issue could be the wrong files, or drivers, or something on the GPflags. Any help? Thanks for reading
waltermaffy said:
I can't solve my problem I've tried any possible files. I made a right installation of the drivers disabling signature using win10. When I turn on my phone appears "Intel inside" and I need to shut down the phone, pressing and holding power button + vol up in order to make appear usb logo that stay there for just 1 sec and then it shutdown again. Connecting my phone to the pc in that second I can make detected it and the usb logo on the phone is still there. Pressing "Begin Download" the download start but it stops after the 5%, the bar under the usb logo on the phone became red, and the log tells me "Windriver Error: 0x20000015, timeout expired" after xfstk tried to send OSIP.
I don't know if the issue could be the wrong files, or drivers, or something on the GPflags. Any help? Thanks for reading
Click to expand...
Click to collapse
sorry buddy i posted wrong link. i have written guide to unbrick ZE500CL and provided link for required files
---------- Post added at 07:08 PM ---------- Previous post was at 07:08 PM ----------
waltermaffy said:
I can't solve my problem I've tried any possible files. I made a right installation of the drivers disabling signature using win10. When I turn on my phone appears "Intel inside" and I need to shut down the phone, pressing and holding power button + vol up in order to make appear usb logo that stay there for just 1 sec and then it shutdown again. Connecting my phone to the pc in that second I can make detected it and the usb logo on the phone is still there. Pressing "Begin Download" the download start but it stops after the 5%, the bar under the usb logo on the phone became red, and the log tells me "Windriver Error: 0x20000015, timeout expired" after xfstk tried to send OSIP.
I don't know if the issue could be the wrong files, or drivers, or something on the GPflags. Any help? Thanks for reading
Click to expand...
Click to collapse
sorry buddy i posted wrong link. i have written guide to unbrick ZE500CL and provided link for required files
http://forum.xda-developers.com/zenfone2/general/guide-bring-to-life-zenfone-2-ze500cl-t3503144
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
bakzlags said:
I'm not very familiar with phone terms but the situation is like this:-
- suspected like bricked
- connect USB to computer and press Volume Up + Power = USB Logo with white load bar
- disconnect USB and turn on = Repeatedly show Asus logo
- disconnect and press Volume Up + Power = USB Logo with red bar with a splash off Asus logo and turn off (a blink an eye)
- real problem is unable to enter droidboot/fastboot
I have tried to search for the thread to solve this problem but not successful yet. Method that I have tried so far:-
- installing iSocUSB
- installing Intel driver
- installing xfstk (FW+OS failed)
- installing MFT (not know which file that be used as zip/xml)
- run adb tools command (error: device not found)
- Intel SOC appear on device manager and when connect the phone to USB, it will appear CloverView too.
- installing asus pc link
- installing PDANet
I have seen most thread and discussion mention a phrase like "press volume up + power and you will enter fastboot/droidboot" but how about IF I can't enter fastboot/droidboot; they not mention the step. What should I do to enter it? I also search for key "Z00D(ZE500CL) unable to enter droidboot/fastboot" but result from google shows as what I mention before; the phrase "press volume up + power and you will enter fastboot/droidboot" which not working on me.
can anyone help to solve this problem?
please read detail... power button + volume up not working
Click to expand...
Click to collapse
sorry buddy use this link to unbrick. any question post in that thread.
http://forum.xda-developers.com/zenfone2/general/guide-bring-to-life-zenfone-2-ze500cl-t3503144
My ADB is On in settings and I can use ADB normal. But when my Phone is off I can't turn it on anymore the only way would be with ADB command: ADB reboot devices!
Power button + Volume UP/DOWN isn't working anymore...
The thing is, when connecting my Phone to my PC after it gets off it will show the charging animation. And when my phone reached 100% it stays in the animation and doesn't boot up. ADB isnt working in that state.
How can I boot my phone?? Pls I hope someone can help me PLS PLS
You must try conclude pins on motherboard for button volume up when you connecting USB cable, after that fastboot was started and you can type fastboot reboot command on pc.
my volume up button broken and i need that to flash stock rom again as phone in bootloop and cant access recovery,phone boots and shows logo for 1 sec and reboots again any ideas plz i flashed the oneos rom
ireaper4592 said:
my volume up button broken and i need that to flash stock rom again as phone in bootloop and cant access recovery,phone boots and shows logo for 1 sec and reboots again any ideas plz i flashed the oneos rom
Click to expand...
Click to collapse
If you have power and volume-down buttons functioning, boot the phone with the power button and when the bootloader unlocked warning comes up, press the volume-down button and you will get the options for restart, fastboot, recovery etc. Simply choose what you want with the volume-down button and confirm with the power button.
tnsmani said:
If you have power and volume-down buttons functioning, boot the phone with the power button and when the bootloader unlocked warning comes up, press the volume-down button and you will get the options for restart, fastboot, recovery etc. Simply choose what you want with the volume-down button and confirm with the power button.
Click to expand...
Click to collapse
yes got that problem is i need volume up button to work so i can put in adb mode so i can flash stock rom,i decrypted my devices then installed the oneos rom and thats when i lost access to recovery and goot into bootloop?
I do not know in depth about all this stuff, I've just been thrown into it because my phone decided to brick itself in a system update after it got into my hands. I updated it and it went into crash dump, a few times, the just nonstop boot looped with the oneplus logo on, and some pixels bugging, then it stopped showing the oneplus logo all together and just boot loops, I can go into fast boot and nothing else, if I restart bootloader it now goes to a charge menu and rarely actually restarts fast boot, I just tried msm and I've tried booting into twrp but it wont work, i believe this is because the phone wont connect to my pc properly but i have tried universal adb drivers, new sdk, and official QUALCOMM ones to all get the same result of appearing in device manager as just andrioud and nothing else with no options for drivers, on msm it would show up but it wouldn't get past waiting for device. also i cant find a proper twrp rom for the 9 pro on here, atleast the stock one, nor can i find it anywhere else, i can only find the img. also i feel I'm missing something with flashing on the fastboot and am not seeing if I'm supposed to be doing something (of the limited things i can do) on the phone, or its all in commands and stuff on here. sorry this is horribly written, I'm tired and stressed because of this.
Search stock rom and download
unzip rom ,connect your phone in download mode and flash STOCK ROM.
DaNyaWa said:
Search stock rom and download
unzip rom ,connect your phone in download mode and flash STOCK ROM.
Click to expand...
Click to collapse
what is download mode
Shaggers said:
I do not know in depth about all this stuff, I've just been thrown into it because my phone decided to brick itself in a system update after it got into my hands. I updated it and it went into crash dump, a few times, the just nonstop boot looped with the oneplus logo on, and some pixels bugging, then it stopped showing the oneplus logo all together and just boot loops, I can go into fast boot and nothing else, if I restart bootloader it now goes to a charge menu and rarely actually restarts fast boot, I just tried msm and I've tried booting into twrp but it wont work, i believe this is because the phone wont connect to my pc properly but i have tried universal adb drivers, new sdk, and official QUALCOMM ones to all get the same result of appearing in device manager as just andrioud and nothing else with no options for drivers, on msm it would show up but it wouldn't get past waiting for device. also i cant find a proper twrp rom for the 9 pro on here, atleast the stock one, nor can i find it anywhere else, i can only find the img. also i feel I'm missing something with flashing on the fastboot and am not seeing if I'm supposed to be doing something (of the limited things i can do) on the phone, or its all in commands and stuff on here. sorry this is horribly written, I'm tired and stressed because of this.
Click to expand...
Click to collapse
I suggest to try the MSM tool again.
MSM tool for OP9pro you can find here : MSM tool OP9pro
More guides how to use it find here : MSM guide
Shaggers said:
what is download mode
Click to expand...
Click to collapse
You shod download "EDL" tool (even called MSN)
unzip and exetute ad admin (read specifications and troubleshooting in the related thread)
ensure tour phone is off
press and keep both volume buttons while connecting it to PC
then the COM X connection should become "green + connected"
go with "start" and just wait the processo to end
Shaggers said:
what is download mode
Click to expand...
Click to collapse
Volume up+power
DaNyaWa said:
Volume up+power
Click to expand...
Click to collapse
Download mode is not vol up + power, that's bootloader
EDL (Download mode) is both vol buttons + power
It should show up in the device manager on the computer as a Qualcomm device if it's worked correctly.
djsubterrain said:
Download mode is not vol up + power, that's bootloader
EDL (Download mode) is both vol buttons + power
It should show up in the device manager on the computer as a Qualcomm device if it's worked correctly.
Click to expand...
Click to collapse
EDL mode is NOT both Volume buttons + Power, it's just HOLDING BOTH THE VOLUME BUTTONS and WHILE HOLDING THE VOLUME BUTTONS, CONNECT THE USB CABLE. The phone needs to be in a switched OFF state before doing this.
By holding both volume buttons and the power button, you will force restart your phone into bootloader mode (fastboot mode).
And VOLUME UP + POWER BUTTON is recovery mode.
djsubterrain said:
Download mode is not vol up + power, that's bootloader
EDL (Download mode) is both vol buttons + power
It should show up in the device manager on the computer as a Qualcomm device if it's worked correctly.
Click to expand...
Click to collapse
Sory ok
Powerup+powerdown
DaNyaWa said:
Sory ok
Powerup+powerdown
Click to expand...
Click to collapse
Power up + power down?
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Renate said:
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Click to expand...
Click to collapse
I will try this
I found the issue:
> EDL exits after 10 seconds if it is not captured by the MSM tool.
> The MSM tool only monitored 4 of my 10 USB ports
> So it was not captured because I was plugged in to an unmonitored USB port and rebooted after 10 seconds
> I have successfully used the MSM tool now
Oh! A bit off-topic, but I have never understood why EDL is commonly used over a "serial" port.
The interface that EDL presents is a generic USB bulk interface with two endpoints. You can use it just like that.
But no. They have to use a Qualcomm driver that makes it look like a "serial" port and then you can connect to that.
Me? I use a generic "WinUSB" Zadig driver. I have an EDL client that just connects to that fine.
So does the Python client implementation.
Also, I've never run into that 10 second timeout.
TraktorHenk said:
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Click to expand...
Click to collapse
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
ekin_strops said:
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
Click to expand...
Click to collapse
Thanks for the help. The problem ended up to be a bit different than this for me, but this is a good post for anyone to find in the future!