[DISCONTINUED][AOSP][6.0.1] Fire Nexus ROM - [SUBSTRATUM] [M4B30X] [22 Oct 2016]

[ggow]

Fire Nexus ROM​

Introduction
This ROM is based off AOSP marshmallow. I have merged changes from CAF and Cyanogenmod to enable this boot on our HDX devices.

Features
- AOSP with optimisations from CAF
- Open GAPPS nano is built-in
- Clear all recents
- Advanced Power Menu
- Substratum Theming Support
- Init.d Support
- SuperSU is built-in

Prerequisites for Installation
- Unlocked bootloader is a must
- TWRP 3.0.2-0 installed
- This does NOT work with Safestrap

Downloads
*** Please do NOT create any mirrors ***
- Fire Nexus ROM for APOLLO
- Fire Nexus ROM for THOR

Issue List
- Sideloading of some apps may be necessary
- Bluetooth
- LTE
- WiFi may need to be manually toggled after wakeup

Kernel Source Code
- https://github.com/CyanogenMod/android_kernel_amazon_hdx-common

Credits
- AOSP
- CodeAurora Forum
- Cyanogenmod
- Substratum Team

XDA:DevDB Information
mm-fire-nexus-rom, ROM for the Amazon Kindle Fire HDX 7" & 8.9"

Contributors
ggow
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP

Version Information
Status: Testing

Created 2016-10-22
Last Updated 2019-10-02

 

[ggow]

Release Notes / Change log

22 October 2016
- Initial Release
- Xposed needs testingConfirmed as working

 

[schr01]

Thank you for this new rom. I have testet it with the open camera app, but it showes me a picture whith a rotation error (180 degrees).

 

[ggow]

Thank you for this new rom. I have testet it with the open camera app, but it showes me a picture whith a rotation error (180 degrees).

Yes, rotation is a problem. If I remember rightly it is the same issue as with other custom ROMS. Try locking the screen rotation in the correct aspect then running open camera again. The app should then appear correctly.

 

[schr01]

Thank you for your tip. It works.

 

[DB126]

Woohoo!

Initial findings after a quick 15 min test:
- clean flashed (Thor) with Xposed 23; booted fine (wiped system/data/cache/dalvik)
- installed a handful of essential apps from Play Store - no compatibility issues
- installed GravityBox 6.1.6 and tested a few tweaks that tend to be problematic on some devices/roms - no issues
- big test: installed my preferred messaging app which hates everything including no-SIM devices - worked perfectly!!

Very excited on first take! Sadly, rom hangs w/dirty flash or if CM 12.1 data partition restored after initial boot. Will need to fall back temporarily until I have time to perform a manual migration of existing app portfolio. No ding against the rom; dirty flashes are always a crap shoot and I have been bringing this one forward since Jelly Bean (yikes!). I have an old Fire Nexus KitKat build I may try too. Hate rebuilding from scratch.

The only (minor) suggestion is to include recovery and soft boot options to the Advanced Power Menu. No big deal as I can easily get this from Xposed; just seems a natural as it was noted in the feature set (not normally part of AOSP). Love having GAaps Nano and SuperSU built in; avoids many initial flash headaches and simplifies upgrades.

Really nice work, @ggow. Clean and simple.

Edit: I did need to enable 'all rotations' in GravityBox as expected on this device. Likely could achieve the same result via Nova or other third party tweak. Native setting was largely ignored.

 

[ggow]

Initial findings after a quick 15 min test:
- clean flashed (Thor) with Xposed 23; booted fine (wiped system/data/cache/dalvik)
- installed a handful of essential apps from Play Store - no compatibility issues
- installed GravityBox 6.1.6 and tested a few tweaks that tend to be problematic on some devices/roms - no issues
- big test: installed my preferred messaging app which hates everything including no-SIM devices - worked perfectly!!

Good to hear Xposed is working and your problematic messaging app

Very excited on first take! Sadly, rom hangs w/dirty flash or if CM 12.1 data partition restored after initial boot. Will need to fall back temporarily until I have time to perform a manual migration of existing app portfolio. No ding against the rom; dirty flashes are always a crap shoot and I have been bringing this one forward since Jelly Bean (yikes!). I have an old Fire Nexus KitKat build I may try too. Hate rebuilding from scratch.

I would expect CM 12.1 data restore to not work. The framework in this ROM is very different from CM 12.1.
You might also run into problems dirty flashing from the KitKat build of the ROM.
Clean flash would be recommended in both cases when coming from an older or different ROM.

The only (minor) suggestion is to include recovery and soft boot options to the Advanced Power Menu. No big deal as I can easily get this from Xposed; just seems a natural as it was noted in the feature set (not normally part of AOSP). Love having GAaps Nano and SuperSU built in; avoids many initial flash headaches and simplifies upgrades.

