I boot looped my 2017 Fire 8 trying to install the Xposed framework. I have booted to recovery in an attempt to flash the Stock Firmware to my device, and selected the "apply update from ADB" option. When I attempt to do so, ADB does not recognize the device as connected.
I assume I have the correct ADB drivers installed, as I am capable of opening up a root shell on my 2017 Fire 10 when it is connected with the same USB cable and port. Maybe there is something wrong with the Fire 8 drivers?
Is there anything additional that must be done to enable ADB in recovery mode?
Edit: fixed it by manually updating the fire drivers through the device manager. This could only be done when in ADB sideload from recovery boot.
Related
i was able to root but now adb won't recognize my kindle. have tried reinstalling the drivers like i found in many threads. they install fine but adb won't recognize kindle. any ideas?
to help further a bit more information would be helful
os/bit of computer ?
rooted - which method ? burritoroot3 ? via patched kfu ?
status of kf ? normal boot - hang ?
fff / twrp or cwm allready installed ?
allready tried cold reset ? holding pwr ~20sec
i had this trouble too
i couldnt get adb to work then out of some miracle it started working after restarting my kindle and installing different usb drivers. i ended up using the nexus s driver and i guess it worked
b63 said:
to help further a bit more information would be helful
os/bit of computer ?
rooted - which method ? burritoroot3 ? via patched kfu ?
status of kf ? normal boot - hang ?
fff / twrp or cwm allready installed ?
allready tried cold reset ? holding pwr ~20sec
Click to expand...
Click to collapse
win7 64bit
rooted burritoroot2
kindle works normal. boot shows fff and then boots up
fff installed. no twrp or cwm (that's my next step if i get this adb thing fixed)
yes already tried cold reset? no difference.
Make sure that Android USB Debugging is enabled (checked) in settings. You could also try going to device manager in Windows and uninstall the kindle fire drivers, then reinstall them, restart computer. Hopefully will work then.
would recommend to use kfu cause there is everything included that you need
http://forum.xda-developers.com/showthread.php?t=1399889
place/extract it to c:\ and rename it to "kfu" - it don't like spaces in pathname
patch it for use with burritoroot3
http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
Follow these steps to set driver verification levels:
1.Press [Windows]Break to display the System Properties dialog box.
2.Select the Hardware tab and click the Driver Signing button in the Drivers panel.
3.Select the Block-Never Install Unsigned Driver Software button. (Verify that the Make This Action The System Default check box is selected.)
4.Click OK twice.
try to install the included drivers by running install_drivers.bat
if it does'nt work try to update them manually:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
the drivers are in c:\kfu\drivers\kindle
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
also check adb_usb.ini in your .android folder in your personal folder
it should include 0x1949 and 0x18D1 - if not add it in a new line
also unplug, restart of kf & computer and replug sometimes helps ...
My shield won't boot, and every indication is that it needs to be reflashed with the system OS, per a few threads here. I can get to the fastboot menu, but I can't get adb to recognize the device. I have tried several rounds of adb drivers-the android SDK, the 2015 NVidia USB drivers, and the 2018 NVidia drivers. I used USBDView to verify that the Shield is connected to USB, and checked the VendorID and ProductID and verified that it was listed in the driver INF. Still, the adb utility doesn't show the device.
I'm in way over my head as far as trying to reflash this, and I'm hoping someone who has this device and already has success in flashing it might be willing to reflash it for me?
Fastboot and ADB are different, check you are connected VIA fastboot with a USB to USB cable. You should have fastboot in the same folder you are trying to ADB
To check connection
<folder> fastboot devices
To flash the firmware
Download the full recovery image here
https://developer.nvidia.com/gameworksdownload
Unzip to your fastboot folder
run the flash_all.bat
<folder> fastboot flash_all.bat
Be patient, it will take a while, do not unplug. Let it run its course and it will reboot when complete.
This should get it working, it did for me.
i downloaded. the usb driver from https://developer.amazon.com/docs/f...indows-user-uninstall-the-existing-usb-driver
installed
adb reboot recovery.
once in recovery from the tablet i select adb sideload the the tablet goes into that mode.. i no longer have adb
adb devices doesnt work. so i cant do adb sideload firefirmware 5.6.1.0
please help i'm trying to go back to stock because i deleted some apps in bloatware that messed up the tablet.
I found this link to sideload adb, you can try it:
https://forum.xda-developers.com/ama...evice-t3238740
Firmware:
https://forum.xda-developers.com/sho...23&postcount=2
I hope it will help
Hi,
I have an HD 10 that's stuck on the fire screen.
I can boot into recovery but ADB won't recognise the device and it doesn't show up in device manager.
If I reboot into bootloader the fire appears in device manager, loads the drivers and I can use fastboot and see the device.
Is there a way to push the update.bin file to the device using fastboot so i can try and restore or is there a way to get ADB working that I've missed out?
Thanks
Nick
OK, ignore me. I had to choose 'apply from adb' so the device appeared in device manager and then manually select the drivers. All good now!
I hope someone in here can help me with the following problem:
I had an old Android version on my X720, which I wanted to update/install LineAge custom ROM with Android 10 on. Since the old Android was acting weird and USB debugging couldnt be enabled for some reason, I decided to wipe the System/Cache on it using TWRP recovery BECAUSE the device wasnt found on Windows 7 when plugging in via USB. Previously I installed ADB drivers and everything needed, but still Windows couldnt find the device and I was unable to move the Lineage ROM (plus GApps) to the device to be able to install it via TWRP. Anyway, now there is no OS installed and I can only boot into TWRP. I tried to ADB sideload the Lineage ROM via TWRP (via connected USB to my Notebook), but after typing "adb devices" and "adb sideload path...." etc. in Windows Terminal as Admin I always get "no devices found". So, when connecting the device to my Notebook, nothing is shown and the device doesnt appear under "Device Manager" and I think that's the main problem.
Does anyone have any solution or idea? Thanks a lot in advance!
try reading this useful thread:
https://forum.xda-developers.com/le-pro3/how-to/unbrick-leeco-phones-leeco-variants-t3847220
good luck!