Develop Bugs

[Q] Kindle Fire bricked for good?

Alright, So I've been through a copious amount web surfing and self pondering. Attempted to "unbrick" my Kindle Fire several times and nothing seems to work. I've read so many threads on trying to fix it and I can't come up with a solution to my problem. Out of despair and fear of having to discard my kindle I joined this site in hopes that you guys could help me out. So here's my problem;
I rooted my kindle using TWRP 2.0 and followed all instructions. It turned out flawless and I was able to turn my amazon kindle into an "android device" aka change the OS on the kindle. At first I had it running ICS and that worked out great. I got bored of it, reformatted and changed the OS to AOKP. Fell quickly in and out of love. Eventually I wanted to see if my kindle was capable of being "unrooted". Obviously it failed and now I'm stuck at original kindle fire boot logo with no TWRP or anything. I think somehow I may have screwed up the files in my kindle to make it unresponsive. Fixes I've tried using to no avail;
KFU - Device Not Found (However my computer recognizes it as Android ADB Interface or whatever)
KF Unbrick Utility - Same problem (Device not found)
Re installing Usb Drivers repetitively isn't working. (Even editing the adb_*****.ini in notepad isnt working.)
Turning the kindle fire on and off (I read somewhere that this was a potential fix)
Fully charging my kindle fire (even though I can't see the percentage) and switching out the usb cable to a factory one (still not working)
Also, whenever I double click my kindle device from my computer the following message appears "Please insert disk into drive D:"
Sorry if all this is an eye sore but as you can tell I'm exerting all my options! Any advice on this would be very much appreciated seeing as how you will have saved my device from the trash can. I'm really not that tech savvy so you might have to answer in detail. One last thought, I was wondering if it is possible to maybe use something like daemon tools to mount an ISO image onto the kindle or if anything like that is even possible. I'm STUCK T-T

Try firekit http://forum.xda-developers.com/showthread.php?t=1430038 pm me sometime if you cant get it setup and I will help you via teamviewer
---------- Post added at 10:51 PM ---------- Previous post was at 10:49 PM ----------
Download linux mint mate 13 32 bit and pendrive we'll get ya rollin
---------- Post added at 10:58 PM ---------- Previous post was at 10:51 PM ----------
In fact its very likely that its just a matter of fastboot flashing fff.bin and twrp with your factory cable flash a rom and gapps and your fixed

Thepooch said:
Try firekit http://forum.xda-developers.com/showthread.php?t=1430038 pm me sometime if you cant get it setup and I will help you via teamviewer
---------- Post added at 10:51 PM ---------- Previous post was at 10:49 PM ----------
Download linux mint mate 13 32 bit and pendrive we'll get ya rollin
---------- Post added at 10:58 PM ---------- Previous post was at 10:51 PM ----------
In fact its very likely that its just a matter of fastboot flashing fff.bin and twrp with your factory cable flash a rom and gapps and your fixed
Click to expand...
Click to collapse
I must admit, I'm a little confused about the last thing you said. What's the fff.bin file and how can I mount anything onto my device when none of the utilities are picking it up? My computer reads it as any other normal device with the exception that whenever I double click to view files, it says I have to insert a drive.

I had issues with me being stock in Fastboot, is it possible you're stuck in Fastboot?
Open KFU, and go into bootmode menu, and hit the option for normal, then reboot the kindle (don't exit out of KFU) and when it starts up, it should detect it (Windows will normally make a sound of the device connecting) and it'll send the command.
My KFU has never once "detected" my Kindle. But, I've been able to do loads with KFU regardless, as if it were detected. Just doesn't say it is.
Give it a shot.

[Q] TWA'a CM10/JB USB not detected/mounting

I just got into flashing my KF (noob, I know) and everything went smoothly except for this. I like the CM10 ROM that TWA put out and according to posts in that thread USB mounting works fine, but it doesn't for me. The PC and KF don't recognize that they are connected with a USB at all. There is no notifications on either end. This worked fine before I flashed. And I changed ROMs to Hashcodes JB AOSP ROM and USB notification and mounting worked fine there. I then flashed back to the CM10 and still no love.
So how can I debug this? What settings should I check? Are there an apps out there that will let me get more info about my setup to see if something is screwy regard USB. Any helpful tips would be appreciated.
I have tried a couple tips I found in the CM10 thread, but they didn't help. (specifically switching to Hashcodes ROM and back again)

SenorSmartyPants said:
I just got into flashing my KF (noob, I know) and everything went smoothly except for this. I like the CM10 ROM that TWA put out and according to posts in that thread USB mounting works fine, but it doesn't for me. The PC and KF don't recognize that they are connected with a USB at all. There is no notifications on either end. This worked fine before I flashed. And I changed ROMs to Hashcodes JB AOSP ROM and USB notification and mounting worked fine there. I then flashed back to the CM10 and still no love.
So how can I debug this? What settings should I check? Are there an apps out there that will let me get more info about my setup to see if something is screwy regard USB. Any helpful tips would be appreciated.
I have tried a couple tips I found in the CM10 thread, but they didn't help. (specifically switching to Hashcodes ROM and back again)
Click to expand...
Click to collapse
which one did you try ? go to developer option and make sure there is a check in android debugging
---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------
Thepooch said:
which one did you try ? go to developer option and make sure there is a check in android debugging and no check in protect usb storage
Click to expand...
Click to collapse
give that a try
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
also did you wipe? wipe factory reset wipe cache wipe dalvik wipe system flash rom flash gapps reboot

Debugging was turned off. I turned it back on, rebooted and that did the trip.
Many thanks.
I think I will do a full wipe (was just doing the cache/dalvik after the first install) to make sure nothing else is screwy
Thepooch said:
which one did you try ? go to developer option and make sure there is a check in android debugging
---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------
give that a try
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
also did you wipe? wipe factory reset wipe cache wipe dalvik wipe system flash rom flash gapps reboot
Click to expand...
Click to collapse

no prob

SenorSmartyPants said:
Debugging was turned off. I turned it back on, rebooted and that did the trip.
Click to expand...
Click to collapse
After playing around with this a bit something is still not right.
I have debugging turned on, but USB is only successfully detected if I reboot with the usb cable plugged in to a PC. Then I can mount and dismount as many times as I want. everything is fine. But once I disconnect the USB cable, the KF will never detect the cable plug in again (nor will the PC). I have to reboot plugged in again to get it to show up.
I've done this several times same thing. I've tried plugging the cable in at different points too, before I unlock the screen, after. Only when in from reboot to unlock does it work.

SenorSmartyPants said:
After playing around with this a bit something is still not right.
I have debugging turned on, but USB is only successfully detected if I reboot with the usb cable plugged in to a PC. Then I can mount and dismount as many times as I want. everything is fine. But once I disconnect the USB cable, the KF will never detect the cable plug in again (nor will the PC). I have to reboot plugged in again to get it to show up.
I've done this several times same thing. I've tried plugging the cable in at different points too, before I unlock the screen, after. Only when in from reboot to unlock does it work.
Click to expand...
Click to collapse
i have the same issue on mine, using twa builds
also, sometimes when i plug in the usb cable it makes the kindle run extremely slow and laggish, requiring a reboot.

*Bump*
Does only detecting usb connected once per reboot only happen to the two of us in this thread? CM10 works pretty well for me, but this is a bit of an annoyance. I have a work around, reboot, but still...

I have the same issue. In fact, I can't get USB storage to work after installing CM10 8/24.
But I think the issue has to do with multiple Android USB drives being installed in Win7. I have a TF201 and Xoom and when I plug in the KF, USB reports the TF201 being connected. Of course Win7 does not show KF in Desktop Explorer. The only way I can download a new ROM to my KF is via my NAS which I connect via ES File Manager....
Can anyone confirm that having multiple Android devices causes this USB confusion?

You have to specifically enable USB storage before it will mount.

Unable to root! Stucked on TWRPP 2.2.0 Screen with several options
Hello!
I've tried to root my Kindle Fire, following the same steps that most of the users have followed (Using KFU 0.9.6).
Unfortunately, while installing the root (I guess) once it installs TWRPP, it inmediately boots up to the TWRPP screen with several options ( Install, Backup, Restore...) and the KFU software keeps a message that says Please wait.
Does anyone know how to fix this and finish the rooting of the device?
Thanks in advanced.
jjosue17

soupmagnet said:
You have to specifically enable USB storage before it will mount.
Click to expand...
Click to collapse
I have enabled but it still will not mount for some reason. I had a forced reboot issue appear as well.

try the previous build see if that doesnt solve your problem you must have usb debugging enabled and then tap on the icon in your status bar to transfer files...

I've been limping along just using the work around of rebooting while plugged in to get usb mounting to work.
But today I had KF mount to my PC, deleted the ADB drivers in windows from the device manager. Did a factory wipe on the tablet (even wiped the SD card), I'm running the latest TWA rom 8/28. I still can only get usb to detect if I reboot while connected to a pc. A couple little differences; after the wipe ADB was turned off on the ROM, I left it that way to see what happens. It does still mount (only after reboot, did I mention that ) but now it shows up under "Portable Devices" in device manager and the Device ID string is different in some apps (on PC) "Amazon Kindle Fire" instead of "Kindle Fire" which is what it was before today.
What else can I try? Do I need to do a super duper wipe? Factory, reinstall ROM, cache/dalvik? Do I need to purge even usb android driver on my system? (And how would I do that?)
Thanks for any help. I would love to get rid of this issue and just be able to plug in the KF and not worry about rebooting all the time.

Funny thing is I worked with someone the other day and when he mounted nothing would come up..... Reinstalled his adb drivers from kfu and it worked like a champ... Dont really know why... This is what I would try instead of messing with windows try creating a live usb as a formidable test to see if its simply just windows stupid drivers that are killing you... Create it with persistent and use this script to set up the drivers http://forum.xda-developers.com/showthread.php?t=1850038 very good chance it will work then you will know its a driver problem...

I'll see if I can give the Live USB thing a try if KFU driver reinstall doesn't help.
But I have a laptop that I never messed with the drivers on. With stock usb was always detected, after rooting and rom installed, had the same usb detection problems as my desktop.

Well I never did give the Live linux USB thing a try. I just keep going with my work around of rebooting with the usb connected and then doing my file transfers. I would only do this about once a week. I even noticed that with a couple of the more recent builds if I would plug KF in several times it would detect usb and I would not have to reboot.
But now with the last build (or two?) not exactly sure when it changed even that isn't working. Plugging in several times never detects usb now (95%+ detects usb charging though). And now it also won't detect usb after reboot while the cable is plugged in during the reboot. So I've had to do my file transfers in recovery mode. Recovery mode always works. What is different about what recovery mode "says" to the computer compared to what the full ROM "says"
Oh, and I only get USB 1.1 transfer speeds. But I think I read that this is a kernel driver issue that is well known, or has that been fixed somewhere?
Thanks

[Q] Help my kindle is stick on the fastboot mode

hi I am using the safe root method of root and trying to flash the FFF and TWRP , in this stib I am stuck in the fastboot mode I unplugged it and reconnect it help plz

Windows version?
How is it listed in Device Manager?
Error message?

I'm having the same problem and had posted a separate thread in the general forum, but coming here I see that I'm not the only one. I was following a guide here on how to saferoot, install FFF and TWRP on a 1st gen Kindle fire and after setting it for fastboot the first time my laptop could no longer see the device and it was stuck sitting at the non-animated "kindle fire" screen. I reset the device, uninstalled drivers and re-installed, rebooted my laptop, all to no avail, so I left it and went to bed. Little did I know that the device wasn't charging while at this screen and just left it plugged to my laptop and went to bed.
Now it seems the device is completely dead, or too dead to boot. The kindle fire screen will display for a couple seconds then the screen goes black, over and over. I used a high power charger(5v 2.2A) instead of the laptop USB port for over 12 hours and it's still just looping. Is there anything that can recover this thing?
Windows 7
Shows in Device MGR as Android ADB (before it went dead)
Before it went dead it just sat at the non-animated Kindle Fire screen, now it boot loops to the non-animated kindle fire screen
In linux, watching /var/log/messages, I see the Amazon Kindle and serial # pop up the first time I plug it in and then it says the device was disconnected as it reboots.
Thanks

g17jimmy said:
I
Windows 7
Shows in Device MGR as Android ADB (before it went dead)
Click to expand...
Click to collapse
That is what you wanted.
Before it went dead it just sat at the non-animated Kindle Fire screen, now it boot loops to the non-animated kindle fire screen
In linux, watching /var/log/messages, I see the Amazon Kindle and serial # pop up the first time I plug it in and then it says the device was disconnected as it reboots.
Thanks
Click to expand...
Click to collapse
you tried powering off Kindle? Hold power for 15 secs
then reconnect to wall charger

sd_shadow said:
That is what you wanted.
you tried powering off Kindle? Hold power for 15 secs
then reconnect to wall charger
Click to expand...
Click to collapse
Previously ,if I disconnected from any power source it just powered off and the power button didn't seem to stop the loop. As soon as I plugged it in it would start the loop again. *BUT* - I just reconnected after having had it disconnected for a few hours and was able to power it off by holding the power button ~15sec. It seems like I was able to leave it plugged in but not have it in a loop. Maybe it will charge now.

g17jimmy said:
Previously ,if I disconnected from any power source it just powered off and the power button didn't seem to stop the loop. As soon as I plugged it in it would start the loop again. *BUT* - I just reconnected after having had it disconnected for a few hours and was able to power it off by holding the power button ~15sec. It seems like I was able to leave it plugged in but not have it in a loop. Maybe it will charge now.
Click to expand...
Click to collapse
It will not charge in Fastboot mode, best to flash the twrp and FFF, if it is a stable connection
---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------
Edit: It will not charge in Fastboot mode

It has charged now that it stopped the boot loop, but still just sitting at the fastboot non-animated 'kindle fire' screen. Soupkit on my linux laptop doesn't see it, still:
{see attachment, I couldn't link to the image host site since I'm a new member}
My system sees the kindle:
{see attachment, I couldn't link to the image host site since I'm a new member}
I'll check from my windows system in a sec.

g17jimmy said:
It has charged now that it stopped the boot loop, but still just sitting at the fastboot non-animated 'kindle fire' screen. Soupkit on my linux laptop doesn't see it, still:
{see attachment, I couldn't link to the image host site since I'm a new member}
My system sees the kindle:
{see attachment, I couldn't link to the image host site since I'm a new member}
I'll check from my windows system in a sec.
Click to expand...
Click to collapse
not sure, but soupkit may only work on 32bit systems

sd_shadow said:
not sure, but soupkit may only work on 32bit systems
Click to expand...
Click to collapse
It did not want to work due to missing 32bit libraries at first, but you can install the 32bit libraries along side the 64 bit libraries, don't know if that makes soupkit happy though. It stopped complaining. I have a 32bit live-cd I can run just to test-
but.... here's where things are on the windows side:
Device manager sees "android ADB interface", neither ADB nor fastboot can see the device. Kindle just sits there as shown in the phone pic. At least now the thing isn't acting completely weird, I'll do some more searching on the forum, but if you have any suggestions I'm all ears. FWIW this is the post I was following - http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3 - I am stuck after completing step 5.
Thanks!

g17jimmy said:
It did not want to work due to missing 32bit libraries at first, but you can install the 32bit libraries along side the 64 bit libraries, don't know if that makes soupkit happy though. It stopped complaining. I have a 32bit live-cd I can run just to test-
but.... here's where things are on the windows side:
Device manager sees "android ADB interface", neither ADB nor fastboot can see the device. Kindle just sits there as shown in the phone pic. At least now the thing isn't acting completely weird, I'll do some more searching on the forum, but if you have any suggestions I'm all ears. FWIW this is the post I was following - http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3 - I am stuck after completing step 5.
Thanks!
Click to expand...
Click to collapse
tried different usb ports? usb 2.0?

sd_shadow said:
tried different usb ports? usb 2.0?
Click to expand...
Click to collapse
If I leave it hung on the kindle fire screen and plug it in to a different port Windows gives an error (screenshot attached.) If I turn it off (power button 15sec) and then plug it in it comes on and windows sees it properly as an android adb interface, but adb and fastboot still cannot see it.
I haven't looked into messing with it on my mac, I'll check that out, too.

The only live cd I had handy was an old version of Backtrack (BT5r3,) but it's 32bit and still adb and fb cannot see the device, even though the system sees it being plugged in and disconnected.
BTW- on the 64bit Centos 7 side of this system, I installed these packages to make Soupkit at least seem to work:
yum install gtk2.x86_64 gtk2.i686 libXtsc.x86_64 libXtsc.i686 ncurses-libs.i686​
Something about the way the new CentOS works won't allow you to install the i686 libraries without including the x86_64 install at the same time.

Ok, disregard my issues. I can write to the device even though ADB and fastboot couldn't see it. I'm past step 5 now.

g17jimmy said:
Ok, disregard my issues. I can write to the device even though ADB and fastboot couldn't see it. I'm past step 5 now.
Click to expand...
Click to collapse
good.
Not sure what is causing the no reply to fastboot devices
I may need to change my directions.
Did you ever try?
Code:
fastboot reboot

android tools
I like to have two terminals open. One with root permissions for fastboot commands and a normal terminal for adb. Some distros have a root terminal program, but if you don't, just sudo <gnome-terminal>,<xterm>, or whatever your favorite is.
Thanks to SD_Shadow for all his work. I don't know how he can keep track of all the possible screw ups one can perform rooting and flashing, and get to the bottom of things.

sd_shadow said:
good.
Not sure what is causing the no reply to fastboot devices
I may need to change my directions.
Did you ever try?
Code:
fastboot reboot
Click to expand...
Click to collapse
I'm not sure why it didn't show in the fastboot devices list either. It shows now if I put it in fastboot. I have twrp 2.8.3.0 loaded and I'm trying to install a ROM but it doesn't work. I used adb to copy the file to the kindle but it's not installing. If I try to mount the device in windows or linux I get a message that the disk isn't formatted. Is this normal? I don't see any steps that indicate I should format a disk.

g17jimmy said:
I'm not sure why it didn't show in the fastboot devices list either. It shows now if I put it in fastboot. I have twrp 2.8.3.0 loaded and I'm trying to install a ROM but it doesn't work. I used adb to copy the file to the kindle but it's not installing. If I try to mount the device in windows or linux I get a message that the disk isn't formatted. Is this normal? I don't see any steps that indicate I should format a disk.
Click to expand...
Click to collapse
another pic

g17jimmy said:
another pic
Click to expand...
Click to collapse
Uncheck all in Mount options
, then try mounting storage
---------- Post added at 01:36 PM ---------- Previous post was at 01:34 PM ----------
Also I don't recommend 2.8.x.x, suggest downgrading to 2.7.x.x
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
Kindle Fire Flashable Recoveries TWRP/COTR/CWM[2014]

OK. I'll go back to 2.7.x and try again.

I tried to downgrade to 2.7.x, but it said "image too large for partition", but while trying to clear that up I seem to have accidentally fixed the sdcard mount. I wiped everything and rebuilt sdcard and now it allowed me to run the install of cm11. What causes the "image too large for partition error"?
Thanks.
Merry Christmas

[Q] DHD USB and SD brick... help?!

Hi, I recently rooted and flashed cm11 to my DHD
It is S-OFF and rooted, 4ext recovery installed.
Problem is that now the phone is not recognised by my computer (or any computer, not a driver issue) I use linux and there is no output whatsoever from dmesg when phone is plugged/unplugged to usb.
Reading through other posts (but not relevant to DHD) it seems to be a prob with the misc partition (mtd0 on the desire, not sure on the DHD)
So I have no fastboot usb or adb over usb access, but can SSH into phone and use root shell on it, any suggestions?
Also, SD card not working - assume this is related to the USB problem since started happening at same time.

correction, sd works, so just usb needs sorting, tried reflashing /misc but no joy

jmprince80 said:
Hi, I recently rooted and flashed cm11 to my DHD
It is S-OFF and rooted, 4ext recovery installed.
Problem is that now the phone is not recognised by my computer (or any computer, not a driver issue) I use linux and there is no output whatsoever from dmesg when phone is plugged/unplugged to usb.
Reading through other posts (but not relevant to DHD) it seems to be a prob with the misc partition (mtd0 on the desire, not sure on the DHD)
So I have no fastboot usb or adb over usb access, but can SSH into phone and use root shell on it, any suggestions?
Also, SD card not working - assume this is related to the USB problem since started happening at same time.
Click to expand...
Click to collapse
No...when flashing to cm 11+ you need to update your SDK. Update the files(all the android versions). To access fastboot u have to open platform folder..then anywhere in that folder hold shift and right click..chose command here
---------- Post added at 03:20 AM ---------- Previous post was at 03:19 AM ----------
P.s.
Edit: its either platforms or platform tools folder. Sorry about that.
---------- Post added at 03:23 AM ---------- Previous post was at 03:20 AM ----------
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/

it is not a problem with the computer, since the phone is not even shown on list of USB devices. even with no SDK or any other tools installed on a computer there should still be a USB vendor and product code when plugged in. the phone itself also does not recognise that it is plugged into anything but a power source. problem is phone side hence content of original post.

jmprince80 said:
it is not a problem with the computer, since the phone is not even shown on list of USB devices. even with no SDK or any other tools installed on a computer there should still be a USB vendor and product code when plugged in. the phone itself also does not recognise that it is plugged into anything but a power source. problem is phone side hence content of original post.
Click to expand...
Click to collapse
No! With the android versions 4.4 and up, you need to install the SDK updated files for that android versions. Believe me,I know
---------- Post added at 11:35 AM ---------- Previous post was at 11:34 AM ----------
If one cannot find the specific drivers for a device, they can use the SDK toolkit

Im happy to try installing the latest SDK.
However Im pretty sure that its not going to change anything.
Simple fact is that is a USB device is plugged in, whether or not there are drivers present, it will still show up with a LSUSB or as an unknown device in windows device manager.
I think the problem lies somewhere in one of the configuration partitions - I am able to flash different ROMS by adb pushing to /sdcard but none i have tried have yet solved the USB issue. If I flash back to stock I will lose recovery and be unable to fix problem at all.

Dude. Yes it will

in RUU are *ALL* partitions replaced back to stock? Don't fancy being stuck back on GB....

Its not a matter of "staying"on gingerbread. Its a matter of getting your device back on track. Running that ruu after locking your bootloader will sort things out. You can always unlock it again and flash a fresh custom ROM.
---------- Post added at 02:16 AM ---------- Previous post was at 02:13 AM ----------
If u are s off, then all that will be wiped pertaining to wiping is your bootloader. There u can use SDK to access your device. U don't exactly need the "USB" thing sorted. All u need is to have SDK updated with all android versions and getting access to your bootloader via platform tools in SDK. Ppl are sadly misguided by this USB situation.

PC Link not mirroring phone on PC

I have the Z00AD ZE551ML Zenfone 2. I just rooted it, and tried 2 different roms (Cyanogen, and SuperZen (which I currently have on)), on neither rom did the PC Link work correctly. It will register that it's connected to the computer, I can open the pc link on both my phone and computer, and connect. I even get notifications on my computer when I get them on my phone while it's connected. But the window will not pop up mirroring my phone on my pc, no matter what I try. Any suggestions?

Did you get any solution. I am facing same problem while connecting other (non ASUS) device via pc liNk.

same problem here, I'm using stock marshmallow though so I don't know what the problem is
---------- Post added at 02:22 AM ---------- Previous post was at 02:19 AM ----------
I also noticed that PC Link is no longer available on the playstore, is it unsupported by asus on later ZenUI versions (ZenUI 3 and 4?)