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] demo unit unsuccessful

hey guys. I have a demo unit.
Now before anything else, I should say that I looked at all three other threads on demo units, and that didn't help.
I looked at ThePooch's alternate method, and it didn't work.
In KFU, it gives the output of what is in the picture.
and in Soupkit, it says "permission denied" when trying to install either FFF or TWRP (I can't remember which, but if this is important, I will find out).
Can someone shed some info on what to do?
More pics are available to those who ask.

jma9454 said:
hey guys. I have a demo unit.
Now before anything else, I should say that I looked at all three other threads on demo units, and that didn't help.
I looked at ThePooch's alternate method, and it didn't work.
In KFU, it gives the output of what is in the picture.
and in Soupkit, it says "permission denied" when trying to install either FFF or TWRP (I can't remember which, but if this is important, I will find out).
Can someone shed some info on what to do?
More pics are available to those who ask.
Click to expand...
Click to collapse
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.

soupmagnet said:
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.
Click to expand...
Click to collapse
This could be the VMWare problem that you were mentioning in the other thread. upon reboot, VMWare says something to the effect that it could not connect to the kindle because it is in use by another program. I will try USB-Ubuntu in a few hours, but I think it didn't work last night, if i remember correctly.

I have witnessed one demo unit that was completely unrootable even with the use of a factory cable. So at the end it was only good for parts and the motherboard unusable.

soupmagnet said:
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.
Click to expand...
Click to collapse
when trying to switch bootmodes, Ubuntu just reboots the kindle. It isn't able to get into fastboot. If I could figure out how to take a screeshot of this I would, but I don't know how.
Anyways, I forgoed that, and tried to just do the TWRP installation and this is what I got:
Verifying MD5 checksum...
openrecovery-twrp-2.2.2.1-blaze.img: OK
Checksum matched.
Installing openrecovery-twrp-2.2.2.1-blaze:
Please wait...
1122 KB/s (4972544 bytes in 4.324s)
/dev/block/mmcblk0p5: cannot open for write: Permission denied
Team Win Recovery Project has been installed.
Do you wish to reboot into recovery now?
-- any ideas?

That`s pretty much what I experienced with the demo unit that would not root, it simply would not enter fastboot no matter which approach I took. I can take a look for you but I feel it`s pretty much a moot point if it wont enter fastboot. Power the device off, open a terminal
Code:
fastboot -i 0x1949 getvar product
hit enter, when it says waiting for device, plug the kindle in. if it does not enter fastboot and return product: kindle you are dead in the water.

jma9454 said:
This could be the VMWare problem that you were mentioning in the other thread. upon reboot, VMWare says something to the effect that it could not connect to the kindle because it is in use by another program. I will try USB-Ubuntu in a few hours, but I think it didn't work last night, if i remember correctly.
Click to expand...
Click to collapse
I've really gotta start reading the names on these posts
jma9454 said:
when trying to switch bootmodes, Ubuntu just reboots the kindle. It isn't able to get into fastboot. If I could figure out how to take a screeshot of this I would, but I don't know how.
Anyways, I forgoed that, and tried to just do the TWRP installation and this is what I got:
Verifying MD5 checksum...
openrecovery-twrp-2.2.2.1-blaze.img: OK
Checksum matched.
Installing openrecovery-twrp-2.2.2.1-blaze:
Please wait...
1122 KB/s (4972544 bytes in 4.324s)
/dev/block/mmcblk0p5: cannot open for write: Permission denied
Team Win Recovery Project has been installed.
Do you wish to reboot into recovery now?
-- any ideas?
Click to expand...
Click to collapse
That's the tricky thing about ADB and shell scripts. I won't go into too much detail, but part of that has to do with how ADB handles the exit status. Typically in Linux, an error results in an exit status of 2 (sometimes 1 depending on the type of error). ADB tends to have errors come out with an exit status of 0, which is why it said TWRP had been installed, when in all actuality it hadn't. The reason TWRP wasn't installed is because you need to either have root privileges, or be in fastboot, hence my previous instructions to boot into fastboot first.
In my opinion, your best bet would be to forgo the VM, forget about the dilapidated WinXP computer and figure out a way to boot your Win7 computer into Ubuntu from a USB stick. You are dealing with way too many variables to effectively determine exactly where things are going wrong.

I 'fixed' two demo KF's, messed up a lot on the first (lucky I didn't brick it).... On the second, I used a fast boot cable and installed TWRP, had a JB ROM on it in 15 minutes.
Try this.... Send TWRP to it using the command line, when it says 'waiting on device', open another window and get it to reboot in fastboot mode. On the first KF I found the utility would only put it in fast boot for a few seconds, but it was long enough to write TWRP if you did it this way.
Not sure why some won't work at all, maybe Amazon got smart on the demo units.
Larry
Sent from my Kindle Fire that thinks it's a Nexus 7

soupmagnet said:
I've really got to start reading the names on these posts
That's the tricky thing about ADB and shell scripts. I won't go into too much detail, but part of that has to do with how ADB handles the exit status. Typically in Linux, an error results in an exit status of 2 (sometimes 1 depending on the type of error). ADB tends to have errors come out with an exit status of 0, which is why it said TWRP had been installed, when in all actuality it hadn't. The reason TWRP wasn't installed is because you need to either have root privileges, or be in fastboot, hence my previous instructions to boot into fastboot first.
Click to expand...
Click to collapse
The above statement took place from USB boot, not VMware. Also, like I said, I attempted to set it into fastboot and it just booted regularly. I tried several times with different cables and ports with no success.
Sent from my Amazon Kindle Fire using Tapatalk HD

I will stick with my original idea no fastboot = no fun. You cant push FBmode manually because installation from unknown sources is disabled by default on a large percentage if not all demo units. Regardless if the device doesn`t enter fastboot not much you can do. Taking advantage of the small window of fastboot at boot is risky if the write time isn`t long enough to get it sent and written but it could be your best bet. IMO I would not attempt this with the bootloader only recovery no harm no fowl.

[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

[Help] Bricked AFTV 1 stuck at colorful Logo. No boot menu.

AFTV 1.
I just rooted using kingroot. Then tried to swipe kingsuer by supersu. Something happened.
Therefore, I have no CWM or others. I do not have boot menu.
I have a USB cable. I've tried fastboot devices but no devices found.
I've tried adb reboot recovery and I was into Amazon system recovery <3>, but there was on recovery menu at all.
Please help. It looks I could use shell and su, but not fastboot.
I am not an expert so please forgave my languages.
Thanks.
C:\adb>cmd.exe C:\adb
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
1|[email protected]:/ $ reboot recovery
C:\adb>

vincentjones said:
AFTV 1.
I just rooted using kingroot. Then tried to swipe kingsuer by supersu. Something happened.
Therefore, I have no CWM or others. I do not have boot menu.
I have a USB cable. I've tried fastboot devices but no devices found.
I've tried adb reboot recovery and I was into Amazon system recovery <3>, but there was on recovery menu at all.
Please help. It looks I could use shell and su, but not fastboot.
I am not an expert so please forgave my languages.
Thanks.
C:\adb>cmd.exe C:\adb
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
1|[email protected]:/ $ reboot recovery
C:\adb>
Click to expand...
Click to collapse
Don't know if this will work but here's a link you may wanna try -
http://forum.xda-developers.com/showthread.php?t=2799779
If you don't get any joy sit tight cause I'm sure rbox may make a in bricking image at sum point like he did with our AFTV2 so don't panic just play the waiting game ok.
If this helps press that thanks button

supersume is causing issues with devices. lots of threads open regarding this.
why did you need root for if you are not good at understanding?

vincentjones said:
AFTV 1.
I just rooted using kingroot. Then tried to swipe kingsuer by supersu. Something happened.
Therefore, I have no CWM or others. I do not have boot menu.
I have a USB cable. I've tried fastboot devices but no devices found.
I've tried adb reboot recovery and I was into Amazon system recovery <3>, but there was on recovery menu at all.
Please help. It looks I could use shell and su, but not fastboot.
I am not an expert so please forgave my languages.
Thanks.
C:\adb>cmd.exe C:\adb
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
1|[email protected]:/ $ reboot recovery
C:\adb>
Click to expand...
Click to collapse
You should had visit this forum and read first before you removed kingroot with superuser, box is bricked for now and your only hope is ....rbox. Removing kingroot with superuser will brick your box!
Wait for him to release OS5 recovery for fireTV 1 and he may be releasing an unbrick image as he did for fireTV 2. This is your only hope for now anyway.

I knew there was a risk but I did it anyway. Now I regret it.
Actually I saw the firetv2 unbrick image and I was almost started to try it for my fireTV 1 before I posted this help post. Now I know I should wait.
Thanks a lot.
I really appreciated.
bula1ca said:
You should had visit this forum and read first before you removed kingroot with superuser, box is bricked for now and your only hope is ....rbox. Removing kingroot with superuser will brick your box!
Wait for him to release OS5 recovery for fireTV 1 and he may be releasing an unbrick image as he did for fireTV 2. This is your only hope for now anyway.
Click to expand...
Click to collapse

Supersume was what I used.
I do not know why I did it. I just can not help doing it even I know it was stupid. Maybe it was the new feature or the desire of getting rid of kinguser.
Thanks a lot.
El_Nino9 said:
supersume is causing issues with devices. lots of threads open regarding this.
why did you need root for if you are not good at understanding?
Click to expand...
Click to collapse

deanr1977 said:
Don't know if this will work but here's a link you may wanna try -
http://forum.xda-developers.com/showthread.php?t=2799779
If you don't get any joy sit tight cause I'm sure rbox may make a in bricking image at sum point like he did with our AFTV2 so don't panic just play the waiting game ok.
If this helps press that thanks button
Click to expand...
Click to collapse
I've tried the keyboard method and no luck.
I better just wait.
Thanks.

There is no way to create an unbricking image for the FireTV1 if your bootloader is locked.

rbox said:
There is no way to create an unbricking image for the FireTV1 if your bootloader is locked.
Click to expand...
Click to collapse
Cheers for clearing that up rbox
vincentjones said:
I've tried the keyboard method and no luck.
I better just wait.
Thanks.
Click to expand...
Click to collapse
Oh well sorry mate but unless someone else has any ideas you have your answer above
Sent from my SM-G900F using Tapatalk

Thanks a lot. rbox.
rbox said:
There is no way to create an unbricking image for the FireTV1 if your bootloader is locked.
Click to expand...
Click to collapse

rbox said:
There is no way to create an unbricking image for the FireTV1 if your bootloader is locked.
Click to expand...
Click to collapse
that sucks big time glad i got an FTV 2 with the whole preloader method which can take 2 hours or so but at least revive.
i was thinking if he has adb, can he not push an official update to it and revive it?
the keyboard trick usually works but i understand it hasn't for this user. can official recovery not do adb side load?
a shame to see the device go like that.
i've had to unplug my stick. i disabled OTA using adb yet it still updated and it causes issues with watching stuff it just leaves the video and i have to load it again. got annoying. i'll just wait

El_Nino9 said:
that sucks big time glad i got an FTV 2 with the whole preloader method which can take 2 hours or so but at least revive.
i was thinking if he has adb, can he not push an official update to it and revive it?
the keyboard trick usually works but i understand it hasn't for this user. can official recovery not do adb side load?
a shame to see the device go like that.
i've had to unplug my stick. i disabled OTA using adb yet it still updated and it causes issues with watching stuff it just leaves the video and i have to load it again. got annoying. i'll just wait
Click to expand...
Click to collapse
su would need to be working to put an official update on it.

rbox said:
su would need to be working to put an official update on it.
Click to expand...
Click to collapse
i guess the only way is hardware mod and write the files directly.

Freakin SuperSU me. I wish I wouldn't have been so stupid to try it.

mrchrister said:
Freakin SuperSU me. I wish I wouldn't have been so stupid to try it.
Click to expand...
Click to collapse
I was lucky I tried it about 10times but it wouldn't work.... after the reports of bricks come I was so happy it didnt work. I feel sad for you unlucky people who bricked with that app! It's a shame
Sent from my SM-G900F using Tapatalk

same happened here .. 'supersu me' didnt work. after a reboot root was lost and supersu didnt work ... so i tried supersu me pro which messed it up.

i wish i never tried super sume either .. my fire tv is bricked also!!

yep. supersu me cost me $100. now i got the new firetv 2 already rooted. i still want to revive the bricked firetv through mmc hardware access.
Sent from my iPhone using Tapatalk

mrchrister said:
yep. supersu me cost me $100. now i got the new firetv 2 already rooted. i still want to revive the bricked firetv through mmc hardware access.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
somebody mentioned in reddit about "EMMC chip".
I am waiting for his progress report.

It is possible to unbrick the firetv through soldering 4 cables on the logic board. Google for 'exploitee emmc firetv' and you will find an online shop selling the adapter to communicate with the firetv's emmc (its internal hard drive) for $17. I just got the adapter but I don't have a fine enough soldering iron tip yet. The contacts on the logic board of the firetv are tiny, so you really need to know what are you doing. Should you succeed with soldering it on you can then reflash the system partition through the dd command to unbrick.
Sent from my X98 Air III(M5C5) using Tapatalk

Fire TV Gen 1 Bricked

Hi All,
First, i'd like to thank you all in advance for your help.
I have Gen 1 FIre TV that was working fine, so i thought i'd update the firmware to latest using rbox prerooted image. I was running bueller-5.2.6.7-rooted_r1 but YouTube wasn't working. So i downloaded the latest and just adb pushed into the box. Then i issued adb reboot command, and somehow the box bricked.
Now No Power Light, No HDMI signals, when i connect with Computer, it shows as Qualcomm hs-usb qdloader 9006 fire and opens the drive with files in it.
I did some research and came across, that i need to manually dd=if all 8 partitions and i need to have linux installed. I managed to download a firmware update-kindle-bueller-51.6.3.2_user_632552020 extracted it all.
Question - Can i use the update-kindle-bueller-51.6.3.2_user_632552020 to dd=if?
Second, can someone please confirm the partition layout or provide commands to view the layout.
Or Perhaps guide me to a direction which i can follow to fix this.
Thank you,

I bricked my FireTV twice and just resurrected it with the expert/relentless help from "Sus_i" using rbox's https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676.
I read thru page 55 to 110 of rbox's thread https://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337 and those with unlocked bootloader and have an "Image" folder with a bunch of files inside the FireTV are most likely to bring their FireTV back but losing the unlocked bootloader in the process (mine included). https://forum.xda-developers.com/fire-tv/help/firetv-1-gen-rooted-running-pre-rooted-t4035609/page6
1st gen FireTV is built tough, don't give up and all the best to you.
Question - Can i use the update-kindle-bueller-51.6.3.2_user_632552020 to dd=if?
I used this one "update-kindle-bueller-51.6.4.8_user_648594820.bin" credit to "Sus_i"
https://d1s31zyz7dcc2d.cloudfront.n...te-kindle-bueller-51.6.4.8_user_648594820.bin

@Matt_7 when I connect to Linux box, I'm terminal
Do I just issue dd=if NON-HLOS.bin of=/dev/sda3
Or do I need to do additional commands to make sure it is connected like adb stuff.
And thank you very much for replying

nycelitemaster said:
@Matt_7 when I connect to Linux box, I'm terminal
Do I just issue dd=if NON-HLOS.bin of=/dev/sda3
Or do I need to do additional commands to make sure it is connected like adb stuff.
And thank you very much for replying
Click to expand...
Click to collapse
For mine, I entered:
Sudo su
dd if=NON-HLOS.bin of=/dev/sdb3
dd if=sbl1.mbn of=/dev/sdb4
dd if=sbl2.mbn of=/dev/sdb5
dd if=sbl3.mbn of=/dev/sdb6
dd if=tz.mbn of=/dev/sdb7
dd if=rpm.mbn of=/dev/sdb8
dd if=emmc_appsboot.mbn of=/dev/sdb9
dd if=boot.img of=/dev/sdb10
sudo eject /dev/sdb
Make sure you read rbox post https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676 regarding the correct partitions (in my case /dev/sdb (sdb1 to sdb20). Details instructions provided by "Sus_i" here https://forum.xda-developers.com/fire-tv/help/firetv-1-gen-rooted-running-pre-rooted-t4035609/page5, just make sure to check and double check which partition is OK to ignore (if mounted).

Thank you very much. I'll try today.

@Matt_7; thank you so much. I used the Ubuntu Live USB.
Sudo SU did not work, so i used sudo bash which did the job
When i did df -h, it showed my fire tv as sdc1
then i ejected those, and did the commands, it did not work.
I replugged them, some drives populated and i ran the commands it worked
At the end, i issued command eject /dev/sdc, it didn't work, but i ejected by right clicking, then i powered the fire tv box and it booted.
Luckily it showed TWRP as recovery.
I ran the command in adb
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
SU prompted on fire tv to accept, which i did then it showed
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
[email protected]:/ # cat /proc/cmdline
androidboot.hardware=qcom user_debug=22 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 androidboot.selinux=enforcing androidboot.emmc=true androidboot.serialno=709xxxxxxxx301G7 androidboot.prod=1 androidboot.baseband=apq
[email protected]:/ #
Does this mean, it is unlocked?
a) if it is not unlocked, is it possible for me to unlock bootloader again?
b) if not, can I go restore to stock w/o root?
if yes, can i follow the guide on aftvnews?
http://www.aftvnews.com/how-to-fully-unlock-the-amazon-fire-tv-bootloader/
Btw, i was able to update to 5.2.7.2 r1 latest using pre-rooted from TWRP.

Hey, great to hear that you got your FireTV back, another success story! (credit to Sus_i & rbox)
This is what Sus_i told me:
For checking bootloader status, simply run
adb shell
su
cat /proc/cmdline
Bootloader is unlocked if you see: androidboot.unlocked_kernel=true
Yes, its good to have unlocked bootloader (I've no clue if that's possible again after doing the dd). Sus_i will most likely give us an answer on this thread or mine.
Best regards.

Matt_7 said:
Hey, great to hear that you got your FireTV back, another success story! (credit to Sus_i & rbox)
This is what Sus_i told me:
For checking bootloader status, simply run
adb shell
su
cat /proc/cmdline
Bootloader is unlocked if you see: androidboot.unlocked_kernel=true
Yes, its good to have unlocked bootloader (I've no clue if that's possible again after doing the dd). Sus_i will most likely give us an answer on this thread or mine.
Best regards.
Click to expand...
Click to collapse
I can't thank you enough for guiding me into the right direction. You saved me lot of aggravation and going out and spending money on new crappy versions.
Thank you sooooo much to you and sus_i and rbox.