Hi!
I'm having a weird problem with this device, when i connect IT with USB debugging on and permission for OEM unlock, it shows from the prompt that the device is detected and so i can easily reboot it in fastboot mode. But after this point i'm getting stucked, the device isnt recognized and if i try to do any action it just get stucked in waiting for device screen. Any help? Thank You in andvance
Related
Hi,
I ran into a problem with my Nexus 4, the plan was to unlock the bootloader using my mac and fastboot. (used this as information but didn't follow it step by step, youtube.com/watch?v=fHZJ2f6JLw0)
I turned off the phone and went into the bootloader with volume down + power button. From here i used "fastboot devices" to secure that i was able to communicate with the phone. My device showed up together with an error message saying "ERROR: could not get pipe properties nexus 4".
Before doing any more i wanted to understand what this message meant so I searched the web without any success. I booted up my android, turned on usb debugging and used "adb devices". This time only my devices showed up and no error messages. I used the "adb reboot boatloader" to access the bootloader once again.
I still had the same error message with "flashboot devices" as before.
From here i didn't do anything more, I may have disconnected the usb from the computer while the terminal window was open and the phone in bootloader but without running any command from fastboot.
So I didn't run "fastboot oem unlock" or anything else.
I turned off the phone and tried to access the bootloader one more time with the volume down + power button. It didn't respond to this any more and nothing happened, the device just stayed turn off.
I turned on the phone and tried to use adb to access the bootloader but now when running the "adb devices" it just responds "-bash: adb: command not found".
I have tried to restore the phone thru the android setting meny without any success. The phone is working fine without any problem except i cant access the bootloader or use adb.
So I desperately need help from you guys. :crying:
Have any of you heard of this problem before?
Regards Rasmus
I have to change my statement.
Actually I succeeded rooting and installing CWM recovery using a win7 computer together with Nexus4 toolkit.
The issue i have right now is that i can't start the device into bootloader using volume and power buttons.
To access bootloader i have to go thru the toolkit and this can be an issue in case i flash a bad rom or kernel and can access android usb debugging.
Is it possible to restore the bootloader?
rallanand said:
The issue i have right now is that i can't start the device into bootloader using volume and power buttons.
Click to expand...
Click to collapse
Are you holding the down volume and pressing the power button?
What OS is the computer that you are using? If you have reset the device, make sure that USB debugging is checked again. I know it sounds dumb, but a lot of times it's the simplest things we forget. Once you factory reset your device, it resets everything.
If you are on Windows 7, make sure you are starting the command prompt from the same location your adb is installed. If you are on Ubuntu or another Linux distro, please let me know which one. This seems like it should be an easy fix for you, but a little more info is needed. Thanks!
I am trying to get into fastboot mode to unlock my bootloader. I enabled usb debugging, and allowed the oem unlock mode. when I press volume down and power button, i do not see "fastboot mode" anywhere. in device manager, my device shows up with a exclamation mark and triangle. I installed the google usb driver via sdk manager. when i type "fastboot devices" on my desktop, my 6p does not show up. how can I get this to work?
sniper8752 said:
I am trying to get into fastboot mode to unlock my bootloader. I enabled usb debugging, and allowed the oem unlock mode. when I press volume down and power button, i do not see "fastboot mode" anywhere. in device manager, my device shows up with a exclamation mark and triangle. I installed the google usb driver via sdk manager. when i type "fastboot devices" on my desktop, my 6p does not show up. how can I get this to work?
Click to expand...
Click to collapse
Holding power + volume down will get you to the bootloader, this is fastboot mode. Is the phone in this mode when issuing the "fastboot devices" command? Does Windows show any driver installation/update dialogue when you connect the phone in this mode?
Yes, it is.
I believe a driver installation popup came up before.
Heisenberg said:
Holding power + volume down will get you to the bootloader, this is fastboot mode. Is the phone in this mode when issuing the "fastboot devices" command? Does Windows show any driver installation/update dialogue when you connect the phone in this mode?
Click to expand...
Click to collapse
It also tells me to connect a usb data cable, when it's already plugged in.
So I found a usb driver, and it works now. Up to the point where I go into TWRP, but it asks for a password to decrypt the data. So I enter the password I use to get onto my phone, and it gets to "Unable to mount storage. Full SELinux support is available." Where do I go from here?
Are you using the Android N Dev Preview?
I am not being able to unlock my K4 Note no matter and I will have to admit it's so frustrating. I am not new to unlocking and modding party but i just cannot get to have this done!
I downgraded from S230 to s218 & now on s219. I am able to get adb to recognize my device but not fastboot. Thus I am unable to unlock bootloader!
When I type in " adb reboot bootloader" or click on the "unlock_recovery.bat" file provided, I get booted into a dark screen where "fastboot" is written at the bottom left & the command prompt window says < waiting for device> & I am stuck there until I reboot my phone.
i have been seeking an answer to this since the last 3 days but am yet to find one
This is problem with the driver, I too had problem. Do enable usb debugging, connect to PC, it will ask permission in phone, give ok. Now a lenovo folder will appear on PC, click on usb driver installation, done.
Now try adb and fastboot device will detect.. Also i hope u enabled oem unlock in usb debugging
Hit Thanks if it helped!!!
Same problem
I am also facing the same problem
Please provide solution if you found one
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.
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