Restore Stock Recovery - Fire HD 8 5th Gen (Thebes) - Fire HD 8 and HD 10 Q&A, Help & Troubleshooting

If you have lost access to your stock recovery on your Amazon Fire HD 8 5th Gen (Thebes) for whatever reason I would highly recommend restoring your recovery before doing any further customization to your device. Without recovery you have absolutely nothing to fall back on if your device becomes inoperable. If you have tried flashing any type of custom recovery directly to your device its more then likely you have lost access to your stock recovery. Hopefully youve made it to this thread before it was too late and luckily its a pretty simple process to restore your access.
Before we begin you must have a working OS for this process to work. If your device will not successfully boot then you can not complete the steps necessary to restore access to your recovery.
First lets
• Download Fire HD 8 Stock Recovery Image https://app.box.com/s/667bqfdgfi5qs7wufleobtirkub4gx4l
• Download and install Flashify
http://www.apkmirror.com/apk/christian-gollner/flashify/
Next we'll
• Start up the Flashify App and give it root access
• Press "Select Recovery Image" then "choose file"
• Browse to the Fire HD 8 Stock Recovery Image you downloaded earlier, select it and choose "Yup"
• Once flashing is complete reboot to recovery to confirm access has been restored
That's it now you're back in action!!!

Why cant we use this to flash twrp?

coopmaster said:
Why cant we use this to flash twrp?
Click to expand...
Click to collapse
Bootloader doesn't allow

Then how does bootloader allow flashing stock recovery?

madsc13n41s4 said:
Then how does bootloader allow flashing stock recovery?
Click to expand...
Click to collapse
it's signed by Amazon
Sent from my KFFOWI using XDA Labs

Related

