Database Users

Computer unable to recognize kindle stuck at Boot logo

I've attempted to install drivers, but it still isn't recognized by fastboot, kindle fire utility, and everything else. I reconnect it to my computer and it just comes up as "Unknown usb device"... It came to be this way because while I was installing TWRP with Kindle fire utility it froze and it's been like that for at least 30 minutes now. I've tried restarting it, resetting it, and nothing is working. Please help!

Look here http://forum.xda-developers.com/showthread.php?t=1417966
You maybe need to change boot mode to normal
Sent from my Kindle Fire using Tapatalk

But how do I manage to change the bootmode when my computer won't recognize that my kindle is connected?
Sent from my MB525 using XDA App

Follow the instructions posted by me, there and then your device should be recognized....
Sent from my Kindle Fire using Tapatalk

http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
Had the same issue. This solution worked for me

guillotinedream said:
http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
Had the same issue. This solution worked for me
Click to expand...
Click to collapse
I love you. No homo, of course. Thanks a ton! This worked great for me. I thought that my kindle was screwed Thanks so much for that!

lol You're welcome. Glad it worked for you

Computer doesn't even recognize that a device is connected...
Okay, I'm not having the same issue, but I'm pretty sure I've completely, irevicalbly, bricked my kindle.
I know that I'm not in Fastboot mode, I've experienced that issue and solved it with the KFU.
Here's what I did:
I used the KFU to root my kindle. That worked fine. I was able to load all the Google apps (which was my initial goal). Then, I got greedy and decided that ICS was my next step - oops.
I followed the instructions on the following site:
androidauthority.com/kindle-fire-miui-4-ics-55853/
Note: I know, I'm an idiot - I should have paid attention to comments! UGH!
After I did this, I now only get the firefirefire logo and that is it. I can't load/reload TWRP and I can't change my bootmode to normal or recovery. The thing is, no matter which computer I plug the device into, the computer won't recognize the device. I get a message saying something "malfunctioned" when I plug it in. I've tried 3 different Windows machines (I've installed/reinstalled drivers I don't know how many times!) and I even tried loading Linux on a spare laptop and that didn't work either.
So, I tried the next thing I could think of. I followed the instructions on the following site:
ramble.karrth.com - Section "Troubleshooting TWRP
which involved removing the back cover, shorting a circuit (to force usbboot) and plugging my Kindle in. This didn't work for me either.
At this point, I'm willing to try anything. I'm not quite sure how to fix this issue. I think my next step is to either order a factory cable or make my own and try that, but if my bootloader is broke (truely broke) will that even work?
Please, if I should post this in another forum/place, just let me know. Any help appreciated!
I should also not that nothing comes up in my device manager. It does come up as a unrecognized USB bit goes away after telling me there was a malfunction (it tries to recognize it twice).

Please don't post the same question in multiple threads... especially ones that have been dead for 4 months. I've replied to the same question as a followup to your other post.

TF101 Won't Enter APX Mode

If you want to offer help PLEASE read through the thread, or at least the initial post. It seems like I'm repeatedly answering the same questions that were already answered.
I've tried to boot in APX and all I get is the black screen, yet neither Windows 7 64bit/Linux Mint 64 on one PC and Windows XP on another don't detect it at all. I know the cable works because when I had CWM installed I could see it attached via ADB. I'm a b30
Edit: I managed to get the stock ROM back on it, but it still doesn't want to boot into the bootloader/APX mode. I know it's not necessary but I would like to have it as a failsafe for the future.

