Database Users

[Q] Trouble when installing TWRP on Kindle

So I was following the tutorial HERE to install TWRP, after successfully installing root via the previous tutorial.
I got to the step where you have to hit "reboot" on the kindle screen, and then press any key in the CMD prompt. I waited till it was on the yellow triangle screen, with text at the bottom stating I can press power button for recovery. I hit "space" to progress my installation, and it got stuck at "activating normal <4000>" as the video said might happen.
Following the instructions, I opened Device Manager and sure enough, the kindle was displaying a missing driver icon (although mine was still called kindle, in the video it was called something else.) I told it to reinstall the drivers, and this is where it got strange. It claimed the driver was up to date, but still displayed the yellow driver error symbol. Now, when I plug in the kindle, it shows up as "unknown device" and when I try to install the driver, it claims my driver for unknown device is up to date.
Meanwhile, the kindle itself it chilling on the yellow fire/triangle screen.
wat do

It says your drivers are up to date? You shouldn't be trying to auto install drivers, you have to do it manually, or are you trying but its just not letting you?

I am manually selecting the folder in the Device Manager dialog, and it tells me that the driver for "unknown device" is up to date

I have found that if I turn the kindle off by holding the power button down, then plugging it in(while off) it will show up as "ADB Device" (not ADB Composite Device), but nothing works, and if at this point it is unplugged and re-plugged in, it returns to Unknown Device giving an error code 43

Okay getting to adb device works, reinstall the drivers like your supposed to under that and then use KFU to try to get it to boot normally

googlelover said:
Okay getting to adb device works, reinstall the drivers like your supposed to under that and then use KFU to try to get it to boot normally
Click to expand...
Click to collapse
well, I got it to display "ADB Composite Interface, but when I run the KFU, it says ADB Status: Offline.
Furthermore, when I run "adb devices" my kindle does not show up

What device IDs do you have listed in %userprofile%\.android\adb_usb.ini? I know most people only list one ID but I found that a surefire way to get the driver working is to have both 0x1949 and 0x18D1. You also need to have those IDs in android_winusb.inf
This was the only way I could get my Kindle to be recognized while in recovery

SirVilhelm said:
What device IDs do you have listed in %userprofile%\.android\adb_usb.ini? I know most people only list one ID but I found that a surefire way to get the driver working is to have both 0x1949 and 0x18D1. You also need to have those IDs in android_winusb.inf
This was the only way I could get my Kindle to be recognized while in recovery
Click to expand...
Click to collapse
I added the 0x18D1 to adb_usb.ini, and I beleive it was already in the other .inf file. Now, my kindle is connected, and device manager sees adb composite device, but adb devices says nothing is connected. Im feeling a reboot might be necessary, which sucks because my computer doesnt reboot well (long story)

You can try adb kill-server and try again

Trouble
Having trouble getting TWRP to install on my Kindle Fire, I had no problems getting it Rooted and getting the Market installed, but trying to run the TWRP program it just hangs at the waiting for device and the Kindle hung at the KindleFire logo. I'm running Window's 7 64 bit is this suitable for TWRP
Thanks for any help.

SirVilhelm said:
You can try adb kill-server and try again
Click to expand...
Click to collapse
it is still not seeing the kindle connected. Anyway, how do I use KFU to restore the device?

I fixed my device using the info I found in a thread: http://forum.xda-developers.com/showthread.php?t=1431785
fastboot oem idme bootmode 4000
fastboot reboot
Unplug your Fire from USB, turn it off (hold the power button ~30 sec), run the first fastboot command above, then plug it in. If the first command completes, do the second.
Click to expand...
Click to collapse

ADB not recognizing nexus 7 in recovery

Hello,
First of all, the problem started when Android Kitkat update ota came to my device. After downloading it, my device was not able to verify it, as a result of which, it started downloading the update all over again. It downloaded the update more than 10 times without any success.
So finally I decided to sideload it. I set up everything properly, double checked everything. As I was going to send the update.zip to my tablet through command, the cmd prompt showed me "error: device not found".
I restarted the device, checked the drivers in my computer, even checked whether adb recognized it by commanding "adb devices". It did.
So again I turned it off, entered fastboot mode, But this time before entering recovery, I connected the device (it gave the connecting sound as on Win7). I ran the command "adb devices" and it showed no device at all!
My device is complete stock, unrooted. Usb debugging is turned on and MTP is selected.

