Related
[Q] Help: Failed Kindle Fire 6.3 rooting/ fastboot problems (Linux), and ROM choice
Hello, everyone!
I have a Kindle Fire running OS 6.3, and I've decided to root it so I can use custom ROMs, and have access to the Google Market from the Caribbean.
Despite lots of reading and several attempts, I haven't been successful in my attempts to root my Kindle Fire from my Linux laptop. (Ubuntu 12.04.)
I've set up and rechecked adb and fastboot as outlined on this page:
http://androidforums.com/i7500-all-things-root/32481-howto-linux-adb-fastboot-mass-storage.html
And I've been trying the rooting method outlined in this thread:
http://forum.xda-developers.com/showthread.php?t=1568340
ADB successfully sees my device, as confirmed when I type
./adb devices
into my terminal with the KF attached to my USB cable.
The first set of adb commands seems to work fine:
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
...but the first fastboot command doesn't seem to do anything- I get "waiting for device" and nothing more.
I should note that "fastboot devices" command doesn't result in any output from the terminal.
What should I do next?
Also, what recommendations for a custom ROM can you folks suggest?
I am an avid reader and a gamer. I may watch some YouTube videos or sitcom reruns, but hi-def video isn't important to me at all; neither the Fire's storage nor my bandwidth are well suited to HD.
I'm currently looking at MoDaCo and MIUI.
thanks in advance,
adrian.
Any ideas, anyone?
Try turning your device off then restarting after you see the <waiting for device>
If that doesn't work you can still use adb to root your device before installing TWRP and FireFireFire. (just skip the fastboot steps)
After you are rooted you can use "Gscripts" to install FireFireFire and custom recovery
Sent from my Amazon Kindle Fire using xda premium
Just curious, what are the exact fastboot commands you are using; exactly how you typed them.
Sent from my Amazon Kindle Fire using xda premium
If you followed that guide to set up your udev rules, it may be insufficient to get it working with adb. Try this Kindle Fire specific guide...
http://forum.xda-developers.com/showthread.php?t=1475740
As for fastboot, you'll probably need elevated privileges to get that working. Switch to root or use sudo when executing fastboot commands.
Thanks for the replies!
I'm trying the suggestions now, detailed responses to follow.
Reply
The ADB commands went fine, as before.
The first Fastboot command
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
seemed also to succeed, giving OKAY status reports for downloading and booting, and ending with the feedback "finished".
The Kindle Fire then booted into recovery; I pressed the Reboot button, and the device was "stuck" on the Yellow Triangle. This is the first time I've seen this- I think it may be because I edited the adb_usb.ini file tonight.
Anyway, when I entered
fastboot oem idme bootmode 5002
I only got the "waiting for device" response.
Power cycling didn't make any difference.
I checked my adb_usb.ini and udev rules files, and they look fine.
guttaperk said:
Reply
The ADB commands went fine, as before.
The first Fastboot command
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
seemed also to succeed, giving OKAY status reports for downloading and booting, and ending with the feedback "finished".
The Kindle Fire then booted into recovery; I pressed the Reboot button, and the device was "stuck" on the Yellow Triangle. This is the first time I've seen this- I think it may be because I edited the adb_usb.ini file tonight.
Anyway, when I entered
fastboot oem idme bootmode 5002
I only got the "waiting for device" response.
Power cycling didn't make any difference.
I checked my adb_usb.ini and udev rules files, and they look fine.
Click to expand...
Click to collapse
Turn off the device. Run the fastboot command (you'll probably want bootmode 4000 to get to normal) just before powering the device up again. fastboot will tell you that it's waiting for device and it will send the command when FireFireFire goes into temporary fastboot mode. Then you can run the fastboot reboot command and it should boot to your system. Since you have FFF loaded, you can always get to recovery by pressing power during startup without using bootmode 5001 (not sure if 5002 will work anyway).
kinfauns said:
Turn off the device. Run the fastboot command (you'll probably want bootmode 4000 to get to normal) just before powering the device up again. fastboot will tell you that it's waiting for device and it will send the command when FireFireFire goes into temporary fastboot mode. Then you can run the fastboot reboot command and it should boot to your system. Since you have FFF loaded, you can always get to recovery by pressing power during startup without using bootmode 5001 (not sure if 5002 will work anyway).
Click to expand...
Click to collapse
It didn't work. But, I booted into Windows and got KFU to switch the KF to normal boot mode, so that's OK.
So, I now have FFF. But:
adb shell mount system
results in
Usage: mount [-r] [-w] [-o options] [-t type] device directory
and
adb push su /system/xbin/su
results in a warning that I don't have write access.
What should I do from here?
guttaperk said:
It didn't work. But, I booted into Windows and got KFU to switch the KF to normal boot mode, so that's OK.
So, I now have FFF. But:
adb shell mount system
results in
Usage: mount [-r] [-w] [-o options] [-t type] device directory
and
adb push su /system/xbin/su
results in a warning that I don't have write access.
What should I do from here?
Click to expand...
Click to collapse
That mount command should work in TWRP 2.0.0. I'm guessing that you are trying this while booted into the system or another version of TWRP. This one should work better in a wider range of situations....
Code:
adb shell mount -o remount,rw /system
The same problem
Hi, I have the same problem.
I stuck in the command
fastboot -i 0x1949 flash bootloader fire.zip
ok
fastboot -i 0x1949 flash recovery twrp.img
ok
fastboot reboot
My kindle fire reboot but i don't see any thing, the screen has not thing, not yellow triangle.
I hold on the power button 20s to restart. Then the power botton did not come red. My kindle fire not power on.
The adb command did not work.
The fastboot say: wait for devices
Please help me!
trungblc said:
Hi, I have the same problem.
fastboot -i 0x1949 flash bootloader fire.zip
Click to expand...
Click to collapse
This is where you screwed up. You need to read about what you are installing BEFORE you install it. The above named file is in .zip format. The newest version of FireFireFire was put in a .zip format for flashing in recovery.
If you use the "fastboot flash bootloader" command, you can only flash files in a .bin format. You now have a broken bootloader resulting in one of the hardest of bricks.
Research Firekit LiveUSB because that's your only hope at this point.
And let this be a lesson to anyone who wants to make ANY modification to their bootloader...Pay attention!
Thanks you so much
Thanks you so much. I will try and post the result soon.
I've owned you a beer now
Sorry to hear about your trouble trungblc at least you have two of the very best here watching your thread kinfauns and soupmagnet if anyone can get you out of a brick like this it would be them for sure good luck
Update status
I had used Firekit LiveUSB, and short the CPU method.
[email protected]:~/firekit# 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 [ 0.073s]
finished. total time: 0.073s
Installing x-loader...
sending 'xloader' (128 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 55.162s
Flash FFF...
sending 'bootloader' (211 KB)...
FAILED (status read failed (No such device))
finished. total time: 211.638s
Flash TWRP...
< waiting for device >
After that, kindle boot in TWRP, but when i reboot, it still not power on.
Have you tried holding the power button for 30 seconds and trying again?
Oh.
soupmagnet said:
Have you tried holding the power button for 30 seconds and trying again?
Click to expand...
Click to collapse
Oh holding for 30s? I had tried with 20s. But kindle fire still not power on.
I will try again now
Pls help me more.
[email protected]:~/firekit# 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 [ 0.072s]
finished. total time: 0.072s
Installing x-loader...
sending 'xloader' (128 KB)...
OKAY [ 0.036s]
writing 'xloader'...
OKAY [ 0.279s]
finished. total time: 0.314s
Flash FFF...
sending 'bootloader' (211 KB)...
OKAY [ 0.057s]
writing 'bootloader'...
OKAY [ 0.042s]
finished. total time: 0.099s
Flash TWRP...
sending 'recovery' (5260 KB)...
OKAY [ 1.319s]
writing 'recovery'...
OKAY [ 4.118s]
finished. total time: 5.437s
Resetting bootmode to standard boot...
...
OKAY [ 0.079s]
finished. total time: 0.079s
Loading TWRP...
downloading 'boot.img'...
OKAY [ 1.319s]
booting...
OKAY [ 0.004s]
finished. total time: 1.323s
In the TWRP, I mount the SDCARD and copy the amazon update.zip (rename from update-6.2.1.bin) to sdcard. The install - Flash - Reboot.
The Kindle Fire still not power on. I really don't know why.
It appears you did all the right stuff with the firekit but then you wiped that out by installing stock 6.2.1 are you getting the fff screen ? Can you still get into twrp? Shame you got that far with the firekit only to put yourself in the same situation might wanna try the firekit again
Thepooch said:
It appears you did all the right stuff with the firekit but then you wiped that out by installing stock 6.2.1 are you getting the fff screen ? Can you still get into twrp? Shame you got that far with the firekit only to put yourself in the same situation might wanna try the firekit again
Click to expand...
Click to collapse
I had been tried to do that before. I just pressed reboot button when it gets into TWRP many times but nothing happened. After that, I had tried to flash room again but still the same.
I don't know why.
I'm confused.... I'm following all the instructions using the toolkit v10.
I was able to unlock the bootloader without an issue, but when it comes to rooting, I'm having problems.
I use option 16 for the build, then option 4 to root. In the fastboot screen, the bottom Fastboot status says FAILInvalid Command as soon as it pulls up, then it goes to "reboot" after the 30 second wait.
It doesn't reboot automatically, so I press the power button to reboot it myself. then it reboots and then goes back into fastboot with the fail invalid command. Then this comes up:
downloading 'boot.img'
FAILED (remote: Invalid Command)
finished. total time: 0.006s
Waiting for device.
I'm at a loss. I feel like last time did this, I had to get the factory image and the boot.img file from somewhere and place them in the folders within the c:/galaxy nexus toolkit folder.
Any help would be greatly appreciated!
Thanks,
Nick
put on your big boy pants and root your phone this way:
http://forum.xda-developers.com/showthread.php?t=1529058
I have tried that... i get a similar message:
sending 'recovery' (5990 KB)
FAILED (remote: Invalid Argument)
finished. total time: 0.006s
then the fastboot status on the phone changes to "download 005d9800"
not sure what to make of that either.
is the cwm/twrp image actually named recovery? and is it in the fastboot.exe directory?
are you typing the command correctly? ( fastboot flash recovery nameofrecovery.img
It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.
waldo22 said:
It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.
Click to expand...
Click to collapse
Yep that's it
Sent from my Galaxy Nexus using Tapatalk 2
I'm guessing you mean that that's the correct way to do it and not, "yep that's you're problem." Any ideas where to go from there?
crazy... I switched to a different computer, and used the most up to date pdanet drivers, and it's going like a champ.
I have a GSM Galaxy Nexus with bootloader TWRP v2.1.2 installed. The OS has been wiped...how do I load files onto the device to flash a new OS since the device doesn't have a microSD card slot? TWRP v2.1.2 it seems does not support adb transfers and I'm not sure how I can update the bootloader or get files to the device's storage?
In short: get to fastboot mode, update bootloader if necessary (most likely not), reboot bootloader, flash a new version of TWRP, reboot into recovery and start pushing ROMs with ADB.
Sent from Samsung Galaxy Nexus @ CM11
How do I get into fastboot mode on the phone? I have the necessary files on OS X for adb and fastboot commands. What would I type to send a file to the phone once in fastboot?
rhattan503 said:
How do I get into fastboot mode on the phone? I have the necessary files on OS X for adb and fastboot commands. What would I type to send a file to the phone once in fastboot?
Click to expand...
Click to collapse
Looks like you need more assistance.
Get to fastboot: when powered off, hold VOLUME+ and VOLUME- and press POWER until it shows a green Android with START on top.
Flash a bootloader: connect to PC, and use this command: "fastboot flash bootloader *PATH-TO-BOOTLOADER*". Flashing a recovery goes similarly.
Once you have a higher version of recovery set up, get to recovery and enable ADB Sideload. Then on PC, use command "adb sideload *PATH-TO-ROM*" to sideload (push and flash) a ROM to the phone.
Sent from Google Nexus 4 @ CM11
Thank You!
I thought my phone was bricked...Thank you for taking the time to go into more details for me.
-Robert
Fastboot flashing not working?
I tried the following commands for both the latest Galaxy Nexus CWM and TWRP.
I tried "./fastboot flash bootloader ./recovery.img"
sending 'bootloader' (7124 KB)...
OKAY [ 1.206s]
writing 'bootloader'...
FAILED (remote: Write Fail)
finished. total time: 1.237s
Galaxy Nexus displays: "FASTBOOT STATUS - FAILWite Fail"
I also tried
"./fastboot flash boot recovery.img"
sending 'boot' (7124 KB)...
OKAY [ 1.207s]
writing 'boot'...
OKAY [ 0.430s]
finished. total time: 1.637s
Galaxy Nexus displays "FASTBOOT STATUS - OKAY" but when I reboot into recovery the old TWRP is still running.
What am I doing wrong?
Fixed!
Ran the command "./fastboot flash recovery recovery.*img" and it worked like a charm. Now I have a new recovery image installed...sweeeet!
I bought a bnib tmobile g2 off swappa the other day. I want to install a newer rom and started following the instructions to gain permaroot and install a recovery in the wiki here http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
First I downgraded by following this guide http://forum.xda-developers.com/showthread.php?t=1178912 which worked fine.
But now my phone is no longer recognized as a usb device when I am in android, so I can't obtain adb access. After messing around a bit, changing usb cables, plugging it into different computers, etc I booted into hboot by holding down+power. When I am in hboot I can see the phone over usb and see it when I run fastboot devices. I tried flashing cwm recovery with fastboot but it didn't work.
Code:
[email protected]:/home/necronian/xfr/root# fastboot flash recovery recovery-clockwork-5.0.2.7-vision.img
sending 'recovery' (3652 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
Hboot lists the following
Code:
VISION PVT SHIP S-OFF
HBOOT-0.82.000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010,17:59:38
Does anyone have any idea where I should go from here? I can't follow any of the wiki instructions without adb access. Otherwise everything on the phone seems to be working fine although I haven't transferred my sim over from old G2 so I don't know if the cell works.
I tried letting it install a system update that brought me to 1.22.531.8 but it still isn't detected as a usb device. I know that I have the correct drivers (I'm on linux anyway) because I previously used adb to downgrade the phone and I've tried several usb cables and computers.
Any help would be appreciated.
Looks right to me, try running fastboot as root and see if this helps ya
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Looks right to me, try running fastboot as root and see if this helps ya
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply, I was actually already running fastboot as root. I tried a few more things is morning, but no luck.
Code:
[email protected]:/home/necronian/xfr/root# fastboot erase cache
erasing 'cache'...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[email protected]:/home/necronian/xfr/root# fastboot oem rebootRUU
...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
[email protected]:/home/necronian/xfr/root# fastboot flash recovery recovery-clockwork-5.0.2.7-vision.img
sending 'recovery' (3652 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[email protected]:/home/necronian/xfr/root# fastboot flash zip ../vision.hboot-0.76.2000.zip
sending 'zip' (216 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
I don't the issue is the phone, try to update your fastboot binaries, try another USB cable or port, try renaming the images to something simple like recovery.img or bootloader.img (don't know why but I have seen this work) or try another PC or run a virtual box
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
I don't the issue is the phone, try to update your fastboot binaries, try another USB cable or port, try renaming the images to something simple like recovery.img or bootloader.img (don't know why but I have seen this work) or try another PC or run a virtual box
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ended up downloading visionary and put it on an sdcard, then I gained temproot and installed clockworkmod from the play store and the engineering hboot. I'll try flashing a new rom later but I should be good to go now.
That's your choice, but if you don't root with gfree method you could run into issues down the road, happens a lot on these forums.
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
That's your choice, but if you don't root with gfree method you could run into issues down the road, happens a lot on these forums.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just installed cyankat and I have adb access again, thanks for the help.
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----