brando56894 said:
This all started with me wanting to go back from AOKP to stock, I flashed a rooted version of 9.2.1.17 and it kept telling me to update, but when I did it failed because CWM was installed. It also wiped my system. I found 9.2.1.24 but couldn't flash it because TWRP wouldn't stick. I tried to install the stock recovery, which worked in a sense that it removed CWM but left me with just the Android and the exclamation point (I can't seem to get past that no matter what I do [vol +, Vol -, power or any combination of those] ) I decided to use NVflash to get back to complete stock and start over.... The only problem is that Windows 7 doesn't even detect the TF when its in APX mode, hence it doesn't ask me to install the drivers, nor will they install manually.
So my TF is soft bricked and nothing works. I'm going to reboot into Linux now to see if I can get nvflash working. Any other suggestions?
Edit: Linux Mint didn't detect it either I know it's not the cable since I was able to see the TF via ADB when I had CWM installed. Also the major thing that is worrying me is will the TF be recoverable if the battery dies? I have no way of knowing if it is actually off or just in APX mode, I obviously can't do a battery pull and I can't power it down from the recovery or the OS. IIRC it also won't charge when it is in recovery and I'm assuming the same is true for boot-up and APX mode.
Click to expand...
Click to collapse
Same to me-- win7 does not recognize my tf 101- apx is installed-works with another transformer well- if i do vol down and then vol up i see the laying android with exclamation mark.
no solution till now- hope you had more luck-
By the way- try to load it normal - in my case it works.
kind regards
gandalf

I just tried connecting it to an older Dell with a P4 in it and it doesn't detect it either, it just seems like the TF doesn't want to boot into APX mode. I'm doing Vol + and Power from both the recovery and from the initial splash screen, then it reboots to a black screen which I'm assuming is APX mode. From the black screen I've tried Vol + and Power for as long as 30 seconds and still nothing. There were also times when it would sit at the initial splashscreen and then go to a black screen, then I'd try to enter APX mode from there but it would be the same thing.
I've been contemplating getting a Nexus 7, partially because I lightly stepped on the screen of my TF one night and damaged it enough to cause the LCD crystals to break (there about two or three grayish "lines" where I stepped on it) but not hard enough to crack the glass. The screen will also flicker some times on that side and will also randomly shut the screen off. Maybe this is a sign telling me to get a N7?

Do you have debug mode enabled?
Where did you get the win 7 APX mode software. Some links in this site are to defective software. Go to the SDK kit site and download the software there. http://developer.android.com/sdk/index.html

Rumbleweed said:
Do you have debug mode enabled?
Where did you get the win 7 APX mode software. Some links in this site are to defective software. Go to the SDK kit site and download the software there. http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
Debug mode is for ADB, not APX. Debug mode is set in Android and with APX no Android is loaded.
I have used the live cd of Ubuntu 11.10 without installing any driver by myself. It recognized the TF with APX in my case.

There is no debug mode considering that the OS isn't installed. AFAIK debug mode is only necessary to use ADB while booted into Android. APX is something that is built in to the device. I downloaded the drivers from android.mobi which has an "unroot/unbrick" package, that doesn't matter though because Windows never asks me to install the driver so the drivers don't seem to be the problem, considering Linux (which doesn't require any drivers) doesn't see the device either.

I had the same, downloaded the drivers, but couldn't install.
After I made sure I had the correct drivers, I clicked in hardware settings on the thingy with the exclamation point, I choose manual search and had Windows search the entire c:\ drive, after a while it installed
Sent from my Transformer TF101 using xda premium

That's my problem guys. APX mode/unknown device doesn't show up in device manager

oi, than I cant help you, sorry

I think it's F'ed because I took it apart to make sure it was turned off by disconnecting the battery and then did the power and Vol+ combo but the PC still doesn't detect it.

1. your battary is empty, charge it
2. your battary is done.
3. your power key or vol-up key do not work.
4. you did not press two keys in the same time long enough
5. cable doesn't work
6. usb port doesn't work, try another one.
7. you did not pay attention on the sound of device connected nor the device list.
8. your windows broke. try another pc.
---------- Post added at 11:39 PM ---------- Previous post was at 11:33 PM ----------
get a micro sd and copy rom to it and flash, since you said cwm works ok