Use a toolkit to install\test adb drivers then slide load using it. Some times windows install some crap adb drivers u have to remove them and install the naked drivers.
Toolkit is in development section.
I tested with wugfresh toolkit.
Please ignore my spelling mistakes. English is not my native language.

Moto G4 seen by Windows but not by adb in fastboot mode

I'm trying to unlock the bootloader on my XT1622.
I can transfer files etc and backup when connected to PC and in Windows
I have installed the drivers and fastboot and adb and opened a cmd window in Admin mode in the directory where fastboot.exe and adb.exe are installed.
I have restarted the phone in fastboot mode (power up plus Vol Down) and connected by USB cable to my PC but when I type adb devices I get no information coming back.
Does anyone have any idea, please, where I may be going wrong?

Anyone able to help, please?
My post above is getting a number of views but sadly no replies.
Since posting I have tried different cables, different USB ports and even installed the drivers on my wife's laptop, but to the same effect - the device is seen in File Explorer but after booting into bootloader both fastboot devices and adb devices return blanks.
I think I'll just give up on the idea, which is a shame as accomplished it easily on my old Nexus tablet and on previous Moto G iterations.

actomox said:
My post above is getting a number of views but sadly no replies.
Since posting I have tried different cables, different USB ports and even installed the drivers on my wife's laptop, but to the same effect - the device is seen in File Explorer but after booting into bootloader both fastboot devices and adb devices return blanks.
I think I'll just give up on the idea, which is a shame as accomplished it easily on my old Nexus tablet and on previous Moto G iterations.
Click to expand...
Click to collapse
adb mode doesn't work when you are in the bootloader. But fastboot should. Boot into your phone and go to settings/Developer options and make sure you have OEM unlocking and Android debugging both enabled. Then on your PC connect your cable and open a command window. type the command "adb devices" and see if your phone shows up now. If so you can then boot into the bootloader via the command "adb reboot bootloader" While in the bootloader type the command "fastboot devices" and see if your phone shows up. If so you are good to go.
Oh, and I am assuming you have a non-Amazon model?

Still no show
Thanks Palmyra. I have followed those instructions to the letter.
In Developer options both OEM unlocking and USB debugging are switched on.
When I connect to the PC and run adb devices in a CMD window it first responds that daemon has been successfully started then that the list of devices is attached but it then returns me to the command prompt.
I did then try 'adb reboot bootloader' but it returned 'error: device not found' - not unexpected given the first command result.
In File Explorer however under this PC it does list Moto G(4) and I am able to explore the phone contents there.
It is not an Amazon model.
I really am at a loss to understand why this is happening.
pastorbob62 said:
adb mode doesn't work when you are in the bootloader. But fastboot should. Boot into your phone and go to settings/Developer options and make sure you have OEM unlocking and Android debugging both enabled. Then on your PC connect your cable and open a command window. type the command "adb devices" and see if your phone shows up now. If so you can then boot into the bootloader via the command "adb reboot bootloader" While in the bootloader type the command "fastboot devices" and see if your phone shows up. If so you are good to go.
Oh, and I am assuming you have a non-Amazon model?
Click to expand...
Click to collapse

actomox said:
Thanks Palmyra. I have followed those instructions to the letter.
In Developer options both OEM unlocking and USB debugging are switched on.
When I connect to the PC and run adb devices in a CMD window it first responds that daemon has been successfully started then that the list of devices is attached but it then returns me to the command prompt.
I did then try 'adb reboot bootloader' but it returned 'error: device not found' - not unexpected given the first command result.
In File Explorer however under this PC it does list Moto G(4) and I am able to explore the phone contents there.
It is not an Amazon model.
I really am at a loss to understand why this is happening.
Click to expand...
Click to collapse
Have you installed Motorola Device Manager? I had your same issue until I had installed the Motorola drivers.

Still no joy
negusp said:
Have you installed Motorola Device Manager? I had your same issue until I had installed the Motorola drivers.
Click to expand...
Click to collapse
Thanks. Yes, I have installed Motorola Device Manager. In Windows Device Manager the MotoG4 shows under Portable Devices only when USB set to Charging or File Transfer and as an Android device with Motorola Device Manager when connected as PTP. The situation has persisted since updating to Nougat and 'adb devices' draws a blank no matter which USB connection mode I use.