[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

QFire fire fire and cwm (solved)

I saw a post like this before but I can't find it so sorry for making a new thread anyway,do you need to install fire fire fire in order to install cwm.
Sent from my Droid using XDA
Read the kindle fire for beginners guide up top, it'll allow you to understand the relationship between FFF and CWM. Then it'll be clear what your answer is.
There are so many pseudo bricks on here because the rooting process is WAY too easy, so most android newbs run headfirst into rooting and screwing everything up without understanding what they're doing and why they're doing it.
Gone are the old nexus one rooting days where it was only performed through adb/fastboot and involved sanding down your battery plus pulling/pushing in SD card. None of this one click crap that never weeds out the mis, under, or non-informed.
To my understanding after reading, fire fire fire is a bootloader that goes into fastboot mode for 5 seconds,wich means I don't need fire fire fire and cwmr.All I need is CWMR, correct.
Thanks
Sent from my Droid using XDA
and it offers the possibility to boot to recovery at startup by repeatently pressing the power button till it gets orange
how do you get to recovery if your system is failing ?
b63 said:
and it offers the possibility to boot to recovery at startup by repeatently pressing the power button till it gets orange
how do you get to recovery if your system is failing ?
Click to expand...
Click to collapse
Now I'm confused again.do you need both or can you just install CWMR and it will work???
Sent from my Droid using XDA
both !!!
the custom bootloader (fff) and a recovery (cwm or twrp)
to fully understand how it is working i would recommend to read kinfauns sticky thread
thanks
b63 said:
both !!!
the custom bootloader (fff) and a recovery (cwm or twrp)
Click to expand...
Click to collapse
Ok but last time I installed twrp all I had to do is click install twrp and I didn't need to install fff first.can I do the same with CWMR...does KFU automatically install fff when you click install twrp or cwmr.
twrp and cwm use different installation methods:
if you install twrp then it installs fff 1.0 as integrated part of the installation package
if you want the newest fff with twrp then you have to install it additionally again afterwards
if you use cwm then cwm will be pushed to the recovery partition - not more
therefore if you want to use cwm you have to install both fff & cwm
in kfu this would be: "install newest fff" and "install cmw"
b63 said:
twrp and cwm use different installation methods:
if you install twrp then it installs fff 1.0 as integrated part of the installation package
if you want the newest fff with twrp then you have to install it additionally again afterwards
if you use cwm then cwm will be pushed to the recovery partition - not more
therefore if you want to use cwm you have to install both fff & cwm
in kfu this would be: "install newest fff" and "install cmw"
Click to expand...
Click to collapse
Thank you...thanks for not getting frustrated with me also.
Sent from my Droid using XDA
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
b63 said:
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Click to expand...
Click to collapse
I just did.one last question.should I install cwmr or fff first.
Sent from my Droid using XDA
that is up to you - as you like - it makes no difference

Installed firefirefire & clockworkmod; rooting and twrp failed

I'm trying to install jelly bean on my kindle fire but using KFU I've only managed firefirefire and clockworkrecovery.
I tried rooting using KFU to root but that doesn't work. Always gets stuck with the twrp.img error saying it's the wrong image (seems to be a common problem)
I've tried getting twrp installed using adb shell but when I get to the command to load the recovery image I get error; couldn't load recovery image. I thought maybe there was a problem so I tried loading the fff bootloader even though I already had it on my kf but it also returned with error: couldn't load image.
Theoretically, if you have clockwork recovery, there is no need for TWRP. But if you must have TWRP instead, use clockwork to flash a rom (and FFF1.4 while you're at it). Boot into the rom and use the Smirkit to install TWRP. It will save you a lot of hassle.
soupmagnet said:
Theoretically, if you have clockwork recovery, there is no need for TWRP. But if you must have TWRP instead, use clockwork to flash a rom (and FFF1.4 while you're at it). Boot into the rom and use the Smirkit to install TWRP. It will save you a lot of hassle.
Click to expand...
Click to collapse
The problem is getting root access. Most of the guides I've tried to follow require twrp installed to get into recovery. Without root I can't flash another rom.
I also already have FFF 1.4.
So I reverted back to stock and went through the manual process again and I was able to get it to work. When I was initially trying to flash twrp with the command line I copied pasted the name of the file without adding the file extension. Fixed that by adding .img and everything went through. Got Jellybean on here now and it's running great.
If you are installing a custom rom (including MoDaCo), there is no need to go through the "rooting" process, hence saving you "a lot of hassle". Recoveries, like CWM and TWRP provide temporary root access.
soupmagnet said:
If you are installing a custom rom (including MoDaCo), there is no need to go through the "rooting" process, hence saving you "a lot of hassle". Recoveries, like CWM and TWRP provide temporary root access.
Click to expand...
Click to collapse
This is odd because I tried installing the JB rom after I got CWM on there. It booted up to a black screen and left it there for 5 minutes and still black screen. I reverted back with the update bin from amazon website after that.
hxu976 said:
This is odd because I tried installing the JB rom after I got CWM on there. It booted up to a black screen and left it there for 5 minutes and still black screen. I reverted back with the update bin from amazon website after that.
Click to expand...
Click to collapse
That has nothing to do with "rooting". Most of the time it's caused by a bad download (always check MD5s) or not "wiping" correctly before installation.

[Q] best way to upgrade TWRP ?

currently I'm on 2.6.0.0 and I was thinking of the benefits to upgrading to the latest version, plus also the risks involved. Whats the best way to upgrade TWRP ?
Use goomanager. It's by far the easiest since it's mostly automated.
mjb152 said:
currently I'm on 2.6.0.0 and I was thinking of the benefits to upgrading to the latest version, plus also the risks involved. Whats the best way to upgrade TWRP ?
Click to expand...
Click to collapse
I just downloaded the latest version of TWRP, booted into the bootloader and loaded the image by
Code:
fastboot flash recovery {insert name of image file here}
. Easy peasy,,,
oops, it's a bit late. I found the goomanager and installed it, trouble is I installed the OTA update which has set my device unrooted. There is no TWRP any more, not sure how to get into recovery mode as a dead android with a red triangle appears. I'm unlocked, but just cant get into recovery.
I took a full TWRP backup before I started, any tips ?
mjb152 said:
oops, it's a bit late. I found the goomanager and installed it, trouble is I installed the OTA update which has set my device unrooted. There is no TWRP any more, not sure how to get into recovery mode as a dead android with a red triangle appears. I'm unlocked, but just cant get into recovery.
I took a full TWRP backup before I started, any tips ?
Click to expand...
Click to collapse
Just use ADB to Fastboot flash recovery. Either Fastboot flash your root file or copy it to your device. If you copy it to your device, then boot to recovery and flash your Superuser or SuperSU .zip. You don't want to restore your backup though if your on the latest OTA now and your backup is the previous OTA.
SwiftKey'ed from my White Note 2 via XDA Premium HD
Wug works well.. Simple too.
Sent from my Nexus 7 using xda app-developers app
theres TWRP flashable zips in the TWRP thread, this is the easiest if you alrady got TWRP
you can use wug to install it for the first time then use goomanager to update it later or TWRP manager to dl manually.

Enable SU4TL-49 Stock Tethering + Back to Stock for OTA

DISCLAIMER - It usually goes without saying, but if you screw up your phone, don't blame me, blame yourself. I am not responsible for data loss, bricking, etc. As always, back up your data before doing anything.
As has already been mentioned by @jcase and @TheSt33v, taking the OTA will not affect an unlocked bootloader. However, unless you have a pure stock system partition, the OTA will not install. These instructions will work only if you're on a slightly modified stock SU4TL-44 ROM. If you're on another ROM (CM12/13, etc), you can follow the instructions posted in TheSt33v's thread.
Step 0: (optional, not tested, may not work) If you've installed xposed, uninstall any modules and flash the uninstaller located here through TWRP. More uninstall info may be found here.
Step 1: If rooted, use the SuperSU app to fully unroot, then reboot.
Step 2: Flash SU4TL-44_Tether_Stock_Restore.zip from TWRP. (restores build.prop to stock).
Step 3: Flash stock recovery through fastboot.
Step 4: Take OTA
Step 5: Flash TWRP through fastboot.
Step 6: Flash SU4TL-49_Tether_Enable.zip through TWRP
Done!
If you're going to do a full system restore via the xml (curtesy of @Tomsgt, aka RootJunky), after you've done so you can begin at step 4. Just make sure you backup all your data (downloads, photos, etc). I'm in no way responsible for anything you may inadvertently do to your phone!
And as a refresher, for those who may not remember how to flash a recovery. Just make sure both the fastboot executable and the recovery.img file are in the same folder
Windows
Code:
fastboot flash recovery file_name.img
Mac/Linux
Code:
./fastboot flash recovery file_name.img
I've also included the SU4TL-49 restore file for anyone who wants it. This simply reverts back to the stock build.prop
Alternatively, you can install the stock recovery image through TWRP by selecting Install, selecting Install Image, selecting the stock recovery image file that you've downloaded and selecting recovery.
Also, this flashable zip will get you back to 100% SU4TL-44 stock (except for the recovery menu. It doesn't touch that) and not wipe any of your data: http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
TheSt33v said:
Alternatively, you can install the stock recovery image through TWRP by selecting Install, selecting Install Image, selecting the stock recovery image file that you've downloaded and selecting recovery.
Click to expand...
Click to collapse
I had no idea you could flash the stock recovery from within TWRP. It never fails, you learn something new every day.
Sent from my XT1254 using XDA-Developers mobile app
If I have already taken the OTA update and re-rooted my phone with SuperSU, would I be able to simply flash TWRP an then the SU4TL-49_Tether_Enable.zip? Or would I have to disable root first.
Thanks
iloveamp said:
If I have already taken the OTA update and re-rooted my phone with SuperSU, would I be able to simply flash TWRP an then the SU4TL-49_Tether_Enable.zip? Or would I have to disable root first.
Thanks
Click to expand...
Click to collapse
This mod does not require root, just an unlocked bootloader so you can flash TWRP, then install the patch through TWRP.
And if you're rooted, you can install TWRP via Flashing.
I'm sorry I'm new here, but could this method work on this [ROM][6.0.1][Stock][Odexed]MPG24.107-70.2 Brazilian 6.0.1 for XT1254[TWRP Flashable] ROM? thanks.

Categories

Resources