Database Develop

phone doesn't boot (can only get to fastboot USB menu)

i can only access the white screen when i chose bootloader>recovery i get the /!\ sign.
i installed the USB driver and i was able to use only the "fastboot" commends. adb commend didn't work. when i type fastboot devices i get the serial no. of the device.
when i use the adb devices commend i get: "List of devices attached" and an empty line.
is it possible to fix this phone? thanx in advance.

Asilns said:
i can only access the white screen when i chose bootloader>recovery i get the /!\ sign.
i installed the USB driver and i was able to use only the "fastboot" commends. adb commend didn't work. when i type fastboot devices i get the serial no. of the device.
when i use the adb devices commend i get: "List of devices attached" and an empty line.
is it possible to fix this phone? thanx in advance.
Click to expand...
Click to collapse
adb only works within android since it's a debugger if I'm not mistaken. Try using fastboot to flash the system images of the stock rom back to their respective partitions. (ie. fastboot flash system system.img; fastboot flash boot boot.img; etc.)
You must be unlocked for that to work however.

problem solved
after almost 10 hours of research the solution was really easy.
1.download "recovery-RA-nexus-v1.6.2.img" and fastboot it using this commend:
fastboot-windows flash recovery recovery-RA-nexus-v1.6.2.img
2.flash a rom from SD card and everything should work fine

[Q] Unlock Bootloader Problem

Hi guys, I have a problem.
I want to flash my N1 with the Cyanogenmod, but I have a problem with Bootloader unlocking. I do exactly what here is written (in the N1 guide from wiki.cyanogenmod), but when I open CMD (win XP) and write "fastboot oem unlock", it just doesn't works, but "adb devices" works and shows my phone. What can I do ? Any ideas ?

You need to boot into bootloader to work with fastboot. And if "adb devices" shows your phone - you obviously didn't boot.
adb reboot bootloader
Click to expand...
Click to collapse
Also, for a more comprehensive guide, please read the Wiki.

Code:
C:\fastboot>fastboot oem unlock
'fastboot' is not recognized as a
operable program or batch file.
This is what it shows in bootloader mode.
P.S. I have already re-installed my drivers. I have to notice that when I try to reinstall the drivers (in fastboot mode), they always auto-install themselves and when I try to update them, they say that there isn't newer version.

Fastboot executable isn't in the same directory as ADB executable, and isn't in the path you're executing it from (which is C:\fastboot).
Check, what is the actual executable you're trying to run, and if you have one. It might be called fastboot-windows.exe, if you didn't get it from downloading the Android SDK.

There is a executable file named "fastboot-windows.exe", but when I try to run it, it just open and close for 1 second. Any ideas ?

I thought the message would be clear by now... Oh well.
Open command prompt.
Run:
fastboot-windows oem unlock
Click to expand...
Click to collapse

I think It's done but my computer shows this message (see attached) 5 mins and I don't know it's ready or not ? Could I turn on the phone ? (Sry for the easy questions but I'm a real noob, because that's my 1st Android phone.)

The "too many links" message doesn't look good.
Reboot your computer.
Reboot the phone.
Use different USB port in your computer.

Ok well if you want my input try "fastboot devices" this should return your S/N (starting with "HT") if it gives you the same error then I would reinstall the SDK.

HELP with adb and fastboot (fixed)

man, i am losing my mind over this now. i have no idea why my phone seems like it isn't recognized in adb fastboot. however, when i am not in fastboot it shows just fine.
before i go into fastboot mode on the phone i can use command prompt and it shows
>adb devices
List of devices attached
d858f4c6 device
i can even command the phone to go into fastboot
adb reboot bootloader - and my phone goes into fastboot
then when in fastboot:
i type fastboot devices - nothing listed
adb devices - nothing listed
what am i doing wrong here? everything seems to be fine before going into fastboot but once i am in fastboot none of the same commands work the device isn't recognized
yes, of course i have usb debugging turned on.
any ideas? i've been messing with this going on two hours now uninstalling my files and reinstalling them.
EDIT - ok it took me like 3 hours but the device needs different drivers when in fastboot but you can only fix it while its in fastboot on my machine for some reason

You can't use adb commands when in fastboot mode and vice versa.

