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] fb mode: premission denied in KFU 0.9.5

im try to root my Fire v6.3 with KFU v0.9.5. The drivers are installed corrected and my ADB status - online and Boot status - 4000. But when i try and root with option 2(or use any option actually) i see /local/data/fbmode: permission denied
Can anyone tell me what my issue is?
thanks guys.

Change the permissions of fbmode. In command prompt, navigate to the KFU folder that contains adb.exe and enter...
adb shell chmod 775 /data/local/fbmode
...and try again
Sent from my Amazon Kindle Fire using xda premium

i tried that and i'm still getting permission denied. I've been messing about with this for a few days now. I just copied and pasted what you told me to type. I actually tried "adb shell chmod 755 /data/local/fbmode" i saw that on another website. Still no working!
Any other tips?
thanks

[Edit:] I changed my mind
Instead, try rooting manually. Without KFU.
http://forum.xda-developers.com/showthread.php?p=24124828
Sent from my Amazon Kindle Fire using xda premium

soupmagnet said:
[Edit:] I changed my mind
Instead, try rooting manually. Without KFU.
http://forum.xda-developers.com/showthread.php?p=24124828
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
i just finished trying that and got permission denied on this line "adb shell /data/local/fbmode". I'm quickly exhausting all options. I've tried on 2 pc's, one running xp and one running windows 7 and get to the same stage!

Did you "adb root" and "adb remount" to mount system as read/write?
Sent from my Amazon Kindle Fire using xda premium

i managed to get it rooted manaully using /tmp/ in the comand lines as below.
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
Came across it on a thread on here. Thank for you help man

[Q] System software version 6.3_user_4019920 root possible?

Hi all,
I have a kindle fire with system version 6.3_user_4019920.
I used Kindle Fire Utility 0.9.5, installed TWRP, FFF and Permanent Root with Superuser (option 2).
I did NOT installed Google Apps/Go Luncher EX though!
Everything went just fine with no errors at all.
I installed ProxyDroid 2.6.2 and that tells me that I am not root. I checked also to see if the device is rooted installing Root Checker app and that tells me also: "Sorry, you don't have root access"
Any help would be appreciated!
Regards,

osceoladad said:
Hi all,
I have a kindle fire with system version 6.3_user_4019920.
I used Kindle Fire Utility 0.9.5, installed TWRP, FFF and Permanent Root with Superuser (option 2).
I did NOT installed Google Apps/Go Luncher EX though!
Everything went just fine with no errors at all.
I installed ProxyDroid 2.6.2 and that tells me that I am not root. I checked also to see if the device is rooted installing Root Checker app and that tells me also: "Sorry, you don't have root access"
Any help would be appreciated!
Regards,
Click to expand...
Click to collapse
I have this problem too, KFU doesn't seem to copy su binary to /system/xbin, so just do it your self from adb (su binary located in the "files" folder inside KFU), then set permission to it as 06755, finally open install Superuser.apk.
Reboot into recovery mode
adb shell mount system
adb push ..\files\su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install ..\files\Superuser.apk

Thank you.
I did all steps, but at the last command (adb install ..\files\Superuser.apk) I got the following error:
/sbin/sh: pm: not found

osceoladad said:
Thank you.
I did all steps, but at the last command (adb install ..\files\Superuser.apk) I got the following error:
/sbin/sh: pm: not found
Click to expand...
Click to collapse
You must boot out of recovery and back into the system before executing the adb install command.

kinfauns said:
You must boot out of recovery and back into the system before executing the adb install command.
Click to expand...
Click to collapse
Thanks,
I saw that KFU was showing 5000 status mode. So, I did: "fastboot oem idme bootmode 4000" I got an OKAY on the PC screen and now the Kindle Fire is stucked at the logo (I cannot even power it off). I disconnected and reconnected but know even the computer is not recognizing it.
Any other suggestions?

