First off let me thank each of you that share your expertise to help others on this forum. I’m truly amazed and so impressed at the level and detail of the technical insight provided through this forum. I know it takes time and patience, so again I say thank you.
I’ve read through as many posts in this KFDH forum as I could find on this topic and tried just about every recommendation. There may not be a workable solution to this problem but I figured I’d pass it up to the gods for their insight and expertise!
First off, I am not the original owner of this device. I purchased from someone in the current condition with the idea that given enough time I might could resurrect it. I honestly have no idea if they acquired it through legitimate means.
This KFHD 7” is stuck at the Fastboot screen. I can reboot and see the Kindle Fire splash screen and then it goes straight to the fastboot screen.
I finally got the device drivers loaded under Win7. I had to modify the .INF file for the driver to load. It shows as a Kindle Fire/Android Composite ADB interface.
The hardware ID shows as:
USB\VID_1949&PID_0007&REV_0100
USB\VID_1949&PID_0007
I loaded the Android SDK but could never get ADB to connect/work.
I’ve downloaded and tried the KFHD_SR tool and the KF Fist Aide tools.
I can connect to the device via fastboot and successfully issue a reboot command fastboot -i 0x1949 reboot
A fastboot -i 0x1949 getvar product returns:
product: Tate-PVT-08
finished. total time: 0.002s
Prior to my last attempt to flash 7.2.1 from the KF System Recovery tool via fastboot I also received the serial info on a getvar product command (I masked the serial with XXXX but numbers were there)
product: Tate-PVT-08
finished. total time: 0.000s
XXXX000200000001 fastboot
If I try to change the boot mode via fastboot -i 0x1949 oem idme bootmode 4000 I receive
...
FAILED (remote failure)
finished. total time: 0.023s
I’ve tried twice to flash the boot, recovery and system and then erase the cache and userdata and via fastboot. All of it looks to work just fine. But rebooting brings it right back to fastboot.
I don’t have a factory cable, but seems like I didn’t need one since it already goes to fastboot and I can talk to the device.
So can anyone point me in a direction to further assess or attempt to resolve this brain teaser?
Thanks in advance for any assistance!
MAX
I wonder if somehow pin 1 and 4 is shorted on your kindle
That would probably force you into a permanent fastboot....
Sent from my GT-P3110 using xda app-developers app
mrkhigh said:
I wonder if somehow pin 1 and 4 is shorted on your kindle
That would probably force you into a permanent fastboot....
Sent from my GT-P3110 using xda app-developers app[/QUO
Try getting a fastboot cable either make one or buy one. Then follow these steps to install all drivers and necessary sdk files.
1. Download the sdk package from here http://developer.android.com/sdk/index.html#download
2. Open the file you downloaded and take the sdk folder and the sdk manager file and copy it to you hard drive. C:/sdk C Being the hard drive letter.
3. Now you need to open up sdk manager and go to tools menu and select manager addon sites. Now select user defined sites tab and select new and enter this site http://kindle-sdk.s3.amazonaws.com/addon.xml and click ok.
4. You need to click the following boxes to install the packages you need. TOOLS, ANDROID 4.0.3 (api 15), and EXTRAS. Then click install packages to install them.
5. Now you need to install JDK from here http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
6. Now you need to install your basic java from here http://www.java.com/en/download/index.jsp
7. Now you need to install kindle fire hd adb drivers from here http://forum.xda-developers.com/showthread.php?t=1890413
8. Now shut down your kindle and connect your kindle to your pc and let it boot all the way and unlock the lock screen.
You should now be able to use your fastboot cable by shutting down and plugging it in.
Sent From My Rooted Kindle HD 7"
Click to expand...
Click to collapse
Thank you for the responses.
After reading the response from mrkhigh, I thought i'd take a look. I pulled the motherboard off and took a close look at the microUsb connection and where it attached tot he circuit board. So now things make a little more sense
Looks like some type of liquid or something got inside to the motherboard.
So now i guess i'll part it out or something.
Anyone got any other ideas?
You cant clean it?
Brush dipped in contact cleaner and distilled water....
Dont spray contact cleaner directly on it ... they tend to eat stuff...
Sent from my GT-P3110 using xda app-developers app
Apparently i've now somehow corrupted or deleted the bootload on my KFHD. Is there anyway to restore it or do i now own a doorstop?
Did you clean it?
Monkey_max said:
Apparently i've now somehow corrupted or deleted the bootload on my KFHD. Is there anyway to restore it or do i now own a doorstop?
Click to expand...
Click to collapse
Did you follow mrkhigh's suggestion and clean it, and now it won't boot at all?
If so, you probably just need a factory cable. This XDA thread has the necessary pinout information, and there are several people selling them. I had an old MiniUSB to MicroUSB adaptor lying around that just got the necessary pins jumpered, and now any MiniUSB cable can be a factory cable.
It seems like (with fastboot) it's pretty hard to permanently brick these.
i have this exact problem. tried everything and it still goes right back to fastboot mode. any fix or anything?
Try this
http://forum.xda-developers.com/showthread.php?p=46993192
Sent from my XT907 using xda app-developers app
---------- Post added at 01:23 AM ---------- Previous post was at 01:22 AM ----------
Try this
http://forum.xda-developers.com/showthread.php?p=46993192
Sent from my XT907 using xda app-developers app
mrkhigh said:
Try this
http://forum.xda-developers.com/showthread.php?p=46993192
Sent from my XT907 using xda app-developers app
---------- Post added at 01:23 AM ---------- Previous post was at 01:22 AM ----------
Try this
http://forum.xda-developers.com/showthread.php?p=46993192
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply but the command fastboot -i 0x1949 oem idme bootmode 4000 only gives me a failed error "FAILED (remote failure)"
Idme 4000 is for the kf1, on the kf 2nd Gen's they are single digits if I remember right, I don't know the number offhand but try something like 1 or 2 and so on.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Related
Hello!
I'd appreciate it if anybody could make a backup image of his KFHD and post it here. Pls make a backup after 2nd part of rooting, as it said http://forum.xda-developers.com/showthread.php?t=1930656
Thx in advance!
Yes please .... you will help a lot of depressed users
This evening I'm going to set everything back to stock(except for su binary) on my system partition and will post it here when I finish. You will need a factory cable to enable fastboot
Sent from my SCH-I500 using xda app-developers app
In case you have tried downloading these files and were not able to, I have changed the links below(the others were disabled by dropbox for too much traffic). You must now unzip these files before use!!
Here are copies of backups I created from KFHD(Don't think this will work with KF2).
WARNING!!!- use at your own risk, I am not responsible for anything you do to your device. If you do not know what these .img files are for you should not be using them. See- http://forum.xda-developers.com/showthread.php?t=1930656 for directions on restoring with fastboot
System.img-(with su binary, vending.apk, and latest versions of go-launcher ex and apex launcher. Note: you will still need superuser.apk to obtain root and googleservicesframework.apk to access play store) These new links have zipped files, you MUST unzip before using :
https://docs.google.com/open?id=0B4lZEJI5lYeMR2k3NW1QRUR3dzg
System.img-(with su binary only. Note: same as above plus vending.apk), Also this file is named [system(2)] you may want to rename to [system] These new links have zipped files, you MUST unzip before using :
https://docs.google.com/open?id=0B4lZEJI5lYeMcldVWUwzd3BqRUE
I just noticed on Play that go-launcher ex has been updated so the above image does not have latest go-launcher ex, but will still work, just update in Play store
I messed up my kindle and now i have to restore a backup, do I have to have one of these cables that is mentioned? because in my country there is no kfhd much less these cables? please help this kfhd of mine has been giving me hard time since I got it.
You are the hero. Thank you.
hamidwt said:
I messed up my kindle and now i have to restore a backup, do I have to have one of these cables that is mentioned? because in my country there is no kfhd much less these cables? please help this kfhd of mine has been giving me hard time since I got it.
Click to expand...
Click to collapse
Yes you must have a factory cable to enable fastboot(unless you still have the ability to download and open an app with root access). Check out this link- http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9. They say they ship international and pricing is extremely cheap with what looks to be good quality. Personally I made mine, It is pretty simple if you have a spare micro usb cable, a 1k resistor, and a soldering iron. Just google factory cable kindle fire. Be very careful it might be simple but there is the potential to ruin your device and fry the usb board on your computer(at the minimum) if not done correctly. I do not say this lightly be absolutely sure of everything you are doing before attempting.
Works like a dream
Thanks for the image! I used it revive my dead kindle and it works!
Only thing right now is that my Date and time settings seems to have greyed out. I will need to figure this out as the date and time is wrong.
Also, i didn't use a factory cable - I had an issue with a blank screen appearing after the words Kindle Fire upon start up. So I got into fastboot by using the ADB: Fastboot reboot-bootloader
Cheers1
onemeila said:
Sorry this took so long just wanted to make sure I had the files straight and they worked
Here are copies of backups I created from KFHD(Don't think this will work with KF2).
WARNING!!!- use at your own risk, I am not responsible for anything you do to your device. If you do not know what these .img files are for you should not be using them. See- http://forum.xda-developers.com/showthread.php?t=1930656 for directions on restoring with fastboot
System.img-(with su binary, vending.apk, and latest versions of go-launcher ex and apex launcher. Note: you will still need superuser.apk to obtain root and googleservicesframework.apk to access play store) :
https://www.dropbox.com/s/y90vk1igk0ml5qv/system.img
System.img-(with su binary only. Note: same as above plus vending.apk), Also this file is named [system(2)] you may want to rename to [system] :
https://www.dropbox.com/s/t5rarzakk9p1to5/system (2).img
I just noticed on Play that go-launcher ex has been updated so the above image does not have latest go-launcher ex, but will still work, just update in Play store
Click to expand...
Click to collapse
onemeila said:
Yes you must have a factory cable to enable fastboot(unless you still have the ability to download and open an app with root access). Check out this link- http://forum.xda-developers.com/showpost.php?p=20380015&postcount=9. They say they ship international and pricing is extremely cheap with what looks to be good quality. Personally I made mine, It is pretty simple if you have a spare micro usb cable, a 1k resistor, and a soldering iron. Just google factory cable kindle fire. Be very careful it might be simple but there is the potential to ruin your device and fry the usb board on your computer(at the minimum) if not done correctly. I do not say this lightly be absolutely sure of everything you are doing before attempting.
Click to expand...
Click to collapse
thank you for your help
my kindle is working , I download and install easily but I have problem with Google play and also logging into Imo and I'm+ , I did some factory reset but still nothing ,that got me thinking there must be something wrong with system. so considering what I said , do I still need this cable?
hamidwt said:
thank you for your help
my kindle is working , I download and install easily but I have problem with Google play and also logging into Imo and I'm+ , I did some factory reset but still nothing ,that got me thinking there must be something wrong with system. so considering what I said , do I still need this cable?
Click to expand...
Click to collapse
No you wouldn't need a factory cable but if the device is still working then the best thing would be to figure what mods you made to the system and reverse them before flashing an image in fastboot. If you cant figure that out and need to flash the system.img, the post above said they were able to get into fastboot through cmd window(though I think because the device was frozen, I was not able to do this with my working device, then again i could be doing something wrong). I know that if you use the app- Rom Toolbox Lite and under the rebooter section there is an option to reboot bootloader, that will boot into fastboot. Then you can use a regular cable.
---------- Post added at 11:37 AM ---------- Previous post was at 11:31 AM ----------
Arithon said:
Thanks for the image! I used it revive my dead kindle and it works!
Only thing right now is that my Date and time settings seems to have greyed out. I will need to figure this out as the date and time is wrong.
Also, i didn't use a factory cable - I had an issue with a blank screen appearing after the words Kindle Fire upon start up. So I got into fastboot by using the ADB: Fastboot reboot-bootloader
Cheers1
Click to expand...
Click to collapse
Glad it helped. With the date and time mine are grayed out as well(think its like that from factory, don't remember noticing since date and time were changed during initial setup), you just need to select the right time zone and it automatically changes to proper time.
Also are you still able to get into fastboot via cmd prompt now that your device is working properly? If so what commands did you use?
cmd
onemeila said:
No you wouldn't need a factory cable but if the device is still working then the best thing would be to figure what mods you made to the system and reverse them before flashing an image in fastboot. If you cant figure that out and need to flash the system.img, the post above said they were able to get into fastboot through cmd window(though I think because the device was frozen, I was not able to do this with my working device, then again i could be doing something wrong). I know that if you use the app- Rom Toolbox Lite and under the rebooter section there is an option to reboot bootloader, that will boot into fastboot. Then you can use a regular cable.
---------- Post added at 11:37 AM ---------- Previous post was at 11:31 AM ----------
Glad it helped. With the date and time mine are grayed out as well(think its like that from factory, don't remember noticing since date and time were changed during initial setup), you just need to select the right time zone and it automatically changes to proper time.
Also are you still able to get into fastboot via cmd prompt now that your device is working properly? If so what commands did you use?
Click to expand...
Click to collapse
fastboot reboot-bootloader
---------- Post added at 02:23 AM ---------- Previous post was at 01:58 AM ----------
Arithon said:
fastboot reboot-bootloader
Click to expand...
Click to collapse
sorry it was "adb reboot-bootloader"
Arithon said:
fastboot reboot-bootloader
---------- Post added at 02:23 AM ---------- Previous post was at 01:58 AM ----------
sorry it was "adb reboot-bootloader"
Click to expand...
Click to collapse
Are you still able to do this with the device working? I couldn't.
adb
onemeila said:
Are you still able to do this with the device working? I couldn't.
Click to expand...
Click to collapse
Yes - but i think you must turn it (ADB) on in 'Settings'....
Another Beg!
I am adding a BEG!!!
Anyone have a system.img file for the 10.2.1 Kindle Fire 2 device?
Please..
I did a backup when I was on 10.1.3 and it wont let me restore that system..img file!!!!!!!
I get this error!
fastboot -i 0x1949 flash system system.img
sending 'system' (907264 KB)...
FAILED (remote: data too large)
finished. total time: 0.188s
[edit:] nevermind
Thanks the image files has saved my Kindle Fire HD!
I know this is a system.img but I really need a boot.img for the fire hd 7" can someone please post one it would be greatly appreciated thanks
dark_samus said:
I know this is a system.img but I really need a boot.img for the fire hd 7" can someone please post one it would be greatly appreciated thanks
Click to expand...
Click to collapse
Look here:
http://forum.xda-developers.com/showthread.php?t=1951254
Hello,
Let me start by saying I have looked a searched through several other threads but cannot seem to find anything that mimics my problem 100%. I had rooted the Kindle Fire HD 7" a few weeks ago and have been going along with no problem. One day (cannot remember what I installed) the KFHD crashed on me and wanted me to Restore the device in a "download mode" type of screen (used the volume buttons to select restore and power to confirm selection.) The device restarted just fine and was working normally. I went through the KFFirstAide root process again, root checker told me it was rooted. Starting using the options in KFFA to diable OTA, install play store, install google apps, installed Holo Launcher.. Some of the programs did not seem to install properly and didn't like the way things were behaving so I went to the Settings/Device/Restore to Factory Defaults...
After that process finished I am not at an Android setup screen. It has a blue Welcome at the top, select Language below that, Start below that, and a green outlined Android guy below that. When I hit start it says Just a sec.... and eventually get the message Setup Wizard has Stopped.. I can no longer see Kindle Fire ADB in the Device Manger.. Nothing seems to work on KFFA.. I have tried using the fastboot command in a command prompt (says waiting for device) and never does anything..
Basically I would like to know, what steps I may have to take to get the device to load properly again, and hopefully root the device again. IIRC the software version I last saw was 7.3.1...
Thank you for your time and assistance and appologize if it has been discussed before, but I just couldn't seem to find it and not sure what this problem is called to be able to properly search for it..
Before. it says "waiting for device", you should have the kindle powered off and disconnected from the computer. Plug it in after it says "waiting for device" and it should boot into fastboot.
Sent from my CyanogenFire HD7
Krsmqn said:
Before. it says "waiting for device", you should have the kindle powered off and disconnected from the computer. Plug it in after it says "waiting for device" and it should boot into fastboot.
Sent from my CyanogenFire HD7
Click to expand...
Click to collapse
Yep, it is powered off and the cable is disconnected. I plug it in after it says waiting for device and it powers up to the Welcome Setup screen.the command prompt on the computer still says < waiting for device >
When I hold one of the volume buttons and press power on it says Safe Mode at the bottom of the screen. Might there be something I can work with in that? Is there another boot method similar to "download" mode on the GalaxySIII?
jhutch825 said:
Yep, it is powered off and the cable is disconnected. I plug it in after it says waiting for device and it powers up to the Welcome Setup screen.the command prompt on the computer still says < waiting for device >
Click to expand...
Click to collapse
Sounds like you just need to get a factory cable and use that to get into fastboot mode. If the device is not recognized by adb using the fastboot cmds will not work on the 7" variant, that only works on the 8.9".
Is there a way to make on or do I have to order it?
Just ordered a factory cable ... what should I do when I get it?
onemeila said:
Sounds like you just need to get a factory cable and use that to get into fastboot mode. If the device is not recognized by adb using the fastboot cmds will not work on the 7" variant, that only works on the 8.9".
Click to expand...
Click to collapse
You can get fast boot on the KFHD7 using the stock cable and adb by issuing the adb commands then running "adb reboot bootloader" I think it was. I did it this afternoon when coming off the stock ROM to cm10.1
Edit: n/m, I though he had adb but it wouldn't boot fastboot on a restart with the cable. Guess it doesn't help his case if adb itself won't show.
-Ken
---------- Post added 30th April 2013 at 12:03 AM ---------- Previous post was 29th April 2013 at 11:41 PM ----------
jhutch825 said:
Just ordered a factory cable ... what should I do when I get it?
Click to expand...
Click to collapse
Since your boot loader is still starting up okay, when powered up with the factory/fastboot cable attached it should jump straight into fastboot. You can then use the fast boot command line tool in the adb kit from Google to push either a backup you made previously, or one from a recovery thread back onto your device. Check in the android development section, there's plenty on info on using fastboot.
-Ken
codepoet82 said:
You can get fast boot on the KFHD7 using the stock cable and adb by issuing the adb commands then running "adb reboot bootloader" I think it was. I did it this afternoon when coming off the stock ROM to cm10.1
Edit: n/m, I though he had adb but it wouldn't boot fastboot on a restart with the cable. Guess it doesn't help his case if adb itself won't show.
-Ken
---------- Post added 30th April 2013 at 12:03 AM ---------- Previous post was 29th April 2013 at 11:41 PM ----------
Since your boot loader is still starting up okay, when powered up with the factory/fastboot cable attached it should jump straight into fastboot. You can then use the fast boot command line tool in the adb kit from Google to push either a backup you made previously, or one from a recovery thread back onto your device. Check in the android development section, there's plenty on info on using fastboot.
-Ken
Click to expand...
Click to collapse
Ok. I will try that forum when it arrives.. To the best of my knowledge, I had not created a backup at any time so I will search out something from the Recovery Thread.
Thank you
-Joe
I am just 100% confused now.. I have searched and searched and everything I am reading is just making me more confused.
The cable will put the device into fast boot and will show up in Device Manager as an ADB Device.. I ran option 3 on KFFA and I don't believe the entire system image downloaded as now I am stuck on a screen with a red triangle asking to reboot or restore the device. Neither option does anything.
I have looked in recovery threads for fresh stock images but only find links and directions to TWRP.. Which, if I understand correctly, needs a 2nd bootloader.. And still will need a fresh stock image from amazon. Also, in KFFA it says to connect the device with a normal cable, not fastboot cable, in ADB mode for TWRP and the second bootloader.. I cannot get into the KF to enable ADB like it asks because I cannot get anything to load..
I have downloaded kfhd7-amazon-os-7.3.1 from goo.im and it comes in a zip file. I am not really sure of what to do..
I looked in the Android Development section of this forum and there are only 18 threads that don't talk about fastboot either. Do I need to go to a general Android Development section, not in the Kindle Fire Forum Sections?
I just want to go back to 100% factory original and start over from there..
Also, the KindleFireFirstAide dropbox seems to be overloaded and suspended, so I cannot get the images from there at the moment through their tool.
jhutch825 said:
Just ordered a factory cable ... what should I do when I get it?
Click to expand...
Click to collapse
You didn't need a fast boot cable. All you needed to do was setup ADB drivers and issue the command "adb reboot bootloader"
Sent from my KFTT using xda app-developers app
-a- said:
You didn't need a fast boot cable. All you needed to do was setup ADB drivers and issue the command "adb reboot bootloader"
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Even though the device was no longer showing up in the windows device manager as Kindle Fire ADB? The Kindle was being recognized under Mobile Devices.
I don't know if I will be able to do that now that I used Fastboot to reload Factory Reset through KindleFire First Aide (option 3).. I don't think the entire system.img downloaded before it tried to install it and their dropbox server is down now so I can't rerun the command right now.
Solved
Found a link, finally, to onemeila's KFHD System.img Restore tool... Used the fastboot cabled and got it installed and everything seems to be running flawlessly.
Same Story Here...
jhutch825 said:
Even though the device was no longer showing up in the windows device manager as Kindle Fire ADB? The Kindle was being recognized under Mobile Devices.
I don't know if I will be able to do that now that I used Fastboot to reload Factory Reset through KindleFire First Aide (option 3).. I don't think the entire system.img downloaded before it tried to install it and their dropbox server is down now so I can't rerun the command right now.
Click to expand...
Click to collapse
Hello, after looking through many, many threads..I have finally found this one. Same story here..I have not order the factory cable. I have the original cable that came with my kindlehd. Before I go and buy the cable I wanted to see if this question can be addressed?
Dnoob, it's been a while don't remember the solution but I did get a factory cable and worked everything out through fast boot
Sent from my Amazon Kindle Fire HD using Tapatalk now Free
Hey all, so my sister wanted me to help he install CM10 on her Kindle so I followed Hashcode's guide in the development forum. I carefully read the instructions step by step but for some reason, the Kindle ended up bootlooping on the Kindle Fire logo.
I proceeded to order a fastboot cable but it never arrived so I ended up creating my own this afternoon. It managed to get the Kindle into fastboot mode just fine and here's where things really go south. I downloaded the SRT from here http://forum.xda-developers.com/showthread.php?t=1951254 and chose option 5 "Check fastboot status" to ensure the Kindle is correctly recognised. Then for some reason the Kindle rebooted and is now stuck in a bootloop that I cannot get out of with my homemade fastboot cable.
It will boot showing the Kindle Fire logo, then immediately show the "fastboot" screen and then reboot immediately after that all in the space of 2 seconds. Rinse and repeat. So is this Kindle done for? I've tried normal USB as well as the fastboot cable but it just seems to constantly reboot as described to no avail. What I don't get is why it will go to the fastboot screen even if I try turning it on "without being plugged in" / "plugged in with normal cable" / "plugged in with factory cable".
Is it possible my home made factory cable is a dud and if I get a proper one I can fix it? Or maybe the battery is dead and it doesn't have enough charge to stay on? Any help would be greatly appreciated.
Ok, spent the whole day reading over threads on XDA and it seems like the Kindle is done for
Doesn't seem like anyone has ever recovered from this before. *sigh* my first ever Android device brick
http://forum.xda-developers.com/showthread.php?t=2146480
http://forum.xda-developers.com/showthread.php?t=1943437
http://forum.xda-developers.com/showthread.php?t=2314715
So with the fast boot cable plugged in you don't get a fast boot logo that stays booted?
Sent from my XT907 using xda app-developers app
---------- Post added at 02:15 AM ---------- Previous post was at 02:06 AM ----------
Might make sure you have the proper fast bit drivers then try a few commands in fast boot to attempt to exit fast boot
fastboot -i 0x1949 reboot
then try to use the kindle fire HD restore tool instead I just don't trust the ffaide tool.
Sent from my XT907 using xda app-developers app
mrkhigh said:
So with the fast boot cable plugged in you don't get a fast boot logo that stays booted?
Sent from my XT907 using xda app-developers app
---------- Post added at 02:15 AM ---------- Previous post was at 02:06 AM ----------
Might make sure you have the proper fast bit drivers then try a few commands in fast boot to attempt to exit fast boot
fastboot -i 0x1949 reboot
then try to use the kindle fire HD restore tool instead I just don't trust the ffaide tool.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Ahhh!!! I'm so happy right now!! Thank you so so much mrkhigh. I had ENTIRELY given up on the fastboot screen because it only ever showed up for a second or two before bootlooping. I thought it was a corrupt bootloader and I tried so many times to reflash the bootloader in those couple of seconds but I'd always be stuck on the "waiting for device" screen.
I then tried your command "fastboot -i 0x1949 reboot" and it worked. So I'm now thinking simple commands may do the trick. I then entered the command "fastboot -i 0x1949 oem idme bootmode 4000" and now it's no longer looping.
Attempting to restore my original boot.img, recovery.img and system.img files now and hopefully it boots!
By the way, as I was following Hashcode's guide http://forum.xda-developers.com/showthread.php?t=2128848
It required downgrading the bootloader to 7.2.3. I'm pretty sure I was updated to the latest version before this whole debacle. Will my original backups work with the older bootloader than I downgraded to?
EDIT - Nevermind! Everything restored back to stock!! All working perfectly!
Thank you so so much!
I think you are doing a complete restore so you should be fine but as long as you have fast boot you'll get it.
Just get back to normal a second attempt if you follow his directions exactly step by step you will succeed.
Make sure you have a rom on it to flash .
it isn't a suggestion as he makes it sound you WILL boot loop if you do not.
Sent from my XT907 using xda app-developers app
mrkhigh said:
I think you are doing a complete restore so you should be fine but as long as you have fast boot you'll get it.
Just get back to normal a second attempt if you follow his directions exactly step by step you will succeed.
Make sure you have a rom on it to flash .
it isn't a suggestion as he makes it sound you WILL boot loop if you do not.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Ok, tried a second time at installing a 2nd bootloader and TWRP and it worked. I've now got Kinology installed on the Kindle and all is well. So relieved I didn't kill my sister's device!
I was considering binning the tablet because my warranty is out and the symptoms matched exactly with all the other threads I linked and there was never a solution other than to return the Kindle.
If anyone ever runs into the same problem, hopefully they can fix it the same way I did with the command:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
So now you have twrp working. Gratz! Kinology is a solid Rom, but there's a handful of others that offer way more options. You have the luxury now of being able to "test drive" each Rom, so long as you back up your "old reliable" in twrp before you have a go at it.
I suggest Hashcodes cm10.1, pacman or jellybeer. Remember though, these roms have been modified to run on our device... so expect some minor issues. Read up on each before flashing.
Good luck!
Sent from my JellyBeer Fire HD
keyman91 said:
Ok, tried a second time at installing a 2nd bootloader and TWRP and it worked. I've now got Kinology installed on the Kindle and all is well. So relieved I didn't kill my sister's device!
I was considering binning the tablet because my warranty is out and the symptoms matched exactly with all the other threads I linked and there was never a solution other than to return the Kindle.
If anyone ever runs into the same problem, hopefully they can fix it the same way I did with the command:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
Click to expand...
Click to collapse
my kindle is stuck in fastboot mode but running this command just gives me a failed error
"FAILED (remote failure)"
Does it respond your product id when you type
Fastboot -i 0x1949 getvar product
If it doesn't then you do not have fast boot communicating on your computer.
Sent from my GT-P3110 using xda app-developers app
I have my nephews kindle fire hd 7 was using kffaide on it flashed it now when it boots up I get a red screen wipe across then it goes straight to fastboot and stays there is this a brick how can I fix this tried a few methods yes I have fastboot cable running windows 7 anyone how can I fix this to get kindle going again also I forgot to mention I have tried srt tool as well but still get red wipe then stuck in fboot mode nothing seems to work ahhhhhhhhhhhhhhhhh
You tried reflashing the bootloader? If you haven't then try that, but please remember to verify the bootloaders md5sum before flashing it or your kindle could end up worse off(it wouldn't power on).
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You tried reflashing the bootloader? If you haven't then try that, but please remember to verify the bootloaders md5sum before flashing it or your kindle could end up worse off(it wouldn't power on).
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
thanks for answering im not a noob but can you explain more on what your saying as I don't want to be worse of than I am now thanks
kindle product soho-pvt-prod-07
I'm going to throw my kindle.... I just typed a very lengthy description and then a stupid tapatalk notification came up right next to the post button as I was hitting it and cleared my entire post... Anyways i thought at first that was a signature but if this kindle is indeed a 2013 model then your first problem was attempting to isntall 2nd bootloader and a custom rom, becuase thats not possible on the 2013 model, also would explain why srt and kffa wouldnt work, their images are incompatible, so before i post any further instructions, please tell me whether i am correct because if its a 2013 model i think i can help you fix it thanks to someone posting the images recently but you are going to have to manually fix this, not too difficult.
Sent from my Amazon Kindle Fire HD using Tapatalk
my nephew got it for Christmas put a pin in it and locked him self out of it gave to me sort for him now I realise I have gone abut getting into it all wrong and now have this problem if you can help me that would be awesome I don't know how I can find out if it is a 2013 model????all I know is it was brought for xmas I will do some looking on the net honestly thanks for your time
stunts513 said:
I'm going to throw my kindle.... I just typed a very lengthy description and then a stupid tapatalk notification came up right next to the post button as I was hitting it and cleared my entire post... Anyways i thought at first that was a signature but if this kindle is indeed a 2013 model then your first problem was attempting to isntall 2nd bootloader and a custom rom, becuase thats not possible on the 2013 model, also would explain why srt and kffa wouldnt work, their images are incompatible, so before i post any further instructions, please tell me whether i am correct because if its a 2013 model i think i can help you fix it thanks to someone posting the images recently but you are going to have to manually fix this, not too difficult.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
my nephew got it for Christmas put a pin in it and locked him self out of it gave to me sort for him now I realise I have gone abut getting into it all wrong and now have this problem if you can help me that would be awesome I don't know how I can find out if it is a 2013 model????all I know is it was brought for xmas I will do some looking on the net honestly thanks for your time
stunts513 said:
I'm going to throw my kindle.... I just typed a very lengthy description and then a stupid tapatalk notification came up right next to the post button as I was hitting it and cleared my entire post... Anyways i thought at first that was a signature but if this kindle is indeed a 2013 model then your first problem was attempting to isntall 2nd bootloader and a custom rom, becuase thats not possible on the 2013 model, also would explain why srt and kffa wouldnt work, their images are incompatible, so before i post any further instructions, please tell me whether i am correct because if its a 2013 model i think i can help you fix it thanks to someone posting the images recently but you are going to have to manually fix this, not too difficult.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
im being told in another thread in xda it is indeed a 2013 model they our also saying to me about finding the images http://forum.xda-developers.com/showthread.php?t=2096888&page=325
Someone just posted the images today if I remember correctly, think he was going to verify their md5sum or something first so I might wait. This is the thread: http://forum.xda-developers.com/showthread.php?t=2650596
I would wait till they confirm they are all good before using them but I doubt it would make the device any worse since it isn't flashing the bootloader or anything, just the boot and system partitions mainly. I might modify the SRT script to use the new images and post my own SRT to help out. I'm in the midsts of debugging a ROM I'm working in so I'll only do it if I have some time free( like when I have questions to ask and there's no devs available to question). Might even tweak his script a bit, not sure how it works but I may add a md5sum checker to double check that the images didn't corrupt if it doesn't have one in it, I know nothing is more annoying than flashing your device back and getting a error from fastboot about size mismatch or something.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Someone just posted the images today if I remember correctly, think he was going to verify their md5sum or something first so I might wait. This is the thread: http://forum.xda-developers.com/showthread.php?t=2650596
I would wait till they confirm they are all good before using them but I doubt it would make the device any worse since it isn't flashing the bootloader or anything, just the boot and system partitions mainly. I might modify the SRT script to use the new images and post my own SRT to help out. I'm in the midsts of debugging a ROM I'm working in so I'll only do it if I have some time free( like when I have questions to ask and there's no devs available to question). Might even tweak his script a bit, not sure how it works but I may add a md5sum checker to double check that the images didn't corrupt if it doesn't have one in it, I know nothing is more annoying than flashing your device back and getting a error from fastboot about size mismatch or something.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
thanks for getting back to me and thanks for the time you have spent trying to help me I will look into this honestly thanks for the help m8 with this problem I have hopefully when I have a proper look a bit later on I may be able to get this brand new kindle up and running hope you don't mind if I get lost or stuck at any point I can send ya a message and you may be able to help if I get stuck as your knowledge seems far more than I know once again thankyou
i have the images how would I now apply them to the kindle I take it it will be with fast boot but how to apply them to get this kindle running again
Something like putting it in fastboot and open a command prompt, now here's to hoping you have basic command line experience. I would recommend putting the images you downloaded into for instance the same folded as the fastboot command in SRT, or if you have another fastboot command that is fine as well. Idk if SRT defaultly put its images in the same folder as fastboot, but if it did feel free to deleted them to avoid confusion. Anyways for the commands, CD into the directory containing the fastboot commands that you placed your images in. Now I believe this is what you want to run:
Code:
fastboot -i 0x1949 flash boot stock-boot.IMG
Fastboot -i 0x1949 flash system stock-system.IMG
Fastboot -i 0x1949 flash recovery stock-recovery.IMG
Note that I am not positive on the file names but if it was incorrect just change the name in the command of the IMG file as it needs be. Wouldn't recommend flashing the bootloader unless you have to, bad bootloader flashes result in hard bricks so I avoid flashing it unless absolutely necessary, and also note boot is not bootloader, boot is the kernel+intramfs. Also don't flash the boot0block image at all. That contains that persons serial number, Mac address and other info, idk why he put it in there, its kinda personal.
Sent from my Amazon Kindle Fire HD using Tapatalk
thanks
stunts513 said:
Something like putting it in fastboot and open a command prompt, now here's to hoping you have basic command line experience. I would recommend putting the images you downloaded into for instance the same folded as the fastboot command in SRT, or if you have another fastboot command that is fine as well. Idme if SRT defaultly put its images in the same folder as fastboot, but if it did feel free to deleted them to avoid confusion. Anyways for the commands, CD into the directory containing the fastboot commands that you placed your images in. Now I believe this is what you want to run:
Code:
fastboot -i 0x1949 flash boot stock-boot.IMG
Fastboot -i 0x1949 flash system stock-system.IMG
Fastboot -i 0x1949 flash recovery stock-recovery.IMG
Note that I am not positive on the file names but if it was incorrect just change the name in the command of the IMG file as it needs be. Wouldn't recommend flashing the bootloader unless you have to, bad bootloader flashes a hard bricks so I avoid flashing it unless absolutely necessary, and also note boot is not bootloader, boot is the kernel+intramfs. Also don't flash the boot0block image at all. That contains that persons serial number, Mac address and other info, idk why he put it in there, its kinda personal.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
thanks for the info m8 and yeah I got a bit of knowledge with command prompt,thanks for the advice ill see what happens thanks again
you online now???question.
stunts513 said:
Something like putting it in fastboot and open a command prompt, now here's to hoping you have basic command line experience. I would recommend putting the images you downloaded into for instance the same folded as the fastboot command in SRT, or if you have another fastboot command that is fine as well. Idk if SRT defaultly put its images in the same folder as fastboot, but if it did feel free to deleted them to avoid confusion. Anyways for the commands, CD into the directory containing the fastboot commands that you placed your images in. Now I believe this is what you want to run:
Code:
fastboot -i 0x1949 flash boot stock-boot.IMG
Fastboot -i 0x1949 flash system stock-system.IMG
Fastboot -i 0x1949 flash recovery stock-recovery.IMG
Note that I am not positive on the file names but if it was incorrect just change the name in the command of the IMG file as it needs be. Wouldn't recommend flashing the bootloader unless you have to, bad bootloader flashes result in hard bricks so I avoid flashing it unless absolutely necessary, and also note boot is not bootloader, boot is the kernel+intramfs. Also don't flash the boot0block image at all. That contains that persons serial number, Mac address and other info, idk why he put it in there, its kinda personal.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
im running cmd with fastboot now to flash the images my question is if you can help flashed stockboot image okay next stocksystem that has come back as failed fastboot is now flashing stock recovery but it just seems to be sitting there any ideas on how long the process should take not sure if something is up and not sure this gonna work if stock recovery failed any ideas worried about unplugging or turning it off.
Weird, recovery is rather small compared to the system image, I wonder why it was hanging. I normally don't advise on pulling during a fastboot flash, but what else can you do if its hanging... I would just attempt again. If all the images are in a zip check the CRC listed, and I don't know exactly how to do that offhand, think it depends on the program you use, think some list it in a column, I use Linux a lot and I haven't ever checked crc's, I usually go by md5sums. Sorry I can't be of much help other then say try again, this is kinda the only images we have as if yet and the kfhd2 is kinda new territory sorta so we have to see if we can get it working like we did on the previous one, really shouldn't be any learning to it since it is just a modified version of the kfhd7".
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Weird, recovery is rather small compared to the system image, I wonder why it was hanging. I normally don't advise on pulling during a fastboot flash, but what else can you do if its hanging... I would just attempt again. If all the images are in a zip check the CRC listed, and I don't know exactly how to do that offhand, think it depends on the program you use, think some list it in a column, I use Linux a lot and I haven't ever checked crc's, I usually go by md5sums. Sorry I can't be of much help other then say try again, this is kinda the only images we have as if yet and the kfhd2 is kinda new territory sorta so we have to see if we can get it working like we did on the previous one, really shouldn't be any learning to it since it is just a modified version of the kfhd7".
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
thanks for the advice ill see what happens ill keep going with it gotta suss in the end rooted a few tabs in the past got there with them in the end tanks for all you help so far
just as the title says! its my moms. any help or links to get help would be nice. most of the stuff i find is able to turn on or must be rooted.
joeyx2 said:
just as the title says! its my moms. any help or links to get help would be nice. most of the stuff i find is able to turn on or must be rooted.
Click to expand...
Click to collapse
ok well in either situation your going to need a fastboot cable/adapter, i recommend getting the blackhat adapter mentioned in hashcodes 2nd bootloader + twrp tutorial. Now for the other thing i need to know, is this a 2012 or 2013 model? (2013 has no front facing camera)
It does have a front facing camera. Can you give me a link? First time looking in the Kindle fire section.
joeyx2 said:
It does have a front facing camera. Can you give me a link? First time looking in the Kindle fire section.
Click to expand...
Click to collapse
Ok lemme grab 2 links you will need.
The thread i was talking about it this: http://forum.xda-developers.com/showthread.php?t=2128848
I personally recommend a custom rom over amazon os so that tutorial could be useful to you in the future should you decide to flash a custom rom on it. There's a link towards the top that goes to the site where you get the fastboot adapter.
Alright and secondly you will need this: http://forum.xda-developers.com/showthread.php?t=2096888
Read its instructions or you might have issues. Also when you plug in your kindle with the fastboot adapter it will show up as a tate device in the device manager, download the drivers in my signature and extract them somewhere on your computer, then in the device manager right click the tate device and hit update drivers and choose a place to search for them and choose where you extracted my drivers and it should install the drivers. If you are on windows 8 you will have to disable driver signature enforcement first though. Once drivers are working you should be able to restore with kffa.
well i ordered the fastboot adapter and it does go into fastboot mode but i have tried a few utilities and they all seem to blow right threw the process. its like it seeing the phone but not doing anything. the only thing i can think of is USB debugging was not turned on and that may be why i cant get it to act right. of course i cant turn it on cause i'm stuck at the logo so is there a way around that or is there a program like Samsung has called Odin that i can use to flash stock everything on?
Nonono. Adb has nothing to do with fastboot. Adb commands can't even be used with fastboot, only fastboot commands can. Try opening a command prompt that's cd'd into a directory with fastboot in it (kffa or SRT) and run "fastboot -i 0x1949 getvar product", if it reports back something then we can establish that fastboot is atleast working.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Nonono. Adb has nothing to do with fastboot. Adb commands can't even be used with fastboot, only fastboot commands can. Try opening a command prompt that's cd'd into a directory with fastboot in it (kffa or SRT) and run "fastboot -i 0x1949 getvar product", if it reports back something then we can establish that fastboot is atleast working.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
ok sorry but i havent played with the kindle much as far as rooting, or with command prompt on any device so im kinda lost on what to do and not sure what kffa or srt is.
joeyx2 said:
ok sorry but i havent played with the kindle much as far as rooting, or with command prompt on any device so im kinda lost on what to do and not sure what kffa or srt is.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Kffa was one of the links I sent you.... download and extract it. Shift + right click it's folder and hit New command window here. Then run that command I mentioned.
Sent from my LG-P769 using Tapatalk
i did what you said and at first i didn't but eventually got the command you told me to put in to recognize and read something tate in the command window but i did not see tate in device manager and the utilities still blows though really fast and dont work. im on vista so do you think that is the problem? this is really pissing me off that i cant get this figured out. im about to uninstall everything and delete everthing and start over.
joeyx2 said:
i did what you said and at first i didn't but eventually got the command you told me to put in to recognize and read something tate in the command window but i did not see tate in device manager and the utilities still blows though really fast and dont work. im on vista so do you think that is the problem? this is really pissing me off that i cant get this figured out. im about to uninstall everything and delete everthing and start over.
Click to expand...
Click to collapse
well the good news is that means fastboot is working, it only is called a tate device in the device manager initially, once you isntall th edrivers it will show up a s a adb interface which is confusing becuase you don't use adb with fastboot. Anyways you should be able to attempt manualyl flashing the device from that command prompt now using certain commands like
Code:
fastboot -i 0x1949 flash <partition name> imagename
so something like
Code:
fastboot -i 0x1949 flash system system.img
it could be that kffa failed to retreive the files or something so it dint flash, sometimes its download links don't work, try srt i think linear posted the link to it, it might actually work out of the box.