yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] ggow:
I have sent emails to amazon asking them to release the latest kernel sources for all devices. I also specified that for all devices it should be the same source that they used to build the latest version of FireOS. Once we have the kernel sources for FireOS 5.6.3.0 then work can begin getting a later version of android working.
[Fire Original Android Development] Rortiz2:
Yes. THANKS!

Enviado desde mi Mi A2 mediante Tapatalk
[Fire Original Android Development] DragonFire1024:
Question. It seems any variety of the mt8173 I came across is on Android 7.0. it would be safe to say amazon is the only one running lollipop on that chipset (HD 10). From what I have been reading, even with a still locked bootloader, a rom from another device with the same chipset, but higher Android (7.0) could still be ported to it? What about just a fresh system build?
[Fire Original Android Development] frumpy:
Got this ROM up and running nicely on my 5th gen Fire, thank you ggow!
[Fire Original Android Development] Rortiz2:
And what do you think? Which Amazon is going to pay attention to you? It's not to offend, but I do not think they update nougat because a user tells them.

About porting ROMS from other tablets, I assure you IT IS IMPOSSIBLE.

I have come to carry port ROMS from other MT8163B to my Aquaris M8 and NONE WORKS. You need to update the lk.bin and the preloader and if you try the fire will never turn on again.:o
[Fire Original Android Development] Oco:
Hello, coming from the looooong trip to downgrading-unbrick-twrp, installing Lineage which looks great thank and install nano gapps. My problem is that google calendar wont install despite all the efforts. Is it expected this? my only option is to install super big stock gapps? Regards
[Fire Original Android Development] Oco:
No all Amazon logo missing means a lost tablet, follow those guidelines suggested, mine was not showing anything at all and battery disconnect make the trick
[Fire Original Android Development] HaiKaiDo:
Sooo I was running a slightly older build of lineage from sometime in 2018 and I decided to update tonight.....

Long story short, I was using flashfire and I didnt move the WIPE step as the first step -_- So now I just boot to an amazon logo and it sits there forever. I dont see a recovery either...Did I just completely destroy this thing?
[Fire Original Android Development] riverstyxxx:
Dumb question: Can I install supersu if I flash it with twrp?
[Fire Original Android Development] platypoid:
I think root is built in and you have to enable developers options ( tap a bunch of times on serial number in settings) then go to Root Access and enable it .( and reboot after enabling root) But you can probably also flash SuperSU since I see it is on mine though I would have used Flashfire at the time ( so nice don't have to use that any longer !)

Do a search on this forum topic - all this info is in past discussion in detail.
[Fire Original Android Development] Neffy27:
You pick one root or the other. Use the built in one or you disable the built in one for supersu.
[Fire Original Android Development] Michajin:
Have you tried rooting/unlocking to get TWRP installed? With that you can boot right into recovery and flash from there.

https://xdaforums.com/amazon-fire/development/unlock-fire-t3899860
[Fire Original Android Development] ajislav:
Thank you for posting the solution, I recently run into this issue too. I searched the Internet and found I needed to run the above command as root, never-the-less it was your post which made me realize I need to do this while the USB cable is plugged in...

So for me the takeaway is "keep USB computer connection as it is", i.e. MTP.
[Fire Original Android Development] llamasking:
Hello. My apologies if this was already covered in a previous conversation, I did search for Magisk but the only results are about the locked bootloader.

Anyways, after using k4y0z's method to unlock the bootloader and install twrp (the device was bricked prior after a downgrade attempt from FireOS 5.3.2.1 to 5.3.1) I flashed this rom along with Gapps and Magisk, I found that everything, including Magisk Hide works just fine, except for if I flash any Magisk module, either from the app or TWRP, the boot animation rotates 90 degrees clockwise and it never actually boots.

Wiping cache and dalvik does nothing.

It's fixed by uninstalling Magisk and reinstalling it.
[Fire Original Android Development] Neffy27:
Supposed to use either the built-in root Privacy Guard or SuperSU. It's been said to not use Magisk since it's systemless and will bootloop the device.
[Fire Original Android Development] Pix12:
You CAN use magisk if you use the unlock, as it's essentially a bootloader unlock.
[Fire Original Android Development] llamasking:
Yeah. It works just fine after the unlock. You just can't use any modules.

It's rooted as it should and MagiskHide works. Just CtsIntegrity or whatever is tripped. BasicIntegtiry is fine.
[Fire Original Android Development] Reynald0:
You can bypass CTS Integrity spoofing the signature, with another signature from any 5.1.1. device, it is indeed amazing to have TWRP now,

I taken also the chance to replace the embedded SystemWebView with BromiteWebView, and updated PrivacyBrowser to the latest,

I really like this ROM, so I will stay with this : )
[Fire Original Android Development] mrmazak:
FYI

