Database Develop

Fastboot Devices not found

Hey guys. I am running ubuntu 10.10 and i have successfully installed android sdk and the eclipse in their proper places and added the neccessary coding to make everything work. One problem though. When i have my G1 32B in fastboot mode, it wont recognize my phone so i can use fastboot to flash the newest radio and SPL. i know others have achieved to being able to flash it without a problem.. I have tried to troubleshoot this myself with the help of the internet and xda... but still the same problem keeps re occuring. and to tell you the truth, it is really pissing me off. I have downloaded fastboot drivers and placed them in the sdk/tools folder and moved adb to that folder as well for easier access. I dont know what else to do. If any one has any solutions or would be a help please. Thank you for reading.

bosna110 said:
. When i have my G1 32B in fastboot mode, it wont recognize my phone so i can use fastboot to flash the newest radio and SPL
Click to expand...
Click to collapse
The question is: can linux see the phone (plug in the phone while in fastboot mode and check dmesg)
If linux sees it and fastboot can't.. make sure its not permission issues [read is fastboot running as root? if not can your user read the USB device?] The phone identifies its self differently in fastboot mode vs. adb/mass storage mode. So don't assume the fact adb works from your normal login means fastboot will also.

linux sees it no problem.. but when im in fastboot mode, its not wanting to list the device.

Try executing fastboot as root.
Sent from my Gingerbread on Dream using XDA App

ok give me 1 sec.. ill go try it our right now. i am trying to flash terry's spl and radio so i can have the extra 14 or 15 megs of ram extra because my g1 is so sluggish right now i can barely use it for anything.

Strange thing with me is that it loads a different driver in fastboot. If I have it turned on normally, in my Device Manager it shows as "ADB interface -> HTC Dream Composite ADB Interface". (I think it used to show as just "HTC Dream"). I had to switch to HTC Bootloader. :/
Edit: only skimmed. Missed anything about Linux.

He's on linux ... the drivers should load automatically.
Sent from my Gingerbread on Dream using XDA App

ok i must be doing something wrong its either me or the laptop.. im doing "su" on the terminal and then when i enter in my password, it says auth failed.... this is friggen bee ess

Try
sudo fastboot devices
And when asking for the password you enter your user's password.
Sent from my Gingerbread on Dream using XDA App

still doing the same thing.
ok, what i did was
1. open terminal
2. cd sdk/tools
3. now i make sure my phone is recognizable while in fastboot mode so i do ./adb devices
4. then when i look at the listed devices, my phone isnt listed..
5. then i try doing sudo fastboot devices and entering my password and its still not working.
let me try restarting my laptop.. perhaps that is going to fix it..

ok, just to make my self look dumber lol.. when my phone is shut off
i pressed back and the power buttons at the same time until the white screen with the android skateboards come up.. am i supposed to then press the trackball button to get into fastboot mode?
cause maybe i am not pressing something correctly to get it to work right. ill keep refreshing this page every minute for a reply..

bosna110 said:
3. now i make sure my phone is recognizable while in fastboot mode so i do ./adb devices
Click to expand...
Click to collapse
adb will never work if you are in fastboot mode... and fastboot will only work when in fastboot mode.
so Dont run './adb devices' run './fastboot devices' or as we mentioned to run it as root 'sudo ./fastboot devices'

ok, gotcha. when i did the ./fastboot devices, it told me the Permission denied.

im sorry, i must be really brain dead right now.. i totally forgot to checkmark fastboot as an exectuable on its properties.. now its recognizing my G1 no problem. now its the flashing that is giving me some trouble

Please help. Strange problem with fastboot mode

Hello guys,
I have 3 identical phones i-mobile IQ2. They are shared among our family.
Mine (fortunately) is runnng fine. The 2 others not so. That's the reason why I want to flash a different ROM.
I have 2 Computers, One with Windows, the other Linux. Both are equipped with adb/fastboot.
What did I do?
1) enabled developer options in the settings.
2) enabled USB debugging and OEM unlock in developer options.
3) Connect the phone via USB
4) Terminal command "adb devices" shows correct serial number of the phone
5) and here it starts. After typing "adb reboot bootloader", the phone shows the white i-mobile screen which is shown when you enter fastboot mode. But....
6) "fastboot devices" results in the terminal message "waiting for any devices"
And that's it. Nothing happens. Retried with 2 phones and always the same. The funny thing is that on my identical phone, there is not a problem and typing "fastboot devices" results in a proper recognition of my phone.
So.... is there anything that I could have done wrong or that I forgot? How can I unlock my bootloader in a different way? As far as I know, adb commands are usually the last resort.
I would appreciate every help. Thanks

