Develop Bugs

[ROM][MTK][STOCK] fairphone FP1 kitkat 4.4.4

This is Android 4.4.4 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).
It includes various security fixes on top of 4.4.4 - but most likely not all. Major security hole detectors are green now (VTS, Bluebox, Zimperium).
NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!
Without much ado...
To install...
- Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
- Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/filedl/devs...mhoffmann/fp1-kk-stock/fp1-kk444-CH-0.9.7.zip MD5sum: 9140c93ff8f2b8327fdd330d2448c16f
- I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
- You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711
Bugs:
- IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?
- CTS is complaining about some issues. https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml
- As this is a merge of 4.4.4 into the MTK stuff, watch out for more bugs than the previous release. Not merged: the new 4.4.4 dialer screen (we stick with 4.4.2 dialer as the modifications are too heavy), chromium does not support wml anymore (who cares?).
- You most likely need to wipe to install this when coming from the previous KK version to 4.4.4. Email app e.g. seems to crash without.
- Playstore version of Google Authenticator does not work (see https://github.com/google/google-authenticator-android/pull/4). Use the OSS version https://github.com/google/google-authenticator-android/releases - this is not specific to FP1 but seems an MTK issue.
- A dirty update (without wipe) from 0.8 on an encrypted device seems to reboot once during the "Android is upgrading" dialog
- Sometimes the lower part of the homescreen launcher seems to lose transparency.
Changelog fp1-kk444-CH-0.9.7 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-MAY-2016 (https://source.android.com/security/bulletin/2016-05-01.html)
- Kernel CVEs including the mediatek wifi ones from https://source.android.com/security/advisory/2016-03-18.html, CVE-2016-2549, CVE-2016-2847, CVE-2016-2547, CVE-2016-2546, CVE-2016-2545, CVE-2016-2384
Changelog fp1-kk444-CH-0.9.6 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 2-APR-2016 (https://source.android.com/security/bulletin/2016-04-02.html)
- Kernel CVEs including the one from https://source.android.com/security/advisory/2016-03-18.html, CVE-2015-7550, CVE-2016-0774, CVE-2016-0821, CVE-2016-0723.
Changelog fp1-kk444-CH-0.9.5 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-MAR-2016 (https://source.android.com/security/bulletin/2016-03-01.html)
(incl. the kernel fixes that Google only publishes for Google One / Sprout - ported to MT6589)
Changelog fp1-kk444-CH-0.9.4 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-FEB-2016 (http://source.android.com/security/b...016-02-01.html)
- Kernel CVE CVE-2015-8785
Changelog fp1-kk444-CH-0.9.3:
- Android Security Updates from Google bulletin 1-JAN-2015 (http://source.android.com/security/bulletin/2016-01-01.html)
- Some kernel CVEs (CVE2015-8543, CVE2015-8575, CVE2015-7509)
- Attempt to fix German's E-PLUS on O2 roaming
Changelog fp1-kk444-CH-0.9.2:
- Fix that you can now call funny numbers like *143# without phone application crash
- Fix to be able to add contacts to SIM card
Changelog fp1-kk444-CH-0.9.1:
- several kernel CVEs (CVE-2015-5697, CVE-2015-8539, CVE-2015-8215, and a few more without CVE yet)
- the december 1st security advisory bulletin skia issue introduced in 0.9.0 - aka as the dilbert bug - is fixed now
Changelog fp1-kk444-CH-0.9:
- android security bulletin https://source.android.com/security/bulletin/2015-12-01.html
- also update gapps if you install them: http://opengapps.org/?api=4.4&variant=nano
Changelog fp1-kk444-CH-0.8:
- google location providers are used now, which should enable network location provider (in case you installed google apps).
Changelog fp1-kk444-CH-0.7:
- National roaming should be fixed (at least as good as CM). If you still have issue with national roaming, send me your mmc/mmn data.
- Use original FP1 lens parameters for fm50af lens - does this improve the auto/manual focus issues that some people reported compared to stock FP jellybean?
- Attempt to fix the problem where sometimes the scrollbar and recents screen stopped working and screen locked despite having higher screen timeouts.
- Full CTS result: https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml
Changelog fp1-kk444-CH-0.5:
- SELinux enforcing
- Camera app now shows all resolutions
- adb now requires acceptance of adb key
Changelog fp1-kk444-CH-0.4:
- ro.adb.secure set
- browser default pages revisited (removed wrong thumbnail).
- removed MTK root CAs that are not in AOSP
- fixed remaining security false-positives in VTS and Bluebox Trustable - all green now
- USB default setting should be MTP now
Changelog fp1-kk444-CH-0.3:
- More CVE fixes (e.g CVE-2015-3845). VTS and Bluebox Trustable are almost green. For some reasons they still think "Stagefright" is not fixed. Zimperium nevertheless shows all stagefright OK. Edit: found out why. It's false positive as MTK reports errors in MPEG4Extractor differently than stock.
Changelog fp1-kk444-CH-0.2:
- Netflix issue fixed with new blob from E3
- Some CTS issues fixed
- More security fixes CVE-2014-7911
Changelog fp1-kk444-CH-0.1:
- Upgraded to 4.4.4_r2.0.1: Yay! That was an insane amount of work. The following "shortcuts" were taken:
-- Chromium sources taken from AOSP - MTK added wml but it was too much work to merge this back in
-- Email app sources taken from aosp - MTK customized something there esp. exchange sync, is that really giving someone problems?
-- Dialer app taken from MTK without 4.4.4 updates - that stuff is too heavily customized also for dual sim, and 4.4.4 revamped the UI, so this was just too much work for now.
- Latest security fixes up to November 2015. Security fixes also for wpa_supplicant_8 (thanks to Michael Bestas for collecting them for CM)
- Kernel sec fixes
- FP1 power profile xml (does this actually change anything)
As usual some credits:
- @Santhosh M : for some advice on the modem/baseband
- @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
- @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
- @CyanogenMod for the stagefright fixes
Let me know if
- it works also on older FP1 (without U).
- you have problems with your IMEI, too
- if you find other major issues
- if you think I am missing some security updates
- i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.

Reserved - why do all people do this?

chrmhoffmann said:
This is Android 4.4.2 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).
It includes various security fixes on top of 4.4.2 - but most likely not all.
NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!
Without much ado...
To install...
- Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
- Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/devs/chrmhoffmann/fp1-kk-stock
- I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
- You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711
Bugs:
- IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?
As usual some credits:
- @Santhosh M : for some advice on the modem/baseband
- @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
- @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
- @CyanogenMod for the stagefright fixes
Let me know if
- it works also on older FP1 (without U).
- you have problems with your IMEI, too
- if you find other major issues
- if you think I am missing some security updates
- i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.
Click to expand...
Click to collapse
so far it works on my fp1 (without U), no Problems with my IMEI-Numbers. Thank you very very much, great!

Just flashed it and it works! Thank you so much! (although instructions how to create such a rom would be nice for me )
EDIT: some answers to your question:
I am using the FP1u.
No problems with my IMEI.
Other major issues: none noticed, and this actually fixed the transparency bug in the Play Store
Missing security patches: Stagefright CVE-2015-6602 is not fixed.
Thank you very much!

How do i flash the recovery? the typicall fastboot method does not work for me (says "flash not supported")

fredflegel said:
How do i flash the recovery? the typicall fastboot method does not work for me (says "flash not supported")
Click to expand...
Click to collapse
There's an old thread about it: http://forum.xda-developers.com/showthread.php?t=2615613
So in this case:
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/recovery
And because I can never remember if it's volume up or down when powering on: "Hold the Volume Up button, while at the same time press and hold the Power button. Hold these two buttons at the same time for about 10 seconds until the screen changes."
Then install from sideload, etc. and
Code:
adb sideload fp1-kk-stock-0.1.zip
Takes quite a while to update. I did NOT disable rom recovery, I don't think this one reverts the recovery, right?
aaaand
Sound and bluetooth seem to work fine, didn't test more so far.
Edit: By the way, are you going to do a Lollipop rom? That would be even more awesome than this. Meanwhile: Good job for raising the FP1 software to the minimum requirements for today.

Great Work! Thanks alot!
I will check this rom thoroughly. On little cosmetic issue that was fixed in Fairphones official rom is the issue with national roaming in german 02/E-Plus networks. I now allowed data roaming as a workaround, but this can get pretty expensive pretty soon. Any chance you can fix that in a future build?

fredflegel said:
Great Work! Thanks alot!
I will check this rom thoroughly. On little cosmetic issue that was fixed in Fairphones official rom is the issue with national roaming in german 02/E-Plus networks. I now allowed data roaming as a workaround, but this can get pretty expensive pretty soon. Any chance you can fix that in a future build?
Click to expand...
Click to collapse
You can enable "National data roaming" with GravityBox, which you can install via the Xposed installer. Helped in Austria with bob (and A1)

You forgot to mount the "external" storage:
Code:
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0
Workaround for getting the correct one for now:
Code:
umount /storage/emulated
mount -t vfat /dev/block/mmcblk0p8 /storage/emulated
But there are still symlinks to /storage/emulated/legacy.
So that needs some kind of fix up.

ccxxx said:
You forgot to mount the "external" storage:
Code:
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0
Workaround for getting the correct one for now:
Code:
umount /storage/emulated
mount -t vfat /dev/block/mmcblk0p8 /storage/emulated
But there are still symlinks to /storage/emulated/legacy.
So that needs some kind of fix up.
Click to expand...
Click to collapse
I think that you are using the old non-repartitioned fp1?
There's no such thing as /dev/block/mmcblk0p8 anymore on the repartitioned devices.
Chris

chrmhoffmann said:
I think that you are using the old non-repartitioned fp1?
There's no such thing as /dev/block/mmcblk0p8 anymore on the repartitioned devices.
Chris
Click to expand...
Click to collapse
Uhm, yes, I guess.
TIL https://fairphone.zendesk.com/hc/en-us/articles/201327645-What-is-Fairphone-s-storage-layout-

ccxxx said:
Uhm, yes, I guess.
TIL https://fairphone.zendesk.com/hc/en-us/articles/201327645-What-is-Fairphone-s-storage-layout-
Click to expand...
Click to collapse
You should then upgrade. It's much nicer with a single partition... And as you can see, I don't support the old storage layout any more
Chris

Upgrade to 4.4.4. available
See OP. Please test this. It's an update to android 4.4.4 and lots of additional security fixes.
Oh, and yeah, I recommend to wipe. Email (e.g. and maybe others) will crash without.
Chris

It wasn't obvious, how to do that, so I downloaded the "Storage Upgrader 1.8.7 * (~200MB)" from https://fairphone.zendesk.com/hc/en-us/articles/201189497-Fairphone-OS-multiple-versions-
It doesn't update the partitions when flashing, it does so on the first boot. It also overwrites the recovery.
After that I installed the 4.4.4 image and it boot loops: https://gist.github.com/ChristophHaag/64da8b31533d2c562c92
edit: And so does the 4.4.2 image that has worked before.
*sigh*
edit 2: Formatted a few partitions and tried again - now 4.4.4 works.

0.2 released.
It should fix Netflix (will confirm when all apps are installed after wipe) and should also squash a security problem that bluebox reported (CVE-2014-7911).
It should also make less CTS tests fails.
Still uploading... Edit: Uploaded.
Chris

Hallo, nach dem neuesten update funktioniert xposed-aktivierung nicht mehr. Sonst alles bestens
Sorry, in english:
After the newest update to 4.4.4 no chance to activate xposed-framework. Anyway, thanks a lot
for your hard work

btw Google Authenticator doesn't seem to work correctly on the 4.4.2 version. Authy works though.

jogri said:
Hallo, nach dem neuesten update funktioniert xposed-aktivierung nicht mehr. Sonst alles bestens
Sorry, in english:
After the newest update to 4.4.4 no chance to activate xposed-framework. Anyway, thanks a lot
for your hard work
Click to expand...
Click to collapse
Yes, the last security patches break xposed. https://android.googlesource.com/pl...+/d4d3181d013f8d9b96de8e396b029f8a418894a7^!/
See e.g. here: https://plus.google.com/114407246718577124209/posts/BwiPxSu84bD
Chris

z3ntu said:
btw Google Authenticator doesn't seem to work correctly on the 4.4.2 version. Authy works though.
Click to expand...
Click to collapse
This is most likely related to this issue: https://github.com/google/google-authenticator-android/pull/4
It is most likely an MTK issue with problematic math library (or something like that).
Anyway, it works for me when I use the open source version of the google authenticator: https://github.com/google/google-authenticator-android/releases
Chris

Jeah, I used the Play Store version, but this is also mentionable in "known bugs" (and that they should use the open-source version)

[ROM] [8.1] nAOSProm for Xperia S / Acro S

The purpose of this rom is to provide a rom not so far of the AOSP with some cool features (nAOSP means "near AOSP").
This rom is legacy of @mickybart's work from 5.0 to 7.1 versions. He also did initial rom setup for oreo.
This version is based on @AdrianDC oreo port for huashan/blue devices.
NOTE: Please read this post before flashing b05
nAOSP 8.1 Oreo Changelog
b11
android-8.1.0_r74 (March 2020 security patches)
fixed storage permission grant
gps: fixed location timestamps
bluetooth: display bt device battery level in bt QS tile label
bluetooth: stopped background scan after turning off bluetooth
SystemUI: fixed crash when on some QS tile long press (jack detect,...)
Settings: added 0.25x animations scale to Developer options
b10
android-8.1.0_r70 (November 2019 security patches)
added support for flashing Magisk
b09
fixed boot to charging mode
fixed Bluetooth pairing
b08
android-8.1.0_r65 (June 2019 security patches)
fixed Bluetooth/FM Radio crashes
Previous Builds
b07
android-8.1.0_r63 (April 2019 security patches)
fixed flac playback
b06
android-8.1.0_r62 (March 2019 security patches)
Setup Wizard re-enabled
b05
android-8.1.0_r52 (December 2018 security patches)
Added Superuser permission to App settings
Fixed motion detections
Fixed OTG for Acro S
Fixed nAOSProm settings crashes
Fixed Fast charge QS toggle
Fixed Jack detection QS toggle
Changed Fast charge icon
b04
android-8.1.0_r50 (November 2018 security patches)
added build for Xperia Acro S
Fixed manual network selection
Fixed OTG
Fixed wifi hotspot
Fixed lightbar notifications
Fixed Desk Clock alarm
SystemUI: QS tiles in 3 rows in potrait
SystemUI: Added tiles from nAOSP-7.1
Added nAOSProm options (Settings > System)
Added "About nAOSProm" (nAOSProm options)
Added WakeUp (nAOSP options and System > Gestures)
b03
android-8.1.0_r47 (October 2018 security patches)
Improved stability
Enforced selinux
Fixed soft reboot when turining GPS on
Disabled Setup Wizard
Fixed proximity sensor
Added lineage apps: Jelly, Eleven, Gallery2
Changed boot animation to pixel dark bootanimation
Developer options enabled by default
SystemUI tuner enabled by default
Advanced restart menu enabled by default
b02
android-8.1.0_r46 (September security fixes)
Beta build - relatively stable.
b01 alpha - alpha4
Alpha builds.
Gradualy enable hardware features
Android Go
Selinux permissive
Root
This ROM has built in superuser however since b10 it is also possible to flash Magisk, by using Boot Bridge:
flash BootBridge-Init.zip
flash Magisk zip (currently Magisk-v20.1.zip)
flash BootBridge-Restore.zip
Built in superuser is official/preferred root method and I will not fix issues with Magisk like not being able to reboot to recovery.
Source
nAOSP 8.1 on GitHub
Boot Bridge - GitHub
Downloads
Android File Host - nAOSP 8.1 for Xperia S (nozomi)
Android File Host - nAOSP 8.1 for Xperia Acro S (hikari)
TWRP-3.2.3 for Xperia S
TWRP-3.2.3 for Xperia Acro S
Android File Host - Boot Bridge
Thanks
@mickybart for all of his work on this rom
@AdrianDC for oreo port & Boot Bridge
LineageOS team
TWRP team
All the community around Android

nAOSProm 8.1 screenshots

Features
F2FS support
Advanced Reboot Menu
Integrated superuser
Lineage apps: Jelly, Eleven, Gallery2
Wakeup gestures
Additional quick setting tiles
Customizable number of QS tile columns
nAOSProm settings

Flashing
You need to merge partitions /data and /sdcard (already done if you come from nAOSP 6.0 or 7.x).
Please, read the 6.0 procedure to flash this ROM.
If you come from nAOSP 6.0 or 7.x you should clean flash.
Setup wizard is disabled for this version because of numerous force closes.
For google account setup go to Settings > Users & Accounts > Add account.
Recomended gapps: Open Gapps ARM 8.1 micro (nano, pico)

reserved

Thanks a lot @millosr
I will flash the update this evening and revert with feedback
Btw, any recommended Gapps?

hotspot and otg work?

@millosr Download and flashing and let you know

Hi tnx for your greate work. Which gapp 8.1 is good for this rom??

Abdollah hosh said:
hotspot and otg work?
Click to expand...
Click to collapse
Unfortunately those don't seem to work. I will try to fix them in the next build.
mehdips3 said:
Hi tnx for your greate work. Which gapp 8.1 is good for this rom??
Click to expand...
Click to collapse
I am using OpenGapps micro 8.1 arm.
When clean flashing, flash rom and gapps together. I've disabled setup wizard, so set up account from settings.

@millosr Hi Friend, well friend I did a dirty flash, so far the Rom work fine, proximity sensor is working , not tested yet hot spot or otg. I continue testing and let you know if I found some issues.
thank a lot for this version :good:

@millosr
I am not able to download the zip, its getting stuck within 3 MB download. i tried different mirrors.
Any one else facing problem with downloading zip?

Fir3lordZuk0 said:
@millosr
I am not able to download the zip, its getting stuck within 3 MB download. i tried different mirrors.
Any one else facing problem with downloading zip?
Click to expand...
Click to collapse
Here's alternative download link:
nAOSProm-8.1.0-b03.zip — Yandex.Disk

millosr said:
Here's alternative download link:
nAOSProm-8.1.0-b03.zip — Yandex.Disk
Click to expand...
Click to collapse
Updated to 8.1 b03.
So far so good..thanks

@millosr great work friend..although I m not using xperia s more often these days but still I m visiting xperia s thread frequently. Now I saw this new thread..and with pleasure I congratulate you for your great effort.Thanks

Hi why all naosp rom is laggy on xperia s i use naosp from 5.1

Friendly reminder that 6.0 >b14 had 60fps fix too.

finally, look whos made a new thread.. millosr listens to me.. good work again mate.. thank you..
all other users, is the battery life bad or just the age of the battery taking a toll on the life?

Xperia S battery Life
Seemanthinis said:
all other users, is the battery life bad or just the age of the battery taking a toll on the life?
Click to expand...
Click to collapse
I found the best battery life was gained in Android 5.1 builds at around 5days idle, with only 2-3days idle time on newer 6.0-7.0 builds.
The screens(342ppi) on these older devices chew through the battery so OST will never be that great on any version using an Xperia S, where you're probably counting the time in hours, not days.
I'll have to make a few spiders homeless and fire up my XS and see how it fares with the 'latest' OS.
Thanks @millosr

well after having tried the ROM during this time I can say that it works excellent I made some modifications like using the pixel launcher to install the app duo dialer and pixel (include weather) contacts and all its working perfectly
Excellent work @millosr
Now waiting for the next update

China Stable Pie Rom - no official release yet!

The latest China stable Pie rom V10.2.3.0.PDTCNXM isn't presented at official download website yet.
http://www.miui.com/download-353.html
It is a second Pie China stable rom and none of them is released officialy yet so it is presumable that Global, Xiaomi.Eu and other variants based on Android P are not good as they should be.
quote (google translated) from kuaibao website:
http://kuaibao.qq.com/s/20190329A08HIM00
The problem that is fixed in V10.2.3.0.PDTCNXM is:
Long screen cannot be pulled down to the end;
The processing strategy after the card is not showing in the dual card scenario is optimized.
Fixed the problem of occasionally turning off the floating notification,
the floating notification still shows the problem, and the problem that the charging circle overlaps with the expected charging time when the screen is locked;
In the setting, the synchronization page is clicked, the synchronization is invalid, and the mobile phone name is set to the maximum length,
Hotspot. The problem that can't be opened;
There is the problem of fixing the file open after cutting the picture video in the private folder in the file manager.
This update has a lot of bug fixes.
However, some say that the update package they received was 1.9G. Why is the same model phone different? In fact, this is a problem left over when the previous Android P was pushed. Due to several bugs, the package was later removed, and some users did not receive the Android P update. This time, after the repair, xiaomi pushed Android P again, users who have not updated Android P before have received the 1.9GB update package. The ones that have updated the Android P, they received the 223MB update package.
Click to expand...
Click to collapse
https://hugeota.d.miui.com/V10.2.3.0.PDTCNXM/miui_MI8Lite_V10.2.3.0.PDTCNXM_d6a7ddabb7_9.0.zip
https://bigota.d.miui.com/V10.2.3.0.PDTCNXM/miui_MI8Lite_V10.2.3.0.PDTCNXM_d6a7ddabb7_9.0.zip
list of releases:
V10.2.3.0.PDTCNXM (Latest)
V10.2.3.0.ODTCNXM
V10.2.2.0.ODTCNXM
V10.2.1.0.PDTCNXM (Rolled back)
V10.0.8.0.ODTCNFH
V10.0.7.0.ODTCNFH
V9.6.6.0.ODTCNFD
* PDT - Pie
ODT - Oreo

Just an update:
There are official Pie downloads now, the latest stable is :
V10.3.3.0.PDTCNXM (MIUI10) Size: 2.0G

[UNOFFICIAL][ROM] LineageOS 17.1 for Galaxy Tab E [SM-T560NU]

I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading posts 1, 2, and 3 before posting.
Try this build at your own risk. It's likely to have bugs and is EXPERIMENTAL as 17.1 is a work in progress. It boots and seems to work fine on my SM-T560NU, but I have only tested it for 24 hours. Problems will likley surface later?
BACKUP YOUR FILES and have a copy of your working image BEFORE trying my build.
I built a new image of SM-T560NU following the instructions at
https://wiki.lineageos.org/devices/gtelwifiue/build
What works.
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. Google play store (using gapps pico)
Known problems.
1. stock camera
Stock LineageOS camera app back camera does not display properly. It is split into 8 frames. Use opencamera apk from
https://f-droid.org/en/packages/net.sourceforge.opencamera/
I will not be spending anytime trying to fix the stock camera problem. I never use it and opencamera works.
2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.
3. FM Radio is not support since this device doesn't have the LTE functionality.
4. text on home screen looks funny. This only seems to affect the home screen and nowhere else. Problem is with stock trebuchet launcher and/or its fonts. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.
I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?
https://f-droid.org/en/packages/amirz.rootless.nexuslauncher/

Dec 14, 2021 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:Q_asb_2021-12
2. Whatever LiineageOS changed since last November release (about 4,400 files had to be recompiled).
Nov 8, 2021 release notes
1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318647
2. Whatever LiineageOS changed since last October release (about 5,100 files had to be recompiled).
Oct 10, 2021 release notes
1. Oct 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317410
2. Whatever LiineageOS changed since last Sept release (about 4,200 files had to be recompiled).
Sept 16, 2021 release notes
1. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/316083
2. Whatever LiineageOS changed since last August release (about 49,000 files had to be recompiled).
Aug 7, 2021 release notes
1. August 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/314572
2. Whatever LiineageOS changed since last July release (about 5000 files had to be recompiled).
July 12, 2021 release notes
1. July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313448
2. Whatever LiineageOS changed since last June release (about 4500 files had to be recompiled).
June 15, 2021 release notes
1. June 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/312240
2. Whatever LiineageOS changed since last May release (about 6000 files had to be recompiled).
May 9, 2021 release notes
1. May 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309564
2. Whatever LiineageOS changed since last April release.
April 12, 2021 release notes
1. April 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307454
2. Whatever LiineageOS changed since last March release. Nearly 59,000 out of the 70,000 files had to be recompiled due to the last set of changes.
Release notes for March 7, 2021
1. Mar 5 security patches.
2. Whatever LiineageOS changed since last February release.
Release notes for Feb 11, 2021
1. Feb 5 security patches.
2. Whatever LineageOS changed since last Jan 2021 update.
3. fixed audio over bluetooth. Problem was one variable pointing to the wrong audio directory which was changed in 17.1.
Release notes for Jan 14, 2021
1. Jan 5 security patches.
2. Whatever LineageOS changed since last Dec 2020 update.
Release notes for Dec 14, 2020
1. Dec 5 security patches
2. Changed some error messages to verbose to stop spamming log files
3. Whatever LineageOS changed since last Nov update
Release notes for Nov 7, 2020
1. Nov 5 security patches
Release notes for Oct 8, 2020
1. Oct 5 security patches
Release notes for Sept 15, 2020
1. Sept 5 security patches
2. added on screen nav buttons (you can change via settings)
Release notes for Aug 26, 2020
1. add fix for missing some play store apps (I have removed the Aug 20 build)
2. changed build fingerprint to a stock fingerprint
Release notes for Aug 20, 2020
1. initial release
2. initial testing, have no idea about long term stability
3. bug with hal hwbinder vibrator that causes tablet to be stuck at boot logo animation (have removed hal vibrator for now)
4. msm8916 kernel overclocked CPU to 1.6Ghz in kernel with 17.1 by default
5. incoporates aug 5 security patches

FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1) What TWRP should I use?
A1) Use 3.2.3 found at
https://msm8916.com/?view=downloads&dist_name_short=TWRP&codename=gtelwifiue
Or use 3.5.2_9 that I built.
retiredtab - Browse /SM-T560NU/TWRP at SourceForge.net
sourceforge.net
Q2) Does the build work on xyz?
A2) I have no idea. I only have the SM-T560NU. It will not work on the SM-T561 and SM-T560 as it uses a different SoC (CPU).
Q3) Application xyz doesnt' work. Can you fix it?
A3) I only fix what I use. If you use app xyz and it doesn't work, then try 16.0 or going back to the last rom that worked for you.
Q4) My tablet hangs or crashes with 17.1. This build is slow and buggy. Can you fix it?
A4) Go back to the last working stable rom for you. 17.1 is a work in progress and will have bugs and frequent changes.
Q5) Do you plan to update the rom?
A5) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.
Q6) Can you build this for the SM-T560?
A6) No, I don't have the SM-T560.
Q7) Can I turn off the on screen navigation keys?
A7) To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation.
Q8) Can I build this rom? Where are the source and kernel source files?
A8) Yes. The kernel source files are at
Samsung MSM8916 Devices
Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.
github.com
I have attached the repo diff and roomservice.xml file that I have used. The repo diff are all the changes I have made to the "stock" msm8916 code.
Q9) Where can I download this rom?
A9) The 2020 builds are at
https://www.androidfilehost.com/?w=files&flid=315153
I'm moving to sourceforge for all 2021 uploads. The main reason is that I would like to see the stats of where this rom is being downloaded from worldwide. All 2020 builds will remain on androidfilehost.
2021 builds at
retiredtab - Browse /SM-T560NU/17.1 at SourceForge.net
sourceforge.net

