Kindle Fire Stuck at logo - Kindle Fire Q&A, Help & Troubleshooting

Hello !
I have bricked my kindle fire 7" by rooting,When the kindle start root i have unplug the cable
And now the kindle stuck at logo
but one day I had turn it on and i go to buy something after that i don't know what happen, when i plug in to charge it it turn on then turn off ..
what's can i do now ??
The problem can be from the battery or what ?
Thank you.

try a Factory Cable (Fastboot Cable)
FAQ Q26: What is a factory cable? What is it used for? How do I use it?
A factory cable, not to be confused with the OEM USB cable that comes with the Kindle Fire, is a USB cable made to emulate a Motorola factory programming cable. With the Kindle Fire, it is an easy way to access fastboot mode, especially when no other options are available. To use it, while plugged into your computer, simply plug it into a Kindle Fire that has been completely powered down.
Click to expand...
Click to collapse
see Kindle Fire Factory Cable

My son's Kindle started doing the same things. None of the Kindles are rooted so I started doing some research and tried using Kindle_Fire_Utility_v0.9.9. However every time I try to enter fastboot I get the error that:
"failed to copy 'files\fbmode' to '/data/local/fbmode': no space left on device"
Now, is it truly completely out of space (which I wouldnt doubt with my 7 year old) and if so will I not be able to fix this no matter what?
Or is that not the case and ordering a factory cable would do the trick? I'll order it if it means fixing this much easier but I just didn't want to drop the $15 without knowing if that space error is going to still be an issue.

JynxRD said:
My son's Kindle started doing the same things. None of the Kindles are rooted so I started doing some research and tried using Kindle_Fire_Utility_v0.9.9. However every time I try to enter fastboot I get the error that:
"failed to copy 'files\fbmode' to '/data/local/fbmode': no space left on device"
Now, is it truly completely out of space (which I wouldnt doubt with my 7 year old) and if so will I not be able to fix this no matter what?
Or is that not the case and ordering a factory cable would do the trick? I'll order it if it means fixing this much easier but I just didn't want to drop the $15 without knowing if that space error is going to still be an issue.
Click to expand...
Click to collapse
which opton where you trying 3? install TWRP?
try power off kindle, start kindle fire utility, select option 3, connect/power on kindle.
if that doesn't work there is a coupe of other options, see my UnBricking Tools list
if it does work
KFU will install TWRP version 2.5.0 you can not reinstall stock rom with that, you can try wiping Cache and/or Data.
if you want stock you will need to downgrade TWRP to 2.2.2.1, just download zip-otter-twrp-2.2.2.1-blaze(sd_shadow).zip and install in current TWRP.

Doesn't matter the option. If I choose option 1 to attempt to enter fastboot (as the status currently says its in 4000 not 4002) or if I choose options 3 to install recovery, I still get:
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
failed to copy 'files\fbmode' to '/data/local/fbmode': No space left on device
Unable to chmod /data/local/fbmode: No such file or directory
/data/local/fbmode: not found
The kindle has been told to reboot in Fastboot Mode.

Anyone have any other suggestions. Seems like my only problem is this space error or I'd be able to complete the unbricking process.

JynxRD said:
Anyone have any other suggestions. Seems like my only problem is this space error or I'd be able to complete the unbricking process.
Click to expand...
Click to collapse
did you lookk @ [fastboot] stock 6.2.1 fastboot mode without rooting or cables?

sd_shadow said:
did you lookk @ [fastboot] stock 6.2.1 fastboot mode without rooting or cables?
Click to expand...
Click to collapse
Yes but it still requires me to perform
"adb push fbmode /data/local/tmp"
which produces
failed to copy 'files\fbmode' to '/data/local/tmp/fbmode': No space left on device
And I can't wipe any files without root. So it looks like I may need that factory cable, assuming that gives me access to clear up space without root.

and you tried starting KFU option 3, then turning on kindle fire?

sd_shadow said:
and you tried starting KFU option 3, then turning on kindle fire?
Click to expand...
Click to collapse
Yes, While it's ON
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
failed to copy 'files\fbmode' to '/data/local/fbmode': No space left on device
Unable to chmod /data/local/fbmode: No such file or directory
/data/local/fbmode: not found
If I do it while its OFF and then turn it on, it just sits here:
***********************************************
* Activating Fastboot (4002) *
***********************************************
Oops... something went wrong.
We are unable to locate your Kindle Fire.
Make sure it is plugged in and powered on.
0 [main] cat 2784 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list [email protected]
< waiting for device >

JynxRD said:
So it looks like I may need that factory cable, assuming that gives me access to clear up space without root.
Click to expand...
Click to collapse
no, fastboot cable just boots kindle to fastboot mode, where you can flash twrp recovery, which is what the fbmode file would do if you could push it.

sd_shadow said:
no, fastboot cable just boots kindle to fastboot mode, where you can flash twrp recovery, which is what the fbmode file would do if you could push it.
Click to expand...
Click to collapse
So if there isn't enough space on your Kindle to push the file 'fbmode' to it, your pretty much screwed with a brick? I tried searching the web over and over for anyone else experiencing this. With such a small space available I can't believe this hasn't been ran into multiple times.

JynxRD said:
So if there isn't enough space on your Kindle to push the file 'fbmode' to it, your pretty much screwed with a brick? I tried searching the web over and over for anyone else experiencing this. With such a small space available I can't believe this hasn't been ran into multiple times.
Click to expand...
Click to collapse
The twrp recovery will be flashed over recovery partition, space available does not matter
Sent from my Amazon Kindle Fire using Tapatalk

sd_shadow said:
The twrp recovery will be flashed over recovery partition, space available does not matter
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
So what do you think I should try next? Maybe just ordering the factory cable?

What is kindle listed as, in device manager.
Sent from my Amazon Kindle Fire using Tapatalk

sd_shadow said:
What is kindle listed as, in device manager.
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Sorry for the late response, things got a little busy around here.
Here is what I have in the DM while its plugged in.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

So I decided to follow clean install steps again. When I try to install the drivers those I get this error as it appears per some searching a lot of other's have gotten.
I'm using Windows 8.1 64bit.
So I'm installing Windows 7 32bit on a virtual machine to see if that's possibly the issue.

Related

Kindle Fire Bricked - Need Assistance

