I have a 5" android tablet (I know, I know, world's smallest tablet) running on an Allwinner A33 chip referred to in device info as "astar_evb-eng" that I got from a Chinese no-name manufacturer. I am running Windows 8 (not 8.1) and have installed and tried every version of the adb driver (i.e. Android ADB Interface, which works fine) and fastboot driver (e.g. Android Bootloader Interface, which hates me), and ADB commands always work, but my computer just refuses to see my device from fastboot when it's in fastboot mode. Nothing comes up with "fastboot devices" and things like "fastboot flashing unlock" just hang, perpetually saying "waiting for device..."
As a side note, "adb reboot fastboot" just restarts into the main OS, so the only way I can stick it into fastboot mode is by holding the volume and power buttons. Additionally, "adb reboot bootloader" works (sort of), but the bootloader on the device screen is just the startup picture and that's it (totally static). The only thing that actually works is "adb reboot recovery", and from the recovery menu I can get it into sideload mode, but that's it.
I am running "fastboot devices" in an administrator command prompt window and it comes back with nothing. I need fastboot to work in order for me to use the manufacturer's suite (called PhoenixSuit 3.1.0) to push a new ROM onto the device, as it is presently crippled. I even tried a driver specifically for Allwinner-based devices and it did nothing. Help!
Related
I found this thread about my Prism
http://forum.xda-developers.com/showthread.php?t=1698905 post 5
I can press volup and power for 15 sec and get android recovery screen.
I can connect my phone to my laptop.
I can run "adb devices" and get List of devices attached: "20F3A........... recovery" so i think it sees it.
But when I run "fastboot reboot" (to test the connection) it says "waiting for device".
I think I have to give another command to adb, but don't know what.
If you can help, I'd much appreciate it!
KrisM22 said:
I found this thread about my Prism
http://forum.xda-developers.com/showthread.php?t=1698905 post 5
I can press volup and power for 15 sec and get android recovery screen.
I can connect my phone to my laptop.
I can run "adb devices" and get List of devices attached: "20F3A........... recovery" so i think it sees it.
But when I run "fastboot reboot" (to test the connection) it says "waiting for device".
I think I have to give another command to adb, but don't know what.
If you can help, I'd much appreciate it!
Click to expand...
Click to collapse
If the phone runs ADB, it's not in fastboot mode.
fastboot is a boot loader feature. ADB is a service at the operating system level. They are mutually exclusive.
Take to phone back to fastboot if it's what you want.
Code:
$ adb reboot-bootloader
kuisma said:
If the phone runs ADB, it's not in fastboot mode.
fastboot is a boot loader feature. ADB is a service at the operating system level. They are mutually exclusive.
Take to phone back to fastboot if it's what you want.
Code:
$ adb reboot-bootloader
Click to expand...
Click to collapse
Thanks! Please pardon my ignorance... I did:
Code:
adb devices
pause
adb reboot-bootloader
pause
fastboot reboot
After adb reboot-bootloader my phone changed from the recovery screen to the white tmo logo screen and hung.
fastboot reboot still says waiting for device...
EDIT Okay, I think I've figured out that, from power off, volup+power=recovery screen , and voldn+power=fastboot screen(white with tmo logo).
But I can't do anything from that fastboot screen. The computer recognizes it when I USB plug it, but it still says waiting for device.
EDIT: It appears I have a driver for adb, but no driver for fastboot, or just plugging the powered off phone in to usb.
fixed.
<deleted>
I boot my Acer Iconia Tab A200 into fastboot mode (robot lying down and RED exclamation mark over it). I plug it into my Windows 7 (64bit) desktop computer with SDK installed, and from the directory with fastboot.exe I type FASTBOOT DEVICES but the device is not being seen, it just goes back to the prompt, like the command executed but didn't do anything. I assume this is because the drivers aren't installed. But I don't know how to install the "adb drivers". How is this done?
Go to Acer support page, you'll get the drivers there.
This device will not fully boot. It gets stuck at an "encryption unsuccessful" message. I'm trying to flash a rom image from my desktop computer using fastboot, but when my tablet is in fastboot mode, my desktop computer won't recognize it. ie adb devices command doesn't show that there is any device connected, and I think it's because the drivers aren't installed. I think those Acer drivers only work if the tablet can be fully booted.
Installed the Google USB Drivers from the SDK Manager already. Don't know what's wrong.
Alright I figured out how to get fastboot to interface with my Android tablet. The problem was that I wasn't getting the tablet into fastboot mode to recieve commands.
But now it's working. However, I'm trying to unlock the bootloader and it gives me an errors that says:
SetUnlockedMode: Error occured while unlock the device ...
Fastboot: Failed to set unlock mode
I have to unlock the bootloader before I flash an image to the tablet, right ?
Yep, surely.
I'm trying to test a twrp recovery I ported to my phone, but fastboot isn't working correctly. Adb works fine, adb devices shows my phone. Windows device manager shows adb composite device, all is well. Adb reboot bootloader puts the phone into fastboot as it should. Device manager then shows android boot loader interface. It should be working since it seems like the appropriate drivers are loaded, but fastboot devices gives me a blank line. Fastboot reboot just shows waiting for device and never gets any further. What am I missing?
Jesseb342 said:
I'm trying to test a twrp recovery I ported to my phone, but fastboot isn't working correctly. Adb works fine, adb devices shows my phone. Windows device manager shows adb composite device, all is well. Adb reboot bootloader puts the phone into fastboot as it should. Device manager then shows android boot loader interface. It should be working since it seems like the appropriate drivers are loaded, but fastboot devices gives me a blank line. Fastboot reboot just shows waiting for device and never gets any further. What am I missing?
Click to expand...
Click to collapse
Hello men.
Did you get the fastboot to work?
I'm in the same situation here.
Thanks :fingers-crossed:
Hi guys,
This Is my first post so I hope I do it correctly. As the title says I am having problems with fastboot on my Acer Iconia One 10 B3-A40. I have enabled developer settings on my device and turned on the setting to unlock OEM. The problem is when I try to run the tablet in fastboot mode to unlock the OEM through ADB commands. When connected to my computer and running the command "adb devices" it shows my device Id and that it is connected. I then run the command "adb reboot-bootloader" to which the tablet switches off and makes the chime that it was disconnected from the computer and makes another chime and connects back onto the computer, the screen on my tablet remains blank with no indication it is in fastboot mode. When I run the command "fastboot devices" my device id shows up again that it is connected. When I originally tried to flash a patched boot image of my stock firmware it went through the process and failed mid way through saying it couldn be done cos the device was locked. After that I googled a bit to see what to do so that’s when I realised OEM unlock was to be switched on in developer settings and also using ADB commands. After returning to fast boot mode I ran the command "fastboot oem unlock" the 3 dots come up on command prompt to show the process is going but nothing happens on my device. Nothing will happen if I press the power button or the volume down button but if I press the volume up bottom, on command prompt it shows OKAY and then the amount of seconds it took to complete, the time changes based on how quick or long i take to press the volume up button but the device remains locked. I have being trying to find a solution for days and have searched everything i could find before making this post. It would be greatly appreciated if someone could help.
Hello Friends,
I have recently Purchased an Oppo F15, I have enabled developer mode, OEM Unlocked, and USB Debugging, with the latest adb drivers installed on my PC.
while I am running the command "adb devices" it returning with the device name I have connected i.e. Oppo F15 but when I am running the command "adb reboot fastboot", "adb reboot-bootloader", "adb reboot bootloader" the device reboots but not going to fastboot, it just reboots in normal mode.
Please help me if I am missing something in this. My device is running with Android version 9.
@Venomiest
Try this commands sequence
Code:
adb reboot
adb devices
adb reboot bootloader
fastboot devices
jwoegerbauer said:
@Venomiest
Try this commands sequence
Code:
adb reboot
adb devices
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
Those are the proper commands
([emoji88]Havoc GSI[emoji88])
Venomiest said:
Hello Friends,
I have recently Purchased an Oppo F15, I have enabled developer mode, OEM Unlocked, and USB Debugging, with the latest adb drivers installed on my PC.
while I am running the command "adb devices" it returning with the device name I have connected i.e. Oppo F15 but when I am running the command "adb reboot fastboot", "adb reboot-bootloader", "adb reboot bootloader" the device reboots but not going to fastboot, it just reboots in normal mode.
Please help me if I am missing something in this. My device is running with Android version 9.
Click to expand...
Click to collapse
The bootloader is blocked by code combination. If you try to see more attentive you'll notice the tiny message on the black screen while rebooting.
Not Working
Alien object