Fastboot unable to connect - Hero, G2 Touch Q&A, Help & Troubleshooting

Hi
I have got a hero on the cheap currently using an iPhone boot looking to move over.
The hero has a custom rom on it, I would liketo try others. Holding down the home button and powering on just leaves it with the G2 boot screen. Holding down back button and power brings me into fastboot USB. When connected to the mac I am unable to see the device / list it using adb devices. If I boot into the os and connect to the mac not mounting the sdcard I can see the device with adv devices.
I'm trying to install a recovery image, this is proving dificult with not seeing the device in fastboot.
Has anyone any thought/suggestions on to resolve? Or point me in the direction of some threads to read.
Tia
deano

use fastboot devices when in fastboot...

HI,
thanks for the reply, when in fastboot on the device I use fastboot which i have downloaded from the andriod site and put in my "tools" folder when trying to lash a recovery image it just comes back with a prompt saying "waiting for device"
thanks

just to make sure: you turn off the phone, then turn it on again while holding down BACK. this brings you to a screen with a white background and fastboot written somewhere. then you plug in the usb cable and execute "fastboot devices". if it still doesn't recognize your device then you got a problem somewhere, no idea where though. not sure if windows needs drivers or anything for fastboot to work correctly...

Yes that's correct.
Phone is recognize in everything other than when connected by fastboot.
Thanks for your input

Related

[Q]Fastboot not working?

On my Atrix 4G, I can't get the fastboot to work. I have installed the latest drivers for windows and created the rules files in linux and for both operating systems when I try to run fastboot I just get a <waiting for device>. Can anyone help me with this problem?
enderx1 said:
On my Atrix 4G, I can't get the fastboot to work. I have installed the latest drivers for windows and created the rules files in linux and for both operating systems when I try to run fastboot I just get a <waiting for device>. Can anyone help me with this problem?
Click to expand...
Click to collapse
That happen to me. All i did was put the phone in fastboot mode and it connect right away. Press volumn down button while powering on the phone. When the screen said Fastboot, then you press up on the volumn button.
I'd suggest trying to run "fastboot devices" before any other commands, just to verify that you have connected to the phone successfully. If you don't get any response from the "fastboot devices" command, you've still got an issue. For my money, the probable sources are lack of drivers, or phone isn't in fastboot mode.
the piont is how to do?
I have the phone in fastboot mode, and fastboot devices returns nothing. Where would I get the correct drivers? I believe I have the correct ones, for windows that is. For linux I have configured the rules.d files as well.
Hi,
Use moto-fastboot, you can find links in the dev section from -eval and others, it will detect the device, also it supports large partitions, unlike the regular fast boot binary you might find via Google. If you do a lsusb and it shows an nvidia entry, you are good to go on the phone side.
Cheers!
Hi,
I have been searching the forums for it, and I have not been able to find the moto-fastboot binary. Could you link to it?
http://forum.xda-developers.com/showthread.php?t=1138092

[Q] Stuck in boot cycle after flashing to Neutrino 2.5p, can't boot in to recovery

I was on Neutrino 2.5, I flashed to 2.5p (without wiping).
It wasn't working as I wanted so I went in to recovery to reflash the google apps zip.
After that I'm now stuck in a boot cycle loop and I can't even boot in to recovery mode. When I try to enter recovery it says "Entering Android Recovery Mode" then the screen just goes blank.
Really sorry to make this my first post but I'm kinda freaking out right now. Don't have any idea how to recover from this.
rodabi said:
I was on Neutrino 2.5, I flashed to 2.5p (without wiping).
It wasn't working as I wanted so I went in to recovery to reflash the google apps zip.
After that I'm now stuck in a boot cycle loop and I can't even boot in to recovery mode. When I try to enter recovery it says "Entering Android Recovery Mode" then the screen just goes blank.
Really sorry to make this my first post but I'm kinda freaking out right now. Don't have any idea how to recover from this.
Click to expand...
Click to collapse
flash the recovery again using fastboot
Thanks for the reply. So my problem so is that I'm trying to boot in to RSD mode but it get the message "Battery is too low to flash".
I'm trying to charge the battery but whenever i plug it in to charge phone starts up and ends up in the boot cycle, and the battery doesn't end up charging.
How can i force the phone not to turn on when I plug it in to the wall charger?
Ok, I was able to McGyver a usb charger from an old cable and I got the battery charged enough where it would enter fastboot.
However... now I can't get either of my laptops to recognize the phone in fastboot.
I attach the phone to the usb port, turn the phone on and hold the volume down button. I press the volume up button when fastboot appears, the message "Starting Fastboot protocol support" appears and then nothing happens. Windows just sits there, the phone just sits there...
If I do moto-fastboot devices at the command prompt there is no serial.
Any thoughts?
Well, normally nothing happens until you issue a fastboot command. I usually boot into fastboot mode first, THEN connect the phone & open a command line, etc.
What happens if you do the above and type "fastboot devices"? Does it see your phone then?
Ok, so I tried your method, and installing some different windows drivers and now windows does recognize the phone!
For the record, I am on windows xp and currently i'm using driver version 2.0.40 (same problem with 2.0.53).
Now windows isn't able to install the fastboot drivers, it comes up as an unrecognized device. Is there a way to manually install the fastboot drivers?
Although it's recognized by windows, issuing the moto-fastboot devices command still returns blank.

