Develop Bugs

Kindle Fire 6.3 root

Warning
Below be dragons, please gather armor and basic computing knowledge before preceding </ubergeek>. Working adb AND fastboot are requires, support for adb and fastboot are NOT offered by me. If you question is related to OSX or Linux I may be able to help. If it is windows related, don't get pissed when I tell you "I have no idea", it is the truth.
This is at your own risk! Do not blame me if something goes wrong!
For 6.2, 6.2.1 and 6.2.2 please see BurritoRoot3 -> http://rootzwiki.com/topic/13027-rootbootloader-burritoroot3-kindle-fire-root-easy-root-edition/
While I have another root exploit, Amazon neglected pokey's far more beautiful one this update, and we have no good reason to blow another root for this update, so isntead here is a guide using fbmode.
Full credits for this goes to pokey9000 (see http://forum.xda-developers.com/showthread.php?t=1414832). This guide requires you to have adb and fastboot working FOR THE KINDLE FIRE, on whatever os you are on.
Required files:
fbmode.zip - http://forum.xda-developers.com/showthread.php?t=1414832
twrp2 - http://teamw.in/project/twrp2/79
su - http://dl.dropbox.com/u/8699733/kindlefire/su
firefirefirefire http://forum.xda-developers.com/showthread.php?t=1369405
fastboot + adb for your OS of choice.
unzip fbmode.zip
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
Your kindle will "get stuck" on the kindle fire screen, but really it's just in fastboot mode.
fastboot -i 0x1949 flash bootloader <name of firefirefire image here>
fastboot -i 0x1949 flash recovery <name of recovery image here>
Your device will now boot into twrp recovery, and flash the firefirefire bootlaoder. When done it will prompt you to reboot. Upon reboot you will get stuck on the "yellow triangle" screen of firefire fire.
fastboot oem idme bootmode 5002
fastboot reboot
Once in recovery
adb shell mount system
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
Lets disable the root check before rebooting
adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
adb shell idme bootmode 4000
adb reboot
Once booted into Android, install superuser
adb install Superuser.apk

So this is strictly to add root for someone who is running stock 6.3, correct?
Thanks for the write up.

Once again! You rule.

Your fast! I was gonna suggest pokeys bootmodes before tossing an exploit but u went straight for it lol. Great work jcase
Sent from my Kindle Fire using xda premium

kernelsandirs said:
Once again! You rule.
Click to expand...
Click to collapse
It's pokey's not mine, I just posted up a guide to stop ppl from asking me

smirkis said:
Your fast! I was gonna suggest pokeys bootmodes before tossing an exploit but u went straight for it lol. Great work jcase
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I flashed back to stock and updated. My "secondary" exploit still exists, but after getting root I decided to check and see if fbmode would still work, and it does.
So we should be good for the next one as well.

Quick question you wonderful people,
Does this work with kinfauns 1.3 firefirefire?
It's basically just pokey9000's with some quirks and a different boot menu but figured I would ask the "big guys" first before I turn into one of those "I bricked my fire" folks. Cheers.

Laquox said:
Quick question you wonderful people,
Does this work with kinfauns 1.3 firefirefire?
It's basically just pokey9000's with some quirks and a different boot menu but figured I would ask the "big guys" first before I turn into one of those "I bricked my fire" folks. Cheers.
Click to expand...
Click to collapse
should work with anything

Wow, it didn't take them long to implement a root check at all. I guess more people are rooting their devices than had previously expected. They're selling them at a loss in the hopes that they will make it up in app store and prime sales. Woops. Oh well, I'm just glad I switched rooms when I did. It won't be long before they make them either unrootable (less likely) or stop selling them altogether (more likely).
Sent from my Amazon Kindle Fire using xda premium

soupmagnet said:
Wow, it didn't take them long to implement a root check at all. I guess more people are rooting their devices than had previously expected. They're selling them at a loss in the hopes that they will make it up in app store and prime sales. Woops. Oh well, I'm just glad I switched rooms when I did. It won't be long before they make them either unrootable (less likely) or stop selling them altogether (more likely).
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
no, every update has "broke" root. amazon does this so that their updates wont brick rooted devices. they haven't done anything to prevent people from rooting.

Worked fine, maybe I misread it or maybe you left out sticking superuser.apk in the adb/fastboot folder? Anywhoo I got root on 6.3 with this method, thanks

jcase said:
should work with anything
Click to expand...
Click to collapse
Indeed it does and I even re-added FFF 1.3 working like a charm. Thank you and pokey9000 for all the hard work!

Another fantastic job! Thanks so much!!

raiderep said:
Worked fine, maybe I misread it or maybe you left out sticking superuser.apk in the adb/fastboot folder? Anywhoo I got root on 6.3 with this method, thanks
Click to expand...
Click to collapse
No, I assume people setup their paths correctly during adb installation, negating the need for that.

BigFuzzyArchon said:
no, every update has "broke" root. amazon does this so that their updates wont brick rooted devices. they haven't done anything to prevent people from rooting.
Click to expand...
Click to collapse
Actually, this is the first time they have implemented something like this, its a separate service that checks for root, they run it at boot.

jcase said:
Actually, this is the first time they have implemented something like this, its a separate service that checks for root, they run it at boot.
Click to expand...
Click to collapse
they run it at boot and do what ?
would be interesting ...

Perhaps a stupid question, but where do I get the "Superuser.apk" used at the end of the instructions under 'adb install Superuser.apk'? Because It wasn't one of the files listed under needed files section. Thanks

daggy1985 said:
Perhaps a stupid question, but where do I get the "Superuser.apk" used at the end of the instructions under 'adb install Superuser.apk'? Because It wasn't one of the files listed under needed files section. Thanks
Click to expand...
Click to collapse
just google for "superuser.apk download" ...

daggy1985 said:
Perhaps a stupid question, but where do I get the "Superuser.apk" used at the end of the instructions under 'adb install Superuser.apk'? Because It wasn't one of the files listed under needed files section. Thanks
Click to expand...
Click to collapse
It's in the OP, just abbreviated as "su."
http://dl.dropbox.com/u/8699733/kindlefire/su

Droidanian said:
It's in the OP, just abbreviated as "su."
http://dl.dropbox.com/u/8699733/kindlefire/su
Click to expand...
Click to collapse
the su command and the superuser.apk are different things
the superuser.apk is a wrapper to su command

[Q] Bricked need help....

So I was loading a new cm9 rom last night and everything seemed fine until reboot now its stuck at the roms boot screen...
So I attempted to get it to reboot to recovery or fast reboot no dice...
went through all the forums and couldnt get anythign to work...
adb devices sees my kindle fine...
i can adb shell and do a ls and it see directorys and i can cd to a different directory...
and time i try too do the commands to push fbmode or any of that i always get
failed to copy 'fbmode' to '/data/local/temp': No such file or directory
if i try to put it in a different directory or mkdir through shell i get an error for read-only file system
someone please help me out here...

First of all, what recovery are you using?

Bornxero said:
So I was loading a new cm9 rom last night and everything seemed fine until reboot now its stuck at the roms boot screen...
So I attempted to get it to reboot to recovery or fast reboot no dice...
went through all the forums and couldnt get anythign to work...
adb devices sees my kindle fine...
i can adb shell and do a ls and it see directorys and i can cd to a different directory...
and time i try too do the commands to push fbmode or any of that i always get
failed to copy 'fbmode' to '/data/local/temp': No such file or directory
if i try to put it in a different directory or mkdir through shell i get an error for read-only file system
someone please help me out here...
Click to expand...
Click to collapse
/data/local/tmp not /data/local/temp

soupmagnet said:
First of all, what recovery are you using?
Click to expand...
Click to collapse
think i was using cwm cant remember for sure but i cant get it to boot into anything but the cm9 bootscreen...
and tmp vs temp doesnt matter...all directories show either no such directory or read only system

Bornxero said:
think i was using cwm cant remember for sure but i cant get it to boot into anything but the cm9 bootscreen...
and tmp vs temp doesnt matter...all directories show either no such directory or read only system
Click to expand...
Click to collapse
It is important to know because the newer ICS roms won't work with CWM, only TWRP.

from the screenshots ive seen of twrp looks like it was cwm...I just want to be able to restore to stock first then I'll do another rom via twrp...

I previously loaded the hellfire ICS without issue as well...

Hey is it a 3.0 kernel from like energy's, I ,may have your answer then. I just need to know if thats the issue you are having.
Sent from my Amazon Kindle Fire using Tapatalk 2

Bornxero said:
I previously loaded the hellfire ICS without issue as well...
Click to expand...
Click to collapse
How recently? Trust me, from what I've seen here, you need TWRP. None of the 3.0 kernel based ICS roms work well or at all with CWM these days, including Hellfire.

Bornxero said:
So I was loading a new cm9 rom last night and everything seemed fine until reboot now its stuck at the roms boot screen...
So I attempted to get it to reboot to recovery or fast reboot no dice...
went through all the forums and couldnt get anythign to work...
adb devices sees my kindle fine...
i can adb shell and do a ls and it see directorys and i can cd to a different directory...
and time i try too do the commands to push fbmode or any of that i always get
failed to copy 'fbmode' to '/data/local/temp': No such file or directory
if i try to put it in a different directory or mkdir through shell i get an error for read-only file system
someone please help me out here...
Click to expand...
Click to collapse
I would try to use KF utility which is very useful for all kinds of issues with KF and very easy to use. It has helped me a great deal.

Yea its was a 3.0 kernel...gedeROM..

forest1971 said:
I would try to use KF utility which is very useful for all kinds of issues with KF and very easy to use. It has helped me a great deal.
Click to expand...
Click to collapse
I deff. tried everything in the kindle unbrick utility if thats what your talking about...

Bornxero said:
I deff. tried everything in the kindle unbrick utility if thats what your talking about...
Click to expand...
Click to collapse
I'm guessing you still have the stock bootloader ("kindle fire" bootlogo when the device first powers up) or you would have gotten yourself to recovery already. You'll want to try and get the bootmode changed to recovery and reboot like this...
Code:
adb shell idme bootmode 5001
adb reboot
If you can get back to CWMR, the first thing you should do is flash a new bootloader... probably FFF 1.4a that you can find in the dev section. Then use that to get into fastboot mode and flash TWRP.
If you cannot change bootmodes through adb. You'll have to push fbmode or rcmode in some writeable directory. I'm guessing /data/local/tmp doesn't exist in CM9, so try pushing it to /data instead.
If none of that works and my guess about your bootloader is right, you're going to need a factory cable.

kinfauns said:
I'm guessing you still have the stock bootloader ("kindle fire" bootlogo when the device first powers up) or you would have gotten yourself to recovery already. You'll want to try and get the bootmode changed to recovery and reboot like this...
Code:
adb shell idme bootmode 5001
adb reboot
If you can get back to CWMR, the first thing you should do is flash a new bootloader... probably FFF 1.4a that you can find in the dev section. Then use that to get into fastboot mode and flash TWRP.
If you cannot change bootmodes through adb. You'll have to push fbmode or rcmode in some writeable directory. I'm guessing /data/local/tmp doesn't exist in CM9, so try pushing it to /data instead.
If none of that works and my guess about your bootloader is right, you're going to need a factory cable.
Click to expand...
Click to collapse
w00t solved thanx....i was crying over here lol...
used this to put back the old rom I was using then used KFU to install twrp and installed the new rom without issue....
thanx again....

[Q] Very Frustrated NOOOOOOOOOB

I have a Kindle Fire HD 8.9 running 8.4.8 front facing camera. In the last week i think i have read every thread on here and watched every video here and on youtube trying to get a procedure to follow. I have tried a couple and ended up 3 different times having to restore to factory to get my kindle to boot back up normal. What I would like to do is have the ability to use the google play store as well as keep my amazon loader and amazon store just because i think its easier for what i do. I know i need to root my device and prob add a 2nd bootloader. My problem is i don't see one that says that it will work with 8.4.8 or im just dumber then i think i am. I have seen some posts that say they have been successful in this venture but used different options then are stated that really makes it more confusing. I can follow a procedure just need to know which ones to use. Thanks For anybodies help....
Frustrated unrooted Kindle User Larry

larryb1951 said:
I have a Kindle Fire HD 8.9 running 8.4.8 front facing camera. In the last week i think i have read every thread on here and watched every video here and on youtube trying to get a procedure to follow. I have tried a couple and ended up 3 different times having to restore to factory to get my kindle to boot back up normal. What I would like to do is have the ability to use the google play store as well as keep my amazon loader and amazon store just because i think its easier for what i do. I know i need to root my device and prob add a 2nd bootloader. My problem is i don't see one that says that it will work with 8.4.8 or im just dumber then i think i am. I have seen some posts that say they have been successful in this venture but used different options then are stated that really makes it more confusing. I can follow a procedure just need to know which ones to use. Thanks For anybodies help....
Frustrated unrooted Kindle User Larry
Click to expand...
Click to collapse
The old procedure works with 8.4.8 so don't worry about that, the problem with it is that the current freedomboot image is incompatible with 8.4.8, it will bootloop into twrp, so you have two options, don't install 2ndbootloader+twrp until a update comes out, or the easier option, flash a rom on it like cm. If you decide to flash a custom rom on it then remember to put it on the device ahead of time or you will have to push it onto the device with "adb push" from a command line.

frustrated kindle nooooob
stunts513 said:
The old procedure works with 8.4.8 so don't worry about that, the problem with it is that the current freedomboot image is incompatible with 8.4.8, it will bootloop into twrp, so you have two options, don't install 2ndbootloader+twrp until a update comes out, or the easier option, flash a rom on it like cm. If you decide to flash a custom rom on it then remember to put it on the device ahead of time or you will have to push it onto the device with "adb push" from a command line.
Click to expand...
Click to collapse
Revision: Well it appears some how i Have my kindle rooted if i run root checker it says it is and busybox you answered my question about twrp and a second bootloader so i guess i will wait for an update hopefully soon not sure how i accomplished this bc the last thing i did was a factory restore but i have run root checker and it says it ok. my next question is can i still load google store with the stock loader until a fix comes for twerp and 2nd bootloader??????thanxxxxxxx ps whats the old proceedure?

You can still use the Google play store as long as it is rooted, also as to the method there are 2, one is for people not familiar with command line, while the other is purely from command line. While I am completely comfortable with command line myself, I used the fire flash method, the only thing you have to make sure you don't skip is the part where you check the box either above or beside the red warning text or you will have a nice red screen brick on reboot that usually you can recover from. Somehow people don't see that checkbox. Either way the bootloader has to be downgraded first, if you do it the command line way you will definitely want to md5sum the file to make sure it is a perfect downloaded copy of the original or risk a hard brick. The guides on how to do it are here:
Fireflash
Command Line
Sent from my Amazon Kindle Fire HD using Tapatalk

Very Frustrated NOOOOOOOOOB
What should I charge to replace kfhd8-freedom-boot-8.4.6.img like my version 8.4.8

boris_m80 said:
What should I charge to replace kfhd8-freedom-boot-8.4.6.img like my version 8.4.8
Click to expand...
Click to collapse
you don't theres not a newer verison out yet, just use the old one and put the rom you want to flash on it ahead of time so when it bootloops you can flash anothe rrom instead.

stunts513 said:
The old procedure works with 8.4.8 so don't worry about that, the problem with it is that the current freedomboot image is incompatible with 8.4.8, it will bootloop into twrp, so you have two options, don't install 2ndbootloader+twrp until a update comes out, or the easier option, flash a rom on it like cm. If you decide to flash a custom rom on it then remember to put it on the device ahead of time or you will have to push it onto the device with "adb push" from a command line.
Click to expand...
Click to collapse
Dam I should've read this before i tried to do mine.
It was 8.4.8 and its stuck on the twrp now coz i used the old freedomboot image with it.
If anyone could tell me a way to revert back to amazon or just get out of this loop i would be very grateful. thanks!

Adb push.... See my pm that explains further.
Sent from my Amazon Kindle Fire HD using Tapatalk

only Partly frustrated noob
stunts513 said:
you don't theres not a newer verison out yet, just use the old one and put the rom you want to flash on it ahead of time so when it bootloops you can flash anothe rrom instead.
Click to expand...
Click to collapse
Well I have the rooting down and the playstore down ive done it so many times as well as restore and factory resets now my problem is
1. first i can boot to fastboot by using adb commands but if i try to boot to fast boot using for instance KFFirstAide it just sits at waiting for device but i can command fast boot and reboot to normal from ADB . Fast boot commands dont work any fix for that.
2. I have tried to load the google aps using the tutorial both automatically and manually but cant seem to get them to work during automatic it returns with not enough disk spave for half the aps and trying to do it manually there are about 6 apks it will not let me move to system aps folder and will not let me move any of the lib.so files to system/lib says copy or move failed no reason given any body have any ideas about this thx i have have done and half not lol i see a restore again in my future if i dont get this figured out. Tried to ask in the KFFirstaide Thread but i think they are gone???????
BTW kindle fure hd 8.9 8.4.8 rooted and playstore and ES3 installed THANX

You probably didn't mount the system partition as read write before you attempted to copy. BTW Don t use the MV command across partitions, it doesn't work correctly for some reason last I checked. If you are doing this from an adb or uneven if you aren't, run this:
Code:
adb shell
su
mount -o rw,remount /system
Now copying files to system should work.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
You probably didn't mount the system partition as read write before you attempted to copy. BTW Don t use the MV command across partitions, it doesn't work correctly for some reason last I checked. If you are doing this from an adb or uneven if you aren't, run this:
Code:
adb shell
su
mount -o rw,remount /system
Now copying files to system should work.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
thanks again u always have the answers how about the fast boot issue any ideas?

I'm a little confused as to what it's doing but maybe I didn't read far back enough(also I had a almost complete post in tapatalk, came back half an hour later to finish and bumped the back button and cleared my post... OK let's see if I can finish this post without throwing my kindle across the room...) Alright first things first, if it's going into fastboot and your commands aren't worming with it keep in mind you have to install the adb driver again when it goes into fastboot. If it already doesn't show up as jem or tate or w/e and shows up as an adb device when in fastboot then remember this: fastboot commands have to be prefixed on kindles with "-i 0x1949", like so "fastboot -i 0x1949 getvar product". Hope that helps.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
I'm a little confused as to what it's doing but maybe I didn't read far back enough(also I had a almost complete post in tapatalk, came back half an hour later to finish and bumped the back button and cleared my post... OK let's see if I can finish this post without throwing my kindle across the room...) Alright first things first, if it's going into fastboot and your commands aren't worming with it keep in mind you have to install the adb driver again when it goes into fastboot. If it already doesn't show up as jem or tate or w/e and shows up as an adb device when in fastboot then remember this: fastboot commands have to be prefixed on kindles with "-i 0x1949", like so "fastboot -i 0x1949 getvar product". Hope that helps.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
well let me see if i can explain better using firstaide if i run diagnostic and boot to fastboot it goes in to fastboot and boots out using adb commands and if i send a fastboot command while it is off it boots into fastboot but if i run option thats says if kindle can respond to simple fastboot commands it says i have a damaged
*********************************************************
* This Option Will Use A Fastboot To Command To Simply *
* Query The Kindle To Display It's System Informtion *
* This Simple Non-Destructive Command Is A Good Way To *
* Determin If Fastboot Is Enabled And If The Kindle Is *
* Responding To Simple Commands. If The Kindle Responds *
* To This Command It Is Safe To Proceed With Other *
* Fastboot Commands. *
*********************************************************
Press any key to continue . . .
*************************************************
* OK Here We Go, We Are Beginning The Process! *
The system cannot find the file specified.
*The Kindle Is Not Responding To Simple Fastboot*
* Commands. Check The Device Manager For Yellow *
* Traingles. If You See One Or Two Traingles *
* Post The Screen Shot In Our Thread. You May *
* A Damaged Recovery Partition. *
*************************************************
< waiting for device >
and thats what i get. Thx
oh and still cant copy those files for google aps procedure just dont get it i can copy some of the apks to the system/aps folder and change permission so system must be rw but there are 7 of them i cant and cannot move any of the lib files at all to the system/lib folder im perplexed

This is why I do things manually... I get more technical output. Shift + right click kffa's folder and hit "open command prompt here"(or something like that. )Type "fastboot -i 0x1949 getvar product" and press enter while your kindle is in fastboot. See if it responds.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
This is why I do things manually... I get more technical output. Shift + right click kffa's folder and hit "open command prompt here"(or something like that. )Type "fastboot -i 0x1949 getvar product" and press enter while your kindle is in fastboot. See if it responds.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
C:\KFFirstAide>fastboot -i 0x1949 getvar product
< waiting for device >
thats the result!

Sounds like its either not showing up or is a driver issue then. If it doesn't show up while in fastboot, that's usually bad. If it doesn't show up, I believe you should be able to reflash the bootloader from inside whatever os is on it as long as it is rooted. Wouldn't suggest doing that unless you have to.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Sounds like its either not showing up or is a driver issue then. If it doesn't show up while in fastboot, that's usually bad. If it doesn't show up, I believe you should be able to reflash the bootloader from inside whatever os is on it as long as it is rooted. Wouldn't suggest doing that unless you have to.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
well i can boot to fastboot using adb if i need be so really not sure there is a real problem unless i have to use fast boot command then it will fail but as long as i have the option to boot to fast boot using ADB maybe im better off leaving things alone ?

