[RECOVERY] TWRP Recovery 2.8.5.0 - Thor

[cdub50]

Wrong again

Actually,
You need to check your data. Since Lollipop, towelroot no longer works, and the only root solutions require adb and an unlocked boot loader (though there are some options which make this quite easy, and chainfire's does it all automatically). This is a decision by Google as evidenced by the annoying nag screen which pops up when trying to install towelroot (It installs, just does not run). The point is, know what you are buying. Amazon has a right to lock down their devices (though it is annoying and I wish they did not do it). Most providers do the same to some degree; Amazon just takes it further. This is why you get such good hardware for such little money. Unfortunately, playing by their rules is the price of admission.

your data again is wrong. towelroot was patched in 4.4.4 (for most vendors) and chaifires root for lollipop does not require an unlocked boot loader any more. Again your data is incorrect please stop trying to comment on things you obviously know nothing about.

 

[r3pwn]

Actually,
You need to check your data. Since Lollipop, towelroot no longer works, and the only root solutions require adb and an unlocked boot loader

Nobody said anything about Lollipop. Besides, Lollipop had no effect on Towelroot. Towelroot used a kernel-level exploit, so if the manufacturer didn't patch it, it would still be vulnerable in Lollipop (nearly all manufacturers have patched it already, though).

 

[058515471]

Hello,

Somebody help me upload your stock recovery please? I got problem when install this TRWP img before roll back to 13.1.10 (_ _!)

 

[jimyv]

Hello,

Somebody help me upload your stock recovery please? I got problem when install this TRWP img before roll back to 13.1.10 (_ _!)

you're going to have to tell us which firmware you started off on to get the correct recovery. If its. .4 I thought I saw it uploaded somewhere here already.

 

[murso74]

I started off with 3.2.3, flashed the IMG file with flashify, and now I can only boot into twrp. Trying to reboot to system seems me back to recovery (twrp). I missed something somewhere

OK, so when I reboot into system, it sends me to twrp. When I reboot to recovery, it sends me to a screen that says

Kindle fire system recovery

Your kindle doesn't seem to be able to boot....

Then give me options to reboot or reset to factory. If I choose reboot, I end up back in twrp

 

[ggow]

I started off with 3.2.3, flashed the IMG file with flashify, and now I can only boot into twrp. Trying to reboot to system seems me back to recovery (twrp). I missed something somewhere

OK, so when I reboot into system, it sends me to twrp. When I reboot to recovery, it sends me to a screen that says

Kindle fire system recovery

Your kindle doesn't seem to be able to boot....

Then give me options to reboot or reset to factory. If I choose reboot, I end up back in twrp

Hello murso74,

It sounds like you may have flashed twrp to your /boot partition and that you still have the stock recovery installed in the /recovery partition.

Important: First thing to do now is to flash twrp to the correct partition.

Boot into twrp and use the following command substituting your recovery.img for your filename:

dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

Only once you have twrp installed in your recovery partition then you will be able to flash a rom like cm11 or hdx nexus 2.03 which will also update the /boot partition enabling your system to boot.

 

[murso74]

Hello murso74,

It sounds like you may have flashed twrp to your /boot partition and that you still have the stock recovery installed in the /recovery partition.

Important: First thing to do now is to flash twrp to the correct partition.

Boot into twrp and use the following command substituting your recovery.img for your filename:

dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

Only once you have twrp installed in your recovery partition then you will be able to flash a rom like cm11 or hdx nexus 2.03 which will also update the /boot partition enabling your system to boot.

the second part of the command, i'm getting the error "can't open 'dev/block/platform/msm-sdcc.1/by-name/recovery': no such file or directory"

do i have to create a recovery directory under "by-name" or should that read "recovery.img"

edit:: nevermind, fat fingered it

 

[058515471]

you're going to have to tell us which firmware you started off on to get the correct recovery. If its. .4 I thought I saw it uploaded somewhere here already.

nvm, i found it. thanks! :good:

 

[DQEight]

Assistance please?

I've been out of the HDX scene for a while, my tablet is still on 13.3.1.0. I used the hdx toolkit to block updates back then. How should i proceed in getting to the right version and getting this installed.

 

[EncryptedCurse]

I've been out of the HDX scene for a while, my tablet is still on 13.3.1.0. I used the hdx toolkit to block updates back then. How should i proceed in getting to the right version and getting this installed.

All you need to do is flash the image with Flashify.

 

[DQEight]

All you need to do is flash the image with Flashify.

So I shouldn't update to 13.3.2.3 first?

 

[EncryptedCurse]

So I shouldn't update to 13.3.2.3 first?

You certainly can, but it'll make no difference in whether you can install the recovery or not.
The exploit just doesn't work on x.3.2.4 and above — anything before that is fine.

 

[DB126]

Thank You!

A big thanks to cpasjuste for making this available along with other contributions throughout these threads. TWRP is an essential tool for nobs like me who occasionally farkle up a flash do other stupid things to themselves. It's even more important on Amazon devices given limited recovery options and increased brick potential. I realize several others were involved; my gratitude extends to them as well. And yeah, I donated a cup of java as others should consider if they benefited and are able.

 

[Cpasjuste]

A big thanks to cpasjuste for making this available along with other contributions throughout these threads. TWRP is an essential tool for nobs like me who occasionally farkle up a flash do other stupid things to themselves. It's even more important on Amazon devices given limited recovery options and increased brick potential. I realize several others were involved; my gratitude extends to them as well. And yeah, I donated a cup of java as others should consider if they benefited and are able.

Many thanks Davey , much appreciated

 

[DB126]

Question: After TWRP is installed (following a successful downgrade to 13.3.1.0) can one of ggow's pre-rooted stock roms be flashed to bring the device back up to 13.3.2.6? I saw some cautions in the Apollo thread (post #21) and my own attempts yielded a blue screen on reboot. I ultimately had to reflash stock 13.3.2.6 which of course rewrote the recovery partition and wiped out TWRP. Fortunately, stock ROM is working fine (rooted via towelroot; OTA off via HDX toolkit) but it appears recovery took a fatal hit (no response to power + vol-up) so I am a bit nervous trying again.

Ultimately I'll be using Nexus ROM or CM11 but one of my HDXs has a fair number of sideloaded apps/data so I wanted to keep that device on 13.3.2.6 for a bit with TWRP.

Thoughts?

 

[Cpasjuste]

Question: After TWRP is installed (following a successful downgrade to 13.3.1.0) can one of ggow's pre-rooted stock roms be flashed to bring the device back up to 13.3.2.6? I saw some cautions in the Apollo thread (post #21) and my own attempts yielded a blue screen on reboot. I ultimately had to reflash stock 13.3.2.6 which of course rewrote the recovery partition and wiped out TWRP. Fortunately, stock ROM is working fine (rooted via towelroot; OTA off via HDX toolkit) but it appears recovery took a fatal hit (no response to power + vol-up) so I am a bit nervous trying again.

Ultimately I'll be using Nexus ROM or CM11 but one of my HDXs has a fair number of sideloaded apps/data so I wanted to keep that device on 13.3.2.6 for a bit with TWRP.

Thoughts?

Hi Davey,

In fact twrp is probably still there, but since 13.3.2.6 is not compatible you have to downgrade again. To do this you HAVE TO RESTORE STOCK 13.3.2.6 RECOVERY FIRST BEFORE DOWNGRADING.

Then you should not update to 3.2.6 as its not compatible with twrp and you can't use ggow images as they don't contains a boot image.

You should (after having a working twrp recovery) :

- flash 13.3.2.3.2 stock amazon update renamed to zip from twrp recovery to update the bootloader to latest vulnerable, don't reboot
- flash my modified 13.4.5.1 update (in one of this thread post) from twrp
- disable WiFi / remove ota !

Edit : http://android.mydedibox.fr/hdx/update-kindle-13.4.5.2_user_452004120-twrp.zip

 

[DB126]

@Cpasjuste - thank you! I'm not sure where to locate a stock 13.3.2.6 recovery image. I read through posts that discussed extracting/generating a recovery image from a stock bin but I wasn't sure that was the best approach. My skills/tools in this area are rather limited (always willing to learn). My hope was to update to a stock recovery via flashify but that obviously needs a .img or .lok file to work with. Also comfortable at the command line. Yeah, I am quickly exposing nob tendencies.

 

[jeryll]

[MENTION=503571]I'm not sure where to locate a stock 13.3.2.6 recovery image.

https://s3.amazonaws.com/kindle-fire-updates/update-kindle-13.3.2.6_user_326001820.bin Here you go :good:
Oops, you need recovery image ONLY? Well, this is the whole update, which contains recovery image ... if you dont mind upgrade your 13.3.1.0 system amazon way, you could use this.

 

[DB126]

Thanks, jeryll. I do have a copy of that image along with stock 13.3.1.0.

I may be over reacting to cpasjuste who emphasized that I need to restore a stock 13.3.2.6 recovery before downgrading to 13.3.1.0, flashing TWRP, etc. If I can go directly from 13.3.2.6 with no working recovery to 13.3.1.0 (which presumably will rewrite the stock recovery) then I am good to go.

 

[DB126]

@Cpasjuste - thank you! I'm not sure where to locate a stock 13.3.2.6 recovery image. I read through posts that discussed extracting/generating a recovery image from a stock bin but I wasn't sure that was the best approach. My skills/tools in this area are rather limited (always willing to learn). My hope was to update to a stock recovery via flashify but that obviously needs a .img or .lok file to work with. Also comfortable at the command line. Yeah, I am quickly exposing nob tendencies.

Update: I opened a representative 13.3.2.6 bin file with 7zip and noted the recovery folder with a couple files including 'recovery-from-boot.p' which looks like what I need. I'll need to do some homework on how to prepare an appropriate image that can be safely flashed to recovery. Thoughts/guidance/cautions welcome!

Update #2: Seems 'recovery-from-boot.p' isn't a valid recovery image after all. It is some mechanism to preserve the stock recovery so that it is automatically restored after each boot. I'm back to seeking a stock 13.3.2.6 recovery.img that can be flashed. Probably any recovery.img from the 13.3.x.x series would due.