yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DragonFire1024:
Or those with an 8.9iin Kindle Fire where any version of that can be rooted, TWRPed and rommed.
[Fire Original Android Development] DB126:
Or any 3rd gen HDX (7 and 8.9") and several other past Amazon devices. But this forum isn't about those devices. Ideally discussions should be confined to 5th/7th gen 7" Fire models. HD 8/10 have their own forum. And yes, I have broken the 'rules' a few times myself being a big HDX fan. :)
[Fire Original Android Development] ggow:
New Build is Up

- Dated 27 November 2017

- Ported relevant November Security Patches

- Ported relevant October Security Patches

- Upgraded OpenSSL

- Upgraded Privacy Browser to 2.7.2
[Fire Original Android Development] ceanth:
I'm new to your rom. Does it have an ota update feature?
[Fire Original Android Development] ggow:
No it doesn't have OTA.
[Fire Original Android Development] ms372591:
It does not. You will need to flash the updates manually with Flashfire or TWRP depending on which firmware you are on.
[Fire Original Android Development] tobyxx:
Thanks for the update! Works great.
[Fire Original Android Development] blueberry.sky:
Thank you! Glad to have the Krack wifi vulnerability closed for the Fire7.

edit: thanks for the clarification Ggow.
[Fire Original Android Development] ggow:
KRACK vulnerability is not patched in this one. The patch level for this version of the ROM is 01 November 2017. I am working on the 06 November 2017 patches. When I have it figured out, will do another release very shortly.

I'll add this note to the changelog.
[Fire Original Android Development] STE-Vi:
Does it work with the Fire 7 2017?

Hi there

I wanted to know if somebody tried to flash the newest version of the fire 7? If not is there a separate Thread?

Greetings

STE-Vi
[Fire Original Android Development] ms372591:
I seriously doubt that it would work. Check your firmware version and if it's higher than 5.3.1 you are out of luck flashing roms.
[Fire Original Android Development] DB126:
Not sure what you are asking. Latest build (Nov 27th) released by [MENTION=5749760]ggow[/MENTION]? If so this is the relevant thread. I have not updated; no hurry to do so.
[Fire Original Android Development] Michael_Ge:
Thank you

Update from CM 12.1 -> Lineage 12.1 with Flashfire - all ok

My Files :

open_gapps-arm-5.1-nano-20171127

lineage-12.1-20171127-UNOFFICIAL-ford

SR1-SuperSU-v2.82-SR1-20170608224931

my firmware Fire 7 -> 5.1.2
[Fire Original Android Development] ggow:
KRACK vuln

So, I have applied the patches to the ROM, however

There is an issue in that it seems amazon's own bin/wpa_supplicant doesn't follow a standard setup which we know, therefore at least for now we stuck using the amazon proprietary blob.

Compiling my own results in non-working wpa_supplicant, probably because it's not compatible with the hardware interface layer.

I will try upgrading to the wpa_supplicant in FireOS 5.4.0.0. If it works, then at least we will have the blob with their latest security patches (if any).
[Fire Original Android Development] DB126:
When convenient you should update SuperSU 2.82 to SR5. There were several issues with SR1 that have since been resolved. Spontaneous loss of root on Lollipop (Android 5.0/5.1) was one of them.
[Fire Original Android Development] Michael_Ge:
ooh Thx - update on 2.82.SR5 with flashfire -> all ok :)
[Fire Original Android Development] ggow:
Following on from here

I'm testing a new build with just an updated amazon wpa_supplicant binary. On the surface it seems to work. Just need to test WiFi display (cast) function. If all is good will release tomorrow. The patch level string will stay at 01 November 2017.
[Fire Original Android Development] STE-Vi:
Sorry what I meant was the newest fire 7 2017 version.
[Fire Original Android Development] DB126:
No root for 7th gen (2017) devices which is a prerequisite for installing any type of custom ROM.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 29 November 2017

- Use bin/wpa_supplicant blob from FireOS 5.4.0.0
[Fire Original Android Development] 4js:
thx
[Fire Original Android Development] DB126:
thanks - we all needed to know that ...
[Fire Original Android Development] ggow:
FireOS 5.4.0.0 binary blobs

