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!
Related
For 6.3 see http://forum.xda-developers.com/showthread.php?p=24129239
Please do not reupload/redistribute BurritoRoot2/BurritoRoot3, instead link directly to my hosting. I own the server, it will no go away any time soon. This allows me to update it if a bug is found.
BurritoRoot3 is not opensource, it is free, but it is not free to distribute. Please do not redistribute it.
Tested on 6.2, 6.2.1 and 6.2.2
Disclaimer:
BurritoRoot3 may void your warranty. While it was tested, over and over, a chance of data loss or hardware damage always exists. If something bad happens due to your use of BurritoRoot3, well it is your fault not our's, don't blame any of us.
Wine/Coffee/Device Funding:
To donate to jcase of TeamAndIRC for BurritoRoot go here:
http://forum.xda-developers.com/donatetome.php?u=2376614
To donate to pokey900 for the FireFireFire Bootloader go here:
http://forum.xda-developers.com/donatetome.php?u=466725
Download:
http://download.cunninglogic.com/BurritoRoot3.apk
BurritoRoot3 is an all in one package, to root and install the custom bootlaoder, FireFireFire, onto the KindleFire.
Instructions are pretty plain and simple, however you will have to get adb working on your own (if you have written, or know of adb guides for the Kindle Fire please PM me to list them here).
ADB GUIDES
MAC GUIDE: http://forum.xda-developers.com/showthread.php?t=1443071
WINDOWS GUIDE: http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
LINUX GUIDE: http://forum.xda-developers.com/showthread.php?p=22067293
What it does:
Gains root, installs superuser, installs su and installs the FireFireFire bootloader.
At this time, we do not have permission to distribute any recovery, once one is available for our use, we will add auto flashing of recovery.
How to use:
adb shell chmod 777 /data/local/tmp
Run app, follow directions given by the app.
Usage example :
[email protected]:~$ adb shell chmod 777 /data/local/tmp <---- This one is important, it may not create BurritoRoot3.bin if this is not done
[email protected]:~$ adb install BurritoRoot3.apk
4897 KB/s (1151520 bytes in 0.229s)
pkg: /data/local/tmp/BurritoRoot3.apk
Success
<go open the app now>
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --root
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
Gaining root...
Installing Superuser APP, if it erros as already exists, please ignore the error.
pkg: /data/data/net.andirc.burritoroot3/bin/Superuser.apk
Success
Restarting adbD as root...
Please run adb shell /data/local/tmp/BurritoRoot3.bin --install
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --install
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
BurritoRoot3 kroot 0.1 - TeamAndIRC
Remounting /system...
Cleaning up, ignore any errors
rm failed for /system/xbin/su, No such file or directory
rm failed for /system/bin/su, No such file or directory
Installing su...
Remounting /system..
Root installed
Starting: Intent { act=android.intent.action.MAIN cmp=net.andirc.burritoroot3/.FireFireFire }
Please check your Kindle's screen
[email protected]:~$
If you already have root, and want to safely install the FireFireFire bootloader, you can use the app, just install, open/close the app then
adb shell am start -a android.intent.action.MAIN -n net.andirc.burritoroot3/net.andirc.burritoroot3.FireFireFire
To install the CWR recovery by DoomLord after gaining root:
Download it, and push it to your Kindle
adb push <filename> /data/local/recovery.img
adb shell dd if=/data/local/recovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
Would you support the archos G9 devices
jutley said:
Would you support the archos G9 devices
Click to expand...
Click to collapse
Doesn't archos sign or lock system?
I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
---------- Post added at 10:06 AM ---------- Previous post was at 09:55 AM ----------
CharlieBoy808 said:
I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
Click to expand...
Click to collapse
LoL Nevermind I think I know why mine isn't there... I've already installed ADB from before. I shall continue on and see what happens :-D
I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.
AproSamurai said:
I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.
Click to expand...
Click to collapse
adb kill-server
sudo -s
adb devices
should see it now
Quit following me around jcase
Unheard said:
Quit following me around jcase
Click to expand...
Click to collapse
Hah Where you been?
I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.
notsointeresting said:
I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.
Click to expand...
Click to collapse
I'm sure its related to windows' drivers but I have no clue. Sorry
jcase said:
adb kill-server
sudo -s
adb devices
should see it now
Click to expand...
Click to collapse
Thanks man, I knew I must have failed to do something. It's much appreciated.
Dis this last night and it worked fine. Thanks!
I did have a few minor stumbles though. It seems the newest version of the software changed the name of the superuser app but the guide still uses the old name in the install command. Once I realized this I just changed the name in the command and it went right in.
Also for some reason I couldn't select the text in the adb box on the web page so I had to enter the commands by hand. No big deal but I would have felt more secure if the commands were in simple text so I could have copy/paste them in.
Like I said though everything worked and I have the market installed now. Thanks for the hard work!
I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated
My sd card is showing up as unmounted and not sure how to remount it. I sent adb remount and it didn't work. Any help would be appreciated.
Fee454 said:
I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated
Click to expand...
Click to collapse
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889
[/COLOR]
b63 said:
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889
Click to expand...
Click to collapse
This tool will attempt to install the correct Drivers for the Kindle Fire.
It will also perform the setup required for adb_usb.ini in .android for you.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Press any key to continue . . .
I tried to install the drivers for the kindle but i receive the above message
---------- Post added at 09:56 PM ---------- Previous post was at 09:07 PM ----------
My issue is it cannot find my device...where can I find the kindleADB.zip I keep hearing about?
did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue
You should get the same files from the android Sdi. Good luck.
Jcase, I know that you said the unroot button did not work, but is there a method of unrooting?
b63 said:
did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue
Click to expand...
Click to collapse
Yes thank you. Moving it to the same as the run.bat seemed to have worked as it shows online now when running the Kindle Fire Utility. I switched it to fast boot but now seems to have been frozen at the kindle fire logo for quite some time now. I heard you have to switch to fastbook to install TWRP first before rooting?
I am not sure if I should attempt to somehow reboot this as it seems to be stuck at the boot up screen
wrong - switch back to normal boot and use the utility
Hi,
I recently got a new Kindle fire and tried to root it.
I followed the instructions given in this post.
http://forum.xda-developers.com/showthread.php?t=1568340
However, my kindle fire seems to be stuck in an infinite boot loop after first step itself.
Here are the step I followed (I am using Windows 7 32bit).
1. Installed android sdk.
2. Updated the Kindle driver to install "android abd composite interface"
3. Downloaded all the required files in the platform-tools folder
Required files:
fbmode.zip - http://forum.xda-developers.com/show....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/show....php?t=1369405
fastboot + adb for your OS of choice.
4. Followed following commands:
unzip fbmode.zip
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
5. After this, my kindle fire seems to have stuck in an infinite boot loop.
- It starts up only when a USB cable is connected.
- Power light is orange and not green
- It starts up Kindle Fire logo comes up, then shuts down again
- My computer is not detecting any device, probably because KF is in an infinite boot loop
- When I run adb devices -- no devices show up
- When I run fastboot command [fastboot -i 0x1949 flash bootloader .....] it says "waiting for devices"
- When I remove the USB cable from KF, It doesn't powers on (even after long pressing the power button).
- I tried many things posted on different forums on two laptops (Windows 7 32 bit as well as 64 bit) and using different USB cables but nothing worked.
- Only thing I haven't tried is Factory cable as I don't have it and don't have money to buy it.
PLEASE HELP!!
http://forum.xda-developers.com/showthread.php?t=1623244
Superuser not working
Thanks for the help with the charging issue Kinfauns!!!
I charged my kindle fire using stock charger and finally rooted it.
However, I am still not able to install android market on my KF.
After rooting Kindle (followed all the steps given in the thread), I installed Superuser.apk.
Then to install android market, I installed root explorer and downloaded Kindle Fire android market zip file. (followed instructions from one of the NAT3MIL's video on youtube).
First step is to install googleServicesFramework.apk file, which I did.
The next step is to move market.apk file to system/apps folder. However, when I tried doing that, I got a warning:
"Your phone doesn't appear to be rooted. This is requires in order to change or delete protected files such as this ......"
I don't understand why is it saying so as I have followed all the steps in the thread to root my KF?
How to check if the KF is really rooted?
Are there any settings to be changed in the superUser.apk?
Please help!!
Thanks a ton!!
Superuser not working
One more thing.
when I tried to update SU binary file,
I got following:
Downloading manifest .. OKAY!
parsing manifest.. Okay!
Latest Version = 3.0.3.2
Checking installed version .. legacy
Fixing database .. okay!
checking for busybox .. not found
Downloading custom busybox .. okay!
checking md5sum ... okay!
checking current install path .. fail!
Failed to find current installed su binary. Update cannot continue.
Does this mean I have to re-root the KF or just install the su binary file? how to do that?
Thanks!
Download the latest kindle fire utility and rerun it for permanent root.
Known Tricks
If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Please note: If your device can't be seen in fastboot mode, please make sure to install the drivers packaged with this, as it will show up afterwards. You can use the install_drivers.bat with the device plugged in for this.
Copied from the instructions of the kindle fire utility
Above are the tricks if you get stuck but after root install twrp then install fff
I would assume that your not rooted sounds that way to me.
By the way the yellow triangle will be replaced with the new bootloader a white kindle and a blue fire this will be considered the yellow triangle in the description. Good luck
Install permanent root
Install twrp
Install fff
All should be the newest at this point hopefully
Thanks ThePooch.
So, apparently I have to re-root my KF as for some reason it was not rooted correctly. Right?
I believe so the worst that could happen is it could fail if the file already exists but let's hope it goes fine
tanwar said:
Thanks ThePooch.
So, apparently I have to re-root my KF as for some reason it was not rooted correctly. Right?
Click to expand...
Click to collapse
You don't necessarily have to let KFU do its entire "rooting" process.
If you can get into recovery and you are comfortable with adb, you can follow the "Rooting the stock software" section in this guide...
http://forum.xda-developers.com/showthread.php?t=1638452
to push the 'su' binary into the /system partition and set ownership/permissions.
If you are not comfortable with that, you can use KFU, but it will be doing a lot of extraneous things that you probably don't need.
Under extras you will put on Google frame work and go launcher after you have confirmed bootloader recovery and root note that the market can only be seen using go launcher not the kindle one.
---------- Post added at 12:32 AM ---------- Previous post was at 12:13 AM ----------
The easiest way to test root is to download an app that will request root permissions like root explorer for instance if you open the app and you don't see a dialogue pop up requesting permission its very likely that it isn't rooted.
Read-Only file system
Thanks Kinfauns and ThePooch for tips.
@kinfauns, I tried following the steps given in "Rooting the stock software" section of the given link.
http://forum.xda-developers.com/showthread.php?t=1638452
However, when I tried to push su binary file to system folder
adb push C:\kfu\software\su /system/xbin/
I got following message:
failed to copy 'su' to 'system/xbin/su': Read-only file system.
How can I change the permissions of the folder to copy su file?
I tried using shell command:
adb shell chmod 755 /system
However, I got the same message again "Read-only file system"
Please help!!
nevermind I see your on windows 7 like me. adb shell mount system will mount system to read/ write
its all in kinfauns post you just need to be it recovery to execute the commands I believe I would paste it here but its just as easy to read them from there
adb shell chmod 6755 /system/xbin/su not 755 you can probably safely copy and paste the commands from his post right into cmd he has it written up very nicely
tanwar said:
Thanks Kinfauns and ThePooch for tips.
@kinfauns, I tried following the steps given in "Rooting the stock software" section of the given link.
http://forum.xda-developers.com/showthread.php?t=1638452
However, when I tried to push su binary file to system folder
adb push C:\kfu\software\su /system/xbin/
I got following message:
failed to copy 'su' to 'system/xbin/su': Read-only file system.
How can I change the permissions of the folder to copy su file?
I tried using shell command:
adb shell chmod 755 /system
However, I got the same message again "Read-only file system"
Please help!!
Click to expand...
Click to collapse
I think you may be trying to do this while booted into the system software. That won't work because you don't have root access there and you won't be able to mount (or remount) a partition without those privileges. The rest of it won't work without R/W access to the partition, as you've already seen.
To be clear, the device needs to be booted into recovery (TWRP or CWMR) where you do have root privileges. Make sure you start with step one to get the system partition mounted. If successful, "mount" will provide no output.
I have tried every version of KFU from 0.9.5 on up, and have reinstalled the KFU drivers multiple times. FFF & TWRP install fine, but when KFU gets to the part where it removes the root checker I get an error:
Attempt to remove root checker
mv: can't rename 'system/bin/check_rooted': No such file or directory
Please wait...
The Kindle then continues to boot up as normal. It then attempts to install SU:
Installing Superuser.apk
Error: Cound not access the Package Manager. Is the system running?
KFU then states that root has been installed, when in fact it has not. I know that I could simply use TWRP to flash CM 10.1 which would have root, but this Kindle is my wife's (I already have CM on mine). I need root to be able to use Titanium Backup and save all of her app data. Any help resolving this would be appreciated!
diskoman21 said:
I have tried every version of KFU from 0.9.5 on up, and have reinstalled the KFU drivers multiple times. FFF & TWRP install fine, but when KFU gets to the part where it removes the root checker I get an error:
Attempt to remove root checker
mv: can't rename 'system/bin/check_rooted': No such file or directory
Click to expand...
Click to collapse
This is normal. Nothing to really worry about.
Installing Superuser.apk
Error: Cound not access the Package Manager. Is the system running?
KFU then states that root has been installed, when in fact it has not. I know that I could simply use TWRP to flash CM 10.1 which would have root, but this Kindle is my wife's (I already have CM on mine). I need root to be able to use Titanium Backup and save all of her app data. Any help resolving this would be appreciated!
Click to expand...
Click to collapse
I've run into this problem before. This is from attempting to install the .apk before the device is booted far enough for the package manager to be available. This can be easily fixed by pausing the script for an amount of time to ensure the package manager is available before continuing with the rest of the script. You should probably contact the developer about it.
You might be able to just install Superuser.apk using the following command:
Code:
adb shell pm install -r /system/app/Superuser.apk
THANK YOU!!!
soupmagnet said:
This is normal. Nothing to really worry about.
I've run into this problem before. This is from attempting to install the .apk before the device is booted far enough for the package manager to be available. This can be easily fixed by pausing the script for an amount of time to ensure the package manager is available before continuing with the rest of the script. You should probably contact the developer about it.
You might be able to just install Superuser.apk using the following command:
Code:
adb shell pm install -r /system/app/Superuser.apk
Click to expand...
Click to collapse
Your response made all the sense in the world (duh moment for me, lol)! I took a look at the batch file for KFU, and located the line of code where it calls the sleep function to wait for the Kindle to boot up:
::Wait for Android to finish booting, and install Superuser.apk.
tools\adb wait-for-device
tools\sleep 20
echo. Installing Superuser.apk
tools\adb install -r files\Superuser.apk 2> nul
I changed the 2nd line of the section to call sleep for 60 seconds instead of just 20. Voila! That did the trick. I have sent a message to the developer as well, so that he can make this simple fix. Thanks again for taking the time to help get me on the right path! :highfive:
diskoman21 said:
Your response made all the sense in the world (duh moment for me, lol)! I took a look at the batch file for KFU, and located the line of code where it calls the sleep function to wait for the Kindle to boot up:
::Wait for Android to finish booting, and install Superuser.apk.
tools\adb wait-for-device
tools\sleep 20
echo. Installing Superuser.apk
tools\adb install -r files\Superuser.apk 2> nul
I changed the 2nd line of the section to call sleep for 60 seconds instead of just 20. Voila! That did the trick. I have sent a message to the developer as well, so that he can make this simple fix. Thanks again for taking the time to help get me on the right path! :highfive:
Click to expand...
Click to collapse
Yeah, 60 seconds may be a bit much LOL, but I'm glad it worked out for you :good:
Hello All,
Purchased an Amazon Fire TV from Amazon, it shipped in one day and I have been toying with it for the last few hours. Rooting was easy, as was installing SU, Busybox, Stickmount etc.. However, I am not to the point to where I want to install a custom recovery so I can update to the latest firmware without loosing root. The instructions say I need to downgrade to an earlier firmware in order to do this. My problem is that every time I reboot into recovery it says "Update was not successful" and It boots back to the same version that I started with.
The version I have now is 5.1.1.1.0 fully rooted w/ Busybox. I don't know exactly what I am doing wrong. I have both pushed the update.zip to the AFTV, and I have also put it on a thumb drive. I have tried earlier versions then the one recommended in the guide that I was following. All of this to no avail.
Please help.
Thank you.
Anybody? I was up till little after 3 AM trying to figure this out. Factory reset, re-rooted, nothing seems to work. Has anyone else had this issue?
I had the exact same problem. Try a different firmware download option. I used the "mirror' on AFTVnews.com the first time and had the same fail at the end that you did. I also re installed busybox before I performed the downgrade, so I'm not sure which of the two fixed the problem, but I suspect it was a bad download from the mirror.
roaoro said:
I had the exact same problem. Try a different firmware download option. I used the "mirror' on AFTVnews.com the first time and had the same fail at the end that you did. I also re installed busybox before I performed the downgrade, so I'm not sure which of the two fixed the problem, but I suspect it was a bad download from the mirror.
Click to expand...
Click to collapse
Just tried the mirror. That ended in the same result. I am going to try re-installing Busybox again to see if that has any change.
roaoro said:
I had the exact same problem. Try a different firmware download option. I used the "mirror' on AFTVnews.com the first time and had the same fail at the end that you did. I also re installed busybox before I performed the downgrade, so I'm not sure which of the two fixed the problem, but I suspect it was a bad download from the mirror.
Click to expand...
Click to collapse
Tried re installing busybox that didn't crack it either.
The exact error is "The System Update was not successful." Your AFTV will restart in a few minutes and should resume normal operation.
Any other ideas I can try?
brotherandyslb said:
Tried re installing busybox that didn't crack it either.
The exact error is "The System Update was not successful." Your AFTV will restart in a few minutes and should resume normal operation.
Any other ideas I can try?
Click to expand...
Click to collapse
You need to list exactly what you are doing so we can tell you what you are doing wrong.
I had to do it a couple of times because it didn't work right at first either.
nyder said:
You need to list exactly what you are doing so we can tell you what you are doing wrong.
I had to do it a couple of times because it didn't work right at first either.
Click to expand...
Click to collapse
Ok,
Lets start from the top:
Factory Reset
Watch Video
Sign into Amazon Prime
So no to parental controls
Go to developer options and turn it to on so I can use ADB
Connect with ADB
adb install towelroot
go into towelroot and root
adb install supersu
go into supersu and let it update
adb install busybox
go into busybox and install it and let it symlink
adb the command to turn off updates
Then I follow the guide over at aftvnews.com to downgrade
Download the firmware version you wish to install from the software page
Rename the downloaded file to update.zip
Connect to your Fire TV using ADB
(If you don’t know how, follow up to Step 4 Part 2 in our Windows or Mac guide)
Run the command: adb shell
Run the command: su
(If this is the first time you’ve ever run su, a pop-up will appear on the Fire TV, select Grant)
Run the command: chmod 777 /cache
Run the command: chmod 777 /cache/recovery
Note: If
you see a message saying “No such file or directory”, then run the following two commands:
mkdir /cache/recovery
chmod 777 /cache/recovery
Run the command: cd /cache/recovery
Run the command: echo --update_package=/cache/update.zip > command
Run the command: exit
Run the command (yes, again): exit
Run the command: adb push update.zip /cache
(This assumes the update.zip file you renamed in step 2 is in the same directory as adb, otherwise enter the full path to the file like adb push C:\full\path\to\update.zip /cache)
Once the update.zip file has finished transferring to the Fire TV, run the command: adb reboot recovery
At this point your fire TV should restart and begin installing whichever firmware version you selected.
Click to expand...
Click to collapse
At this point the AFTV restarts and proceeds to install the new firmware about 1/4 way thru it gives the error message and then restarts.
DISCLAIMER: THIS METHOD WORKS ON THE FIRE TV, AND MAY NOT WORK FOR THE FIRE PHONE. IT HAS WORKED FOR ME, BUT I TAKE NO RESPONSIBILITY FOR ANY DAMAGE CAUSED TO ANY DEVICES. USE AT YOUR OWN RISK.
I searched around and couldn't find a way to do this on my own. Some threads suggest deleting system files to get this to work, but I found you can disable OTA updates on the Fire Phone the same way you can with the Fire TV.
You need to have root access to the phone, which requires both:
A) Downgrading your phone to 3.5.0, and installing the ADB. Which you can read about in the first part of B1ackByte's guide HERE.
B) Using towelroot to get root access HERE (Click the symbol, download the apk and run it.)
After you have the ADB and drivers installed on your system, and your phone has been downgraded to 3.5.0, you MUST choose
"Wipe Data and Factory Reset" in the recovery menu before rebooting your phone. If you do not, you can get a couple glitches and hangs... nothing major, but you'll still have to boot into recovery to do the wipe and finish the process.
After you're downgraded, rebooted, and rooted... Install the latest version of SuperSu from HERE then REBOOT AGAIN!!! If you don't, SuperSu might not take over properly.
Open CMD or Command prompt as an administrator, and navigate to where you have the adb.exe, then issue these commands:
adb start-server
adb shell
su
Click to expand...
Click to collapse
Your phone will then ask you to grand permissions to the adb console, click "grant" or "accept" (Depending on the version of SuperSU you have.)
Then Type:
pm disable com.amazon.dcp
Click to expand...
Click to collapse
You should see an output message that says "Package com.amazon.dcp new state: disabled"
And Voila! OTA updates are turned off.
EDIT: I've also read a couple guides about how people have used the Fire HD FirstAide package to install google apps and maintain root, but that process didn't work for me. The Fire Phone (or mine, at least) doesn't come with busybox, and the FirstAide script relies on busybox. You can manually install busybox into the system files of the Fire Phone and give it system permissions, but that is outside the scope of this tutorial.
Also, even after manually installing busybox and granting root permissions to the adb shell running the commands, the script still fails to copy some files because the filesystem isn't EXACTLY the same as the Fire HD. (I may be wrong on this, but I just couldn't get the process to work due to some missing folders on my end.)
I tried this and it worked for me. Thanks!
is that possbile to downgrade 4.6.6 to 3.5 reply quick please guys