Im having issues using fastboot on my vista x64 machine, it cant seem to find my G1. Im currently using the signed x64 adb driver. Has anyone gotten fastboot to work on x64? Thanks in advance for any responses.
Just to provide a bit more info, iv confirmed that my g1 is in fastboot mode via the engineering SPL. when attempting to flash images to it, fastboot cant seem to find the g1 in fastboot mode.
Works fine for me (Vista 64 + signed drivers + fastboot)...
Are you sure it's in fastboot mode? The screen actually says fastboot?
Also make sure fastboot is using AdbWinApi.dll from the 1.1 SDK and not the 1.0 SDK.
Hmm, i must be doing something wrong.. Im able to use adb normally with the x64 driver , just no fastboot. Can you send me a link to the driver you are using? Thanks.
Never mind, i think i got it, i was using an older 1.0 r2 sdk, ill try the new one. Thanks, your answer fixed my problem.
I am having the same problem. I'm using the 64 bit drivers and can use adb just fine.
When I boot the phone up I hold the camera and power, says "serial0", i insert the phone usb, push the back button so that it displays "fastloader" it then makes a "USB chime" in windows and my device manager flickers for a second.
The I run "fastboot flash system system.img' with admin privs and all i get is <waiting for device>...
Please help!!
Are you using the 1.1r1 android sdk?
http://developer.android.com/sdk/1.1_r1/index.html
So I am trying to flash an updated recovery of ClockworkMod onto my device, rooted, bootloader unlocked, etc. and installed the Android SDK to use ADB and fastboot. My Samsung USB driver is installed obviously because when I type "adb devices" it pops up with a mix of numbers and letters, which I assume is my device plugged in. I use "adb reboot bootloader" to get into bootloader and once I am in there my device is not recognizable by fastboot. ADB and fastboot are in the same folder in the C:\ drive, and I have tried using PDAnet drivers as well. I could really use some help! USB Debugging is on in the settings as well.
Syflox said:
So I am trying to flash an updated recovery of ClockworkMod onto my device, rooted, bootloader unlocked, etc. and installed the Android SDK to use ADB and fastboot. My Samsung USB driver is installed obviously because when I type "adb devices" it pops up with a mix of numbers and letters, which I assume is my device plugged in. I use "adb reboot bootloader" to get into bootloader and once I am in there my device is not recognizable by fastboot. ADB and fastboot are in the same folder in the C:\ drive, and I have tried using PDAnet drivers as well. I could really use some help! USB Debugging is on in the settings as well.
Click to expand...
Click to collapse
The GS3 does not have fastboot. All flashing is done through odin.
ddggttff3 said:
The GS3 does not have fastboot. All flashing is done through odin.
Click to expand...
Click to collapse
Thanks! Also, how do I update ClockworkMod recovery to the newest one? I've used ODIN before but am not sure if it is capable of flashing .img files.
EDIT: Nevermind, I just downloaded ROM Manager and used that to flash 6.0.2.3
I want to root my tablet so I flashed TWRP 2.6.0.0 using fastboot everything works fine.
But now I want to install the zip to root the tablet, problem is TWRP cannot mount any storage, internal sdcard external sdcard nothing at all is alway says E:Can't mount 'xxx' on anything I tap.
I tried CWM, and 2.5.0.0 and nothing seems to work.
I can boot fine in the stock OS, everything works fine but that
My bootloader is 10.6.1.27.1-20130711
Can anyone help me?
Ok now it is bad, I tried to factory reset using the bootloader (power + volume down)
It booted in the buged TWRP and now it keeps booting in TWRP and I cannot even reach the bootloader
Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE
aarsyl said:
Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
I cannot get this to work on Windows 8, I have Asus Transformer ADB interface lister in device manager but I cannot see my device with the adb devices command.
Also, in TWRP when I try adb sideload it says failed.
win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster
Buster99 said:
win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster
Click to expand...
Click to collapse
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help
Matiosse said:
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help
Click to expand...
Click to collapse
fastboot should work. hold Vol-down and reset the device and keep vol-down pressed. it should go to fastboot. when you're in fastboot connect it to your laptop and see if the OS recognized your device - if not you have a driver issue. resolve that by installing the asus driver or the newest google generic drivers.
when you can see your device on dosprompt/powershel with fastboot devices then continue with getting recovery to work.
btw- stuck in twrp means? booting twrp (teamwin screen) but not responding?
good luck
-Buster
The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways
Matiosse said:
The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways
Click to expand...
Click to collapse
but you are still able to boot into android?
I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.
Matiosse said:
I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.
Click to expand...
Click to collapse
can you boot into twrp? and i mean just boot into it? so that you see install, backup, restore etc. buttons?
if yes - twrp has an adb mode
connect your tab in twrp to your pc (check that you can see it - adb devices) if yes type: adb reboot bootloader
and you should boot into that. test it with fastboot devices.
most important thing is that you get into fastboot or a working recovery to flash or prepare to flash a (custom) rom back onto your device.
Buster
I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)
Matiosse said:
I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)
Click to expand...
Click to collapse
learn to crawl before you run :angel:
Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android
Matiosse said:
Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android
Click to expand...
Click to collapse
dude - you can't boot into android anymore, you can't boot into fastboot to your own accord - yet you try to sideload stuff in twrp for what ever reason.
i gave you more hints and tips in my previous posts and link to get it to work yet it eems you did none.
so don't get me wrong - but what excactly is your goal here?
My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.
Matiosse said:
My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.
Click to expand...
Click to collapse
yes i read your posts - but im still unclear what you are trying to accomplish with sideload?
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?) "adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
-B
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
Matiosse said:
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
Click to expand...
Click to collapse
when its connected - is device manager at least showing it as faulty or not at all? (yellow triangle exclamation mark thingy, i just installed asus on my VM) -> see attached file
UPDATE: I succeeded to go in fastboot mode
I couldn't get my tab to be recognized by windows so I installer my Nexus 4 using the toolkit, when it was succesfully installed I could manually install my tab since the "android devices" option appeared in the list when you want to manually install a driver in the devices manager. So I could choose Asus ADB interface.
Now I can boot into Android, but it will go into TWRP as soon as I restart my tablet.
Now I will try the link you sent me to get TWRP recognize my storage so I can flash a new rom, I will let you know if something go wrong.
Thanks for helping
For some reason I cant get TWRP to show my device using adb commands, which is making it impossible to adb push a rom.zip to storage. Everytime i run the adb push command i get "error: device '(null)' not found"
In bootloader, the fastboot devices command shows my device, in android adb devices shows my device also.
Ive installed and uninstalled the motorola driver numerous times and i also tried a universal adb driver. Im running windows 10 64bit, Device manager picks up my device fine when in android and in bootloader, but in twrp device manager shows a yellow exclamation under "other devices, android"
well heres the resolution to the issue...
heres what it wasnt
-tried on a fresh install of windows 7=no go
tried different drivers=no go
tried different versions of twrp=no go
The problem, it appears, was TWRP
The solution was to install Philz recovery, once this was installed i had no further issues with the device showing up in recovery using "adb devices" and consequently adb push works just fine now
TWRP ADB does work with Linux - no drivers required. It has however, always been a tricky affair when it comes to Windows.
lost101 said:
TWRP ADB does work with Linux - no drivers required. It has however, always been a tricky affair when it comes to Windows.
Click to expand...
Click to collapse
twrp has never been tricky with my samsung or HTC phones, i guess i just have to get use to all the quirks with motorola phones
Hi Team,
Greetings.
I have been using LG Nexus 5 running cm12.1 but since the moment I updated the phone to cm13 I have started facing lots of troubles. The phone boots up and stuck on cm logo also I did something and the twrp recovery is not seen anymore instead I only have cyanogemode recovery which is driving me nuts. The present situation I am facing is I can't connect my phone to the pc for me to reinstall twrp. I really appreciate your help in this matter.
Thanks a lot for your time.
Merry Christmas!
Jinson Jose.
So the phone is not detected when connected in fastboot mode? Adb commands are often used when the phone has fully booted into the installed rom.
audit13 said:
So the phone is not detected when connected in fastboot mode? Adb commands are often used when the phone has fully booted into the installed rom.
Click to expand...
Click to collapse
Hi Yes the phone is not detected and I tried adb commands too but in vain. I guess I messed up the phone while I am on cyanogenmode recovery by trying to format the phone.
Is the phone detected when you connect the phone to the computer in fastboot mode? ADB commands will not work in fastboot mode as you need to use fastboot commands.
Maybe it might be the PC drivers? I lost connection too and managed to restore it by using the driver setup module in Wugfresh's Nexus Root Toolkit. It will walk you through removing vestiges of old drivers and help install new drivers.
audit13 said:
Is the phone detected when you connect the phone to the computer in fastboot mode? ADB commands will not work in fastboot mode as you need to use fastboot commands.
Click to expand...
Click to collapse
No the phone is not detected. All I can see is a usb sign and it says nexus 5. I can't open nexus 5 files.
The computer is a Windows xp or win7 machine?
No devices are found and you run a fastboot command?
audit13 said:
The computer is a Windows xp or win7 machine?
No devices are found and you run a fastboot command?
Click to expand...
Click to collapse
Hi Thanks for your reply. The Machine is Windows 10. I tried fastboot commands as seen in one of the google searches. When I connect the phone it is not detected. I was able to see the nexus but I think I messed things by trying to factory reset and wipe cache using cyanogenmode recovery. Now the computer shows only universal serial bus devices when I connect the phone.
OP, hello...? Am I inaudible/illegible? Have you tried setting up the ADB/Fastboot via NRT as I suggested?
I don't use Win10. I do all of my flashing on a Win7 x64 machine and everything works perfectly when I am dealing with my Nexus 4, Nexus 5, and nexus 7.
I use Win10 with no problems. It must be the driver setup. NRT will fix it for the OP if he can clear whatever is preventing him seeing my post...