this works with the newest boot.img

one from 5.3.6.4 Nov 12, 2018 (often called 5.6.3)
[Fire Original Android Development] Rortiz2:
Yes

Enviado desde mi Mi A2 mediante Tapatalk
[Fire Original Android Development] Pix12:
Amazon has the source code for 5.3.6.4.

It might be useful for the porting of other roms.

https://fireos-tablet-src.s3.amazon...Kk/Fire_7_LC_5th_Gen-5.3.6.4-20181203.tar.bz2
[Fire Original Android Development] mrmazak:
the date stamp on that file doesn't match up to what I saw on amazon.

https://www.amazon.com/gp/help/customer/display.html?nodeId=200203720

Unless that is the OS source , not just kernel.
[Fire Original Android Development] ggow:
Just a heads up that going forward the next builds, will be for unlocked devices only.

I'm still trying to get some sense from Amazon about the kernel source code. Will let you know if I get it resolved. The latest is that they are saying 5.3.6.4 on the source code notice is the latest. Had a half assed response regarding compilation issues and not been able to reproduce the zImage from the latest fireos 5.6.x.
[Fire Original Android Development] DragonFire1024:
You're not the only one. On the fire 10, unless I did something wrong the equivalent of a zImage was created and successfully. According to what I've been able to come up with, you should just need to copy over that file to the unpacked boot image and delete the zImage, and update the parameters in the rest of the files in the same directory. I did everything I presume correct but the image just won't boot. I am going to try again today if I have time. Amazon may not have the full source. From what I understand it's not easy to get a full mediatek source.
[Fire Original Android Development] k4y0z:
What issues are you having, I may be able to help.

You can try the same fixes I did when I was working on selinux-permissive and kexec back in 2015:

https://github.com/chaosmaster/andr...mmit/5b71ce8bab684cff2534bee0175b5579f5f1b9e1

Maybe they are still necessary on the newer sources.

PM me If you need more info.
[Fire Original Android Development] Drycloud:
Hi ggow - would you be able to post your local manifest for this build? thanks in advance!
[Fire Original Android Development] ggow:
I don't have one or use one, all the source is linked on the OP.
[Fire Original Android Development] ggow:
A while back I applied your fixes to the 5.3.6.4. The kernel does not boot a ROM build.

However It boots a recovery image.

I took the zImage from stock and placed it my ROM build and that works.
[Fire Original Android Development] k4y0z:
That's strange, could you get a serial-dump?

You can use a Mediatek Debug Cable.

(A Micro-USB-breakout and a Serial-TTL-adapter (FTDI) should do)
[Fire Original Android Development] mrmazak:
I saw similar situation with the kernels I am working on. At least on the 5th gen Ford.

But I built the 7th gen Austin kernel , it apparently booted on your. LineageOS that was ported.

When I did a diff on the two defconfig files ( not including image sensor or lcm driver) there was only two differences.

I was about to merge those changes to the Ford source and see if that build will boot on a built ROM. As it is now it does boot on revamped. (Fireos)

particularly gonna start by removing this line from ford_defconfig

CONFIG_SECURITY_PERF_EVENTS_RESTRICT=y

this line is not in Austin_defconfig and that one boots on lineageos

And Adding these lines as second option

CONFIG_I2C_CHARDEV=y

CONFIG_SQUASHFS=y
CONFIG_SQUASHFS_XATTR=y
# CONFIG_SQUASHFS_ZLIB is not set
CONFIG_SQUASHFS_LZO=y
# CONFIG_SQUASHFS_XZ is not set
CONFIG_SQUASHFS_4K_DEVBLK_SIZE=y
# CONFIG_SQUASHFS_EMBEDDED is not set
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
[Fire Original Android Development] Nootboot64:
Hey, I'm pretty sure this is a stupid question, but...

I am satisfied with this amazing custom rom! But is there any way to have a newer Lineage OS build? I think this question is stupid because the stock 5th gen kffowi (the one I have and installed lineage 12.1) only ran Android Lollipop in the first place.

