Related
Not sure if this will help anyone, but I had a problem when rooting my new kindle fire 6.2.1
If you tried the Burrito Root method, I saw some few mistakes that I've done or didn't see in the video.
1. Updating the Kindle Drivers
I had previously rooted my android phone before, so when I plugged the kindle fire on my windows 7 laptop, I noticed that the windows was already indetifying it as an android phone, and had already labeled it for ADB. This auto-driver update thing might work for some people, but I find much better success replacing that driver that your computer identifies Kindle as, with the one that the BurritoRoot driver provides.
2. Getting the Kindle Root in the Listed Devices of ADB in command prompt.
This was probably the biggest issue I had when rooting the Kindle Fire. I was scratching my head, thinking why my Kindle Fire wasn't listed in the command prompt after typing "adb devices." I knew I did everything right from the beginning. Or so I thought?
One way I found that fixed that was downloading the Kindle Fire Utility v0.9.1
Unlucky for me, the download link was gone....
LUCKY for me, a fellow member here uploaded a mirror.
I somehow got it to work, with just luck but figured out the exact steps that seem to work for me (on Win 7 64 bit here).
1) Open up command prompt again, do the cd c:\KindleADB etc... upto the point where you typed in adb devices. you should be seeing no listed devices on the cmd (if you have that problem). LEAVE IT OPEN.
2) DOwnload the kindle fire utility, open the run.bat , it should have a message saying daemon started sucessfully, THEN QUICKLY FOLLOW THE NEXT STEP.
3) When the daemon started successfully message popped up on the KFU, go back to your CMD where you typed in adb devices and quickly type in "adb devices" again. it should say something like, killing out of date, starting daemon, and something about successful (Sorry if I'm not that much of a help, I tend to forget what the exact message said).
4) It should list the device. if not type it again.
5) Walla ! it should show a bunch of numbers, under listed devices.
3. Rooting the Kindle Fire in command prompt ERRORS
This wasn't much of a problem as it really was my mistake. I kept getting error messages when i typed in ADB ROOT in the command prompt during the BurritoRoot rooting method.
1) You have to make sure you have the BurritoRoot app installed in your kindle fire before starting the CMD adb root part. The app will tell you when to start typing away in CMD!
2) If you're doing the burritoroot method, you have to make sure you got all the names and directory right.
3) When you're doing the CMD adb root part, copy and paste it usually the best way to do it in CMD to avoid mistakes and erorrs! And no, you don't press CTRL+V in CMD. Rather, you right-click the CMD , then click paste (after copying the line you want to input).
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install com.noshufou.android.su-1.apk
adb reboot
Notice all those commands above that you're suppose to type in (or copy and paste). The ones I bolded, people tend to make mistakes there. When you put those files you downloaded into KindleADB, PLEASE MAKE SURE IT IS NAMED com.noshufou.android.su-1.apk, otherwise when you get to the part
Code:
adb install [B]com.noshufou.android.su-1.apk[/B]
change it to :
adb install WHATEVER IT IS CALLED.apk that is Superuser.
The most important part is to push the SU file (that has no file extension).
I had my kindle rooted, with Superuser installed, but I couldn't get any pop-ups from Superuser asking permission for any apps! That is, until I found out I forgot to push the su file to /system/xbin/su and other steps to chmod it.
Anyways, I hope this helps anyone that goes through any problem like I did above. If not, sorry to waste your time! If you guys have any other problems, please leave a question below and perhaps I could or a fellow member here could help you.
Thanks again!
http://forum.xda-developers.com/showthread.php?t=1417234
Ok, so I did something stupid, I tried to install a slider lock theme on my kindle and probably screwed up the Framework-Res. I did not have TWRP or a backup of any kind.
Now the kindle just sits at the boot splash screen.
The device was running on 6.2.2 and most tutorials seem to be made for 6.2.1
I have tried a few manual commands but remount is just say "Operation Not Permitted" (I cant figure out how to fix this either.
Running automated programs like Unbrick Utility just don't work, it says it has completed but you can see a bunch of errors saying it could not copy or not permitted etc...
At this point I just want my kindle fire back even if that means a complete restore, can someone please try to help or point me in the right direction I am about to go insane.
Added Info: To be more exact, I tried to use metamorph to install a slider lock theme, nothing seemed to happen so I closed the app. I thought everything was fine so I put the kindle to sleep, but I could not wake it up. I tried restarting it and that's how I got to were I am now.
Update:
Thanks to b63 I was able to get this fixed, I cant thank him enough.
Ok here is how I got it fixed
First I followed the directions given to me below by b63
he told me to refer to this http://forum.xda-developers.com/show...8&postcount=29 which I did, however When I got to 8 I did something different, I did not need to re install the whole Rom because I had only messed up the Framework-res.apk
So instead I pulled the Framework-res.apk from /system/framework in the official kindle 6.2.2 update.zip
I then used these commands to replace the broken apk on the device and restart in normal boot mode.
4. "adb remount"
5. "adb push framework-res.apk /system/framework/framework-res.apk"
6. "adb shell chown root /system/framework/framework-res.apk"
7. "adb shell chmod 644 /system/framework/framework-res.apk"
8. "adb shell idme bootmode 4000"
9. "adb reboot"
I know that this explanation is not super descriptive but most of what you need can be found below in the thread.
This problem is rather specific to my situation so if you are having the same problem and you can't figure it out send me a PM or reply to this thread.
Anyone? I'm starting to think i should just try to return it.
would need some more concrete information:
is it rooted only ?
what is the boot splash screen "kindle fire" (static or animated) or yellow triangle ?
do you have kfu available ?
moved and renamed so that it is at c:\kfu ?
patched the run.bat of kfu ?
what are the 3 status lines of kfu when you just start it ? - please don't do any option at the moment
os/bit of computer ?
driver status in device manager ?
b63 said:
would need some more concrete information:
is it rooted only ?
what is the boot splash screen "kindle fire" (static or animated) or yellow triangle ?
do you have kfu available ?
moved and renamed so that it is at c:\kfu ?
patched the run.bat of kfu ?
what are the 3 status lines of kfu when you just start it ? - please don't do any option at the moment
os/bit of computer ?
driver status in device manager ?
Click to expand...
Click to collapse
Thank you for the response, I'm not at my normal Computer now, but I will answer what I can from here.
Yes I believe it is rooted only, no roms or anything installed.
The Splash screen is Kindle Fire, It is static (no shine animation). I also never installed TWRP or firefirefire so I don't think it should be yellow. (I tried though)
I do have KFU available, but I'm getting operation not permitted errors
No I did not move/rename it (maybe that's the not permitted issue?)
Three Lines: ADB Status: Online ADB Rooted: No (it was rooted) Boot Status: 4000
Vista 32 Bit
Cant check at the moment (however I believe the drivers are working properly)
Thank you for the response Ill try to help the best I can, Im pretty techy but Ill admit I'm a noob at ADB
Damieok said:
Thank you for the response, I'm not at my normal Computer now, but I will answer what I can from here.
Yes I believe it is rooted only, no roms or anything installed.
The Splash screen is Kindle Fire, It is static (no shine animation). I also never installed TWRP or firefirefire so I don't think it should be yellow. (I tried though)
I do have KFU available, but I'm getting operation not permitted errors
No I did not move/rename it (maybe that's the not permitted issue?)
Three Lines: ADB Status: Online ADB Rooted: No (it was rooted) Boot Status: 4000
Vista 32 Bit
Cant check at the moment (however I believe the drivers are working properly)
Thank you for the response Ill try to help the best I can, Im pretty techy but Ill admit I'm a noob at ADB
Click to expand...
Click to collapse
ok i see a lot out of this - thanks
would recommend to do the move/rename of kfu to sort out any additional problems
you should have adb commands available and the kf is in normal boot mode
now the ultimate test is to issue:
"adb shell"
- if it goes into the shell ($ or # prompt) you can resume
- if it responds something like <exec "system/bin/sh": No such file or directory> then there is no possibility to get to fastboot mode to install fff and twrp which is necessary to install a fresh rom - if this is the case your only solution is to build or buy a "factory cable" - look at this thread :
http://forum.xda-developers.com/showthread.php?t=1392693
b63 said:
I would recommend to do the move/rename of kfu to sort out any additional problems
you should have adb commands available and the kf is in normal boot mode
now the ultimate test is to issue:
"adb shell"
- if it goes into the shell ($ or # prompt) you can resume
- if it responds something like <exec "system/bin/sh": No such file or directory> then there is no possibility to get to fastboot mode to install fff and twrp which is necessary to install a fresh rom - if this is the case your only solution is to build or buy a "factory cable" - look at this thread :
http://forum.xda-developers.com/showthread.php?t=1392693
Click to expand...
Click to collapse
Ok so I renamed the "Kindle Fire Utility" folder to "kfu" moved it to C:\
(if this is incorrect please let me know.)
And good news, adb shell responds with $, were should I go next. (also I have access to my normal computer now)
Thanks again for helping me out with this.
great !!! - simply try to follow this post starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
place the downloaded files in the tools folder of kfu since you are doing the commands from there
b63 said:
great !!! - simply try to follow this post starting at point 2:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
place the downloaded files in the tools folder of kfu since you are doing the commands from there
Click to expand...
Click to collapse
Im a little confused at this guide are the commands being entered into adb or in kfu? Were does kfu come into play?
Sorry the guide is a little hard to understand
it' not so complicated as it sounds ...
open a elevated command prompt and cd to c:\kfu\tools
here are all commands you need and where kfu comes in play
- you don't need kfu itself - only the tools folder
- leave the command window open all the time
This how-to originally started out as a part of the Kindle Fire For Beginners (KFFB) guide, but evolved into this supplemental guide. Because of its origin, this guide assumes the reader is already familiar with KFFB, so reading it is a mandatory prerequisite. Users who post questions in this thread already covered in KFFB will be directed to go back and read it again.
My motives for writing this guide are very much in line with the reasons why I wrote KFFB. I'm hoping users will take the time to learn what they are doing and why they are doing it instead of crossing their fingers and hitting a button on an automated program. While I understand this is the more tedious route to their destination, the knowledge gained here can be used to get back on track when things go wrong or methods inevitably change over time.
The first post in this series details the process of rooting and installing a ROM on a stock device. The two share many of the same preliminary steps, so it makes sense to go over both at the same time.
Preparations
Again, please read Kindle Fire For Beginners before continuing. The conventions introduced in KFFB (e.g. having KFU installed in "C:\kfu") will continue to be used here. Make sure the battery is fully charged. A drained battery is not something you'll ever want to encounter and especially not while in the middle of this process. Create a new folder "C:\kfu\software" on your hard drive. Downloaded software to be installed on the Kindle Fire will be moved there.
Download and install WinMD5Free to some place on your Computer. The developers for most of the software you'll download for the Kindle Fire will provide an MD5 checksum. The checksum is used to verify the integrity of downloaded file, so you can be sure that you haven't gotten a bad download or a corrupted file. Tell WinMD5Free what file you want to check and compare the calculated checksum with the one provided by the developer. If the two match, you can be confident about installing it on your Kindle Fire.
For all required software listed in this document...
Extract (unzip) the files from the compressed archive (unless otherwise noted)
Verify the MD5 checksums if they have been provided
Move them to the C:\kfu\software folder
As with any other how-to guide, it's always a good idea to just read through the document first to get a basic idea of the process involved. Once you are comfortable with the concepts, then go back through and actually perform the steps required.
Getting to fastboot mode
The first step to modifying the Kindle Fire is to get the device into fastboot mode. The easiest and safest way to do this on a stock device is to use a factory cable. The factory cable is safe because it does not require the bootmode to be changed on the device. If something unexpected happens, you'll be able to disconnect the factory cable and reboot straight back into the stock software.
If you choose not to use a factory cable and change the bootmode to get into fastboot mode, you'll be taking a small gamble that you'll be able to issue fastboot commands to the device and change the bootmode back to normal. If you cannot change the bootmode back for some reason (e.g. your device drivers for fastboot mode fail to recognize the device), the device will be stuck in fastboot mode until you find a way to do so. In nearly every case, if you are able to issue the adb commands to get into fastboot mode, you should be able to send the fastboot commands necessary to get out of it. This is just a fair warning out of an abundance of caution... make sure you've done everything to ensure the ADB device drivers have been installed properly.
If you have a factory cable, you can turn the Kindle Fire off and connect the cable to the device, then the computer. The Kindle Fire will power up and put you directly into fastboot mode. You can then skip the rest of this section and go directly to flashing a recovery and bootloader. Otherwise...
Required software:
pokey9000's fbmode
1) Boot up the Kindle Fire normally and connect a USB cable to the device and computer.
2) Copy pokey9000's fbmode program into a user writeable location on the Kindle Fire...
Code:
adb push C:\kfu\software\fbmode /data/local/tmp/
3) Change the permissions on the fbmode program so it can be executed (run) on the device...
Code:
adb shell chmod 755 /data/local/tmp/fbmode
4) Execute (run) the fbmode program to change the bootmode to fastboot...
Code:
adb shell /data/local/tmp/fbmode
5) Reboot the device...
Code:
adb reboot
Note: In case you are wondering why the "adb shell idme bootmode 4002" command previously discussed in KFFB was not used here, that command requires root privileges not available in the stock configuration. Without root privileges, the above workaround is required.
Installing a recovery and custom bootloader
Required software:
FIREFIREFIRE bootloader
TeamWin Recovery Project (TWRP) recovery
Note: Do not extract the contents of the FIREFIREFIRE bootloader zip file. It will be flashed as-is with TWRP recovery.
1) Install the TWRP recovery...
Code:
fastboot -i 0x1949 flash recovery C:\kfu\software\openrecovery-twrp-2.2.2.1-blaze.img
2) Set the bootmode to recovery (5001)...
Code:
fastboot -i 0x1949 oem idme bootmode 5001
3) Reboot the device into TWRP recovery. If you used a factory cable to get into fastboot mode, turn off the device by holding down the power button for about 20 seconds. Replace the factory cable with a generic USB cable and the device will start up again automatically. Otherwise...
Code:
fastboot -i 0x1949 reboot
4) Copy the FIREFIREFIRE bootloader zip file to the /sdcard directory on the Kindle Fire...
Code:
adb push C:\kfu\software\fff-u-boot_v1.4a.zip /sdcard/
5) From the main menu of TWRP, press the "Install" button to flash the FFF bootloader onto the bootloader partition. Navigate to the /sdcard directory on the left (should be the default the first time you use TWRP) and select the file from the list on the right. Then simply "Swipe to Confirm Flash" to install.
6) Optional: Make a nandroid backup of the stock software. From the main menu of TWRP, press the "Backup" button and then "Swipe to Back Up" to create a snapshot of the stock system. If you change your mind later about rooting or have second thoughts about the ROM, just "Restore" the backup and return to the stock configuration.
Rooting the stock software
Users interested in flashing a custom ROM may elect to skip this section. Rooting the stock software is not a requirement to flash a custom ROM because the custom ROM will completely overwrite the stock software. However, if you are undecided on the question of rooted stock vs. custom ROM, root the stock software first and try that out for a while. The option to flash a custom ROM will still be available at a later time.
The following method of rooting the Kindle Fire stock software has been tested on 6.3.x and 6.2.x systems. Skip step #5 when rooting 6.2.x systems because the root checker does not exist in those versions.
Required software:
Superuser by ChainsDD
Note: Two separate files will be needed from the contents of this zip file: the su binary from the system\bin folder and the Superuser.apk file from system\app folder.
This section assumes the device is already booted into TWRP recovery.
1) Remount the /system partition in read/write mode...
Code:
adb shell mount system
2) Copy the su binary onto the device...
Code:
adb push C:\kfu\software\su /system/xbin/
3) Change the owner of the su binary to root...
Code:
adb shell chown root:root /system/xbin/su
4) Set permissions for the su binary to run as root...
Code:
adb shell chmod 6755 /system/xbin/su
5) Disable the root checker by renaming the check_rooted executable...
Code:
adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
6) Change the bootmode back to normal...
Code:
adb shell idme bootmode 4000
7) Reboot the system...
Code:
adb reboot
8) Once the Kindle Fire has rebooted into the system, install the Superuser app...
Code:
adb install C:\kfu\software\Superuser.apk
Congratulations! You have gained root privileges on the stock Kindle Fire software!
Installing a custom ROM
It should go without saying, but users who intend on staying with a rooted stock device need to skip this section. Flashing a custom ROM will overwrite the stock software and leave no trace of the original Kindle Fire interface.
Required software:
Any ROM you choose to install. Check the KF Development List as a starting point.
Note: Do not extract the contents of the ROM archive. The recovery program will need the actual zip file to install.
This section assumes the device is already booted into TWRP recovery.
1) Carefully read the ROM thread for specific directions and warnings provided by the developer when flashing any new ROM.
2) Copy the custom ROM zip file to the /sdcard directory on the Kindle Fire...
Code:
adb push C:\kfu\software\ROM.zip /sdcard/
You must replace the "ROM.zip" part of the above command to the actual name ROM's zip file you've downloaded.
3) From the main menu of TWRP, "Wipe -> Factory Reset" to remove the existing files in the data and cache partitions that could interfere with the operation of the new system software. A "Factory Reset" will delete any installed apps, software/network settings, etc. It will not touch the /sdcard directory that contains music, eBooks, and files of that nature.
4) From the main menu of TWRP, "Install" to flash the ROM onto your device. Navigate to the /sdcard directory on the left (should be the default the first time you use TWRP) and select the file from the list on the right. Then simply "Swipe to Confirm Flash" to install.
5) From the main menu of TWRP, "Reboot -> System" to boot into the newly flash ROM.
Congratulations! You have completely replaced the stock Kindle Fire software with a custom ROM!
Cleaning up
The zip files pushed onto the /sdcard during installation are only necessary during the installation process and do not need to take up space on the device after completing the install. Use a file manager or mount the storage device on the host computer to delete the files and reclaim the used space.
Coming soon...?
I've got some other topics in mind, but like I did with the KFFB, I'll see how users respond to this post before I continue. Please feel free to comment and make suggestions. I may not respond to everything, but I will keep the helpful comments in mind if/when I decide to expand this how-to guide. Thanks for reading.
Credits
jcase - For providing the basis for this guide and lending his expertise in rooting devices
pokey9000 - For his work on FFF and providing the fbmode exploit
TeamWin and Dees_Troy - For providing the TWRP recovery and continuing its development
ChainsDD - For the Superuser package
Unroot or Revert to Stock Software
This second post in the series details the procedures required to undo the steps taken in the first. Use it to unroot or revert back to the stock software like it just came from the factory. If you tried out the rooted stock software or a custom ROM for a while, but just prefer the no-frills stock software, you've come to the right place.
Unrooting the stock software
Required software:
None
This section assumes the device is already booted into the system software.
1) Uninstall the Superuser app
Code:
adb uninstall com.noshufou.android.su
2) Optional: Set the bootmode to recovery. Alternatively, use the recovery selection feature in FFF to boot into recovery during startup without manipulating the bootmode setting here. If you are more comfortable setting the bootmode directly...
Code:
adb shell su -c 'idme bootmode 5001'
3) Reboot the device into recovery...
Code:
adb reboot
4) Mount the data partition...
Code:
adb shell mount data
5) Optional: Delete the files that the Superuser app left behind...
Code:
adb shell rm -rf /data/data/com.noshufou.android.su
6) Mount the system partition...
Code:
adb shell mount system
7) Re-enable the root checker by renaming the check_rooted executable...
Code:
adb shell mv /system/bin/check_rooted.bak /system/bin/check_rooted
8) Delete the su binary from the device...
Code:
adb shell rm /system/xbin/su
9) From the main menu of TWRP, "Reboot -> System" to restart the device into the system software.
Congratulations! You have unrooted the stock Kindle Fire software!
Reverting to stock software
Required software:
Amazon Kindle Fire Software Update
Warning: Installing the Amazon Kindle Fire Software Update will not only replace the system software, but also overwrite the bootloader and recovery with the stock versions. Any custom bootloader and recovery like FFF and TWRP will be overwritten in the process.
This section assumes the device is already booted into TWRP recovery.
1) Copy the update bin file to the /sdcard as update.zip
Code:
adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip
2) From the main menu of TWRP, "Wipe -> Factory Reset" to remove the existing files in the data and cache partitions that could interfere with the operation of the new system software. A "Factory Reset" will delete any installed apps, software/network settings, etc. It will not touch the /sdcard directory that contains music, eBooks, and files of that nature.
3) From the main menu of TWRP, press the "Install" button to flash the stock software onto your device. Navigate to the /sdcard directory on the left and select the "update.zip" file from the list on the right. Then simply "Swipe to Confirm Flash" to install.
4) Optional: From the main menu of TWRP, "Wipe -> SD Card" to remove all files on the USB mountable storage space. This step will permanently delete all of the files that appear on a computer when the device is connected as a USB storage device.
5) From the main menu of TWRP, "Reboot -> System" to restart the device into the system software.
Congratulations! You have reverted the device to a completely stock Kindle Fire!
KFFB Supplement Post #3
Reserved...
Great explanations!
I wanted to thank you for explaining everything clearly so that people can understand what they are doing when installing their bootloader, recovery and new ROMs.
Thanks again... plee3
Thanks so much!
This worked flawlessly. I had gotten stuck trying to root with KFU (I think the driver is slightly funky in fastboot - so KFU failed to flash either recovery or bootloader and left me in fastboot mode) but using the '-i 0x1949' option with fastboot made everything work perfectly.
Once again you have done a beautiful guide. You are very good at this, and always look forward to more guides from you.
Keep um coming !!
Cheers
Thibor69 said:
Once again you have done a beautiful guide. You are very good at this, and always look forward to more guides from you.
Keep um coming !!
Cheers
Click to expand...
Click to collapse
I know, right?
can i follow this to root 6.3.1?
xXezmacXx said:
can i follow this to root 6.3.1?
Click to expand...
Click to collapse
Yes, it's been tested to work from 6.2.0 and up.
Needs Sticky
Great Work. Gets my vote (and really needs) to be sticky'd.
Thanks for listening
Sincerely,
William
[Kindle Fire: gedeROM v1.25 [KeyClicks Added] {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Thanks to all. I'm glad some of the readers got some use out of it.
Docs009 said:
Great Work. Gets my vote (and really needs) to be sticky'd.
Thanks for listening
Sincerely,
William
[Kindle Fire: gedeROM v1.25 [KeyClicks Added] {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Click to expand...
Click to collapse
If you think this guide will be useful to other users here, you can ask the moderators to review the thread and possibly make it a sticky. I would ask, but it seems a bit... uncouth to nominate my own post for sticky status.
Thanks for reading!
Gotta tell you, there should be some warnings/things to look out for in this guide. If you install all the latest Android SDKs (I pretend to develop in my spare time) it loads the wrong drivers. It will show up as "Android Device" or something like that. The correct drivers have it show up as "Android Composite Device". If you have the SDK in your path (which you need for Eclipse) after the first reboot it might load the wrong drivers again as it did with me which are the wrong ones and basically you won't be able to communicate with the Kindle again.
Took me almost an hour to get this thing off the "Kindle Fire" loading screen because of this problem/unawareness.
ExploreMN said:
Well, I followed the instructions. Got as far as "adb shell reboot" after the fbmode command. Now it just sits at "kindle fire" and shows up as an unknown device in device manager.
Is there anyway to recover from this or did I just junk my fire?
Click to expand...
Click to collapse
Your Kindle Fire is fine... it's in fastboot mode. The computer is most likely the problem. You'll have to make sure your device drivers are working properly, so the computer can send fastboot commands to the device.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
kinfauns said:
Your Kindle Fire is fine... it's in fastboot mode. The computer is most likely the problem. You'll have to make sure your device drivers are working properly, so the computer can send fastboot commands to the device.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
Thanks Kinfauns. I actually got it fixed without even reading about it...I get a little medieval on things that frustrate me and eventually got it figured out...I edited my post to warn people about what tripped me up!
ExploreMN said:
Gotta tell you, there should be some warnings/things to look out for in this guide. If you install all the latest Android SDKs (I pretend to develop in my spare time) it loads the wrong drivers. It will show up as "Android Device" or something like that. The correct drivers have it show up as "Android Composite Device". If you have the SDK in your path (which you need for Eclipse) after the first reboot it might load the wrong drivers again as it did with me which are the wrong ones and basically you won't be able to communicate with the Kindle again.
Took me almost an hour to get this thing off the "Kindle Fire" loading screen because of this problem/unawareness.
Click to expand...
Click to collapse
Well, I actually tell you at the beginning of this guide to read my guide for beginners. In that guide, I tell you to use the driver installer included in KFU. Any how-to guide has to make some set of assumptions and I made the assumption that you'd actually follow the previous set of instructions before proceeding onto the next. I think you'd agree that I cannot possibly account for every possible deviation a user might take away from my actual directions. If I even attempted such a thing, this guide would turn into Encyclopedia Britannica.
In addition, I also gave you ample warning about putting your device into fastboot mode by manipulating the bootmode. I made a clear suggestion for you to get a factory cable and use it to get into fastboot mode the "safe" way. I've never seen any other rooting guide/utility even make mention of this possibility, so I've gone above and beyond what you'd get anywhere else.
With those things together, I believe I've done the very best I can to minimize the possibility that you might get stuck and have to "get a little medieval" on your device. Regardless, I'm glad you got it figured out. Good luck with the rest of it.
kinfauns said:
Well, I actually tell you at the beginning of this guide to read my guide for beginners. In that guide, I tell you to use the driver installer included in KFU.
Click to expand...
Click to collapse
True enough. Just didn't think it would keep reloading the drivers from the SDK if the SDK was in the path for Eclipse. I'm guessing anyone who set up Eclipse would not think this is an issue and might get stuck like I did...so it's still worth mentioning. (to me at least)
The second installment of this how-to guide has been posted. Included are instructions on unrooting and reverting back to the stock software. Suggestions and comments are always appreciated. Thanks!
Thank you for the excellent guide.
For what it's worth, this guide is very helpful for the admitted "noob" who has somehow failed with a utility like KFU and needs to go back and work through the pieces step by step. Thank you for laying out an instruction manual with enough detail to not only do the steps needed - but also to begin to understand what I'm doing.
I've rooted my KF (thanks to your assistance) so that I could install Swype. I then was able to use OTA-Rootkeeper to "hide" my SU file so that I can use Amazon media on my Fire as I want to, but still get the benefits I wanted from a rooted device (primarily the use of the Android Market, "Google Play", and the use of Swype).
For those that don't *really* want to unroot but do want to still use the Amazon content tools, I HIGHLY recommend the OTA-Rootkeeper utility.
Thanks again!
Kinfauns,
My Kinde Fire was bricked, with power problems. So I did the short trick to repair the bootloaders, using the linux stick and this script here, provided by firekit: usb_fix_parts_and_install_fff_twrp
When I look into device manager i have "Android Phone - Android Composite ADB Interface", at printers and devices the name shows as Kindle.
Can I go direct to these instructions here?
Rooting the stock software
Users interested in flashing a custom ROM may elect to skip this section. Rooting the stock software is not a requirement to flash a custom ROM because the custom ROM will completely overwrite the stock software. However, if you are undecided on the question of rooted stock vs. custom ROM, root the stock software first and try that out for a while. The option to flash a custom ROM will still be available at a later time.
The following method of rooting the Kindle Fire stock software has been tested on 6.3.x and 6.2.x systems. Skip step #5 when rooting 6.2.x systems because the root checker does not exist in those versions.
Required software:
Superuser by ChainsDD
Note: Download the latest zip for Gingerbread/ICS (the filename should end in "efghi-signed.zip"). Two separate files will be needed from the contents of this zip file: the su binary from the system\bin folder and the Superuser.apk file from system\app folder.
This section assumes the device is already booted into TWRP recovery.
1) Remount the /system partition in read/write mode...
Code:
adb shell mount system
2) Copy the su binary onto the device...
Code:
adb push C:\kfu\software\su /system/xbin/
3) Change the owner of the su binary to root...
Code:
adb shell chown root:root /system/xbin/su
4) Set permissions for the su binary to run as root...
Code:
adb shell chmod 6755 /system/xbin/su
5) Disable the root checker by renaming the check_rooted executable...
Code:
adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
6) Change the bootmode back to normal...
Code:
adb shell idme bootmode 4000
7) Reboot the system...
Code:
adb reboot
8) Once the Kindle Fire has rebooted into the system, install the Superuser app...
Code:
adb install C:\kfu\software\Superuser.apk
Congratulations! You have gained root privileges on the stock Kindle Fire software!
Click to expand...
Click to collapse
DuendePaladino said:
Kinfauns,
My Kinde Fire was bricked, with power problems. So I did the short trick to repair the bootloaders, using the linux stick and this script here, provided by firekit: usb_fix_parts_and_install_fff_twrp
When I look into device manager i have "Android Phone - Android Composite ADB Interface", at printers and devices the name shows as Kindle.
Can I go direct to these instructions here?
Click to expand...
Click to collapse
If you used that script in Firekit, you should have FFF 1.2 and TWRP 2.0.0 installed, so technically, yes.... you can boot into TWRP and start following those directions. However, I would recommend that you upgrade your bootloader and recovery to the versions I have in the previous section... FFF 1.4a and TWRP 2.1.1. I won't go into all the reasons why, but they are "better" and likely to keep you out of trouble in the future. Since you already have FFF installed, it will be easy for you to get into fastboot mode. Once you are in fastboot mode, start with flashing TWRP and continue on from there.
Hi everyone. I followed the procedure and everything and this is what I get...
***********************************************
* Installing Permanent Root *
***********************************************
***********************************************
* Activating Fastboot (4002) *
***********************************************
Oops... something went wrong.
We are unable to locate your Kindle Fire.
Make sure it is plugged in and powered on.
twrp.img is missing.
So we will download it for you!
tools/cat: files/files.log: No such file or directory
tools/cat: files/files.log: No such file or directory
Access is denied.
Cannot open input file recovery\twrp.img
Download successful.
fff.bin is missing.
So we will download it for you!
tools/cat: files/files.log: No such file or directory
tools/cat: files/files.log: No such file or directory
Access is denied.
Cannot open input file recovery\fff.bin
Download successful.
***********************************************
* NOTICE *
***********************************************
tools/cat: files/files.log: No such file or directory
tools/cat: files/files.log: No such file or directory
Fastboot uses a different device than ADB.
You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU.
Installing FFF...
Cannot open input file recovery\fff.bin
error: cannot load 'recovery\fff.bin'
Installing TWRP...
Cannot open input file recovery\twrp.img
error: cannot load 'recovery\twrp.img'
Setting Recovery Bootmode.
... OKAY [ 0.198s]
finished. total time: 0.199s
rebooting...
finished. total time: 0.002s
Please wait...
Invalid permission
Usage: mount [-r] [-w] [-o options] [-t type] device directory
failed to copy 'files\su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Attempt to remove root checker.
failed on '/system/bin/check_rooted' - Read-only file system
Please wait...
Installing Superuser.apk
Error: Could not access the Package Manager. Is the system running?
***********************************************
* Root Installed *
***********************************************
Permanent root has been installed.
With great power, comes great responsibility.
Please be careful with how you use root.
Press any key to continue . . .
Everything is pluged in and working. I don't understand why I am getting all these errors.
Can someone please help me, I am a freshie...
Did the kfu detected your of correctly? Try to check your adb drivers.
aioen said:
Did the kfu detected your of correctly? Try to check your adb drivers.
Click to expand...
Click to collapse
Yes my drives are installed properly and KfU shows status as online.
did you allow installation from unkown sources? did you disconnect the usb transfer application? were you connected to the internet? and your drivers say android adb composite interface? and there are no question marks or exclamation points next to your driver? and are you using only a 2.0 usb port? have you downloaded a fresh copy to make sure the copy of kfu you have isnt in some form corrupted?
Thepooch said:
did you allow installation from unkown sources? did you disconnect the usb transfer application? were you connected to the internet? and your drivers say android adb composite interface? and there are no question marks or exclamation points next to your driver? and are you using only a 2.0 usb port? have you downloaded a fresh copy to make sure the copy of kfu you have isnt in some form corrupted?
Click to expand...
Click to collapse
Installation from unknown sources-OK
I m connected to internet on PC not on kindle
My driver says android adb composite interface and no exclamation mark there
i m using 2.0 usb port.
I have downloaded KFU from Xda 0.9.6 forum so it should be an updated one
AND hwta do you mean by disconnect the usb transfer application???
So what can be wrong?
I had same problem on a windows 7 machine. I then used my wife's win xp machine and it worked first try
Sent from my GT-N7000 using Tapatalk 2
In my experience the Windows drivers are flaky. I've had similar problems to what you are describing and fixed them by removing and reinstalling the drivers. And rebooting Windows. It's very frustrating when everything looks like it should be working only to find out a reinstall or reboot immediately fixes it.
I can't know if that will work in your case but might be worth a try.
- S
Sent from my Galaxy Nexus using xda premium
Same for me.
The same thing happens for me when I try to use the KFU v0.9.6. I dont believe it to be a driver issue either.
The install_drivers.bat would not install the drivers due to drivers not signed. So I had to install them manually. I also had to edit the adb_usb.ini file by adding the line:
0x1949
in my android sdk but ADB now reports connected.
The FFF did install but TWRP and root will not install. I have not tried clockwork mod.
I noticed that while trying to install root, the KFU reported that it was attemping to download TWRP. Is this normal behavior?
The TWRP will not download as the link it broken. It does download something and renames it to twrp.img but what it gets is way too small.
The link: TWRP=Click Here that is listed in the instructions under extras on This Page is broken and I suspect that the KFU is attemping to download from that location and instead getting the file doesn't exist page instead and renaming it.
When I manually track down twrp-blaze-2.0.0RC0.img and rename it to twrp.img then place it in the resources folder, the KFU finds it and attempts to install it but fails with md5 error.
akki12345 said:
Installation from unknown sources-OK
I m connected to internet on PC not on kindle
My driver says android adb composite interface and no exclamation mark there
i m using 2.0 usb port.
I have downloaded KFU from Xda 0.9.6 forum so it should be an updated one
AND hwta do you mean by disconnect the usb transfer application???
So what can be wrong?
Click to expand...
Click to collapse
Like when you first plug it in to your computer are you hitting the disconnect but to stop the file transfer app.. Also I would redownload the utility there's something amuck with your copy sounds like
can't download from KFU
Looks like im having the same problem. i'm not able to download superuser or TWRP via KFU. FFF, however, installed just fine... so now, everytime i reboot i get the new blue "kindle fire" logo with boot options. I gave up after a couple days of looking for a solution, and decided to try factory reset, to see if that would clear it off... nope. so i guess my question is does anybody know how to remove FFF after a failed but not detrimental root attempt.... orrrr, does anybody know of a real solution to the download issues i had. its weird, i was able to connect fine ( it detected my kindle, it said i was online, and in normal boot mode 4000, no root ) and install FFF, but nothing else seemed to work in the hundred (give or take a few) times i attempted the root process via KFU. thanks. tell me there's something i'm missing here.
---------- Post added at 11:05 AM ---------- Previous post was at 10:57 AM ----------
Also, it looks as if im getting the same errors you are. "Warning download couldn't be completed" Permissions denied, and mounting fails as well.
big mistake?
well i f'd up. i finally got twrp to install using a different file. however, it appears that i must've accidentally hit a wrong number when installing late last night, cause it appears i also have clockworkmod installed and it superceded twrp i guess.. can't load it. Anyone got any ideas on how to remove CWM with TWRP also installed. damn what a mess.
Instaling twrp with kfu 0.9.6 problem solve
dbramage said:
Looks like im having the same problem. i'm not able to download superuser or TWRP via KFU. FFF, however, installed just fine... so now, everytime i reboot i get the new blue "kindle fire" logo with boot options. I gave up after a couple days of looking for a solution, and decided to try factory reset, to see if that would clear it off... nope. so i guess my question is does anybody know how to remove FFF after a failed but not detrimental root attempt.... orrrr, does anybody know of a real solution to the download issues i had. its weird, i was able to connect fine ( it detected my kindle, it said i was online, and in normal boot mode 4000, no root ) and install FFF, but nothing else seemed to work in the hundred (give or take a few) times i attempted the root process via KFU. thanks. tell me there's something i'm missing here.
---------- Post added at 11:05 AM ---------- Previous post was at 10:57 AM ----------
Also, it looks as if im getting the same errors you are. "Warning download couldn't be completed" Permissions denied, and mounting fails as well.
Click to expand...
Click to collapse
Hey everybody I had the same problem with twrp, but you just have to download the twrp image from the team win site and placed into the folder call recovery and rename it to twrp, after that the kfu will install it correctly.
I am trying to sideload the new 7.1.1 OTA image from Google. When I run the command adb sideload [PATH TO UPDATE]\updatefile.zip it comes back with:
loading: 'update.zip'
* cannot read 'update.zip' *
File Permissions are all OK
The platform-tools have been updated using sdk-manager
ADB devices shows the device.
The phone is encrypted (I am guessing this is the issue)
Any help would be appreciated.
hideous said:
I am trying to sideload the new 7.1.1 OTA image from Google. When I run the command adb sideload [PATH TO UPDATE]\updatefile.zip it comes back with:
loading: 'update.zip'
* cannot read 'update.zip' *
File Permissions are all OK
The platform-tools have been updated using sdk-manager
ADB devices shows the device.
The phone is encrypted (I am guessing this is the issue)
Any help would be appreciated.
Click to expand...
Click to collapse
Just checking the obvious....but updatefile.zip is in your computer that's executing the ADB command, not on you phone, correct?
edit: Also, is your ota file actually named updatefile.zip?
Phone's encryption doesn't matter here.
Yes, I am running this from my computer. I have tried the original name for the OTA (also tried downloading it multiple times)
Also the phone is completely stock with a locked bootloader.
EDIT:
I turned on Tracing and this is the full error:
c:\Users\user\Nexus6P\ROMS\OTA>adb sideload angler-ota-nmf26f-61b4a915.zip
adb I 15200 3428 adb_trace.cpp:169] Android Debug Bridge version 1.0.36
adb I 15200 3428 adb_trace.cpp:169] Revision 302830efc153-android
adb I 15200 3428 adb_trace.cpp:169]
loading: 'angler-ota-nmf26f-61b4a915.zip'adb I 15200 3428 sysdeps_win32.cpp:145] load_file: could not allocate 1331770063 bytes
* cannot read 'angler-ota-nmf26f-61b4a915.zip' *
Are you on Windows 10? Experienced this issue yesterday and I also searched a long time.
In the device manager, my device showed up as "LeMobile Android Device", because this seems to be the newest Android driver. ADB is not working correctly with the LeMobile drivers. Had to switch back via "Use previous drivers" to the Nexus 6P drivers, then it worked like a charm.
The OTA image needs to be in the platform-tools folder along with the adb executable. Then Shift/right- click in the folder and select "Open command prompt here". Next type the command "adb sideload angler-ota-nmf26f-61b4a915.zip" without the quotes, this after selecting "Apply update from ADB" from the recovery menu. You may need to unplug your phone, and then plug it back in if the command fails.