Database Users

[Q] can't boot into os after ota 6.3 update

My kindle fire is rooted by using BurritoRoot3 method,with firefirefire bootloader and CWR recovery installed.
this morning,my kindle fire automatically rebooted,then stuck at CWR recovery interface,i realized it may related with a new ota update,so i shutdown kindle fire and power on,it reboot into recovery as long as it going into the os.
now i can boot into the recovery but cannot into the os,what should i do ?

puppyguy said:
My kindle fire is rooted by using BurritoRoot3 method,with firefirefire bootloader and CWR recovery installed.
this morning,my kindle fire automatically rebooted,then stuck at CWR recovery interface,i realized it may related with a new ota update,so i shutdown kindle fire and power on,it reboot into recovery as long as it going into the os.
now i can boot into the recovery but cannot into the os,what should i do ?
Click to expand...
Click to collapse
I think I read somewhere that CWM stops the ota from installing so it starts bootlooping. Twrp would let the update go through but if it did, you would lose root anyway. Maybe using CWm you could install the 6.3 pre-rooted stock rom

I was having the same issue with twrp and this upgrade. To get out of the bootloop I used adb:
adb shell
idme bootmode 4000
reboot
It Didn't install the update but got me the kindle back. I then used eldarerathis rooted 6.3 image:
http://forum.xda-developers.com/showthread.php?t=1569298:p

