[discontinued][ROM][unlocked][ford,austin] Fire Nexus ROM [26 MAY 2019]

Status
Not open for further replies.
Search This thread

tyderian

Member
Oct 23, 2010
25
4
Checked out this thread for the first time in about a year and I see the ROM has been updated!

Having bootloops trying to install the May 3rd release (ford). Tablet was working properly before. I have an old model that's never had the bootloader updated and am able to use TWRP.

Getting bootloops even with a clean flash. I was able to go back to the previous release (2018-06-02) and got it working with nano gapps. Then I tried dirty flashing the May 3rd on top of it, that bootloops too.

Any ideas?

Edit to add: Now that I'm poking around a bit, I remember having issues a couple years ago where I had to use a "standalone build" of the ROM to get it to work...any relevance? Since I'm trying to clean flash I wouldn't think so.
 
Last edited:

nirogu325

Senior Member
Oct 15, 2010
3,557
1,882
Amazon Fire HD 8 and HD 10
Amazon Fire
I have performed dirty flashes on my two Fires without issues.
It was a suggestion. I like guaranteed stability down the line and so I like clean flashing. Nothing wrong with that.

---------- Post added at 08:08 AM ---------- Previous post was at 08:03 AM ----------

Any ideas?
Original post's prerequisites was updated as well. Newer releases require an unlocked bootloader. Procedure to do so is in another thread if you look around. If reluctant to unlock the bootloader, you may stay on the 2018 releases.
 

silverstream

Senior Member
Sep 24, 2009
759
70
Unlocked bootloader only releases from now on. DON'T dare flash if you haven't unlocked your tablet's bootloader (there's a thread for that procedure, look around). If reluctant to unlock the bootloader, stick with 2018 releases. If you already unlocked your bootloader then you already have the latest TWRP to flash this ROM and that negates the need for Flashfire. Since lots of stuff changed in the transition, I recommend a clean flash.

I've forgotten if I ever unlocked my bootloader. I know I've no TWRP and I'm using previous 2018 version of this ROM and used FlashFire...

I am worried taking a wrong step and brick it. It'll be great to have instructions for upgraders like myself
 

nirogu325

Senior Member
Oct 15, 2010
3,557
1,882
Amazon Fire HD 8 and HD 10
Amazon Fire
Gotcha, I think it's been so long that I've played with the tablet I forgot that being able to boot TWRP over fastboot doesn't mean the bootloader is unlocked.

So in theory I should be able to perform https://forum.xda-developers.com/showpost.php?p=78898974&postcount=1, correct? And I'm on an older firmware so I should be able to use recovery mode without needing the downgrade procedure?
I've forgotten if I ever unlocked my bootloader. I know I've no TWRP and I'm using previous 2018 version of this ROM and used FlashFire...

I am worried taking a wrong step and brick it. It'll be great to have instructions for upgraders like myself
I'm afraid this is not the right thread for those questions. Referring you both to the right one: https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860

...and again, if reluctant, stay with the 2018 releases.
 
  • Like
Reactions: silverstream

toasterboy1

Senior Member
Sep 18, 2013
200
45
Coming over from your lineageos build. Thank you for this ROM. Perfect for my kids' tablets. Freed up so much room. Was a little shocked there was no camera or gallery app but that just leaves it open to user preference. Keep up the good work. Wifi seems better on this build.
 

leaskovski

Senior Member
Mar 31, 2006
489
20
I have to say, this is awesome. Now that my kids tablets are exploited and have this ROM installed, they are a thousand times better!

The only niggle I have at the moment is location services. I cannot seem to get it to work. I know the device doesn't have GPS, but I thought that the old wifi based LS would work. For some reason I cannot seem to get it to work. I had a search through the thread and found this comment that suggests that it isn't working...
https://forum.xda-developers.com/am...m-fire-nexus-rom-lmy49f-t3300714/post65214421
...and that was back in 2016. The release notes in the first post, don't seem to suggest it has ever been fixed. Am I being stupid?
 