osceoladad said:
Thanks,
I saw that KFU was showing 5000 status mode. So, I did: "fastboot oem idme bootmode 4000" I got an OKAY on the PC screen and now the Kindle Fire is stucked at the logo (I cannot even power it off). I disconnected and reconnected but know even the computer is not recognizing it.
Any other suggestions?
Click to expand...
Click to collapse
That only changes the bootmode. You need to actually tell it to reboot.
Code:
fastboot reboot
Maybe you want to read the first few posts of this link...
http://forum.xda-developers.com/showthread.php?t=1552547
It will help you understand what you are doing rather than just typing commands.

kinfauns said:
That only changes the bootmode. You need to actually tell it to reboot.
Code:
fastboot reboot
Maybe you want to read the first few posts of this link...
http://forum.xda-developers.com/showthread.php?t=1552547
It will help you understand what you are doing rather than just typing commands.
Click to expand...
Click to collapse
That is exactly the article from were I have the command. Unfortunetly because the kindle is now stucked at the logo (cannot turn it off) even if I issue fastboot reboot is waiting for a device that is not recognized.

osceoladad said:
That is exactly the article from were I have the command. Unfortunetly because the kindle is now stucked at the logo (cannot turn it off) even if I issue fastboot reboot is waiting for a device that is not recognized.
Click to expand...
Click to collapse
Hold the power button until it shuts off. Then restart.

First what is the charge level on your battery that can happen from your battery being flat also maybe try powering it off by holding the power button for 20 seconds till it does completely power down some say to reinstall your drivers but I can't imagine why how and where they could have changed considering how far you have gotten

It worked and I was able to finishe the rooting also.
Thanks for all guys who replied, wasted their time and helped me out!
I needed all this because of a Europe trip and I run a Squid proxy here in US that I want to use it for netflix. Hopefully ProxyDruid will help me out.
Best,

I'm having a similar problem. I used KFU 0.9.6 and installed permanent root and twrp. I've even flashed the latest jandycane ROM. It's super stable and have had no problems except that I can't run apps that require root. The root checker says I don't have root. I tried running the above adm commands but with no luck. Any help is appreciated.
Sent from my Amazon Kindle Fire using Tapatalk 2

mcqueena9845 said:
I'm having a similar problem. I used KFU 0.9.6 and installed permanent root and twrp. I've even flashed the latest jandycane ROM. It's super stable and have had no problems except that I can't run apps that require root. The root checker says I don't have root. I tried running the above adm commands but with no luck. Any help is appreciated.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Enter the following command and post the results:
adb shell ls /system/xbin | grep '\bsu\b'; echo $?
Click to expand...
Click to collapse

soupmagnet said:
Enter the following command and post the results:
Click to expand...
Click to collapse
I'm not on mac or linux so the grep command fails. The output of
Code:
adb shell ls /system/xbin/su
is
Code:
/system/xbin/su
---------- Post added at 04:39 PM ---------- Previous post was at 03:57 PM ----------
I ran the utility again. Now /system/xbin/su is a symbolic link to /system/bin/su. The output of
Code:
adb shell ls -al /system/xbin/su
is
Code:
lrwxrwxrwx root root 2012-10-10 16:29 su -> /system/bin/su
and the output of
Code:
adb shell ls -al /system/xbin/su
is
Code:
-rwsr-sr-x root root 173934 2008-08-01 08:00 su

Sorry, it's easy for me to forget about you windows users
Do you have terminal emulator?
See if the "su" command is successful.

soupmagnet said:
Sorry, it's easy for me to forget about you windows users
Do you have terminal emulator?
See if the "su" command is successful.
Click to expand...
Click to collapse
Code:
/system/bin/sh: /system/bin/su: not executable: magic 7F45

Apparently your su binary is corrupt. Use adb shell to remove it and then adb push a new version to your /system/xbin folder. Afterwards (adb shell) chown and chmod to give it the proper ownership/permissions and try again.
I'm assuming you already know how to do this.
---------- Post added at 05:06 PM ---------- Previous post was at 04:59 PM ----------
Upon further inspection, it seems as though you installed the wrong su binary. There are two available; x86 and ARM. You need ARM.

Thanks for the help. I pushed a new su file. Now it says permission denied. What should the permissions be set to? I tried 06755 as above but no luck.
Sent from my PC36100 using Tapatalk 2