larryb1951 said:
I have a Kindle Fire HD 8.9 running 8.4.8 front facing camera. In the last week i think i have read every thread on here and watched every video here and on youtube trying to get a procedure to follow. I have tried a couple and ended up 3 different times having to restore to factory to get my kindle to boot back up normal. What I would like to do is have the ability to use the google play store as well as keep my amazon loader and amazon store just because i think its easier for what i do. I know i need to root my device and prob add a 2nd bootloader. My problem is i don't see one that says that it will work with 8.4.8 or im just dumber then i think i am. I have seen some posts that say they have been successful in this venture but used different options then are stated that really makes it more confusing. I can follow a procedure just need to know which ones to use. Thanks For anybodies help....
Frustrated unrooted Kindle User Larry
Click to expand...
Click to collapse
Im in your same situation, just got the same exact kindle with 8.4.8. Would you mind telling me which tutorial you finally used that worked? I have been rooting and putting custom roms on my galaxy s4 for a year, jailbreaking iphones for years, etc., but this rooting the kindle is just driving me crazy trying to figure out what instructions to follow that dont leave me with an expensive brick. All I really want to do is be able to install google play store and apps, and change the background and/or lockscreen wallpaper... Thanks,..

Solange82200 said:
Im in your same situation, just got the same exact kindle with 8.4.8. Would you mind telling me which tutorial you finally used that worked? I have been rooting and putting custom roms on my galaxy s4 for a year, jailbreaking iphones for years, etc., but this rooting the kindle is just driving me crazy trying to figure out what instructions to follow that dont leave me with an expensive brick. All I really want to do is be able to install google play store and apps, and change the background and/or lockscreen wallpaper... Thanks,..
Click to expand...
Click to collapse
welli have rooted my kindle hd about 25 times now seem, to have no problem with that and added the play store. I used the KFFirstAide Tutorial works like a champ as far as as background and lock screen thats beyound my minimal knowledge but i believe you will need to add a custom rom t for that and i am not brave enough yet to try that im sure one of the really smart hackers could answer that. I have been able to get individual apps to load but i didnt have any luck with the install google aps part of that tuturial but the rest works fine. Good Luck

