Related
I have a Kindle Fire HD 7 (7.4.6) rooted and I want to know if there's a way that I can install the TWRP Recovery without flashing any rom at the moment and most important without bricking it. I want to have it installed in case that in a future I want to flash a rom. I think it's a must have tool on this device but I'm not quite sure if it's possible and I don't want to try how-to's that I've read in these forums because it's not what I'm looking for and I don't want to mess up the KF . Any help or advice on this will be very appreciated. :angel:
There is a way but you have to do 1 of 2 things outside of what the standard tutorial says. The newer is checks the boot loader for its version to see if it matches with the is version, if it mismatches it will cause a boot loop. So if you tried the default instructions, you would boot loop since you are on a 7.4.6 os, so you have 2 choices, downgrade the is first to the same as the freedom boot image in the tutorial, or download the latest kinology ROM which has a 7.4.6 freedom boot image inside it that for some reason isn't posted by itself last I check. If you download the kinology ROM you don't have to flash it to install that freedom boot image you can just extract it from the ROM and use it in place of the freedom boot the tutorial tells you to use. Take note of one last thing, make sure to check the box in fire flash at the top with red warning text under it about downgrading the boot loader or you will get stuck with a red screen and that requires a fastboot cable to fix. Anyways here's the tutorial: http://forum.xda-developers.com/showthread.php?t=2271909
I suggest reading through it in its entirety to familiarize yourself. You also have a option for the lazier person, you can simply download the kinology ROM onto the device before flashing 2nd boot loader + twrp (because it will bootloop as I previously mentioned) and first make a backup of data and system, then flash the kinology ROM, then restore your backup you just made. In theory I think that will work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
There is a way but you have to do 1 of 2 things outside of what the standard tutorial says. The newer is checks the boot loader for its version to see if it matches with the is version, if it mismatches it will cause a boot loop. So if you tried the default instructions, you would boot loop since you are on a 7.4.6 os, so you have 2 choices, downgrade the is first to the same as the freedom boot image in the tutorial, or download the latest kinology ROM which has a 7.4.6 freedom boot image inside it that for some reason isn't posted by itself last I check. If you download the kinology ROM you don't have to flash it to install that freedom boot image you can just extract it from the ROM and use it in place of the freedom boot the tutorial tells you to use. Take note of one last thing, make sure to check the box in fire flash at the top with red warning text under it about downgrading the boot loader or you will get stuck with a red screen and that requires a fastboot cable to fix. Anyways here's the tutorial: http://forum.xda-developers.com/showthread.php?t=2271909
I suggest reading through it in its entirety to familiarize yourself. You also have a option for the lazier person, you can simply download the kinology ROM onto the device before flashing 2nd boot loader + twrp (because it will bootloop as I previously mentioned) and first make a backup of data and system, then flash the kinology ROM, then restore your backup you just made. In theory I think that will work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for the response, I'm trying that... but before I do this... I want to make sure I'm on the right track. I copied three files on the main kindle directory (fireflash11.apk, kfhd7-freedom-boot-7.4.6.img and kfhd7-twrp-2.6.3.1-recovery.img). I've installed the Fire Flash and now... I'm seeing the interface to flash the boot partition and recovery partition, and the bootloader says the warning thing that the bootloader is not kfhd7-u-boot-prod-7.2.3.bin. That last part is where I'm stuck in... I don't know if checking the box will mess up my kindle... so far, I know that I had to check the "apply stack override", "disable recovery auto update", then unplug cable and hit flash. I'm not sure if I'm still needing the kinology rom since I've downloaded the freedom boot from hashcode.
stunts513 said:
There is a way but you have to do 1 of 2 things outside of what the standard tutorial says. The newer is checks the boot loader for its version to see if it matches with the is version, if it mismatches it will cause a boot loop. So if you tried the default instructions, you would boot loop since you are on a 7.4.6 os, so you have 2 choices, downgrade the is first to the same as the freedom boot image in the tutorial, or download the latest kinology ROM which has a 7.4.6 freedom boot image inside it that for some reason isn't posted by itself last I check. If you download the kinology ROM you don't have to flash it to install that freedom boot image you can just extract it from the ROM and use it in place of the freedom boot the tutorial tells you to use. Take note of one last thing, make sure to check the box in fire flash at the top with red warning text under it about downgrading the boot loader or you will get stuck with a red screen and that requires a fastboot cable to fix. Anyways here's the tutorial: http://forum.xda-developers.com/showthread.php?t=2271909
I suggest reading through it in its entirety to familiarize yourself. You also have a option for the lazier person, you can simply download the kinology ROM onto the device before flashing 2nd boot loader + twrp (because it will bootloop as I previously mentioned) and first make a backup of data and system, then flash the kinology ROM, then restore your backup you just made. In theory I think that will work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Wait, so if you were to install 7.4.6 freedomboot, it would bootloop? Why?
x10knight said:
Wait, so if you were to install 7.4.6 freedomboot, it would bootloop? Why?
Click to expand...
Click to collapse
Because they were running 7.4.6 so the 7.4.6 bootloader is a match. The problem is that the exploit was patched at 7.3.0 so one really should downgrade to 7.2.3 first because sometimes clicking flash 7.2.3 bootloader while using FireFlash app does not work and you get a bootloop anyway. It's best to drag and drop a ROM onto the internal sd card before flashing. If you do bootloop, just go into TWRP and flash the ROM.
x10knight said:
Wait, so if you were to install 7.4.6 freedomboot, it would bootloop? Why?
Click to expand...
Click to collapse
I'm new and a complete noob to this, I'm running 7.4.6, can someone please explain freedom boot and if it would be possible for me to get a custom Rom loaded on my tablet without downgrading to 7.2.3?
Sent from my KFTT using xda premium
Freedom boot if I understand correctly is a patch to the kernel used for second bootloader, I believe it also has version data stored in it that the kindle is checks on boot, if the kernel doesn't match the kindle os version it boot loops into recovery. So yes you can do all without downgrading the os, its just suggested you do because amazon patched the boot loader a while back and downgrading ensures you don't boot loop in case you have an older freedom boot image or you are on 7.4.7. Its probably also flashes the old boot loader too which helps. Never used kffa so not positive about that though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
So how do you suggest I go about flashing my custom Rom, I don't want to downgrade and I want to use fireflash preferable?
Sent from my KFTT using xda premium
I prefer the fire flash method but if you or the program mess up and don't flash the boot loader with the older version first, you will need a fastboot cable to fix it. I haven't ever had a problem with fire flash myself, as long as you check the first box with a bunch of red warning text under it you should be OK.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I prefer the fire flash method but if you or the program mess up and don't flash the boot loader with the older version first, you will need a fastboot cable to fix it. I haven't ever had a problem with fire flash myself, as long as you check the first box with a bunch of red warning text under it you should be OK.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks figured it out on my own before your post but it's the thought that counts lol your post will help others tho, I was a complete noob it was actually easier than what I thought, I'm running CM11 right now
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
So... what I should do... run the fire flash app checking that box about the warning of boot loader... and put the files in place and check the "apply stack override" and that's it? I'm getting confused because the post went out of topic...
gracielatf said:
So... what I should do... run the fire flash app checking that box about the warning of boot loader... and put the files in place and check the "apply stack override" and that's it? I'm getting confused because the post went out of topic...
Click to expand...
Click to collapse
First, drag and drop what ever ROM you are going to use onto the root of the internal SD card (CM, Paranoid Android, which ever one). This is important. If you do loop, access TWRP and flash the ROM.
Make sure to put the images in the right place, tick "apply stack override" and also tick "disable recovery auto update" and also chaeck "7.2.3 bootloader."
Here is the original tutorial as well for your reference. http://forum.xda-developers.com/showthread.php?t=2271909
Edit: when you do go to flash the ROM from TWRP you first "swipe" then flash the ROM and then wipe only Dalvic and CACHE.
LinearEquation said:
First, drag and drop what ever ROM you are going to use onto the root of the internal SD card (CM, Paranoid Android, which ever one). This is important. If you do loop, access TWRP and flash the ROM.
Make sure to put the images in the right place, tick "apply stack override" and also tick "disable recovery auto update" and also chaeck "7.2.3 bootloader."
Here is the original tutorial as well for your reference. http://forum.xda-developers.com/showthread.php?t=2271909
Edit: when you do go to flash the ROM from TWRP you first "swipe" then flash the ROM and then wipe only Dalvic and CACHE.
Click to expand...
Click to collapse
Got it, wish me luck! :cyclops:
gracielatf said:
Got it, wish me luck! :cyclops:
Click to expand...
Click to collapse
Good luck!
Well... that was fast. I didn't need the Kinology ROM, but I downloaded and dragged it to the Kindle, just in case it boot loop and so have the rom as backup. Just needed the three fiiles. I'll place the instructions clearly just in case anyone wants to do this and worked perfectly for me.
Download:
fireflash11.apk,
kfhd7-freedom-boot-7.4.6.img and
kfhd7-twrp-2.6.3.1-recovery.img.
Copy or Drag & Drop the three files to Kindle Fire HD 7". Make sure to have ON the "allow installations of applications" options found in drop down window (More+ -> Device). Then install the fireflash11.apk, after installation, open the app, if you got the warning message, check the box on the right, then place the kfhd7-freedom-boot-7.4.6.img in the "boot partition" section and tick "apply stack override", then the kfhd7-twrp-2.6.3.1-recovery.img in the "recovery partition" section and tick "disable recovery auto update". Unplug your KFHD7 from the USB, then hit Flash, and that's it! :victory:
No ROM needed, but in case you want like to go in "safe mode" like I did, download the Kinology ROM found here.
Rooted my kindle and flashed a custom ROM. Let a friend borrow it and when I got it back i through it in a closet. Recently moved and found my kindle, charged it, and nothing. I can boot into TWRP but that's about it. I've tried to flash new ROM and get an error message saying "error installing from zip". I've downloaded multiple ROMS multiple times and still no go. Is the kindle done for or am I doing something wrong?
Well your version of twrp is kinda outdated(at least according to the thread title, latest is 2.7), I would first try flashing the latest twrp update hashcode just posted, just download the zip, push it to the device with adb, and flash it and reboot into recovery again. Then try a cm 11 flash. What is did it have on it before all this happened?
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Well your version of twrp is kinda outdated(at least according to the thread title, latest is 2.7), I would first try flashing the latest twrp update hashcode just posted, just download the zip, push it to the device with adb, and flash it and reboot into recovery again. Then try a cm 11 flash. What is did it have on it before all this happened?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Not exactly sure. It has been about a year.
MaelstromMonkey said:
Not exactly sure. It has been about a year.
Click to expand...
Click to collapse
Ok, basing it off that it was either amazon os or a cm 10.1 based os. Only reason i ask is because if you tried to install cm 11, and maybe cm 10.2 onto the device at this point it would probably fail with that version of twrp because of lack of selinux support, so i would say go grab latest twrp zip(2.7) for your device, and flash it in recovery, reboot into recovery again, and flash cm 11. Probably should do a factory reset while your at it. I don't think internal storage will need wiping as i doubt it has any selinux xattrib's on it since its more than likely pre-cm10.2ish.
Firstly, thanks to SafinWasi and Red_81 who both helped me on other threads, this question follows on from those threads.
I'm trying to downgrade from 7.4.9 user 4952320. Eventually, I will probably install CM11 (I tried once and bricked my device), but for now I just want to downgrade the OS and be able to change the wallpaper, I'm sick of the black paper. (I've tried Stunts wallpaper fix and it didn't work)
When the device upgraded to 7.4.9 I made backups of the whole 12 img files (inc boot0block).
I've read that you need a 7.2.3 boot image to be able to install TWRP as part of the CM11. I obtained a rooted 7.2.3 boot image from Red_81s google drive. I then flashed that boot image and tried rebooting the device. No joy. I got the red triangle. I flashed my 7.4.9 boot image and rebooted. The device rebooted and worked as normal.
I then flashed the 7.2.3 rooted system image and rebooted. Again I got the red triangle. I then flashed the 7.2.3 boot image, (so the device had 7.2.3 system and boot images) but again I got the red triangle.
So, how do you downgrade? Should I have flashed all 3 of the 7.2.3 images? (I don't have the checksums of the images so I recognise if one of the images was corrupted the exercise was doomed to failure.)
By flashing my 7.4.9 system and boot images, my device was restored to functionality, and I learned a bit, but not enough to achieve the goal. I'm hoping someone can show me how to downgrade.
Thought I'd add that I did try Kindle Fire First Aide but got lots of errors about dropbox not being available.
Did you flash the system and recovery? Both are needed to successfully downgrade. I always wipe data too.
Sent from my Nexus 7 using XDA Premium 4 mobile app
cecr said:
.
Click to expand...
Click to collapse
You need to flash a custom recovery on a second bootloader as well. You can't just flash the system. You also need to flash the 7.2.3 boot.img and stack override. Any tutorial dealing with this mod will include all the steps. It important to pay attention to details and not skip any steps. http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
Red_81 said:
Did you flash the system and recovery? Both are needed to successfully downgrade. I always wipe data too.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't flash recovery, at my first attempt, just boot, then I tried boot & system. Both tries gave the red triangle.
I've tried again, with all 3 rooted images from your gdrive - recovery, boot & system, and again got the red triangle. I tried again with the 3 images from another source (my own unrooted 7.2.3 backup when I first got the HD7) and again, got the red triangle.
I haven't wiped the data because I would prefer to keep it so I can use the device (and think it should be possible to downgrade without wiping). I haven't been able to find a command to wipe just the cache...
So I'm more than a bit puzzled. The fastboot commands (eg fastboot -i 0x1949 flash boot boot.img) all return with "sending" then "OKAY", then "writing", then "OKAY" so I don't think there's any problem there.
I must be doing something wrong or missing something.
LinearEquation said:
You need to flash a custom recovery on a second bootloader as well. You can't just flash the system. You also need to flash the 7.2.3 boot.img and stack override. Any tutorial dealing with this mod will include all the steps. It important to pay attention to details and not skip any steps. http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your response, but at this stage I don't want to flash a new custom ROM, that may (probably will) come later, but at this stage I want to just downgrade. I've been warned that installing TWRP etc may leave the stock system in a bootloop, so a working stock backup won't be possible.
As I have to downgrade the stock boot image anyway in order to install a custom ROM, I thought I'd downgrade the whole OS in order to have a functioning stock system, then I can make a backup of it in TWRP, then install a custom ROM.
If I'm having problems with a simple downgrade, I might have more severe problems flashing a new ROM and be left with a dead device like I was previously, hence my caution and not wanting to move on until I know I can recover to the previous step if things go wrong.
Did you try downloading the original 7.2.3 from the thread and try flashing them ?
Red_81 said:
Did you try downloading the original 7.2.3 from the thread and try flashing them ?
Click to expand...
Click to collapse
Yes, I did. Tried them twice, in a different order (didn't think it would make a difference but you never know....). Anyway, tried again, this time, wiped data and cache (took 45 mins) and it worked! I now have 7.2.3 and access to Gplay (was already there).
I haven't registered it to my Amazon account yet, so email and contacts don't work, and am wondering if I should go straight to installing a custom ROM. I'm thinking if it isn't registered to Amazon, then they can't update it via OTA...... or can they?
It's been a bit of a task getting this far, but at least I'm more confident about getting into ADB and Fastboot!
cecr said:
I'm thinking if it isn't registered to Amazon, then they can't update it via OTA...... or can they?
Click to expand...
Click to collapse
well, I know the answer, yes, even though it hasn't logged into an Amazon account (I realise they pre-register them to your account before dispatch), it updated back to 7.4.9 just as I finished the above post and whilst I was thinking I should disable OTA updates using KFFA!
flip. This is turning into hard work. lol, still I know how to do it now.
I was having many issues after the last OTA and got mine to cm-11-20140609-SNAPSHOT-M7 last night. Mine was at 7.4.9 also. I followed rootjunky youtube videos to get mine re-rooted, flashed and working. After getting it rooted, he uses Fire Flash app to put twrp on the Kindle. I deviated a little and put the twrp 2.7.0.0 version other than that, I followed to a T. Once I got all that done, I went on the internet to Hashcode's repository and downloaded the newest cm-11 UNOFFICIAL he had listed directly to the device. I downloaded the latest Gapps from cyanogenmod and then booted into recovery(twrp) and installed. Everything is working beautifully now. Everything seems faster and smoother so far. I did go ahead and do an update from the about area in the settings to cm-11-20140609-SNAPSHOT-M7. I was also able to get all my books that I had purchased through kindle in the kindle reader.
greg2074 said:
I was having many issues after the last OTA and got mine to cm-11-20140609-SNAPSHOT-M7 last night. Mine was at 7.4.9 also. I followed rootjunky youtube videos to get mine re-rooted, flashed and working. After getting it rooted, he uses Fire Flash app to put twrp on the Kindle. I deviated a little and put the twrp 2.7.0.0 version other than that, I followed to a T. Once I got all that done, I went on the internet to Hashcode's repository and downloaded the newest cm-11 UNOFFICIAL he had listed directly to the device. I downloaded the latest Gapps from cyanogenmod and then booted into recovery(twrp) and installed. Everything is working beautifully now. Everything seems faster and smoother so far. I did go ahead and do an update from the about area in the settings to cm-11-20140609-SNAPSHOT-M7. I was also able to get all my books that I had purchased through kindle in the kindle reader.
Click to expand...
Click to collapse
Nice to know. Think I'll be doing something very similar, now I've made backups of 7.4.9 "just in case". Just have to go through all the above again!
Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.
twrp works, but SU binary still wont flash :/
edit - the combination of this APK and TWRP gave me all I need for root + rebooting and keeping root
Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.
I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.
Steel01 said:
I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.
Click to expand...
Click to collapse
So you were successful in getting TWRP installed, SuperSU installed and removing KingRoot clean - leaving only SuperSU on the system, surviving a reboot?
Ink Rampant Wolf said:
Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.
Click to expand...
Click to collapse
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks
You might wanna include the instructions as shown here,
http://forum.xda-developers.com/xpe...how-to-root-lollipop-xperia-tablet-z-t3115107
It basically tells you how to install SuperSU and remove the entire KingRoot library after that. It worked on my Z and on my SHIELD as well.
This was essentially what I did:
http://greenrobotgamer.com/shieldzone/root-shield-portable-lollipop-5-1/
Mine seems to be working just fine, after obtaining root and installing SuperSU. I didn't bother with installing TWRP, I just hotboot the recovery. I'm rebooting my SHIELD as we speak, see if there's any issue
EDIT: Scractch that, it's not booting. How do I flash the latest image back in?
JCESAR2 said:
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks
Click to expand...
Click to collapse
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Ink Rampant Wolf said:
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.
JCESAR2 said:
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.
Click to expand...
Click to collapse
You need to unlock your bootloader first.
ok long story short: since i had the shield drivers installed and tha adb drivers installed i did the oem unlock and after a confirmation screen on the shield i did it, then i immediately flashed the twrp image from the same command line. now the shield is stuck in nvidia android boot logo. any suggestions? thanks
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.
341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
JCESAR2 said:
nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.
Click to expand...
Click to collapse
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Ink Rampant Wolf said:
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
Guess I'll have to flash the old firmware then, it's been sitting there forever.
341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870
JCESAR2 said:
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870
Click to expand...
Click to collapse
I just re-flashed the system using RAM, should be fine now. I'll just have wait for the OTA all over again. UGH.
I wish someone could provide a KitKat version tho.
EDIT: Annnd battery's at 15% so the system won't let me OTA yet.
SuperSU will work fine with my latest TWRP builds posted here. The older 2.8.5.0 builds will not work, neither will any build in the linked thread before yesterday. I used SuperSU 2.49 Beta and it worked as expected.
Side Note: The older builds will have the problem where boot will just hang. That seems to be because the older builds didn't have selinux policies built in, so some things never get set up right and the boot panics.
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
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.
Awesomeslayerg said:
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.
Click to expand...
Click to collapse
- 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
ggow said:
- 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
Click to expand...
Click to collapse
Oh ok. So we can try sideload in or flashing a custom image now?
Awesomeslayerg said:
Oh ok. So we can try sideload in or flashing a custom image now?
Click to expand...
Click to collapse
Yes, we can flash a custom rom
ggow said:
Yes, we can flash a custom rom
Click to expand...
Click to collapse
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
Vlasp said:
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
Click to expand...
Click to collapse
- 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
ggow said:
- 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
Click to expand...
Click to collapse
We should be able to use custom boot.img when we get safestrap, right?
Sent from my KFFOWI using Tapatalk
ggow said:
- 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
Click to expand...
Click to collapse
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?
this works on t he 50$ fire tab?
patt2k said:
this works on t he 50$ fire tab?
Click to expand...
Click to collapse
This is FOR it dummy
stkpxl said:
Is it possible to flash the OpenGApps package? I usually stick with the Pico one and install apps from there.
Click to expand...
Click to collapse
inscythe said:
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?
Click to expand...
Click to collapse
- Yes, I'll post it shortly
- I have only flashed it so far with no testing
- My Fire hasn't been online yet because I haven't blocked OTA updates yet
- Will test and provide a link for download
EDIT: Good news the Gapps package works with full play store functionality
I'll upload it and post a link in the General Section
Vlasp said:
We should be able to use custom boot.img when we get safestrap, right?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
- I started investigating this and Safestrap may not be possible
- Safestrap is usually for locked devices granted, however...
- Even if it were possible our kernel doesn't have kexec capabilities
- As with other amazon devices we really need a way to unlock the bootloader.
Modified Open Gapps Package
inscythe said:
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?
Click to expand...
Click to collapse
stkpxl said:
Is it possible to flash the OpenGApps package? I usually stick with the Pico one and install apps from there.
Click to expand...
Click to collapse
- I have posted the Modified Open Gapps package here.
- Tested and seems to be working fine.
ggow said:
- I have posted the Modified Open Gapps package here.
- Tested and seems to be working fine.
Click to expand...
Click to collapse
Very nice will have to play around with this later have this tablet for my grandma so at least with root and custom launcher I can make it easier to use at least
ggow is the ****ing bomb!
Between all your work on the FirePhone and this tablet, tell me what I owe you!
Moogagot said:
ggow is the ****ing bomb!
Between all your work on the FirePhone and this tablet, tell me what I owe you!
Click to expand...
Click to collapse
Your first born maybe?
If someone wouldn't mind explaining the process of getting this recovery in my tablet. I' mused to flashing on my phone. Thanks
sandman512 said:
If someone wouldn't mind explaining the process of getting this recovery in my tablet. I' mused to flashing on my phone. Thanks
Click to expand...
Click to collapse
No problem. You can find instructions here.
sandman512 said:
If someone wouldn't mind explaining the process of getting this recovery in my tablet. I' mused to flashing on my phone. Thanks
Click to expand...
Click to collapse
you need adb and fastboot files
several options there are some basic information in my Amazon Fire Index
Fire Index: Which Amazon (Kindle) Fire Do I have?
once you have adb setup
boot Fire into fastboot mode: power off, Hold volume down, power on
if it boots to recovery select bootloader
once in fastboot mode check device manager Fire should be listed as Android adb interface
If so you should test fastboot commands with
Code:
fastboot -i 0x1949 getvar product
should get this back
Code:
ford
if so
place recovery.img in the same location as listed in command prompt
then boot recovery.img with
Code:
fastboot boot 2015-11-04-cm-12-recovery.img
Sent from my KFFOWI using Tapatalk