knives of ice said:
man, i am losing my mind over this now. i have no idea why my phone seems like it isn't recognized in adb fastboot. however, when i am not in fastboot it shows just fine.
before i go into fastboot mode on the phone i can use command prompt and it shows
>adb devices
List of devices attached
d858f4c6 device
i can even command the phone to go into fastboot
adb reboot bootloader - and my phone goes into fastboot
then when in fastboot:
i type fastboot devices - nothing listed
adb devices - nothing listed
what am i doing wrong here? everything seems to be fine before going into fastboot but once i am in fastboot none of the same commands work the device isn't recognized
yes, of course i have usb debugging turned on.
any ideas? i've been messing with this going on two hours now uninstalling my files and reinstalling them.
EDIT - ok it took me like 3 hours but the device needs different drivers when in fastboot but you can only fix it while its in fastboot on my machine for some reason
Click to expand...
Click to collapse
I have same problems. Please explain how you have solved. Which drivers the Mi Mix needs in fast boot mode?

basically, you have to watch your device manager for the ANDROID to pop up and it should have a yellow exclamation. you have to fix the drivers, but the problem is at least in my case you have to complete and fix the drivers before the mix puts itselt out of fastboot and into charging (which it does quite quickly when not connected)
install this:
http://forum.xda-developers.com/showthread.php?t=2588979
and follow the guide that he posts in the pictures on what you need to change
here
http://forum.xda-developers.com/attachment.php?attachmentid=2480396&d=1388281089
as soon as you have the drivers fixed windows will tell you and the mix will stay connected

Cannot see my OnePlus 3T with fastboot with Ubuntu 16.10 Yakkety Yak

I'm using Ubuntu Yakkety Yak, 16.10.
According to Android SDK manager: Android SDK Tools v 25.0.3 Android Build Tools v 25.0.2 Android SDK Tools v 25.2.5
My phone is a OnePlus 3t and I'm developing for it for a while, adb works normally, udev rules are configured. I enabled OEM boot, and manage to reboot in a way which looks like to me fastboot. After rebooting to "fastboot" the device's USB id is exactly the same as in normal boot, that's a red flag.
Regular USB ID is Bus 001 Device 024: ID 05c6:676c Qualcomm, Inc.
I get the desired fastboot one when I switch the USB mode to MTP (Bus 001 Device 013: ID 2a70:9011).
My final goal is to unlock my phone ans install TWRP (for DayDream mod). Since fastboot devices doesn't show any device I cannot issue fastboot oem unlock.
Do I need some USB driver for Linux for the MTP mode? The Bus 001 Device 013: ID 2a70:9011 doesn't show any OEM manufacturer string.
This should just work. I don't get it. I'm tearing my hair out.
android.stackexchange.com/questions/169509/why-fastboot-devices-is-empty-on-ubuntu-16-10
android.stackexchange.com/questions/166033/how-to-flash-and-root-oneplus-3t-on-linux?noredirect=1&lq=1

MrCsabaToth said:
I'm using Ubuntu Yakkety Yak, 16.10.
According to Android SDK manager: Android SDK Tools v 25.0.3 Android Build Tools v 25.0.2 Android SDK Tools v 25.2.5
My phone is a OnePlus 3t and I'm developing for it for a while, adb works normally, udev rules are configured. I enabled OEM boot, and manage to reboot in a way which looks like to me fastboot. After rebooting to "fastboot" the device's USB id is exactly the same as in normal boot, that's a red flag.
Regular USB ID is Bus 001 Device 024: ID 05c6:676c Qualcomm, Inc.
I get the desired fastboot one when I switch the USB mode to MTP (Bus 001 Device 013: ID 2a70:9011).
My final goal is to unlock my phone ans install TWRP (for DayDream mod). Since fastboot devices doesn't show any device I cannot issue fastboot oem unlock.
Do I need some USB driver for Linux for the MTP mode? The Bus 001 Device 013: ID 2a70:9011 doesn't show any OEM manufacturer string.
This should just work. I don't get it. I'm tearing my hair out.
android.stackexchange.com/questions/169509/why-fastboot-devices-is-empty-on-ubuntu-16-10
android.stackexchange.com/questions/166033/how-to-flash-and-root-oneplus-3t-on-linux?noredirect=1&lq=1
Click to expand...
Click to collapse
Just OEM unlock from the settings...