Yeah I prefer custom ROMs any day over Amazon's os. The fireflash method is the easiest as it doesn't involve any command line at all. Though it seems most people for get to check off the box next to downgrade bootloader because the warning text telling you that you need to makes it hard to notice the check box... This results in a pita to fix because we have to get into fastboot. I think I heard its even worse on 8.9 inch models when this happens because sometimes the bootloader won't show up as a fastboot service briefly and since fastboot cables don't work on 8.9 models they were screwed. But I don't tend to worry about these kinda things.
As for the wallpaper, the fix in my signature should do it, its a little buggy. Sometimes it causes peoples status bar to disappear, not sure why, assuming the dalvik cache and cache need to be cleared in such a case.
Sent from my Amazon Kindle Fire HD using Tapatalk

[Q] Kindle Fire 8.4.9 Root?

Just got a "factory refurbished" Kindle Fire 8.9 HD for a STEAL (Amazon gave $50 back on the refurb).
Anyway, now that I have it and have been playing with it for a few weeks, I've realized that the current root methods (including Root Many Android) say they have rooted it, but I don't quite have all the SU access. Digging deeper, I've found that I have System Version 8.4.9.
I can get a partial root, but cannot mount the system to RW
Anyone out there working on the Root of Kindle Fire 8.4.9?

