Related
OK so I have an issue that I just cannot seem to fix. I've followed Max Lee's guide to unlocking the bootloader, obtaining root, and getting twrp. I've followed the written and video instructions to the t and a few guides in here, I have installed and updated the proper drivers and sdk tools, but my hitch is when I type the "fastboot oem Unlock" command, it says it finishes but my device doesn't reboot and ask if I want to proceed to unlock my bootloader, instead it just stays on the fastboot logo and does nothing until I restart it. This happens on both my mac and my pc so I'm not sure what the issue is I have usb debugging enabled and the allow oem Unlock slider is in the on position, any help or advice 8s greatly appreciated, thank you.
Sent from my ONE A2005 using Tapatalk
do you run an actual version of sdk-tools? fastboot recognized your phone, right? You can test it with following command: fastboot devices
Output is something like this:
33a0cde4 fastboot
Click to expand...
Click to collapse
nevermind i just fixed it, thanks
hi,
trying to flash the breadcrust recovery using my linux pc, but the Z1 doesn't appear in the list of devices when running adb devices. Image attached. Normally I would get a request to accept the RSA key for a trusted pc when enabling usb debug. But I don't get this option.
- Adb tools are loaded and working on my linux laptop
- My nexus 7 responds to ADB devices and shows up ok
- tried on wifes windows laptop with adb/sdk tools loaded and no joy there too
- i have developer USB debug options enabled, i've tripple checked this
could it be the cable? I'm using the one which came with the phone, so that should be ok?!!
cheers
SOLUTION - I ran this One Plus Two script modified with the Z1 device ID and now I can see my device in adb devices and interact with it. I get the SHA screen to allow access and can run commands from linux terminal. YAY!
See the attachments for script.
I think it´s a driver fault. Did u install them in windows?
im using linux, i dont get any rsa pop up confirmation either!
EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
and that was the reason, why i installed windows last night. as long you dont get rsa pop up, the device will not listed (i think so)
EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
But u said, that u tried ur wifes Windows notebook. Did u install the drivers there?
ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.
MKKLR21 said:
ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.
Click to expand...
Click to collapse
Good tip - I'll give it a go.
My nexus 7 works as expected on all PCs and laptops Linux/windows so it must be the phone
Sent from my Nexus 7 using Tapatalk
Maybe sudo or check this:
http://1.bp.blogspot.com/-rDdBnJTh870/U-hxVzxMf3I/AAAAAAAAKwQ/WrZkaMjaReo/s1600/Unlock-Bootloader-linux-terminal-xperia-z.png[img/]
Source: [url]http://linuxwelt.blogspot.de/2014/08/cyanogenmod-unter-linux-installieren.html[/url]
ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader, but the device doesn't boot into fastboot, just reboots as normal!
I could also hold down up/down volume buttons and get into the bootloader, but again the device isn't picked by any fastboot oem checks for unlocking!!
arrrgh!!!
You'll have to add -i switch followed by the device ID to your fastboot command. I don't have it at hand, so just read the TWRP thread.
ok! Some progress...ish.
running "adb reboot bootloader"command in windows worked when I switched Cyanogen recovery updates off in developer options. The Z1 reboots into bootloader.
Running "fastboot -i 0x2b4c oem get-device-info" returns nothing just "....."
So I tried "fastboot -i 0x2b4c oem unlock" an error returns cannot unlock use command "fastboot -i 0x2b4c oem unlock-go" which works. The phone wipes data and reboots back into OS.
I re-enable the developer options and adb debug. and reboot into bootloader
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
weird!
Your commands are simply wrong, thats why they don´t work.
It is:
fastboot -i 0x2b4c oem device-info
fastboot -i 0x2b4c oem unlock-go
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
Click to expand...
Click to collapse
Flashing does NOT work on the international version, you have to boot into it directly from fastboot.
fastboot -i 0x2b4c boot z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img
Should be correct instead of the flash command.
EggZenBeanz said:
ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader...
...
Click to expand...
Click to collapse
What made the change? I was able to see the RSA screen only once, but after device restored to defaults I can't get it back. same drivers installed, and it appears in the device manager.
I honestly don't know, it just worked after many attempts. I read somewhere about USB 3 ports with Linux so might be the same for windows?
Sent from my Z1 using Tapatalk
It's an USB 3.0 issue. Plug the phone into an USB 2.0 port, or an USB 2.0 hub plugged into an USB 3.0 port and it will magically start working. God knows why this is the case...
Ironically, fastboot works fine even on USB 3.0...
For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?
Planet X said:
For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?
Click to expand...
Click to collapse
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.
MrColdbird said:
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.
Click to expand...
Click to collapse
Okay, I have found out that it is impossible to boot from TWRP as log as the bootloader is locked. It just took me 2 hours to setup my phone again after unlock.
Have a look at this thread, I am going to give it a try later.
http://forum.xda-developers.com/showthread.php?t=2408802
This did the trick on Linux (Ubuntu):
- run on terminal "sudo gedit ~/.android/adb_usb.ini"
- put "0x2b4c" in
- run on terminal "adb kill-server" and "adb start-server"
And run the fastboot commands with "sudo".
Hi essential phone owners, I'm hoping you are willing to help me out.. Anyway, i used adb reboot bootloader for fastboot access after I enabled OEM unlock from the developer options. The device state is LOCKED. I then typed fastboot devices and received no permissions (verify udev rules). Does that mean I'm stuck on stock?
dirtyreturn said:
Hi essential phone owners, I'm hoping you are willing to help me out.. Anyway, i used adb reboot bootloader for fastboot access after I enabled OEM unlock from the developer options. The device state is LOCKED. I then typed fastboot devices and received no permissions (verify udev rules). Does that mean I'm stuck on stock?
Click to expand...
Click to collapse
What type of computer?
Hopefully, not using cable that came with the phone. Don't use it for flashing.
What are you trying to do?
tech_head said:
What type of computer?
Hopefully, not using cable that came with the phone. Don't use it for flashing.
What are you trying to do?
Click to expand...
Click to collapse
Thanks for your questions. I am using Ubuntu 18 I believe. I have a nexus 6p also, and adb/fastboot commands worked just fine with that phone. What i would like to do successfully is to unlock the bootloader and critical partition, flash twrp, and finally be able to flash AICP/Magisk.
Edit- from computer to phone I am using the extra type C USB cable that came with the 6p. And I must note that the essential is found using command adb devices. And command adb reboot bootloader gets me to the point of fastboot.
Ubuntu ?
sudo fastboot devices
I'm using Linux Mint, so basically Ubuntu. I created a file under /etc/udev/rules.d and put this line in it:
SUBSYSTEM=="usb", ATTR{idVendor}=="2e17", MODE="0666", GROUP="plugdev"
(My login ID is in the plugdev group.)
I'm able to execute adb and fastboot without needing sudo.
is there a root method for this version ? I try to unlock bootloader but when I open CMD type fastboot unlock OEM it said waiting for device. I already instal abd and OnePlus 6t driver so i don't know what else to do. Please help me
What I usually do is leave my OnePlus 6T unplugged from the computer, and run "fastboot oem unlock" or any other bootloader commands in terminal, when it says "waiting for device", I plug it back into the computer, the command will be processed. It's a bug in the bootloader.
***EDITED*** If the phone is still stubborn, just reboot it back into Fastboot Mode, and do above, it will finally do its job.
Sent from my OnePlus 6T using Tapatalk
I had same issue it was driver issue had to install qcom drivers open command in adb fastboot folder if that don't just flash oos fresh
I have a brand new Oneplus 8 Pro from China with global ROM installed.
I wanted to unlock the bootloader however there is no fastboot option in the boot menu.
There is Start, Restart Bootloader, Recovery and Turn Off.
The Fastboot option is missing.
I can connect the phone to my PC, adb recognizes the phone, but Fastboot is missing.
Any ideas?
Docomoco said:
I have a brand new Oneplus 8 Pro from China with global ROM installed.
I wanted to unlock the bootloader however there is no fastboot option in the boot menu.
There is Start, Restart Bootloader, Recovery and Turn Off.
The Fastboot option is missing.
I can connect the phone to my PC, adb recognizes the phone, but Fastboot is missing.
Any ideas?
Click to expand...
Click to collapse
Sure. You are allready in that mode. Just type fastboot devices and check..
I did that but no response.
The cursor jumps to the next line but there is no response from the phone.
If I type adb devices the phone is listed but the fastboot command doesn't return anything.
Docomoco said:
I have a brand new Oneplus 8 Pro from China with global ROM installed.
I wanted to unlock the bootloader however there is no fastboot option in the boot menu.
There is Start, Restart Bootloader, Recovery and Turn Off.
The Fastboot option is missing.
I can connect the phone to my PC, adb recognizes the phone, but Fastboot is missing.
Any ideas?
Click to expand...
Click to collapse
Restart to bootloader, then fastboot should work. If your phone is still on, and you can access adb, you should also be able to type adb reboot bootloader
Thanks.
So apparently the command "fastboot devices" returns nothing.
However I was able to unlock the bootloader just by entering "adb reboot bootloader" then
"fastboot oem unlock".
What confused me was that there is no "fastboot" option on the phone itself as there was on my Oneplus 5t.
Docomoco said:
Thanks.
So apparently the command "fastboot devices" returns nothing.
However I was able to unlock the bootloader just by entering "adb reboot bootloader" then
"fastboot oem unlock".
What confused me was that there is no "fastboot" option on the phone itself as there was on my Oneplus 5t.
Click to expand...
Click to collapse
The option in the power menu is called bootloader (fastboot only will work there) the hint was in the adb command I gave you, adb reboot BOOTLOADER. Not sure why they changed what the menu was called but I'm glad you got it sorted. To give you a short summary, adb will only work when your phone is powered on and booted into android, or if you have recovery mode open and on the adb section, and fastboot only works in the bootloader hope that could help!
Edit: fastboot devices should work but only in bootloader mode, not when your phone is started normally
Docomoco said:
I have a brand new Oneplus 8 Pro from China with global ROM installed.
I wanted to unlock the bootloader however there is no fastboot option in the boot menu.
There is Start, Restart Bootloader, Recovery and Turn Off.
The Fastboot option is missing.
I can connect the phone to my PC, adb recognizes the phone, but Fastboot is missing.
Any ideas?
Click to expand...
Click to collapse
You have to insert a SIM card, boot of the device and make a phone call to get it to register your device. Wait a few minutes and then restart your phone. Go into settings under about phone and enable developer options. Back out and go into developer options and you will see OEM unlock. You need to turn that on and USB debugging. Both of them must be turned on. Now you can boot into fastboot and unlock your bootloader. It will wipe the device so if you have any data you want to save you better do it now.
hey i am having this issue, i am able to adb reboot bootloader but when i try to oem unlock or anything else, it is just waiting for device and not finding it....
SourPower said:
hey i am having this issue, i am able to adb reboot bootloader but when i try to oem unlock or anything else, it is just waiting for device and not finding it....
Click to expand...
Click to collapse
That's a driver issue.
Are you using Windows 7? If so use 10
If not then sort out your driver's and it'll be fine.
Theres a bug in 7 where the driver for ADB cannot be collaborated with fastboot drivers.
dladz said:
That's a driver issue.
Are you using Windows 7? If so use 10
If not then sort out your driver's and it'll be fine.
Theres a bug in 7 where the driver for ADB cannot be collaborated with fastboot drivers.
Click to expand...
Click to collapse
thanks for the reply, i am on windows 10 and i dont know what is causing the issue when the phone goes in fastboot, but i went on my wife's laptop and got it working within a few minutes after installing adb...
Having similar problem here:
win10x64, drivers installed, USB debugging is enabled.
ADB sees the devices, reboots it correctly with "adb reboot bootloader"
then bootloader menu's shown:
START // RESTART BOOTLOADER // RECOVERY MODE // SHOW BARCODE // POWER OFF
Fastboot mode
Product_name - kona
Variant - SM8 UFS
BOOTLOADER VERSION - (nothing appears here)
BASEBAND VERSION - (nothing appears here)
Serial number - (appears 8-symbol sn)
SECURE BOOT - YES
DEVICE STATE - LOCKED
trying to communicate with smartphone via terminal "fastboot" command doesn't do much:"fastboot devices" doesn't return anything at all, "fastboot oem unlock" just shows <waiting for device>
tried to reinstall drivers
tema_ka said:
Having similar problem here:
win10x64, drivers installed, USB debugging is enabled.
ADB sees the devices, reboots it correctly with "adb reboot bootloader"
then bootloader menu's shown:
START // RESTART BOOTLOADER // RECOVERY MODE // SHOW BARCODE // POWER OFF
Fastboot mode
Product_name - kona
Variant - SM8 UFS
BOOTLOADER VERSION - (nothing appears here)
BASEBAND VERSION - (nothing appears here)
Serial number - (appears 8-symbol sn)
SECURE BOOT - YES
DEVICE STATE - LOCKED
trying to communicate with smartphone via terminal "fastboot" command doesn't do much:"fastboot devices" doesn't return anything at all, "fastboot oem unlock" just shows <waiting for device>
tried to reinstall drivers
Click to expand...
Click to collapse
If you type fastboot reboot what happens? If nothing then either you're device doesn't have usb debugging on, could be the cable/usb slot (some people have had issues with this)
Or its the driver installed for fastboot.
Show hidden devices in device manager you may have multiple devices, remove them all and start over.
Your also need to have used ADB and have trusted the device (prompt will appear on your phone the first time you connect it successfully whilst in your phones system, not fastboot)
for windows 10:
firstly download the google adb driver:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
then do the following:
1. adb devices [you should see your device ] > adb reboot bootloader
2. device manager > update driver > chose from list [android device]
3. still in device manager got the newly populated Android device and then update driver > choose adb interface
3. fastboot oem unlock
etc.
hope this helps
i have similar problem
then bootloader menu's shown:
START // RESTART BOOTLOADER // RECOVERY MODE // SHOW BARCODE // POWER OFF
Fastboot mode
Product_name - kona
Variant - SM8 UFS
BOOTLOADER VERSION - (nothing appears here)
BASEBAND VERSION - (nothing appears here)
Serial number - (appears 8-symbol sn)
SECURE BOOT - YES
DEVICE STATE - LOCKED
i reached till fastboot. fastboot oem unlock is not working because SECURE BOOT - Yes.
any help will be highly appreciated
shweta007 said:
i have similar problem
then bootloader menu's shown:
START // RESTART BOOTLOADER // RECOVERY MODE // SHOW BARCODE // POWER OFF
Fastboot mode
Product_name - kona
Variant - SM8 UFS
BOOTLOADER VERSION - (nothing appears here)
BASEBAND VERSION - (nothing appears here)
Serial number - (appears 8-symbol sn)
SECURE BOOT - YES
DEVICE STATE - LOCKED
i reached till fastboot. fastboot oem unlock is not working because SECURE BOOT - Yes.
any help will be highly appreciated
Click to expand...
Click to collapse
Secure Boot means your Bootloader is locked.
Setup fastboot correctly, open a cmd window, navigate to fastboot.exe and enter fastboot oem unlock, follow instructions on phone screen