Thank you in advance for tolerating my noob question!
[Fire Original Android Development] mrmazak:
[MENTION=5749760]ggow[/MENTION]

I made those changes as listed above, now my built kernel is booting on both SlimRom and LineageOS.

I2C dev and squash file system , was the key.

I am sure you can do same thing, but here is the modified defconfig

https://github.com/mrmazakblu/Fire_...b/master/arch/arm/configs/ford-mod1_defconfig
[Fire Original Android Development] DB126:
Not with stock kernel and/or on devices with locked bootloaders.
[Fire Original Android Development] Nootboot64:
That makes sense, thank you for answering so quickly!
[Fire Original Android Development] ggow:
Cool, will take a look. Thanks for the heads up.

I've started pulling stuff together for a more maintainable kernel. Working from Amazon's kernel release with no history is unworkable going forward.
[Fire Original Android Development] DragonFire1024:
I feel your pain. Even though we have an extensive source for the HD 10, I don't think its complete and everything is out of order. I have found one marshmallow ROM that's pretty much identical in the build prop minus fingerprint stuff.
[Fire Original Android Development] k4y0z:
Yeah, it sucks not having the history, makes it a pain merging upstream changes, since you have to cherry-pick everything.

Sadly GPL doesn't require them to publish the history or publish just their changes in the form of patches :(
[Fire Original Android Development] ggow:
I looked into this, something must have been wrong in my build environment. I cleaned it and all is good now. The only change to the kernel to fix build errors that was necessary on the 5634 sources was to enable High resolution timers and include the pre-generated trapz header :)

No idea how amazon got their released kernel sources to build an output binary without it :rolleyes:
[Fire Original Android Development] ggow:
New Build is Up

- Dated 16 April 2019

- ASB March 2019 patches (sec. string 2019-04-05)

- Privacy Browser updated to version 2.17.1

- Android System Webview updated to M72 (includes CVE-2019-5786)

- This is for unlocked devices only

- Updated OP
[Fire Original Android Development] Rortiz2:
Thanks! Installing now on my ford and porting it to my austin!
[Fire Original Android Development] fmc000:
Out of curiosity, what do you mean with "Fix of carrier display"?
[Fire Original Android Development] ggow:
Not relevant to this device, lifted from the changelog of the ROM source.

Edited post to reflect, mindless copy and paste now fixed :)
[Fire Original Android Development] Rortiz2:
Updated! (FORD)

Flashing on austin..

By the way, [MENTION=5749760]ggow[/MENTION] why you now used system.new.dat? It is harder to make the port ..
[Fire Original Android Development] ggow:
I built it with a clean ROM download. With not needing all the mods for Flashfire etc I thought a clean start would be best. And I want a clean as possible ROM source to ease maintenance going forward to support other devices, one of them being 'austin'.
[Fire Original Android Development] mrmazak:
Are you using the build.sh in that source, or the build-kernel.sh that came with the full release source.

they are quite different.
[Fire Original Android Development] DB126:
For s#its & grins tried installing this on a locked Ford with 5.0.1 bootloader via twrp. As expected bootlooped prior to ROM load. Was worth a try :)
[Fire Original Android Development] platypoid:
Are the new method of installing TWRP considered unlocked bootloaders now ?
[Fire Original Android Development] mrmazak:
​

Yes, the bootrom.sh and fastboot_step.sh.

Yes this is effectively making device unlocked
[Fire Original Android Development] mrmazak:
I have magisk root and magisk hide setup on the "revampted fireos"

I did this because of my tv service app having error " this app will not run on rooted devcie"

I really want to use this lineage instead, but majisk is making trouble here.

ie -- hanging on amazon splash screen,

-- reloading (optimizing 82 apps every time it boots)

Have any of you been successful in replaceing the sysem superSU for magisk?
[Fire Original Android Development] DragonFire1024:
You have to remove the lineage SuperSU upon installation of the rom. So wipe everything except storage, install the rom, gapps if necessary, and flash the lineage SuperSU removal zip located here for your correct architecture https://download.lineageos.org/extras then flash magisk. That should work. But it's not always certain.

Edit: not sure it will work for 12.1. if not, remove the line in the script that checks the Android version and see if that works.
[Fire Original Android Development] ajislav:
So basically you are saying that even for Ford with 5.0.1. firmware I need to do those 2 steps before flashing the latest LineageOS ROM?

(I inferred the answer is yes, but I want to be double sure as well as time-effective)
[Fire Original Android Development] DragonFire1024:
Delete. Wrong post.
[Fire Original Android Development] DB126:
Yep. However, anything prior to 20190416 build should go in fine on qualifying locked bootloaders.
[Fire Original Android Development] ggow:
Just realised I didn't add the sdcard read/write fix, will add it for the next update.
[Fire Original Android Development] Reynald0:
Flashed over old build the newest one with kernel mrmazak, and Magisk19, I saw the permission thing for sdcard, anyway was enough to grant to file manager permissions again, replaced the stock Webview with Bromite webview because overwritten.

Thank you ggow

---------- Post added at 02:42 PM ---------- Previous post was at 01:59 PM ----------

Testing the latest ROM seems the old bug when you screen off, screen rotates, and defocus, someone else having it?
[Fire Original Android Development] ggow:
Yes, also will add the screen rotation fix for the next release.
[Fire Original Android Development] mrmazak:
I constantly get "waiting to download" when installing apps from play. If I toggle WiFi off then on, they start right away. Is that a gapps issue or rom?
[Fire Original Android Development] DragonFire1024:
What is the difference between this ROM and the Nexus? I just recently acquired the ability to be able to install a custom ROM, but there's no real list of features unless I missed it. Do either support Live Wallpapers? Do I need to install SU into this ROM or is it integrated? Does anyone have either or installed and if so which do you prefer?
[Fire Original Android Development] DB126:
- Fire Nexus is an AOSP clone; pure Android bereft of customizations not included in the base Google build; a minimal (mandatory) GAaps build plus SuperSU are included as a convenience

- LineageOS is the spiritual successor to CyanogenMod ROMs which are generally lean but contain a suite of useful UI enhancements; a proprietary root and privacy manager is built in; a suitable GAaps package must be obtained and flashed separately

- both are based on Android 5.1.1 and are constrained by the locked Amazon bootloader; hardware/kernel issues (eg: minimum panel brightness) are shared by all ROMs for this device

- AOSP ROMs are an ideal platform for Xposed framework; Xposed can also be used with LineageOS but some module functionality many conflict with native features (eg: nav bar customization)

- many online reviews of CM and Lineage ROMs; best read up and not spam the threads with feature questions; better yet try them both!

- my personal preference is for AOSP for ultimate customization; however, I run LineageOS on most of my Fire 7s as they primarly serve as secondary devices that I don't want to invest time in personalizing/tweaking

- have no idea if life wallpapers are supported; don't use this eye candy
[Fire Original Android Development] aaronson2012:
Awesome work on this!

Is anyone else having issues with the brightness slider? It seems to be stuck at minimum brightness for me, but I can still move the slider.

Thanks!
[Fire Original Android Development] DragonFire1024:
Thanks. So if I don't like one or prefer one over the other, I can switch? That's really cool all on it's own.
[Fire Original Android Development] Currying:
This occurred here as well until the first boot. Hence, rebooting should help.

---------- Post added at 08:11 PM ---------- Previous post was at 07:42 PM ----------

The only slight issue I have found with this ROM is the integrated camera app. The shutter button is partly off screen and sometimes hidden by the system buttons. More importantly, the shutter can only be triggered once. Subsequent taps do cause the shutter animation, but do not take any more photo until an app restart or switch between photo/video modes.

Of course one can use another camera app. E.g. Open Camera works.
[Fire Original Android Development] :
Yep - just follow the target ROM OP carefully, especially w.r.t. wipes and their positioning w/FlashFire. A borked flash means a factory reset from stock recovery and the normal hoops to secure root on FireOS v5. A lucky few can boot TWRP; assuming your device is not one of those.
[Fire Original Android Development] micgeb:
FlashFire say to me incompatible data. I checked the md5 sum and it's ok.

on the 3rd try it's working.

Now I can test it. Ty
[Fire Original Android Development] m00head:
One of these 2 specific versions of the Google Camera app should work on this device:

Google Camera 2.5.052 APK Download by Google Inc. - APKMirror

https://www.apkmirror.com/apk/google-inc/camera/camera-2-5-052-release/

Google Camera 2.7.008 APK Download by Google Inc. - APKMirror

https://www.apkmirror.com/apk/google-inc/camera/camera-2-7-008-release/
[Fire Original Android Development] DragonFire1024:
I tried the Google camera on my HD 8 and wasn't too impressed. I'll likely look it over again and experiment with it, but for now I'll stick with Open Camera.
[Fire Original Android Development] N0tHum4n:
[MENTION=5749760]ggow[/MENTION]

