Database Develop

[Q] Kindle Fire Unknown Device FFF Loop

Hey guys. I have been coming to these forums for a bit over a year now just reading posts and decided to make an account to get help with a problem I am having. I got a Kindle Fire almost a year ago and I rooted it successfully as soon as I got it. I installed FFF and TWRP to it and an ICS version loaded to it. However recently I tried to update the KF to the Jellybean version as well as update my TWRP version. Well, long story short, I got it stuck in the FFF fastboot.
Normally this wouldn't be a problem since I could just use the KFU to set the bboot back to normal, however the Kindle is also listed as an Unknown Device in my device manager and it says all the drivers are up to date. I tried manually overriding this by going into the device manager -> updating driver software -> and selecting from a list on my pc, however I either get an error saying there is no compatible file (which it is the sdk google usb driver downloaded for this exact reason so I know it should work) or I am getting the message saying windows thinks my driver is already up to date. I can't use the command prompt or adb to even locate the device. I am getting frustrated and need help. Thanks!

Ilumene said:
Hey guys. I have been coming to these forums for a bit over a year now just reading posts and decided to make an account to get help with a problem I am having. I got a Kindle Fire almost a year ago and I rooted it successfully as soon as I got it. I installed FFF and TWRP to it and an ICS version loaded to it. However recently I tried to update the KF to the Jellybean version as well as update my TWRP version. Well, long story short, I got it stuck in the FFF fastboot.
Normally this wouldn't be a problem since I could just use the KFU to set the bboot back to normal, however the Kindle is also listed as an Unknown Device in my device manager and it says all the drivers are up to date. I tried manually overriding this by going into the device manager -> updating driver software -> and selecting from a list on my pc, however I either get an error saying there is no compatible file (which it is the sdk google usb driver downloaded for this exact reason so I know it should work) or I am getting the message saying windows thinks my driver is already up to date. I can't use the command prompt or adb to even locate the device. I am getting frustrated and need help. Thanks!
Click to expand...
Click to collapse
You say you have FFF installed, right? What version...better yet...what does the boot logo look like? A yellow triangle?

soupmagnet said:
You say you have FFF installed, right? What version...better yet...what does the boot logo look like? A yellow triangle?
Click to expand...
Click to collapse
Yes, It had the yellow triangle with a flame in the middle...as to the version I don't know since I got a new pc since installation on the kindle and don't have those files available at the moment.

soupmagnet said:
You say you have FFF installed, right? What version...better yet...what does the boot logo look like? A yellow triangle?
Click to expand...
Click to collapse
I just fixed it after many, many hours of work. I found a solution by bootloading a usb stick of ubuntu and using firekit to reset it into normal boot where KFU couldn't. That guy who wrote the program and article is a savior. Here's the link for anyone else who has this same problem and thanks for the help! http://forum.xda-developers.com/showthread.php?t=1430038

[Q] Most in depth brick I'm sure you'll ever see. . .

Alright from the get go. I am running 10.3.1. I rooted using a tutorial from this site, it was rather easy. It only took me like 25 minutes and then to add the Play store, another 25. I had it running perfectly fine with GO launcher and it was the way i liked it till I saw NEXT launcher and I wanted that instead. I had GO still running and being a noob I thought if I installed NEXT launcher that it would be able to be set by default when I was asked and that would be it. From what I can tell they were fighting for the kindle's affection and it was at a constant refresh directly after the install. I then soft reset it and I'm stuck at a kindle fire screen. The animation is very fast, with no delay between ending and beginning again. I tried today using the KFU to no avail. I also tried to reinstall the drivers, nada. my computer in device manager does read it, "other devices" Kindle" Uppercase "K". I've uninstalled and reinstalled. I cannot get the SDK to work on my computer. Even with the correct environment setup, nothing. I've viewed plenty of other fixes, none help my situation, not because I don't think they do, but because I've tried. When I KFU I get a Waiting for Device, nothing further happens (40 minute waiting period). I tried to Recovery boot and I tried to push TWRP, nothing. I'm at a loss. To be clear idk what fastboot is and I don't know how to "code" anything so anything help in detail, would be awesome, you guy are a great community and I wouldn't dream going any where else for expertise. Thanks for any help. Btw AMA and I'll try and best accommodate so I can fix this