For the next build I plan to fully transition to using FireOS 5.4.0.0 binary blobs and boot.img. The last hurdle to upgrading the binary blobs was getting WiFi display (Cast) to work. I have got it working and it seems good now.
[Fire Original Android Development] ggow:
Screen brightness getting stuck possibly fixed

It's early days in my testing, however it looks like the new kernel (5.4.0.0 boot.img) could have fixed the screen brightness getting stuck on minimum. I had this issue within minutes of using the tablet normally. Will put a note on my findings in the next release notes.

Does anyone have any consistent way of reproducing the issue that I could try out?
[Fire Original Android Development] DB126:
Interestingly I never experienced this issue with Lineage/CM and had it occur only once or twice on early Nexus builds. Must have turned a knob or two that blocks the 'triggers'. I do a fair bit of kernel parameter tuning and run Xposed; one or both may contribute to hapless good fortune.
[Fire Original Android Development] DragonFire1024:
I also have to admit to never having the issue. Also like you, have Xposed installed.
[Fire Original Android Development] nirogu325:
Hmm, a consistent way? I think it would be the same procedure you did of opening several apps (you know, using the device as it were a daily driver) and eventually I bump into that once I turn off the screen and leave the device idle for some time. It has happened to my two Fire tabs (a relative has the other one but I maintain both).
[Fire Original Android Development] ggow:
Ok, no worries. I haven't managed to break it yet today. Will keep trying over tomorrow. Should have already locked up in fairness.
[Fire Original Android Development] t3chwizard:
How did you manage to stop the screen brightness issue? I still get it occasionally
[Fire Original Android Development] DB126:
Nothing overt; just doesn't happen with my workflows. Possibly related to the presence of Xposed (or specific modules) but no supporting evidence. Looks like [MENTION=5749760]ggow[/MENTION] has a universal fix coming in the next build which will benefit everyone.
[Fire Original Android Development] t3chwizard:
I usually see it after playing a game for a while and then locking the device or leaving it to charge for a while.

Has anyone else been getting a toast message to update Xposed installer even though there is no new version?
[Fire Original Android Development] chillma:
I only had this bug before I used L Speed. Somehow the problem was fixed with some memory tweaks.
[Fire Original Android Development] tonibm19:
Why don't use FireOS 5.6 blobs and boot.img?
[Fire Original Android Development] ggow:
I didn't know there was a FireOS 5.6, have you got a link?
[Fire Original Android Development] melvinaury:
I had installed Xpose LSpeed and with a graphics intense game it had the bug without turning the screen off. Just playing the game the screen dim...
[Fire Original Android Development] DB126:
It's now the standard downloadable build for 5th-7th gen devices on Amazon's support pages. Probably best to grab it from there. Note there are several acknowledged flaws in 5.6.0.0 that Amazon promises to remedy in a future release. 5.4 might be better for now.
[Fire Original Android Development] ggow:
I found 5.6.0.0 on the Amazon US page. UK page which is default here still shows 5.4.0.0 as the latest.

I'll try the 5.6.0.0 blobs.
[Fire Original Android Development] steve8x8:
I may have missed that, but is there a way to reduce the minimum display brightness? I'm getting complaints when using the tablet at night time, and I suspect that my sleep quality has diminished - when still on stock, I had used the night mode, but I'd prefer to keep colors and not turn everything reddish. Any help?
[Fire Original Android Development] DB126:
Nope - min brightness is set in the kernel and apparently can't be lowered. It is the only device I own where this can't be tweaked via Xposed module or other kernel manager. Far too bright to use in a dark room so I use a supposed 'blue light filter' which is questionable but lowers the lumens to an acceptable level (no battery savings as the backlight remains at the same intensity).
[Fire Original Android Development] nirogu325:
I use an app called "Bluelight Filter Pro", I got it free months ago, but you can customize the filter color to black and toy around with the contrast to get what you're asking for. There could be alternatives, though.
[Fire Original Android Development] ggow:
Going with 5.4.0.0 blobs

- There are issues using the binary blobs from FireOS 5.6.0.0

- The boot.img won't boot, perhaps amazon changed something in the boot.img header, my device is is on the 5.0.1 bootloader. Haven't had a chance to investigate properly.

- Several media functions break using these latest blobs

- Will make a new release with 5.4.0.0 blobs
[Fire Original Android Development] steve8x8:
Is it normal that this app requests so many permissions, including network and payment? Suspicious