Thanks for building this, downloading it now. Do you use opengapps or mindthegapps?

sillycat98 said:
Do you use opengapps or mindthegapps?
Click to expand...
Click to collapse
I tested opengapps pico and micro-g on the 16.0 build, but not on the 171. build.

retiredtab said:
Q5)This build is slow and buggy. Can you fix it? A5) Go back to the last working stable rom for you. 17.1 is a work in progress and will have bugs and frequent changes.
Click to expand...
Click to collapse
Isn't everything on this tablet slow and buggy? Even the stock rom was horrible for me. Think I might try mindthegapps when I get home. Any problems I'll swap over to opengapps.

sillycat98 said:
Isn't everything on this tablet slow and buggy? Even the stock rom was horrible for me. Think I might try mindthegapps when I get home. Any problems I'll swap over to opengapps.
Click to expand...
Click to collapse
This tablet isn't my daily driver so I have no reference if it's slow. I just got it and it happens to share some of the same code base as the SM-T350.
If this tablet is slow, it could be due to google services (gapps). You can always try microg. It's a way of running some Google services, but with a lighter set of software and some privacy.
https://microg.org/
I ran microg on this tablet with 16.0 and it seemed to work fine.

Runs great, the only problem I'm having is with one magisk module to spoof the props. It bootloops if I use it to change the fingerprint and I can't figure out why. Any ideas?