I rooted my Kindle Fire and have TWRP recovery installed. I flashed a CM9 Rom followed the directions step by step including wiping cache / dalvik etc... from recovery before rebooting. When my kindle fire boots now I first see the Kindle Fire logo screen and then it switches to the CM9 bootup logo (looks like a bunch of multicolored squares that appear and disappear). When I get to this point my computer makes the noise like it detects something plugged into the USB port and the device listed says Amazon under unspecified in my device list. When I right click on it i have the option to eject amazon.
Running the kindle fire unbrick utility wont work on any option I click. Each option says waiting for device or device not found.
Running kindle fire utility reports ADB status offline boot status unknown. My computer sees the kindle but I guess it's not mounting. The farthest I can get on this thing is the spinning bootup logo and I cannot get it to go back to TWRP recovery no matter what I try.
I'm guessing this thing is permanently screwed but if anyone has any suggestions i'd really appreciate it.
Okay, first I have to ask...because this mistake has been made by others, making this a much more difficult process than needed...what color is your "TWRP" screen?
soupmagnet said:
Okay, first I have to ask...because this mistake has been made by others, making this a much more difficult process than needed...What color is your TWRP screen?
Click to expand...
Click to collapse
I cant pull it back up so i'm only going by memory... I'm fairly certain it was a dark background with orange buttons.
urge311 said:
I cant pull it back up so i'm only going by memory... I'm fairly certain it was a dark background with orange buttons.
Click to expand...
Click to collapse
Did it look like this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...or this?....
The first one (CWMR), cannot install ICS or JB based ROMS. For that, you need to install the second one (TWRP).
It definitely looked like the second one with the big buttons.
I guess my question is, why are you leaving it plugged into your computer when flashing a new ROM? Just curious.
My next question is...what does your boot logo look like? (in detail)
I was plugging it into the computer in an effort to fix the problem using the kindle fire unbrick utility... My problem is when I turn the kindle fire on since installing my rom it gets stuck on a boot loop with the CM9 boot screen and never fully loads the rom. I have no way of fixing it by getting into recovery because it wont open no matter what I try.
My bootup screen first shows the kindle fire logo then goes to the cm9 wallpaper where it's like a bunch of colored squares the appear and disappear and it never gets any farther than that.
Connecting the kindle to my computer was only so I could try to reflash recovery which is not working because none of the downloadable utilities i've tried recognize the kindle is plugged in but my computer seems to know it's there because it recognizes a device but it doesn't mount to it at all allowing me to transfer data to it.
::facepalm::
No. I know what your problem is. I need to know what your boot logo looks like, in detail...Which is why I asked, "What does your boot logo look like? (in detail)"...as in, identifying characteristics...of the boot logo. (This is very important)
soupmagnet said:
::facepalm::
No. I know what your problem is. I need to know what your boot logo looks like, in detail...Which is why I asked, "What does your boot logo look like? (in detail)"...as in, identifying characteristics...of the boot logo. (This is very important)
Click to expand...
Click to collapse
Here's a link to a youtube video I made today showing exactly what happens when I turn the kindle fire on.
http://www.youtube.com/watch?v=Dl-VAunzSqc
urge311 said:
Here's a link to a youtube video I made today showing exactly what happens when I turn the kindle fire on.
http://www.youtube.com/watch?v=Dl-VAunzSqc
Click to expand...
Click to collapse
I would have taken "Kindle Fire in orange and white"...but that works just as well.
You never installed a custom bootloader. The Kindle Fire logo you see indicates that it's the stock bootloader that comes with the device. The custom bootloader we all use is FireFireFire (FFF). What makes FFF different from the stock version, is that it allows you to use the power button at startup to access custom recovery, and the most recent version has the ability to reset your bootmode (very handy). Your problem is that you have a bad ROM flash, possibly from a bad download or using the wrong recovery (yes I know, we went over that) or perhaps you didn't wipe properly (I know, we went over that as well). The typical fix for this is to access recovery and flash a new or different ROM (w/wipes) in TWRP, not CWM. Here's where the problem lies, without a custom bootloader like FFF, you have to rely on your computer's ability to connect with your device to send adb commands. The key to that is having working drivers, and I can tell by your previous description that you don't. So, install or reinstall, fix or whatever you have to do to your drivers to get connected with the adb, then send the command to change the bootmode to recovery.
And...before you ask any more questions (I can feel them coming), you need to read...
http://forum.xda-developers.com/showthread.php?t=1552547
first three posts
http://forum.xda-developers.com/showthread.php?t=1638452
install a ROM section
http://forum.xda-developers.com/showthread.php?t=1668159
all of it...just in case
soupmagnet said:
I would have taken "Kindle Fire in orange and white"...but that works just as well.
You never installed a custom bootloader. The Kindle Fire logo you see indicates that it's the stock bootloader that comes with the device. The custom bootloader we all use is FireFireFire (FFF). What makes FFF different from the stock version, is that it allows you to use the power button at startup to access custom recovery, and the most recent version has the ability to reset your bootmode (very handy). Your problem is that you have a bad ROM flash, possibly from a bad download or using the wrong recovery (yes I know, we went over that) or perhaps you didn't wipe properly (I know, we went over that as well). The typical fix for this is to access recovery and flash a new or different ROM (w/wipes) in TWRP, not CWM. Here's where the problem lies, without a custom bootloader like FFF, you have to rely on your computer's ability to connect with your device to send adb commands. The key to that is having working drivers, and I can tell by your previous description that you don't. So, install or reinstall, fix or whatever you have to do to your drivers to get connected with the adb, then send the command to change the bootmode to recovery.
And...before you ask any more questions (I can feel them coming), you need to read...
http://forum.xda-developers.com/showthread.php?t=1552547
first three posts
http://forum.xda-developers.com/showthread.php?t=1638452
install a ROM section
http://forum.xda-developers.com/showthread.php?t=1668159
all of it...just in case
Click to expand...
Click to collapse
Thank you for your help. I really do appreciate it.
Have you tried restoring it with data unchecked on the restore option of twrp?
Sent from my Kindle Fire using xda app-developers app
pandapounds said:
Have you tried restoring it with data unchecked on the restore option of twrp?
Click to expand...
Click to collapse
I'm guessing that's probably not an option...
urge311 said:
I have no way of fixing it by getting into recovery because it wont open no matter what I try.
Click to expand...
Click to collapse
I could be wrong though.
soupmagnet said:
I'm guessing that's probably not an option...
I could be wrong though.
Click to expand...
Click to collapse
Well after a lot of trial and error with installing and uninstalling drivers I finally got the kindle to boot into TWRP but i'm unable to get it back to stock. TWRP loads after white and orange kindle fire logo. I can access any of the menus on that but cant really do much else. I've tried flashing FFF but I can no longer get the device into fastboot mode. I've tried various ADB commands to do this manually but i'm getting some odd readings through ADB:
C:\Kindle Fire Utility\tools>adb devices
List of devices attached
313A02600000001 recovery
C:\Kindle Fire Utility\tools> adb shell
~ # ←[6n
C:\Kindle Fire Utility\tools>
Basically i'm stuck in a recovery boot loop now and the kindle fire unbrick utility with the recovery loop option just gets stuck at waiting for device. Kindle Fire Utility when launched shows ADB status: Online and Boot Status: Unknown.
Anyone know of a way around this? I'm guessing i'll have to run some commands but dont really know where to go from here.
urge311 said:
Well after a lot of trial and error with installing and uninstalling drivers I finally got the kindle to boot into TWRP but i'm unable to get it back to stock. TWRP loads after white and orange kindle fire logo. I can access any of the menus on that but cant really do much else. I've tried flashing FFF but I can no longer get the device into fastboot mode. I've tried various ADB commands to do this manually but i'm getting some odd readings through ADB:
C:\Kindle Fire Utility\tools>adb devices
List of devices attached
313A02600000001 recovery
C:\Kindle Fire Utility\tools> adb shell
~ # ←[6n
C:\Kindle Fire Utility\tools>
Basically i'm stuck in a recovery boot loop now and the kindle fire unbrick utility with the recovery loop option just gets stuck at waiting for device. Kindle Fire Utility when launched shows ADB status: Online and Boot Status: Unknown.
Anyone know of a way around this? I'm guessing i'll have to run some commands but dont really know where to go from here.
Click to expand...
Click to collapse
You can use recovery to install FFF1.4. See if you can use the mount function to mount your sdcard to the computer.
soupmagnet said:
You can use recovery to install FFF1.4. See if you can use the mount function to mount your sdcard to the computer.
Click to expand...
Click to collapse
The mount option does indeed mount the kindles SD card to my computer. Do I need to hunt for a FFF1.4 in a .zip file to flash through recovery?
Yes, indeed.
http://forum.xda-developers.com/showpost.php?p=25598837
soupmagnet said:
Yes, indeed.
http://forum.xda-developers.com/showpost.php?p=25598837
Click to expand...
Click to collapse
Just wanted to say thanks again. Everything is working now. I was able to flash FFF with a zip I found on another post on here which still kept me in a TWRP recovery bootloop but I was able to fix that with the kindle fire unbrick utility with the recovery boot loop option. Everything is working great now. You definitely got me pointed in the right direction and I really appreciate it.
urge311 said:
I was able to flash FFF with a zip I found on another post on here which still kept me in a TWRP recovery bootloop but I was able to fix that with the kindle fire unbrick utility with the recovery boot loop option.
Click to expand...
Click to collapse
FFF1.4 was designed to (among other things) address that problem. By holding the power button to bring up the boot menu and selecting "reset boot mode", it will reset the idme bootmode to 4000 and it will stay that way.