actomox said:
Thanks. Yes, I have installed Motorola Device Manager. In Windows Device Manager the MotoG4 shows under Portable Devices only when USB set to Charging or File Transfer and as an Android device with Motorola Device Manager when connected as PTP. The situation has persisted since updating to Nougat and 'adb devices' draws a blank no matter which USB connection mode I use.
Click to expand...
Click to collapse
Did an RSA key dialogue ever pop up when you plugged it into your PC?
If fastboot shows no devices when your phone is in fastboot mode (voldown+power hold), then something is seriously off. Have you tried multiple USB cables?
On your wife's PC did you make sure to install adb/fastboot and drivers: https://forum.xda-developers.com/showthread.php?t=2588979
And make sure to run the cmd shell as administrator/root? (right click cmd, click run as admin)

Will double check everything
Will double check all of those pointers over the weekend and report back. Thanks

Success at last
Went onto my wife's computer and deleted all that I could find relating to SDK and Motorola. Re-installed adb tools and the Motorola drivers and now adb devices return the details of the connected phone. Onto the next stage of unlocking the bootloader and then rooting. Thanks for the help.

Bootloop/ADB/Data Recovery - Phone Not Recognized With Correct Drivers

I am trying to recover the data from my old bootlooping LGV20. My drivers are updated. When I plug my current, working LGV20 into the computer, the phone is immediately recognized and the driver is listed as LG v4.2.0, the most current in Device Manager. The phone is labled as its model number in Devices and Printers. When I plug in my old V20 (which has full access to stock recovery and download mode but does not boot) the computer recognizes something is plugged in, but in Device Manager the device doesn't show up. In Devices and Printers the phone shows up, but as "LGE Android Phone".
Summary:
When a working LGV20 is plugged in, it is recognized and the latest 4.2.0 driver is used.
When the bootlooping phone is plugged in and completely off, it is only recognized as "LGE Android Phone"
Not recognized in Recovery mode
Because of this issue, I cannot use adb on the phone to recover my data.
The phone is stock, non-rooted, android 7, LG-VS995. I have the usb debugging option in the recovery menu though the phone bootloops when this is selected.
ADB installed via 15 second installer and SDK.
"ADB Devices" returns nothing.
When in Download mode, "Fastboot devices" returns nothing.
This issue was repeated on a second computer.
USB 2.0 and 3.0 tried.
The phone is recognized in LGMobileSupportTool
In Download mode the phone is recognized as "LGE AndroidNet" in Devices and Printers and as a COM41 port (changed from 7) in Devices and printers.
What do? I'm at a loss and it feels like I've tried everything.
Edit: I've successfully dumped the phone via LGUP, tried flashed a new image, phone is still bootlooping. Is there any way I can browse the userdata dump file?

Device not recognized in Bootloader

I know I am probably the millionth person to say this, but I can't for the life of me get my device recognized in ADB when it's in Bootloader.
What I have tried so far:
- Activated OEM Unlock, USB debugging and set my computer to always be allowed for usb debugging
- Manually installed latest google usb drivers through device manager
- started up adb in cmd, made sure the device was recognized, rebooted in bootloader to check device list again
- Same thing, but with the drivers from the Mi A1 Tool)
The results:
- in Bootloader: Not recognized in ADB, but windows device manager shows "Android Bootloader Interface" as properly installed with google's driver 11.0.0.0.
- booted up: Recognized in ADB as " d59.... device" and in device manager as "ADB Interface"
This is not my first android rooting experience, but I have never had such problems installing drivers before. Is there anything special about the MI A1 I don't know? Anything I am forgetting maybe? All other Threads I found weren't helpful.
Thank you in advance for just taking the time to read until this point Any pointers even just links will be much appreciated!

Did you type 'su' after opening ADB/command prompt?

No I did not. Will try it out at home, but isn't that just for superuser meaning root access? The command to list devices should be "adb devices" not matter what mode the device is in, no?
Thank you for the tip!

Use "fastboot devices" "fastboot oem unlock".