Hello guys,
Seems like my bootloader is dead.
When i'm trying to reload it with ADB, i'm getting the <waiting for device> message.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your help is appreciated,
Thanks!
That all i have in the kindle properties
Is the kindle in fastboot mode when you run this command? If it is and you are still seeing it as a MTP device, uninstall the MTP device in the device manager, if it then still reinstalls as a MTP device or doesn't show up as anything then look for a USB composite device with a vid of 1949 and remove it. I wouldn't say your bootloader is dead since your PC can detect it.
stunts513 said:
Is the kindle in fastboot mode when you run this command? If it is and you are still seeing it as a MTP device, uninstall the MTP device in the device manager, if it then still reinstalls as a MTP device or doesn't show up as anything then look for a USB composite device with a vid of 1949 and remove it. I wouldn't say your bootloader is dead since your PC can detect it.
Click to expand...
Click to collapse
First of all thank you for trying to help me!
When I delete the MTP device it was reinstalls once again.
I'm not sure I understand what do you mean by "vid of 1949".
can you give me some more information ?
I deleted all USB composite devices but no result.
My PC recognize it as MTB USB Device. I can enter into TWRP but can do nothing there.
So when in twrp does it show up still in the device manager? And by vid I mean if you right cluck a device in the device manager and hit properties, then goto the details tab and choose hardware id's from the drop-down list, if the vid has 1949 next to it then it's the kindle. Its basically the hardware id of the device before you see a name that is user-friendly.
Related
My KFFOWI (ford) is not recognized in fastboot, but is recognized in ADB. The device manager on my computer says "Needs trouble shooting." Any help is appreciated! Thanks!
trentonpls said:
My KFFOWI (ford) is not recognized in fastboot, but is recognized in ADB. The device manager on my computer says "Needs trouble shooting." Any help is appreciated! Thanks!
Click to expand...
Click to collapse
you installed drivers from here? http://forum.xda-developers.com/amazon-fire/general/howto-install-drivers-adb-fastboot-mode-t3236187
Don't worry if you see "failed to install MT65xx Preloader driver" errors every kffowi boots through that before fastboot mode.
If drivers are not selected automatically and selecting folder does not work
right click on android_winusb.inf file (latest_usb_driver_windows\usb_driver)
select install
Then manually select drivers
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface for Stock rom or recovery/adb sideload
Select Android ADB interface for Fastboot mode
or Android Composite ADB interface
next
you may have to reboot pc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried everything I could think of, try different cable, install adb driver, try in different computers, turn ADB debugging on and off, turn MTP on and off.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It doesnt even see it in portable devices nor does it install drivers when I plug it in.
ReiHayashi said:
I tried everything I could think of, try different cable, install adb driver, try in different computers, turn ADB debugging on and off, turn MTP on and off.
It doesnt even see it in portable devices nor does it install drivers when I plug it in.
Click to expand...
Click to collapse
Possible the USB port is damaged if there is no host acknowledgement when the device is initially tethered.
Davey126 said:
Possible the USB port is damaged if there is no host acknowledgement when the device is initially tethered.
Click to expand...
Click to collapse
I wouldn't think so since I just got it last week and it was working fine..
ReiHayashi said:
I wouldn't think so since I just got it last week and it was working fine..
Click to expand...
Click to collapse
It would seem you have ruled out most common obstacles by trying different hosts, ports, cables drivers, etc. Windows should acknowledge a hardware connection (audibly and in device manager) even if the 'wrong' driver is installed/selected. A final test might involve placing your device in recovery mode and invoking the sideload option while monitoring Windows device manager. If nothing shows up the you have a 'hardware' issue would could be any component in the chain.
I bought a used phone. The boot loader was unlocked from the beginning. I'm doing the steps to install Android 10, but something is weird.
I tried to go through the fastboot mode, but when I press the button, it doesn't respond, so I enter the computer through adb and there is no response, and then it returns to the system soon. When entering the boot loader mode to adb, a blue LED turns on. When I enter the recovery mode into adb, there is no reaction the same as when entering the fastboot. Also, when the power is turned off and plugged in, it automatically enters the flash mode.
When I first use the phone, the battery level is displayed when I plug it in, and it responds when I turn it on, but when I reinstall the stock rom of the same version with flashtool, nothing happens. There is no response even though I installed the 8.0 global version with the flashtool obtained from the deveploperworld homepage.
Strangely, the Android system works fine.
What should I do?
(I am Korean, and the sentences may be weird using Google Translate. Please understand.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I installed the Google USB driver and updated it, but it looks like this..
problem Solved!
Inscartia said:
I installed the Google USB driver and updated it, but it looks like this..
Click to expand...
Click to collapse
Solved the problem! If the Google USB driver does not work when recognized as other devices, try updating with the Samsung USB driver. It is recognized as a samsung adb interface and is recognized as normal in the fastboot devices command. You can install twrp in this state!
Cannot flash Pixel 5 back to stock Android for Calyx. Have tried everything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As soon as I enter fast boot mode the phone disconnects from my computer or something. I can't get it to work with the Flash Tool or without it. Has anyone else had this problem? I'm at a loss and don't know what to do.
I get this error as attached.
Have you got usb debugging on ? And bootloader unlocked
jaythenut said:
Have you got usb debugging on ? And bootloader unlocked
Click to expand...
Click to collapse
Yes, I have bootloader unlocked and debugging turned on.
Open your Windows Device Manager while connected in fastboot mode (Right click Windows logo -> Device Manager).
Do you see your phone in the list with an exclamation or question mark?
Open your Windows Device Manager while connected in fastboot mode (Right click Windows logo -> Device Manager).
Do you see your phone in the list with an exclamation or question mark?
Try with a USB-A to C cable. Do not use the supplied C to C cable.
There is something wrong with Calyxos.
Unlocked bootloader becomes LOCKED when you try to use flash.android.com on the first reboot.
How did I get it ON the phone if it was locked? well, it wasn't and now Calyx won't unlock the boot loader (even though it says it is)
Calyx website is not working.
I don't have windows, This is F'd
Anyone able to help me get this garbage off my phone?
Hi,
I want to flash TRWP onto my REDMI 8. However, as soon as I boot into fastboot, adb shell can't find my device anymore.
I've tried everything, installing new Fastboot drivers in Device Manager, new USB cable, other USB port, nothing works. ADB finds my phone in normal mode, but not in fastboot mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try waiting a little longer for it to register your device also make sure that usb debugging is on and that all the latest drivers for your phone are installed on your pc
Na, it won't register, it doesn't find the device.
USB debugging is on.
I've even installed the Xiaomi Tool V2, which supposedly has all the right drivers.
in fastboot mode, its fastboot devices and not adb ;P
if that also fails, try clockwork mod (cwm) universal adb drivers. worked for me for all these years including this phone
also, there are still plenty of roms available iirc, in case they dont show up for olive, you might be able to try mi439
Since you're in Windows, when you plug it in it might/should "bong".
Then you have to find out what is there and whether it has a driver.
ADB and fastboot are usually mutually exclusive.
You might try looking deeper with UsbView.exe https://www.ftdichip.com/Support/Utilities.htm#MicrosoftUSBView
Or you could look in Device Manager C:\>devmgmt.msc
Or you could shell out >$1000 for a hardware USB protocol analyzer.
I got it to work now, thx. Starting from ADB into Fastboot didn't work, but manually booting into FB and the installing twrp did the trick.