fastboot "waiting for device"

Hi there,
I have a problem that i suspect others may have, i did my searching on google and on xda but found nothing so i have no other choice but to post. I am trying to fastboot flash a prerooted .67 firmware, i put my phone into fastboot and connected the usb cable, the led STAYS blue that seems to be fine(i have installed fastboot drivers using flashtool /drivers directory), i type in the fastboot command to flash it and it just sticks at "waiting for device".
Any ideas?
Thanks
What happens when you type:
fastboot.exe -i 0x0fce getvar version
Also:
1. Disable any antivirus
2. reboot your PC
3. Change to another USB port
4. Make sure the .img is in the same folder as the fastboot.exe
Try fastbooting an official firmware instead if that works then I believe you have encountered the 'bug' in the bootloader that is currently stopping any custom roms
unrealboot1 said:
Hi there,
I have a problem that i suspect others may have, i did my searching on google and on xda but found nothing so i have no other choice but to post. I am trying to fastboot flash a prerooted .67 firmware, i put my phone into fastboot and connected the usb cable, the led STAYS blue that seems to be fine(i have installed fastboot drivers using flashtool /drivers directory), i type in the fastboot command to flash it and it just sticks at "waiting for device".
Any ideas?
Thanks
Click to expand...
Click to collapse
Hi,
you know that every smartphone has a flash and a fast boot Feature ?
Some Smartphone, look´s like Sony, use:
Speaker UP Button and USB Connect for Fastboot
(by Sony the Home Button lights blue)
and
Speaker Down Button and USB Connect for Flash
(by Sony the Home Button lights green)
For Fastboot.exe ........ xy.img must be use the Fastboot
Feature.
In first using Fastboot.exe, after Phone Connect you must
wait that the PC find all Drivers.
If Fastboot doesn´t work again, maybe you need "SDK Android"
and "Google SDK Driver"... will find over Net.
Doesn´t work again, the use "Flashtool.exe" Methode and
convert the xy.xy Firmware to xy.ftf for Flashtool use.
Onex1
my version is 0.5
i tried all of this except the last point of Onex1. Nothing works still sticks at waiting for device. Also havent restarted my pc i will try that soon but i think that might be a long shot.
Also my device is recognised as an adb device if that helps.
Any ideas guys? I have been trying but now im all spent. My xperia s is unlocked and factory bootloader unlocked if that helps
I know this thread is really old, but I was having this same issue and it was fixed by using a newer version of the Android SDK. So if you're having problems, try updating!
U must enable USB debugging mode
Send from Xperia U
i have the same issue
power on off button is broke
i can boot to recovery but i cant select to flash anything because of the button its not working
adb works for me too because its recognized when i write adb devices but when i write fastboot devices nothing happens and everything i do it says waiting for device
anyway PrakashGD, he said adb is working, that means USB Debugging is ON, if it was off adb would've not worked duh
Ensure fastboot driver is installed
Sent from my ST25i using xda premium

[Q] Can't fastboot boot.img

