I was just playing with the Rom tool box app. I hit re boot recovery and a screen popped up that said Fastboot kindle fire and just stayed there until I held the power button and re booted the device. Has anyone seen this and can fastboot be used?
Sent from my KFTT using xda app-developers app
Are you sure this is the new kindle fire hd. Because I tried it and it said your kindle cannot boot and gave me the option to re boot or factory reset. And since it has a locked boot loader you can not use fast boot.
Its definitely KFHD. I'll try to do it again a take a pic. I guess my real question is can fast boot be used with a locked bootloader?
Sent from my KFTT using xda app-developers app
Here is a pic of what it looked like. And I'm sorry I hit reboot bootloader.
Sent from my SCH-I500 using xda app-developers app
Yes, the new KF's can be put into fastboot mode.
Yes, you can issue fastboot commands to it.
No, that does not mean you can flash it with a new recovery or ROM and have it boot.
Be careful what you do here. There are very few options left to you if you brick this device. If you don't know what you're doing and you don't think things through before playing around in fastboot, you may not like the results.
I didn't think so. And I definitely won't be playing around in fast boot. Thanks for the response though
Sent from my KFTT using xda app-developers app
Is there any way to flash update.zip with fastboot?
fastboot devices command doesn't recognise my KHD..
I want to FULL restore Kindle to factory condition, as I 've messed up keyboard and some othe things. Resetting to default doesn't help.
Yuretz said:
Is there any way to flash update.zip with fastboot?
fastboot devices command doesn't recognise my KHD..
I want to FULL restore Kindle to factory condition, as I 've messed up keyboard and some othe things. Resetting to default doesn't help.
Click to expand...
Click to collapse
try- fastboot -i 0x1949 getvar product
you have to use the -i 0x1949 with commands, if you use fastboot help it will give you a list of commands
check out this thread:
http://forum.xda-developers.com/showthread.php?t=1930656
Related
My issue is, I was installing a ROM but instead of wiping only cache + dalvik, I went and wiped the entire Internal Storage. Now, there's nothing on the "sdcard". ADB doesn't seem to recognize the kindle in recovery and I can't ADB sideload or anything. Has anyone got any ideas on how to fix this?
sandsrules said:
My issue is, I was installing a ROM but instead of wiping only cache + dalvik, I went and wiped the entire Internal Storage. Now, there's nothing on the "sdcard". ADB doesn't seem to recognize the kindle in recovery and I can't ADB sideload or anything. Has anyone got any ideas on how to fix this?
Click to expand...
Click to collapse
You need a factory cable. Then just use the system restore tool.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Hinzman420 said:
You need a factory cable. Then just use the system restore tool.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
Funnily enough, that's arriving tommorow. What exactly is the system restore tool? Is it user made by a person here on the forums or provided by amazon?
Thanks.
http://forum.xda-developers.com/showthread.php?t=1951254
http://forum.xda-developers.com/showthread.php?t=2096888
sandsrules said:
Funnily enough, that's arriving tommorow. What exactly is the system restore tool? Is it user made by a person here on the forums or provided by amazon?
Thanks.
Click to expand...
Click to collapse
bro1 said:
http://forum.xda-developers.com/showthread.php?t=1951254
http://forum.xda-developers.com/showthread.php?t=2096888
Click to expand...
Click to collapse
Well, here's another problem. I was fed up of waiting so I went ahead and made the cable. It's in fastboot and says fastboot kindle fire. The problem is, when I use the restore tool, fastboot doesn't detect it either, it just says "waiting for device". Any ideas what that could be?
not 100% have you installed this http://developer.android.com/sdk/index.html and ticked tools then installed
reading your first post you may have already done this
sandsrules said:
Well, here's another problem. I was fed up of waiting so I went ahead and made the cable. It's in fastboot and says fastboot kindle fire. The problem is, when I use the restore tool, fastboot doesn't detect it either, it just says "waiting for device". Any ideas what that could be?
Click to expand...
Click to collapse
Ok try this, when you get the device into fastboot switch cords unplug the factory cable and use the one that came with the kindle. You should stay in fastboot.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Try Hinzman's suggestion, the Fastboot cable is literally only to get it into Fastboot, once there, unplug and plug in your original USB cable.
Hinzman420 said:
Ok try this, when you get the device into fastboot switch cords unplug the factory cable and use the one that came with the kindle. You should stay in fastboot.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
Katalystik said:
Try Hinzman's suggestion, the Fastboot cable is literally only to get it into Fastboot, once there, unplug and plug in your original USB cable.
Click to expand...
Click to collapse
Thanks for the help. Unfortunately it's still not detecting it. I'm trying to find someway of ADB'ing through recovery but there's no luck. All I want to do is push a ROM, how hard can that be
Try this
http://forum.xda-developers.com/showthread.php?p=41978371
[ROM-AOSP] Unofficial CM10.1 for Kindle Fire HD 7" (JB 4.2.2) [05/14: MIC SEMI-WORKI]
Sent from my KFTT using xda app-developers app
I just tried to flash 2nd booltloader and tarp recovery on my 7". I went to reboot into recovery one got a Bootloop. It flashes kindlefire for 5 seconds and then goes black for 5 seconds and on and on for about a minute and then shuts down. When I try fastboot my computers hang at and adb says no device. I searched the forum and googled and found nothing so I'm sorry if I missed the answer somewhere. I do have the drivers installed on my computer. I appreciate any help or advice
Sent from my LG-E970 using xda app-developers app
popshovit said:
I just tried to flash 2nd booltloader and tarp recovery on my 7". I went to reboot into recovery one got a Bootloop. It flashes kindlefire for 5 seconds and then goes black for 5 seconds and on and on for about a minute and then shuts down. When I try fastboot my computers hang at and adb says no device. I searched the forum and googled and found nothing so I'm sorry if I missed the answer somewhere. I do have the drivers installed on my computer. I appreciate any help or advice
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Im haveing the same problem
Yeah I tried everything I know of so hopefully someone has a trick. I'm thinking about sending it for warranty but if they see it was rooted then I might be sol.
Sent from my LG-E970 using xda app-developers app
You say you got in in fast boot or that you were trying to from adb? Because if your trying to get it in fast boot your going to need a factory cable. From there once its in fast boot you plug it back in to your PC with the normal cable and run fastboot.exe -i 0x1949 getvar product
That should return Tate something. If that happens you should be able to fix it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I can't even get it in fastboot. I have the cable that it came with. maybe I'm nit doing something right. How should I do it with the factory cable. So far I've tried adb = device not found and fastboot = waiting for device
Sent from my LG-E970 using xda app-developers app
popshovit said:
I can't even get it in fastboot. I have the cable that it came with. maybe I'm nit doing something right. How should I do it with the factory cable. So far I've tried adb = device not found and fastboot = waiting for device
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
A factory cable puts kfhd7 in fast boot automatically, not the cable that comes with device,search eBay for Motorola factory cable around 4 euros
Thank you. I'll give this a try
Sent from my LG-E970 using xda app-developers app
fixed
So i ordered the factory which put it right into fastboot. downloaded kfhdsrt, restored system,boot,recovery and it booted up and is running great. thanks for the help. it as fixed within a half hour from when i got the factory cable in the mail :good:
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 a Kindle Fire HD 7'' (According to this is the 2012 version).
I followed this tutorial and something went wrong,I'm now in a bootloop.(My error,I think, is that I forgot the stack override check,damn me! ).
Anyway KFHD System.img Restore tool is what he suggest to unbrick the device,but it's not working in my case.
I even tried the KFFirstAide tool,but it didn't work either.
My actual situation is changed,I think I still have a bootloop(If Kindle is plugged in with my pc it's connecting and disconnecting in loop),but I only see the Kindle logo once,followed by the Fastboot logo and then by only a black screen.
When the Kindle is discharged if I plug the usb in I can see the battery logo.
Other info that can maybe be useful:I also tried to flash images using fastboot directly without any tool and when I gave the command to erase user data and cache
Code:
fastboot -i 0x1949 -w
the command reported : erase successful but not automatically formatting.
Does anyone have any idea on how to fix this?
Can you boot into TWRP?
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
Anonymous.123 said:
Can you boot into TWRP?
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No,fastboot is the only thing working right now.
If you made backups of your system,boot and recovery partitions before flashing,you can restore them by following seokhun's thread.
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
Anonymous.123 said:
If you made backups of your system,boot and recovery partitions before flashing,you can restore them by following seokhun's thread.
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did not
gyosko said:
I did not
Click to expand...
Click to collapse
Well then,I guess you have no other choice than to go completely stock. Follow this thread:
http://forum.xda-developers.com/showthread.php?p=33156486
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
go to
gyosko said:
I have a Kindle Fire HD 7'' (According to this is the 2012 version).
I followed this tutorial and something went wrong,I'm now in a bootloop.(My error,I think, is that I forgot the stack override check,damn me! ).
Anyway KFHD System.img Restore tool is what he suggest to unbrick the device,but it's not working in my case.
I even tried the KFFirstAide tool,but it didn't work either.
My actual situation is changed,I think I still have a bootloop(If Kindle is plugged in with my pc it's connecting and disconnecting in loop),but I only see the Kindle logo once,followed by the Fastboot logo and then by only a black screen.
When the Kindle is discharged if I plug the usb in I can see the battery logo.
Other info that can maybe be useful:I also tried to flash images using fastboot directly without any tool and when I gave the command to erase user data and cache
Code:
fastboot -i 0x1949 -w
the command reported : erase successful but not automatically formatting.
Does anyone have any idea on how to fix this?
Click to expand...
Click to collapse
Go to this thread:
http://forum.xda-developers.com/show...php?p=33156486 try it
Anonymous.123 said:
Well then,I guess you have no other choice than to go completely stock. Follow this thread:
http://forum.xda-developers.com/showthread.php?p=33156486
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Latonya1 said:
Go to this thread:
http://forum.xda-developers.com/showthread.php?p=33156486 try it
Click to expand...
Click to collapse
I've already tried this tool,but it's not working..
gyosko said:
I've already tried this tool,but it's not working..
Click to expand...
Click to collapse
Disclaimer - I am not an expert at this, and what follows is simply a description of what worked for me!
I had the same problem and for the same reasons last night (unless my model is slightly different, I'm not 100% sure). These tools didn't work for me, either. But I found the solution - I downloaded the full update bin from amazon (update-kindle-7.4.6_D025_4620220.bin), unzipped it, and flashed the files boot-prod.img (to boot), MLO-pvt (to xloader), u-boot-prod.bin (to bootloader) and recovery-prod.img (to recovery) using fastboot (fastboot -i 0x1494 xloader MLO-pvt, for example). Then I could boot to android. My system partition had a valid android system on it already - if yours doesn't you would need to flash a stock system.img (from where, I don't know, the file I mentioned had a system/ folder rather than an img file)
Perhaps there is something else going on for you, it's so hard to tell because there are no visible error codes like you would have on a windows blue screen, or a linux boot log, for example. I really wish tablet devs would include such things
mmcoder said:
Disclaimer - I am not an expert at this, and what follows is simply a description of what worked for me!
I had the same problem and for the same reasons last night (unless my model is slightly different, I'm not 100% sure). These tools didn't work for me, either. But I found the solution - I downloaded the full update bin from amazon (update-kindle-7.4.6_D025_4620220.bin), unzipped it, and flashed the files boot-prod.img (to boot), MLO-pvt (to xloader), u-boot-prod.bin (to bootloader) and recovery-prod.img (to recovery) using fastboot (fastboot -i 0x1494 xloader MLO-pvt, for example). Then I could boot to android. My system partition had a valid android system on it already - if yours doesn't you would need to flash a stock system.img (from where, I don't know, the file I mentioned had a system/ folder rather than an img file)
Perhaps there is something else going on for you, it's so hard to tell because there are no visible error codes like you would have on a windows blue screen, or a linux boot log, for example. I really wish tablet devs would include such things
Click to expand...
Click to collapse
Nope,not working I've tried without flashing any system and flashing system.img that comes with KFHD restore tool,but nothing worked.
I also tried to make a system.img from the system folder from the downloaded file,but it did not work(I'm not sure I've done the .img in the right way though).
gyosko said:
Nope,not working I've tried without flashing any system and flashing system.img that comes with KFHD restore tool,but nothing worked.
I also tried to make a system.img from the system folder from the downloaded file,but it did not work(I'm not sure I've done the .img in the right way though).
Click to expand...
Click to collapse
Get a fastboot cord and use this tutorial http://forum.xda-developers.com/showthread.php?t=1951254 Run the bat
Hi there,
I have a new KFHD 7" with bootloader version 7.4.9, which I tried to put a custom ROM with the How-To from the Cyanogen website (Install_CM_for_tate).
I have a fastboot cable and everything went fine, after flashing the files, the device started TWRP. I pushed the CyanogenMod and Gapps over, which completed successfully and then back-upped as recommended.
After that, I was asked if I wanted it to install SU which I accepted. In the next reboot, I got into a bootloop with the kindle logo not turning blue anymore.
I tried to reflash, but that resulted also in a bootloop without getting into TWRP.
Any ideas what I should try next? Thanks!
3rd gen.
2012
Tate-PVT-08
thatissounfair said:
Hi there,
I have a new KFHD 7" with bootloader version 7.4.9, which I tried to put a custom ROM with the How-To from the Cyanogen website (Install_CM_for_tate).
I have a fastboot cable and everything went fine, after flashing the files, the device started TWRP. I pushed the CyanogenMod and Gapps over, which completed successfully and then back-upped as recommended.
After that, I was asked if I wanted it to install SU which I accepted. In the next reboot, I got into a bootloop with the kindle logo not turning blue anymore.
I tried to reflash, but that resulted also in a bootloop without getting into TWRP.
Any ideas what I should try next? Thanks!
3rd gen.
2012
Tate-PVT-08
Click to expand...
Click to collapse
Use the KFHD system restore tool. Make sure it's for the 7" tablet. You'll need a fastboot cord to restore.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
Use the KFHD system restore tool. Make sure it's for the 7" tablet. You'll need a fastboot cord to restore.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your reply!
I tried following the instructions from Thread 1951254.
Problem is, I plugged in the fastboot cable, the Kindle shows the fastboot logo, I enter
Code:
adb shell su -c "reboot bootloader"
and get
Code:
error: device not found
When entering
Code:
fastboot -i 0x1949 getvar product
the product type is printed.
I thought adb commands don't work in fastboot mode?
Is it maybe the Kindle boot version that I have? I think it was 7.4.9...
Adb takes adb commands.
Fastboot takes fastboot commands.
There is no need to issue a reboot command because you are already in bootloader mode (fastboot).
thatissounfair said:
Thanks for your reply!
I tried following the instructions from Thread 1951254.
Problem is, I plugged in the fastboot cable, the Kindle shows the fastboot logo, I enter
Code:
adb shell su -c "reboot bootloader"
and get
Code:
error: device not found
When entering
Code:
fastboot -i 0x1949 getvar product
the product type is printed.
I thought adb commands don't work in fastboot mode?
Is it maybe the Kindle boot version that I have? I think it was 7.4.9...
Click to expand...
Click to collapse
The ADB commands are there in case you still have access to your OS and root. That's when this can be done with a regular USB cord. You don't have that so use your fastboot cord to enter fastboot automatically (should.) Run the bat and choose option 3.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
The ADB commands are there in case you still have access to your OS and root. That's when this can be done with a regular USB cord. You don't have that so use your fastboot cord to enter fastboot automatically (should.) Run the bat and choose option 3.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Awesome, it worked!! Thanks for the explanation too, very helpful!
I would like to retry the flashing. Any recommendations or tips I need to follow?
Got it, thanks everyone!!
thatissounfair said:
Awesome, it worked!! Thanks for the explanation too, very helpful!
I would like to retry the flashing. Any recommendations or tips I need to follow?
Click to expand...
Click to collapse
If you want the 2nd bootloader and TWRP,use FireFlash or Flasher or flash them manually
Sent from my device running CyanogenMod 11