Database Users

Stuck unlocking my Atrix.

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

Bricked nexus 7 please read!

Hi,
I. Have gotten myself into quit a frustrating situation. My nexus 7 was unlocked, rooted and had several different custom roms installed at various times and had never had a problem. But then one time in particular, when trying to flash a rom (which I can't even remember which one it was,) after the rom had "successfully" been flashed, it rebooted to the splash screen, which it stayed at for a very long time; before just turning into a series of flashing vertical lines that never end. I can use the power+vol- method to get to fastboot, but not recovery; it would appear that my recovery has been wiped as I get the same google splash screen loop as when I try to boot. My problem is that nothing I do allows me to successfully connect the device to my pc (w7, 32bit.)
I have uninstalled any conflicting drivers, un/re-installed the proper drivers from like 7 different guides, I have also tried two different nexus root toolkits. I even tried to use a Linux machine to no avail. I have switched USB cables, everything I have tried has not worked. This is by no means my first foray into android devices, I even freshly installed my android SDK and still my computer just fails to recognize the nexus 7 in fastboot mode.
Any tips or advice would be a godsend. Thanks.

This sounds like a issue a few people have been having.. As far as i know as of a week ago there is no solution . You need to flash the boot-loader it sounds like. There is a thread about this. Search for NV FLASH .. OR APX MODE. Sorry for being lazy and not looking for the thread for you..
They may have some things in that thread that you have not tried.

Turn your Nexus off and plug it into your computer. Does your Nexus start charging? A completely bricked Nexus wouldn't charge. If it starts charging, then try turning it on into Fastboot mode.
Sorry, I'm no dev. Just a random thought to try. But if your Nexus can charge you shouldn't be fully bricked, hopefully. At least this is what I think.

When you say your computer fails to recognise the device...
If you open your device manager in Windows and then plug in the nexus 7 in fastboot mode, what happens? Does it show up in the device manager in any category? Even with a yellow exclamation mark or as unknown device?
Sent from my Nexus 7 using Tapatalk 2

My bro bricked his N7
He was rooted and unlocked, flashed a rom now it bootloops on the logo. Now when doing adb devices, it doesnt detect the device when in bootloader, went to device manager and shows problem with driver. Tried other drivers but says its up to date. Thing is I just upgared his friends N7 with the same drivers so I know thats not a problem.
It wont go into recovery either. Now when it is bootlooping, the decive is recognised when doing adb devices. So can I flash a factory image when it is bootlooping or does it have to be in fastboot?

TRY THIS
from powered down,
hold VOL- and POWER for ten seconds,. then let go of POWER and still hold down VOL-

dramdrum said:
When you say your computer fails to recognise the device...
If you open your device manager in Windows and then plug in the nexus 7 in fastboot mode, what happens? Does it show up in the device manager in any category? Even with a yellow exclamation mark or as unknown device?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
it doesn't even acknowledge that I plugged anything in to the computer at all.

chismay said:
TRY THIS
from powered down,
hold VOL- and POWER for ten seconds,. then let go of POWER and still hold down VOL-
Click to expand...
Click to collapse
Just goes to bootloader?
Edit seems to be working now even though when doing adb devices in fastboot it doesnt list the device id

In fatboot mode you don't have adb access - down load a recovery image and name recovery.img
Hold shift and right click in the folder recovery.img is in
Choose open command here, in cmd type
fastboot devices
If you see your serial number proceed
fastboot flash recovery recovery.img
When finished reboot to recovery and flash rom of choice
ps, you have had to either change your path in enviromental variables to include platform-tools from the sdk or have both fastboot.exe and recovery.img in the same folder that cmd is pointed to
Sent from my HTC Vision using xda premium

[Q] Cant access bootloader

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!

ADB doesn't see the phone in fastboot mode (although windows sees it)

Hello,
I'm trying to flash a TWRP, but for some reason the phone doesn't show up any more in adb when in fastboot mode (at the bottom of the phone screen it tells me to connect a USB cable). It was showing fine until yesterday. I have tried several different USB ports. The cable is definitely working (in fact plugging and unplugging it causes Windows to notice and make a sound, and also it works fine in ADB when the phone is booted up.
The only thing that I can think that happened since I had last connected to it in fastboot mode (to unlock the bootloader) is that I connected my PC to a couple other phones (Galaxy S3 and Nexus 5) using them in MTP mode. I have reinstalled Google and universal drivers several times, deleted the device from device manager, etc etc. No good.
Any ideas?

We gonna start off with are you using the right commands? Using Fastboot devices?
You must remember ADB and Fastboot are two different things. ADB is only when the phone is on and fastboot is only in bootloader mode

Simer03 said:
We gonna start off with are you using the right commands? Using Fastboot devices?
You must remember ADB and Fastboot are two different things. ADB is only when the phone is on and fastboot is only in bootloader mode
Click to expand...
Click to collapse
Arghhhh :-|
that was it, I was using adb devices. Thanks! (I feel dumb now)

Fastboot commands hang

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.