Kids sometimes use my tablet so having the reboot to recovery options etc can be a problem.

Really nice work, @ggow. Clean and simple.

Edit: I did need to enable 'all rotations' in GravityBox as expected on this device. Likely could achieve the same result via Nova or other third party tweak. Native setting was largely ignored.

Thanks for the detailed feedback :good:

 

[ish.org]

Thank you for nexus rom.

Thank you for nexus rom.
It works almost good for me, but google contacts cannot synchronize gmail account.
In nexus5 (6.0.1), it can be synchronized by contacts->settings->accounts->google.
In thor, contacts->settings->accounts->(not shown google).

 

[rootnooby]

Will the install work with twrp 2.8.7 or is 3.0.2 a requirement?

 

[DB126]

Will the install work with twrp 2.8.7 or is 3.0.2 a requirement?

FWIW - install worked fine on 3.0.0.x (3.0.2 has permission issues)

 

[DB126]

ADB Backup/Restore

May have found a bug: adb backup and restore commands are ignored. Command is accepted (Win 10 x64 host) but no response from device. Other adb commands appear to work fine. Tinkered with the various USB modes but behavior is always the same. Also tried setting/clearing device debug password. With no password there is a 3-4 sec delay before returning to command prompt; with a password exit is nearly instantaneous. Did some searching online but not a lot of good info on the net. Works on CM 12.1 build (Thor).

Anyone else experiencing this?

 

[schr01]

I had no installations problemes with TWRP 3.02.

 

[ggow]

May have found a bug: adb backup and restore commands are ignored. Command is accepted (Win 10 x64 host) but no response from device. Other adb commands appear to work fine. Tinkered with the various USB modes but behavior is always the same. Also tried setting/clearing device debug password. With no password there is a 3-4 sec delay before returning to command prompt; with a password exit is nearly instantaneous. Did some searching online but not a lot of good info on the net. Works on CM 12.1 build (Thor).

Anyone else experiencing this?

Will take a look, before the next release.

 

[DB126]

Will take a look, before the next release.

Thanks. Two reasons for wanting this:
- transfer apps and all associated data between devices
- create targeted backups or nandroid clone on devices with limited internal storage

Titanium used to be the go-to choice but it hasn't been updated in nearly two years (struggles on Android 6+) and also utilises adb functions for transport.

 

[DB126]

FYI - I was able to get this rom to dirty boot a CM 13 build but that's as far as it went. Processor pegged on lock screen judging from heat and sluggish response (5+ sec per key press). Obviously a clean flash is highly recommended by dev but was looking for a path to bring my existing CM 12.1 build (apps and data) forward. Probably hang out on Lollipop for awhile as it meets my needs with no meaningful loss of functionality vs Marshmallow with Greenify, Nova and a few Xposed modules thrown in.

Might give Nexus 6 another whirl once adb backup/restore is working (see previous posts for background). I do miss AOSP ...

Also sad CyanogenMod can't get their act together and fix the ridiculous bug that throws up a fur ball when SIM access is requested on CM 13 if there ain't no SIM card installed (hello...tablets!!). Regression was introduced in a nightly build last March and never resolved.

 

[pxrave]

Camera isn't working on apollo

 

[chipsugar]

@ggow Nice to see the work you're doing for the hdx. I'm just curious - before I decide to upgrade to this- are there any plans to get Bluetooth stable on this ROM or is it going to have the same issues as on other ROMs. Thanks.

 

[ggow]

@ggow Nice to see the work you're doing for the hdx. I'm just curious - before I decide to upgrade to this- are there any plans to get Bluetooth stable on this ROM or is it going to have the same issues as on other ROMs. Thanks.

I have been looking into Bluetooth as I need this working too. But with these new versions of android running with old binaries, it becomes really difficult to get everything working as it should.

 

[rootnooby]

FWIW - install worked fine on 3.0.0.x (3.0.2 has permission issues)

Installed with 2.8.7, Apollo, with no issue!

 

[paragon1a]

My Apollo was on 4.5.5.1, then installed with Safestrap v4, and then Fire Nexus KK ROM. After waiting weeks for the 1-Click bootloader unlock tool, I finally decided to go for the step-by-step unlock procedure and managed to have my Apollo unlocked yesterday afternoon.

I clean flashed your TWRP 3.0.2.0 and this Fire Nexus MM ROM immediately after unlock and am really pleased with the new ROM and the newly found freedom. The ROM works quite well so far except for 1) camera (tried Snap Camera and Camera MX), 2) Google Contacts cannot sync with Gmail account.

As I came over from SafeStrap v4, is there any old files and folders need to be tidy up?