sillycat98 said:
Runs great, the only problem I'm having is with one magisk module to spoof the props. It bootloops if I use it to change the fingerprint and I can't figure out why. Any ideas?
Click to expand...
Click to collapse
I have only seen the need to change fingerprint to pass google's CTS. Is this what you are trying to do?
Does it bootloop with 16.0?

For boot loops, undo your changes.
Then unlock developer options, enable adb debugging and adb root. Then reboot tablet, re-enable your changes, reboot again and get a logcat while it's booting. It should show error messages in the logcat.
That's how I was able to figure out the vibrator hal causing a bootloop on the 560NU.

retiredtab said:
I have only seen the need to change fingerprint to pass google's CTS. Is this what you are trying to do?
Does it bootloop with 16.0?
Click to expand...
Click to collapse
It is what I was trying and it didn't with 16 but I can live without it, I'll just have to download what I want to my phone and extract the apks then transfer when over.
retiredtab said:
For boot loops, undo your changes.
Then unlock developer options, enable adb debugging and adb root. Then reboot tablet, re-enable your changes, reboot again and get a logcat while it's booting. It should show error messages in the logcat.
That's how I was able to figure out the vibrator hal causing a bootloop on the 560NU.
Click to expand...
Click to collapse
I'll try to get a logcat later.

