• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[RECOVERY] TWRP Recovery 2.8.7.0 - Apollo/Thor

Status
Not open for further replies.
Search This thread

ggow

Recognized Developer
Feb 28, 2014
3,892
10,557
Amazon Fire
Samsung Galaxy Tab S7 / S7 Plus
Hello All,

NOTE: You should unlock your bootloader.

These are patched TWRP recovery images for the Apollo and Thor devices only. Now Built from the latest .4.5.3 sources.

WARNING:
- Be sure to have a working /system partition before proceeding with installation.

Installation
- Ensure you are running stock firmware .3.2.3.2
- Obtain Root
- Copy the recovery image to the root of your sdcard
- Flash the recovery image by issuing the following commands:

Code:
adb shell
su
dd if=/sdcard/signed-<device>-twrp-2870.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

Download
- Apollo Recovery Image
- Thor Recovery Image

Thanks

- @vortox for the exploit
 
Last edited:

jeryll

Senior Member
Dec 23, 2010
862
686
Xiaomi Poco X3 NFC
Redmi Note 10 Pro
Working on 14.3.1.0

I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
 
Last edited:

ggow

Recognized Developer
Feb 28, 2014
3,892
10,557
Amazon Fire
Samsung Galaxy Tab S7 / S7 Plus
Thanks ggow. Could we expect CM roms soon from your new release? ;)

Hello tuanda82,

It depends on Amazon, my unlocked Apollo stopped working so they sent me a new one but came pre-installed with 4.5.2.

They have refused to downgrade me back to the old firmware. And after a lot of to and fro they agreed to replace it again .

I hope I have luck with the new device been on the required firmware.

But yes I definitely would like to make such a release.
 
  • Like
Reactions: jeryll and tuanda82

jimyv

Senior Member
Jan 31, 2012
583
188
central Indiana
dangerous

I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
I would not be trying interchang eROMs and or backups ppluntil certain things are verified by our developersgosh it only takes a few minutes to understand that one is built for locked bootloader the other one bypasses and they both flash completely different partitions and have different installation scripts.you're just asking to be one of the ignorant whiners on the sidelines while we have fun ..stuck with your brick. be patient guys this is all new stuff if you can't afford to be a developer then I devise you let somebody else take the risk
 

tbm13

Member
Feb 26, 2014
15
3
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?

What happens when TWRP Recovery is damaged? Is there still a way to recover?

And is there a difference in how TWRP is started as opposed to Safestrap?

Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
 
Last edited:

r3pwn

Inactive Recognized Developer
Jul 11, 2012
1,745
2,046
Lakeland, FL
r3pwn.com
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?

What happens when TWRP Recovery is damaged? Is there still a way to recover?

And is there a difference in how TWRP is started as opposed to Safestrap?

Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.

SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
 

Håvi

Senior Member
Oct 27, 2012
97
22
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.

SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?
 

kingpin32

Senior Member
Jan 18, 2010
74
7
Jacksonville
I was able to roll back to 3.1.0 and installed twrp. I was able to make a backup and successfully restored the backup. However after about an hour I came back to my kindle an noticed it updated itself to 4.1.1. I was under the impression with recovery installed any new updates would . Not be able to install. Now when I try to boot into recovery it on l y boots kindle recovery not twrp.

Sent from my KFAPWI using Tapatalk
 

Cpasjuste

Senior Member
Jun 8, 2007
962
1,358
Thanks ggow. Could we expect CM roms soon from your new release? ;)

The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ... :)
 
Last edited:

GSLEON3

Retired Senior Moderator
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ... :)

Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.
 
  • Like
Reactions: jimyv and ggow

ggow

Recognized Developer
Feb 28, 2014
3,892
10,557
Amazon Fire
Samsung Galaxy Tab S7 / S7 Plus
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ... :)

Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.

When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.
 
  • Like
Reactions: tbm13 and jeryll

Cpasjuste

Senior Member
Jun 8, 2007
962
1,358
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.