Gesendet von meinem KFFOWI mit Tapatalk
[Fire Original Android Development] nirogu325:
You should ask the app's developer for that answer.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 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. Need more people to test this, please report back your experiences. It works for me so far :)
[Fire Original Android Development] DB126:
This is the app I use. Reliable, flexible, permissions consistent with similar apps (in reality only boot and keep awake are requested/used). Enables/disables itself as needed (eg: when sideloading apps). 10 million downloads. To be clear this is not an unequivocal endorsement; there are many options in the Play Store and elsewhere. This one just works for me. Paid for Pro as token of appreciation to developer. Ads are universally blocked on all my devices; not sure how obnoxious they are on free version.
[Fire Original Android Development] Earthsape:
Thanks for this, not seeing the download on https://androidfilehost.com/?w=files&flid=200071 does it take a while to appear?
[Fire Original Android Development] melvinaury:
Me too I don't see the new ROM link...

---------- Post added at 05:09 PM ---------- Previous post was at 04:10 PM ----------

Ok, it was already posted on the download page. Downloading right now...
[Fire Original Android Development] ggow:
Should be there now, upload was interrupted.
[Fire Original Android Development] Michael_Ge:
Update on 2.12.2017 -> all ok ...at first glance :good:
[Fire Original Android Development] tonibm19:
Ok for me too.

Thanks!
[Fire Original Android Development] melvinaury:
2 hours and still no brightness bug. Excellent job..
[Fire Original Android Development] t3chwizard:
The link goes nowhere

---------- Post added at 03:57 AM ---------- Previous post was at 03:56 AM ----------

Did u clean flash or just wipe system before flashing? I always forget how to update with FlashFire lol
[Fire Original Android Development] DB126:
Argh! Google makes things so difficult when working from a mobile platform. Fixed link in previous post (or click here). Thanks for noting the problem.
[Fire Original Android Development] Michael_Ge:
No clean flash ... I proceeded according to the instructions on the first page :

Upgrading to new version via FlashFire >= 0.57

- Click the Red + button and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Lineage ROM Zip

- Click the Red + again and choose 'Wipe'

- ONLY tick Dalvik Cache and Cache.

- Press the big FLASH button.
[Fire Original Android Development] melvinaury:
Just to report 24 hours without the bug..

I upgrade without wipe dalvik or cache..
[Fire Original Android Development] DB126:
Why the heck would you do that? Arguably cache is flushed at each boot and dalvik will be regenerated as needed. That said, running with a stale cache is just asking for trouble. You loose nothing save an extra few minutes on the *initial* boot after a ROM update by flushing dalvik. Just say'in ...
[Fire Original Android Development] rwbonesy:
I can honestly say I wasn't expecting this. Looking forward to using it when it's more stable and I figure out account transfers on my crappy mobile games!
[Fire Original Android Development] lost_droid21:
First off, thanks for your hard work! I'll be testing it throughout this week and provide some useful feedback.

I had the same issue when first flashing. Amazon logo boot loop. Root issue was the mounting. Had to sideload original ROM and use rootjunky's YouTube tutorial to flash SuperSU and flashfire.

I think the way around that if you're coming from CM is to make sure the mounting is checked off "mount /system" (referenced in the photo below).

I am not a developer/programmer, so I'm just taking a shot in the dark here, but I hope this helps.

Feedback to come! Viva la Fire.
[Fire Original Android Development] DB126:
Perfectly stable; issues discussed to date involve minor cosmetic issues.
[Fire Original Android Development] ggow:
Fixed the sdcard issue, will be in the next release.
[Fire Original Android Development] Alaxmofo:
How would I go from slimlp to this rom? Do I have to go back to fireos then reflash to lineage?
[Fire Original Android Development] ggow:
I haven't tested going from from slimlp -> this rom. However you should be able to follow the "Fresh installation from FireOS or other ROM FlashFire >= 0.57" instructions in the OP. Theory is this should work.

Just in case make sure you know which version of FireOS you originally had and make sure you have a copy of it handy to start from fresh if needed.
[Fire Original Android Development] Alaxmofo:
I only have a Linux os, and I can't get adb to recognize that the tablet is plugged in... but I read somewhere on the slimlp forum that it's something to do with the setting not being able to go to mtp or adb.
[Fire Original Android Development] ggow:
Sorry I just assumed you would have to use FlashFire, what was your FireOS version?