sillycat98 said:
It is what I was trying and it didn't with 16 .
Click to expand...
Click to collapse
For 17.1, it's possible that a lineageos change in the future will fix the boot loop since 17.1 is still a work in progress.
Or what we did for the sm-t350, is we used a stock fingerprint and over rode the fingerprint to pass CTS. If I can get a stock SM-T560NU fingerprint, I can look at putting it into the 17.1 code. It's a single line of code in one of the mk files. It looks like this for the 350.
BUILD_FINGERPRINT=samsung/gt58wifixx/gt58wifi:7.1.1/NMF26X/T350XXU1CQJ1:user/release-keys
That spoofs play store into thinking its "certified" Samsung device.
Source:
https://github.com/Evervolv/android...mmit/5ad790d570e1c18e0706a7b2ce121e5c58ba79ba

BTW, if it works on 16.0, I plan to do monthly security patch builds for 16.0 as well, so you can stay on 16.0 if that makes life easier for you.
I'm likely to run 17.1 just to keep testing and again because 17.1 is a work in progress by the Lineageos team.

As I mentioned, this is NOT my daily driver tablet and I just got it and I wanted to run only microg and not use any gapps. As such, I didn't test gapps. Now that I loaded gapps and google plays store, I do see a problem. I will try to fix it over the next few days. I will update post #1 to reflect potential problems with google play store.
Google play store works in my 16.0 build. So if you need Google play store, use 16.0 for now.
For future builds, I will test goolge play store before releasing another build.

