Related
Guys,
Details: Using Windows 7 64 bits, on a notebook.
Here is the full history of my brand new brick... call me stupid.
Second day with my Kindle Fire, I tryed to root my kindle fire.
Downloaded the KFU 0.9.5, instaled the drivers.
But the KFU wasn't workig... I only was getting the ADB offline status and the "waiting for device" message.
When I realized that the drivers I had were from my Motorola Milestone.
Next step: Uninstall the wrong drivers, and reinstall the new ones.
Only with this i could get the device to work with KFU.
Open the Run application at KFU folder.
Choosed option 2: Install Permanent Root with Superuser.
All worked fine until i get the message "with great powers come great responsabilityies" press any key to continue...
[EDIT: Tried to install Gapps extras... I don't remember if Kindle was dead before this or after]
The Kindle rebooted, got to the screen with the "kindle" word, and died.
Since that I'm getting no power on, no led lights, no response when connected to usb... nothing.
What should I do?
Go to Motorola Tech Support (here in my city) and try to use a factory cable?
or
I can only put my hopes on USB Boot Mode?
Guys, thanks in advance and sorry for my english, I certainly made some msitakes.
Or I can try Firekit?
That's strange, installing the wrong device drivers on your computer shouldn't affect your Kindle.
What it really sounds like is your battery died in the process of installing the FFF bootloader. How was your battery before you started? Have you tried holding the power button for 20 seconds for a hard shutdown?
As far as I know, the only thing that will cause power on issues is a broken bootloader. In which case, USB boot with firekit is your only option.
I guess I had at least 50% o battery charge, or more... I can't remember...
If I push the power button now, the Kindle will get warm, as if it was in use. And if I hold for 20s, will shut down...
I don't even started to install de fire fire fire bootloader, I installed the permanent root with super user and then went to install GApps. I guess my kindle was shutdown before Gapps install.
What should I do? Test the factory cable first?
When you say that I have to use Firekit, you are saying that I have to open my Kindle?
Left the Fire charging for at least 12 hours.
Tried to power on, to hold 20s and nothing happened.
I'll gonna try this:
Fix power on problems: If the Fire's screen never seems to turn on, you may have wrecked the bootloaders or the partitioning. Fortunately most of the time this results in the CPU falling into the low level USB boot mode. Use the "usb_fix_parts_and_install_fff_twrp" to rebuild the flash enough to boot TWRP. You don't need to use the USB shorting trick for this one, just power up the Kindle after running the script.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1430038
My question is: I'm running Ubuntu within VMWare tools. Can I boot from usb stick this way?
Gonna try this before I use factory cable or open my Kindle Fire.
EDIT:
Reading the FIREKIT Topic, this post: http://forum.xda-developers.com/showpost.php?p=25814062&postcount=26
My issue is kind of different from his... I'm guessing I'll have to open my Kindle anyway... Started yesterday, but I was messing with the case, gonna find some proper tools
VMs will not work. You have to create a bootable Linux LiveUSB thumb drive.
DuendePaladino said:
Left the Fire charging for at least 12 hours.
Tried to power on, to hold 20s and nothing happened.
I'll gonna try this:
http://forum.xda-developers.com/showthread.php?t=1430038
My question is: I'm running Ubuntu within VMWare tools. Can I boot from usb stick this way?
Gonna try this before I use factory cable or open my Kindle Fire.
Click to expand...
Click to collapse
If you already have a working Ubuntu installation, you don't have to make the USB stick. You can just run the fk binary in your Ubuntu setup.
kinfauns said:
If you already have a working Ubuntu installation, you don't have to make the USB stick. You can just run the fk binary in your Ubuntu setup.
Click to expand...
Click to collapse
I've tried it on a VM and had it confirmed by other users that VMs aren't fast enough to detect the USB in time. From what I've seen, it has always been suggested to either use either a straight Linux install or a bootable LiveUSB.
soupmagnet said:
I've tried it on a VM and had it confirmed by other users that VMs aren't fast enough to detect the USB in time. From what I've seen, it has always been suggested to either use either a straight Linux install or a bootable LiveUSB.
Click to expand...
Click to collapse
I guess it might depend on the VM, but I disagree with the generalization that VMs are too slow and have issues with USB.
The only thing I've seen is that Oracle's VirtualBox USB implementation breaks adb. I've never tried VMWare, but Parallels Desktop for both my Ubuntu and Windows setups work perfectly. Never had an issue.
DuendePaladino said:
What should I do? Test the factory cable first?
Click to expand...
Click to collapse
Anybody who is going to be modifying the basic software of their Kindle, or even just root it and play around, should have a factory cable. Xda member SkOrPn makes good ones at a reasonable price and ships them quickly. See http://forum.xda-developers.com/showpost.php?p=25725396&postcount=338.
(From what you wrote earlier, I presume that you don't yet have convenient access to a factory cable but would have to go out of your way to use one. If you do, in fact, have easy access to one, I can't imagine why you wouldn't try using it instead of putting a lot of effort into looking for alternatives.)
aarons510 said:
Anybody who is going to be modifying the basic software of their Kindle, or even just root it and play around, should have a factory cable. Xda member SkOrPn makes good ones at a reasonable price and ships them quickly. See http://forum.xda-developers.com/showpost.php?p=25725396&postcount=338.
(From what you wrote earlier, I presume that you don't yet have convenient access to a factory cable but would have to go out of your way to use one. If you do, in fact, have easy access to one, I can't imagine why you wouldn't try using it instead of putting a lot of effort into looking for alternatives.)
Click to expand...
Click to collapse
Without a working bootloader, a factory cable is useless.
soupmagnet said:
Without a working bootloader, a factory cable is useless.
Click to expand...
Click to collapse
All the scene leads to this... USB Boot.
About the USB stick, I was making some confusion about it.
But, I´ll gonna make one stick right now.
Guys,
I made the usb stick... just figuring how to open the kindle fire, without ruining the case.
But I guess today I'll made the short trick.
Question: I'll keep the 6.3 stock room that i tried to root? Or I'll have to download another ROM?
Is there any know issues about firekit compatibility with ubuntu 12.04?
Like this here? http://forum.xda-developers.com/showpost.php?p=25918331&postcount=10
I WON!!!!
I'M BEOWULF!!!!
Serious now...
Firekit method, with short trick... keep trying... until you find the right spot for the shor... and will work
EDIT:
THANK YOU GUYS!!!
I wouldnt be that happy without your help and your knowledge... You're the real Beowulf!
I was given a "bricked" kindle to take a look at last week. Here is the story I was given.
User installed a custom rom, but it was for a lower version (didnt fully understand this)
Afterwards it locks on the kindle fire logo during boot.
User made a factory cable to restore the unit, and now anytime ANY usb is plugged into the device it shuts off immediately.
I tried opening the device and shorting the required pins, but plugging in the usb doesnt do anything. It appears to be charged, but I have no way of knowing.
It doesnt show as anything in device manager (it looks to be fully off)
Pressing the power button still gets it to start and hang at the kindle logo.
My guess is the factory cable was made incorrectly and shorted the usb board but I figured I would see what others thought.
Thanks
Any opinions?
I had this problem a couple times. I'm not 100% sure how to resolve the problem you're having but I will tell you what I did to solve mine, so you at least have some kind of help to try and fix the issue.
When I plugged it in, my computer wouldn't recognize my Kindle but I noticed it would show a new device in the USB Controller list, showing it as a USB Composite device. I went and deleted the OEM files that are created for Android devices from c:\windows\inf\ just to make sure the next process would have better success (Mine were labeled 64, 65 and 88). Then I simply selected the composite device option for my Kindle and hit Update Driver and selected the drivers folder that came with KFUtility. Once it was detected, I used the Unbrick utility found here -> http://forum.xda-developers.com/showthread.php?t=1428428
After rebooting it worked like a charm.
I realize this may not work for you, but it is at least something worth trying because you never know.
narume said:
I had this problem a couple times. I'm not 100% sure how to resolve the problem you're having but I will tell you what I did to solve mine, so you at least have some kind of help to try and fix the issue.
When I plugged it in, my computer wouldn't recognize my Kindle but I noticed it would show a new device in the USB Controller list, showing it as a USB Composite device. I went and deleted the OEM files that are created for Android devices from c:\windows\inf\ just to make sure the next process would have better success (Mine were labeled 64, 65 and 88). Then I simply selected the composite device option for my Kindle and hit Update Driver and selected the drivers folder that came with KFUtility. Once it was detected, I used the Unbrick utility found here -> http://forum.xda-developers.com/showthread.php?t=1428428
After rebooting it worked like a charm.
I realize this may not work for you, but it is at least something worth trying because you never know.
Click to expand...
Click to collapse
Thanks for the thought, but nothing shows in device manager. I believe this is due to the kindle shutting off the second you plug any usb into it.
bump?
The shutting off thing doesn't sound inherent of a properly made factory cable the rest of it points directly to drivers IMO as far as your device not being recognized I can show you how to rule out the driver issue out of the equation lemme know
Thepooch said:
The shutting off thing doesn't sound inherent of a properly made factory cable the rest of it points directly to drivers IMO as far as your device not being recognized I can show you how to rule out the driver issue out of the equation lemme know
Click to expand...
Click to collapse
I'll definitely try the factory cable again (the user tried this, but who knows)
But as far as the device not being recognized... Like I said, the second you plug it into usb (either computer, or power plug) it shuts off.
Its not that I get a windows notification for "not recognized" windows doesnt see it period.
it should not turn your device off it should appear stuck at the logo like I said sounds like a bad build guess you misunderstood
---------- Post added at 06:45 PM ---------- Previous post was at 06:38 PM ----------
only use a 2.0 usb port and try it from the device in an off position
If this is the wrong forum, please move as needed and I apologize.
I recently purchased (2) refurb'd 1st-gen Fire's with the intent of loading CM10.1 on them. I don't know what version was on the first one, but the second has 6.3.1 on it.
I downloaded KFU 0.9.9, the CM zip, the gapps zip, and after some playing around, was able to make it all work on the first Kindle, via a Win7 laptop.
When I plugged the second Kindle in (same laptop, same USB cable,) it was not recognized. I then plugged the first, now-flashed one back in, and it wasn't recognized, either (within KFU.) I checked the device manager, and the Kindle had the yellow triangle of doom attached to it, but it at least showed up. I again plugged the second unit in, and not only is it not recognized by KFU, it's not being recognized as a connected device within the device manager at all. I can't view files on it, nothing.
I then tried installing KFU on a second laptop, and got the same scenario again. I tried downloading a different KFU utility, no luck in either case.
Am I doing something completely wrong here? I just want to get CM on this second Kindle, and nothing at all seems to be working now, after the first one seemed to go pretty smoothly.
Thanks
SlightlyOpaque said:
If this is the wrong forum, please move as needed and I apologize.
I recently purchased (2) refurb'd 1st-gen Fire's with the intent of loading CM10.1 on them. I don't know what version was on the first one, but the second has 6.3.1 on it.
I downloaded KFU 0.9.9, the CM zip, the gapps zip, and after some playing around, was able to make it all work on the first Kindle, via a Win7 laptop.
When I plugged the second Kindle in (same laptop, same USB cable,) it was not recognized. I then plugged the first, now-flashed one back in, and it wasn't recognized, either (within KFU.) I checked the device manager, and the Kindle had the yellow triangle of doom attached to it, but it at least showed up. I again plugged the second unit in, and not only is it not recognized by KFU, it's not being recognized as a connected device within the device manager at all. I can't view files on it, nothing.
I then tried installing KFU on a second laptop, and got the same scenario again. I tried downloading a different KFU utility, no luck in either case.
Am I doing something completely wrong here? I just want to get CM on this second Kindle, and nothing at all seems to be working now, after the first one seemed to go pretty smoothly.
Thanks
Click to expand...
Click to collapse
Try re-installing the driver
Guitarman2010 said:
Try re-installing the driver
Click to expand...
Click to collapse
Sorry, forgot that in the OP.
I reinstalled the drivers using install_drivers.bat several times (each time it says successful.) I also uninstalled the "working" device (Kindle 1) from Device Manager and then installed the drivers afterward. No change.
I called Amazon support earlier this evening, and (but of course) the device is out of warranty. They recommended that I called the company that I purchased them from (Best Buy,) but the 15-day return window has passed so I'm assuming they'll tell me to pound sand.
On the call, I did ask whether or not there was a newer system version available (this is on 6.3.1_user_4107920) and was told that there is a newer version, and to let it sleep for 2 hours without interruption and it would find it. Several hours later, it's listing as no updates available. I thought that maybe if there were a system issue, an update would overwrite the problem and I'd actually be able to see the device in some way. So, with no cable and no auto-update, I manually installed the .bin (via Amazon's updates page, but I don't have enough posts for external links) and ran it successfully. The device was updated to 6.3.2_user_4110520, but is still not recognized in any way, beyond the fact that it charges, as indicated by the battery icon.
I'm going to stop by Best Buy tomorrow, but I don't imagine they're going to try and help me out.
The idea of the USB port being bad crossed my mind, but because it was charging I disregarded it. After running out of realistic ideas, I finally compared the two USB ports. The flashed, working unit has a pristine-looking port, while the problematic one looks mangled. I tried to ever so gently straighten and isolate the pins, but the connection may be severed at the base where I can't see it.
I'm fairly sure this is the problem. After doing this, and holding the cable just so, I was able to get the device manager to update, although not what I wanted. When it updated, and recognized the Kindle to some degree, it actually dropped connection to my mouse. When I let the cable go from where I was holding it, the device manager recognized my mouse again.
So, yea, I guess a trip to Best Buy is in order.
SlightlyOpaque said:
The idea of the USB port being bad crossed my mind, but because it was charging I disregarded it. After running out of realistic ideas, I finally compared the two USB ports. The flashed, working unit has a pristine-looking port, while the problematic one looks mangled. I tried to ever so gently straighten and isolate the pins, but the connection may be severed at the base where I can't see it.
I'm fairly sure this is the problem. After doing this, and holding the cable just so, I was able to get the device manager to update, although not what I wanted. When it updated, and recognized the Kindle to some degree, it actually dropped connection to my mouse. When I let the cable go from where I was holding it, the device manager recognized my mouse again.
So, yea, I guess a trip to Best Buy is in order.
Click to expand...
Click to collapse
So... you think the USB port on the tablet is bad? Or you think the USB port on the PC is bad?
I'm having a very similar problem with trying to root a second KF. First one rooted just fine. Installled CM10, gapps, the works. Go to try and do the same thing, and it won't work.
I also tried it on another PC, and it didn't work on that one either. That other PC however is an old server PC that I forced Windows 7 on, and it has some major issues, so not really a reliable PC.
Now the PC I'm on is too old, I'm gonna need to take Windows 7 off of it. A recent update rendered my PS/2 ports obsolete, and I'm not PC-literate enough to know how to roll back a KB file. Linux it is.
...speaking of; have you tried connecting the KF/rooting it via Linux? I have a bookmark for that somewhere. Lemme see if I can find it... or link you to it:
http://forum.xda-developers.com/showthread.php?t=1568340
Have you seen that thread?
The drivers that come with KFU always caused me problems to no end. I would suggest you uninstall them and install the Windows 8 drivers I supplied
http://forum.xda-developers.com/showthread.php?t=2185402
Sometimes (don't know why), you need to mount your Kindle for it to be detected. If you've booted in recovery, mount the usb drive. If you're loaded inside the ROM, turn on debugging.
need these drivers, site doesnt redirect properly
Socially Uncensored said:
The drivers that come with KFU always caused me problems to no end. I would suggest you uninstall them and install the Windows 8 drivers I supplied
http://forum.xda-developers.com/showthread.php?t=2185402
Sometimes (don't know why), you need to mount your Kindle for it to be detected. If you've booted in recovery, mount the usb drive. If you're loaded inside the ROM, turn on debugging.
Click to expand...
Click to collapse
ok guys I have a unmodded 1st generation kindle fire here
it works fine except it does not recognize on my pc at all.
the usb charges the battery and all but I can not load files to or off my kindle via usb
it does not show up at all in my
windows 7 64 bit OS
any help would be great
The same thing happened with to me. I just switched the usb port on my pc that the cable was plugged into, and it worked.
Sent from my Amazon Kindle Fire using xda app-developers app
if only..............
BillBill17 said:
The same thing happened with to me. I just switched the usb port on my pc that the cable was plugged into, and it worked.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
wish that it was that simple
but alas I have tried different cables, pc's ports it even cuts off when its on the charger
and according to amazon, on the charger it should power on and it won't
so thanks for the input
am stuck side loading for now, amazon has offered a trade in amount for it, but honestly
this close to Christmas, there is no money for it, hope they honor it after the new year
kindlefire not seen by computer FIX
I have 8 different Kindle Fire devices for my family. I tried to hook my daughter's best friend's Kindle to my computer so I could books on hers through Calibre. My computer couldn't see her Kindle. I tried different ports. Nothing. It could see all the other Kindle devices just fine (HD and non-HD alike) - just not hers (a second generation Kindle). I dug for hours trying to figure it out. At last I stumbled upon a post that helped. This is what I did and my computer sees it fine and Calibre is working beautifully with it.
Systems I used:
Windows 7 Home Premium SP 1
KindleFire Gen 2 System Version: 10.5.0_user_5060020
DISCLAIMER: Messing with device drivers is NOT for the unexperienced user, and can much mess up your computer beyond the point that the same user can repair it. I cannot take responsibility nor offer help if things go wrong beyond your capability to repair it.
Connect your kindle (as normal- you don't need to slide to unlock or anything... just connect it)
Open your Device Manager: Click Start -> (search) Device Manager
If your device was not recognized, a device with a yellow exclamation mark will be listed under Other devices. Mine was just listed as "mtp".
It stated that there were driver issues including an MTP issue.
To set your Kindle as a Kindle portable device, do this:
Right-click the device in the Device Manager and select Uninstall. This removes the current driver, and provided you disabled automatic driver installation, will leave it as a unrecognized device with the yellow exclamation mark icon under Other devices. You may have to unplug and replug the Kindle after you uninstall it in order to see it listed under the "Other devices".
Right-click the device again and select Update Driver Software ->Browse my computer for driver software -> Let me pick from a list of device drivers on my computer.
You should now have a large list of common hardware types. Here, scroll down and select portable devices -> Standard mtp device -> mtp USB device under the Disk drive.
You will be prompted to confirm this selection, click Yes. The Kindle will now be recognized as a portable device listed as "Kindle" by your computer.
Calibre sees it fine. It is now listed under my "My Computer" as a portable device sublisted as a Kindle.
Doing this did NOT change how my computer saw my KindleFire HD 8.9. It did not change anything EXCEPT the particular Kindle that would not be seen previously. I hope this helps some others who are lost figure out theirs as well.
cougarkittyn said:
I have 8 different Kindle Fire devices for my family. I tried to hook my daughter's best friend's Kindle to my computer so I could books on hers through Calibre. My computer couldn't see her Kindle. I tried different ports. Nothing. It could see all the other Kindle devices just fine (HD and non-HD alike) - just not hers (a second generation Kindle). I dug for hours trying to figure it out. At last I stumbled upon a post that helped. This is what I did and my computer sees it fine and Calibre is working beautifully with it.
Systems I used:
Windows 7 Home Premium SP 1
KindleFire Gen 2 System Version: 10.5.0_user_5060020
DISCLAIMER: Messing with device drivers is NOT for the unexperienced user, and can much mess up your computer beyond the point that the same user can repair it. I cannot take responsibility nor offer help if things go wrong beyond your capability to repair it.
Connect your kindle (as normal- you don't need to slide to unlock or anything... just connect it)
Open your Device Manager: Click Start -> (search) Device Manager
If your device was not recognized, a device with a yellow exclamation mark will be listed under Other devices. Mine was just listed as "mtp".
It stated that there were driver issues including an MTP issue.
To set your Kindle as a Kindle portable device, do this:
Right-click the device in the Device Manager and select Uninstall. This removes the current driver, and provided you disabled automatic driver installation, will leave it as a unrecognized device with the yellow exclamation mark icon under Other devices. You may have to unplug and replug the Kindle after you uninstall it in order to see it listed under the "Other devices".
Right-click the device again and select Update Driver Software ->Browse my computer for driver software -> Let me pick from a list of device drivers on my computer.
You should now have a large list of common hardware types. Here, scroll down and select portable devices -> Standard mtp device -> mtp USB device under the Disk drive.
You will be prompted to confirm this selection, click Yes. The Kindle will now be recognized as a portable device listed as "Kindle" by your computer.
Calibre sees it fine. It is now listed under my "My Computer" as a portable device sublisted as a Kindle.
Doing this did NOT change how my computer saw my KindleFire HD 8.9. It did not change anything EXCEPT the particular Kindle that would not be seen previously. I hope this helps some others who are lost figure out theirs as well.
Click to expand...
Click to collapse
This is a thread for the first gen kindle fire, you may get better help in the 2nd gen Q and A section
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
Start here http://forum.xda-developers.com/showthread.php?t=2228539
Frequently Asked Questions - 2nd Generation Kindle Fires
I installed COTR (Cannibal Open Touch Recovery), and tried to install a KitKat ROM. It didn't work, and my android installation was removed.
I had backed up the system using TWRP, but now it has been replaced with COTR, and I don't have a working zip on my kindle to flash.
I tried to connect using adb, but I'm not sure how (I'm on a mac), and trying to mount the sd card using COTR doesn't seem to work either.
I'd really like to fix this because it's my main device and I rely on it
jji7skyline said:
I installed COTR (Cannibal Open Touch Recovery), and tried to install a KitKat ROM. It didn't work, and my android installation was removed.
I had backed up the system using TWRP, but now it has been replaced with COTR, and I don't have a working zip on my kindle to flash.
I tried to connect using adb, but I'm not sure how (I'm on a mac), and trying to mount the sd card using COTR doesn't seem to work either.
I'd really like to fix this because it's my main device and I rely on it
Click to expand...
Click to collapse
The quick and painless fix here would be soupkit. If you follow the instructions it's quite simple. If you can't use soupkit for whatever reason look for a tutorial on adb with Mac. I don't own a Mac myself so I can't be much help in that department.
When I connect my kindle to my Mac it doesn't appear at all, even when I mount as USB mass storage using recovery, and adb/fastboot doesn't detect it either, so I suspect that my usb connection may only work for charging, and not for data. I've had problems with the usb port before as well, and I wasn't able to mount my kindle before the brick either (though I presumed it was a jelly bean bug).
Therefore I think my kindle is a hard brick with no solution.
Ok I pronounce my kindle dead. It was a good run, didn't expect it to end so abruptly
I might sell it for parts or something later.
Sad... Kikat does not work with cotr
I was using cotr
Twrp 2.6.0.0 was not able to make a backup, now that thing is fixed, so I came back to twrp for kitkat
Sent from my air powered ceiling fan
jji7skyline said:
When I connect my kindle to my Mac it doesn't appear at all, even when I mount as USB mass storage using recovery, and adb/fastboot doesn't detect it either, so I suspect that my usb connection may only work for charging, and not for data. I've had problems with the usb port before as well, and I wasn't able to mount my kindle before the brick either (though I presumed it was a jelly bean bug).
Therefore I think my kindle is a hard brick with no solution.
Click to expand...
Click to collapse
You could use the USB shorting trick coupled with the advice I already posted and you'd very likely fix your Kindle. The USB trick skips all the driver BS and listens directly to the USB before the OS or boot even has a chance to do anything.
Keep in mind it can take many, many tries to actually do the USB trick right. The first time I did the USB trick it took 20 tries or more, others have had the same problem. Some people say a strong piece of copper wire works best, but I didn't have one on hand.
Firekit is built in with Soupkit (which I already posted).
http://forum.xda-developers.com/showthread.php?t=1405052
8) Short the point shown here to the metal frame around the CPU area using your paperclip or whatever. While keeping it shorted, plug in the USB cable. This will power up the Fire with the CPU in USB boot mode.
I'm 99% sure you can fix your Kindle like that. Ask if you need anything clarified.
So just get Soupkit set up, get it into Firekit and order "usb_fix_parts_and_install_fff_twrp". It will say <waiting for device>, at this point you do the USB trick again and again until it works. It absolutely should work, keep trying.
The problem is that i think the usb is broken and only works for charging - no data.
Ill give it a go anyway though. Thanks.
Sent from Google Glass
So I was trying to change my son's Fire 2 over to the new Kit Kat OS, and as I was downloading the necessary files to my computer, I thought I would wipe everything, since he had managed to pretty much fill it with junk, (he's 8). I have TWRP, (2.3.3.0) installed, and used that to wipe everything, including the internal storage and the format data wipe. I have done this with my Fire 1 with no issues, but this time I ran into a problem. TWRP works fine, but now windows won't recognize the tablet. When I go to mount the usb storage to copy the os files over, windows 7 cant load the device drives, and in my device manager it shows the Amazon Kindle fire 2 with the yellow exclamation mark next to it, saying that the drivers for this device are not installed. I have the SDK installed, and I have gone through and re installed the device drivers several times, and also uninstalled the kindle from the device list in manager. Nothing is working. I have attempted fastboot, but when I do try, it gets stuck at the "press the button menu" for TWRP, and after running the fastboot -i 0x1949 getvar product command, it tells me it sees an Otter2-Prod-04.
Does anybody have any ideas or suggestions on how I can get into the usb storage so I can load the OS info? Thanks for any help.
Dead?
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
xanthian23 said:
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
Click to expand...
Click to collapse
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
mindmajick said:
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
Click to expand...
Click to collapse
I have the standard cheap Kf2, no HD, just the upgrade from the first from last year, (2012), they were selling around Christmas last year. I have tried getting it to start back up, but with no success. I don't even understand why it shut down like that. I hadn't done anything to it other than reboot, which I had done successfully several times before. As for the fastboot, I may be incorrect. I ran the adb command: fastboot -i 0x1949 getvar product in CMD, and then plugged the kindle in and booted up. It showed it was an otter4 or something like that, which I thought meant it was in fastboot. At that time I was using my S4 usb cable. I'm sure I can sort out ho to sideload a rom via adb if I can ever get it started back up again. I had thought about opening it up and unplugging the battery and then re-plugging it back it to try to reset it, but I doubt it will help. Would getting a fastboot cable possibly make it start back up? If anyone has any suggestions on how I can get this thing started up again I would greatly appreciate it. I fell like crap for bricking my kids kindle, he's 8, so it's really important to him. It'll take me several months to save up to buy another one, so if I can get it running again, that would be awesome.
Here's a bit of an oddity, and maybe this spells some hope for me yet. So I plug the KF2 into the computer with the factory cable, hold down the power button for twenty seconds, let go, and then hit the power button again, for about a second, and windows makes the usb device plugged in sound, followed by a usb rejected or not recognized sound. It repeats this over and over for about thirty seconds or so and then stops. So there is something going on with the kindle, and its not flat out dead, or at least it seems. Is this a good sign? Does this help anyone to figure out what I might need to do?
So just to be sure that I was using a fastboot cable, even though I believe that my samsung s4 cable is fastboot capable, and I'm pretty sure I am using the factory cable, (it's not marked so I can't be 100% sure), I built my own fastboot cable, via instructions on how to do so on xda. (found HERE) It's doing the same thing with windows making the usb device inserted / recognized sound, followed by the usb device error sound. I'm guessing that this is a bad thing, am I correct?
One more bit of information to add to the list. I attempted to do the fastboot mode again,and decided to watch my device manager. Whenever windows chimes off that it detects a usb device, something called OMAP 4430 pops up for about a second before disappearing when the error sound comes on. I'm going to try and get a driver for that, just to see what happens. Maybe it'll help. I doubt it, but you never know until you try...
This just keeps getting weirder and weirder. So I installed the omap driver for windows and android, and now windows recognizes the device, but only for about a second. It just keeps cycling through the usb connected sound, recognizing the omap device, and then the usb disconnected sound, as though the device were being plugged in and then unplugged about every second for roughly thirty seconds. I'm starting to think there is something seriously wrong, which bites. If anyone has any suggestions, I'm all ears.
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
OK, I have both a tf - micro sd card usb card reader, and a full sd card usb card reader. I'll have to go digging for them in the morning, but I think I can find them. I'm also really good with a soldering iron, (used to be a vcr / tv repair technician), It took me roughly two minutes to do the homemade factory cable. So I am game, especially since at this point I really have nothing to loose by trying. Would you mind posting a link to where the tutorial is? I'm going to go looking for it, but just in case I can't find it, a link would help. And thank you so much for this suggestion!
OK, I found the tutorial on how to wire everything up and what's needed. I'll have to go get some small wire and a better tip for my iron, but aside form that, the wiring and soldering seems simple enough. My problem is going to be dealing with linux. I know Windows backwards and forwards, but I have a pretty limited knowledge of linux, aside from a few things we did in school to cover general PC repair. I can get it up an running, which I will do tomorrow, but I may need some help sorting out what to do with it once I have the board lined up and ready to roll, which will have to wait till next week when I get back from a work trip. Do you know if kurohyou offers repairs? If it's not too expensive, I would be willing to pay for the fix.
He might repair it, he just made a solderless repair tool to repair them. But like I said I'm more than willing to help with the Linux side, I'm a PC tech myself and use Linux primarily, you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
... you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Click to expand...
Click to collapse
Yeah, I've ran a live usb version of unbuntu a few times, and in the past I have had the full version on my system, but I rarely ever used it, so I got rid of it. I have an extra 600 gig's of space just sitting around on my laptop, so I will install a full version, and get off my lazy rear and start learning linux. This should be a good first lesson. I can't do any of this until next week though, so I will be pm'ing you once I've gotten everythig hooked up and ready to go. Thanks again for the help.
I had a question about the repair though. I went through the discussion, and I may have just missed it, but did he ever figure out how to get the OS up and running? From what I could tell, he was still working on it, and hadn't managed to get a working rom loaded. I probably just either missed it, or didn't understand one of the post's.