H E L P - bootlooping, COM does not recognize phone - Nexus 6P Q&A, Help & Troubleshooting

Hi everybody,
ill try to make it short:
My 6p has entered into the bootlooping mode.
I have never unlocked the bootloader/changed ROM/kernal.
After I let it bootloop until the battery is dead it's changing from bootlooping into blinking red dot. Then when I charge it for a couple of minutes it comes back to life after 10~ min it's bootlooping again - so I have a window of possibilities to play with the setting. In that window I have used the "OEM unlocking" option.
In the bootlooping state when I boot into the bootloader and connect it into the PC the device doesn't recognize that it has been connected and a PC ,and the PC recognize a entry of new device but doesn't recognize it is a Nexus 6p.
this situation is the same when I connect the phone when it is alive.
I have installed adb and fastboot with this software
https://forum.xda-developers.com/showthread.php?t=2588979
with the 1.4.3 version it shows in the end of the process "0 files copied" and then I tried the 1.3 version and it showed that 4 files were copied but it also showed an error.
I have also downloaded ADB from google site but it does not work either.
When I try to open the powershell in a folder where I have downloaded an img and type in a fastboot command the computer doens't recognize any type of command.
So if anyone can help me ill be glad.
Thanks in advance,
Matan.

matan4442 said:
Hi everybody,
ill try to make it short:
My 6p has entered into the bootlooping mode.
I have never unlocked the bootloader/changed ROM/kernal.
After I let it bootloop until the battery is dead it's changing from bootlooping into blinking red dot. Then when I charge it for a couple of minutes it comes back to life after 10~ min it's bootlooping again - so I have a window of possibilities to play with the setting. In that window I have used the "OEM unlocking" option.
In the bootlooping state when I boot into the bootloader and connect it into the PC the device doesn't recognize that it has been connected and a PC ,and the PC recognize a entry of new device but doesn't recognize it is a Nexus 6p. Matan.
Click to expand...
Click to collapse
What is the new device identified as....Qualcomm HS-USB QDLoader 9008? Your phone may be stuck in EDL mode. If that is the case you need to search XDA and attempt solutions for that problem first.
Did you previously have your PC setup properly with the correct USB drivers and it was working OK, or just now trying to get your dead phone to communicate? If the former it may be the EDL issue above. If it was the latter, the communication problem may just be the drivers were never set up in the first place. Have you tried a different cable or port on your PC, or another PC?
With no access to the OS you will be unable unlock the bootloader or access to ADB because those have to be enabled FIRST in the OS, so there's no helping you here until you can actually boot into the OS. Do you have access to Recovery mode? Tried a factory reset? If you don't have recovery, that was a major omission.

Related

[Q] Can go to fastboot but USB device not detected by PC