Looks like this is a known issue with the msm8916 team as per github (June 25th, 2020).
https://github.com/Galaxy-MSM8916/android_device_samsung_msm8916-common/pull/43
"Google PlayStore not showing some apps fix #43" Thanks for continuing, there is a fix on the way.

The fix at
https://github.com/ArbabAliRajper/a...mmit/73e686a841cb282299b97c133f097dfa2256706b
# Google Play Store
PRODUCT_PROPERTY_OVERRIDES += \
ro.opengles.version=196608
works. I can see more apps at the play store. I'll build this fix into the next September build after all the security patches are incorporated.
I don't know when msm8916 team will incorporate it or do something different.

I uploaded an Aug 26 build with the play store fix as per above and changed the build fingerprint. If I just use Magisk and enable hide Magisk, it passes CTS and shows as a "device is certified" in play store.
You may have to delete the files and cache in google play services and google play store to get rescanned for CTS.
I removed the Aug 20 build.

retiredtab said:
I uploaded an Aug 26 build with the play store fix as per above and changed the build fingerprint. If I just use Magisk and enable hide Magisk, it passes CTS and shows as a "device is certified" in play store.
You may have to delete the files and cache in google play services and google play store to get rescanned for CTS.
I removed the Aug 20 build.
Click to expand...
Click to collapse
Sorry for the delay, been busy the last few days. I appreciate you looking at it, this is the best this tablet has worked since I bought the thing. The main reason I wanted to go to 17.1 is Android 10 supports Bluetooth dual shock for remote play and 16 didn't. So I really appreciate everything you are doing. I wish I could afford to give you a little something, you deserve it, but unfortunately I can't at the moment. Let me know if you need anything from me though.
Edit: I hate to keep bothering you but is there any way to turn on the on-screen nav bar? I hate those buttons at the bottom and disabled them but I'm having some difficulty with XDA's navigation gestures, I'm used to my Pixel and I can't quite get it setup correctly.