Thanks gsleon but don't rob your mom :p

---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------

Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.

When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.

Crossing fingers :)
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 20
    Hello All,

    NOTE: You should unlock your bootloader.

    These are patched TWRP recovery images for the Apollo and Thor devices only. Now Built from the latest .4.5.3 sources.

    WARNING:
    - Be sure to have a working /system partition before proceeding with installation.

    Installation
    - Ensure you are running stock firmware .3.2.3.2
    - Obtain Root
    - Copy the recovery image to the root of your sdcard
    - Flash the recovery image by issuing the following commands:

    Code:
    adb shell
    su
    dd if=/sdcard/signed-<device>-twrp-2870.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

    Download
    - Apollo Recovery Image
    - Thor Recovery Image

    Thanks

    - @vortox for the exploit
    7
    Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?

    What happens when TWRP Recovery is damaged? Is there still a way to recover?

    And is there a difference in how TWRP is started as opposed to Safestrap?

    Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
    New recovery system
    - Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
    - Installed to "recovery" partition
    - Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
    - Called from the bootloader
    - If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.

    SafeStrap
    - No custom kernels (no CM)
    - Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
    - Designed to provide semi-custom ROMs on devices with locked bootloaders
    - Called from the Kernel
    6
    TWRP 3.0.0-0



    Maybe this helps you (ggow) with developing and improoving CM 13 :)

    - I have been testing Twrp 3.0.0-0 for a few weeks on Thor and Apollo
    - Looks good so far
    - Will release sometime during the coming week

    Sent from my Kindle Fire HDX 8.9 using Tapatalk
    5
    Davey126, HDX aren't very popular models.
    Unlock of the bootloader has became available later than a year after start of the sales.
    Also it is not so easy for everyone to install custom ROM natively.
    Amazon updates can't be rolled back to use unlock. I'm sure there are a lot of customers which are absolutely fine running latest FireOS.
    The device is some kind of obsolete and it's not produced anymore.
    All these facts limit the users of custom ROMs. I see there are not so many users of custom ROMs.
    Also I'm the kind of person that will face each and every bug without any seeking of it. This was proved by several Android devices starting from 1.6. I'll never buy anything on Android anymore, Apple sometimes have the bugs too but there are no any broken custom ROMs and no need in them. My opinion is Android is broken by design. I'm happy that there are no any custom broken ROMs for my BlackBerry.
    I see that every new ROM that made by ggow includes some old issues which sometimes can be found reported by lonely user somewhere in a thread. Each ROM has known issues.
    Also I can see that ggow doesn't use HDX as a primary device anymore and he's not interested in development, these issues can't be unnoticed.
    Just to prove my words regarding the bugs in HDX TWRP:

    - I share some of the same frustrations as you
    - It is unfortunate that the hdx unlock didn't come sooner
    - Amazon really went to town locking the devices down
    - I am interested in developing the cm13 rom further. However I have a life with multitude of things going on and going through. This isn't a job, its something I enjoy, genuinely passionate about and share with the community here
    - The HDX devices have been tough devices to develop due to lack of info or updated binaries and also my first
    - its a miracle anything past KitKat actually works let alone been bug free
    - to enable cm13 to run I had to use a mish-mash of binaries from various other devices to enable it to boot
    - It doesn't look like Amazon is interested in these devices and Amazon if you are watching this it would be great to see some kind of support in providing hal source/drivers, updated proprietary blobs for marshmallow so we can get a stable user experience on aosp at least
    - The HDX is still my primary tablet which I am still working on
    - I have been working on other Amazon devices like the fire phone and Amazon fire tablet which is fully functional and 99.99% bug free
    On Twrp recovery my device was faulty leading to the issue you mentioned- haven't had issues since.


    Sent from my Nexus 6 using Tapatalk
    5
    Update

    New Apollo Recovery Image Posted built from latest 4.5.3 sources.

    Thanks @p1gl3t for solution to boot new kernel.