Hello everyone,
just this morning I began the process of rooting my Kindle Fire and everything seemed to be working fine until the process came to this step and now everything has been stuck on that. My KF shows "kindle fire" on the screen and nothing's happening. Since I cannot post links to pictures the computer screen shows command prompt windows with red letters saying this:
NOTICE
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...
<waiting for device>
I didn't uplug the cable or anything else, just left it like that before someone tells me what I should do.
I don't think that anything on KF has been tampered with since I only got two "download successful" messages before I got this one. Maybe I can just reboot KF and KFU and then change the bootmode to normal?
yes you can with the bootloader or with kfu have you tryed to rerun the drivers though? Powering it off and back on with it plugged in may be beneficial.
I tried that but I cannot get it pass that logo.
I restarted my comp and KF and when I connect them with the cable windows recognises it as Android ADB Interface but my KFU doesn't "see it" (says: ADB Stauts Offline).
Is there any other way to change the bootmode? Or am I doing something wrong?
EDIT: I have managed to resolve the problem using adb commands (fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot).
I think I will not try to root it again..
What does your boot logo look like?
It looked like standard kindle fire logo upon turning it on, but without that "animation" (that slightly changes it's colour).
It made me really scared I must admit and now I am not willing to try to root it again, at least not for some time
What you need to do at this point is make sure you have TWRP and FFF1.4 installed. They are essential to fixing problems easily in the future.
Can I install them without rooting?
=FI=Ghost said:
Can I install them without rooting?
Click to expand...
Click to collapse
Yes, but by the sound of it you already are rooted. The problem isn't with rooting, it's how Windows handles adb and fastboot.
If you were able to change your bootmode back to 4000, the rest should be simple.
I would suggest reading this to get a better understanding of what's going on:
http://forum.xda-developers.com/showpost.php?p=23747567
Is there a way to check if my KF is rooted or not?
I've read that guide a few times and even written down some notes but I am still a bit puzzled with all these things.
Get TerminalEmulator.apk (side load it if you have to) and enter the following command:
Code:
su
You should get a Superuser request. When you accept, your prompt should change from $ to #
If your prompt doesn't change, then you aren't rooted.
Hi there,
it's been a while since I had a chance to play with my KF.
Anyway, I've managed to install the Terminal Emulator and when I enter "su" command I get "su: permission denied" message.
That means I am not rooted, right?
Most likely that is the case unless perhaps you missed a prompt asking for permissions at the intial launch but I would say your not rooted
Thank you very much.
Can there be any harm done if I try to root it again and it turns out that I am already rooted?
I do have a little recommendation for you if perhaps you attempt to root again and you have adb online and working when you see that on the intial start of kfu when your kindle is plugged in leave the utility open unplug your kindle and run a number like 2 or 3 (remember while unplugged) it will update the files and links in the utility itself then reboot your computer and recheck device status with kfu. If your kindle is in good working condition take some time read around before taking the leap the more you learn the better it can save you alot of heartache.
---------- Post added at 03:23 AM ---------- Previous post was at 03:21 AM ----------
if your rooted it will likely fail because the file already exists or it will just overwrite shouldnt be any harm that I am aware of.
---------- Post added at 03:27 AM ---------- Previous post was at 03:23 AM ----------
if I had to pick an order to do the process I would first root then install twrp then fff each time waiting till it has rebooted and your sure the process is complete never panic and unplug it
You are very helpful mate, thank you very much.
When I tried to root the first time I followed this tutorial:
http://www.youtube.com/watch?v=mwMHIkX20YI
In the video description it says this:
***NOTICE
there seems to be an issue with the kindle fire utility not installing the superuser app which will finish giving you root. So what you can do to remedy this is once you have the twrp recovery, you can flash this stock rooted version of 6.3 (THIS WILL WIPE ALL UR DATA)
OR you can just download this superuser.apk, and sideload it onto your kindle fire (I have a video for sideloading if you dont know how, your data will NOT be wiped)
Maybe this is the reason why I get this message?
there was an intial problem with kfu just a while back where it wasnt pushing the superuser apk. I believe that problem has been remedied another thing make sure your computer is online when you do it so it can download the files thats why I say do a dry run with out your kindle plugged in so it auto updates the download links
---------- Post added at 03:33 AM ---------- Previous post was at 03:32 AM ----------
the superuser apk can be side loaded as well just make sure all the rest was successful
---------- Post added at 03:35 AM ---------- Previous post was at 03:33 AM ----------
and I really dont recommend flashing stock unless you have serious problems thats kinda a last resort cause flashing stock will also wipe your twrp and bootloader so that doesnt make sense
---------- Post added at 03:37 AM ---------- Previous post was at 03:35 AM ----------
Nat3mill is a good guy and he makes pretty good video but this last one wasnt as good as the rest
Ok, then I will do what you recommended in message 15.
Once again thank you very much, I will report with the results later
I used his videos for all my procedures but I didnt have anything go awry make sure you have checked allow installtion from unknown sources this will allow the loading of the files and is a very common mistake
---------- Post added at 03:42 AM ---------- Previous post was at 03:40 AM ----------
if you get in a bind dont do anthing ask for help that isnt a problem
---------- Post added at 03:43 AM ---------- Previous post was at 03:42 AM ----------
good luck
kinda the same situation... kinda
well i can say that i had the exact same issue you were having. turned out i was stuck in fastboot just needed to change boot mode in KFU. can also be done from FFF if its the right version i believe. My issue is that i had the same problems, not being 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 said i was online, and in normal boot mode 4000 ) and install FFF, but nothing else seemed to work in the hundred (give or take a few) times i attempted the root process vis KFU. thanks.
Related
I'm beggining to find desperation, please help
so my kindle was full of crappy apps (mybad) so i tried to restore it to factory defaults as i had done it before through the Android settings, as usual but, when it was supposed to start up again it just got stuck on TWRP and I've tried fastboot, I've tried normal boot through all means but it just stucks up on the kindle logo, quite disappointing, when I use ADB to fastboot or normalboot, i get this error:
-exec ' /system/bin/sh' failed: No such file or directory (2) -
also the ADB status refers to online and an unknown bootmode, but in one of the many methods I've tried, i saw a bootmode that read 0x5001 which was really weird for me to read but anyway, i'd thank you for your differential diagnosis and treatment
PLEASEE!!!!!
PD: i tried ubuntu with the firekit but the file "fk", it just won't open on the terminal, it even crashes opening as text
Alright, I think I might be able to help with this. Download kindle fire update.
http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620#download
Boot into twrp, and go to to mount. Plug in Kindle fire to your computer. Select mount usb storage. Rename the file to update.zip, move it to your kindle fire. Select un-mount, Then go to home in twrp. Then, wipe factory reset, dalvik cache, cache, and system. Then, go and flash the zip. After that is done, reboot system. You should then be ok.
Good luck
didnt work
okay, i did it.. and it seemed like it was over but then.. when it was supposed to start, it said... battery is too low.. so i left it charging and when it wanted to boot it got stuck again on kindle logo, and now i cannot even boot on recovery
any thoughts?
This seems very weird. Give the KF a full charge. When is is done charging power it up and plug it in to your computer. Use KFU to set boot mode as recovery. Then re-flash the update. Or, you might try going to wipe and selecting factory reset
---------- Post added at 09:19 PM ---------- Previous post was at 09:15 PM ----------
You might find that Twrp was un-installed. If it was, Use KFU to re-install it.
bigger problem!! TWRP wont install... am I dead?
No hows your battery?
---------- Post added at 06:15 PM ---------- Previous post was at 06:12 PM ----------
Firekit http://forum.xda-developers.com/showthread.php?t=1430038
Are you able to connect your KF via adb?
Why don't you try this repair kit.
http://forum.xda-developers.com/showthread.php?t=1430038
Or this and use fastboot to flash twrp just dont fastboot flash a zip to your bootloader or you will have a seroius brick. Bin format only for fastboot http://forum.xda-developers.com/showthread.php?t=1670405
Or, you could take a different approach, the amazon update that you flashed before might have partly worked. If you did not see twrp when you booted up kf, then your at stock. You can return it to amazon and get full refund. They will never know you rooted it.
Just a thought let it charge via usb for a few hours and then hold the power button for a minute or so to be assured it is powered off then power it up.
yakkn said:
Are you able to connect your KF via adb?
Why don't you try this repair kit.
http://forum.xda-developers.com/showthread.php?t=1430038
Click to expand...
Click to collapse
yeah... tried that one too but ... ubuntu wont open the freaking file, has it happened to anyone?
Cibersebas951027 said:
yeah... tried that one too but ... ubuntu wont open the freaking file, has it happened to anyone?
Click to expand...
Click to collapse
Sounds like you have firekit put on your usb incorrectly
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
You extract the file to the head of the usb there is only one file inside of the zip folder I believe its firekit.sh
If you have it correctly placed the command in the op will launch it and you need to be connected to the internet for some of the options to work in case there is any fetching of files from the net. I can almost guarantee the trouble your having with firekit is one of two things not applied to the USB correctly or your launching it wrong. Open a terminal and type sudo /cdrom/fk this will give you a great list of commands in the terminal simply copy and paste your chosen command do the short trick keep it shorted and plug it in after it says waiting for device you'll know when you got it right
nothing is working
Please! HELP Nothing is working!! are there any very specific steps on the ubuntu installation_ because i get stuck on the SDK installation.. it says it failed doing something!!.. this is really disappointing.. plus.. i live outside the US .. and retrieving it is not an option .. please give me some ideas because im out of them!
thank you!!
Sent you a pm also I believe you have firekit applied incorrectly I will assist if you wish
---------- Post added at 03:50 PM ---------- Previous post was at 03:44 PM ----------
Could just be a matter of reseting your bootmode and getting you to recovery where you can do a fresh flash
HELPPPP
PLEASE HELP!!
firekit sends an error... the same that kfu does... and andab.sh is also not working.. im on ubuntu finnally but i can't unbrick im desperate .. please help.. there has got to be a way of like reconstructing the kindles firmware!! im begging
I used the Kindle FIre Utility that was stickied to install ClockworkMod. Unfortunately, the utility gives an error message when I attempted to root or install FFF or really do anything else. However, I was able to boot into CWM using the utility. I remember from my experience with ROMs on the Samsung Captivate (AT&T) that installing new ROMs would overwrite things like being unrooted or even recovery mode itself. So I downloaded the zip of Alien Droid and flashed it using ClockworkMod. I wiped data and cache and dalvik cache. I then rebooted the device to find it bootlooping on the Alien Droid logo. So I plug it back into the computer, the computer recognizes the ADB interface as "Android." However, Kindle Fire Utility does not recognize the device anymore since it is not known as "kindle" or at least that's what I seemed to gather. So It's stuck bootlooping for now and I'm not sure how to get it out of the boot loop or how to get back to stock. Anybody have any pointers?
Links:
[Root][TWRP][FFF][CWM]Kindle Fire Utility v0.9.6 (5/09/12)
[ROM] [CM10] [JB]â–ºAlien Droidâ—„(Complete GUI customization)
What version of CWM did you use? (very important)
soupmagnet said:
What version of CWM did you use? (very important)
Click to expand...
Click to collapse
The version that came with the Kindle Fire Utility I linked above. I'm not sure what number it is, but it allowed for touch functions and was black with red text.
The only version that comes to kfu anymore is sbloods but I only know it to be gb and ics safe don't know about jelly bean
---------- Post added at 09:47 PM ---------- Previous post was at 09:41 PM ----------
Also you should have included a factory reset and system wipe to you scheme of wipes all you have is a broken system very likely...
I would say install twrp manually in fastboot (temporary or otherwise)
Thepooch said:
The only version that comes to kfu anymore is sbloods but I only know it to be gb and ics safe don't know about jelly bean
---------- Post added at 09:47 PM ---------- Previous post was at 09:41 PM ----------
Also you should have included a factory reset and system wipe to you scheme of wipes all you have is a broken system very likely...
Click to expand...
Click to collapse
I did do a factory reset. I accidentally mentioned in the post that I wiped data, but what I meant was factory reset. The kindle still shows up in the computer when I plug it in, so I feel like there is some hope.
Did you create a backup?
soupmagnet said:
I would say install twrp manually in fastboot (temporary or otherwise)
Click to expand...
Click to collapse
How would I go about this while bootlooping?
Thepooch said:
Did you create a backup?
Click to expand...
Click to collapse
No, but how would I use a backup anyway while bootlooping?
EDIT: could I use a backup from another kindle fire using this method?
My thought was to get back into recovery and restore your backup but that's not possible without fff
A backup from another kindle if it was created in cwmr yes I believe this is possible...
thethinkman said:
How would I go about this while bootlooping?
Click to expand...
Click to collapse
Even while bootlooping, you should still be able to issue adb commands, check your drivers. Also, the Alien Droid animation takes a really long time the first time around. How long did you let it sit before shutting it off?
soupmagnet said:
Even while bootlooping, you should still be able to issue adb commands, check your drivers. Also, the Alien Droid animation takes a really long time the first time around. How long did you let it sit before shutting it off?
Click to expand...
Click to collapse
If your bootlooping but still get adb acces before it reboots, you should try the steps in this post...
http://forum.xda-developers.com/showpost.php?p=30098800&postcount=7
Then flash whatever rom or erase cache/dalvik-cache/userdata.
Even while bootlooping, you should still be able to issue adb commands, check your drivers. Also, the Alien Droid animation takes a really long time the first time around. How long did you let it sit before shutting it off?
Click to expand...
Click to collapse
This is true. Although I don't know much about how to operate adb, I do have it installed. I waited an hour or two, the animation stops at some point and freezes but the usb connection still works.
lmntone said:
If your bootlooping but still get adb acces before it reboots, you should try the steps in this post...
http://forum.xda-developers.com/showpost.php?p=30098800&postcount=7
Then flash whatever rom or erase cache/dalvik-cache/userdata.
Click to expand...
Click to collapse
I don't currently have TWRP installed on the kindle, just clockworkmod. I will try to install TWRP from adb and see what I can do.
EDIT: While my computer detects the kindle as an "Android ADB Interface" when I type "adb devices" into cmd nothing shows when the kindle is plugged in (but my phone shows when it's plugged in with USB debugging enabled, so I know I have it installed properly at least). I think the proper drivers are not installed.
EDIT 2: I uninstalled the driver for it to install the google usb driver but it failed to install the new one. Now when I plug the Kindle in it shows up as an empty Removable device in Computer butt does not show up anywhere else.
thethinkman said:
This is true. Although I don't know much about how to operate adb, I do have it installed. I waited an hour or two, the animation stops at some point and freezes but the usb connection still works.
I don't currently have TWRP installed on the kindle, just clockworkmod. I will try to install TWRP from adb and see what I can do.
EDIT: While my computer detects the kindle as an "Android ADB Interface" when I type "adb devices" into cmd nothing shows when the kindle is plugged in (but my phone shows when it's plugged in with USB debugging enabled, so I know I have it installed properly at least). I think the proper drivers are not installed.
EDIT 2: I uninstalled the driver for it to install the google usb driver but it failed to install the new one. Now when I plug the Kindle in it shows up as an empty Removable device in Computer butt does not show up anywhere else.
Click to expand...
Click to collapse
"Android ADB Interface" usually appears in the device manager when the KF is in fastboot mode, but if you are seeing the boot animation from the ROM, it cannot be in fastboot mode. I'm not sure where your KF is in the boot process, so it's important to figure that out first. Take a look at this fastboot guide...
http://forum.xda-developers.com/showthread.php?t=1668159
and it sounds like your device drivers are going to need some help as well...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
kinfauns said:
"Android ADB Interface" usually appears in the device manager when the KF is in fastboot mode, but if you are seeing the boot animation from the ROM, it cannot be in fastboot mode. I'm not sure where your KF is in the boot process, so it's important to figure that out first. Take a look at this fastboot guide...
http://forum.xda-developers.com/showthread.php?t=1668159
and it sounds like your device drivers are going to need some help as well...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
I installed the drivers and now the Kindle is detected by adb when I type adb devices. ADB tells me it is in normal boot mode (4000). However, I cannot switch to ffastboot. It tells me it cannot find the drive specified and that permission is denied.
FFF, assuming you installed it, goes into temporary fastboot for the first few seconds the the bootloader is running. Use that time to do what you need to do in fastboot. When the device detects you are trying to do something in fastboot during this time, it will stop the countdown and stay in fastboot.
So for hours I have been in the forums everywhere on the internet always leading back here. I am trying to root my kindle fire. I have everything set up the way it should adb enabled the whole 9 yards. I used the kindle fire utility to root. However Burrito root on my kindle fire says i need to run "adb shell /data/local/tmp/BurritoRoot3.bin --root" so i did, after I do that I do the "adb shell /data/local/tmp/BurritoRoot3.bin --intstall" it shows up and looks good. BurritoRoot says thank you I go to flash the bootloader and it says access denied bootloader not flashed then run "adb shell /data/local/tmp/BurritoRoot3.bin --root" . If i opt not to install the bootloader i'm back at the run"adb shell /data/local/tmp/BurritoRoot3.bin --root"
I HATE THIS, i'm so stuck so lost. and so new to this. Please someone shed some light on this!!! I want jellybean on here bad!
That's because burrito root is outdated it will not work for 6.31
You need the 9.6 version of kfu if your gonna flash a rom rooting is obsolete all you need is fff and twrp and you can flash a rom but right now the download for twrp is broken I would wait till it is fixed and confirmed fixed before attempting to do anything plain and simple....
The newest version can be found here http://forum.xda-developers.com/showthread.php?t=1399889
Thepooch said:
That's because burrito root is outdated it will not work for 6.31
You need the 9.6 version of kfu if your gonna flash a rom rooting is obsolete all you need is fff and twrp and you can flash a rom but right now the download for twrp is broken I would wait till it is fixed and confirmed fixed before attempting to do anything plain and simple....
The newest version can be found here http://forum.xda-developers.com/showthread.php?t=1399889
Click to expand...
Click to collapse
No.. I have the 9.6 version and I do not have 6.31 on my kindle. When I try to install twrp and firefirefire it tells me I need to run "adb shell /data/local/tmp/BurritoRoot3.bin --intstall"
I may be wrong (unlikely) but I'm 99.999999999% sure KFU 9.6 does NOT use (or even call for) BurritoRoot to gain temporary root access. It uses a certain binary to set your bootmode to "fastboot" so you can install and access custom recovery, which is what gives you the temporary root access needed to permanently root the device.
Perhaps you downloaded the wrong one?
soupmagnet said:
I may be wrong (unlikely) but I'm 99.999999999% sure KFU 9.6 does NOT use (or even call for) BurritoRoot to gain temporary root access. It uses a certain binary to set your bootmode to "fastboot" so you can install and access custom recovery, which is what gives you the temporary root access needed to permanently root the device.
Perhaps you downloaded the wrong one?
Click to expand...
Click to collapse
I have the correct one. About a year ago i tried to root it and I got that error. I thought before I unrooted and restored my kindle. i guess i did not. So now I cant seem to do anything because of my current issue. It works fine, however when i plug my kindle into my computer the sdcard does not show up. I just want this thing to be normal now!
Ok, what ROM are you running? Most custom ROMs these days require you to turn USB debugging off before it will mount the sdcard to USB, unless you're in recovery, in which case you have to use the "mount" function.
soupmagnet said:
Ok, what ROM are you running? Most custom ROMs these days require you to turn USB debugging off before it will mount the sdcard to USB, unless you're in recovery, in which case you have to use the "mount" function.
Click to expand...
Click to collapse
No rom.. Its the standard kindle fire android os. I tried rooting about a year ago with burrito root. didnt work.. and now Its still the standard kindle os. It does not show the sdcard. ALSO when i boot i get the triangle to boot into recovery but I cant actually boot into it. this has been going on for a year....
Well, what do you want to do with it? Do you want to try and root it again? Install recovery and FFF?
There's probably no way to tell exactly what's wrong (or fix it) without reinstalling either a new stock or custom ROM. But if I were to guess, I would say it would probably have something to do with your computer, considering you haven't done much to the device other than attempting root. Although, the fact that your recovery partition is either missing or corrupt is a bit concerning. It was obviously installed because of the version of FFF you have was packaged with it, so the fact you can't access it is pretty strange.
soupmagnet said:
Well, what do you want to do with it? Do you want to try and root it again? Install recovery and FFF?
There's probably no way to tell exactly what's wrong (or fix it) without reinstalling either a new stock or custom ROM. But if I were to guess, I would say it would probably have something to do with your computer, considering you haven't done much to the device other than attempting root. Although, the fact that your recovery partition is either missing or corrupt is a bit concerning. It was obviously installed because of the version of FFF you have was packaged with it, so the fact you can't access it is pretty strange.
Click to expand...
Click to collapse
Well, I wanted to install jellybean on it, but seeing as I cant get it rooted fully or unrooted? appearently and FFF and twrp on there correctly i tried just making it "normal" or "stock" however from what i read, i cant do that without access to the sdcard. So I'm lost. it doesnt only happen on the one computer, it happens on several. Any ideas?
tadcrazio said:
Well, I wanted to install jellybean on it, but seeing as I cant get it rooted fully or unrooted? appearently and FFF and twrp on there correctly i tried just making it "normal" or "stock" however from what i read, i cant do that without access to the sdcard. So I'm lost. it doesnt only happen on the one computer, it happens on several. Any ideas?
Click to expand...
Click to collapse
http://www.linuxliveusb.com/
http://forum.xda-developers.com/showthread.php?p=22067293
I'm on ubuntu as we speak.. no sdcard.. not sure what you want me to do..
tadcrazio said:
I'm on ubuntu as we speak.. no sdcard.. not sure what you want me to do..
Click to expand...
Click to collapse
I did what was in that thread.. and now getting jellybean?
tadcrazio said:
I'm on ubuntu as we speak.. no sdcard.. not sure what you want me to do..
Click to expand...
Click to collapse
::banging head on desk::
Why didn't you say you were already on Linux? Is it safe to assume you already have your udev rules set up for the KF as well?? Use the Pokey9000 method (fbmode) to put it into fastboot, reinstall TWRP and then use TWRP to install FFF1.4. Neither one of those requires the sdcard (but TWRP may give you access to it). TWRP gives you the temporary root needed to flash a custom ROM and permanently root it, which may very well fix all of your problems.
If not, at least you have something better to work from.
---------- Post added at 11:29 PM ---------- Previous post was at 11:26 PM ----------
Are you unable to use TWRP to mount your sdcard or use "adb push" to get something to it? You may have to try and mount it with the command line. It seems you somehow lost your mountpoint
---------- Post added at 11:50 PM ---------- Previous post was at 11:29 PM ----------
What do you get when you enter (in recovery):
Code:
adb shell cat /proc/partitions
soupmagnet said:
::banging head on desk::
Why didn't you say you were already on Linux? Is it safe to assume you already have your udev rules set up for the KF as well?? Use the Pokey9000 method (fbmode) to put it into fastboot, reinstall TWRP and then use TWRP to install FFF1.4. Neither one of those requires the sdcard (but TWRP may give you access to it). TWRP gives you the temporary root needed to flash a custom ROM and permanently root it, which may very well fix all of your problems.
If not, at least you have something better to work from.
---------- Post added at 11:29 PM ---------- Previous post was at 11:26 PM ----------
Are you unable to use TWRP to mount your sdcard or use "adb push" to get something to it? You may have to try and mount it with the command line. It seems you somehow lost your mountpoint
---------- Post added at 11:50 PM ---------- Previous post was at 11:29 PM ----------
What do you get when you enter (in recovery):
Code:
adb shell cat /proc/partitions
Click to expand...
Click to collapse
okay.. Well I was on windows 7 all prior to this. I do not have edev rule set up i dont think.. All of this is new to me. Only thing i did was set up adb from the link you posted earlier
Ok, my apologies. You need to get into recovery and enter the previous code so we can see if your sdcard partition even exists. If so we'll try to mount it via command line. It may be as simple as reformatting it or recreating the mountpoint.
If not, we'll probably have to rebuild your partition table, which isn't as bad as it seems.
Either way, it's most likely fixable.
soupmagnet said:
Ok, my apologies. You need to get into recovery and enter the previous code so we can see if your sdcard partition even exists. If so we'll try to mount it via command line. It may be as simple as reformatting it or recreating the mountpoint.
If not, we'll probably have to rebuild your partition table, which isn't as bad as it seems.
Either way, it's most likely fixable.
Click to expand...
Click to collapse
I can't get into recovery. When i boot up it has the yellow triangle with fire and at the bottom says press powerbutton for recovery. If i hold the powerbutton it either gets in a bootloop or shuts off..
tadcrazio said:
I can't get into recovery. When i boot up it has the yellow triangle with fire and at the bottom says press powerbutton for recovery. If i hold the powerbutton it either gets in a bootloop or shuts off..
Click to expand...
Click to collapse
Which is why I said earlier to reinstall TWRP and then FFF1.4.
[Edit:] just be sure to flash FFF1.4 in recovery.
soupmagnet said:
Which is why I said earlier to reinstall TWRP and then FFF1.4.
[Edit:] just be sure to flash FFF1.4 in recovery.
Click to expand...
Click to collapse
Reinstall them on linux or in windows? if on linux how?
Whichever one works for you. If you're able to send adb and fastboot commands with no problem in Windows then use it. If not, you'll have to use Linux.
soupmagnet said:
Whichever one works for you. If you're able to send adb and fastboot commands with no problem in Windows then use it. If not, you'll have to use Linux.
Click to expand...
Click to collapse
oi, i'm probably overlooking something and being a pain in the neck. But I dont know the commands for either one.. I'm sorry i need like step by step instructions unfortunately
Okay, so I had rooted my Fire, installed a Rom there and then decided to put it back to stock for a bit and then finally decided to flash yet another rom... This last time it appears to have completely bricked my Fire.
It's stuck at the "Kindle Fire" logo screen. I've tried the "Unbrick utility" as well as several others. It won't allow me to do much of anything with it.
My computer recognizes it as a device when you plug it in. It shows up in device manage as an android device. All drivers had been loaded before, as well as updated.
I'm at a loss at this point, does anyone have any recommendations to even get me back to twrp so I can attempt to do something with it?
Thanks
Neely
The device is in fastboot. Use fastboot commands to install FFF1.4 and TWRP, then change your bootmode to normal.
soupmagnet said:
The device is in fastboot. Use fastboot commands to install FFF1.4 and TWRP, then change your bootmode to normal.
Click to expand...
Click to collapse
I have tried installing TWRP and FFF before and it doesn't appear to get me anywhere. Is there a special trick to do this?
Thanks for your help btw!
Nope. If your drivers are working properly the device will accept fastboot commands.
obvious noob or oblivious maybe
soupmagnet said:
Nope. If your drivers are working properly the device will accept fastboot commands.
Click to expand...
Click to collapse
I've tried pushing fff and twrp and i'm still stuck in the same spot. It's obvious to me that I am needing a complete hand holding baby step guide. I'm admitting my ignorance.
I've tried several different things and have yet to have one that has worked.
Try this to sort your driver issues the we'll go from there http://forum.xda-developers.com/showthread.php?t=1850038
Thepooch said:
Try this to sort your driver issues the we'll go from there http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
Okay, tried Soupkit using Ubuntu 12.04 and still no luck. With the device still plugged into Ubuntu and when I run either adb or fastboot commands I'm still getting "waiting for device". I've tried turning off the KF and then plugging it in, as well as leaving it on. It won't even accept the reboot command from Ubuntu. I am at least able to get that within windows.
I tried:
adb shell idme bootmode 4002
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
fastboot -i 0x1949 getvar product
fastboot -i recovery twrp.img
All of which just return "waiting for device" and never actually do anything.
are there any other commands I should be trying, or any other commands I'm missing?
Yep, it has come to my attention that the stock bootloader (orange Kindle Fire logo) has a different product ID. I'll post a version for stock bootloaders sometime today.
---------- Post added at 12:55 PM ---------- Previous post was at 12:51 PM ----------
PM me and I'll help you fix it.
soupmagnet said:
Yep, it has come to my attention that the stock bootloader (orange Kindle Fire logo) has a different product ID. I'll post a version for stock bootloaders sometime today.
---------- Post added at 12:55 PM ---------- Previous post was at 12:51 PM ----------
PM me and I'll help you fix it.
Click to expand...
Click to collapse
Okay great!!
Kindle Fire Bricked
zacpac2020 said:
If you still need help, try using this. It's the Kindle Fire Utility, and you can run the install-drivers.bat file to ensure your drivers are correctly installed, and then use it to change the bootmode. http://forum.xda-developers.com/showthread.php?t=1399889
Click to expand...
Click to collapse
Thanks I appreciate your help, but I'd been using the KFU and something happened this last time while installing a ROM that basically bricked my device. But between the help of Soupmagnet and SkOrPn I've got a factory cable on the way and this sounds like it will correct all of my issues.
Thanks again,
Neely
Hello,
I am attempting to install CyanogenMod on a Kindle Fire HD 8.9". It appears the Fire OS received the recent OTA update to 8.5.1.
Whenever I attempt to root it using the restore exploit used in KFFirstAide or Bin4ry, the device will reboot into a state in which it is nearly unusable. It takes ~2 minutes just to get to the carousel screen from the lock screen. A reset to factory settings fixes this, and I have done this a two times thus far. I tried an application on my PC called Kingo Root to root it, and it does not cause the device to act strangely and slowly, but I do not have access to su. Beyond this, I am unable to access Fastboot. Fastboot just says <Waiting for device> whenever I start my device after using the fastboot -i 0x1949 getvar product or any other Fastboot command. I believe I have installed the drivers properly, and the ADB works fine.
What other information should I provide? Are there any steps I could/should try?
Thanks!
When i installed cm11 i had this same problem immediately after root. Once i installed cm11 it went away. Not sure why but i hope this helps. If you are keeping the Amazon os i don't have a good solution
Well, I was able to get into Fastboot and install TWRP. Now the tablet will not let me push the CyanogenMod ZIP to the internal storage.
Any ideas? ADB sideload refuses to load in TWRP and ADB says no devices are connected.
Uninstall the drivers in the device manager and let it reinstall the drivers, then adb should work.
I love it if this guy gets it working, teamwork ftw!
Shack70 said:
I love it if this guy gets it working, teamwork ftw!
Click to expand...
Click to collapse
i'm stuck with the 5.8.1 (my fault i would to try i lost my root) .
Anyone found solution to root this rom ?
i tried a lot of old tools, but no luck....
thank you
Same problem here, I have lost root with 8.5.1 update, old root methods don't work.
Update!
Hi everyone!
I gave up on trying to root and decided to just get the ROM flashed via TWRP (which can be done without root).
So I installed the drivers from here after disabling driver signature enforcement: http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Now, I am in TWRP.... But I did not transfer the CyanogenMod ZIP to my device. Now I am stuck trying to get ADB sideload to work so I may push the zip to the device. No success thus far. I cannot get the sideload to work, though. The Kindle will not connect to the PC for ADB (no yellow triangles in Device Manager, nothing) and I cannot get into the original OS... So, I am stuck.
Any ideas now?
jasona99:
I am not an expert, but I understand that before install twrp, second bootloader and a custom rom in a Kindle Fire Hd 8.9, you need to be ROOTED. In all the guides to be rooted is a must step, maybe that is where begin all your problems...
jasona99 said:
Hello,
I am attempting to install CyanogenMod on a Kindle Fire HD 8.9". It appears the Fire OS received the recent OTA update to 8.5.1.
Whenever I attempt to root it using the restore exploit used in KFFirstAide or Bin4ry, the device will reboot into a state in which it is nearly unusable. It takes ~2 minutes just to get to the carousel screen from the lock screen. A reset to factory settings fixes this, and I have done this a two times thus far. I tried an application on my PC called Kingo Root to root it, and it does not cause the device to act strangely and slowly, but I do not have access to su. Beyond this, I am unable to access Fastboot. Fastboot just says <Waiting for device> whenever I start my device after using the fastboot -i 0x1949 getvar product or any other Fastboot command. I believe I have installed the drivers properly, and the ADB works fine.
What other information should I provide? Are there any steps I could/should try?
Thanks!
Click to expand...
Click to collapse
I too tried to root I was able to get fast boot working but had to reapply my driver in settings. I have the LTE variant and thus need a working root solution. Does anyone know a method to achieve root without the slowness?
no root this sucks
I was able to root where the device is slow then use adb commands to get the device into fast mode from there you can follow the tutorial that helps you get a second boot loader.
Once you have root and the device is connected over adb then use the command adb shell then run reboot bootloader.
Can you please share your rooting instrcutions from the Amazon OS 8.5.1?
I'm on 8.5.1 and tried all methods of the rooting, but failed all.
Many thanks.
macman005 said:
I was able to root where the device is slow then use adb commands to get the device into fast mode from there you can follow the tutorial that helps you get a second boot loader.
Once you have root and the device is connected over adb then use the command adb shell then run reboot bootloader.
Click to expand...
Click to collapse
???
---------- Post added at 01:03 AM ---------- Previous post was at 12:11 AM ----------
Try this app keyrootmaster I just root my kindle 8.9 with it
taller238 said:
Can you please share your rooting instrcutions from the Amazon OS 8.5.1?
I'm on 8.5.1 and tried all methods of the rooting, but failed all.
Many thanks.
Click to expand...
Click to collapse
I used Root_with_Restore_by_Bin4ry_v36 with option 3. Once complete device is basically unusable but you can still connect over ADB and you do have root. I then followed http://forum.xda-developers.com/showthread.php?t=2277105 for installing a different boot loader. I didn't follow it exactly as I again opened an ADB shell then ran the commands as I was getting an error if I just ran them as is. If you open a shell you only run the command in "" without the quotes. Once complete you can then flash to cm11 or another ROM of your choosing.
macman005 said:
I used Root_with_Restore_by_Bin4ry_v36 with option 3. Once complete device is basically unusable but you can still connect over ADB and you do have root. I then followed http://forum.xda-developers.com/showthread.php?t=2277105 for installing a different boot loader. I didn't follow it exactly as I again opened an ADB shell then ran the commands as I was getting an error if I just ran them as is. If you open a shell you only run the command in "" without the quotes. Once complete you can then flash to cm11 or another ROM of your choosing.
Click to expand...
Click to collapse
This don't work no more I try already u got use the app keyrootmaster if u on 8.5.1 to Root it
Can you post a link to keyrootmaster? The above works if you want an alternative rom.
http://getandroidapp.org/applications/comics/905-key-root-master-mod-version-1-3-6.html
---------- Post added at 05:22 AM ---------- Previous post was at 05:22 AM ----------
This one
esema1o said:
http://getandroidapp.org/applications/comics/905-key-root-master-mod-version-1-3-6.html
---------- Post added at 05:22 AM ---------- Previous post was at 05:22 AM ----------
This one
Click to expand...
Click to collapse
Being a total Kindle newbie here... do you know of a tutorial on how to use key root mater for my Kindle 8.5.1 version? Or maybe you can tell me how I install the apk file?
Reading and reading without a very good explanation driving me crazy(er)
Thanks!
justanumber said:
Being a total Kindle newbie here... do you know of a tutorial on how to use key root mater for my Kindle 8.5.1 version? Or maybe you can tell me how I install the apk file?
Reading and reading without a very good explanation driving me crazy(er)
Thanks!
Click to expand...
Click to collapse
I had luck with a different method I outlined in this thread.
http://forum.xda-developers.com/kindle-fire-hd/8-9-inch-help/success-rooting-8-5-1-t2943620