I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Stunts,
I'd love to do that, but one of the issues with the current root is I can't use KFFirstAide to do much of anything. I would like to keep the KF as close to stock as I can, as I have kids and the FreeTime app is nice. I'm mostly looking to get the Google Play store up and working.
I've done a search but don't see anything on how to downgrade the KF from 8.4.9 without having root.
What am I missing?

You don't need root. When you initially power the device on it should briefly be detected as a jem device. Download then drivers in my signature and extract them somewhere. Now open the device manager and plug the kindle in while off, when you see the jem device, right click it and hit update drivers, and tell it to look where you extracted mine. If this is windows 8 you will have to disable driver signature enforcement first. If you can manage to get this step completed the rest is simple, it basically involves this: grab a utility like kindle fire first aid and shift + right click it and hit new command window here. With the kindle off and unplugged type
Code:
fastboot -I 0x1949 getvar product
once it says waiting for device plug the kindle in while it is off, it should enter fastboot, from there you can use kffa to downgrade it.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
You don't need root. When you initially power the device on it should briefly be detected as a jem device. Download then drivers in my signature and extract them somewhere. Now open the device manager and plug the kindle in while off, when you see the jem device, right click it and hit update drivers, and tell it to look where you extracted mine. If this is windows 8 you will have to disable driver signature enforcement first. If you can manage to get this step completed the rest is simple, it basically involves this: grab a utility like kindle fire first aid and shift + right click it and hit new command window here. With the kindle off and unplugged type
Code:
fastboot -I 0x1949 getvar product
once it says waiting for device plug the kindle in while it is off, it should enter fastboot, from there you can use kffa to downgrade it.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Tried to downgrade. I can get to fastboot without any issues, but it looks like there are issues with KFFA (I'm using 4.1.87-beta). I get the following when trying to "Completely Restore the KFHD 8.9 8.1.4" (Option 7)
(snipped to the last one for space, all have the final "Unable to establish SSL Certificate)
**********************************************************************
*I Have Fetched The recovery.img - 1 More To Download................*
**********************************************************************
--2014-06-14 13:04:18-- y
<snip> (don't have 10 posts so can't post all the links)
HTTP request sent, awaiting response... 302 FOUND
Cookie coming from address attempted to set domain to dropbox.com
Cookie coming from address attempted to set domain to dropbox.com
Location: (removed as I don't have 10 posts)] [following]
--2014-06-14 13:04:18-- (removed as I don't have 10 posts)
Connecting to address... connected.
ERROR: cannot verify address's certificate, issued by `address High Assurance Server CA':
Unable to locally verify the issuer's authority.
To connect to address insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
****************************************************************************************
*I Have Fetched The system.img - I Am Ready To Flash The 3 Images......................*
****************************************************************************************
Press any key to continue . . .
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
Would You Like To Wipe Data And Cache (y/n) ?
After this, I wipe data and cache and then didn't finish the registration (so I didn't get "pushed" an update, just in case)
Come back up and I'm still in 8.4.9
I've gone in to dropbox and pulled all the images to my computer. Is there a way to move these and get them properly mounted in adb? I'm a relative n00b but getting a bit more comfy in the adb environment and may be able to do it from there, with a bit of help?
Thanks!

Do not actually use KFFA use this method --> http://forum.xda-developers.com/showthread.php?t=2468988
You only need kffa for adb.exe and fastboot.exe ect.
PS. Be sure NOT to to connect to the Internet after until you have OTA blocked, and if you Like you can manually upgrade to what ever firmware you would like, I went back to v848

jmpiv4 said:
Do not actually use KFFA use this method --> http://forum.xda-developers.com/showthread.php?t=2468988
You only need kffa for adb.exe and fastboot.exe ect.
PS. Be sure NOT to to connect to the Internet after until you have OTA blocked, and if you Like you can manually upgrade to what ever firmware you would like, I went back to v848
Click to expand...
Click to collapse
Now I'm stuck in the Kindle Fire boot screen - orange. I got through all the flashes without an issue and unplugged on the final reboot per your instructions. I try to adb to it and there are no devices found.
Edit: Whoops. Was using my old shortcut command keys (arrows) and just changed what flashed to system - forgot to flash to the right places. Trying again!

Illinifan97 said:
Now I'm stuck in the Kindle Fire boot screen - orange. I got through all the flashes without an issue and unplugged on the final reboot per your instructions. I try to adb to it and there are no devices found.
Edit: Whoops. Was using my old shortcut command keys (arrows) and just changed what flashed to system - forgot to flash to the right places. Trying again!
Click to expand...
Click to collapse
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "

KatanAlive said:
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
Click to expand...
Click to collapse
Is your Kindle up and running? I also have a Kindle Fire HD 8.9 and yesterday I downloaded latest update.bin file (8.4.9) from Amazon and updated my Kindle and later rooted it using the manual method described in http://forum.xda-developers.com/showthread.php?t=2069117 thread. It was total success. Just don't miss a single step from that method.
Actually I had my Kindle (ver 8.4.8) rooted before and Google Play installed with the same method but I was having some issues (not because of rooting but because I had been tinkering with the system apps) so decided to update to overcome those glitches. I installed RootKeeper from Google Play and told it to protect my root access during update process but this crap could not. After update I lost my root and now Google Play Store and related services stopped working, as I didn't have root access so couldn't manage to delete their apks from System apps. So I decided to root it again with the same method and I did it, after rooting it again I went to system apps and deleted old apks of Google Play and other related apks. Then I agin installed Google Play using the automatic method mentioned in above thread.
Sorry if this story is irrelevant but I just wanted to share my experience so any one searching for something could find a clue from it. One thing is confirmed here, KFFirstAid can easily install Google Play after 8.4.9 update and the above mentioned manual method can root it successfully. I am not sure about automatic method though.

you have been very usefull! Thx...but, i still can't root with any method
Can i ask you for some help (i've actually the 8.4.9 version) in private?

KatanAlive said:
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
Click to expand...
Click to collapse
KatanAlive said:
you have been very usefull! Thx...but, i still can't root with any method
Can i ask you for some help (i've actually the 8.4.9 version) in private?
Click to expand...
Click to collapse
Of course. I am not very knowledgable but I would try my best to share my experience.

akb1ajay said:
Of course. I am not very knowledgable but I would try my best to share my experience.
Click to expand...
Click to collapse
I write you a pm

I just tried the fastboot stuff and it will not enter fastboot. Do i need a fastboot cable?
Also i would like to remove all things kindle aka custom roms. So thats a non issue meaning if the only way to root a hd 8.9 with 8.4.9 rom version that was some how pushed on to my kindle via ota that i had turned off but got turned back on some how. Then thats fine and infact i want to remove amazons crap rom any how.

Nanaki-seto said:
I just tried the fastboot stuff and it will not enter fastboot. Do i need a fastboot cable?
Also i would like to remove all things kindle aka custom roms. So thats a non issue meaning if the only way to root a hd 8.9 with 8.4.9 rom version that was some how pushed on to my kindle via ota that i had turned off but got turned back on some how. Then thats fine and infact i want to remove amazons crap rom any how.
Click to expand...
Click to collapse
Read post 9 on previous page.

akb1ajay said:
Read post 9 on previous page.
Click to expand...
Click to collapse
Already tried this. It works partially only once it is fully done rebooting the kindle fire is running so slowly as to be unworkable for any thing. Also the lock swipe etc looks torn inhalf. At this point i have to use recorvery to get it to respond properly. I need to root or change rom out right (preferably) But the fast boot commands do nothing. Tried getting it to show up as gem device and use the other drivers that are suppose to let me enter fast boot by a fastboot command. It does not seem to work.
So after trying the method in post 9 again i need to recover to factory again. As it is running extremely slow

stunts513 said:
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Stunts what is the best surefire way to downgrade? My previously rooted kindlefire hd 8.9 just got ota updated to 8.4.9. I had disabled ota i thought but it would seem it wasnt. Now i can not reroot it properly. I want to just go with a custom rom and be done with this mess. I do not have a fastboot cable. But it would seem there are ways around that such as the fastboot -i etc etc how ever i tried that and it did not work (including getting the drivers to the jem. I think i may be missing the chance to get the update drivers bit done intime (not sure here). At any rate help!!! heh
Again what i want to do
Downgrade to easiest rom ver to flash from to a custom rom using what ever meathod is the most effective minus fastboot cable. also recommendations on rom to use are very welcome.

akb1ajay said:
Is your Kindle up and running? I also have a Kindle Fire HD 8.9 and yesterday I downloaded latest update.bin file (8.4.9) from Amazon and updated my Kindle and later rooted it using the manual method described in http://forum.xda-developers.com/showthread.php?t=2069117 thread. It was total success. Just don't miss a single step from that method.
Actually I had my Kindle (ver 8.4.8) rooted before and Google Play installed with the same method but I was having some issues (not because of rooting but because I had been tinkering with the system apps) so decided to update to overcome those glitches. I installed RootKeeper from Google Play and told it to protect my root access during update process but this crap could not. After update I lost my root and now Google Play Store and related services stopped working, as I didn't have root access so couldn't manage to delete their apks from System apps. So I decided to root it again with the same method and I did it, after rooting it again I went to system apps and deleted old apks of Google Play and other related apks. Then I agin installed Google Play using the automatic method mentioned in above thread.
Sorry if this story is irrelevant but I just wanted to share my experience so any one searching for something could find a clue from it. One thing is confirmed here, KFFirstAid can easily install Google Play after 8.4.9 update and the above mentioned manual method can root it successfully. I am not sure about automatic method though.
Click to expand...
Click to collapse
This worked for getting root back, but didn't initially work for the Google apps. It looks like Amazon filled the file system /system leaving no room for the apps. Since I don't use Text To Speech, I removed /system/tts/ivona/vox_en_us_salli22i which is 100+MB, freeing plenty of space for Google apps. I saved a copy to /sdcard just in case. I recommend saving a copy of system.img first, since my first attempts at removing files deleted the apk, but didn't free the space and I had to do a restore once.

Full Manual Root - Kindle Fire HD 8.9 System Version 8.4.9 on Ubuntu Linux 14.04
Hi Guys,
If none of the usual methods work, here is a method for rooting Kindle Fire HD 8.9 with the new 8.4.9 system version. It was written for and tested on Linux, but should work on Windows as well.
Requires Linux and "DOS" scripting knowledge - particularly if anything goes wrong. If you are not familiar with linux shell, please do not try!
USE AT YOUR OWN RISK!!!
I was struggling a whole day with rooting my Kindle Fire HD 8.9 with the 8.4.9 stock rom. I use Linux (Ubuntu 14.04) and don't really have access to Windows. I've tried several methods, including several versions of the Bin4ry method, but the result was:
a) nothing happened at the end,
b) the system was hell slow, but did not get the root prompt/access.
Finally I've managed to root with a full manual - no script running - method. It was based on Bin4ry v18.5.1 root: the tools were uploaded to the kindle from the package, and the rooting steps were based on the RunMe.bat (manually entering step-by-step). It requires an installed adb on the linux machine (I have it from an Android SDK install)!
Sources:
http://forum.xda-developers.com/showthread.php?t=2277105 : I've started from here. I recommend to read this before starting the process.
http://forum.xda-developers.com/showthread.php?t=2069117 : "C-2) The next steps are used to Root the Kindle - Alternative Method (Manual Version)"
http://pocketnow.com/2012/10/10/root-without-unlocking : for understanding the exploit
Requirements:
1. Install adb on the linux machine.
2. Download Root MANY ANDROID 32-bit!(Dropbox): https://dl.dropbox.com/u/54456659/Win32.zip and extract.
Rooting:
The steps are based on manually entering the commands of the "1)Normal" method of the RunMe.bat:
1) In a terminal change to the directory where Win32.zip was extracted and enter:
Code:
adb push stuff/busybox /data/local/tmp/.
adb push stuff/su /data/local/tmp/.
adb push stuff/Superuser.apk /data/local/tmp/.
adb shell chmod 755 /data/local/tmp/busybox
2) Restore the fake “backup”. Note: _do not click restore on your Kindle device_! Just enter the command into the command prompt on your PC and press the enter key:
Code:
adb restore fakebackup.ab
3) Run the “exploit”:
Code:
adb shell “while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done”
(It will display a lot of "link failed File exists" lines)
4) Now that the “exploit” is running, click restore on your device.
5) Once it finishes, reboot your device. Note: Don’t use your kindle yet, this exploit reboots into emulator mode which will be laggy with a flickering screen (or no display at all). This is normal.
Code:
adb reboot
6) Once rebooted, open a shell:
Code:
adb shell
Check: Once you do step 6, your should have a root shell (your prompt should be #, not $). If it’s not #, start again from step 2.
7) Continue with the steps of the RunMe.bat - now entering the commands in the root shell:
Code:
/data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
chmod 655 /system/app/Superuser.apk
chmod 755 /system/xbin/busybox
rm /data/local.prop
reboot
Done .