You need to install fastboot drivers for your device when your device is in fastboot mode as I know.
here is the right drivers for me in the whole internet: https://mega.nz/#!YcUABBpR!_8w6S5zj_Ct2eBMPr6cL1d1NhC4AZEfphOSQJRJZmjU

I had the same problem on my gm4g nd i solved installing the correct driver just like nhmanas said. Good luck.

nhmanas said:
You need to install fastboot drivers for your device when your device is in fastboot mode as I know.
here is the right drivers for me in the whole internet: https://mega.nz/#!YcUABBpR!_8w6S5zj_Ct2eBMPr6cL1d1NhC4AZEfphOSQJRJZmjU
Click to expand...
Click to collapse
Ok, I will try and get back to you again. Thanks for now.

Super noob here, need help with adb

I installed hisuite which is easily able to access all my device data. Installed adb universal which created c:/abd in my pc or don't know what created that. Installed minimal abd fast boot . Now the problem is, i go to c:/adb and open command line and keep getting "waiting for devices" then goto x86/minimal adb.... Again same thing. Even installed android sdk without even knowing what I'm doing. Now I'm feeling like dumb (probably I'm) and about about to give up. What I'm missing??

What are you trying to do and what commands are you issuing?
I'm assuming at the very least you have phone connected with debugging enabled.

Just trying to follow commands of "Unlock Bootloader, Even without code! by hackintosh5". But first I'm doing some simple commands like "fastboot reboot recovery" or "fastboot devices" but no luck. I must be doing something terribly wrong. At least show me a guide article, cause when i search i get extremely confused.
Some more info.
-usb debugging enabled, and pc authorized (maybe)
-hisuite is able to read everything so i must GUESS i have installed correct driver (tho i have no idea what it is)

Ok, to use the fastboot commands, the phone must be in fastboot mode. This is achieved by when phone is off , hold Vol - and connect phone to PC via USB.
Then try the above commands.

It finally worked, thanks a lot brother :laugh:

A guide for flashing TWRP?

I've been searching all over the place...
Could anyone point me at a guide for newbs?
Thanks!
X

1xcalibur1 said:
I've been searching all over the place...
Could anyone point me at a guide for newbs?
Thanks!
X
Click to expand...
Click to collapse
First, you need your bootloader to be unlocked. It's pretty easy if you have that done already.
You'll need ADB and Fastboot. It can be tricky to get the right drivers. The driver used when your phone is connected in normal mode is not the same when connected in fastboot mode, in my experience anyway. You'll want the 15sec ADB driver and you'll need to update the driver when it is in fastboot mode.
Next, get the correct twrp img and put it in the ADB folder(you'll need a different one based on flashing a pie rom or a q rom). You may want to rename it so it's easier to type in fastboot.
To enter fastboot mode, hold volume up and plug in the usb cable. The LED should light up blue.
Open a command prompt and navigate to wherever you've installed ADB(mine is on C:\ so it's really easy).
Type "fastboot devices" to double check if the driver is installed and your phone is connected in fastboot mode.
------It should show something like: BH9090808E fastboot
Then type "fastboot flash recovery twrp.img" - or whatever you've named the file. It will take less than a few seconds.
Then type "fastboot reboot" and let your phone reboot.
Done

Thanks a lot for the reply!
I've been experiencing the exact issues you described. I'm having issues unlocking the Bootloader. "Fastboot.exe devices" does not show anything, the phone is with a blue led on and a balck screen and when I look in Device Manager there's an "Other" Android device with an "!".
Could you please share the drivers you mentioned? Because I really went through
everything and none was accepted. Also the 15 Seconds ADB Drivers did not help.
Thanks!

1xcalibur1 said:
Thanks a lot for the reply!
I've been experiencing the exact issues you described. I'm having issues unlocking the Bootloader. "Fastboot.exe devices" does not show anything, the phone is with a blue led on and a balck screen and when I look in Device Manager there's an "Other" Android device with an "!".
Could you please share the drivers you mentioned? Because I really went through
everything and none was accepted. Also the 15 Seconds ADB Drivers did not help.
Thanks!
Click to expand...
Click to collapse
My apologies. It's been so long since I've started from scratch, I must've gotten the drivers mixed up. The 15sec ADB is for the phone connected in normal mode.
I'm pretty sure this one is the fastboot one:
https://developer.sony.com/file/download/xperia-xz1-compact-driver/
If not, I'm sorry because that's all I have.

