Related
Hi, my kf2 is stucked at fastboot, i'm not able to boot into recovery or system, i have succesfully installed fff-1.4a using a factory cable (because it was bricked with the stock bootloader) and have installed the otter2-twrp-2.4.4.0-recovery.img from hashcode..
It boots and i see the blue kindle logo, and have a menu, but when i select recevery it just turns on the amber light and stays there, i have left it for about 5 minutes waiting to see if it get to revery with no luck.
I tried this:
Code:
sudo fastboot -i 0x18d1 getvar product
< waiting for device >
product: kindle
finished. total time: 0.000s
sudo fastboot -i 0x18d1 oem format
...
OKAY [ 0.068s]
finished. total time: 0.068s
Then
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
< waiting for device >
sending 'boot' (243 KB)...
OKAY [ 0.065s]
writing 'boot'...
OKAY [ 0.051s]
finished. total time: 0.115s
sudo fastboot reboot
rebooting...
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
< waiting for device >
sending 'boot' (243 KB)...
OKAY [ 0.065s]
writing 'boot'...
OKAY [ 0.051s]
finished. total time: 0.115s
It succeed as you can see, it has the fff bootloader and twrp recovery is installed!!
Then i tried
Code:
sudo fastboot -i 0x18d1 flash zip cm-10.1-20130704-NIGHTLY-otter2.zip
< waiting for device >
sending 'zip' (155204 KB)...
OKAY [ 38.806s]
writing 'zip'...
FAILED (remote: partition does not exist)
finished. total time: 38.813s
It seem like a partition table problem maybe because i'm trying to install Cyanogenmod and not a stock image...
I think maybe i must reformat the partitions but i only have access to fastboot and i have read the documentation of Android Fastboot in OmapPedia but i'm not sure it's a "generic" information and don't want to mess up things more.
I have read many trheads in the forum but all of them use adb and there's not a thread with instructions about it..
Or maybe i need to flash all the images (system, kernel, etc..) with fastboot but i don't know where to get it, the main problem is that i'm not able to boot into recovery and maybe that point to the real problem
Any help is appreciated !!
Thank's
You can't write CyanogenMod from fast boot.
Sounds like somewhere in there you formatted the system partition. You need the stack file on the system partition in order to boot into recovery.
Restore to stock using fast boot and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
How?
mindmajick said:
You can't write CyanogenMod from fast boot.
Sounds like somewhere in there you formatted the system partition. You need the stack file on the system partition in order to boot into recovery.
Restore to stock using fast boot and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Maybe it is the problem as fastboot oem format seems to do the job...
I have downloaded the stock update-kindle-6.3.2_D01E_4110520.bin, please can you point to the thread explainig how to do that using fastboot or it's just as easy as rename the file to update.zip and flash it directly?
Edited: also i'm not completely sure it's a kf2 and can't get a hint on how to discover it without knowing the is version :banghead: I've looked one the motherboard and is a MB0090 F3F.
I've downloaded the stock bin for the kf2 too...
Thank' for your quick reply
Well. If you have a kf2... The update you downloaded is wrong. IT'S FOR THE ORIGINAL KINDLE FIRE.
Without knowing what device u have u better slow down a sec. Any advice i give COULD permabrick u of you're on the wrong device.
What color was the BOX it came in? What is the model# on the back? (Same for kf1 AND 2 BUT NOT THE KF HD 7" OR 8").
Be advised- this device is EASY TO BRICK. BE CAREFUL.
--
Sent from my mind to your screen.
---------- Post added at 02:48 AM ---------- Previous post was at 02:40 AM ----------
Also. The correct update file wont work either.
You can only flash image files from fastboot.
--
Sent from my mind to your screen.
It's apparent you have a KF1 and not a KF2. The command "fastboot -i 0x18d1..." would not work on the KF2 because it still has the stock bootloader (unless something miraculous happened while I was AFK). The stock bootloader has a VID of 1949, and will not answer to commands using a different VID. 18d1 is Goggle's VID and is indicative of having FFF installed (KF1 only).
BTW, the "-i 0x18d1" part is completely unnecessary on FFF.
That's not your biggest problem though....
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
That command is completely wrong. What you're doing there is flashing the bootloader (fff-u-boot_v1.4a.bin) to the boot (kernel) partition. Obviously, there is no way that could possibly would work out for you. After the "fastboot" portion of the command, you need to specify what you want done with the image in question: flash or boot. "Flash" is persistent, "boot" is for one boot only. In the next part of the command, you need to specify which partition the image in question goes to; bootloader, recovery, boot, etc.
What you need to do is get an actual recovery.img and flash it to your recovery partition before you can even think of accessing said recovery to flash a ROM and get your device working again.
soupmagnet said:
It's apparent you have a KF1 and not a KF2. The command "fastboot -i 0x18d1..." would not work on the KF2 because it still has the stock bootloader (unless something miraculous happened while I was AFK). The stock bootloader has a VID of 1949, and will not answer to commands using a different VID. 18d1 is Goggle's VID and is indicative of having FFF installed (KF1 only).
BTW, the "-i 0x18d1" part is completely unnecessary on FFF.
That's not your biggest problem though....
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
That command is completely wrong. What you're doing there is flashing the bootloader (fff-u-boot_v1.4a.bin) to the boot (kernel) partition. Obviously, there is no way that could possibly would work out for you. After the "fastboot" portion of the command, you need to specify what you want done with the image in question: flash or boot. "Flash" is persistent, "boot" is for one boot only. In the next part of the command, you need to specify which partition the image in question goes to; bootloader, recovery, boot, etc.
What you need to do is get an actual recovery.img and flash it to your recovery partition before you can even think of accessing said recovery to flash a ROM and get your device working again.
Click to expand...
Click to collapse
Well you are completely right!! Didn't realize I was flashing it to the kernel partition, I bought this on eBay and it was already bricked, when I used the factory cable first time I got a lab26 device, and it was a 1949 so, if I'm right it's a kf2.
I've already flashed a twrp recovery but it won't boot.. I'll try sintering else and post the results here
Sent from my SPH-D710 using xda premium
LUC4X said:
when I used the factory cable first time I got a lab26 device, and it was a 1949 so, if I'm right it's a kf2.
I've already flashed a twrp recovery but it won't boot.. I'll try sintering else and post the results here
Click to expand...
Click to collapse
No. The stock bootloader on all generations and variants of Kindle Fires have vendor IDs of 1949. The fact that your device responds to the "fastboot -i 0x18d1..." clearly means you have a custom bootloader installed in its place. If you have an actual custom bootloader installed (not 2nd bootloader) then you clearly cannot possibly have a KF2.
In this thread, you say you have installed recovery twice, but the information given seems to suggest otherwise.
So to try and get to the root of the problem, what is the exact command you used to install custom recovery, and what custom recovery (version) did you install?
Glad you are here soupmagnet!
I didn't even look at the commands he was using but i definitely learned stuff from your posts. Thanks again
--
Sent from my mind to your screen.
Commands used
soupmagnet said:
No. The stock bootloader on all generations and variants of Kindle Fires have vendor IDs of 1949. The fact that your device responds to the "fastboot -i 0x18d1..." clearly means you have a custom bootloader installed in its place. If you have an actual custom bootloader installed (not 2nd bootloader) then you clearly cannot possibly have a KF2.
In this thread, you say you have installed recovery twice, but the information given seems to suggest otherwise.
So to try and get to the root of the problem, what is the exact command you used to install custom recovery, and what custom recovery (version) did you install?
Click to expand...
Click to collapse
Sorry guys i was out of town...
These are the commands (bootloader & recovery) i've used till now:
sudo fastboot -i 0x18d1 flash bootloader fff-u-boot_v1.4a.bin
< waiting for device >
sending 'bootloader' (243 KB)...
OKAY [ 0.065s]
writing 'bootloader'...
OKAY [ 0.083s]
finished. total time: 0.148s
sudo fastboot -i 0x18d1 flash recovery otter2-twrp-2.4.4.0-recovery.img
sending 'recovery' (8153 KB)...
OKAY [ 2.042s]
writing 'recovery'...
OKAY [ 2.705s]
finished. total time: 4.748s
Click to expand...
Click to collapse
Also tryed the twrp from teamw's site in both versions (otter & blaze) just to make sure, by issuing the following commands:
sudo fastboot -i 0x18d1 flash recovery openrecovery-twrp-2.5.0.0-blaze.img
< waiting for device >
sending 'recovery' (6144 KB)...
OKAY [ 1.540s]
writing 'recovery'...
OKAY [ 1.514s]
finished. total time: 3.054s
Click to expand...
Click to collapse
With this, when i reboot and select the recovery it turns on the amber light for 2 seconds and shuts down.
Then when i install the other recovery version (blaze from teamw):
sudo fastboot -i 0x18d1 flash recovery openrecovery-twrp-2.5.0.0-otter.img
< waiting for device >
sending 'recovery' (6144 KB)...
OKAY [ 1.540s]
writing 'recovery'...
OKAY [ 0.684s]
finished. total time: 2.224s
Click to expand...
Click to collapse
When select recovery i get the same result: amber light for 2 seconds and turns off.
And with hashcode otter2-twrp-2.4.4.0-recovery.img:
sudo fastboot -i 0x18d1 flash recovery otter2-twrp-2.4.4.0-recovery.img
< waiting for device >
sending 'recovery' (8153 KB)...
OKAY [ 2.042s]
writing 'recovery'...
OKAY [ 0.894s]
finished. total time: 2.937s
Click to expand...
Click to collapse
It hangs on amber light and i have to manually turn it off holding the power buttom for 10 seconds...
So you think it is a kf1 based on the device id?, it shows that id after i installed the fff-u-boot_v1.4a.bin from hashcode that i intended for the kf2...
Well, based on that i have installed a kf1 bootloader:
Downloaded the Kindle Fire Utility v0.9.9.zip from http://forum.xda-developers.com/showthread.php?t=2192818
Unzipped it (as i'm GNU/Linux)
"Grepped" recursively till find the web address to download files from
Downloaded fff-u-boot_v1.4a.bin
Downloaded openrecovery-twrp-2.4.4.0-blaze.img
Followed the install procedure
Same result !!, still can't get it to boot into recovery...
Really i hope someone here can point me to the right direction to fix this tablet, can't figure out what's wrong with kf(?)
LUC4X said:
So you think it is a kf1 based on the device id?, it shows that id after i installed the fff-u-boot_v1.4a.bin from hashcode that i intended for the kf2...
Well, based on that i have installed a kf1 bootloader:
Downloaded the Kindle Fire Utility v0.9.9.zip from http://forum.xda-developers.com/showthread.php?t=2192818
Unzipped it (as i'm GNU/Linux)
"Grepped" recursively till find the web address to download files from
Downloaded fff-u-boot_v1.4a.bin
Downloaded openrecovery-twrp-2.4.4.0-blaze.img
Followed the install procedure
Same result !!, still can't get it to boot into recovery...
Really i hope someone here can point me to the right direction to fix this tablet, can't figure out what's wrong with kf(?)
Click to expand...
Click to collapse
Lets get a few things clear right off the bat. The file named fff-u-boot_v1.4a.bin is the custom bootloader for the KF1. The bootloader flashed in the KF2 2nd bootloader installation is named otter2-u-boot-prod-10.2.4.bin. If you flash the fff-u-boot_v1.4a.bin (FFF1.4a) onto a KF2, you would end up with something that is slightly less useful than a doorstop.
Why you re-installed it is a mystery to me. You already had FFF1.4a installed. I know this (as I explained earlier) by the fact that your commands, using the "-i 0x18d1" switch, were successful. If you had a stock bootloader, no commands containing that particular vendor ID would work at all. If you had a KF2, there is absolutely NO WAY you would have a device that responds to fastboot commands using "-i 0x18d1". Even with a modified KF2, with 2nd bootloader installed, the vendor ID would still be 1949 and all fastboot commands must include "-i 0x1949" or they will not work. You can confirm the fact that you have FireFireFire installed by entering a fastboot command without adding "i- 0x18d1". With FireFireFire (KF1 only), the commands will still work because it is unnecessary to specify the vendor ID.
That being said, I'm not entirely sure what's going on with TWRP using both "otter" and "blaze" for the board name (I think it has something to do with Goo Manager?), but anything you get from the TWRP website should work for the KF1 (for the time being at least). Anything you get from Hashcode will be for the 2nd generation KFs.
I would suggest, to avoid complicating things any further, that you download Cannibal Open Touch recovery, confirm that the MD5sums match after downloading, and flash it to recovery in fastboot. COTR only works for the KF1 (not made for the 2nd Generation devices yet) so there is "practically" no way you can get the wrong one. If that works and you still want to try TWRP, download the one for Blaze, check the MD5 (as you should with everything), and try flashing it in recovery again.
If you still can't get your device to boot into recovery, try the command again, but replace the word "flash" with the word "boot" and leave out the partition (i.e. 'fastboot boot openrecovery-twrp-2.4.4.0-blaze.img'). If the device boots into recovery, then you know you have the right one and you may have bad blocks in your recovery partition preventing it from booting, but you won't know for sure without checking a few things out first.
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, but where can i get those files?
What do you think?
soupmagnet said:
Lets get a few things clear right off the bat. The file named fff-u-boot_v1.4a.bin is the custom bootloader for the KF1. The bootloader flashed in the KF2 2nd bootloader installation is named otter2-u-boot-prod-10.2.4.bin. If you flash the fff-u-boot_v1.4a.bin (FFF1.4a) onto a KF2, you would end up with something that is slightly less useful than a doorstop.
Why you re-installed it is a mystery to me. You already had FFF1.4a installed. I know this (as I explained earlier) by the fact that your commands, using the "-i 0x18d1" switch, were successful. If you had a stock bootloader, no commands containing that particular vendor ID would work at all. If you had a KF2, there is absolutely NO WAY you would have a device that responds to fastboot commands using "-i 0x18d1". Even with a modified KF2, with 2nd bootloader installed, the vendor ID would still be 1949 and all fastboot commands must include "-i 0x1949" or they will not work. You can confirm the fact that you have FireFireFire installed by entering a fastboot command without adding "i- 0x18d1". With FireFireFire (KF1 only), the commands will still work because it is unnecessary to specify the vendor ID.
That being said, I'm not entirely sure what's going on with TWRP using both "otter" and "blaze" for the board name (I think it has something to do with Goo Manager?), but anything you get from the TWRP website should work for the KF1 (for the time being at least). Anything you get from Hashcode will be for the 2nd generation KFs.
I would suggest, to avoid complicating things any further, that you download Cannibal Open Touch recovery, confirm that the MD5sums match after downloading, and flash it to recovery in fastboot. COTR only works for the KF1 (not made for the 2nd Generation devices yet) so there is "practically" no way you can get the wrong one. If that works and you still want to try TWRP, download the one for Blaze, check the MD5 (as you should with everything), and try flashing it in recovery again.
If you still can't get your device to boot into recovery, try the command again, but replace the word "flash" with the word "boot" and leave out the partition (i.e. 'fastboot boot openrecovery-twrp-2.4.4.0-blaze.img'). If the device boots into recovery, then you know you have the right one and you may have bad blocks in your recovery partition preventing it from booting, but you won't know for sure without checking a few things out first.
Click to expand...
Click to collapse
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, i've found you uploaded a system.img to androidfilehost...
What do you think?
I posted that ages ago. I'm not even sure what device it's for.
Check the file size. If it's around 350MB go ahead. If it's closer to 500MB then it's probably for the HD.
I can't imagine why you couldn't load recovery using the 'fastboot boot recovery.img' command. Did you receive any errors when trying?
soupmagnet said:
I posted that ages ago. I'm not even sure what device it's for.
Check the file size. If it's around 350MB go ahead. If it's closer to 500MB then it's probably for the HD.
I can't imagine why you couldn't load recovery using the 'fastboot boot recovery.img' command. Did you receive any errors when trying?
Click to expand...
Click to collapse
There's not error message, this is the output:
Code:
sudo fastboot boot CannibalOpenTouch-v2.1_otter.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.394s]
booting...
OKAY [ 0.004s]
finished. total time: 1.398s
But it never boots up and stays off.
I'm seriously thinking it may be a hardware failure but i wont give up until i'm completely sure about it.. that's why i though i should reformat partitions at the first time but the fastboot oem format command "seems" to work, perhaps it takes very short time to execute 0.068s and it is a very short time, so i though maybe it isn't really formatting anything, is it a "normal time"?
Right now i'm downloading the file it's 380MB maybe something good could happen!!
I'll try the following and will post the results:
Code:
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
LUC4X said:
There's not error message, this is the output:
Code:
sudo fastboot boot CannibalOpenTouch-v2.1_otter.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.394s]
booting...
OKAY [ 0.004s]
finished. total time: 1.398s
But it never boots up and stays off.
I'm seriously thinking it may be a hardware failure but i wont give up until i'm completely sure about it.. that's why i though i should reformat partitions at the first time but the fastboot oem format command "seems" to work, perhaps it takes very short time to execute 0.068s and it is a very short time, so i though maybe it isn't really formatting anything, is it a "normal time"?
Right now i'm downloading the file it's 380MB maybe something good could happen!!
I'll try the following and will post the results:
Code:
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
The command 'fastboot oem format' will only make sure the partition layout is stock, it does not format the partitions themselves. The information within the limits of the partitions will remain untouched, so it won't do you much good in this situation. The only way to properly format any partition is with recovery (or 'parted' which is usually run from recovery anyway). Your situation is rather unique because the "fastboot boot' command doesn't write anything to the recovery partition. It loads the disk image you choose, into active memory, as if your computer were a separate partition on which that image is stored. There shouldn't be any reason for it to not work properly.
Try to flash the system partition you downloaded and see how it goes. I would also suggest that you make absolutely sure the md5sums match before installing any image to your device, including the recovery images you downloaded before.
soupmagnet said:
The command 'fastboot oem format' will only make sure the partition layout is stock, it does not format the partitions themselves. The information within the limits of the partitions will remain untouched, so it won't do you much good in this situation. The only way to properly format any partition is with recovery (or 'parted' which is usually run from recovery anyway). Your situation is rather unique because the "fastboot boot' command doesn't write anything to the recovery partition. It loads the disk image you choose, into active memory, as if your computer were a separate partition on which that image is stored. There shouldn't be any reason for it to not work properly.
Try to flash the system partition you downloaded and see how it goes. I would also suggest that you make absolutely sure the md5sums match before installing any image to your device, including the recovery images you downloaded before.
Click to expand...
Click to collapse
Code:
sudo fastboot flash system system.img
sending 'system' (389120 KB)...
OKAY [ 97.308s]
writing 'system'...
OKAY [ 36.819s]
finished. total time: 134.131s
sudo fastboot erase userdata
erasing 'userdata'...
OKAY [116.935s]
finished. total time: 116.935s
sudo fastboot erase cache
erasing 'cache'...
OKAY [ 29.189s]
finished. total time: 29.189s
sudo fastboot reboot
rebooting...
finished. total time: 0.000s
Must be hardware, it's sad... if it where a SMD flash memory i would try to changed it but it's a tyni BGA chip...
Thank you very much for your help
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
soupmagnet said:
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
Click to expand...
Click to collapse
I'll try tonight !!
Sent from my SPH-D710 using xda premium
soupmagnet said:
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
Click to expand...
Click to collapse
./usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
... OKAY
Installing x-loader...
sending 'xloader' (128 KB)... OKAY
writing 'xloader'... OKAY
Flash FFF...
sending 'bootloader' (211 KB)... OKAY
writing 'bootloader'... OKAY
Flash TWRP...
sending 'recovery' (5260 KB)... OKAY
writing 'recovery'... OKAY
Resetting bootmode to standard boot...
... OKAY
Loading TWRP...
downloading 'boot.img'... OKAY
booting... OKAY
Click to expand...
Click to collapse
Same as before, it won't reboot after sending the boot to recovery command and if try to get into recovery it turns off after an amber light..
LUC4X said:
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, but where can i get those files?
What do you think?
Click to expand...
Click to collapse
At the begining i saw you were using "fastboot flash zip...." that's wrong command.. should be "fastboot flash update xxxx.zip"
so if you find the totally package, youcan use it.
also you has mixture the boot.img and bootloader.bin..
recovery is not needed if you can flash the right bootloader and boot.:laugh:
First off download the following files
KFHD_SRTv2.1- 8.1.4
img files
KFFirstAide32
or
KFFirstAide64
Extract KFFirstAide whichever version 32 or 64
Copy the folder to c:\
rename it to just KFFirstAide
add that to your path
Code:
;C:\KFFirstAide
Open the folder KFHD_SRTv2.1 then open images folder and copy system.img
paste it into the KFFirstAide folder
then open the two other img files you downloaded and paste them into the KFFirstAide folder as well
you should now have:
system.img
boot.img
recovery.img
All three files in the KFFirstAide folder
now
Open up an Administrative Command Prompt from within the KFFirstAide
go to the c:\ drive hold the shift key and right click on the folder KFFirstAide then select Open a command prompt here.
enter this command at the prompt
Code:
fastboot -i 0x1949 getvar product
it should come back with
< waiting for device >
If you are stuck at the red triangle screen
Make sure your device is totally off hold the power button for like 30 seconds until it turns off
next plug in your device with the usb cable
it should boot into fastboot mode
and show something like:
product: Jem-PVT-Prod-04
finished. total time: 0.009s
then type this command
Code:
fastboot -i 0x1949 devices
should come back with something like this
7EE400003C002FFF fastboot
then type this command
Code:
fastboot -i 0x1949 flash system system.img
should come back with something like
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
OKAY [ 60.331s]
finished. total time: 109.193s
next command
Code:
fastboot -i 0x1949 flash boot boot.img
should show something like
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.449s]
writing 'boot'...
OKAY [ 0.571s]
finished. total time: 1.024s
next command
Code:
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
should see something like
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.449s]
writing 'recovery'...
OKAY [ 0.565s]
finished. total time: 1.020s
these next commands take forever
Code:
fastboot -i 0x1949 erase cache
should come back with
erasing 'cache'...
OKAY [ 47.246s]
finished. total time: 47.250s
Code:
fastboot -i 0x1949 erase userdata
should come back with
erasing 'userdata'...
OKAY [2149.490s]
finished. total time: 2149.494s
and finally
Code:
fastboot reboot -i 0x1949
once it starts rebooting disconnect the USB cable
once you are back up and running you will be at version 8.1.4
to get to current version
you can use KFFirstAide and this time run
c:\KFFirstAide\RunMe.bat
use the option enable OTA updates
you will have to make sure ADB is enabled under security first on your kindle
once you enable OTA updates then unplug the USB
Next :
Charge the battery, and then connect to a Wi-Fi network.
Swipe down from the top of the screen, and then tap Sync.
The software update automatically downloads in the background and installs after the download is complete and the device is asleep.
Your Kindle Fire will restart during the software update. After the restart, the message “Kindle is updating” will appear on the screen and when it's finished you will be at the latest software version.
i ****ing love you, may you breed with amany and spread your DNA far and wide
Lamere said:
First off download the following files
KFHD_SRTv2.1- 8.1.4
img files
KFFirstAide32
or
KFFirstAide64
Extract KFFirstAide whichever version 32 or 64
Copy the folder to c:\
rename it to just KFFirstAide
add that to your path
Code:
;C:\KFFirstAide
Open the folder KFHD_SRTv2.1 then open images folder and copy system.img
paste it into the KFFirstAide folder
then open the two other img files you downloaded and paste them into the KFFirstAide folder as well
you should now have:
system.img
boot.img
recovery.img
All three files in the KFFirstAide folder
now
Open up an Administrative Command Prompt from within the KFFirstAide
go to the c:\ drive hold the shift key and right click on the folder KFFirstAide then select Open a command prompt here.
enter this command at the prompt
Code:
fastboot -i 0x1949 getvar product
it should come back with
< waiting for device >
If you are stuck at the red triangle screen
Make sure your device is totally off hold the power button for like 30 seconds until it turns off
next plug in your device with the usb cable
it should boot into fastboot mode
and show something like:
product: Jem-PVT-Prod-04
finished. total time: 0.009s
then type this command
Code:
fastboot -i 0x1949 devices
should come back with something like this
7EE400003C002FFF fastboot
then type this command
Code:
fastboot -i 0x1949 flash system system.img
should come back with something like
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
OKAY [ 60.331s]
finished. total time: 109.193s
next command
Code:
fastboot -i 0x1949 flash boot boot.img
should show something like
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.449s]
writing 'boot'...
OKAY [ 0.571s]
finished. total time: 1.024s
next command
Code:
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
should see something like
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.449s]
writing 'recovery'...
OKAY [ 0.565s]
finished. total time: 1.020s
these next commands take forever
Code:
fastboot -i 0x1949 erase cache
should come back with
erasing 'cache'...
OKAY [ 47.246s]
finished. total time: 47.250s
Code:
fastboot -i 0x1949 erase userdata
should come back with
erasing 'userdata'...
OKAY [2149.490s]
finished. total time: 2149.494s
and finally
Code:
fastboot reboot -i 0x1949
once it starts rebooting disconnect the USB cable
once you are back up and running you will be at version 8.1.4
to get to current version
you can use KFFirstAide and this time run
c:\KFFirstAide\RunMe.bat
use the option enable OTA updates
you will have to make sure ADB is enabled under security first on your kindle
once you enable OTA updates then unplug the USB
Next :
Charge the battery, and then connect to a Wi-Fi network.
Swipe down from the top of the screen, and then tap Sync.
The software update automatically downloads in the background and installs after the download is complete and the device is asleep.
Your Kindle Fire will restart during the software update. After the restart, the message “Kindle is updating” will appear on the screen and when it's finished you will be at the latest software version.
Click to expand...
Click to collapse
well this procedure saved me thanks but now using KFFaide i run diagnostics on my machine and test fastboot commands it sits at waiting for device and windows say device is not responding to simple fastboot commands check device manager no yellow triangles what to do now? I am rooted and have a 8.9 running 8.4.8 just completed recovery to 8.4.1 and updated to 8.4.8 b4 root flashed a new boot system and recovery image using command prompt but don't know why fastboot isn't working now????? Thanks
larryb1951 said:
well this procedure saved me thanks but now using KFFaide i run diagnostics on my machine and test fastboot commands it sits at waiting for device and windows say device is not responding to simple fastboot commands check device manager no yellow triangles what to do now? I am rooted and have a 8.9 running 8.4.8 just completed recovery to 8.4.1 and updated to 8.4.8 b4 root flashed a new boot system and recovery image using command prompt but don't know why fastboot isn't working now????? Thanks
Click to expand...
Click to collapse
had the same problem on windows 8.1 moved to my windows 7 box and it worked so 8.4.8 didn't kill fastboot at least
I get to.....
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
FAILED <remote: write partition>
Can anyone help?
Got my kindle back
Just want to vouch for this procedure. I followed it and got my Kindle back to its stock settings. It is 8.4.8. I was able to root it, but when I tried installing the bootloader, I must have done something wrong (wrong version maybe?). It hung on a reboot and just sat there with the orange Kindle Fire logo. Volume buttons did nothing. I was able to get it to go into fastboot, so I figured it wasn't a total loss. After trying about everything else, including using KFFirstAide just by itself, this procedure finally did the trick. I unrooted it now, and I don't think I'll make a second attempt.
what can i fix this...?
When i try to reboot my Kindle in fastboot mode, i see his logo for one second only and then the system restart normally...
Sorry for my bad english but i'm italian
I killed my KFHD8.9 by some naughty fastboot command.. Had twrp and some older CM rom but everything was buggy so I was trying to update when I did something I shouldn't have apparently (I think the last command was a fastboot command before everything died). The kindle won't boot up, no screen, nothing. It just heats up if you connect it to charge is all I can tell.
I downloaded everything per instructions in this thread but after the first fastboot command nothing happens it just stays at "< Waiting for device >". Also, 'adb devices' doesn't report anything connected. All my other devices connect fine. I have also pressed the power button for 30s to make sure the kindle is off prior to connecting for fastboot command...
Can this be fixed? Thanks!
mrgv said:
I killed my KFHD8.9 by some naughty fastboot command.. Had twrp and some older CM rom but everything was buggy so I was trying to update when I did something I shouldn't have apparently (I think the last command was a fastboot command before everything died). The kindle won't boot up, no screen, nothing. It just heats up if you connect it to charge is all I can tell.
I downloaded everything per instructions in this thread but after the first fastboot command nothing happens it just stays at "< Waiting for device >". Also, 'adb devices' doesn't report anything connected. All my other devices connect fine. I have also pressed the power button for 30s to make sure the kindle is off prior to connecting for fastboot command...
Can this be fixed? Thanks!
Click to expand...
Click to collapse
Try holding down the power button only for 2 minutes. Right around the 90 second to 120 second point, the device should reboot.
Damocles66 said:
Try holding down the power button only for 2 minutes. Right around the 90 second to 120 second point, the device should reboot.
Click to expand...
Click to collapse
Sry about the delay.. I was counting on an email notification but never got one.. Anyway.
Tried it several times and this didn't work. The tablet doesn't boot up with this 2min+ power button press. Anyone have any other ideas please?
KatanAlive said:
what can i fix this...?
When i try to reboot my Kindle in fastboot mode, i see his logo for one second only and then the system restart normally...
Sorry for my bad english but i'm italian
Click to expand...
Click to collapse
Not sure what Kindle you have since you did not say.
The HD Kindles as far as I know will not boot into fastboot using commands so, your is normal.
Regards
---------- Post added at 07:31 AM ---------- Previous post was at 07:26 AM ----------
mrgv said:
Sry about the delay.. I was counting on an email notification but never got one.. Anyway.
Tried it several times and this didn't work. The tablet doesn't boot up with this 2min+ power button press. Anyone have any other ideas please?
Click to expand...
Click to collapse
I am pretty sure your tablet is not recoverable depending on what fastboot commands you were trying when it stopped booting.
Do you remember what you were attempting to do?
If an incorrect non-signed partition was flashed to the tablet (e.g., from some other Kindle model), the tablet will be bricked.
If the wrong image was flashed to the bootloader partition, you are also bricked since the bootloader is key to turning on the tablet.
If your tablet is warm when plugged in, it means it charges at least.
Since the tablet will not turn on, or get into fastboot using the command line on your PC, there is nothing else to do.
The 8.9 tablet does not support the use of a fastboot cable.
Lamere said:
First off download the following files
KFHD_SRTv2.1- 8.1.4
img files
KFFirstAide32
or
KFFirstAide64
Extract KFFirstAide whichever version 32 or 64
Copy the folder to c:\
rename it to just KFFirstAide
add that to your path
Code:
;C:\KFFirstAide
Open the folder KFHD_SRTv2.1 then open images folder and copy system.img
paste it into the KFFirstAide folder
then open the two other img files you downloaded and paste them into the KFFirstAide folder as well
you should now have:
system.img
boot.img
recovery.img
All three files in the KFFirstAide folder
now
Open up an Administrative Command Prompt from within the KFFirstAide
go to the c:\ drive hold the shift key and right click on the folder KFFirstAide then select Open a command prompt here.
enter this command at the prompt
Code:
fastboot -i 0x1949 getvar product
it should come back with
< waiting for device >
If you are stuck at the red triangle screen
Make sure your device is totally off hold the power button for like 30 seconds until it turns off
next plug in your device with the usb cable
it should boot into fastboot mode
and show something like:
product: Jem-PVT-Prod-04
finished. total time: 0.009s
then type this command
Code:
fastboot -i 0x1949 devices
should come back with something like this
7EE400003C002FFF fastboot
then type this command
Code:
fastboot -i 0x1949 flash system system.img
should come back with something like
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
OKAY [ 60.331s]
finished. total time: 109.193s
next command
Code:
fastboot -i 0x1949 flash boot boot.img
should show something like
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.449s]
writing 'boot'...
OKAY [ 0.571s]
finished. total time: 1.024s
next command
Code:
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
should see something like
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.449s]
writing 'recovery'...
OKAY [ 0.565s]
finished. total time: 1.020s
these next commands take forever
Code:
fastboot -i 0x1949 erase cache
should come back with
erasing 'cache'...
OKAY [ 47.246s]
finished. total time: 47.250s
Code:
fastboot -i 0x1949 erase userdata
should come back with
erasing 'userdata'...
OKAY [2149.490s]
finished. total time: 2149.494s
and finally
Code:
fastboot reboot -i 0x1949
once it starts rebooting disconnect the USB cable
once you are back up and running you will be at version 8.1.4
to get to current version
you can use KFFirstAide and this time run
c:\KFFirstAide\RunMe.bat
use the option enable OTA updates
you will have to make sure ADB is enabled under security first on your kindle
once you enable OTA updates then unplug the USB
Next :
Charge the battery, and then connect to a Wi-Fi network.
Swipe down from the top of the screen, and then tap Sync.
The software update automatically downloads in the background and installs after the download is complete and the device is asleep.
Your Kindle Fire will restart during the software update. After the restart, the message “Kindle is updating” will appear on the screen and when it's finished you will be at the latest software version.
Click to expand...
Click to collapse
Amazing! THANKS!! after weeks stuck in FB and logo, I'm back. cheers
ant17 said:
Amazing! THANKS!! after weeks stuck in FB and logo, I'm back. cheers
Click to expand...
Click to collapse
Do I need to let it update before root and twrp install?
mrgv said:
Sry about the delay.. I was counting on an email notification but never got one.. Anyway.
Tried it several times and this didn't work. The tablet doesn't boot up with this 2min+ power button press. Anyone have any other ideas please?
Click to expand...
Click to collapse
Hi, my Kindle 2nd gen 8.9" HD will not power up at all either after flashing the wrong bootloader. Did you ever figure out how to start up your Kindle. Thanks.
Hi! Amazon Fire HD 8.9”. How to Install Google OS? Chromium? ArnoldTheBat? FydeOS? CloudReady?
My 8.9" gets to the TWRP 3.0.2.0 splash screen, but not past that... adb sees the device as being in recovery, but the device doesn't respond to adb commands, and fastboot doesn't see the device.
The 2-min power button trick powered the device off, but not back on.
Any recommendations?
llleonid said:
Hi! Amazon Fire HD 8.9”. How to Install Google OS? Chromium? ArnoldTheBat? FydeOS? CloudReady?
Click to expand...
Click to collapse
Hi there! Can Windows 8 be installed? As?
brilliant
ibrahimsow1 said:
i ****ing love you, may you breed with amany and spread your DNA far and wide
Click to expand...
Click to collapse
simply superb , it was brutal trying to find the recovery img as all links were to dev host mostly. i got an old recovery.img file from an old zip . hey were back to stock. time to root again . thanks m8 excellent guide and work
llleonid said:
Hi there! Can Windows 8 be installed? As?
Click to expand...
Click to collapse
Hello illeonid. Yes you have to search thread for disable driver signature enforcement. There is a thread somewhere on here with how to do windows 8 driver for firehd. I haven't time just now to find it. Will post back later
---------- Post added at 06:40 PM ---------- Previous post was at 06:38 PM ----------
llleonid said:
Hi! Amazon Fire HD 8.9”. How to Install Google OS? Chromium? ArnoldTheBat? FydeOS? CloudReady?
Click to expand...
Click to collapse
You cannot install these on the firehd the chipset just is not capable of handling such sofware with the paltry 1gb ram being main culprit. This is mostly tied up with fireOS and system apps already
Q&A for Kindle Fire 2 7" Stock Restore
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Kindle Fire 2 7" Stock Restore. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Gen2 Kindle stock restore - stuck in a boot loop - following overlode's doc
Overlode - Huge thank you for the simple list for us NOOBS of how to get a stock Kindle stuck in a boot loop back up and running. I am having some problems though and was hoping for some help.
I am running Win7 on my PC. I've installed Android SDK, I have a factory cable and my gen 2 Kindle has the pretty "Fastboot" logo with the flashing green light and a non-flashing red light. When I go into my devices manager and see the "Otter2-***.***" it does have the yellow triangle. This is where I deviate from your instructions (in your .doc file). When I right click I do not see the simple "update driver software". I have to go through several windows to finally reach that option. No big deal. But... I clicked the option to "browse my computer for driver software" then "Let me pick from a list of device drivers on my computer". I do not have the option to select "Kindle". I went to have it list ALL DRIVERS and it is not in that list either.
I'm stuck. I don't know how to get the drivers up and working so I can continue with your instruction sheet. I REALLY appreciate all your efforts (with the drop box and everything). I've been fighting this boot loop for a month now and I'm scared to make a bigger mistake. I can build a pc from scratch- no problem... programming and mobile devices just make my brain hurt. Be kind. Everyone seems to throw around abbreviations like Halloween candy and this just makes me want to run for the hills. I'm learning but please don't just assume I know what you're talking about. Thanks in Advance!!
Myth421 said:
Overlode - Huge thank you for the simple list for us NOOBS of how to get a stock Kindle stuck in a boot loop back up and running. I am having some problems though and was hoping for some help.
I am running Win7 on my PC. I've installed Android SDK, I have a factory cable and my gen 2 Kindle has the pretty "Fastboot" logo with the flashing green light and a non-flashing red light. When I go into my devices manager and see the "Otter2-***.***" it does have the yellow triangle. This is where I deviate from your instructions (in your .doc file). When I right click I do not see the simple "update driver software". I have to go through several windows to finally reach that option. No big deal. But... I clicked the option to "browse my computer for driver software" then "Let me pick from a list of device drivers on my computer". I do not have the option to select "Kindle". I went to have it list ALL DRIVERS and it is not in that list either.
I'm stuck. I don't know how to get the drivers up and working so I can continue with your instruction sheet. I REALLY appreciate all your efforts (with the drop box and everything). I've been fighting this boot loop for a month now and I'm scared to make a bigger mistake. I can build a pc from scratch- no problem... programming and mobile devices just make my brain hurt. Be kind. Everyone seems to throw around abbreviations like Halloween candy and this just makes me want to run for the hills. I'm learning but please don't just assume I know what you're talking about. Thanks in Advance!!
Click to expand...
Click to collapse
EDIT: (a day or so later) Hey.. Nevermind. I was able to finally figure things out and downloaded KindleFireFirstAid and was able to wipe it out back to stock using my factory cable. The boot loop was limiting my options. Thanks Anyway.
Fastboot
What would be stopping Fastboot from recognizing my device? I have a fastboot cable for my kindle fire 2, I plug it into my computer then into the kf2, the kf2 boots up into fastboot mode my computer see the kindle and it has the proper drivers installed, but fastboot can't see it for some reason.
I had this problem before when I installed CM10 onto my kf2 but that was a year ago and for the life of me I don't remember how I got fastboot to see my kf2.
All i want to do is downgrade my kf2 back to stock and sell it on ebay. PLEASE HELP! I'm dying here
Any other options?
Overlode-My wife;s KF2 was stuck in boot loop so I tried your stock restore method with a factory cable. Everything seemed to work fine. The drivers were installed, fastboot commands worked on the device, etc. When I did the last reboot step, the device never turned back on. Now the device will not power up with the factory cable or USB cable. Is there anything I can do to fix this KF2 or is it permanently screwed? Thanks.
Kindle Fire 2 - Bricked
Today I tried the procedure in post http://forum.xda-developers.com/kindle-fire-hd/fire-2-development/kindle-fire-2-7-stock-restore-t2840987 but as I use Linux and have the SDK installed I entered the commands from console.
A couple of days ago I flashed Cyanogenmod using very similar steps.
Here is my log for the attempt to restore the stock ROM:
Code:
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.060s]
writing 'bootloader'...
OKAY [ 0.060s]
finished. total time: 0.120s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash boot boot.img
sending 'boot' (4310 KB)...
OKAY [ 1.082s]
writing 'boot'...
OKAY [ 1.053s]
finished. total time: 2.134s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash recovery recovery.img
sending 'recovery' (4828 KB)...
OKAY [ 1.211s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 2.165s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 -w
erasing 'userdata'...
OKAY [114.081s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 28.939s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 143.021s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash system system.img
sending 'system' (777953 KB)...
FAILED (remote: data too large)
finished. total time: 0.004s
(1)
What is worse, after the failure I rebooted in order to restart with the procedure that worked a couple of days ago and leave Cyanogenmod in the Kindle...
but...
No reboot, no lights, no USB detected....
It seems that the tablet is hard bricked.
Is there anything that can be done except using it as a paperweight?
Thanks in advance
KF2 - hardbricked and restored.......almost!!!
Hi,
I have a KF2, which I had previously rooted and installed CM10 custom ROM. Had no problems with it, but decided to try a few more custom ROMS. Forgot about NOT using the KFU program as it was for KF1 devices, and for some stupid reason went ahead and flashed the wrong bootloader.
Result is fairly predictable - HARD BRICKED KF2!!
Thought that was it - searched the forums and everyone was saying the same - no way back from that! Then I came across Kurohyou's post and brilliant guide about hacking a card reader and attaching direct to motherboard. Followed his guide and voila - managed to boot up into recovery (TWRP). However after pushing the ROM files etc to try and install CM ROM again just kept getting "error flashing ROM" . I left the thing after trying various methods and different PC's etc to push the files across and gave up. When I went back to it this morning I couldn't get it to boot into recovery - which I thought was a bit strange. However FASTBOOT mode is ok - I have made a fastboot cable myself which works fine. Kindle was booting up with orange logo, quick flash, orange kindle logo again and repeat. It would not boot into recovery even though I had flashed the correct files via fastboot.
Again almost giving up when I came across Overlode's instructions. Followed them to the letter, and what I am left with now is the standard Kindle Fire logo (orange) which blinks after about 5 seconds and just stays there - left it for about an hour just in case....
I can post screenshots of me flashing the files as per Overlode's instructions if it helps. I get a few errors when using the wipe command, response is "erase successful, but not automatically formatting. File system type not supported" everything else is ok.
I still have the hacked card reader attached which through Ubuntu can see the EMMC directly so don't know if might be worth copying the files directly instead of flashing via fastboot?
Any suggestions gratefully received...... I'm at my wits end with this thing - I know I should have left well alone!!! but I feel like I have run a marathon with this thing only to have fallen flat on my face 5 metres from the finish line!!
Thanks in advance for any help.
lmayala said:
Today I tried the procedure in post http://forum.xda-developers.com/kin...opment/kindle-fire-2-7-stock-restore-t2840987 but as I use Linux and have the SDK installed I entered the commands from console.
A couple of days ago I flashed Cyanogenmod using very similar steps.
Here is my log for the attempt to restore the stock ROM:
Code:
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.060s]
writing 'bootloader'...
OKAY [ 0.060s]
finished. total time: 0.120s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash boot boot.img
sending 'boot' (4310 KB)...
OKAY [ 1.082s]
writing 'boot'...
OKAY [ 1.053s]
finished. total time: 2.134s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash recovery recovery.img
sending 'recovery' (4828 KB)...
OKAY [ 1.211s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 2.165s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 -w
erasing 'userdata'...
OKAY [114.081s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 28.939s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 143.021s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash system system.img
sending 'system' (777953 KB)...
FAILED (remote: data too large)
finished. total time: 0.004s
(1)
What is worse, after the failure I rebooted in order to restart with the procedure that worked a couple of days ago and leave Cyanogenmod in the Kindle...
but...
No reboot, no lights, no USB detected....
It seems that the tablet is hard bricked.
Is there anything that can be done except using it as a paperweight?
Thanks in advance
Click to expand...
Click to collapse
Hi - see my last post - I too have a hard bricked kindle. if you're handy with a soldering iron you can try it - I can confirm it does work.
details here -
http://forum.xda-developers.com/showthread.php?t=2415870
I managed to get my kindle from nothing (not even charging light) to back up and running with TWRP installed. I couldn't get a custom ROM installed, kept getting errors - but I think my board has other issues. While I was putting it back together I managed to stick my screwdriver through the battery (don't ask!!!) Since then I think I have caused other damage and it was never the same again I think I may have damaged the memory or the EMMC..... on the hunt for new motherboard at present!
Good luck!
registered an account just to thank you. You saved my KF2.
Here's my problem...
My Kindle Fire HD (Jem) is stuck on the Kindle Fire boot screen (orange logo, no animation). I haven't been able to get it to mount to any of my computers running various operating systems. More details below.
Here are the steps that made my device like this...
Got root using the latest eploit for 8.5.1 successfully. I confirmed that I did have root level access.
Side loaded FireFlash11
Used FireFlash11 to try installing 2nd-bootloader, TWRP and CM. I got the files from here: http://forum.xda-developers.com/showthread.php?t=2128175
Booted into recovery mode and immediately performed a backup.
When I soft rebooted after the backup I only ever saw the Kindle Fire boot screen (orange logo, no animation).
Some other notes...
In Ubuntu when I hard shut down the device and then start it up I get the message Unable to mount JEM-etc. etc.
In Windows if I when I hard shut down the device and then start it up I see something about JEM-etc etc in device manager for a quick second and then it dissapears.
I tried SoupKit on Ubuntu with no luck. I've tried just about every option but no luck. The device never mounts.
I've never had root on this device before. I just got this device a couple of days ago.
Please help! Thanks in advance for your time and effort!
sotrite5 said:
Here's my problem...
My Kindle Fire HD (Jem) is stuck on the Kindle Fire boot screen (orange logo, no animation). I haven't been able to get it to mount to any of my computers running various operating systems. More details below.
Here are the steps that made my device like this...
Got root using the latest eploit for 8.5.1 successfully. I confirmed that I did have root level access.
Side loaded FireFlash11
Used FireFlash11 to try installing 2nd-bootloader, TWRP and CM. I got the files from here: http://forum.xda-developers.com/showthread.php?t=2128175
Booted into recovery mode and immediately performed a backup.
When I soft rebooted after the backup I only ever saw the Kindle Fire boot screen (orange logo, no animation).
Some other notes...
In Ubuntu when I hard shut down the device and then start it up I get the message Unable to mount JEM-etc. etc.
In Windows if I when I hard shut down the device and then start it up I see something about JEM-etc etc in device manager for a quick second and then it dissapears.
I tried SoupKit on Ubuntu with no luck. I've tried just about every option but no luck. The device never mounts.
I've never had root on this device before. I just got this device a couple of days ago.
Please help! Thanks in advance for your time and effort!
Click to expand...
Click to collapse
Completely power off the Kindle (hold power button for 10 seconds), and then type fastboot -i 0x1949 getvar product into the terminal. Plug in the Kindle as soon as you get the <waiting for device> message. after a few seconds, you should get a string beginning with "Jem-PVT". If you do, download the 2nd bootloader, etc. from Hashcode's thread and flash them as directed in step 5. After that, follow the directions to reboot into TWRP, and your recovery process should be complete.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Completely power off the Kindle (hold power button for 10 seconds), and then type fastboot -i 0x1949 getvar product into the terminal. Plug in the Kindle as soon as you get the <waiting for device> message. after a few seconds, you should get a string beginning with "Jem-PVT". If you do, download the 2nd bootloader, etc. from Hashcode's thread and flash them as directed in step 5. After that, follow the directions to reboot into TWRP, and your recovery process should be complete.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thanks for taking the time to post, monster. Unfortunately this doesn't work for me. In fact, before I ever changed a thing on my device fastboot wasn't working for me (just ADB), in spite of everything being properly installed on my computer. Could this be an issue with 8.5.1? Any other thoughts?
sotrite5 said:
Thanks for taking the time to post, monster. Unfortunately this doesn't work for me. In fact, before I ever changed a thing on my device fastboot wasn't working for me (just ADB), in spite of everything being properly installed on my computer. Could this be an issue with 8.5.1? Any other thoughts?
Click to expand...
Click to collapse
If you've got ADB enabled on your Kindle (settings -> security if I remember correctly?), you should be able to type adb reboot bootloader and have it boot into fastboot without a hitch.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
If you've got ADB enabled on your Kindle (settings -> security if I remember correctly?), you should be able to type adb reboot fastboot and have it boot into fastboot without a hitch.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Although I did have ADB enabled on my Kindle, I am no longer able to communicate with it via ADB since using FireFlash11 to install the 2nd-bootloader, TWRP and CM. The Kindle now does not appear when I type adb devices (although it always had before using FireFlash).
Alright, I think I'm just going to return this one. I have lost all hope. Were the steps that I took above flawed? I'd consider purchasing this same device, but I need to know the mistake that I made. Can anyone tell me?
sotrite5 said:
Alright, I think I'm just going to return this one. I have lost all hope. Were the steps that I took above flawed? I'd consider purchasing this same device, but I need to know the mistake that I made. Can anyone tell me?
Click to expand...
Click to collapse
I wouldn't give up just yet. Try repeating the same directions I gave you, expect from Linux (Ubuntu) this time as opposed to Windows.
Sent from my Amazon Jem using XDA Labs
*EDIT #2 - WE DID IT, BOYS! I just want to say god bless the following:
monster
hashcode
goldenbullet
cyanogenmod
my mother
america
Monster, thanks for all of your help. I will name my first born male child after you. You earned it.
*EDIT I MADE IT INTO RECOVERY by using "fastboot -i 0x1949 oem recovery" once in fastboot mode. I'll continue with your instructions now.!
Well, fastboot worked and so I got excited for a second there but unfortunately I'm stuck again. I successfully followed all of the instructions in step 5, but unfortunately I am still stuck on the orange kindle fire boot-screen. The logo never becomes blue....
I am not able to get into recovery by holding the up and/or down volume buttons
I am not able to get into recovery via terminal yet. I can still see "fastboot mode" with the blue arrow when I issue the "fastboot -i 0x1949 getvar product" command, but it does not respond when I issue commands like "fastboot boot kfhd8-twrp-2.8.7.0-recovery.img" or fastboot flash recovery kfhd8-twrp-2.8.7.0-recovery.img" -- always just "waiting for device".
The device appears in Ubuntu's launcher as Jem PVT 04 (ONLY when in fastboot mode), but when I try to access it I get an error message about it being inaccessible.
The device still does not respond to ADB
Any other ideas?
Code:
[email protected]:~/Downloads$ fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.022s]
writing 'bootloader'...
OKAY [ 0.042s]
finished. total time: 0.063s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.546s]
writing 'boot'...
OKAY [ 0.572s]
finished. total time: 1.118s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.566s]
finished. total time: 1.097s
[email protected]:~/Downloads$ fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.050s
sotrite5 said:
*EDIT #2 - WE DID IT, BOYS! I just want to say god bless the following:
monster
hashcode
goldenbullet
cyanogenmod
my mother
america
Monster, thanks for all of your help. I will name my first born male child after you. You earned it.
*EDIT I MADE IT INTO RECOVERY by using "fastboot -i 0x1949 oem recovery" once in fastboot mode. I'll continue with your instructions now.!
Well, fastboot worked and so I got excited for a second there but unfortunately I'm stuck again. I successfully followed all of the instructions in step 5, but unfortunately I am still stuck on the orange kindle fire boot-screen. The logo never becomes blue....
I am not able to get into recovery by holding the up and/or down volume buttons
I am not able to get into recovery via terminal yet. I can still see "fastboot mode" with the blue arrow when I issue the "fastboot -i 0x1949 getvar product" command, but it does not respond when I issue commands like "fastboot boot kfhd8-twrp-2.8.7.0-recovery.img" or fastboot flash recovery kfhd8-twrp-2.8.7.0-recovery.img" -- always just "waiting for device".
The device appears in Ubuntu's launcher as Jem PVT 04 (ONLY when in fastboot mode), but when I try to access it I get an error message about it being inaccessible.
The device still does not respond to ADB
Any other ideas?
Code:
[email protected]:~/Downloads$ fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.022s]
writing 'bootloader'...
OKAY [ 0.042s]
finished. total time: 0.063s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.546s]
writing 'boot'...
OKAY [ 0.572s]
finished. total time: 1.118s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.566s]
finished. total time: 1.097s
[email protected]:~/Downloads$ fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.050s
Click to expand...
Click to collapse
Many years later and I find this post still helpful and it saved my KFHD8.9. I had this same issue with a KFHD 8.9 that I had repurposed to a photo frame. I flashed a new ROM to it, thinking it my photo frame app might run better on a different ROM. Only I hadn't flashed a ROM for a few years and got sloppy with the flashing sequence and wound up stuck at the Kindle Fire orange logo. I spent hours reading XDA posts and trying things to get fastboot and adb to get into the device during the roughly 2 or 3 second bootup window before it gets stuck. The problem is that the way windows 10 and windows 7 handle the USB drivers makes it almost impossible. I made an Ubuntu USB stick to boot from and loaded up fastboot, adb and the android usb drivers and was able to get my KFHD into fastboot mode instantly. Once there, it was simply a matter of running the fastboot commands above and I then I was in recovery and able to restore from a backup.
Many thanks!!!
---Delete----
hi i hope someone can help me the problem is the kindle keeps rebooting and i cant get to access twrp it only goes to blue screen teamwin and just stays there i can get fastboot to work but thats about all
i think it has twrp-2.6.0.0 and cyanogenmod but thats all i know as im trying to fix it for a friend any suggestions or help would be much appreciated thank you
updae
update
ok this is what I've tried KFHD System.img Recovery Tool which is not doing any good
I've selected option 2 restore-su/supersu.apk this says writing 'system'...
FAILED (remote: : Write partition)
tried various different versions with no luck all saying failed
i have erase cache and user data
ive tried fastboot -i 0x1949 getvar product
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot boot.img
Fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.735s]
writing 'system'...
FAILED (remote: : Write partition)
finished. total time: 50.907s
I've just been trying and trying
when i try adb devices while stuck on twrp teamwin screen
i get List of devices attached
B0C910013086074C unauthorized
so i cant use any adb commands
could this be that development options has been turned off in the settings sometimes it does load up but i cant do anything as i get loads of pop ups on the screen something to do with google has stopped report or ok avg has stopped and ect so i press ok and this constantly happens it then switches off and goes back on the blue android and stays there is there any way to recover from fastboot or delete the apps what's on there using fastboot any help would be appreciated thank you for your time