I've just got a new Z5 and am trying to install LineageOS, like I did on my dearly departed HTC m8.
I've got the android platform tools installed, and the device shows up if I use "adb devices". "adb reboot bootloader" appears to work - it shuts the device down then the LED goes blue (the documented behaviour of being in fastboot mode). However, "fastboot devices" lists nothing.
*#*#SERVICE#*#* indicates bootloader unlock is allowed, I've got dev mode enabled, I've got my unlock code ready and waiting... No fastboot mode though. Any ideas?
Hang on a sec.
It's just occurred to me that something else might be wrong. Booting into "fastboot" is the same as entering recovery mode, right? Well, when I try doing it, all I get on my phone is the blue LED. Just a black screen. That seems obviously wrong, because it should be displaying Sony's built-in recovery mode stuff, right?
While we're at it, I've just tried again on my work computer, holding volume up and inserting a USB cable. The computer recognised and installed "S1Boot Fastboot", and I can see it in Device Manager under "Other devices". However, the status is "The drivers for this device are not installed. (Code 28) There are no compatible drivers for this device."
This was the same on my home machine. I tried installing Sony's drivers, and the Android drivers, but each time I pointed Windows at the directory I'd unzipped to it would just say that it couldn't find any drivers there.
e: #$%&!
I'm trying with Sony's "Emma" tool. It says to hold vol-down and connect the phone, which gives a green light (not a blue one), but says "this phone is locked". But I've unlocked it! Sony's instructions at the address listed in the error message say to enable debugging then select "OEM unlocking" from the dev options, which I have done! What gives?
Got it!
I Can't post the URL due to low number of posts, but I found what I needed from the question on the android Stack Exchange called "Windows 10 Fastboot Driver". I grabbed a tool called Zadig, which was able to install a driver for Fastboot, so I could flash recovery.
Right. Now to get set up! Woo!
Thank you!
Hyperlynx said:
Got it!
I Can't post the URL due to low number of posts, but I found what I needed from the question on the android Stack Exchange called "Windows 10 Fastboot Driver". I grabbed a tool called Zadig, which was able to install a driver for Fastboot, so I could flash recovery.
Right. Now to get set up! Woo!
Click to expand...
Click to collapse
Thank you! I had the same problem. The device showed up as "Android" and I couldn't install the drivers.
You can find instructions and the download link here: https://android.stackexchange.com/questions/129174/windows-10-fastboot-driver
Related
Hi, partial noob here, I've rooted a different Xoom but this one was stock US wifi only, MZ604.
Amazon appstore was restarting continually so I navigated away but left it open. Later in the day when I tried to reopen it, it crashed my Xoom. Now it is locked on red M screen. I can soft resest and get to "starting fastboot protocol support" but when connected to pc with oem usb cable, it doesn't show up under adb devices. If I adb reboot bootloader, it says device not found. I have checked my drivers, they show up under "Mot Single ADB Interface" with file version 1.1.0.0 and file version 1.7.6001.0 (two drivers). I have adb and fastboot in my SDK_tools folder, what am I missing?
Thanks for any help,
Peter
pepond said:
Hi, partial noob here, I've rooted a different Xoom but this one was stock US wifi only, MZ604.
Amazon appstore was restarting continually so I navigated away but left it open. Later in the day when I tried to reopen it, it crashed my Xoom. Now it is locked on red M screen. I can soft resest and get to "starting fastboot protocol support" but when connected to pc with oem usb cable, it doesn't show up under adb devices. If I adb reboot bootloader, it says device not found. I have checked my drivers, they show up under "Mot Single ADB Interface" with file version 1.1.0.0 and file version 1.7.6001.0 (two drivers). I have adb and fastboot in my SDK_tools folder, what am I missing?
Thanks for any help,
Peter
Click to expand...
Click to collapse
Are you rooted with custom recovery or stock? After soft reset when the "M" first appears count to three and press the volume down button, hopefully you will see "android recovery". If you do press the volume up button to enter recovery and you could do a system restore from it. I'm thinking maybe you didn't have "usb debugging" turned on in developer settings, does it show a pop up on your computer when you plug in the xoom where you can browse it's file contents? If so save any photos or important docs and do a system restore like I explained earlier.
Same woes here
solved
Good afternoon everyone
I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.
I've been following the guide based off of Nvidia's website
I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run
Code:
adb devices
I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)
At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:
Code:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked
Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff
Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.
Thanks for your time everyone.
You have boot into the bootloader before being able to use fastboot. Just reboot your device and hold vol- during startup. The tablet will show some console messages, offering some options. If you see that screen, you can use fastboot.
bob3rt said:
Good afternoon everyone
I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.
I've been following the guide based off of Nvidia's website
I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run
Code:
adb devices
I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)
At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:
Code:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked
Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff
Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.
Thanks for your time everyone.
Click to expand...
Click to collapse
Adb works in normal mode.
Fastboot works in Bootloader mode.
Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.
dzidexx said:
Adb works in normal mode.
Fastboot works in Bootloader mode.
Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.
Click to expand...
Click to collapse
Hey there, sorry for my late reply, I've been swamped with work. I've tried your advice with no luck so far.
I can reboot to the bootloader, but when I select "fastboot protocol" I don't get to choose Select on/yes. it just refreshes the screen with the same options that I listed above. If you'd like when I get home I can provide a screenshot of my tablet so you can see the options, but I'm not getting anything like you described. Am I missing something?
Thank you for your time so far helping me.
Connect k1 to pc, type in cmd:
adb devices
adb reboot bootloader
fastboot devices
/Enable fastboot protocol on k1, type again/
fastboot devices
Give here screenshot from pc - all command/answers in cmd. @bob3rt
I had the same issue and lasted untill I tried different usb cable
Shield K1 connectivity is very sensible to cable quality
try others
dzidexx said:
Connect k1 to pc, type in cmd:
adb devices
adb reboot bootloader
fastboot devices
/Enable fastboot protocol on k1, type again/
fastboot devices
Give here screenshot from pc - all command/answers in cmd. @bob3rt
Click to expand...
Click to collapse
Hey Sorry again for a late response! However the good news is that I got it working!
What I ended up doing was hooking up the tablet to my Raspberry Pi with MATE and running adb/fastboot there. I originally ran into the same issue, but since I was able to sudo fastboot everything was recognized and seemed to work fine. I appreciate all of your help, and I apologize once again for the late replies!
For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.
Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.
:good:
0mad said:
For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.
Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.
:good:
Click to expand...
Click to collapse
Worked like a charm! Thanks.
I could not even find my device when i use fastboot devices command in fast boot mode. Because of this i could not flash twrp also.
I installed adb and drivers and connected the phone in all sorts of modes (usb debugged, usb undebugged, fastboot, system on, switch off mode).
When the phone is connected in switch off mode, i could see something like "usb device not found" message in pc. Tried changing desktop. But it's the same result.
Bootloader is unlocked and on stock open beta 4 pie.
harigavara said:
I could not even find my device when i use fastboot devices command in fast boot mode. Because of this i could not flash twrp also.
I installed adb and drivers and connected the phone in all sorts of modes (usb debugged, usb undebugged, fastboot, system on, switch off mode).
When the phone is connected in switch off mode, i could see something like "usb device not found" message in pc. Tried changing desktop. But it's the same result.
Bootloader is unlocked and on stock open beta 4 pie.
Click to expand...
Click to collapse
I have noticed this as well,
My solution is to "install" the drivers every time I connect it in fastboot mode.
The reason why I put "" around install is, that I really don't install but I tell windows my devices is a fastboot device.
Open device manager
Right click your one plus device, most likely named Android with a yellow exclamation mark
Choose update driver software
Choose Browse my computer for driver software
Choose Let me pick from a list of device drivers on my computer
Choose android
Choose bootloader device (or something similar)
Apply
??
Voila you can now use fastboot commands on your OP6
ChemoNL said:
I have noticed this as well,
My solution is to "install" the drivers every time I connect it in fastboot mode.
The reason why I put "" around install is, that I really don't install but I tell windows my devices is a fastboot device.
Open device manager
Right click your one plus device, most likely named Android with a yellow exclamation mark
Choose update driver software
Choose Browse my computer for driver software
Choose Let me pick from a list of device drivers on my computer
Choose android
Choose bootloader device (or something similar)
Apply
??
Voila you can now use fastboot commands on your OP6
Click to expand...
Click to collapse
it worked foe me.
Thank you
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
MugenG said:
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
Click to expand...
Click to collapse
Installed adb SystemWide?
adb drivers are Installed corrcetly? , better to reinstall them.
Hello,
I am hoping for some advice on how to revert my phone back to its original "factory settings" after a botched instal of GrapheneOS onto an unlocked Google Pixel 3A.
I got to the point at which I needed to Flash the Graphene Rom to the phone, but rather than installing, I received a message from Smart Screen MS edge asking if I really wanted to run as it's protecting my PC - I clicked run anyway and a blank command line window appeared for a second. Now my pc doesn't seem to be recognising the pixel 3A when I type ADB devices. My phone is currently in Fastboot mode "unlocked" and I'm hoping for some advice on what to do next. I'm total noob, so unsure how to start the process over (return the phone to it's previous state) before, maybe, trying again on a different PC.
I have since turned on my phone and Android 11 is still present and seems to work fine (however it gives me a warning on startup that the bootloader is unlocked.
Any help would be very much appreciated - thank you in advance.
Is all what happened that your phone now:
complains about "'maybe not safe bootloader unlocked".
This is just what android does when the bootloader is unlocked.
This you did before trying the flash.
If you want the warning gone simply lock it again.
However if you into the market for graphene OS then I would recomend: along with following their guide to a t to also read up here on xda about the general rooting unlocking thing a bit more so you get the overall process a bit better perhaps next time.
About windows. There are so many tools out there to help ya with disabling some of it's spying, turning off smartscreen, auto - uploads of all your data to M$oft, etc etc.
It's not hard to find.
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Ignore
deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go
Tamsta_T said:
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go
Click to expand...
Click to collapse
Hey there,
This is brilliant - thanks for all the advice. Having this support is helping me gain the confidence to learn more, research more, and then give it a go.
All the best.
deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
thats if I am not wrongly remembering my experience:
because now your phone is in fastboot mode thus it won't show up with that command anymore.
Try: 'fastboot devices'
I imagine you put it into fastboot through: 'reboot fastboot' when you where in adb?
When in fastboot you can go on and flash the recovery and such.
Are you still in need of help here?
Hey, thanks for the clarification - been away and so haven't implemented all suggestions, yet.
I typed "adb reboot booloader" which I assumed put it into fastboot mode and then unlocked it using "fastboot flashing unlock".
I tried fastboot devices but the PC still doesn't see the phone. I'm going to try the update usb driver suggested by Tamsta_T and see how it goes.
Thanks for your help.