Develop Bugs

Unroot

rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
I have followed this guide to unroot my kindle. Is twrp still installed? and is there any trace that my kindle has been rooted previously?
I would like to send my kindle to amazon for screen defect, and if they find that my kindle has been previously rooted I will lose my warranty?
can you guys please help.

whoqwerty said:
rootkindlefire.com/kindle-fire-unroot/how-to-unrootunbrick-rooted-kindle-fire/
I have followed this guide to unroot my kindle. Is twrp still installed? and is there any trace that my kindle has been rooted previously?
I would like to send my kindle to amazon for screen defect, and if they find that my kindle has been previously rooted I will lose my warranty?
can you guys please help.
Click to expand...
Click to collapse
if you don't get the yellow triangle from fff at startup i would think twrp is'nt istalled eighter
just watched the guide - you should be good to go - it's like out of the box after this

Do one of the following...
Method 1
1) Download the stock update-kindle-6.2.2_D01E_3205220.bin from Amazon
2) Boot into TWRP by pressing the power button at the FFF logo.
3) adb push the update to the sdcard "adb push update-kindle-6.2.2_D01E_3205220.bin /sdcard/update.zip"
4) Tap "Install", select the update.zip, and tap "Flash".
Method 2
1) Download the stock update-kindle-6.2.2_D01E_3205220.bin from Amazon
2) adb push the update to the kindleupdates folder in the sdcard "adb push update-kindle-6.2.2_D01E_3205220.bin /sdcard/kindleupdates/"
3) Reboot the device
4) Go to "Device" in the Settings menu.
5) Tap on "Update your kindle"
Both of those methods will remove FFF, TWRP, and root.

lmntone said:
Do one of the following...
Method 1
1) Download the stock update-kindle-6.2.2_D01E_3205220.bin from Amazon
2) Boot into TWRP by pressing the power button at the FFF logo.
3) adb push the update to the sdcard "adb push update-kindle-6.2.2_D01E_3205220.bin /sdcard/update.zip"
4) Tap "Install", select the update.zip, and tap "Flash".
Method 2
1) Download the stock update-kindle-6.2.2_D01E_3205220.bin from Amazon
2) adb push the update to the kindleupdates folder in the sdcard "adb push update-kindle-6.2.2_D01E_3205220.bin /sdcard/kindleupdates/"
3) Reboot the device
4) Go to "Device" in the Settings menu.
5) Tap on "Update your kindle"
Both of those methods will remove FFF, TWRP, and root.
Click to expand...
Click to collapse
Do I necessary need to do the "adb push" ? Can I just zip it and put it in sdcard (for method 1), or put it in sdcard/kindleupdates/ (for method 2) ?

I wanted to get mine back to stock because I use amazon prime streaming a lot.
I downloaded the latest update from Amazon's site, renamed it update.zip, dropped onto the internal storage of the device and used TWRP to flash it.
After it all done, the Kindle was 100% stock and had no traces of root.

just a question
I have a friend that i helped put cm7 on thier kindle fire, but they are now complaining about the fff logo. Is there anyway to just uninstall fff and twrp? I know its best to leave them on the kindle, but he is quite adamant about this. Perhaps maybe a way to suppress the fff logo?

a1morrison said:
I have a friend that i helped put cm7 on thier kindle fire, but they are now complaining about the fff logo. Is there anyway to just uninstall fff and twrp? I know its best to leave them on the kindle, but he is quite adamant about this. Perhaps maybe a way to suppress the fff logo?
Click to expand...
Click to collapse
You can't "uninstall" FFF because then your device won't boot without the bootloader, but the later versions (v1.3 and v1.4) have different logos that your friend might find less upsetting. There's no way to suppress the logo, but you can build one yourself without a bootlogo if you are so inclined. Back to your original question... you can reinstall the stock bootloader with the original "kindle fire" logo. I get the sense that you understand the consequences of such a move, so I won't reiterate. TWRP is something that you don't need to "see" unless you need to use it, so I'm not sure why they would gripe about it.
Either way, you can download Amazon's Kindle Fire software update (google it), change the .bin suffix to .zip, extract the contents and you'll find both of them (recovery.img and u-boot.bin) there that you can flash with fastboot. Alternatively, you can use the smirkit scripts and flash them while booted into CM7.

{q} How to install TWRP 2.1.1 over TWRP 2

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.

Noober help please..rooting using Utility v0.9.6

Rooting kf for the first time using “Kindle Fire Utility v0.9.6”.
In the instruction from NatMil it says:
“***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)
http://forum.xda-developers.com/showthread.php?t=1569298
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)
http://uploading.com/files/2f495fa7/Superuser.apk/”
Here’s my total noob question:
When do I sideload the superuser.apk. Once my kf boots to TWRP???
Thanks,
Marty

http://forum.xda-developers.com/showthread.php?p=25730650

[Q] Kindle Fire Utility - TWRP

Folks,
I am trying to root my first gen Kindle Fire using the Kindle Fire Utility. One of the Options "5" is to install the latest TWRP 2.3.1.1. I have read about Wipe problems with this. How can I ensure that the KFU will install the older TWRP 2.2.1.1. Is it easily done by just copying the TWRP 2.2.1.1 file to the recovery folder within the KFU folder?
Thanks!

