Related
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
Hi all,
I've a nexus s updated to 2.3.4 and need to root the device.
I've installed the SDK on my windows 7, and hopefully installed the drivers correctly
1- for android 1.0 driver, which one should I choose: (ADB interface, bootog interface, composite interface) ?
2-trying loading the 3 choices, when I try to run the adb devices command it returns nothing, so what could be the problem?
Hope to help me out as I've trying solving this for a long time
Search the forums for the PDA.net app the driver package there works well for windows 7.
Sent from my Nexus S 4G using XDA Premium App
Thanks
I've just discovered that fastboot command is working fine.
I did fastboot devices and got the serial. adb command is not working.
I think I can go with rooting now.
how to get the lates version of clockworkMod for 2.3.4?
heshamsalah said:
Thanks
I've just discovered that fastboot command is working fine.
I did fastboot devices and got the serial. adb command is not working.
I think I can go with rooting now.
how to get the lates version of clockworkMod for 2.3.4?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1039584
Download it from the first post here. Make sure you extract the .img file from the .zip file. (don't try to flash the zip )
Hey guys I have given up. Been looking at this for two days now and it will not work. Heres the problem.
I have ran X-factor unlock as per instructions and it ran successfully all the way to the point where it asked did I want to see the identifier token. I hit yes and then the it froze. Let it sit there for like 5 minutes and nothing. So I closed X-factor and open cmd and booted the phone into fastboot. Then I plugged my phone into my computer and ran the fastboot command "fastboot oem get_identifier_token" and I does nothing. I also tried running "fastboot devices" and still notthing. I have reinstalled htc sync manager, pdanet for the drivers, have tried all different version of fastboot and adb and nothing is working. What could I possibly be doing wrong? Pdanet recognizes that the phone is plugged into the pc and the phone recognizes it too but fastboot doesn't. Any help is appreciated.
Are you running the fastboot command from the folder where you extracted it ? And did you download the latest file of X-factor unlock ( First one had few bugs)
Extract the zip file which you downloaded and now open Command Prompt, change the directory to the folder where you extracted the fastboot zip.
Example ( if you extracted in Downloads Folder then) cd C:\Users\username\Downloads\fastboot-win32
then execute the command again " fastboot oem get_identifier_token"
Sent from my HTC One XL using xda premium
abhipati said:
Are you running the fastboot command from the folder where you extracted it ? And did you download the latest file of X-factor unlock ( First one had few bugs)
Extract the zip file which you downloaded and now open Command Prompt, change the directory to the folder where you extracted the fastboot zip.
Example ( if you extracted in Downloads Folder then) cd C:\Users\username\Downloads\fastboot-win32
then execute the command again " fastboot oem get_identifier_token"
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I downloaded X-factor last night around 12a.m. And when I run the cmd I first hold down shift and then right click in my the folder android sdk/ platform tools. Adb, and fastboot along with several other files are in this folder. when running the command nothing happens. Cmd just adds another line.
ImagioX1 said:
I downloaded X-factor last night around 12a.m. And when I run the cmd I first hold down shift and then right click in my the folder android sdk/ platform tools. Adb, and fastboot along with several other files are in this folder. when running the command nothing happens. Cmd just adds another line.
Click to expand...
Click to collapse
Did you install HTC sync
First things first, do you get anything when you do adb devices?
APSBiker said:
First things first, do you get anything when you do adb devices?
Click to expand...
Click to collapse
Yaa, when u plug in your device type "adb devices" in command prompt (from android platform tools folder) did u get any response "[serialNumber] [state]"??
Sent from my HTC One XL using xda premium
abhipati said:
Did you install HTC sync
Click to expand...
Click to collapse
I said in my firt post that I did.
I have tried adb devices and for some reason it works some times and other times I get nothing. I suppose X-Factor is using adb though and the adb part( the two backups and the reboot into fastboot) of X-Factors works all the time. Its only when the phone reboots into fastboot that the rest of the commands don't work with X-factor. Only once did it work and it said it was successfull- i go the 111111111 for my CID. But when I hit enter to view the token X-Factor did nothing.
I have another idea that might work. I was wonder what you guys thought. I have vmware running Mac Os and I was wondering if I could download the Mac tools to my vm and try running the commands that way. Since Mac doesn't doesn't need drivers do you think that would work?
I still haven't figure the problem out. So I just booted up Mac OS in vmware and used the mac fastboot and it work. Yay! unlocked bootloader! Now to flash super user.
ImagioX1 said:
I still haven't figure the problem out. So I just booted up Mac OS in vmware and used the mac fastboot and it work. Yay! unlocked bootloader! Now to flash super user.
Click to expand...
Click to collapse
Awesome! Thanks for updating us on how you got it to work. I guess I was one of the lucky ones that it worked the first time for.
That was a tough fix. Windows still will not recognize my device in adb or fastboot. I don't know what the problem is. But the only catch to running Mac Os in vmware is it is against the EULA so I am not telling you to try that. But It will work. I have been looking at this for 2 days now and I had to go install Mac Os in vmware and register with apple and all that good stuff before I could even start running commands. It was tough but I hope its worth it.
USB debugging
I have a Desire without OS, it can boot into fastboot. Is there any way to know if USB debugging was switched on from here? I tried to unlock the bootloader, im on S-ON, but keep getting errors:
C:\Users\Alienanihilator\Desktop\Roms\HTC Roms\HTC One X\HTC_fastboot_files>fast
boot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
Maybe has to do with USB debugging not being turned on before?
You're in the wrong forum, this is the One XL forum. You need to ask in the Desire forum.
Sent from my Evita
Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
I'm stuck, I need my phone the next few days very often...
I dont know what to do anymore if I try to do the same with the OTA zip file it says FAILED (remote: 24 parsing android-info fail)
(When I tried before with TWRP ADB Sideload before I flashed the firmware.zip, it told me "file_getprop failed to stat /system/build.prop"
What can I do now to get my phone working again
Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?
jollywhitefoot said:
Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?
Click to expand...
Click to collapse
- HBOOT 2.22.000
- openrecovery-twrp-2.7.1.0-m4.img (It's the only version where I even can see my devices with "adb devices")
- Yes I am
- Not really I can go with ADB Sideload but using "adb sideload" does not work...
It tells me:
sending: 'rom.zip' 100%
On my phone it's saved under /data/media/sideload.zip but it tells me:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/data/media/sideload.zip'
Click to expand...
Click to collapse
I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2
jollywhitefoot said:
I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2
Click to expand...
Click to collapse
The problem is that I cant install the ROM.
I've push'ed it do the ROM but as you can see my post above TWRP only gives me error :/
LuvMyHTC21 said:
Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
Click to expand...
Click to collapse
just try to flash not OTA, but ROM
version 2 from here will be Ok
Sweet Jesus, finally after 9 hours (no joke) I got it working, thank you so much !
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both.
Oneplus 7 pro is running 10.3.0GM21AA
>fastboot devices
>adb devices
List of devices attached
966c8016 device
Trying to use fastboot to flash patched magisk img and install magisk.
Do you enter in fastboot in phone?
Sent from my GM1910 using Tapatalk
Yes tried from bootloader as well
fustyler said:
Yes tried from bootloader as well
Click to expand...
Click to collapse
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
redpoint73 said:
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
Click to expand...
Click to collapse
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
fustyler said:
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
Click to expand...
Click to collapse
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
redpoint73 said:
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
Click to expand...
Click to collapse
Have tried different cables and different machines both pc and mac
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
mnemesis said:
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
Click to expand...
Click to collapse
I ran adb reboot bootloader from pc to boot phone into fastboot.
In the bootloader it states device state is unlocked
However fastboot devices ran from pc still shows no device.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thanks this fixed it.
Issue fixed by billyt1's comment above. case closed.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Giri Prasad said:
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Click to expand...
Click to collapse
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
I have a similar problem. I tried to disable the signature. Installed a new Redmi Note 7 driver. The phone is recognized as an Android phone in the device manager. In Orangefox recovery it is recognized with ADB command. In fastboot it is not recognized. In Orangefox I can't format data. So my ROM is not booting up. So I want to flash fastboot ROM with Fastboot but in Fastboot device is not even recognized.
t
puyow18 said:
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
Click to expand...
Click to collapse
Sorry on the late reply. Pretty sure you can only do fastboot boot boot(recovery).img or\and boot_a or boot_b. Wont let you fastboot flash boot.img.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thank you so much!
I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.
Thank you Thank you Thank you Thank you Thank you Thank you...I have been fooling with this all day
Hi, I already solved this issue (but this only works for xiaomi phone (Redmi Note 7 to be specified), for other brands I think need to download your devices flasher/driver tool)
For Xiaomi user only
1. Download Mi Unlock Tool (https://mi-globe.com/download-xiaomi-mi-unlock-tool-all-versions/) (Version 4.5.813.51)
2. Extract the files anywhere you like
3. Run MiUsbDriver.exe to install the driver
4. Try fastboot devices command
I hope this helps you guys. The Mi Unlock Tool also useful to unlock device locked bootloader.
For other devices maybe can follow this tutorial
Fixed: Fastboot not detecting your Android device
Fix the Fastboot not detecting your device. If your device is not detected by the Fastboot then these tricks will really help you.
www.qasimtricks.com