sillycat98 said:
but is there any way to turn on the on-screen nav bar?
Click to expand...
Click to collapse
I'll add
qemu.hw.mainkeys=0
to the September security patch build.
For now, if you have Magisk installed, the easiest way to get on screen nav bar is goto Magisk Manager, menu, downloads, search for props, dowload and install and reboot.
Once rebooted, go settings, about tablet, tap build number 7 times to enable developer settings. Then system, advanced, developer options, enable local terminal.
Then go home, choose terminal app and type "props".
Choose 5 (add custom props), n (new), qemu.hw.mainkeys, enter, 0, enter.
Screen should say this will set qemu.hw.mainkeys to: 0
Press y to accept and reboot.
Your screen nav bar should appear after reboot.
Then goto settings, system, advanced, gestures, system navigation.
navigation bar settings are at buttons menu to let you swap (invert) the back and recent menu buttons to match hardware buttons.
Yes, I tested the above and there are no boot loops while adding this prop or use the prop editor that is downloaded from Magisk.

retiredtab said:
I'll add
qemu.hw.mainkeys=0
to the September security patch build.
For now, if you have Magisk installed, the easiest way to get on screen nav bar is goto Magisk Manager, menu, downloads, search for props, dowload and install and reboot.
Once rebooted, go settings, about tablet, tap build number 7 times to enable developer settings. Then system, advanced, developer options, enable local terminal.
Then go home, choose terminal app and type "props".
Choose 5 (add custom props), n (new), qemu.hw.mainkeys, enter, 0, enter.
Screen should say this will set qemu.hw.mainkeys to: 0
Press y to accept and reboot.
Your screen nav bar should appear after reboot.
Then goto settings, system, advanced, gestures, system navigation.
navigation bar settings are at buttons menu to let you swap (invert) the back and recent menu buttons to match hardware buttons.
Yes, I tested the above and there are no boot loops which adding this prop or use the prop editor that is downloaded from Magisk.
Click to expand...
Click to collapse
Thanks again, this worked a treat. I had used props to change the fingerprint before but had never messed with the custom option. I finally have a reason to use this tablet again thanks to you.
You rock.