The Method described above didn't work for me.
Tried to do it step by step but the exploit part is not working, gives me a syntax error.
Then i used runme.bat and the exploit seems to work (slow reboot, scrambled kindle logo) but root isn't working properly afterwards.
It's kinda half-rooted now, with SuperSU working and displaying "granted root access..."-messages but if i try to install the play store i'm stuck.
ESexplorer is in root mode, mounted system R/W but when i try to move vending.apk to system/app it fails. No root access it seems
Opening SuperSU results in a failed update process....
Any kind of help is deeply appreciated...

Fixing that syntax error
Toastytwo said:
The Method described above didn't work for me.
Tried to do it step by step but the exploit part is not working, gives me a syntax error.
Then i used runme.bat and the exploit seems to work (slow reboot, scrambled kindle logo) but root isn't working properly afterwards.
It's kinda half-rooted now, with SuperSU working and displaying "granted root access..."-messages but if i try to install the play store i'm stuck.
ESexplorer is in root mode, mounted system R/W but when i try to move vending.apk to system/app it fails. No root access it seems
Opening SuperSU results in a failed update process....
Any kind of help is deeply appreciated...
Click to expand...
Click to collapse
This method worked for me! I also got a syntax error the first time arround but I fixed it by splitting this command (adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done") into 2 separate command 1) adb shell, 2) while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done
After taking away the quotes it worked exactly as described!

Bricked AFTV1 - Is repair possible with hardware mod?

I feel like a bonehead cuz I bricked my FireTV by getting ahead of myself. This FTV came shipped with 51.1.3.0 and I have always had updates blocked in my router. I purchased a SD-card adapter and was able to gain root by injecting su into /system/xbin, Installed busybox, and all that fun stuff. Everything was going along just fine, until i tried to install RBox's boot menu/Recovery without fully understanding everything. Following a guide, I ran the full bootloader unlock script and it seemed to complete fine and FTV would still boot normally with root access. What I did next is the following, trying to install recovery I download the bootmenu.img file, uploaded it to my sd card and issued the following commands:
mount -o remount,rw /system
mkdir /system/boot
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
exit
exit
adb reboot​My FTV restarted and has been stuck at the FireTV Logo every since. Not exactly sure where I went wrong. Did I have to downgrade before trying to install the boot menu? I did to the checksum test on the file before using it and it matched. Anyways, I tried factory reseting by holding the back/right remote control keys....no joy, tried the alt+prtsc+i keyboard procedure....nothing, tried a fastboot cable recovery.......got the drivers installed, firetv listed in devices using kindle usb driver, but although fastboot would connect and communicate to the FTV, it wouldn't respond to any fastboot commands.
I have the ability to gain direct access to the FTV's file system, but although my electronic skills are superb, my linux/android skills are quite lacking. When I disable the CPU and connect the flash to my Ubuntu 15 VMWare system via usb, I am able to mount up 6 linux partitions from the FTV. I explored around them, but don't want to go plowing through anything like a bull in a china shop until I have a direction to take from someone who actually knows what they are doing to get my beloved Firetv booting again. Any suggestions would be GREATLY appreciated. Thanks in advance.

Plug in the fire TV with a USB to USB to your PC. If the boot loader is fully unlocked you should be able to fastboot boot clockwork recovery and flash the rom that doesn't require boot menu.

{ParanoiA} said:
Plug in the fire TV with a USB to USB to your PC. If the boot loader is fully unlocked you should be able to fastboot boot clockwork recovery and flash the rom that doesn't require boot menu.
Click to expand...
Click to collapse
I mentioned in my OP that I have already tried this and although the fastboot drivers install correctly, the "fastboot devices" command returns nothing, and the "fastboot reboot recovery" command waits for about 10 seconds, then returns "no reply received by device". So this is a dead end and I guess the problem lies in the fact that my bootloader failed to unlock. I was also guessing that the solution would be to put the stock bootloader back onto the FireTV, but cannot figure out where it goes on the fire's 6 mounted partitions in linux using the soldered-in USB flash device. I can access the /system directory, but cannot locate the /dev/block/platform/msm_sdcc.1/by-name/boot folder where the bootmenu.img file was written to which caused the bricking. Any other ideas?

No I'm not that familiar with the partitions. @rbox would probably be the best one to answer this

Adaptel said:
I mentioned in my OP that I have already tried this and although the fastboot drivers install correctly, the "fastboot devices" command returns nothing, and the "fastboot reboot recovery" command waits for about 10 seconds, then returns "no reply received by device". So this is a dead end and I guess the problem lies in the fact that my bootloader failed to unlock. I was also guessing that the solution would be to put the stock bootloader back onto the FireTV, but cannot figure out where it goes on the fire's 6 mounted partitions in linux using the soldered-in USB flash device. I can access the /system directory, but cannot locate the /dev/block/platform/msm_sdcc.1/by-name/boot folder where the bootmenu.img file was written to which caused the bricking. Any other ideas?
Click to expand...
Click to collapse
boot is partition 10. You should be able to use gdisk on the mmc device to see the partition table with the partition labels.

rbox said:
boot is partition 10. You should be able to use gdisk on the mmc device to see the partition table with the partition labels.
Click to expand...
Click to collapse
Thank you for chiming in Rbox. I am in awe of your amazing work with FireTV and keep up the spectacular work!!!
Anyways, I wanted to attach a screenshot of my dead fireTV1's MMC partition layout, but becasue I am new here, the forum won't let me add a screenshot jpg. I used gparted because as I said before, I am a linux novice and couldn't get gdisk to show me what I wanted to. Partition 10 is labeled "boot", is 10MB in size, and shows up as having a file system type "Unknown". Should I dd the stock recovery file to this partition, or what do I need to do to undo these commands which bricked my device. (Which I am pretty sure due to the fact that I didn't get the bootloader unlocked correctly).
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot​Thank you so much for your help in advance!