Okay, so basically I am a HUGE idiot. My phone has been running the latest version of ParanoidAndroid and I decided that I wanted to try MIUI. I booted into TWRP v2.6.3 and wiped everything a couple of times before installing it, and I forgot to install the boot.img afterwards (it was s-on). So now everytime I turn the phone on, it is just always on the boot animation for an eternity, and my computer won't recognize my phone so I can't use fastboot or use an RUU. I am also unable to flash PH98IMG from the phone itself. Is there anything I can do to fix this? Thank you very much in advance.
trp6senile said:
Okay, so basically I am a HUGE idiot. My phone has been running the latest version of ParanoidAndroid and I decided that I wanted to try MIUI. I booted into TWRP v2.6.3 and wiped everything a couple of times before installing it, and I forgot to install the boot.img afterwards (it was s-on). So now everytime I turn the phone on, it is just always on the boot animation for an eternity, and my computer won't recognize my phone so I can't use fastboot or use an RUU. I am also unable to flash PH98IMG from the phone itself. Is there anything I can do to fix this? Thank you very much in advance.
Click to expand...
Click to collapse
Take out the battery, put it back together, power on the phone while holding down the volume down key til you get the splash screen, that'll boot you to the bootloader...
No I understand that, but there's nothing I can do from the bootloader. Once I get there, I can either go to TWRP or choose Fastboot. When I choose fastboot, it will say Fastboot USB after connecting to my PC but it will still not show up or be recognized (and I have the drivers). My only other options are Recovery (TWRP), factory reset (also TWRP), clear storage, simlock, and image crc. All I need to do is load the boot.img file, but it appears to me I have no way of doing that now.
trp6senile said:
No I understand that, but there's nothing I can do from the bootloader. Once I get there, I can either go to TWRP or choose Fastboot. When I choose fastboot, it will say Fastboot USB after connecting to my PC but it will still not show up or be recognized (and I have the drivers). My only other options are Recovery (TWRP), factory reset (also TWRP), clear storage, simlock, and image crc. All I need to do is load the boot.img file, but it appears to me I have no way of doing that now.
Click to expand...
Click to collapse
Being seen in fastboot has nothing to do with the ROM at all, you need to troubleshoot this from the PC end. When you start fastboot on the phone and connect to your PC you get nothing? Not even a connect sound?
acejavelin said:
Being seen in fastboot has nothing to do with the ROM at all, you need to troubleshoot this from the PC end. When you start fastboot on the phone and connect to your PC you get nothing? Not even a connect sound?
Click to expand...
Click to collapse
I do get the connect and disconnect sounds. Whenever it makes the connect sound, it doesn't show up under "Devices with Removable Storage." When I heard the connect sound the first time I went to the cmd prompt and typed "fastboot devices" but it showed nothing.
trp6senile said:
I do get the connect and disconnect sounds. Whenever it makes the connect sound, it doesn't show up under "Devices with Removable Storage." When I heard the connect sound the first time I went to the cmd prompt and typed "fastboot devices" but it showed nothing.
Click to expand...
Click to collapse
It won't show up as a drive at all in Fastboot mode, to see if it is connected properly go to Device Manager and look for ADB Interface -> My HTC, if it isn't there then your drivers are not installed properly. Drivers come from HTC Sync, which can be downloaded here: http://www.htc.com/us/support/content.aspx?id=6196 once installed and the connections in Fastboot and ADB verified to be working, HTC Sync can be uninstalled (the drivers will stay).
When you run "fastboot devices" you get nothing? Or do you get something like "< waiting for device >" or literally nothing?
What version of Windows are you running, you need to be on Windows 7 or older? Running under Windows 8 is not recommended.
acejavelin said:
It won't show up as a drive at all in Fastboot mode, to see if it is connected properly go to Device Manager and look for ADB Interface -> My HTC, if it isn't there then your drivers are not installed properly. Drivers come from HTC Sync, which can be downloaded here: <link> once installed and the connections in Fastboot and ADB verified to be working, HTC Sync can be uninstalled (the drivers will stay).
When you run "fastboot devices" you get nothing? Or do you get something like "< waiting for device >" or literally nothing?
What version of Windows are you running, you need to be on Windows 7 or older? Running under Windows 8 is not recommended.
Click to expand...
Click to collapse
Ah, that may be my problem then, as I am on a Windows 8 computer. I will try all of this on a friends W7 computer in the next few hours and report back with the results. And when I did fastboot devices it literally said nothing and was ready for another command. Thanks for the help!
trp6senile said:
Ah, that may be my problem then, as I am on a Windows 8 computer. I will try all of this on a friends W7 computer in the next few hours and report back with the results. And when I did fastboot devices it literally said nothing and was ready for another command. Thanks for the help!
Click to expand...
Click to collapse
You can also use a live Linux CD like Ubuntu and boot that and install the Linux version of ADB, it works fine.

How to change build. prop file in the devices without fastboot option??

Hii I have a chinese yxtel g905 android mobile. I have rooted it and changed the build. prop file. After rebooting it the phone is not booting. It is just powering on and immediately after the boot animation is completed it is turning off and it also don't have fastboot mood or recovery option.I have tried this by long pressing all the possible combinations of buttons. So someone tell me friends is there any solution for such a problem?? Like feeding new build. prop file into the device or anything like that.
Some devices show no signs of activity in fastboot mode.
It might look like that the phone is switched off but it would actually be in fastboot mode.
To check, try power + volume up/volume down/both then connect the phone to the PC (with all the necessary tools and drivers) and type
Code:
fastboot devices
Into the command prompt.
It will show a list of all devices that are in fastboot mode and connected to the PC.
If you are able to confirm that the phone is now in fastboot, you can proceed to flash the stock ROM (given that you already have it) to your device.
Sent from my Xiaomi HMNote1W using Tapatalk

Categories

Resources