This device uses the same command as the Pixel 2 to unlock the bootloader:
Code:
fastboot flashing unlock
So far I have not been able to successfully flash an entire factory image. I tried a single partition, /vendor, with success.
Let us know your results with flashing!
Does it require unlock_critical?
Is there a different set of update fastboot drivers needed to unlock the bootloader? My phone and cord are recognized for adb commands but nothing for fastboot ones? Never mind had to do it from a Windows shell as min fastboot would not work.
Archangel said:
Is there a different set of update fastboot drivers needed to unlock the bootloader? My phone and cord are recognized for adb commands but nothing for fastboot ones? Never mind had to do it from a Windows shell as min fastboot would not work.
Click to expand...
Click to collapse
I ran into the same issue and downloaded the latest platform tools and it unlocked fine. I just had to unplug the phone and replug it in while in fastboot for my laptop to recognize it.
Sent from my Pixel 3 using Tapatalk
Related
Ok ive spent the last 2 hours trying to unlock my bootloader on my lg-h901. Ive done everything from adb to nexus root toolkit. Ive installed every lg samsung google and universal driver rebooted my computer and everything. I can reboot my device using adb and it shows adb devices connected. When i type fastboot oem unlock it stays on waiting for device for ever. What am i doing wrong?
dillonorden said:
Ok ive spent the last 2 hours trying to unlock my bootloader on my lg-h901. Ive done everything from adb to nexus root toolkit. Ive installed every lg samsung google and universal driver rebooted my computer and everything. I can reboot my device using adb and it shows adb devices connected. When i type fastboot oem unlock it stays on waiting for device for ever. What am i doing wrong?
Click to expand...
Click to collapse
Could be a bad cable.. Do you have OEM unlock checked in developer options.
Wait.... Are you typing fastboot oem unlock when connected to ADB? Because you need to be connected to Fastboot in the bootloader, not ADB in the OS to do an unlock
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode. I get a blank space in return. Can anyone help me with this? ADB works fine, it's only Fastboot. Is there a Fastboot driver that I might be missing?
Thank you.
Edit: I'm trying to unlock the bootloader of my phone.
Me too !
Drivers are here: https://developer.android.com/studio/run/win-usb
These are the ones I use for ADB/Fastboot.
May I ask if anybody solved this already?
Having the same issue, tried various drivers, but fastboot won't find my phone
Help is highly apperciated!
Clock
If you using windows 10 have you disable the drivers signature verification.. And search on here (XDA) for Min ADB & Fastboot tools, easier than using SDK tools unless you modding apks ect..
Okay, I got this working.
When in fastboot mode, you have to go to the device manager, update driver, and manually choose the google fastboot driver. Then the ! is gone and it works.
Fastboot drivers for Xperia XZ1
Redcalibur said:
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode.
Click to expand...
Click to collapse
I add a hint to the solution that is working for me (Windows 7, 64 bit): https://forum.xda-developers.com/showpost.php?p=79221714&postcount=44
Redcalibur said:
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode. I get a blank space in return. Can anyone help me with this? ADB works fine, it's only Fastboot. Is there a Fastboot driver that I might be missing?
Thank you.
Edit: I'm trying to unlock the bootloader of my phone.
when u connect phone to pc choose no data transfer then open cmd and write: adb reboot fastboot
Click to expand...
Click to collapse
I am having trouble rooting my Galaxy J7 Prime sm-j727t
Every Odin version I use with every TWRP tar file I try to use doesn't work. They either Fail or Odin stops responding when I try to load the tar file into the AP.
I've tried just using the CF Auto Root and those fail as well.
Any ideas what the issue is? I've been trying for two days with no success
Is your bootloader unlocked?
Emir Çetin said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
I thought Samsung phones come with bootloader unlocked already??
BramaKnox said:
I thought Samsung phones come with bootloader unlocked already??
Click to expand...
Click to collapse
You can check bootloader with dialer (search it).
Of phone has fastboot mode you can check bootloader with fastboot commands (search it too)
Emir Çetin said:
You can check bootloader with dialer (search it).
Of phone has fastboot mode you can check bootloader with fastboot commands (search it too)
Click to expand...
Click to collapse
When I put the phone in FastBoot mode I have the following options
Reboot System Now
Reboot to Bootloader
Apply update from ADB
Apply Update from SD card
Wide data/factory reset
Wipe Cashe partition
Mount /system
View recovery logs
Run graphics test
Power off
Lacking storage booting
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Emir Çetin said:
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Click to expand...
Click to collapse
Am I doing something wrong here ? see attached for screnshot
Emir Çetin said:
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Click to expand...
Click to collapse
I tried a some other steps. Tried using the video on youtube on a tut. When I get to the oem unlock I just get stuck with a msg sayng "waiting for any device" my device is plugged in, from what I know I have updated the samsung drivers (from previous attempt of other methods) the adb bootloader cmd did put my phone into fastboot mode
(White box, blue arrow point down with a straight line under the point)
(Blue screen with Downloading...)
do not turn off target
What am I missing here?
I tried rooting TWRP 3.2.3. with Odin on the phone again and it still failed
Does anyone else have any more insight to a possible solution?
Have you checked bootloader with dialer?
BramaKnox said:
I am having trouble rooting my Galaxy J7 Prime sm-j727t
Every Odin version I use with every TWRP tar file I try to use doesn't work. They either Fail or Odin stops responding when I try to load the tar file into the AP.
I've tried just using the CF Auto Root and those fail as well.
Any ideas what the issue is? I've been trying for two days with no success
Click to expand...
Click to collapse
Witch android you are?
Hello, I don't know if anyone here has been there
Simply no computer recognizes my Mi A3 in fastboot mode, it appears as if there is nothing connected to the PC (I have tested it on other computers, all drivers are right, I tried with other cables, and nothing detected)
The adb works normal (Detects the device), MTP also (I can pass files from the PC to it), Only Fastboot that does not appear devices
My bootloader is unlocked, this happened a few days ago. I'm stuck on MIUI, because anything I do I can't use fastboot to fix.
I'm afraid to try EDL and he dies for good (He detects EDL Mode via the USB cable, holding volume down). Would you have any fix for that, be it opening it, removing the battery, shorting some part of the board?
What is the output when you type
Code:
fastboot devices
Or any fastboot codes you type?
garylawwd said:
What is the output when you type
Code:
fastboot devices
Or any fastboot codes you type?
Click to expand...
Click to collapse
C:\adb>fastboot devices
C:\adb>
My device manager also doesn't recognize the phone in fastboot
Andley302 said:
C:\adb>fastboot devices
C:\adb>
Click to expand...
Click to collapse
Looks like you don't have fastboot installed just adb. Your working from an adb folder are you sure you have the full platform tools installed or just adb?
garylawwd said:
Looks like you don't have fastboot installed just adb. Your working from an adb folder are you sure you have the full platform tools installed or just adb?
Click to expand...
Click to collapse
yes, fastboot is in that same folder, I even installed a Redmi 7A Stock via fastboot for him
Andley302 said:
yes, fastboot is in that same folder, I even installed a Redmi 7A Stock via fastboot for him
Click to expand...
Click to collapse
Only mi a3 does not work on fastboot, does not detect on any computer
I have recently purchased 3 used Nexus 9 tablets. I want to install a ROM with no Google apps, etc.
I have enabled developer mode, enabled USB debugging, enabled oem unlock.
I have successfully unlocked the bootloader, and re-setup the device, re-enabled usb debugging and booted back into the bootloader in "fastboot usb" mode using adb reboot bootloader (I have also entered fastboot usb mode by powering off and holding the volume down and power buttons.
When I send fastboot devices to the tablet, I get the device listed but without fastboot following it. When I try to flash TWRP, it hangs at the Sending 'bootloader' line. Same if I try to flash using Google's script.
I'm on Manjaro Linux, using android-tools 31.0.2.
The command I'm using is fastboot flash recovery twrp-3.5.2_9-0-flounder.img
If I send fastboot flashing get_unlock_ability I get the same hang at Sending 'boot.img'
It seems for some reason it won't actually respond to fastboot commands. Any suggestions? Is there some setting or file I need on the device itself to enable it? Is there a way to dd or something into the recovery partition?
I'm not great with Android, but I'm pretty good with desktop Linux.
Aloha.
Hours later, and I resolved this by installing the Android SDK and then using the SDK to install fastboot and adb into /opt. The versions there worked, the versions from the community repo and the AUR did not. No idea why.