Adaptel said:
Thank you for chiming in Rbox. I am in awe of your amazing work with FireTV and keep up the spectacular work!!!
Anyways, I wanted to attach a screenshot of my dead fireTV1's MMC partition layout, but becasue I am new here, the forum won't let me add a screenshot jpg. I used gparted because as I said before, I am a linux novice and couldn't get gdisk to show me what I wanted to. Partition 10 is labeled "boot", is 10MB in size, and shows up as having a file system type "Unknown". Should I dd the stock recovery file to this partition, or what do I need to do to undo these commands which bricked my device. (Which I am pretty sure due to the fact that I didn't get the bootloader unlocked correctly).
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot​Thank you so much for your help in advance!
Click to expand...
Click to collapse
You can just dd that boot.img in /system/boot back to the partition to undo what you did.

rbox said:
You can just dd that boot.img in /system/boot back to the partition to undo what you did.
Click to expand...
Click to collapse
That did the trick & my FTV is now booting and still has root and all my stuff just where I left it......you are the best!
Should I not even try to install boot menu/recovery? I thought i was on 51.1.3.0, but I just now checked and I am actually on 51.1.4.0. I ran the full bootloader unlock script right before I reflashed the recovery partition which bricked my fire. Is it because 51.1.40 is the version-of-no-return for installing recovery, should I have ran the partial bootloader unlock, or something else? Any advice? I am happy to have my Fire TV working again, but half the fun of this is learning and understanding what goes on inside and how it works. THANKS AGAIN!!!!!