vista1984 said:
1. your battary is empty, charge it
2. your battary is done.
3. your power key or vol-up key do not work.
4. you did not press two keys in the same time long enough
5. cable doesn't work
6. usb port doesn't work, try another one.
7. you did not pay attention on the sound of device connected nor the device list.
8. your windows broke. try another pc.
---------- Post added at 11:39 PM ---------- Previous post was at 11:33 PM ----------
get a micro sd and copy rom to it and flash, since you said cwm works ok
Click to expand...
Click to collapse
1 & 2 It boots up to the initial splash screen and to the android recovery so the battery is ok
3. The Vol + does work unless it suddenly died because I was using it moments before I bricked it
4. I would say 30+ seconds is long enough
5. The cable does work because it charges the unit and when I had CWM installed I could see it via ADB
6. Tried another port, nothing
7. The sound is definitely noticeable and it's kind of obvious if it's not in the device manager list
8. I tired two different computers, and three different operating systems. Including Linux.
I know you are trying to be helpful but ALL of these were answered in previous posts, if not the OP.

I'm having the same issue with my pad not booting into APX, might I ask how you got the stock ROM back on it without APX?

Luckily I had the stock recovery installed and I was able to place the OTA on A MicroSD card and named it so that it would flash automatically once I booted into the recovery.
Sent from my Transformer TF101 using Tapatalk 2
Edit: here's how to do it
baseballfanz said:
Download the latest official firmware from Asus.
Extract the zip from within and rename it to "EP101_SDUPDATE.zip" (without the"" )
Put it on the root of your sdcard
Boot into stock recovery and it should flash it
Click to expand...
Click to collapse

I have to go with #5. My Transformer would charge when using my cord and so I thought it was good. Plugged it into the computer and nothing. Switch to my wife's cord and the computer saw it instantly. It was then able to see APX mode.

Yea it was actually the cord being stupid, when I got back to my house I tried my other cord and it connected just fine. I actually just sold my TF yesterday to a friend for $250 so that I can get a Nexus 7
Sent from my ADR6425LVW using Tapatalk 2

So this is making me thing that my cord is the issue, but I tried 3 different cords and none of them recognized. Is it possible the device itself has a faulty connection?

It's entirely possible, have you tried a different computer/different USB ports first though?

Tried every port on two machines as well as in linux. My HTC G2 connects just fine to everything.

You may be screwed Do you have the dock? Does it connect and charge fine with that?

[Q] Need a newbie guide for installing CM10

greetings,
i recently got my thinkpad tablet and find it quite laggy to use, so i want to install the CM10 mod here:
http://forum.xda-developers.com/showthread.php?p=32744561
i had successfully installed CM9 on my HP touchpad and my samsung galaxy exhibit phone using step by step guide, but i am still a newbie when comes to tech stuff like this.
so to install this rom, i believe i need to root my device first, and install the CM10 with CWM in recovery mode?
please correct me if i am wrong.
i am running stock 4.0.3 on the TPT, and i was trying to follow this thread to root my device:
http://forum.xda-developers.com/showthread.php?t=1925025
however, when i plug in my device to my computer it only charge itself, and a brief message of "USB device not recognize" pop up.
and sometimes i can't even find the "unknown device" from my device manager.
i tried many method and still no luck, and yes i already have usb debugging mode checked.
any advice would be appreciated.
thanks.

Hi telly0050
I haven't installed any custom ROM on this tablet, since I got mine bricked and Lenovo does not provide a way to recover it, since the bootloader is locked.
But I think that the order that you ask is the correct one. 1) Root the device 2) Install CWM recovery Menu 3)Install custom ROM.
I had tried to document as much of the Thinkpad Tablet on this wiki:
http://forum.xda-developers.com/wiki/index.php?title=Lenovo_ThinkPad
It is not a step by step guide, it only has some links, but everybody is welcome to create an step by step guide and add it to the XDA Wiki.
Regards
Martin

I'm curious to know if you managed to find a fix for this. I'm having the same issue with this device and I can't get any microUSB cable (including the factory cable) to be recognized.
I have the Thinkpad dock and even when i plug into the back of the dock with the tablet inserted I still get the "Connected to Charge Only" message.
Is there something I can do about this? Because obviously without taking it out of Charge Only I can't adb to the device.

[Q] Bootloop with no USB [Solved]