rekindle said:
Alright from the get go. I am running 10.3.1. I rooted using a tutorial from this site, it was rather easy. It only took me like 25 minutes and then to add the Play store, another 25. I had it running perfectly fine with GO launcher and it was the way i liked it till I saw NEXT launcher and I wanted that instead. I had GO still running and being a noob I thought if I installed NEXT launcher that it would be able to be set by default when I was asked and that would be it. From what I can tell they were fighting for the kindle's affection and it was at a constant refresh directly after the install. I then soft reset it and I'm stuck at a kindle fire screen. The animation is very fast, with no delay between ending and beginning again. I tried today using the KFU to no avail. I also tried to reinstall the drivers, nada. my computer in device manager does read it, "other devices" Kindle" Uppercase "K". I've uninstalled and reinstalled. I cannot get the SDK to work on my computer. Even with the correct environment setup, nothing. I've viewed plenty of other fixes, none help my situation, not because I don't think they do, but because I've tried. When I KFU I get a Waiting for Device, nothing further happens (40 minute waiting period). I tried to Recovery boot and I tried to push TWRP, nothing. I'm at a loss. To be clear idk what fastboot is and I don't know how to "code" anything so anything help in detail, would be awesome, you guy are a great community and I wouldn't dream going any where else for expertise. Thanks for any help. Btw AMA and I'll try and best accommodate so I can fix this
Click to expand...
Click to collapse
I guess from your words that you installed a new launcher and probably you forgot to fix permissions. After that you tried a lot of things without success. I recommend you to buy a factory cable, get into fastboot a then yowill be able to restore
Enviado desde mi KFTT usando Tapatalk 2

rekindle said:
Alright from the get go. I am running 10.3.1. I rooted using a tutorial from this site, it was rather easy. It only took me like 25 minutes and then to add the Play store, another 25. I had it running perfectly fine with GO launcher and it was the way i liked it till I saw NEXT launcher and I wanted that instead. I had GO still running and being a noob I thought if I installed NEXT launcher that it would be able to be set by default when I was asked and that would be it. From what I can tell they were fighting for the kindle's affection and it was at a constant refresh directly after the install. I then soft reset it and I'm stuck at a kindle fire screen. The animation is very fast, with no delay between ending and beginning again. I tried today using the KFU to no avail. I also tried to reinstall the drivers, nada. my computer in device manager does read it, "other devices" Kindle" Uppercase "K". I've uninstalled and reinstalled. I cannot get the SDK to work on my computer. Even with the correct environment setup, nothing. I've viewed plenty of other fixes, none help my situation, not because I don't think they do, but because I've tried. When I KFU I get a Waiting for Device, nothing further happens (40 minute waiting period). I tried to Recovery boot and I tried to push TWRP, nothing. I'm at a loss. To be clear idk what fastboot is and I don't know how to "code" anything so anything help in detail, would be awesome, you guy are a great community and I wouldn't dream going any where else for expertise. Thanks for any help. Btw AMA and I'll try and best accommodate so I can fix this
Click to expand...
Click to collapse
1. You should have a fast boot cable. I bricked last week and SkorPon sent me one in 7 days. I am now back in business running CM10.1
2. If you have the Kindle up and running and you're computer isnt recognizing - reinstall the drivers from Device Manager (Update Drivers button and manually find the Android drivers on the C: drive) This simple task has done wonders for me. Try it.

Recovery Mode - what to do?

Found my fire tablet with a black screen and in Amazon system recovery <3e> this morning - not sure how it got into that state & how to get out of it. To my knowledge I didn't press any combination of keys that would get me into that state. It had been only very low battery when I plugged it into the electrical socket last night but I didn't touch it until the morning when I found it in this black screen state.
From searching I think this is the Amazon version of Android System Recovery screen. The exact options are:
-------
Amazon system recovery <3>
Volume up/down to move highlight;
enter button to select.
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
----------
I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)"
(http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122)
I've had it for about a month without problems although a couple of days ago it kept trying to update several times in succession.
It has attempted to update a couple of times in the past, which put me into a panic at the time but when I'd check afterwards it would still show 5.0.1. firmware. Also the difference this time was that in the past it would only attempt to update the once, not several times in succession.
I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed. So when it happened in the past I didn't worry.
I'm not sure what to do (logically I'd assume I should just select the 1st option and reboot) but I'm not sure how I even got into this screen and if there's a reason for it so hoped someone might be able to advise me.
With thanks & crossed fingers
Frankie

Sorry - one other question!
Which key is the "enter button"?

FrankieChen said:
Sorry - one other question!
Which key is the "enter button"?
Click to expand...
Click to collapse
I've not used it but as we only have three buttons I'm going with the power button.

Pond-life said:
I've not used it but as we only have three buttons I'm going with the power button.
Click to expand...
Click to collapse
That's what I suspected!

