Database Develop

[Q] ADB Device Not Recognized

Any help with my problem would be greatly appreciated!
Recently I managed to soft brick my Kindle Fire HD 7", and hoped to use the "KFHD System.img Restore Tool" to fix. I bought a factory cable and was able to put my Kindle into fastboot mode. Prior to this I had ADB installed so I could root my KFHD (which I did).
Now obviously when I rooted my KFHD, ADB recognized my device then. Unfortunately, now I have no such luck. While in fastboot I tried to use the command ---> adb shell su -c "reboot bootloader" <--- but I kept getting error messages that stated there was no recognized device.
I re-installed the AndroidSDK file to ensure there were no errors there and tested ADB with successful results. I also re-installed the Device Drivers and made sure that in my device manager under Kindle Fire it said "Android ADB composite interface" (or similar, I don't remember off of the top of my head). I went back and tested again, and ADB still does not recognize my device while in fastboot. I then left my Kindle on until it ran out of battery to test to see if ADB would recognize when out of fastboot.
After turning on my Kindle when not in fastboot, I typed in the command prompt "adb devices" and no device showed up. Also, now under my device manager "Android ADB composite interface" or whatever doesn't even show up. I have searched over and over again on many forums with no luck. Does anyone know what I am doing wrong? Or what I should try doing?
Sorry for that ^huge story^ but thanks in advance for any feedback!

ADB and fastboot are completely different programs that work in completely different modes. And entering ’ adb shell su -c "reboot bootloader" ’ is pointless because (even if adb commands in fastboot were possible) fastboot mode is the "bootloader" part of the aforementioned command.
"That's a special kind of stupid. The kind that makes me laugh."

I have a similar problem with both linux and windows 8
I have a factory cable and the kindle is in fastboot mode
Under linux I just get a "waiting for fastboot" upon entering a command
Under windows I have an otter2-prod-04 device which I have no drivers for. I have tried the latest ADB composite drivers and the amazon kindle ones.
I'm pulling my hair out now, not only have I got into this situation that I need to restore but now find I cant!!
Any help, please....
Bryan

bryanchapman9999 said:
I have a similar problem with both linux and windows 8
I have a factory cable and the kindle is in fastboot mode
Under linux I just get a "waiting for fastboot" upon entering a command
Under windows I have an otter2-prod-04 device which I have no drivers for. I have tried the latest ADB composite drivers and the amazon kindle ones.
I'm pulling my hair out now, not only have I got into this situation that I need to restore but now find I cant!!
Any help, please....
Bryan
Click to expand...
Click to collapse
In Linux, you need udev rules set for adb and sometimes fastboot. And from what I've seen, Windows 8 is incompatible with the Android device drivers.
"That's a special kind of stupid. The kind that makes me laugh."

soupmagnet said:
In Linux, you need udev rules set for adb and sometimes fastboot. And from what I've seen, Windows 8 is incompatible with the Android device drivers.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Ive been using the android drivers on windows 8 without an issue. They have to be manually installed and driver signing needs to be turned off.
Sent from my KFOT using Tapatalk 2

soupmagnet said:
ADB and fastboot are completely different programs that work in completely different modes. And entering ’ adb shell su -c "reboot bootloader" ’ is pointless because (even if adb commands in fastboot were possible) fastboot mode is the "bootloader" part of the aforementioned command.
Click to expand...
Click to collapse
I see, well the program seemed to work fine without it apparently (the line of code). My Kindle is working perfectly again! Thank you for the reply.

[Q] Can't get adb working on my One

Hello
I have done all many researches in forum, and made sure all of below are done but just can't get adb working on my device in fastboot mode...
- Installed USB driver
- Debugging mode is on
- Not using 3.0 USB port
- Using Win 7 64 bits
Fastboot is working fine but adb can't find my device at all. It shows blank list after I typed "adb devices"
Funny thing is when I boot into TWRP recovery and use the adb sideload function, adb can find my device correctly!
Anyone got a clue what's happening on my One? I really want to make adb works so I can make it s-off.
Thanks.

adb doesn't work in fastboot mode.

BenPope said:
adb doesn't work in fastboot mode.
Click to expand...
Click to collapse
Thanks and sorry for my noobiness.
I always think I need to boot into fastboot mode for adb.
:fingers-crossed:

try an custom recovery witch support adb like teawin

I use TWRP for ADB. TWRP > Advanced > ADB Sideload.

Fastboot Commands

Hey Guys any1 knows the fastboot commands for booting Device into recovery Mode and checking connected Devices?
Help would be nice, need to know
Thx Advanced

Function: Check connection and get basic information about devices connected to the computer.
"adb devices"
"fastboot devices" - This is essentially the same command as adb devices above. However, it works in the bootloader, which ADB does not.
Function: Reboot your phone into recovery mode.
"adb reboot recovery"
Obviously without the speech marks.

Stock ROM install without ADB commands

Hello all
Please is it possible to install stock ROM or stock OTA update without ADB commands?
Some other way for install?
Because my watch blocking ADB authorization!!!
Simply not show confirmation ADB dialog window
I tryed everything around ADB and nothing
I´m on stock recovery for info...
Thank you very much for help :good:
Have a nice day for all

Somebody help me?
Thank you very much

https://forum.xda-developers.com/zenwatch-3/how-to/guide-how-to-revert-to-android-wear-1-5-t3635196
No adb commands required. To enter fastboot press and hold Upper button+ Center button on turned off watch.
Here you can find more useful info https://forum.xda-developers.com/zenwatch-3/how-to/guide-reboot-recovery-fastboot-unlock-t3546743

djdarkrider said:
https://forum.xda-developers.com/zenwatch-3/how-to/guide-how-to-revert-to-android-wear-1-5-t3635196
No adb commands required. To enter fastboot press and hold Upper button+ Center button on turned off watch.
Here you can find more useful info https://forum.xda-developers.com/zenwatch-3/how-to/guide-reboot-recovery-fastboot-unlock-t3546743
Click to expand...
Click to collapse
Thank you for reply but in both links are adb commands...

those are fastboot commands. You don't need adb popup on watch to use them.

djdarkrider said:
those are fastboot commands. You don't need adb popup on watch to use them.
Click to expand...
Click to collapse
I can't use adb commands because my device is unauthorized for adb commands
I can't authorize my watch because not showing pop up window for allow adb.
Note: all my other Android devices works fine for adb commands and authorization...
This mean that problem is in the watch...

Hoffmanns said:
I can't use adb commands because my device is unauthorized for adb commands
I can't authorize my watch because not showing pop up window for allow adb.
Note: all my other Android devices works fine for adb commands and authorization...
This mean that problem is in the watch...
Click to expand...
Click to collapse
I get it.
Those commands are typed in adb command line, when your watch are in FASTBOOT mode. There will be no authorization for fastboot mode. Turn your watch off, then press and hold power+upper buttons, until you are in fastboot mode(it will be written on watch screen). Then connect watch to pc and type "fastboot devices" in adb window.
Just try it. NO AUTHORIZATION REQUIRED

djdarkrider said:
I get it.
Those commands are typed in adb command line, when your watch are in FASTBOOT mode. There will be no authorization for fastboot mode. Turn your watch off, then press and hold power+upper buttons, until you are in fastboot mode(it will be written on watch screen). Then connect watch to pc and type "fastboot devices" in adb window.
Just try it. NO AUTHORIZATION REQUIRED
Click to expand...
Click to collapse
God bless you :laugh::good:
It's working :laugh:
I tryed many many things but not this
Thank you very much for your help and time :good::good::good:

(Remote Failure) Failed to flash Partition Error while installing Stock Rom

My Nexus 6 was Running on Blissrom and I tried Magisk to Root it and it works perfectly. But When I rebooted my device it stuck at Ap Fastboot mode So I tried to install stock rom and it giving me (Remote Failure) Failed to flash Partition.
Iam on Latest Bootloader Version.
Please Help me Devs

I’m thinking that your problem is that you are using a platform tool set that is too new. The newer versions were not designed to work well with the N6.
I suggest using minimal ADB & Fastboot. Use an older release to better match the older nature of the N6. try one of the 1.3 versions. Then just follow the install instructions on the factory full OTA images page to sideload the OTA. Or, if you are bootloader unlocked (says so on the screen when booted into the bootloader) you could Fastboot flash using the Google Factory Images page.
The instructions on each page are very accurate. Make sure to note when the say “older device” that includes the N6.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

I Tried 1.3 Mnimal adb version but still get this error remote failure .
ktmom said:
I’m thinking that your problem is that you are using a platform tool set that is too new. The newer versions were not designed to work well with the N6.
I suggest using minimal ADB & Fastboot. Use an older release to better match the older nature of the N6. try one of the 1.3 versions. Then just follow the install instructions on the factory full OTA images page to sideload the OTA. Or, if you are bootloader unlocked (says so on the screen when booted into the bootloader) you could Fastboot flash using the Google Factory Images page.
The instructions on each page are very accurate. Make sure to note when the say “older device” that includes the N6.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
i tried older 1.3 Minimal adb but still get this error . I attached an Image

I'm so not a Windows person, but are you positive the minimal version was actually being run, and not the studio version of Fastboot? The whole slot thing didn't exist way back.
Have you tried sideloading the OTA?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

Post a photo of the phone in bootloader mode - maybe we can spot something unusual.
Can you start recovery from bootloader?

No I Cant Reboot to Recovery
runekock said:
Post a photo of the phone in bootloader mode - maybe we can spot something unusual.
Can you start recovery from bootloader?
Click to expand...
Click to collapse
I can't reboot to recovery but i can temporaily boot twrp using nexus root toolkit
i have attached an image of Ap fastboot mode

I Can't Reboot to Recovery
ktmom said:
I'm so not a Windows person, but are you positive the minimal version was actually being run, and not the studio version of Fastboot? The whole slot thing didn't exist way back.
Have you tried sideloading the OTA?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
When I try to reboot to recovery from ap fastboot nothing happens. So I try Nexus root toolkit to temporary boot into twrp but in twrp nothing is mounted so I cant do anything.
Please Help ME

Your photo shows nothing unusual.
Honestly, I don't have much hope. My guess is that your flash disk is damaged.
When you have TWRP running, it should be possible to get some diagnostics with adb on the PC. Below are some commands to try, they write the diag to some text files which you can post. Maybe some of it will tell us something, but I warn you that I won't know how to fix it in any case.
adb shell dmesg >dmesg.txt
adb shell cat /proc/partitions >parts.txt
adb shell df >df.txt
adb shell cat /tmp/recovery.log >recover.txt

it showing me access denied
runekock said:
Your photo shows nothing unusual.
Honestly, I don't have much hope. My guess is that your flash disk is damaged.
When you have TWRP running, it should be possible to get some diagnostics with adb on the PC. Below are some commands to try, they write the diag to some text files which you can post. Maybe some of it will tell us something, but I warn you that I won't know how to fix it in any case.
adb shell dmesg >dmesg.txt
adb shell cat /proc/partitions >parts.txt
adb shell df >df.txt
adb shell cat /tmp/recovery.log >recover.txt
Click to expand...
Click to collapse
Showing me Access Denied

Does adb devices work? And show the phone?

Yes it work it shows adb recovery but adb shell is not working when I try adb shell command its shows some variables like '$#

panup310 said:
Yes it work it shows adb recovery but adb shell is not working when I try adb shell command its shows some variables like '$#
Click to expand...
Click to collapse
~# are correct prompts when in the ADB shell. But the commands posted by @runekock should be entered as written without first entering the ADB shell. What willl happen is the ADB shell will execute the command and then dump the information into a text file in the directory where you are working on the PC.
Code:
adb shell dmesg >dmesg.txt
adb shell cat /proc/partitions >parts.txt
adb shell df >df.txt
adb shell cat /tmp/recovery.log >recover.txt
The first command tells ADB to enter a shell then read the dmseg file and output it to a text file "dmesg.txt". Each subsequent line is doing the same type of thing.
You'll want to post the output files of each of those.
If you can boot recovery and use ADB, I would think you should be able to sideload the factory full OTA image (linked in earlier post).
This should be achievable by:
Code:
adb shell twrp sideload
TWRP will switch to a screen "Running Recovery Commands". it should also have a line that says "Starting ADB sideload feature..."
Now flash the OTA using:
Code:
adb sideload NameOfFactoryOTA.zip

panup310 said:
When I try to reboot to recovery from ap fastboot nothing happens. So I try Nexus root toolkit to temporary boot into twrp but in twrp nothing is mounted so I cant do anything.
Please Help ME
Click to expand...
Click to collapse
If I'm understanding correctly. You need the file(s) you're trying to flash or restore & TWRP isn't showing any files.
If so I'd load an USB OTG device loaded with all possible files you might need. Then plug it in to your N6 microUSB & point TWRP to OTG device NOT Internal Storage. Then flash or restore whatever you want.

I Can't use USB OTG because it is not mounted
zapjb said:
If I'm understanding correctly. You need the file(s) you're trying to flash or restore & TWRP isn't showing any files.
If so I'd load an USB OTG device loaded with all possible files you might need. Then plug it in to your N6 microUSB & point TWRP to OTG device NOT Internal Storage. Then flash or restore whatever you want.
Click to expand...
Click to collapse
Its Show Internal Storage (0mb) OTG(0mb)

I tried to flash ota through side load but it failed
ktmom said:
~# are correct prompts when in the ADB shell. But the commands posted by @runekock should be entered as written without first entering the ADB shell. What willl happen is the ADB shell will execute the command and then dump the information into a text file in the directory where you are working on the PC.
Code:
adb shell dmesg >dmesg.txt
adb shell cat /proc/partitions >parts.txt
adb shell df >df.txt
adb shell cat /tmp/recovery.log >recover.txt
The first command tells ADB to enter a shell then read the dmseg file and output it to a text file "dmesg.txt". Each subsequent line is doing the same type of thing.
You'll want to post the output files of each of those.
If you can boot recovery and use ADB, I would think you should be able to sideload the factory full OTA image (linked in earlier post).
This should be achievable by:
Code:
adb shell twrp sideload
TWRP will switch to a screen "Running Recovery Commands". it should also have a line that says "Starting ADB sideload feature..."
Now flash the OTA using:
Code:
adb sideload NameOfFactoryOTA.zip
Click to expand...
Click to collapse
I have attached an Image of Twrp Error