On the normal boot mode, my Asus zenfone2(ZE551ML) running android 5.0 is listed when I type adb devices. Then, I put the phone to the fastboot mode by adb boot bootloader. When the phone is already entering the fastboot mode, fastboot devices returns no result. But, lsusb listed the device's details including vendorid, productid, and device name.
I have tried to modified the 51-android.rule, run fastboot as root, change owner of the /dev/bus/usb/, re-install and update the android-tools. But my ubuntu still can not detect the zenfone2 on fastboot mode.
Moreover, I connect my other phone(Redmi2) which also on fastboot mode and it can be detected seamlessly. Also,when I tried to connect the zenfone2 to other ubuntu PC, it can be detected.
Has anyone ever encountered and solved the similar problem? Or perhaps have an idea what is the potential cause?
Any help will be appreciated! Thanks.
Hi,
Try posting your question here:
ZenFone 2 Q&A, Help & Troubleshooting
The experts there may be able to help.
Good luck!
Related
Hi guys,
i have a tricky problem.
I bought a used nexus S, without any hope to recover it.
This is the state at the moment (after installed SDK and drivers).
I think the device is in his standard state (all locked up, never rooted, stock rom)
It boot up and ask for a password to encrypt device (works : volume and emergency call).
If i connect usb, he tries to mount USB storage but he dosen't success.
I connect to pc and pc see an Android ADB device in the devices list.
BUT if i lauch 'adb devices' i dont see anything.
I start it in bootloader mode (Vol Up + Power) ... it starts.
BUT Vol Up and Vol down didn't work. I can only press power and return again in bootloader. (volume work if i normally boot)
In bootloader state i tried 'fastboot devices' and i didn't see any device.
So the state is :
Bootloader i think "broken" (volumes dosen't work and fastboot dosen't see device)
Debug usb disabled (adb don't see my device)
Device encrypted
Any idea ?
I think is a nice problem to let your brain works on :laugh::laugh:
Thanks in advice.
Daniele
Hey guys, there is anybody out there ?
I dont think that no one could try to solve this problem.
Thanks
Do you have the drivers installed onto your PC? You will need to get the adb drivers and fastboot drivers. Download Samsung Kies and that will take care of your ADB drivers. Click here: http://www.mediafire.com/download/5a7gou9droidi53/drivers.rar for your fastboot drivers. Hope this helps.
I've already installed drivers.
But i will give a try to the ones you linked.
Thanks you.
sirhaplo said:
I've already installed drivers.
But i will give a try to the ones you linked.
Thanks you.
Click to expand...
Click to collapse
I'd suggest just booting Linux and doing whatever you need to do in there.
The kernel already supports communicating with the Nexus S, no need to mess with drivers like on Windows.
I have a Moto G 4g. ADB recognizes the cell and I can restart it in fastboot mode, but when I check in the terminal with:
Code:
fastboot devices
Nothing appears, and if I go on with
Code:
fastboot oem get_unlock_data
It gets stuck at
Code:
< waiting for device >
I tried as a user and as root on an Archlinux machine with android-udev rules as shown in the Archlinux wiki (sorry, i can't put the link). AP Fastboot fast boot menu shows that the cell is locked.
Hi,
You can try a different cable, or USB port on the pc...or even a different pc. Until fastboot devices detects your device, there's nothing you can do.
Reinstall drivers...and you are on the bootloader mode right?
If none of that helps, you can ask in your device section for help....
http://forum.xda-developers.com/moto-g/help
Good luck!
Hi
I've tried with a win 7 machine and i got fastboot working on my phone after installing the drivers. Now i'm able to do the thing i want to, but the problem still persist in linux, so i don't know if i close this thread or leave it open for someone who can solve this.
trichocereus said:
Hi
I've tried with a win 7 machine and i got fastboot working on my phone after installing the drivers. Now i'm able to do the thing i want to, but the problem still persist in linux, so i don't know if i close this thread or leave it open for someone who can solve this.
Click to expand...
Click to collapse
Please start one in your section. Xda Assist is here to help navigate the site, not for support.
Thanks!
Hello,
A friend of my asked me to install a new version on his iOcean X8 Mini.
After a few minutes into the process, I discovered that I couldn't modify anything at all.
Problems start occuring when I enter Fastboot via ADB (I power up the phone, connect it to PC, give it permission to use Android USB Debugging, then via 'adb rebeoot fastboot' I enter the Fastboot menu). Every command I enter here returns 3 dots just doing nothing. My command prompt is unusable after entering a command (for example 'fastboot oem unlock').
I've tried to push a ROM via ADB but this isn't working as well since it returns something like 'no permission' when trying to install, but I figured this was due to the locked bootloader.
Searched all over the internet for solutions, but so far nothing has really worked. What I somehow did mange to do is root the device (don't know if it was by default, I assume not), via RootGenius.
Anybody got any experience with this, and perhaps know some steps I can undertake to indeed unlock the bootloader of this phone?
Thanks in advance!
Hello and thank you for using XDA Assist,
please create an account and ask your question in this section. The experts there should know the best about your device.
Kind regards and good luck
Trafalgar Square
XDA Assist
Hi,
I'm looking for some assistance to unbrick an Allview Viva P8 Pro tablet.
All this mess started from looking after some disk space to install more apps on on the default second partition.
First I've tried some tools like app2sd with no luck and finally decided to try adb/fastboot way, using a linux machine, to root the device.
Before starting the root procedure i was able to boot into recovery mode and while being into recovery mode I could see the tablet as a google device with the proper vendor id 0x18d1. Also "adb devices" command could find the device as expected. Right after issuing "adb restart bootloader", i cannot enter into recovery mode and it hangs with the logo displayed on the screen, i think it's a boot phase before entering into recovery mode.
I can still see it as usb attached device, not with google vendor id but identified as "Onda unverified", with vendor id 0x1f3a. Windows OS finds it as Android Bootloader Interface USB Developer and that's it. I've tried to install some drivers to establish communication but with no luck so far.
Thank you in advance.
iulian.popa said:
Hi,
I'm looking for some assistance to unbrick an Allview Viva P8 Pro tablet.
All this mess started from looking after some disk space to install more apps on on the default second partition.
First I've tried some tools like app2sd with no luck and finally decided to try adb/fastboot way, using a linux machine, to root the device.
Before starting the root procedure i was able to boot into recovery mode and while being into recovery mode I could see the tablet as a google device with the proper vendor id 0x18d1. Also "adb devices" command could find the device as expected. Right after issuing "adb restart bootloader", i cannot enter into recovery mode and it hangs with the logo displayed on the screen, i think it's a boot phase before entering into recovery mode.
I can still see it as usb attached device, not with google vendor id but identified as "Onda unverified", with vendor id 0x1f3a. Windows OS finds it as Android Bootloader Interface USB Developer and that's it. I've tried to install some drivers to establish communication but with no luck so far.
Thank you in advance.
Click to expand...
Click to collapse
Greetings!
Thank you for using XDA Assist.
Please consider posting your question here:
http://forum.xda-developers.com/android/help
You'll receive expert advice there.
Good luck!
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.