DB126

Senior Member
Oct 15, 2013
15,259
10,037
Amazon Fire HD 8 and HD 10
Google Pixel 4a
I have to say, this is awesome. Now that my kids tablets are exploited and have this ROM installed, they are a thousand times better!

The only niggle I have at the moment is location services. I cannot seem to get it to work. I know the device doesn't have GPS, but I thought that the old wifi based LS would work. For some reason I cannot seem to get it to work. I had a search through the thread and found this comment that suggests that it isn't working...
https://forum.xda-developers.com/am...m-fire-nexus-rom-lmy49f-t3300714/post65214421
...and that was back in 2016. The release notes in the first post, don't seem to suggest it has ever been fixed. Am I being stupid?
It is difficult to secure Google's location services (included in Play Services) working/stable on Fire 7s. I believe @DragonFire1024 found a way via hacks/trickery; give him a day or two to respond.
 
  • Like
Reactions: leaskovski
I have to say, this is awesome. Now that my kids tablets are exploited and have this ROM installed, they are a thousand times better!

The only niggle I have at the moment is location services. I cannot seem to get it to work. I know the device doesn't have GPS, but I thought that the old wifi based LS would work. For some reason I cannot seem to get it to work. I had a search through the thread and found this comment that suggests that it isn't working...
https://forum.xda-developers.com/am...m-fire-nexus-rom-lmy49f-t3300714/post65214421
...and that was back in 2016. The release notes in the first post, don't seem to suggest it has ever been fixed. Am I being stupid?

Google uses AGPS, it's a function but into the framework, it's used in all of their apps that use location based services. At the heart of that is fused location, it's tied into a device on an individual basis and removing it is fatal to location services across the device and cannot be fixed without reflashing stock. It sends the location to play services (com.google.android.gms). With that said, the only way Amazon's could stop Google's location services without breaking it, was to remove com.google.android.gms from the framework-res. It's literally one string. I can fix it on fire OS up to 5.6.2.0. I'm having trouble with the lastest releases. Amazon may have added some clutter to the apks and apktool reads them as errors. I haven't been able to recompile one from anything above 5.6.2.0. until then the various other hacks and tricks are give and take. Sometimes they work and other times they don't. without reading that to the framework the easiest way is to install Google app, chrome, maps and an app like a weather app. Turn off location services and open weather app. If a window to turn location on doesn't pop up, then open maps and the same thing should happen again if it doesn't pop up open Google and so on. With location services turned off opening one of those to a part that asks for location a pop-up will appear asking you to confirm to turn it on.
 
  • Like
Reactions: leaskovski

Signor Rossi

Senior Member
Sep 13, 2013
484
74
Hey guys,

sorry it's the first time I'm working with the Device again and I'm a bit lost. It's in boot-loop now and I don't know how to go on from here. Fastboot and sideload is available...

Plz help me :)
 

tyderian

Member
Oct 23, 2010
25
4
Hey guys,

sorry it's the first time I'm working with the Device again and I'm a bit lost. It's in boot-loop now and I don't know how to go on from here. Fastboot and sideload is available...

Plz help me :)

Most likely your device is on a later Amazon firmware. The newest version of this ROM requires the 5.0.1 firmware and unlocked bootloader.

Try flashing the 2018 build (same download link in the original post) instead.
 

DB126

Senior Member
Oct 15, 2013
15,259
10,037
Amazon Fire HD 8 and HD 10
Google Pixel 4a
Err.. It only requires unlocked BL.. The firmware does not matter.
For clarity, Nexus builds dated 2018 and earlier will install on rooted 5th gen 7" Fire devices (aka Ford) with the bootloader packaged with FireOS 5.3.2.0 and below.

There is no safe FireOS downgrade path for devices running FireOS 5.3.2.1 and above. However ....