[Q] Won't boot into recovery.

Good day, I gonna be quickly.
Device information:
Kindle fire 8.9
System Version: 8.4.6_user_4620220
I'd like to install CM10.2 on my table, so i follow the next tutorial to get root, recovery, 2nd-bootloader, etc: (I can't post links but it's from the webpage wwwDOTrootkindlefireDOTcom, the article is called "How to Root & Convert Kindle Fire HD 8.9 into Pure Android Tablet!"
I follow every step as was there with two exception,
I change:
1. kfhd8-freedom-boot-8.4.3.img for kfhd8-freedom-boot-8.4.6.img (from official post of Hashcode)
2. and kfhd8-twrp-2.6.0.0-recovery.img for kfhd8-twrp-2.6.3.1-recovery.img (from official post of Hashcode)
everything went right, not errors, no mistake, just fine.
when i try to go into recovery by pressing power bottom and then volumen up, it doesn't do anything, i have tried with few seconds, holding it together, nothing works.... the table is working normal, once it turn on show the yellow logo, then the blue logo, and then yellow logo again and star normally the amazon os...
So am i doing something wrong? what should i do?
one more thing, the blue logo doesn't show up quickly as the video i saw, after the yellow logo it fades, turn off, on before stay quiet normaly, and then the yellow one again. is that normal?
Thank you very much.
Its in this order like this: turn on, let go of power button, hold volume down button until you see blue logo, and either continue holding it or let go as you see fit until you see the twrp logo. You can also get into recovery from in the os by using a mobile terminal and running something like
Code:
su -c "reboot recovery"
hope this helps!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Its in this order like this: turn on, let go of power button, hold volume down button until you see blue logo, and either continue holding it or let go as you see fit until you see the twrp logo. You can also get into recovery from in the os by using a mobile terminal and running something like
Code:
su -c "reboot recovery"
hope this helps!
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Now after i enter the command my kindle won't turn on, it stuck on the yellow logo.
any other solution?... i gonna leave some doubts i have.
what would happen if i re flash everything after the root, i mean reflash the kfhd8-twrp-2.6.3.1-recovery.img, kfhd8-freedom-boot-8.4.6.img and kfhd8-u-boot-prod-8.1.4.bin? will i brick my kindle fire? what happen if i re flash a older version of recovery? and boot?
Any suggestion what should i do now?
Um that's kinda odd, maybe twrp didn't flash correctly, even then I wouldn't expect recovery to corrupt itself that badly. Try restoring with kindle fire first aid and give it another shot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Um that's kinda odd, maybe twrp didn't flash correctly, even then I wouldn't expect recovery to corrupt itself that badly. Try restoring with kindle fire first aid and give it another shot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
i didn't make a back up of the system (i want it to do it thought twrp) and was the version 8.4.6, can i find any back up of that version here?
Edit: I kinda understand how that works now, i don't need the image of system, I'm downloading it to try to restore it, if not I'm going to use this method: http://forum.xda-developers.com/showthread.php?t=2011126. is that a good thing to do?
Thanks for everything, I'm sure my kindle will come back to life later.
That tool should work too, go for it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
That tool should work too, go for it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Good morning..
I tried eveything yesterday but it won't pass the waiting for devices, with both application, but yesterday night i was able to go to the fastboot, with the fastboot today i can't go to fastboot with fastboot -i 0x1949 getvar product it just turn on the kindle to stay stuck in kindle logo.. i might be wrong but i think this might be because i tried to many drivers... i don't know.
What can i do? i need to fix this :S, there's anyway to get into the fastboot? with other computer, if that so what should be the processes clean of installing everything, SDK, drivers, etc.
I knew what was the first problem, the twrp file i flashed was corrupted. i checked it with md5 :S.
help!
OK download the drivers in my signature and extract them somewhere. When you turn the kindle off, open the device manager on your PC, as soon as you plug the device back in and see a jem device with a yellow triangle right click it and hit update drivers and choose the location of my drivers you extracted. Its hard to get the timing right because it will only appear for a few seconds. If you can't get the timing right then try kindle fire first aims driver installer. I believe it has one that will automatically put the drivers in windiow's cache so it will install them automatically. If that still fails then go download a Ubuntu 13.10 live CD and either boot it from a flash drive or CD, and install the fastboot command package from the Ubuntu software center. From their you can type the command and it would automatically work because Linux is awesome like that and doesn't tend to have driver issues like windows. xD
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK download the drivers in my signature and extract them somewhere. When you turn the kindle off, open the device manager on your PC, as soon as you plug the device back in and see a jem device with a yellow triangle right click it and hit update drivers and choose the location of my drivers you extracted. Its hard to get the timing right because it will only appear for a few seconds. If you can't get the timing right then try kindle fire first aims driver installer. I believe it has one that will automatically put the drivers in windiow's cache so it will install them automatically. If that still fails then go download a Ubuntu 13.10 live CD and either boot it from a flash drive or CD, and install the fastboot command package from the Ubuntu software center. From their you can type the command and it would automatically work because Linux is awesome like that and doesn't tend to have driver issues like windows. xD
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks, I'm going to use Ubuntu, windows will not work.
Once i get into the fastboot throught ubuntu, Do I have to come back to windows and use KF First Aide to restore stock os right?
or can I use ubuntu to do this? if that so, how? KF First Aide works on ubuntu?
Can't I just simple flash the system.img that is in KFHD_SRT_v2.1 folder? (throught ubuntu)
thanks a lot for the patience
I gonna leave these question to try no bother anymore. I'm asking because my KF First Aide yesterday won't pass after this lines..
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it get stuck there...
and the KFHD_SRT_v2.1 didn't recognize the device even when i was in the fastboot already and my kindle was on the device manager installed as Kindle ----> Android ABD device (what i see is kinda wierd is that the first time i get working in the fastboot if i ask for devices it would should me some kinda of ID XXXXXXXXXXX but yesterday (and I'm sure is because the drivers and maybe something is not right installed even i read could be a conflict with Android SDK,) just show me the device product: Jem-PVT-Prod-04 not the ID.
This all the information i can give.
My kindle software/hardware was or is:
Kindle fire 8.9
System Version: 8.4.6_user_4620220
My OS is windows 7 64bits
I did install everything JAVA develoment, I did have android SDK already (because I flash a xperia sucefully) and it's on my C:\Program Files\Android SDK but i didn't install it, i just unzip it. here's a capture:
I'm using the fastboot that i used to get the kindle into the fastboot from the folder i used to flash twrp and root.
thanks for everything, sorry bother.
any advice will be great, have a good day.
kffa won't work in ubuntu since its a batch file, for some reason it never got converted into a bash script. You can just manually flash those images from ubuntu and it should work just fine, though i'm thinking there might not even be a need to, i mean flash the recovery image and it should work again theoretically, seems to me the idme mode just got stuck to recovery and never got reset because recovery is broken, but thats just my take on it, if that was the case you could change the idme from fastboot but thats kinda complicated because the numbers for idme on the first gen's were in the 4000's and the newer gen ones are single digits and i dont rember which digit is what option so i'd say try to flash recovery from srt and see what happens.
stunts513 said:
kffa won't work in ubuntu since its a batch file, for some reason it never got converted into a bash script. You can just manually flash those images from ubuntu and it should work just fine, though i'm thinking there might not even be a need to, i mean flash the recovery image and it should work again theoretically, seems to me the idme mode just got stuck to recovery and never got reset because recovery is broken, but thats just my take on it, if that was the case you could change the idme from fastboot but thats kinda complicated because the numbers for idme on the first gen's were in the 4000's and the newer gen ones are single digits and i dont rember which digit is what option so i'd say try to flash recovery from srt and see what happens.
Click to expand...
Click to collapse
great i'll try that, while i'm waiting for the ubuntu to download i tried to install the drivers and i know now if the work, i guess not, i turn off the kidle run the command to go to fastboot and this is what i get.
that command was off, you left off a word, its supposed to be "fastboot -i 0x1949 getvar product", just thought you might need it for future reference in ubuntu.
stunts513 said:
that command was off, you left off a word, its supposed to be "fastboot -i 0x1949 getvar product", just thought you might need it for future reference in ubuntu.
Click to expand...
Click to collapse
THANKS!!! i did fix my kindle fire.
But i still have a very last question...
once i get back to kindle with KFFA the OS system 8.1.2, I tried again to install the Cyangenmod. and get the stuck in the blue logo.
this time i made sure everything was checked, and everything was fine with MD5, all the files are from Hashcode. here's my question:
The kindle fire is running 8.1.2 and this file is kfhd8-freedom-boot-8.4.6.img that means i need to find my version? or that will not matter at all?
I get back to stock amazon os, waiting to see if i try again.
THANKS A LOT ONCE AGAIN..
For future references, i did fix my kindle fire by uninstalling every driver once the kindle fire show up for 3 seconds, Use ccleaner, reboot the computer, and the in those 3 seconds i installed the stunts513 drivers, then i go back to stock with KFFA.
RE-EDIT: THANKS, i'm running now cm10.2. Thanks very much, this is solved, can be closet.

