I have all of the proper drivers and the cable I'm using is good and the USB port I am using is good. However, everytime I put my phone into the bootloader mode where the screen goes black and the white text shows up, it disconnects from the computer. Then when I go to type in fastboot oem bootloader the command prompt just says searching for device.
Related
I'm currently attempting to root my atrix but I've come across a problem that I can't seem to be able to solve through googling or otherwise.
I'm using the tutorial stickied on the Atrix homepage labelled [HOWTO MAY16].
I got as far as step 8 and my phone passed the sbf flash using RSD lite but continuing on with the process to step 13 where it is asking me to type "fastboot oem unlock" into cmd I get an error message telling me that cmd is waiting for my device but nothing seems to happen.
I've tried reinstalling drivers (64 bit), restarting computer, restarting phone, trying different leads/usb sockets with no change to my result.
The exact thing that I'm doing with cmd is to navigate to the platform-tools folder, open adb, open flashboot and then attempt fastboot oem unlock.
Additional information:
UK Orange Atrix 4G running 3.4.4
using IHOP sbf file
running windows 7 64-bit, using the 64-bit drivers.
Do you have access to win 7 or xp? Win 8 is really new and possibly that could be the problem. Worth a shot.
pre4speed said:
Do you have access to win 7 or xp? Win 8 is really new and possibly that could be the problem. Worth a shot.
Click to expand...
Click to collapse
Ops, typo. I'm running Windows 7 64-bit. I'll edit my post when xda allows me to.
Unlock
Enter the bootloader program by powering off the phone, Hold the volume down key and the power at the same time. The phone will be in the bootloader program when it powers up, use the volume down key to scroll through bootloader menu options. the second option will be fastboot program. Select the fastboot option with the volume up key, this will enter the fastboot mode of operation. Connect the phone to the PC via USB cable. Enter the directory where the fastboot program resides on the PC. Type the Fastboot oem unlock command. If sucessful a message will display on PC retuned by the phone. Reboot phone and unlocked will display in the upper left corner of the phones display. Continue to follow the original post, flash recovery, root phone, flash custom ROM. Happy Flashing, Enjoy! :fingers-crossed:
fdaconta said:
Enter the bootloader program by powering off the phone, Hold the volume down key and the power at the same time. The phone will be in the bootloader program when it powers up, use the volume down key to scroll through bootloader menu options. the second option will be fastboot program. Select the fastboot option with the volume up key, this will enter the fastboot mode of operation. Connect the phone to the PC via USB cable. Enter the directory where the fastboot program resides on the PC. Type the Fastboot oem unlock command. If sucessful a message will display on PC retuned by the phone. Reboot phone and unlocked will display in the upper left corner of the phones display. Continue to follow the original post, flash recovery, root phone, flash custom ROM. Happy Flashing, Enjoy! :fingers-crossed:
Click to expand...
Click to collapse
I just gave it another try and it gets stuck after I type fast boot oem unlock. I definitely have the right directory but I still get stuck here. Cmd just tells me it's waiting for my device and stops there. I think it's a driver issue after a bit of googling but the official drivers aren't working. This socks.
I had a similar problem with my device not showing up. There wasn't really a big fix for it but I just waited longer before trying to execute the command. I'm not sure if you're experiencing the same thing I did but when it couldn't detect my device it just hadn't been recognized by the computer yet. Make sure your drivers are working (connect usb and select every option on the pull down menu and are sure the device gets installed). After that do the same thing as before for fastboot but make sure you securely plug it in and wait for the computer to detect your phone before you move forward
Sent from my MB860 using xda app-developers app
Hi all you good people, I have a nexus 4 with a bootloop also additional problems are:
1. Im a complete novice and can only do things with simple instructions (sorry!)
2. No debugging mode was enabled
3. I only have a Mac
4. The Mac is not showing the device with the android transfer app and also I've tried a few things in terminal - but again comes up with device not found.
I can get to the Postboot mode by pressing the power/volume buttons so thats okay, on that screen it says: SECURE BOOT - enabled & LOCK STATE -locked
I have tried all the clear cache/restore factory on the recovery screen and taken the battery out for a while but to no avail.
thanks in advance!
You should unlock the bootloader and then flash a stock Google image. Unlocking the bootloader will wipe all data on the phone.
First thing would be to at least get the phone to recognize fastboot commands. Not sure if this will help: http://forum.xda-developers.com/showthread.php?t=1917237
audit13 said:
You should unlock the bootloader and then flash a stock Google image. Unlocking the bootloader will wipe all data on the phone.
First thing would be to at least get the phone to recognize fastboot commands. Not sure if this will help: http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Thankyou that is really helpful how ever when I type in: ./adb devices it dosnt list any devices including my phone, if I try a command such as:
./fastboot oem unlock
it just hangs on: "waiting for device"
The USB cable is good as I tried it with another device - could it be a damaged USB female socket on the device itself?
thanks
Adb commands will not work when the phone is in fastboot mode.
With the phone connected and in fastboot mode, type "fastboot devices" and press enter. It should return your phone's serial number. If not, try different USB cables and USB ports.
audit13 said:
Adb commands will not work when the phone is in fastboot mode.
With the phone connected and in fastboot mode, type "fastboot devices" and press enter. It should return your phone's serial number. If not, try different USB cables and USB ports.
Click to expand...
Click to collapse
Thanks when you say 'fastboot' mode - how do I get it in that mode?
audit13 said:
Adb commands will not work when the phone is in fastboot mode.
With the phone connected and in fastboot mode, type "fastboot devices" and press enter. It should return your phone's serial number. If not, try different USB cables and USB ports.
Click to expand...
Click to collapse
is there a command line I can input for fastboot?
nexus4uk said:
is there a command line I can input for fastboot?
Click to expand...
Click to collapse
Fastboot mode is when you boot into the bootloader where it said secure boot enabled.
Sent from my Nexus 4 using XDA Labs
To enter fastboot mode on the phone, power off the phone, press and hold volume up + volume down + power at the same time.
audit13 said:
To enter fastboot mode on the phone, power off the phone, press and hold volume up + volume down + power at the same time.
Click to expand...
Click to collapse
Thanks tried this - and and nothing came up with the command 'fastboot devices' - thanks anyway
If nothing comes up when executing the command, that tells me the drivers are not installed or the connection between the phone and computer is not good.
HI
How can I install the drivers on a mac? thanks
This may help: http://forum.xda-developers.com/android/general/adb-fastboot-binaries-os-x-inclusive-t2941205
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
I want to unlock the bootloader of my phone using the unofficial method. I reboot my phone into fastboot mode using "adb reboot bootloader" and plug my phone to my laptop. Fastboot detects my devices, however, when I try to execute any command, for example "fastboot reboot", the command hangs. There is no output and I can't send a SIGINT signal to it either by pressing Ctrl+C. It should actually reboot my phone instead of hanging. Also, sometimes my phone would just display "Press any key for shutdown" right after I plug it to the laptop (similar to what's happening here). I tried running same commands on my old Zenfone Selfie (Z00T, ZD551KL) on fastboot and they work fine, I could even flash a custom recovery with no issues.
My system parameters:
Processor is Intel Core i5-8250U.
Operating system is Ubuntu 20.04 LTS.
ADB and fastboot versions are 1:8.1.0+r23-5ubuntu2 each.
My phone's firmware is PKQ1.WW_Phone-16.2017.1912.060-20191125
So far I've tried:
Changing the cable I use to connect my phone with my laptop. No results.
Changing the port I connect my device to from USB 3.1 to USB 2.0. No results.
Using a different fastboot version (the one that came with the unofficial bootloader unlock method). Nothing either.
Using a Windows 10 virtual machine, connecting my phone to it and executing fastboot commands there. No results either.
Updating my phone's firmware to 087, also Pie version. No results either.
Updating my phone to the beta version of Q, 438. No results.
Unplugging the phone during the process of command hanging and then plugging it back. Results vary. Sometimes it takes exactly 3.02 seconds and it does nothing, sometimes it would display the aforementioned "Press any key for shutdown" message.
Executing the command on my laptop and then plugging my phone in. Same as the previous point.
Executing "fastboot oem device-info" instead, using a method described in the previous point. It says "FAILED (remote: unknown command)"
Rebooting my phone to fastboot mode with Volume Up + Power and through recovery mode. No results.
Any idea what could be the issue and how do I solve it? Since ASUS stopped supporting our device, I would really like to unlock the bootloader of my phone so I could install custom ROMs.
Thank you for your time.