Update
Well I ran out of power so the tablet switched off.
When I plugged it into an electricity socket, I decided to try the "reboot system now" option but it just rebooted and cam back to the same screen. I tried it about 4 times with the same result so I tried the "power down" option but it still returned to the same screen when switched back on.
Would really appreciate anyone's help.

Hmm, is there anything in the recovery logs?
Maybe reboot to bootloader, and see if it'll let you twrp to it from a pc, head to the twrp thread and grab the files.
fastboot boot TWRP_Fire_2.8.7.0.img
If it'll do that it's not on 5.1.1 at least, if not it might have tried to get there.

I haven't followed your instructions yet as after I posted last, it started to flash an error message along the lines of battery was too low to "factory reset" and something else - I don't recall what though. I didn't actually select any options apart from reboot and power down.
It was plugged in at the time but I unplugged it & replugged it in, in case for some reason it wasn't charging.
Since then the error message has stopped flashing and I just have a blank screen although you can see it is backlit. Pressing the power button has no effect

And that's on the charger it came with?
It's not looking good.

FrankieChen said:
...I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore...
...I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed....
Click to expand...
Click to collapse
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.

julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
True but the thread he's referring to does offer that function as an option in the batch file.
http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
Tomsgt has put together a little install bat (Amazon-Fire-5th-Gen-Install-Play-Store.zip)
Now includes Removing Advertising and Blocks Over the Air System Updates (02 Nov 2015)
Click to expand...
Click to collapse

julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
It's still useful information - thanks

