One plus 9pr complete brick. Cannot access fastboot or recovery. Will not turn on and when I plug in only shows a connect a chargwer screen. It is charged. I cannot get msm tool to connect either.
What led up to this point?
We'll need more info than this:
Are you using a Windows computer?
Is it Windows 10?
Have you plugged in USB via USB port on the computer or USB hub? (Should always plug directly into the computer)
Windows 10 has driver signature checks on by default, the Qualcomm drivers are not signed so you need to disable signing before trying to use MSM tool : https://www.tenforums.com/tutorials...river-signature-enforcement-windows-10-a.html (I usually use option 2, BCDEdit)
Here's the Qualcomm EDL drivers : https://www.androidfilehost.com/?fid=14943124697586335873
You need to press both VOL buttons and POWER to get into EDL mode, make sure you choose the correct assignment from the top "TARGET" dropdown in the MSM tool too and make sure it's the correct MSM tool for your region/phone. They're all available from here
There's a decent guide here
There's a video here for OnePlus 8/8 Pro but it's the same technique (remember to give him a like if he helps you out ) :
If the MSM tool doesn't show "CONNECTED" on any COM port then keep the cable connected and try rebooting the phone back into EDL mode again, it will eventually show up.
Related
Hi everyone,
My zenfone 2 ZE551ML is bricked, so i followed this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
The problem comes when i arrived to the step of IntelSoc:
I install it, no problem until here, i got IntelSoc driver in my device manager .
But when i want to have the MOOREFIELD driver, I cant get it. Following this perfectly
Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables( I don't have hanging cables though, I just have the Logo Asus and write on the top in blue Fastboot mod !!!).
-Connect to your computer via USB cable, to standard Intel SOC driver position, wait a few seconds if the current add an item immediately below another MOOREFIELD new devices is successful.
-If You have not been, the test performed as follows: turn off the machine, plug the cable into the computer, press the power button until the device vibrates slightly, then release.
If you have an idea can you help me please. I think this is the only thing who blocks me in repairing my phone...
Thank you
Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.
Anagh21 said:
Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.
Click to expand...
Click to collapse
it is clearly instructed in that thread you mentioned. just keep few things in mind.. uninstall every mobile related driver before installing isoc. uninstall xFSTK tool if you already installed it before installing isoc. third as you are concerned about the line you mentioned morefield under intel soc. well during soc install you will see windows like attached below. at this stage you need to power cycle your device . ( turn off your device holding power button for 10 sec. then connect to pc and turn on. leave connected to pc and turn off again and turn on second time to make sure so driver are installed) don't worry if you don't see morefield under soc now. just go ahead and install xFSTK. now your concern that your device don't stays in morefield download stage ( i mean it appears in device manager and disapear) . after installing xFSTK. run it as administrator and load files. and change gp flag value. also change device detection timeout to 120. now click begin download it will start waiting for device. now turn off your device completely and connect to pc and turn on. xFSTK will force it to stay in required mode. if download do not starts. just power cycle the device while being connected to the tool.
( note: it is strongly recomended that you install isoc and connect mobile before installing. if you have already installed xFSTK then plz uninstall it and install it after performing above said steps. remove all other mobile related drivers also and if you are using windows 8 or 10 disable driver signature enforcement again even if you did it earlier)
The problem with asus flash tool solved
Solution : Open device manager i.r. Windows + X .... if your phone is not being detected... switch it on and off ... there will be ( other devices menu ) that will show your phone there..
right click on the phone , click update drivers, ofcoarse no drivers online, locate the drivers manually , wherever your bootloader file is i.e. the 1 gb file you download or the raw file as we can speak ... i didn't pin pointed it ... my file was on the desktop so I just chose desktop and it searched it and installed it.
After that the phone was successfully in the computer and being detected by the flash tool.
I followed all the instructions on the Internet by donwloading the flash tool, kmz file, and everything else. I followed all methods and none of them work! When I press Install button when everything is set up in the flash tool, the support tool window does appear, and it always says 'The computer and your phone has been disconnected. Please try again by plugging your phone again." Are there any solutions to this?
p.s. my phone is currently bricked which means that I cannot boot, and I did not enable USB Debugging in Developer Options.
You need to install LG drivers on PC, then you need to enter download mode on your phone. Phone turned off then hold volume up + volume down and connect it to PC via USB cable. It will show download mode on the screen. Only then you can flash new kdz file using LG Flash Tool. If I remember correctly flash tool will show error connecting to server but just ignore it (do not press ok) and just wait for it to finish. It will finish when your phone will power itself on into language configuration etc.
Doesn't work
The message does pop up saying that the USB connection is not properly plugged with my LG G Pro. It says nothing like Server Error
Can you see this on phone screen?
http://tech2mech.com/wp-content/uploads/2015/03/download-mode-lg-g-pro-f240.jpg
---------- Post added at 08:23 AM ---------- Previous post was at 08:19 AM ----------
second thing you need LG USB drivers install on your PC:
http://www.lg.com/us/support-mobile/lg-LGE980
1. Run flash tools under administrative mode and Windows 7 compatibility mode if on windows 8+. Even better, use it on Windows 7 machine.
2. don't use USB3 ports.
And make sure you're in download mode, it doesn't need usb debugging to work, but you have to boot it into download mode to be able to use flash tool.
So,
Now I got the issue that was the main culprit of the error happening while flashing in EDL mode through mi flash tool .. .
Current status of my phone- Nothings working no buttons working
Black screen
When I connect to PC blue led flashes. Without battery red led flashes only one time
Phone detects as Qualcomm HS USB qdloader 9008 port
And after that when I try to flash it .. the port kepps refreshing and the phone connects and disconnects...
On the device manager it seems that the qdloader 9008 converts into diagonastics 9006 then reverts back to 9008. And in the disk management the Qualcomm mmc storage do the same just connects and 2 or 3 second later disconnects. Then reconects and disconnects..
And at that point the flash tool gives the error....
Changing usb wire and changing pc gives the same result .
Now please suggest me a way to get rid out of it.
The thread is very long sorry for that ....
Please help me out .
Windows driver issue maybe?
Are you sure that this is not a driver problem in Windows?
I have never tried flashing in Download Mode, but I'm just making a (possibly silly) guess.
Enable Test-signing in Windows and try again :-
Put this command in an elevated command prompt and restart the computer to enable test signing:-
Code:
bcdedit /set testsigning on
Good luck!
First trying with disable driver signature enforcement from boot option and now tried with cmd ran the code but same result. Is this my windows 7 problem?
I haven't tried it on windows 10....
Hi all
during without pc next to me. I’m using MacBook Pro to run windows 10 in virtual machine, but now the problem is appearing, how can I get my phone in edl mode and connect to windows? Cause normally, when I connect to MacBook, there’s options for me to choose connect to windows or Mac system. Please help.
Mr-Zhag said:
Hi all
during without pc next to me. I’m using MacBook Pro to run windows 10 in virtual machine, but now the problem is appearing, how can I get my phone in edl mode and connect to windows? Cause normally, when I connect to MacBook, there’s options for me to choose connect to windows or Mac system. Please help.
Click to expand...
Click to collapse
Why do you need EDL mode? If you already unrooted and your phone is working, you shouldn't need MSM. That is mainly used to recover a bricked device.
To get in EDL mode, power off the phone and unplug from the computer. Hold down Vol+ and Vol- while you connect USB to computer. Keep holding both Vol buttons until it gets to EDL mode. I don't know about your virtual machine, you'll just have to look at settings and see if there are different options for how to handle USB devices.
adb reboot edl
is my preferred way when possible. I also found on my windows computer I needed the non-64bit Qualcomm USB driver or my device would just reboot after going into EDL mode.
UPDATE: The issue stands solved [see post 5].
........................................................................................................................................................................
I am facing a rather intriguing issue wherein the device tends to automatically exit EDL Mode after around 5 seconds. During that short-time frame, the Device Manager recognizes it in EDL Mode as Qualcomm HS-USB QDLoader 9008. Even the MSM Tool is able to identify the connected device. However, right after a few seconds the device gets booted to the OS.
So could anyone let me know why is this happening and more importantly how it could get rectified. [Windows Driver Signature Verification is disabled and Qualcomm USB Drivers are successfully installed].
Moreover, currently I'm on Pixel Experience ROM. So are custom ROM's known to cause any conflict with EDL Mode?
EDIT My device is not bricked and I could easily access the OS [Pixel Experience]. However, I still want to use MSM Tool as opposed to say, Fastboot Enhance Tool, for testing purpose. So any insights in this regard will be highly appreciable.
My way was :
Launch MSM Tool
Launch Phone into Recovery
Connect USB Cable
Advanced -> allow ADB
On PC : adb reboot edl
As soon as the Device Screen turns black, Phone gets detected in MSM Tool and then Start Process. That worked for me
ohwarumbloss said:
My way was :
Launch MSM Tool
Launch Phone into Recovery
Connect USB Cable
Advanced -> allow ADB
On PC : adb reboot edl
As soon as the Device Screen turns black, Phone gets detected in MSM Tool and then Start Process. That worked for me
Click to expand...
Click to collapse
I face the same issue on my OnePlus 9 and this help me. Thank you so much.
binary**# said:
I am facing a rather intriguing issue wherein the device tends to automatically exit EDL Mode after around 5 seconds. During that short-time frame, the Device Manager recognizes it in EDL Mode asQualcomm HS-USB QDLoader 9008. Even the MSM Tool is able to identify the connected device. However, right after a few seconds the device gets booted to the OS.
So could anyone let me know why is this happening and more importantly how it could get rectified. [Windows Driver Signature Verification is disabled and Qualcomm USB Drivers are successfully installed].
Moreover, currently I'm on Pixel Experience ROM. So are custom ROM's known to cause any conflict with EDL Mode?
EDIT My device is not bricked and I could easily access the OS [Pixel Experience]. However, I still want to use MSM Tool as opposed to say, Fastboot Enhance Tool, for testing purpose. So any insights in this regard will be highly appreciable.
Click to expand...
Click to collapse
were you able to find any work around. I am currently on OOS 12 F.22. I am having another issue of widevine L1 certification as my device has L3 certificate. To rectify this i am trying to use MSM tool.
raoakashyadav said:
were you able to find any work around. I am currently on OOS 12 F.22. I am having another issue of widevine L1 certification as my device has L3 certificate. To rectify this i am trying to use MSM tool.
Click to expand...
Click to collapse
Sorry for the delay in reply. Yup, I fixed this issue via the Disable Driver Signature Verification tweak as shown in this video. In short -->
Install Qualcomm USB Driver and download MSM Tool.
Boot your device to EDL Mode and connect it to your PC.
Then DO NOT disable Driver Signature Verification on your PC.
So as of now, your device will be listed as Qualcomm HS USB QDLoader under Device Manager but will have a yellow exclamation mark [because Drive Signature is enabled]. But at the same time, Windows will hold your device in this ELD Mode and wouldn't let it boot to the OS [which is what we wanted].
So while having your device connected to your PC in EDL Mode, now disable Driver Signature Verification. With this, your device should now stay in EDL Mode and will be listed without any yellow warning sign under Device Manager. You could now proceed ahead with the flashing via MSM Tool without any issues.