Code:
adb shell
chown 0.0 /system/xbin/su
chmod 755 /system/xbin/su
Then try su in terminal emulator

Still getting permission denied.
Sent from my Amazon Kindle Fire using Tapatalk 2

mcqueena9845 said:
Still getting permission denied.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Sorry, I told you wrong.
Code:
adb shell chmod 06775 /system/xbin/su

[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....

How to unbrick kindle fire hdx 7?

Today I was thinking: "It would be great to install cm12.1 on mine KFHDX7"
So i downgraded my tablet, rooted it with tovelroot and than I found, what i need a twrp. So i tried this:
1. Root your Kindle Fire using SuperOneClick and make sure adb is enabled.
2. Download the latest version of FireFireFire, a custom recovery tool for the Kindle Fire.
3. Unzip the utility and copy the u-boot.bin file to the directory where you have adb installed. For instance, c:\androidsdk\
4. Download the twrp-blaze.2.0.0RC0.img, which is the version of TWRP 2.0 for the Kindle Fire.
5. Copy that file to the same directory (such as :\androidsdk\)
6. Open a command prompt by opening the Start Menu and typing “cmd” and pressing enter.
7. Navigate to c:\androidsdk\ or whatever directory you’ve placed your files in by entering “cd c:\androidsdk\” or the appropriate directory.
8a. Make sure your tablet is connected to your computer with a USB cable.
8b. Optional: type “adb devices” to make sure your Kindle Fire is connected and adb is functioning properly. If this works, you should see a listing for your device.
9. Copy the two files to your Kindle SD card by entering the following commands and pressing enter after each:
adb push u-boot.bin /sdcard/
adb push twrp-blaze-2.0.0RC0.img /sdcard/
10. Open an ADB shell and then install the bootloader and recovery by entering the following commands one at a time. Note that if you get a message saying “permission denied,” it means that your tablet hasn’t been rooted properly. Try running SuperOneClick again.
adb shell
su
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
11. Reboot your device with the following commands.
exit
adb reboot
I wasn't mentioned, what this tutorial is for Fire HD and I bricked my device.
What should I do?

Capitan_Veshdoki said:
Today I was thinking: "It would be great to install cm12.1 on mine KFHDX7"
So i downgraded my tablet, rooted it with tovelroot and than I found, what i need a twrp. So i tried this:
1. Root your Kindle Fire using SuperOneClick and make sure adb is enabled.
2. Download the latest version of FireFireFire, a custom recovery tool for the Kindle Fire.
3. Unzip the utility and copy the u-boot.bin file to the directory where you have adb installed. For instance, c:\androidsdk\
4. Download the twrp-blaze.2.0.0RC0.img, which is the version of TWRP 2.0 for the Kindle Fire.
5. Copy that file to the same directory (such as :\androidsdk\)
6. Open a command prompt by opening the Start Menu and typing â??cmdâ? and pressing enter.
7. Navigate to c:\androidsdk\ or whatever directory youâ??ve placed your files in by entering â??cd c:\androidsdk\â? or the appropriate directory.
8a. Make sure your tablet is connected to your computer with a USB cable.
8b. Optional: type â??adb devicesâ? to make sure your Kindle Fire is connected and adb is functioning properly. If this works, you should see a listing for your device.
9. Copy the two files to your Kindle SD card by entering the following commands and pressing enter after each:
adb push u-boot.bin /sdcard/
adb push twrp-blaze-2.0.0RC0.img /sdcard/
10. Open an ADB shell and then install the bootloader and recovery by entering the following commands one at a time. Note that if you get a message saying â??permission denied,â? it means that your tablet hasnâ??t been rooted properly. Try running SuperOneClick again.
adb shell
su
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
11. Reboot your device with the following commands.
exit
adb reboot
I wasn't mentioned, what this tutorial is for Fire HD and I bricked my device.
What should I do?
Click to expand...
Click to collapse
http://forum.xda-developers.com/kindle-fire-hdx
Sent from my KFFOWI using XDA Labs