Hello,everyone.I've got a Sprint optik(zte v55) 7" pad coming with HC 3.2.
After I flash a modified kernel, Its usb debugging mode can't work properly and my pc can't recgonize it.
Before I flash the kernel, when I switched to usb debugging mode and connect to my pc(runing win7), v55 will display a icon in taskbar showing it's connected with pc, my pc will show a new driver that showing the dirs and files in v55's internal storage, and when I run command "adb devices", it will show v55 is connected.
now, all the above is not happening anymore.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
Click to expand...
Click to collapse
Can anybody know what should I do now ? My intention is to root and flash CM10 to v55,and can be recongize by my pc again.
The kernel I flashed into is in http://forum.xda-developers.com/showthread.php?t=1473555,kernel #60 for v55.
mdky said:
Hello,everyone.I've got a Sprint optik(zte v55) 7" pad coming with HC 3.2.
After I flash a modified kernel, Its usb debugging mode can't work properly and my pc can't recgonize it.
Before I flash the kernel, when I switched to usb debugging mode and connect to my pc(runing win7), v55 will display a icon in taskbar showing it's connected with pc, my pc will show a new driver that showing the dirs and files in v55's internal storage, and when I run command "adb devices", it will show v55 is connected.
now, all the above is not happening anymore.
Can anybody know what should I do now ? My intention is to root and flash CM10 to v55,and can be recongize by my pc again.
The kernel I flashed into is in http://forum.xda-developers.com/showthread.php?t=1473555,kernel #60 for v55.
Click to expand...
Click to collapse
Hi, here are some things to keep in mind when using adb.
Be sure of the command you are issuing
Insure you are in fact cd'd to wherever on your pc the adb binary is located
Insure your jdk is included in your path on your pc
To make things easier you can always also add the tools and platform-tools folder of the android sdk to your path
Lets make sure you are properly set up first before you start flashing things randomly.
For more info, you should check Android's page on ADB if you would like. http://developer.android.com/tools/help/adb.html
I'm not sure if any of this is actually directly related to your issue, but it is nice to start with the basics.
wildstang83 said:
Hi, here are some things to keep in mind when using adb.
Be sure of the command you are issuing
Insure you are in fact cd'd to wherever on your pc the adb binary is located
Insure your jdk is included in your path on your pc
To make things easier you can always also add the tools and platform-tools folder of the android sdk to your path
Lets make sure you are properly set up first before you start flashing things randomly.
Click to expand...
Click to collapse
Thank you for reply.
The adb command I use is install by v55's driver.Everytime I use adb, I always go into the driver's dir (C:\Program Files\ZTE Tablet V55 USB Driver) which adb.exe is in.
And this dir is in my path.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
mdky said:
Thank you for reply.
The adb command I use is install by v55's driver.Everytime I use adb, I always go into the driver's dir (C:\Program Files\ZTE Tablet V55 USB Driver) which adb.exe is in.
And this dir is in my path.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
Click to expand...
Click to collapse
Ooook now we're getting somewhere, I think
Make sure when you send your fastboot flash command you send it like so:
Code:
fastboot flash recovery recovery.img
Replace 'recovery.img' with the actual name of the img, whatever it is.
Also if you are getting the device offline error try killing server:
Code:
adb kill-server
and then restart it
Code:
adb start-server
See if that helps.
wildstang83 said:
Ooook now we're getting somewhere, I think
Make sure when you send your fastboot flash command you send it like so:
Code:
fastboot flash recovery recovery.img
Replace 'recovery.img' with the actual name of the img, whatever it is.
Also if you are getting the device offline error try killing server:
Code:
adb kill-server
and then restart it
Code:
adb start-server
See if that helps.
Click to expand...
Click to collapse
I will try these command when I get home, thank u!:good:
"adb kill-server" and "adb start-server" works fine.They turn v55's "adb devices" from "offline" to "recovery".
And I run command "adb reboot-bootloader", it seems that v55 is in bootload mode.
But after that,I run command "fastboot flash recovery CWMrecovery.img",it returns '<waiting for device>' and stuck there.
Before I flash the kernel #60, I can run "fastboot boot CWMrecovery.img" to boot to cwm,so I think it's not likely be the driver's problem,am I right?
mdky said:
"adb kill-server" and "adb start-server" works fine.They turn v55's "adb devices" from "offline" to "recovery".
And I run command "adb reboot-bootloader", it seems that v55 is in bootload mode.
But after that,I run command "fastboot flash recovery CWMrecovery.img",it returns '<waiting for device>' and stuck there.
Before I flash the kernel #60, I can run "fastboot boot CWMrecovery.img" to boot to cwm,so I think it's not likely be the driver's problem,am I right?
Click to expand...
Click to collapse
Sorry to take so long to reply. I think it is not a driver issue. Do you know if debugging/adb is even enabled in the ramdisk? This generally would have to be done by the dev who created the kernel. Speaking of that, have you tried to contact that dev for further support? For sure they would know more than me since I don't own the device myself. I just know enough to be slightly dangerous, lol
wildstang83 said:
Sorry to take so long to reply. I think it is not a driver issue. Do you know if debugging/adb is even enabled in the ramdisk? This generally would have to be done by the dev who created the kernel. Speaking of that, have you tried to contact that dev for further support? For sure they would know more than me since I don't own the device myself. I just know enough to be slightly dangerous, lol
Click to expand...
Click to collapse
It's very nice of you to keep help me here ,thanks again:good:!
After keep trying in past two days, I found that in ftm mode adb is enabled, and 'adb reboot bootloader' truly made the device into bootloader mode.
On my win7 pc, It can't be recognized.I switch to my old xp pc,and install the driver come from other zte user,and then...fastboot works.
Now I have the v55 running CM10,Awesome!Thanks to all contributors.
Still, my win7 pc and xp pc can't recognize my v55 through usb.But it's not big deal now.I can use tf and wifi and other ways to transfer file to v55.
mdky said:
It's very nice of you to keep help me here ,thanks again:good:!
After keep trying in past two days, I found that in ftm mode adb is enabled, and 'adb reboot bootloader' truly made the device into bootloader mode.
On my win7 pc, It can't be recognized.I switch to my old xp pc,and install the driver come from other zte user,and then...fastboot works.
Now I have the v55 running CM10,Awesome!Thanks to all contributors.
Still, my win7 pc and xp pc can't recognize my v55 through usb.But it's not big deal now.I can use tf and wifi and other ways to transfer file to v55.
Click to expand...
Click to collapse
Oh wow, that is quite the ordeal, but atleast its something huh, lol
I wonder if you could run adb and fastboot commands in xp mode on your win7 pc?
I know there is a way to run programs in XP mode, its just been awhile since I've done it.
And its no problem to keep trying to help, even if I don't know the device and all that. Maybe I can learn to while we are at it, and maybe make a new friend along the way
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 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!
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:
I am on an older macbook pro running High Sierra. the phone I'm using is a Blu G5 running android 9. I have the developer options unlocked and oem unlocked and usb debugging checked. When i open my terminal i type cd and drag and drop the platform tools folder into the terminal window changing the directory to the folder containing the adb and fastboot files. I can use adb commands such as adb devices and get the serial number and it says devices. So far so good. Then i reboot the phone into the bootloader manually or using command adb reboot bootloader and the phone goes into fastboot mode. I know because it says it on top of the screen in white letters. Then i run into the problem fastboot commands don't work. If I type in fastboot devices nothing but a new command line shows up. When i type in any other command like fastboot device or fastboot oem unlock it says "waiting for any devices." I wait and wait but nothing happens. I have looked on the internet for a solution but all i find is that the driver may not deinstalled properly. I have tried manually installing fastboot driver and used sdk manager to install the fastboot driver and I have tried it using the terminal in android studio but no matter what when i try useing fastboot commands i get the "waiting for any device" message. Does any have a solution or could anyone recommend and forum for android development on MacOSX?
@DimDreams
Seems the Fastboot driver is invalid.
jwoegerbauer said:
@DimDreams
Seems the Fastboot driver is invalid.
Click to expand...
Click to collapse
I have literally tried like 10 different sdk tool downloads just platform tool download basically every thing i can find. By chance would you or anyone out there have a working driver for MacOSX 10.13.6? or link a guide that can help me figure this out. I have made a little progress with a forum on xda about fastboot on macs but i still just keep getting the waiting for any device message.
@DimDreams
May also be that the Fastboot Android mode is not available on the phone in question.
I've had similar issues before and noticed that fastboot mode works better via USB 2.0 than USB 3.0. Maybe check which port you're using and switch. ADB seems to work well either way, however. Hope that helped.
I just had this problem as well and I found this, what worked for me is first boot your phone into bootloader mode with
Code:
adb reboot bootloader
. While in the bootloader fastboot worked for me. Hope this helps someone!