I found two bugs in this rom and in Fire Nexus Rom - LMY49M:

Two identical strings in the build.prop file: ro.config.notification_sound=Verso.ogg and ro.config.notification_sound=Argon.ogg. The Verso.ogg file does not exist;

Both roms have no low battery's notification sound.
[Fire Original Android Development] yolarrydabomb:
Sorry guys but a few questions.

So is LineageOS have any optimized benefits from other mods like CM and Nexus?

Does this have "Move to SD" option on app settings?

Can I wipe+flash directly from Nexus to Lineage skipping the god awful FireOS rom?

I might wait for low battery's notification sound fix update that N0tHum4n mention that way I don't have to do this all over again lol

Can't wait to try this mod Thanks.
[Fire Original Android Development] dctan:
After trying it for a week, I see no difference between previous CM & the new Lineage OS. The difference is miracast now working on Linage OS but after miracast for 10-15 mins it became very hot near the rear camera and auto shut down. Another issue is that the camera can only take photo or video at 1 time, I was not able to take photo/video for 2 or 3 time, the camera will auto hang sometime. Hope to see some fixed in the next upgrade…..

Overall the Lineage OS was good…..
[Fire Original Android Development] s.i.t.h.l.o.r.d:
After installing LineageOS onto my ford, I noticed an important game for my daughter won't start anymore.

It's called HorseWorld 3D - Premium [https://play.google.com/store/apps/details?id=com.tivola.horseworld.full.gp] :cowboy:

It only shows my the splash screen and a tiny rotating circle in the top left hand corner. Even when I let it sit over night, i still only showed the splash screen in the morning.

If this app won't work, I'll regretfully have to return to AOSP.:rolleyes:

/edit

Would it be possible for you guys to install the app and see if it starts up?
[Fire Original Android Development] DB126:
Installed a non-premium variant by the same author. Launched/loaded just fine. Obviously not decisive as it's a different app but suggest the issue may be local. Make sure you have sufficient room for the game and any temp files it may create. Several hundred MB at a bare minimum.

Seeing this launch brought back memories. My daughter (long since grown) played a crude variant on a Windows 3.1 box that I assembled in the early 90s before DIY PCs were a thing. Heavy gage metal case, huge CRT monitor, keyboard that could qualify as a WMD. Entire rig probably weighed 50lbs! Dimmed the lights when powered on. :)
[Fire Original Android Development] ssb13:
Not getting root??

I was having trouble as well. Here is what I did.

1. Enable in Dev options.

2. Rebooted

3. Used RootJunky's tools to root

4. After the tool installed KingRoot, reboot and KingRoot will request Root access on boot.

5. Continue the tool and it replaced with SuperSu and updated.

Sorry I can't go into more details, but that's the jist.
[Fire Original Android Development] Jrhotrod:
A better process imo is to download the SuperSU 2.79 apk and grant it root when it needs to update the SU binary.
[Fire Original Android Development] xenokc:
Just wanted to say this ROM is working well and thanks. Hope to see monthly security patches as long as possible.
[Fire Original Android Development] EtoileLabrie:
simple question. Should I put the lineageos-..ZIP file in my microSDCARD or can I put in the internal storage? Many thanks.
[Fire Original Android Development] DragonFire1024:
I don't think it matters. Just follow the steps precisely to flash it using FlashFire. Once the ROM is flashed successfully the .zip can be deleted or place it somewhere as backup.
[Fire Original Android Development] EtoileLabrie:
thanks for the reply.

Another question: Does this ROM has adb-root option available in ADB? I like to play with adb/to add things to /etc/hosts .

Or should i install as extra SuperSu?
[Fire Original Android Development] DragonFire1024:
See if play services need updated. If not, it will eventually last for a less amount of time. I usually only see it last for a longer period just following installation. it's not really an issue. It will always happen now. Sometimes more, sometimes less.
[Fire Original Android Development] Reynald0:
Wait for download also here, after flashed latest gapps-pico-04-18-19

Regards.

I tested downloading vlc, the wait time was of about 1-2 minutes, then started.
[Fire Original Android Development] ggow:
Maybe it should settle down after some time. I don't use gapps so can't comment. I can only say when using fdroid or Aurora Store downloads work just fine.