Hi,
I recently got ahold of a european XT610 which I rooted and flashed to CM7 without problem. Unfortunately I missed the warnings which said not to run bootstrap after installing cyanogenmod... and now I have the infamous bootloop. It gets to the CM loading screen, but goes on indefinitely from there. I know the answer is to restore the motorola sbf, however I can't seem to get my phone to communicate at all via usb. I installed motorola drivers and RSD and all in windows, but the phone seems to ignore the USB completely. I'm normally a linux guy, so I when I tried to plug it in there and watch the output of dmesg, absolutely nothing came up. Holding R, M and power when I plug in the usb causes a black screen after a bit of the motorola logo, but still no USB. Tried a few different cables, and checked them with other devices to confirm they're working.
So any ideas on how to recover the phone?
Update:
I discovered the main step I was missing was that the bootloader can be accessed by holding down both volume buttons and the power with the device off. For some reason I still couldn't get windows to recognize the correct drivers, even after installing the motorola driver package, but good old linux saw it without a problem. Following these instructions I was able to do a quick SBF and now all is good in the world!

same probleme for me?
ObsidianOps said:
Hi,
I recently got ahold of a european XT610 which I rooted and flashed to CM7 without problem. Unfortunately I missed the warnings which said not to run bootstrap after installing cyanogenmod... and now I have the infamous bootloop. It gets to the CM loading screen, but goes on indefinitely from there. I know the answer is to restore the motorola sbf, however I can't seem to get my phone to communicate at all via usb. I installed motorola drivers and RSD and all in windows, but the phone seems to ignore the USB completely. I'm normally a linux guy, so I when I tried to plug it in there and watch the output of dmesg, absolutely nothing came up. Holding R, M and power when I plug in the usb causes a black screen after a bit of the motorola logo, but still no USB. Tried a few different cables, and checked them with other devices to confirm they're working.
So any ideas on how to recover the phone?
Update:
I discovered the main step I was missing was that the bootloader can be accessed by holding down both volume buttons and the power with the device off. For some reason I still couldn't get windows to recognize the correct drivers, even after installing the motorola driver package, but good old linux saw it without a problem. Following these instructions I was able to do a quick SBF and now all is good in the world!
Click to expand...
Click to collapse
Can you tell me more about it please : i've made the same mistake...
I nead a real lesson !:laugh:

[Q] Cannot get PC to see Nexus (2012) is connected (Code 10) on driver. Help please!!

I have tried many options. My Nexus died shortly after a KitKat update, but it may have been frazzled by a faulty car charger.
Cannot access recovery mode.
Cannot get PC to see ADB device
Would replacing the USB board help?
Out of warranty so willing to try almost anything.

Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app

xateeq said:
Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi, I was only ever stock. Unrooted, but had USB debugging.
I sideloaded KitKat when it came out and installed the Google Experience launcher. Received an OTA a day later that was only 1-2Mb.
The sideloading worked perfectly using the adb sideload kitkat.zip.
The evening after the OTA and the unit died. It is possible that it was a car charger, but I think highly unlikely as it never affected a Kindle or Xperia Z. But now I cannot get the PC to even see that the device is connected and neither can I get Recovery Mode to fully start. I select Recovery Mode and all I see is the Google logo. I have tried all sorts of button presses to get the android on its back with the red triangle. I may have missed something obvious so any suggestions would be a help.

Connect to wall charger if u cant get it to charge then it is ok,
try changing ur data cable that ur using to connect it to pc.
if ur tablet was not connected to charger when it dies then it is not the carger. OTA usually mess things up on modified/ rooted devices.

Hi, Thanks for the response.
I've tried all my cables. I can get the unit to charge no problem. It is just that I cannot get it to recover itself.
Powering on freezes on the Google logo and the CPU overheats like a really good overheating thing.
I go into the bootloader and if it doesn't freeze I can select all the various top level options. I have tried selecting Recovery mode and I cannot get that to work either. If I select Recovery mode and hit the power button it once again freezes on the Google logo. I have tried holding the volume up and pressing the power, but nothing happens. The only option I have is to power off again.
I had hoped that the nexus Root toolkit would help, but as it is never seen or recognized by the laptop I think I am totally screwed. I am thinking that my best hope is to sell it for spares. Unless there is a way of resetting the machine without a computer or being able to access recovery mode. I haven't seen anything like this.