Fire 7 (7th gen) doesn't connect to any computer - Fire Q&A, Help & Troubleshooting

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.

Related

Vista Sync

I can only get Vista WMDC to see a new ROM once. I have followed the driver updates for the RUU. Still it doesn't alllow me to sync.
It just says not connected. USB or Bluetoothe.
I can use the phone to connect to the net either way though...
I searched and didn't see much on this...
Without connecting your device, open WMDC, click on Mobile Device Settings, End a partnership, Choose which partnership to end, click on End Partnership. Re-establish connection to your device from WMDC.
I have tried doing that. That will only work if the ROM I am using is different than the one I had original set up WMDC with.
For instance the other day I loaded Dutty's latest offering and when I went to download some pictures WMDC just said not connected. I deleted the device and upon reconnecting the device it saw it fine. I disconnected the device and when I tried later to connect it said not connected. I checked the cable, used the same USB port, tried blue tooth aand deleted the device and reconnected all with the same result. Not connected...
I of course made sure that USB was checked. I even did the driver upgrade for RUU for Vista.
My Kaiser tethers to the laptop perfectly through USB and Bluetooth so it doesn't seem a port problem, cable problem... The Kaiser syncs fine with my XP laptop as well using the same cable.
I am running Vista Home Premium and Dutty's latest...
Are you running the latest version of WMDC? I believe the latest version is 6.1.
you can always double check if
{
"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"
}
are running.
for me i had to reinstall wmdc when i flash
I am running WMDC 6.1.6965 and I show all three of the services in the post above this as started.

GalaxyTab(GT1000) flashed by USB ? USb seems to be defect..

Hello,
actually don't know why but my galaxy tab doesn't seem to work over usb. It loads through usb like normal.. but it doesnt connect for odin or just as hard drive.
wether in ubuntu(linux) nor OS X or even Windows 7 (tried several pcs and several editions, with and without kies bein installed!)
Any clue if I can flash it through SD without the need of connecting it to a PC ? Or how I can fix the usb problem ?
I guess it came through a "failed flash" but I dont know. I tried to flash it once through ODIN but after that try it didn't work. The TAB itself works like everything else but just the usb connection doesnt!
I think maybe after flashing a new rom it will work again ?
hackint0sh said:
Hello,
actually don't know why but my galaxy tab doesn't seem to work over usb. It loads through usb like normal.. but it doesnt connect for odin or just as hard drive.
Go to menu, settings, wireless and network, go down to usb settings and make sure it is selected as mass storage. I am not sure if you have tried this or not but after I flashed I had no working usb so I went into the usb setting and I had to select mass storage and now it works perfect.
I hope this helps you in any way
Sent From Githrog's Tab
Click to expand...
Click to collapse
OP you will be better served posting this in Q&A section.
Sent from my SPH-D700 using XDA App
Here is the info you should read..
http://forum.xda-developers.com/showthread.php?t=1099036
{
"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"
}

[Q] screen with a yellow triangle

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.

OPO stuck on recovery mode loop and PC won't recognise it in order for me to flash it

So recently I did a stupid and accidentally switched off my OPO during an update installation and completely screwed it all up. I tried switching it back on only to find that it was stuck in a recovery mode loop. I then hit factory reset in a last ditch attempt to save the poor bugger without flashing it and even that didn't work.
I've then had to resort to flashing it using the OPO toolkit software on my PC however when connecting to the PC, my OPO only shows up as an MTP USB Device and nothing else. I have tried installing recommended Samsung drivers for the phone but I wasn't able to as it the "update drivers" button was greyed out on the MTP USB Device properties window.
{
"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"
}
Basically, the OPO toolkit will not work as no android devices are recognised by the PC even though an android device is showing up in the control panel.
There is no way I can currently access the settings on my phone due to recovery mode loop obviously.
The last thing I want to do here is end up with being forced to use the OnePlus support which I hope most of you understand why.
Thanks for any suggestions!
Hi,
This thread is being moved to your own dedicated forum , where the experts may be able to help you better.
Good luck!
Put it in downloading mode and then use adb to use the toolkit since bow u don't have a os on the OPO happened with me too but I fixed it this way
Sent from my A0001 using Tapatalk

ADB can't find my device in fastboot

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.

Categories

Resources