I nailed it eventually!
For anyone that comes across this thread,
this video will solve all your problems with adb drivers:

Question [Fixed] ASUS logo stucks on recovery, only access to bootloader

Hi all,
I'm encountering a very annoying issue with my brand new Zenfone 8.
I wanted to install the last LineageOS image, but now my phone seems stuck.
Here are what I did:
- Unlocked the bootloader: success with the ASUS APK after a few tries (error 11000 and 11006 ans eventually worked).
- Rebooted to bootloader
- Entered into recovery
- Used fastboot to flash the vendor partition.
At this point, everything looked OK. But then.... :
- Powered off the phone and restarted to bootloader.
- Tried to enter into recovery to flash the Lineage Recovery
But at this point, I had a ASUS logo stucked on the screen.
I can't do anything with adb or fastboot commands.
I tried the method explained here (https://www.asus.com/Content/Android-13-Beta/) to rollback to stock Android 12, but nothing happened too: I looked at the shell script (I'm on Linux) and I reckon that it stucks on fastboot command (the phone is in the bootloader).
Any idea about what failed? The last command used (vendor partition flash) said "OKAY".
And especially, what can I do now? Any way to reinstall the ASUS recovery?
Thanks in advance guys.

Not quite sure what your status is if you say "can't do anything with adb or fastboot commands". I've flashed Zenfones a couple of times (my household has 3 Zenfone 8's on LineageOS) and I had one that went into ramdump. I recovered from that using fastboot to manually reflash all 19 firmware partitions, in both slots. That got the phone out of ramdump, and I got to continue the upgrade to the new LineageOS. So: if you can boot to the fastboot environment, then that would be a road that might leaed you out. But if you can't even get a response to the command "fastboot devices" then I don't know of a course of action for you.

To use fastboot commands I had to run the phone into bootloader mode, then to "recovery" and eventually "fastboot" (I'm note 100% sure but it's what I remembered).
Without that, I was unable to use any fastboot commands like device or flash.
And now the issue is that I'm not able to go to recovery/fastboot again, because I have just the ASUS logo and nothing else.
It looks like that the stock recovery was dead, but I don't know why - and I don't know how to fix/reset it.

From the bootloader you should be able to flash the raw image again, it should flash everything

Adaoh said:
From the bootloader you should be able to flash the raw image again, it should flash everything
Click to expand...
Click to collapse
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.

semurel said:
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
Click to expand...
Click to collapse
On Linux and maybe macs too you need to run fastboot commands as Root (sudo fastboot devices) for example. The raw image script should ask you for your Root password for this reason

Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).

semurel said:
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
Click to expand...
Click to collapse
Yes, they work from the bootloader, I always run the script from the BL too. Ironically, I had issues running fastboot commands from fastbootd for installing Omnirom, so I did it all in the bootloader and all worked fine.
I am not sure I can help you more at this point, it looks like it maybe got interrupted mid flashing and now something is wrong somewhere. Maybe if you look inside the bash script file you can find the command that it got stuck on and run that manually if you manage to get fastboot command access.

Strange - they have never worked from the bootloader. I tried that before according to the LineageOS wiki. I thought it was a mistake and use the recovery > fastboot to do that. I dont like that - I hope it's not a local version of the Zenfone or something like that.
I'm not at home tonight but yes I'll try to find commands not requiering the fastboot command.

Unfortunately all commands from the script are using fastboot. And as "fastboot devices" sees nothing, I can't do anything.
I've tried from the bootloader screen (with start, recovery, poweroff option) - from the start screen showing unlocked bootloader warning and from the ASUS logo when I try to start the recovery. I've tried the commands/scripts with Linux and Windows: same result.
So :
- I can't use any fastboot commands.
- I don't have the ASUS recovery.
Speaking of the ASUS recovery, I've found screenshots on internet and they don't have a "fastboot" submenu (I'm not sure it's a Zenfone 8). May had I a different version?
I don't like that. If I don't have others option, I guess that the warranty doesn't work because the phone is unlocked?

I eventually found a solution! I've tried with my old OnePlus cable and fastboot commands start working from the bootloader screen.
I have no idea why my other cable was faulty (it can charge the phone and executes commands from the Recovery > Fastboot menu - but not on the BL screen).
Anyway my problem is now fixed.
Thanks all for help and support.