It's on the charger it came with and it has finally returned to the same Amazon system recovery screen.
In regards to preventing the updates - I think I did that when I installed the google apps but it was the 1st time i ever did this (it's my 1st tablet), and as it was over a month ago I can't be sure - this is all very new to me.
There are 4 recovery logs, completely meaningless to me.
/cache/recovery/last_kmsg
/cache/recovery/last_log
/cache/recovery/last_log1
/cache/recovery/last_log2
the kmsg log zooms past too fast to read with endless pages dealing with "swapper/0"
the last_log seems to have stuff reffering to tzdata, build, product.cpu, ro.product, dalvik and so on . Log1 and log2 seem to be similar stuff but shorter.
Any idea what I should be looking for?

I hoped it would be readable, build number might yield clues.
Given it will show something seems worth trying to see if twrp can see it in bootloader.

It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
In desperation this morning I took the wipe data/factory reset option but it didn't work. It returned with the same screen and the error message
E:Error in /cache/recovery/dropbox_last_kmsg (Read-only file system)
I had installed the dropbox app but I had never actually signed in so there wouldn't be any data there.
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.

FrankieChen said:
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
Click to expand...
Click to collapse
At this point, if you have adb drivers (or are comfortable installing them) you may as well try sideloading an update bin file. Links are here. I'd get the 3820 file.
If you want to do this, post back and I or someone will give you the steps. Otherwise, Amazon has been good about replacing tablets if you just describe what you say in the 1st paragraph of your post.

FrankieChen said:
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
Click to expand...
Click to collapse
use the reboot to bootloader option
set pc up with fastboot and see if it can be booted into twrp by fastboot
http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548

Thank you for the replies. Sorry not to have responded earlier, I had a busy few days and although I have spent a lot of hours trying to read through the forums and find out about twrp, this is the 1st opportunity I have had to get back to trying to resolve the problem.
If I understand correctly, DoLooper has suggested sideloading an update bin file. (3820). I just started trying to do this but as the file to be downloaded is over 600MB and I am on a very slow connection it's showing it's going to take between 7-8 hours to download. If I take this option I will need to wait until tomorrow when I can get to a faster internet.
Pond-life, you have suggested that I
1. "use the reboot to bootloader option"
I'm presuming that this means that I have to select this option from the recovery screen on the tablet - does the tablet have to be attached to the pc via the USB cable when I select the option?
What should I expect once I have selected this option?
Would the tablet not need to be rooted to access the bootloader (as it isn't)?
2. "set pc up with fastboot and see if it can be booted into twrp by fastboot"
When I 1st got the tablet I had difficulties getting the adb drivers to install on my pc and after several days of trying I ended up doing it on another pc which I no longer have access to.
I have tried again to reinstall the drivers using rootjunkies file but again without success. I tried doing it using that method as I remember trying to do it that way (what felt like a billion times) though I don't remember if I finally ended up succeeding with that method or another.
I followed your link "http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9" and tried the 1st method
"[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05"
running the "adb-setup-1.4.3.exe" I get "0 files copied" after selecting "Yes to install ADB system-wide" which I recall was the problem (zero files copied) that I had previously.
Openning Device Manager after this does show any Fire or Android devices even when the tablet is connected so I'm assuming that the adb driver installation is failing.
I tried again with "adb-setup-1.3.exe". This time I had 4 files copied and got fire listed in the device manager but when I tried to update the driver I am not given the Android option in the list when I select the option to install driver.
I googled to see if anyone else had this error and I found that some peoplehad difficulties installing on XP but seems that MTP not being supported is the reason and it is resolved by installing WMP v10 and above. I have v11 so presume that's not the problem.
I don't have access to another computer at the moment to try and install the adb drivers but should be able to use another one tomorrow. Last time when I got the drivers to install it was on a vista machine so I wondered if that might have something to do with it.
The other thing that occurred to me was maybe there is something wrong with the cable as I only get the fire shown in the device manager for a few moments before it refreshes and then the fire is no longer shown.
I wondered if I should try to use USBDeview (as per http://www.inlovewithandroid.com/android-usb-connection-problems.html) to see if that is the problem. Certainly if I can the drivers installed on another pc it might suggest that there's a problem with mine.
Anyway, if I get the adb drivers to install successfully on another pc, could you explain what I am trying to do by "booted into twrp by fastboot"? Sorry to be so useless!
Huge thanks

Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.

Pond-life said:
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Click to expand...
Click to collapse
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.

FrankieChen said:
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
Click to expand...
Click to collapse
Better luck with the new one

Need help Rooting Kindle Fire HD Stuck In Demo Mode

Hello. I have a Kindle Fire HD that I need to root so I can get it back to normal working order.
A few things about this tablet:
-Will not hard reset
-Cannot get into settings
-Parental controls are on but unable to access due to inability to get into settings
I've even stumped the Amazon tech support guy.
Now, I want to attempt to root it. I've never done this before, and I've scoured the forums looking for a step-by-step guide on how to do this (with no success, everything is all over the place, and no-one seems to use the same 2 tools, so no guide is actually helpful).
I have the adb drivers and fastboot in one folder, and have Windows 10 in test mode, but thats as far as I've gotten.
Any help would be greatly appreciated.

Unbrick Fire 7 (2017, 7th gen)?

I decided to factory reset a completely stock kindle but doing so has soft bricked it. It will go through the "optimizing system" process and attempt to load the initial set up screen which only remains visible for a brief second until turning black. Once there, it remains black forever. I can access the recovery menu again, and do another factory reset, but it simply does the same thing. Yes the battery is 100% charged, and yes I have the factory cable as well. So it's my understanding that I will need to flash this device in order to recover it. I've been reading around and looking at all the tools available, but I'm not sure what the best course of action is.
This method appears to be a solution to my problem. However, I've never once in my life used Linux so I am unfamiliar with it. In the recovery menu, the option to update via adb is sadly not present. Is there ANY way I can flash a stock rom on this device without Linux? Or is my only option the process in the post that I just linked? This is all new to me, and I am very willing to learn, but any help would be astoundingly appreciated. Please, I'm so out of my depth.

U
sturmvogel2 said:
I decided to factory reset a completely stock kindle but doing so has soft bricked it. It will go through the "optimizing system" process and attempt to load the initial set up screen which only remains visible for a brief second until turning black. Once there, it remains black forever. I can access the recovery menu again, and do another factory reset, but it simply does the same thing. Yes the battery is 100% charged, and yes I have the factory cable as well. So it's my understanding that I will need to flash this device in order to recover it. I've been reading around and looking at all the tools available, but I'm not sure what the best course of action is.
This method appears to be a solution to my problem. However, I've never once in my life used Linux so I am unfamiliar with it. In the recovery menu, the option to update via adb is sadly not present. Is there ANY way I can flash a stock rom on this device without Linux? Or is my only option the process in the post that I just linked? This is all new to me, and I am very willing to learn, but any help would be astoundingly appreciated. Please, I'm so out of my depth.
Click to expand...
Click to collapse
You need to short the pin like it says.
You are running the 7th gen so you need to short it.
The 5th gen has the ADB sideload option.

Kenora_I said:
U
You need to short the pin like it says.
You are running the 7th gen so you need to short it.
The 5th gen has the ADB sideload option.
Click to expand...
Click to collapse
I know that is required for the linked method. But my biggest question is, if there exists a method by which I can flash it without Linux? I would think I could connect it via USB and do it from command line somehow.

sturmvogel2 said:
I know that is required for the linked method. But my biggest question is, if there exists a method by which I can flash it without Linux? I would think I could connect it via USB and do it from command line somehow.
Click to expand...
Click to collapse
The scripts are from linux.
There isnt a linux terminal for windows
Unless you count windows subsystem for linux