domsch1988 said:
Just OEM unlock from the settings...
Click to expand...
Click to collapse
I wish it was that easy. The Settings option is more precisely called "OEM unlocking" with the explanation "allow the bootloader to be unlocked". So it just allows it, but does not do the unlocking itself. I turned this option on. For the unlocking I should issue the fastboot oem unlock command. I did try to install TWRP BTW without it, but obviously it didn't succeed. I need to unlock first, just as other tutorials say. For that I first have to see my phone in the fastboot devices list, which is empty. I'm still tearing my hair out.

MrCsabaToth said:
I wish it was that easy. The Settings option is more precisely called "OEM unlocking" with the explanation "allow the bootloader to be unlocked". So it just allows it, but does not do the unlocking itself. I turned this option on. For the unlocking I should issue the fastboot oem unlock command. I did try to install TWRP BTW without it, but obviously it didn't succeed. I need to unlock first, just as other tutorials say. For that I first have to see my phone in the fastboot devices list, which is empty. I'm still tearing my hair out.
Click to expand...
Click to collapse
Try running
Code:
sudo fastboot devices

casual_kikoo said:
Try running
Code:
sudo fastboot devices
Click to expand...
Click to collapse
Yes, sudo didn't make any difference from the beginning.

Hello,
I too am going crazy trying to get fast boot to work on this OnePlus 3T. My research prior to purchasing indicated that this phone was friendly to rooting. I'm no on hour 6, and still can't get fast boot to work. Using Ubuntu 16.04, and the adb and fastboot packages installed from the standard repositories (apt-get install adb..)
sudo, sudo -s, udev rules, etc. nothing has worked.
If anyone has used this phone and os combination to get the unlocking working, please advise.

I've found out the root cause of my problem. I thought that fastboot is one step further from the "actual" fastboot screen. You have to issue the fastboot commands when you see the screen what is in my android stackexhange link.

So I could unlock the bootloader now, now when I try to flash TWRP I get:
Code:
[email protected]:~/Android/Sdk/platform-tools$ sudo ./fastboot flash recover twrp-3.0.3-1-oneplus3t.img
target reported max download size of 440401920 bytes
sending 'recover' (17588 KB)...
OKAY [ 0.560s]
writing 'recover'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.580s

The USB device I see is
Code:
Bus 001 Device 018: ID 18d1:d00d Google Inc.
and I set up udev rules for it.

Ok, it was just a typo: recover -> recovery

Finally!
Thank you MrCsabaToth!
After 2 more hours trying this following instructions for Windows 7, and OS X (after Ubuntu 16), MrCsabaToth's reply looks to be the way to get past the fastboot oem unlock step.
You have to run it while actually on the phone's boot screen where it gives you options of what type of boot to do, where the top line option is "fast boot". Only then, will the fastboot command from the terminal work.
Not even the oneplus web site tutorial, which is for this exact phone, mentions this. WTF......

Cannot relock bootloader with Tool-all-in-one on ROG Phone 3

Hello,
despite presumably doing everything correctly, Tool spews this error when I'm trying to relock the BL by using "fastboot oem asus-lock" command:
FAILED (remote: 'Command not supported in default implementation')
1. I have connected the phone to the side port.
2. Tool folder is directly in C:\ directory.
3. ADB binaries are installed correctly.
4. Phone is in fastboot mode and detected, but the tool cannot detect correctly which phone it is and asks me to choose the model manually, but ROG 3 is not on the list, so I chose ROG Phone 2. Does it matter? If so, what do I do? I also set priviledges for Tool-all-in-one systemwide, does it matter?
Also, should I use the command line in Advanced Options of the tool, or should I rightclick the folder and summon the command line from there? Please help, I don't have any more ideas! Thank you!

use the side usb port (the top black one, not the bottom orange one) and try the command again through FB

Thank you for fast response!
I'm constantly using the sideport, and the command still fails with the message above.
What I can add is that EVERY fastboot process fails with the SAME message, so it's not just relocking that is the problem, but it seems that every fastboot command cannot be executed on my ROG Phone 3 (aside from fastboot devices, which correctly shows my device as connected).
Which suggests to me that something is wrong with my setup. Anybody has any idea?

When I try to relock my rog phone 3 I do the list devices command and it shows my device, I then reboot into fastboot
and type command fastboot oem asus-lock and all it says is <waiting for device> how can I relock bootloader???????? If there was an apk to unlock it shouldnt there be an apk to relock it?

You need install fastboot drivers on your pc, so device manager will see your phone