Just like the title says. At first when I plugged my Kindle Fire in it showed up as the processor name. I installed the drivers by just using that hoping to get some sort of PC connection.
Im on Windows.
TWRP was messed up and wouldnt boot for me. (when screen worked.)
Had ICS beta. (When screenworked)
Would like to get back to stock.
Could anyone help me out?
maybe out of battery ? charge for an hour with the wall plug (pc loads very slowly)
some more information would be helpful:
what exactly have you done ?
os/bit of your computer ?
do you have newest kfu available ?
if yes please move and rename to c:\kfu (win7 64bit drivers will not install with spaces and it's easier to help cause in the tools folder are all necessary commands)
b63 said:
maybe out of battery ? charge for an hour with the wall plug (pc loads very slowly)
some more information would be helpful:
what exactly have you done ?
os/bit of your computer ?
do you have newest kfu available ?
if yes please move and rename to c:\kfu (win7 64bit drivers will not install with spaces and it's easier to help cause in the tools folder are all necessary commands)
Click to expand...
Click to collapse
Usually it charged through the USB port on my computer but currently I put it on the wall charger to see if that would be the problem.
Well the history is this: Rooted 6.2.1, installed ICS, but after messing with TWRP my Kindle Fire arrived at a point where ICS was the ONLY OS, no backup available and TWRP being stuck at the logo not proceeding. I used the KFU to try to install a new TWRP on it but I think that might of messed it up. Im not sure to be honest theres been a lot done on this and its been a week til I had time to resolve my issue.
Windows 7 64bit
EDIT: Btw the green light from the power button never comes on. Ill plug the device in and nothing will happen until I hold the power button down for a while.
It shows up in the device manager, but only for a second to be disconnected, then the cycle repeats constantly.
Bricked to hell....I got a chuckle out of that.... Good luck man, hope you can get it fixed.
Sent from my Kindle Fire using xda premium
Okay. So at this point you are unable to power the device on? Even after charging it off of the wall port? (PC charging my android devices never personally worked for me)
Also have you loaded a custom kernel on? And have you checked if ADB can recognise the device?
Sent from my Kindle Fire using xda premium
Ok, all you have to do if twrp is messed up is to reflash it in fastboot. You can never Really brick a device.... See if you have adb.
http://forum.xda-developers.com/showpost.php?p=21715022&postcount=9
Zomboogz said:
Okay. So at this point you are unable to power the device on? Even after charging it off of the wall port? (PC charging my android devices never personally worked for me)
Also have you loaded a custom kernel on? And have you checked if ADB can recognise the device?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Well I know its on cause how would the PC be able to recognize it? It keeps going on and off so I cant time it correctly or its just too fast I cant tell.
b63 said:
http://forum.xda-developers.com/showpost.php?p=21715022&postcount=9
Click to expand...
Click to collapse
Im going out to dinner but I will try that and let you know how it works after
Related
Hey All,
So my kindle fire was chugging along just fine and it showed up in Windows device manager, mounted as a drive etc. I ran the 'Kindle Fire Utility' v3 and used zergrush - no problem. Then I selected 'Install latest TWRP'. It did something, rebooted, then it all went tits up.
Now when I turn on my kindle fire, I'm stuck on the logo. It doesn't show up in device manager and I've spent about 2 hours trying just about every adb/fastboot command I can find.
Obviously none of them are working because they just say device not found or sit on 'waiting for device' forever.
Anyone got any ideas at all what I could do? I've only had the bloomin' thing for about 2 weeks and I think I've really bodged it up!
I've read through every related post I could find and none of them seemed to match my conditions and none of the commands have done the job.
Fingers crossed! Cheers
UPDATE: I finally managed to fix this by booting from a live Ubuntu disc where the kindle was found over usb and I was able to use fastboot.
philstuffs said:
Hey All,
So my kindle fire was chugging along just fine and it showed up in Windows device manager, mounted as a drive etc. I ran the 'Kindle Fire Utility' v3 and used zergrush - no problem. Then I selected 'Install latest TWRP'. It did something, rebooted, then it all went tits up.
Now when I turn on my kindle fire, I'm stuck on the logo. It doesn't show up in device manager and I've spent about 2 hours trying just about every adb/fastboot command I can find.
Obviously none of them are working because they just say device not found or sit on 'waiting for device' forever.
Anyone got any ideas at all what I could do? I've only had the bloomin' thing for about 2 weeks and I think I've really bodged it up!
I've read through every related post I could find and none of them seemed to match my conditions and none of the commands have done the job.
Fingers crossed! Cheers
Click to expand...
Click to collapse
There is several threads about this use the search
Actually I think the answer to your problem is contained in the thread where you downloaded the tool.
Hiya,
I appreciate the reply but I think you're wrong. There are similar issues but I haven't yet seen any that are exactly the same.
You *think* there's a solution in that thread? or you know? Because I've looked through it and several others over the last couple hours and I'm still not making any progress.
Like any forum you're quick to jump on the bandwagon and scream 'use the search'. I'm active on other forums and I get the reasoning behind it. But I think you've jumped the gun in this case.
Cheers
others have reported the same behavior with version 3 of the tool.
they recovered by downloading version 1 or 2 and use the usb driver
from one of theese versions.
have not tried it, just read it today ...
Thanks for the heads up b63. I saw the same earlier and tried v2 but not yet v1. The reason being that although the drivers are bundled, I can't (that I know of) install them without the device at least showing in the device manager..
Cheers
philstuffs said:
Now when I turn on my kindle fire, I'm stuck on the logo. It doesn't show up in device manager ...
Click to expand...
Click to collapse
From this I read "doesn't make the USB Connected noise when you plug it in". I don't imagine that different drivers will make much difference. Have you seen the post on how to make a factory USB cable?
http://forum.xda-developers.com/showthread.php?t=1392693
philstuffs said:
Thanks for the heads up b63. I saw the same earlier and tried v2 but not yet v1. The reason being that although the drivers are bundled, I can't (that I know of) install them without the device at least showing in the device manager..
Cheers
Click to expand...
Click to collapse
Here's what you need to do to fix that:
Go to device manager
Right click the device. It will be Android USB Composite Device or just kindle
Click uninstall
Disconnect the kindle and reboot the computer
When the computer is back up, turn on the kindle and plug it in
It will fail to install the driver. So, go back to device manager
Right click kindle
Click update driver
Click let me choose...
Click let me pick the driver...
Click have disk
Point the file browser to C:\Program Files (x86)\Android\android-sdk\extras\google\usb-driver\android_winusb.inf and click ok.
Choose Android USB Device when prompted
Click install anyway if prompted
The driver should have installed properly now
open Kindle utility
Choose factory reset
Unplug kindle
Boot kindle
Have fun!!!
daveoggy,
That's right, no ding dong. Although if I turn the kindle fire on and plug the usb cable in immediately (have it sitting ready to push into the fire) then the device manager does refresh after about 5 seconds, as if something was connected. Although no new device is shown.
I'll look into the factory cable, thanks for that.
does the usb connection make a noise - thats the right question !
if jes then ist a driver problem - there is something wrong with the driver from v3
if it makes the typical noise then a factory cable is like shooting with a cannon on flys
jlocohustler said:
Here's what you need to do to fix that:
Go to device manager
Right click the device. It will be Android USB Composite Device or just kindle
Click uninstall
Disconnect the kindle and reboot the computer
When the computer is back up, turn on the kindle and plug it in
It will fail to install the driver. So, go back to device manager
Right click kindle
Click update driver
Click let me choose...
Click let me pick the driver...
Click have disk
Point the file browser to C:\Program Files (x86)\Android\android-sdk\extras\google\usb-driver\android_winusb.inf and click ok.
Choose Android USB Device when prompted
Click install anyway if prompted
The driver should have installed properly now
open Kindle utility
Choose factory reset
Unplug kindle
Boot kindle
Have fun!!!
Click to expand...
Click to collapse
Thanks but remember I said it's not showing up in device manager?
b63 said:
if it makes the typical noise then a factory cable is like shooting with a cannon on flys
Click to expand...
Click to collapse
... is the right metaphor
to uninstall a device you don't see:
http://support.microsoft.com/kb/315539/en-us
b63 said:
to uninstall a device you don't see:
http://support.microsoft.com/kb/315539/en-us
Click to expand...
Click to collapse
Good man. Uninstalled and rebooting now. It's been a long time since I've used Windows.
Will update shortly.
Cheers
Try completely powering the device down. IE holding power for 20+ seconds. Give it a minute, then turn it back on with it plugged in.
DO you hear it dinging over and over for like 10 seconds?
I was able to uninstall the device by following b63's advice on items not listed in device manager.
I then rebooted and connected the kindle. It came up with the new hardware alert in my taskbar but that then disappeared and no new hardware is being shown in the device manager. There was no ding ding at any time.
Vashypooh, I held the power button for 20 seconds, the kindle fire turned off. I then booted it back up about a minute or two later. Still no ding.
*sigh*
You say you are stuck on a logo on the Fire which logo?
Sent from my Kindle Fire using Tapatalk
The logo is static. No animation.
philstuffs said:
The logo is static. No animation.
Click to expand...
Click to collapse
I meant what does it look like
Sent from my Kindle Fire using Tapatalk
which logo ?
"kindle fire" static or yellow triangle ?
It says 'kindle fire' in static text
Kindle in white
Fire in gold
No other icons/logos on the screen.
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.
I was trying to root my Kindle Fire and now it wont restart and my PC does not recognise it. Ive looked at other threads but they keep suggesting using fastboot which i cant do because its not seen.
The procedure i was following is here
http://forum.xda-developers.com/showthread.php?p=24129239
I had flashed the bootloader and recovery but it seemed to stick on the Kindle screen. I then turned it off but now there are no lights on and it wont restart.
I tried to plug it into the wall socket to charge and also my laptop to see if it would recognise it again.
I have checked device manager and it cant see the Fire device.
Help :crying:
I have left the Kindle on charge all day long but it still isnt being recognised on my laptop and the power button is doing nothing.
Has anyone else had this before or something similar.
Ive tried all the fastboot commands but it just says waiting for device.
Ive also tried adb commands but the device can not be seen.
If its not already too late, what you need to do is access device manager
-Start
-Control Panel
-Hardware and devices
-Device manager
From here, find a driver called adb composite device, or something similar. Delete all of these drivers.
Now go into kfu, and reinstall drivers using install_drivers.bat
Or however you installed your drivers if it was manual.
Now try again. If it doesnt work, tell me, ill see what else i can think of
Sent from my Kindle Fire using XDA
pokey's firekit
Sent from my Galaxy Nexus using xda premium
Nothing i do will give me access to the Fire so i called Amazon and there sending me a replacement.
andyloftus said:
Nothing i do will give me access to the Fire so i called Amazon and there sending me a replacement.
Click to expand...
Click to collapse
If you get to keep your old one ill buy it off you
Sent from my MB865 using Tapatalk 2
I will be sending the Fire back but if i cant access it and it isnt recognised on my laptop it makes me wonder what you would do with it if i could sell it to you.
andyloftus said:
I will be sending the Fire back but if i cant access it and it isnt recognised on my laptop it makes me wonder what you would do with it if i could sell it to you.
Click to expand...
Click to collapse
Parts
Sent from a thingymajig that sends things.
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
herghost said:
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
Click to expand...
Click to collapse
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
jombo2323 said:
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
Click to expand...
Click to collapse
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
herghost said:
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
Click to expand...
Click to collapse
you are 100% positive you did EXACTLY what i said?
I have no idea what went wrong
That's the problem with toolkits though. People don't know what they're doing and when something goes wrong you don't know how to fix it!! I understand where toolkits come from, but they are only useful if you know what happens in the background when you click on a button.
Thread Moved
Thread belongs in Q&A. Not the Dev Forum
Post moved.
MD
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
erica_renee said:
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
Click to expand...
Click to collapse
You Star
Put me on the right track, my PC was basically assuming that it was my S3, in the end I removed everything with samsung in it from the registry, uninstalled all the drivers then tried again, correctly showing as a nexus and not a samsung
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.