[ROM] [STOCK] Optimized Stock ROMs for Amazon Fire 7 (Ford & Austin) [APR 12 2019]
Optimized Stock ROM for the Amazon Fire 7 (the Ford and Austin models ONLY). Do not use any FireOS versions LOWER than what you are already using, or you will bootloop. In other words, no downgrading to an older version.
- Ford Firmware is based off of Amazon FireOS 5.3.1.0 (update-kindle-global-37.5.5.2_user_552153420.bin) and rebuilt using @superR Kitchen. Do not downgrade from a newer version. Austin firmware is based off the latest current release. As of April 12, that's 5.3.6.4.
- Deodexed. When uninstalling system apps, the odex files are left behind. The process of deodexing, making a long story short, puts those files back where they belong. In turn, when or if you uninstall the system application(s) associated with them, you gain a little more space. This also makes the uninstall process smoother with less risks of screwing up. I am down to about 93 Apps. 89 if you take away the 4 user apps installed
- Ford: Rooted. During installation, the ROM will be rooted with the last and final version of SuperSU, v2.82 by @Chainfire and contain the latest Busybox by @osm0sis.
- Austin: You must flash SuperSU or Magisk separately, after installing your firmware.
- Zipaligned. For smooth operations and better performance.
- No OTA. Both APKs associated with over the air updates (OTA) have been removed. This means no more waiting to connect to WiFi. You can safely sign into your network on the very first boot.
-YOU decide what you want. No apps have been removed aside from the above mentioned and none have been added aside from the above mentioned. Which means NO Gapps or Xposed. You are in control of your device therefore you should also decide what you want to keep, install or uninstall.
- STOCK. This ROM does NOT include my modifications or any other modifications not mentioned here.
Requirements and Installation
1. For Amazon Fire 7 Ford and Austin ONLY. Must already have root access or already have your bootloader unlocked.
2. If TWRP: Disconnect the tablet from PC and power it off. Reboot to recovery, hold down the volume down button and power button until the white amazon logo appears. When in recovery, tap wipe and select dalvik, cache, system and data ONLY and swipe to confirm. When done, tap home then reboot then recovery and swipe to confirm.
3b. If FlashFire (UNTESTED): First refer to step 2. When done open FlashFire. Tap the '+' and select OTA package or zip. Select the ROM fire_7_ford_stock_deodexed_rooted_no_ota-signed.zip. Tap the checkmark to confirm. Tap the '+' again and select wipe. Make sure EVERYTHING is selected EXCEPT storage. Tap the checkmark. Long press the wipe option on the screen and move it ABOVE the ROM zip. If Ever-root appeared, tap it and make sure ONLY preserve recovery is selected. Tap the flash button and confirm.
4 (TWRP continued). When back in recovery, navigate to the storage location of the New ROM and tap on it: fire_7_ford_stock_deodexed_rooted_no_ota-signed.zip and swipe to confirm installation. When done, reboot system.
5. Enjoy.
Downloads
- Ford Optimized ROM: fire_7_ford_stock_deodexed_rooted_no-ota_stock_rom-signed.zip
- Austin Optimized ROM: fire_7_austin_deodexed_rooted_no-ota_stock_rom-signed.zip
DragonFire1024 said:
Optimized Stock ROM for the Amazon Fire 7 (Ford)
- Based off of Amazon FireOS 5.3.1.0 (update-kindle-global-37.5.5.2_user_552153420.bin) and rebuilt using @superR Kitchen
- Deodexed. When uninstalling system apps, the odex files are left behind. The process of deodexing, making a long story short, puts those files back where they belong. In turn, when or if you uninstall the system application(s) associated with them, you gain a little more space. This also makes the uninstall process smoother with less risks of screwing up. I am down to about 93 Apps. 89 if you take away the 4 user apps installed
- Rooted. During installation, the ROM will be rooted with the last and final version of SuperSU, v2.82 by @Chainfire and contain the latest Busybox by @osm0sis.
- Zipaligned. For smooth operations and better performance.
- No OTA. Both APKs associated with over the air updates (OTA) have been removed. This means no more waiting to connect to WiFi. You can safely sign into your network on the very first boot.
-YOU decide what you want. No apps have been removed aside from the above mentioned and none have been added aside from the above mentioned. Which means NO Gapps or Xposed. You are in control of your device therefore you should also decide what you want to keep, install or uninstall.
- STOCK. This ROM does NOT include my modifications or any other modifications not mentioned here.
Requirements
1. For Amazon Fire 7 Ford ONLY. Must already have root access or already have your bootloader unlocked.
2. Plug your tablet into the PC and Download the zip attached to this post. Place it on internal or external storage. Go to the Open Gapps website and download the PICO Gapps Package for ARM, 5.1.1 and place it on your tablet's internal or external storage.
3. If TWRP: Disconnect the tablet from PC and power it off. Reboot to recovery, hold down the volume down button and power button until the white amazon logo appears. When in recovery, tap wipe and select dalvik, cache, system and data ONLY and swipe to confirm. When done, tap home then reboot then recovery and swipe to confirm.
3b. If FlashFire (UNTESTED): First refer to step 2. When done open FlashFire. Tap the '+' and select OTA package or zip. Select the ROM fire_7_ford_stock_deodexed_rooted_no_ota-signed.zip. Tap the checkmark to confirm. Tap it again. Tap the '+' again and select OTA/zip and select the Gapps zip. Tap the checkmark when done. Tap it again. Tap the '+' again and select wipe. Make sure EVERYTHING is selected EXCEPT storage. Tap the checkmark. Long press the wipe option on the screen and move it ABOVE the ROM zip. If Ever-root appeared, tap it and make sure ONLY preserve recovery is selected. Tap the flash button and confirm.
4 (TWRP continued). When back in recovery, navigate to the storage location of the ROM and Gapps zips. Tap the ROM: fire_7_ford_stock_deodexed_rooted_no_ota-signed.zip and swipe to confirm installation. When done, tap BACK and select the Gapps zip. Swipe to install. When done, reboot system.
5. Enjoy.
Downloads
- ROM: fire_7_ford_stock_deodexed_rooted_no_ota-signed.zip
- Gapps: Arm, 5.1.1, Pico. Open Gapps Project.
Click to expand...
Click to collapse
Good Job!
Waiting for the 7th gen..
PS: If you want to implement custom otas pm me. I know a method that works.
Rortiz2 said:
Good Job!
Waiting for the 7th gen..
PS: If you want to implement custom otas pm me. I know a method that works.
Click to expand...
Click to collapse
I just need the firmware .bin file. I can't test a build but I can build it and you can test it. In theory it should work. I'm pretty sure now, unless amazon changes something drastically, I think every fireOS version under 6 can be rooted on the spot from here on out. In other words FireOS can be permanently rooted.
Sent from my MotoG3 using XDA Labs
Gapps is optional. I recommend you uninstall the apps you don't want and flash gapps after.
Sent from my MotoG3 using XDA Labs
Didn't work for me. Just sat on the Fire animation screen for about 30 minutes.
riverstyxxx said:
Didn't work for me. Just sat on the Fire animation screen for about 30 minutes.
Click to expand...
Click to collapse
I think that it don't work because uses the 5.3.1.0 boot.img and the new preloader doesn't seem to be compatible with this boot.img.
Should follow in the footsteps of the other one, Fire OS Revamped. It's running on 5.6.3.0 perfectly.
Rortiz2 said:
I think that it don't work because uses the 5.3.1.0 boot.img and the new preloader doesn't seem to be compatible with this boot.img.
Click to expand...
Click to collapse
The boot.img isn't unpacked. It's simply a system install. No imgs are unpacked.
Sent from my MotoG3 using XDA Labs
Rortiz2 said:
I think that it don't work because uses the 5.3.1.0 boot.img and the new preloader doesn't seem to be compatible with this boot.img.
Click to expand...
Click to collapse
This is only for the Ford tablet too. I will have to optimize the more recent firmware releases for newer tablets.
Sent from my MotoG3 using XDA Labs
riverstyxxx said:
Should follow in the footsteps of the other one, Fire OS Revamped. It's running on 5.6.3.0 perfectly.
Click to expand...
Click to collapse
This is only for the Ford model. Essentially for those who remain and continue to remain on 5.3.1. ill have some more ready this week. Please note when I specify a device, it's only for that device.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
This is only for the Ford model. Essentially for those who remain and continue to remain on 5.3.1. ill have some more ready this week. Please note when I specify a device, it's only for that device.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
Yeah, Ford. KFFOWI. Flashed it and gapps with TWRP. Didn't work.
riverstyxxx said:
Yeah, Ford. KFFOWI. Flashed it and gapps with TWRP. Didn't work.
Click to expand...
Click to collapse
We're you already on 5.3.1? I made a note that this likely only works if you're already on 5.3.1.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
We're you already on 5.3.1?
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
I downgraded to whatever was in the twrp tutorial and went from the latest lineage to this. If that helps.
riverstyxxx said:
I downgraded to whatever was in the twrp tutorial and went from the latest lineage to this. If that helps.
Click to expand...
Click to collapse
Yeah you shouldn't downgrade again once you've moved on from 5.3.1. even taking out the boot.img, the old versions just aren't compatible with the new generation of fire 7s. I apologize. I have made a note in the OP. At least this time you can recover form it. I now know how it feels for those back in the day only they couldn't recover from this. Again apologies.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
Yeah you shouldn't downgrade again once you've moved on from 5.3.1. even taking out the boot.img, the old versions just aren't compatible with the new. I apologize. I have made a note in the OP.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
It's understandable. If you work on the latest build, that would be awesome because I do like what the other developer did but he left in a few things (and left out a few things) that he shouldn't have.
riverstyxxx said:
It's understandable. If you work on the latest build, that would be awesome because I do like what the other developer did but he left in a few things (and left out a few things) that he shouldn't have.
Click to expand...
Click to collapse
Link me to the latest firmware for your tablet, and give me the model of your tablet and I'll see what I can do.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
Link me to the latest firmware for your tablet, and give me the model of your tablet and I'll see what I can do.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
I assume it's this: https://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
The one on my tablet is FireOS Revamped 5.3.6.0, in the other part of the forums.
riverstyxxx said:
I assume it's this: https://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
The one on my tablet is FireOS Revamped 5.3.6.0, in the other part of the forums.
Click to expand...
Click to collapse
Ok I'll look at it in the next day or two. So far I've tried 2 firmwares, fire 7 ford, and HD 10. Both can already be rooted. So let's see if that makes any difference. I'm hoping it doesn't. If it works, then every amazon update from here on out, unless they change something, can be pre rooted.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
Ok I'll look at it in the next day or two. So far I've tried 2 firmwares, fire 7 ford, and HD 10. Both can already be rooted. So let's see if that makes any difference. I'm hoping it doesn't. If it works, then every amazon update from here on out, unless they change something, can be pre rooted.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
If you want to PM Me test versions for austin i can test it. But use 5.6.3.4 as base:
https://fireos-tablet-src.s3.amazon...z43/update-kindle-55.6.2.6_user_626533320.bin
Regards!
Rortiz2 said:
If you want to PM Me test versions for austin i can test it. But use 5.6.3.4 as base:
https://fireos-tablet-src.s3.amazon...z43/update-kindle-55.6.2.6_user_626533320.bin
Regards!
Click to expand...
Click to collapse
I have a few days off starting tomorrow. I'll see what I can accomplish.
Sent from my MotoG3 using XDA Labs
Related
*** USE AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF THINGS GO WRONG. ***
Introduction
I am very proud to bring you HDX Nexus Safestrap ROM. This is for both the Kindle Fire HDX 7" and 8.9" WIFI only variants and brings full AOSP functionality which are using Safestrap. You must be running stock firmware .3.2.4 - 3.2.8
Click to expand...
Click to collapse
Features
- Full Jelly Bean 4.2.2 AOSP functionality
Click to expand...
Click to collapse
Bug Reports
- Please use the Bugs section on this thread, it will make it a lot easier to to keep track.
Click to expand...
Click to collapse
Fresh Installation
- Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
- Flash hdx-nexus-gapps-v1.2.zip
- Then flash any addons
- If coming from any other ROM then do a factory reset.
- Reboot and enjoy.
Click to expand...
Click to collapse
Upgrading From Previous Version
- Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
- Flash hdx-nexus-gapps-v1.2.zip
- Wipe Dalvik Cache and Cache
- Then flash any addons
- Reboot and enjoy.
Click to expand...
Click to collapse
Changelog
- x -> v1.0.1
Code:
- Initial Release.
- Branched from mainline HDX Nexus ROM v2.0.5
Click to expand...
Click to collapse
Downloads
- Safestrap Apollo Nexus ROM
- Safestrap Thor Nexus ROM
- Gapps 1.2
Click to expand...
Click to collapse
Add-Ons
- Dolby Digital v1.2
Click to expand...
Click to collapse
FAQ
TBD
Source Code
- Kernel Source: Kindle HDX stock kernel, build number 1314.3.2.4
Finally
- Thank you to everyone for your ongoing support and to everyone that made a Donation.
Click to expand...
Click to collapse
XDA:DevDB Information
HDX Nexus Safestrap, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: .3.2.4 - 3.2.8
Based On: AOSP JDQ39
Version Information
Status: Stable
Current Stable Version: 1.0.1
Stable Release Date: 2015-02-07
Created 2015-02-07
Last Updated 2016-02-10
Reserved
Reserved
Update
Hello All,
Files are now up
Ggow much appreciated that safetrap version is coming back!
Just to clarify that this rom will work with devices that got upgraded to 4.5.2 and then downgraded by ACS to 3.2.7/8 and rooted with safetrap working.
Here are some questions that I'm sure people will be curious about:
- I'm currently on 2.0.2 and root checker says root is enabled, but couldn't find the supersu app. How does it work? Do i need to flash supersu?
- Can you install xposed with modules on this version? For example to mod notifications bar, status bar, power menu, etc.
- can I safely upgrade from the older 2.0.2 to this version?
- what about addons like the dolby digital? I assume its safe to flash too?
- current build.prop ids the device as Nexus HDX and tgere are a lot of apps on play store that are not compatible with the device, but they work just fine installed from another market (say 1mobile). Can we do something about it?
Sorry for so many questions, but i tried reading most stuff from the other thread but for some reason search in thread is disabled (no idea why).
Cheerz!
Awesome, thanks!!!
johim said:
Ggow much appreciated that safetrap version is coming back!
Just to clarify that this rom will work with devices that got upgraded to 4.5.2 and then downgraded by ACS to 3.2.7/8 and rooted with safetrap working.
Correct, yes.
Here are some questions that I'm sure people will be curious about:
- I'm currently on 2.0.2 and root checker says root is enabled, but couldn't find the supersu app. How does it work? Do i need to flash supersu?
The ROM is pre-rooted with the su binary and a daemon. SuperSU is a root manager so its up to you if want that functionality.
- Can you install xposed with modules on this version? For example to mod notifications bar, status bar, power menu, etc.
Yes you can.
- can I safely upgrade from the older 2.0.2 to this version?
Yes
- what about addons like the dolby digital? I assume its safe to flash too?
Yes
- current build.prop ids the device as Nexus HDX and tgere are a lot of apps on play store that are not compatible with the device, but they work just fine installed from another market (say 1mobile). Can we do something about it?
No matter how I modify the build.prop, google play store ends up not playing nice. So no not at the moment. Market helper used to work for this problem but seems to but patched now on googles servers.
Sorry for so many questions, but i tried reading most stuff from the other thread but for some reason search in thread is disabled (no idea why).
Cheerz!
Click to expand...
Click to collapse
See my responses above. I'll add some information to the FAQ when possible.
Sent from my Nexus 6 using Tapatalk
OK, I updated and flashed all gapps and addons. Everything works!
Then I tried installing Xposed Framework, and on reboot the result was black screen after rom bootup (right after android animation). Waited like 2-3 minutes, but nothing. Then had to force reboot it via power button. After reboot everything works again with Xposed installed. No idea what happened. Any guidelines on where I can check logs probably.
havent tried any module yet, but it would be nice if we keep a list of compatible and safe modules.
Question: can any of the xposed modules trip eFuse or break stock kernel (as rom is running on top of it) or safetrap makes it safe so any changes to system would be just to the slot rom?
johim said:
OK, I updated and flashed all gapps and addons. Everything works!
Then I tried installing Xposed Framework, and on reboot the result was black screen after rom bootup (right after android animation). Waited like 2-3 minutes, but nothing. Then had to force reboot it via power button. After reboot everything works again with Xposed installed. No idea what happened. Any guidelines on where I can check logs probably.
havent tried any module yet, but it would be nice if we keep a list of compatible and safe modules.
Question: can any of the xposed modules trip eFuse or break stock kernel (as rom is running on top of it) or safetrap makes it safe so any changes to system would be just to the slot rom?
Click to expand...
Click to collapse
Use this verison of Xposed found here.
Try Gravitybox (JB).
I don't know if any of the modules can trigger the efuse. You are correct, in theory Safestrap makes it so that any changes should only occur in that slot.
So far this ROM has been excellent. Great job and thanks a lot!
I have the problem, that there is no Play Store and I can't install downloaded applications. I downloaded applications through the browser and when I try to execute them I get the error "can't open file". So I can literally install no app. I tried to install ES File Explorer and gapps pico.
Anyone else who had this problem or knows how to solve it or has some ideas?
faulix said:
I have the problem, that there is no Play Store and I can't install downloaded applications. I downloaded applications through the browser and when I try to execute them I get the error "can't open file". So I can literally install no app. I tried to install ES File Explorer and gapps pico.
Anyone else who had this problem or knows how to solve it or has some ideas?
Click to expand...
Click to collapse
Did you flash gapps?
- Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
- Flash hdx-nexus-gapps-v1.2.zip
Click to expand...
Click to collapse
Is this the only iteration of the ROM for 3.2.8?
jeryll said:
Did you flash gapps?
Click to expand...
Click to collapse
That's quite embarrassing, I forgot it and now everything works perfectly, thanks.
In case anyone else has the same problem, flash the gapps stuff in safestrap
Thank you for still supporting those of us stuck with safestrap only... lol
ggow said:
*** USE AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF THINGS GO WRONG. ***
Hi GGow, I'm a complete noob to the scene, have searched around the forums. Finally got Safestrap 3.75 and SuperSU working on my Amazon Kindle Fire HDX that was downgraded to 13.3.2.8 by ACS from 4.5.2. Utilized the TowelRoot method to get rooted.
I want to make sure the installation procedure for this ROM, since I've never done one. Currently I utilized SafeStrap 3.75 and backed up my stock 13.3.2.8 ROM on the device.
The process to install this ROM would be -
1. Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
2. Flash hdx-nexus-gapps-v1.2.zip
3. Then flash any addons
4. If coming from any other ROM then do a factory reset.
5. Reboot and enjoy.
My only issue is that do I flash all of these roms like the safestrap-thor-nexus-rom.zip onto seperate slots? Or keep re-flashing the same slot? I apologize for my noobness, but I'm really new to Android Dev and rooting.
Click to expand...
Click to collapse
All same slot.
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
Just queue them all up to flash all in one shot.
camerajunkie said:
ggow said:
*** USE AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF THINGS GO WRONG. ***
Hi GGow, I'm a complete noob to the scene, have searched around the forums. Finally got Safestrap 3.75 and SuperSU working on my Amazon Kindle Fire HDX that was downgraded to 13.3.2.8 by ACS from 4.5.2. Utilized the TowelRoot method to get rooted.
I want to make sure the installation procedure for this ROM, since I've never done one. Currently I utilized SafeStrap 3.75 and backed up my stock 13.3.2.8 ROM on the device.
The process to install this ROM would be -
1. Flash safestrap-thor-nexus-rom.zip or safestrap-apollo-nexus-rom.zip
2. Flash hdx-nexus-gapps-v1.2.zip
3. Then flash any addons
4. If coming from any other ROM then do a factory reset.
5. Reboot and enjoy.
My only issue is that do I flash all of these roms like the safestrap-thor-nexus-rom.zip onto seperate slots? Or keep re-flashing the same slot? I apologize for my noobness, but I'm really new to Android Dev and rooting.
Click to expand...
Click to collapse
To add to what @gqukyo said:
1. If you intend for HDX Nexus ROM to be your main ROM and because you are on 13.3.2.8 I would make sure you take a backup of your current stock ROM.
2. Restore the backup to slot 1 . Ensure slot 1 then boots correctly
3. You can then switch back to your stock slot and follow the instructions above.
4. Otherwise if you want stock to be your main ROM then just follow the instructions as they are above after creating a new ROM slot.
Click to expand...
Click to collapse
ggow said:
camerajunkie said:
To add to what @gqukyo said:
1. If you intend for HDX Nexus ROM to be your main ROM and because you are on 13.3.2.8 I would make sure you take a backup of your current stock ROM.
2. Restore the backup to slot 1 . Ensure slot 1 then boots correctly
3. You can then switch back to your stock slot and follow the instructions above.
4. Otherwise if you want stock to be your main ROM then just follow the instructions as they are above after creating a new ROM slot.
Click to expand...
Click to collapse
Ha! I didn't even think to use the "stock rom" for any custom roms... I don't suppose it really matters does it? I did create the max 16gb for my rom slot though I did hear about people having issues installing games when it complained device didn't have enough space... if it does matter then I'd rather use the stock slot since there doesn't seem to be any other roms to try anyways.
Click to expand...
Click to collapse
I don't think he ment to replace your stock slot with custom rom.
I was wondering why would i restore stock backup to slot 1? Is this just to verify if backup works? Can i later remove it from slot 1.
It would take too much space to have a stock and slot 1 as stock and then slot 2 for nexus.
Fyi you can safely install Xposed 2.7 experimental and then activate gravitybox, and other aosp modules.
Sent from my Nexus HDX 7 using XDA Free mobile app
***PLEASE UNLOCK YOUR BOOTLOADER INSTEAD. ***
*** IF ANY OF THE INFORMATION ON THIS THREAD IS MISUSED IT CAN RESULT IN A BRICKED DEVICE ***
Introduction
- BEFORE PROCEEDING READ THROUGH CAREFULLY, IF THERE IS ANY DOUBT THEN ASK BEFORE PROCEEDING
- Safestrap provides TWRP like recovery capabilities for locked devices.
- This is based on the original work of Hashcode.
- This is for Apollo and Thor devices only.
Known Issues
- Secondary slots boot, but the WiFi module does not load
- Since the secondary slots work but have no WiFi, you will need to flash Nexus v4 to the stock slot for now
Compatible ROMS
- HDX Nexus ROM v4
- CM-11
- Fire Nexus ROM
Prerequisites for Installation
- You must be on FireOS stock firmware 4.5.2, 4.5.3, 4.5.4, 4.5.5 or 4.5.5.1 <- Please confirm this before proceeding <-
- You must have root access
Installation
- Install the app
- Grant root access if needed
- Read user agreement and accept to proceed
- Then click install recovery
- When recovery is installed click reboot to recovery
- You should eventually end up in safestrap recovery.
Download
*** Please do NOT create any mirrors ***
- Safestrap for THOR
- Safestrap for APOLLO
Thanks to my Testers
- Davey126
- kudoz83
- lekofraggle
- zamtang
- paul26rem
XDA:DevDB Information
Safestrap KK, Device Specific App for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
Version Information
Status: Stable
Current Stable Version: 4.0.1
Stable Release Date: 2015-06-18
Created 2015-06-18
Last Updated 2019-10-02
Reserved
Is there a possibility of running cm 12 in this recovery?
paul26rem said:
Is there a possibility of running cm 12 in this recovery?
Click to expand...
Click to collapse
- Not at the moment and probably not likely.
- If amazon release a FireOS based on lollipop and we get root then yes maybe.
ggow said:
- Not at the moment and probably not likely.
- If amazon release a FireOS based on lollipop and we get root then yes maybe.
Click to expand...
Click to collapse
Although I prefer AOSP/Nexus the next logical question would be CM11 as it shares common roots with FireOS v4 / Nexus v4 and at present does not require an unlocked bootloader. Actually, not sure why anyone would opt for CM11 over Nexus on HDX given the status of the two roms. Don't get me wrong - CM is great and has some nice built in functionality (all of which is obtainiable via Xposed on Nexus) but the CM11/CM12 implementations still have a few issues with the HDX variants.
Davey126 said:
Although I prefer AOSP/Nexus the next logical question would be CM11 as it shares common roots with FireOS v4 / Nexus v4 and at present does not require an unlocked bootloader. Actually, not sure why anyone would opt for CM11 over Nexus on HDX given the status of the two roms. Don't get me wrong - CM is great and has some nice built in functionality (all of which is obtainiable via Xposed on Nexus) but the CM11/CM12 implementations still have a few issues with the HDX variants.
Click to expand...
Click to collapse
I agree. Don't get me wrong, I love cm, but If you want a stable Rom, Nexus is where it's at.
Hi, I used your safetrap version on fire OS 4.5.2 rooted, when I flash rom nexus 4.0.1 on secondary slot rom, It booted greatly! But as you said, it haven't wifi module, but when I flash it in stock slot, successfully, but it only boot to splash screen and no more, do you know my error? Please help me, thanks!
One more thing, I use fire OS 14.4.5.2.2004220, not 2004120, nothing different, right?
thuyrs said:
Hi, I used your safetrap version on fire OS 4.5.2 rooted, when I flash rom nexus 4.0.1 on secondary slot rom, It booted greatly! But as you said, it haven't wifi module, but when I flash it in stock slot, successfully, but it only boot to splash screen and no more, do you know my error? Please help me, thanks!
One more thing, I use fire OS 14.4.5.2.2004220, not 2004120, nothing different, right?
Click to expand...
Click to collapse
Can you get into Safestrap recovery? If so try a 'factory reset' located under the 'wipe' option and then reboot. If that does not work return to Safestrap recovery and perform an 'advanced wipe'. Check all of the partitions (Dalvik Cache, Data, Cache, System). After wiping reinstall Nexus v4 and gaps from within Safestrap and then reboot.
A few cautions/notes:
- make sure you are working with the correct slot!
- make sure you perform the 'factory reset' from safestrap recovery - not the native Amazon recovery built into your Kindle
- gaps is important for proper operation of Nexus v4. Some low level functions (eg: the home button) do not work correctly if gaps is not flashed immediately after Nexus v4
Please post the results to others can learn from your experience. Thanks!
Hi, after I wiped everything and reinstall to slot stock, it booted, and Wifi module worked correctly, thanks for your help!
hi
does ur version of stock 4.5.2 that u attached here already rooted? or do i have to towelroot it?
thx
loco09 said:
hi
does ur version of stock 4.5.2 that u attached here already rooted? or do i have to towelroot it?
thx
Click to expand...
Click to collapse
Flash SuperSU after and you have root access.
Also you will need to block ota updates so do not enable WiFi until you have done so.
EDIT: I have just added a note to the OP about this.
Sent from my Nexus 6 using Tapatalk
I run HDX 7in ver 3.2.8 rolled back by Amazon CS with OTA blocking included, with Safestrap and Nexus 1.0.1. Why will I need to update to this and how do I do it safely?
hfpop said:
I run HDX 7in ver 3.2.8 rolled back by Amazon CS with OTA blocking included, with Safestrap and Nexus 1.0.1. Why will I need to update to this and how do I do it safely?
Click to expand...
Click to collapse
You are in a tough situation given Amazon CS performed the 3.2.8 rollback and OTA is apparently blocked using an unknown method (likely at the Amazon servers but can't be sure).
Options as follows:
1) Contact Amazon CS and request an upgrade to 4.5.2. However, they will likely upgrade to 4.5.4 which is unrootable at present. You would then need to manually rollback to 3.2.8 followed by a manual upgrade to 4.5.2. All this involves risk with the consequence being a bricked device if things go wrong.
2) Attempt to manually update to 4.5.2 which may or may not work given the OTA block. There is less risk but the consequence of a bad upgrade is equally severe (bricked tablet).
3) Stay on FireOS 3.2.8, Safestrap v3.7.x and Nexus 1.0.1 for now. Better/safer upgrade options will likely evolve with time. Nexus 1.0.1 remains quite serviceable for all but the newest applications especially when combined with Xposed Framework and Gravitybox.
I strongly advise option #3 unless you are willing to toss your Kindle in the trash if things go wrong (or are still within your 1 year warranty).
Davey126 said:
You are in a tough situation given Amazon CS performed the 3.2.8 rollback and OTA is apparently blocked using an unknown method (likely at the Amazon servers but can't be sure).
Options as follows:
1) Contact Amazon CS and request an upgrade to 4.5.2. However, they will likely upgrade to 4.5.4 which is unrootable at present. You would then need to manually rollback to 3.2.8 followed by a manual upgrade to 4.5.2. All this involves risk with the consequence being a bricked device if things go wrong.
2) Attempt to manually update to 4.5.2 which may or may not work given the OTA block. There is less risk but the consequence of a bad upgrade is equally severe (bricked tablet).
3) Stay on FireOS 3.2.8, Safestrap v3.7.x and Nexus 1.0.1 for now. Better/safer upgrade options will likely evolve with time. Nexus 1.0.1 remains quite serviceable for all but the newest applications especially when combined with Xposed Framework and Gravitybox.
I strongly advise option #3 unless you are willing to toss your Kindle in the trash if things go wrong (or are still within your 1 year warranty).
Click to expand...
Click to collapse
Just to add to what Davey126. My current understanding is that a manual upgrade does indeed work. 3.2.8 only stops the OTA updates from coming through.
after install safetrap now i got a problem, i cannot boot on stock slot, my kindle boot and stop at logo kindle fire (white - yellow). I try wipe all but nothing change. How can i copy Stock Image to the sd card to flash in stock slot, my computer does not find kindle. Please help
ChuTeng said:
after install safetrap now i got a problem, i cannot boot on stock slot, my kindle boot and stop at logo kindle fire (white - yellow). I try wipe all but nothing change. How can i copy Stock Image to the sd card to flash in stock slot, my computer does not find kindle. Please help
Click to expand...
Click to collapse
Can you still get into Safestrap?
ggow said:
Can you still get into Safestrap?
Click to expand...
Click to collapse
adb driver in my computer is problem, i fixed. Thanks.
ChuTeng said:
adb driver in my computer is problem, i fixed. Thanks.
Click to expand...
Click to collapse
Does that mean you are up and running again?
Awesome job!!!!!!!!!!
Confirmation number: 67M75398MF9375820
I'm on 4.5.4 7", any options for me? Can I contact amazon n hope they will roll me back? What version do I ask for?
Has anybody seen this "incompatible data" error when installing rom using Flashfire?
I recently purchased a fire 7 which came with fireOS 5.1.4 on it which I downgraded to 5.1.2 (verified version in settings). I used KingRoot to get root and have verified that apps require root are working. I installed Flashfire and everything appears to work fine until I select flash. I can see it does the wipes fine, but when it tries to install cyanogenmod I receive an error that says "can't install package on top of incompatible data."
Has anybody seen this issue before in flashfire? I've been looking for some time now and I seem to be alone.
Things I have tried so far (which have not changed the error is see when flashfire is flashing CM and GAPPS):
Reset device to factory defaults (in settings and through recovery; loaded into 5.1.2 like it was new however it still had root)
Sideloaded Fireos 5.1.2 again and rerooted using kingroot.
Used a different version of CM.
Used different versions of Flashfire (0.5 and 0.51)
Went through the process start to finish again using the Supertool
I've been stuck on this for the last 5 hours... Any hints would be appreciated.
Update: I've had success at flashing the Fire Nexus ROM by ggow (http://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714/). I have tried to flash the latest CM and the stable release from November without success. I suppose I might be satisfied with the nexus rom. It seems sexy enough.
LazyTurtle said:
I recently purchased a fire 7 which came with fireOS 5.1.4 on it which I downgraded to 5.1.2 (verified version in settings). I used KingRoot to get root and have verified that apps require root are working. I installed Flashfire and everything appears to work fine until I select flash. I can see it does the wipes fine, but when it tries to install cyanogenmod I receive an error that says "can't install package on top of incompatible data."
Has anybody seen this issue before in flashfire? I've been looking for some time now and I seem to be alone.
Things I have tried so far (which have not changed the error is see when flashfire is flashing CM and GAPPS):
Reset device to factory defaults (in settings and through recovery; loaded into 5.1.2 like it was new however it still had root)
Sideloaded Fireos 5.1.2 again and rerooted using kingroot.
Used a different version of CM.
Used different versions of Flashfire (0.5 and 0.51)
Went through the process start to finish again using the Supertool
I've been stuck on this for the last 5 hours... Any hints would be appreciated.
Update: I've had success at flashing the Fire Nexus ROM by ggow (http://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714/). I have tried to flash the latest CM and the stable release from November without success. I suppose I might be satisfied with the nexus rom. It seems sexy enough.
Click to expand...
Click to collapse
Quick post to verify you are including a wipe action in FlashFire 0.51 with System, User Data, Dalvik and Cache ticked positioned *above* the rom flash action.
Same problem
Davey126 said:
Quick post to verify you are including a wipe action in FlashFire 0.51 with System, User Data, Dalvik and Cache ticked positioned *above* the rom flash action.
Click to expand...
Click to collapse
I am not OP, but I am having a similar problem after a failed ROM installation. I can verify that when I tried the steps listed, it did not work. The Nexus build, while quite nice, doesn't support loading apps onto the SD card yet, so it's not a long term solution for me.
SimonHova said:
I am not OP, but I am having a similar problem after a failed ROM installation. I can verify that when I tried the steps listed, it did not work. The Nexus build, while quite nice, doesn't support loading apps onto the SD card yet, so it's not a long term solution for me.
Click to expand...
Click to collapse
Lollipop based support for installing/migrating apps to SD cards is sketchy regardless of rom. Recommend using a tool that leverages 'symbolic links' which is both reliable and robust. Link2SD is one example.
I am having this exact same problem.
I've successfully downgraded from 5.1.3 to 5.1.2.
ROOT
Now using fireflash I am using the newest CM12 build and Google apps but get the same problem.
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
Very frustrating....
Havent tried the Nexus rom yet, but any suggestions as the best alternative to CM as i also do not like the fireOS at all.
ratbrain said:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
Click to expand...
Click to collapse
Did you add a wipe action (system/data/dalvik/cache) *above* the installation action in FlashFire? Pretty important going to/from FireOS.
Davey126 said:
Did you add a wipe action (system/data/dalvik/cache) *above* the installation action in FlashFire? Pretty important going to/from FireOS.
Click to expand...
Click to collapse
Yes. made sure to drag wipe action to top of the queue.
THis puts my fire into boot loop/ amazon logo stuck status
ratbrain said:
Yes. made sure to drag wipe action to top of the queue.
THis puts my fire into boot loop/ amazon logo stuck status
Click to expand...
Click to collapse
Obviously CM is not flashing correctly. You will need to reload FireOS 5.1.2 (or 5.3.1) via stock recovery to recover your device.
CM flash failures are not common suggesting a procedural or image integrity problem. Be sure to verify CM file md5 on the device. Use the SuperTool to root and perform other house keeping tasks. Grab the latest FlashFire build from APKMirror or another trusted source. Accept all defaults...some early guidance advised flipping various FF options which is no longer needed. You'll also want to flash GAaps (nano) concurrent with ROM; adding later is problematic. No need for SuperSU; can add later.
Davey126 said:
Obviously CM is not flashing correctly. You will need to reload FireOS 5.1.2 (or 5.3.1) via stock recovery to recover your device.
CM flash failures are not common suggesting a procedural or image integrity problem. Be sure to verify CM file md5 on the device. Use the SuperTool to root and perform other house keeping tasks. Grab the latest FlashFire build from APKMirror or another trusted source. Accept all defaults...some early guidance advised flipping various FF options which is no longer needed. You'll also want to flash GAaps (nano) concurrent with ROM; adding later is problematic. No need for SuperSU; can add later.
Click to expand...
Click to collapse
I've confirmed the files.
Using latest CM 12 ROM
Using FlashFire 0.53
Only difference Ive used is PICO Gapps.
All after restoring back to 5.1.2
Then ROOT with SuperTool
Note: per the OP, I am also successful in loading the NEXUS ROM. However, the CM Rom always ends up with the error.
ratbrain said:
I've confirmed the files.
Using latest CM 12 ROM
Using FlashFire 0.53
Only difference Ive used is PICO Gapps.
All after restoring back to 5.1.2
Then ROOT with SuperTool
Note: per the OP, I am also successful in loading the NEXUS ROM. However, the CM Rom always ends up with the error.
Click to expand...
Click to collapse
If you're happy with Nexus stick with it. It is my favorite rom for Amazon tablets and the one I prefer as my daily driver. I run CM on this device (5th gen Fire) as it is secondary and contains some nice usability enhancements that take time to apply on Nexus.
As for CM have to see what shakes out over time. Others are not reporting issues; send 3-4 reports of successful installations in the past 24 hours. At least one was on a 5.1.2 base (bootloader/kernel).
Before rooting/removing ads etc, I want to use the phone for a week or so stock so Ill have a baseline to compare it to.
Would it be OK to let the phone update fully while using it? I know with some devices (Amazon kindle) if you update it to a certain point, then there is no going back and the bootloader gets locked.
Lemme know what you think.
lourivellini said:
Before rooting/removing ads etc, I want to use the phone for a week or so stock so Ill have a baseline to compare it to.
Would it be OK to let the phone update fully while using it? I know with some devices (Amazon kindle) if you update it to a certain point, then there is no going back and the bootloader gets locked.
Lemme know what you think.
Click to expand...
Click to collapse
If you allow it to update, you will not be able to unlock bootloader, so if you want to root do not update.
The latest update has been posted in this forum, so you are not missing any of the update by rooting either.
mrmazak said:
If you allow it to update, you will not be able to unlock bootloader, so if you want to root do not update.
The latest update has been posted in this forum, so you are not missing any of the update by rooting either.
Click to expand...
Click to collapse
Is the root junky method still good?
https://youtu.be/KMobKWfZbJg
Or should I follow a different guide? I know some of his files on his website are outdated.
I also am having a problem when trying to use the flashtool. When I plug my phone in powered off, at first it says the battery is low no matter what, then disconnects, then says 95% or whatever it is. This is preventing me from using flashtool when in download mode.
Any idea why this is happening? My r1 hd is on 6.0 btw
lourivellini said:
Is the root junky method still good?
https://youtu.be/KMobKWfZbJg
Or should I follow a different guide? I know some of his files on his website are outdated.
I also am having a problem when trying to use the flashtool. When I plug my phone in powered off, at first it says the battery is low no matter what, then disconnects, then says 95% or whatever it is. This is preventing me from using flashtool when in download mode.
Any idea why this is happening? My r1 hd is on 6.0 btw
Click to expand...
Click to collapse
All the R1-HD line is on Android 6.0
The Blu release version is what changes.
I believe this was the order
6.1
6.4
6.5
6.6
7.4.2
8.3
8.4
The flashtool stopped working at v6.6
The new method was the use dirty cow. There is a tool thread for directions.
This new method stopped working at v8.3
mrmazak said:
All the R1-HD line is on Android 6.0
The Blu release version is what changes.
I believe this was the order
6.1
6.4
6.5
6.6
7.4.2
8.3
8.4
The flashtool stopped working at v6.6
The new method was the use dirty cow. There is a tool thread for directions.
This new method stopped working at v8.3
Click to expand...
Click to collapse
So the phone is brand new from Amazon, haven't touched it or even connected it to the internet. Not home right now, but I remember seeing software version 6.0 not Android 6.0.
Anyways, I guess I should look into the dirty cow method. Do you have the link?
Sent from my Moto G (5) Plus using Tapatalk
lourivellini said:
So the phone is brand new from Amazon, haven't touched it or even connected it to the internet. Not home right now, but I remember seeing software version 6.0 not Android 6.0.
Anyways, I guess I should look into the dirty cow method. Do you have the link?
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333
mrmazak said:
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333
Click to expand...
Click to collapse
Thanks
Sent from my Moto G (5) Plus using Tapatalk
mrmazak said:
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333
Click to expand...
Click to collapse
Is there a ROM i should flash afterwards?
I just installed twrp using the dirty cow method (steps 1-4), and then also did step 5-1 (install supersu).
At this point, in the past Ive always just flashed a brand new rom and gapps. Is there a "stock" rom that I should flash with twrp - which is just the stock rom with no ads? And which build should I? Im on 6.6 right now.
Ive read that lineage has some problems with the camera - no big deal ill roll will the stock non-ad rom for now.
Thanks again!
lourivellini said:
Is there a ROM i should flash afterwards?
I just installed twrp using the dirty cow method (steps 1-4), and then also did step 5-1 (install supersu).
At this point, in the past Ive always just flashed a brand new rom and gapps. Is there a "stock" rom that I should flash with twrp - which is just the stock rom with no ads? And which build should I? Im on 6.6 right now.
Ive read that lineage has some problems with the camera - no big deal ill roll will the stock non-ad rom for now.
Thanks again!
Click to expand...
Click to collapse
So the non-prime ROMs latest is v21 it comes with none of the prime ads.
Or v8.4 that came with the ads but they were removed. .some have said n-ify not working on 8.4 but does on 21. I do not know first hand.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
You will have to do SuperSU again after the rom
mrmazak said:
So the non-prime ROMs latest is v21 it comes with none of the prime ads.
Or v8.4 that came with the ads but they were removed. .some have said n-ify not working on 8.4 but does on 21. I do not know first hand.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
You will have to do SuperSU again after the rom
Click to expand...
Click to collapse
Last question(s):
So I installed V21, supersu, removed ALL amazon with dirtycow.
1. Is my phone now disabled from receiving OTA updates? Or do I have to do something else to make sure auto updates are OFF.
2. Is there a way to remove this stupid blu app (blu help) that keep requiring me to register my device? Every time I power on I have to force stop the app or I have a constant notification to do it.
Thanks again!
lourivellini said:
Last question(s):
So I installed V21, supersu, removed ALL amazon with dirtycow.
1. Is my phone now disabled from receiving OTA updates? Or do I have to do something else to make sure auto updates are OFF.
2. Is there a way to remove this stupid blu app (blu help) that keep requiring me to register my device? Every time I power on I have to force stop the app or I have a constant notification to do it.
Thanks again!
Click to expand...
Click to collapse
The debloat done with the tool supposed to have disabled the ota checker program.
And as a second method of not getting ota, having twrp and root will also make the ota fail even if it was to download.
The Blu app is called warrenteer. What I do is belete the whole folder.
/system/priv-app/warrenteer
You can take baby steps and just rename the apk inside that folder to add "-" or "_" to end of it's name
This can be done with a root explorer app or with recovery file manager. Either way.
Hi all after trying hundreds of different roms on my old nexus. I think i have found the best way to boost the speed. I'm using xenonhd 5.1.1 with parrot mod and M-kernels. ??
Trying it out right now and it seems snappy. But I am using f2fs version of Xenonhd without the M kernel.
Give the xenonhd please...
Links please
GrandLuLu said:
Give the xenonhd please...
Click to expand...
Click to collapse
Sab3elbromba said:
Links please
Click to expand...
Click to collapse
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
"Lightning fast" and "Nexus 7 2012" are not normally used in the same sentence.
Maybe I'll have to give this a try. I've kept mine on stock KitKat, and it's dog slow.
Are you using SuperSU as recommended by ParrotMod, or does it work with Magisk? Thanks.
Edit: To answer my own question, it seems to work fine with Magisk.
so, you have to downgrade the bootloader to use this?
beside that, in the xenonhd thread someone said .. after u install some apps you'll get the same slow down like on every other rom
https://forum.xda-developers.com/showpost.php?p=69949425&postcount=1817
I just got myself a new Nexus 7 and all i've done is run the updates up to 5.1 as 5.1.1 fails to install.
It is pretty slow and crashes a lot, I don't remember it being this laggy and slow when I first got one in 2012. Is it just a function of the new OS's or the new apps? What is the best build to be in for speed? I don't mind losing some of the newer features of the OS. Would just prefer something I can use without being frustrated...
Thanks
Sorry to ask this, but can the nexus 7 2012 roms be used on a nexus 7 3g 2012? are they the same? I am new to this model, I am about to buy one (just as ereader), but would like to have the best rom on it.
jbaumert said:
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
Click to expand...
Click to collapse
The latest version update-XenonHD-09-13-15 is not available anymore. If anyone that has the files could share.
I was also pointed to try this rom: https://forum.xda-developers.com/nexus-7/development/rom-android-7-aosp-grouper-t3467514
And this one, but again no working links https://forum.xda-developers.com/showthread.php?t=2784244
I will buy today a Nexus 7 3G 2012 very cheap, so I will try some roms on it.
skinniezinho said:
Sorry to ask this, but can the nexus 7 2012 roms be used on a nexus 7 3g 2012? are they the same? I am new to this model, I am about to buy one (just as ereader), but would like to have the best rom on it.
Click to expand...
Click to collapse
To use a "Grouper" ROM on the "Tilapia / 3g" device, you just need to flash the Grouper ver of TWRP recovery. Granted, you will not have use of the 3g radio, but otherwise it will function normally.
jbaumert said:
To use a "Grouper" ROM on the "Tilapia / 3g" device, you just need to flash the Grouper ver of TWRP recovery. Granted, you will not have use of the 3g radio, but otherwise it will function normally.
Click to expand...
Click to collapse
Thanks. The device comes with 4.2.2 should I flash first 5.1.1 (in order to update radios and stuff) and then root=>recovery=>rom? Or should I just root it in 4.2.2?
If anyone have the older files that I pointed I would appreciate, I will test them and leave my feedback.
I would download the last "official" update from Google for your device (Tilapia I'm assuming), and manually flash the radio and bootloader with fastboot. (Granted, you could install the entire update, but why bother if you're going to put on a custom ROM anyways) Then, unlock the bootloader (if not already done) install TWRP recovery and flash away.
Anyone tested this ROM yet (with a bunch of apps installed to see if slows down or not) ?
jbaumert said:
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
Click to expand...
Click to collapse
The download links are dead. :crying:
Jaguar10301 said:
I just got myself a new Nexus 7 and all i've done is run the updates up to 5.1 as 5.1.1 fails to install.
It is pretty slow and crashes a lot, I don't remember it being this laggy and slow when I first got one in 2012. Is it just a function of the new OS's or the new apps? What is the best build to be in for speed? I don't mind losing some of the newer features of the OS. Would just prefer something I can use without being frustrated...
Thanks
Click to expand...
Click to collapse
Root it and load RootBooster and choose the last option..
andynroid said:
Root it and load RootBooster and choose the last option..
Click to expand...
Click to collapse
I have a 2012 Nexus 7 running Resurrection Remix M (Android 6.0.1), and I can say that RootBooster *does* help. My N7 was *very* laggy and slow to respond when tapping on anything. I chose "Basic Mode -- Speed", re-booted and it's a LOT faster now. Time will tell if it lasts.
I've had MultiROM and TWRP on this tablet for quite awhile, so I also have RR-N installed as a secondary ROM. I'm going to try RootBooster on that ROM also.
I have a Nexus 7 2012 wifi model and need it strictly for Chromecast audio to control Pandora and Spotify.
What's the best rom for that?
Don't care for anything else really...
I installed the setup mentioned by the OP on my Nexus 7 2012, and it is working well so far. Thank you OP.
Initially I tried to use the kernel that is included with the XenonHD ROM, but it seemed to have issues with lag, not waking from sleep, etc. Then I switched to M Kernel and it was much better, so switching the kernel is necessary in my opinion.
Links:
Main XenonHD thread:
https://forum.xda-developers.com/showthread.php?t=1826484
XenonHD download:
The main download link in post #2 of the above thread doesn't seem to contain the download anymore. But if you go to the "Older builds" link, you can find the 08-20-15 build there. Here is a direct link.
https://androidfilehost.com/?fid=24052804347797659
M kernel:
I used the latest a77 version available from the main M Kernel thread here:
https://forum.xda-developers.com/showthread.php?p=38551156
ParrotMod:
I used the universal version available from the main ParrotMod thread here.
https://forum.xda-developers.com/ne...arrotmod-speed-2012-nexus-7-emmc-fix-t3300416
GApps:
I used the "nano" version from Open GApps:
http://opengapps.org/
Magisk:
Main thread and downloads here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
My Procedure:
I was starting with stock rooted Android 4.4.4. I had previously used the WugFresh toolkit to root and install twrp. If you have something older or custom, you may need to flash a recent stock rom first to update your bootloader.
1) Update to current version of twrp. I used the twrp app from the play store.
2) Boot into twrp. Factory reset.
3) Boot into Android.
4) Download XenonHD, M Kernel, ParrotMod, and GApps files to PC, transfer to tablet via USB. (or download on tablet)
5) Boot into twrp. Wipe everything except internal storage.
6) Install XenonHD, M Kernel, ParrotMod, GApps
7) Boot into Android. Be patient, first boot takes a while
I also replaced SuperSU with Magisk, because I don't consider recent non-Chainfire versions of SuperSU to be trustworthy. To do this:
1) Download Magisk and Magisk Manager to PC, transfer to tablet via USB. (or download on tablet)
2) Open SuperSU settings, select option to uninstall and prepare for alternate su manager.
3) Reboot to TWRP. Flash Magisk. Wipe cache/davlik (not sure this is necessary). Reboot to Android. IMPORTANT: If twrp says device does not appear to be rooted and prompts you to install SuperSU, you must decline.
4) In Android, install Magisk manager.
Hope this helps someone else.
spocko said:
I installed the setup mentioned by the OP on my Nexus 7 2012, and it is working well so far. Thank you OP.
Initially I tried to use the kernel that is included with the XenonHD ROM, but it seemed to have issues with lag, not waking from sleep, etc. Then I switched to M Kernel and it was much better, so switching the kernel is necessary in my opinion.
Links:
Main XenonHD thread:
https://forum.xda-developers.com/showthread.php?t=1826484
XenonHD download:
The main download link in post #2 of the above thread doesn't seem to contain the download anymore. But if you go to the "Older builds" link, you can find the 08-20-15 build there. Here is a direct link.
https://androidfilehost.com/?fid=24052804347797659
M kernel:
I used the latest a77 version available from the main M Kernel thread here:
https://forum.xda-developers.com/showthread.php?p=38551156
ParrotMod:
I used the universal version available from the main ParrotMod thread here.
https://forum.xda-developers.com/ne...arrotmod-speed-2012-nexus-7-emmc-fix-t3300416
GApps:
I used the "nano" version from Open GApps:
http://opengapps.org/
Magisk:
Main thread and downloads here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
My Procedure:
I was starting with stock rooted Android 4.4.4. I had previously used the WugFresh toolkit to root and install twrp. If you have something older or custom, you may need to flash a recent stock rom first to update your bootloader.
1) Update to current version of twrp. I used the twrp app from the play store.
2) Boot into twrp. Factory reset.
3) Boot into Android.
4) Download XenonHD, M Kernel, ParrotMod, and GApps files to PC, transfer to tablet via USB. (or download on tablet)
5) Boot into twrp. Wipe everything except internal storage.
6) Install XenonHD, M Kernel, ParrotMod, GApps
7) Boot into Android. Be patient, first boot takes a while
I also replaced SuperSU with Magisk, because I don't consider recent non-Chainfire versions of SuperSU to be trustworthy. To do this:
1) Download Magisk and Magisk Manager to PC, transfer to tablet via USB. (or download on tablet)
2) Open SuperSU settings, select option to uninstall and prepare for alternate su manager.
3) Reboot to TWRP. Flash Magisk. Wipe cache/davlik (not sure this is necessary). Reboot to Android. IMPORTANT: If twrp says device does not appear to be rooted and prompts you to install SuperSU, you must decline.
4) In Android, install Magisk manager.
Hope this helps someone else.
Click to expand...
Click to collapse
The Gapps don't seem to fit on the standard storrage anymore. Did you enlarge the system storage?
Nevermind, found what I didn wrong. Thanks for your post where you gather all the info
Strormrage said:
The Gapps don't seem to fit on the standard storrage anymore. Did you enlarge the system storage?
Nevermind, found what I didn wrong. Thanks for your post where you gather all the info
Click to expand...
Click to collapse
What was it in your case?