[Q] Bricked (Stuck) Kindle Fire 6.3.2

My Kindle Fire is 6.3.2.
I tried to root it using KFU. I went to install_drivers.bat, and it says "google, inc- Winusb failed." For some stupid reason, i chose to ignore that and went on to root through the KFU and "Install permanent root with superuser" and now it says
Fastboot uses a different device than ADB.
You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU
Installing FFF...
<waiting for device>
So I am now stuck on a permanent logo screen (Black and orange), with no animation. I can turn it off and on.
Pretty much everything I try to do ends with "waiting for device."
I believe it has something to do with missing drivers, although I am not entirely sure on any of this at this point.
Windows 7 or 8?
Sent from my XT862 using Tapatalk
Maybe try the unbrick utility.
I'm having some issues with the KFU myself, after installing the drivers Windows device manager no longer sees the Kindle when it's stock booted. I can mount from TWRP but it appears under Portable devices as E:/ , not Kindle. Root and installation of google apps did not take, though it ran to completion and said all done. KFU hangs when it tries to activated Fastboot (4002) so many of the other options of KFU wont run.
Arkasai said:
Maybe try the unbrick utility.
I'm having some issues with the KFU myself, after installing the drivers Windows device manager no longer sees the Kindle when it's stock booted. I can mount from TWRP but it appears under Portable devices as E:/ , not Kindle. Root and installation of google apps did not take, though it ran to completion and said all done. KFU hangs when it tries to activated Fastboot (4002) so many of the other options of KFU wont run.
Click to expand...
Click to collapse
If drivers are installed correctly Kindle Fire should be seen as Android Phone>adb interface
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 07:35 PM ---------- Previous post was at 07:34 PM ----------
sd_shadow said:
Windows 7 or 8?
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
Windows 8.1, sorry. I've already disabled driver signature reinforcement.
Itzel_55 said:
Windows 8.1, sorry. I've already disabled driver signature reinforcement.
Click to expand...
Click to collapse
is kindle listed like in screenshots in my last post?
sd_shadow said:
is kindle listed like in screenshots in my last post?
Click to expand...
Click to collapse
Ok, this is new...
It says:
Kindle Fire
-Kindle Orange Fastboot Mode | Gen 1
Itzel_55 said:
Ok, this is new...
It says:
Kindle Fire
-Kindle Orange Fastboot Mode | Gen 1
Click to expand...
Click to collapse
have you tried the install TWRP option in KFU?
may have to restart the Kindle a couple of times
sd_shadow said:
have you tried the install TWRP option in KFU?
may have to restart the Kindle a couple of times
Click to expand...
Click to collapse
Note: Now the Kindle is not being recognized when plugged in via USB. not sure why, no conditions have changed.
Tried to install TWRP via KFU. Says that...
Oops... something went wrong.
We are unable to locate your Kindle Fire.
Make sure it is plugged in and powered on.
<waiting for device >
I have already tried the options on the KF Unbricking Utility.
Itzel_55 said:
Note: Now the Kindle is not being recognized when plugged in via USB. not sure why, no conditions have changed.
Tried to install TWRP via KFU. Says that...
Oops... something went wrong.
We are unable to locate your Kindle Fire.
Make sure it is plugged in and powered on.
<waiting for device >
I have already tried the options on the KF Unbricking Utility.
Click to expand...
Click to collapse
could be low battery, power off, then try charging with wall charger
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
or maybe time for SoupKit
sd_shadow said:
could be low battery, power off, then try charging with wall charger
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
or maybe time for SoupKit
Click to expand...
Click to collapse
Ok, I wasn't running KFU through administrator. Smoooooth...
The Kindle is now recognized when plugged in through USB, still says
Kindle
-Kindle Orange Fastboot Mode | Gen 1
KFU says ADB Status: Online, Boot Status: Unknown
I tried installing TWRP through KFU and now it says
Setting normal bootmode
Please wait....
The system cannot find the path specified
The system cannot find the path specified
*******************************************************
* All Done! *
*******************************************************
Thats all folks, TWRP has been installed.
Please tap reboot on the kindle.
Press any key to continue....
So obviously, I tried rebooting again, and again, and still the same logo screen, no animation.
Note: In the device manager driver details, my kindles drivers are the same as the screenshot posted earlier.
Ok, just switched to a Windows 7 PC. I just successfully installed the drivers using the install_drivers.bat in the KFU.
In the Device Manager, it's now showing up as..
Android Phone
Android ADB Interface
The Kindle still shows as the white and orange splash screen, with no animation.
try my Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
just don't need the fastboot cable if already in fastboot mode
sd_shadow said:
try my Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
just don't need the fastboot cable if already in fastboot mode
Click to expand...
Click to collapse
THANK YOU!
I followed the video, and now I am at the point that the video left on.
So obviously I'm trying to install a ROM (Jellybean/ Cyanamogen). From this point, how would I go about doing that?
I just really don't want to screw this up again.
Itzel_55 said:
THANK YOU!
I followed the video, and now I am at the point that the video left on.
So obviously I'm trying to install a ROM (Jellybean/ Cyanamogen). From this point, how would I go about doing that?
I just really don't want to screw this up again.
Click to expand...
Click to collapse
Some more here http://forum.xda-developers.com/showthread.php?t=2828056
[How To][Videos] For Kindle Fire 1 [2014]
Sent from my XT894 using Tapatalk
sd_shadow said:
Some more here http://forum.xda-developers.com/showthread.php?t=2828056
[How To][Videos] For Kindle Fire 1 [2014]
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Once again, thanks for the help.
I am now happily running cyanogen.
Itzel_55 said:
Once again, thanks for the help.
I am now happily running cyanogen.
Click to expand...
Click to collapse
Ok, now I have another problem, with a completely different Kindle (6.3.2)
I've installed FFF and TWRP, and I'm trying to install Jellybean 4.2.2 on it through TWRP.
When I'm trying to move the ROM and GAPPS zips to the G: folder, it won't show up, even though the kindle is recognized as..
Android Phone
Android ADB Composite Interface
I'm almost positive this is because the Kindle has a passcode on it, which i forgot to remove before this whole process. This wouldn't be a huge deal, as a factory reset through TWRP would erase the pass code anyways. However, after I do the factory reset successfully, and then go to reboot-system, it will go back to the blue/white logo, then go to the white/orange unanimated logo, which it gets stuck at.
If there was a way to get the files onto the SD without going through the conventional way, it wouldn't be an issue, but i don't know of way to
In twrp wipe/advanced/SD card swipe to wipe
Or
Use adb
adb push filename /sdcard
Sent from my XT894 using Tapatalk
sd_shadow said:
In twrp wipe/advanced/SD card swipe to wipe
Or
Use adb
adb push filename /sdcard
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Tried the first one, didn't work.
What do you mean by the second one?
Itzel_55 said:
Tried the first one, didn't work.
Click to expand...
Click to collapse
what does that mean? error(s)?
What do you mean by the second one?
Click to expand...
Click to collapse
You used fastboot.exe to flash twrp and bootloader, right?
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.7.1.0-otter.img
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
so you have adb.exe that came with it, use adb.exe to push rom and gapps to sd card
place rom and gapps files in c:adb folder use exact file names
Code:
adb push romname.zip /sdcard
adb push gappsname.zip /sdcard
like I did in my [YouTube] OtterX ROM/TWRP/Bootloader [2014-05-08] @12:20

[Q&A] [How To][Root] Kindle Fire 1 update 6.3.3/6.3.4 and Flashing FFF/TWRP [2015]

[Q&A] [How To][Root] Kindle Fire 1 update 6.3.3/6.3.4 and Flashing FFF/TWRP [2015]
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Rooting Kindle Fire Update 6.3.3 and Flashing FireFireFire and TWRP (2014)
Click link here>> (http://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955) <<Click link here
Please feel free to share issues, questions and offer help
It is always best to use the Thanks button, in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on the topic described in the OP
[SIZE=+1]FAQs: For System Version 6.3.3 and 6.3.4[/SIZE]
[SIZE=+1]Q1: Can the Kindle Fire Utility root a Kindle Fire 1 with system version 6.3.3?[/SIZE]No, It can not​[SIZE=+1]Q2: Can the Kindle Fire Utility install a custom bootloader/recovery on a Kindle Fire 1 with system version 6.3.3?[/SIZE]No, It can not​[SIZE=+1]Q3: What can the Kindle Fire Utility with a Kindle Fire 1 with system version 6.3.3?[/SIZE]The included install.drivers.bat can install drivers on a PC
Once the Kindle is rooted, The Kindle Fire Utility can install Google Apps​[SIZE=+1]Q4: What can root a Kindle Fire 1 with system version 6.3.3?[/SIZE]SafeRoot Can [Windows/Linux/Mac]​[SIZE=+1]Q5: Can be used on Linux and Mac?[/SIZE] Yes see
The Easiest Way to Install Android's ADB and Fastboot Tools on Any OS
[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) by AshtonTS
[Guide] How To Setup And Use Fastboot by demkantor
problem with step 6 " Flashing FFF and TWRP without Fastboot Cable"
HI, in the stepvto putting on the last command (fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin fastboot -i 0x1949 oem idme bootmode 4000 fastboot -i 0x1949 reboot
), stays loading and does not advance, what i can do in this case? even is loading, says: waiting for the device. and nothing happen, now the kindle not start and stays on the logo.. and does not recognize my laptop or pc in Usb.
skins20 said:
HI, in the stepvto putting on the last command (fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin fastboot -i 0x1949 oem idme bootmode 4000 fastboot -i 0x1949 reboot
), stays loading and does not advance, what i can do in this case? even is loading, says: waiting for the device. and nothing happen, now the kindle not start and stays on the logo.. and does not recognize my laptop or pc in Usb.
Click to expand...
Click to collapse
How is kindle listed in device manager?
Sent from my XT894 using Tapatalk
sd_shadow said:
How is kindle listed in device manager?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
just say "kindle" in device manager.
skins20 said:
just say "kindle" in device manager.
Click to expand...
Click to collapse
Did you get drivers installed?
x2110311x said:
Well, I tried that, and I ended up bricking my kindle (most likely because I tried the experimental version of his binaries) and neither of my computers (one runs linux, one Windows) are able to see the device correctly. Windows shows it as an unknown device, but I have the fastboot drivers installed. That's why I said I need a factory cable, hoping that I'd be able to get it into fastboot to repair it
Click to expand...
Click to collapse
I have little experience with Linux, but windows will not work till drivers are correct.
Did you in device manager uninstall unknown device, remove driver if asked, install drivers with Kindle Fire Utility's install.drivers.bat, reboot pc and kindle
may take a few reboots to get it.
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
x2110311x said:
Well, I tried that, and I ended up bricking my kindle (most likely because I tried the experimental version of his binaries)
Click to expand...
Click to collapse
what binaries? su? you didn't install TWRP/FFF?
What is it doing now?
sd_shadow said:
I have little experience with Linux, but windows will not work till drivers are correct.
Did you in device manager uninstall unknown device, remove driver if asked, install drivers with Kindle Fire Utility's install.drivers.bat, reboot pc and kindle
may take a few reboots to get it.
Click to expand...
Click to collapse
I've done work with fastboot on my kindle fire with this computer before, probably only like a month ago, so I don't think that was the issu
sd_shadow said:
what binaries? su? you didn't install TWRP/FFF?
What is it doing now?
Click to expand...
Click to collapse
Sorry, I didn't mean to say binaries, I wrote that response in a rush.
I used Pokey9000's experimental version of fbmode.
Right now, whenever I try turning it on, the green LED stays on, and it just stays at the "Kindle Fire " screen. Neither fastboot nor adb are recognizing it at this point.
x2110311x said:
I've done work with fastboot on my kindle fire with this computer before, probably only like a month ago, so I don't think that was the issu
Sorry, I didn't mean to say binaries, I wrote that response in a rush.
I used Pokey9000's experimental version of fbmode.
Right now, whenever I try turning it on, the green LED stays on, and it just stays at the "Kindle Fire " screen. Neither fastboot nor adb are recognizing it at this point.
Click to expand...
Click to collapse
If all you used is the alt fbmode file, it is likely in fastboot mode, which just shows Kindle fire screen with no animation.
If there is animation on the kindle fire screen, it's bootlooping...
It turns out that it was just stuck in fastboot, and windows was having some issues. I did nothing to the drivers, and it worked fine after trying again
Stuck on Kindle Fire(Doesn't Change) screen
Hello,
Sorry if this is addressed somewhere else, as I have been unable to find it.
I successfully rooted my kindle fire, then made it all the way to the "fastboot" part of step 6 of the fff and twrp post. The command prompt stuck at waiting for device. The kindle fire is now stuck on the unchanging kindle fire logo. I have tried the unbricking utility, holding the power button down for 20 sec. removing the device and drivers under device manager(I saw this somewhere else).
Any help would be greatly appreciated!
dharangamer said:
Hello,
Sorry if this is addressed somewhere else, as I have been unable to find it.
I successfully rooted my kindle fire, then made it all the way to the "fastboot" part of step 6 of the fff and twrp post. The command prompt stuck at waiting for device. The kindle fire is now stuck on the unchanging kindle fire logo. I have tried the unbricking utility, holding the power button down for 20 sec. removing the device and drivers under device manager(I saw this somewhere else).
Any help would be greatly appreciated!
Click to expand...
Click to collapse
99% of the time drivers are the issue
How is it listed inn device manager?
---------- Post added at 05:05 PM ---------- Previous post was at 05:04 PM ----------
Which windows version? 7, 8?
It is listed as 'other devices' and then kindle in the drop down from that. I am running windows 8.1 at the moment.
Btw, thank you so much for the help you've already provided, the youtube video and your posts really helped me figure out how to troubleshoot and eventually root it successfully.
dharangamer said:
It is listed as 'other devices' and then kindle in the drop down from that. I am running windows 8.1 at the moment.
Btw, thank you so much for the help you've already provided, the youtube video and your posts really helped me figure out how to troubleshoot and eventually root it successfully.
Click to expand...
Click to collapse
With windows 8, You need to disable driver signature enforcement, before installing drivers, and use the Instal.drivers.bat from Kindle Fire Utility
That took care of it. Thank you so much!
help on kindle 7.5.1
How can I root my KINDLE fire hd whose firm got upgraded to 7.5.1 thanx a lot
nilnyl said:
How can I root my KINDLE fire hd whose firm got upgraded to 7.5.1 thanx a lot
Click to expand...
Click to collapse
see http://forum.xda-developers.com/fire-hd/help/how-to-root-kindle-fire-hd-7-firmware-7-t2931436
Can't root KindleFire
hi I am trying to root my kindle but it does work I use the Saferoot way and it does work
Corrupted settings.db- stuck in boot loop
Help, I toasted my Kindle Fire!
Ok, now that I got that out of the way, here's the details. I followed the steps from SDShadow's first post on how to root my Kindle Fire (6.3.3) and it worked great. Many thanks SDShadow! What followed was how I went off the reservation.
My purpose in rooting was to change 'mock_locations' to 1 so that I can receive GPS position over wifi and use my Kindle screen for navigation. Being focused on my end goal, I did not take the time to install Google Apps or FFF or TWRP. My mistake. Another thread (http://forum.xda-developers.com/showpost.php?p=19688907&postcount=1) gave directions to do update 'mock_locations', but as with others on that thread, I ran into permission errors. Unable to figure out SQLite3, but able to find the 'settings.db' using ESFileExplorer, I managed to corrupt the file.
Not knowing how to test the updated 'settings.db' in any way, I copied the corrupted version to my Kindle and rebooted. The Kindle never finished booting, and that's when I realized that I must have corrupted the file. But now I can't copy my backup file where it needs to go because my Kindle never finishes booting to give me access to ESFileExplorer on the Kindle. I still have adb access to the Kindle from my computer, but still get permission errors when I try to push a file.
Is there a workaround to upload my backup settings.db file through adb, or do I need a factory cable? Does the workaround involve installing FFF and TWRP through adb while the Kindle is in its reboot loop? Either way, can someone provide detailed instructions for that?
BTW, I figured out how to modify my settings.db using SQLite3 Browser on my PC. So I can actually upload my desired file, if I can figure out how. But if I could perform a check in some way, that would be good...
cwaskey said:
Help, I toasted my Kindle Fire!
Ok, now that I got that out of the way, here's the details. I followed the steps from SDShadow's first post on how to root my Kindle Fire (6.3.3) and it worked great. Many thanks SDShadow! What followed was how I went off the reservation.
My purpose in rooting was to change 'mock_locations' to 1 so that I can receive GPS position over wifi and use my Kindle screen for navigation. Being focused on my end goal, I did not take the time to install Google Apps or FFF or TWRP. My mistake. Another thread (http://forum.xda-developers.com/showpost.php?p=19688907&postcount=1) gave directions to do update 'mock_locations', but as with others on that thread, I ran into permission errors. Unable to figure out SQLite3, but able to find the 'settings.db' using ESFileExplorer, I managed to corrupt the file.
Not knowing how to test the updated 'settings.db' in any way, I copied the corrupted version to my Kindle and rebooted. The Kindle never finished booting, and that's when I realized that I must have corrupted the file. But now I can't copy my backup file where it needs to go because my Kindle never finishes booting to give me access to ESFileExplorer on the Kindle. I still have adb access to the Kindle from my computer, but still get permission errors when I try to push a file.
Is there a workaround to upload my backup settings.db file through adb, or do I need a factory cable? Does the workaround involve installing FFF and TWRP through adb while the Kindle is in its reboot loop? Either way, can someone provide detailed instructions for that?
BTW, I figured out how to modify my settings.db using SQLite3 Browser on my PC. So I can actually upload my desired file, if I can figure out how. But if I could perform a check in some way, that would be good...
Click to expand...
Click to collapse
best option is fastboot cable, but you can try some adb commands like
Code:
adb devices
you will need adb files
power off kindle, run command, turn on kindle, also can try
Code:
fastboot devices
if you get one of them to work we have some options
sd_shadow said:
best option is fastboot cable, but you can try some adb commands like
Code:
adb devices
you will need adb files
power off kindle, run command, turn on kindle, also can try
Code:
fastboot devices
if you get one of them to work we have some options
Click to expand...
Click to collapse
Code:
adb devices
does show my Kindle serial number. As I said, adb seems to be working, despite the fact that the Kindle doesn't complete the boot process.
I have not installed or tried fastboot on my PC, so I can't answer whether that works.
Edit: I should mention that when the Kindle was still running, I allowed just about every permission in the on-Kindle superuser app.

Bricked 1st Gen KF.

Howdy all, I have an old KF here that I have bricked. I'm stuck at the logo. I'm trying to issue shell commands and I get the "- exec '/system/bin/sh' failed: No such file or directory (2)" error. So far I've found that this means I screwed up my /system when I tried getting this thing back to stock. I cannot remember what I was running on it earlier today.
I do know that I downloaded a factory update.zip and installed that from TWRP. I wiped everything before hand. I'm afraid wiping the SD card after installing the update.zip may have caused me to be stuck at the logo without being able to issue shell commands? I've tried the KindleFireUtility and KindleUnbrickUtility and a few things with soupkit. Nothing is working.
I seem to have found a few hints that there are indeed workarounds to this problem without having to make or buy a factory cable. I'm terrible at soldering.. much better at typing in terminals.
If there is any help out there, I would massively appreciate it.
All I want to do is read a d*** book.
-Ellison
UPDATE:
I bought a fastboot cable.
It appears that I can boot in to fastboot mode (Kindle Fire logo, green light, and screen never dims) but I think at some point, the device gets lost. I installed the android bootloader ADB drivers for the fastboot mode. If I start the kindle without the factory cable and it boots normally and sits at the logo screen forever, it gets listed as an ADB device. While the kindle is still attached, I can reboot it in to what I am assuming is fastboot mode. My Windows10 rig sees it as a composite ADB bootloader interface. But I can't get unBrickUtility to do anything... the only thing I saw it do to the kindle was wipe the userdata. Other than that, UnBrickUtility cannot see my kindle in fastboot mode.
Unplugging my factory cable and plugging it back in causes the kindle to be completely unrecognized ( unknown usb device set address failed) on Windows 10.
I have soupkit running on a netbook... it tells me that my shell is damaged, which I know is the problem. But now I'm not sure what to do next as I can't get linux (mint) to recognize my kindle in fastboot mode either.
I really hope someone out there has been here before and can help. I'd love to see this thing running back to normal again.
related image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UPDATE: I FIXED IT.
What ultimately saved this device was being able to get in to fastboot mode. I bough the cable, flashed FFF and TWRP from fastboot mode. I then found I could not run shell commands. I fixed this by running
Code:
fastboot oem format
from fastboot mode. Then going back in to TWRP, I was able to mount /System and was then able to use Soupkit's kindle fire utility to fix the /sdcard. The version of TWPR I was using would not flash the stock update, so I downloaded and flashed that. Afet that installed, I was able to flash the stock update and now I'm up and running again! WOO! Thank you so much for the developers here!!!
Admin: can I get the thread title so reflect the fact that I have fixed this for future users? Thank you!
most likely need a fastboot cable
did you try command
adb devices
Sent from my KFFOWI using Tapatalk
bump for update!
Help
I have a question, I acquired from a guy from another repair shop a couple first gen kindle fire's and one has the red screen upon boot. I have tried to attach it to my pc and I get a USB driver error. Says can't install driver even though I have the driver installed. Also when it pops up in device manager it shows up as Otter 2 prod 4. Only thing I can think of is the person before me flashed the kindle fire hd bootloader to the device. Any ideas on a fix? I have a fastboot cable if that helps. Also when I attach the device to my computer it shows me fast boot with a flashing green light and a solid red one.
arsonone said:
I have a question, I acquired from a guy from another repair shop a couple first gen kindle fire's and one has the red screen upon boot. I have tried to attach it to my pc and I get a USB driver error. Says can't install driver even though I have the driver installed. Also when it pops up in device manager it shows up as Otter 2 prod 4. Only thing I can think of is the person before me flashed the kindle fire hd bootloader to the device. Any ideas on a fix? I have a fastboot cable if that helps. Also when I attach the device to my computer it shows me fast boot with a flashing green light and a solid red one.
Click to expand...
Click to collapse
otter 2 is kindle Fire 2 (2nd generation /2012)
Sent from my KFFOWI using XDA Labs
umm...
sd_shadow said:
otter 2 is kindle Fire 2 (2nd generation /2012)
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Yeah I know, that's what I was saying. Whoever had this thing before me flashed it with the kindle fire 2 rom or whatever not entirely sure. The model number is D10400 which is the first gen. Any clue if it can be saved? Right now I can't get it to connect to my PC or I'd just flash it
arsonone said:
Yeah I know, that's what I was saying. Whoever had this thing before me flashed it with the kindle fire 2 rom or whatever not entirely sure. The model number is D10400 which is the first gen. Any clue if it can be saved? Right now I can't get it to connect to my PC or I'd just flash it
Click to expand...
Click to collapse
i think Amazon used D10400 for both 1st and 2nd generation fires
at least there have been several people ask about a D10400 with a 2nd generation bootloader, trying to flash 1st generation bootloader has always ended up with a bricked device
but if it doesn't connect to pc now, cannot do anything anyways
Sent from my KFFOWI using XDA Labs
sd_shadow said:
i think Amazon used D10400 for both 1st and 2nd generation fires
at least there have been several people ask about a D10400 with a 2nd generation bootloader, trying to flash 1st generation bootloader has always ended up with a bricked device
but if it doesn't connect to pc now, cannot do anything anyways
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
It's a paperweight now lol. I got it to connect and flashed FFF to it as well at the rest of the software needed and when I typed in reboot into the fastboot cli it went dark and wont power back on now...oops lol
arsonone said:
It's a paperweight now lol. I got it to connect and flashed FFF to it as well at the rest of the software needed and when I typed in reboot into the fastboot cli it went dark and wont power back on now...oops lol
Click to expand...
Click to collapse
yep
Sent from my XT1060 using XDA Labs
... still need help. Can't seem to find any straight-forward threads on fixing partitions and/or /shell.
lsngregg said:
... still need help. Can't seem to find any straight-forward threads on fixing partitions and/or /shell.
Click to expand...
Click to collapse
don't use Unbrick utility, it doesn't work with newest versions 6.3.3 or 6.3.4
How to flash twrp and firefirefire with a Fastboot cable
Sent from my KFFOWI using XDA Labs
sd_shadow said:
don't use Unbrick utility, it doesn't work with newest versions 6.3.3 or 6.3.4
How to flash twrp and firefirefire with a Fastboot cable
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Currently, I'm able to attempt to flash the stock ROM.
I was able to fix the /sdcard by first running the "fastboot oem format" command in fasboot mode and then mouting /System in TWRP enabled being able to run shell commands. So I fired up my "bug" (a netbook running Mint) and had Soupkit fix sd card problems. That worked.
Now I'm stuck at not being able to flash the stock ROM because of a
Code:
E: unknown command [err_string]
getProp("ro.build.product") == blaze
E: unknown command [err_string]
E: Error executing updater binary in zip '/sdcard/update-kindle..... .zip'
lsngregg said:
Currently, I'm able to attempt to flash the stock ROM.
I was able to fix the /sdcard by first running the "fastboot oem format" command in fasboot mode and then mouting /System in TWRP enabled being able to run shell commands. So I fired up my "bug" (a netbook running Mint) and had Soupkit fix sd card problems. That worked.
Now I'm stuck at not being able to flash the stock ROM because of a
Click to expand...
Click to collapse
which twrp version?
Sent from my DROID Turbo using XDA Labs

Categories

Resources