If it was 5.0.1 then you can boot TWRP which would get you adb access.

Failing that then you'd need to figure out getting adb functional on slimlp.
[Fire Original Android Development] Alaxmofo:
My fireos version was 5.1.1. I still have stock recovery of course, but when I do update from adb my terminal wont recognize it being plugged in. I tried with my note 3 and it shows up just fine
[Fire Original Android Development] ggow:
Can you install a terminal app on your tablet?

If so, do the following:

1. Open Terminal app

2. Type su, then press Enter. (Allow access if needed)

3. Type setprop persist.sys.usb.config mtp, then press Enter.

4. Type setprop sys.usb.config mtp, then press Enter.

5. Developer Option >> Enable USB debugging

6. "Connected as a media device" notification should now shown. Click on this notification, and then click on MTP (even though it's checked already).
[Fire Original Android Development] Alaxmofo:
Still not working, and I have buildprop editor and double checked to see if I did anything from the terminal and it didn't make changes so I did it my self and still didn't work. Plus "sys.usb.config" wasn't in the build prop.
[Fire Original Android Development] bullet25:
All the yeses!

Okay first note: I noticed its still branded CyanogenMod, even though it has the LOS boot screen. I'm assuming thats on Lineage's end not yours though.

and SD card write issue that I think you said you already fixed for next build.

Everything else seems golden!
[Fire Original Android Development] yochananmarqos:
First install android-tools-adb & android-tools-fastboot if you haven't already. Then install Nexus Tools and let it update your adb & fastboot binaries. Your Fire tablet will be detected after that.
[Fire Original Android Development] DB126:
I have read the back-and-forth on getting ADB working; eventually you will find the culprit (don't forget to throw a cable and USB port swap into the mix). Still begs the question of why FlashFire is a 'nogo' assuming SlimLP is rooted with SuperSU. Should do the trick with proper wipes in the proper sequence sans tether. That said, if something goes wrong then a tethered reload of FireOS from the stock recovery menu is the only recourse.

Also not sure what you are trying to accomplish via adb given 5.1.1 bootloader.
[Fire Original Android Development] Jrhotrod:
So great to finally see an update for the CM ROM! Just installed this on my Fire tablet, have noticed no issues so far except for that weird screen rotation glitch that occurs whenever I press the power button. [MENTION=5749760]ggow[/MENTION] - I am totally fine with testing any beta releases of this ROM if it helps make it more stable. Just let me know if there's any contributions I can make and I will do my best. I'm very happy to see an update on CM!
[Fire Original Android Development] ggow:
Next release should clean up remaining minor issues then it will go to stable status.
[Fire Original Android Development] Alaxmofo:
I am trying to adb sideload the fireos. So that I can flash this rom from fireos, and not risk a brick from trying to do it from flashfire on Slimlp rom.
[Fire Original Android Development] DB126:
- FireOS can only be loaded/reloaded via stock recovery (to the best of my knowledge); you won't be able to flash via Fastboot or ADB (obviously)

- If installation of LinOS 12.1 failed via FlashFire from SlimLP you could always recover device by reloading FireOS from stock recovery which should remain accessible
[Fire Original Android Development] rwbonesy:
Thus far haven't had any actual issues other than some of the cosmetic ones mentioned earlier. I totally forgot how to enable using the power button to take screenshots, though. Or am I crazy and that option never existed?
[Fire Original Android Development] ipdev:
Settings - Buttons - Power menu

(Or hardware keys - volume down and power buttons)
[Fire Original Android Development] melvinaury:
I just forgot to clear cache and dalvik when upgrade. I just finish doing the wipe.
[Fire Original Android Development] Andrewmail83:
GOOD WORK...

Excuse me if I have mistakes in English. I use the google translator:

Excellent ROM, very well polished. And better yet in each Update. It gave me Tremendous joy to return after enough time and see that you continue on ROM CM 12.1. What can I say is an excellent and stable ROM and to my understanding it was the best of all (And believe me ... I have installed and tried them all, I have more fun making the poor Tablet suffer than using it)

When I read that you were going to contribute in the Fire Nexus ROM, I put myself in plan ¡NOooo Whyyyy, this is PERFECT do not abandon it !!! So when i saw this ROM, was like a child in a Candy Store.

Only one request. You could in future updates add more time zones. In my case specifically that I am from Cuba, In the case of mobiles, the provider assigns us (GMT-05: 00) Cuba's standard time. But in these cases where that is not an option we must select (UTC-05: 00) Eastern Time (USA and Canada). Although in theory any -05: 00 should work for me. Games like CoverFire give me an error.

Greetings and keep up the good work. Andrew.
[Fire Original Android Development] DB126:
No issue w/dirty flash from TWRP (caches wiped). Nice and easy. :)
[Fire Original Android Development] akz1x1:
Thanks for still keeping the device updated for some of us users still using it :)