Adaptel said:
That did the trick & my FTV is now booting and still has root and all my stuff just where I left it......you are the best!
Should I not even try to install boot menu/recovery? I thought i was on 51.1.3.0, but I just now checked and I am actually on 51.1.4.0. I ran the full bootloader unlock script right before I reflashed the recovery partition which bricked my fire. Is it because 51.1.40 is the version-of-no-return for installing recovery, should I have ran the partial bootloader unlock, or something else? Any advice? I am happy to have my Fire TV working again, but half the fun of this is learning and understanding what goes on inside and how it works. THANKS AGAIN!!!!!
Click to expand...
Click to collapse
You can't unlock that version. You should block updates and wait until I release TWRP and prerooted fireos5 roms.

hey rbox, quick question: once you release the prerooted fireos5 is it possible to dd recovey.img through hardware mmc to get the unlocked bootloader?
my firetv got bricked using supersu me and now i wonder what the best way is to bring it back alive..

Adaptel said:
That did the trick & my FTV is now booting and still has root and all my stuff just where I left it......you are the best!
Click to expand...
Click to collapse
Can you tell me the command wich give you finally the success ?
Another question by me is how to create a system.img from the bin files.
I know that there is folder in the bin-zip but how to create from them a system.img or how to create a valid stuck-recovery.img
Greetings by Idijt

I_did_it_just_tmrrow said:
Can you tell me the command wich give you finally the success ?
Click to expand...
Click to collapse
Certainly. The process I went through (using Ubuntu Linux 15 with Fire's eMMC chip connected via USB via hardware mod) is as follows (keep in mind I'm not a Linux genius but know enough to get by:
When eMMC is successfully connected, Ubuntu auto-mounted 6 partitions with partition names/ids that consisted of a long string of hex digits.
By looking around these ext4 partitions, I noticed that one of them was obviously the entire contents of the Fire's /system folder.
I navigated to /system/boot/ and saw that the boot.img file was in there. I right clicked on it, selected Properties to gain a full path of the files location and copied it
I installed and ran gparted partition editor to view the partition layout of the eMMC. There are a total of 20 partitions on fire's disk, (/dev/sdb1 through /dev/sdb20 on my system) but most of them aren't mounted because they use a non-linux standard file format).and as Rbox said. Partition 10 was 10.00MB in size, type=unknown, name=boot, and was located at /dev/sdb10 (on my system).
Now all I had to do was issue this command: sudo dd if=/<long string of hex digits described abouve>/system/boot/boot.img of=/dev/sdb10
Remove 4 wires soldered to Firetv, Solder CPU oscillator pads together, Reboot and Cheer​The fire tv rebooted fine and everything was good....but I do have an update with even more good news. I felt emboldened having access to my MMC ao since my software was on version 51.1.40, I was able to then follow the guide (EXACTLY) at http://solderwiresandplastic.com/20...the-amazon-firetv-to-achieve-root-privileges/​starting at "Step 2", and was able to successfully install the latest clockworkmod recovery, RBox's AWESOME boot menu, and install RBox's latest prerooted rom. This worked because I was on version 51.1.4.0 and the bootloader eFuse freeze occurred on 51.1.4.1 (so don't even think of trying the steps in this link if your box has 51.1.4.1 or higher on it. Hope this makes sense and helps in some way.

mrchrister said:
hey rbox, quick question: once you release the prerooted fireos5 is it possible to dd recovey.img through hardware mmc to get the unlocked bootloader?
my firetv got bricked using supersu me and now i wonder what the best way is to bring it back alive..
Click to expand...
Click to collapse
No. To unlock your bootloader you need an old version of the aboot partition. But if you're on the latest software, you will brick if you attempt to flash that old version.

thanks, good to know!
Sent from my iPhone using Tapatalk

Hello. I have a bricked fire tv because of supersu me. I've extracted a system.img from a working one via adb. My problem is, that i don't know how to install this on my bricked one with hardware mod (card reader). Any advice?

where did you find the 5.0.5 image i need it also , mines bricked also from super sume just waiting for EEMC chip to come in..

geist_patrick said:
Hello. I have a bricked fire tv because of supersu me. I've extracted a system.img from a working one via adb. My problem is, that i don't know how to install this on my bricked one with hardware mod (card reader). Any advice?
Click to expand...
Click to collapse
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
[/COLOR]
geist_patrick said:
Hello. I have a bricked fire tv because of supersu me. I've extracted a system.img from a working one via adb. My problem is, that i don't know how to install this on my bricked one with hardware mod (card reader). Any advice?
Click to expand...
Click to collapse
think you could send me your img file thanks. as im on 5.0.5 firmware bricked also. thanks

Rootet system.img
https://drive.google.com/open?id=0B8P7DODeSgf8cmk5UUx4UUFXYkk