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

Search This thread

jodabonito

New member
Apr 11, 2016
1
0
Hello Chris, i would like to spent some money for this great work. Do you have an official bank account or something....
 

nrnrn

New member
May 5, 2016
2
0
When downloading this image, avast reports the "Android/Gedma-c" trojan in this image
I find it somewhat strange that nobody else reported this. Is there any info on this?

Until this is resolved I won't be installing this, although this seems like a great ROM
 

z3ntu

Member
May 2, 2015
26
5
When downloading this image, avast reports the "Android/Gedma-c" trojan in this image
I find it somewhat strange that nobody else reported this. Is there any info on this?

Until this is resolved I won't be installing this, although this seems like a great ROM

I am pretty sure, that this is a false positive.
 

manu_26

Member
Apr 23, 2014
35
13
When downloading this image, avast reports the "Android/Gedma-c" trojan in this image
I find it somewhat strange that nobody else reported this. Is there any info on this?

Until this is resolved I won't be installing this, although this seems like a great ROM
You could check what specific file in the image causes your scanner to report a positive. And then upload the file to virustotal.com. That way you can check almost every antivirus scanner available and hopefully see that it's most likely a false positive.
 
  • Like
Reactions: z3ntu

chrmhoffmann

Inactive Recognized Developer
Nov 11, 2006
941
3,154

chrmhoffmann

Inactive Recognized Developer
Nov 11, 2006
941
3,154
Hi to all.

Does anyone know if Bluetooth 4 LE now works with the current fp1-kk444-CH-0.9.5?
With fp1-kk444-CH-0.9.4 I have problems with some BT 4 LE devices like fitbit flex. According to some research this is a bug.

thank you.

No, Bluetooth LE does indeed not work. I have tried a few things, but couldn't find any solution.

Chris
 
  • Like
Reactions: koerma

Josemofly

New member
May 10, 2016
1
0
Fairphone FP1

Hello,
I bought a FP1 long time ago. Now I got a smartwatch and I need the version of Android 4.3 at least.
I was looking for information in website of Fair Phone, also in Forums like this, how I could do by myself...
I do not have a real good skill with PCs, cellphones, etc.
I would appreciate if you could address me to other easier tutorial (easier = people with my knowledge), even better it would be if you could add screenshots, etc.
Thanks in advance and also for making large the lifes of our cellphones (philosophy which I thought that also Fair Phone company used to share).
J
 

stereok

New member
Mar 12, 2016
2
0
Hello,
I bought a FP1 long time ago. Now I got a smartwatch and I need the version of Android 4.3 at least.
I was looking for information in website of Fair Phone, also in Forums like this, how I could do by myself...
I do not have a real good skill with PCs, cellphones, etc.
I would appreciate if you could address me to other easier tutorial (easier = people with my knowledge), even better it would be if you could add screenshots, etc.
Thanks in advance and also for making large the lifes of our cellphones (philosophy which I thought that also Fair Phone company used to share).
J

I suggest you check out the tutorial "HOWTO Testing the latest UNOFFICIAL 4.4.4 ROM and switching back to FP OS again [for Unix & FP1]" at the official Fairphone Forum.
That tutorial is pretty straight forward and includes this ROM.

Regards,
Markus
 

jogri

Member
May 14, 2015
28
5
53
When downloading this image, avast reports the "Android/Gedma-c" trojan in this image
I find it somewhat strange that nobody else reported this. Is there any info on this?

Until this is resolved I won't be installing this, although this seems like a great ROM

No Problem, it depends on two files in /system/app; smsreg.apk and smsreg.odex. Look at "https://forum.fairphone.com/t/unofficial-stock-rom-android-4-4-2-4-4-4-kitkat-for-fp1-fp1u/10788/119". These two files are also in the original Fairphone OS. Just delete them after the installation of the rom.
Joachim
 

nrnrn

New member
May 5, 2016
2
0
No Problem, it depends on two files in /system/app; smsreg.apk and smsreg.odex. Look at "https://forum.fairphone.com/t/unofficial-stock-rom-android-4-4-2-4-4-4-kitkat-for-fp1-fp1u/10788/119". These two files are also in the original Fairphone OS. Just delete them after the installation of the rom.
Joachim

Sorry for the late reply. I extracted the image and checked again, and the malicious files are
Code:
system/app/SmsReg.apk        // Android:Gedma-C [Trj] 
system/priv-app/Settings.apk // Android:Rooter-CS [PUP]
The results on virustotal.com are mixed, but I'm wary if even one AV reports a file.
I checked against the FP1U stock ROM and a Nexus 4.4.4 stock ROM, which have no AV alerts in these files.
Actually the FP1U rom has reports for Andr/Gedma-A in SmsReg.apk, but less & different than chrmhoffmann's rom.

After reading about SmsReg.apk, I thought about deleting it. Can it be deleted from the zip before flashing the ROM?
I suppose the rooter in Settings.apk is of no concern, but I'd like confirmation on that, as the default FP1U rom goes without it.

Generally, I find the amount of trust required here at XDA baffling:
  • There are links posted to some 3rd-party image for flashing, without reference to an author or anything
  • ROMs are uploaded to some 4th-party site (at least here it wasn't mega.nz & chrmhoffmann posted some MD5 hash :good:)
  • Nobody ever seems to talk about security concerns
Now a ROM seems to contain at least one trojan, and I should not be worried?
I don't know much about android development, but wouldn't it be possible to provide the sources somewhere, so the image can be checked & compiled by a 3rd party?
 

Marco3K

Member
Feb 15, 2009
5
1
Hi,
Just trying to flash the Rom (fp1-kk444-CH-0.9.7) on my FP1U, seems to work, but when I installed Gapps (arm 4.4, nano or micro pack from opengapps ), I lost the keyboard.

It prompts continuously "...AOSP Keyboard has stopped...".

I can't get where I'm wrong, I did wipe /data, /cache & Dalvik (even if I'm not very sure if needed).

anybody that have some ideas ?
 

Marco3K

Member
Feb 15, 2009
5
1
Hi,
First of all a very big thanks for your work, it is really nice to see some support for newer android version for the Fairphone.

I have to say (and I will say to the the fairphone team) a phone without long term software support cannot be sustainable, ethical or anything.

i'm only here to report a minor bug. Here, in France, the provider "Free" often use the network from "Orange".

The 0.9.7 consider it as roaming with all limitation, which is not very cool for an unlimited plan.
In the Stock rom from Fairphone, There was a "National roaming" concept which was pretty useful to sort these kind of issue.

Hopes it get corrected in the futur.
Thank you very much.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 27
    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.
    8
    0.7

    0.7 changelog:
    - fix the R - oaming symbol for some virtual operators (like Free in France)
    - Use fm50AF lens params from original FP - does this make auto focus better?
    - Fix lock screen issue (thx @Quallenauge for the reproducible test case from Google Maps navigation). This fixes at least one pattern that broke the slider and recents screen. I am not sure if this fixes all those issues, but I hope so :)

    Give it a go!
    Chris
    7
    0.9.6 released. Changelog see OP.

    Chris
    6
    0.9.1 released...

    It fixes:
    - several kernel CVEs
    - the december 1st security advisory bulletin skia issue introduced in 0.9.0 - aka as the dilbert bug
    6
    0.9.4 released. Changelog: See OP