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
Related
I have the old TWRP installed via KFU and now want to update it.
Can I just install it straight over the old one and if so how do I do it ?
I understand that it's not as simple as using KFU to do it.
Any advice appreciated.
Use fastboot if you can. Assuming you have FFF installed and know how to use fastboot:
fastboot flash recovery /path/to/twrp.img
...or you could use one of smirkis' scripts.
http://forum.xda-developers.com/showthread.php?p=22608974
Is there an advantage to the new TWRP? I'm currently at 2.0 and trying to flash AOKP and hung at the opening animation and wondering if it has to do with an old TWRP .
I have FFF but as fire as I know that just takes me into twrp.
How do I get into fastboot. I've previously done this through KFU I think.
All I need is a step by step of how to do the install.
I get that I put the twrp 2.1.1 file on my pc and point the fire at it by running the fastboot command but I'm really not sure how to get into fastboot.
wigsey, I couldn't figure this out either. I had switched from TWRP 2 to CWM. Messed around with ADB and Kindle Fire Utility and I was only able to get back to TWRP 2; then I followed soupmagnet's advice. Installed Root Browser, downloaded and installed the scriptfiles. BEFORE running the scripts, however, I moved the latest version of TWRP into the Files folder of the scripts; renamed the twrp2-blaze.img version that was in there to "old" out of habit; copied over the new version of TWRP and renamed that to "twrp2-blaze.img" and then ran the script. Rebooted and had the 2.1.1 come up.
I am sure that there is an easier way, but for whatever reason using ADB just didn't work for me and this did.
So basically use the soupmagnet method but replace his twrp file with the new one renamed to the same name.
When you renamed the old one did you move it or leave it there. Wouldn't it be easier to delete it ?
Is the based place to get the new file from the TWRP website by the way ?
wigsey said:
So basically use the soupmagnet method but replace his twrp file with the new one renamed to the same name.
When you renamed the old one did you move it or leave it there. Wouldn't it be easier to delete it ?
Is the based place to get the new file from the TWRP website by the way ?
Click to expand...
Click to collapse
If you can, you want to get into fastboot and flash it from there. You don't have to copy it over to your KF first, fastboot knows where your recovery partition is located, it will do some basic checks to see that it will fit on the partition, etc.
Code:
fastboot flash recovery twrp.img
If at all possible, do it this way.
Alternatively, you can put the image on your /sdcard partition (this is what pops up when you mount the Kindle Fire's USB mass storage device on your computer) and write it directly to the recovery partition.
From the terminal emulator app...
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p5
This is essentially identical to the way smirkis' script will do the job.
It's a pain to type this on a virtual keyboard, so you can also use adb like this...
Code:
adb shell dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p5
In both cases above, you must have the mass storage device unmounted from your computer so your KF can access the file.
If you need fastboot or adb help, you can find it in the 3rd post of this thread...
http://forum.xda-developers.com/showthread.php?t=1552547
It should be noted that the "dd" command is nothing to be trifled with. It's been nicknamed "data destroyer" for a reason.
Pay CLOSE attention and verify what you have typed is correct before entering.
kinfauns, I tried the fastboot method, having renamed the 2.1.1 IMG file and it did not work for me. Seemed to go along, but when I rebooted into recovery, I still had 2.0.
The scripting method is a kludge, granted, but in my case it was idiot-proof.
---------- Post added at 03:00 PM ---------- Previous post was at 02:58 PM ----------
wigsey said:
So basically use the soupmagnet method but replace his twrp file with the new one renamed to the same name.
When you renamed the old one did you move it or leave it there. Wouldn't it be easier to delete it ?
Is the based place to get the new file from the TWRP website by the way ?
Click to expand...
Click to collapse
Actually I renamed the old one ".old" in case I needed it later. After success I deleted it. And yes, the TWRP website seems to be the best place to get the latest version.
koop1955 said:
kinfauns, I tried the fastboot method, having renamed the 2.1.1 IMG file and it did not work for me. Seemed to go along, but when I rebooted into recovery, I still had 2.0.
The scripting method is a kludge, granted, but in my case it was idiot-proof.
Click to expand...
Click to collapse
This sounds like you used the wrong fastboot command. The old install directions for 2.0 had you "fastboot boot" the image and now you need to "fastboot flash recovery" for version 2.1.0 and beyond. Any chance you just mixed up the commands? If you were not successful with the "fastboot flash recovery" command, it would have told you so... otherwise, it almost certainly would have wrote it out to the recovery partition.
"Any chance you just mixed up the commands? "
Always a chance of that, but I am all sorted anyway. FFF 1.3 and TWRP 2.1.1
koop1955 said:
"Any chance you just mixed up the commands? "
Always a chance of that, but I am all sorted anyway. FFF 1.3 and TWRP 2.1.1
Click to expand...
Click to collapse
You're on a roll, may as well get the latest FFF while you're hot.
Hashcode's new FFF 1.4
Very nice...damn near brick-proof now.
Hi
I rooted my KF using kindle fire utility 0.9.5 -successfully.
After flashing gede ROM, KF is boot looping (there is a CM9 logo with the android guy flashing on the screen)---rebooting KF brings me back to the same screen
I have absolutely no access to the device. Kindle unbrick v.1--does not do anything, it gives: waiting for device
kindle fire utility gives: device offline
adb device gives: error: device not found
however, when i plug in the KF into my computer, under Device Manager--the KF is listed as "Galaxy" with a yellow triangle. No longer listed as kindle.
Please help! Thanks
Does this sound like it may apply to you?
http://forum.xda-developers.com/showthread.php?p=25400963
&
http://forum.xda-developers.com/showthread.php?p=20317299
soupmagnet said:
Does this sound like it may apply to you?
http://forum.xda-developers.com/showthread.php?p=25400963
&
http://forum.xda-developers.com/showthread.php?p=20317299
Click to expand...
Click to collapse
Thank you for your response. the KF is fully charged so power is not an issue. The biggest issue is I have no access to the device in order to do anything. Device cannot be recognized and it reads as a Galaxy in device manager
Oh, that problem...
OK, read these
Driver information:
http://forum.xda-developers.com/showthread.php?p=23747671
Hardware ID information and reply from gedemis w/fix:
http://forum.xda-developers.com/showthread.php?p=25444709
soupmagnet said:
Oh, that problem...
OK, read these
Driver information:
http://forum.xda-developers.com/showthread.php?p=23747671
Hardware ID information and reply from gedemis w/fix:
http://forum.xda-developers.com/showthread.php?p=25444709
Click to expand...
Click to collapse
Thanks soupmagnet. However still no progress. my device is still bootlooping.
How can I get into recovery while it is still bootlooping.
I am quite (100%) certain the issue you are describing is a dead battery. It is the only issue known that causes the boot logo to flash like that. Your battery most likely died while asleep as some roms don't sleep or shut down properly.
I'm willing to bet if you pay attention and follow the steps from the links I originally gave you, you'll be able to fix your device.
soupmagnet said:
I am quite (100%) certain the issue you are describing is a dead battery. It is the only issue known that causes the boot logo to flash like that. Your battery most likely died while asleep as some roms don't sleep or shut down properly.
I'm willing to bet if you pay attention and follow the steps from the links I originally gave you, you'll be able to fix your device.
Click to expand...
Click to collapse
Qem is saying that as soon as the ROM was flashed and went into boot mode, the kindle kept bootlooping the ROM intro over and over.
Turning the KF on and off does nothing as the KF is trying to boot into the ROM but never gets past the intro screen (blue-ish android cartoon, CM9 type intro).
Because of the bootlop, there is no way to get into recovery physically and when connected to the computer, the kindle is being shown as a galaxy unit with no drivers, probably due to the flashed ROM.
mrslax said:
Qem is saying that as soon as the ROM was flashed and went into boot mode, the kindle kept bootlooping the ROM intro over and over.
Turning the KF on and off does nothing as the KF is trying to boot into the ROM but never gets past the intro screen (blue-ish android cartoon, CM9 type intro).
Because of the bootlop, there is no way to get into recovery physically and when connected to the computer, the kindle is being shown as a galaxy unit with no drivers, probably due to the flashed ROM.
Click to expand...
Click to collapse
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?
soupmagnet said:
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?
Click to expand...
Click to collapse
Qem can't post links so I posted her response instead.
"Again, thanks for your response. Yes I have clockwork Mod.
At first the KF kept bootlooping to the KF intro screen followed by a small portion of the ROM intro.
After multiple resets the intro just continues forever.
Here is a link to what it looks like. Its been like this even after powering off and on.
http://www.youtube.com/watch?v=npx9HIbF5Po"
Any ideas for bootloop
soupmagnet said:
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?
Click to expand...
Click to collapse
Please do you have any ideas re:bootloop. I am stuck.
Qem said:
Please do you have any ideas re:bootloop. I am stuck.
Click to expand...
Click to collapse
Yes. I'll try to explain it in a way that you'll understand.
You have Clockwork Mod
You need TWRP
no way to mount TWRP
soupmagnet said:
Yes. I'll try to explain it in a way that you'll understand.
You have Clockwork Mod
You need TWRP
Click to expand...
Click to collapse
Thanks.
However did you see the you-tube link in chat #9?
I do not have any access to the device (in order to install TWRP) because no application (KF utility, Kindle unbrick, cmd prompt) can find the device: "ERROR: device not found".
The only place in which the device is found is in device manager but it lists the KF as "Galaxy".
May be I might be missing something...
You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.
soupmagnet said:
You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.
Click to expand...
Click to collapse
I am having the same issue.
The problem is we flashed CWM, then a CM9 rom. Now just runs the aminamtion.zip boot screen and does nothing. it is unable to get into fastboot or CWM. inorder to flash another rom to install TWRP
KF has internal sdcard... cant mount TWRP
soupmagnet said:
You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.
Click to expand...
Click to collapse
Thanks. I appreciate your help.
Pardon me I am desperate to get my KF in a working condition.
However the KF does not have an external SD card. Therefore to mount TWRP on the sdcard, I need access to the device. This access is what i dont have... The sdcard on the KF is internal and I cannot open any folders in the KF due to the bootloop
Qem said:
Thanks. I appreciate your help.
Pardon me I am desperate to get my KF in a working condition.
However the KF does not have an external SD card. Therefore to mount TWRP on the sdcard, I need access to the device. This access is what i dont have... The sdcard on the KF is internal and I cannot open any folders in the KF due to the bootloop
Click to expand...
Click to collapse
No, you're misunderstanding me.
If you want to install the TWRP from inside the rom (i.e. using gscript or smirkit), you have to access recovery (in your case, CWM) to mount your sdcard. It will mount to your computer as an external drive, like a thumb drive. While mounted, transfer a rom that will work with CWM from your computer to your sdcard, then flash it in recovery to have a working rom to install TWRP.
Otherwise, if you want to use the command line method to install TWRP...
fastboot flash recovery /path/to/twrp2.1.img
...but considering KFU says "offline", that is out of the question unless you can get your drivers working.
soupmagnet said:
No, you're misunderstanding me.
If you want to install the TWRP from inside the rom (i.e. using gscript or smirkit), you have to access recovery (in your case, CWM) to mount your sdcard. It will mount to your computer as an external drive, like a thumb drive. While mounted, transfer a rom that will work with CWM from your computer to your sdcard, then flash it in recovery to have a working rom to install TWRP.
Otherwise, if you want to use the command line method to install TWRP...
fastboot flash recovery /path/to/twrp2.1.img
...but considering KFU says "offline", that is out of the question unless you can get your drivers working.
Click to expand...
Click to collapse
So I was able to find drivers for the "Galaxy" (http://pastebin.com/nhbaaWMu) and installed it. This enabled KFU to recognize my device as "online".
However there are two issues (1) there is no access to the drive. it mounts like an external drive, but does not open/explore. like an external drive or USB would.
(2) when i try to go into recovery mode via KFU, KFU gets stuck.
When you say fastboot flash recovery /path/to/twrp2.1.img, does the "path/to/twrp2."1-- mean the actual file path to where TWRP is located on my computer or is the "path/to" part of the cmd line input
Qem said:
When you say fastboot flash recovery /path/to/twrp2.1.img, does the "path/to/twrp2."1-- mean the actual file path to where TWRP is located on my computer or is the "path/to" part of the cmd line input
Click to expand...
Click to collapse
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.
still boot looping affter fastboot+twrp2
soupmagnet said:
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.
Click to expand...
Click to collapse
Thank you for your help thus fat, I appreciate it. However I still have not fixed the issue...
I tried it (actual path to file), it still said "waiting for device".
after a while, I held held power button to manually reboot, still nothing.
I also uninstalled and re installed the drivers... nothing
using KFU to boot into normal mode still returns "system cannot find the drive specified."
at wits end...
Pardon the typo..
soupmagnet said:
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.
Click to expand...
Click to collapse
In prev post, I meant thanks for your help thus "far" and not "fat"
sorry for the typo
Hi everyone, I have two kindle fire, I messed with both of them.
I've root them the first one has the problem with the yellow triangle logo stucked. And the other one I've tried to reset it to the factory settings and everything was cool until I hit the TWRP utility and I think I erased everything.
I've see tons of posts regarding rooting and troubleshooting related to rooting and i'm pretty sick of rooting, I think that 3 months is sufficient time, please DON'T POST anything related to rooting.
I'm here asking if anyone knows how to flash all the data ofthe kindle from the pc and been able to install the factory software, firmware (I don't know) from scratch from my pc. Anyone, please?
The first one is probably stuck in fastboot. Try giving it a go with "fastboot oem idme bootmode 4000 && fastboot reboot".
For the second one, "I think I erased everything" is as descriptive as not wanting people to post about your procedure is helpful. What exactly is going on with it? For future reference: http://forum.xda-developers.com/showthread.php?t=1644970
You should also update both FFF and TWRP on both devices once they are working normally.
If i may suggest flashing modaco first after a good wipe everything except your sdcard I believe this will make a smoother transition if you desire to return to stock before returning to stock always do a good wioe to remove remnants of previous roms download the latest stock bin and rename it to update.zip do not place it in any folder just at the root of your sdcard flash in twrp this will also wipe out twrp and fff I really dont recommend doing this lots of people fail at doing the procedure correcty modaco is stock with only the market added try this approach first then you can retain fff and twrp for custom backups.
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
Click to expand...
Click to collapse
To restore back to full factory
1. Download Kindle Fire Software Update Version 6.3.1
2. Rename the file to update.zip
3. Get in to TWRP and mount USB drive
4. Copy update.zip to Kindle Fire
5. Unmount USB drive
6. Do factory reset, then wipe system cache, and dalvik cache
7. Flash the update.zip
8. Let it bootloop about 3 times or so...
If you want FFF and TWRP then flash Stock 6.3.1 Basic from TWRP. This has no root or gapps.
Dasanko said:
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
Click to expand...
Click to collapse
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
jRam90 said:
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
Click to expand...
Click to collapse
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Dasanko said:
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Click to expand...
Click to collapse
Both of the kindles, are damaged. I can't access them. I just can access one by USB.
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Dasanko said:
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Click to expand...
Click to collapse
Thanks a LOT, Dasanko !!!!
jRam90 said:
Thanks a LOT, Dasanko !!!!
Click to expand...
Click to collapse
Ok, So, I have the factory cable. How can I test its Ok?
I have another question, the kindle is pratically empty no system, no sdcard memory, probably corrupted ¿How do I use the factory cable, to format the Kindle and install the Stock ROM again?
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Dasanko said:
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Click to expand...
Click to collapse
Well, I'm at my job now. So I will try this at home, but the shell is not working since system/sh (shell) it's not in the Kindle. I was trying to boot it yesterday with "fastboot boot twrp.img" and nothing. I also tried: "fastboot getvar product" and nothing but I only used the console. Anyway, let's see what happens...
Quick question, I've read that the factory cable puts the Kindle straight into bootmode, ¿So the color of the power button, has something to do with it? ¿I mean how do I know the kindle has entered factory mode? ¿The orange light is an indicator? (With a standard USB Cable I only get the green light with the power button, with the factory cable I first get green light, then orange light)
I've also read that if I can see the Kindle fire logo, the bootloader is Ok. Hence my Kindle is OK, but I can't enter fastboot mode. ¿Can anyone confirm this?
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Dasanko said:
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Click to expand...
Click to collapse
OK, I've finally made myself a working factory cable. And in the device manger I can see the kindle listed as "Android phone" and in that root it says "Android ADB Interface". Look like drivers are not working. Where can I download them?
Those are the proper drivers for fastboot you should be able to use kfu to send twrp and fff to the device if that doesn't work you will need to fastboot flash them
All I get is < waiting for device>. Looks like the drivers are not installed.
Simply hold the power button down while connected when it says waiting then power it back on and it should send also try unplug replug when it says waiting
---------- Post added at 03:49 PM ---------- Previous post was at 03:44 PM ----------
If you would like some help I have some time before work but you must finish your thread for the benefit of others
So I was messing with my kindle and it was trying to upgrade it to jelly bean and i guess i missed one of the steps and bricked it. I was going through the process of unbricking but when i was trying to do extract the update.zip folder it would not allow me to because it could not mount the SD card. All i need to figure out how to do is get the SD slot mounted. I am slowly picking up on command prompt and still trying to figure out adb shell but that is all i need help with.
I can unbrick it if someone knows how i can get my kindle to mount back to my computer!
Any advice or step by step for it would be very helpful, Thanks guys
Could you be more specific as to how your Kindle is "bricked"?
soupmagnet said:
Could you be more specific as to how your Kindle is "bricked"?
Click to expand...
Click to collapse
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see
Forgive my redundancy but please describe the "boot loop". Does it just sit at the Kindle Fire logo? Does the Kindle Fire logo flash, or change brightness? Does it make it to the boot animation? Black screen?
soupmagnet said:
Forgive my redundancy but please describe the "boot loop". Does it just sit at the Kindle Fire logo? Does the Kindle Fire logo flash, or change brightness? Does it make it to the boot animation? Black screen?
Click to expand...
Click to collapse
It will go to the kindle fire logo and then it would go to a black screen. It makes no boot animation. It will change some brightness. The words kindle fire are in white and blue. It flashes where is needs to do the boot animation and then just goes to a black screen
dontgoback4cody said:
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see
Click to expand...
Click to collapse
The image shows a very low battery. The behavior you describe suggests a low battery. You're in a boot loop caused by no power.
Let it sit for several hours (better...over night).
Edit:...ie. let it sit with your charger attached.....
---------- Post added at 11:14 AM ---------- Previous post was at 10:46 AM ----------
dontgoback4cody said:
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see
Click to expand...
Click to collapse
It might be a good idea to consider installing TWRP rather than using CWM. CWM is known to have problems with some newer ROMs.
acii22 said:
The image shows a very low battery. The behavior you describe suggests a low battery. You're in a boot loop caused by no power.
Let it sit for several hours (better...over night).
Edit:...ie. let it sit with your charger attached.....
---------- Post added at 11:14 AM ---------- Previous post was at 10:46 AM ----------
It might be a good idea to consider installing TWRP rather than using CWM. CWM is known to have problems with some newer ROMs.
Click to expand...
Click to collapse
I have tried to install it from KFU but it is always has a problem doing so. I let it charge over night and it is still doing the same thing. Here is what is says when i try to install twrp
Replace the TWRP.img that comes with KFU, with the ACTUAL one from the TWRP website.
soupmagnet said:
Replace the TWRP.img that comes with KFU, with the ACTUAL one from the TWRP website.
Click to expand...
Click to collapse
Ok i did that but it still will not let me connect the kindle to the computer it keeps giving me sdcard errors. any idea how to fix the sd card issue?
Hey were u able to fix it??
Had the same problem with mine when I used TWRP to format my SD card..but was able to solve it..
What I did was a very simple thing..got the kindle recognised as a drive..used windows partition manager to format it
It worked.. I tx the stock and installed it
Try it and let me know
Sent from my MB526 using Tapatalk 2
I had the same problem before and only had to reboot the kindle.
Nothing is working. i have given up all hope. Like this is crazy. It is screwed up for good. I cant get it to mount. If anyone wants to take a shot at it just shoot me a pm with an address and we can discuss something about trying to fix it or what the hell i did to it. Its crazy! and really messed up.
dontgoback4cody said:
Nothing is working. i have given up all hope. Like this is crazy. It is screwed up for good. I cant get it to mount. If anyone wants to take a shot at it just shoot me a pm with an address and we can discuss something about trying to fix it or what the hell i did to it. Its crazy! and really messed up.
Click to expand...
Click to collapse
I have an Idea. If you have fastboot working on your computer. You could try flashing a rom from your computer by typing
fastboot -w(wipes device)
fastboot update <path to rom> (flashes rom)
If it works, you can then fix the sdcard easier with adb/shell/partition manager. Its worth a shot.
I also found this on a website
ROM update without SDcard
If you don't have an sd card, or your slot is broken you can try this trick, but you will need a custom recovery like Clockwork.
Boot up your phone to recovery. And move your rom file to the adb directory, and start a command line ( cmd )
adb shell
mount data
adb push D:\custom_rom.zip /data/
Wait until the push finised, and restart your device to recovery again with "adb reboot-bootloader"
mount data
mount /data /sdcard ( mount the data folder into your sdcard folder, so your recovery will think that you have an sdcard installed )
Locate the ROM .Zip file you wish to flash.
Confirm the flash by following the on-screen instructions (ie: pressing the trackball, pressing the call button, etc.)
If no errors arise during the flashing process then the ROM flash was successful, Reboot the device.
With some root file explorer, remove the rom file if you don't need it anymore, to free up space.
Or use adb to remove the custom recovery
adb shell rm data/custom_rom.zip
I will give it a shot. Only thing is i dont think there is even any software on here. when i try to get it into fastboot mode here is what it says.
Then you need a factory cable to get into fastboot.
dontgoback4cody said:
I will give it a shot. Only thing is i dont think there is even any software on here. when i try to get it into fastboot mode here is what it says.
Click to expand...
Click to collapse
Hey i had the same exact problem and i had posted what i did to recover it.. did you try..
I know it sounds too simple.. but it worked for me
sometimes its the way you have formatted ur sd card
kishorev said:
Hey i had the same exact problem and i had posted what i did to recover it.. did you try..
I know it sounds too simple.. but it worked for me
sometimes its the way you have formatted ur sd card
Click to expand...
Click to collapse
When you see the error message:
Code:
- exec '/system/bin/sh' failed: No such file or directory (2)
It means you don't have access to the shell in order to switch bootmodes and access recovery, which is needed to fix this type of problem. The only way to change bootmodes without access to the shell, is in fastboot. Unfortunately, you need access to the shell to change the bootmode to fastboot as well...catch-22.
For this, you need a factory cable. The factory cable will tell the device to boot into fastboot without the need for a shell. Even with a factory cable, and access to recovery, you'll still likely need to either reformat, or repartition your sdcard in order to get it to mount.
soupmagnet said:
When you see the error message:
Code:
- exec '/system/bin/sh' failed: No such file or directory (2)
It means you don't have access to the shell in order to switch bootmodes and access recovery, which is needed to fix this type of problem. The only way to change bootmodes without access to the shell, is in fastboot. Unfortunately, you need access to the shell to change the bootmode to fastboot as well...catch-22.
For this, you need a factory cable. The factory cable will tell the device to boot into fastboot without the need for a shell. Even with a factory cable, and access to recovery, you'll still likely need to either reformat, or repartition your sdcard in order to get it to mount.
Click to expand...
Click to collapse
You are right..
But i too was had the same msg when i was trying to fastboot it.. but then it worked.. I had formatted it and then tx the stock rom and flashed it..
Probably i missing something here..
Anyways thnx
Can't mount SD card on kindle fire
I was in a similar situation and after reading the various forums i came across this action "hold down the power button until the kindle goes off and continue to hold for about 30 seconds I believe this resets the kindle and then tick debugging and mount usb storage the sdcard will open on your pc" and then you can go from there. Worked for me so good luck.
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