The most recent Nexus builds (2019 forward) require an unlocked bootloader but are completely independent of FireOS version or hardware generation (works on both 5th and 7th gen 7" devices).

tl;dr - unlock the bootloader if you want to install the latest Fire Nexus ROM.
 
Last edited:
  • Like
Reactions: Signor Rossi

Rortiz2

Senior Member
Mar 1, 2018
2,034
1,241
Barcelona
But part of the process of unlocking is downgrading to 5.0.1.

I can see how that wasn't clear from my previous post, though.

Downgrades some partitions like tz and lk but not the system...

---------- Post added at 03:18 PM ---------- Previous post was at 03:17 PM ----------

For clarity, Nexus builds dated 2018 and earlier will install on rooted 5th gen 7" Fire devices (aka Ford) with the bootloader packaged with FireOS 5.3.2.0 and below.

There is no safe FireOS downgrade path for devices running FireOS 5.3.2.1 and above. However ....

The most recent Nexus builds (2019 forward) require an unlocked bootloader but are completely ndependent of FireOS version or hardware generation (works on both 5th and 7th gen 7" devices).

tl;dr - unlock the bootloader if you want to install the latest Fire Nexus ROM.

This is what I said... I don't understand you response...
I only said that the firmware doesn't matter, only requires a unlocked BL.
And yes, for the 2018 builds you need a rootable Fire OS...
 

DB126

Senior Member
Oct 15, 2013
15,259
10,037
Amazon Fire HD 8 and HD 10
Google Pixel 4a
Downgrades some partitions like tz and lk but not the system...

---------- Post added at 03:18 PM ---------- Previous post was at 03:17 PM ----------



This is what I said... I don't understand you response...
I only said that the firmware doesn't matter, only requires a unlocked BL.
And yes, for the 2018 builds you need a rootable Fire OS...
Expands upon your post and (hopefully) clarifies update scenarios for those who have been with this device since the beginning. Lots of different iterations out there with a segment of users that may not want to go for the full BL unlock.
 
  • Like
Reactions: Rortiz2

Signor Rossi

Senior Member
Sep 13, 2013
484
74
Thanks to everyone for the reply. I'm back on stock but got issues getting my device Authorized for ADB. ADB is enabled in the Developer Options, driver looks good. Not sure what is missing

Gesendet von meinem CMR-AL09 mit Tapatalk

---------- Post added at 03:58 PM ---------- Previous post was at 03:48 PM ----------

For clarity, Nexus builds dated 2018 and earlier will install on rooted 5th gen 7" Fire devices (aka Ford) with the bootloader packaged with FireOS 5.3.2.0 and below.

There is no safe FireOS downgrade path for devices running FireOS 5.3.2.1 and above. However ....

The most recent Nexus builds (2019 forward) require an unlocked bootloader but are completely independent of FireOS version or hardware generation (works on both 5th and 7th gen 7" devices).

tl;dr - unlock the bootloader if you want to install the latest Fire Nexus ROM.
Btw. I always thought that unlocking the bootloader was not possible for the 5th Gen Device?

Gesendet von meinem CMR-AL09 mit Tapatalk
 

ggow

Recognized Developer
Feb 28, 2014
3,890
10,536
Thanks to everyone for the reply. I'm back on stock but got issues getting my device Authorized for ADB. ADB is enabled in the Developer Options, driver looks good. Not sure what is missing

Gesendet von meinem CMR-AL09 mit Tapatalk

---------- Post added at 03:58 PM ---------- Previous post was at 03:48 PM ----------

Btw. I always thought that unlocking the bootloader was not possible for the 5th Gen Device?

Gesendet von meinem CMR-AL09 mit Tapatalk


I updated the OP a little bit. Read here on how to unlock the bootloader:
https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 177
    Code:
    [COLOR="gray"]
    /*
     * 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 flashing it!
     * YOU are choosing to make these modifications.
     */
    [/COLOR]

    Information + Features
    - Pure AOSP Experience
    - Also ideal for customisation through Xposed

    - EVEN MORE IMPORTANT: As of January 2019 this ROM only works on devices using the bootloader hack. See <<< HERE >>> to unlock your devices.

    - IMPORTANT: Do not update Magisk via the Magisk Manager App, your device will enter a bootloop if you do. Instead update Magisk via TWRP only. If you do this by accident then it is recoverable by just flashing the latest version of the ROM again (with gapps etc as required).

    Rules
    - Please search the thread before asking questions
    - Please try to stay on topic, I know it's not always possible
    - Please report bugs here
    - Report only one issue per bug report
    - When reporting bugs please post a logcat and/or dmesg containing pertinent information regarding the issue...
    - Saying something isn't working without proper explanation will not attract any attention.

    Prerequisites for Installation
    - Unlocked Bootloader
    - TWRP Installed

    Downloads
    *** Please do NOT create any mirrors ***
    - Fire Nexus ROM for Amazon Fire 7"

    Source Code
    - Kernel Source: https://github.com/ggow/android_kernel_amazon_mt8127-common

    Credits
    - Google / AOSP
    - Lineage
    - CAF
    - Temasek

    XDA:DevDB Information
    lp-fire-nexus-rom, ROM for the Amazon Fire

    Contributors
    ggow
    ROM OS Version: 5.1.x Lollipop
    Based On: AOSP

    Version Information
    Status: Beta

    Created 2016-01-25
    Last Updated 2019-05-26
    54
    Change log / Release Notes

    [tbd] August 2019
    - ASB August 2019 patches (sec. string 2019-08-05)
    - Update Chromium WebView to 76.0.3809.111
    -

    26 May 2019

    - ASB May 2019 patches (sec. string 2019-05-05)
    - Fixed video recording
    - WiFi: Use hardware MAC address
    - Bluetooth: Use hardware MAC address
    - Fixed swype functionality when using AOSP keyboard

    03 May 2019

    - Fix certificate store issue which prevented connections to google servers.

    01 May 2019

    - ASB Apr 2019 patches (sec. string 2019-04-05)
    - Upstreamed kernel to 3.10.108
    - Add support for Austin Fire 7 7th Gen
    - Updated webview
    - Removed AOSP Calculator
    - Tested with Latest OpenGapps Pico
    - Tested with Magisk 19.1
    - Unlocked bootloader only
    - Gapps no longer included
    - Root no longer included
    - Enjoy!

    02 June 2018
    - ASB May 2018 patches (sec. string 2018-05-05)
    - Android System Webview updated to M66

    05 May 2018
    - Port relevant security patches up to April 2018
    - Update chromium-webview: 59.0.3071.92 -> 65.0.3325.144

    17 December 2017
    - Port relevant security patches to up December 2017

    02 December 2017
    - Port relevant security patches to up November 2017
    - Switch to using FireOS 5.4.0.0 update-kindle-37.5.7.9_user_579225620 binaries and boot.img
    - Fixed backlight becoming stuck on minimum setting. This needs more users to test. It works for me so far :)

    02 October 2017
    - Port relevant security patches to up September 2017
    - Includes all bluebourne patches
    - Standalone build is now available in the same download location
    - First standalone filename is "lp-fire-nexus-rom-ford-standalone-20171002.zip"

    22 July 2017
    - Upgrade ROM base LMY49M
    - Port security patches up to July 2017
    - Integrate Prebuilt webview.apk from CM-14.1
    - Compile ROM using Snapdragon LLVM 3.8.8
    - Upgrade to open_gapps-arm-5.1-nano-20170702.zip
    - Tested flashing from Lineage-12.1 -> Fire Nexus ROM via FlashFire 0.57
    - Tested upgrading from 08 FEB version to this via FlashFire 0.57

    08 February 2017
    - Switch to using FireOS 5.1.4 update-kindle-37.5.4.4_user_544271020 binaries and boot.img
    - Fix Miracast
    - Fix-up camera and video camera connect and recording problems.
    - Re-tested:
    • Snapshot Camera
    • Video Camera
    • Google Services
    • VLC
    • Miracast
    • Video Playback
    • Audio Playback

    02 February 2017
    - Fixed bug causing google play services to repeatedly crash
    - Fixed supersu.apk disappearing
    - Updated SuperSU to 2.79
    - Updated gapps to open_gapps-arm-5.1-nano-20170202.zip

    Older HIstory
    24 November 2016
    - November 2016 AOSP Security Patch Level
    - Switch to using lastest FireOS 5.3.2 - update-kindle-global-37.5.6.0_user_560177220 binaries and boot.img
    - Fix Video Recorder bug [Cannot connect to camera]
    - Fix bug in OMX causing freeze of video

    04 November 2016
    - October 2016 AOSP Security Patch Level
    - Fix x265 video playback - Thanks @jeromeof

    23 September 2016
    - September 2016 Security Patch Level
    - Updated integrated gapps to open_gapps-arm-5.1-nano-20160923
    - Switch to using lastest FireOS 5.3.1 - update-kindle-global-37.5.5.2_user_552153420 binaries and boot.img

    12 August 2016
    - August 2016 Security Patch Level
    - Updated integrated gapps to open_gapps-arm-5.1-nano-20160812
    - Fix audio lag issue in games - thanks @$ideWinder

    28 July 2016
    - July 2016 Security Patch Level
    - Fixed SuperSU update binary problem
    - Updated integrated gapps to open_gapps-arm-5.1-nano-20160728
    - Upgrade SuperSU to 2.76 Stable

    15 June 2016
    - June 2016 Security Patch Level
    - Added CIFS Support (Instructions here)
    - Fix Swipe for stock keyboard
    - Fixed failure to mount /system partition error due to change in build system
    - Switch to using lastest update-kindle-37.5.4.4_user_544271020 binaries and boot.img

    19 May 2016
    - May 2016 Security Patch Level

    20 April 2016
    - Add app name to "Android is Upgrading..." dialog
    - Fix sdcard write access
    - Enable Bluetooth LE

    05 April 2016
    - Includes April 2016 Security Patch Level
    - Update to android-5.1.1_r37
    - Switch to using lastest update-kindle-global-37.5.4.2_user_542168620 binaries and boot.img

    29 March 2016
    - Includes 01 March 2016 Security Patch Level
    - Upgrade SuperSU to 2.65 Stable

    29 Feb 2016
    - Fixed Downloads App Crash
    - Updated integrated gapps to open_gapps-arm-5.1-nano-20160228

    09 Feb 2016
    - Fixed AOSP Keyboard Swype functionality
    - Location Services Fixed
    - Screen Rotation Glitches Fixed

    07 Feb 2016
    - Built in SuperSU
    - Updated codebase to android-5.1.1_r34
    - Includes 01 February 2016 Security Patch Level
    - Upon installation open SuperSU and update binary via the Normal Method following the prompts

    27 Jan 2016
    - Fix Screenshot capture by rotating memory buffer according to ro.sf.hwrotation
    - Fixed camera/media/stagefright issues causing inability to save images
    - Fixed sdcard access, tested from ES File Explorer

    25 Jan 2016
    - Initial Release
    41
    New Build is Up

    - Dated 22 July 2017
    - Upgrade ROM base LMY49M
    - Port security patches up to July 2017
    - Integrate Prebuilt webview.apk from CM-14.1
    - Compile ROM using Snapdragon LLVM 3.8.8
    - Upgrade to open_gapps-arm-5.1-nano-20170202.zip
    - Tested flashing from Lineage-12.1 -> Fire Nexus ROM via FlashFire 0.57
    - Tested upgrading from 08 FEB version to this via FlashFire 0.57
    20
    Progress for Next version

    - I'm working on an update which should fix up the previous borked release.
    - This ROM relies on gapps been included to work correctly so will not be releasing without it
    - I've fixed a bug in one of the last security updates I back-ported. Google services using the latest gapps now seems stable.
    - I wanted to check over a few more things and do some testing before release.
    - Hopefully should be done within the next couple of days.
    18
    New Build is Up

    - Dated 17 December 2017
    - Port relevant security patches to up December 2017