FORUMS
Remove All Ads from XDA

[CUSTOM RECOVERY] Cyanogen Recovery (2015-11-04)

3,142 posts
Thanks Meter: 7,815
 
Post Reply Email Thread
Announcement from ggow: Cyanogenmod Recovery for Amazon Fire 2015
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before using it! YOU are choosing to make these modifications.

Notes
- The recovery cannot boot if flashed to the recovery partition instead it must be booted via fastboot using:

Code:
fastboot boot recovery.img
- The reason it cannot be flashed is that the bootloader is signature checking the flashed image against Amazon's RSA keys.
- External sdcard is not accessible from the recovery at the moment - will fix
- The touchscreen panel is not usable at the moment - instead use the volume up/down keys to navigate and power button to select
- The volume up/down keys are swapped - will fix this
- Apply update from internal memory and sideload are working.
- This is a basic recovery - it has no backup or restore function
- This does the job until TWRP is available

Download
- Amazon Fire Cyanogen Recovery

XDA:DevDB Information
Cyanogenmod Recovery, Tool/Utility for the Amazon Fire

Contributors
ggow

Version Information
Status: Beta

Created 2015-11-04
Last Updated 2015-11-06
The Following 19 Users Say Thank You to ggow For This Useful Post: [ View ] Gift ggow Ad-Free
 
 
4th November 2015, 02:10 PM |#2  
Senior Member
Flag Los Angeles
Thanks Meter: 229
 
More
So what can we sideload and cannot? And the amzn rsa is located in /system/vendor/data. Now I'm wondering if someone still has the rsa bug from the hdx the old one and we can replace that with that file and try unlocking the bootloader.
4th November 2015, 02:16 PM |#3  
ggow's Avatar
OP Senior Member
Thanks Meter: 7,815
 
Donate to Me
More
Quote:
Originally Posted by Awesomeslayerg

So what can we sideload and cannot? And the amzn rsa is located in /system/vendor/data. Now I'm wondering if someone still has the rsa bug from the hdx the old one and we can replace that with that file and try unlocking the bootloader.

- Pretty much anything we want to sideload, we can
- I have sideloaded:
Official Amazon Firmware
SuperSU.zip
Modified Gapps Package.zip
Xposed
- CVE-2014-0973 (the vulnerability which was exploited on the HDX) is patched in the Fire's bootloader
4th November 2015, 02:28 PM |#4  
Senior Member
Flag Los Angeles
Thanks Meter: 229
 
More
Quote:
Originally Posted by ggow

- Pretty much anything we want to sideload, we can
- I have sideloaded:

Official Amazon Firmware
SuperSU.zip
Modified Gapps Package.zip
Xposed
- CVE-2014-0973 (the vulnerability which was exploited on the HDX) is patched in the Fire's bootloader

Oh ok. So we can try sideload in or flashing a custom image now?
4th November 2015, 02:30 PM |#5  
ggow's Avatar
OP Senior Member
Thanks Meter: 7,815
 
Donate to Me
More
Quote:
Originally Posted by Awesomeslayerg

Oh ok. So we can try sideload in or flashing a custom image now?

Yes, we can flash a custom rom
4th November 2015, 02:42 PM |#6  
Vlasp's Avatar
Senior Member
Flag Plano, Texas
Thanks Meter: 275
 
More
Quote:
Originally Posted by ggow

Yes, we can flash a custom rom

And the bootloader won't recognise the different Rom? I have heard on some devices if you install a different ROM then it doesn't go past the bootloader.

Sent from my XT912 using Tapatalk
4th November 2015, 02:56 PM |#7  
ggow's Avatar
OP Senior Member
Thanks Meter: 7,815
 
Donate to Me
More
Quote:
Originally Posted by Vlasp

And the bootloader won't recognise the different Rom? I have heard on some devices if you install a different ROM then it doesn't go past the bootloader.

Sent from my XT912 using Tapatalk

- The bootloader has no knowledge of the Android ROM AFAIK
- We have to bear in mind that we are limited to the stock boot.img therefore
- Any rom we produce should be based off the stock boot.img
- If we did base the ROM off a custom kernel then we would have to "fastboot boot" the custom_boot.img each boot or reboot - so this is not feasible in terms of user experience.
- On the HDX, when it was a locked device I was able to boot AOSP in this manner
4th November 2015, 03:05 PM |#8  
Vlasp's Avatar
Senior Member
Flag Plano, Texas
Thanks Meter: 275
 
More
Quote:
Originally Posted by ggow

- The bootloader has no knowledge of the Android ROM AFAIK
- We have to bear in mind that we are limited to the stock boot.img therefore
- Any rom we produce should be based off the stock boot.img
- If we did base the ROM off a custom kernel then we would have to "fastboot boot" the custom_boot.img each boot or reboot - so this is not feasible in terms of user experience.
- On the HDX, when it was a locked device I was able to boot AOSP in this manner

We should be able to use custom boot.img when we get safestrap, right?

Sent from my KFFOWI using Tapatalk
4th November 2015, 03:29 PM |#9  
Senior Member
Thanks Meter: 104
 
More
Is it possible to flash the OpenGApps package? I usually stick with the Pico one and install apps from there.
4th November 2015, 03:37 PM |#10  
inscythe's Avatar
Senior Member
Thanks Meter: 126
 
More
Quote:
Originally Posted by ggow

- Pretty much anything we want to sideload, we can
- I have sideloaded:

Official Amazon Firmware
SuperSU.zip
Modified Gapps Package.zip
Xposed
- CVE-2014-0973 (the vulnerability which was exploited on the HDX) is patched in the Fire's bootloader

I'm actually interested in that modified gapps package... I'd like to keep the gapps as system apps properly.

Do you mind sharing which gapps package did you use and what modification you did?
4th November 2015, 04:17 PM |#11  
Senior Member
Thanks Meter: 545
 
More
this works on t he 50$ fire tab?
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes