Database Develop

[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.

Backup Data from Malfunctioning(Soft-Bricked?) not-Rooted Locked M7

Hi,
My One M7 started malfunctioning all of the sudden and now cannot boot android and stuck at HTC splash screen.
I would like to recover contacts and data(pdfs, images) from the phone.
The device is not-rooted, locked(as it seems in bootloader) and stock rom is installed.
On my PC drivers are installed(ADB mode) and ADB, FastBoot up-to-date.
When I'm in HBOOT 1.61 I choose fastboot mode and I plug the phone via USB2 to the Win10 machine.
I can see fastboot USB in red and send the command
Code:
fastboot devices
it returns the serial of my device.
But when i try
Code:
adb devices
command i get empty list.
So i cannot backup.
I also tried to
unplug USB and plug it back in
Code:
adb kill-server
Code:
adb start-server
Code:
adb devices
But still get empty list of devices.
Also tried the recovery option in bootloader but I get empty list of devices for both
Code:
fastboot devices
Code:
adb devices
How can I backup my data?
Is it possible to unlock the device from bootloader install custom recovery(with backup features) without losing data?
Any help is much appreciated!

minamoto19 said:
Hi,
My One M7 started malfunctioning all of the sudden and now cannot boot android and stuck at HTC splash screen.
I would like to recover contacts and data(pdfs, images) from the phone.
The device is not-rooted, locked(as it seems in bootloader) and stock rom is installed.
On my PC drivers are installed(ADB mode) and ADB, FastBoot up-to-date.
When I'm in HBOOT 1.61 I choose fastboot mode and I plug the phone via USB2 to the Win10 machine.
I can see fastboot USB in red and send the command
Code:
fastboot devices
it returns the serial of my device.
But when i try
Code:
adb devices
command i get empty list.
So i cannot backup.
I also tried to
unplug USB and plug it back in
Code:
adb kill-server
Code:
adb start-server
Code:
adb devices
But still get empty list of devices.
Also tried the recovery option in bootloader but I get empty list of devices for both
Code:
fastboot devices
Code:
adb devices
How can I backup my data?
Is it possible to unlock the device from bootloader install custom recovery(with backup features) without losing data?
Any help is much appreciated!
Click to expand...
Click to collapse
You don't say what version of ADB you're using. Try this version, worked for me on W10
http://minimal-adb-and-fastboot.software.informer.com/1.1/
http://external.informer.com/forum.xda-developers.com/showthread.php?p=42407269#post42407269

Adb works ONLY in booted ROM or custom recovery. So, you can only use fastboot when in bootloader. Also, unlocking bootloader will erase all your data, so that's not a good idea

minamoto19 said:
Hi,
My One M7 started malfunctioning all of the sudden and now cannot boot android and stuck at HTC splash screen.
I would like to recover contacts and data(pdfs, images) from the phone.
The device is not-rooted, locked(as it seems in bootloader) and stock rom is installed.
On my PC drivers are installed(ADB mode) and ADB, FastBoot up-to-date.
When I'm in HBOOT 1.61 I choose fastboot mode and I plug the phone via USB2 to the Win10 machine.
I can see fastboot USB in red and send the command
Code:
fastboot devices
it returns the serial of my device.
But when i try
Code:
adb devices
command i get empty list.
So i cannot backup.
I also tried to
unplug USB and plug it back in
Code:
adb kill-server
Code:
adb start-server
Code:
adb devices
But still get empty list of devices.
Also tried the recovery option in bootloader but I get empty list of devices for both
Code:
fastboot devices
Code:
adb devices
How can I backup my data?
Is it possible to unlock the device from bootloader install custom recovery(with backup features) without losing data?
Any help is much appreciated!
Click to expand...
Click to collapse
Like said above, ADB commands only works from a custom recovery or from a booted rom with USB debug turned on.
Unlocking the bootloader will wipe the phone for obvious security reasons: anyone could simply unlock the bootloader and flash a recovery to extract data from anyone's phone.
If the phone isn't booting to the OS and your bootloader wasn't already unlocked, your data are lost, sorry. Thats why you should sync your important files or make regular backup on a computer.
You might be able to recover your phone using a RUU or by unlocking the bootloader and flashing a recovery + rom but again your data is lost.

alray said:
Like said above, ADB commands only works from a custom recovery or from a booted rom with USB debug turned on.
Unlocking the bootloader will wipe the phone for obvious security reasons: anyone could simply unlock the bootloader and flash a recovery to extract data from anyone's phone.
If the phone isn't booting to the OS and your bootloader wasn't already unlocked, your data are lost, sorry. Thats why you should sync your important files or make regular backup on a computer.
You might be able to recover your phone using a RUU or by unlocking the bootloader and flashing a recovery + rom but again your data is lost.
Click to expand...
Click to collapse
Well I somehow made it to kernel.
When the device boots it show me a message of:
"Please wait while android is updating" or something similar.
After 10 secs or less the android boots as normal but after a couple of minutes the phone freezes like the first time.
The good thing is that adb devices returns the device id.
I tried to:
Code:
adb backup -f backup.ab -all
I can see that the backup starts but it cant finish before the device hangs.
It freezes around 1GB of filesize. I turn it off by pushing the power button for 10-15 secs and after that the device wont turn on at all.
I have to wait for a couple of hours before the device responds again.
Next try was:
Code:
adb backup -f backup.ab -shared -nosystem
Although the phone hangs and not responding the backup was complete.
Now I'm ready to do a factory reset, but I would like to know whats included in "shared" option for a non-rooted phone.
Will I lose the contacts and gallery after all or have been backed up?

minamoto19 said:
Now I'm ready to do a factory reset, but I would like to know whats included in "shared" option for a non-rooted phone.
Will I lose the contacts and gallery after all or have been backed up?
Click to expand...
Click to collapse
I never had to use adb backup commands since I always make regular backups using twrp. Maybe someone else can answer this one.
Here is a guide that I just found, might give you some info you are looking for.
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351

alray said:
I never had to use adb backup commands since I always make regular backups using twrp. Maybe someone else can answer this one.
Here is a guide that I just found, might give you some info you are looking for.
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Click to expand...
Click to collapse
Thanks for the link.
The first post is pretty much explaining the adb manual (adb help command)
Some of the posters reported that -shared option backed up the contacts.
Anyway I'll have to check it myself.

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......

OnePlus3t bricked can only boot into fastboot, however my ADB driver no longer works

I have ran into a bit of an odd problem due to me messing up a root and then messing my phone up even more while trying to fix it.
my phone is fully bricked and only boots into fastboot mode. i tried to fix it with the one-plus fixer (idk its official name) but i got an error 7. I now need to re flash an older version of TWRP and try a diffrent method but i cant as my phone no longer is recognized in fastboot using the ADB tool. I have the USB driver installed on Windows. On Linux i ran the .sh script as root and it still doesn't work.
I have both Ubuntu and Windows installed on my PC so i can do whatever you suggest me to do regardless of the os.
Thank you to anyone that can help in advanced
Malte

This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.

You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.

I want to be able to do that but if i do adb devices it no longer finds my phone
Didgeridoohan said:
You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.
Click to expand...
Click to collapse
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command

Ive done this but it didnt fix my phone.
przemcio510 said:
This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.
Click to expand...
Click to collapse
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now

Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
Like I said, the adb commands won't work while in the booloader (that's why it's called fastboot mode). You need to use fastboot commands... The equivalent command would be:
Code:
fastboot devices

Bandella said:
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now
Click to expand...
Click to collapse
I had the same issues with md5, all you have to do is try a different USB port. I suggest the ones on your motherboard if you're on a PC. Then run the tool as administrator. I hope this helps, good luck!
P.S if it still doesn't work, try a different PC, I'm 100% sure it'll work

Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
As Didgeridoohan touched upon, adb and fastboot (while related) are different. They have different requirements and applications.
adb won't work while the device is in fastboot mode. Conversely, when the device is able to use adb, fastboot commands won't work.
adb: only works booted to OS or alternately in TWRP. Debugging must be enabled
fastboot: only works in bootloader-fastboot mode. Debugging is not required to be enabled.
For flashing TWRP, it's fastboot that you need. Well, there is a way to do it with adb, but fastboot is by far the more common way.
When in fastboot mode, adb command won't work, and there fore it is completely expected that "adb devices" yields not response. Try "fastboot devices" (no quotes) and if you get the phone's ID in response, you are in business.

Bandella said:
...
my phone ... only boots into fastboot mode...
Click to expand...
Click to collapse
I've had this happen to me when I've triggered dm-verity. Instead of getting the dm-verity warning display the phone would simply boot straight back to fastboot.
My solution was to:
- flash the latest TWRP using
Code:
fastboot flash recovery <recovery file. img>
- reboot into recovery (use the volume keys on the phone to select recovery and then press the power key)
-flash the full stock image I was using before the problem started
This would clean up any changes made to the boot and system images and allow me to boot the system normally.
Note: because this leaves you with a stock kernel you'll end up with the stock recovery after you boot the system.
Sent from my OnePlus3T using XDA Labs

boot your PC into Ubuntu and install adb/fastboot (tons of guides available off the 'net). then boot your 3t to dl mode and connect it to your PC. as mentioned already "fastboot devices" should list your 3t and you should now be able to flash to your heart's content. no need for drivers, unlike under Windows. i have a bootable linux usb drive primarily for this reason. curious what script you're trying to run though..

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