KFU actually tells you which version it`s installing last time I checked it was still downloading the older version. You can check it by dry running the program without the kindle plugged in read what it says in the terminal.

Josepho1997 said:
Actually, last time I checked KFU couldn't download TWRP. But maybe that's fixed.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Thanks for the replies folks .. I copied TWRP 2.2.2.1 in the "recovery" folder and the KFU checked for existing TWRP in the recovery folder and it installed it.
Thanks!

How to get TWRP?

I rooted my Kindle Fire two weeks ago and updated it to jellybean 4.2 using the ROM developed by hashcode. Now after the update, I feel like I bricked my device. Because first of all TWRP (blue Kindle fire logo with boot options below) is not loading in startup but regular Kindle fire logo is seen. And I can't install TWRP using Kindle Fire Utility because my device is now a different ROM and KFU can't detect my Kindle. And I'm not at all satisfied with the battery life of Kindle Fire on JB 4.2 and it gets hot like red-hot-iron even just when I watch a video. Somebody please help me to at least to get TWRP on my kindle so I could just set it to default ROM or any other. Or please tell me a way to get out of this condition.
Sent from my Amazon Kindle Fire using xda app-developers app

srvrpc said:
I rooted my Kindle Fire two weeks ago and updated it to jellybean 4.2 using the ROM developed by hashcode. Now after the update, I feel like I bricked my device. Because first of all TWRP (blue Kindle fire logo with boot options below) is not loading in startup but regular Kindle fire logo is seen. And I can't install TWRP using Kindle Fire Utility because my device is now a different ROM and KFU can't detect my Kindle. And I'm not at all satisfied with the battery life of Kindle Fire on JB 4.2 and it gets hot like red-hot-iron even just when I watch a video. Somebody please help me to at least to get TWRP on my kindle so I could just set it to default ROM or any other. Or please tell me a way to get out of this condition.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
The blue & white Kindle Fire logo with boot options is FireFireFire, not TWRP. You may or may not have TWRP installed but without access to it you'll probably never know.
If you have root permissions, the easiest and most straight forward way of getting FFF installed is to do so through terminal emulator on your device (install it if you have to).
1) Download FFF1.4.zip onto your device and extract it. That should put the resulting folder in /sdcard/extracted. There, find the uboot.bin file and move it directly to the root of your sdcard (i think it's named something like "firefirefire1.4u-boot.bin"...rename it to "u-boot.bin").
2) Then open terminal emulator and enter the following commands:
Code:
su
dd if=/sdcard/uboot.bin of=/dev/block/mmcblk0p[B]2[/B][COLOR=Red]<---This is a [U]TWO[/U][/COLOR]
That will overwrite your bootloader partition with the new u-boot.bin. Just reboot and it should work. The problem with that is, if you get a corrupt download, it may hard-brick your device. Be sure to do an md5 check.
A safer way to do this is through TWRP. You can install and access TWRP relatively in the same manner with terminal emulator.
1) Download the TWRP.img and the FFF1.4.zip (don't extract it) onto your device and place them on the root of your sdcard. (rename TWRP to "twrp.img" to make things easier)
2) In terminal emulator, enter the following commands:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p[B]5[/B][COLOR=Red]<---This is a [U]FIVE[/U], not a TWO...pay attention[/COLOR]
idme bootmode 5001
reboot
3) In TWRP, flash the FFF1.4.zip, but don't wipe anything. This method will automatically check the md5 of FFF before installing it and reduce the possibility of accidentally bricking the device.
Reboot and all will be well.

soupmagnet said:
The blue & white Kindle Fire logo with boot options is FireFireFire, not TWRP. You may or may not have TWRP installed but without access to it you'll probably never know.
If you have root permissions, the easiest and most straight forward way of getting FFF installed is to do so through terminal emulator on your device (install it if you have to).
1) Download FFF1.4.zip onto your device and extract it. That should put the resulting folder in /sdcard/extracted. There, find the uboot.bin file and move it directly to the root of your sdcard (i think it's named something like "firefirefire1.4u-boot.bin"...rename it to "u-boot.bin").
2) Then open terminal emulator and enter the following commands:
Code:
su
dd if=/sdcard/uboot.bin of=/dev/block/mmcblk0p[B]2[/B][COLOR=Red]<---This is a [U]TWO[/U][/COLOR]
That will overwrite your bootloader partition with the new u-boot.bin. Just reboot and it should work. The problem with that is, if you get a corrupt download, it may hard-brick your device. Be sure to do an md5 check.
A safer way to do this is through TWRP. You can install and access TWRP relatively in the same manner with terminal emulator.
1) Download the TWRP.img and the FFF1.4.zip (don't extract it) onto your device and place them on the root of your sdcard. (rename TWRP to "twrp.img" to make things easier)
2) In terminal emulator, enter the following commands:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p[B]5[/B][COLOR=Red]<---This is a [U]FIVE[/U], not a TWO...pay attention[/COLOR]
idme bootmode 5001
reboot
3) In TWRP, flash the FFF1.4.zip, but don't wipe anything. This method will automatically check the md5 of FFF before installing it and reduce the possibility of accidentally bricking the device.
Reboot and all will be well.
Click to expand...
Click to collapse
Thanks for the help! But I have a doubt, because my Kindle is on Jelly Bean, it is on MTP mode when connected to computer. Will it be a problem? And where do i get a non-corrupted FFF1.4.zip ?

srvrpc said:
Thanks for the help! But I have a doubt, because my Kindle is on Jelly Bean, it is on MTP mode when connected to computer. Will it be a problem? And where do i get a non-corrupted FFF1.4.zip ?
Click to expand...
Click to collapse
Terminal emulator is an app that is run on the device, not the computer, so it doesn't matter what settings you have enabled or whether your drivers are working properly. And there is one main source for FFF1.4. Corruption, if it happens, usually happens when downloading so an md5 check needs to be done before flashing the file you downloaded to your bootloader partition.