Tab S3 T820 security version

So yesterday I installed LineageOS 17.1 on my Tab S3 (T820). Installation went without a lot of problems, but when I booted into the system for the first time, I got a notification about the security version. I clicked the notification to see what's up. Turns out I'm running a security patch from February 5, 2020
(See screenshots in link)
imgur (dot) com/a/yBfDlnH
I already tried updating via several buttons, but no luck.
Is there any way for me to update this manually to a new security patch? Or is it not needed?

MrDanMan said:
So yesterday I installed LineageOS 17.1 on my Tab S3 (T820). Installation went without a lot of problems, but when I booted into the system for the first time, I got a notification about the security version. I clicked the notification to see what's up. Turns out I'm running a security patch from February 5, 2020
(See screenshots in link)
imgur (dot) com/a/yBfDlnH
I already tried updating via several buttons, but no luck.
Is there any way for me to update this manually to a new security patch? Or is it not needed?
Click to expand...
Click to collapse
It's not about patch level. It says "signed with public keys" that's typical for unofficial builds.
The patch levels can only be updated by building a new installation zip. Vendors patch level only if manufacturer releases an update and developer includes updated components.

kurtn said:
It's not about patch level. It says "signed with public keys" that's typical for unofficial builds.
The patch levels can only be updated by building a new installation zip. Vendors patch level only if manufacturer releases an update and developer includes updated components.
Click to expand...
Click to collapse
So there is no way for me to update to a newer security version (for example September 2020)?

MrDanMan said:
So there is no way for me to update to a newer security version (for example September 2020)?
Click to expand...
Click to collapse
Way 1 - search
Way 2 - wait
Way 3 - build