I did OTA update to 4.3 of my N7 3G which was rooted and unlocked (I know now I shouldn't have done it...).
I got an error at the end of the update (when was installing radio).
Rebooted, and got stuck in the google loop...
NOW, I CAN ENTER FASTBOOT MODE, BUT THE PROBLEM IS THAT THE USB DEVICE IS NO MORE DETECTED BY THE PC (I tried Windows XP, Windows 7, Linux), so I cannot re-flash it... It's not a driver's issue, because at USB level the N7 is not even detected when connected to the PC (for instance, dmesg shows nothing in ubuntu and windows does not "beep").
Is it possible that that was corrupted only the "USB stack" of the bootloader??? I could not find a similar issue in this or other forums (??).
Is there any chance to get the USB working again?
Is there any chance to send it for repair to ASUS (I bought it one month ago) with this described symptoms and with the "unlocked" icon on power on?
Is there a payed service to flash it with JTAG?
Thanks to anyone who can give me a clue...
Same problem - updated to 4.3 OTA today, N7 not recognized as an USB device at all. Still haven't tried on a Mac but I doubt it will be any different. The device isn't detected in normal mode or fastboot
c0ldblooded said:
Same problem - updated to 4.3 OTA today, N7 not recognized as an USB device at all. Still haven't tried on a Mac but I doubt it will be any different. The device isn't detected in normal mode or fastboot
Click to expand...
Click to collapse
I solved by sending it to assistance. Excellent service by ASUS... I did not have to pay although the tablet was unlocked/rooted.
Andrea.
since the new update to 4.3, N7 requires authorization with your pc before you can use ADB. I had this issue and had to go into developer options and click on the 'Revoke USB debugging authorization'. when I connect it to the pc again and ran adb, my N7 then asked for authorization to allow pc access. That restore my ADB.
Also make sure you have the lastest SDK installed on your pc too.
If you can enter Fastboot via pc you certainly can reflash it.
dilldoe said:
since the new update to 4.3, N7 requires authorization with your pc before you can use ADB. I had this issue and had to go into developer options and click on the 'Revoke USB debugging authorization'. when I connect it to the pc again and ran adb, my N7 then asked for authorization to allow pc access. That restore my ADB.
Also make sure you have the lastest SDK installed on your pc too.
If you can enter Fastboot via pc you certainly can reflash it.
Click to expand...
Click to collapse
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea
andreabix said:
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea
Click to expand...
Click to collapse
Exactly the case. Unfortunately I can't send it to ASUS
andreabix said:
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea
Click to expand...
Click to collapse
you said you could boot into fastboot, did 'fastboot devices' on your pc not detect it? Does it detect it now?
dilldoe said:
you said you could boot into fastboot, did 'fastboot devices' on your pc not detect it? Does it detect it now?
Click to expand...
Click to collapse
That's the point: I could boot into fastboot but 'fastboot device' was not detected by the PC (so I could not re-flash it). Now if I boot into fastboot the PC correctly detects the device...
What I find very, very strange is that an OTA update to 4.3 caused the USB port to stop working!! From what I read googling around, even with a problem during a system update going to fastboot mode (on + volume down) should always allow a connection to the PC for reflashing, or, at least, you could enter APX mode (on + volume up), which is an even lower level mode that is detected by the PC with different drivers (for direct programming, but need encryption key and SW not yet available for Nexus 7).
Maybe it was just a coincidence: an USB hardware failure just before I did the OTA update, which I realized only afterwards, when I needed USB for reflashing...
However the ASUS Service Repair Report states:
Problem/Symptoms: Pad Battery can't be charged. OS ERROR
Replaced Part:
ME370TG BAT COSLI-POLY FPAC
ME370TG MAIN_BD.1G/T30L/NFC
The first one looks the battery (????)
The second sounds like the mainboard...
Andrea

[Q] Nexus 4 recognised as qualcomm device 'bricked'

Hi all, I posted several questions in the Nexus 4 Q&A thread but the situation has gone from bad to worse so decided it would be easier to just create my own thread...
This started off with being unable to boot the phone into the OS, Fastboot and Recovery mode were both accessible although wiping the cache failed to do anything it just returned unable to mount cache errors.
I then attempted to unlock the bootloader so I could load a custom recovery and try repairing, however upon selecting "yes" to unlock the phone the screen flashed the fastboot screen up then went blank and has stayed blank since, all I get now is a qualcomm usb device detected when I plug it in.
Installed Qualcomm drivers and the phone is recognised as being in download mode in QPST but from what i've read on this site so far it seems no one has been able to unbrick a Nexus 4 using QPST?
I read the unbrick guide using LGNPST, the software recognises a device being connected but it keeps prompting that the phone is off or unplugged even though windows is still detecting it as plugged in (qualcomm device detected, no noise for device unplugged etc).
Finally if I hold down vol-/+&power when connecting the USB lead the red LED comes on (solid) for about 3 seconds.
Do I have any option other than RMA?

Stuck at twrp loading screen, no other boot options is working.

hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
senny22 said:
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
Click to expand...
Click to collapse
both volume buttons + plug the wire doesn't work?
senny22 said:
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
Click to expand...
Click to collapse
I have exactly the same problem, could you solve it? I'm very worried about my phone
ale0796 said:
I have exactly the same problem, could you solve it? I'm very worried about my phone
Click to expand...
Click to collapse
Hi! When I held both volume buttons and the power I dunno in what mode I was in but while my phone was on this mode and plugged in to my PC it was recognized in device manager as ADB something (I don't remember). I was shocked when I saw that my PC would recognize the phone because no LEDs was lit (not even the red LED you get in edl mode) and also my phone would start instantly with pressing the power button, (in edl it takes about 10 to restart the phone). Anyway so I tried zadig, Qualcomm drivers and even a different pc but it would still connect as ADB something. Lastly I disabled automatic driver updates in windows and installed the qualcomm axon 7 firmware driver (Google it). After that I rebooted and my phone was now recognized as "qualcomm hs loader" something and so I could use Miflash to flash a stock firmware. Miflash would work right away though but after maybe 15 tries and lots of reboots it then worked for some reason I don't know. After that I had a stock recovery back and it was all going smooth again from there.
senny22 said:
Hi! When I held both volume buttons and the power I dunno in what mode I was in but while my phone was on this mode and plugged in to my PC it was recognized in device manager as ADB something (I don't remember). I was shocked when I saw that my PC would recognize the phone because no LEDs was lit (not even the red LED you get in edl mode) and also my phone would start instantly with pressing the power button, (in edl it takes about 10 to restart the phone). Anyway so I tried zadig, Qualcomm drivers and even a different pc but it would still connect as ADB something. Lastly I disabled automatic driver updates in windows and installed the qualcomm axon 7 firmware driver (Google it). After that I rebooted and my phone was now recognized as "qualcomm hs loader" something and so I could use Miflash to flash a stock firmware. Miflash would work right away though but after maybe 15 tries and lots of reboots it then worked for some reason I don't know. After that I had a stock recovery back and it was all going smooth again from there.
Click to expand...
Click to collapse
THANK YOU SO MUCH, after 30 more attempts, I get the xiaomi miflash flashed my device, the last thing I tried was to disconnect the phone, keep the power button for 10 seconds and then connect it. The device was recognized as "Qualcomm HS-USB QDLoader 9008" download this rom https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip unzip it and select the folder with miflash and flash it. Miflash did not send me the "can not get hello package" message anymore. I really appreciate it a lot, without your message I would probably have kept my phone in a box and forget it. I hope all people can read this comment and solve this problem. THANK YOU
ale0796 said:
THANK YOU SO MUCH, after 30 more attempts, I get the xiaomi miflash flashed my device, the last thing I tried was to disconnect the phone, keep the power button for 10 seconds and then connect it. The device was recognized as "Qualcomm HS-USB QDLoader 9008" download this rom https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip unzip it and select the folder with miflash and flash it. Miflash did not send me the "can not get hello package" message anymore. I really appreciate it a lot, without your message I would probably have kept my phone in a box and forget it. I hope all people can read this comment and solve this problem. THANK YOU
Click to expand...
Click to collapse
Really glad I could help

Nexus 6p boots into fastboot, not detected by pc

The other day I was trying to flash my 6p back to stock so I can sell it, and I was flashing everything through cmd, until all of a sudden cmd stopped working towards the end for some reason. Now my phone only boots into fastboot mode and is NOT being detected by my pc. When it's plugged in, the fastboot menu says to connect the data cable. I've tried restarting my computer and reinstalling the drivers, but nothing seems to work. When I go into cmd and type adb devices, nothing shows up when it's plugged in, and device manager doesn't show any changes whether it's plugged in or not.
I've called local cellphone repair shops, but apparently if it's not Samsung or iPhone they can't help
Btw I've searched the forums and haven't found a solution to this problem.
Robertdudeman said:
The other day I was trying to flash my 6p back to stock so I can sell it, and I was flashing everything through cmd, until all of a sudden cmd stopped working towards the end for some reason. Now my phone only boots into fastboot mode and is NOT being detected by my pc. When it's plugged in, the fastboot menu says to connect the data cable. I've tried restarting my computer and reinstalling the drivers, but nothing seems to work. When I go into cmd and type adb devices, nothing shows up when it's plugged in, and device manager doesn't show any changes whether it's plugged in or not.
I've called local cellphone repair shops, but apparently if it's not Samsung or iPhone they can't help
Btw I've searched the forums and haven't found a solution to this problem.
Click to expand...
Click to collapse
Can you enter recovery?
No I can't enter recovery

Moto G4 got stuck

My friend tried to root his moto g4. Now his phone got stuck. When he starts his phone it enters the fastboot mode and when he tries to connect it with pc it says usb not recongized. Oem is locked and usb debugging is off. And when i try to enter in recovery mode it comes back to fastboot mode. Any solutions?
Pranill said:
My friend tried to root his moto g4. Now his phone got stuck. When he starts his phone it enters the fastboot mode and when he tries to connect it with pc it says usb not recongized. Oem is locked and usb debugging is off. And when i try to enter in recovery mode it comes back to fastboot mode. Any solutions?
Click to expand...
Click to collapse
He should unlock bootloader before root. Yes there is solution. You must install all need drivers. Then try computer see your phone as qualcomm driver. If it is not recognized, try soft mode or safe mode or something in your computer and then try after restart, try many times. After seen as qualcomm driver you must run flashbat or flashbank bat file via administrator maybe or not for write bootloader and then type run commands in fastboot via computer. Files is next thread: search google - guide how to unbrick noto g4 plus. Desktop in one folder must be all files - adb and fastboot or something whats name, flashbank.bat file, stock rom files. I had same problem and solved for me but bootloader was unlocked. Main is that your phone must seen as qualcomm driver, first time mine was usb not recognized and then changed computer soft or safe or something different mode on or off

Resources