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
Related
I spent the whole of yesterday trying to add MoDaCo custom rom. from this post http://forum.xda-developers.com/showthread.php?t=552591 The first of my problems was that I couldn't get the right driver which now seems to be fixed now comes up as - ADB Interface -HTC Bootloader.
So this now means that when i go to fastboot I can load cyanogenMod (system recovery) by typing fastboot boot cm-hero-recovery.img
However none of these commands below in the CMD work. All i get is error: device not found
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
Any ideas please
robboy said:
I spent the whole of yesterday trying to add MoDaCo custom rom. from this post http://forum.xda-developers.com/showthread.php?t=552591 The first of my problems was that I couldn't get the right driver which now seems to be fixed now comes up as - ADB Interface -HTC Bootloader.
So this now means that when i go to fastboot I can load cyanogenMod (system recovery) by typing fastboot boot cm-hero-recovery.img
However none of these commands below in the CMD work. All i get is error: device not found
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
Any ideas please
Click to expand...
Click to collapse
Still sounds like a driver issue.. have you installed HTC + the SDK?
Restert ur handset into bootloader, hold power + back, then plugin the USB cable.. "FASTBOOT" (,In the red square) shoud change to FASTBOOT USB..
Skip the "adb shell reboot bootloader" and go straight to the next line and boot the recovery image via fastboot
should be plain sailing from there
It does change to fastboot usb on red. The only thing I can think of is do you have to install the sdk as I couldn't see a setup app. I just have all the files on the c dive. Will try skipping the first step when I get home
you dont install the sdk, just unzip it
thats right just the unzip, sorry, the drivers come with the SDK, if you still have no sucsess, do a Controll pannel > system >device manager then scan for device changes, if it finds the device select to install drivers and point it to the SDK folder
jackdaniels_lee said:
Still sounds like a driver issue.. have you installed HTC + the SDK?
Restert ur handset into bootloader, hold power + back, then plugin the USB cable.. "FASTBOOT" (,In the red square) shoud change to FASTBOOT USB..
Skip the "adb shell reboot bootloader" and go straight to the next line and boot the recovery image via fastboot
should be plain sailing from there
Click to expand...
Click to collapse
Grrrr still no joy. Just device not found. Im deleting all files that I have downloaded for drivers sdk etc and try and start again from scratch.
Do I need to partion my SD card before I do this as i have been having probs with that as well.
jackdaniels_lee said:
thats right just the unzip, sorry, the drivers come with the SDK, if you still have no sucsess, do a Controll pannel > system >device manager then scan for device changes, if it finds the device select to install drivers and point it to the SDK folder
Click to expand...
Click to collapse
Done that as well. If My device runs fastboot this should mean the drivers are correct.
robboy said:
Done that as well. If My device runs fastboot this should mean the drivers are correct.
Click to expand...
Click to collapse
yes if u succeed to enter fastboot, it means it had recognised the phone? are u using windows 7 by the way? cause u have to download the precise drivers for the OS u r using whether x64, win 7 ....
I seem to remember having problems with this until I enabled the USB debugging mode in the options somewhere.
As for drivers, I'm running Windows 7 x64 and the x64 Vista drivers did the job fine.
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>
Hi guys. I have an HTC OX+... I tried to flash a rom but something went wrong and I erased everything... Now I managed to switch my phone on in fastboot and in recovery mode. How can I sort the problem out?
My recovery is TWRP 2.7.1.0
lorenk93 said:
Hi guys. I have an HTC OX+... I tried to flash a rom but something went wrong and I erased everything... Now I managed to switch my phone on in fastboot and in recovery mode. How can I sort the problem out?
My recovery is TWRP 2.7.1.0
Click to expand...
Click to collapse
I assume your PC has all drivers installed so go to command prompt, there go to your folder where adb and fastboot are.
It should be like this, cd C:\folder_where_adb_is
Now go to recovery mode on the phone and search for Sideload, it can be in install zip from your recovery, click it when you found it.
Go to your Pc and put the ROM to the folder where adb and fastboot are.
Then make sure your phone says it's in adb sideload mode,
On the PC write
Code:
adb sideload file_name.zip
And wait until it's finished
Let's say that's done, but you can't boot, it keeps restarting forever.
In this case, go to your rom.zip open it on the PC and there will be a file called boot.img
Extract boot.img to your folder where fastboot and adb are.
Now on your phone, force it to close by holding power, open fastboot
Again open cmd on the PC and point it to your folder where fastboot and adb are.
Then write
Code:
fastboot flash boot boot.img
oziboy said:
I assume your PC has all drivers installed so go to command prompt, there go to your folder where adb and fastboot are.
It should be like this, cd C:\folder_where_adb_is
Now go to recovery mode on the phone and search for Sideload, it can be in install zip from your recovery, click it when you found it.
Go to your Pc and put the ROM to the folder where adb and fastboot are.
Then make sure your phone says it's in adb sideload mode,
On the PC write
Code:
adb sideload file_name.zip
And wait until it's finished
Let's say that's done, but you can't boot, it keeps restarting forever.
In this case, go to your rom.zip open it on the PC and there will be a file called boot.img
Extract boot.img to your folder where fastboot and adb are.
Now on your phone, force it to close by holding power, open fastboot
Again open cmd on the PC and point it to your folder where fastboot and adb are.
Then write
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
When I write adb sideload file_name.zip, it
returns "error: closed". why?
lorenk93 said:
When I write adb sideload file_name.zip, it
returns "error: closed". why?
Click to expand...
Click to collapse
file_name.zip is your ROM name, for example if you have arhd it can be ARHD_V8.zip or something, just see what name the zip file of your rom has
if this is not the case try
ADB usb before trying adb sideload
oziboy said:
file_name.zip is your ROM name, for example if you have arhd it can be ARHD_V8.zip or something, just see what name the zip file of your rom has
if this is not the case try
ADB usb before trying adb sideload
Click to expand...
Click to collapse
so... I have to write "ADB usb file_name.zip". tath's right?
lorenk93 said:
so... I have to write "ADB usb file_name.zip". tath's right?
Click to expand...
Click to collapse
No, you have to write only "adb usb".
Then try "adb sideload yourrom.zip" again.
if that didn't work, then reboot into recovery and go to command prompt, and write
Code:
adb kill-server
adb usb
adb push yourromname.zip /sdcard
that should work if nothing else works. im having kinda the same issue right now :/
oziboy said:
No, you have to write only "adb usb".
Then try "adb sideload yourrom.zip" again.
if that didn't work, then reboot into recovery and go to command prompt, and write
Code:
adb kill-server
adb usb
adb push yourromname.zip /sdcard
that should work if nothing else works. im having kinda the same issue right now :/
Click to expand...
Click to collapse
I don't know why, but when I write adb usb it returns "error: device not found"
lorenk93 said:
I don't know why, but when I write adb usb it returns "error: device not found"
Click to expand...
Click to collapse
I just fixed this on my phone, now to to control panel - uninstall a program and delete htc sync manager (only sync manager, not the drivers)
Then try again, if nothing, go to here and install that.
If installed, go to fastboot mode, plug in your phone and in that program, when you open it, it says install drivers, flash rom and such...
Now on the right there is flash TWRP recovery, flash that, if your device is an LTE variant (ATT, Telus) install the ones for that and international for international version, make sure you got the correct one.
Then go to recovery, on the lower-right side there is an "advanced" button, hit that and there should be adb sideload somewhere, click that and swipe left to right to enable.
Go to your PC and repeat the sideloading steps as I said before.
oziboy said:
I just fixed this on my phone, now to to control panel - uninstall a program and delete htc sync manager (only sync manager, not the drivers)
Then try again, if nothing, go to here and install that.
If installed, go to fastboot mode, plug in your phone and in that program, when you open it, it says install drivers, flash rom and such...
Now on the right there is flash TWRP recovery, flash that, if your device is an LTE variant (ATT, Telus) install the ones for that and international for international version, make sure you got the correct one.
Then go to recovery, on the lower-right side there is an "advanced" button, hit that and there should be adb sideload somewhere, click that and swipe left to right to enable.
Go to your PC and repeat the sideloading steps as I said before.
Click to expand...
Click to collapse
I did it... Thanks to you... So thank you so much...
lorenk93 said:
I did it... Thanks to you... So thank you so much...
Click to expand...
Click to collapse
No problem, I had almost the same problem and just told what I did xD
Hi everyone.
I apologize if this was already asked.
I own a Symphony H50. I am trying to install windows via change my software but it shows device too slow or protected by manufacturer.
So googled it and found that i need to unlock my boot loader.
So I installed adb,fastboot,drivers including bootloader interface driver. And booted into fastboot mode. And typed "fastboot oem get_unlock_data" and the command prompt shows 3 dots (...) And the cursor keeps flashing. And no confirmation message shows up on my phone.
It only shows "FASTBOOT mode".
Another thing i found out while installing adb drivers that it listed my phone manufacturer as HTC.
So is the problem with my phone?
And how do i fix it?
It may be a problem with driver, uninstall the previous one and install Koush universal adb driver from kaushikdatta.com
Use the link given below for a thorough tutorial to replace drivers.
http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/
Thanks for reply,
I'll try the drivers.
Though my adb drivers are working fine. My issue is with fastboot.
When i boot into fastboot mode it shows "FASTBOOT mode" on a black screen.
But i would try with the
That black screen with fastboot mode written at the bottom comes up on every phone when you boot into bootloader.
Please read the whole guide before proceeding.
You may skip the driver and adb installation part if u have already taken the measures I stated before.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot or any other tool for rooting.
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!