My kindle did the same thing it's because the OTA update doesn't work right with TWRP. Take a look at my thread. Basically you need to download the update, rename it update.zip put it in the root directory of the kindle, and then power up the kindle it will go into TWRP and click on the update/flash function (not sure what it's called off the top of my head right now) and let it do it's thing and you will be back to normal.
Alternatively if you don't feel like re-rooting your device, download this version and update it using the instructions above.

Thank you! This worked perfectly.
Laquox said:
My kindle did the same thing it's because the OTA update doesn't work right with TWRP. Take a look at my thread. Basically you need to download the update, rename it update.zip put it in the root directory of the kindle, and then power up the kindle it will go into TWRP and click on the update/flash function (not sure what it's called off the top of my head right now) and let it do it's thing and you will be back to normal.
Alternatively if you don't feel like re-rooting your device, download this version and update it using the instructions above.
Click to expand...
Click to collapse

Laquox said:
My kindle did the same thing it's because the OTA update doesn't work right with TWRP. Take a look at my thread. Basically you need to download the update, rename it update.zip put it in the root directory of the kindle, and then power up the kindle it will go into TWRP and click on the update/flash function (not sure what it's called off the top of my head right now) and let it do it's thing and you will be back to normal.
Alternatively if you don't feel like re-rooting your device, download this version and update it using the instructions above.
Click to expand...
Click to collapse
Do you have to wipe. Any "cache"? Or Factory reset...Or do you only do that if you are going to a different ROM. ?
Sent from my Kindle Fire using Tapatalk

[Q] Nexus 7 (4.1.2) can't root

Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message

IAmNice said:
usb debugging on? Have you checked that?
Click to expand...
Click to collapse
Hi. Yes mam (usb debugging on) have a look to the attachment.
Toolkit me boot into fastboot then reboot then for something to fastboot loaded and back to android and trying to upload the files but nothing superuser is not recorded because of (read-only file system).
have a look on the attachment is there to see everything ...

yep same issue here - problem with the forum regs is unless you have enough posts you can't actually address the issue to the appropriate person can you? Anyway, able to unlock but then is unable to root and rest due to a permissions problem. have tried as administrator but of coure this doesn't make any difference.

NexusTropers said:
Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message
Click to expand...
Click to collapse
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.

try:
http://forum.xda-developers.com/showthread.php?t=1796109

comminus said:
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.
Click to expand...
Click to collapse
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.

bazabaza said:
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.
Click to expand...
Click to collapse
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.

comminus said:
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.
Click to expand...
Click to collapse
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.

NexusTropers said:
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
Click to expand...
Click to collapse
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
NexusTropers said:
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.
Click to expand...
Click to collapse
I'm not really sure what you're trying to say...

I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.

comminus said:
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
I'm not really sure what you're trying to say...
Click to expand...
Click to collapse
1. THX u i try it.
2. AH sorry translator make crazy text.
homerbrew said:
I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.
Click to expand...
Click to collapse
Oki THX u i try this tool...

I'm also having this same problem but here's my story:
Using the Nexus 1.5.4 Toolkit, I Unrooted + Flashed jzo54k, success. I locked OEM, success. I unlocked again, success. Then I ran the root process again, and it keeps freezing at the android recovery screen. Following the prompt in the toolkit, I walked away for a few hours hoping time would resolve the issue.
If you're wondering why I unlocked + rooted, and decided to unroot, lock, unlock, and root again, its because I'm super-noob to anything android related after version 1.5, I wanted to learn the processes after I found out I was having troubles with certian things after my Nexus 7 updated from 4.1 to 4.1.2

I am having the same issue as you. 4.1.2 is not rooting for me. I can't install CWM or TWRP because it needs to rename recovery files, and to do that you need to be rooted. If I boot in recovery I always get stock

Having the same issue with a stock 4.1.2. I can unlock no problem but I cannot get it rooted. Everything appears to have worked, but it is not rooted. If I revert back to 4.1.1 I can unlock, root, etc. without issue. I was able to root 4.1.1 and use the root keeper app to then update to 4.1.2 and I was rooted still. However, it would not let me install CWM or anything. ROM Manager says it was installed, but booting to recovery always too me to stock.
Any ideas?

Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app

MetalMadness said:
Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I used Nexus Root Toolkit v1.5.4 and selected the "Flash Stock + Unroot" option. When prompted I choose the default 4.1.1 option and away it went.

To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.

hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!

hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Indy1204 said:
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!
Click to expand...
Click to collapse
Thanks. I did this earlier and it didnt work, but I checked boot instead of flash
FLASH THE OLDER BOOTLOADER DON'T BOOT IT!!!

[Q] Booting into recovery shows "no command"

Hi there,
yesterday succesfully rooted my device using the insecure boot image.
Today booted and also flashed the new CWM recovery image but now, when booting into recovery only get an android logo and the text "no command" ?
Any ideas ? Flashed back to original recovery image but no change either ?
Root remains though and working fine.
Thanks

CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app

n7of9 said:
CMW can't be flashed yet... read the official CMW thread in the N4 Original Development forum for help
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Not true read here again :
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
Click to expand...
Click to collapse

has anyone reported it working?
Sent from my Nexus 7 using xda app-developers app

It seems tonight clockwork will release a new version with bugfixes which should make recovery working when flashed also.
Sent from my Nexus 4 using xda app-developers app

New clockworkmod recovery 6.0.1.8 had been released and I can confirm myself that it is working perfectly and stays when flashed !
You can download it here and follow the instructions as written here.
Good luck !

excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)

n7of9 said:
excellent, i was waiting for someone to confirm before flashing it myself
(looks like this thread is just a party for the two of us, wooohooo, let's find the hidden alcohol)
Click to expand...
Click to collapse
Meanwhile a newer 6.0.1.9 is released as well, which will hopefully also fix the backup being in the wrong location and not usable

CWM is fixed. Read this thread: http://forum.xda-developers.com/showthread.php?t=1995440

6.0.1.9 is the one i flashed and I'm still looking for my backup :s
n7'd from my n7

Disregard this post! It was meant for LBE which is a Virus or acts like one (Newest version that was translated)

I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?

k3nav7 said:
I'm having the "no command" message as well. I've flashed CWM 6.0.2.3 no-touch (following this guide), and it doesn't seem to be sticking. It'll work the first time, but then revert to the "no command" screen. I've also tried flashing the stock recovery, and then I receive the same message. I have an unlocked bootloader, and I managed root via the same guide. Anybody have any ideas?
Click to expand...
Click to collapse
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD

El Daddy said:
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.

k3nav7 said:
Perfect! Thank you! I had just previously downloaded 4.2.1, and so renaming recovery-from-boot.p did the trick. I had to remount my /system as read/write (used Total Commander, and it worked like a charm.
Click to expand...
Click to collapse
No problem! Glad to help!
Sent from my Nexus 7 using Tapatalk HD

No Command recovery problem
Hello im using a Canvas Magnus A117 its an amazing phone i rooted it but wanted to install chainfire 3D on it but it didnt work and now my phone is bricked. I tried flashing a custom rom but in recovery when i click on apply update from sdcard it says No command. with a dead android and a red triangle with !. So i cant use any feature in the Recovery mode and my phone is bricked. What do i do?

KINDLE FIRE HD stuck on TWRP v2.6.0.0 and recogniced in adb mode on pc

Hi, I am very new and I really need some help I was trying to install a custom rom but something went wrong.
Waht I did was.
I first rooted my device,
then I installed the second bootloader TWRP
And I forgot the wifi on, so thw kindle fire HD updated itself and eliminate the super user app.
So I restored the kindle fire hd to ist default in the restore option in the main manu.
then I root it again,
and try to instal the second boot loader again,
but after I installed the second boot loader it never boots up into the kindle fire hd system,
what happends is, in turns on, appears the kinfle fire letter in orange, the aperars kinfle fire letters is blue, then kinfle fire letters in orange again, whit a animation, that use to appear when is about lo load the system, then it reboots itself and repeate the entire process but this time goes into the TWRP second boot loader.
I think I could fix it by just using the backuo files I made o I coul install the custom room I want from there, but the problem is that I cannot load any file to the kindle fire hd because when I connect it the pc it shows as ADB device. Please help me out with this. I would like to you help to restore it to stock or tell how can I transfer files to my kindle fire hd when is in TWRP mode.
I already tried the mount option on the TWRP but the pc does not recognized it as a portabla device where I can store files.
:crying::crying::crying::crying:

I think this is what happens when flash the old freedom boot image on the latest updates, not positive though. Anyways what kind of backups did you make, like a nandroid backup from twrp that u moved to Ur PC, or a backup as described in the fire flash tutorial made using adb? If its the adb method its really simple, you just boot into twrp and hit restart and then hit boot loader, it will go into fastboot where you can flash those images. Otherwise I suggest just downloading the latest prerooted amazon ROM in the android development section and trying to use the side load feature. I'll explain more after you post back.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

It happened to me this weekend, i messed up with my kindle, the solution was to use Kindle Fire HD and 2 First Aide Software http://forum.xda-developers.com/showthread.php?t=2096888
Hope it will help you
Nb: if the driver are not working use the one included in this post Qemu automated root http://forum.xda-developers.com/showthread.php?t=1893838

I also have the exact problem I went into fastboot mode but I don't know how to flash images in fastboot mode . I also tried to sideload the cm10 rom but it fails please help me I cannot figure out what to do .
---------- Post added at 02:59 AM ---------- Previous post was at 02:54 AM ----------
abbashaider said:
I also have the exact problem I went into fastboot mode but I don't know how to flash images in fastboot mode . I also tried to sideload the cm10 rom but it fails please help me I cannot figure out what to do .
Click to expand...
Click to collapse
stunts513 said:
I think this is what happens when flash the old freedom boot image on the latest updates, not positive though. Anyways what kind of backups did you make, like a nandroid backup from twrp that u moved to Ur PC, or a backup as described in the fire flash tutorial made using adb? If its the adb method its really simple, you just boot into twrp and hit restart and then hit boot loader, it will go into fastboot where you can flash those images. Otherwise I suggest just downloading the latest prerooted amazon ROM in the android development section and trying to use the side load feature. I'll explain more after you post back.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I also have the exact problem I went into fastboot mode but I don't know how to flash images in fastboot mode . I also tried to sideload the cm10 rom but it fails please help me I cannot figure out what to do .

So can you get into twrp or you mean you only have fastboot access? If you only have fastboot access you just need to make sure that you have installed the driver for the device (use the one in my signature if you haven't) and just use kindle fire first aid to restore the system.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

similar trouble - stuck with blue logo
I hope that this is the right thread for my problem. I've also tried to install a custom ROM on my KFHD 7'' - I did it using this guide: http://forum.xda-developers.com/showthread.php?t=2271909
I'm able to get into TWRP, wiped and I flashed the latest CM 10.2 from hashcode + the gapps but when I try to reboot the Kindle (after wiping again) it goes into orange logo, which changes to blue logo and stays there. I've waited for a long time and nothing changes - tried to advanced wipe all the stuff from my tablet and flash again, but I always end up on the blue logo. Also does not matter if I only flash the CM 10.2 alone without gapps.
Does anyone have any idea how I can progress from here? I should be able to restore my backups via Factory Cable - but this is not what I would like to do.
Thanks in Advance!
Gildoniel

So did you factory reset when doing this? And are you sure you grabbed the version of the ROM for your kindle?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
So did you factory reset when doing this? And are you sure you grabbed the version of the ROM for your kindle?
Click to expand...
Click to collapse
I did a factory reset, yes. And I took the ROMs from Hashcode for version Kindle Fire HD 7'' (my tablet) I managed to successfully flash CM 11 now -> I checked zip verification when installing the ROM, this seems to have helped. It is booting after a few seconds now.
Did not realize, that the zip verification was important (this was the only difference afaik) and now it seems to work smoothly.
All in all I am still a bit puzzled - but at least my tablet is up and running again.

I reckon the problem was caused by using the wrong boot partition image.
So as your KFHD had updated to v7.4.6 you would need to flash the
kfhd7-freedom-boot-7.4.6.img instead of the kfhd7-freedom-boot-7.2.3.img
Using the instructions from Hashcode's thread on installing a second bootloader and TWRP
Here: http://forum.xda-developers.com/showthread.php?t=2128848
I had the same problem and solved it by flashing the matching the correct Boot Image. I had Kindle v7.4.6 installed and used 7.2.3 Boot Image
Hope this helps,
Phill
Sent from my Amazon Kindle Fire HD using XDA Premium HD app

Same Problem, can't fix
Hi,
could you please let me know how did you flashed and replaced boot image...?
I have same problem and I can't do anything...
pls help me...
Thank you

shibli_xda said:
Hi,
could you please let me know how did you flashed and replaced boot image...?
I have same problem and I can't do anything...
pls help me...
Thank you
Click to expand...
Click to collapse
hurrah... I've fixed this problem in fastboot mood with my regular usb cable by the code below in cmd:
fastboot -i 0x1949 flash boot kfhd7-freedom-boot-7.4.6.img
special thanks to hashcode for this tutorial:
http://forum.xda-developers.com/showthread.php?t=2128848

firmware 6.3.3 -=Post your rooting progress here=-

All attempts that I have made to root this Kindle Fire on 6.3.3 have failed. KFU fails. Towelroot fails. Nothin.

Ok so I was at least able to use a factory cable to put the kindle into fastboot mode. After that I was able to flash FFF and TWRP and then flash a stock 6.3.2 Rom which is rootable.
Also you can install custom rom from this point. Not exactly succeeding and rooting stock 6.3.3 but its a start.

Kafluke said:
Ok so I was at least able to use a factory cable to put the kindle into fastboot mode. After that I was able to flash FFF and TWRP and then flash a stock 6.3.2 Rom which is rootable.
Also you can install custom rom from this point. Not exactly succeeding and rooting stock 4.3.3 but its a start.
Click to expand...
Click to collapse
Please post steps in flashing firmware 6.3.2. I'm not sure if I'll be able to go back though, because I reset to factory settings before I realized that the firmware had updated.

Kafluke said:
Ok so I was at least able to use a factory cable to put the kindle into fastboot mode. After that I was able to flash FFF and TWRP and then flash a stock 6.3.2 Rom which is rootable.
Also you can install custom rom from this point. Not exactly succeeding and rooting stock 4.3.3 but its a start.
Click to expand...
Click to collapse
So how are you preventing it from taking another OTA of 6.3.3?

has anyone figured out the root for kindle fire on 6.3.3

jblindy said:
Please post steps in flashing firmware 6.3.2. I'm not sure if I'll be able to go back though, because I reset to factory settings before I realized that the firmware had updated.
Click to expand...
Click to collapse
Here's what I did:
1. Download stock firmware 6.3.2 (latest KFU will get it for you)
2. Copy stock firmware to internal storage on Kindle Fire (boot up Kindle Fire and plug into your computer)
3. Download TWRP 2.2.2.1 from here. (thanks sd_shadow).
4. Download latest FFF using KFU
5. Put TWRP and FFF into a folder on your computer that contains fastboot.exe
6. Make a factory cable (google "make Motorola factory usb cable") or you can buy a premade one or an adapter. Here's an example.
7. Turn off your Kindle fire and unplug it from your computer.
8. Plug one end or your factory cable into your computer.
9. Open a windows command prompt from the folder with fastboot.exe in it.
10. While the Kindle Fire is turned off, plug in the other end of your factory cable into the Kindle fire. This should throw the KF into fastboot mode.
If you have created the factory cable correctly you should see the red Kindle screen but it should stay there and you should get a new driver install notification in Windows. Install the driver for the Kindle Fire bootloader.
11. From your Windows command prompt run these commands (substituting the names for whatever your TWRP and FFF files are called)
Code:
fastboot -i 0x1949 flash recovery twrp.img
fastboot -i 0x1949 flash bootloader fff.bin
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Now you should see the FireFireFire blue screen and you can push the power button to boot into TWRP. From TWRP you can wipe everything and install the 6.3.2 file you placed on the Kindle Fire earlier (if you want to flash a KitKat ROM like CM11 or others then you must re flash recovery with latest TWRP from here). After you are using 6.3.2 you can run latest KFU and it will work just fine.
So how are you preventing it from taking another OTA of 6.3.3?
Click to expand...
Click to collapse
I don't know how to prevent it. Maybe its best to just flash CM11 on it.

Cool.....thanks!

Kafluke said:
From TWRP you can wipe everything and install the 6.3.2 file you placed on the Kindle Fire earlier.
Click to expand...
Click to collapse
Unless newest Twrp is different, only Twrp 2.2.2.1 or lower can install stock kindle firmware. Other TWRP versions will bootloop the Kindle Fire, and Twrp will need to be flashed in bootloader

sd_shadow said:
Unless newest Twrp is different, only Twrp 2.2.2.1 or lower can install stock kindle firmware. Other TWRP versions will bootloop the Kindle Fire, and Twrp will need to be flashed in bootloader
Click to expand...
Click to collapse
Correct or cannibal open touch recovery but it won`t flash Kit Kat.

sd_shadow said:
Unless newest Twrp is different, only Twrp 2.2.2.1 or lower can install stock kindle firmware. Other TWRP versions will bootloop the Kindle Fire, and Twrp will need to be flashed in bootloader
Click to expand...
Click to collapse
Well, whatever KFU .99 downloaded, that's what I flashed. And it worked. I don't have the Kindle anymore to check TWRP version .
I don't want anyone bricking their fire because of my steps though. I'll edit the post. Thanks sd_shadow!

KFU will download latest twrp the first time you select install twrp, after that will install same version, and will not check for update, unless you remove twrp.IMG from folder.
Sent from my Amazon OtterX using Tapatalk

Has OTA root keeper been tried? Voodoo or Superuser option. It needs to be backed up before update is installed

need help with a stock 6.3.3
Ever since my wife asked me to try to root her stock 1st generation Kindle Fire (currently running 6.3.3), I have had a hell of a time trying to get this thing rooted. I will also admit that I am a relative newbie when it comes to rooting devices. I am perfectly comfortable doing a few tweaks here and there, even through using command-line tools, but this is my first attempt at trying to root a device. I have both my MacBook Pro OSX (Mavericks) laptop and my Windows 7 desktop at my disposal, but I have only been able to make limited progress in rooting the KF.
I have used a number of tools (which I realize are mostly variants of one another): Kindle Fire Utility 0.9.9, RootKindleFire631 (from RootKindleFire.com), Breakdroid, and KindleFireRootMacLinux (which basically uses the ZergRush method). All to no avail. The most common error that I get is "Couldn't write bp1, panic". Hope this helps some developers out there to finally find a feasible rooting method for this one.
Curse you, Amazon, you may have won this round, but the war is far from over!

I created a prerooted 6.3.3 update that can be installed in twrp.
I have Installed with 2.2.2.1 and 2.7.1.0 versions of Twrp
Didn't change much,
I replaced stock install script with tobiascuypers' install script from [Rom] Stock 6.3.2 [Mods] [04.22.13] [Primary/Alt]
Added Root files (busybox, su, SuperSU)
Added Google Apps (Framwork, Play Store, Calendar, Google Voice, Google +)
Added other apps (Root Browser, Go Launcher, Facebook)
Instructions
Download update-kindle-prerooted.6.3.3.v1.zip, place on sd card, wipe data (may be optional), install with TWRP
wipe cache, reboot, may take a few mins to boot first time.
Tested Google play (signed in, downloaded apps)
Didn't test amazon sign in.
Edit; see my [2014][Pre-Rooted][Stock]System Version 6.3.3-Original Kindle Fire Only thread

sd_shadow said:
I created a prerooted 6.3.3 update that can be installed in twrp.
I have Installed with 2.2.2.1 and 2.7.1.0 versions of Twrp
Didn't change much,
I replaced stock install script with tobiascuypers' install script from [Rom] Stock 6.3.2 [Mods] [04.22.13] [Primary/Alt]
Added Root files (busybox, su, SuperSU)
Added Google Apps (Framwork, Play Store, Calendar, Google Voice, Google +)
Added other apps (Root Browser, Go Launcher, Facebook)
Instructions
Download update-kindle-prerooted.6.3.3.v1.zip, place on sd card, wipe data (may be optional), install with TWRP
wipe cache, reboot, may take a few mins to boot first time.
Tested Google play (signed in, downloaded apps)
Didn't test amazon sign in.
Click to expand...
Click to collapse
Does this require a factory cable?

Xeddicus said:
Does this require a factory cable?
Click to expand...
Click to collapse
if 6.3.3 is installed already yes a fastboot cable is needed to install fff bootloader and twrp.
If 6.3.2. Is installed, use kindle fire utility, to install bootloader and twrp.
Sent from my XT894 using Tapatalk

@sd_shadow - Installed fine with only dalvik / cache wipe over existing 6.3.3 (I removed most of the 3rd party apps prior to install).
Probably deserves it's own thread in development.
First thing I did was freeze OTASilentInstall.apk in /system/app/. I may consider removing it completely in the future.
Thanks for this. :good:

overground said:
@sd_shadow - Installed fine with only dalvik / cache wipe over existing 6.3.3 (I removed most of the 3rd party apps prior to install).
Click to expand...
Click to collapse
If I make a new version I will remove updater, and maybe all the extra apps other than play store, and ones need for root (supersu, binary, and busybox),
Probably deserves it's own thread in development.
Click to expand...
Click to collapse
Yes thought I would start a thread in Dev, but wasn't sure about the new General Public License rules (posting sources like the kernel), most of the devices I follow have it stickied in the dev section, but I see it is not in Kindle dev section?
First thing I did was freeze OTASilentInstall.apk in /system/app/. I may consider removing it completely in the future.
Thanks for this. :good:
Click to expand...
Click to collapse
I hadn't really looked for the updater apk, so that will help.
Thanks for the feedback

sd_shadow said:
Yes thought I would start a thread in Dev, but wasn't sure about the new General Public License rules (posting sources like the kernel), most of the devices I follow have it stickied in the dev section, but I see it is not in Kindle dev section?
Click to expand...
Click to collapse
You're not modifying the kernel, therefore there is no source (or changes) to post. GPL does not apply in this case.
Just specify in your thread that the ROM contains the stock, unmodified Amazon kernel.
If anyone beefs you on it, you can point them to this post.

overground said:
You're not modifying the kernel, therefore there is no source (or changes) to post. GPL does not apply in this case.
Just specify in your thread that the ROM contains the stock, unmodified Amazon kernel.
If anyone beefs you on it, you can point them to this post.
Click to expand...
Click to collapse
Thanks Posted here [2014][Pre-Rooted][Stock]System Version 6.3.3-Original Kindle Fire Only