---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------

Sorry for OT but is there a kitkat version of the fire nexus rom available for this device.

I think it'll run much better than LP.
[Fire Original Android Development] DB126:
All ROMs (stock and custom) for this device are Android 5.1.1 based due to kernel restriction. Not sure I concur with your KK/LP assessment having used both variants on similar hardware. Is there a specific issue you are facing?
[Fire Original Android Development] t3chwizard:
Never forget to wipe, that's when things start to stink ?
[Fire Original Android Development] ggow:
No the ROM does not have OTA update.
[Fire Original Android Development] cybermcm:
Thanks for fixing the back light bug, really great!:good:
[Fire Original Android Development] Hallo32:
[MENTION=5749760]ggow[/MENTION]

Is there a guide how I can build this image from scratch?
[Fire Original Android Development] ggow:
No, there is no guide as far as I'm aware.
[Fire Original Android Development] Hallo32:
May it be possible to get such a guide?
[Fire Original Android Development] ggow:
I certainly haven't got time to be writing guides as I work on many different projects.

Basic gist of it goes like this:

1. sync lineage-12.1 source tree

2. get https://bitbucket.org/amazonfire2015/cm_device_amazon_ford

3. get vendor blobs from stock rom

4. get https://bitbucket.org/amazonfire2015/android_kernel_amazon_ford

5. then build the rom following lineage instructions

I haven't synced my device configs in a while, it's on my todo list.
[Fire Original Android Development] Hallo32:
Thanks for the information. :)
[Fire Original Android Development] xsteven77x:
Dude, I thank you from the bottom of my heart... sincerely, for still supporting his piece of **** device that some of us are stuck with LOL. You make using this piece of garbage tolerable and if I wasn't an unemployed loser right now, I would tip you some money from here to the moon. Instead, all I can offer is my positive sentiment. Thanks a lot dude.
[Fire Original Android Development] akz1x1:
Just heard of the android Oreo Go version for low ram devices which struggles to run normal verison.

Wish there was some way it could be built for this device. :*(
[Fire Original Android Development] DB126:
A rooted device can realize similar benefits through appropriate tuning. Oreo Go packages and optimizes the streamlined experience with emphasis on Google applications/services. How well it works in the wild has yet to be seen. Initial release is targeted for India.
[Fire Original Android Development] platypoid:
Stuck on Amazon Screen

update - I was able to adb side load back to stock 5.1.2 so guess I will start all over again !

I had Cyanogenmod working just fine on my Fire Kindle 5th generation and just followed all the instructions exactly as on first page to flash Lineage using Flashfire.

It rebooted up to Amazon screen and is stuck there.

I can get to Amazon system recovery with reboot, apply update from ADB, etc options . I tried reboot but no luck - same Amazon screen.

What is recommended I do next to try and get this back up and running ?

I don't remember the first stock kindle version I started with - I believe it was 5.1.4 maybe but not sure . Hopefully I posted somewhere when I was successful and can look it up.

Thanks for any help.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 17 December 2017

- Port relevant security patches to up December 2017
[Fire Original Android Development] DB126:
If FireOS 5.1.2 has been successfully loaded head to the SuperTool thread to reroot and migrate to SuperSU in preparation for reinstalling a custom ROM. Recommend using a more recent FlashFire build (currently 0.73) which can be obtained from APKMirror. Be sure to maintain network isolation (WiFi radio off except when starting KingRoot runs) to avoid an unfortunate OTA update that may leave you with an unrootable device.

https://www.apkmirror.com/apk/chainfire/flashfire/